Modify WF2 with new forms: F49 - F50

[AishaHassen]

Context

New forms have been added in OpenMRS that need to sync to DHIS2 under their respective programs. The current wf2-omr-dhis2 workflow was designed to handle existing programs (MentalHealth, Family Planning, Surgery...). We need to modify the workflow to accommodate the F49 - F50 forms.

Specific Request

Update wf2-omrs-dhis2 workflow to include F49 - F50 forms custom form mappings.

• branch off from staging: git checkout -b [169-new-forms]
• Create a sandbox on the msf-lime-mosul-staging project on app.openfn.org
• Connect the sandbox to this branch(169-new-forms) on git
• toggl: ACTIVE - MSF Extension 2025 [Addendum 3 - Nov]
• New Metadata file - LIME EMR - Iraq Metadata - Release 1 - v2025-12-11.xlsx

Test Data

• Create a new patient in OMRS
• Create F49 - F50 encounters for the new patient on OMRS
  See how to create encounters video here
• Trigger wf2-omrs-dhis2 workflow from Get patients steps and watch out the
  output of Get Encounters step. It should contain encounters for F49 - F50

Changes

In Events Mapping Step

• Add custom logic mapping as per mapping spec for F49 - F50 forms.

• Mapping-specs can be found here in sheets named after the form names.

• adaptor: [common@2.1.1]

• credentials: LP: ..., FN: OpenMRS Demo

In Create Events Step

When Get Encounters run successful, then Create events should run
successful. Troubleshoot any error that might be caused by the new mappings

• adaptor: [dhis2@5.0.1]
• credentials: LP: ..., FN: MSF DHIS2 UAT

Important

• How to? video links:
  • How to create encounters in OpenMRS
    video
  • How to test in DHIS2 // TODO: create loom video
• See adaptor registry cache for available versions
• Claude Project for FAQ

---

Pre-deployment Checklist (For consultants)

Before closing off this issue, ensure the following items are checked:

• Run test suite: For major releases that affect most parts of the
  workflow, run the entire test suite and ensure that it passes
• Version-locking of Adaptors: Ensure that each job is version locked to
  the adaptor versions that are specified in the
  cache registry.
• Export Configuration: Export both project.yaml (the project spec) and
  projectState and version the release
• Modify documentations and diagram: Consider if user guide, README
  docs, diagrams, and/or test suite need to be updated.
• Submit for Review on MSF github repo: Push changes to a GitHub branch
  and create a PR for MSF to review.

[AishaHassen]

@mtuchi this is ready for you. Please ping Justin if you have questions

[mtuchi]

For errors saying "Value brabra is not a valid option for dataElement
We need to use optsMap,
Currently how we map using optsMap we need two things ?

1st: externalId and matching option set (formuud-extid-formpath)

const optCodeByExtId = optsMap.find(
      (o) =>
        o["value.uuid - External ID"] === extID &&
        o["DHIS2 Option Set UID"] === matchingOptionSet
    )?.["DHIS2 Option Code"];

or
2nd: externalId and answer display value

 const optCodeByDisplayAndExtId = optsMap.find(
      (o) =>
        o["value.uuid - External ID"] === extId &&
        o["value.display - Answers"] === display
    )?.["DHIS2 Option Code"];

[mtuchi]

This is ready for QA, See latest run

[jfeldman-openfn]

Moving to Blocked due to ongoing issues with the metadata. We will picknup testing once Ludovic has resolved these config issues.

[mtuchi]

Getting this error for F49 and F50

 {
        "message": "Enrollment OrganisationUnit: `sUpt0j2GmBD`, and Program: `l3r2cXKdmuv`, dont match.",
        "errorCode": "E1041",
        "trackerType": "ENROLLMENT",
        "uid": "eGW2BVrsFUz"
      }

[mtuchi]

Hooray 🙌🏽 , This is ready for QA, @jfeldman-openfn for testing please don't create new patients, re-use my patients if possible. Also to reduce time spent analysing error logs or missing options sets i suggest we create 1 encounter for 1 patient

• F49 workflow run, F49 test patient + encounter, F49 Test Sheet
• F50 workflow run, F50 patient + encounter, F50 Test Sheet

[jfeldman-openfn]

@mtuchi I'm attaching Claude's testing feedback from F49 and F50. I haven't had time to validate that everything in the F50 testing feedback is accurate. Please can you review and action any items that you think are relevant.

It would also be VERY helpful if you could document which issues and feedback from Claude were helpful/accurate vs. which ones were not, so that I can tweak my prompts and try to improve it.

f50-validation-report.pdf
f49-validation-report.pdf

CC: @AishaHassen

[mtuchi]

Hey @jfeldman-openfn thanks for the feedback, let me get back to you on this tomorrow.

[mtuchi]

Hiya @jfeldman-openfn both F49 and F50 forms now uses questionId for mapping the answer, so the report is outdated. Can you test again and share the claude report for those two form. Please use the workflow on sandbox in this link

This is the workflow run for F49 and this is workflow run for F50