As ReportStream,
I want to define my user's HL7 validation specifications
so that they can be configured and used to ensure good HL7 data in the pipeline.
Description/Use Case
Determine what kinds of validations need to be performed for HL7 senders and receivers in ReportStream. Ideally validations can be reused across multiple senders or receivers.
Risks/Impacts/Considerations
This may require collaboration with Onboarding
This ticket is loosely coupled to #9161 which defines the structure/schema of a validationProfile
Dev Notes:
See the code example from the design ticket for examples of how to create a custom configuration.
Acceptance Criteria
[ ] Validation requirements for each HL7 sender and receiver documented
[x] Common validation schemes are identified
[x] Determined if we are going to need the validation profiles used by the current validation tool GUI and which those are.
User Story:
As ReportStream, I want to define my user's HL7 validation specifications so that they can be configured and used to ensure good HL7 data in the pipeline.
Description/Use Case
Determine what kinds of validations need to be performed for HL7 senders and receivers in ReportStream. Ideally validations can be reused across multiple senders or receivers.
Risks/Impacts/Considerations
Dev Notes:
Acceptance Criteria