Clinical reasoning artifacts — the durable spine
Clinical reasoning artifacts — the durable spine
Section titled “Clinical reasoning artifacts — the durable spine”Nexus uses clinical reasoning artifacts as the durable platform record.
Clinical reasoning artifacts hold the structured reasoning record that downstream surfaces can reuse. Final narratives and reports are downstream surfaces.
What an artifact holds
Section titled “What an artifact holds”| Part | Meaning |
|---|---|
| Facts | Structured claims or extracted truths |
| Evidence | Where those claims came from |
| Interpretation | The product’s reasoning layer over those facts |
| Uncertainty | Confidence, ambiguity, missingness, conflicts |
| References | Stable source refs, ids, page numbers, record ids, dates |
| Lineage hooks | Enough information for audit and downstream composition |
Why artifacts are the durable record
Section titled “Why artifacts are the durable record”- A report is one surface.
- A chart is another surface.
- A clinician card is another surface.
- A patient chat response is another surface.
If the primary record is a final report, other surfaces require additional translation or separate output logic. If the primary record is an artifact, multiple surfaces can compose from the same record.
Trusted values are computed in code
Section titled “Trusted values are computed in code”Models may copy stable references. They should not be trusted to invent artifact ids, source URLs, version stamps, hashes, or lineage links. Those values are computed in code so the system stays auditable.