|
|
||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RESEARCH AND PRACTICE |
Trang Quyen Nguyen is with the EIS Field Assignments Branch of the Office of Workforce and Career Development at the Centers for Disease Control and Prevention, assigned to the Division of Epidemiology, New York City Department of Health and Mental Hygiene, New York, NY. Lorna Thorpe is with the Division of Epidemiology, New York City Department of Health and Mental Hygiene, New York. Hadi A. Maki is with the Division of Financial and Strategic Management, New York City Department of Health and Mental Hygiene, New York. Farzad Mostashari is with the Division of Health Care Access and Improvement, New York City Department of Health and Mental Hygiene, New York.
Correspondence: Requests for reprints should be sent to Trang Nguyen, New York City Department of Health and Mental Hygiene, Division of Epidemiology, 125 Worth St, Room 315, CN-6 New York, NY 10013 (e-mail: tnguyen{at}health.nyc.gov).
| ABSTRACT |
|---|
|
|
|---|
Objectives. Despite national support for electronic laboratory reporting (ELR), the transition from paper to electronic reporting has been slow both nationally and locally. We assessed the ELR experience of New York Citys surveillance programs to identify barriers to ELR implementation and generalizable lessons about automated electronic notifiable disease surveillance.
Methods. We conducted interviews with key staff of the New York City Department of Health and Mental Hygiene to evaluate ELR implementation. A review of paper and ELR disease reports enabled a comparison of the reporting systems.
Results. The completeness and timeliness of ELR were similar to, and sometimes better than, paper reporting for certain diseases. Incorporating electronic data into surveillance databases created new problems with data quality, shifted work demands, and required additional skills for data monitoring. ELR improved the handling of high-volume and time-sensitive diseases but did not completely automate reporting for diseases that required complicated assessments by staff.
Conclusions. Although ELR streamlines data processing, electronic reporting has its own limitations. A more successful use of ELR can be achieved by understanding its strengths and limitations for different disease types.
| INTRODUCTION |
|---|
|
|
|---|
Over the past decade, much progress was made in understanding and addressing the challenges of translating local laboratory codes into public health standards5 and creating secure systems for electronic data transmission. To accelerate adoption of ELR, the Centers for Disease Control and Prevention advanced standards for vocabulary, format, and messaging; funded the development of software; and conducted an extensive outreach campaign to state and local health departments to increase use of the software. Despite these efforts, the transition from paper to electronic reporting has been slow both nationally and locally. By April 2005, nearly 5 years after states received federal funding to initiate plans for ELR, only 35 state and 2 municipal health departments had begun developing or implementing an electronic system for disease surveillance.6
Comparisons between electronic and paper reporting have focused on expected improvements to the completeness and timeliness of reporting.7–11 Less attention has been paid to understanding the barriers and benefits of adopting ELR by health departments and, in particular, the challenges of incorporating electronic data into surveillance databases in an automated fashion. The experience of the New York City Department of Health and Mental Hygiene (NYC DOHMH) can be illustrative. In 2002, NYC DOHMH began receiving electronic reports through the Electronic Clinical Laboratory Reporting System (ECLRS). Because of concerns about the quality and completeness of ECLRS, laboratories were required to undergo a certification process during which they temporarily sent electronic and paper reports in tandem, for comparison, before any electronic reports were uploaded into routine surveillance databases. Beginning in July 2006, the NYC Board of Health legally mandated ELR of notifiable diseases to NYC DOHMH. We sought to assess the benefits and disadvantages of ECLRS experienced during the premandate time frame from the perspective of the NYC DOHMH disease surveillance programs.
| METHODS |
|---|
|
|
|---|
NYC DOHMH staff feedback regarding ECLRS certification and implementation was summarized according to the challenges that they experienced and the benefits to surveillance that they identified. Completeness was assessed first as the coverage of electronic reporting, which is the proportion of laboratories certified to use ECLRS by the communicable disease, STD, and TB surveillance programs for individual diseases. Because laboratories vary in the amount of testing that they conduct, we also calculated the proportion of all of the laboratory reports received through ECLRS as a second measure of the completeness of ECLRS coverage. Timeliness of reporting was measured as the time between the specimen collection date and the date when the health department was notified of a positive result.
| RESULTS |
|---|
|
|
|---|
|
|
Laboratories were certified when the level of transmitted detail was considered sufficient for appropriate public health response. In some instances, staff would not certify a laboratory from which they needed specific details, such as patient address for field follow-up, even in cases when this information was not readily available; the possibility still existed that the laboratory could obtain the information either from the requesting provider or another database (e.g., hospital billing). Yet, other laboratories were certified without such detail if NYC DOHMH staff thought that they were getting the most information possible from a laboratorys own database, as long as the electronic reports were at least as complete as the paper reports. This approach made certification challenging for both laboratory and health department staff.
Surveillance staff reported that certifying and monitoring laboratory data was tedious and cumbersome. Without the consistent urging and encouragement by the NYC DOHMH staff for laboratory staff to communicate and collaborate with their information technology department, test results would frequently be coded incorrectly. Even after laboratories were certified, NYC DOHMH informatics and surveillance staff had to continually monitor data for quality-assurance purposes. Although complicated, quality assurance was a process that had not been easily conducted using paper reports. Furthermore, automated electronic analyses of the quantity of laboratory reports were implemented to flag any erratic deviations from the expected number of reports, which created new tasks for health department staff and new communication needs with the laboratories.
Prioritizing Laboratory Certification for Certain Diseases
The health department staff recognized that the primary benefits of ELR were improved timeliness and automatic data upload (when possible within existing work-flows), thereby eliminating substantial data entry needs. In 2005, 65% of the 43 568 hepatitis C cases and 52% of the 35 814 chlamydia cases were entered into the health department surveillance databases through electronic reporting, which equated to 47204 reports that staff would have otherwise had to hand enter. As a result, more staff resources could be dedicated to conducting field work, which was especially important for diseases when the immediate treatment of the patients and prophylaxis of their contacts could prevent further sequelae and transmission. Thus, the surveillance programs identified high-volume diseases (e.g., hepatitis B, hepatitis C, and chlamydia) and time-sensitive diseases requiring field follow-up (e.g., hepatitis A and syphilis) as priority targets for ECLRS certification.
Limitations of Electronic Reporting
Despite enhancements to reporting, ECLRS did not equally improve surveillance of all diseases. For some diseases, such as gonorrhea, ECLRS markedly reduced work burden, because a positive test report equates to a new case. Yet, despite the reduction of data entry time for other, more complex diseases, reporting was still complicated because of the intricacies related to testing. Numerous TB tests, for example, are conducted and reported on multiple specimens (i.e., smears, cultures, rapid diagnostic tests, and susceptibility results) collected over several months, so updating case information electronically was difficult. Similarly, determining the case status of complex diseases requires comparisons with other patient data and might necessitate field follow-up to collect more information than what is reported electronically. For example, before adding a syphilis test report to the registry, staff must review multiple past tests and treatments. Therefore, for these complex diseases, ECLRS had less impact, because the work burden could not be fully automated.
ECLRS also created unique problems that could not be consistently monitored under quality-assurance protocols. False reports of rare diseases could be caused by incorrect automapping of electronic codes. For example, an electronic report for the relatively rare disease trichinosis led to an investigation of a case that turned out to be an error of reading in the common STD, trichomoniasis, which is not a reportable disease. In addition, the burden of obtaining basic patient details sometimes shifted from the laboratory staff to health department personnel when data were unavailable from electronic laboratory information systems. Finally, the lack of uniformly applied standards for representing laboratory results carried the risk that some negative or equivocal results (e.g., "positive for multiple contaminants") could be reported through ECLRS. Validating the specificity of automated filters (software programs) that limit electronic reporting to reportable cases could be difficult for both NYC DOHMH and laboratories, particularly for high-volume conditions that are not manually reviewed or investigated.
| DISCUSSION |
|---|
|
|
|---|
ELR does not necessarily enhance surveillance for all diseases to the same extent. The advantages are obvious for reporting diseases where volume is high and timeliness is a concern. However, raw laboratory data are not always suitable for automatic uploading into surveillance databases. In fact, some laboratories that sent complete paper reports in turn had difficulty with preparing equally complete electronic reports, often because of limited staff resources dedicated to data entry or coding. For a disease that is as complicated to report as TB,12 electronic reporting can remove 1 step of data entry but does not automate the entire reporting and classification process, partly because of the inability to automate complex judgments.13 Complete reporting requires very close collaboration between laboratory and health department staff.
Surveillance programs might want to follow the example of the certification process that NYC DOHMH undertook. Having the opportunity to educate laboratories about reporting requirements was particularly valuable. Several laboratories did not know that certain diseases were reportable, whereas many more were not clear about the details that they had to send in their reports, which in part explains the differences that we identified in completeness of reporting by disease category. Many laboratory information management systems do not include patient information required by health departments, thereby shifting labor from data entry at the laboratories to information gathering by health department staff.3 Laboratories might need additional resources (e.g., technical expertise and increased staff time) to create interfaces or change work-flows that improve their reports and address the problems that hinder their certification.
Although ELR eliminates paper burden and the need for data entry staff, additional support is required at the health department and laboratories to establish and maintain the system. Furthermore, health departments will need a higher level of technological support and skilled surveillance staff that can assure the quality of data, identify problems rapidly, and provide continual feedback to laboratories. To assure that ELR is integrated into public health surveillance workflows, close attention must be paid to understanding the limitations, as well as the benefits, of automated ELR for public health staff.
| Acknowledgments |
|---|
Human Participant Protection
Institutional review board approval was not required for this evaluation.
| Footnotes |
|---|
Note. The findings and conclusions in this report do not necessarily represent the views of the Centers for Disease Control and Prevention.
Contributors
T.Q. Nguyen, L. Thorpe, and F. Mostashari were responsible for the concept of the evaluation. T.Q. Nguyen had full access to all of the data in the evaluation and was responsible for the integrity of the data, as well as the accuracy of the data analysis and interpretation. H. A. Makki was responsible for acquisition of the reporting data, and T.Q. Nguyen was responsible for acquisition of the interview data. T.Q. Nguyen, L. Thorpe, and F. Mostashari were responsible for writing. All of the authors critically reviewed and revised the article and supervised aspects of the evaluation.
Accepted for publication December 21, 2006.
| References |
|---|
|
|
|---|
2. Panackal AA, Mikanatha NM, Tsui F-C, et al. Automatic electronic laboratory-based reporting of notifiable infectious diseases at a large health system. Emerg Infect Dis. 2002;8:685–691.[Web of Science][Medline]
3. Wurtz R, Cameron BJ. Electronic laboratory reporting for the infectious diseases physician and clinical microbiologist. Clin Infect Dis. 2005;40:1638–1643.[CrossRef][Web of Science][Medline]
4. Centers for Disease Control and Prevention. Preventing emerging infectious diseases: a strategy for the 21st century. Atlanta, Ga: Centers for Disease Control and Prevention; 1998.
5. Centers for Disease Control and Prevention, Public Health Information Network (PHIN). Notifiable condition mapping tables. Available at: http://www.cdc.gov/phin/vocabulary/ncmt.html. Accessed November 24, 2006.
6. Centers for Disease Control and Prevention. Progress in improving state and local disease surveillance—United States, 2000–2005. August 26, 2005. MMWR Morb Mort Wkly Rep. 2005;54:822–825.[Medline]
7. Doyle TJ, Gwynn MK, Groseclose SL. Completeness of notifiable infectious disease reporting in the United States: an analytical literature review. Am J Epidemiol. 2002;155:866–874.
8. Silk BJ, Berkelman RL. A review of strategies for enhancing the completeness of notifiable disease reporting. J Public Health Manage Pract. 2005;11: 191–200.[Web of Science][Medline]
9. Jajosky RA. Groseclose SL. Evaluation of reporting timeliness of public health surveillance systems for infectious diseases. BMC Public Health. 2004;4:29.[CrossRef][Medline]
10. Jansson A, Arneborn M, Ekdahl K. Sensitivity of the Swedish statuatory surveillance system for communicable diseases 1998–2002, assessed by the capture-recapture method. Epidemiol Infect. 2005;133: 401–407.[CrossRef][Medline]
11. Ward M, Brandsema P, van Straten E, Bosman A. Electronic reporting improves timeliness and completeness of infectious disease notification, the Netherlands, 2003. Euro Surveill. 2005;10:27–30.[Medline]
12. Hripcsak G, Jain NL, Knirsch C, et al. Applied Informatics: using the NII to coordinate health care (abstract). In: Proceedings of the 1996 AMIA Spring Congress; June 5–8, 1996; Kansas City, Mo.
13. Hripcsak G, Knirsch C, Jain NL, Stazesky RC, Pablos-Mendez A, Fulmer T. A health information network for managing inner-city tuberculosis: bridging clinical care, public health, and home care. Comput Biomed Res. 1999;32:67–76.[CrossRef][Web of Science][Medline]
This article has been cited by other articles:
![]() |
S. Sengupta, N. S. Calman, and G. Hripcsak A Model for Expanded Public Health Reporting in the Context of HIPAA J. Am. Med. Inform. Assoc., September 1, 2008; 15(5): 569 - 574. [Abstract] [Full Text] [PDF] |
||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| HOME | HELP | FEEDBACK | SUBSCRIPTIONS | ARCHIVE | SEARCH | TABLE OF CONTENTS |