Downtime Solution Reports by Presenter: Monthep Hongsyok Title: Data Analytics Architect

Downtime Solution ReportsDowntime Solution Reportsbyby

Presenter: Monthep Hongsyok Presenter: Monthep Hongsyok Title: Data Analytics ArchitectTitle: Data Analytics Architect

DOWNTIMEDOWNTIME

Planned DowntimePlanned Downtime

Unplanned DowntimeUnplanned DowntimeChallenges:Challenges:1) No preparation1) No preparation2) Unknown root cause2) Unknown root cause3) Unpredictable timeline to restore the 3) Unpredictable timeline to restore the system system

Critical Patient Information Critical Patient Information Covered by Downtime SolutionCovered by Downtime Solution

Medical Administration Record (MAR)Medical Administration Record (MAR) Problem ListProblem List AllergiesAllergies LabsLabs Vital SignsVital Signs Physician DocumentsPhysician Documents

Major ConsiderationsMajor ConsiderationsThe downtime solution must be:The downtime solution must be: AccurateAccurate As current as possible As current as possible ReliableReliable Up to 48-hour coverageUp to 48-hour coverage AccessibleAccessible Easy to troubleshoot and reprintEasy to troubleshoot and reprint Location based (nurse station or office)Location based (nurse station or office) Easy to maintainEasy to maintain FREEFREE

AccurateAccurate Use Cerner’server to populate (write) the Use Cerner’server to populate (write) the

data to data to FILL_PRINT_ORD_HXFILL_PRINT_ORD_HX table table

This table is periodically purged depending on This table is periodically purged depending on how often you want to purge it.how often you want to purge it.

- The data set is based on - The data set is based on RUN_IDRUN_ID column column- Easy to troubleshoot with - Easy to troubleshoot with RUN_ID RUN_ID

and ENCNTR_ID and ENCNTR_ID

Use our custom script to read the data from Use our custom script to read the data from FILL_PRINT_ORD_HXFILL_PRINT_ORD_HX table table

As current as possibleAs current as possible

Utilize operation jobs to populate and to Utilize operation jobs to populate and to read the data every two hoursread the data every two hours

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

Up to 48-hour coverageUp to 48-hour coverage

We have seen one hospital that We have seen one hospital that experienced nearly 48 hours of downtimeexperienced nearly 48 hours of downtime

For inpatients, our solution covers 48 For inpatients, our solution covers 48 hours with 24 hour interval (0 to 24 hours hours with 24 hour interval (0 to 24 hours and 24+ to 48 hours)and 24+ to 48 hours)

For outpatients, our solution has 24 hour For outpatients, our solution has 24 hour coverage for office hourscoverage for office hours

Inpatient MAR ReportInpatient MAR Report

Creation of Inpatient MAR ReportCreation of Inpatient MAR Report



Today MAR Reports

Tomorrow MAR Reports


Today MAR Reports






Write data to FILL_PRINT_ORD_HXtable




and generate the report output files tothe backend in Production

Read the date from FILL_PRINT_ORD_HX table


All files with MAR1 prefix are TODAY MAR


All files with MAR2 prefix are TOMORROW MAR




Copy the output files from Production toDevelopment backend

Today MAR Reports



Today MAR Reports



Today MAR Reports



Today MAR Reports


Today MAR Reports




AccessibleAccessible Can be viewed and printed from many Can be viewed and printed from many sourcessources

- Production domains- Production domains- Development domains- Development domains- Intranet- Intranet

Demonstration of deploying Demonstration of deploying Inpatient MAR ReportsInpatient MAR Reports

Easy to troubleshoot and reprintEasy to troubleshoot and reprint

Display confirmation message of the Display confirmation message of the successful printingsuccessful printing

Upon the deployment (printing) of the Upon the deployment (printing) of the downtime reports, we must be able to:downtime reports, we must be able to:

Identify if there is any point of failure and Identify if there is any point of failure and causecause

Reprint if requestedReprint if requested

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

Easy to maintainEasy to maintain Automated via operation jobsAutomated via operation jobs

Using custom (non-Cerner) table called Using custom (non-Cerner) table called NMH_PRINTERS to maintain relationships NMH_PRINTERS to maintain relationships between report output files and printersbetween report output files and printers

Demonstration of using Demonstration of using NMH_PRINTERS table and NMH_PRINTERS table and NMH Printer Maintenance NMH Printer Maintenance ApplicationApplication

Advantages of using Advantages of using NMH_PRINTERS tableNMH_PRINTERS table

• Avoid manual hardcode of printer queue

• Regular verification via CCL operation job to notify us if any printer queue becomes obsolete

• Easy, fast, and less likelihood for typo errors when updating the printer queue

• Can be utilized in other programming projects

Creation of Ambulatory Patient Summary ReportCreation of Ambulatory Patient Summary Report





Read data from the database andgenerate the report output files tothe backend in Production




Copy the output files from Production toDevelopment backend

Demonstration of deploying Demonstration of deploying Ambulatory Patient Summary ReportAmbulatory Patient Summary Report

Same as MAR report’s, the selected location/printer is based on NMH_PRINTERS table

Ambulatory Patient Summary ReportAmbulatory Patient Summary Report

Ambulatory Patient Summary Report Ambulatory Patient Summary Report via Intranetvia Intranet

Ambulatory Patient Summary Report Ambulatory Patient Summary Report via Intranetvia Intranet

Questions?Questions?

Monthep HongsyokMonthep HongsyokData Analytics ArchitectData Analytics ArchitectE-mail: E-mail: [email protected]@nmh.orgPhone: 312-926-3254Phone: 312-926-3254