JohnNKing commented 1 month ago

Bug

Describe the Bug

We've identified a few issues with OBX mapping for the CA sample ORU: https://github.com/CDCgov/trusted-intermediary/blob/main/examples/CA/002_CA_ORU_R01.hl7

~~OBX.2 of TN is rejected by RS (and if changed to XTN, OBX.5 is lost)~~
- To confirm with CDPH if this would be used for UCSD
OBX.2 of CE are losing OBX.3 and OBX.5
- Confirmed that data is lost when converting HL7 => FHIR
- Mappings for OBX.3 and OBX.5 are here: prime-router/metadata/HL7/catchall/hl7/segments/OBX/Observation.yml
- RS is looking into this issue
OBX.6: For μmol, 'μ' has an incorrect encoding in the resulting HL7
- Fixed in PR #1134

Impact

This will prevent integration with CA.

To Reproduce

Submit the sample ORU (https://github.com/CDCgov/trusted-intermediary/blob/main/examples/CA/002_CA_ORU_R01.hl7) to ReportStream.

Expected Behavior

The content of the input and output HL7 matches

Screenshots

n/a

Logs

n/a

Version

Current main

Additional Context

Related backlog items:

905
1071

JohnNKing commented 1 month ago

Attempting to confirm if TN data type support is a requirement: https://www.slack.com/archives/C044P2CBEKS/p1717695906835449?thread_ts=1717623207.357699&cid=C044P2CBEKS

basiliskus commented 1 month ago

I just found out that the CE OBX mapping issue is a known bug in RS. A ticket will be created and someone from RS will take a look next week: https://flexion.slack.com/archives/C048S3GPSQG/p1717795087843699?thread_ts=1717793348.863279&cid=C048S3GPSQG

basiliskus commented 4 weeks ago

A ticket to address the OBX CE issue was created in RS: https://github.com/CDCgov/prime-reportstream/issues/14685

basiliskus commented 3 weeks ago

Waiting for RS to look into this issue. Tagged as blocked

jorg3lopez commented 3 weeks ago

Findings:

HL7-2.5.1 supports CE datatype for OBX.2
HL7-2.7 does not support CE datatype for OBX.2
The issue happens when HL7 -> FHIR translation occurs. If OBX.2 has CWE, the FHIR resource comes with a coding resource as part of the Observation resource. This coding resource is used to populate OBX.3 and OBX.5, and this resource is missing when OBX.2 has CE as the datatype.

CWE datatype:

CE datatype:

jorg3lopez commented 3 weeks ago

Worked together with Josh Fisk from Report Stream to fix this issue. Findings: RS turns all CE datatypes for OBX.2 into CWE. Reason being, some clients have a hybrid message with v251 and v27 configurations. To address this problem, RS uses the v27 model to parse the file.

CE to CWE: