HIM 220 Module 4 Project One Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 220 Module 4 Project One sample builds the document that ends arguments over whose number is right. It is written for SNHU HIM 220 (HIM-220), and its BS Health Information Management readers see how a data dictionary makes a measure reproducible. The composite system of two hospitals and eleven clinics reported readmission rates of 14.2% and 11.6% from the same data because two teams used unwritten, different rules. The project identifies users and purposes, defines three labeled versions of the readmission measure, recalculates each to show how the two figures arise, documents every data element with its type, allowed values, source, owner and business rules, sets version control and validates the definitions with a chart review.

CourseHIM 220 Healthcare Data Management
ModuleModule 4
Paper typeundergraduate project building a data dictionary for a readmission dashboard
LengthAbout 1,020 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramBS Health Information Management
UpdatedSeptember 2026

Free sample paper for HIM 220 Module 4

1

Project One: One Measure, Written Down, a Readmission Data Dictionary for Kettle River Health

[Student Name]

Southern New Hampshire University

HIM 220: Healthcare Data Management

Project 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.

What this page is doingThe title states the project's goal of a written, shared definition.
2

Project One: One Measure, Written Down, a Readmission Data Dictionary for Kettle River Health

Kettle River Health's leaders saw two readmission rates for the same months and could not tell which to believe. The first module traced the gap to definitions nobody had written down. This project writes them down. It describes who uses readmission data and why, defines three labeled measure versions, documents each data element and sets rules for maintaining the dictionary.

What this page is doingThe introduction states the project's purpose.
3

What a Data Dictionary Does

A data dictionary is a shared reference that defines each data element and measure: its name, meaning, format, allowed values, source, owner and the rules used to calculate or derive it. Kahn et al. (2016) emphasized that data quality depends on conformance to agreed definitions; a dictionary is where those definitions live. It also makes reports reproducible, so two analysts following the same entry should get the same number.

What this page is doingThe purpose of a data dictionary is explained.
4

Users and Purposes

Three groups use readmission data for different purposes. The quality department wants to find every patient who returns to any Kettle River site so care transitions can improve. Finance wants to anticipate penalties and payer contract measures, which count only certain returns. The board wants a single headline figure it can track over time. One definition cannot serve all three, so the dictionary defines three measures, each labeled with its purpose.

What this page is doingUsers and purposes are identified.
5

Measure A: System All-Cause Return

Measure A, for quality improvement, counts any inpatient admission or observation stay at either Kettle River hospital within 30 days after an index inpatient discharge, for patients of any age and payer. It excludes index stays ending in death, transfer to another acute hospital or discharge against medical advice. Planned returns are included, since quality staff review them separately. Zuckerman et al. (2016) showed that observation stays rose as readmissions fell under Medicare's penalty program, which is why this measure counts observation returns.

What this page is doingThe first measure definition is documented.
6

Measure B: Unplanned Inpatient Return, Same Hospital

Measure B, for finance and contract monitoring, counts unplanned inpatient readmissions to the same hospital within 30 days after an index inpatient discharge. It excludes observation stays, planned readmissions identified by a documented scheduled procedure or chemotherapy list, index stays ending in death, transfer or discharge against medical advice and returns to the other hospital. This matches how the finance team calculated 11.6%.

What this page is doingThe second measure definition is documented.
7

Measure C: Board Headline

Measure C, for the board, counts unplanned inpatient or observation returns to either hospital within 30 days, excluding planned returns and the same index exclusions. It sits between the other two and changes little when coding practices shift between inpatient and observation status. Joynt and Jha (2012) cautioned that readmission rates reflect patient and community factors as well as hospital care, so the board report will show Measure C alongside the share of index patients living in high-deprivation neighborhoods.

What this page is doingThe third, headline measure is documented with context.
8

Reconciling the Two Figures

Recalculating last quarter's data under each definition reproduces both original numbers and explains the gap. Measure A yields 14.2%, matching the quality report. Measure B yields 11.6%, matching finance. Measure C yields 12.9%. About half the difference between A and B comes from observation returns, a third from planned readmissions and the rest from returns to the other hospital.

Table 1. Three Readmission Measures, Same Quarter

MeasurePurposeObservation returnsPlanned returnsOther hospitalRate
A: System all-cause returnQuality improvementIncludedIncludedIncluded14.2%
B: Unplanned inpatient, same hospitalFinance and contractsExcludedExcludedExcluded11.6%
C: Board headlineGovernanceIncludedExcludedIncluded12.9%

Note. Recalculated by the author from warehouse data for the most recent quarter.

What this page is doingThe reconciliation is shown in Table 1.
9

Element-Level Entries

Each measure depends on data elements that also need definitions. Table 2 shows selected entries. Every entry lists the element's name, definition, data type, allowed values, source system, owner and any business rule. Owners are roles, not individuals, so entries survive staff turnover.

Table 2. Selected Data Dictionary Entries

ElementDefinitionType and allowed valuesSourceOwnerBusiness rule
Index dischargeInpatient encounter with a discharge date and timeEncounter record; type = inpatientEHR encounter tableHIM data integrity leadExclude disposition = expired, acute transfer, against medical advice
Return encounterInpatient or observation encounter after an index dischargeType in (inpatient, observation)EHR encounter tableHIM data integrity leadAdmit time minus index discharge time between 0 and 30 days
Encounter typeLevel of care at registration and final statusInpatient, observation, emergency, outpatientRegistration; utilization reviewPatient access managerUse final status after utilization review
Planned return flagReturn scheduled in advance for a listed procedure or therapyYes or noScheduling system; planned listQuality analytics leadPlanned list reviewed yearly
Patient identifierEnterprise identifier after duplicate mergeNumeric; uniqueMaster patient indexHIM MPI coordinatorUse merged identifier, never source-system ID

Note. Selected entries; the full dictionary contains 24 elements.

What this page is doingSelected element entries appear in Table 2.
10

Rules That Prevent Drift

Definitions drift when people change them quietly. Every change will be requested in writing, reviewed by the data governance committee and recorded with a version number, effective date and reason. Reports will display the measure name and dictionary version beneath each chart. Retired definitions stay in the dictionary so historical reports can be reproduced. New analysts will be trained on the dictionary during orientation, and any report built outside it will carry a warning label until it is reviewed.

What this page is doingVersion control rules are set.
11

Validating the Definitions

To confirm the dictionary works as intended, a sample of 50 index discharges was reviewed against the full record. Measure logic matched the chart in 47 cases. The three mismatches involved observation stays later converted to inpatient status, which the warehouse had captured before utilization review finished. The encounter type entry now specifies using the final status, and the warehouse load will wait 72 hours after discharge before classifying encounters.

What this page is doingA chart review validates the definitions.
12

Connections to Data Quality

The dictionary also depends on the quality problems identified in Module Two. Duplicate records can hide readmissions when a patient's two stays sit under different identifiers, which is why the patient identifier entry requires the merged enterprise number. Implausible timestamps can create negative intervals, so the return encounter rule rejects them for review.

What this page is doingLinks to earlier data quality findings are explained.
13

Conclusion

Writing down three purpose-specific definitions ended the argument over Kettle River's readmission rate: both numbers were right for their purposes, and a third serves the board. Element-level entries with owners and business rules, version control and validation make the measures reproducible. The next module calculates core healthcare statistics using the same discipline.

What this page is doingThe conclusion summarizes the project.
14

References

Joynt, K. E., & Jha, A. K. (2012). Thirty-day readmissions: Truth and consequences. New England Journal of Medicine, 366(15), 1366-1369. https://doi.org/10.1056/NEJMp1201598

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 18. https://doi.org/10.13063/2327-9214.1244

Zuckerman, R. B., Sheingold, S. H., Orav, E. J., Ruhter, J., & Epstein, A. M. (2016). Readmissions, observation, and the Hospital Readmissions Reduction Program. New England Journal of Medicine, 374(16), 1543-1551. https://doi.org/10.1056/NEJMsa1513024

What the HIM 220 Module 4 instructions ask for

HIM 220 Project One generally asks you to create a data dictionary, or part of one, for a healthcare measure, report or database. Around 1,400 to 1,800 words with tables and at least three scholarly sources in APA 7 suits most versions. Identify users and purposes, define each measure precisely, including inclusions and exclusions, and document data elements with definitions, types, allowed values, sources, owners and business rules. Show how you would maintain the dictionary and test that the definitions produce correct results. Where possible, reconcile any conflicting numbers your organization already reports, since that shows the dictionary solving a real problem. HIM 220 graders notice clean headings in HIM 220 papers. HIM 220 names and dates need checking before HIM 220 submission. HIM 220 prompts vary by term, so recheck HIM 220 directions.

How this HIM 220 Module 4 project one example is built

The project explains what a data dictionary does using Kahn and colleagues' emphasis on conformance, identifies three user groups and defines three labeled readmission measures. Zuckerman and colleagues' observation findings justify including observation returns in the quality measure, and Joynt and Jha's caution shapes the board measure. A table reproduces the 14.2% and 11.6% figures and a middle 12.9%. Element entries, version control, a 50-case chart review with three mismatches and links to duplicate records complete it. Each entry names an owning role, so the dictionary survives staff changes. HIM 220 students can reuse this structure for HIM 220 work. HIM 220 claims here trace to cited HIM 220 sources. HIM 220 readers can adapt each section to HIM 220 data.

Where the HIM 220 Module 4 rubric puts the points

Data dictionary projects in HIM 220 are commonly graded on precision of definitions, completeness of element entries, attention to users and purposes, business rules, maintenance and validation and APA 7 mechanics. Standout projects reconcile conflicting figures using the new definitions, assign owners by role and test definitions against source records. Graders reward entries specific enough that another analyst could reproduce the number without asking questions. Clear version control and a documented validation step show that the writer expects definitions to be maintained, not written once and forgotten. HIM 220 marks favor careful formatting across HIM 220 sections. HIM 220 citations keep every HIM 220 argument credible. HIM 220 instructors weigh evidence heavily in HIM 220 grading.

HIM 220 Module 4 help: the mistakes that cost points

Dictionary projects lose points when definitions are vague, when inclusions and exclusions are missing, when elements lack sources or owners or when there is no plan to keep definitions current. Another frequent gap is assuming one definition can serve every purpose. Define precisely, document every element, assign owners, add version control and validate. If your prompt names a different measure, such as length of stay or no-show rate, send it with your HIM 220 notes so the dictionary covers it. Sample reports or screenshots of current dashboards, with identifying details removed, help the project reconcile real figures. HIM 220 drafts start well from a HIM 220 outline. HIM 220 feedback already received guides HIM 220 revisions. HIM 220 rubrics posted in Brightspace clarify HIM 220 expectations.

Get HIM 220 Module 4 written to your instructions

Send the HIM 220 Project One prompt and the measure or report you are documenting. The project will define purpose-specific measures, document each element with type, allowed values, source, owner and business rules and add maintenance and validation steps, within 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 220 papers and related BS Health Information Management samples

HIM 220 Module 4 questions, answered

Where can I find a free HIM 220 Module 4 Project One sample?

HIM 220 Project One appears in full: a readmission dashboard data dictionary with three labeled definitions, element entries, owners and validation.

What belongs in a data dictionary entry?

The element's name, definition, data type, allowed values, source system, owner and any business rules used to derive it.

Why can two readmission rates both be correct?

They may use different inclusions, such as observation stays, planned returns or other hospitals, suited to different purposes.

How do you keep a data dictionary current?

Require written change requests, governance review and version numbers with effective dates, and display the version on reports.

How can a data dictionary be validated?

Compare measure results for a sample of cases against the full record and correct any definitions that produce mismatches.