MEDITECH Reports

MEDITECH NPR Change Process for Problem Tickets

Tweet

  

 

Like most people, you want to do things right the first time. But in the event something doesn't go as planned, you need a standardized Change Process in place so the change can be backed out. Let's examine a Change Process we can use in MEDITECH NPR to work a problem ticket to completion.

1) Login to LIVE & backup the BAR.PAT.zcus.duplicate.charges.npr.report to BAR.PAT.zcus.duplicate.charges.npr.report.0.

2) Test the report BAR.PAT.zcus.duplicate.charges.npr.report in LIVE.

3) If the problem can be reproduced in LIVE, create another copy of the report named BAR.PAT.zcus.duplicate.charges.npr.report.dev in LIVE.

4) Put trap code in the .DEV report and resolve the problem.

5) Put the .DEV report on a testing menu in LIVE and have the reporting party test and approve the changes. This is big. Do this step, and it will take care of a lot of problems.

6) Enter an Emergency Change Control request.

7) Check TEST and make sure there isn't a .DEV report already there. If there is a .DEV report in TEST, backup as BAR.PAT.zcus.duplicate.charges.npr.report.dev.0. Someone might be making report modifications per another change request, we don't want to lose the work that might already be in progress.

8) Move the .DEV version from LIVE to TEST.

9) Remove the .DEV report from the testing menu in LIVE.

10) Delete the .DEV report in LIVE.

11) Delete BAR.PAT.zcus.duplicate.charges.npr.report in TEST.

12) Rename the .DEV report in TEST to BAR.PAT.zcus.duplicate.charges.npr.report.

13) Move BAR.PAT.zcus.duplicate.charges.npr.report LIVE.

14) Validate changes in LIVE production report.

15) Request the reporting party validate the change in the production report as well.

I'd like to hear from you via email at: jsharpe@comstock-software.com on how you would improve this process.

Want an alert when the next post is published? Click the phone and Subscribe to the MEDITECH Reports Blog!