1 / 113

Downtime Solution Reports by

Downtime Solution Reports by. Presenter: Monthep Hongsyok Title: Data Analytics Architect. DOWNTIME. Planned Downtime Unplanned Downtime Challenges: 1) No preparation 2) Unknown root cause 3) Unpredictable timeline to restore the system.

amir-woods
Download Presentation

Downtime Solution Reports by

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. Downtime Solution Reportsby Presenter: Monthep Hongsyok Title: Data Analytics Architect

  2. DOWNTIME • Planned Downtime • Unplanned Downtime Challenges:1) No preparation 2) Unknown root cause 3) Unpredictable timeline to restore the system

  3. Critical Patient Information Covered by Downtime Solution • Medical Administration Record (MAR) • Problem List • Allergies • Labs • Vital Signs • Physician Documents

  4. Major Considerations The downtime solution must be: • Accurate • As current as possible • Reliable • Up to 48-hour coverage • Accessible • Easy to troubleshoot and reprint • Location based (nurse station or office) • Easy to maintain • FREE

  5. Accurate • Use Cerner’server to populate (write) the data to FILL_PRINT_ORD_HX table • Use our custom script to read the data from FILL_PRINT_ORD_HX table This table is periodically purged depending on how often you want to purge it. - The data set is based on RUN_ID column - Easy to troubleshoot with RUN_ID and ENCNTR_ID

  6. As current as possible • Utilize operation jobs to populate and to read the data every two hours

  7. Reliable • The data will be saved under .DAT and .PDF file formats, and ready to print whenever needed including when the database is down

  8. Up to 48-hour coverage • We have seen one hospital that experienced nearly 48 hours of downtime • For inpatients, our solution covers 48 hours with 24 hour interval (0 to 24 hours and 24+ to 48 hours) • For outpatients, our solution has 24 hour coverage for office hours

  9. Inpatient MAR Report

  10. Creation of Inpatient MAR Report

  11. Creation of Inpatient MAR Report

  12. Creation of Inpatient MAR Report

  13. Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports

  14. Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports

  15. Creation of Inpatient MAR Report

  16. Creation of Inpatient MAR Report

  17. Creation of Inpatient MAR Report Write data to FILL_PRINT_ORD_HX table

  18. Creation of Inpatient MAR Report

  19. Creation of Inpatient MAR Report

  20. Creation of Inpatient MAR Report Read the date from FILL_PRINT_ORD_HX table and generate the report output files to the backend in Production

  21. Creation of Inpatient MAR Report All files with MAR1 prefix are TODAY MAR

  22. Creation of Inpatient MAR Report All files with MAR2 prefix are TOMORROW MAR

  23. Creation of Inpatient MAR Report

  24. Creation of Inpatient MAR Report

  25. Creation of Inpatient MAR Report Copy the output files from Production to Development backend

  26. Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports

  27. Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports

  28. Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports

  29. Creation of Inpatient MAR Report Today MAR Reports Today MAR Reports Tomorrow MAR Reports Tomorrow MAR Reports

  30. Creation of Inpatient MAR Report

  31. Accessible • Can be viewed and printed from many sources - Production domains - Development domains - Intranet

  32. Demonstration of deploying Inpatient MAR Reports

  33. Easy to troubleshoot and reprint Upon the deployment (printing) of the downtime reports, we must be able to: • Display confirmation message of the successful printing • Identify if there is any point of failure and cause • Reprint if requested

  34. Location based • All data are saved with the file name based on the nurse station or office. Therefore, easy to identify, print, and view.

More Related