Creation of a Technical Tool to Improve Syndromic Surveillance Onboarding in Tennessee
PDF

How to Cite

Leegon, J., Wiedeman, C., Nukala, V., & Petersen, P. (2018). Creation of a Technical Tool to Improve Syndromic Surveillance Onboarding in Tennessee. Online Journal of Public Health Informatics, 10(1). https://doi.org/10.5210/ojphi.v10i1.8907

Abstract

Objective: 

To show how the creation of a software tool and implementation of new processes improved the efficiency of syndromic surveillance onboarding at the Tennessee Department of Health.


Introduction: 

Syndromic surveillance is commonly supported by information generated from electronic health record (EHR) systems and sent to public health via standardized messaging. Before public health can receive syndromic surveillance information from an EHR, a healthcare provider must demonstrate reliable and timely generation of messages according to national standards. This process is known as onboarding. Onboarding at the Tennessee Department of Health (TDH) focused heavily on human review of HL7 messages. However, the visual inspection of messages was time-intensive and delayed efforts to provide constructive feedback to participating healthcare providers. To ease the quantity of manual review done during the onboarding process, TDH created an application to assist in the process of reviewing syndromic surveillance messages.


Methods: 

The application for reviewing syndromic surveillance messages was developed in Python 3.6, a general purpose programming language. Python was selected because of the strong libraries already developed in the language for data analysis, database interaction, and interacting with healthcare related data. To support TDH onboarding efforts, the application performed three tasks : file handling, HL7 processing, and database loading.
File handling was completed using Python core libraries. Healthcare facilities participating in onboarding regularly uploaded test HL7 batch files containing all emergency department (ED) visits to a secure File Transfer Protocol (sFTP) server owned by the State of Tennessee. Files are then retrieved from the sFTP server and delivered to the TDH integration engine, Rhapsody. Rhapsody processes the incoming files and makes a copy available to the Python application. The copies are then loaded by the application into a database and backed up in an archive.
After the application has finished handling the received files, the raw HL7 messages within the files are processed to extract relevant information needed to validate the message. The extraction was supported by the “python-hl7” library. The application referenced a CSV file with the names and locations of all of the PHIN 2.0 guide HL7 data elements to guide data processing. Processed HL7 fields and file metadata were then extracted into a relational database using the Python library SQL Alchemy.


Conclusions: The creation of this application has greatly assisted in the process of reviewing syndromic surveillance messages at TDH by automating data extraction and organization for all received HL7 messages. The database tables of extracted HL7 data elements allowed for easy analysis in any tool that can connect to a database (e.g., SAS, R, Python, Excel, Tableau) and faster, more manageable message validation. TDH has been able communicate better feedback to more healthcare providers because of the efficiencies gained after deploying the application.



https://doi.org/10.5210/ojphi.v10i1.8907
PDF
Authors own copyright of their articles appearing in the Online Journal of Public Health Informatics. Readers may copy articles without permission of the copyright owner(s), as long as the author and OJPHI are acknowledged in the copy and the copy is used for educational, not-for-profit purposes. Share-alike: when posting copies or adaptations of the work, release the work under the same license as the original. For any other use of articles, please contact the copyright owner. The journal/publisher is not responsible for subsequent uses of the work, including uses infringing the above license. It is the author's responsibility to bring an infringement action if so desired by the author.