Clinical Intelligence StandardsVersion 0.2

Functional standard / People / PatientInstance

Relationship

A link from a patient to a family member who is also a Patient.

Kind
relationship
Collection
/v1/relationships
Initial state
active
Classification
Operational

Scope and usage

Records who is related, who may grant consent, and who receives communication.

Boundaries and relationships

Resource content

Elements this resource adds. It also carries the Instance, including patient_id.

NameCard.TypeFlagsDescription
related_patient_id1..1id—The other Patient.
relation1..1string—mother, spouse, son, friend, or a local term.
is_guardian1..1boolean—May grant consent for the scopes listed.
is_care_taker1..1boolean—May see the record as a representative.
consent_scopes0..*codeBScopes this person may grant. See Consent.
receives_communication1..1boolean—Operational contact flag. Not a clinical consent.

State machine

active → ended.

Frozen: None.

Invariants

Operations

MethodPathMeaning
GET/v1/relationshipsList relationship. Filter by patient_id, status, and where the model has them, encounter_id or definition_key.
POST/v1/relationshipsCreate a relationship. Body is the resource minus harness-owned elements.
GET/v1/relationships/{id}Read one relationship.
PATCH/v1/relationships/{id}Update elements that are not immutable, frozen, or harness-owned.
POST/v1/relationships/{id}/transitionMove status. Body is { to, reason }. A gated move returns 202 and an Approval.
DELETE/v1/relationships/{id}?reason=Soft-delete. Reason is required. Refused when the resource is not deletable or is frozen.

Example

{ "patient_id": "pat_…", "related_patient_id": "pat_…", "relation": "mother", "is_guardian": true, "consent_scopes": ["treatment"] }