This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.

Slides:



Advertisements
Similar presentations
Dipak Kalra, David Lloyd Health Record Information The information in a health record is inherently hierarchical –Clinical observations, reasoning and.
Advertisements

“Designing” an IHIA Health Information Systems; Integration and Interoperability.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Universal Medical Record. What is a medical record –Sources of information –Uses –How is it maintained –What are its component parts Medical Record.
Chapter 5. Describe the purpose, use, key attributes, and functions of major types of clinical information systems used in health care. Define the key.
Definition of Purpose of the Patient Record
New ISO projects Joint meeting HL7, IHE and ISO Pharmacy groups Leonora Grandia, Z-Index.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
Terminology in Health Care and Public Health Settings
Component 10 – Fundamentals of Workflow Process Analysis and Redesign Unit 10 – Process Change Implementation and Evaluation This material was developed.
Unit 11C: Data Quality Attributes Data Quality Improvement This material was developed by Johns Hopkins University, funded by the Department of Health.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Chapter 6 – Data Handling and EPR. Electronic Health Record Systems: Government Initiatives and Public/Private Partnerships EHR is systematic collection.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
Component 11/Unit 8b Data Dictionary Understanding and Development.
Component 2: The Culture of Health Care Unit 9: Sociotechnical Aspects: Clinicians and Technology Lecture 1 This material was developed by Oregon Health.
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
Component 8 Installation and Maintenance of Health IT Systems Unit 1a Elements of a Typical Electronic Health Record System This material was developed.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
Component 3-Terminology in Healthcare and Public Health Settings Unit 17-Clinical Vocabularies This material was developed by The University of Alabama.
Component 6 - Health Management Information Systems
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
Component 3-Terminology in Healthcare and Public Health Settings Unit 16-Definitions and Concepts in the EHR This material was developed by The University.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Unit 2 Part 2: “Under the Hood” Component 7 – Working with HIT Systems This material was developed by Johns Hopkins University, funded by the Department.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Component 3-Terminology in Healthcare and Public Health Settings Unit 14-What is Health Information Management and Technology? This material was developed.
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
Terminology in Health Care and Public Health Settings Unit 14 What is Health Information Management and Technology?
Data Quality Improvement This material was developed by Johns Hopkins University, funded by the Department of Health and Human Services, Office of the.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
Component 6 - Health Management Information Systems Unit 9-2 Administrative, Billing, and Financial Systems This material was developed by Duke University,
Object storage and object interoperability
The Culture of Healthcare Healthcare Processes and Decision Making Lecture a This material (Comp2_Unit4a) was developed by Oregon Health & Science University,
CCD and CCR Executive Summary Jacob Reider, MD Medical Director, Allscripts.
Terminology in Healthcare and Public Health Settings Electronic Health Records Lecture b – Definitions and Concepts in the EHR This material Comp3_Unit15.
Component 6- Health Management Information Systems Unit 5-2 Clinical Decision Support Systems This material was developed by Duke University, funded by.
Health Management Information Systems Clinical Decision Support Systems Lecture b This material Comp6_Unit5b was developed by Duke University, funded by.
Chapter 4: The Patient Record: Hospital, Physician Office, and Alternate Care Settings.
Chapter 4: The Patient Record: Hospital, Physician Office, and Alternate Care Settings.
Health Management Information Systems Health Information Systems Overview Lecture a This material Comp6_Unit2a was developed by Duke University, funded.
Fundamentals of Health Workflow Process Analysis and Redesign Process Analysis Lecture a This material Comp10_Unit5a was developed by Duke University,
Health Informatics Awareness Planned DayTopicPlanned Time Day 1 22/7/ Course introduction & pre course survey 2.Pre evaluation test 3.Introduction.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Health Management Information Systems Electronic Health Records Lecture b This material Comp6_Unit3b was developed by Duke University, funded by the Department.
Health Management Information Systems What is Health Informatics? Lecture a This material Comp6_Unit1 was developed by Duke University, funded by the Department.
History of Health Information Technology in the U.S. The HITECH Act Lecture b – Meaningful Use, Health Information Exchange and Research This material.
Component 6 - Health Management Information Systems Unit 2-1b - Hardware and Software Supporting Health Information Systems.
Networking and Health Information Exchange
Networking and Health Information Exchange
Component 11 Configuring EHRs
WP1: D 1.3 Standards Framework Status June 25, 2015
Abstract descriptions of systems whose requirements are being analysed
Networking and Health Information Exchange
Electronic Health Information Systems
Component 11 Unit 7: Building Order Sets
Presentation transcript:

This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC Component 9 - Networking and Health Information Exchange Unit 6-1 EHR Functional Model Standards

Unit Objectives Understand the definition(s) of an Electronic Health Record Understand architecture for an EHR Identify and understand key standards for the EHR Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

What is an EHR? Many definitions – why? What is its form and format? What is its purpose? Who is it for? Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

What is an EHR? Also Known As: –Automated Medical Record –Computerized Medical Record –Computer-Based Medical Record –Electronic Medical Record –Electronic Health Record It’s not a: –Data Warehouse –Clinical Data Repository –Disease Registry Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

Institute of Medicine (IOM) Definition (1991, 1997) The patient record is: principal repository for data concerning a patient’s health care affects virtually everyone associated with providing, receiving, auditing, regulating or reimbursing health care services Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

IOM Definition (1991, 1997) "A computer-based patient record is an electronic patient record that resides in a system specifically designed to support users by providing accessibility to complete and accurate data, alerts, reminders, clinical decision support systems, links to medical knowledge, and other aids." Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

Expanding the Definition Different groups have expanded on these earlier definitions of the EHR Groups include ISO, CEN, IOM, ASTM, and others Common understanding is important for sharing and aggregating of clinical data Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO EHR Standards ISO TR –EHR Definition, Scope and Context ISO TS –Requirements for an Electronic Health Record Reference Architecture ISO IS –EHR Communication- Part 1: Reference Model Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO TR Describes a pragmatic classification of electronic health records Provides simple definitions for the main categories of EHR Provides supporting descriptions of the characteristics of EHRs and record systems Defines the set of components that form the mechanism by which patient records are created, used, stored, and retrieved Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

EHR Architecture A model of the generic features necessary in any EHR in order that the record may be communicable, complete, a useful and effective ethical-legal record of care, and may maintain integrity across systems, countries and time The architecture does not prescribe or dictate what anyone stores in their health records –Nor does it prescribe or dictate how any EHR system is implemented –It places no restrictions on the types of data which can appear in the record, including those which have no counterpart in paper records Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO TS Scope "Assemble and collate a set of clinical and technical requirements for an electronic health record reference architecture that supports using, sharing, and exchanging electronic health records across different health sectors, different countries, and different models for health care delivery." Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO TS Scope Does not define functional requirements for an EHR System Rather “… a set of clinical and technical requirements for a record architecture that supports using, sharing, and exchanging electronic health records across different health sectors, different countries, and different models for health care delivery.” Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO Considers the EHR to be the persistent longitudinal and multi- enterprise record of health and care provision relating to a single subject of care, created and stored in one or more physical systems in order to inform the subject’s future health care and to provide a medico-legal record of care that has been provided. Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO Goal: –Define a rigorous and stable information architecture for communicating part or all of the EHR of a single subject of care –Preserve original clinical meaning intended by author –Reflect the confidentiality of that data as intended by the author and patient Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO Not intended to specify internal architecture or database design Supports a dual model approach –Reference model – represents the generic properties of health record information –Archetype Model – a formal expression of a distinct, domain-level concept, expressed in the form of constraints on data whose instances conform to the reference model Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO Assumes a hierarchical structure as base for EHR architecture Top level is an EHR Extract that can contain part or all of an EHR Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO Hierarchical Structure EHR EXTRACT – is a hierarchy of folders FOLDER – contains compositions –Compartment relating to care provider for a single condition over a fixed period of time COMPOSITION – contains nested sections –Set of information committed to EHR by one agent as a result of single encounter Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ISO Hierarchical Structure Section –Contains entries –Data under one clinical heading Such as lab data Entry –Contains elements and clusters –Result of one observation Cluster –Contains elements –Means of organizing nested data structures Such as a time series Element –Leaf node containing a single data value Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ASTM EHR Standards E 1239 Standard Guide for Description of Reservation/Registration-Admission, Discharge, Transfer (R-ADT) Systems for Automated Patient Care Information Systems E 1384 Standard Guide for Content and Structure of the Electronic Health Record E 1633 Standard Specification for the Coded Values Used in the Electronic Health Record Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ASTM EHR Standards E 1715 Standard Practice for an Object- Oriented Model for Registration, Admitting, Discharge, and Transfer (R-ADT) Functions in Computer Based Patient Record Systems E 1744 Standard Guide for a View of Emergency Medical Care in the Computerized Patient Record Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

ASTM E 1769 Defines functions for an EHR Addresses reminders and alerts Addresses authorized use of EHR Discusses multiple uses of EHR Discusses protection of data in EHR Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring

Summary Component 9/Unit 6-1Health IT Workforce Curriculum Version 2.0/Spring In this subunit, we have: Drawn attention to several standards from various SDOs that deal with EHR definition, architecture and content None of these standards are complete and definitive Unfortunately, the current state of the art for EHRs is similar to the story of five blind men and the elephant Until a stronger agreement is reached, content interoperability, efficiency, and query will be compromised We are unlikely to ever have a single standard for an EHR architecture The reasons include: Lack of agreement among developers The proprietary nature of the architectural design Legacy systems Many other reasons