Closed GilmoreA6 closed 1 week ago
slack thread with SR "Hey there SR. Per Ellaison's email from earlier, I've tracked down the issue with the OBR-25 not being populated and it looks like we are receiving a value "entered-in-error" for diagnosticReport.status (which is a valid value in FHIR). The problem is that that FHIR -> HL7 mapping maps "entered-in-error" to HL7 value "W" from table HL70085 (https://hl7-definition.caristix.com/v2/HL7v2.5.1/Tables/0085). Table HL70085 is only used for OBX-11 result status not OBR-25 in HL7 v2. OBR-25 uses table HL70123 (https://hl7-definition.caristix.com/v2/HL7v2.5.1/Tables/0123) which does not have "W" available as an option. My question is what is actually occurring when we receive the value "entered-in-error". Are users indicating a previous result was incorrect?"
response from SR "I’ll need to dig into the mapping to verify but my initial thought is that this is likely the correction flow. edit: to clarify this is in response to James’ original question. (edited) "
PR for fix added #15726
Message from Ellaison:
'We had a few NAK’d results missing OBR-25 which is the order status field (typically F for final). Are you guys receiving those with the REST connection? If so, are you monitoring and resolving the errors? An example from Aug 22 was accession # 6e6ba575-5211-46f5-b9fa-9ae98fd55c49 '.