Functional standard / Foundation
Capability status
What version 0.2 implements for longitudinal care, and what it does not. Items that are partial or absent are not conformance requirements.
| Capability | Status | In this version | Not yet |
|---|---|---|---|
| Workflow definition | Implemented | States, transitions, requirements, gates, automatic moves, SLA board | Requirements and gates outside encounter journeys |
| Version pinning | Implemented | Instances record and use the version they started under | Migration between versions |
| Schedules and adherence | Partial | Fixed-interval schedules, due, overdue, missed, adherence | Event-relative anchors, windows, sequences |
| Trajectories and outcomes | Partial | Slope, status, outcome evaluation | Rules over history. Rules see the latest value only. |
| Evidence | Partial | Citations and PICO on protocols, review before publishing | Evidence per recommendation, recorded deviation with a reason |
| Execution | Partial | Depth limit, cascades, duplicate-free routines | Conflict handling across concurrent protocols, atomic multi-record instantiation |
| Episodes of care | Partial | A care_program journey and an episode profile | Pause, relapse, transfer, and close semantics |
| Cohort-level measurement | Not implemented | Membership records and the encounter board | Denominators, measures, care gaps |
| General links between records | Not implemented | Specific fields such as basis, evidence, source_id, supersedes | A general relationship primitive |
| Terminology portability | Not implemented | Codes may carry any system | Mapping a local code to a shared one across sites |