Functional standard
Foundation
How to read the reference model, and the behaviour every resource shares.
- How to read this standard — Clinestra Care Standard 0.2 is a specification for running longitudinal clinical care: how care workflows are defined, how they are managed over time, and how a care model is installed on a fixed set of primitives. It is not a clinical guideline.
- The longitudinal care model — Every long-term care program, whatever the disease or setting, is built from the same few elements. The primitives stay fixed. The care model is what you install on top.
- Care workflows — A journey definition is the workflow language of this standard: named states, allowed moves, what must be done before leaving a state, what each state permits, and what moves care forward by itself.
- Time — How the standard represents what is due, what was missed, and which way a patient is heading.
- Versioning of care definitions — Long-term care outlives any one version of a protocol. This page says which version governs a patient who is already in care.
- 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.
- Conformance — What an implementation must do to claim Clinestra Care Standard 0.2.
- Data types — The types named in element tables. They are deliberately few.
- Instance — Every resource carries these elements. Patient-scoped resources also carry patient_id. Resource pages list only their own elements and point here.
- Actors — Who is calling. The actor is not an element of the clinical resource. It is the subject of created_by and of the timeline.
- Operations — Five operations on every resource, plus a short list of named operations. This is the REST surface, in the same role as FHIR's HTTP API.
- Reactions and the tiered rule — State changes cause other records. Whether they are written or only proposed depends on the target, not on who configured the reaction.
- Packs and connectors — Two extension mechanisms. Packs add definitions. Connectors add other systems. Neither adds a resource type.