Design of Modern Mobile Devices based on Medical Information Interchange Standards Med e Tel, 2015 Luxembourg

Transcription

1 D. Tcharaktchiev University Hospital of Endocrinology, Sofia, Bulgaria I. E. Ivanov, V. Gueorguiev Technical University Sofia, Bulgaria D. V. Georgieva 4New Bulgarian University, Bulgaria Design of Modern Mobile Devices based on Medical Information Interchange Standards Med e Tel, 2015 Luxembourg

2 Introduction The increasing use of mobile and individual healthcare devices is one of the major tendencies in out of hospital care. Many vendors provide extensive sets of those devices. Most of them cannot work together The way to solve this problem is to follow available standards and to maintain new devices to be compatible with them.

3 Introduction Common use and exchange of information between different actors in the healthcare process, in particular in clinical diagnostics process, is only possible if all partners adopt a common format, content, structure and meaning of exchanged messages.

4 Health data exchange Communication standards in health data exchange Infrastructure level corresponds to layers 1 6 of the OSI model Application level corresponds to layer 7 of the OSI model Syntax layer Semantic layer Context (pragmatic) layer

5 Health data exchange Standards Syntax layer Generic standards ASN.1 ; EDIFACT ; XML ; Health standards HL7; DICOM; IEEE 1073; WADO; DICOM SR. Semantic layer LOINC; GALEN; GRAIL; SNOMED CT. Pragmatic layer EHCRA; TS 18308; ISO/TR 20514; CEN EN

6 Archetypes as conceptual structures The GEHR (Good European Health Record) initiative started at the beginning of the 90 s The most noteworthy concept of this initiative is a knowledge based model, also known as the archetype modelling technique Methodology to define EHR structure First level the Reference Object Model (ROM) Second level constraining rules and mechanisms definition (archetypes) The archetypes role they have to specify the common data structures, which have been created in the first level

7 Archetypes as conceptual The Archetype Definition Language (ADL) Purpose to describe the descriptive data, constraints and ontological definitions of the archetype The descriptive data contains the ID, clinical concepts descriptor, metadata (ver., author, etc.) The constraints structures The ontological definitions contain the defined vocabulary

8 Archetypes as conceptual structures The Clinical Investigator Record Ontology

9 Design of a software for mobile Steps to design an application for mobile device conforming to the Archetype concept: Definition of minimum clinical data set Data standardization Communication design device

10 Design of a software for mobile device An example blood pressure monitor Minimal data set definition: Blood pressure (BP) systolic BP diastolic BP mean arterial BP pulse BP

11 Design of a software for mobile device An example blood pressure monitor Minimal data set definition (cont.): State/ Position Standing Sitting Reclining Lying Lying with the tilt on the left Other cuff size, location of measurement, method, mean arterial pressure formula, diastolic endpoint, etc.

12 Design of a software for mobile device Map View of the Blood Pressure measurement archetype

13 Implementation lessons learned The software design has to be very precise and to follow the archetype design without variants and adaptations. The communication increases because more data are transferred. Data composition in the mobile device and its parsing in the HIS are simple. Every mobile device conforming the presented archetype can exchange data to the experimental HIS. The protocol can be unified also.

14 Conclusion Today the problem is to achieve a common understanding of the exchanged content between systems. The proposed new type of thinking in terms of archetypes and conceptual structures solves many problems in this area and reduces standards contradictions.

15 Thank you for your attention!