Functional standard / Profiling
Definition kinds
A definition configures a resource. It does not add a resource type. Eighteen kinds.
- cohort constrains CohortMembership. Who belongs in a program, which protocols are offered, and what happens on entry and exit.
- protocol constrains ProtocolAssignment. A care program: criteria, the PICO question, evidence notes, and the templates to instantiate.
- careplan constrains Careplan. The lines a plan should contain when a protocol instantiates it.
- note_page constrains NotePage. The case-sheet or chart layout: blocks, which are required, and which become observations.
- assessment constrains Assessment. A questionnaire or calculator: items, kernel, and the observation code for the score.
- encounter constrains Encounter. A visit type: duration and which note pages open with the record.
- journey constrains Journey. The workflow language: states, allowed moves, requirements, gates, automatic moves, and effects. See Care workflows.
- care_team constrains CareTeam. The roles a patient's roster must fill.
- health_profile constrains HealthProfile. Which codes a profile watches, and when it is created automatically.
- journal_plugin constrains JournalEntry. The fields a patient logs, and which of them become observations.
- clinical_document constrains ClinicalDocument. A printable template: type, letterhead slots, body placeholders, sharing and protection.
- clinical_setting constrains ClinicalSetting. A reusable setting. Instance fields carry the services. This definition exists so a pack can ship the setting.
- regimen constrains Regimen. A named regimen a pack offers, usually as a protocol template.
- task constrains Task. A reusable task a protocol or routine can spawn.
- routine constrains Routine. A reusable repeating duty.
- conversation constrains Conversation. Structure of an agent conversation for one actor role.
- patient_fields constrains Patient (site configuration, no instance of its own). Which standard demographics a site collects, and which custom fields it adds.
- reaction constrains No resource. It configures the harness.. When a resource enters a state, and an optional expression matches, run effects.