Business Requirements for process orchestration

[dcdlz]

Context

HL7 message processing follows the same general flow...

1. Receive/Debatch
2. Redact
3. Structure Validate (with NIST IGAMT)
4. Normalize to a Data Product

The application code for (1), (2) and (3) should be identical for all HL7v2 messages. For the pedants:

• (2) identical application code; redact config changes
• (3) identical application code; IGAMT input varies

However, the normalize to data product will differ depending on the purpose of the HL7v2 message. For example Case Notification messages vs Laboratory messages

Requirements

1) We should be able to orchestrate functions into pipelines, such that the pipelines can i) change and ii) reuse Functions

[rmharrison]

Solutioning: Orchestration

Current state: Orchestrated from EventHub queues.

Potential options for "config-based" orchestration...

• Azure Logic Apps: https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-overview
• Durable Functions: https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-overview?tabs=csharp