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.

A protocol, guideline, orderset or other definition that was adhered Note: This is a business identifier, not a resource identifier (see discussion ). It is best practice for the identifier to in whole or in part by this event. 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 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 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]] (Event pattern)[event.html#statemachine] 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 reasonCode, not here.

[distinct reason codes for different time period. statuses can be enforced using invariants if they are universal bindings].

Describes why Partitions the event did not occur in coded {{title}} into one or more categories that can be used to filter searching, to govern access control and/or textual form. to guide system behavior.

Categorization might be specified if NotDone is "true" ( expression : notDone done automatically (inferred by code) or notDoneReason.exists().not(), xpath: f:notDone/@value=true() manually by user assertion. The absence of a category may limit the ability to determine when the element should be handled, so strong consideration should be given to how systems will be able to determine category values for legacy data and how data that cannot be categorized will be handled. As well, some categories might not be mutually exclusive, so systems should prepare for multiple declared categories - even within a single category 'axis'. In general, there should not be a 'strong' binding ('required' or not(exists(f:notDoneReason))) 'extensible') on the category element overall. Instead, the element can be sliced and bindings can be asserted that apply to particular repetitions.

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

[In some cases, the service type is implicit based on the scope of the resource and only a product element will be present].

Indicates the product supplied or manipulated by this {{title}}.

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

Links the event {{title}} to the Patient context. May also affect access control.

[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 Encounter during which this {{title}} was created or episode of care that establishes to which the context for creation of this event. record is tightly associated.

Links the request {{title}} to the Encounter context. May also affect access control.

This will typically be the encounter the event occurred within, {{title}} was created during, 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.

The recorded date indicates the date when the data was placed in the record maintained by the performing practitioner, or the date of disclosure by Patient or RelatedPerson, not a date of record transfer. If the record is transferred from one system to another (in paper or electronic form), it does not create a distinct recorded date. In most cases, performing practitioners will record on the same date the event occurred, but sometimes there are delays. If information is being relayed second-hand, the recorded date indicates when the system is first made aware of the data.

The recorded date is NOT intended to be the same as a database.createdTimestamp - that would be captured as part of resource.meta or possibly Provenance.

It is possible for the same event to be disclosed to different systems at different times. E.g. a patient might tell two different clinicians about a historical event at different visits. If the disclosure is from the patient rather than record transfer from clinician A to B, the recorded date would be the date each respective clinician put the data in their record. If the data flowed from clinician A to B, the recorded date would remain the recorded date as initially set in clinician A's system.

Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report.

Reported data may have different rules on editing and may be visually distinguished from primary data.

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. form or Indicates another resource whose existence justifies this {{title}}.

Textual reasons can be captured using reasonCode.text.

Indicates another resource whose existence justifies this event. Comments made about the {{title}} by the performer, subject or other participants.

Comments made about Links to Provenance records for past versions of this resource or component resources that identify key state transitions or updates that are likely to be relevant to a user looking at the event by current version of the performer, subject or other participants. resource.

This element 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. Referenced provenances should adhere to the provenance-relevant-history profile.

See additional guidance here .