Alert-v3.0(2016EN)
General information
Name: nl.zorg.Alert 
Version: 3.0
HCIM Status:Final
Release: 2016
Release status: Published
Release date: 1-5-2016
Metadata
| DCM::CoderList | Kerngroep Registratie aan de Bron |
| DCM::ContactInformation.Address | * |
| DCM::ContactInformation.Name | * |
| DCM::ContactInformation.Telecom | * |
| DCM::ContentAuthorList | Projectgroep Generieke Overdrachtsgegevens & Kerngroep Registratie aan de Bron |
| DCM::CreationDate | 15-12-2014 |
| DCM::DeprecatedDate | |
| DCM::DescriptionLanguage | nl |
| DCM::EndorsingAuthority.Address | |
| DCM::EndorsingAuthority.Name | PM |
| DCM::EndorsingAuthority.Telecom | |
| DCM::Id | 2.16.840.1.113883.2.4.3.11.60.40.3.8.3 |
| DCM::KeywordList | alerts, alert, waarschuwing |
| DCM::LifecycleStatus | Final |
| DCM::ModelerList | Kerngroep Registratie aan de Bron |
| DCM::Name | nl.zorg.Alert |
| DCM::PublicationDate | 1-5-2016 |
| DCM::PublicationStatus | Published |
| DCM::ReviewerList | Projectgroep Generieke Overdrachtsgegevens & Kerngroep Registratie aan de Bron |
| DCM::RevisionDate | 1-4-2015 |
| DCM::Superseeds | nl.nfu.Alert-v1.0 |
| DCM::Version | 3.0 |
| HCIM::PublicationLanguage | EN |
Revision History
Only available in Dutch
Publicatieversie 1.0 (01-04-2015)
| ZIB-109 | Onduidelijk wat wel/niet onderdeel uitmaakt van bouwsteen OverdrachtAlert; definities aanpassen |
| ZIB-132 | Aanpassingen in SNOMED CT codes en omschrijvingen voor codelijst AlertTypeCodelijst n.a.v. review terminologie expert. |
| ZIB-203 | In de klinische bouwsteen OverdrachtAlert DCM::ValueSet SNOMED CT aangepast van concept AlertOmschrijving naar tagged value DCM::ContentExpression. |
| ZIB-204 | In de klinische bouwsteen OverdrachtAlert DCM::ValueSet G-Standaard aangepast van concept AlertOmschrijving. |
| ZIB-306 | Aanpassen modellering keuzebox, boundary en cardinaliteit |
| ZIB-308 | Prefix Overdracht weggehaald bij de generieke bouwstenen |
| ZIB-352 | Opsplitsen bouwsteen OverdrachtAlert |
Incl. algemene wijzigingsverzoeken:
| ZIB-94 | Aanpassen tekst van Disclaimer, Terms of Use & Copyrights |
| ZIB-154 | Consequenties opsplitsing Medicatie bouwstenen voor overige bouwstenen. |
| ZIB-200 | Naamgeving SNOMED CT in tagged values klinische bouwstenen gelijk getrokken. |
| ZIB-201 | Naamgeving OID: in tagged value notes van klinische bouwstenen gelijk getrokken. |
| ZIB-309 | EOI aangepast |
| ZIB-324 | Codelijsten Name en Description beginnen met een Hoofdletter |
| ZIB-326 | Tekstuele aanpassingen conform de kwaliteitsreview kerngroep 2015 |
Publicatieversie 3.0 (01-05-2016)
.
Concept
An alert describes a clinical or administrative fact brought to the attention of the users of the clinical systems to be taken into account when shaping diagnostic and therapeutic policy or in dealing with the patient, usually because of a safety risk.
Disorders that describe the body’s sensitivity to a substance which results in a specific physiological reaction after being exposed to that substance are referred to as allergies. These are described in a separate information model.
Warnings for non-allergic disorders can concern:
- A disorder (condition or diagnosis which can be considered as a contraindication for the use of groups of medication or undergoing a certain type of therapy), such as pregnancy or long QT syndrome
- Impaired functioning of an organ system (heart failure, impaired liver or kidney function, weakened immune system)
- Risk of spreading certain microorganisms (multi-resistant bacteria, tubercle bacilli, HIV, HBV, Ebola virus)
- Other risks
Purpose
Documenting and entering disorders or conditions that require attention is an important part of medical registration. It concerns the core of patient safety. In the execution of research and treatment, these patient characteristics - which are marked as a warning - constantly have to be taken into account. They provide information that is important for the patient’s condition and the options a healthcare provider has for therapy. Disorders that are registered or transferred as an Alert can also be described as a Problem. The difference is in the fact that the healthcare provider considers the problem as an Alert = warning. In many cases, transfer will be subject to strict privacy rules, as the warning will not always elicit an adequate reaction in the informed environment.
Information Model
| Type | Id | Concept | Card. | Definition | DefinitionCode | Reference | |||||||
|
NL-CM:8.3.1 |  Alert
|
Root concept of the Alert information model. This root concept contains all data elements of the Alert information model. | ||||||||||
|
NL-CM:8.3.3 |  Condition::Concern
|
(0..1) | The patient’s health problem or condition that is the subject of the alert. This could involve a patient’s problem, condition or diagnosis that is seen as a contraindication in prescribing medication or which has to be taken into account when shaping diagnostic and therapeutic policy. This can be in the patient’s own interest, or it can involve a problem or disorder that can make the patient a risk to their surroundings, such as an infection hazard. These are references to conditions included on the patient’s problem list.
If there is a contraindication, the code system G-Standard Contraindications (Table 40) from the ProblemNameCodeList of the ConcernTransfer information model should be used. |
| ||||||||
|
NL-CM:8.3.4 | AlertName
|
(0..1) | A warning, other than a condition or problem. For example, a patient can be given an ‘Aggressive patient' alert.
The warning can be entered in code (there are codes for frequently used alerts), but seeing the dynamic nature of the warnings cf. SARS and Ebola, these alerts will often be entered as free text. |
| ||||||||
|
NL-CM:8.3.5 | StartDateTime
|
0..1 | The date and time at which the described condition was entered as a warning.
This can be an exact date and time, or a rough indication of the date (such as only the year, or the month and the year). |
|||||||||
|
|
NL-CM:8.3.6 | AlertType
|
1..1 | Indicates the type of alert, meaning a rough description of the cause or origin of the warning. |
| ||||||||
Columns Concept and DefinitionCode: hover over the values for more information
For explanation of the symbols, please see the legend page 
Example Instances
Only available in Dutch
| AlertType | BegindatumTijd | Conditie |
| ProbleemNaam | ||
| Conditie | 15-9-2012 | Zwanger |
| AlertType | BegindatumTijd | AlertNaam |
| Waarschuwing | 01-06-2010 | Drager MRSA |
Valuesets
AlertNameCodelist
| Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.8.3.2 | Binding: |
| Conceptname | Conceptcode | Codesystem name | Codesystem OID | Description |
| Infectious disease carrier | 66598005 | SNOMED CT | 2.16.840.1.113883.6.96 | Drager van besmettelijke ziekte |
| Methicillin resistant staphylococcus aureus carrier | 432415000 | SNOMED CT | 2.16.840.1.113883.6.96 | Drager MRSA |
| Carrier of vancomycin resistant enterococcus | 431109006 | SNOMED CT | 2.16.840.1.113883.6.96 | Drager VRE |
| Human immunodeficiency virus (HIV) carrier | 699433000 | SNOMED CT | 2.16.840.1.113883.6.96 | Drager HIV |
| Other | OTH | NullFlavor | 2.16.840.1.113883.5.1008 | Anders |
AlertTypeCodelist
| Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.8.3.1 | Binding: |
| Conceptname | Conceptcode | Codesystem name | Codesystem OID | Description |
| condition | 75323-6 | LOINC | 2.16.840.1.113883.6.1 | conditie |
| alert | 74018-3 | LOINC | 2.16.840.1.113883.6.1 | waarschuwing |
This information model in other releases
- Release 2015, (Version 1.0)
- Release 2017, (Version 3.2)
- Prerelease 2018-2, (Version 3.3)
- Prerelease 2019-2, (Version 4.0)
- Release 2020, (Version 4.1)
- Prerelease 2021-2, (Version 4.1)
- Prerelease 2022-1, (Version 4.1)
- Prerelease 2023-1, (Version 4.1)
- Prerelease 2024-1, (Version 4.2)
Information model references
This information model refers to
This information model is used in
- --
Technical specifications in HL7v3 CDA and HL7 FHIR
To exchange information based on health and care information models, additional, more technical specifications are required.
Not every environment can handle the same technical specifications. For this reason, there are several types of technical specifications:
- HL7® version 3 CDA compatible specifications, available through the Nictiz ART-DECOR® environment
- HL7® FHIR® compatible specifications, available through the Nictiz environment on the Simplifier FHIR
Downloads
This information model is also available as pdf file 
or as spreadsheet 
About this information
The information in this wikipage is based on Release summer 2016
Conditions for use are located on the mainpage
This page is generated on 21/12/2018 15:37:50 with ZibExtraction v. 3.0.6929.24609