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

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

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

Note: This is a business identifer, 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.

The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this {{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}}.

This might be 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 {{title}}.

Allows tracing of authorization for the {{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 {{title}} is a component or step.

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

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

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

The current state of the {{title}}.

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

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

Captures the reason for the current state of the {{title}}.

This is generally only used for "exception" statuses such as "not-done", "suspended" or "cancelled". The reason for performing the event at all is captured in reasonCode, not here.

[distinct reason codes for different statuses can be enforced using invariants if 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 {{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 {{title}}.

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

This will typically be the encounter the {{title}} occurred within, but some {{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, period or timing when the {{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. The use of 'Timing' in type is generally only appropriate for Events that are typically used to represent summary information.].

Indicates who or what performed the {{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 the function performed].

Distinguishes the type of involvement of the performer in the {{title}}. [Consider adding examples].

Allows disambiguation of the types of involvement of different performers.

Indicates who or what performed the {{title}}.

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

Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

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

Textual reasons can be captured using reasonCode.text.

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

[Additional resources may be added as appropriate].

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