Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Downtime Solution Reports by Presenter: Monthep Hongsyok Title: Data Analytics Architect."— Presentation transcript:

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

2 DOWNTIME Planned Downtime Planned Downtime Unplanned Downtime Challenges: 1) No preparation 2) Unknown root cause 3) Unpredictable timeline to restore the system 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) Medical Administration Record (MAR) Problem List Problem List Allergies Allergies Labs Labs Vital Signs Vital Signs Physician Documents 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 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  Use our custom script to read the data from FILL_PRINT_ORD_HX table

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 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 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 For outpatients, our solution has 24 hour coverage for office hours

9 Inpatient MAR Report

10 Creation of Inpatient MAR Report

11

12

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

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

15

16

17 Write data to FILL_PRINT_ORD_HX table

18 Creation of Inpatient MAR Report

19

20 and generate the report output files to the backend in Production Read the date from FILL_PRINT_ORD_HX table

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

25 Copy the output files from Production to Development backend

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

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

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

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

30

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

32 Demonstration of deploying Inpatient MAR Reports

33

34

35

36

37

38

39

40

41

42

43

44

45

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

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

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68 Easy to maintain  Automated via operation jobs  Using custom (non-Cerner) table called NMH_PRINTERS to maintain relationships between report output files and printers

69 Demonstration of using NMH_PRINTERS table and NMH Printer Maintenance Application

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90 Advantages of using NMH_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

91 Creation of Ambulatory Patient Summary Report

92

93

94

95 Read data from the database and generate the report output files to the backend in Production

96 Creation of Ambulatory Patient Summary Report

97

98 Copy the output files from Production to Development backend

99 Demonstration of deploying Ambulatory Patient Summary Report

100

101

102

103

104

105

106

107

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

109 Ambulatory Patient Summary Report

110 Ambulatory Patient Summary Report via Intranet

111

112 Questions?

113 Monthep Hongsyok Data Analytics Architect Phone:


Download ppt "Downtime Solution Reports by Presenter: Monthep Hongsyok Title: Data Analytics Architect."

Similar presentations


Ads by Google