HIM 220 Module 7 Project Two Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 220 Module 7 Project Two sample assembles the course's findings into a plan a health system could fund. It is written for SNHU HIM 220 (HIM-220), and it shows BS Health Information Management students how to move from assessment to improvement. The composite system of two hospitals and eleven clinics has five measured data problems: 6.4% suspected duplicate records, 19% missing race and ethnicity, 12% of reference laboratory results without standard codes, problem lists current for only 58% of primary care patients and implausible hospital timestamps. The plan sets a target for each, fixes each at the point where the data are created, assigns stewards and owners, defines a quarterly scorecard, sets a timeline and budget and explains how staff will be engaged and results evaluated.

CourseHIM 220 Healthcare Data Management
ModuleModule 7
Paper typeundergraduate data quality improvement plan for a health system
LengthAbout 1,000 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramBS Health Information Management
UpdatedSeptember 2026

Free sample paper for HIM 220 Module 7

1

Project Two: Fixing Data Where It Starts, a Data Quality Improvement Plan for Kettle River Health

[Student Name]

Southern New Hampshire University

HIM 220: Healthcare Data Management

Project Two

[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 plan's principle of fixing problems at the point of capture.
2

Project Two: Fixing Data Where It Starts, a Data Quality Improvement Plan for Kettle River Health

Summary

Kettle River Health's data problems are measurable, and most begin where data are first recorded. This plan targets five problems identified in the Module Two assessment and assigns each to the governance roles defined in Module Six. Over twelve months it aims to cut suspected duplicates from 6.4% to below 2%, missing race and ethnicity from 19% to below 5% and unmapped laboratory results from 12% to below 2%, while raising problem list currency to 80% and eliminating implausible timestamps from reports. First-year costs are about $96,000.

What this page is doingThe summary states the problems, targets and cost.
3

Guiding Principles

Three principles shape the plan. Fix problems at the point of capture rather than cleaning them repeatedly downstream. Judge quality by fitness for use, as Kahn et al. (2016) recommend, so each target is tied to a purpose such as safety or equity reporting. And measure every problem with a repeatable method so progress can be seen, drawing on the dimensions Weiskopf and Weng (2013) described.

What this page is doingGuiding principles are stated with research.
4

Problem 1: Duplicate Records

Target: suspected duplicates below 2% and confirmed overlays at zero. Actions: adopt the registration search standard requiring three search attempts with name variations; add photo capture at registration; standardize address and name formats; and fund a temporary merge specialist for six months to clear the 9,000-pair backlog. Grannis et al. (2019) found that standardizing fields improved matching sensitivity only modestly, so the plan relies on search behavior and photos as well. Owner: vice president of revenue cycle. Steward: HIM MPI coordinator.

What this page is doingThe duplicate record plan is set out.
5

Problem 2: Missing Race and Ethnicity

Target: missing below 5% at every site within twelve months. Actions: adopt one script and category list; let patients self-report on check-in tablets and in the portal; train registration staff, especially in the emergency department, to explain why the question matters; and add a completeness report by registrar. Polubriaginof et al. (2019) found that 86% of patients gave meaningful answers when self-reporting, which supports shifting collection toward patients. Owner: chief equity officer. Steward: equity office analyst.

What this page is doingThe race and ethnicity plan is set out.
6

Problem 3: Unmapped Laboratory Results

Target: unmapped reference laboratory results below 2%. Actions: map the 140 local test names now lacking codes, require LOINC codes in the reference laboratory contract renewal and set the interface to hold unmapped results in a review queue rather than loading them silently. McDonald et al. (2003) described LOINC as the means by which results from different laboratories are recognized as the same test, so mapping restores those results to dashboards and registries. Owner: chief medical information officer. Steward: laboratory information system analyst.

What this page is doingThe laboratory mapping plan is set out.
7

Problem 4: Stale Problem Lists

Target: 80% of primary care patients with a problem list reviewed in the past year. Actions: add a problem list review step to annual wellness and chronic care visit templates, give medical assistants a pre-visit checklist that flags resolved conditions for clinician review and share clinic-level currency rates monthly. Owner: vice president of ambulatory care. Steward: primary care nurse informaticist.

What this page is doingThe problem list plan is set out.
8

Problem 5: Implausible Timestamps

Target: no negative lengths of stay or stays over 400 days reaching reports without review. Actions: add warehouse plausibility checks that route suspect records to the nursing informatics team within 48 hours and revise downtime procedures so staff record actual times on paper forms for later entry. Owner: chief nursing officer. Steward: nursing informatics lead.

What this page is doingThe timestamp plan is set out.
9

The Quarterly Scorecard

Stewards will report each measure quarterly to the governance committee. Table 1 lists baselines, targets and measurement methods.

Table 1. Data Quality Scorecard

MeasureBaseline12-month targetMethod
Suspected duplicate rate6.4%Below 2%MPI software flags; monthly sample review
Race and ethnicity missing19%Below 5% at every siteWarehouse completeness query by site
Unmapped reference lab results12%Below 2%Interface review queue count
Problem list reviewed in past year58%80%EHR report, primary care patients
Implausible timestamps reaching reports212 per year0 unreviewedWarehouse plausibility check log

Note. Baselines from the Module Two assessment.

What this page is doingThe scorecard is presented in Table 1.
10

Timeline

Months one and two focus on approving the search and demographic standards and hiring the merge specialist. Months three to six launch self-reporting tablets, laboratory mapping and warehouse plausibility checks. Months six to nine add problem list template changes and registrar-level reports. Months ten to twelve evaluate results and set second-year targets.

What this page is doingThe timeline is summarized.
11

Budget

First-year costs total about $96,000: $38,000 for a six-month merge specialist, $22,000 for photo capture at registration desks, $14,000 for check-in tablet configuration and self-reporting screens, $12,000 for laboratory mapping support from the vendor, $6,000 for training time and $4,000 for reporting development. Savings are harder to count but real: fewer repeated tests from split records, less analyst time reconciling reports and fewer rejected exchange transactions.

What this page is doingThe budget is itemized.
12

Engaging the People Who Create the Data

Registration staff, medical assistants and nurses create most of the data this plan improves. Each group will help design the changes that affect them, receive feedback on their own performance rather than only system averages and see how better data help patients, such as a duplicate that hid an allergy. Early wins will be publicized, and the governance committee will recognize high-performing sites.

What this page is doingThe change management approach is described.
13

Risks

Registration may slow as staff search more carefully, so the search standard will be tested at two desks before rollout. Patients may worry about why race and ethnicity are asked, so scripts will explain the purpose and allow a declined answer. The reference laboratory may resist contract changes, so the mapping team will prepare codes in advance to reduce its burden.

What this page is doingRisks and mitigations are described.
14

Evaluation

At twelve months, the plan will be judged on whether scorecard targets were met, whether the readmission and equity dashboards changed as data improved and whether registration times rose by more than a minute on average. A brief survey of stewards will assess whether the governance process supported or slowed their work.

What this page is doingEvaluation criteria are defined.
15

Conclusion

Each of Kettle River's data problems has a measurable target, an owner, a steward and a fix at the point of capture. With a quarterly scorecard, a modest budget and front-line staff involved in the changes, the system can make its dashboards trustworthy and its data fit for the uses that matter most: safety, equity and sound decisions.

What this page is doingThe conclusion summarizes the plan.
16

References

Grannis, S. J., Xu, H., Vest, J. R., Kasthurirathne, S., Bo, N., Moscovitch, B., Torkzadeh, R., & Rising, J. (2019). Evaluating the effect of data standardization and validation on patient matching accuracy. Journal of the American Medical Informatics Association, 26(5), 447-456. https://doi.org/10.1093/jamia/ocy191

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

McDonald, C. J., Huff, S. M., Suico, J. G., Hill, G., Leavelle, D., Aller, R., Forrey, A., Mercer, K., DeMoor, G., Hook, J., Williams, W., Case, J., & Maloney, P. (2003). LOINC, a universal standard for identifying laboratory observations: A 5-year update. Clinical Chemistry, 49(4), 624-633. https://doi.org/10.1373/49.4.624

Polubriaginof, F. C. G., Ryan, P., Salmasian, H., Shapiro, A. W., Perotte, A., Safford, M. M., Hripcsak, G., Smith, S., Tatonetti, N. P., & Vawdrey, D. K. (2019). Challenges with quality of race and ethnicity data in observational databases. Journal of the American Medical Informatics Association, 26(8-9), 730-736. https://doi.org/10.1093/jamia/ocz113

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 220 Module 7 instructions ask for

HIM 220 Project Two generally asks for a plan to improve data quality or data management in a healthcare organization, building on earlier assessment work. Around 1,400 to 1,800 words with tables and four or more scholarly sources in APA 7 fits most versions. Set measurable targets tied to data uses, propose fixes at the point of capture, assign owners and stewards, define a scorecard with methods and include a timeline, budget, engagement plan, risks and evaluation. Cite research that supports each major strategy. 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 7 project two example is built

The plan targets five problems measured earlier, with principles drawn from Kahn and colleagues and Weiskopf and Weng. Duplicates are addressed by a search standard, photos and a merge specialist, informed by Grannis and colleagues; race and ethnicity by self-reporting based on Polubriaginof and colleagues; unmapped results by LOINC mapping citing McDonald and colleagues; plus problem list templates and timestamp checks. A scorecard table, timeline, $96,000 budget, staff engagement, risks and evaluation criteria complete it. Each problem has a named owner and steward, so accountability is explicit. 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 7 rubric puts the points

Data quality improvement plans in HIM 220 are commonly graded on measurable targets, fixes that address root causes, clear ownership, a repeatable measurement method, feasibility of timeline and budget, attention to people and workflow and APA 7 mechanics. The strongest plans link every action to a documented problem, cite research for key strategies and anticipate side effects such as slower registration. Scorecards with baselines and methods show that progress can be verified. Plans that name who will review progress, and how often, make it clear the work will continue after launch. 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 7 help: the mistakes that cost points

Improvement plans lose points when they propose downstream cleanup instead of capture fixes, when targets lack baselines, when no one owns each problem or when budgets and timelines are missing. Another frequent gap is ignoring the staff who create the data. Tie actions to problems, set targets, assign roles, define measures, budget and plan engagement. If your prompt focuses on a specific data problem or requires a particular improvement model, send it with your HIM 220 notes so the plan follows it. 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 7 written to your instructions

Send the HIM 220 Project Two prompt and your earlier assessment findings. The plan will set measurable targets, propose fixes at the point of capture, assign owners and stewards, build a scorecard and add a timeline, budget and engagement plan, 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 7 questions, answered

Where can I find a free HIM 220 Module 7 Project Two sample?

Every section of HIM 220 Project Two is published here: a health system's data quality plan with targets, fixes at the point of capture, a scorecard and budget.

Why fix data quality at the point of capture?

Cleaning data downstream must be repeated forever; fixing the process that creates errors prevents them.

What belongs in a data quality scorecard?

Each measure's baseline, target, measurement method and owner, reviewed on a regular schedule.

How can hospitals reduce duplicate records?

Require thorough searches with name variations at registration, capture photos, standardize fields and clear backlogs.

How do you evaluate a data quality plan?

Check whether targets were met, whether dependent reports changed and whether workflows such as registration slowed.