Page tree
Skip to end of metadata
Go to start of metadata

Published  


Table of contents



Changes introduced: MVC 2.2.2 to MVC 3.0.0.RC1

Value SetChangeJustification of the change: Change Proposal

epSOSUnits

  • NEW CODE SYSTEM OID

The source of the 'Table of Example UCUM Codes for Electronic Messaging' has OID: 1.3.6.1.4.1.12009.10.3.1

Up to MVC 2.2.2 the OID for UCUM was used: 2.16.840.1.113883.6.8

Adoption of the 'Table of Example UCUM Codes for Electronic Messaging'

(https://loinc.org/usage/units/)

  • NEW CONTENT FOR THE VALUE SET

The complete content (812 codes) included in the 'Table of Example UCUM Codes for Electronic Messaging', version 1.4, released 18/07/2016.

With the content from the 'Table of Example UCUM Codes for Electronic Messaging', the issue identified in the previous version of the Value Set, the one referred to the use of the Greek letter 'μ' instead of 'u' to represent 'micro', will be solved.

epSOS Absent and Unknown Information Value Sets

  • NEW CODE SYSTEM

Adoption of the Code System IPS Absent and Unknown Data, OID 2.16.840.1.113883.5.1150.1

Adoption of the IPS Code system Absent and Unknown Data and 5 Value Sets derived from it


  • 5 NEW VALUE SETS
    • eHDSI-AbsentOrUnknownAllergies - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.47
    • eHDSI-AbsentOrUnknownDevices - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.48
    • eHDSI-AbsentOrUnknownMedication - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.49
    • eHDSI-AbsentOrUnknownProblems - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.50
    • eHDSI-AbsentOrUnknownProcedures - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.51

With the content specified below:

eHDSI-AbsentOrUnknownAllergies - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.47
CodeDisplay NameCode SystemDescription
no-allergy-infoNo information about allergiesIPS CodeSystem - Absent and Unknown DataThere is no information available regarding the subject's allergy conditions
no-known-allergiesNo known allergiesIPS CodeSystem - Absent and Unknown DataThe subject has no known allergy conditions
no-known-medication-allergiesNo known medication allergiesIPS CodeSystem - Absent and Unknown DataThe subject has no known medication allergy conditions
no-known-environmental-allergiesNo known environmental allergiesIPS CodeSystem - Absent and Unknown DataThe subject has no known environmental allergy conditions

no-known-food-allergies

No known food allergiesIPS CodeSystem - Absent and Unknown DataThe subject has no known food allergy conditions
eHDSI-AbsentOrUnknownDevices - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.48
CodeDisplay NameCode SystemDescription
no-device-infoNo information about deviceIPS CodeSystem - Absent and Unknown DataThere is no information available regarding implanted or external devices for the subject
no-known-devicesNo known devices in useIPS CodeSystem - Absent and Unknown DataThere are no devices known to be implanted in or used by the subject that have to be reported in this record. This can mean either that there are none known, or that those known are not relevant for the purpose of this record
eHDSI-AbsentOrUnknownMedication - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.49
CodeDisplay NameCode SystemDescription
no-medication-infoNo information about medicationsIPS CodeSystem - Absent and Unknown DataThere is no information available about the subject's medication use or administration
no-known-medicationsNo known medicationsIPS CodeSystem - Absent and Unknown DataThere are no medications for the subject that have to be reported in this record. This can mean either that there are none known, or that those known are not relevant for the purpose of this record
eHDSI-AbsentOrUnknownProblems - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.50
CodeDisplay NameCode SystemDescription
no-problem-infoNo information about current problemsIPS CodeSystem - Absent and Unknown DataThere is no information available about the subject's current health problems or disability
no-known-problemsNo known problemsIPS CodeSystem - Absent and Unknown DataThe subject is not known to have any health problems or disabilities that have to be reported in this record. This can mean either that there are none known, or that those known are not relevant for the purpose of this record
eHDSI-AbsentOrUnknownProcedures - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.51
CodeDisplay NameCode SystemDescription
no-procedure-infoNo information about past history of proceduresIPS CodeSystem - Absent and Unknown DataThere is no information available about the subject's past history of procedures
no-known-proceduresNo known proceduresIPS CodeSystem - Absent and Unknown DataThe subject has no history of procedures that have to be reported in this record. This can mean either that there are none known, or that those known are not relevant for the purpose of this record
  • REMOVED VALUE SETS
    • epSOSUnknownInformation - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.17
    • epSOSCodeNoMedication - OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.22
Value SetChangeJustification of the change: Fix

epSOSDisplayLabel

The following codes will be added to the Value Set: codes that were missing and for that reason currently hard coded in the CDA Display Tool (Reference Implementation)

Concept CodeDescription
108Original narrative
109Translated coded
110Clinical sections
111Prescription and Dispensation details
112Code System
113Code
114Name
115Dispensed Number of packages
116If substitution of brand name is marked as not allowed, pharmacists may still consider dispensing the national equivalent even though the brand name might be slightly different.
This is a known situation: the same pharmaceutical company is marketing the same medicinal product in different countries with slightly different names due to marketing reasons.
If the pharmacist is certain that this is the case, the systems allows the input of the new brand name.
117Original Document Language
118Diagnostic Date
119Blood Group
120Min
121Max
122Administered
123Severity
  • Inclusion of concepts needed due to being hard coded labels in the CDA Display Tool (Reference Implementation)

EHSEMANTIC-394 - Getting issue details... STATUS

The following concepts will be removed from the Value Sets given that they are not used by the CDA Display Tool (Reference Implementation)

Concept CodeDescription
14Country A Medicinal Product Code
57Prescriber details
59Prescription Item Details
60Prescription Item ID
61Prescription Items List
82I have identified the patient-data subject
83I confirm that the patient –data subject has consented to the following statement: ‘I agree that my ePrescription may be transferred to a registered Health Professional in [COUNTRY B] for the purposes of providing me with medical care and/or medication’
99Physical Findings
100+/-
107I confirm that the patient –data subject has consented to the following statement: ‘I agree that my Patient Summary may be transferred to a registered Health Professional in [COUNTRY B] for the purposes of providing me with medical care and/or medication’

epSOSIllnessesandDisorders

This Value Set was expected to contain all four-character codes from the WHO International Classification of Diseases 10th Revision: including the ones that are not present as such in the release file, but need to be generated by the processing of the Modifier Element of the ClaML file.

The concepts to be added to the Value Set are: ICD-10 missing four-character codes_2016.xlsx

  • Inclusion of missing four-character codes from WHO ICD-10 (which were never included in the epSOS and EXPAND MVC)
    EHSEMANTIC-410 - Getting issue details... STATUS

Removal of  Chapter titles and "blocks" of three-character categories of the structure of the Classification, as these are not intended for encoding information and should not be part of the Value Set: e.g. A00-A09 - Intestinal infectious diseases.

The concepts to be removed from the Value Set are: ICD-10 Chapter titles and blocks to remove from epSOSIllnessesandDisorders.xlsx

  • Remove Chapter titles and blocks of three-character categories
    EHSEMANTIC-406 - Getting issue details... STATUS



Tips to upgrade to a new version of the MVC


This section contains tips or strategies to facilitate deploying countries already working on their MTC to upgrade to a new version as well as to easily publish a new version of the national MTC in the Central Terminology Services as a result of the release of a new version of the MVC.

1. Uploading and publishing a new version of the national MTC in the Central Terminology Services (CTS)

For deploying countries that already uploaded and published their national MTC in the CTS:

The final step, after uploading translations and transcodings to the CTS, is the publishing of the national MTC by clicking on the "Agree" button. This action - performed by the Country Terminology Responsible Author/Curator - will then allow the synchronisation of the content of the national MTC with the Local Terminology Repository in the NCPeH.

If a country uploaded and published its MTC corresponding to the MVC 2.2.2, the way to proceed to upload, translate/transcode, and publish the new MTC - corresponding to the MVC 3.0.0.RC1 - is the following:

(info) Please note that not all situations are applicable for the upgrade to the MVC 3.0.0.RC1

1

Export the Excel files for translations and transcodings (Check the User Guide for the CTS here)

22.1

Value Sets with a new version of the underlying code system will have the cells for translations and transcodings empty.

Carefully copy and paste the content of your previous MTC (translations and transcodings).

This situation is not applicable in the upgrade from MVC 2.2.2 to MVC 3.0.0.RC1

2.2

Value Sets affected by the fixing of typos in the display name in English → check that your translations are correct.

This situation is not applicable in the upgrade from MVC 2.2.2 to MVC 3.0.0.RC1

2.3

Value Sets affected by removal of deprecated/inactive/erroneous concepts or by the addition of new concepts → if you had mapped in the previous version of the MVC to those excluded concepts, you should now establish new mappings to the existing concepts when appropriate.

Removal of concepts from MVC 2.2.2 to 3.0.0: Release details above.

Translate the new concepts included in the MVC 3.0.0

(lightbulb) In this case, when the number of changes in a Value Set is limited (for example, to the epSOSDisplayLabel Value Set), other option is to skip this step and import the Excel files (point 3). Consequently, no mappings or translations have been added to the new concepts (the line in the Excel file was left empty) and the new translations and mappings could then be added using the new features for translation and mapping.
2.4Value Sets whose content has not changed from the previous version of the MVC present the same content as it was uploaded (imported) previously and no action is required from your side.
3Upload (import) the Excel files with the translations and the transcodings to the CTS
4Publish the new version of the MTC by clicking the "Agree" button, that action will permit the synchronisation with the LTR in the NCPeH

(info) Alternatively:

1

Use only the new translation and mapping features of the CTS (Check the User Guide for the CTS here)

2Publish the new version of the MTC by clicking the "Agree" button, that action will permit the synchronisation with the LTR in the NCPeH




2. Deploying countries working on translations and transcodings not already uploaded and published in the CTS

Deploying countries may still be working on translations and/or mappings to the MVC 2.2.2 - this depends on their national policy and it may not be necessary to translate all Value Sets or perform some mappings.

For these countries, the way to upgrade to the MVC 3.0.0.RC1 could be:

1Export the Excel files for translations and transcodings from the CTS (Check the User Guide for the CTS here)
2Identify the Value Sets in which you have been working that have been impacted by the changes, for this check the Release details above

2.1Value Sets with new concepts included (e.g. epSOSDisplayLabel Value Set): copy and paste carefully your previous work, translate and transcode as necessary the new concepts.

2.2Value Sets where concepts have been excluded (e.g. epSOSDisplayLabel Value Set): remove those concepts from your previous work and copy paste into the new one.

2.4Check the overall correctness of the impacted Value Sets
3Continue working with translations and transcodings
4Once finished the previous step upload (import) the Excel files with the translations and the transcodings to the CTS
5Publish the MTC by clicking the "Agree" button, that action will permit the synchronisation with the LTR in the NCPeH

(info) Alternatively, and depending on the extent of the work already performed translating/transcoding the MVC 2.2.2:

1Consider uploading and publishing the MTC corresponding to the MVC 2.2.2
2

Use the new translation and mapping features of the CTS (Check the User Guide for the CTS here)

3Once finished, publish the MTC by clicking the "Agree" button, that action will permit the synchronisation with the LTR in the NCPeH


  • No labels