Provenance information of a resource is a record that describes the activity entities and processes involved in producing and delivering or otherwise influencing that led to the creation of resource. Provenance provides a set critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of resources. This information contextual metadata and can be used to help determine themselves become important records with their reliability or trace where the information own provenance. Provenance statement indicates clinical significance in them came from. The focus terms of the provenance resource is record keeping, audit confidence in authenticity, reliability, and traceability, trustworthiness, integrity, and not explicit statements stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of clinical significance. which may impact security, privacy, and trust policies.

Some parties may be duplicated between the target resource and its provenance. For instance, the prescriber is usually (but not always) the author of the prescription resource. This resource is defined with close consideration for W3C Provenance.

The resource(s) Reference(s) that were generated or updated by the activity described in this resource. A provenance can point to more than one target if multiple resources were created/updated by the same activity.

Target references are usually version specific, but may not be, if a version has not been assigned or if the provenance information is part of the set of resources being maintained (i.e. a document). When using the RESTful API, the identity of the resource may not be known (especially not the version specific one); the client may either submit the resource first, and then the provenance, or it may submit both using a single transaction. See the notes on transaction for further discussion.

The period during which the activity occurred.

The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

The instant of time at which the activity was recorded.

This can be a little different from the time stamp on the resource if there is a delay between recording the event and updating the provenance and target resource.

The reason that the activity was taking place.

An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.

Where the activity occurred, if relevant.

Policy or plan the activity was defined by. Typically, a single activity may have multiple applicable policy documents, such as patient consent, guarantor funding, etc.

For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element.

An agent takes a role in an activity such that the agent can be assigned some degree of responsibility for the activity taking place. An agent can be a person, a piece of software, an inanimate object, an organization, software, or other entities that may be ascribed responsibility.

Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa.

The role that function of the participant played. agent with respect to the activity.

For example, author, performer, enterer, attester, etc.

The type of individual, device or organization that participated in the participant. event.

The identity of resource, then the entity identified agent as known by the resource is the participant. authorization system.

A relationship between two the agents referenced in this resource. This is defined to allow for explicit description of the delegation between agents. For example, this human author used this device, or one person acted on another's behest.

The type of participant. May be a logical or physical uri and maybe absolute or relative. relationship between agents.

An internal reference to another agent listed in this provenance by its identifier.

The uri has the form #[id] where [id] is on another Provenance.agent in this same resource.

An entity used in this activity.

Multiple userIds may be associated with the same Practitioner or other individual across various appearances, each with distinct privileges.

How the entity was used during the activity.

The type of the entity. If the entity is a resource, then this is a resource type.

If the type is "resource" then the resource itself was the participant. If the type is a type of resource, then the entity identified by the resource is the participant.

Identity of participant. the Entity used. May be a logical or physical uri and maybe absolute or relative.

Identity may be a reference to a resource or to something else, depending on the type.

Human-readable description of the entity.

The entity is attributed to an agent to express the agent's responsibility for that entity, possibly along with other agents. This description can be understood as shorthand for saying that the agent was responsible for the activity which generated the entity.

A digital signature on the target resource(s). Reference(s). The signature signer should match a Provenance.agent.reference in the provenance resource. Provenance.agent. The signature is only added to support checking cryptographic integrity of the resource, and not to represent workflow and clinical aspects purpose of the signing process, or to support non-repudiation. signature is indicated.