Overview for IHE The MITRE Corporation. Overview hData was originally developed by The MITRE Corporation – Internal R&D – Focus on simplifying Continuity.

Slides:



Advertisements
Similar presentations
REST Introduction 吴海生 博克软件(杭州)有限公司.
Advertisements

© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use SOA Working Group Meeting Mark Kramer July 22, 2013 Status Update: hData Record.
OASIS OData Technical Committee. AGENDA Introduction OASIS OData Technical Committee OData Overview Work of the Technical Committee Q&A.
HData History : Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding.
Web Services Seminar: Service Description Languages
Copyright © IBM Corp., All rights reserved. The presentation is licensed under Creative Commons Att. Nc Nd 2.5 license. RESTful Service Oriented.
© 2013 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
Mpeg-21 and Medical data A strategy for Tomorrow ’ s EMR.
IHE IT Infrastructure mHealth access to Document Sharing Profile John Moehrke June 6, 2012.
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 11 July 2013 Meeting #6 hData Record Format Task Force 1 © 2012 The MITRE Corporation.
PAWN: A Novel Ingestion Workflow Technology for Digital Preservation
FHIR and Primary Care Systems; and a FHIR Query Tool Robert Worden Open Mapping Software Ltd
Peoplesoft: Building and Consuming Web Services
Note: This is a preliminary discussion
José Costa Teixeira January 2015 Medication Data Capture and Management.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Initial slides for Layered Service Architecture
Adaptability for flexible mobile service provision in 3G and beyond Nikos Houssos
An XMPP (Extensible Message and Presence Protocol) based implementation for NHIN Direct 1.
Publication and Discovery XDS IHE IT Infrastructure Webinar Series.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
September, 2005What IHE Delivers 1 Key Image Notes Evidence Documents Simple Image & Numeric Report Access to Radiology Information IHE Vendors Workshop.
Toolkit for Planning an EHR-based Surveillance Program | HL7 Clinical Document Architecture An Introduction.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
Open Data Protocol * Han Wang 11/30/2012 *
Generic model for services: health domain study Zoran Milosevic Deontik, Australia
HL7 hData Security Elements. Security Considerations hData can be used in a broad variety of situations – EHR systems, line of business applications –
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 13 June 2013 Meeting #3 hData Record Format Taskforce 1 © 2012 The MITRE Corporation.
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 5 July 2013 Meeting #5 hData Record Format Task Force 1 © 2012 The MITRE Corporation.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise HIMSS Demonstration XDS Document Content Specifications Keith W.
Exploitation of Dynamic Information Relations in the Service-Oriented AFRL Information Management Systems Andrzej Uszok, Larry Bunch, Jeffrey M. Bradshaw.
Gpi gordon point informatics Information Decomposition at NCI Jean Duteau HL7 UK RIMBAA Conference, November 4, 2010.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
6/4/2016 8:05 PM Healthcare Services Specification Project Decision Support Service (DSS) Overview and Areas of Active Discussion HL7 Clinical Decision.
Practical Image Management for Pharma Experiences and Directions. Use of Open Source Stefan Baumann, Head of Imaging Infrastructure, Novartis.
September, 2005Cardio - June 2007 IHE for Regional Health Information Networks Cardiology Uses.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Common Terminology Services 2 CTS 2 Submission Team Status Update HL7 Vocabulary Working Group May 17, 2011.
Meeting Etiquette Please announce your name each time prior to making comments or suggestions during the call Remember: If you are not speaking keep your.
WSDL in a Healthcare Enterprise Architecture Lorraine Constable, Constable Consulting John Koisch, Guidewire Architecture Jean Henri Duteau, GPI.
© 2012 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
HIT Standards Committee Overview and Progress Report March 17, 2010.
September, 2005Cardio - June 2007 Retrieve Information for Display (RID) and Retrieve ECG for Display (ECG)
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
REST By: Vishwanath Vineet.
Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.
September, 2005What IHE Delivers 1 Presenters Scanned Documents.
Medication Statement Event Query RMIM. Simple Query Implemented using query parameter in the GET URI – (section URI)/?(queryParameter)=(value) –
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
CDA Overview HL7 CDA IHE Meeting, February 5, 2002 Slides from Liora Alschuler, alschuler.spinosa Co-chair HL7.
DICOMwebTM 2015 Conference & Hands-on Workshop University of Pennsylvania, Philadelphia, PA September 10-11, 2015 DICOMweb Workflow API (UPS-RS) Jonathan.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
CCD and CCR Executive Summary Jacob Reider, MD Medical Director, Allscripts.
Tung Tran, Ph.D. What is the EMR? Computerized legal medical record created by healthcare organizations Enables storage and retrieval of patient information.
© 2010 IBM Corporation RESTFul Service Modelling in Rational Software Architect April, 2011.
Software Architecture Patterns (3) Service Oriented & Web Oriented Architecture source: microsoft.
XML and Distributed Applications By Quddus Chong Presentation for CS551 – Fall 2001.
SMART Architecture and Application Development Overview
IBM Data Server Gateway for OData
Electronic Health Information Systems
Retrieve Protocol for Execution (RPE)
Quality Measure & Interoperability Solutions
SMART on FHIR for managed authorised access to medical records
WCF Data Services and Silverlight
Presentation transcript:

Overview for IHE The MITRE Corporation

Overview hData was originally developed by The MITRE Corporation – Internal R&D – Focus on simplifying Continuity of Care use cases – Broad initial goal set: Wire format simplification Strict data modeling and content separation from exchange mechanics Flexible metadata model Transport simplification Patient-centric identity management and access control Significant interest from XML, health IT, and government communities

hData goes Standard To improve quality and adoption, hData pursued standardization – Health Layer 7 (HL7) and Object Management Group (OMG) – Part of Service-Oriented Architecture catalog of standards Realization of Resource Locate and Update Service (RLUS) Functional Model REST Binding established Resource-Oriented Service approach – Limited scope for initial set of standards Packaging and meta-data (HL7) REST Transport and RLUS realization (OMG) Current status: Draft/Beta Standards (Q1CY2012)

Core Specifications

Scoping hData What can hData do? – Uniform way to organize clinical information – Standard metadata annotation – Transport/network API – Normalized way to describe content models What does hData not do? – Provide topical/domain specific content – Offer XML simplification approach

Architecture Focus: Health Data Exchange hData focuses on system-to-system data exchange – There is no architectural requirement on the system itself – hData’s network-facing interfaces are simple and can be “plugged on” existing clinical systems

Architectural Concepts “Service and Resource Oriented” “Disaggregated, but Linked Data” “Uniform Access, Rich Semantics”

“Service and Resource Oriented” hData departs from message/document exchange paradigm Context for exchange is set by service contract, deployment parameters, and exchange – NOT – implicitly within document/message

“Disaggregated, But Linked Data” Allow (but do not require!) small information pieces – Individual allergies, medications, lab results, orders, etc., but allow full CCD or V3 messages – Provide full set of meta-data for each information piece – Offer chronological lists of pieces, sorted by type or by other criteria; subscription to new information Allow complex and semantically rich linking between data – Abstract links or URLs for web based access Visibility of individual pieces – Hide sensitive information; don’t redact – just do not share – Data re-use through simple de-identification and selective sharing

“Uniform Access, Rich Semantics” Uniform data access methods – REST Binding for RLUS defines default effects of GET/PUT/POST/DELETE on record elements Semantics through self-describing structures – “Root.xml” manifest describes high-level structure of actually contained information – RLUS “semantic signifiers” indicate support for data types and content profiles Negotiable resource representation – Device/data consumer selectable wire-level format (XML, JSON, PDF, PNG, DICOM, etc.)

hData in a Nutshell hData enabled System GET resource 2 XML listing of patient documents (metadata and hyperlinks) 1 GET ATOM feed CCD or CCR XML DICOM images Other formats

Integration Points With XD* MIME-centric payload model Meta-data alignment – Initial mapping table on HL7 hData wiki page Hierarchical sectional structure in HRF supports IHE Folders and Submission Sets – Semantics will need to be clearly defined Developing concepts of linked data

BACKUP

Relation to Other HL7 Products (Note: this is not UML)

hData Mobile Architecture 15 There’s a problem with your Blood Sugar! Alert patient or local care provider Cloud Push Compliance ↑ Cost ↓ Clinician views EHR with hData client on iPad or Android device hData hData Server Server polls device for new readings device polls server for updates and alerts hData Monitoring hData Patient Domain App (e.g Diabetes) Bluetooth hHub App Enabler parsing, persistence, and OAuth2 negotiation