1.14k likes | 1.37k Views
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.
E N D
Downtime Solution Reportsby 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
Critical Patient Information Covered by Downtime Solution • Medical Administration Record (MAR) • Problem List • Allergies • Labs • Vital Signs • Physician Documents
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
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
As current as possible • Utilize operation jobs to populate and to read the data every two hours
Reliable • The data will be saved under .DAT and .PDF file formats, and ready to print whenever needed including when the database is down
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
Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports
Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports
Creation of Inpatient MAR Report Write data to FILL_PRINT_ORD_HX table
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
Creation of Inpatient MAR Report All files with MAR1 prefix are TODAY MAR
Creation of Inpatient MAR Report All files with MAR2 prefix are TOMORROW MAR
Creation of Inpatient MAR Report Copy the output files from Production to Development backend
Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports
Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports
Creation of Inpatient MAR Report Today MAR Reports Tomorrow MAR Reports
Creation of Inpatient MAR Report Today MAR Reports Today MAR Reports Tomorrow MAR Reports Tomorrow MAR Reports
Accessible • Can be viewed and printed from many sources - Production domains - Development domains - Intranet
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
Location based • All data are saved with the file name based on the nurse station or office. Therefore, easy to identify, print, and view.