Provenance Profile¶
| Canonical | https://fhir.apps.health/StructureDefinition/nexus-emr-core-provenance |
|---|---|
| Status | draft · 1.33.0 |
| Base | Provenance (constraint) |
| Source | FSH · JSON |
Attribution for AI-mediated writes, cross-boundary writes and record-lifecycle events such as linking an arriving result to a chart or entering a resource into the record: what was produced, when, by which agent (human or non-human), from what inputs, and -- for generated text -- which verbatim source passage each statement rests on. Used standalone against a produced resource, and contained in an AI-suggestion review Task against the suggestion contained alongside it.
Examples
Conforming instances (each opens inside this tab):
- AI-Drafted Note Accepted by a Clinician — Provenance for an AI-generated encounter note -- two agents distinguished by agent.type (Device author, Practitioner attester) plus the entity list naming the inputs the draft der…
- AI-Generated Summary With Per-Fact Citations — Provenance for an AI-generated pre-visit summary carrying the attributed-fact extension -- every statement backed by verbatim quotes with run-relative chunk labels, one citation r…
- Import Provenance for a Migration File — A Provenance for one import file and the one patient it covers, targeting every record the import wrote for that patient (the migrated immunization and the wellness-program source…
- Prov lab link automatic inr 20250402
- Prov lab link confirmed cbc 20250408
- Prov lab link manual us 20260312
- Prov lab unlink manual cbc 20250409