TWIINE-117.JPG

Contact


📞 +256 771250497

✉️ twiineenockfox**@gmail.com**

Github:

Twiineenock - Overview

Linkedn: https://www.linkedin.com/in/twiine-enock-264b6b280/

OpenMRS Talk:

twiine

Interests


🔢 0s & 1s

🏀 basketball

📚 Reading

Languages


🇬🇧 English

<aside> <img src="/icons/cactus_orange.svg" alt="/icons/cactus_orange.svg" width="40px" />

<aside> 💡

🧑🏾‍💻 Introduction

</aside>


I'm glad to be a GSoC intern with OpenMRS, working on updating the Fast Data Entry (FDE) app to be compatible with the O3 RefApp, which uses the React-based esm-form-engine-app. The goal is to enhance the React Form Engine (RFE) to support FDE workflows—without hardcoded changes to FDE itself—so it remains compatible with both the React and Angular engines.

As part of this, I explored key FDE workflows like single-patient form entry and group sessions to understand their original design. In doing so, I discovered that some workflows are currently broken or inconsistent.

I'll highlight these issues below and would appreciate input from anyone still using the Angular Form Engine:

Are these issues consistent for you as well?

</aside>

Fix the Fast Data Entry feature (GSOC 2025) - Projects - OpenMRS Wiki

My Mentors

samuel34

ibacher

Nature of current workflows


fill form.png

🧾 Fill Form for a Single Patient

I’ve observed that this workflow breaks when attempting to fill a form for a patient with an active visit—triggering errors like "colliding visits." However, the form submits successfully if the patient does not have an active visit.

Question for users of the Angular-based esm-form-entry-app:

Do you experience this same behavior, or might you be using a different version or configuration of the app?

Screenshot 2025-06-04 at 11.39.39.png

👥 Group Session Workflow

In this workflow, most forms don’t open, and for the few that do, submissions fail. Key action buttons like Next Patient and Save are also non-functional, making the workflow unusable within the FDE.

Additionally, pre-filled questions are not showing up as expected.

I'm curious to know if others using the Angular esm-form-entry-app experience the same issues. If not, it would be helpful to understand how this workflow is expected to function—possibly through access to a working test environment—so I can properly validate behavior as I integrate it with the React Form Engine.

My Experimental Observations


I've recorded a few videos demonstrating my findings while working with the FDE using the Angular Form Engine. You can find them below.

Single form workflow

<aside> 💡

https://vimeo.com/1090405071/dfb6f8b70a

</aside>

Group session workflow

<aside> 💡

https://vimeo.com/1090408933/b103e318ee

</aside>


Pre-filled form questions workflow

<aside> 💡

https://vimeo.com/1090409626/d8c1ad2df9

</aside>

Stack


Skills