HCIM Release 2020(EN)
Versie door Update bot (overleg | bijdragen) op 20 aug 2024 om 12:14
This is the most recent HCIM prerelease.
The most recent HCIM prerelease is ''2024''.
Inhoud
- 1 Release 2020
- 2 Health and care information models release 2020
- 2.1 group: Administrative, count: 7
- 2.2 group: Clinical context, count: 25
- 2.3 group: Measurements, count: 15
- 2.4 group: Medication, count: 7
- 2.5 group: Partial information models, count: 8
- 2.6 group: Patient context, count: 17
- 2.7 group: Scales en screening tools, count: 14
- 2.8 group: Selfcare, count: 10
- 2.9 group: Treatment, count: 7
- 3 New information models and deprecated information models in release 2020
- 4 Errata release 2020
- 5 Special information models
- 6 Downloads
- 7 Additional information
Release 2020
This is a release. More information about prereleases and releases you can find here.
The following summary shows which hcim's are part of this release, including the version numbers.
More information on Release 2020 you can find in the ReleaseNotes 2020 
(in Dutch) and in the sections below.
Health and care information models release 2020
group: Administrative, count: 7
| CareTeam-v1.0 | Encounter-v4.0.1 | HealthProfessional-v3.5 | Payer-v3.1.1 |
| ContactPerson-v3.4 | HealthcareProvider-v3.4 | Patient-v3.2 |
group: Clinical context, count: 25
group: Measurements, count: 15
group: Medication, count: 7
| AdministrationAgreement-v1.0.3 | MedicationAdministration2-v1.1.1 | MedicationContraIndication-v1.0 | MedicationUse2-v1.1.1 |
| DispenseRequest-v1.0.3 | MedicationAgreement-v1.2 | MedicationDispense-v2.0.2 |
group: Partial information models, count: 8
| AddressInformation-v1.1 | ContactInformation-v1.2 | NameInformation-v1.1 | Range-v1.0.1 |
| AnatomicalLocation-v1.0 | InstructionsForUse-v1.2.1 | PharmaceuticalProduct-v2.1.2 | TimeInterval-v1.0 |
group: Patient context, count: 17
group: Scales en screening tools, count: 14
group: Selfcare, count: 10
group: Treatment, count: 7
| CareAgreement-v1.0 | NursingIntervention-v3.2 | Procedure-v5.2 | TreatmentObjective-v3.2 |
| FreedomRestrictingIntervention-v1.0 | OutcomeOfCare-v3.2 | TreatmentDirective2-v1.0 |
New information models and deprecated information models in release 2020
In release 2020 a number of new information models are added to the national set of HCIM's.
A number of existing information models on the other hand are declared deprecated.
New HCIM's
Deprecated HCIM's
| BasicElements |
| FreedomRestrictingMeasures |
| GeneralMeasurement |
| TreatmentDirective |
Reason for deprecation
- BasisElementen
- The reason for the withdrawal of the BasicElements HCIM is that from the beginning of the existence of the HCIMs and the BasicElements HCIMs, there has been discussion about the data elements in BasicElements in relation to individual HCIMs:
- InformationSource: not clinically relevant for every HCIM, and moreover not clear for each HCIM what is meant by this, especially in relation to the element Author.
- Subject: implicitly this is always the patient. In the sporadic cases where the patient is not the subject, this has already been explicitly modeled in the HCIMs concerned, as in FamilyHistory, for example.
- DateTime: often multiple dates and times are relevant and relevant in zibs and the basic element creates confusion. It has already been explicitly modeled in many zibs.
- Author: not clinically relevant for every HCIM, and moreover not clear for each HCIM what is meant by this, especially in relation to the source of the information and the recorder in the file.
- IdentificationNumber: not clinically relevant for every HCIM and, moreover, usually without clinical significance. And for HCIMs, where this is not a point of discussion, it is often already modeled in the HCIM concerned.
- Consequences of the withdrawal of the Basic Elements HCIM::
- For HCIMs, for which this is (clinically) relevant, some of the data elements that were present in BasisElements in (Pre-)publications prior to Publication 2020 will be modeled in the HCIM itself, if not already present. The clinical significance will be defined in the context of the HCIM concerned.
- Users of the HCIMs are called upon to indicate (by submitting a change proposal to the HCIM concerned) which data elements from the BasicElements must be explicitly modeled, and what the clinical significance is, of which (1.) has not yet been done is.
- The fact that the BasisElements HCIM in Publication 2020 no longer exists means that data elements from the BasicElements, which are not explicitly modeled in the HCIM concerned, can possibly be added, for example, and in particular in application datasets.
- FreedomRestrictingMeasures
- The FreedomRestrictingMeasures HCIM is superseded by the FreedomRestrictingIntervention HCIM as a result of new legislation on involuntary care (Mandatory Care In Mental Health Act and the are and Compulsion Act).
- GeneralMeasurement
- The HCIM GeneralMeasurement is deprecated. As of release 2020 a different approach will be used for this type of generic information models. For more informtion, see special wiki page on templates.
- TreatmentDirective
- The TreatmentDirective HCIM has been replaced by the TreatmentDirective2 HCIM. If the concept of a HCIM contains fundamental changes, then the agreement (also laid down in ISO13972) is that the HCIM in question will be renamed and will get a new id, which also indicates that there is no backwards compatibility. This is the case for TreatmentDirective, partly due to the input from primary care.
Errata release 2020
After the publication of release 2020, the following errors in the release came to light.
| Issue ZIB-1252 | Date | 12-11-2020 | |
| Information model: | NursingIntervention-v3.2 | Subject: | Reference to codelist InterventionNICCodelist |
| The concept Intervention includes a reference to the NIC as a permitted coding system to code an intervention. This option is no longer valid. Therefore, only a term from SNOMED CT can be selected for coding an intervention. | |||
| Issue ZIB-1378 | Date | 23-06-2021 | |
| Information model: | ContactPerson-v4.3 | Subject: | RolCodelist has numeric codes (1,2,3,..) in stead of strings (01,02,03,...) |
| In valueset RolCodelist the concept codes 1 - 9 should be extended with one leading zero and therefore must be changed to 01 - 09. | |||
| Issue ZIB-1477 | Date | 18-08-2021 | |
| Information model: | Problem-v4.4 | Subject: | Modification codelijst ProblemNameCodelist |
| The ProbleemNameCodelist of the concept ProblemName contains een entry voor NANDA-I as codesystem to code a problem. This option is no longer available. | |||
| Issue ZIB-1454 | Date | 29-09-2021 | |
| Information model: | MedicationAgreement-v1.2 | Subject: | Replacement of deprecated SNOMED CT codes in <HCIMname>StopTypeCodelist codelists |
| MedicationUse2-v1.1.1 | |||
| AdministrationAgreement-v1.0.3 | |||
| The <HCIMname>StopTypeCodelist's contain two codes that are never activated en that are replaced with new codes . It concerns the codes 112171000146100 (Drug therapy temporarily stopped) en 112161000146106 (Drug therapy definitively stopped). They are replaced with the codes 113381000146106 resp. 113371000146109. The new codes have the same name and description as the old codes. | |||
| Issue ZIB-1201 | Date | 30-09-2021 | |
| Information model: | Pregnancy-v4.0 | Subject: | Modification SNOMED CT code of the rootconcept |
| The Snomed code of rootconcept is changed from 364320009 to 118185001, Finding related to pregnancy, with reason that the current code is an observable entity which is not the correct type for a root concept within the SNOMED system. | |||
| Issue ZIB-1296 | Date | 06-10-2021 | |
| Information model: | Burnwound-v3.4 | Subject: | Concept BurnType erroneously removed |
| In Release 2020, the BurnType concept was erroneously removed from the BurnWound information model. The information model should also include this concept in this publication as described in prerelease 2019, including the associated codelist. | |||
| Issue ZIB-1314 | Date | 07-10-2021 | |
| Information model: | GlasgowComaScale-v3.2 | Subject: | Replacement of the Verbal en Motor code lists |
| In Release 2020, the Verbal and Motor code lists have been modified. Unfortunately, a number of serious mistakes have been introduced in the lists. It has therefore been decided to replace these code lists entirely. The new codelists can be found in attached document
| |||
| Issue ZIB-1856 | Date | 08-03-2023 | |
| Information model: | AllergyIntolerance-v3.3 | Subject: | Replacement deprecated reference set SNOMED CT |
| The CausativeAgentAllergicAgentCodelist used in the CausativeAgent concept and the SpecificSubstanceAllergicAgentCodelist used in the SpecificSubstance concept, refer to a deprecated reference set in SNOMED CT: 42931000146101. The reference set has been replaced by: 98061000146100. | |||
| Issue ZIB-1536, ZIB-1586 | Date | 05-07-2023 | ||||||||||||||||
| Information model: | MedicalDevice-v3.3.1 | Subject: | Add values for ‘none’ to ProductTypeCodelist, allow OTH with required Binding | |||||||||||||||
To ensure that the constrained value lists (see for definition https://zibs.nl/wiki/Codelist_Bindings) VisualAidTypeCodelist (from VisualFunction -v3.1) and HorenHulpmiddelTypeCodelijst (from HearingFunction-v3.2) do not contain values that do not appear in the base value list ProductTypeCodelist, add the following values to ProductTypeCodelist:
Also it is clarified that the value OTH from the NullFlavor code system is also available for required bindings unless otherwise defined (see for definition https://zibs.nl/wiki/Codelist_Bindings). | ||||||||||||||||||
| Issue ZIB-1977 | Date | 07-07-2023 | |
| Information model: | DOSScore-v1.0 | Subject: | How to deal with "-" in the observations for DOSScore. |
| For all score elements when an answer is "don't know" one should not use the value "-" but instead should not instantiate the concept. | |||
| Issue ZIB-1917 | Date | 26-10-2023 | |
| Information model: | VisualAcuity-v1.0 | Subject: | Changes to definition codes |
| In the HCIM, VisusAcuityType and DecimalVisusAcquity have the same definition code, this is not allowed. In addition, the root concept has a definition code which fits better for VisusAcuityType. Therefore, the following concepts have a new definition code:
Root concept Visus changes to SNOMED-CT: 260246004 Visual acuity finding VisusMeasurementType changes to SNOMED-CT: 16830007 Visual acuity testing | |||
| Issue ZIB-1635 | Date | 20-08-2024 | |
| Information model: | SNAQrcScore-v1.1 | Subject: | Change total score range. |
| Adjust value range zib SNAQrc from 0-5 to 0-6 to allow valid score (6). | |||
When using publication 2020, the solutions mentioned for these errors must be applied.
The solutions of these issues will be included in the next (pre)release.
Special information models
Partial information models
To enable reuse of information patterns, which do not themselves describe a complete (care) concept, partial information models (substructures) have been defined and applied.
Unlike complete HCIM’s, partial information models are never used independently, but always included (inclusion) in the model of a complete HCIM.
See Architecture Document Volume 1 for more information on this.
Partial information models can be identified by the prefix "nl.zorg.part" in the HCIM name.
Templates for HCIM's
As of publication 2020, templates will be used where possible as design patterns for the development of new HCIM's.
More information about these templates can be found on the special wiki page on this topic. This page is also accessible via the main menu on the left of this page.
Downloads
At the bottom of each HCIM wikipage you can find links to download the HCIM information in PDF of XLSX format.
It is also possible to download the whole set of HCIM's of this release in one file as PDF
(71 MB), XLSX or XMI. The last file also contains valuelist in XML format.
Additional information
NEW!
- Starting from prepublication 2018-1, LOINC and SNOMED CT terms are displayed in Dutch wikipages in Dutch and in English wikipages in English, if an official translation is available.
- A section has been added to each HCIM wikipage indicating which other HCIM's the building block refers to and in which other HCIM's the HCIM is used.
