Clinical Intelligence StandardsVersion 0.2

Functional standard / Governance / Instance

Proposal

A suggested create, update, or transition waiting for a clinician.

Kind
proposal
Collection
/v1/proposals
Initial state
pending
Classification
Clinical

Scope and usage

The tiered rule. Reactions, agents and cohort rules put clinical effects here. A clinician accepts, with optional edits, or rejects with a reason.

Boundaries and relationships

Resource content

Elements this resource adds. It also carries the Instance.

NameCard.TypeFlagsDescription
patient_id0..1id—Patient the suggestion is about.
op1..1codeBcreate, transition, or update.
target_kind1..1code—Resource to change.
target_id0..1id—Existing record, for transition or update.
data0..1object—Proposed body or patch.
to_state0..1code—For a transition.
origin1..1string—reaction:key, agent:id, cohort:key, or protocol:key.
rationale0..1string—Why it was suggested.
result_id0..1idRRecord created or changed. Harness-owned.
decided_by0..1idRHarness-owned.

State machine

Decided only through /accept and /reject.

Frozen: accepted and rejected.

Terminology bindings

ElementStrengthValues
oprequiredcreate | transition | update

Invariants

Operations

MethodPathMeaning
GET/v1/proposalsList. Inbox is the pending list.
GET/v1/proposals/{id}Read one.
POST/v1/proposalsCreate a proposal. Agents use this rather than a clinical create.
POST/v1/proposals/{id}/acceptBody may include edits.
POST/v1/proposals/{id}/rejectBody includes reason.

Example

{ "patient_id": "pat_…", "op": "create", "target_kind": "clinical_state", "data": { "scope": "condition", "condition_code": "mdd", "state": "severe" }, "origin": "reaction:severe_phq9_flag" }