eHealth Digital Services
Infrastructure –
Semantic task force
January 11, 13.00-16.00 CET
Agenda
• Welcome!
• Meeting minutes – December 22
• Round table
• Members and e-mail list
• Substance information
• Change proposals
• MVC 2.0
• Work ahead, next steps and time plan
• Any other business
• Snomed CT licence status update
• Next meeting
• Close of meeting
Meeting minutes
• Comments?
• https://ec.europa.eu/cefdigital/wiki/display/EHSEMANTIC/2016-1222+WG+on+Semantics
• Priview in browser may not work. Download button works fine.
Round table
• What has happened since last week
WG Semantic participants
Name
Peter Brosch
Ingrid Mertens
Niklas Kramer
Norbert Sigmond
Marta TERRON CUADRADO (SANTE)
Arturo Romero
France TEAM
Carla Pereira
Estefania Araujo
Tiago Soares
Oskar Thunman
MS
AT
BE
DE
DE
EC
ES
FR
PT
PT
PT
SE
email
Coord.
Organ.
Archit.
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
m
m
m
m
m
Semanti
c
m
m
m
m
m
m
m
m
m
m
C
Info
Substance information
Question on intentions to use list of substances maintained by the European Medicines
Agency
• Sent to
• Croatia, Finland, Estonia, Sweden
• Suggestion: Follow up with a separate meeting. In January?
• With these countries + STF WG leaders and Licinio.
Change proposals
• Change Proposal ready for Consultation by Semantic Task Force
• 008
• 009
• 011
• 012
• Due date: January 19, 2017
• Next steps?
• Distribute to the entire STF
• Send feedback to Oskar, no later than Wednesday
MVC 2.0 initial findings
The hypothesis from last meeting was that there were two types of activities
that would be needed to prepare MVC 2.0 for production:
1. 1. Remove technical Value Sets
1. Label of CDA display tool
2. Label of document
3. Error messages
2. 2. Update ValueSets to the latest version of the underlying CodeSystem
3. Additional to this is the descision to act on recommendations from
EXPAND.
MVC 2.0
ValueSets target for removal
Removal means Moving the ValueSets from the MVC and instead making them part
of the Implementation Guides as they are not translated and are of technical
nature.
Suggested valueSets to be made obsolete:
•
•
•
•
•
•
epSOSActCode, 1.3.6.1.4.1.12559.11.10.1.3.1.42.29
epSOSActSite, 1.3.6.1.4.1.12559.11.10.1.3.1.42.44
epSOSEntityNamePartQualifier, 1.3.6.1.4.1.12559.11.10.1.3.1.42.33
epSOSIHEActCode, 1.3.6.1.4.1.12559.11.10.1.3.1.42.35
epSOSIHERoleCode, 1.3.6.1.4.1.12559.11.10.1.3.1.42.36
epSOSURL, 1.3.6.1.4.1.12559.11.10.1.3.1.42.42
•
Also epSOSMedicalEquipment and epSOSObservationInterpretation are in the MVC but not
used in the CDA:s. Remove?
Status: Active, Depricated, Development or relevant status codes.
MVC 2.0
VaueSets needing updating
Updating a valueSet in this context is to be done for CodeSystems that are subject to
reoccuring releases of new versions.
Identified valueSets are:
•
epSOSActiveIngredient, 1.3.6.1.4.1.12559.11.10.1.3.1.42.24
•
epSOSDoseForm, 1.3.6.1.4.1.12559.11.10.1.3.1.42.2
•
epSOSPackage, 1.3.6.1.4.1.12559.11.10.1.3.1.42.3
•
epSOSRouteofAdministration, 1.3.6.1.4.1.12559.11.10.1.3.1.42.12
•
epSOSIllnessesandDisorders, 1.3.6.1.4.1.12559.11.10.1.3.1.42.5
•
+ All of the Snomed CT based ValueSets, although for this time only one term has been updated.
Explain "version" selection for each yearly cycle. Pick the right version for this MVC Release.
Example: allow removal of deprecated Snomed CT concepts more frequently.
MVC 2.0
Other recommendations from EXPAND
Clarify the use:
•
epSOSHealthcareProfessionalRoles, 1.3.6.1.4.1.12559.11.10.1.3.1.42.1: Consider if
provide an intensional definition of this value set
•
epSOSPatientContactRole, 1.3.6.1.4.1.12559.11.10.1.3.1.42.39: Consider to
provide an intensional definition of this value set.
•
epSOSTimingEvent, 1.3.6.1.4.1.12559.11.10.1.3.1.42.41: Consider if provide an
intensional definition
MVC 2.0
Other recommendations from EXPAND
Replace:
•
epSOSAdministrativeGender, 1.3.6.1.4.1.12559.11.10.1.3.1.42.34: Evaluate the
usage of the HL7 Value Set
•
epSOSConfidentiality, 1.3.6.1.4.1.12559.11.10.1.3.1.42.31: Consider providing an
intensional definition of this value set and/or refer directly to the “standard” value
set.
•
epSOSCountry, 1.3.6.1.4.1.12559.11.10.1.3.1.42.4: Consider extending this value
set to the whole code system
•
epSOSLanguage, ISO 639-1 1.0.639.1 1 1.3.6.1.4.1.12559.11.10.1.3.1.42.6:
Consider using instead IETF RFC 5646 and change the binding rules
•
epSOSSubstitutionCode, 1.3.6.1.4.1.12559.11.10.1.3.1.42.7: Consider the results
of the openmedicine project for possible updates
•
epSOSUnits, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16: Adopt the wider set of units see
e.g. Table of Example UCUM Codes for Electronic Messaging - Version 1.3. Concider
having several valueSets for differet purposes.
MVC 2.0
Other recommendations from EXPAND
Ask member states to add codes to the ValueSet?
•
epSOSProcedures, 1.3.6.1.4.1.12559.11.10.1.3.1.42.10: : re-evaluate the need of
updating this value set
•
epSOSReactionAllergy, 1.3.6.1.4.1.12559.11.10.1.3.1.42.11: : this value set should
be reconsider for possible updates
•
epSOSSocialHistory, 1.3.6.1.4.1.12559.11.10.1.3.1.42.14: Consider making the
listed concepts obsolete, Specify an ad hoc (new) value set for describing Diet
•
epSOSVaccine, 1.3.6.1.4.1.12559.11.10.1.3.1.42.28
Material from EXPAND
THE EXPERIENCE OF SELECTING THE CODE SYSTEMS FOR THE DEVELOPMENT OF THE
The following criteria were adopted in order to define a Value
EPSOS MVC_V_1.0:
Coding Systems Selecting Criteria
•
•
Internationally Used
•
In Use
•
Existence of translation in Different
Languages
Set
•
If the coding system is adopted by the large majority of the
PNs and translations are available for all the languages and
it is fully in scope with the associated dataset:
•
The full coding system is adopted as Value Set. The example is
ATC for active ingredients.
•
Has a Maintenance Process
If the Coding System is adopted by the large majority of the
PNs and translations are available for all the languages, but
there are terms non related to the Data Set
•
Existence of Transcoding
•
•
Cost of licenses, implementation and
maintenance
•
The code system must be easily
implementable
•
•
Terms related to the Data Set are selected. The example ISO
for languages, EDQM for route of administration and dose
form; in this case there are also limitations on translations.
If the selected coding system is not adopted by the large
majority of the PNs (transcoding is required) and the
translations are not available:
•
A careful analysis is performed with the domain experts
(physicians, pharmacists) in order to identify the needed Value
Set to provide adequate capability of covering the large
majority of the clinical cases, limiting the effort of translation
and avoiding, as far as possible, the risk of having potential
one-to-many mapping alternatives (avoiding ambiguities).
Examples are all the SNOMED-CT related Value Set and ICD10
for Problems.
Work ahead, next steps and time plan
•
Final decision by January 25
•
Light Change Proposals by Jan 18 (Oskar)
•
Next meeting
• January 25, 14.00-16.00 CET
Thank you!