As a report stream sender,
I would like my RadxMars OTC compliant message to be processed through the pipeline losslessly
so that receivers receive all the data I submitted
Note: This ticket should NOT do anything related to de-identification
Risks/Impacts/Considerations
Dev Notes
Step one is to create a test that verifies the UP can process a maximally configured RadxMars message, meaning it can translate RadxMars 2.5.1 -> FHIR -> RadxMars 2.5.1 without losing any data.
IF NEEDED: Step two is to update the catchall mappings so that the above test passes
Acceptance Criteria
[ ] RADxMARS OTC 2.5.1 message can be translated to and from FHIR without losing data
User Story
As a report stream sender, I would like my RadxMars OTC compliant message to be processed through the pipeline losslessly so that receivers receive all the data I submitted
Description/Use Case
Implement mappings for RadxMars OTC:
See RadxMars software requirements document section: II. Translation support
Note: This ticket should NOT do anything related to de-identification
Risks/Impacts/Considerations
Dev Notes
RadxMars 2.5.1 -> FHIR -> RadxMars 2.5.1
without losing any data.Acceptance Criteria