Provenance Profile

Canonical	../StructureDefinition/nexus-emr-core-provenance
Status	draft · 1.26.0
Base	Provenance (constraint)
Source	FSH · JSON

Attribution for AI-mediated and cross-boundary writes: 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…