EM-HCP-04 · Subject model · W-IND
Care episode and care plan
A period of responsibility of a provider or care team for a patient's health issue, with the planned activities, goals and their review. Diagnoses are recorded as clinical observations and referenced.
Partially published; research continues
Claude: initial-industry-contour-and-card-supplement; Grok: not-started.
Published results
The independent second-provider study, fixtures and the full research protocol remain open. Runtime promotion is governed by the package allocation holds.
Subject boundary and candidate types
- EpisodeOfCare
- CareTeam
- CarePlan
- CareGoal
- PlannedActivity
- PlanReview
Deep research questions
- When does an episode start and end, and who decides?
- How are plan revisions kept so that past decisions remain visible?
- How are activities of several providers combined without taking over each other's records?
Verifiable invariants
- An episode has one managing organization at a time
- A care plan revision keeps the previous version
- A planned activity links to the order or appointment that carries it out
End-to-end acceptance scenario
For a synthetic follow-up of a chronic condition, open an episode, create a plan with two goals and three activities, revise it after a review, and close the episode with a transfer to another provider.
Negative case
A care plan template is stored as the patient's plan, so activities appear planned that no clinician has decided.
Approaches to compare
- HL7 FHIR: EpisodeOfCare, CareTeam and CarePlan resources
- openEHR: care plan and instruction archetypes
- Integrated care and case management practice
Candidates in the live catalogue
- WM-ACT-049 · Care Plan / Episode · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-046 · Clinical Observation / Diagnosis · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.