Developer shortcuts: Technical Overview
The HTML Form Entry allows anyone with basic HTML programming skills and a knowledge of the OpenMRS system to create forms. It is an alternative to the Infopath FormEntry module in many (but not all) cases.
The key point about writing forms with this module is that you only have to write HTML (with some special tags for things in the OpenMRS model) and the module will automatically "just know" what to do when the user clicks the submit button.
Currently a form submission creates one encounter for one patient.
Comparison with Infopath FormEntry module
- Forms are entered in-the-webapp. No need for installed software on the client.
- You can review a form after entering it and have it look "just like you entered it"
- Form submission immediately creates data (i.e. no waiting for queues to be processed.)
- No WYSIWYG editor (though one is in the works)
- Behavior is not really programmable
Want to help improve this module? Contact Darius.
- Download the module from the repository and install it.
- Create a Form in OpenMRS via Manage Forms. You do not need to build the form schema. You cannot use an existing form schema from a prior InfoPath form (even if it's marked as retired) or it will not show up if using both Form Entry and HTML Form Entry. Ticket # 1967
- Go to Manage HTML Forms, create a new form there, point it at the desired Form in OpenMRS, and put in the HTML behind the form. HTML Form Entry Module HTML Reference
Filling out a form
Note that if you put in an illegal value (per the constraints in the concept dictionary) it is immediately flagged.
Viewing a form
This looks pretty close to the initial entry.
Here's the code behind the screenshots
The following privileges may be necessary for various activities. It may be necessary to create them manually, and add them to your user's role.
- _=1.4 "Patient Dashboard - View Html Forms Section" <-- Required to view the HTML Forms tab on the patient dashboard
- _=1.5 "Form Entry" <-- Required to enter forms generally
- "Add Encounters" <-- Required to submit a form
To request more features, leave a comment on the Discussion section of this page: Talk__Html_Form_Entry_Module.
Want to build an interface out of nothing but html forms? The HtmlFormFlowsheet module provides an easy way of combining html forms into a simple patient-dashboard-type configurable interface. Or, you can embed flowsheet tables directly into your existing htmlforms. This module is particularly useful if you are trying to model patient-based flowsheet type data (such as an MDRTB CAT-IV treatment card, or a chronic care flowsheet). See: HtmlFormFlowsheet_Module
Version 1.6.6 (@revision 14939)
- Added style="autocomplete" option to obs tag
- Added includeIf & excludeIf tags
Version 1.6.5 (@revision 14430)
- Added ability to reference a concept by mapping, or by uuid
- Added ability to handle nested obsgroups
- Replaced dojo functionality with jquery
- Minor bug fixes
Version 18.104.22.168 (@revision 13717)
- Changed all controllers so that sessionForm=false
- Minor tweak to assure properly compatibility with HTML Form Designer module
- Minor layout tweaks
- Updated so that HTML Forms now have uuids and other BaseOpenmrsMetadata. This will allow Html Forms to work with the sync module.
- Fixed bug with HTML Form Entry privileges
- Fixed #2261 - Problem using an obs with the same concept id in two obsgroups on one form
- Fixed #2262 - encounterProvider defaults broken in OpenMRS 1.6
- Updated rendering of date/time widgets to be compatible with OpenMRS 1.7
- Added support for handling observations of types Time and Datetime with appropriate widgets - #2231
- Fixed bug with setting time using the Time widget
- Fixed bug with rendering international characters in "Preview HTML Forms from File" on systems when UTF-8 is not set as default in JVM - #2218
- Significant performance improvement in generating forms
- Fixed #1993 - HTML Form Entry visible to all users under Administration
- #2084 - Allow constrained options for numeric and text obs in HTML Form Entry
- Works with OpenMRS 1.6 (since encounter.provider is now a Person, not a User). Incompatible with version of OpenMRS before 1.6.
- Backported fix for bug setting time with Time widget
- Fixed Linux Velocity Errors: Failed to initialize org.apache.velocity.runtime.log.Log4JLogChute (#1953/#1960)
- Added ability to make encounterProvider default to the currently logged in user (#1925) (credit: Daniel Futerman)
- Added ability to enroll a patient in a program
- Added ability to specify encounter time (#1910)
- Bumped up the version number due to a build error, no code changes occurred
- Fixed the log4j.xml file that ships with the module so that logs can be viewed in the openmrs admin interface again
- Exactly like 1.4.0 but it attaches to the new extension point in OpenMRS 1.5.
- Incompatible with versions of OpenMRS before 1.5.0 RC1
- You may now edit a form after having entered it.
- Enable opening a form based on either formId or htmlFormId
- translations element so you can localize your form for different languages
- Fixed #1630 - htmlformentry: international characters not allowed
- support for date formatting within the velocity lookup tag
- support for translation of values within the velocity lookup tag
- localization of boolean obs, location widget, and user widget
- Support for answerCode/answerCodes in obs elements
- Widgets and elements:
- a section tag
- a repeat element which provides the ability to display a repeating section with different parameters
- a location widget to enter a locationId in valueText for concepts with text datatype
- radio button inputs for coded questions
- Support for answerClasses attribute in obs elements
- boolean obs elements can have their yes/no text customized
- encounterLocation and encounterProvider tags now allow default values
- encounterDatetime is no longer allowed to be in the future
- coded obs lists are now sorted by display name by default
- Designing forms:
- Display a Form Schema that shows concepts and the text that maps to them
- ability to view an in-progress form during design from a file on the filesystem
- fix htmlform edit page to ensure that the html form that is displayed in the textbox is first escaped correctly
- enable opening a form based on either formId or htmlFormId
- Fixed some inconsistent behavior because of an upstream bug in Concept.equals(Concept)
- Fixed #1302 - Html Form Entry module doesn't clear old error messages
- Fixed #1303 - Html Form Entry module doesn't warn you if you leave out a required encounter metadata component
- Exactly like version 1.1 except compiled with Java 1.5 compliance.
- If your session expires while entering a long form you are prompted to re-login, instead of losing your work.
- You may now fill out multiple forms simultaneously in different windows.
- Initial alpha release