In order to receive monkeypox files/data that labs have for us while the API is being worked, we need to adjust the /validate page to be more of an /hl7 page with two paths: "validate" and "upload". Naming TBD since it would accept CSV and HL7 🤔
What you need to know
For MVP, this would just be for internal users, but we might want to open it up to labs (4) that are sending up monkeypox data very soon.
A new sender (or multiple senders) would be created to handle the schema mappings, etc
We have to be extra careful to separate concerns enough that a user wouldn't accidentally upload a file when they're trying to just validate
Assumptions
The new sender(s) and schema will be set up for us
The new sender schema is permissive enough to let files through appropriately
Acceptance criteria
[ ] There are two routes a user can visit:
[ ] upload to upload an HL7 file for ingestion by the pipeline
[ ] validate to validate a file without saving any data (separate endpoint pending as part of #5713)
[ ] new upload route is separate from old csv uploader path /upload that is being deprecated
[ ] upload & validate use some shared components (streamline & reduce duplicate code)
Problem statement
In order to receive monkeypox files/data that labs have for us while the API is being worked, we need to adjust the
/validate
page to be more of an/hl7
page with two paths: "validate" and "upload". Naming TBD since it would accept CSV and HL7 🤔What you need to know
Assumptions
Acceptance criteria
upload
to upload an HL7 file for ingestion by the pipelinevalidate
to validate a file without saving any data (separate endpoint pending as part of #5713)upload
route is separate from old csv uploader path/upload
that is being deprecatedupload
&validate
use some shared components (streamline & reduce duplicate code)To do