Functional standard / Foundation
Conformance
What an implementation must do to claim Clinestra Care Standard 0.2.
A conforming server
- Exposes every resource in this standard with the five operations, except where the resource page says an operation is absent. Approval has no caller create. Proposal is decided through accept and reject.
- Rejects a state move that is not listed.
- Treats clinical resources and clinical target states as clinician-only. Reactions and agents create proposals instead.
- Refuses self-approval.
- Refuses update and delete in a frozen state.
- Does not delete a resource whose page says it is not deletable.
- Attributes every write to the authenticated actor and appends a hash-chained timeline entry.
- Isolates sites. Library definitions are readable across sites and not writable.
- Scores assessments with the named kernel. It ignores a client-supplied score, band, or safety flag.
- Records the definition version on each instance made from a definition, and applies that version to the instance's later behavior as described under Versioning.
- Refuses a journey move that is not allowed or leaves requirements unmet, unless care-team staff force it with a reason, and records it as forced.
A conforming client
- Does not compute a clinical score, band, trajectory, or schedule status locally and present it as the record.
- Submits a form only on the person's action. Filling a form from a protocol is not a create.
- Shows the server's refusal text.
- Sends the actor via authentication, never in the body.
A conforming pack
- Is a set of Definition resources, valid against the definition kind's element table.
- Uses only the sandboxed expression language in rules, criteria, and reaction conditions.
- Marks clinical effects as effects on clinical resources, and expects them to be proposed.
- States that it is an example or a reviewed local protocol. The standard does not certify its medicine.
A conforming connector
- Writes through the API as a system actor or as a named person.
- Creates or cancels operational resources only, unless a person accepts a proposal.
- Exports a clinical element only when the map names it and consent scope data_sharing is granted.
- Keeps invoices, tax, and campaign data in the external system.