Phase 0 foundation

Care Platform

Staff-facing control layer for patient management, protocols, diet operations, and content governance.

Platform work surfaces

Approved module routes

Patients

Longitudinal clinical record with app-user compatibility, care team, studies, protocols, plans, encounters, outcomes, labs, and safety context.

Practitioner workspace

Scaffold

Organizations

Tenant boundary for partner clinics and Emma-owned operations, with scoped patients, practitioners, access, and billing summaries.

Platform operations

Scaffold

Practitioners

Staff and practitioner access with platform roles, org memberships, MFA, invites, BAA acknowledgment, and quarterly review.

Access management

Existing surface

Studies

Research overlays with IRB metadata, cohorts, consent versions, eligibility gates, and study enrollment status.

Research operations

Scaffold

Protocols

Versioned clinical templates that own phases, diet definitions, sensitivity thresholds, and algorithm rule mappings.

Clinical programs

Prototype only

Plan Review

Clinical queue for per-element review, edits, regeneration, approval, scheduling, publish notifications, and audit events.

Clinical review

Prototype only

Algorithm Registry

Data-driven clinical logic: lab marker templates, compound rules, STOP rules, patient input questions, libraries, IP vocabulary, and dry-run simulator.

Clinical logic

Existing surface

Food Intelligence

Protocol-scoped food, recipe, ingredient, evidence, provenance, and phase-readiness operations.

Nutrition operations

Prototype only

Outcomes

Individual and cohort views tying interventions, adherence, symptoms, marker changes, and responder status back to protocol outcomes.

Clinical analytics

Identity and tenant primitives

Primitive	State	Operational meaning
Staff realm	Phase 0 active	Admin login can use StaffIdentity, StaffOtp, and StaffSession while legacy admin tokens remain allowed in dual mode.
Patient identity mirror	Dual-write ready	Patient creation and updates can mirror dbo.Users into Patient and PatientIdentity without breaking app users.
dbo.Users retained	Compatibility protected	Web, iOS, and Android can continue using the existing user contract while platform tables are introduced.
Organization anchor	Seeded primitive	System organization and practitioner records give the platform a tenant-safe place to attach staff and patients.

Care queues

Protocol intelligenceRules and simulator evidence Operational visibilityActions and audit coverage Ops monitorStudy and kit health Eligibility reviewClinical gating Diagnosis reviewProvider verification Kit ordersLab logistics

Next API layer should expose patient-practitioner assignment, staff roster, protocol versioning, and tenant-scoped audit events.