(docs): Document FDE integration with RFE/AFE and pre-filled questions#141
Merged
samuelmale merged 2 commits intoopenmrs:mainfrom Sep 2, 2025
Merged
(docs): Document FDE integration with RFE/AFE and pre-filled questions#141samuelmale merged 2 commits intoopenmrs:mainfrom
samuelmale merged 2 commits intoopenmrs:mainfrom
Conversation
Contributor
Author
|
CC @samuelmale |
samuelmale
reviewed
Aug 25, 2025
README.md
Outdated
| * Identify **which forms** the question applies to. | ||
| * Point to the **question ID** within the form schema. | ||
| * Optionally define a **default answer**. | ||
| * Optionally limit the set of **answer choices** (for multi-select fields). |
Member
There was a problem hiding this comment.
(for multi-select fields).
Does this only apply to multi-select inputs or all coded inputs, such as drop-downs?
Contributor
Author
There was a problem hiding this comment.
Ah, slipped past me — Great observation.
README.md
Outdated
| * **`forms`**: Array of form UUIDs. The pre-fill rule applies only to these forms. | ||
| * **`questionId`**: The field identifier in the form schema to pre-fill. Must exist in the published form schema. | ||
| * **`defaultAnswer`** *(optional)*: A concept UUID or value to use as the default answer. | ||
| * **`answers`** *(optional, multi-select only)*: Array of concept UUIDs to restrict the available answer options. |
README.md
Outdated
| - [Form Engine App](https://github.com/openmrs/openmrs-esm-patient-chart/tree/main/packages/esm-form-engine-app) | ||
| - [Form Entry App](https://github.com/openmrs/openmrs-esm-patient-chart/tree/main/packages/esm-form-entry-app) | ||
|
|
||
| ⚠️ **Important**: Only one wrapper can be active in a distribution. A distribution must choose either the **React-based** or **Angular-based** engine, depending on its architecture. |
Member
There was a problem hiding this comment.
Well, there are O3 distribution(s) using the HTML Form Entry (HFE) engine. That being said, let's rephrase the above statement to echo that the FDE feature is currently limited to JSON schema-based engines, etc..
Contributor
Author
There was a problem hiding this comment.
Caught me there — thanks!
Does that mean that the such distributions don't have hopes of using the FDE module?
CC @samuelmale @ibacher
samuelmale
approved these changes
Sep 2, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requirements
Summary
Proceeding from Fix FDE for RFE forms instances, this PR updates the README.md to highlight the flexibility of FDE with both Angular and React form engines and adds detailed documentation for pre-filled/specific questions.
Screenshots
Related Issue
Other