The 'htmlformflowsheet' module is an OpenMRS module that allows you to generically model a paper flowsheet. The basis for the design of this module was originally the WHO Cat-IV treatment card for multi-drug resistant tuberculosis, which contains baseline information (filled out once), and then flowsheet-type information that is appended to the paper form over time (for items such as monthly regimen adherence, monthly smear and culture results, and regimen changes).
htmlformflowsheet custom tag for flowsheets
This module provides basic functionality for embedding small htmlforms inside of larger htmlforms, where the small htmlforms each represent one row in a patient chart. This functionality is provided by the 'htmlformflowsheet' custom htmlform tag (see htmlformflowsheet: custom tag for htmlformentry section).
tabbed interface for flowsheets
Additionally, the module allows you to specify any number of tabs in a tab-based layout, each containing a distinct html form. You can then designate whether or not the html form should be used once (as in baseline demographics), or as a flowsheet (where a new row will be added for every month, as in monthly adherence, for example). Forms that are one-time forms (like baseline demographics and medical history forms) can be as complex as is necessary, and working with these is almost identical to dealing with a stand-alone htmlform externally -- it just all happens within a tab.
Htmlforms that are meant to be flowsheets should represent exactly one row in a table on the paper form. A 'flowsheet' type tab will display the longitudinal history of the entry of this form, and allow you to append new entries, and edit/delete existing entries.
Any form entry of either type can be viewed and edited later, and this has been optimized for performance such that only that tab will be reloaded after a new entry or edit is made.
(Note: this module was previously called the 'mdrtbpatientchartwidgets' module. The previous 'mdrtbpatientchartwidgets' module will receive no further development. All further development will happen here.)
1.2.2: This version adds the role-based-homepage portlet. I hope that this will be a fairly short-lived version, because i want to add a configuration data model, and give the option of including portlets in tabs. I will continue to support this feature, but the setup is going to change. Here's how it currently works:
Using the "URL-based Interface" syntax describe below, you first need to configure the setting named htmlformflowsheet.programConfigurationMap which maps program Ids to configuration strings. Here's an example value:
This maps two programs to configurations, programs 5 and 6.
Next, in your role-based homepage for a given role, you just need to include a new portlet that is included in htmlformflowsheet. Here's an example role-based homepage:
Notice that the portlet tag includes program Ids 5 and 6, which correspond to the global property described above. For the create patient widget created by the portlet, you must also specify an htmlform that creates a patient, which in this example is form Id 16. Here's a sample htmlform for creating a patient that was created by Berchmas, at PIH/IMB Rwanda:
1.2: I have recently updated the version of htmlformflowsheet in the module repository to version 1.2. This version was tested against openmrs1.6.4.x and htmlformentry version 1.7.4. I have not tested against openmrs1.7 or higher, although i'd be grateful for someone to try this and let me know how it goes. Additionally, we only use the htmlformflowsheet tag in production, so i have less of an incentive to keep up with the tabbed interface side of the module (although i tested this when adding version 1.2 to the repository). If someone wants to help me push this functionality forward, that would be a great help. Version 1.2 also includes full support for the htmlformentry drugOrder tag. Using htmlformflowsheet + htmlforms with the drugOrder tag allows you to create a regimen management UI within an htmlform that won't duplicate drug orders. For a better explanation of how the drugOrder tag, see the HtmlForms Reference wiki page.
TODO: regimen management screenshot
The HtmlFormFlowsheet Module now allows you to embed its flowsheet widget into an html form. This means that you can embed multiple htmlforms inside of other htmlforms as flowsheets. Another way to think of this functionality is that the 'flowsheet' view in this module can be embedded in a parent htmlform as a widget.
To do this, all you have to do is upload HtmlFormFlowsheet version 1.1 (or higher), and then in your htmlform xml, you can now use the tag:
In this example, formId corresponds to Form 39, not html_form_id = 39. 'formId' is the only attribute that this tag takes. Here, form #39 will be rendered as a flowsheet in the parent htmlform. As long as the htmlformflowsheet module is installed on your system, the htmlformflowsheet tag will always be a valid tag within htmlforms.
Example of HTML form with three embedded flowsheets
By default, the "Add another" button in the flowsheet table will appear at the top of the table, with default text. You can set the location of this to be the bottom of the table, using the global property value:
You can customize the label for this button within the htmlformflowsheet tag, as described below.
Also by default, the flowsheet table will list encounters in chronological order, most recent at the top, oldest at the bottom. You can reverse this order by configuring the global property:
The HtmlFormFlowsheet Module can now be used to have its htmlformflowsheet widgets either create a new encounter per flowsheet when a new new row is added (available in 1.1), OR, you can choose an existing encounter of the same encounter type to append Obs to. This allows you to use multiple flowsheet widgets to 'build' a month's rendez-vous encounter.
For this to work, all you need to do is add the attribute sharedEncounter="true" to the htmlformflowsheet tag, like this:
<htmlformflowsheet formId="39" sharedEncounter="true"/>
When the sharedEncounter attribute is set to true, users will be prompted to choose from a list of existing encounters. The Obs will be then appended to the chosen encounter.
The only additional piece of setup that you need for this to work is that you need to make sure that all of the htmlforms that are going to be used in your patient chart to represent a row in an htmlformflowsheet widget are of the *same encounter type*. And, you need htmlformentry module version 1.6.6 or greater.
If you only want a single tab-based interface, there are two global properties that allow you to configure your tab layout:
This global property essentially does the entire layout of the tabs. Here is an example property value:
S:Demographics:15:LAST|F:Smear:21|F:Culture:22|F:Labs:20|F:Adherence:23|F:Adverse Effects:17|F:Steering Committee:19|F:Comments:18
These are pipe-delimited entries of the form:
<<Type>>:<<Title:FormID>>:<<FIRST or LAST>>, where
This global property allows you to place external links above the rendered tab interface. These are also pipe-delimited and take the form:
for example, here is a valid sample value: Bacteriologies:/module/mdrtb/mdrtbPatientOverview.form?view=BAC|DSTs:/module/mdrtb/mdrtbPatientOverview.form?view=DST|Regimens:/module/mdrtb/mdrtbPatientOverview.form?view=REG|Treatment Outcomes:/module/mdrtb/mdrtbPatientOverview.form?view=STATUS
Once you have configured these global properties, you can see the results by navigating to:
NOTE: After changing either of these global properties, you will need to stop and start the module in order for your new values to take effect.
If you would like for your application to have multiple flowsheet layouts, this can be done by adding the URL parameters 'configuration', 'links', and 'fullPage' to the module's URL.
This global property essentially does the entire layout of the tabs.
These are pipe-delimited entries of the format:
<<Type>>:<<Title:FormID>>:<<FIRST or LAST>>, where
This optional parameter allows you to place external links above the rendered tab interface. These are also pipe-delimited and take the form:
This optional parameter allows you to specify whether or not you want to include the OpenMRS header and footer. The only two allowed values are "true" and "false". If you specify fullPage=true, you get the default 'everything' view of the configured tabs. Or when omitted from the URL the full page including header and footer are displayed. If you specify fullPage=false, you don't get the header, patient header, or footer, making the tabs suitable for insertion into a ui framework (tested against the ui.springmvc module). Note, fullPage is case sensitive in respect to both the parameter name and parameter value.
fullPage=true or fullPage parameter is omitted
Header and Footer are displayed
Header and footer are hidden
Htmlformflowsheeet version 1.2.1 additionally adds the parameter 'title' which puts the title argument above the flowsheet tabs. For example you could add &title=ASTHMA%20PROGRAM to add ASTHMA PROGRAM to the top of the tabbed interface. Other parameters that work across all tabs are 'showHtmlForm', which will change the flowsheet renderer to use htmlformentry native rendering if set to true rather than htmlformflowsheet default rendering, and 'showAllEncsWithEncType', which will allow you to append the data entered in a flowsheet to already existing encounters.
For example, if you navigate to the following, you get the default tab view for patient #33.
If you navigate to the following, you get a tab view with only the culture and lab forms, and a link to mdrtb treatment outcomes.
Here is one-time form in the tab structure: http://archive.openmrs.org/wiki/Image:Single.JPG
This is a flowsheet-type form in the tab structure: http://archive.openmrs.org/wiki/Image:Flowsheet.JPG
keywords: flowsheet, patient chart, htmlformentry, formflowsheet, treatment card, tabs
The most updated HTML Form Flowsheet module version with working tabbed interface is the Github 21 Febrary 2013 master branch snapshot.
This has been tested with: