Overview

Each summary is a velocity template script. The script, as it works now, spits out an xml document. The xml document is parsed with the associated xslt.

The default xslt converts the xml to fop for pdf generation.

As of version 2.3, printing is handled by an external application. When an encounter form is submitted, clinical summaries are automatically generated to a location in the file system. Printing is performed manually. Printing does not do the actual printing, but sends the generated clinical summary .pdf to a separate location in the file system for printing.

Setup

Versions prior to 2.3 require The Printing Module.

Download the module and install it in OpenMRS.

Go to the administration screen and click "Manage Clinical Summaries". There are two summaries provided by default: Basic Summary and the current AMPATH clinical summary. The AMPATH clincial summary makes some assumptions about concepts and encounters being used that are specific to the AMPATH program. The basic summary is as generic as possible.

Usage

The Manage screen for clinical summaries allows you to change both the summary xml code and the way that xml is translated. Currently you must translate the xml into Apache FOP for pdf generation.

The xml code is generated using velocity scripting tags. The functions available are found in the summary functions class. This class extends the data export functions class and has access to all of those methods as well.

Generating Clinical Summaries Automatically

Clinical Summaries are generated on the Clinical Summary Print Queue automatically after filling out an encounter form. The process is outlined in the steps below.

1. Find/Create Patient
2. Type in a name and select a patient. The page should redirect to the Patient Dashboard.
3. Click on the "Forms" tab.
4. Select one of the following forms that were created at Setup. Current supported forms are: Ampath Adult Return Visit Form and Ampath Adult Initial Visit Form.
5. At the Pop-up window, select Open with Microsoft Office InfoPath. Click OK.
6. Fill out at least part of the form. Required fields on page one of Return Visit Form are: Date, Location, Name. Required fields on page two of Return Visit Form are: Add New Problem, Remove Problem From List, Select Provider.
7. Submit the form and wait a few minutes.
8. Go to Administration --> Clinical Summary Module --> "View Clinical Summary Queue" and look for the Clincal Summary on the queue.
9. If on the InfoPath form (step 5) you selected to have lab tests done, then the STATUS will be WAITING_ON_LABS. If you did not select tests the STATUS will be PENDING.
10. Printing is done manually. Nothing should automatically be sent to the printer. You will have to make selections on the "View Clinical Summary Queue" page and then click Print Selected Summaries.

Printing Clinical Summaries

Go to Administration --> Clinical Summary Module --> View Clinical Summary Queue

1. In Filter Viewable Summaries section, select GENERATED for the Queue Status
2. Optionally select a start and end date for Encounter Date
3. Select a Location
4. Check Apply/Remove Filter to apply the filter
5. Check Check/Uncheck all to select all summaries; or just check individual summaries to print
6. Press the Print Selected Summaries button. When printing is done, the page will refresh.
   

Resources

• http://xmlgraphics.apache.org/fop/
• http://velocity.apache.org/

Global Properties

Printing Logic Class

clinicalsummary.printLogicClass must be filled in as a global property. Currently, the only available value is "org.openmrs.module.clinicalsummary.AMPATHClinicalSummaryPrintingLogic".

File System Directories

• clinicalsummary.queueItemGenerateDir defaults to ${OpenMRS Application Data Directory}/clinicalsummary/generated
• clinicalsummary.queueItemPrintDir defaults to ${OpenMRS Application Data Directory}/clinicalsummary/to_print
• These can be overwritten to anywhere on the file system.

  How Tomcat recognizes a Network Directory

  In our case, we want to generate and print clinical summaries to a mapped drive on another computer. Instead of the default above, we fill in //REMOTE-COMPUTER/amrs/clinicalsummary/generated for the global property. In order to map the network drive for Windows:

1. Create a user in Windows that will run Tomcat. Maybe "TomcatUser".
2. In the Windows services, set Tomcat Service to Log On as this account: TomcatUser
3. Access the remote computer (maybe "REMOTE-COMPUTER") and set TomcatUser as a user on that computer. Set desired privileges.
4. Create a shared directory. In our case we created a folder "C:/amrs". Right click and set properties to C:/amrs so that it is shared. Make sure TomcatUser has privilege to access the folder.
5. On the server, where Tomcat is running under the user TomcatUser, log in as TomcatUser. Create a mapping to the hard drive of REMOTE-COMPUTER. Since TomcatUser is also a user on REMOTE-COMPUTER, authentication should not be a problem (as long as the passwords are the same). In our case we mapped \\REMOTE-COMPUTER\c$ (Alternatively, \\123.45.6.789\c$) to the Z: drive.
6. At a convenient moment, restart Tomcat.
7. In the global properties for file system directories do not use Z:/amrs/clinicalsummary/generated because Tomcat will not recognize it. Instead use //REMOTE-COMPUTER/amrs/clinicalsummary/generated for the global property.

Workflow

Clinical Summary Queue Item

U1. User looks at View Clinical Summary Queue page.

W1. Set status=WAITING_ON_LABS.

G1. If status==null or status!=WAITING_ON_LABS, Set status=GENERATED.

P1. Get fileName and path.

R1. If fileName!=null, remove File from file system.