| Forms |
restrict forms based on context |
restrict forms based on:privileges location other forms that have been entered (e.g. only allow 1 follow-up per visit, only allow follow-up after intake completed etc....) |
GAP |
High |
|
|
|
|
|
| Forms |
Basic obs capture |
capture observations based on concepts in drop downs, text boxes, check boxes, radio buttons etc... support auto-suggest |
READY |
|
|
|
|
|
|
| Forms |
obs comments |
capture obs comments (e.g. when selecting an "other" choice, may want to allow the user to enter text and have it saved in the comment) |
GAP |
High |
MG: I'd debate whether this is necessarily a high priority |
|
|
|
|
| Forms |
labeling/units |
flexible question labeling (different than concept name) and units display |
READY |
|
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 - Form Engine: support translation/localization in labels TO DOO3-1903 - React Form Engine MVPIN PROGRESS |
|
|
|
|
| Forms |
required fields |
ability to make fields required to save form |
READY |
|
|
|
|
|
|
| Forms |
Skip logic/hiding exposing questions/sections |
Ability to default questions or sections as hidden until a box is checked which would expose them |
|
High |
MG: I believe this is supported but need to test further |
|
|
|
|
| Forms |
single field data validations |
prevent entry of data outside of a certain range to be entered |
GAP |
High |
https://issues.openmrs.org/browse/O3-1931 - Form Engine: Get the Absolute high and low values from a concept. TO DO(ticket may need review to make sure it covers all our use caess) |
|
|
|
|
| Forms |
Flexible question formatting |
ability to format questions (checkboxes/radio buttons/text boxes/dropdowns) in multiple columns or tables |
GAP |
High |
https://talk.openmrs.org/t/react-forms-form-builder-questions/39663https://talk.openmrs.org/t/react-forms-form-builder-questions/39663 |
|
|
|
|
| Forms |
text display |
display of informational "helper" text. tooltips |
|
High |
MG: There may be support for this. I need to confirm |
|
|
|
|
| Forms |
create order |
ability to create orders (labs, meds, radiology etc..) from within forms |
GAP |
Low |
https://talk.openmrs.org/t/react-forms-form-builder-questions/39663https://talk.openmrs.org/t/react-forms-form-builder-questions/39663 |
|
|
|
|
| Forms |
Order renew/revise/discontinue |
ability to renew/revise/discontinue active orders within forms |
GAP |
Low |
|
|
|
|
|
| Forms |
obs group capture |
capture obs in a group |
READY |
|
There is support for this within the current form engine, and I've tested it and it generally works for entering and editing, though I haven't tested complex use cases. It relies on the underlying id of each field to set the form-schema-and-path. It does set any form-schema-path on the grouping concept, so the id of each child element must be unique across the entire form. |
|
|
|
|
| Forms |
Repeating Sections |
ability to capture 1 to many obs or groups (e.g. diagnoses) |
READY |
High |
https://issues.openmrs.org/browse/O3-2166https://issues.openmrs.org/browse/O3-2166 - Form Engine: Repeating Obs Not re-displayed properly TO DO |
|
|
|
|
| Forms |
Reuse sections |
ability to reuse a section across multiple forms (e.g. MCH and Pediatric form both may have a vaccination section) |
|
High |
https://ampath-forms.vercel.app/docs/core-concepts/componentshttps://ampath-forms.vercel.app/docs/core-concepts/components |
|
|
|
|
| Forms |
translations |
labels, units and other text to be shown in chosen locale |
GAP |
Medium |
https://issues.openmrs.org/browse/O3-2128 - Form Engine: support translation/localization in labels TO DO |
|
|
|
|
| Forms |
program enrollment/management |
ability to enroll/complete patient program or modify patient program workflow status |
GAP |
Low |
https://github.com/openmrs/openmrs-form-engine-lib/issues/78https://github.com/openmrs/openmrs-form-engine-lib/issues/78We should probe further |
|
|
|
|
| Forms |
display past values |
display past captured obs for a patient. E.g. show latest vitals for a patient within a form |
|
High |
|
|
|
|
|
| Forms |
diagnosis capture |
easily usable diagnosis capture including auto-suggest, non-coded entry, 1-many diagnoses, associated obs in groups (order, certainty etc...) |
GAP |
High |
|
|
|
|
|
| Forms |
automatic navigation |
ability to force user to navigate to other forms/pages after submitting. E.g. navigate to "mark patient deceased" after entering disposition = death |
|
High |
https://github.com/openmrs/openmrs-form-engine-lib/issues/78https://github.com/openmrs/openmrs-form-engine-lib/issues/78 |
|
|
|
|
| Forms |
restrict forms avaialble |
We 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) |
GAP |
High |
Could this/should this be a configuration parametmer in the esm-form-entry-app or esm-form-entry-engine in the Patient Chart? |
|
|
|
|
| Form |
edit forms |
We 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 |
GAP |
High |
|
|
|
|
|
| Form |
view forms |
We need to have the ability to view previously-entered forms |
GAP |
High |
|
|
|
|
|
| Form |
Calculations within form |
be able to flexibly calculate values within forms (e.g. BMI, EDD from LMD) |
|
High |
https://ampath-forms.vercel.app/docs/performing-calculationshttps://ampath-forms.vercel.app/docs/performing-calculations |
|
|
|
|
| Form |
References by mapping |
We need to be able to reference concepts by mapping when buiilding forms |
GAP |
High |
https://issues.openmrs.org/browse/O3-2127 - Form Engine: Support referencing concepts by mapping CANCELLED |
|
|
|
|
| Form |
Improved developer experience |
We 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. |
GAP |
High |
https://pihemr.atlassian.net/browse/UHM-7212https://pihemr.atlassian.net/browse/UHM-7212)Will add O3 ticket once this is fleshed out |
|
|
|
|
| Form |
Specify encounter role |
Withi 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 |
GAP |
High |
|
|
|
|
|
| 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) |
GAP |
High |
|
|
|
|
|
| Form |
Specify 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) |
GAP |
High |
|
|
|
|
|