Skip to main content

Provenance

ResourceFoundation · SecurityTrial useMaturity 3

Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies.

Tested supportFull test results →
Backends
PostgreSQLElasticsearch
Interactions
CreateReadUpdatePatchDelete
Search
10 of 10 parameters tested

Structure​

ElementCard.TypeDescription
targetRequiredΣ
1..*Reference(Resource)Target Reference(s) (usually version specific)
occurred[x]
0..1Period | dateTimeWhen the activity occurred
recordedRequiredΣ
1..1instantWhen the activity was recorded / updated
policy
0..*uriPolicy or plan the activity was defined by
location
0..1Reference(Location)Where the activity occurred, if relevant
reason
0..*CodeableConceptReason the activity is occurringBinding (extensible): v3-PurposeOfUse
activity
0..1CodeableConceptActivity that occurredBinding (extensible): provenance-activity-type
agentRequired
1..*BackboneElementActor involved
typeΣ
0..1CodeableConceptHow the agent participatedBinding (extensible): provenance-agent-type
role
0..*CodeableConceptWhat the agents role wasBinding (example): security-role-type
whoRequiredΣ
1..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)Who participated
onBehalfOf
0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)Who the agent is representing
entity
0..*BackboneElementAn entity used in this activity
roleRequiredΣ
1..1codederivation | revision | quotation | source | removalBinding (required): provenance-entity-role
whatRequiredΣ
1..1Reference(Resource)Identity of entity
agent
0..*Same as Provenance.agentEntity is attributed to this agent
signature
0..*SignatureSignature on target

Σ in _summary results · ?! modifier element · 1.. required · inherited elements in grey

Search parameters​

Query with GET [base]/Provenance?[parameter]=[value]. Type decides which modifiers and prefixes apply, see search features.

ParameterTypeDescriptionPGES
agentreference

Who participated

Provenance.agent.who
agent-roletoken

What the agents role was

Provenance.agent.role
agent-typetoken

How the agent participated

Provenance.agent.type
entityreference

Identity of entity

Provenance.entity.what
locationreference

Where the activity occurred, if relevant

Provenance.location
patientreference

Target Reference(s) (usually version specific)

Provenance.target.where(resolve() is Patient)
recordeddate

When the activity was recorded / updated

Provenance.recorded
signature-typetoken

Indication of the reason the entity signed the object(s)

Provenance.signature.type
targetreference

Target Reference(s) (usually version specific)

Provenance.target
whendate

When the activity occurred

(Provenance.occurred.ofType(dateTime))

PG: PostgreSQL, ES: Elasticsearch. passes its TestScript checks, fails, not tested yet.

Common parameters on every resource (8)
_haste-health-authorreference

The author of the resource

_idtoken

Logical id of this artifact

_lastUpdateddate

When the resource version last changed

_profileuri

Profiles this resource claims to conform to

_securitytoken

Security Labels applied to this resource

_sourceuri

Identifies where the resource comes from

_tagtoken

Tags applied to this resource

_typetoken

Derived from the R4B Definition