My name is Raghav Goel, and I am excited to join the OpenMRS community as a GSoC 2026 aspirant. I’ve been following the project ideas and am particularly drawn to the Forms Migration Tool: Help HTML Form users switch to using O3 React Forms.
Why this project? I have a strong background in Node.js and React. Interestingly, I recently built a multi-step health form component for a separate project, so I am very familiar with the complexities of structuring clinical data into a user-friendly, step-by-step experience.
My Progress so far:
I’ve cloned the hfe-o3-form-schema-converter repository to understand the current Java/JavaScript logic.
I’m currently reviewing the differences between the Angular Form Engine (AFE) and React Form Engine (RFE) schemas.
I’ve been reading through the O3 documentation on the React Form Engine library.
I’m looking forward to contributing to the migration from HFE to O3, especially for organizations like Partners In Health (PIH) that have a significant library of legacy forms.
Could anyone point me toward any recent discussions or “good first issues” related to the converter script or the RFE schema?
I’m Abdullah Kamel, an IT student from Egypt, and I’m very excited about the “Forms Migration Tool” project. While I appreciate the work being done in JS/React, I believe a Python-based automation approach can significantly speed up the migration of legacy HFE forms.
My Progress so far:
Prototype Development: I’ve already built a Python prototype using BeautifulSoup and Regex to parse legacy HTML tags and map them directly to the O3 React Form Schema.
Field Mapping: Successfully automated the conversion of encounterDate and obs tags, including complex dropdown logic.
Gold Badge Python Developer: I’m leveraging my problem-solving experience (HackerRank Gold Badge) to ensure data integrity during migration.