Mapping IEEE PHD to FHIR - context

Slides:



Advertisements
Similar presentations
Helmut König, Siemens Medical Solutions
Advertisements

March 7, 2011 COMPARATIVE ANALYSIS HL7 V2.5.1 Implementation Guide: Orders and Observations; Interoperable Laboratory Result Reporting to EHR (US REALM)
QIDAM Issues and proposals for a logical model For discussion during HL7 WG Meeting in Jan 2014 Thursday Q3.
LESSON 2 FRACTIONS. Learning Outcomes By the end of this lesson, students should be able to: ◦ Understand types of fractions. ◦ Convert improper fractions.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
FHIR-Based CDS An approach to the implementation of Clinical Decision Support Use Cases using FHIR.
FHIM Overview How the FHIM can organize other information modeling efforts.
Public Health Reporting Initiative June 13, 2012.
Initial slides for Layered Service Architecture
Body Mass Index (BMI) Content Profile Brief Profile Proposal for 2012/13 presented to the Quality, Research & Public Health (QRPH) Planning Committee Jennifer.
Public Health Data Element Standardization - A Framework for Modeling Data Elements Used for Public Health Case Reporting Case Reporting Standardization.
HSPC Profiles: Conformance and Interoperability. Definitions.
1 HITSP – enabling healthcare interoperability Current Framework and Fundamental Concepts  For those unfamiliar with the HITSP Harmonization Framework.
© 2010 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Virtual Medical Record Aziz Boxwala, MD, PhD March 12, 2013.
EHR Standards Project DSTU Basic Observations Professional Service July 05, 2006 Webcast.
Logical Model Collaboration Scope, proposal, and next steps.
PCD - WCM Waveform Communication Management [WCM].
DICOM SR / CDA Rel.2 Mapping San Antonio WGM, May 2006 Helmut König Co-Chair II SIG / DICOM WG20 Siemens Medical Solutions.
© 2012 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
: Adding and Subtracting Rational Expressions Introduction Expressions come in a variety of types, including rational expressions. A rational expression.
Slide 1 © Copyright 2015 Qvera LLC All rights reserved N Main Suite D140 Kaysville UT FHIR is a registered trademark of HL7.org.
HL7 Health Care Devices (DEV) Summary 2016 January HL7 WGM, Orlando.
Helping the Cause of Medical Device Interoperability Through Standards- based Test Tools DoC/NIST John J. Garguilo January 25,
© 2015 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
Chapter 23: Overview of the Occupational Therapy Process and Outcomes
Object Hierarchy Containment Tree
Biopharma Breakout Goals
Representation of Hypersensitivity, Allergy and adverse reactions in SNOMED CT Bruce Goldberg, MD, PhD.
Chapter 3 DOCUMENTING ACCOUNTING SYSTEMS
IHE PCD F2F San Diego, America’s Finest City
JANENE: WE ARE ON A SEPARATE PHONE LINE:
IEEE Nomenclature Status IEEE GC at HL7, San Antonio, TX
JANENE: WE ARE ON A SEPARATE PHONE LINE:
Current Framework and Fundamental Concepts
Nutrition in HL7 Standards
Paul Schluter, GE Healthcare
Nutrition in HL7 Standards
Validate device bundle example
SOA FHIR Action Items Creating SOA labeling standard/name space/naming convention for FHIR Operations.
SOA FHIR Action Items Creating SOA labeling standard/name space/naming convention for FHIR Operations. The expectation is that SOA FHIR services will be.
FHIR PlanDefinition for Care Planning
CDA Document ‘Executive’ Summary Section
IHE DEC and Continua WAN Interface Proposals for Remote Monitoring
ACM Across Domains and the Enterprise
Device related Resources
IEEE and NIST RTMMS Terminology Process
Mapping IEEE PHD to FHIR - context
Converting HL7v2.6 to FHIR Mattes Rhein1, Stefan Schlichting2, Josef Ingenerf3 1Medizinische Informatik, Universität zu Lübeck 2Drägerwerk AG, Lübeck;
WE ARE ON A SEPARATE PHONE LINE:
Clinical Observation Interoperability March 18, 2008
LHS – Care Team Value Sets
JANENE: WE ARE ON A SEPARATE PHONE LINE:
_ Update Seth Blumenthal, MBA Director, Data & Innovation PCPI
Electronic Health Record Access Control 7
Software Analysis.
IEEE GC at HL7, Baltimore, MD
LIVD on FHIR Draft Discussion.
Patient Care WG Allergy and Intolerances Project
JANENE: WE ARE ON A SEPARATE PHONE LINE:
Howard Follis, MD Juxly CEO
Michael Faughn Prometheus Computing
Basic Data Provenance April 22, 2019
US Core Data for Interoperability (USCDI): Data Provenance IG
Personal Health Device (PHD) Implementation Guide
Recommender System.
Point-of-care devices in fhir
Presentation transcript:

Mapping IEEE 11073 PHD to FHIR - context The PCHA is working on a mapping from observations originating from IEEE 11073 Personal Health Devices to HL7 FHIR Resources This work is part of the H.812.5 implementation guide – for trial use This work also defines an HL7 implementation guide that profiles a number of FHIR resources. Similar work is done for IEEE 11073 PoCD. This set of slides focuses on issues with the PHD FHIR usage.

Mapping PHD to Device[Component] in FHIR - details H.812.5 uses 3 FHIR resource types to map IEEE PHD data to FHIR: Patient – to identify the patient to whom the observations apply DeviceComponent – data identifying the PHD device and its status Observation – measurements or assertions on a patient or on a PHD device Issues: A PHD that supports multiple specializations is mapped to multiple DeviceComponents – one per specialization and a top-level DeviceComponent that contains the productionSpecification This is done since DeviceComponent.type is a single attribute that can contain only one device type value To map the System-Type-Spec-List multiple DeviceComponents are needed that reference a top-level DeviceComponent – to avoid repeating the productionSpecification This is a rather complex mapping The FHIR Device resource does include UDI as an attribute and DeviceComponent does not and vice versa the FHIR Device resource does not include the productionSpecification. => a Device resource will be needed or UDI should be added to DeviceComponent The conceptual difference between Device and DeviceComponent is unclear and many of the attributes overlap already. Note that FHIR Observations can reference a Device, a DeviceComponent or a DeviceMetric Since EHRs are, due to CDA, more likely to support Device, we prefer to use Device for the mapping.

Background: FHIR resources - UML

(Example) Mapping PHD to FHIR Note: IEEE PHD Metrics are not mapped (yet) to FHIR DeviceMetric IEEE 11073 PHD MDS Object With prodSpec and UDI SpO2 Numeric Pulse Rate Numeric Body Mass Numeric Height Numeric BMI Numeric Event report (carrying a metric) FHIR Resources Device FHIR Observation UDI WeightScale DeviceComponent TopLevel DeviceComponent Body Mass DeviceMetric Height DeviceMetric BMI DeviceMetric productionSpec PulseOx DeviceComponent SpO2 DeviceMetric PulseRate DeviceMetric

PCHA Requested changes on HL7 FHIR resources Can Device and DeviceComponent be merged in the next FHIR release? If a merge cannot be achieved, can UDI be added to DeviceComponent? Can there be an attribute in DeviceComponent and/or Device that can carry multiple device types? E.g. DeviceComponent.type with 1..* multiplicity Question: would a mapping of the IEEE Metric objects to FHIR DeviceMetric resources be useful?