-
Looking for something specific? You can type Ctrl+F (for Windows or Linux) or ⌘-F (on Macs) to find something on this page using your browser’s built-in search.
| Millie M. |
Thank you
|
|
|---|---|---|
| Michael N. |
Ah.. Thank You!!!
|
|
| Kristy L. |
Malai, Millie | APHL <millie.malai@datapult.aphl.org> is able to help. They will ask you to update your preferences on receiving OTC data again.
|
|
| Michael N. |
Good Morning! Have any other states received ELR from Care Evolution <CAREEVOLUTION^00Z0000024^CLIA> with no patient names? If so, were you able to contact them and ask them to stop sending them? PS: Any email contacts are welcome :)
|
|
| Carmen P. |
Labcorp has some 2.5.1 de-identified test messages available and would like to test with any state that is willing. I have tested with a handful of states and implemented their suggested changes. I have also tested with NIST tool, and am pretty happy with the feedback from that. Please send me an email, Pughc@Labcorp.com if you would like a test message. I can only send through email, so PHINMS or sFTP to test systems.
|
|
| Nancy B. |
Hi all- Looking for any updates to the LOINC-SNOMEDs for TB resistance genes. I have an older list but looking for an updated list. Here is what I have. Thanks so much!
| 46247-3 | M. tuberculosis embB gene ethambutol resistance mutation molecular | PHC1896 | embB | 72866-7 | M. tuberculosis ethA gene ethionamide resistance mutation molecular | PHC1902 | ethA | 72276-9 | M. tuberculosis gyrA gene fluoroquinolone resistance mutation molecular | PHC1900 | gyrA | 72867-5 | M. tuberculosis gyrB gene fluoroquinolone resistance mutation molecular | PHC1901 | gyrB | 63072-3 | M. tuberculosis ihnA gene isoniazid resistance mutation molecular | PHC1891 | inhA | 46246-5 | M. tuberculosis katG gene isoniazid resistance mutation molecular | PHC1890 | katG | 46245-7 | M. tuberculosis pncA gene pyrazinamide resistance mutation molecular | PHC1895 | pncA | 72864-2 | M. tuberculosis rpsL+rrs gene aminoglycoside resistance mutation molecular | PHC1903 | rpsL | | | PHC1897 | rrs | 46244-0 | M. tuberculosis rpoB gene rifampin resistance mutation molecular | PHC1894 | rpoB | TBMolGen_ahp | M. tuberculosis ahpC-oxyR gene resistance mutation molecular | PHC1892 | ahpC-oxyR | TBMolGen_eis | M. tuberculosis eis gene resistance mutation molecular | PHC1898 | eis | TBMolGen_fabG1 | M. tuberculosis fabG1 gene resistance mutation molecular | PHC1893 | fabG1 | TBMolGen_tlyA | M. tuberculosis tlyA gene resistance mutation molecular | PHC1899 | tlyA |
|
| Nancy B. |
Hi all - I'm looking for ELR/eCR/DMI contacts from New England, NY, NJ, PA for the NE Regional Epi meeting S&I track we are planning. I have heard from a few folks but would like to hear back from more. Meeting will be in Mystic CT Nov 30 and Dec 1 with a pre-meeting day on Nov 29. My co-planning colleague and I have some ideas for a half day pre-meeting and we've also asked to have a session track for Nov 30. Thanks! Pdf attached
|
|
| Nancy B. | ||
| Swathi R. |
Thank you!
|
|
| Swathi R. |
Hi Millie, here is my email Swathi.Ramahayam@idph.iowa.gov and also include John Satre John.Satre@idph.iowa.gov
|
|
| Millie M. |
|
|
| Swathi R. |
Hi Millie, please let Iowa know as well. We would be interested to explore.
|
|
| Nancy B. |
Hi Millie, please let CT know as well.
|
|
| Millie M. |
Will do! My colleague Annette will reach out to you via email. Thank you. :)
|
|
| Cody M. |
Hi Millie. Oregon would be interested in exploring what this looks like. Let me know when a good time is to connect so we can discuss and scope out what this might look like. Thanks!
|
|
| Millie M. |
Hi everyone! We have heard that there is a Connect-a-thon in May that is based on FHIR - and our NIH partner for the RADx MARS program has asked if any states are able to currently accept FHIR (or might be interested in receiving FHIR ELR for this Connect-a-thon in May). Would any jurisdictions be interested in participating in this Connect-a-thon as a data recipient of FHIR-based ELR messages?
|
|
| Ann K. |
Hey Nereida, we have NTM reportable in MN and are getting these through ELR using 2.3.1 format. We did have to do some advanced Rhapsody logic to get these to run through smoothly since micro messages send a bit differently than non-micro. Happy to discuss it with you! We are utilizing some mapping from an additional OBX segment that has OBX.3 as ^^^ORGANISM^ORGANISM^L to assist with this logic.
|
|
| Nancy B. |
Hi Nereida, NTM is reportable in CT also, but I have not seen much reported in the csv files ARUP posts for us. Even though they are a smallish reporter for us, we do get reports regularly. I have not moved them to ELR because I refuse to map local codes. There really needs to be a push for ARUP to use HL7 2.5.1.
|
|
| Kristy L. |
Hey Nereida, it is reportable in MD but we are still receiving faxes. When we tried onboarding them several years ago there seemed to be a lot of limitations, I think particularly relating to micro so we stopped the project until they had a better system. Are you seeing that with other micro results?
|
|
| Nereida C. |
Hi everyone, Do other states where NTM (non tuberculosis mycobacterium) is reportable have issues with ARUP sending the results in the notes segment? We reached out and they said that they can't change it but it seems odd to me that this would work for other states too. Any work arounds/suggestions are welcome!
|
|
| Riki M. |
David - If you have already made "CLIA" numbers for each state, do you want to share those? I was asked by VT to create CLIAs for the PHAs - but haven't gotten around to it, but is more of you need it I can move that up in the prioirty list - I was going to move my OID/CLIA management to smartsheet, so I can give folks read only access. Let me know if that is something I should do.
|
|
| David D. |
In NY we give each state their own specific CLIA for MSH-4 which we use for that state. The lab CLIA comes in the OBX segment.
|
|
| Garrett J. |
Thanks, Randi. Yes, configuring in our intake engine and disease management system. The practice you're describing to group incoming messages by sending state based on a value in the MSH segment is exactly what I was considering. We also do that for some data aggregators, but I'm interested to know whether any jurisdictions who are farther down the interpartner/interstate exchange process have any lessons learned that would lead them to encourage or discourage the same practice for interstate exchange.
|
|
| Randi H. |
Are you referring to configuring the new lab in your Rhapsody environment or something else? In TN, we have used other MSH values that are consistent in the sending jurisdiction's messages such as MSH-3, MSH-5, or MSH-6 so that all messages with a specific value would be grouped as a specific state. We do this with some of our data aggregators as well that send different facilities in MSH-4.
|
|
| Garrett J. |
Hi All, |
|
| Jordyn D. |
Good morning, has anyone had any issues with Labcorp messages failing, starting 6/8
|
|
| Nereida C. |
thank you!
|
|
| Riki M. |
It would be an OBX segment - most liky as a string. |
|
| Nereida C. |
Hello! Have any other states started receiving GISAID from sequencing labs for COVID variants? If so, can you share where in the HL7 message they are sending it? Or, where you would expect to see it? \
|
|
| Brooke B. |
Hi all, just a reminder that we do NOT have an ELR Workgroup call today. Thanks!
|
|
| Nereida C. |
Hi all, has anyone been able to reach "Vitagene" for COVID reporting? If so, can you share your contact? We see on their website that they offer COVID testing, but we have been unable to reach them. Additionally, our lab was unable to find any information for them via CLIA. Thank you!
|
|
| Nancy B. |
Hi all -- CDC guidance for reporting SARS-CoV-2 sequencing results is out https://www.cdc.gov/coronavirus/2019-ncov/lab/resources/reporting-sequencing-guidance.html
|
|
| Brooke B. |
Hi all, potentially of interest: https://www.cms.gov/files/document/clia-sars-cov-2-variant.pdf |
|
| Tamara H. |
THANK YOU, Allison! Much appreciated.
|
|
| Allison L. |
Sorry about the names being copied twice
|
|
| Allison L. |
These are the contacts we have. For our ELR, they use Lifepoint as a data broker Ahmed Kamel <ahmedfkamel@hotmail.com>; Emily York <emily@chemisyslabs.com>; Patrick Schaffer <pschaffer@lifepoint.com>; Kathy Muschlitz <kmuschlitz@lifepoint.comAhmed Kamel <ahmedfkamel@hotmail.com>; Emily York <emily@chemisyslabs.com>; Patrick Schaffer <pschaffer@lifepoint.com>; Kathy Muschlitz <kmuschlitz@lifepoint.com
|
|
| Tamara H. |
Does anyone happen to have a point of contact for ChemiSys Labs?
|
|
| Tamara H. |
THANK YOU!!😊
|
|
| Riki M. | ||
| Riki M. |
Here is the latest guidance document draft |
|
| Tamara H. |
This issue of how to receive variant information continues to pick up steam. Wondering if anyone has actually received any variant reports via ELR yet?
|
|
| Tamara H. |
Thank you
|
|
| Chris B. | ||
| Chris B. |
WA State has just started to look at how we could receive these results via HL7 and get them into our Surv System... |
|
| Cody M. |
|
|
| Nereida C. |
I suspect this is specific to variants of concern but I am not able to answer your other questions. I was just curious on whether other state labs are reviewing sequencing from other labs before reporting the variant of concern.
|
|
| Nereida C. |
Hi Annie,
|
|
| Annie F. |
Nereida, when you say "sequencing results" are you just referring to variants of concern, and transmission via ELR of the name of the variant? Or are specific mutations being transmitted? How does a variant of concern get defined, especially locally - e.g., if our lab starts to see rapid emergence of a virus with a particular sequence, is there a specific threshold or rapidity of growth that would put it into the category of a variant of concern? Thanks! Doing a lot of catching up/learning here so pardon if these questions do not make sense or if I should know the answer!
|
|
| Nereida C. |
Hello all, we are actively working on finding a workflow for this here in CO. Our current plan is that sequencing results will be sent to our lab staff for review and then generate a flat file to be picked up by our ELR system. Are other states lab staff reviewing sequencing from other labs for consistency?
|
|
| Jason H. |
Thanks Carmen. The guidance is with our communications staff being prepared to post. I'm happy to send you the draft.
|
|
| Carmen P. |
Hi Tamara. I have talked to Jason Hall and he indicated CDC is working on a recommended format. It would be for identifying variant and not the actual DNA sequence.
|
|
| Tamara H. |
Hi ELR friends! Wanted to check in with this group to see if anyone has any information about formatting and/or sending variant data in ELR messages?
|
|
| Riki M. |
The suggestion is to truncate at 19 characters and add # to make it 20 - if that is your length restriction and then ask that the full length device ID be sent in an NTE. |
|
| Jordyn D. |
Hi, is anyone working with Azova? We're having issues with their OBX-17.1 being too long. If you also had this issues, did you have them truncate it? Thank you! Jordyn
|
|
| Bill S. |
Greetings. I should probably know if this exist, but do we have an ELR Coordinators List on here? I need contacts for ELR Coordinator for KY and IN please if those folks can send me an email please. William.Storm@odh.ohio.gov. Thanks! - Bill
|
|
| Nereida C. |
Hi Morgan, in CO Walgreens was sending a formatted spreadsheet for rapid tests on persons that were not previously registered and all other reports came in from PWN health (via fax for awhile - now they are sending electronically by either ELR or flat time, I am not sure). I believe Walgreens is now sending a flat file for all CO locations once daily which is processed via Rhapsody/ELR. It took awhile to get this sorted out. Our website will be updated again in a few days but the flat file format is linked here if you are interested: https://cdphe.colorado.gov/report-a-disease
|
|
| Morgan H. |
|
|
| Nancy B. |
and that was the source I used when I couldn't find it on CMS or CDC
|
|
| Nancy B. |
Hi Rita!! Yes I found that also, and when I asked the lab, they said it wasn't them... weird
|
|
| Rita A. |
Don't know if you trust this source, but... |
|
| Nancy B. |
HI -- does anyone know what lab this CLIA is 07D0986637 we are having trouble finding it via the usual sources
|
|
| Kristy L. |
One contacted me last week and said there were talks about working with AIMS but I do not know what has been done.
|
|
| Rachelle B. |
We just had a facility reach out to us, too. We'd love to have them report through AIMS, as well.
|
|
| Kristy L. |
Thanks for mentioning this. I have been encountering the same issues with the ones I have reached out to. I have been able to get one facility to use MD's template, but it would be great if they all could send with the method you have proposed.
|
|
| Megan T. |
Hi all. I've been outreached by about 5 military facilities this week regarding reporting, as it looks like DOD developed a standard report extract csv that they'd like to provide to us. However, it doesn't meet our state's local flat file format, and they can't seem to change it. One entity is Walter Reed Medical, which understandably can't adjust to all of our own templates. How do we get DOD to use the national flat file and report to AIMS? If they want to develop one and only one format, seems to be the best solution for them. Wouldn't that be great for routing to the right jurisdiction too?!
|
|
| Hyung-Suk ". |
Thanks Riki for your response! Stay healthy and Safe!
|
|
| Riki M. |
The HHS guidance will be an additional profile component, that you can then use ON TOP of the normal ELR you are using now - and yes, it is addressing all these elements - the additional elements for ELR are the device ID, the Order Test Date and the AOEs - the PHA then forwards the data to CDC/HHS.
|
|
| Riki M. |
The dataflow for the AOEs is in the order from the provider to the testing lab - then the testing lab will include the AOEs back in the result message to the provider (usually, because normally AOEs are ONLY asked when the answer is used in result interpretation), so I am not sure, if these would be sent back to the provider, but they should be in the ELR feed.
|
|
| Hyung-Suk ". |
I understand LOI interface is between lab and CDC. So their electronic data gets reported directly to HHS at CDC or whatever the platform CDC is designated, differently from our PH reporting ELR data. I remembered there was a talk in one of HL7 workgroup tried to reconcile the specification of LOI interface and ELR interface (ORU_R01, which is the message type and event type for ELR interface) in the past, but not sure if there was any progress made…. |
|
| Hyung-Suk ". |
If I do not understand correctly, please correct me.
|
|
| Hyung-Suk ". |
Oops, sorry, my mistake. I clicked enter to get a line break and kept uploaded incomplete comments. Promised to be careful... It is so glad to hear you are working on a HHS guidance profile component that can be added to LRI/ELR requirements or any other specification. LA County was curious if there is the plan regarding the new HHS reporting requirement from CARES act to ELR implementation specification for Public Health Reporting as the HHS guidance mentioned about Lab Order Interface, but not clearly about ELR interface although mentioned about PH reporting. Do you have any time line that the ELR HL7 2.5.1 Public Health Reporting specification might be updated reflecting all additional components described in HHS guideline? |
|
| Hyung-Suk ". |
It is so glad to hear you are working on a HHS guidance profile component that can be added to LRI/ELR requirements or any other specification. What is the plan regarding the new HHS reporting regs from CARES act. Are you going to update this spreadsheet and incorporate those fields?
|
|
| Hyung-Suk ". |
It is so glad to hear you are working on a HHS guidance profile component that can be added to LRI/ELR requirements or any other specification.What is the plan regarding the new HHS reporting regs from CARES act. Are you going to update this spreadsheet and incorporate those fields? |
|
| Riki M. |
Tom - HL7 has been working on this and we hope we have this nailed down by tomorrow - here is the confluence page with the current state of things: https://confluence.hl7.org/display/OO/Enhanced+ELR+Reporting - the main focus is to better understand which test (kit plus insturment) was performed where - it can be assigned by the manufacturer and shared in the LIVD document, though currently that information is NOT YET in the published file here: https://www.cdc.gov/csels/dls/sars-cov-2-livd-codes.html Overall we are working on creating a HHS guidance profile component that can be added to LRI / ELR Rq or any other specification - it involves a few pre-adopted elements (from v2.8.2) to identify AOEs etc. APHL is also working on a flatfile for those that cannot create HL7 messages (and we are planning on providing conversion into ELR R1+) in a rhapsody route and mirth channel.
|
|
| Tom S. |
Has anyone figured out this newly specified requried data element called "device identifier" for the automated ELR message? I'm suspecting someone at Federal level is expecting to capture info about the testing platform for COVID tests to better track comparative lab testing volumes for different company products--but that's sheer speculation. Sounds like a code that FDA assigns to devices used for lab testing. Thoughts??
|