1 / 10

iEHR Standards Project HL7 PC Presentation

Learn about the Canadian iEHR Project, its care objects, and how it aligns with the PC Committee. Explore the iEHR components, messages, and infostructure requirements.

rebac
Download Presentation

iEHR Standards Project HL7 PC Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. iEHR Standards Project HL7 PC Presentation HL7 WGM Boca Raton September 2006

  2. Presentation Objectives • To introduce the Canadian iEHR Project • To introduce the Canadian iEHR Care Objects • To demonstrate that our work fits with the PC Committee • To discuss how we can work together

  3. Presentation Overview • Background • iEHR Components • iEHR Messages • EHR Infostructure • Requirements • Canadian mini-D-MIMs derived from PC Care Statement

  4. Background Canada Health Infoway (Infoway) has initiated the Interoperable Electronic Health Record (iEHR) project to set the foundation for establishing the messaging standards by which the EHR community in Canada will interoperate. These specifications will form the basis of the interoperable messaging platform within the EHR Infostructure as detailed in Infoway’s blueprint document.

  5. iEHR Components • The iEHR specifications will address the requirement by the healthcare community (Point of Service or PoS) to interact with two specific components of the EHR Infostructure; • The Shared Health Record (SHR) • The EHR Index. • The SHR is primarily responsible for housing healthcare information related to encounters, events and episodes which spans multiple business domains; that is, information specifically identified as not belonging to an already existing business area (e.g. Drug Information, Laboratory, and Diagnostic Imaging) • The EHR Index will contain meta information about healthcare events, episodes and encounters stored in the SHR and in domain-specific repositories (Drug, Lab, DI). This meta data will effectively catalogue the information to allow for easier storage to, and retrieval from the SHR and the domain-specific repositories.

  6. Longitudinal Record Services Common Services Communication Bus JURISDICTIONAL INFOSTRUCTURE Ancillary Data& Services EHR Data& Services DataWarehouse Registries Data& Services OutbreakManagement PHSReporting SharedHealth Record DrugInformation DiagnosticImaging Laboratory HealthInformation ClientRegistry ProviderRegistry BusinessRules EHRIndex MessageStructures NormalizationRules LocationRegistry TerminologyRegistry Security MgmtData Privacy Data Configuration HIAL Public HealthServices PharmacySystem RadiologyCenterPACS/RIS Lab System(LIS) Hospital, LTC,CCC, EPR PhysicianOffice EMR EHR Viewer Public Health Provider Pharmacist Radiologist Lab Clinician Physician/Provider Physician/Provider Physician/Provider POINT OF SERVICE EHR Infostructure: Conceptual Architecture

  7. iEHR HL7 v3 Messages • The iEHR Standards Project has develop HL7 V3 messaging and associated terminology standards • to support PoS recording/retrieval of clinical information to/from the SHR for high priority clinical needs. • to support the capture of EHR Index Metadata.

  8. Requirements • Common Observations • Record/List/Get Common Observation (Coded/Measured) • Procedure • Record/List/Get Procedure (Physical/Non-Physical) • Care Composition • Record/List/Get/Update Encounter/Episode/Generic Care Event • EHR Index • Retrieve a list of events described at a high level for a particular patient based on various search criteria • Notify a Point of Service application that an event previously captured in the index is being revised (e.g. status change) • Patient Clinical Profile • Obtain Patient clinical profile from SHR & Domain-specific Repositories

  9. Canadian mini-D-MIMs derivedfrom PC Care Statements Common Observation Observation • Coded Observation • Measured Observation Substance Admin Pharmacy Supply Lab Other Supply Supply DI Procedure Procedure • Cognitive Service • Physical/Surgical Service Encounter • Encounters • Episodes • Generic Care Events Care Composition Organizer Act Reference EHR Index

  10. For more information John Kufuor-Boakye kufuor@telusplanet.net Lloyd McKenzie lloyd@lmckenzie.com

More Related