Modify WF2 to include new forms F59 - F63

[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 F59 - F63 forms.

Specific Request

Update wf2-omrs-dhis2 workflow to include F59 - F63 forms custom form mappings.

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

Test Data

• Create a new patient in OMRS
• Create F59 - F63 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 F59 - F63

Changes

In Events Mapping Step

• Add custom logic mapping as per mapping spec for F59 - F63 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 Custom mapping is missing for these forms. Waiting on Ludovic. Will confirm when they are available and you should be able to start then

[AishaHassen]

@mtuchi the mapping logic is ready for this

[mtuchi]

Ludovic address the missing header in OptionSet sheet. And i was able to regenerate the mappings for LIME EMR - Iraq Metadata - Release 1 - v2025-11-14.xlsx. See run here

[mtuchi]

Will sync with @AishaHassen to translate Map with stage 'Discharge' (stage UID = 'sBepdVG2c9O')

[mtuchi]

@AishaHassen couple of questions

• F59 to F63 forms are not enabled in metadata file, Should i enable these forms ?
• I don't see a programStage in F61 custom mapping is that accurate or we need to update the transformation notes ?
• In F62 custom mapping i am seeing two programStage id [YivvTlIw5Ep, Otoff7Cj8JQ] is this accurate ?
• Have you confirmed with Ludovic why F63 custom mapping is the same as F62 mapping ?

[mtuchi]

Facing an error on Create Teis Relationship Step:

{
  "httpStatus": "Internal Server Error",
  "httpStatusCode": 500,
  "status": "ERROR",
  "message": "element cannot be mapped to a null key"
}

[mtuchi]

For F62 and F63 build hospitalisationEvent() similar to buildExitEvent but the difference is it will create an event for each program stage

[mtuchi]

Hiya @AishaHassen i have pushed the latest change on main sandbox. for both WF2 and WF3. You should be able to test now. But just the heads up WF2 i am still blocked on with this error message

{
        "message": "Provided Program: `od0M4kEn5Rp`, is a Program without registration. An Enrollment cannot be created into Program without registration.",
        "errorCode": "E1014",
        "trackerType": "ENROLLMENT",
        "uid": "zOLsiBAhhvp"
      }

So i was not able to run the whole workflow

[mtuchi]

See feedback here #166 (comment)

[mtuchi]

Changes for F59-F63 have been deployed to staging