CDCgov / trusted-intermediary

Bringing together healthcare providers by reducing the connection burden.
Apache License 2.0
11 stars 5 forks source link

CA Round-Trip Testing #1110

Open JohnNKing opened 5 months ago

JohnNKing commented 5 months ago

Story

As a PHL or HCO, so that we're confident the various branches of our workflows will work under ETOR, we need to test various scenarios of NBS results between partner systems (e.g. EHR, LIMS).

Pre-conditions

Acceptance Criteria

Tasks

Test Case Scenarios (link to master test scenarios sheet)

Definition of Done

Research Questions

Decisions

Notes

GilmoreA6 commented 1 week ago

For Task "Track down cause of 3 undelivered sample messages on 10/16" - -We've confirmed that two of the 3 messages that didn't route due to absence of ORC-21-10 that is used for filtering reports on the RS side and for identifying messages for applying the USCD transform in ETOR-TI. -The third message did not route due to an exception when attempting to parse the fhir bundle in RS for element Bundle.entry.resource.ofType(Observation).ValueQuantity.value of "065.88" where exception " ca.uhn.fhir.parser.DataFormatException: HAPI-1861: Failed to parse JSON encoded FHIR content: Invalid numeric value: Leading zeroes not allowed at [line: 1, column: 137695]" was thrown. The problematic value was converted from the OBX-5 value from the OBX segment: OBX|1|NM|38473-5^17-Hydroxyprogesterone^LN|1|0065.88|nmol/L|<85|N|||F|||202410150557

scleary1cs commented 1 week ago

"Determine if ORC-21-10 data issue was an artifact of testing, or if modification of the filters will be required"

We received a verbal and email confirmation that this data issue will not effect Prod.

"Two of the test messages are missing ORC-21.10. This value is critical for routing - can CDPH confirm it will always be populated in production? Sumitha, can you please answer this question? – Yes it will be always populated in PROD." Subject = "Vocabulary Clarifications for ETOR Intermediary"

kwright-bio commented 1 week ago

Confirmed in SME call that 2b was ingested into the system. Can mark as complete once receiving a PDF from UCSD. TCs 1, 7A, and 4 have had successful ingestion into UCSD but prior to the mu fix being implemented. These messages can likely be redropped and resent to UCSD and get confirmation the mu character looks good in final PDF exports for these (confirm this plan with team / HCO)

kwright-bio commented 1 week ago

Also a note that the CDPH generated results being used in testing are from a custom-built test result generator and not their SpecimenGate system.

scleary1cs commented 1 day ago

@kwright-bio and @dbgolson happy to circle back here and update the test cases based on what was just shared at Sprint Review.

kwright-bio commented 18 hours ago

Added the newly created Indeterminate test cases. Note that 2b's comparison uncovered an issue where likely they have not mapped a code correctly.