Injury Surveillance Workgroup 7 (ISW7)- Poisoning Surveillance Efforts Continue to Move Forward
What’s next after the release of the poisoning surveillance recommendations in the ISW7 report (http://www.safestates.org/associations/5805/files/ISW7%20Full%20Report.pdf) released in May 2012? Testing and translating them to basic public health surveillance practice. Two core groups (a mortality-focused group and a morbidity-focused group) are doing just that. The Council of State and Territorial Epidemiologists (CSTE) Poisoning Surveillance Workgroup has recruited epidemiologists and others across the nation to focus on poisoning deaths, specifically deaths from opioids and illicit drugs. More than 18 people representing more than 13 states, local areas, universities and national organizations have volunteered to test the drug overdose mortality surveillance recommendations using data accessible at the state (e.g., underlying and contributory causes of death data from death certificates, literal text from death certificates, medical examiner or coroner reports). The workgroup plans to provide a session during the Substance Abuse pre-conference workshop at the next CSTE conference in June 2013 on a standard process for four levels of poisoning mortality surveillance from basic to advanced, and to share innovative projects. For more information please contact, Annie Tran (email@example.com).
Similarly, the four states funded under CDC’s Core Surveillance Quality Improvement-- Colorado, North Carolina, Massachusetts, and Utah – are planning to assess the quality of morbidity coding for poisoning. This group will review and confirm the ICD-9-CM codes for poisoning in a sample of medical records indicating poisoning. This small but intense effort will set the stage for future groups to examine their morbidity coding for acute opioid and illicit drug poisoning. Information from this effort will be presented next year at the Safe States and CSTE annual meetings. For additional information, please contact Scott Proescholdbell (firstname.lastname@example.org).