| Course | HIM 550 Data Management and Data Quality |
|---|---|
| Module | Module 3 |
| Paper type | graduate milestone assessing the quality of a hospital discharge data set |
| Length | About 1,130 words, 7 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | MS Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 550 Module 3
Final Project Milestone One: Can We Trust the Discharge Data? A Quality Assessment at Cypress Hollow Medical Center
[Student Name]
Southern New Hampshire University
HIM 550: Data Management and Data Quality
Final Project Milestone One
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Final Project Milestone One: Can We Trust the Discharge Data? A Quality Assessment at Cypress Hollow Medical Center
Cypress Hollow Medical Center wants to know whether discharging patients earlier in the day would shorten length of stay and free beds for the emergency department. Before that question can be answered, the data used to answer it must be tested. This milestone assesses the quality of the hospital's inpatient discharge data set for the six months from January through June, describes the methods used, reports the findings field by field and ranks the problems by how much they would distort the analysis planned for the next milestone.
Purpose and Scope
The assessment has one purpose: to decide whether each field needed for a discharge timing analysis is fit for that use. It therefore examines nine fields rather than the full record: encounter number, admission date and time, the registration discharge time, the nursing departure time, admission source, admission type, nursing unit, discharge disposition and principal diagnosis. Fields that the analysis does not need, such as payer and attending physician, were left for later work. Limiting the scope keeps the assessment focused on the question leaders are asking.
Data Set and Methods
The extract drew 9,840 inpatient discharges from the data warehouse, excluding observation stays and newborns. Each field was profiled for missing values, allowed values and ranges, and then compared with a second source where one existed: the nursing departure time against the registration discharge time, unit codes against the bed management system and principal diagnosis against a sample of 120 records reviewed by a credentialed coder.
The checks follow the harmonized framework of Kahn et al. (2016), which groups data quality into conformance, completeness and plausibility and asks each to be judged against the intended use. Weiskopf and Weng (2013) add concordance between sources and currency, and both were useful here. Hripcsak and Albers (2013) warned that record data reflect the process of care as much as the patient's condition, which meant each timestamp had to be traced to the workflow step that creates it.
Summary of Findings
Table 1 summarizes the results for each field. Four fields are fit for the analysis as they stand, three need correction or a substitute and two carry limitations that must be stated with any results.
Table 1. Quality Assessment of Nine Discharge Fields, January to June (n = 9,840)
| Field | Complete | Main problem found | Fit for timing analysis? |
|---|---|---|---|
| Encounter number | 100% | None | Yes |
| Admission date and time | 100% | 37 records after departure time | Yes, after correction |
| Registration discharge time | 100% | Records encounter close, median 3.4 hours after departure | No |
| Nursing departure time | 91% | Missing mostly for deaths, transfers and patients leaving against advice | Yes, with rules for gaps |
| Admission source | 88% | Blanks loaded as Other in warehouse | Limited |
| Admission type | 99.7% | None of note | Yes |
| Nursing unit | 100% | Codes changed March 14; one old code maps to two units | Yes, after crosswalk |
| Discharge disposition | 99.9% | Small conflicts with case management notes | Yes |
| Principal diagnosis | 100% | Coder review agreed on 111 of 120 records | Limited |
Note. Prepared by the author from a warehouse extract and a coder review sample.
Discharge Time: Valid but Unfit
The registration discharge time passes every conformance and completeness check. It is always present, always a valid date and time and never earlier than admission. It fails on relevance. Comparing it with the nursing departure time on the 8,954 records with both values showed a median gap of 3.4 hours, with a longer gap on the medical units, where clerks close encounters in a batch after lunch. By departure time, 37% of patients left before noon; by registration time, only 29% did. A timing analysis built on the registration field would misstate both the problem and any change in it.
Admission Source and Nursing Unit
Admission source is blank on 1,181 records, or 12%, and the warehouse loads those blanks as Other, which makes Other the third largest category in every report. The blanks are not random. They cluster on nights and weekends in the emergency department, when registrars are fewest, so any comparison of patients admitted from home and from other facilities would be biased toward daytime admissions.
Nursing unit codes changed on March 14 when two medical units were reorganized into three. Records before that date use the old codes, and one old code now corresponds to two new units. A crosswalk built with the bed management team assigns 94% of the affected records by room number; the remainder are grouped as a combined unit for the first quarter.
Plausibility and Concordance Checks
Thirty-seven records show a nursing departure time earlier than the admission time. Each traced to manual entry on a downtime form after a system outage in February, and each was corrected against the paper form. Discharge disposition conflicted with case management notes in 11 records, all involving patients whose planned transfer to a skilled nursing facility changed at the last moment.
Principal diagnosis agreed with the coder's review in 111 of 120 sampled records, about 93%. The nine disagreements involved sequencing choices rather than wrong conditions. A systematic review by Burns et al. (2012) found wide variation in the accuracy of routine discharge coding across studies, so a local sample was worth the effort, and diagnosis groupings in the analysis will be broad enough that sequencing differences matter little.
Why the Problems Occur
Each major problem begins in a workflow, not in the warehouse. The discharge time reflects a billing step performed when clerks have time. Admission source is optional at registration and is skipped during busy hours. Unit codes changed without an update to warehouse documentation, and the loading rule that turns blanks into Other was written years ago without a record of why. These causes matter for the recommendations milestone, because a cleaning rule applied to the extract would hide each problem without preventing it.
Priorities for the Analysis
The problems are ranked by their effect on the planned analysis. First, the analysis will use nursing departure time, with rules for the 9% of records where it is missing: deaths and transfers will be excluded, and patients leaving against advice will be analyzed separately. Second, the unit crosswalk will be applied before any unit comparison. Third, results by admission source will be reported with the missing group shown rather than folded into Other. Fourth, the coder sample will be noted as a limitation. Each rule will be written down so the analysis can be repeated next quarter.
Conclusion
The discharge data set is usable for a timing analysis, but only after replacing the field leaders have trusted for years. The departure time, a unit crosswalk and honest reporting of missing admission sources make the next milestone's analysis defensible. The same findings also point to the fixes that the final data management plan must address at the point where the data are created, beginning with the registration screen and the nightly load.
References
Burns, E. M., Rigby, E., Mamidanna, R., Bottle, A., Aylin, P., Ziprin, P., & Faiz, O. D. (2012). Systematic review of discharge coding accuracy. Journal of Public Health, 34(1), 138-148. https://doi.org/10.1093/pubmed/fdr054
Hripcsak, G., & Albers, D. J. (2013). Next-generation phenotyping of electronic health records. Journal of the American Medical Informatics Association, 20(1), 117-121. https://doi.org/10.1136/amiajnl-2012-001145
Kahn, M. G., Callahan, T. J., Barnard, J., Bauck, A. E., Brown, J., Davidson, B. N., Estiri, H., Goerg, C., Holve, E., Johnson, S. G., Liaw, S.-T., Hamilton-Lopez, M., Meeker, D., Ong, T. C., Ryan, P., Shang, N., Weiskopf, N. G., Weng, C., Zozus, M. N., & Schilling, L. (2016). A harmonized data quality assessment terminology and framework for the secondary use of electronic health record data. eGEMs, 4(1), Article 1244. https://doi.org/10.13063/2327-9214.1244
Weiskopf, N. G., & Weng, C. (2013). Methods and dimensions of electronic health record data quality assessment: Enabling reuse for clinical research. Journal of the American Medical Informatics Association, 20(1), 144-151. https://doi.org/10.1136/amiajnl-2011-000681
What the HIM 550 Module 3 instructions ask for
Milestone One of the HIM 550 final project asks for a data quality assessment of the data set your analysis will use. Expect about four to six pages in APA 7 with several scholarly sources. Describe the data set and its source, state the purpose the data must serve and choose the fields that purpose requires. Explain your methods, including profiling for missing and invalid values and comparisons with a second source, and name the quality dimensions you tested using a published framework. Report findings field by field, ideally in a table, explain why each problem occurs in the workflow or system and rank the problems by how much each would distort the analysis you plan next.
How this HIM 550 Module 3 final project milestone one example is built
Cypress Hollow Medical Center's data manager profiles 9,840 discharges from January to June and tests nine fields using Kahn and colleagues' conformance, completeness and plausibility and Weiskopf and Weng's concordance and currency. The registration discharge time is always present and valid but trails nursing departure by a median of 3.4 hours, so 37% of patients left before noon rather than 29%. Admission source is blank on 12% of records, clustered at night, unit codes need a crosswalk after a March reorganization and a coder sample agrees on 111 of 120 diagnoses. The HIM 550 milestone ranks each problem and turns it into a written analysis rule, leaving workflow fixes for the final plan.
Where the HIM 550 Module 3 rubric puts the points
Data quality milestones in HIM 550 tend to be graded on a clearly described data set, a purpose that guides which fields are tested, sound profiling methods, named quality dimensions from a published framework, accurate findings, causes traced to workflow and priorities tied to the next analysis, with APA 7 citations throughout. The strongest assessments show that a field can pass technical checks and still be unfit, and they compare fields against a second source rather than trusting one system. Quantified findings, such as exact missing rates and median gaps, earn more credit than general statements. Clear written rules for handling each problem make the later analysis easier to defend.
HIM 550 Module 3 help: the mistakes that cost points
HIM 550 quality assessments lose points when they profile every field without a purpose, report problems without numbers, name dimensions without testing them or quietly clean data without saying so. Many drafts also stop at the extract and never ask which workflow creates each problem. If your data set is different, such as clinic visits, claims or a registry, or if your instructor supplied a practice file, send it and the assessment will be built around those fields. A short description of the question your analysis will answer helps set the scope. HIM 550 milestones we write test fields against their use, compare sources, quantify gaps and rank problems for analysis.
Get HIM 550 Module 3 written to your instructions
Send the HIM 550 Milestone One guidelines and a description of your data set or practice file. The assessment will define the purpose, profile the fields that matter, test named quality dimensions against a second source, report findings in a table with causes and rank problems for your analysis, done in 24 to 48 hours, free the first time. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.
More HIM 550 papers and related MS Health Information Management samples
- HIM 550 Module 1 Discussion: What Fitness for Use Means for Hospital Data
- HIM 550 Module 2 Journal: Following One Data Element Through Its Life Cycle
- HIM 510 Module 10 Reflection: Growth as a Revenue and Compliance Leader
- HIM 520 Module 8 Policy Short Paper: Revising the Remote Work Policy
- HIM 530 Module 10 Reflection: What Protecting Information Taught the Writer
- HIM 500 Module 8 Emerging Technology Short Paper: Artificial Intelligence and Ambient Documentation
HIM 550 Module 3 questions, answered
Where can I find a free HIM 550 Module 3 Milestone One sample?
A full HIM 550 Milestone One paper is on this page: a data quality assessment of 9,840 discharge records, testing each field before analysis begins.
What is data profiling?
Examining a data set's fields for missing values, allowed values, ranges and patterns to find quality problems before analysis.
What are conformance, completeness and plausibility?
Whether values follow the expected format, whether they are present and whether they are believable given other data and clinical sense.
Why compare a field with a second source?
Concordance checks reveal errors that a single source cannot show, such as a timestamp that records the wrong event.
Should a quality assessment fix the data?
It should document problems and handling rules openly; lasting fixes belong where the data are created.