Meeting Name: | ELR Open Call #138 | Moderator: | Brooke Beaulieu | ||
Date: | Thursday, June 27, 2024 | Notes: | Ray Lewis | ||
Duration: | Attendees: |
| |||
Zoom Link: | Meeting Zoom Link Meeting ID: 940 4241 0458, Dial: (312) 626-6799 | ||||
Recording Link: | |||||
Zoom Chat Notes: | |||||
Propose Topics | |||||
Past Meeting Recordings & Notes | |||||
Agenda | ||
|---|---|---|
Presenter/Facilitator | Topic | Question(s)/Comments |
Tim Longo | Quest IFD - Implementation Status Update | Nicole Stuver (Kikuchi) TN DOH-#1-In the scenario where they did not allow the message to pass validation and it was not sent to the PHA’s, would Quest’s SOP be to follow up with the client to obtain that DOB so that it can be populated and sent to PHA later? Kimberly-In the past they have made every attempt to reach the providers for anything that is missing or causing errors to go through. It would not be one SOP item because there are at least 3 or more interfaces and LIS’s in Quest as a nation. They will attempt to do everything that they can to contact but it is rather difficult to obtain a response from each provider. It would be significantly delayed Tim Tubman-The DOB is generally something that gets called to their clients when it’s missing. They usually don’t delay testing because it is time-critical. When they’re waiting to do that, the result gets released and then eventually fails. When this happens, they are placed in the bucket to be manually re-queued once the PHC’s can obtain that DOB. There are circumstances where you can’t obtain communication from the ordering provider and then they can’t report the result. #2-If this is a required field for an HL7 message, has there been in discussion on the client side for requirements? Tim T.-This is currently a rare event, and it is a required field (in which they will have to place something like unknown or ungiven). Per Brooke-An informal poll was created to gather your preference on the resolution options of the messages that can still flow with the DOB missing with the second option having more strict validation. Please review and complete the linked poll. |
Kim Brown | Proposed solution for missing PID-7 in Quest messages (rare) | Per Riki-LOI and LRI has been published as of 10 days ago. The biggest change is HL7 changing their naming convention. It is no longer a release 1 STU 5 and it is now called an addition. They describe it now as an addition 5. For LOI, there are not many changes. The changes that did occur are only to value sets. On the LOI side, they relaxed the requirements for having to have a DG1 segment in the base LOI while for most commercial orders, there will be a DG1 segment (i.e. newborn screenings). They updated the LOINC table for the newborn screening profile. For the LRI side, they made a lot of changes to the message structure. They may need to place more OBR’s back in but will be reviewing going forward. They decided to go with a single OBR with the main panel code and dropped all of the parent-child linkages. Both IG’s have changed logs (in the back) and should be easy to review and read. They are working to get these new profile versions in GDT, but it will take some time. |
Brooke Beaulieu | Open Mic: Any questions or discussion topics? | |