We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byMalcolm Clinton Alexander
Modified about 1 year ago
© Thomas Beale 2010 Thomas Beale openEHR Services architecture
© Thomas Beale 2011 The Services Part
© Thomas Beale 2011 Enterprise Comprehensive Basic Old view… EHR Multimedia genetics workflow identity Clinical ref data Clinical models terms Security / access control realtime gateway telemedicine HILS other provider UPDATE QUERY demographics guidelines protocols Interactions DS Local modelling notifications DSSPAS billing portal Allied health patient PAYER Msg gateway Imaging lab ECG etc Path lab LAB Secondary users Online drug, Interactions DB Online archetypes Online terminology Online Demographic registries Patient Record
© Thomas Beale 2011 General approach Build from bottom up – ‘Native’ services Needed services, consistent with information and model artefacts And from top-down – ‘Standard’ services Connect IHE, HSSP etc to native services
© Thomas Beale 2011 Services IHEIHE se tsts terminology f rere data java C# etc Querying HSSPHSSP NativeNative
© Thomas Beale 2011 On Services... Some architectural inspiration from Microsoft Connected Health Framework (CHF) Native layer Take as much of IHE, HSSP etc interfaces & adapt for native compatibility, making archetype-aware Standards layer Service – service connection
© Thomas Beale 2011 ProcessModels Service Models Information Models Microsoft CHF
© Thomas Beale 2011 EHR Service demographics Security & privacy Workflow & Pathway Services
© Thomas Beale 2011 The openEHR services architecture http://www.openehr.org/wiki/display/spec/openEHR+Service+Model
© Thomas Beale 2011 Native services All services archetype/template aware Numerous APIs generated from templates Query service based on AQL / a-path No SQL queries against physical database!!!
© Thomas Beale 2011 Key data services - EHR ARCHETYPE-AWARE Virtual EHR – fine-grained creation, modification, retrieval, querying EHR back-end – coarse-grained DVCS-like interface – ‘change-set’ based EHR audit log
© Thomas Beale 2011 Key data services - patient Demographics – ARCHETYPE-AWARE Authentication info Patient relationships HCP relationships – teams etc EHR subject X-ref service openEHR EHRs are identified by EHR id only Deals with merged & split EHRs, i.e. 2 subject ids 1 EHR, 2 EHR ids 1 subject Enables dynamic distribution of EHRs Becoming the EHR meta-data service
© Thomas Beale 2011 Key knowledge services Archetypes & templates Terminology ref-sets Terminology service access Inferencing Terminology administration Medications, devices Allergies & interactions database
© Thomas Beale 2011 Key process services Event-based notifications Care pathway Based on archetyped openEHR structures Booking / appointments Requires access to patient requests & doctor’s diary & other resource availability data Doctor’s diary Forces syncing of appointments to filler Patient diary Allows multi-function visits
© Thomas Beale 2011 Key elements that MUST WORK Standardised querying of data, based on knowledge artefacts, not physical DB standardised knowledge artefact identification, including versions standardised ability to designate finest grain items in the data Enabling URI to any data item
© Thomas Beale 2011 Services lessons Need native and standard layers, i.e. Inside-out, outside-in Knowledge-based architecture brings new needs: New knowledge services – archetypes, ref-sets Other services must be knowledge-aware Business services need to be small, with changeable interfaces
© Thomas Beale 2011 Knowledge awareness means... Service layer understands: knowledge artefact identification system Fine-grained data item identification Which means we need standardised knowledge models Aka Detailed Clinical Models
© Thomas Beale 2010 Thomas Beale openEHR Architecture Overview.
Limning the CTS Ontology Landscape Barry Smith 1.
1 Standards and Ontology Barry Smith
1.View Description 2.Primary Presentation 3.Element Catalog Elements and Their Properties Relations and Their Properties Element Interfaces Element Behavior.
© Thomas Beale 2010 Thomas Beale, July © Thomas Beale 2010 The Archetype framework.
Initial slides for Layered Service Architecture From existing materials: Practical Guide to SOA in Healthcare Part II IHE SOA Whitepaper.
ONC JASON report hearing 31 July 2014 Thomas Beale - openEHR Foundation.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
Cath Workflow Manage multimodality synchronized procedure from admission to lab discharge including unidentified patients Echo Workflow Manage echocardiography.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
The electronic patient record. The patient record Notes made by physician Long history.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing Charles PARISOT GE Healthcare.
METU-SRDCEUROREC Meeting, Geneva, October 10, 2006 RIDE Overview Asuman Dogac Middle East Technical University Ankara, Turkey.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
1 Charles Parisot, GE Healthcare IHE IT Infrastructure Planning Committee Co-chair IHE Update to DICOM.
MEDIQ EuroRec’s First Draft List of EHR Certification Criteria Knut Bernstein MEDIQ
Component overview template. Client Registry (CR) Business function: the CR identifies the same patient across different health settings so that clinical.
© 2005 IBM Corporation IBM Global Business Services 4/10/2006 | Casey Webster and Kevin Julier © 2006 IBM Corporation IBM NHIN Architecture Leveraging.
IHE IT Infrastructure Domain Update Karen Witting – IBM IT Infrastructure Technical Committee co-chair.
Document Registry Framework Il Kon Kim, PhD & Il Kwang Kim PhD Kyungpook National Univ. IHIS, © Copyright, 2006, IHIS. Total Health Care.
1st Workshop on Intelligent and Knowledge oriented Technologies Universal Semantic Knowledge Middleware Marek Paralič,
What IHE Delivers Healthcare Provider Directories IHE IT Infrastructure Planning Committee Eric Heflin - Medicity.
Infrastructure for Electronic Government, An Overview Adegboyega Ojo and Tomasz Janowski UNU-IIST.
IBM Rhapsody Simulation of Distributed PACS and DIR systems Krupa Kuriakose, MASc Candidate.
What IHE Delivers Healthcare Provider Directories IHE IT Infrastructure Planning Committee Eric Heflin – Medicity/THSA.
IHE Update IT Infrastructure, Radiology, Laboratory and Cardiology IHE Update to December 2003 DICOM Committee Charles Parisot, GE Medical Systems Information.
Aligning Health Information Standards Development with the National eHealth Agenda HEALTH INFORMATION MANAGEMENT ASSOCIATION OF AUSTRALIA LIMITED 26 September.
September, 2005What IHE Delivers 1 An Overview of the IHE IT Infrastructure IHE Vendors Workshop 2006 IHE IT Infrastructure Education Glen F. Marshall.
FHIRframe Concept Definition v.07 Note: This is a preliminary discussion.
Solutions for Multi Discipline Healthcare Practice.
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
OpenEHR The Reference Model Thomas Beale Sam Heard.
L SERVICE DELIVERY Pharmacy Public Health Provider Interoperability Services Data Interchange Legacy System Adapters Simulator Health Service Bus Infrastructure.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
Sandy Lum University of Toronto Candidate MHSc in Clinical Engineering The Totally Integrated Electronic Patient Record (EPR)
Massachusetts: Transforming the Healthcare Economy John D. Halamka MD CIO, Harvard Medical School and Beth Israel Deaconess Medical Center.
IHE IT Infrastructure Domain Update Karen Witting – IBM IT Infrastructure Planning Committee co- chair.
NextGen Interoperability – Leading the Charge Presenter – David Venier DISCLAIMER: The views and opinions expressed in this presentation are those of the.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
© 2003 East Collaborative e ast COLLABORATIVE ® eC SoftwareProducts TrackeCHealth.
A Primer on Healthcare Information Exchange John D. Halamka MD CIO, Harvard Medical School and Beth Israel Deaconess Medical Center.
Implementing the XDS Infrastructure Bill Majurski IT Infrastructure National Institute of Standards and Technology.
The Evolution of the Referral Process. Mike Reagin Director of Research and Development Providence Health System Portland,
Lab 301 Populating Template Data from a Third Party Data Source Justin Pava, Software Release Manager Andrew Schoonmaker, Software QA Engineer.
ISO/IEC MFI-4 Extended Registry Masaharu Obayashi SC32/WG
Integrating the Healthcare Enterprise Title of Presentation Name of Presenter IHE affiliation.
© 2017 SlidePlayer.com Inc. All rights reserved.