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.