1 / 22

Viewing non-converted MAGIC Data from a C/S EMR Using the MEDITECH Data Repository

Viewing non-converted MAGIC Data from a C/S EMR Using the MEDITECH Data Repository. By: Glen R. D’Abate MUSE: Session 336. Session Agenda. Background outlining why this project was necessary at Chinook Health Care Summarization of project design strategy

ted
Download Presentation

Viewing non-converted MAGIC Data from a C/S EMR Using the MEDITECH Data Repository

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. Viewing non-converted MAGIC Data from a C/S EMRUsing the MEDITECH Data Repository By: Glen R. D’Abate MUSE: Session 336

  2. Session Agenda • Background outlining why this project was necessary at Chinook Health Care • Summarization of project design strategy • Outline of software components utilized in project development • Discussion of how this project design strategy might be applied in other situations • Demonstration of solution • Questions, answers, & discussion

  3. You Cannot Stop Progress Client / Server (2006) MAGIC (1987) Development of RSHIP Program • Seven Albert Canada Regions • 106 Acute Care Facilities • 25,000 Employees • 2 Million Electronic Medical Records

  4. Data Conversions You can’t always get what you want Application Data Conversions typically do not include “full detail” of historic information in an application. Moreover, data may be converted into an application but not available in EMR (e.g., Pathology Reports)

  5. Options For Accessing Non-Converted Historic Application Data Maintain application data on legacy system Convert data to image archival system Implemented in 1999 -- Application ILs performed then DR offers discrete data but has its drawbacks too

  6. DR Solution Considerations • Chinook Health Region already had DR implemented in MAGIC (version 5.4 SR2) • DR Contains all applications, but NOT all data • DR data had become static, allowing for design strategies not available in a dynamic DR • Tools are available to supplement DR data with any missing MAGIC data • Static data can be indexed for efficiency (we don’t have to worry about it being updated!) • DR’s Microsoft SQL Server RDMS provides powerful reporting technology natively (SSRS)

  7. Project Design Parameters / Constraints OK, we’ll use the DR – now what? • Take full advantage of Microsoft development tools • Minimize code development • Web-based solution • Ease of support • Fast data-access times • Integration with C/S EMR

  8. Dataset Generated Inquiry Response / Reports / etc. Unit # Passed to DR with Session Encrypt Key Patient Identified Design Strategy Schematic SSRS Web Server C/S Application Servers DR Version 5.4.2-3 (Static) DR data was transferred between 1999 when DR was implemented and 2006 when C/S went Live MAGIC Application Servers EMR Client

  9. DR Datamart, Data-Indexing MAGIC Patient Care Inquiry (PCI) provides a good starting point for determining how to best index data in the DR to provide fast access for our project SQL Server is polar opposite of MEDITECH – You add your own indexes and SQL “optimizer” decides if it will be used. Categories of “Reports” Lab Results… By Test Dept By Collect Date By Specimen

  10. EMR Client - Glen D’Abate MEDITECH Modifications to EMR Patient “lookup” or identification process is performed in EMR MEDITECH custom adding button (like this) to the EMR main menu EMR Screenshot

  11. Selecting the MagicView Button • Initiates a call to Internet Explorer passing a patient Unit Number and an encryption key value (to ensure this is a valid call) • Launches the MagicView web page and checks the encryption key -- if valid, presents a page with two sections: • A patient demographics header with identifier information including data from the most recent visit. • A menu containing an index of data available for viewing from this page. The list of potential data sources available was dictated by Chinook Heath Region’s report specifications for historic data to which they require access.

  12. MAGIC Historic Patient Inquiry Patient Data Last Visit Data This is a Menu Control that allows the report options available for a given patient to be dynamically generated Returns to EMR

  13. Sub-Menu Categories Selecting a sub-menu item launches an SSRS report that displays selected information for a patient Mouse-over Control Again, sub-menu items are only displayed if there is corresponding data to report for the identified patient Sub-menu choices are different for each menu item (e.g., Lab – Test Departments; Micro – Specimen Source; Radiology – Exam Type Menu Items

  14. Reports Specifications • Chinook Health Region provided us with detailed specifications for reports identifying historic patient data in the MAGIC LAB, MIC, PTH, PHA, RAD & DPT modules • Provided general report format and layout as well as the level of data detail required • Helped us identify DR data unavailable in MAGIC 5.2 (actually upgraded to 5.3 as part of project) but required for the project • Identified data that were required even though it was convert as part of an applications conversion, but not converted into EMR

  15. Detailed Spec! Creation of detailed report specifications is critical to insuring the information presented is the information that was requested. “Don’t give us what we asked for, give us what we need!”

  16. Reports can be easily formatted to present data in the most efficient and easily interpreted manner This report lists hematology test results with abnormal flags, units and normal range. Results are grouped by specimen number and sorted by most recent results to oldest. Can drill-through the specimen number to provide more detail including comments, query responses, order data, etc. (Not quite ready for prime-time) You just might get what you need

  17. Departmental Report Menu Item Sub-menu items are displayed for reports available for this patient

  18. SINATRA,FRANK 0000574 09/12/1972 35 Ex: Discharge Summary Report Health Record Discharge Summary Report as well as:

  19. Technology Overview • Microsoft Visual Web Developer 2005 Express Edition for web page that serves as main entry to SSRS Reports • Menu Control to display index of report items and sub-items available for selected patient • SQL Server 2000 Query against highly indexed tables to populate Menu Control • SQL Server 2000 Reporting Services for Report Development • MEDITECH Customization in EMR to launch Web page and pass patient Unit Number

  20. Ideas for Application of this Technology • Same strategy can be easily applied to MAGIC PCI application to integrate non-converted data into MAGIC EMR • Integration of any 3rd party non-converted data accessible by open technology (OLE, ODBC, flat file, etc.) can be achieved • MEDITECH Version 6.0 is on the horizon – this technology may provide accessibility to data that is not converted when 6.0 is implemented

  21. Key Points of this Project • Use of low-cost widely-available technologies • Minimal coding requirements • Reliance on EMR to identify a patient (we don’t want to reinvent the wheel!) • Flexible design allows for client customization • SSRS makes enhancing report layout and format with colors, fonts, charts, images, graphing, etc., a snap • Ease of implementation and use

  22. Thank You! Discussion, Questions & Answers

More Related