Skip to main content

Provenance

Overview

The Provenance resource tracks information about the activity that created, revised, deleted, or signed a version of a resource, describing the entities and agents involved. This provides audit trail and data integrity information.

Resource Schema

Key fields in the Provenance resource:

{
"resourceType": "Provenance",
"id": "example-provenance-123",
"target": [
{
"reference": "Patient/123456"
}
],
"occurredDateTime": "2023-07-15T14:30:00Z",
"recorded": "2023-07-15T14:30:00Z",
"activity": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-DataOperation",
"code": "CREATE",
"display": "create"
}
]
},
"agent": [
{
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/provenance-participant-type",
"code": "author",
"display": "Author"
}
]
},
"who": {
"reference": "Practitioner/789"
}
}
]
}

Operations

The Provenance resource supports Read operations only.

CareRecord / SolutionReadSearch
GEHRIMED
myAvatar
myEvolv
myUnity
TheraOffice

Read

Retrieves a specific Provenance resource by ID.

HTTP Method: GET
URL: /Provenance/{id}

Examples

curl -X GET https://fhir.netsmartcloud.com/uscore/v1/Provenance/123456 \
-H "Authorization: Bearer {token}" \
-H "Accept: application/fhir+json"

Integration Patterns

Common Workflows

  1. Audit Trail - Track who created or modified clinical data
  2. Data Integrity - Verify the source and authenticity of information
  3. Compliance Reporting - Generate audit reports for regulatory requirements

Relationships to Other Resources

The Provenance resource can reference any FHIR resource to provide audit information:

Error Handling

For common errors and troubleshooting guidance, see Common Errors.

Supported Profiles

Profiles supported by this resource (as defined in the CapabilityStatement):