Care Standard 0.2
Functional standard
Resources, definitions, and operations for care that continues over time.
Foundation
- How to read this standard
- The longitudinal care model
- Care workflows
- Time
- Versioning of care definitions
- Capability status
- Conformance
- Data types
- Instance
- Actors
- Operations
- Reactions and the tiered rule
- Packs and connectors
Resources (31)
People
patientThe person the whole record is about. Family members are patients too, linked by Relationship.relationshipA link from a patient to a family member who is also a Patient.providerA clinician who can be the primary decision-maker on a care team.care_team_memberA person who cares in a role other than primary clinician: nurse, coordinator, health worker, dietitian.care_teamThe roster actually caring for one patient. The primary provider is the member whose role is primary.clinical_settingA place or service line that can fulfil orders: clinic, ward, lab, pharmacy, home, teleconsult.
How they are
observationOne coded fact: a vital, a lab, a score, a symptom, a finding.conditionA diagnosis or problem. Recording one is a clinical decision.medicationA medicine the patient is taking, prescribed here or reported.clinical_stateThe current grading of a condition, or a general state such as emergency or pregnant.outcomeA target. When it is reached, the harness can propose a new clinical state.health_profileA tagged view over observations: what is present and what is absent.
What can be done
What is being done
careplanWhat is planned: care actions for the patient and tasks for the team.care_actionSomething the patient does or receives: an order, referral, education, journal, medication, self-care, lifestyle, or appointment.taskWork for the care team: a checklist, or a request to complete a note or an assessment.routineA repeating duty. When it is due, the harness creates a Task.regimenA set of drugs and orders prescribed together.journeyThe patient's path through states defined by a journey Definition: a program, an encounter flow, or a setting.
Interactions
encounterA clinical interaction grouped by time and setting: a visit, a teleconsult, a home visit, an admission.clinical_recordThe set of note pages for one encounter. The record holds no clinical values itself.note_pageOne page of a record: a case sheet of blocks, or a chart of observations.assessmentA questionnaire or a calculator. The score is computed by the engine, never by the screen.clinical_documentA printable document that leaves the system: prescription, report, consent form, medical-legal note.journal_entryA patient log through a journal plugin. Mapped fields become patient-perceived observations.conversationA conversation with an agent, about one patient or general. Turns can carry proposal ids.
Governance
consentPermission for one scope: treatment, data sharing, AI, procedure, communication, or research.approvalA request to enter a gated state. Someone other than the requester decides.proposalA suggested create, update, or transition waiting for a clinician.definitionA versioned template. Packs ship published definitions. A site publishes its own, and a site key overrides the library key.
Definition kinds (18)
- cohort — Who belongs in a program, which protocols are offered, and what happens on entry and exit.
- protocol — A care program: criteria, the PICO question, evidence notes, and the templates to instantiate.
- careplan — The lines a plan should contain when a protocol instantiates it.
- note_page — The case-sheet or chart layout: blocks, which are required, and which become observations.
- assessment — A questionnaire or calculator: items, kernel, and the observation code for the score.
- encounter — A visit type: duration and which note pages open with the record.
- journey — The workflow language: states, allowed moves, requirements, gates, automatic moves, and effects. See Care workflows.
- care_team — The roles a patient's roster must fill.
- health_profile — Which codes a profile watches, and when it is created automatically.
- journal_plugin — The fields a patient logs, and which of them become observations.
- clinical_document — A printable template: type, letterhead slots, body placeholders, sharing and protection.
- clinical_setting — A reusable setting. Instance fields carry the services. This definition exists so a pack can ship the setting.
- regimen — A named regimen a pack offers, usually as a protocol template.
- task — A reusable task a protocol or routine can spawn.
- routine — A reusable repeating duty.
- conversation — Structure of an agent conversation for one actor role.
- patient_fields — Which standard demographics a site collects, and which custom fields it adds.
- reaction — When a resource enters a state, and an optional expression matches, run effects.