Page 1 of 16

System Requirements Document for neuro

1. Introduction

This document outlines the system requirements for the Healthopia Clinical AI Platform. The platform is designed to enhance clinical workflows, integrate with existing systems, and provide AI-driven insights for clinicians and patients. The focus is on the clinical portal, AI backend, data integrations, and API handoff with the existing NEURO World Flutter app.

2. System Overview

The Healthopia Clinical AI Platform will deliver a clinician-facing portal, integrate with existing EMR/EHR systems, and provide AI-driven insights and recommendations. It will also facilitate data handoff with the NEURO World app, enabling a seamless flow of clinical and wearable data.

2a. Product Interpretation and Delivery Boundary

The Healthopia Clinical AI Platform is designed to function as a clinical intelligence layer within the NEURO/Healthopia ecosystem. It will not rebuild the existing NEURO World app but will integrate with it through API handoffs. The platform will support six specific roles with permission-driven access and will adhere to the organization structure of Organization → Site → Panel → Patient. The platform will not invent new scores, thresholds, or values but will rely on backend data for visualization.

2b. Source Content Inventory

Not applicable as no explicit content_source directive was provided.

Page 2 of 16

2c. Page Content and Component Coverage

Landing

Purpose: Introduce Healthopia and its clinical intelligence purpose.
Components: Overview of platform benefits, introductory video or image, call-to-action for clinicians to learn more.

Login

Purpose: Allow provisioned clinical portal users to verify their identity.
Components: Username and password fields, forgot password link, login button.

Home

Purpose: Serve as the permission-driven clinical portal home.
Components: Attention review, alerts, pending actions, meaningful changes, navigation links.

Patients

Purpose: Allow browsing of assigned patients and panels.
Components: Patient list, search and filter options, patient detail link.

Alerts

Purpose: Review and acknowledge CRITICAL, ELEVATED, and WATCH signals.
Components: Alert list, evidence details, acknowledgement actions.

Actions

Purpose: Manage exception-based clinician Action Queue.
Components: Action list, follow-up actions, status updates.

Page 3 of 16

Referrals

Purpose: Handle patient referrals and responses.
Components: Referral list, status updates, action buttons.

Clinical Tools

Purpose: Access Clinical Copilot and related clinical tools.
Components: Evidence review, recommendation lifecycle management.

Administration

Purpose: Operational administration for authorized governance.
Components: Organization management, role assignments, site management.

Overview

Purpose: Provide a patient profile overview.
Components: Status, attention state, changes, pillars, trajectory, alerts, actions, recent activity.

Clinical Summary

Purpose: Detail patient clinical summary.
Components: Concise status, context, summary details.

Brain Health

Purpose: Detail patient brain-health with five pillars.
Components: Nutrition, Exercise, Unwind, Restore, Optimize, Cognitive Trajectory.

Page 4 of 16

Assessments

Purpose: Review patient assessments and manage workflows.
Components: Assessment list, status, action buttons.

Wearables

Purpose: Show patient wearable and connected-data trends.
Components: Data trends, freshness indicators, device status.

Timeline

Purpose: Display patient event and completion history.
Components: Event list, timestamps, audit context.

Population

Purpose: Provide authorized population oversight.
Components: Risk filters, site filters, panel filters, pillar filters.

Rule Governance

Purpose: Manage rule configuration and governance.
Components: Rule list, enable/disable actions, version history.

Coverage & On-Call

Purpose: Oversee configured coverage and escalation.
Components: Coverage periods, escalation paths, fallback options.

Page 5 of 16

Organization

Purpose: Manage organization, site, clinician, and panel administration.
Components: Organization list, site management, clinician roles.

Crisis Escalation

Purpose: Review crisis escalation status and history.
Components: Crisis list, current owner, escalation state.

Referral

Purpose: Detail and respond to patient referrals.
Components: Referral details, status updates, response actions.

Consent & Capacity

Purpose: Manage consent, data scopes, and capacity.
Components: Consent status, effective dates, representative details.

Patient Administration

Purpose: Manage patient administrative state and assignments.
Components: Administrative details, clinician assignments, linking status.

Standing Orders

Purpose: Review configured conditional clinical authorizations.
Components: Standing order list, permitted actions, status updates.

Page 6 of 16

3. Functional Requirements

Clinical Scope Discovery and Integration

As a system architect, I want to confirm the final clinical scope to ensure alignment with project goals.
As a system architect, I want to define the system boundary between Healthopia and NEURO World to clarify responsibilities.
As a project manager, I want to define clinical portal user roles and workflows to streamline operations.
As a developer, I want to create an API handoff plan between NEURO World and Healthopia to ensure smooth data exchange.
As a product manager, I want to define a subscription-gated clinical access flow to manage user access.
As a data analyst, I want to map clinical data sources to ensure comprehensive data integration.
As a developer, I want to confirm EMR/EHR access assumptions to plan integration strategies.
As a developer, I want to confirm wearable data access assumptions to ensure data availability.
As a clinician, I want to confirm clinical assessment requirements to ensure they meet clinical needs.
As a project manager, I want to finalize the technical architecture and delivery roadmap to guide development.

Page 7 of 16

Healthopia Clinical Portal

As a clinician, I want a clinician-facing portal to access patient information and insights.
As a clinician, I want a dashboard to view key metrics and alerts.
As a clinician, I want a patient list/roster to manage my patients efficiently.
As a clinician, I want a 360° patient view to understand patient history and context.
As a clinician, I want a clinical summary view to quickly assess patient status.
As a clinician, I want an AI insights view to receive data-driven recommendations.
As a clinician, I want a wearable and health data view to monitor patient activity.
As a clinician, I want a clinical assessment results view to evaluate patient progress.
As a clinician, I want a timeline view to track patient events and interactions.
As a clinician, I want a clinical nudge/action queue to prioritize tasks.
As a clinician, I want a prompt and recommendation area to receive actionable insights.
As a security officer, I want secure role-based access to protect sensitive data.
As a compliance officer, I want audit-ready clinician activity logging to ensure accountability.

NEURO World App Data Handoff

As a developer, I want an API contract for receiving NEURO World user data to facilitate integration.
As a developer, I want to intake data from existing app systems to enrich clinical insights.
As a data analyst, I want to support input categories like user profile data, behavioral metrics, and wearable data to provide comprehensive insights.
As a developer, I want to normalize data into the Healthopia clinical backend to ensure consistency.
As a data analyst, I want to map timestamp, source, and consent metadata to maintain data integrity.

Page 8 of 16

Subscription-Gated Patient Clinical Layer

As a product manager, I want a clinical access/unlock model to manage user subscriptions.
As a developer, I want an API contract to validate clinical subscription entitlement to control access.
As a UI/UX designer, I want to define patient-facing clinical screen requirements to guide design.
As a UI/UX designer, I want to create a clinical module UI/UX where required to enhance user experience.
As a product manager, I want a clinical home/patient clinical dashboard concept to centralize patient information.
As a clinician, I want a pending clinical actions view to track patient tasks.
As a clinician, I want an assigned clinical assessments view to manage patient evaluations.
As a patient, I want clinician recommendations reflected back in the app to understand my care plan.
As a developer, I want to integrate a patient-facing clinical chatbot/avatar to provide support.

Clinical Assessment Workflow

As a clinician, I want a clinical assessment catalog structure to organize assessments.
As a clinician, I want to trigger assessment assignments to evaluate patients.
As a patient, I want a completion flow for assessments to provide my responses.
As a developer, I want to store clinical assessment responses to maintain records.
As a data analyst, I want to normalize assessment results to ensure consistency.
As a clinician, I want follow-up assessment chain support to manage ongoing evaluations.
As a clinician, I want to track pending assessment status to monitor patient progress.
As a clinician, I want assessment completion timeline entries to document patient activity.
As a developer, I want an API contract for the Flutter team to show pending clinical assessments to ensure integration.

Page 9 of 16

Clinician-to-App Action Write-Back

As a developer, I want a care action write-back API to update patient tasks.
As a clinician, I want to trigger task assignments to guide patient care.
As a clinician, I want to trigger assessment assignments to evaluate patient progress.
As a developer, I want a suggested goal/action update API to modify patient goals.
As a clinician, I want to track patient pending action status to monitor task completion.
As a developer, I want an app notification/action handoff contract to ensure patient engagement.
As a developer, I want a completion status return path from the app to the clinical portal to update records.
As a compliance officer, I want an audit log for clinician-generated actions to ensure accountability.

EMR/EHR and Clinical Data Integration

As a developer, I want an EMR/EHR/FHIR-ready ingestion architecture to integrate clinical data.
As a developer, I want initial read-only clinical data ingestion to access patient records.
As a project manager, I want Epic/Athena/FHIR integration scoping to plan system connections.
As a developer, I want a clinical data adapter pattern to standardize data intake.
As a developer, I want a lab result ingestion structure to incorporate lab data.
As a developer, I want a medication, diagnosis, visit, and note ingestion structure to enrich patient records.
As a security officer, I want secure clinical data normalization to protect patient information.
As a data analyst, I want source metadata and timestamp tracking to maintain data integrity.
As a developer, I want access logging and audit trails to ensure compliance.
As a developer, I want error handling for unavailable or limited EMR APIs to manage integration issues.

Page 10 of 16

Wearable and Connected Device Data Sync

As a developer, I want a wearable data ingestion service to collect patient activity data.
As a developer, I want a Fitbit/supported wearable sync architecture to integrate device data.
As a developer, I want scheduled background sync jobs to update data regularly.
As a developer, I want webhook handling where supported to receive real-time updates.
As a developer, I want to track connected device status to monitor data availability.
As a developer, I want to record the last sync timestamp to ensure data freshness.
As a data analyst, I want a data freshness indicator to assess data relevance.
As a developer, I want normalized wearable metrics storage to maintain consistency.
As a clinician, I want wearable metrics available to the clinical portal and AI layer to inform care decisions.

Clinical Data Normalization Layer

As a developer, I want a unified clinical data schema to standardize data formats.
As a developer, I want a normalized patient record model to ensure consistency.
As a developer, I want normalized wearable metrics to integrate device data.
As a developer, I want normalized assessment results to maintain data integrity.
As a developer, I want normalized app behavioral signals to enrich patient profiles.
As a developer, I want timestamp standardization to synchronize data.
As a developer, I want unit conversion to ensure data compatibility.
As a developer, I want source metadata to track data origins.
As a developer, I want data freshness indicators to assess data relevance.
As a developer, I want data quality checks to ensure accuracy.
As a developer, I want duplicate handling to maintain data integrity.
As a developer, I want sync status and error tracking to monitor data flow.
As a developer, I want to convert app data into a consistent structure for use by the clinical portal and AI systems.

Page 11 of 16

Graph Memory / Patient Knowledge Graph

As a developer, I want a graph memory architecture to connect patient data.
As a developer, I want a Graphiti/Neo4j or equivalent graph memory setup to manage relationships.
As a developer, I want a patient knowledge graph schema to organize data.
As a developer, I want a node and relationship model for patients, wearable metrics, clinical records, labs, assessments, app behavior signals, game/assessment scores, clinical summaries, clinician actions, AI insights, nudges, timeline events, and consent/source metadata to structure data.
As a developer, I want versioned health states to track patient changes.
As a developer, I want time-aware relationships to understand data context and when it changed.
As a developer, I want evidence traceability to support clinical decisions.
As a developer, I want retrieval logic for current, relevant patient context.

4. User Personas

RN Care Coordinator

The RN Care Coordinator manages assigned patients and panels, triages alerts, follows up on assessments and tasks, and performs actions under standing orders when permitted. They cannot automatically sign clinical recommendations.

Signing Clinician

The Signing Clinician is responsible for reviewing, editing, approving, and signing clinical recommendations. They acknowledge clinical alerts where permitted and may manage standing orders.

Page 12 of 16

Neurologist

The Neurologist specializes in neurological and cognitive workups, reviews deterioration, and handles relevant referrals. They may review or sign recommendations and manage standing orders where authorized.

Neuropsychologist

The Neuropsychologist performs cognitive and neuropsychological assessments, reviews cognitive results and trajectory, and receives relevant referrals without prescribing authority.

Medical Director

The Medical Director oversees clinical operations at the organization and site levels, focusing on Population View, Rule Governance, and governance functions without assuming patient-level clinical actions.

Administrator

The Administrator handles non-clinical operations, including organization, site, clinician, panel, and patient administration, without clinical decision authority unless explicitly permitted.

Patient

The Patient is the subject of the clinical records, whose care, clinical status, alerts, assessments, referrals, consent, and capacity information are managed through the platform.

Page 13 of 16

5. Core User Flows

RN Care Coordinator: Managing Alerts

Starting Context: RN Care Coordinator logs into the Healthopia Clinical Portal.
Home Page: Reviews the list of patients needing attention and alerts.
Alerts Page: Selects an alert to view details.
Alert Details: Reviews evidence, acknowledges the alert, and decides on follow-up actions.
Next Step: Updates the patient's status and returns to the Home Page.

Signing Clinician: Approving Recommendations

Starting Context: Signing Clinician logs into the portal.
Home Page: Navigates to the Clinical Tools section.
Clinical Tools Page: Reviews pending recommendations.
Recommendation Details: Edits and approves the recommendation.
Next Step: Sends the approved recommendation and logs the action.

Neurologist: Reviewing Cognitive Workups

Starting Context: Neurologist accesses the portal.
Patients Page: Selects a patient with cognitive alerts.
Patient Overview: Reviews cognitive workup details.
Next Step: Updates the patient record with findings and recommendations.

Page 14 of 16

Neuropsychologist: Conducting Assessments

Starting Context: Neuropsychologist logs into the portal.
Assessments Page: Selects an assessment to conduct.
Assessment Details: Completes the assessment and records results.
Next Step: Submits the assessment for review and updates the patient's timeline.

Medical Director: Overseeing Population Health

Starting Context: Medical Director logs into the portal.
Population Page: Applies filters to view risk-tiered patient data.
Population Overview: Reviews population health metrics and trends.
Next Step: Adjusts governance rules as needed and logs changes.

Administrator: Managing Clinician Assignments

Starting Context: Administrator accesses the portal.
Administration Page: Navigates to clinician management.
Clinician Management: Updates clinician roles and assignments.
Next Step: Saves changes and updates the organization structure.

6. Visuals Colors and Theme

Muse: Yves Béhar
Palette: Background #F1F0EE, Surface #FFFFFF, Text #333333, Primary #D95F02, Accent #66A61E, Muted #E6E6E6
Typography: Headings in Work Sans, Body in Karla, Scale 1.5 modular
Shape Language: Rounded product-led heroes and soft cards
Layout: Clean editorial layout with modular panels
Imagery: Real-life product imagery with natural light
Hero Direction: Editorial hero with a primary image of clinician interaction

Page 15 of 16

7. Signature Design Concept

The public entry page will feature a large hero section with a clinician interacting with the portal, emphasizing empathy and care. Rounded cards with soft shadows will separate content areas, and integrated contextual tabs will facilitate navigation. Generous whitespace will enhance readability, and subtle color accents will highlight critical information.

8. Interaction Model & Motion Direction

Interaction Model: Static
Motion Tempo: Restrained
Hero Dimensionality: Layered_2d
Landing Hero Motion Brief: A composed first frame featuring a clinician interacting with the portal, with a focus on empathy and care. Reduced-motion state will maintain clarity and focus.

9. Non-Functional Requirements

Security: Role-based access control, audit-ready logging, and secure data handling.
Performance: Efficient data processing and real-time updates where applicable.
Compliance: Adherence to HIPAA and other relevant regulations.
Scalability: Support for growing user base and data volume.

Page 16 of 16

10. Tech Stack

Frontend: React
Backend: Python/FastAPI
Database: PostgreSQL
Containerization: Docker
Orchestration: Kubernetes (if required for deployment)

11. Assumptions and Constraints

The platform will not rebuild the existing NEURO World app.
Patient assignment and care-team linkage are manual processes.
The platform will not invent new scores, thresholds, or values.
Existing APIs, authentication, and workflows will be preserved.

12. Glossary

AI Insights: Data-driven recommendations provided by the platform.
Clinical Copilot: A tool for clinicians to receive AI-generated insights and recommendations.
EMR/EHR: Electronic Medical Record/Electronic Health Record systems.
FHIR: Fast Healthcare Interoperability Resources, a standard for healthcare data exchange.
RN Care Coordinator: A registered nurse responsible for managing patient care and coordination.
Signing Clinician: A clinician authorized to approve and sign clinical recommendations.

neuro

Comments (0)