Current Build

Event Pattern HL7 Extensions

FHIR Infrastructure Work GroupMaturity Level: N/ABallot Status: Informative
This profile defines extensions that can be used to provide alignment with the Event workflow pattern data elements for concepts that may be generally applicable but may be sufficiently uncommon that they are more appropriate to include as extensions than as core properties of the resource. See the workflow module for more discussion about this specification that are typically involved in workflow.


event-instantiatesCanonicalinstantiatesCanonical :

The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by the event or request resource.

event-instantiatesUriinstantiatesUri :

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by the event or request resource.

event-partOfpartOf :

A larger event of which this particular event is a component or step.

event-statusReasonstatusReason :

Captures the reason for the current state of the resource.

event-reasonCodereasonCode :

Describes why the event occurred in coded or textual form.

event-reasonReferencereasonReference :

Indicates another resource whose existence justifies this event.

event-locationlocation :

The principal physical location where the {{title}} was performed.

event-eventHistoryeventHistory :

Links to Provenance records for past versions of this resource that document key state transitions or updates that are deemed “relevant” or important to a user looking at the current version of the resource. E.g, when an observation was verified or corrected. This extension does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.

event-performerFunctionperformerFunction :

Distinguishes the type of involvement of the performer in the event. For example, 'author', 'verifier' or 'responsible party'.

event-notenote :

Comments made about the event by the performer, subject or other participants.

event-basedOnbasedOn :

A plan, proposal or order that is fulfilled in whole or in part by this event.

event-supportingInfosupportingInfo :

Other resources from the patient record that may be relevent to the event. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available. For example, use Observation.hasMember instead of supportingInformation.for representing the members of an Observation panel.

event-relatedArtifactrelatedArtifact :

Documentation or 'knowledge artifacts' relevant to the base resource such as citations, supporting evidence, documentation of processes, caveats around testing methodology. Note that in contrast this extension, the supportingInfo extension references other resources from the patient record that were used in creating the resource.

event-researchStudyresearchStudy :

Indicates that this event is relevant to the specified research study(ies).