1 / 7

EDT Pilot

The EDT Pilot involves a nationally procured electronic document transfer system implemented in various health boards, including Tayside. The EDT Hub acts as a centralized "mailbox" for sending electronic correspondence to the relevant GP practices. It exposes a web service API and converts documents into the Kettering XML structure for seamless integration with the GP practice's Docman document management system. The pilot also highlights challenges encountered, such as handling exceptions and compatibility issues with various health information systems. Future expansions include integrating with additional systems and practices.

samira
Download Presentation

EDT Pilot

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. EDT Pilot Technical Overview

  2. EDT Background • Procured Nationally • Implemented in several health boards (Tayside) • “EDT Hub” acts as a “mailbox” to send electronic correspondence back to appropriate GP practice • Exposes webservice API • Document goes into “Kettering” XML structure in order to be sent • Letters sent via EDT integrate seamlessly in to the GP practice “Docman” document management system as if they had been scanned

  3. Previous GG&C Pilot • Previous pilot in GG&C used SCI Gateway as transport mechanism • Was used with EDIS (A&E), SMD (letter system) and South Glasgow HIS (PAS) • Gateway didn’t integrate fully with DocMan, GPs had to manually save to DocMan. GPs were happy with process, but LMC raised EDT to agenda • Disagreement whether DocMan supported the use of ClinicalLetter files, or just Referrals via Gateway • Used .NET Windows service to package up letter in ClinicalLetter schema, and send to SCI GW “ReceiveWithAttachments” web method. • Problems handling exceptions: Non-Glasgow patients, invalid GP, etc

  4. Pilot Using EDT • EDIS (A&E) system is initial system to pilot with • It outputs SCI DischargeLetter schema XML, with attached stylesheet • Ensemble will pick up XML, convert document/stylesheet to TIFF, construct SCI DocumentUpload XML and send to Store, then construct Kettering XML, and send to EDT

  5. Process

  6. Challenges • XML from EDIS isn’t strictly to DischargeLetter schema - had to tweak national schema • Invalid postcodes from EDIS can prevent document going into SCI Store – Ensemble performs “clean up” • How to handle exceptions?

  7. Future • Pilot EDIS with a few practices this year, or early next year • Include other systems going into new year, and roll out further by CHP/area (Feb 2012) • Integrate with letters from TrakCare as TrakCare replaces old PAS systems. Currently looking at best way of apporaching – consortium?

More Related