Evaluating the Completeness of Data Elements of Provider Reporting on Indiana's Communicable Disease Reports

dc.contributor.authorLai, Patrick T. S.
dc.contributor.authorGujjula, Kavya
dc.contributor.authorGrannis, Shaun J.
dc.contributor.authorDixon, Brian E.
dc.date.accessioned2014-10-17T19:08:19Z
dc.date.available2014-10-17T19:08:19Z
dc.date.issued2014-04-11
dc.descriptionposter abstracten_US
dc.description.abstractObjective To examine the completeness of data elements required for notifiable disease surveillance from official, provider-based reports submitted to a local health department. Introduction Completeness of public health information is essential for the accurate assessment of community health progress and disease surveillance. Yet challenges persist with respect to the level of completeness that public health agencies receive in reports submitted by health care providers. Missing and incomplete data can jeopardize information reliability and quality resulting in inaccurate disease evaluation and management (1). Additionally, incomplete data can prolong the time required for disease investigators to complete their work on a reported case. Thus, it is important to determine where the scarcity of information is coming from to recognize the characteristics of provider reporting. Methods Data from 1,195 unique patient cases across 7 notifiable diseases were abstracted from official reporting forms (2) submitted to a local health department serving the Indianapolis metropolitan area. The selected diseases were chlamydia, gonorrhea, syphilis, salmonella, histoplasmosis, hepatitis B-acute, and hepatitis C-chronic. Table 1 represents the duration and collection period for each of the selected diseases. Diseases were purposely chosen to represent the broad range managed by local health departments. Diseases were purposely chosen to represent the broad range managed by local health departments. A set of data elements consisting of patient, clinical, and provider information was then evaluated for completeness. The level of completeness was determined using a classification method similar to that used by Dixon et al. (3). Fields were considered complete if they contained a value; the recorded value was not validated for accuracy. Results Table 2 depicts the level of completeness for the selected data elements across the target diseases. Completeness levels and percentages varied by disease and data element with completeness being higher for patient demographic information (e.g., name, address) than provider demographics (e.g., name, clinic address). The majority of data elements for patient demographics were categorized as mostly to always complete. Conclusion It is essential that provider reports are completed in a thorough and timely manner. To increase documentation of provider information, analyses of provider characteristics such as workflow patterns, organizational constraints, and information needs are essential to understand the completeness level of provider information reporting. This will allow us to develop implementation of strategies to increase completeness of reporting across all data elements necessary to assess and investigate notifiable diseases.en_US
dc.identifier.citationLai, P.T.S., Gujjula, K., Grannis, S., Dixon, B. (2014, April 11). Evaluating the Completeness of Data Elements of Provider Reporting on Indiana's Communicable Disease Reports. Poster session presented at IUPUI Research Day 2014, Indianapolis, Indiana.en_US
dc.identifier.urihttps://hdl.handle.net/1805/5316
dc.language.isoen_USen_US
dc.publisherOffice of the Vice Chancellor for Researchen_US
dc.subjectdisease surveillanceen_US
dc.subjectpublic health informationen_US
dc.titleEvaluating the Completeness of Data Elements of Provider Reporting on Indiana's Communicable Disease Reportsen_US
dc.typeOtheren_US
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Lai-Evaluating.pdf
Size:
67.5 KB
Format:
Adobe Portable Document Format
Description:
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.88 KB
Format:
Item-specific license agreed upon to submission
Description: