Wiki cleanup in progress: If you're having trouble finding something, read these tips.

FormEntry Module

Overview

The Form Entry module is currently the main mode of data entry for OpenMRS.

Form Entry allows end user managers to design a form's content and look and then allows for end users to fill out the form and submit it to OpenMRS.

Other Resources

Example Usage

Download

Release Notes

  • 4.5.4
  • Fixed problem with duplicating forms - FORM-103
  • 4.5.3 (unreleased)
  • Improved speed for loading the patient dashboard - TRUNK-1615
  • 4.5.2
  • Added InfoPath taskpane widget for offline relationship selection - FORM-1
  • Enhanced InfoPath encounter taskpane widget to inject more data into the form - FORM-91
  • 4.5.1
  • Added ability to add relationships to form schemas - #1740
  • Added a way to insert InfoPath widgets into forms
  • 4.5
  • Made formentry Sync Module compliant. Xsns objects are now sync-able - #1983
  • Fixed duplicated form from being overwritten when using Sync module - #2351
  • 4.4.3
  • Changed to copy the standard openmrs-infopath javascript file into all XSNs upon publish - #270
  • 4.4.2
  • Fixed fix for formentry admin screen error - #2263
  • 4.4.1
  • Fixed formentry admin screen error - #2047
  • 4.4
  • Adding in fixes for formentry taskpane to point at user instead of person - #2033
    -New line of releases for all OpenMRS 1.6+ versions-
  • 4.3.2
  • Fixed fix for formentry admin screen error - #2263
  • 4.3.1
  • Adding in fixes for formentry taskpane to point at user instead of person - #2033
  • 4.3
  • Fixed a remoteformentry incompatibility with xforms bug archive:TRAC-1934
  • 4.2.1
  • Fixed relationships object to contain patient objects if they exist
  • 4.2
  • Added "relationships" velocity scripting option to form schema
  • 4.1.2
  • Fixed InfoPath schema incorrectly storing the selected name in both sides of the HL7 sextuplet archive:TRAC-1594
  • 4.1.1
  • Fixed taskpane js to load the DWRUserService property correctly. See archive:TRAC-1689
  • 4.1
  • Reverted infopath files to just use triplets. See archive:TRAC-1404
  • 4.0
  • Added compatibility with the new FormEntryHandler extension point that combines the multiple form-entry type of modules forms into one place
    -New line of releases for all OpenMRS 1.5+ versions-
  • 3.7
  • Fixed a remoteformentry incompatibility with xforms bug archive:TRAC-1934
  • 3.6.9
  • Fixed InfoPath schema incorrectly storing the selected name in both sides of the HL7 sextuplet archive:TRAC-1594
  • 3.6.8
  • Fixed taskpane js to load the DWRUserService property correctly. See archive:TRAC-1689
  • 3.6.7
  • Reverted infopath files to just use triplets. See archive:TRAC-1404
  • 3.6.6
  • Fixed utf-8 characters in basic form
  • 3.6.5
  • Fixed taskpane concept name error
  • 3.6.4
  • Fixed call to deprecated method so method works in 1.5
  • 3.6.3
  • Added global property formentry.infopath_taskpane.showAllUsersOnLoad to turn on/off automatic user display in the infopath taskpane
  • 3.6.2
  • Fixed form searching on dashboard to not show garbled text when no forms are found
  • 3.6.1
  • Added a few helpful error messages if errors occur while rebuilding a form
  • 3.6
  • Added changes for concept name searching/saving to obs
  • Added fix velocity errors from forms
  • Fixed required text fields error in Infopath
  • 3.3.2
  • Added delay to Infopath taskpane user search page to fix a bug with the latest trunk code
  • 3.3.1
  • Fixed startup options to actually look at the global properties before warning about their deprecation
  • 3.3
  • Added taskpane widget to select past encounters - How to use the encounter widget
  • Added taskpane widget to add relationships to patients - How to use the relationship widget
  • 3.2
  • Adding option for extra information for question concepts being filled in by normal infopath form (non-taskpane)
  • 3.1
  • Upgraded formentry module to work with OpenMRS version 1.3

Troubleshooting

  • When using FormEntry Module in a non-Windows environment (one that uses cabextract), do not adjust Tomcat memory usage to greater than 4GB. See archive:Ticket # 1987.

Developers

[Ben Wolfe], [Burke Mamlin]

Labels

moduledocumentation moduledocumentation Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.