- 1: epSOS Home.
- 2: About epSOS.
- 3: Project Structure & Results.
- 3.1: Work Package 1.1.
- 3.2: Work Package 1.2.
- 3.3: Work Package 1.3.
- 3.4: Work Package 2.1.
- 3.5: Work Package 3.1.
- 3.6: Work Package 3.2 .
- 3.7: Work Package 3.3.
- 3.8: Work Package 3.4.
- 3.9: Work Package 3.5.
- 3.10: Work Package 3.6.
- 3.11: Work Package 3.7.
- 3.12: Work Package 3.8.
- 3.13: Work Packages 3.9 and 3.10.
- 3.14: Work Package 4.1.
- 3.15: Work Package 4.2.
- 3.16: Work Package 4.3.
- 3.17: Work Package 4.4.
- 3.18: Work Package 5.1.
- 3.19: Work Package 5.2.
- 3.20: Work Package 5.3 .
- 4: epSOS Countries.
- 5: Large Scale Pilot.
- 6: FAQ.
- 7: News & Events.
- 8: Press section.
- 9: Links & Collaborations.
- 10: Download Area.
- 11: Glossary.
Work Package Output
1. A document defining Semantic Services
Deliverables
D.3.5.2: Semantic Services Definition
Work Package 3.5: Semantic Services
Work Package Description
Health Care Providers requesting information, for example a Patient Summary from a different Member State, have to be provided with a document translated into the official language of their own country for the sake of applicability and comprehension. The goal is that, while each country continues to use its own terms, they shall be understood by all other Member States in an automatic fashion, leaving no room for ambiguity and therefore preventing medical error.
Achieving this aim of semantic interoperability is the task of WP 3.5. Through the definition of an epSOS Master Translation/Transcoding Catalogue, a basis for terminology translation shall be provided in line with the functional requirements of the Patient Summary and ePrescription services as defined by Work Packages 3.1 and 3.2.
The ultimate goal is the communication of information that can be processed, while keeping unchanged the structure and contents of the original documents or datasets in each country. This will be achieved by building a pivot document or a model of a dataset based on commonly adopted definitions, content, vocabulary and structures. The content of Patient Summary and ePrescription services, or the data elements, will be thematically grouped into value sets. Once the appropriate value sets are chosen based on the existing Use Cases, they are mapped onto existing code systems.
Although complete code systems for medical conditions, procedures, pharmaceuticals etc. are readily available, it would not be possible to use them in their entirety within the epSOS context. The ICD-10 system (“International Statistical Classification of Diseases and Related Health Problems”, defined by the WHO) alone contains about 155,000 different terms.
Various code systems cover the spectrum of the epSOS value sets as defined by the Use Cases, such as the ICD-10, ATC, ICD-9 and SNOMED CT. However, a selection of the most significant terms has to be made in order to achieve a reasonably manageable content.
The value sets mentioned above provide the basis for the Master Value Set Catalogue (MVS), which will be later turned into the Master Translation/ Transcoding Catalogue. It is also a task of WP 3.5 to define the standard interface to the Master Translation/Transcoding Catalogue: the Terminology Access Services Interface will allow 'on-the-fly' complete and accurate correspondence between the terminology used in the original document and its interoperable counterpart, as well as the target language.
In summary, semantic interoperability needs common elements such as:
- a common data structure of the documents to be exchanged (pivot documents)
- a commonly understood medical terminology based on value sets extracted out of officially existing code systems used in these documents, namely the epSOS Master Value Sets Catalogue. The content of the MVS serves as a basis for translating into each Member State language and cross-reference between different code systems, resulting in the epSOS Master Translation/Transcoding Catalogue
- a way of accessing and maintaining the content present in the Master Translation/Transcoding Catalogue that is transparent to the user: the Terminology Access Services Interface.


