Skip to main content

Registration Service — Epics

Service: registration-service Epic prefix: REG-EPIC Last updated: 2026-04-17

Epics

REG-EPIC-01 — Core patient and encounter registration lifecycle

FieldValue
Issue typeEpic
SummaryDeliver reliable patient registration and encounter lifecycle
StatusIn Progress
PriorityMust
Labelsservice:registration, domain:registration, slice:S0
Componentspatients, encounters, MPI, identifiers
Fix versionM0
FR referencesFR-REG-001, FR-REG-002, FR-REG-008, FR-REG-012, FR-REG-013, FR-REG-014, FR-REG-015
Legacy FR refsFR-REG-001..008 (ADMIN-REG v2.1)
Dependenciescross-service: IDENT-EPIC-01 (JWT auth), FAC-EPIC-01 (location refs)
Rollup statusPartial

Business outcome: Staff can register patients and open encounters, making clinical workflows possible.

Description: Delivers the foundational REST and FHIR APIs for creating, reading, and updating patients and encounters. Includes MRN generation, multi-identifier support, multi-script names, locale-aware address formats, and the encounter status machine. The stable stablePatientId is emitted on all identity events for downstream platform consumers.

Stories: REG-US-001, REG-US-002, REG-US-003, REG-US-004


REG-EPIC-02 — Duplicate detection and governed merge operations

FieldValue
Issue typeEpic
SummaryDeliver MPI duplicate detection and governed patient merge
StatusIn Progress
PriorityMust
Labelsservice:registration, domain:registration, slice:S0
ComponentsMPI, merge, unmerge
Fix versionM0
FR referencesFR-REG-004, FR-REG-005, FR-REG-021
Legacy FR refsFR-REG-004, FR-REG-005 (ADMIN-REG v2.1)
DependenciesREG-EPIC-01
Rollup statusPartial

Business outcome: Split-identity records are detected before creation; duplicate merges are governed, audited, and reversible.

Description: Implements probabilistic MPI scoring (threshold-configurable), 409 DUPLICATE_DETECTED response on create, merge with survivorship rules (identifier transfer, NOK repoint, source deactivation), and optional unmerge when policy allows. Multi-step approval is a phase-D enhancement.

Stories: REG-US-010, REG-US-011, REG-US-012


REG-EPIC-03 — Safe patient search with minimum-necessary controls

FieldValue
Issue typeEpic
SummaryDeliver minimum-necessary patient search with break-glass audit
StatusIn Progress
PriorityMust
Labelsservice:registration, domain:registration, slice:S0
Componentssearch, audit, break-glass
Fix versionM0
FR referencesFR-REG-003, FR-REG-022
Legacy FR refsFR-REG-003, FR-REG-022 (ADMIN-REG v2.1)
DependenciesREG-EPIC-01
Rollup statusPartial

Business outcome: Staff can find patients efficiently; privacy is preserved by requiring sufficient criteria; break-glass access is audited.

Description: Patient search enforces minimum-necessary criteria (strong criterion or two weak factors). Fuzzy name matching via pg_trgm. Break-glass header triggers enriched audit event. Results are paginated and scoped to tenant.

Stories: REG-US-020, REG-US-021


REG-EPIC-04 — Regionalized identity and i18n workflows

FieldValue
Issue typeEpic
SummaryDeliver RTL, multi-script, and locale-aware identity capture
StatusIn Progress
PriorityMust
Labelsservice:registration, domain:registration, slice:S0
Componentsnames, addresses, dates, telecoms
Fix versionM1
FR referencesFR-REG-009, FR-REG-010, FR-REG-011, FR-REG-013, FR-REG-014, FR-REG-015
Legacy FR refsFR-REG-009..015 (ADMIN-REG v2.1)
DependenciesREG-EPIC-01
Rollup statusPartial

Business outcome: Patients from Afghanistan and UAE can be registered accurately in local languages and scripts; national IDs are captured and validated.

Description: Supports multi-script patient names (Dari/Pashto/Arabic + Latin transliteration) with RTL text direction hints. Configurable Afghanistan address hierarchy (province/district). Hijri/Solar calendar date-of-birth picker with ISO storage. National ID digit-length validation. Preferred language from allowed set.

Stories: REG-US-030, REG-US-031


REG-EPIC-05 — Edge identity workflows (deceased, provisional, newborn)

FieldValue
Issue typeEpic
SummaryDeliver safe workflows for deceased, provisional, and newborn patients
StatusIn Progress
PriorityMust
Labelsservice:registration, domain:registration, slice:S1
Componentsvital-status, provisional, newborn, reconciliation
Fix versionM1
FR referencesFR-REG-016, FR-REG-017, FR-REG-018
Legacy FR refsFR-REG-016..018 (ADMIN-REG v2.1)
DependenciesREG-EPIC-01, REG-EPIC-02
Rollup statusPartial

Business outcome: Edge registration scenarios (emergency intake, maternity, deceased) are handled safely with controlled workflows and full audit trails.

Description: Vital status (deceased boolean + optional date/time) with RBAC, correction, and correction audit trail. Provisional patient create for emergency intake with controlled reconciliation merge. Newborn registration with mother/guardian linkage and temporary identifier handling.

Stories: REG-US-040, REG-US-041, REG-US-042


REG-EPIC-06 — National enterprise identity extensions

FieldValue
Issue typeEpic
SummaryDeliver alternate IDs, unidentified intake, portrait, and family graph
StatusTo Do
PriorityMust
Labelsservice:registration, domain:registration, slice:S3
Componentsalternate-id, unidentified, portrait, relationship-graph, extension-schemas
Fix versionM3
FR referencesFR-REG-023, FR-REG-024, FR-REG-025, FR-REG-026, FR-REG-027, FR-REG-028
Legacy FR refsREG-NAT-US-001..050 (enterprise national eHealth requirements)
DependenciesREG-EPIC-01, REG-EPIC-02, REG-EPIC-05
Rollup statusNot started

Business outcome: Unidentified emergency patients are registered safely; rural populations without national IDs can be enrolled using alternate credentials; patient portraits support identity verification; extensible metadata supports national program reporting.

Description: Includes: unidentified person intake with temporary enterprise key and SLA reminders; alternate identity evidence for populations without national IDs; patient portrait upload with consent, retention, and clinical display controls; extensible JSON Schema-validated patient attribute bundles (employment, marital, appearance); multiple NOK entries with relationship graph queries; stable stablePatientId events for cross-program identity binding.

Stories: REG-US-050, REG-US-051, REG-US-052, REG-US-053, REG-US-054, REG-US-055


REG-EPIC-07 — Platform resilience and quality controls

FieldValue
Issue typeEpic
SummaryDeliver idempotency, coverage gates, and production reliability
StatusIn Progress
PriorityMust
Labelsservice:registration, domain:registration, slice:S0
Componentsidempotency, testing, observability
Fix versionM0
FR referencesNFR-REG-001, NFR-REG-002, NFR-REG-003, NFR-REG-004
Legacy FR refsNFR-REG-001..004 (ADMIN-REG v2.1)
DependenciesREG-EPIC-01
Rollup statusPartial

Business outcome: Registration APIs are reliable, measurable, and safe for offline-first client retry patterns.

Description: Idempotent patient create (Idempotency-Key / clientMutationId) for offline-first retries. Coverage ≥ 80% enforced in CI. SLO alerts configured. Outbox relay tested and monitored. Canary deploy gate before production promotion.

Stories: REG-US-060, REG-US-061