Communication Service — Epics
Service: communication-service Epic prefix: COMMS-EPIC Last updated: 2026-04-17
Epics
COMMS-EPIC-01 — Secure messaging core
| Field | Value |
|---|---|
| Issue type | Epic |
| Summary | Secure care-team and patient messaging with threads, participants, escalation |
| Status | In Progress |
| Priority | Must |
| Labels | service:communication, domain:digital-communication, slice:S1 |
| Components | messaging, fhir-communication |
| Fix version | M1 |
| FR references | FR-COMMS-MSG-001..008 |
| Legacy FR refs | FR-MSG-001..007, FR-DCOM-MSG-001..007 |
| Dependencies | INTEROP-EPIC-01, IDENT-EPIC-01 |
| Rollup status | Partial |
Business outcome: Give clinicians a secure, compliant channel for care coordination that replaces pagers, personal SMS, and phone tag; enables patient-clinician conversations when portal is licensed.
Description: Build the thread + message + read-receipt + escalation + archive lifecycle, including patient/encounter linkage with chart-access checks, attachment upload pipeline, and FHIR Communication projection. This is the foundation for every downstream communication capability.
Stories: COMMS-US-001, COMMS-US-002, COMMS-US-003, COMMS-US-004, COMMS-US-005, COMMS-US-006
COMMS-EPIC-02 — Notification orchestration & multi-channel dispatch
| Field | Value |
|---|---|
| Issue type | Epic |
| Summary | Category-driven push/SMS/email dispatch with pluggable providers and Ghasi-SMS-Gateway |
| Status | In Progress |
| Priority | Must |
| Labels | service:communication, domain:notifications, slice:S1 |
| Components | notifications, adapters |
| Fix version | M1 |
| FR references | FR-COMMS-NOTIF-001..006 |
| Legacy FR refs | FR-MSG-009..012, FR-DCOM-NOTIF-001..004 |
| Dependencies | CONFIG-EPIC-01, IDENT-EPIC-01 |
| Rollup status | Partial |
Business outcome: Every domain service can request a notification without knowing the channel, provider, or PHI-policy details. Enables critical-result escalation, appointment reminders, portal notifications in one substrate.
Description: Build category → channel policy → template → provider orchestration with ports for SMS (Ghasi-SMS-Gateway default), push (FCM/APNs/WebPush), and email (SES/SendGrid/SMTP). Include dispatch log with DLR upserts and PHI-minimized payload enforcement.
Stories: COMMS-US-007, COMMS-US-008, COMMS-US-009, COMMS-US-010, COMMS-US-011
COMMS-EPIC-03 — Virtual session lifecycle
| Field | Value |
|---|---|
| Issue type | Epic |
| Summary | Telehealth sessions: create from schedule, admit from waiting room, end, record |
| Status | In Progress |
| Priority | Must |
| Labels | service:communication, domain:virtual-care, slice:S2 |
| Components | virtual-sessions, jitsi-adapter |
| Fix version | M2 |
| FR references | FR-COMMS-VC-001..007, FR-COMMS-VC-016..017 |
| Legacy FR refs | FR-DCOM-VC-001..017 |
| Dependencies | SCHED-EPIC-01, COMMS-EPIC-02 |
| Rollup status | Partial |
Business outcome: Providers and patients can run telehealth visits inside the platform with waiting-room control, deterministic state machine, and billing hand-off.
Description: Consume scheduling.appointment.created (class=VR) to auto-create sessions idempotently. Issue short-lived, one-time join tokens. Enforce waiting-room admit. End and emit billing/recording events.
Stories: COMMS-US-012, COMMS-US-013, COMMS-US-014, COMMS-US-015
COMMS-EPIC-04 — Fallback continuity & critical escalation
| Field | Value |
|---|---|
| Issue type | Epic |
| Summary | Auto-fallback to secure thread on VC failure; critical-result fan-out |
| Status | To Do |
| Priority | Should |
| Labels | service:communication, slice:S3 |
| Components | fallback, escalation |
| Fix version | M3 |
| FR references | FR-COMMS-VC-023, FR-COMMS-MSG-006 |
| Legacy FR refs | FR-DCOM-VC-023, FR-MSG-005 |
| Dependencies | COMMS-EPIC-01, COMMS-EPIC-02, COMMS-EPIC-03 |
| Rollup status | Not started |
Business outcome: Care never stops when infrastructure fails. Critical clinical events automatically reach the right clinician within SLO.
Description: Implement fallback-thread auto-spawn on VC failure. Implement critical-result escalated channel profile (push + SMS + in-app) with ack tracking.
Stories: COMMS-US-016, COMMS-US-017
COMMS-EPIC-05 — Security, entitlement & compliance
| Field | Value |
|---|---|
| Issue type | Epic |
| Summary | RBAC/ABAC, licensing gate, PHI-never-in-push, GDPR participation |
| Status | In Progress |
| Priority | Must |
| Labels | service:communication, domain:security, slice:S1 |
| Components | authz, audit, gdpr |
| Fix version | M1 |
| FR references | FR-COMMS-LIC-001, FR-COMMS-018, FR-COMMS-019 |
| Legacy FR refs | FR-MSG-008, FR-DCOM-LIC-001, FR-DCOM-018, FR-DCOM-019 |
| Dependencies | IDENT-EPIC-02, AUDIT-EPIC-01 |
| Rollup status | Partial |
Business outcome: Compliant multi-tenant operation: no PHI leak in notifications, patient-bound queries for PATIENT role, GDPR erasure participation.
Description: Enforce identity-bound PATIENT access, licensed-module guards, patient-linked thread chart-access checks, PHI minimization on all dispatch channels. Participate in GDPR erasure saga.
Stories: COMMS-US-018, COMMS-US-019, COMMS-US-020
COMMS-EPIC-06 — Observability, delivery status & quality
| Field | Value |
|---|---|
| Issue type | Epic |
| Summary | Per-channel SLO instrumentation, dispatch-status query, coverage gates |
| Status | To Do |
| Priority | Should |
| Labels | service:communication, domain:ops, slice:S4 |
| Components | observability, quality |
| Fix version | M4 |
| FR references | FR-COMMS-ENH-001, NFR-COMMS-001..008 |
| Legacy FR refs | FR-DCOM-ENH-001, NFR-DCOM-001..008, NFR-DCOM-ENH-001 |
| Dependencies | COMMS-EPIC-02 |
| Rollup status | Not started |
Business outcome: Operators answer "did the SMS go through?" for any correlation id within seconds; SLOs surface regressions before customers notice.
Description: Ship the /notifications/dispatch-status query, per-channel dashboards, p95 SLO alerts, coverage-regression CI gates.
Stories: COMMS-US-021, COMMS-US-022