Presentation of my PhD dissertation. Contains three main subjects:
-Archetype representation of non-dual model architectures
-Archetype-based mapping between clinical information models
-Automatic generation of implementation guides from clinical information models
Call Girls Service Charbagh { Lucknow Call Girls Service 9548273370 } Book me...
Â
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>=0.0 and value<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
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â
Casos de estudio
Referencias en las transparencias
Pasamos pues al primer bloque con la motivaciĂłn y objetivos de este trabajoâŚ.
to provide a set of methodologies and tools based on archetypes for the achievement of higher levels of EHR semantic interoperability
Image by Joe Miserendino (CC)
Multiple RM
Sensitivity and Specificit
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)
For Let Where Order by Return
Benchmark is available at http://db.disi.unitn.eu/pages/stbenchmark/
Subrayar sourceâŚ
Image Š Quandtum
Icons by http://www.aha-soft.com/
Finally I am going to introduce
Ejemplo que una las 3 partes
Validaciones
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
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.
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