MEDITECH Reports

MEDITECH Macro Naming Conventions

 Email Article |  Twitter |  digg it |   delicious |   StumbleUpon |   LinkedIn |   Technorati |  reddit 

For a while now, I've been consolidating standard logic from reports into a single report. I call this single report a code library.

I have an allergy/medication routine that until now existed in our Adult & Peds Anesthesia Summary & Adult, Newborn, Obstetrics & Pediatrics Admission Summary reports. Over time this routine has evolved into something generic and very useful. The next step in the process is to move this routine to the code library. I have to ask myself how I will manage changes between facilities and service lines at those facilities.

The last thing I want to do is implement a centrally managed, generic solution and then move the logic back to reports as problems surface. The first problem I can see is a need to change medications but not allergies or vice versa.

The solution may be to implement a set of 2 macros for each set of information (allergies, meds):

1. a setup routine and a data processing routine for allergies
2. a setup routine and a data processing routine for medications

The setup routine would specify queries, data elements or screen ranges to be processed. The data processing routine would gather data to a specified array.

At this time, all facilities I support currently have similar needs. In the future, a facility may need a different solution than the majority of facilities I support.

The solution to this problem may be resolved using a naming convention:

DPM.report.M.allergies.1
DPM.report.M.medications.1

If a facility needs changes that differs from the majority:

DPM.report.M.allergies.facility.1
DPM.report.M.medications.facility.1

If a single department or line of service requires a solution different from the majority of departments at that facility:

DPM.report.M.allergies.facility.dept.1
DPM.report.M.medications.facility.dept.1


.: This relates to NPR Report Writer - Macros. :.