A pattern to be followed by resources that represent the performance of some activity, possibly in accordance with a request or service definition.

Identifiers Business identifiers assigned to this event {{title}} by the performer or and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.

Allows identification of the event {{title}} as it is known by various participating systems and in a way that remains consistent across servers.

Note: This is a business identifier, not a resource identifier (see discussion ). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

A The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that was is adhered to in whole or in part by this event. {{title}}.

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this {{title}}.

[The allowed reference resources may This might be adjusted as appropriate for the event resource]. an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

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

Allows tracing of authorization for the event {{title}} and tracking whether proposals/recommendations were acted upon.

[The allowed reference resources may be adjusted as appropriate for the event resource].

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

E.g. [E.g. Drug administration as part of a procedure, procedure as part of observation, etc. etc.].

Not to be used to link an event {{title}} to an Encounter - use Event.context 'context' for that.

[The allowed reference resources may be adjusted as appropriate for the event resource].

Indicates that this {{title}} is relevant to the specified research study(ies).

This relevance might mean that the {{title}} occurred as part of the study protocol, but can also include events that occurred outside the study but still have relevance.

The current state of the event. {{title}}.

A nominal state-transition diagram can be found in the [[event.html#statemachine | Event pattern]] documentation

Unknown does not represent "other" "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.

If true, indicates that Captures the described event (combination reason for the current state of code, timing, performer, etc.) did not actually occur. the {{title}}.

This is generally only used for "exception" statuses such as "not-done", "suspended" or "cancelled". The more attributes are populated, the more constrained the negated statement is. For example if timeframe and performer are specified, that means reason for performing the event wasn't done by that performer in that time-period, but could well have been done by someone else or by that performer at all is captured in a different time period. Event.notDoneReason Definition Describes why the event did reasonCode, not occur in coded and/or textual form. here.

This is a separate element to allow it to have a distinct binding from reasonCode. Summary true Invariants Affect this element inv-1 : Not Done Reason [distinct reason codes for different statuses can only be specified enforced using invariants if NotDone is "true" ( expression : notDone or notDoneReason.exists().not(), xpath: f:notDone/@value=true() or not(exists(f:notDoneReason))) they are universal bindings].

A code that identifies the specific service or action that was or is being performed.

The individual or set of individuals the action is being or was performed on.

Links the event {{title}} to the Patient context.

[For resources that aren't patient-specific, the set of allowed resources may be extended to include other things. Group should generally be retained unless there's certainty this resource won't be used for veterinary, research or public health settings where Group may be necessary (e.g. this cage of rats/crate of chickens, group of people in a 5 mile radious of the incident, etc.)].

The encounter or episode of care that establishes the context for this event. {{title}}.

Links the request {{title}} to the Encounter context.

This will typically be the encounter the event {{title}} occurred within, but some events {{title}}s may be initiated prior to or after the official completion of an encounter or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests).

The date date, period or time(s) timing when the activity occurred. {{title}} did occur or is occurring.

This indicates when the activity actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this {{event}} is "basedOn". The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds.

[The list of types may be constrained as appropriate for the type of event]. event. The use of 'Timing' in type is generally only appropriate for Events that are typically used to represent summary information.].

The date the occurrence of the {{title}} was first captured in the record - potentially significantly after the occurrence of the event.

Indicates who or what performed the event. {{title}} and how they were involved.

[Resources may choose to replace this with just a single performer or repeating where there's no need to distinguish role and/or responsible organization]. the function performed].

Describes Distinguishes the type of performance (e.g. primary surgeon, anaesthesiologiest, etc.). involvement of the performer in the {{title}}. [Consider adding examples].

Allows disambiguation of the types of involvement of different performers.

The device, practitioner, etc. Indicates who or what performed the action. {{title}}.

The organization principal physical location where the device or practitioner {{title}} was acting on behalf of. performed.

Practitioners Ties the event to where the records are likely kept and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing provides context around the action. event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

Describes why the event {{title}} occurred in coded or textual form.

Textual reasons can be captured using reasonCode.text.

Indicates another resource whose existence justifies this event. {{title}}.

[Additional resources may be added as appropriate].

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