Event-extensions - FHIR v3.3.0

R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Event Pattern HL7 Extensions

FHIR Infrastructure Work Group

Maturity Level: N/A

Ballot 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.

Content

Extensions:
event-instantiatesCanonical	instantiatesCanonical : 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 resource.
event-instantiatesUri	instantiatesUri : 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 resource.
event-partOf	partOf : A larger event of which this particular event is a component or step.
event-statusReason	statusReason : Captures the reason for the current state of the resource.
event-reasonCode	reasonCode : Describes why the event occurred in coded or textual form.
event-reasonReference	reasonReference : Indicates another resource whose existence justifies this event.
event-location	location : The principal physical location where the {{title}} was performed.
event-eventHistory	eventHistory : 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-performerFunction	performerFunction : Distinguishes the type of involvement of the performer in the event. For example, 'author', 'verifier' or 'responsible party'.
event-note	note : Comments made about the event by the performer, subject or other participants.