Track the origin and history of a resource — who created or modified it and when. This page documents the Provenance resource as served by the mock.health synthetic FHIR R4 sandbox — 3 search parameters, US Core 6.1 profiling, and the elements accepted on write.
GET https://api.mock.health/fhir/Provenance — searchGET https://api.mock.health/fhir/Provenance/{id} — read by logical idPOST https://api.mock.health/fhir/Provenance — create (Pro)PUT https://api.mock.health/fhir/Provenance/{id} — update (Pro)patient (reference) — Patient the provenance relates to. Patient-typed by definition, so a bare id is never ambiguous — the most direct way to pull provenance for one patient.target (reference) — Target resource the provenance tracks. Provenance can be about any resource type, so a bare id only works when it names a patient (we resolve it to Patient/id). For any other target, send a typed reference (ResourceType/id).agent (reference) — Agent involved in the provenance eventFields accepted when creating or updating a Provenance. Required elements are base FHIR cardinality; the rest are US Core must-support.
target (Reference(Any)[]) — required — Resource(s) the provenance tracksrecorded (instant) — required — When the activity was recordedagent (BackboneElement[]) — required — Actor(s) responsible — must include a who referenceBase definition: HL7 FHIR R4 Provenance. Category: Infrastructure.
Device · Location · Organization · QuestionnaireResponse
API reference · Quickstart · USCDI compliance · SMART on FHIR