Wiki Spaces


Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack


Page tree
Skip to end of metadata
Go to start of metadata

Gap Analysis




ThemeFeatureCurrent StateFuture State (with 3.x)StatusPriorityNotes/Comments
FormsBasic obs capturecapture observations based on concepts in dropdowns, text boxes, check boxes, radio buttons etc... support auto-suggest


Formsobs commentscapture obs comments (e.g. when selecting an "other" choice, may want to allow user to enter text and have it saved in the comment)

Formslabeling/unitsflexible question labeling (different than concept name) and units display


Althougt this works, I think there is an opposite issue: it doe not  support using the concept name, only a custom label. Tickets here:   O3-2128 - Getting issue details... STATUS

Formsrequired fieldsability to make fields required to save form


FormsSkip logic/hiding exposing questions/sections

Ability to default questions or sections as hidden until a box is checked which would expose them

Formssingle field data validationsprevent entry of data outside of a certain range to be entered

O3-1931 - Getting issue details... STATUS (ticket may need review to make sure it covers all our use caess)

FormsFlexible question formatting ability to format questions (checkboxes/radio buttons/text boxes/dropdowns) in multiple columns or tables 

Note: the Form Engine has been deliberately designed not  to this, may require debate, see Ian's first response here:
Formstext displaydisplay of informational "helper" text. tooltips

Formscreate orderability to create orders (labs, meds, radiology etc..) from within forms

We should consider whether the proper way to do this is to support seamlessly rediercting to the Order Basket, see discussion here:
FormsOrder renew/revise/discontinueability to renew/revise/discontinue active orders within forms

Formsobs group capturecapture obs in a group 

Looking at the code, there's definitely support for this built-in, but we will need to dig deeper to see how it works; specifically, I suspect there may need to be better mapping between obs and forms when editing an encounter
FormsRepeating Sectionsability to capture 1 to many obs or groups (e.g. diagnoses)

FormsReuse sectionsability to reuse a section across multiple forms (e.g. MCH and Pediatric form both may have a vaccination section)

This is a core feature build into React Forms, though we should explore to make sure it meets our needs, see:
Formstranslationslabels, units and other text to be shown in chosen locale


O3-2129 - Getting issue details... STATUS

Formsprogram enrollment/managementability to enroll/complete patient program or modify patient program workflow status

A discussion about this was started here:

We should probe further

Formsdisplay past valuesdisplay past captured obs for a patient.  E.g. show latest vitals for a patient within a form

Formsdiagnosis captureeasily usable diagnosis capture including auto-suggest, non-coded entry, 1-many diagnoses, associated obs in groups (order, certainty etc...) 

Formsautomatic navigationability to force user to navigate to other forms/pages after submitting.  E.g. navigate to "mark patient deceased" after entering disposition = death 

It's possible this might tie into solutions presented here:
Formsrestrict forms avaialbleWe need to be able to config which forms are available in any specific implementation.  (Currently I think the UI simply displays all forms that are configured in the system)

Could this/should this be a configuration parametmer in the esm-form-entry-app or esm-form-entry-engine in the Patient Chart?
Formsrestrict forms based on context

restrict forms based on:

  • privileges
  • location
  • other forms that have been entered (e.g. only allow 1 followup per visit, only allow followup after intake completed etc....)

Formedit formsWe need to have the ability to edit previously-entered forms.  This appears to be possible, but via the UI I'm only seeing how to edit the most recent form of a certain type added for patient

Form view formsWe need to have the ability to view previously-entered forms

FormCalculations within formbe able to flexibly calculate values within forms (e.g. BMI, EDD from LMD)

There is support for this within React Forms, though we need to confirm that it meets our needs as currently designed:
FormReferences by mappingWe need to be able to reference concepts by mapping when buiilding forms

O3-2127 - Getting issue details... STATUS

FormImproved developer experienceWe need to improve the developer experience of forms.  Namely, we need an easy way for devs to build forms in their IDE and upload them to the form builder for testing/review.

(PIH ticket:

Will add O3 ticket once this is fleshed out

FormSpecify encounter roleWithi a form schema, we'd like to be able to specify the encounter role of the provider filling out the form.  Right now the encounter role automatically set to the role with the name "Clinician", and if there is no role with that name, it just picks the first role returned by the REST endpoint

Form Specify encounter provider

I believe the form engine always sets the encounter provider to the current user.  For retrospective entry, we'd need to be able to set the provider to a specific provider via a dropdown list and/or provider search (and be able to restrict that list/search by provider type)

FormSpecify encounter location

It looks like the encounter locaiton is set to the session location, though there may be more support for tweaking this.

We would want the encounter location to default to the session location, but be editable (at least in some cases)

Circular workflow stuff




  • No labels