PHLT 8270 Week 5 Data Quality Appraisal Example

Health Informatics and Surveillance Walden University Free custom sample in 24 to 48h

This PHLT 8270 Week 5 data quality appraisal example measures a composite state's carbapenem-resistant organism reports against three named standards rather than giving an overall impression: the required fields in the state's electronic reporting guide, the one-business-day reporting deadline and the window the infections team needs to start containment. Walden PHLT 8270 asks students to appraise data quality, and the paper reports completeness field by field, finding facility type complete in only 52% and carbapenemase testing status in 65%, compares electronic and faxed reports against the deadline, measures the collection-to-notification interval and checks validity in a sample, where facility type and specimen source errors could misdirect a response. It explains why the standards differ and proposes laboratory scorecards, a method of measuring quality as distance from a standard that fits any PhD in Public Health data review.

CoursePHLT 8270 Health Informatics and Surveillance
WeekWeek 5
Paper typeData quality appraisal
LengthAbout 1,000 words, 6 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramPhD in Public Health
UpdatedOctober 2026

Free sample paper for PHLT 8270 Week 5

1

Measuring Data Quality as Distance From Named Standards: Field Completeness, Report Timeliness and Code Validity in a Composite State's Carbapenem-Resistant Organism Reports

Student Name

Walden University

PHLT 8270: Health Informatics and Surveillance

Instructor Name

Month Day, Year

What this page is doingThe title defines data quality as distance from specific standards, which is the appraisal's central method and its difference from an overall impression.
2

Measuring Data Quality as Distance From Named Standards: Field Completeness, Report Timeliness and Code Validity in a Composite State's Carbapenem-Resistant Organism Reports

The Approach

Data quality is often described in general terms: the reports are mostly complete, or timeliness is improving. Such statements cannot guide repair, because they do not say complete enough for what or timely compared with what. This appraisal measures the composite state's carbapenem-resistant organism reports against three named standards: the reporting deadline in the state's communicable disease rule, the window the healthcare-associated infections team needs to start containment and the fields the state's electronic laboratory reporting guide marks as required. Each measure is reported as the distance between practice and the standard. Dixon et al. (2013) describe completeness, timeliness and accuracy as the dimensions of data quality that most affect surveillance practice, and this appraisal applies them to one system. All figures are composite.

What this page is doingDefining each quality measure against a specific standard makes the results actionable, since every gap points to a rule or a need.
3

Standard 1: Required Fields

The state's reporting guide marks eight fields as required for carbapenem-resistant isolates. Completeness was measured for each field separately across the 412 reports received in one year.

Reporting a single completeness figure across all fields would have shown about 82%, hiding the fields that matter most for containment. The two weakest, facility type and carbapenemase testing, are the two the containment response depends on.

Table 1

Completeness of Required Fields (Composite Figures, n = 412)

FieldCompleteWhy it matters |
Organism identification100%Defines the report |
Specimen collection date97%Starts every timeliness measure |
Specimen source91%Separates infection from screening |
Ordering facility88%Directs the containment call |
Patient address79%Distinguishes facility residents from community patients |
Facility type of patient residence52%Identifies nursing home residents |
Carbapenemase test performed65%Determines whether a case can be confirmed |
Carbapenemase result, if performed81% of testedTriggers containment |

Note. Composite figures. Completeness is the share of reports with a valid, non-blank value.

Standard 2: The Reporting Deadline

The state's rule requires laboratories to report carbapenem-resistant isolates within one business day of the result. Measured from the date the final susceptibility result was released to the date the state received the report, 83% of electronic reports met the deadline, compared with 46% of faxed reports. Electronic reporting's advantage in timeliness has been documented elsewhere; in one comparison, electronic laboratory reports arrived about eight days earlier than spontaneous paper reports (Overhage et al., 2008).

Standard 3: The Containment Window

The healthcare-associated infections team aims to start screening of contacts within three days of learning of a confirmed case, but the clock that matters for spread runs from specimen collection. Measured that way, the median interval from collection to state notification of confirmation was seven days, and the longest delays involved isolates shipped to the state laboratory for mechanism testing. Most of the distance from the containment goal lies before the state is notified, a finding consistent with the evaluation completed in Week 4.

Validity

Completeness measures whether a field is filled; validity measures whether the value is right. A sample of 60 reports was checked against facility records. Facility type was recorded incorrectly in 9, usually listing an acute care hospital when the patient had been transferred from a nursing home. Specimen source was mislabeled in 4, most often a rectal screening swab recorded as stool from a clinical specimen. Errors of the first kind send the containment call to the wrong facility; errors of the second can make a screening result look like an infection. The updated surveillance evaluation guidelines treat data quality as including both completeness and validity (German et al., 2001), and this appraisal shows why both are needed.

Why the Standards Differ

The three standards measure different things, and a report can meet one while missing another. A laboratory can send every required field on time and still deliver a report too late for containment, because the clock that matters for spread starts at specimen collection, before the laboratory has a result. Conversely, a report can arrive within the containment window but lack the facility type needed to direct the response. Reporting each standard separately keeps these failures distinct. It also assigns responsibility clearly: field completeness belongs mainly to laboratory interfaces, the reporting deadline to laboratory workflows and the containment window to the whole chain, including isolate shipment.

How the Appraisal Would Change Practice

The appraisal's results should be shared with each reporting laboratory in a short scorecard showing its completeness for each required field, its share of reports meeting the deadline and its median time from collection to notification for confirmed cases. Laboratories rarely see these measures, and feedback has been described as one of the more effective interventions for improving electronic surveillance data (Dixon et al., 2013). The program should repeat the appraisal every six months so laboratories can see whether changes have helped. Over time, the scorecards would also show the program which laboratories need technical assistance and which have solved their problems, letting scarce staff time go where it does the most good. A laboratory whose completeness for facility type rises from half to nine in ten after a small interface change offers a model the program can share with others using the same software. Publishing the aggregate results, without naming laboratories, would also let partners see the state of the system as a whole. Laboratories that see their own position against the state average often move without further prompting, which makes the scorecard one of the cheapest improvements available to the program. It requires only data the program already holds.

What the Appraisal Recommends

Make facility type and carbapenemase testing status required fields in the electronic reporting interface, so messages without them are flagged at receipt. Move remaining fax reporters to electronic reporting, starting with the laboratories serving nursing homes. Measure timeliness from specimen collection, not from receipt, in routine reports. Repeat the validity check annually on a small sample, because errors that a completeness count cannot see can send a response to the wrong place.

References

Dixon, B. E., Siegel, J. A., Oemig, T. V., & Grannis, S. J. (2013). Electronic health information quality challenges and interventions to improve public health surveillance data and practice. Public Health Reports, 128(6), 546-553. https://doi.org/10.1177/003335491312800614

German, R. R., Lee, L. M., Horan, J. M., Milstein, R. L., Pertowski, C. A., & Waller, M. N. (2001). Updated guidelines for evaluating public health surveillance systems: Recommendations from the Guidelines Working Group. MMWR Recommendations and Reports, 50(RR-13), 1-35.

Overhage, J. M., Grannis, S., & McDonald, C. J. (2008). A comparison of the completeness and timeliness of automated electronic laboratory reporting and spontaneous reporting of notifiable conditions. American Journal of Public Health, 98(2), 344-350. https://doi.org/10.2105/AJPH.2006.092700

What the PHLT 8270 Week 5 instructions ask for

Week 5 usually asks students to appraise the quality of data in their surveillance system. Faculty expect specific measures, typically completeness, timeliness and validity, each defined against a standard such as a reporting rule, an operational need or an implementation guide. Completeness should be reported by field, since an overall figure hides the fields that matter most. Timeliness should be measured from the point relevant to the system's purpose. Validity requires checking values against an independent source. Recommendations should target the weakest measures. Expect four or five pages and a completeness table, with citations to work on electronic data quality. A short note on who controls each standard, laboratories, interfaces or isolate shipment, helps readers see where fixes belong.

How the PHLT 8270 Week 5 example is put together

The paper opens by explaining its approach and citing work on data quality dimensions. Table 1 reports completeness for eight required fields, and the text shows how a single average would hide the two weakest. A section sets electronic against faxed reports on the reporting deadline, drawing on published evidence about electronic reporting. A section measures the interval from specimen collection to notification against the containment window. A validity section reports errors found in a sample checked against facility records, citing the evaluation guidelines. A section explains why the three standards differ and who is responsible for each. Sections on laboratory scorecards and recommendations close the paper.

Where the marks sit in the PHLT 8270 Week 5 rubric

Instructors grade a data quality appraisal on measurement, interpretation and action. Defining each measure against a named standard earns the measurement credit, and the sample's field-by-field completeness table shows why that matters. Interpretation is shown in explaining which gaps affect the system's purpose, such as missing facility type misdirecting containment. Including validity, not only completeness, demonstrates thoroughness. Accuracy is checked in the arithmetic and in claims from the cited sources. Action is shown in targeted recommendations and a feedback plan. Table design, structure and referencing account for the last points. Explaining which party is responsible for each kind of gap makes the recommendations easier to assign.

PHLT 8270 Week 5 help: mistakes that cost marks

Data quality appraisals often report a single completeness percentage, which hides the fields that matter. Report by field and explain which ones drive decisions. Define timeliness from the point that matters for your system's purpose, which may be specimen collection rather than report receipt. Do not skip validity; a filled field can still be wrong. Check a sample against an independent source. Tie each measure to a standard, so readers know what good looks like. Recommend changes aimed at the weakest measures and plan how to give laboratories feedback. A free custom appraisal for the data in your own system can be drafted for you. Remember that the clock for containment starts at specimen collection, not at receipt. Share results with each laboratory so the people who can fix the gaps see them.

Get a PHLT 8270 Week 5 example written to your instructions

Send the Week 5 appraisal instructions with the rubric and name the fields your system's follow-up depends on. The appraisal comes back in 24-48h with each measure tied to a named standard, defined for recomputation and split by owner, and a first sample carries no charge. The audit it describes never happened; benchmarks for your system live in its own rules and guides.

More PHLT 8270 papers and PhD in Public Health samples

PHLT 8270 Week 5 questions, answered

Where can I find a free PHLT 8270 Week 5 sample paper?

This page reproduces the complete Week 5 data quality appraisal, measuring a composite state's resistant organism reports against required fields, the reporting deadline and the containment window. The sources cited are real.

Why not report completeness across all fields at once?

An overall figure averages strong and weak fields together. In the sample, overall completeness of about 82% hid the two weakest fields, facility type and carbapenemase testing status, which are the two the containment response depends on.

Where do timeliness standards come from?

From reporting rules, such as a state's deadline for laboratories, and from operational needs, such as how quickly a response must start to be effective. The sample measures against both and shows they can give different answers.

Is validity part of a data quality appraisal?

Yes. Completeness shows whether a field is filled; validity shows whether the value is correct. The sample checked a sample of reports against facility records and found errors that could send a response to the wrong facility.

How can a program improve data quality from laboratories?

By giving each laboratory regular feedback on its own completeness and timeliness, making key fields required in the reporting interface and helping laboratories that use the same software adopt fixes others have made.