Slice → Epic → Story Mapping

Execution-layer artifact. Companion to ROADMAP.md and module backlog specs in specs/modules/.

This document maps every module epic to the slice and milestone that delivers it. Each mapping includes cross-service dependencies, AI-first requirements, offline-first requirements, security + multi-tenant requirements, and testing + observability gates. Sprint-ready backlog tables follow each slice section.

0. Conventions

• Slice IDs map to milestones: S0→M0, S1→M1, S2→M2, S3→M3, S4→M4, S5→M5.
• Story status per slice is one of: impl (full implementation), stub (minimal, will mature later), back-compat (maintain unchanged), deferred (not in this slice).
• Epic IDs use module prefixes: IAM-EPIC-01, REG-EPIC-01, DESK-EPIC-01, etc.
• Story IDs use module prefixes: IAM-US-001, REG-US-001, DESK-US-001, etc.
• Every story already has its full AC + DoD in the module's backlog/UNIFIED_USER_STORIES.md; this doc adds slice-scoped scope and dependency detail.
• Jira project: GEHR on ghasitech.atlassian.net

---

1. Epic-to-Slice Map (authoritative)

S0 — Platform Foundation (M0)

Module	Epics in S0	Track
iam	IAM-EPIC-01 through IAM-EPIC-05	baseline
tenant	TEN-EPIC-01 through TEN-EPIC-08	baseline
hierarchy	HIER-EPIC-01 through HIER-EPIC-05	baseline
licensing	LICN-EPIC-01 through LICN-EPIC-04	baseline
access-policy	ACPOL-EPIC-01 through ACPOL-EPIC-04 (baseline)	baseline
audit	AUD-EPIC-01 through AUD-EPIC-05	baseline
config-resolver	CFG-EPIC-01 through CFG-EPIC-06	baseline
fhir-gateway	FHIR-EPIC-01 (skeleton)	baseline
terminology	TERM-EPIC-01 (seed data)	baseline
ai-orchestrator	AIO-EPIC-01 (skeleton gateway)	baseline
platform-admin	PADM-EPIC-01 through PADM-EPIC-03 (baseline)	baseline
desktop-electron	DESK-EPIC-01 (shell + auth + IPC), DESK-EPIC-02 (SQLite + outbox + sync)	baseline

S1 — Core Clinical (M1)

Module	Epics in S1	Track
registration	REG-EPIC-01 through REG-EPIC-06	baseline
scheduling	SCHED-EPIC-01 through SCHED-EPIC-08	baseline
provider-directory	PROV-EPIC-01 through PROV-EPIC-05	baseline
facility-management	FAC-EPIC-01 through FAC-EPIC-06	baseline
patient-chart	PCHART-EPIC-01 through PCHART-EPIC-07	baseline
clinical-notes	CNOTE-EPIC-01 through CNOTE-EPIC-04	baseline
vitals	VIT-EPIC-01 through VIT-EPIC-04	baseline
problem-list	PROB-EPIC-01 through PROB-EPIC-05	baseline
allergies	ALG-EPIC-01 through ALG-EPIC-04	baseline
medication-management	MED-EPIC-01 through MED-EPIC-05	baseline
desktop-electron	DESK-EPIC-03 (EHR core vertical slice)	baseline
ai-orchestrator	AIO-EPIC-02 (clinical AI features)	baseline

S2 — Orders & Diagnostics Entry (M2)

Module	Epics in S2	Track
orders-cpoe	ORD-EPIC-01 through ORD-EPIC-06	baseline
results	RES-EPIC-01 through RES-EPIC-05	baseline
terminology	TERM-EPIC-02 through TERM-EPIC-06 (full code systems)	baseline
billing	BILL-EPIC-01 through BILL-EPIC-02 (basic)	baseline
document-management	DOC-EPIC-01 through DOC-EPIC-08 (core)	baseline
desktop-electron	DESK-EPIC-03 (orders extension)	baseline

S3 — Integrated Care (M3)

Module	Epics in S3	Track
laboratory-lis	LAB-EPIC-01 through LAB-EPIC-06	baseline
pharmacy	PHARM-EPIC-01 through PHARM-EPIC-05	baseline
ghasi-e-prescribing-gateway	EPRESC-EPIC-01 through EPRESC-EPIC-05	baseline
patient-portal-api	PPORT-EPIC-01 through PPORT-EPIC-05 (estimated)	baseline
digital-communication	DCOM-EPIC-01 through DCOM-EPIC-11	baseline
insurance	INS-EPIC-01 through INS-EPIC-04 (eligibility + pre-auth)	baseline
desktop-electron	DESK-EPIC-04 (LIS), DESK-EPIC-05 (pharmacy)	baseline

S4 — Full Platform (M4)

Module	Epics in S4	Track
radiology-pacs	RAD-EPIC-01 through RAD-EPIC-05	baseline
billing	BILL-EPIC-03 through BILL-EPIC-05 (full)	baseline
claims	CLM-EPIC-01 through CLM-EPIC-04	baseline
insurance	INS-EPIC-05 through INS-EPIC-08 (full)	baseline
health-population	HPOP-EPIC-01 through HPOP-EPIC-10	baseline
immunizations	IMMZ-EPIC-01 through IMMZ-EPIC-05	baseline
care-plans	CP-EPIC-01 through CP-EPIC-04	baseline
hl7v2-interop	HL7-EPIC-01 through HL7-EPIC-03 (estimated)	baseline
ai-orchestrator	AIO-EPIC-03 (full: ONNX + cloud)	baseline
access-policy	ACPOL-EPIC-05 through ACPOL-EPIC-07 (ABAC depth)	enhancement
desktop-electron	DESK-EPIC-06 (imaging), DESK-EPIC-08 (billing), DESK-EPIC-09 (pop health), DESK-EPIC-10 (AI ONNX)	baseline

S5 — National Scale (M5)

Module	Epics in S5	Track
All services	Hardening epics, L4 gate completion	enhancement
platform-admin	PADM-EPIC-04 through PADM-EPIC-07 (multi-region, white-label)	enhancement
terminology	TERM-EPIC-07, TERM-EPIC-08 (national terminology, extensions)	enhancement
document-management	DOC-EPIC-09 through DOC-EPIC-12 (OCR, advanced)	enhancement
registration	REG-EPIC-07 through REG-EPIC-11 (enhancements)	enhancement
desktop-electron	DESK-EPIC-11 (hardening + a11y + perf + lazy bundles)	baseline

---

2. Slice 0 — Platform Foundation (M0)

2.1 Epics in scope

IAM: IAM-EPIC-01 (Keycloak integration), IAM-EPIC-02 (user provisioning), IAM-EPIC-03 (MFA), IAM-EPIC-04 (session management), IAM-EPIC-05 (audit events) Tenant: TEN-EPIC-01 through TEN-EPIC-08 (full tenant lifecycle) Hierarchy: HIER-EPIC-01 through HIER-EPIC-05 (DAG org units) Licensing: LICN-EPIC-01 through LICN-EPIC-04 (module entitlement) Access-Policy: ACPOL-EPIC-01 through ACPOL-EPIC-04 (RBAC baseline + policy engine) Audit: AUD-EPIC-01 through AUD-EPIC-05 (tamper-evident logging) Config-Resolver: CFG-EPIC-01 through CFG-EPIC-06 (tenant config, themes, flags) FHIR Gateway: FHIR-EPIC-01 skeleton (resource routing, search proxy) Terminology: TERM-EPIC-01 (seed: ICD-10, LOINC, SNOMED CT basics) AI Orchestrator: AIO-EPIC-01 (gateway routes, prompt registry, safety classifier) Platform-Admin: PADM-EPIC-01 through PADM-EPIC-03 (user mgmt, tenant ops, system health) Desktop-Electron: DESK-EPIC-01 (shell + auth + IPC), DESK-EPIC-02 (SQLite + outbox + sync)

2.2 Cross-service dependencies

• iam depends on Keycloak for OIDC; all services depend on iam for JWT validation.
• tenant depends on iam for user lookup on provisioning; all services depend on tenant for tenant context.
• hierarchy depends on tenant for tenant scoping.
• licensing depends on hierarchy for node-level entitlements; all services depend on licensing for ModuleEntitlementGuard.
• access-policy depends on iam (roles) + hierarchy (org units) + licensing (module access).
• audit consumes events from all services (no hard dependency; event-driven).
• config-resolver depends on tenant + hierarchy for config inheritance.
• fhir-gateway routes to all clinical services (stub endpoints at M0).
• ai-orchestrator depends on tenant for budget records + access-policy for AI feature entitlement.
• desktop-electron depends on iam (OIDC) + tenant (context) + sync engine (all services that publish replicable aggregates).

2.3 AI-first requirements (slice-scoped)

• AI gateway live with complete, embeddings, moderate, redact-pii routes.
• Prompt registry with versioned system prompts (safety classifier, PII redactor test harness, admin copy generation).
• Provenance invariant enforceable by domain helper — all AI outputs tagged with model, prompt version, timestamp.
• Budget math per tenant functional (quota tracking, degradation threshold).
• Local-inference SDK stub (returns "not-ready" to validate port).

2.4 Offline-first requirements (slice-scoped)

• Desktop Electron shell boots offline (cached auth token, SQLite ready).
• SQLite initialized with tenant-scoped schema + migrations.
• Sync engine functional: outbox queues mutations, pull fetches server state, conflict resolution per aggregate policy.
• Idempotency via client mutation IDs across all mutations.
• PHI encrypted at rest in SQLite.
• Stale-data age indicator in UI components.
• Device binding: desktop device registered with server; unregistered devices cannot sync.

2.5 Security + multi-tenant requirements

• Two-tenant CI suite (verify cross-tenant isolation).
• RBAC baseline: roles defined per Keycloak realm.
• ABAC skeleton: access-policy evaluates basic policies.
• Audit log hash chain integrity test.
• PHI encryption at rest (server PostgreSQL + client SQLite).
• Kong JWT validation on all routes.
• Rate limiting per tenant on all public endpoints.

2.6 Testing + observability

• Contract tests for all NATS event schemas.
• E2E: tenant provision → user invite → OIDC login → desktop launch → SQLite init → sync round-trip.
• Load test: 100 concurrent users, 2 tenants, API p95 < 500ms.
• Prometheus + Grafana dashboards for all M0 services.
• OTel tracing across Kong → service → NATS → consumer.

2.7 Sprint-ready backlog

#	Epic/Story	Owner Team	Dep	Est	Sprint
1	IAM-EPIC-01: Keycloak OIDC integration	Platform	—	13pts	S0-Sprint 1
2	TEN-EPIC-01: Tenant lifecycle CRUD	Platform	IAM	8pts	S0-Sprint 1
3	HIER-EPIC-01: Hierarchy DAG model	Platform	TEN	8pts	S0-Sprint 1–2
4	LICN-EPIC-01: Module entitlement engine	Platform	HIER	8pts	S0-Sprint 2
5	AUD-EPIC-01: Tamper-evident audit core	Security	—	8pts	S0-Sprint 1–2
6	DESK-EPIC-01: Electron shell + OIDC	Desktop	IAM	13pts	S0-Sprint 1–2
7	ACPOL-EPIC-01: RBAC policy engine	Platform	IAM+HIER	8pts	S0-Sprint 2–3
8	CFG-EPIC-01: Config resolver core	Platform	TEN+HIER	5pts	S0-Sprint 2
9	FHIR-EPIC-01: Gateway skeleton	Platform	—	8pts	S0-Sprint 2–3
10	DESK-EPIC-02: SQLite + outbox + sync	Desktop	DESK-01	21pts	S0-Sprint 2–4
11	AIO-EPIC-01: AI orchestrator skeleton	AI	TEN+ACPOL	13pts	S0-Sprint 3–4
12	TERM-EPIC-01: Terminology seed data	Platform	FHIR-GW	5pts	S0-Sprint 3
13	PADM-EPIC-01: Platform admin baseline	Platform	TEN+IAM	8pts	S0-Sprint 3–4
14	TEN-EPIC-02–08: Tenant depth	Platform	TEN-01	13pts	S0-Sprint 3–5
15	LICN-EPIC-02–04: Licensing depth	Platform	LICN-01	8pts	S0-Sprint 4–5
16	AUD-EPIC-02–05: Audit depth	Security	AUD-01	8pts	S0-Sprint 4–5
17	CFG-EPIC-02–06: Config depth	Platform	CFG-01	8pts	S0-Sprint 4–5
18	Kong + Keycloak hardening	DevOps	—	5pts	S0-Sprint 5–6
19	Two-tenant CI suite	QA	All S0	8pts	S0-Sprint 5–6
20	Sync E2E validation	Desktop+Platform	DESK-02	5pts	S0-Sprint 5–6

S0 total: ~6 sprints (2-week sprints = 12 weeks ≈ 3 months)

---

3. Slice 1 — Core Clinical (M1)

3.1 Epics in scope

Registration: REG-EPIC-01 through REG-EPIC-06 (patient CRUD, duplicate detection, multi-identifier, demographics, photo, FHIR Patient) Scheduling: SCHED-EPIC-01 through SCHED-EPIC-08 (appointments, calendars, check-in, waitlist, recurring, FHIR Appointment/Schedule) Provider-Directory: PROV-EPIC-01 through PROV-EPIC-05 (clinician CRUD, credentials, specialties, FHIR Practitioner) Facility-Management: FAC-EPIC-01 through FAC-EPIC-06 (locations, departments, beds, FHIR Location/Organization) Patient-Chart: PCHART-EPIC-01 through PCHART-EPIC-07 (longitudinal chart aggregation, history tabs, timeline) Clinical-Notes: CNOTE-EPIC-01 through CNOTE-EPIC-04 (SOAP notes, templates, signing, FHIR DocumentReference) Vitals: VIT-EPIC-01 through VIT-EPIC-04 (capture, trending, alerts, pediatric growth, FHIR Observation) Problem-List: PROB-EPIC-01 through PROB-EPIC-05 (active/historical, ICD-10 coding, FHIR Condition) Allergies: ALG-EPIC-01 through ALG-EPIC-04 (recording, severity, reactions, safety alerts, FHIR AllergyIntolerance) Medication-Management: MED-EPIC-01 through MED-EPIC-05 (prescribing, safety checks, interaction alerts, FHIR MedicationRequest) Desktop-Electron: DESK-EPIC-03 (EHR core vertical slice: registration, scheduling, chart, notes) AI-Orchestrator: AIO-EPIC-02 (clinical AI: note suggestions, drug safety enrichment, terminology coding)

3.2 Cross-service dependencies

• registration depends on tenant + hierarchy for scoping; emits patient.registered event consumed by patient-chart, scheduling.
• scheduling depends on registration (patient), provider-directory (provider), facility-management (location/resource).
• patient-chart aggregates from registration, clinical-notes, vitals, problem-list, allergies, medication-management via FHIR gateway.
• clinical-notes depends on patient-chart (encounter context), registration (patient reference).
• vitals, problem-list, allergies, medication-management depend on registration (patient reference).
• medication-management depends on allergies for drug-allergy checks + terminology for RxNorm.
• desktop-electron DESK-EPIC-03 depends on all clinical services + sync engine.

3.3 AI-first requirements (slice-scoped)

• AI note auto-suggestion: given chief complaint → suggest SOAP structure.
• AI drug-allergy cross-check: enrich allergy alerts with AI analysis.
• AI ICD-10 coding: suggest diagnosis codes from free-text notes.
• Prompts registered + versioned in prompt registry.
• Provenance tag on all AI suggestions visible in note history.
• Graceful degradation: AI features hidden when unavailable (not error state).

3.4 Offline-first requirements (slice-scoped)

• Patient registration works fully offline (draft → outbox → sync).
• Appointment viewing from cached schedules.
• Patient chart browsing from FHIR bundle cache.
• Clinical note drafting offline → sync on reconnect.
• Vital signs capture offline.
• Allergy + problem recording offline.
• Medication list viewing offline.
• Conflict resolution: LWW for demographics; server-authority for clinical data.
• Stale-data age indicator: "Last synced X minutes ago" in UI.

3.5 Sprint-ready backlog

#	Epic/Story	Owner Team	Dep	Est	Sprint
1	REG-EPIC-01: Patient CRUD + FHIR	Clinical	S0	13pts	S1-Sprint 1–2
2	PROV-EPIC-01: Provider CRUD + FHIR	Clinical	S0	8pts	S1-Sprint 1
3	FAC-EPIC-01: Facility/Location CRUD	Clinical	S0	8pts	S1-Sprint 1
4	SCHED-EPIC-01: Appointment CRUD	Clinical	REG+PROV+FAC	13pts	S1-Sprint 2–3
5	PCHART-EPIC-01: Chart aggregation	Clinical	REG	13pts	S1-Sprint 2–3
6	CNOTE-EPIC-01: SOAP notes + signing	Clinical	PCHART	13pts	S1-Sprint 3–4
7	VIT-EPIC-01: Vital signs capture	Clinical	REG	8pts	S1-Sprint 2–3
8	PROB-EPIC-01: Problem list CRUD	Clinical	REG+TERM	5pts	S1-Sprint 3
9	ALG-EPIC-01: Allergy recording	Clinical	REG+TERM	5pts	S1-Sprint 3
10	MED-EPIC-01: Medication prescribing	Clinical	REG+ALG+TERM	13pts	S1-Sprint 3–4
11	DESK-EPIC-03: Desktop EHR core	Desktop	All clinical	21pts	S1-Sprint 2–5
12	AIO-EPIC-02: Clinical AI features	AI	CNOTE+MED	8pts	S1-Sprint 4–5
13	Remaining depth epics (REG-02–06, SCHED-02–08, etc.)	Clinical	Core epics	34pts	S1-Sprint 3–6
14	Pilot clinic deployment + testing	Ops+QA	All S1	8pts	S1-Sprint 5–6

S1 total: ~6 sprints (2-week sprints = 12 weeks ≈ 3 months)

---

4. Slice 2 — Orders & Diagnostics Entry (M2)

4.1 Epics in scope

Orders-CPOE: ORD-EPIC-01 through ORD-EPIC-06 (order types, safety checks, routing, FHIR ServiceRequest) Results: RES-EPIC-01 through RES-EPIC-05 (reception, trending, critical alerts, FHIR DiagnosticReport/Observation) Terminology: TERM-EPIC-02 through TERM-EPIC-06 (full code systems, search, mapping) Billing: BILL-EPIC-01 through BILL-EPIC-02 (charge capture, invoicing) Document-Management: DOC-EPIC-01 through DOC-EPIC-08 (templates, scanning, PDF, storage)

4.2 Cross-service dependencies

• orders-cpoe depends on registration (patient), provider-directory (ordering provider), medication-management (drug orders), terminology (order codes).
• results depends on orders-cpoe (order reference), terminology (result codes).
• billing depends on orders-cpoe (charge triggers), registration (patient), terminology (CPT/ICD codes).
• document-management depends on registration (patient reference), tenant (storage config).

4.3 Sprint-ready backlog

#	Epic/Story	Owner Team	Dep	Est	Sprint
1	ORD-EPIC-01: Lab order CRUD	Clinical	S1	13pts	S2-Sprint 1–2
2	ORD-EPIC-02: Radiology orders	Clinical	ORD-01	8pts	S2-Sprint 2
3	TERM-EPIC-02: Full code systems	Platform	S0	13pts	S2-Sprint 1–2
4	RES-EPIC-01: Result reception	Clinical	ORD-01	13pts	S2-Sprint 2–3
5	ORD-EPIC-03–06: Safety + routing	Clinical	ORD-01+02	13pts	S2-Sprint 3–4
6	RES-EPIC-02–05: Trending + alerts	Clinical	RES-01	13pts	S2-Sprint 3–4
7	BILL-EPIC-01: Charge capture	Finance	ORD	8pts	S2-Sprint 3–4
8	DOC-EPIC-01–04: Templates + scanning	Clinical	S1	13pts	S2-Sprint 2–4
9	BILL-EPIC-02: Invoicing	Finance	BILL-01	8pts	S2-Sprint 4–5
10	DOC-EPIC-05–08: PDF + storage	Clinical	DOC-01–04	8pts	S2-Sprint 4–5
11	Desktop offline orders	Desktop	ORD+RES	8pts	S2-Sprint 4–5
12	First revenue validation	Product+Finance	BILL	5pts	S2-Sprint 5–6

S2 total: ~6 sprints

---

5. Slice 3 — Integrated Care (M3)

5.1 Epics in scope

Laboratory-LIS: LAB-EPIC-01 through LAB-EPIC-06 Pharmacy: PHARM-EPIC-01 through PHARM-EPIC-05 E-Prescribing Gateway: EPRESC-EPIC-01 through EPRESC-EPIC-05 Patient-Portal-API: Patient portal epics (record access, appointments, results, messaging) Digital-Communication: DCOM-EPIC-01 through DCOM-EPIC-11 Insurance: INS-EPIC-01 through INS-EPIC-04 (eligibility, pre-auth) Desktop-Electron: DESK-EPIC-04 (LIS), DESK-EPIC-05 (pharmacy)

5.2 Sprint-ready backlog

#	Epic/Story	Owner Team	Dep	Est	Sprint
1	LAB-EPIC-01: LIS core + worklists	Diagnostics	S2 (orders)	21pts	S3-Sprint 1–3
2	PHARM-EPIC-01: Dispensing core	Pharmacy	S1 (meds)	13pts	S3-Sprint 1–2
3	EPRESC-EPIC-01: E-prescribing bridge	Interop	PHARM+MED	13pts	S3-Sprint 2–3
4	DCOM-EPIC-01–05: Messaging core	Engagement	S0	21pts	S3-Sprint 1–3
5	Patient portal: Record access	Engagement	S1 (chart)	13pts	S3-Sprint 2–4
6	LAB-EPIC-02–06: Instruments + QC	Diagnostics	LAB-01	21pts	S3-Sprint 3–5
7	PHARM-EPIC-02–05: Full dispensing	Pharmacy	PHARM-01	13pts	S3-Sprint 3–5
8	EPRESC-EPIC-02–05: Gateway depth	Interop	EPRESC-01	13pts	S3-Sprint 3–5
9	INS-EPIC-01–04: Eligibility + pre-auth	Finance	REG	13pts	S3-Sprint 3–5
10	DCOM-EPIC-06–11: Virtual care + notif	Engagement	DCOM-01–05	13pts	S3-Sprint 4–6
11	DESK-EPIC-04: Desktop LIS	Desktop	LAB	8pts	S3-Sprint 4–5
12	DESK-EPIC-05: Desktop pharmacy	Desktop	PHARM	8pts	S3-Sprint 4–5
13	Hospital pilot deployment	Ops+QA	All S3	8pts	S3-Sprint 5–6

S3 total: ~6 sprints

---

6. Slice 4 — Full Platform (M4)

6.1 Epics in scope

Radiology-PACS: RAD-EPIC-01 through RAD-EPIC-05 Billing (full): BILL-EPIC-03 through BILL-EPIC-05 Claims: CLM-EPIC-01 through CLM-EPIC-04 Insurance (full): INS-EPIC-05 through INS-EPIC-08 Health-Population: HPOP-EPIC-01 through HPOP-EPIC-10 Immunizations: IMMZ-EPIC-01 through IMMZ-EPIC-05 Care-Plans: CP-EPIC-01 through CP-EPIC-04 HL7v2-Interop: HL7v2 adapter epics AI-Orchestrator (full): AIO-EPIC-03 Access-Policy (ABAC depth): ACPOL-EPIC-05 through ACPOL-EPIC-07 Desktop: DESK-EPIC-06, 08, 09, 10

6.2 Sprint-ready backlog

#	Epic/Story	Owner Team	Dep	Est	Sprint
1	RAD-EPIC-01–02: Imaging core + DICOM	Diagnostics	S2 (orders)	21pts	S4-Sprint 1–3
2	HPOP-EPIC-01–04: Cohorts + registries	PopHealth	S1 (clinical)	21pts	S4-Sprint 1–3
3	BILL-EPIC-03–05: Full billing	Finance	S2 (billing)	13pts	S4-Sprint 1–3
4	CLM-EPIC-01–04: Claims lifecycle	Finance	BILL	13pts	S4-Sprint 2–4
5	IMMZ-EPIC-01–05: Immunization mgmt	Clinical	S1	13pts	S4-Sprint 2–4
6	CP-EPIC-01–04: Care plan mgmt	Clinical	S1	8pts	S4-Sprint 3–4
7	RAD-EPIC-03–05: Viewer + reports	Diagnostics	RAD-01–02	13pts	S4-Sprint 3–5
8	INS-EPIC-05–08: Full insurance	Finance	INS-01–04	13pts	S4-Sprint 3–5
9	HPOP-EPIC-05–10: HMIS + quality	PopHealth	HPOP-01–04	13pts	S4-Sprint 3–5
10	HL7v2 adapters (ADT/ORM/ORU/SIU)	Interop	FHIR-GW	13pts	S4-Sprint 3–5
11	AIO-EPIC-03: Full AI (ONNX + cloud)	AI	AIO-02	13pts	S4-Sprint 4–6
12	DESK-EPIC-06,08,09,10: Desktop depth	Desktop	All S4	21pts	S4-Sprint 3–6
13	ACPOL-EPIC-05–07: ABAC depth	Platform	S0	8pts	S4-Sprint 4–5
14	GA readiness review	All	All S4	5pts	S4-Sprint 6

S4 total: ~6 sprints

---

7. Slice 5 — National Scale (M5)

7.1 Epics in scope

All remaining enhancement epics across all modules. Key focus areas:

• Multi-region deployment infrastructure
• Mobile app (Expo React Native)
• SMART on FHIR + FHIR Bulk Data Access
• National HMIS indicator catalog
• Advanced AI analytics
• White-label theming
• Desktop hardening (DESK-EPIC-11)
• Registration enhancements (REG-EPIC-07–11)
• Document management advanced (DOC-EPIC-09–12)
• Terminology national extensions (TERM-EPIC-07–08)

7.2 Sprint-ready backlog

#	Epic/Story	Owner Team	Dep	Est	Sprint
1	Multi-region infra	DevOps	S4	21pts	S5-Sprint 1–3
2	Mobile app (Expo)	Mobile	S1 (chart)	21pts	S5-Sprint 1–4
3	SMART on FHIR	Interop	FHIR-GW	13pts	S5-Sprint 2–4
4	FHIR Bulk Data Access	Interop	FHIR-GW	8pts	S5-Sprint 3–4
5	National HMIS integration	PopHealth	HPOP	13pts	S5-Sprint 2–4
6	Advanced AI analytics	AI	AIO-03	13pts	S5-Sprint 3–5
7	White-label theming	Platform	CFG	8pts	S5-Sprint 3–4
8	DESK-EPIC-11: Hardening + a11y	Desktop	All	13pts	S5-Sprint 4–6
9	Registration enhancements	Clinical	REG	8pts	S5-Sprint 3–5
10	All services L4 hardening	All	All	21pts	S5-Sprint 4–6
11	Government pilot deployment	Ops	All S5	8pts	S5-Sprint 5–6

S5 total: ~6 sprints

---

8. Inter-Slice Dependency Graph

S0 Platform Foundation
 │
 ├──► S1 Core Clinical
 │     │
 │     ├──► S2 Orders & Diagnostics
 │     │     │
 │     │     ├──► S3 Integrated Care
 │     │     │     │
 │     │     │     └──► S4 Full Platform
 │     │     │           │
 │     │     │           └──► S5 National Scale
 │     │     │
 │     │     └──► S4 (billing depth)
 │     │
 │     └──► S3 (pharmacy depends on meds)
 │
 └──► S3 (digital-communication depends on S0 notification)

Critical chain: S0 → S1 → S2 → S3 → S4 → S5 (sequential) Parallel opportunities within slices: See team-capacity-model.md for staffing.

---

9. Slice Exit Criteria

Slice	Exit criteria
S0	Two-tenant CI green; sync E2E proven; freeze points accepted; Kong routing all services
S1	3+ pilot clinics operational 2+ weeks; offline patient intake proven; RTL verified
S2	First revenue; orders → results round-trip; billing functional
S3	Hospital pilot; LIS + pharmacy integrated; e-prescribing verified with mock spine
S4	GA review passed; PACS + claims functional; population health dashboard live
S5	National pilot; multi-region deployed; mobile app in app stores; HMIS verified