EHR Definition, Scope & Context. Sam Heard for Peter Schloeffel ISO/TC 215 WG1 Aarhus, Denmark 3 Oct 2003

Similar documents
ISO/TC 215 Technical Report. Electronic Health Record Definition, Scope, and Context. Second Draft, August 2003

ISO/TR TECHNICAL REPORT. Health informatics Electronic health record Definition, scope and context

The ERS IC-EHR as Local, Regional and National ehealth Infrastructure July 2010

Health Information and Quality Authority. To drive continuous improvements in the quality and safety of health and social care in Ireland

ehealth, HIS, etc ehealth All information about health HMIS mhealth HIS Statistical IS Credited: Karl Brown, Rockefeller Foundation

Semantic Interoperability in electronic health record: a standardised approach. Ruibin Ye

EHR Standards Landscape

ERS EN Product & Services Suite an elevator pitch

EHR vs CCR: What is the difference between the electronic health record and the continuity of care record?

Electronic Health Record (EHR) Standards Survey

Integration Information Model

ELECTRONIC RECORDS - DEFINITION

CEN/tc251 EN EHRcom European and National EHR standard has been published on 28 February 2007

Il lavoro di armonizzazione. e HL7

Open Source Modular Units for Electronic Patient Records. Hari Kusnanto Faculty of Medicine, Gadjah Mada University

Addressing the State of the Electronic Health Record (EHR)

A Metabolic Syndrome Health Check EHR based on openehr

openehr The Reference Model Thomas Beale Sam Heard

ISO INTERNATIONAL STANDARD. Health informatics Requirements for an electronic health record architecture

EHR Systems: an Introduction

Defining the content of shared electronic medical records (emr)

8th Medical Open Source Software Symposium

EHR Archetypes in practice: getting feedback from clinicians and the role of EuroRec

Comparing Different Approaches to Two-Level Modelling of Electronic Health Records

Towards a Repository for Managing Archetypes for Electronic Health Records

ERS. Boundaries between structuring applications and messaging. Trondheim. Tuesday 21 September Electronic Record Services B.V.

Evaluation of a Persistent Store for openehr

How To Write An Electronic Health Record

How To Understand The Difference Between Terminology And Ontology

Private Circulation Document: IST/35_07_0075

Architecture Overview

The next generation EHR

Relationship of HL7 EHR System Draft Standard to X12N

Integration of Distributed Healthcare Records: Publishing Legacy Data as XML Documents Compliant with CEN/TC251 ENV13606

EHR Introduction for the Practicing Physician

Archetype-Based Knowledge Management for Semantic Interoperability of Electronic Health Records

Overview of ehr Development. Slide - 1

e-consent design and implementation issues for health information managers

Electronic Health Record Systems and Secondary Data Use

Report on a preliminary analysis of the dataflow(s) in HealthConnect system

EHR Standards and Semantic Interoperability

The Journal on Information Technology in Healthcare 2003; 1(5): Archetypes, GEHR, openehr and Electronic Health Records

ProRec QREC Workshop 2011 Nicosia, 24 March 2011

Techniques for ensuring interoperability in an Electronic health Record

HL7 EHR System Functional Model: A Major Development Towards Consensus on Electronic Health Record System Functionality

QUESTIONS AND ANSWERS HEALTHCARE IDENTIFIERS BILL 2010

Standards and their role in Healthcare ICT Strategy. 10th Annual Public Sector IT Conference

Component 6 - Health Management Information Systems. Objectives. Purpose of a Patient (medical) Record. Unit 3-1 Electronic Health Records

BI en Salud: Registro de Salud Electrónico, Estado del Arte!

Object-relational EH databases

National Integrated Services Framework The Foundation for Future e-health Connectivity. Peter Connolly HSE May 2013

2009 Progress in Comprehensive Care for Rare Blood Disorders Conference

Priorities and strategies for successful EHR adoption

The EHR and Clinical Archetypes: time for clinical engagement!

Analysis of International EHR Systems

HL7 and SOA Based Distributed Electronic Patient Record Architecture Using Open EMR

Socio-economic benefits of interoperable electronic health record systems in Europe the evidence -

Management and maintenance policies for EHR interoperability resources

CMS & ehr - An Update

Advanced Aspects of Hospital Information Systems

Applying Standards in Cross-sector Communication for an Integrated Health Environment

HL7 CDA, Clinical Modelling and openehr

Templates and Archetypes: how do we know what we are talking about?

Information Governance. A Clinician s Guide to Record Standards Part 1: Why standardise the structure and content of medical records?

Clinical Knowledge Manager. Product Description 2012 MAKING HEALTH COMPUTE

HL7 EHR System Functional Model and Standard (ISO/HL ), Release 2

Health Information Technology: A Key Component of Health Reform

HIT Standards Committee Transitional Vocabulary Task Force Wednesday October 14th, 2015, 10:30 A.M. 12:00 P.M. Et

Health Informatics Standardisation - educational, informative and normative

Table of Contents. Preface CPSA Position How EMRs and Alberta Netcare are Changing Practice Evolving Standards of Care...

Opportunities and challenges for public health surveillance: a new world of interoperability with electronic health records

European Quality Labelling, Certification, Electronic Health Record systems (EHRs) gf v1

Standardization of the Australian Medical Data Exchange Model. Michael Legg PhD

EMR and ehr Together for patients and providers. ehealth Conference October 3-4, 2014

TOWARD A FRAMEWORK FOR DATA QUALITY IN ELECTRONIC HEALTH RECORD

The Role of SOA in the Nationwide Health Information Network: An Update

Health Record Banking Alliance

What s next for openehr. Sam Heard Thomas Beale

Role of Health Plans It s Time to Get out of the Sandbox Health Record Enablement

Advanced and secure architectural EHR approaches

NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0

This document is a preview generated by EVS

The Big Picture: IDNT in Electronic Records Glossary

The Electronic Health Record: What is it's potential for enabling health?

DISCUSSION PAPER ON SEMANTIC AND TECHNICAL INTEROPERABILITY. Proposed by the ehealth Governance Initiative Date: October 22 nd, 2012

Accelerating EMR Interoperability with ELINCS. Streamlining Lab Connectivity to Physician EMRs

Report of the secretariat. CEN/TC 251 secretariat ACTION REQUIRED: For your information

Healthcare Provider Directories. Eric Heflin, CTO/CIO Healtheway & CTO HIETexas

Draft Pan-Canadian Primary Health Care Electronic Medical Record Content Standard, Version 2.0 (PHC EMR CS) Frequently Asked Questions

ISO/HL EHR System Functional Model Standard

What do clinical data standards mean for clinicians? Dr Nick Booth GP and Informatician, Warden, Northumberland, UK

Introduction to openehr Archetypes & Templates. Dr Ian McNicoll Dr Heather Leslie

HYBRID ELECTRONIC HEALTH RECORDS

In ediscovery and Litigation Support Repositories MPeterson, June 2009

Health informatics HL7 Electronic health record system functional model, release 1

Improving EHR Semantic Interoperability Future Vision and Challenges

Achieving meaningful use of healthcare information technology

AN OVERVIEW OF INTEROPERABILITY STANDARDS FOR ELECTRONIC HEALTH RECORDS

The Six A s. for Population Health Management. Suzanne Cogan, VP North American Sales, Orion Health

HIMSS Interoperability Showcase 2011

Transcription:

EHR Definition, Scope & Context Sam Heard for Peter Schloeffel ISO/TC 215 WG1 Aarhus, Denmark 3 Oct 2003

2 Agenda Background to the project A taxonomy and definitions of the EHR Scope of the EHR Context of the EHR EHR systems

Defining the EHR

4 Project background, status & future Project initiated, Melbourne Aug 2002 Discussion paper Oct 2002 Working meeting, San Diego Feb 2003 Joint WG session, Oslo May 2003 1 st draft Technical Report, Jul 2003 Working meeting, Sydney Jul 2003 2 nd draft Technical Report, Sep 2003 TR review, ISO WG meeting, Denmark Oct 2003 3 rd (?final) draft Technical Report, Mar 2003 TR review, ISO plenary meeting, May 2004

5 Purpose of the health record Primary (direct) purposes to benefit the patient through support of current and future healthcare needs Any other purpose for which the EHR is used is considered secondary, as is any other beneficiary. Secondary (indirect/derived/supporting) purposes medico-legal, public & population health, quality management, education, research, policy development, health service management, billing etc.

6 Draft ISO EHR definition, Feb 2003 a longitudinal collection of personal health information concerning a single individual, entered or accepted by healthcare providers, and stored electronically. The information is organised primarily to support continuing, efficient, and quality health care and is stored and transmitted securely. The EHR contains information which is: 1. retrospective: an historical view of health status and interventions; 2. concurrent: a now view of health status and active interventions; and 3. prospective: a future view of planned activities and interventions Draft ISO EHR Definition, Feb 2003

7 Oslo meeting highlights Most of the 3 hour session spent discussing the definition Two main opinion groups on the definition 1. Broadly accepted Feb 03 draft definition structure and content but much discussion about refinement of the definition 2. Questioned the fundamental nature of the draft and generally advocated a much shorter and more generic definition Scope and context discussed only indirectly in relation to the definition

8 Inputs to definition post Oslo All Oslo meeting attendees invited to submit new draft definitions but five people targeted Contributors were encouraged to think outside the square and question both the structure and content of the draft definition Eight draft definitions were received These demonstrate a wide variety of approaches to defining the EHR and the difficulty of encompassing all of the many and varied facets of an EHR in a single definition

9 Towards a new draft definition Several contributors stressed the importance of making a clear distinction between the content of the EHR and its form and structure. Others noted that technical definitions should wherever possible be precise and succinct. This is particularly true of ISO definitions which may be the subject of jurisdictional legal interpretation. It therefore seems prudent to propose a minimalist core definition for the EHR and to elucidate the various functional, temporal, and content related aspects of the EHR through supplementary definitions and/or text.

A taxonomy of EHRs

11 Simple EHR taxonomy EHR Shareable EHR Non-shareable EHR Integrated Care EHR

12 Requirements for interoperability Standardised Logical EHR Reference Model Semantics of EHR management Standardised Service Models Semantics of interface to EHR service Standardised Archetypes and Templates Definitions of compound domain concepts Standardised Terminology The language of health

13 Standards and the EHR What Clinical information About whom By whom When Currency Universal acceptor Standard Reference model

14 Standards and the EHR What Read based on reference model Standard Clinical queries information expressed in terms of archetypes Service models Shared Archetypes Standard Reference model

15 EHR top-level definition A repository of information regarding the health of a subject of care, in computer processable form

16 Notes on the proposed definition The proposed ISO top-level EHR definition: Makes no assumptions about the healthcare system of any country or region Makes no assumptions about the type or granularity of information in the record Is broadly applicable to all healthcare sectors, healthcare disciplines and methods of healthcare delivery Subject of care is synonymous with patient and consumer Subject of care may be more than one individual

17 Shareable EHR definition An EHR with a standardised information model which is independent of EHR systems and accessible by multiple authorised users and user applications 3 additional attributes added to this defn: A standardised information model enables independence from EHR systems Security of information both when stored and transmitted An EHR accessible by multiple authorised users (and only by these authorised users)

18 Integrated Care EHR definition Short form: A Shareable EHR whose primary purpose is the support of continuing, efficient and quality integrated healthcare. The ICEHR contains information which is retrospective, concurrent and prospective. Long form: a repository of information regarding the health of a subject of care in computer processable form, stored and transmitted securely, and accessible by multiple authorised users. The ICEHR has a standardised information model which is independent of EHR systems. Its primary purpose is the support of continuing, efficient and quality integrated healthcare and it contains information which is retrospective, concurrent and prospective.

19 Other types of health records Electronic Medical Record (EMR)* Electronic Patient Record (EPR)* Computerized Patient Record (CPR)* Electronic Health Care Record (EHCR)* Virtual EHR* Personal Health Record (PHR)* Digital Medical Record (DMR)* Computerised Medical Record (CMR) Population Health Record * Conform to proposed ISO EHR definition

20 The Personal Health Record Waegemann describes five types Widespread misapprehension that PHR must be different entity from the EHR if it is to meet the needs of patients/consumers PHR should have the same architecture as the SEHR and ICEHR to enable sharing of information between them, as and when appropriate, under the control of the consumer/patient

21 The Personal Health Record (2) At least 4 different forms of PHR: 1. A self-contained EHR, maintained & controlled by the consumer/patient 2. Same as 1 but maintained by third party such as a web service provider 3. A component of a SEHR/ICEHR maintained by a healthcare provider (e.g. a GP) and controlled at least partially by the consumer/patient 4. Same as 3 but maintained and controlled completely by the patient/consumer

Scope of the EHR

23 Range of views on scope There are currently two broadly different views on the scope of the EHR: The Core EHR ( Small EHR ) The Extended EHR ( All EHR )

24 The Core EHR Key characteristics: Concerns a single subject of care Primary purpose is the support of present and future healthcare of the subject Principally concerned with clinical information simplifies standardisation of the EHR has a clear, limited scope enabling a manageable set of requirements to be specified and a manageable standardised model to be defined Fits more closely with the distributed systems or system-of-systems paradigm Allows more modular health information systems to be built

25 The Extended EHR Includes not only clinical information but essentially the whole health information landscape It is a superset of the Core EHR Extended EHR functions beyond the scope of the Core EHR include: Patient administration Scheduling and resource allocation Billing Decision support Access control and policy management Demographics Order management Terminology Population health recording, querying, and analysis Health professional recording, querying, and analysis Business operations recording, querying, and analysis

26 Active Facilitator vs Passive Repository Active Facilitator EHR Actively manages the healthcare delivery process Incorporates real-time decision support and other functions such as workflow management, resource management, scheduling, costing etc Passive Repository EHR Acts as the central data store and accepts multiple information feeds from front-end application systems

Scope attribute Core EHR Extended EHR Focus Relationship to each other Relationship to purposes of the EHR Relationship to ISO 18308 EHR requirements Modelling paradigm Approach for standardisation Active Facilitator EHR vs Passive Repository EHR Relationship to information and knowledge principally clinical information subset of Extended EHR principally concerned with primary purpose defines the scope small model which interfaces to many similar models for other services in a distributed systems environment separate standard for Core EHR and each other service in the health information landscape (layered approach) Passive Repository contains only information the whole health information landscape superset of Core EHR concerned with both primary and secondary purposes many of the Extended EHR requirements beyond the scope of the 18308 EHR Reference Architecture large model which defines the whole health information landscape single multi-part standard for all services Active Facilitator may contain information and knowledge

The EHR healthcare context

29 The EHR healthcare context The content and granularity of an EHR may vary widely between different: Healthcare paradigms (Allopathic, Social, Chinese) Healthcare systems (funding and access models) Healthcare sectors (hospitals, GPs, rehab clinics) Healthcare settings (ED, office, OR, battlefield, home) Healthcare disciplines (doctor, nurse, social worker) Healthcare discipline within sector (nursing, physio, physician entries in an ICU EHR)

30 The temporal context What do we mean by longitudinal? involving information about an individual or group gathered over a prolonged period COD A 24 hour ICU admission? A single encounter in an ED? A road-side Good Samaritan act? lifetime, before birth to after death definitely yes The proposed EHR definitions and a single standardised Reference Information Model will cover both extremes

Context of the EHR in health information space

Distributed health information landscape 32

EHR systems

34 The functional dimension of the EHR EHR functional requirements or functional specification relates to EHR systems, not to the EHR per se. Function: activity proper to anything, mode of action by which it fulfils its purpose COD EHR system: the set of components that form the mechanism by which electronic health records are created, stored, and retrieved. It includes people, data, rules and procedures, processing and storage devices, and communication and support facilities IOM EHR system: a system for recording, retrieving, and manipulating information in electronic health records CEN ENV 13606-1, modified

35 Types of EHR systems Local EHR systems Systems architecture can be (needs to be) highly variable to meet the needs of different healthcare sectors and disciplines (e.g. large hospital, family GP clinic, community nursing) Shared EHR systems Two main systems architecture models: the federated database model the consolidated EHR model EHR Directory Service systems Systems architecture can be essentially the same as for any distributed directory service system

A multi-layer Shared EHR strategy Wide-area access Meta-data items (EHR Index) Ad Hoc secure Shared-care ICEHR Longitudinal additional indexing? Patientcentred secure Shared-care Patientcentred ICEHR Longitudinal Patientcentred Care Delivery EPR EPR EPR EPR Slide courtesy Thomas Beale

EHR system characteristics EHR system type Local-EHR system Shared-EHR system EHR Directory Service Scope and purpose Individual local healthcare providers Local care communities Regional or national National Trans-national Type of EHR Non-shareable EHR SEHR/ICEHR SEHR/ICEHR Index to SEHR or ICEHR Type of data Detailed local data Shared data Meta-data index Granularity of data Fine Course (summary) N/A Contributors and access to EHR* Local healthcare providers Local care community or extended community (regional/national) N/A** Custodian/maintainer Health Care Facility (Hospital, GP clinic etc) Local health authority, HMO, GP custodian etc Public health departments or similar

38 Thank you www.openehr.org