Prospective warnings of potential issues when providing care to the patient.

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

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

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.

Supports basic workflow.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Allows a flag to be divided into different categories like clinical, administrative etc. Intended to be used as a means of filtering which flags are displayed to particular user or in a given context.

The value set will often need to be adjusted based on local business rules and usage context.

The coded value or textual component of the flag to display to the user.

If non-coded, use CodeableConcept.text. This element should always be included in the narrative.

The patient, related person, location, group, organization, or practitioner etc. this is about record this flag is associated with.

The period of time from the activation of the flag to inactivation of the flag. If the flag is active, the end of the period should be unspecified.

This alert is only relevant during the encounter.

If both Flag.encounter and Flag.period are valued, then Flag.period.start shall not be before Encounter.period.start and Flag.period.end shall not be after Encounter.period.end.

The person, organization or device that created the flag.

Additional information that may be relevant to the flag, such as why the flag was created or how to guide management of the flag.

For example, when the flag represents an alert on difficulty in intubation, supportingInfo could reference details about previous incidents of intubation problems encountered. When the flag represents an alert on swallow or speech difficulty, supportingInfo could reference specific details about stroke or laryngeal carcinoma undergoing radiation therapy as primary or adjuvant therapy to surgery, or damage to recurrent laryngeal nerve from thyroid surgery or tumor. Flag.supportingInfo replaced the extension http://hl7.org/fhir/StructureDefinition/flag-detail in R6. In previous versions, using this extension is correct, not the R6 version extension.