Top Banner
vMR: the HL7 virtual Medical Record Standard May 16, 2013 Health eDecisions All Hands Call Claude Nanjo David Shields

VMR: the HL7 virtual Medical Record Standard May 16, 2013 Health eDecisions All Hands Call Claude Nanjo David Shields.

Mar 27, 2015



Chase Stack
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
  • Slide 1

vMR: the HL7 virtual Medical Record Standard May 16, 2013 Health eDecisions All Hands Call Claude Nanjo David Shields Slide 2 Presentation Goal Provide a broad general understanding of the vMR Describe the motivation for such a model Describe the high-level organizational structure of the vMR Describe the relationship between the vMR and CCDA documents 2 Slide 3 Why do we need a vMR? Motivation and Important Model Features 3 Slide 4 Background A holy grail of clinical informatics is scalable, interoperable CDS Key requirement for interoperable CDS and re-use of CDS knowledge resources = use of a common patient data model Referred to as a Virtual Medical Record or vMR (Johnson et al., AMIA Annu Symp Proc, 2001) Lack of a common vMR has been a major barrier to sharing knowledge and scaling CDS Slide 5 Example Challenge without VMR ObservationBlood Pressure Code = BP Systolic = 120 mmHg Value = 120/80 mmHg Diastolic = 80 mmHg ObservationVital Sign Code = BP Type = BP Observation Value = 120/80 Code = SBP Units = mmHg Value = 120 mmHg Observation Code = DBP Value = 80 mmHg Slide 6 Blood Pressure in the vMR 6 Slide 7 Purpose and Design Principles Designed specifically and solely for CDS Not intended for persistence or provenance as medical document Lightweight and engineered for computability (over human readability) Compromise between clinical detail and broad generalization 80/20 rule Favors model stability 7 Slide 8 Features of the vMR Part I Core datatypes based on simplified ISO 21090, also known as HL7 datatypes R2 Loosely based on CCD and the HL7 Clinical Statement Gave base classes business-friendly names Promoted negation and mood to explicit classes to reduce possible errors Resolved confusion around CDA code, effective-time, and status Removed less useful attributes for CDS 8 Slide 9 Features of the vMR Part II Extensible Attribute/Template extension mechanism Entity and Clinical Statement Relationships Also considering class extension mechanism UML specializations Schema extensions Designed to allow flattening of hierarchical structure for easier computation 9 Slide 10 vMR Goal Provide common information model upon which interoperable clinical decision support resources (e.g., rules) can be developed Slide 11 Project History Analysis of data required by 20 CDS systems from 4 countries (Kawamoto et al., AMIA 2010) Refinement of vMR via implementation within OpenCDS Adopted in September 2011 as Informative Specification Enhancements balloted in May 2013 to address Health eDecision pilot feedback and to better support order set authoring based on an review of existing CPOE system implementations Slide 12 Structural Organization of the vMR 12 Slide 13 Simplified ISO 21090 Data Types Slide 14 vMR-Specific Core Types Support Expressivity and Model Stability 14 Slide 15 Clinical Statement Central to vMR 15 Slide 16 Example Clinical Statement Slide 17 Progressive Specialization 17 Slide 18 Core Data Structures in vMR Entities People, places, and things Clinical Statement Clinical activities Root of vMR is the Patient (an EvaluatedPerson) A Patient may have other associated EvaluatedPersons (e.g., family history) An EvaluatedPerson has associated Clinical Statements 18 Slide 19 Relationships in the vMR Related Entity Example: MMR Vaccine Relationship of following is PartOf above Measles Vaccine Mumps Vaccine Rubella Vaccine XML Example: 19 Slide 20 Relationships in the vMR (cont.) Related Clinical Statement Example: Blood Pressure Observation Relationship of following is PartOf above Systolic Blood Pressure Diastolic Blood Pressure XML Example: 20 Slide 21 Relationships in the vMR (cont.) Entity Relationship To Clinical Statement Example: Lab Diagnostic Procedure Relationship of following is SubjectOf above Sputum Sample Blood Sample XML Example: 21 Slide 22 Groups of Clinical Activities AdverseEvent Encounter Goal Observation Problem Procedure SubstanceAdministration Supply Communication (TBD) 22 Slide 23 Handling Mood UndeliveredProcedure Never performed ProcedureProposal Proposed but not yet ordered ProcedureOrder Ordered ScheduledProcedure Scheduled but not yet delivered ProcedureEvent Delivered and recorded 23 Slide 24 Handling NegationInd as Classes AdverseEvent/DeniedAdverseEvent Problem/DeniedProblem ObservationResult/UnconductedObservat ion SupplyEvent/UndeliveredSupply Etc 24 Slide 25 Why Not Just Use the CCDA as the vMR? CCDA does not include all needed information E.g., Family history model suitable for CDS CCDA is not sufficiently intuitive for direct use by CDS knowledge authors CCDA is deeply nested and verbose, which adds performance penalties in volume production HOWEVER: CCDA can be mapped into the vMR, which has a simpler structure that is more conducive to evaluation The vMR and CCDA are complimentary and intended for different purposes Slide 26 Problem Model CCD vs. VMR Slide 27 From CCDA to vMR CCDA can be transformed into a vMR but not vice-versa (vMR is a subset of CCDA) CDS Services should operate on one model. The vMR was designed for this purpose. Transformation path from CCDA to vMR should be documented (or transform should be provided) Separate CCDA-to-vMR service with service composition? 27 Slide 28 Further Information vMR: Record_(vMR)