© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.

Slides:



Advertisements
Similar presentations
PH Reporting Health IT Standardization Framework Proposal for Review S&I PH Reporting Initiative-Call 10/12.
Advertisements

Consolidation Communicable Diseases User Stories: Meeting Agenda 1.News from other domains 2.Recap of a previous meeting 3.Consolidation of three more.
HL7 EHR-S FM Child Health Functional Profile Project Overview HL7 Pediatric Data Standards Special Interest Group April 2007.
1 HL7 Educational Session – eHealth Week Budapest 2011 © Health Level Seven International, Inc. All Rights Reserved. HL7 and Health Level Seven.
© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
1 © Health Level Seven International ®, Inc. All Rights Reserved. HL7 International and Health Level Seven International are registered trademarks.
© 2013 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
Cross-Jurisdictional Immunization Data Exchange Project Updated 4/29/14.
© 2013 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
HL7 Standards Strategic and Tactical Use Charlie McCay
Hetty Khan Health Informatics Scientist Centers for Disease Control and Prevention (CDC) National Center for Health Statistics (NCHS) August 7, 2012 Developing.
Use Case 16 Care Theme: Maternal & Newborn Health Use Case: Vital Registration and Care Coordination for Newborn Hearing Screening Primary Goal: Demonstrates.
1 © Health Level Seven International ®, Inc. All Rights Reserved. HL7 International and Health Level Seven International are registered trademarks.
Meaningful Use Measures. Reporting Time Periods Reporting Period for 1 st year of MU (Stage 1) 90 consecutive days within the calendar year Reporting.
Initial slides for Layered Service Architecture
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
NAPHSIS Annual Meeting 2009 Electronic Health Records: Why are they important? Linette T Scott, MD, MPH Deputy Director Health Information and Strategic.
WHY is EHDI a part of the HIT conversation A first encounter between providers and public health As an encounter, communication becomes essential Communication.
1 May 2010 © Health Level Seven International®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level.
Public Health Data Standards Consortium
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Development of HL7 Standards for Vital Records NCHS/NAPHSIS Annual Meeting June 3, 2009 Hetty Khan, RN, MS, MGA Michelle Williamson, RN, MS Health Informatics.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Proposed S&I Public Health Reporting Initiative 1 Challenge There is a lack of harmonized activities to enable electronic data exchange between clinical.
Interoperability Showcase In collaboration with IHE Use Case 3 Care Theme: Leveraging National Healthcare Registries in Care Delivery Biosurveillance Monitoring.
Chapter 2 Standards for Electronic Health Records McGraw-Hill/Irwin Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved.
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.
Understanding the Vital Records Functional Profile (VRFP) Hetty Khan Health Informatics Specialist Centers for Disease Control and Prevention National.
HL7 Child Health Work Group Update HL7 EHR-Public Health Task Force Andy Spooner, MD CMIO, Cincinnati Children’s Hospital & Medical Center Co Chair, HL7.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Public Health Data Standards Consortium
Us Case 5 Vital Registration and Care Coordination for Newborn Hearing Screening Care Theme: Maternal & Newborn Health Use Case 16 Interoperability Showcase.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
Hetty Khan Health Informatics Scientist Centers for Disease Control and Prevention (CDC) National Center for Health Statistics (NCHS) September 5, 2012.
Public Health Data Standards Consortium
HL7 Electronic Health Record System (EHR-S) Public Health Functional Profile (PHFP) Project PHDSC Annual Business Meeting November 8, 2012 Hetty Khan Health.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Quality, Research and Public Health (QRPH) Domain HIMSS 2009 Interoperability Showcase Planning Co-Chairs: - Ana Estelrich, GIP-DMP - Ana Estelrich, GIP-DMP.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Public Health Data Standards Consortium
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Public Health Reporting Initiative January 4, 2012.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Primary Goal: To support case detection and investigation for the reportable infectious diseases (conditions) using electronic information exchanges between.
Voting on the Public Health Functional Profile Michelle Williamson Senior Health Informatics Scientist PHDSC Webinar: HL7 EHR-S Public Health Functional.
PEHR ChartChart Claims Data Breadth and Depth Population Quality Measures.
Electronic Health Record (EHR) and Vital Record (VR) Systems Information Exchange National Center for Health Statistics Classifications and Public Health.
SAGE Nick Beard Vice President, IDX Systems Corp..
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill/Irwin Chapter 2 Clinical Information Standards – Unit 3 seminar Electronic.
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
Chapter 15 by Emily B. Barey The Electronic Health Record and Clinical Informatics.
IHE Quality, Research and Public Health QRPH domain
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS.3.9 Clinical Decision Support System Guidelines Updates aka S
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.3 Manage Medication List aka DC in EHR-S FM
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS Manage Patient Advance Directives aka DC in EHR-S.
EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S in EHR-S FM R1.1
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.6.2 Manage Immunization Administration aka DC in EHR-S FM.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.3.3 Manage Clinical Documents and Notes aka DC in EHR-S FM.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List aka DC
Health Information Exchange Interoperability
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS Manage Patient Advance Directives aka DC in EHR-S.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.6 Manage Immunization List aka DC in EHR-S FM R1.1
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) AS.4.1 Manage Registry Communication aka S.1.1 in EHR-S FM R1.1
Objectives Describe the purposes of the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009 Explore how the HITECH Act.
Presentation transcript:

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Public Health Functional Profile of the HL7 EHR System Functional Model and Standard Brief background April 25, 2011 Presented by: John Ritter HL7 EHR Work Group Co-chair

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Adding to the list of Functional Profiles…. Functional Profiles:  EHR-System Records Management and Evidentiary Support  PHR-to-EHR Health Information Exchange  Long Term Care / Nursing Home  Child Health  Behavioral Health  Emergency Department  Clinical Research  Vital Records (Birth and Death Records)  Public Health Functional Profiles: Early Hearing Detection and Intervention Chronic Diseases and Cancer Surveillance (others coming….)

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Overview of the EHR-S FM Standard The EHR-S FM consists of three parts: Direct Care  Doctor places a healing hand on the patient Supportive  Helps the doctor place a healing hand on the patient Information Infrastructure  Provides infrastructure for Direct Care and Supportive

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Direct Care DC.1Care Management DC.2Clinical Decision Support DC.3Operations Management and Communication Supportive S.1Clinical Support S.2Measurement, Analysis, Research and Reports S.3Administrative and Financial Information Infrastructure IN.1Security IN.2Health Record Information and Management IN.3Registry and Directory Services IN.4Standard Terminologies & Terminology Services IN.5Standards-based Interoperability IN.6Business Rules Management IN.7Workflow Management Functions describe the behavior of a system in user- oriented language so as to be recognizable to the key stakeholders of an EHR System EHR-S Functional Model at a Glance

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. EHR-S Functional Model Function ID Function Name Function Statement Function Description Examples See Also Conformance Criteria

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Direct Care (excerpt) IDTypeNameStatementDescription DC.1.5FManage problem list Create and maintain patient- specific problem list A problem list may include, but is not limited to: Chronic conditions, diagnoses, or symptoms, functional limitations, visit or stay-specific conditions, diagnoses, or symptoms. Problem lists are managed over time, whether over the course of a visit or stay… See AlsoConformance Criteria IN IN The system SHALL display all active problems associated with a patient. 2. The system SHALL create a history of all problems associated with a patient. 3. The system SHALL retrieve a history of all problems associated with a patient. 4. The system SHALL provide a user interface to deactivate a problem. 5. The system MAY provide the ability to re-activate a previously deactivated problem. 6. … Source: HL7 EHR-S FM Direct Care Chapter

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Supportive Services (excerpt) Source: HL7 EHR-S FM Supportive Chapter

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Information Infrastructure (excerpt Source: HL7 EHR-S FM Information Infrastructure Chapter

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Structured Use of Imperatives Regular syntax is: “The system SHALL | SHOULD | MAY do something.” Conditional syntax is: “IF the system does X, THEN the system SHALL | SHOULD | MAY do something.” Dependant SHALL syntax is: “The system SHALL conform to IN.2.2 depending on organizational policy, scope of practice, or jurisdictional law.” “The system SHALL do something” vs. “The system SHALL provide the ability to do something”. For example, you don’t want the system to automatically match patient records – without human review.

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Tailoring Conformance Criteria Allow (and prompt) the user to tailor a function to meet a specific need via the key phrase, ”…according to organizational policy, scope of practice, or jurisdictional law”. If universally practiced, there’s no need to tailor the function. If at least one instance where the function needs to be tailored, we add the corresponding key phrase.

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Conformance to Profiles

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Rules for Shall/Should/May

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Q & A Sooo… The Public Health Functional Profile of the HL7 EHR System Functional Model and Standard How does it look to you??