feat(#167): Add Subscription and Feedback workflow with OpenIMIS

[sugat009]

Description

Adds Subscription of Claim resource of OpenIMIS. Also, later on added support on processing the Claim resource Provided by OpenIMIS and then, sending back the feedback data on the same Claim resource back to OpenIMIS as Communication resource.

#167

This PR will be in draft because the task is still in POC phase. The tests in the CI is failing as well because they are not true unit tests. They will be converted once this task takes some form of finalization.

Code review checklist

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or e2e where appropriate
• Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[witash]

There is a function for creating subscriptions in utils/fhir.ts

It is used in the loss to follow up workflow, for what seems to be a similar use case.
Instead of creating new functions for OpenIMIS specifically, can we use that, or, if not, modify it to make it more generic?

[sugat009]

There is a function for creating subscriptions in utils/fhir.ts

It is used in the loss to follow up workflow, for what seems to be a similar use case. Instead of creating new functions for OpenIMIS specifically, can we use that, or, if not, modify it to make it more generic?

That function is not reusable at all for OpenIMIS use-case but I could make the createSubscriptionPayload and subscribe or other functions more generic. Should these generic functions be put in the fhir.ts file or somewhere else?

[witash]

I could make the createSubscriptionPayload and subscribe or other functions more generic. Should these generic functions be put in the fhir.ts file or somewhere else?

Yea, the idea is not to have LTFU subscription and OpenIMIS subscription and OpenMRS subscription but a single subscription that works for any fhir api. could put it in fhir.ts or maybe create another utils file if it makes sense.

[sugat009]

@witash I've refactored createFHIRSubscriptionResource function from mediator/src/utils/fhir.ts as a single function that will request the Subscription endpoint. I've left the generateFHIRSubscriptionResource from mediator/src/utils/fhir.ts and createFhirSubscriptionPayload from mediator/src/utils/openimis.ts because they are creating payloads from the passed params for different things.

[witash]

Can we use the types from the fhir module here instead of redefining them?