Functional standard / Definition kinds / Constrains ProtocolAssignment
protocol
A care program: criteria, the PICO question, evidence notes, and the templates to instantiate.
Runtime
Assignment checks criteria, then creates or proposes each template. Clinical templates become proposals.
Elements
| Name | Card. | Type | Description |
|---|---|---|---|
| defaults | 0..1 | object | Fields copied onto a new instance. Values given at creation win. |
| approval_required_for | 0..* | code | Extra states that need an Approval to enter. |
| cohorts | 0..* | code | Cohorts that surface this protocol. |
| patient_criteria | 0..1 | expression | Must be true to assign. |
| templates | 0..* | Template | kind, definition_key, data, required. |
| pico | 0..1 | object | Population, intervention, comparator, outcome as strings. |
| evidence | 0..* | object | Citations stored with the program: id, title, source_type (guideline, regulation, circular, paper, or local_sop), and optionally issuer, year, url_or_ref, applies_to, accessed_on. Not a live evidence graph. |
Example
{ "patient_criteria": "cond_mdd", "templates": [{ "kind": "careplan", "definition_key": "careplan_mdd", "required": true }] }