Clinical Intelligence StandardsVersion 0.2

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.

CapabilityStatusIn this versionNot yet
Workflow definitionImplementedStates, transitions, requirements, gates, automatic moves, SLA boardRequirements and gates outside encounter journeys
Version pinningImplementedInstances record and use the version they started underMigration between versions
Schedules and adherencePartialFixed-interval schedules, due, overdue, missed, adherenceEvent-relative anchors, windows, sequences
Trajectories and outcomesPartialSlope, status, outcome evaluationRules over history. Rules see the latest value only.
EvidencePartialCitations and PICO on protocols, review before publishingEvidence per recommendation, recorded deviation with a reason
ExecutionPartialDepth limit, cascades, duplicate-free routinesConflict handling across concurrent protocols, atomic multi-record instantiation
Episodes of carePartialA care_program journey and an episode profilePause, relapse, transfer, and close semantics
Cohort-level measurementNot implementedMembership records and the encounter boardDenominators, measures, care gaps
General links between recordsNot implementedSpecific fields such as basis, evidence, source_id, supersedesA general relationship primitive
Terminology portabilityNot implementedCodes may carry any systemMapping a local code to a shared one across sites