Skip to main content

Care Plan Service — Epics

Service: care-plan-service Epic prefix: CAREPL-EPIC Last updated: 2026-04-18

Epics

CAREPL-EPIC-01 — Care Plan Lifecycle Management

FieldValue
Issue typeEpic
SummaryCore care plan CRUD with status lifecycle and versioning
StatusTo Do
PriorityMust
Labelsservice:care-plan, domain:care_plan, slice:S1
Componentscare-plan-service, fhir-gateway
Fix versionM1
FR referencesFR-CAREPL-001, FR-CAREPL-002
Legacy FR refsFR-CP-001, FR-CP-005
DependenciesREG-EPIC-01, IDENT-EPIC-01
Rollup statusNot started

Business outcome: Clinicians can create, activate, review, and close care plans with full audit history and version safety, enabling structured longitudinal care.

Description: This epic covers the foundational lifecycle of a care plan: creation from scratch or from an encounter context, activation, periodic formal review, and terminal closure (completed or revoked). Optimistic concurrency prevents silent overwrite by concurrent editors. Closed plans remain permanently visible and read-only.

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


CAREPL-EPIC-02 — Goal Management

FieldValue
Issue typeEpic
SummaryMeasurable goal creation, status tracking, and overdue detection
StatusTo Do
PriorityMust
Labelsservice:care-plan, domain:care_plan, slice:S1
Componentscare-plan-service
Fix versionM1
FR referencesFR-CAREPL-003
Legacy FR refsFR-CP-002
DependenciesCAREPL-EPIC-01, TERM-EPIC-01
Rollup statusNot started

Business outcome: Care teams can set measurable, coded health goals with targets and due dates, track progress, and automatically surface overdue goals for follow-up.

Description: Goals represent the "why" of a care plan — specific, measurable outcomes the patient should achieve. Each goal carries a coded target (LOINC, SNOMED), a quantitative or qualitative detail, a due date, and a status. Overdue detection drives alert/notification integration with communication-service.

Stories: CAREPL-US-005, CAREPL-US-006, CAREPL-US-007


CAREPL-EPIC-03 — Activity and Intervention Tracking

FieldValue
Issue typeEpic
SummaryActivity assignment, schedule, and completion workflow
StatusTo Do
PriorityMust
Labelsservice:care-plan, domain:care_plan, slice:S1
Componentscare-plan-service
Fix versionM1
FR referencesFR-CAREPL-004
Legacy FR refsFR-CP-003
DependenciesCAREPL-EPIC-01, PROVDIR-EPIC-01
Rollup statusNot started

Business outcome: Specific interventions are assigned to care team members with schedules; completion is tracked, creating an auditable record of executed care.

Description: Activities translate goals into actionable steps. Each activity is assigned to a team member, carries a schedule detail (e.g., monthly, weekly), and progresses through not_started → in_progress → completed. Completion records a timestamp and optional note, contributing to care plan audit trails and population health metrics.

Stories: CAREPL-US-008, CAREPL-US-009


CAREPL-EPIC-04 — CareTeam Coordination

FieldValue
Issue typeEpic
SummaryMultidisciplinary care team composition per plan
StatusTo Do
PriorityMust
Labelsservice:care-plan, domain:care_plan, slice:S2
Componentscare-plan-service, provider-directory-service
Fix versionM1
FR referencesFR-CAREPL-005
Legacy FR refsFR-CP-004
DependenciesCAREPL-EPIC-01, PROVDIR-EPIC-01
Rollup statusNot started

Business outcome: Each care plan has a clear team of responsible practitioners with roles and effective periods, enabling coordinated multidisciplinary care.

Description: CareTeam composition is managed per plan. Practitioners are referenced from provider-directory-service with coded roles (primary physician, care coordinator, specialist, nurse). Team membership has an effective period — practitioners can be added or removed over the plan lifecycle. The care team is exposed via FHIR CareTeam resource.

Stories: CAREPL-US-010, CAREPL-US-011


CAREPL-EPIC-05 — FHIR R4 Read Surface

FieldValue
Issue typeEpic
SummaryFHIR R4 CarePlan/Goal/CareTeam read/search for interop
StatusTo Do
PriorityMust
Labelsservice:care-plan, domain:care_plan, slice:S1, type:fhir
Componentscare-plan-service, fhir-gateway
Fix versionM1
FR referencesFR-CAREPL-006
Legacy FR refs
DependenciesCAREPL-EPIC-01, INTEROP-EPIC-01
Rollup statusNot started

Business outcome: Partner systems, the patient portal, and patient-chart-service can read care plans via standard FHIR R4 resources without bespoke integration.

Description: The FHIR read surface maps domain entities to conformant R4 resources: CarePlan, Goal (as R4 Goal), Task (for activities), and CareTeam. The fhir-gateway routes read/search requests to care-plan-service FHIR adapter. Write interactions via FHIR HTTP are explicitly out of scope for this release.

Stories: CAREPL-US-012, CAREPL-US-013


CAREPL-EPIC-06 — Tenant Security and Licensing

FieldValue
Issue typeEpic
SummaryModule entitlement gate, RLS, and RBAC enforcement
StatusTo Do
PriorityMust
Labelsservice:care-plan, domain:care_plan, slice:S0, type:security
Componentscare-plan-service, identity-service
Fix versionM1
FR referencesFR-CAREPL-007
Legacy FR refs
DependenciesIDENT-EPIC-01, TENANT-EPIC-01
Rollup statusNot started

Business outcome: Only licensed tenants access care plans; no data leaks across tenant boundaries; sensitive program plans restricted to authorized roles.

Description: Covers module entitlement check (403 for unlicensed), RLS policy enforcement validated by adversarial integration tests, RBAC matrix for all roles, and ABAC for sensitive plan categories (mental health, HIV). Security reviewer sign-off required before production.

Stories: CAREPL-US-014, CAREPL-US-015