scleary1cs commented 5 months ago

Design or Research

Consolidate and document results handling sample messages from all resources per state.

Completion Criteria

[x] understanding how or if RS can ingest ORU messages (LRIv3)
- nearly complete looking into this
[x] determine things maintained in 2.5.1 that are only for compatibility
- everything looked into should work in 2.5.1, need to work with RS to ensure it can support these items
[x] comparison of results messages from different partners - are there differences between partners in the examples we have
- comparison has been done and no appreciable differences noted

[x] NBS not generic
[x] 2.5.1 only (not 2.3)
[x] Data types (what is the impact)
- [x] Work with RS to see what can be supported or modifications to RS to support (Raised during RS Architecture Sync; likely that our team would need to extend ReportStream capabilities)
- [x] Test datatypes from https://docs.google.com/spreadsheets/d/1KwuWj6tEAnyv2hIpDisQKaL5gO45aIwo/edit#gid=1760364417 with existing ReportStream capabilities @JohnNKing

See https://docs.google.com/spreadsheets/d/1KwuWj6tEAnyv2hIpDisQKaL5gO45aIwo/edit#gid=2006287034
On the whole, these don’t cause outright failures — in contrast to ‘TN’ or bogus data types that do fail (HTTP 400 w/ JSON encoded error message).
Data lose during the HL7 to FHIR transformation varies. ‘CE’ actually seems to work fine, despite causing a warning. ‘NM’ has no warnings, but seems to lose OBX.3 and OBX.6. This is likely due to incomplete mappings.
I presume the place to update mappings in the future is https://github.com/CDCgov/prime-reportstream/tree/master/prime-router/metadata/fhir_mapping/hl7/datatypes