Alert flag

Common header for all patient-related data

Patient/subject information

Business identifier for the object

Resource authoring details

Author(s) by whom the resource was/were authored. Multiple authors could be provided.

Date and time of the issuing the document/resource by its author.

Date and time of the last update to the document/information

Status of the resource

Reason for the current status of the resource.

Language in which the resource is written. Language is expressed by the IETF language tag.

BCP 47

Business version of the resource.

A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document

A human-readable narrative that contains a summary of the flag and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Example 1: intolerance to aspirin due to gastrointestinal bleeding. Example 2: intolerance to captopril because of cough (the patient is not allergic but can't tolerate it because of persistent cough) Example 3: the patient has a rare disease that requires special treatment Example 4: Airway Alert / Difficult Intubation Example 5: Diagnoses such as malignant hyperthermia, porphyria, and bleeding disorders; special treatments like anticoagulants or immunosuppressants; implanted devices. Example 6: transplanted organs illustrate other information that has to be taken into account in a healthcare contact. Example 7: participation in a clinical trial that has to be taken into account in a healthcare contact.

A code that identifies the priority of the alert.

hl7:Flag-priority-code

Current status of the flag, Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error.

hl7:Flag-status

A coded or textual representation of the flag.

SNOMED CT

Time period when flag is active. 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.

Alert flag

A human-readable narrative that contains a summary of the flag and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Example 1: intolerance to aspirin due to gastrointestinal bleeding. Example 2: intolerance to captopril because of cough (the patient is not allergic but can't tolerate it because of persistent cough) Example 3: the patient has a rare disease that requires special treatment Example 4: Airway Alert / Difficult Intubation Example 5: Diagnoses such as malignant hyperthermia, porphyria, and bleeding disorders; special treatments like anticoagulants or immunosuppressants; implanted devices. Example 6: transplanted organs illustrate other information that has to be taken into account in a healthcare contact. Example 7: participation in a clinical trial that has to be taken into account in a healthcare contact.

A code that identifies the priority of the alert.

hl7:Flag-priority-code

Current status of the flag, Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error.

hl7:Flag-status

A coded or textual representation of the flag.

SNOMED CT

Time period when flag is active. 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.

Alert flag

Common header for all patient-related data

Patient/subject information

Business identifier for the object

Resource authoring details

Author(s) by whom the resource was/were authored. Multiple authors could be provided.

Date and time of the issuing the document/resource by its author.

Date and time of the last update to the document/information

Status of the resource

Reason for the current status of the resource.

Language in which the resource is written. Language is expressed by the IETF language tag.

BCP 47

Business version of the resource.

A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document

A human-readable narrative that contains a summary of the flag and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Example 1: intolerance to aspirin due to gastrointestinal bleeding. Example 2: intolerance to captopril because of cough (the patient is not allergic but can't tolerate it because of persistent cough) Example 3: the patient has a rare disease that requires special treatment Example 4: Airway Alert / Difficult Intubation Example 5: Diagnoses such as malignant hyperthermia, porphyria, and bleeding disorders; special treatments like anticoagulants or immunosuppressants; implanted devices. Example 6: transplanted organs illustrate other information that has to be taken into account in a healthcare contact. Example 7: participation in a clinical trial that has to be taken into account in a healthcare contact.

A code that identifies the priority of the alert.

hl7:Flag-priority-code

Current status of the flag, Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error.

hl7:Flag-status

A coded or textual representation of the flag.

SNOMED CT

Time period when flag is active. 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.