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

Collection dates in NEDSS

Hello,

I am currently dealing with an issue with our state lab where not all ELRs have specimen collection dates. The lab should be getting that information, but in the cases where it is not filled in (very few but I would still like them in our surveillance system), our lab is using "0000" which causes the lab to fail. We have considered using other dates within the HL7 message to populate this field, but we really don't want to change any of the message/falsify any dates. Does anyone else have a solution for this?

Thanks,
Kristy

Comments & Events

Nancy Barrett, Epi 4/PH Informatics Specialist
Hi, our State Lab has the same issue and does not have the staff or a robust enough protocol to call submitters to collect specimen collection date. For diseases that must have this date, like the STDs, we've used date received as a substitute. Usually that is close to the actual spec coll date. 
Riki Merrick, Terminologist at APHL
0000 is the official way to indicate unknown dates in ELR (for fields that are required, like OBR-7/SPM-17) - and best practice, if the lab does not have the resources to actually obtain the date, is what nancy mentions- use the specimen received date (SPM-18), which is also required and all labs should have that.

Riki
Walter Kemper, ELR Coordinator, NC DHHS Div of Public Health
When the specimen collection date value is "0000" we have our integration engine change that field to empty so that when the message is imported into our Maven system the field is empty.