Clinical Intelligence StandardsVersion 0.2

Functional standard / Definition kinds / Constrains Journey

journey

The workflow language: states, allowed moves, requirements, gates, automatic moves, and effects. See Care workflows.

Runtime

move refuses a step that is not listed or leaves requirements unmet, unless care-team staff force it with a reason. on_exit runs before on_enter. Both follow the tiered rule.

Elements

NameCard.TypeDescription
defaults0..1objectFields copied onto a new instance. Values given at creation win.
approval_required_for0..*codeExtra states that need an Approval to enter.
states1..*codeStep names.
initial1..1codeFirst step.
transitions0..1objectFrom-state to allowed next states. Empty means any.
terminal0..*codeSteps that complete the journey.
association_type1..1codecare_setting, encounter, or care_program.
on_enter0..1objectState name to a list of Effects, run on entering it.
on_exit0..1objectState name to a list of Effects, run on leaving it.
stages0..1objectState name to board presentation: label, category (todo, in_progress, done), color, description, sla_minutes.
gates0..1objectState name to allowed operations: case_sheet, finalize_record, close_encounter. Encounter journeys only.
requires0..1objectState name to requirements before leaving it: kind (note_page, clinical_record, assessment, task, observation), state, definition_key, label. Encounter journeys only.
advance_on0..*objectAutomatic moves: when_kind, when_state, to, from_states, definition_key. Encounter journeys only.

Example

{ "states": ["registered", "review", "certified"], "initial": "registered", "transitions": { "registered": ["review"], "review": ["certified"] }, "terminal": ["certified"] }