1 / 19

Integrating the Healthcare Enterprise

Integrating the Healthcare Enterprise. Integrating the Healthcare Enterprise Contribution to an EHR Strategy. José Mussi – Director of Architecture, Canada Health Infoway. Goals of IHE. Increase the rate and quality of integration in healthcare environments.

chynna
Download Presentation

Integrating the Healthcare Enterprise

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. Integrating the Healthcare Enterprise Integrating the Healthcare Enterprise Contribution to an EHR Strategy José Mussi – Director of Architecture,Canada Health Infoway

  2. Goals of IHE • Increase the rate and quality of integration in healthcare environments. • Foster communication among vendors. • Prove that integration is attainable through the use of standards. • Improve the efficiency and effectiveness of clinical practice.

  3. Introduction: EHR Challenges • One of the key integration challenges in healthcare today is achieving longitudinal electronic health records (EHR-LR) • Developing EHR solutions requires many integration profiles, some of which IHE has already addressed: • The Patient Cross-Referencing (PIX) profile provides methods for linking patient ID across multiple enterprises • The Retrieve Information Display (RID) profile defines a simple method for accessing clinical data • The Audit Trail (ATNA) profile addresses the need to have centralized logs of activities for privacy related requirements • IHE is now addressing one of the core profiles for the EHR: • The sharing and exchange of clinical documents across multiple healthcare settings

  4. Introduction: EHR Cross-Enterprise Document Sharing First step towards the longitudinal dimension of the EHR: Focus: Clinical Information Exchange between EHRs in care settings to communicate with a distributed longitudinal EHR. Goal: Meet a broad range of EHR-LR (Longitudinal Record) needs with a distributed, cross-enterprise, document centric document content generic

  5. Continuity of Care: Patient Longitudinal Record Nursing Homes Acute Care (Inpatient) Other Specialized Care(incl. Diagnostics Services) GPs and Clinics (Outpatient) Typically, a patient goes through a sequence of encounters in different Care Setting

  6. EHR-LR Integration Profiles: Publishing & Accessing the EHR-LR EHR-LR Nursing Homes Acute Care (Inpatient) Other Specialized Careor Diagnostics Services GPs and Clinics (Outpatient) The EHR-LR (Longitudinal Record) brings together patient encounter information managed by multiple care delivery systems

  7. EHR-LR EHR-LR EHR-LR Read Create Update Read Identification Decide to Assess demand For care End ofEncounter Define an action plan Selection of informations Actions to order EHR-CR Define healthcare Objective Two types of Integration : EHR-CR: Health Record as used during care delivery EHR-LR: Health Record as used across-encounters Care Delivery Process EHR-Solution = EHR-LR (Longitudinal Record)+ EHR-CR (Care Delivery Record)

  8. Key Statements: EHR-LR Fundamentals • Brings together patient encounter information managed by all types of care delivery systems. • Cross-enterprise, possibly across large geographical regions, and may include many clinical domains. • Typically collected and retained over a large period of time, providing a deep historic record for the patient. • Supported by multiple repositories that contribute to the patient’s longitudinal healthcare record. • Encounter data will very likely include some clinical documents, state and workflow information that willnot be stored in the EHR-LR.

  9. Key Statements: What is in the EHR-LR? • The EHR-LR data is made of discrete, persistent, clinical documents accessed by an unique identifier. • It may also contain other dynamic objects which are not being addressed by IHE at this time. • Metadata will be provided with each document by the EHR-CR and will be stored in the EHR-LR. • EHR-LR data formats will follow relevant clinical domain standards defined by field experts. EHR-CR is responsible for converting its internal data formats to the standard EHR-LR documents. • EHR-LR documents will kept in the EHR-CR or pushed to a separate EHR-LR repository.

  10. Key Statements:Accessing the EHR-LR • EHR-LR shall make available a list of all published documents for a given patient/selection parameters. • The selection of documents is the responsibility of the EHR-LR and not of the consumer applications. This is possible because of the document metadata kept in the EHR-LR. • The EHR-LR must ensure full content fidelity for all clinical documents that have been published. • The actual location of any particular document shall be transparent to the consumer application. • EHR-CR may provide clinical data by processing, extracting, or combining multiple documents.

  11. Key Statements: Deploying IHE EHR-LR Profiles • The deployment of EHR-LR integration profiles will initially be focused on a small number of specialties (cardiology, oncology, etc), disease, and/or on key information for continuity of care (e.g. CCR summaries). • The scope of the EHR-LR profiles will expand progressively as other specialties are included in the use cases.

  12. EHR-LR Integration Profile: Key Actors (Application Roles) • EHR-CR Source • Healthcare point of service system where clinical information is first collected • EHR-LR Directory • Index and metadata database for all published clinical documents • EHR-LR Documents Repository • Maintains and stores published EHR-LR documents • EHR-LR Consumer • Application system that needs access to EHR-LR documents and information • EHR-CR Recipient • Healthcare point of service system that receives clinical documents as part of a continuity of care transfer

  13. Integration Model 1: EHR-LR with Source Repository • An EHR-CR completes a phase of care for a patient where it: • Registers documents with an EHR-LR Directory actor. • Keeps these documents in an EHR-LR Repository actor. • Any other EHR-CR may query an EHR-LR Directory actor, find out about documents related to all phases of care for the patient and chose to retrieve some of these documents from any EHR-LR Repository Actor (Used in use Case 1 & 2). EHR-LRDirectory Register EHR-CR Source Query EHR-LR Consumer EHR-LR Repository Retrieve

  14. Integration Model 2: EHR-LR with Third Party Repository • An EHR-CR completes a phase of care for a patient where it: • Registers documents with an EHR-LR Directory Actor. • Provides these documents to an EHR-LR Repository Actor. • Any other EHR-CR may query an EHR-LR Directory Actor, find out about documents related to all phases of care for the patient and chose to retrieve some of these documents from any EHR-LR Repository Actor (Used in use Case 1 & 2). Register Query EHR-LRDirectory EHR-CR Source EHR-LR Consumer Provide-Transfer EHR-LR Repository Retrieve

  15. Integration Model 3: Direct Patient Transfer-Referral • An EHR-CR completes a phase of care for a patient where it: • Registers and Provides an EHR-CR Recipient Actor that a specific set of documents (newly created and priors of interest documents) are available from an EHR-LR Repository • The EHR-CR Recipient Actor receive both the registration and the documents. EHR-CR Recipient EHR-CR Source Register EHR-LRDirectory Provide-Transfer EHR-LR Repository

  16. Conclusion: EHR Cross-Enterprise Document Sharing • Leverages HL7 CDA (Clinical Document Architecture) and ASTM CCR (Continuity of Care Record). • The proposed strategy addresses one of the key integration problems in the realization of the EHR vision. IHE does not claim to master and address the definition and all aspects of a complete and interoperable EHR System. • In collaboration with well established standards bodies and other EHR related initiatives world-wide (EHRCOM, CCR, HL7, etc.), IHE expects to contribute at a more cost-effective and rapid deployment.

  17. IHE IT Infrastructure An open process for everyone! • To join IT Infrastructure planning or technical committee: • Contact Joyce Sensmeier, HIMSS. jsensmeier@himss.org • Suggest new profiles in IHE IT Infrastructure PlanningPlan IHE at HIMSS 2005 • Produce new profiles in IHE IT Infrastructure Technical Committee

  18. For more information…. • Web sites: www . himss . org / ihe www . rsna . org / ihe • Technical Documentation (www.rsna.org/ihe/tf/ihe_tf_index.shtml) • IHE IT Technical Framework 2004 – V 1.0 • IHE Rad Technical Framework 2003 – V 5.5 • IHE Laboratory Technical Framework 2004 – V 1.0 • Non-Technical Brochures (www.rsna.org/ihe/ihe_faq.shtml) • IHE Fact Sheet and IHE FAQ • IHE Integration Profiles: Guidelines for Buyers • IHE Connectathon Results

  19. Integrating the Healthcare Enterprise Thank You

More Related