What needs to be done

Create a new /process-message endpoint on the eCR Viewer, to replace the one that exists today in Orchestration.

Please keep the method signature / parameter names of the existing Orchestration endpoint. This endpoint will be used directly by our users as they call the pipeline, so it's important not to change this too drastically for them. Some params may not longer be necessary, but for the ones that are shared, please keep the names the same.

Why it needs to be done

We want this endpoint to be protected by the viewer's authentication.

Acceptance Criteria

• New /process-message endpoint exists on eCR Viewer
• New endpoint should:
  • Accept eICR and RR in the request body, like orchestration does today
  • Determine which orchestration configuration is applicable based on eCR Viewer environment variables (AWS, Azure, integrated, non-integrated, etc)
  • Send the eCR and RR to the orchestration service for processing
  • Accept the orchestration response
  • Save eCR data from orchestration (to S3, SQL Server, etc)

Technical Notes

Additional context