1 / 13

Patient Data Exchange BHEPP

Patient Data Exchange BHEPP. BHEPP – Patient Data Exchange. Enabling electronic health record (EHR) exchange when patients are transferred between participating hospitals during a disaster involving mass casualties, for improved patient care. Overview. BHEPP Partnership. Suburban Hospital.

nedra
Télécharger la présentation

Patient Data Exchange BHEPP

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. Patient Data ExchangeBHEPP

  2. BHEPP – PatientData Exchange Enabling electronic health record (EHR) exchange when patients are transferred between participating hospitals during a disaster involving mass casualties, for improved patient care Overview

  3. BHEPP Partnership Suburban Hospital NIH Clinical Center NNMC • Acute care community hospital • Level II Trauma Center • Community preparedness experience • Decontamination capacity • Clinical research facility • Surge capacity • Sophisticated diagnostic laboratory facilities • Skilled campus HAZMAT & decontamination team • Substantial basic science and specialty/subspecialty expertise • Military hospital • Extensive decontamination capacity • Skilled deployable workforce • Availability of “in-residence” staff • Preparedness training

  4. Disaster Scenario 2 1 Disaster causes mass casualties Non-critical patients are transferred to other hospitals to make space for emergency patients 3 Patient data is transferred electronically to the receiving hospital to aid in patient care

  5. What to share ? Which format / standard ? How to share ? Challenges

  6. Patient Summary Record • Required “Minimum Data Set” • Based on “NHIN Core Content • Specification” for exchange • of Patient Summary Record • Content Modules • Person Information • Support (Emergency Contact Information) • Allergies and Drug Sensitivities Conditions (Problem list) • Medications • Information Source

  7. Patient Summary Record “Data Format - HL7 CDA Standard (XML)” DocumentLevel Constraints Machine readable entry Human readable entry

  8. Patient Summary Record Data Transformation – Suburban EHR XML to CDA Using Adapters

  9. Patient Summary Record Data Transformation – NIH Clinical Center XML to CDA Using Adapters

  10. Patient Data Exchange - Application Features Web Upload Hospital 1 Hospital 2 • Web Upload • Mapping and Translation • Patient Search • Patient View • PDF/XML Download • Admin Module • Integration with Triage Data • (Digital Pen) • Integration with RFID Data • (Future) Suburban Adapter NNMC Adapter Mapping & Translation NLM CC Adapter CDA Receiving Hospital HTML Adapter PDF Adapter Search & View

  11. Patient Data Exchange - Application Technical Specifications • ColdFusion 8.0 Application Server • Apache Web Server 2.2 • HTTPS based for security and encryption • ColdBox (MVC) based framework for easier extensibility • Internationalization and localization

  12. CMAX 2009

  13. Future Directions • Integration with RFID for location tracking during disaster • Integration with “NHIN – National Health Information Network” for nationwide real time Patient Data Exchange • DICOM support for including medical images with Patient Summary Record

More Related