Abstract image of a woman sitting on books and studying on a laptop

Detailed Clinical Models and their relation with Electronic Health Records

Download as PPTX, PDF
Y
yampeku

This document discusses the importance of semantic interoperability in electronic health records (EHRs) and proposes methodologies using archetypes to improve this interoperability. It highlights the challenges posed by disparate systems and the need for standardized clinical information models. The research also details advanced tools and methods for developing, editing, and transforming clinical data into archetype-based formats for better integration and understanding across various EHR systems.

Healthcare
1 of 73
Downloaded 52 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás PRESENTED BY: DIEGO BOSCÁ TOMÁS SUPERVISED BY: PhD. MONTSERRAT ROBLES VIEJO and PhD. ALBERTO MALDONADO SEGURA DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONTENTS • Introduction and Objectives • Outline • Research work I. Archetype representation of non-dual model architectures II. Archetype-based mapping between clinical information models III. Automatic generation of implementation guides from clinical information models • Conclusions, Contributions, and Future Work • Projects, Publications, and Research Stays 2
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 3 INTRODUCTION AND GOALS
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás INTRODUCTION • Accessing the full Electronic Health Record (EHR) of a patient is still difficult as this information tends to be distributed into different systems with different semantics, and needs semantic interoperability for their meaningful communication • Semantic interoperability is still far from being achieved in the clinical domain, mostly due to the complexity, variability, and evolving knowledge 4
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás INTRODUCTION • One of the prerequisites to achieve semantic interoperability is the standardization of both the data and clinical information models present in the information system (SemanticHealth) • Standards need to be brought to live. There is a lack of adequate methodologies and tools for they widespread use 5
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás INTRODUCTION HYPOTHESIS Archetypes can be applied to describe the structure, content, and meaning of existing EHRs as well as to facilitate the development and deployment of new EHR systems that require semantic interoperability 6
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE GENERAL OBJECTIVE Provide methodologies and advanced tools based on archetypes to ease the achievement of higher levels of EHR semantic interoperability 7
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE SPECIFIC OBJECTIVES To provide means of applying dual model methodology to non-dual information models To provide tools and methodologies for the transformation of existing data into archetype data instances To generate reference materials automatically from archetypes to achieve suitable views for each type of user 8 O1. O2. O3.
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OUTLINE R III R II 9
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE REPRESENTATION OF NON-DUAL MODEL ARCHITECTURES 10
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MOTIVATION • Current EHR systems (typically based on a single model EHR architecture) tend to have clinical knowledge mixed into the information model • Dual model methodology allows the formal description of clinical models of a given EHR information model • Even single model EHR architectures may be suitable to be used as a reference model for archetype definition • Dual model methodology provides a set of advantages, such as formalization, reuse, terminology bindings, or multilinguality 11
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE Create a set of methodologies and tools to define archetypes for non-dual information models, ease their definition, and support their advanced use 12 O1.
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás REFERENCE MODEL ARCHETYPES • Only a subset of the classes contained in reference models define logical building blocks of EHRs and can be used to define archetypes (business class) • The representation of a business class as an archetype is what we call a Reference Model Archetype (RMA) † • Any other archetype must be a specialization of one of them – Archetype editing becomes a process of subtyping by constraints • This approach opens the door to support multiple reference models 13 † Maldonado et al, LinkEHR-Ed: a multi-reference model archetype editor based on formal semantics. IJMI 2009
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EXAMPLE: ISO13606 BUSINESS CLASSES 14
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás BUILDING REFERENCE MODEL ARCHETYPES • In order to define archetypes in a given reference model, we must build the set of RMAs first – We achieve this by analyzing the formal schema definitions (typically XML Schema) – This is not always possible, as the schema may not be public, is defined in an unsupported format, or is underspecified (e.g. XML Schema any type) • Two alternatives: Creating them from other metamodel representations or defining them manually 15
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CREATING RMA FROM METAMODELS • For this process, a suitable metamodel that faithfully represents a given standard is chosen • The metamodel, e.g. ecore definitions or Basic Meta Model (BMM) definitions, is analyzed 16
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CREATING RMA FROM METAMODELS Base of FHIR Ecore model Transformed into FHIR archetypes / extended resources FHIR Reference Model Archetype Defined in FHIR Resource Base of openEHR BMM Transformed into openEHR archetypes Defined in openEHR RM openEHR RMAs • This approach was used to support archetype creation for FHIR DSTU and BMM-based models such as openEHR and CIMI 17
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CREATING RMA MANUALLY • As RMAs are archetypes it is feasible to build them by defining the object, attribute, and primitive constraints • An Archetype Object Model (AOM) editor was created • Japanese standard MedXML MML RMAs were built using this approach 18
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ADVANCED ARCHETYPE EDITING • Target users of archetype editors come from the clinical domain. Archetype editors must hide the complexity of the underlying reference model – The easiest solutions is to hard-code the reference model into the editors but… – It is harder to cope with multiple reference models and their evolution. • In order to support multiple reference models and at the same time keeping the editing process simple for clinical users, different approaches and methodologies have been investigated, namely: – Use of specific editors – Semantic patterns – Archetype creation from data instances – Syntactic model transformation between standards – Mapping to other standards 19
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás USE OF SPECIFIC EDITORS • Specific editors for each reference model can be defined to hide their complexity when creating archetypes. • These editors are based on a documentation file and can be dynamically included in the tool. • Specific editors for ISO13606, openEHR, and HL7 CDA have been defined. 20
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás USE OF SPECIFIC EDITORS 21
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SEMANTIC PATTERNS • Archetype reuse is not limited to archetype slots and internal references • Semantic patterns are reusable solutions to recurring modeling problems – They combine structural, terminological, and ontological representations • We implemented the semantic patterns as archetype fragments with known semantics • These semantic patterns are useful for creating equivalences between standards – E.g. How an openEHR Observation is represented in ISO13606 or HL7 CDA reference model • Examples of semantic patterns are – General use structures such as table, tree, or panels – Generic clinical models such as exam of XYZ – Representation of archetypable classes of different reference models such as observation, event, or history in ISO13606 • In addition to the support for using semantic patterns in archetype edition, a semantic pattern manager was implemented to allow their versioning and management 22
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE CREATION FROM DATA INSTANCES • One of the biggest challenges when applying archetypes to a non-dual reference model is that defining a minimum set of archetypes is required in order to take advantage of archetype-based methodologies • As the systems are already deployed, it is feasible to obtain sample data instances • A methodology for the creation of archetypes from data instances was developed • This process considers each data instance as a “constant archetype” (an archetype with every constraint fixed to a constant) and reduces the problem to merging two archetypes into a single one 23
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE CREATION FROM DATA INSTANCES • The automatic merging process traverses each instance and loosens the resulting archetype constraints according to the new values 24 Instance 1 Instance 2 Resulting archetype |102..115| |60..70|
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SYNTATIC MODEL TRANSFORMATION BETWEEN STANDARDS • Transformation of clinical models between different standards is a difficult problem – Ontology-based model and data transformations is one of the most promising approaches • However, most of the time equivalences are defined in the standards themselves or are clear enough so complex ontology reasoning is not needed • These equivalences can be declared as rules to be executed • Three different kinds of rules were detected depending on the trigger: – Structure-based rules: triggered by the structure and values – Terminology-based rules: triggered by the terminological binding – Generic rules: transformation to generic classes • Defined rules transform the archetypes and create the mapping equivalences for the automatic data transformation 25
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SYNTATIC MODEL TRANSFORMATION BETWEEN STANDARDS • This methodology is demonstrated by a proposed transformation between openEHR and ISO13606 (and vice versa). Rules were implemented in drools – All archetypes from openEHR CKM (415) were translated to ISO13606 and the Spanish Ministry of Health archetypes (23) were translated to openEHR and tested as valid for their respective reference model Target class in openEHR Source term binding contained in SNOMED CT subset Observation << 363787002 | Observable entity (observable entity) | OR << 284365007 | Examination of body site (procedure) | OR << 122869004 | Measurement procedure (procedure) | Evaluation << 243814003 | Interpretation of findings (observable entity) | Instruction << 243120004 | Regimes and therapies (regime/therapy) | OR << 400999005 | Procedure requested (situation) | Action << 129264002 | Action (qualifier value) | OR << 416118004 | Administration (procedure) | OR << 443938003 | Procedure carried out on subject (situation) | OR << 71388002 | Procedure (procedure) | Admin_entry << 14734007 | Administrative procedure (procedure) | OR << 304784009 | Administrative form (record artifact) | Event << 272379006 | Event (event) | 26
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE-BASED MAPPING BETWEEN CLINICAL INFORMATION MODELS 27
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MOTIVATION • Patient health data is distributed among different healthcare facilities, which makes crucial their integration and communication • Health data communication must be done in a meaningful way, avoiding all possibility of misunderstanding or misinterpretation • This crucially depends on the standardization of the EHR architecture used to represent the data • Standardizing existing data is one of the main problems in adopting EHR standards 28
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE To define and implement a set of methodologies and tools for the normalization of legacy data and the transformation between EHR standards 29 O2.
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás PROBLEM • The problem of data transformation is a difficult one, as deals with differences and mismatches between heterogeneous data formats and models • This is even harder in healthcare domain, due to the intrinsic complexity of EHR data • Standard EHR architectures and archetypes are defined without any consideration to the internal database design • The definition of these transformation programs is a complex process, usually involving the creation of custom non-reusable software 30
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING APPROACH • Existing data transformation formalisms have been studied and adapted to cope with the special requirements of the archetypes • We use a “specify-generate” approach – High-level declarative assertions are used to specify relationships between the source and target schemas – These assertions are compiled automatically into executable scripts 31
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FORMAL DEFINITION • Source schemas can be either XML Schema or an archetype • Target schema is an archetype • We use the Nested Relational (NR) model for the specification of both source and target schemas, as archetypes impose hierarchical structures • NR model generalizes relational model (tuples and relations) by modeling them as records and sets of records respectively • This model allows the representation of hierarchical structures as the archetype 32
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FORMAL DEFINITION • The set of atomic data types of our model are the ones supported by archetypes: – string, integer, real, date, time, date and time, duration, and boolean • Non-atomic types are – Record types of the form Rcd 𝑎1 𝑒1:𝑓1 : 𝜏1, … , 𝑎 𝑛 𝑒 𝑛:𝑓𝑛 : 𝜏 𝑛 – Set types of the form SetOf 𝜏1 𝑙1:𝑢1 … 𝜏 𝑛 𝑙 𝑛:𝑢 𝑛 𝑙 𝜏:𝑢 𝜏 – Choice types of the form ChoiceOf 𝑎1: 𝜏1 … 𝑎 𝑛: 𝜏 𝑛 • where: – 𝜏 represents either an atomic, set, or record type – 𝑛 ≥ 1, 𝑒𝑖 ∈ 0,1 , 𝑒𝑓 ∈ 0,1 and 𝑒𝑖 ≤ 𝑒𝑓 – li is a natural number, ui is a natural number or ∞ and li ≤ ui – 𝑖=1 𝑛 𝑙𝑖 ≤ 𝑢 𝜏 and 𝑖=1 𝑛 𝑢𝑖 ≤ 𝑙 𝜏 33
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FORMAL DEFINITION 34
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION • Only constrained entities (classes and attributes) of the reference model appear in the archetypes – The underlying reference model constraints are implicit – This is also the case of the parent archetype in specialized archetypes • In order to generate correct data instances, archetypes must be merged with the parents archetypes and the underlying reference model 35
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION 36
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION • Mapping language is based on tgds † (tuple-generating-dependencies) • To describe how to compute a value for an atomic attribute of the target schema (archetype) a list of filter/function pairs can be defined 37 $gender={ If (/patient/gender=’M’ OR /patient/gender=’m’) then 0 Else if (/patient/gender=’W’ OR /patient/gender=’w’) then 1 Else if (/patient/gender=0 OR /patient/gender=1) then /patient/gender Else 9 } † Fagin et al, Data exchange: semantics and query answering. TCS 2005
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás • Value correspondences lack expressive power to completely describe grouping semantics • Default grouping semantics is based on the Partition Normal Form (PNF) – In PNF, two distinct records that coincide in all the atomic (non-multivaluated) attributes cannot exist • We use Skolem functions † to achieve PNF GROUPING 38 † Hazewinkel et al, Encyclopædia of Mathematics
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás GROUPING • Grouping semantics can be customized by modifying the Skolem functions or by defining Object Builders • Skolem parameters can be removed from the Skolem functions • Object builders control the generation of target instances taking into account the data in the source – Object Builders represent iterators on the source nodes they are connected to – In each iteration, a new element is constructed, of the kind of the target node reached by the builder 39
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION EXAMPLE 40 Object builder Attribute mapping Object builder nesting $prof/cargo=“cirujano” $prof $ingr $hosp
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás XQUERY GENERATION • Archetype constants are assumed to be transformation functions whose filter has ‘true’ value and the function is fixed to the constant value • Constraints on primitive types (valid ranges, lists of values) are enforced in the transformation script • When the mapping correspondences have been defined, they are traversed in order to generate the transformation script Archetype constraint Value correspondence XQuery extract number matches {|0..10|} If true then /data/measurements/value (specified by user) For $val in /data/measurements/value Where $val≥0 and $val≤10 Return <number> {data($val)}</number> 41 Archetype constraint Value correspondence XQuery extract number matches {1} If true then 1 (automatically generated) Return <number> 1 </number>
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás XQUERY GENERATION • More than one mapping can be applied to a single attribute. In this case, each one of these mappings produces a different transformation program • For each object in the archetype a nested XQuery FLWOR is produced 42
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás XQUERY GENERATION 43
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING SUMMARY Archetype Reference Model XQuery script Source XML instance Output XML instance Mapping source (XML Schema or archetype) Mapping Comprehensive ArchetypeMerge Defines Defines Autogenerates Instance of Generates Instance of Instance of 44
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás TECHNICAL EVALUATION • For the technical validation of the mapping capabilities, the STBenchmark was used – This benchmark describes 17 mapping scenarios that should be supported by mapping systems • Each scenario contains a source and target schema expressed as an XML Schema, an instance of the source schema and a visual and textual description of the scenario – In our case, target schema is modeled as an archetype 45
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás TECHNICAL EVALUATION • From the 17 scenarios, 15 could be successfully tested as the expected target instance could be generated • Two scenarios could not be tested – One scenario could not be tested due to archetypes not supporting the definition foreign keys – One scenario could not be tested due to limitations in the expressive power of our mapping language 46
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EVALUATION IN REAL SETTINGS: MEDICINES RECONCILIATION PROJECT • The objective was to obtain and evaluate a complete medication list of patients regardless where they came from • Archetypes are based on epSOS specifications • Hospital EHR system was upgraded to include the patient summary • The project was awarded with the Spanish Ministry of Health quality award LinkEHR Platform DATA NORMALIZATION DATA INTEGRATION NOMENCLATOR DIGITALIS INDEPENDENT WEB VIEWER HOSPITAL EHR (SELENE) Web Service Primary care OMI-AP Hospital de Fuenlabrada FARMATOOLS SELENE 47
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EVALUATION IN REAL SETTINGS: PATIENT ELIGIBILITY • Use of archetypes and mappings in different abstraction levels to determine if a patient is eligible for a cancer clinical trial • Patient is not eligible if it has severe comorbidity, which is derived from a series of cascade mappings 48
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EVALUATION IN REAL SETTINGS PATIENT ELIGIBILITY • Presence/absence of metastatic tumor (source EHR) • Presence/absence of metastatic solid tumor (source archetype) Condition Mapping @count(summary/problems/problem, @in(summary/problems/problem/code, @descendents(“128462008”))>0 TRUE TRUE FALSE Condition Mapping (Evaluation_problem_DS_metastatic_tumor_v1/structure/present = TRUE) AND (Evaluation_problem_DS_solid_tumor_v1/structure/present = TRUE) TRUE TRUE FALSE 49
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPES FOR THE GENERATION, VALIDATION, AND USE OF EHR SYSTEMS 50
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MOTIVATION • Archetypes ease the communication between clinicians and IT staff • Those clinicians and IT staff who are not experts in dual model architectures need to understand the archetypes – Clinicians are able to provide valuable inputs for archetype validation and evolution – IT staff can use the archetypes as formal specifications of the system • Clinicians and IT staff make use of different sets of artifacts to understand the archetypes and bring them to life in their systems 51
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE To enable the automatic generation of artifacts from clinical archetypes for the validation of current systems and the creation of new ones from both clinical and technical perspectives 52 O3.
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás GENERATION OF ARTIFACTS • Archetypes can be used as guidance to automatically generate a wide range of artifacts –Validation rules –Sample data instances –Mindmaps and Sample forms –Implementation guides 53
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás VALIDATION: NATURAL RULE LANGUAGE • Natural Rule Language (NRL) provides a formal and executable way of defining English-like rules • Archetype constraints are interpreted and translated to NRL • These rules can be translated to OCL or Schematron 54
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás VALIDATION: HL7 STYLE RULES • In the same way, rules from archetypes can be translated into HL7 conformance statements • These statements can be generated in the desired language 55
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás VALIDATION: SCHEMATRON RULES • Different kinds of Schematron rules are derived for each kind of archetype constraint • The definition of two different Schematron phases allows to validate both the explicit and the implicit archetype constraints (only archetype or archetype + reference model) <!-- Rules for archetype path /items[Blood pressure measurement]/parts[Systolic]/value[at0005] --> <rule context="ENTRY/items/parts[archetype_id='at0001']/value"> <!-- Existence for attribute 'units' --> <report test="count(units)=0">Attribute 'units' is required and does not appear in data</report> <!-- Occurrences for the alternatives of attribute 'units' --> <assert test="(count(units)=1)">The attribute 'units' has more than one alternative or empty alternatives</assert> <!-- Existence for attribute 'value' --> <report test="count(value)=0">Attribute 'value' is required and does not appear in data</report> <!-- 'value' constraint is not valid--> <assert test="value&gt;=0.0 and value&lt;1000.0">Constraint for 'value' does not follow the archetype: 'value' <value-of select="value" /> is not in [0.0,1000.0[</assert> </rule> 56
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SAMPLE DATA INSTANCES • Sample data instances allow to perform stress tests on systems • Data instances are created by using the mapping mechanism explained before – Constant values are assigned to each archetype constraint – These constant values are used to generate a transformation script to produce the sample data instance – Generated instances follow the archetype and the reference model, but do not describe real clinical cases 57
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ADDITIONAL ARTIFACTS • A mindmap representation from the archetype is created in order to give an overview of the clinical model • Archetype constraints can also be interpreted as fields of an sample html form • Archetype constraints bound to terminologies can be displayed in summary value set tables 58
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás IMPLEMENTATION GUIDE GENERATION • Presented artifacts can be combined according to user’s needs to provide helpful implementation guides • Each object in the archetype generates a set of NRL, HL7, and Schematron rules, as well as a sample data instance for that object • A general mindmap, archetype metadata, value set tables, sample form, reference model documentation, and a table of contents can also be generated 59
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 60 CONCLUSIONS, CONTRIBUTIONS, AND FUTURE WORK
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONCLUSIONS • The specifications of eHealth interoperability standards must be brought to life by system designers and implementers • The challenge is not the lack of standards, but its implementation at a reasonable cost • Presented methodologies and tools ease the joint use of the three layers of artefacts (Clinical Models, Reference Models, and Clinical Terminologies) needed to achieve high levels of semantic interoperability 61
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONCLUSIONS • The advantages of a joint use of archetypes with non- dual model standards outweigh the disadvantages – Using archetypes for currently used reference models such as HL7 CDA, HL7 FHIR, or MedXML MML will help to the rapid adoption of both the original standard and the dual model approach • The presented set of integrated innovative tools help current systems to achieve semantic interoperability by normalizing data based on clear semantically-rich clinical models • Proposed methodology promotes the involvement of clinical staff in the modeling and validation process • All presented developments have been included in LinkEHR platform 62
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONTRIBUTIONS • Design and implementation of a set of methodologies and tools to support the definition of archetypes from multiple reference models • Design and implementation of a new methodology for the transformation of legacy data into archetype-based data • Reuse of this methodology for the data transformation between archetype-based standards • Design and implementation of a set of methodologies for the automatic generation of implementation guides and reference materials from archetypes 63
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FUTURE WORK • From data perspective, variability in original sources continuously provides new challenges – Support to other source schemas such as RDF or OWL – Automatic schema matching techniques • Based both in clinical terminologies and tree-matching algorithms • Use of clinical vocabularies and ontologies provides challenges on their own. The integration of ontologies in queries and reasoning will benefit both patient and public health – Mapping specification must be improved to support this advanced use • Automatic artifact creation can benefit from terminology bindings • Having available big quantities of normalized archetype-based data provides the opportunity to generate semantically rich research and public health repositories 64
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 65 PROJECTS, PUBLICATIONS, AND RESEARCH STAYS
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás RESEARCH PROJECTS • The results of this PhD Thesis have contributed directly to the results of the following research projects: – ResearchEHR: Platform for the acquisition and sharing of information and knowledge for network-based clinical research communities (TSI2007-66575-C02-01) – Trial-Me: Intelligent tools for linking EHR to clinical trial systems (TIN2010-21388-C02-01) – Clin-IK-Links: Clinical information and knowledge models for linking EHR and Clinical Decision Support Systems (TIN2014-53749-C2-1-R) 66
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás JOURNAL CONTRIBUTIONS AND BOOK CHAPTERS • J. A. Maldonado, D. Moner, D. Boscá, J. T. Fernández-Breis, C. Angulo, and M. Robles, “LinkEHR-Ed: A multi-reference model archetype editor based on formal semantics,” International journal of medical informatics, vol. 78, no. 8, pp. 559–570, 2009 • M. Marcos, J. A. Maldonado, B. Martínez-Salvador, D. Boscá, and M. Robles, “Interoperability of clinical decision-support systems and electronic health records using archetypes: a case study in clinical trial eligibility,” Journal of biomedical informatics, vol. 46, no. 4, pp. 676–689, 2013 • J. A. Maldonado, C. M. Costa, D. Moner, M. Menárguez-Tortosa, D. Boscá, J. A. M. Giménez, J. T. Fernández-Breis, and M. Robles, “Using the ResearchEHR platform to facilitate the practical application of the EHR standards,” Journal of biomedical informatics, vol. 45, no. 4, pp. 746–762, 2012 • D. Boscá, J. A. Maldonado, D. Moner, and M. Robles, “Automatic generation of computable implementation guides from clinical information models,” Journal of biomedical informatics, vol. 55, pp. 143–152, Jun. 2015 67 Publications in Q1 Journals RI RII RIII
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás JOURNAL CONTRIBUTIONS AND BOOK CHAPTERS • S. Kobayashi, D. Boscá, N. Kume, and H. Yoshihara, “Reforming MML (Medical Markup Language) Standard with Archetype Technology,” Indian Association for Medical Informatics, vol. 91, p. 57, 2014. • J. A. Maldonado, D. Boscá, D. Moner, and M. Robles, “LinkEHR: A Platform for the Normalization of Legacy Clinical Data Based on Archetypes,” Interoperability in Healthcare Information Systems: Standards, Management, and Technology: Standards, Management, and Technology, p. 45, 2013. • M. Marcos, J. A. Maldonado, B. Martínez-Salvador, D. Moner, D. Boscá, and M. Robles, “An archetype-based solution for the interoperability of computerised guidelines and electronic health records,” in Artificial Intelligence in Medicine, Springer Berlin Heidelberg, 2011, pp. 276–285. 68 RI RII
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONGRESS PAPERS • CONGRESS PAPERS RELATED WITH THE THESIS – D. Boscá, D. Moner, J. A. Maldonado, and M. Robles, “Combining Archetypes with Fast Health Interoperability Resources in Future-proof Health Information Systems.,” Studies in health technology and informatics, vol. 210, pp. 180–184, 2014. – D. Boscá, L. Marco, D. Moner, J. A. Maldonado, L. Insa, and M. Robles, “Detailed Clinical Models Governance System in a Regional EHR Project,” in XIII Mediterranean Conference on Medical and Biological Engineering and Computing 2013, Springer, 2014, pp. 1266–1269. – D. Moner, J. A. Maldonado, D. Boscá, A. Mañas, and M. Robles, “Development of a Visual Editor for the Definition of HL7 CDA Archetypes,” in XIII Mediterranean Conference on Medical and Biological Engineering and Computing 2013, Springer, 2014, pp. 1258–1261. 69
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONGRESS PAPERS • CONGRESS PAPERS RELATED WITH THE THESIS – D. Boscá, L. Marco, V. Burriel, T. Jaijo, J. M. Millán, A. M. Levin, O. Pastor, M. Robles, and J. A. Maldonado, “Genetic testing information standardization in HL7 CDA and ISO13606.,” in MedInfo, 2013, pp. 338–342. – C. Martínez-Costa, D. Boscá, M. C. Legaz-García, C. Tao, B. J. Fernández, S. Schulz, and C. G. Chute, “Isosemantic rendering of clinical information using formal ontologies and RDF.,” Studies in health technology and informatics, vol. 192, pp. 1085–1085, 2012. – D. Boscá, J. A. Maldonado, D. Moner, and M. Robles, “Detailed clinical models to facilitate interstandard interoperability of data types,” 23rd International Conference of the European Federation for Medical Informatics. Oslo, Norway: European Federation for Medical Informatics, 2011 70
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONGRESS PAPERS • CONGRESS PAPERS RELATED WITH THE THESIS – J. Maldonado, D. Moner, D. Boscá, C. Angulo, L. Marco, E. Reig, M. Robles, and others, “Concept-based exchange of healthcare information: The LinkEHR approach,” in Healthcare Informatics, Imaging and Systems Biology (HISB), 2011 First IEEE International Conference on, 2011, pp. 150–157. – D. Moner, J. A. Maldonado, D. Boscá, C. Angulo, M. Robles, D. Pérez, and P. Serrano, “CEN EN13606 normalisation framework implementation experiences,” Seamless Care, Safe Care: The Challenges of Interoperability and Patient Safety in Health Care: Proceedings of the EFMI Special Topic Conference, June 2-4, 2010, Reykjavik, Iceland, vol. 155, p. 136, 2010. – M. Robles, J. T. Fernández-Breis, J. A. Maldonado, D. Moner, C. Martínez-Costa, D. Boscá, and M. Menárguez-Tortosa, “ResearchEHR: Use of semantic web technologies and archetypes for the description of EHRs,” Studies in health technology and informatics, vol. 155, p. 129, 2010 71
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás RESEARCH STAY • RESEARCH STAY – Main Subject: Detailed clinical model representation of MML Japanese standard – Place: Division of Medical Information Technology and Administration Planning, Kyoto University (Japan) – Length: 3 Months (2011) 72
26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 73

More Related Content

PPTX
Digital Accessibility - Section 508 Refresh: Now What?
Lisa Marchand
 
PDF
EHR- 2016 Eeshika Mitra
Eeshika Mitra
 
PDF
Netex Seminar LT2017 | Make your strategy lean and mean for learning in 2017 ...
Netex Learning
 
PPTX
Harbinger Tech Session in cloud Expo - New Possibilities in Cloud Based Healt...
Harbinger Systems - HRTech Builder of Choice
 
PDF
Semic 2016 highlight report
Semic.eu
 
PPTX
Clear Touch Connect
Apollo Hospitals Group and ATNF
 
PPT
The Circuit EHR Presentation
The Circuit
 
PPTX
Section 508 and 504 Video Captioning Requirements, Workflows, and Best Practices
3Play Media
 
Digital Accessibility - Section 508 Refresh: Now What?
Lisa Marchand
 
EHR- 2016 Eeshika Mitra
Eeshika Mitra
 
Netex Seminar LT2017 | Make your strategy lean and mean for learning in 2017 ...
Netex Learning
 
Harbinger Tech Session in cloud Expo - New Possibilities in Cloud Based Healt...
Harbinger Systems - HRTech Builder of Choice
 
Semic 2016 highlight report
Semic.eu
 
Clear Touch Connect
Apollo Hospitals Group and ATNF
 
The Circuit EHR Presentation
The Circuit
 
Section 508 and 504 Video Captioning Requirements, Workflows, and Best Practices
3Play Media
 

Viewers also liked (15)

PPT
HealthTrust: A PhD Dissertation on the Retrieval of Trustworthy Health Social...
Luis Fernandez Luque
 
PPTX
The Electronic Health Record: Using It Effectively & with Meaning
BU School of Medicine
 
PPTX
Healthcare Interoperability: New Tactics and Technology
Health Catalyst
 
PPTX
2. 2016 top 10 md vendors
Tim Histalk
 
PPTX
Hands-on Machine Learning Using Healthcare
Health Catalyst
 
PPTX
When Healthcare Data Analysts Fulfill the Data Detective Role
Health Catalyst
 
PPTX
National Research Results: How & Why Do Students Use Closed Captioning?
3Play Media
 
PPTX
Against the Odds: How this Small Community Hospital Used Six Strategies to Su...
Health Catalyst
 
PPTX
Healthcare Factoids to Power Your Brain 2015
Health Catalyst
 
PPTX
Governance in Healthcare: Leadership for Successful Improvement
Health Catalyst
 
PPTX
MACRA and the New Quality Payment Program
Health Catalyst
 
PDF
5 Healthcare IT Trends to Watch in 2017
Patrick Hurley
 
PPTX
Is Value-Based Healthcare Here to Stay? Looking for Answers in New Policies
Health Catalyst
 
PPTX
Electronic Health Records Implementation
Nancy McClanahan, MBA, DHA
 
PPTX
The MD Anderson / IBM Watson Announcement: What does it mean for machine lear...
Health Catalyst
 
HealthTrust: A PhD Dissertation on the Retrieval of Trustworthy Health Social...
Luis Fernandez Luque
 
The Electronic Health Record: Using It Effectively & with Meaning
BU School of Medicine
 
Healthcare Interoperability: New Tactics and Technology
Health Catalyst
 
2. 2016 top 10 md vendors
Tim Histalk
 
Hands-on Machine Learning Using Healthcare
Health Catalyst
 
When Healthcare Data Analysts Fulfill the Data Detective Role
Health Catalyst
 
National Research Results: How & Why Do Students Use Closed Captioning?
3Play Media
 
Against the Odds: How this Small Community Hospital Used Six Strategies to Su...
Health Catalyst
 
Healthcare Factoids to Power Your Brain 2015
Health Catalyst
 
Governance in Healthcare: Leadership for Successful Improvement
Health Catalyst
 
MACRA and the New Quality Payment Program
Health Catalyst
 
5 Healthcare IT Trends to Watch in 2017
Patrick Hurley
 
Is Value-Based Healthcare Here to Stay? Looking for Answers in New Policies
Health Catalyst
 
Electronic Health Records Implementation
Nancy McClanahan, MBA, DHA
 
The MD Anderson / IBM Watson Announcement: What does it mean for machine lear...
Health Catalyst
 
Ad

Similar to Detailed Clinical Models and their relation with Electronic Health Records (20)

PPTX
Genetic Testing Information Standardization in HL7 CDA and ISO13606 (Medinf...
yampeku
 
PDF
1st eStandards conference: next steps for standardization in large scale eHea...
chronaki
 
PPTX
Healthcare 5.0
Mithileysh Sathiyanarayanan
 
PDF
Model Management in Systems Biology: Challenges – Approaches – Solutions
Martin Scharm
 
PPT
OAIS as a reference model for repositories
Julie Allinson
 
PPTX
Towards Open Architectures and Interoperability for Learning Analytics
Tore Hoel
 
PDF
Model management for systems biology projects
University Medicine Greifswald
 
PDF
Standards for clinical research data - steps to an information model (CRIM).
Wolfgang Kuchinke
 
PPTX
Cinzia Battistella; Modeling a business ecosystem: a network analysis approach
CBOD ANR project U-PSUD
 
PPTX
Cooperative infraestructure for sustaining non-profit Open Access
REDALYC
 
PPT
Me2011 Presentation by Loniewski
Method Engineering 2011 - IFIP WG.8.1 Working Conference
 
PDF
Managing Big Data - Berlin, July 9-10, 201.
Susanna-Assunta Sansone
 
PDF
Archetype Modeling Methodology
David Moner Cano
 
PDF
Best Practice Reference Architecture for Data Curation
OSTHUS
 
PPTX
Fire and Ice - SNOMED is bound to model - Koray Atalag
HL7 New Zealand
 
PPTX
SNOMED Bound to (Information) Model | Putting terminology to work
Koray Atalag
 
PPTX
Data_analytics_life_cycle in big data.pptx
calvinctttafirei
 
PDF
The state of the art in integrating machine learning into visual analytics
Cagatay Turkay
 
PPTX
SKOS as the focal point of linked data strategies
Semantic Web Company
 
PDF
Handling quantitative data and preparing for sharing and reuse, including dat...
Arhiv družboslovnih podatkov
 
Genetic Testing Information Standardization in HL7 CDA and ISO13606 (Medinf...
yampeku
 
1st eStandards conference: next steps for standardization in large scale eHea...
chronaki
 
Healthcare 5.0
Mithileysh Sathiyanarayanan
 
Model Management in Systems Biology: Challenges – Approaches – Solutions
Martin Scharm
 
OAIS as a reference model for repositories
Julie Allinson
 
Towards Open Architectures and Interoperability for Learning Analytics
Tore Hoel
 
Model management for systems biology projects
University Medicine Greifswald
 
Standards for clinical research data - steps to an information model (CRIM).
Wolfgang Kuchinke
 
Cinzia Battistella; Modeling a business ecosystem: a network analysis approach
CBOD ANR project U-PSUD
 
Cooperative infraestructure for sustaining non-profit Open Access
REDALYC
 
Me2011 Presentation by Loniewski
Method Engineering 2011 - IFIP WG.8.1 Working Conference
 
Managing Big Data - Berlin, July 9-10, 201.
Susanna-Assunta Sansone
 
Archetype Modeling Methodology
David Moner Cano
 
Best Practice Reference Architecture for Data Curation
OSTHUS
 
Fire and Ice - SNOMED is bound to model - Koray Atalag
HL7 New Zealand
 
SNOMED Bound to (Information) Model | Putting terminology to work
Koray Atalag
 
Data_analytics_life_cycle in big data.pptx
calvinctttafirei
 
The state of the art in integrating machine learning into visual analytics
Cagatay Turkay
 
SKOS as the focal point of linked data strategies
Semantic Web Company
 
Handling quantitative data and preparing for sharing and reuse, including dat...
Arhiv družboslovnih podatkov
 
Ad

More from yampeku (6)

PPTX
OpenEHR day 2019 valencia biobanks
yampeku
 
PPT
Combining archetypes with FHIR in future-proof health information systems
yampeku
 
PPTX
openEHR in the world
yampeku
 
PPTX
Implementing dual model systems
yampeku
 
PPT
Plataforma para la Comunicación de Historia Clínica Electrónica Estandarizada...
yampeku
 
PPT
Generating Standardized Demographic Repositories
yampeku
 
OpenEHR day 2019 valencia biobanks
yampeku
 
Combining archetypes with FHIR in future-proof health information systems
yampeku
 
openEHR in the world
yampeku
 
Implementing dual model systems
yampeku
 
Plataforma para la Comunicación de Historia Clínica Electrónica Estandarizada...
yampeku
 
Generating Standardized Demographic Repositories
yampeku
 

Recently uploaded (20)

PPTX
dr vivek orho post op pain.pptxhhhhhhhhhhh
HeartMind1
 
PPTX
Non-Variceal-Upper-GI-Bleeding_-Comprehensive-Review_121037.pptx
saadkhalid88
 
PDF
CASE PRESENTATION1.pdf bipolar disorder in which both mania and depression h...
sheetal1011kumari
 
PPTX
Drugs used in treatment of Malaria. Antimalarial Drugs.pptx
MutegekiAdolf1
 
PPTX
Medical Legal issues in Psychiatry Final.pptx
Ahemigisha
 
PPT
toxicosis in pregnancy preeclampcia eclampcia.ppt
BehriyyeMustafayeva
 
PPTX
lower respiratory disorders chp 31.pptx
tracylynbrowne1
 
PPT
53afocus7fluidelectrolytesacid-basebalance-121205082904-phpapp01.ppt
Bbbbbbb19
 
PDF
Indonesian Healthtech Innovation_11Sep2019_Industry_Geraldine Seow_1.pdf
Moch Kurniawan
 
PPTX
MONOCHORIONIC TWIN PREGNANCY detailed.pptx
jigneshgamot1990
 
PPTX
Seizures in paediatrics as a big cause of morbidity.pptx
TugumeFrancis1
 
PPTX
Conflict Management: Defining conflict and understanding why it occurs is t...
AmandeepKaur793593
 
PPTX
Single Visit Endodontics.pptx root canal treatment in one visit
KarishmaThakur35
 
PPTX
VITAL PULP THERAPY in pediatric dentistry
sadaf566560
 
PPTX
Head Spine trauma assesment and managementATLS Final.pptx
premrajSingh6
 
PPTX
applied physics dental materials basic principles
reyyaarun
 
PPTX
4. Musculoskeletal X ray For health student
jehovajudy2001
 
PPT
FRACTURE CLASSIFICATION AND MANAGEMENT..
GanesanRamGanesan
 
PPTX
Brucellosis. treatment in Uganda. Group II.pptx
MutegekiAdolf1
 
PPTX
The Process of Infection by Windy Mesolas-Luzon.pptx
WindyLuzon1
 
dr vivek orho post op pain.pptxhhhhhhhhhhh
HeartMind1
 
Non-Variceal-Upper-GI-Bleeding_-Comprehensive-Review_121037.pptx
saadkhalid88
 
CASE PRESENTATION1.pdf bipolar disorder in which both mania and depression h...
sheetal1011kumari
 
Drugs used in treatment of Malaria. Antimalarial Drugs.pptx
MutegekiAdolf1
 
Medical Legal issues in Psychiatry Final.pptx
Ahemigisha
 
toxicosis in pregnancy preeclampcia eclampcia.ppt
BehriyyeMustafayeva
 
lower respiratory disorders chp 31.pptx
tracylynbrowne1
 
53afocus7fluidelectrolytesacid-basebalance-121205082904-phpapp01.ppt
Bbbbbbb19
 
Indonesian Healthtech Innovation_11Sep2019_Industry_Geraldine Seow_1.pdf
Moch Kurniawan
 
MONOCHORIONIC TWIN PREGNANCY detailed.pptx
jigneshgamot1990
 
Seizures in paediatrics as a big cause of morbidity.pptx
TugumeFrancis1
 
Conflict Management: Defining conflict and understanding why it occurs is t...
AmandeepKaur793593
 
Single Visit Endodontics.pptx root canal treatment in one visit
KarishmaThakur35
 
VITAL PULP THERAPY in pediatric dentistry
sadaf566560
 
Head Spine trauma assesment and managementATLS Final.pptx
premrajSingh6
 
applied physics dental materials basic principles
reyyaarun
 
4. Musculoskeletal X ray For health student
jehovajudy2001
 
FRACTURE CLASSIFICATION AND MANAGEMENT..
GanesanRamGanesan
 
Brucellosis. treatment in Uganda. Group II.pptx
MutegekiAdolf1
 
The Process of Infection by Windy Mesolas-Luzon.pptx
WindyLuzon1
 

Detailed Clinical Models and their relation with Electronic Health Records

  • 1. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás PRESENTED BY: DIEGO BOSCÁ TOMÁS SUPERVISED BY: PhD. MONTSERRAT ROBLES VIEJO and PhD. ALBERTO MALDONADO SEGURA DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS
  • 2. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONTENTS • Introduction and Objectives • Outline • Research work I. Archetype representation of non-dual model architectures II. Archetype-based mapping between clinical information models III. Automatic generation of implementation guides from clinical information models • Conclusions, Contributions, and Future Work • Projects, Publications, and Research Stays 2
  • 3. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 3 INTRODUCTION AND GOALS
  • 4. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás INTRODUCTION • Accessing the full Electronic Health Record (EHR) of a patient is still difficult as this information tends to be distributed into different systems with different semantics, and needs semantic interoperability for their meaningful communication • Semantic interoperability is still far from being achieved in the clinical domain, mostly due to the complexity, variability, and evolving knowledge 4
  • 5. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás INTRODUCTION • One of the prerequisites to achieve semantic interoperability is the standardization of both the data and clinical information models present in the information system (SemanticHealth) • Standards need to be brought to live. There is a lack of adequate methodologies and tools for they widespread use 5
  • 6. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás INTRODUCTION HYPOTHESIS Archetypes can be applied to describe the structure, content, and meaning of existing EHRs as well as to facilitate the development and deployment of new EHR systems that require semantic interoperability 6
  • 7. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE GENERAL OBJECTIVE Provide methodologies and advanced tools based on archetypes to ease the achievement of higher levels of EHR semantic interoperability 7
  • 8. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE SPECIFIC OBJECTIVES To provide means of applying dual model methodology to non-dual information models To provide tools and methodologies for the transformation of existing data into archetype data instances To generate reference materials automatically from archetypes to achieve suitable views for each type of user 8 O1. O2. O3.
  • 9. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OUTLINE R III R II 9
  • 10. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE REPRESENTATION OF NON-DUAL MODEL ARCHITECTURES 10
  • 11. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MOTIVATION • Current EHR systems (typically based on a single model EHR architecture) tend to have clinical knowledge mixed into the information model • Dual model methodology allows the formal description of clinical models of a given EHR information model • Even single model EHR architectures may be suitable to be used as a reference model for archetype definition • Dual model methodology provides a set of advantages, such as formalization, reuse, terminology bindings, or multilinguality 11
  • 12. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE Create a set of methodologies and tools to define archetypes for non-dual information models, ease their definition, and support their advanced use 12 O1.
  • 13. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás REFERENCE MODEL ARCHETYPES • Only a subset of the classes contained in reference models define logical building blocks of EHRs and can be used to define archetypes (business class) • The representation of a business class as an archetype is what we call a Reference Model Archetype (RMA) † • Any other archetype must be a specialization of one of them – Archetype editing becomes a process of subtyping by constraints • This approach opens the door to support multiple reference models 13 † Maldonado et al, LinkEHR-Ed: a multi-reference model archetype editor based on formal semantics. IJMI 2009
  • 14. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EXAMPLE: ISO13606 BUSINESS CLASSES 14
  • 15. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás BUILDING REFERENCE MODEL ARCHETYPES • In order to define archetypes in a given reference model, we must build the set of RMAs first – We achieve this by analyzing the formal schema definitions (typically XML Schema) – This is not always possible, as the schema may not be public, is defined in an unsupported format, or is underspecified (e.g. XML Schema any type) • Two alternatives: Creating them from other metamodel representations or defining them manually 15
  • 16. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CREATING RMA FROM METAMODELS • For this process, a suitable metamodel that faithfully represents a given standard is chosen • The metamodel, e.g. ecore definitions or Basic Meta Model (BMM) definitions, is analyzed 16
  • 17. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CREATING RMA FROM METAMODELS Base of FHIR Ecore model Transformed into FHIR archetypes / extended resources FHIR Reference Model Archetype Defined in FHIR Resource Base of openEHR BMM Transformed into openEHR archetypes Defined in openEHR RM openEHR RMAs • This approach was used to support archetype creation for FHIR DSTU and BMM-based models such as openEHR and CIMI 17
  • 18. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CREATING RMA MANUALLY • As RMAs are archetypes it is feasible to build them by defining the object, attribute, and primitive constraints • An Archetype Object Model (AOM) editor was created • Japanese standard MedXML MML RMAs were built using this approach 18
  • 19. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ADVANCED ARCHETYPE EDITING • Target users of archetype editors come from the clinical domain. Archetype editors must hide the complexity of the underlying reference model – The easiest solutions is to hard-code the reference model into the editors but… – It is harder to cope with multiple reference models and their evolution. • In order to support multiple reference models and at the same time keeping the editing process simple for clinical users, different approaches and methodologies have been investigated, namely: – Use of specific editors – Semantic patterns – Archetype creation from data instances – Syntactic model transformation between standards – Mapping to other standards 19
  • 20. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás USE OF SPECIFIC EDITORS • Specific editors for each reference model can be defined to hide their complexity when creating archetypes. • These editors are based on a documentation file and can be dynamically included in the tool. • Specific editors for ISO13606, openEHR, and HL7 CDA have been defined. 20
  • 21. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás USE OF SPECIFIC EDITORS 21
  • 22. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SEMANTIC PATTERNS • Archetype reuse is not limited to archetype slots and internal references • Semantic patterns are reusable solutions to recurring modeling problems – They combine structural, terminological, and ontological representations • We implemented the semantic patterns as archetype fragments with known semantics • These semantic patterns are useful for creating equivalences between standards – E.g. How an openEHR Observation is represented in ISO13606 or HL7 CDA reference model • Examples of semantic patterns are – General use structures such as table, tree, or panels – Generic clinical models such as exam of XYZ – Representation of archetypable classes of different reference models such as observation, event, or history in ISO13606 • In addition to the support for using semantic patterns in archetype edition, a semantic pattern manager was implemented to allow their versioning and management 22
  • 23. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE CREATION FROM DATA INSTANCES • One of the biggest challenges when applying archetypes to a non-dual reference model is that defining a minimum set of archetypes is required in order to take advantage of archetype-based methodologies • As the systems are already deployed, it is feasible to obtain sample data instances • A methodology for the creation of archetypes from data instances was developed • This process considers each data instance as a “constant archetype” (an archetype with every constraint fixed to a constant) and reduces the problem to merging two archetypes into a single one 23
  • 24. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE CREATION FROM DATA INSTANCES • The automatic merging process traverses each instance and loosens the resulting archetype constraints according to the new values 24 Instance 1 Instance 2 Resulting archetype |102..115| |60..70|
  • 25. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SYNTATIC MODEL TRANSFORMATION BETWEEN STANDARDS • Transformation of clinical models between different standards is a difficult problem – Ontology-based model and data transformations is one of the most promising approaches • However, most of the time equivalences are defined in the standards themselves or are clear enough so complex ontology reasoning is not needed • These equivalences can be declared as rules to be executed • Three different kinds of rules were detected depending on the trigger: – Structure-based rules: triggered by the structure and values – Terminology-based rules: triggered by the terminological binding – Generic rules: transformation to generic classes • Defined rules transform the archetypes and create the mapping equivalences for the automatic data transformation 25
  • 26. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SYNTATIC MODEL TRANSFORMATION BETWEEN STANDARDS • This methodology is demonstrated by a proposed transformation between openEHR and ISO13606 (and vice versa). Rules were implemented in drools – All archetypes from openEHR CKM (415) were translated to ISO13606 and the Spanish Ministry of Health archetypes (23) were translated to openEHR and tested as valid for their respective reference model Target class in openEHR Source term binding contained in SNOMED CT subset Observation << 363787002 | Observable entity (observable entity) | OR << 284365007 | Examination of body site (procedure) | OR << 122869004 | Measurement procedure (procedure) | Evaluation << 243814003 | Interpretation of findings (observable entity) | Instruction << 243120004 | Regimes and therapies (regime/therapy) | OR << 400999005 | Procedure requested (situation) | Action << 129264002 | Action (qualifier value) | OR << 416118004 | Administration (procedure) | OR << 443938003 | Procedure carried out on subject (situation) | OR << 71388002 | Procedure (procedure) | Admin_entry << 14734007 | Administrative procedure (procedure) | OR << 304784009 | Administrative form (record artifact) | Event << 272379006 | Event (event) | 26
  • 27. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPE-BASED MAPPING BETWEEN CLINICAL INFORMATION MODELS 27
  • 28. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MOTIVATION • Patient health data is distributed among different healthcare facilities, which makes crucial their integration and communication • Health data communication must be done in a meaningful way, avoiding all possibility of misunderstanding or misinterpretation • This crucially depends on the standardization of the EHR architecture used to represent the data • Standardizing existing data is one of the main problems in adopting EHR standards 28
  • 29. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE To define and implement a set of methodologies and tools for the normalization of legacy data and the transformation between EHR standards 29 O2.
  • 30. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás PROBLEM • The problem of data transformation is a difficult one, as deals with differences and mismatches between heterogeneous data formats and models • This is even harder in healthcare domain, due to the intrinsic complexity of EHR data • Standard EHR architectures and archetypes are defined without any consideration to the internal database design • The definition of these transformation programs is a complex process, usually involving the creation of custom non-reusable software 30
  • 31. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING APPROACH • Existing data transformation formalisms have been studied and adapted to cope with the special requirements of the archetypes • We use a “specify-generate” approach – High-level declarative assertions are used to specify relationships between the source and target schemas – These assertions are compiled automatically into executable scripts 31
  • 32. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FORMAL DEFINITION • Source schemas can be either XML Schema or an archetype • Target schema is an archetype • We use the Nested Relational (NR) model for the specification of both source and target schemas, as archetypes impose hierarchical structures • NR model generalizes relational model (tuples and relations) by modeling them as records and sets of records respectively • This model allows the representation of hierarchical structures as the archetype 32
  • 33. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FORMAL DEFINITION • The set of atomic data types of our model are the ones supported by archetypes: – string, integer, real, date, time, date and time, duration, and boolean • Non-atomic types are – Record types of the form Rcd 𝑎1 𝑒1:𝑓1 : 𝜏1, … , 𝑎 𝑛 𝑒 𝑛:𝑓𝑛 : 𝜏 𝑛 – Set types of the form SetOf 𝜏1 𝑙1:𝑢1 … 𝜏 𝑛 𝑙 𝑛:𝑢 𝑛 𝑙 𝜏:𝑢 𝜏 – Choice types of the form ChoiceOf 𝑎1: 𝜏1 … 𝑎 𝑛: 𝜏 𝑛 • where: – 𝜏 represents either an atomic, set, or record type – 𝑛 ≥ 1, 𝑒𝑖 ∈ 0,1 , 𝑒𝑓 ∈ 0,1 and 𝑒𝑖 ≤ 𝑒𝑓 – li is a natural number, ui is a natural number or ∞ and li ≤ ui – 𝑖=1 𝑛 𝑙𝑖 ≤ 𝑢 𝜏 and 𝑖=1 𝑛 𝑢𝑖 ≤ 𝑙 𝜏 33
  • 34. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FORMAL DEFINITION 34
  • 35. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION • Only constrained entities (classes and attributes) of the reference model appear in the archetypes – The underlying reference model constraints are implicit – This is also the case of the parent archetype in specialized archetypes • In order to generate correct data instances, archetypes must be merged with the parents archetypes and the underlying reference model 35
  • 36. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION 36
  • 37. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION • Mapping language is based on tgds † (tuple-generating-dependencies) • To describe how to compute a value for an atomic attribute of the target schema (archetype) a list of filter/function pairs can be defined 37 $gender={ If (/patient/gender=’M’ OR /patient/gender=’m’) then 0 Else if (/patient/gender=’W’ OR /patient/gender=’w’) then 1 Else if (/patient/gender=0 OR /patient/gender=1) then /patient/gender Else 9 } † Fagin et al, Data exchange: semantics and query answering. TCS 2005
  • 38. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás • Value correspondences lack expressive power to completely describe grouping semantics • Default grouping semantics is based on the Partition Normal Form (PNF) – In PNF, two distinct records that coincide in all the atomic (non-multivaluated) attributes cannot exist • We use Skolem functions † to achieve PNF GROUPING 38 † Hazewinkel et al, Encyclopædia of Mathematics
  • 39. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás GROUPING • Grouping semantics can be customized by modifying the Skolem functions or by defining Object Builders • Skolem parameters can be removed from the Skolem functions • Object builders control the generation of target instances taking into account the data in the source – Object Builders represent iterators on the source nodes they are connected to – In each iteration, a new element is constructed, of the kind of the target node reached by the builder 39
  • 40. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING DEFINITION EXAMPLE 40 Object builder Attribute mapping Object builder nesting $prof/cargo=“cirujano” $prof $ingr $hosp
  • 41. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás XQUERY GENERATION • Archetype constants are assumed to be transformation functions whose filter has ‘true’ value and the function is fixed to the constant value • Constraints on primitive types (valid ranges, lists of values) are enforced in the transformation script • When the mapping correspondences have been defined, they are traversed in order to generate the transformation script Archetype constraint Value correspondence XQuery extract number matches {|0..10|} If true then /data/measurements/value (specified by user) For $val in /data/measurements/value Where $val≥0 and $val≤10 Return <number> {data($val)}</number> 41 Archetype constraint Value correspondence XQuery extract number matches {1} If true then 1 (automatically generated) Return <number> 1 </number>
  • 42. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás XQUERY GENERATION • More than one mapping can be applied to a single attribute. In this case, each one of these mappings produces a different transformation program • For each object in the archetype a nested XQuery FLWOR is produced 42
  • 43. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás XQUERY GENERATION 43
  • 44. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MAPPING SUMMARY Archetype Reference Model XQuery script Source XML instance Output XML instance Mapping source (XML Schema or archetype) Mapping Comprehensive ArchetypeMerge Defines Defines Autogenerates Instance of Generates Instance of Instance of 44
  • 45. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás TECHNICAL EVALUATION • For the technical validation of the mapping capabilities, the STBenchmark was used – This benchmark describes 17 mapping scenarios that should be supported by mapping systems • Each scenario contains a source and target schema expressed as an XML Schema, an instance of the source schema and a visual and textual description of the scenario – In our case, target schema is modeled as an archetype 45
  • 46. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás TECHNICAL EVALUATION • From the 17 scenarios, 15 could be successfully tested as the expected target instance could be generated • Two scenarios could not be tested – One scenario could not be tested due to archetypes not supporting the definition foreign keys – One scenario could not be tested due to limitations in the expressive power of our mapping language 46
  • 47. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EVALUATION IN REAL SETTINGS: MEDICINES RECONCILIATION PROJECT • The objective was to obtain and evaluate a complete medication list of patients regardless where they came from • Archetypes are based on epSOS specifications • Hospital EHR system was upgraded to include the patient summary • The project was awarded with the Spanish Ministry of Health quality award LinkEHR Platform DATA NORMALIZATION DATA INTEGRATION NOMENCLATOR DIGITALIS INDEPENDENT WEB VIEWER HOSPITAL EHR (SELENE) Web Service Primary care OMI-AP Hospital de Fuenlabrada FARMATOOLS SELENE 47
  • 48. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EVALUATION IN REAL SETTINGS: PATIENT ELIGIBILITY • Use of archetypes and mappings in different abstraction levels to determine if a patient is eligible for a cancer clinical trial • Patient is not eligible if it has severe comorbidity, which is derived from a series of cascade mappings 48
  • 49. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás EVALUATION IN REAL SETTINGS PATIENT ELIGIBILITY • Presence/absence of metastatic tumor (source EHR) • Presence/absence of metastatic solid tumor (source archetype) Condition Mapping @count(summary/problems/problem, @in(summary/problems/problem/code, @descendents(“128462008”))>0 TRUE TRUE FALSE Condition Mapping (Evaluation_problem_DS_metastatic_tumor_v1/structure/present = TRUE) AND (Evaluation_problem_DS_solid_tumor_v1/structure/present = TRUE) TRUE TRUE FALSE 49
  • 50. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ARCHETYPES FOR THE GENERATION, VALIDATION, AND USE OF EHR SYSTEMS 50
  • 51. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás MOTIVATION • Archetypes ease the communication between clinicians and IT staff • Those clinicians and IT staff who are not experts in dual model architectures need to understand the archetypes – Clinicians are able to provide valuable inputs for archetype validation and evolution – IT staff can use the archetypes as formal specifications of the system • Clinicians and IT staff make use of different sets of artifacts to understand the archetypes and bring them to life in their systems 51
  • 52. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás OBJECTIVE To enable the automatic generation of artifacts from clinical archetypes for the validation of current systems and the creation of new ones from both clinical and technical perspectives 52 O3.
  • 53. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás GENERATION OF ARTIFACTS • Archetypes can be used as guidance to automatically generate a wide range of artifacts –Validation rules –Sample data instances –Mindmaps and Sample forms –Implementation guides 53
  • 54. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás VALIDATION: NATURAL RULE LANGUAGE • Natural Rule Language (NRL) provides a formal and executable way of defining English-like rules • Archetype constraints are interpreted and translated to NRL • These rules can be translated to OCL or Schematron 54
  • 55. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás VALIDATION: HL7 STYLE RULES • In the same way, rules from archetypes can be translated into HL7 conformance statements • These statements can be generated in the desired language 55
  • 56. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás VALIDATION: SCHEMATRON RULES • Different kinds of Schematron rules are derived for each kind of archetype constraint • The definition of two different Schematron phases allows to validate both the explicit and the implicit archetype constraints (only archetype or archetype + reference model) <!-- Rules for archetype path /items[Blood pressure measurement]/parts[Systolic]/value[at0005] --> <rule context="ENTRY/items/parts[archetype_id='at0001']/value"> <!-- Existence for attribute 'units' --> <report test="count(units)=0">Attribute 'units' is required and does not appear in data</report> <!-- Occurrences for the alternatives of attribute 'units' --> <assert test="(count(units)=1)">The attribute 'units' has more than one alternative or empty alternatives</assert> <!-- Existence for attribute 'value' --> <report test="count(value)=0">Attribute 'value' is required and does not appear in data</report> <!-- 'value' constraint is not valid--> <assert test="value&gt;=0.0 and value&lt;1000.0">Constraint for 'value' does not follow the archetype: 'value' <value-of select="value" /> is not in [0.0,1000.0[</assert> </rule> 56
  • 57. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás SAMPLE DATA INSTANCES • Sample data instances allow to perform stress tests on systems • Data instances are created by using the mapping mechanism explained before – Constant values are assigned to each archetype constraint – These constant values are used to generate a transformation script to produce the sample data instance – Generated instances follow the archetype and the reference model, but do not describe real clinical cases 57
  • 58. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás ADDITIONAL ARTIFACTS • A mindmap representation from the archetype is created in order to give an overview of the clinical model • Archetype constraints can also be interpreted as fields of an sample html form • Archetype constraints bound to terminologies can be displayed in summary value set tables 58
  • 59. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás IMPLEMENTATION GUIDE GENERATION • Presented artifacts can be combined according to user’s needs to provide helpful implementation guides • Each object in the archetype generates a set of NRL, HL7, and Schematron rules, as well as a sample data instance for that object • A general mindmap, archetype metadata, value set tables, sample form, reference model documentation, and a table of contents can also be generated 59
  • 60. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 60 CONCLUSIONS, CONTRIBUTIONS, AND FUTURE WORK
  • 61. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONCLUSIONS • The specifications of eHealth interoperability standards must be brought to life by system designers and implementers • The challenge is not the lack of standards, but its implementation at a reasonable cost • Presented methodologies and tools ease the joint use of the three layers of artefacts (Clinical Models, Reference Models, and Clinical Terminologies) needed to achieve high levels of semantic interoperability 61
  • 62. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONCLUSIONS • The advantages of a joint use of archetypes with non- dual model standards outweigh the disadvantages – Using archetypes for currently used reference models such as HL7 CDA, HL7 FHIR, or MedXML MML will help to the rapid adoption of both the original standard and the dual model approach • The presented set of integrated innovative tools help current systems to achieve semantic interoperability by normalizing data based on clear semantically-rich clinical models • Proposed methodology promotes the involvement of clinical staff in the modeling and validation process • All presented developments have been included in LinkEHR platform 62
  • 63. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONTRIBUTIONS • Design and implementation of a set of methodologies and tools to support the definition of archetypes from multiple reference models • Design and implementation of a new methodology for the transformation of legacy data into archetype-based data • Reuse of this methodology for the data transformation between archetype-based standards • Design and implementation of a set of methodologies for the automatic generation of implementation guides and reference materials from archetypes 63
  • 64. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás FUTURE WORK • From data perspective, variability in original sources continuously provides new challenges – Support to other source schemas such as RDF or OWL – Automatic schema matching techniques • Based both in clinical terminologies and tree-matching algorithms • Use of clinical vocabularies and ontologies provides challenges on their own. The integration of ontologies in queries and reasoning will benefit both patient and public health – Mapping specification must be improved to support this advanced use • Automatic artifact creation can benefit from terminology bindings • Having available big quantities of normalized archetype-based data provides the opportunity to generate semantically rich research and public health repositories 64
  • 65. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 65 PROJECTS, PUBLICATIONS, AND RESEARCH STAYS
  • 66. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás RESEARCH PROJECTS • The results of this PhD Thesis have contributed directly to the results of the following research projects: – ResearchEHR: Platform for the acquisition and sharing of information and knowledge for network-based clinical research communities (TSI2007-66575-C02-01) – Trial-Me: Intelligent tools for linking EHR to clinical trial systems (TIN2010-21388-C02-01) – Clin-IK-Links: Clinical information and knowledge models for linking EHR and Clinical Decision Support Systems (TIN2014-53749-C2-1-R) 66
  • 67. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás JOURNAL CONTRIBUTIONS AND BOOK CHAPTERS • J. A. Maldonado, D. Moner, D. Boscá, J. T. Fernández-Breis, C. Angulo, and M. Robles, “LinkEHR-Ed: A multi-reference model archetype editor based on formal semantics,” International journal of medical informatics, vol. 78, no. 8, pp. 559–570, 2009 • M. Marcos, J. A. Maldonado, B. Martínez-Salvador, D. Boscá, and M. Robles, “Interoperability of clinical decision-support systems and electronic health records using archetypes: a case study in clinical trial eligibility,” Journal of biomedical informatics, vol. 46, no. 4, pp. 676–689, 2013 • J. A. Maldonado, C. M. Costa, D. Moner, M. Menárguez-Tortosa, D. Boscá, J. A. M. Giménez, J. T. Fernández-Breis, and M. Robles, “Using the ResearchEHR platform to facilitate the practical application of the EHR standards,” Journal of biomedical informatics, vol. 45, no. 4, pp. 746–762, 2012 • D. Boscá, J. A. Maldonado, D. Moner, and M. Robles, “Automatic generation of computable implementation guides from clinical information models,” Journal of biomedical informatics, vol. 55, pp. 143–152, Jun. 2015 67 Publications in Q1 Journals RI RII RIII
  • 68. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás JOURNAL CONTRIBUTIONS AND BOOK CHAPTERS • S. Kobayashi, D. Boscá, N. Kume, and H. Yoshihara, “Reforming MML (Medical Markup Language) Standard with Archetype Technology,” Indian Association for Medical Informatics, vol. 91, p. 57, 2014. • J. A. Maldonado, D. Boscá, D. Moner, and M. Robles, “LinkEHR: A Platform for the Normalization of Legacy Clinical Data Based on Archetypes,” Interoperability in Healthcare Information Systems: Standards, Management, and Technology: Standards, Management, and Technology, p. 45, 2013. • M. Marcos, J. A. Maldonado, B. Martínez-Salvador, D. Moner, D. Boscá, and M. Robles, “An archetype-based solution for the interoperability of computerised guidelines and electronic health records,” in Artificial Intelligence in Medicine, Springer Berlin Heidelberg, 2011, pp. 276–285. 68 RI RII
  • 69. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONGRESS PAPERS • CONGRESS PAPERS RELATED WITH THE THESIS – D. Boscá, D. Moner, J. A. Maldonado, and M. Robles, “Combining Archetypes with Fast Health Interoperability Resources in Future-proof Health Information Systems.,” Studies in health technology and informatics, vol. 210, pp. 180–184, 2014. – D. Boscá, L. Marco, D. Moner, J. A. Maldonado, L. Insa, and M. Robles, “Detailed Clinical Models Governance System in a Regional EHR Project,” in XIII Mediterranean Conference on Medical and Biological Engineering and Computing 2013, Springer, 2014, pp. 1266–1269. – D. Moner, J. A. Maldonado, D. Boscá, A. Mañas, and M. Robles, “Development of a Visual Editor for the Definition of HL7 CDA Archetypes,” in XIII Mediterranean Conference on Medical and Biological Engineering and Computing 2013, Springer, 2014, pp. 1258–1261. 69
  • 70. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONGRESS PAPERS • CONGRESS PAPERS RELATED WITH THE THESIS – D. Boscá, L. Marco, V. Burriel, T. Jaijo, J. M. Millán, A. M. Levin, O. Pastor, M. Robles, and J. A. Maldonado, “Genetic testing information standardization in HL7 CDA and ISO13606.,” in MedInfo, 2013, pp. 338–342. – C. Martínez-Costa, D. Boscá, M. C. Legaz-García, C. Tao, B. J. Fernández, S. Schulz, and C. G. Chute, “Isosemantic rendering of clinical information using formal ontologies and RDF.,” Studies in health technology and informatics, vol. 192, pp. 1085–1085, 2012. – D. Boscá, J. A. Maldonado, D. Moner, and M. Robles, “Detailed clinical models to facilitate interstandard interoperability of data types,” 23rd International Conference of the European Federation for Medical Informatics. Oslo, Norway: European Federation for Medical Informatics, 2011 70
  • 71. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás CONGRESS PAPERS • CONGRESS PAPERS RELATED WITH THE THESIS – J. Maldonado, D. Moner, D. Boscá, C. Angulo, L. Marco, E. Reig, M. Robles, and others, “Concept-based exchange of healthcare information: The LinkEHR approach,” in Healthcare Informatics, Imaging and Systems Biology (HISB), 2011 First IEEE International Conference on, 2011, pp. 150–157. – D. Moner, J. A. Maldonado, D. Boscá, C. Angulo, M. Robles, D. Pérez, and P. Serrano, “CEN EN13606 normalisation framework implementation experiences,” Seamless Care, Safe Care: The Challenges of Interoperability and Patient Safety in Health Care: Proceedings of the EFMI Special Topic Conference, June 2-4, 2010, Reykjavik, Iceland, vol. 155, p. 136, 2010. – M. Robles, J. T. Fernández-Breis, J. A. Maldonado, D. Moner, C. Martínez-Costa, D. Boscá, and M. Menárguez-Tortosa, “ResearchEHR: Use of semantic web technologies and archetypes for the description of EHRs,” Studies in health technology and informatics, vol. 155, p. 129, 2010 71
  • 72. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás RESEARCH STAY • RESEARCH STAY – Main Subject: Detailed clinical model representation of MML Japanese standard – Place: Division of Medical Information Technology and Administration Planning, Kyoto University (Japan) – Length: 3 Months (2011) 72
  • 73. 26 Enero 2016 DETAILED CLINICAL MODELS AND THEIR RELATION WITH ELECTRONIC HEALTH RECORDS Diego Boscá Tomás 73

Editor's Notes

  • #2: Good morning and thanks everyone for coming. My name is Diego Boscá Tomás, and today I am defending my dissertation on “Detailed Clinical Models and their relationship with EHR”
  • #3: Casos de estudio Referencias en las transparencias
  • #4: Pasamos pues al primer bloque con la motivación y objetivos de este trabajo….
  • #8: to provide a set of methodologies and tools based on archetypes for the achievement of higher levels of EHR semantic interoperability
  • #11: Image by Joe Miserendino (CC)
  • #14: Multiple RM
  • #25: Sensitivity and Specificit
  • #28: Defining archetypes for a given reference model allows us to generate transformation programs that use them as source or target This is a key issue in the normalization of EHR data, as legacy data must be preserved when standardizing the systems. Image by Tom Page (cc)
  • #43: For Let Where Order by Return
  • #46: Benchmark is available at http://db.disi.unitn.eu/pages/stbenchmark/
  • #50: Subrayar source…
  • #51: Image © Quandtum
  • #55: Icons by http://www.aha-soft.com/
  • #61: Finally I am going to introduce
  • #76: Ejemplo que una las 3 partes Validaciones
  • #82: Intuitively, an object builder defines an iterator on the source nodes they are drawn from (a), in each iteration, a new target element (b) is generated for each combination of source values that satisfy the filter (c). It is possible to define hierarchies of builders where parent builders propagate its context to its children. In this example, if no object builders were defined to control the generation of Dept instances, a single instance would be generated. Object builders
  • #83: The source schema consists of a single set of Source/Gene records with three sub elements describing the name of the gene, the type (whether it is ‘primary’ or not) and the protein which the gene belongs to. The target schema consists of two sets of records, Target/Gene and Target/Synonym respectively. Since a protein can have multiple genes but only one of the genes is primary, the primary gene is stored in Target/Gene, while all other genes of the same protein (i.e., synonyms) are stored in Target/Synonyms. Additionally, a foreign key Target/Synonym/GeneWID references Target/Gene/Name to indicate the primary gene of each synonym and the protein which they collectively belong to.
  • #87: Generated instances are correct instances of a given model Instances are constant archetypes that can be tested with the subsumption mechanism Generated rules can correctly validate data instances Typical implementation errors + MU errors incorrect data terminology misuse data heterogeneity Generated implementation guides have good quality and are useful for the development of EHR systems Quality metrics Evaluation by clinical advisors; use in proyects