CSTE National ELR Workgroup

Welcome to the CSTE National ELR Workgroup Basecamp! We hope you will utilize the space to share resources with colleagues, start discussion threads, and identify topics for the workgroup to tackle on future calls. All workgroup members will have the opportunity to join. Please note that you may edit your notification preferences to suit your needs (and your email inbox). If you are not already on the ELR distribution list and would like to receive call communications, please enroll using this subscription form (copy and paste in browser): https://app.smartsheet.com/b/form/5a91a4579952496682084796b82112e6

📈 Update to Expanded ELR

Hi everyone,
Several of you asked in December to get an update on Datapult’s Expanded ELR service posted to Base Camp. Here are the updates. Please let me know if you have any questions or comments to share! millie.malai@aphl.org or post to this thread

When will the Expanded ELR use case be used in production?

  • Initial release is planned for end of March 2023
  • Include ELR for the following agents:
-          Chlamydia trachomatis
-          Haemophilus ducreyi
-          Hepatitis A, B, C viruses
-          Human Immunodeficiency virus (HIV)
-          Influenza A/B viruses
-          Neisseria gonorrhoeae 
-          SARS-CoV-2 (following current rules for OTC, multiplex)
-          Treponema pallidum 
-          Mpox virus

What PHAs should expect to receive?
  • List of reporting requirements and questions to validate prior to March 2023 (Currently collating jurisdiction rules in batches. If you haven’t heard from us yet, we will be completing the initial emails over the next few weeks.)
  • Sample messages during onboarding of laboratories – normalized and standardized to HL7 v2.5.1
  • Normalized and standardized HL7 v2.5.1 ELR in production (Since we are trying to use one format that can work for all PHAs, we will use the same variations to the ELR standard that worked for COVID-19 ELR. If there is any concern with this, please let us know the specific concerns.) 

What is the data validation process?
  • Datapult reviews the original HL7 message from the lab and works with lab to modify to meet minimum requirements necessary (for our service to ingest messages)
  • Once format/content approved, lab will map local terms to standard codes
  • Verify that outbound HL7 messages are valid
  • Complete successful end-to-end testing to ensure outbound HL7 messages adheres to requirements
  • Approval by PHAs for Go-Live

How will the list of agents be expanded from the initial release?

Future releases (in 2023-2024) are planned to cover nationally notifiable diseases and the required reporting based on the test menu of the labs and ELR rules for PHAs in their service areas (if not related to NNDs). See attached PDF.

Is Datapult making/checking any assumptions? 
  • ELR for all other agents/pathogens can be received at the same integration point used by AIMS for Centralized ELR. (This is actively being checked and confirmed.)
  • Deviations from HL7 v2.5.1 ELR standard are already known per that used for COVID-19 ELR (Also, checked and confirmed.)
  • All/Most PHAs expect to review sample messages during onboarding of laboratories to this expanded use case (Will want to know scope of the reviews for each jurisdiction.)
Nancy Barrett, Epi 4/PH Informatics Specialist 👏

Comments & Events

Ann Kayser
Hey Millie, and update to go-live date since the CSTE presentation in March indicating early April, 2023?
Ann Kayser (MN Dept of Health)
Millie Malai
Hi Ann !
We will be live with our new expanded ELR service tomorrow and pending onboarding of laboratories to the service. I believe we may have our first lab sometime in April but none confirmed as of today.

Sincerely,
Millie
Ann Kayser
Hi Millie - curious if there was any updates to provide for the expansion and the progress you are making with lab(s) for Datapult’s Expanded ELR service.

Thanks!
Ann Kayser (MN Dept of Health)
Millie Malai
Hi Ann and others!
We are very, very close with finalizing contracts with 2 laboratories. At least 1 should be onboarding by August – once we have scheduled their onboarding, we will be sharing details about which lab, when, MSH, which ELR, etc. with all of you. We have connected with nearly all PHAs about ensuring we have the onboarding specifics and ELR requirements understood on our end. We just haven’t confirmed with 4 (DE, MI, ND, WV), so we would love to connect with anyone from these states. 
 
These new Expanded ELR files will be delivered to your connections with a different filename (similar to today’s but a different use case “DatapultELRPivot”): InterPartner~DatapultELRPivot~Sender~AIMSPlatform~Test~Test~20230503103115047~STOP~<originalfilename>.hl7
 
A reminder that we are currently in production with the highlighted ELR in the attached PDF – and we have finalized our next batches that we will roll into production (those that are underlined).
 
Please let me know if there are any questions. 
 
Millie Malai
Technical Project Manager
 
Annie Fine, CSTE
Thanks Millie! Curious whether you have a plan to include RSV in the respiratory pathogens given recent emphasis on pan-respiratory surveillance though I know it is not reportable in many jurisdictions. 

When you say you are in production with certain conditions does that mean that some labs are sending production data for those diseases to jurisdictions via Datapult? Thank you!
Millie Malai
Hi Annie! We can add RSV to one of our batches at any time, and we decide the batches based on the lab's test menu and the volume of testing overall (in U.S.). The 2 labs we have in the sign-up process now do not have RSV on their menus, however, if in the future one did, then we would add RSV to our roll-out plan.

When I say we are in production, this does not mean that we have labs sending ELR for the expanded set yet. Production means that we are ready to apply each jurisdiction's reporting criteria for those agents, and there would be no "wait" to get those ELR processed by our system. If a lab were onboarding, but had tests not yet in production, we would add them to our next upcoming deployment batch. 

Thank you!