HI499 Unit 1 Discussion Post Example

Reviewed by Chester Goodwin, MBA Bachelor's Capstone in Health Information Management Purdue University Global Free custom sample in 24 to 48h

This HI499 Unit 1 discussion post chooses a capstone topic by asking which department problem can already be counted. Purdue Global HI 499 opens the BS in Health Information Management capstone with topic selection, and the sample tests three candidates at the composite Callowfield Health system against the same three questions. Release-of-information turnaround fails because five request types run on separate clocks. Outpatient surgery coding accuracy fails because the only figures sit in an outside auditor's report. Duplicate records created by the online self-scheduling tool survive: the merge log already holds every confirmed pair with its source, about 88 a month, and one analyst owns the tool's settings. A paragraph previews the privacy, coding, payment and safety angles, and the reply asks a classmate how incomplete discharge summaries would be counted.

CourseHI499 Bachelor's Capstone in Health Information Management
UnitUnit 1
Paper typeDiscussion board post
LengthAbout 490 words, 2 pages double-spaced
FormatAPA 7 discussion post
SchoolPurdue University Global
ProgramBS in Health Information Management
UpdatedOctober 2026

Free sample paper for HI499 Unit 1

1

Three Department Problems, One Monthly Count Already on File: Choosing a Capstone Topic by What the Merge Log Can Measure

HI499 · Unit 1 Discussion Board Post

Posted by [Student Name]

Callowfield Health, its departments and its figures are composite; the sources cited are real.

What this part is doingPutting the chosen problem and its monthly figure in the first sentence shows the grader that the topic is measurable before any argument is made.
2

Initial Post

My capstone problem is duplicate patient records created by Callowfield Health's online self-scheduling tool, which the data integrity desk confirms at a rate of about 88 a month. I reached it by asking three questions of every candidate, in the same order: can the department count it this month from records it already keeps, does one process produce most of it, and could a change show up in the count before the term ends? I started with release-of-information turnaround, because requesters complain about it often. It failed the second question. Our office handles five request types, from patient portal requests to attorney subpoenas, and each runs on its own clock under its own rules. No single change could move all five within ten units, and averaging them would hide which one is slow. Outpatient surgery coding accuracy came next. It failed the first question. The only accuracy figures come from an outside auditor's annual report, which goes to the compliance office and is not shared with students, and a sample of my own would be too small to show change. The duplicate problem survived because the department already counts it: every confirmed pair sits in the merge log with the registration source that created it. The merge log is kept by two data integrity specialists and read by almost nobody else. It shows that the self-scheduling tool, launched eighteen months ago, creates under a fifth of new records but a much larger share of duplicates. One application analyst owns the tool's settings, so a change has one owner. And because the log closes every month, a change made in Unit 7 could appear in the count before the final paper. Duplicate records are a known national problem, with mismatched names, addresses and birth dates as the usual culprits (Just et al., 2016), but this one has a local source I can point to. The problem will also have to survive four other views: privacy, because a wrong match can expose someone else's record; coding, because a split record hides history; payment, because authorizations can sit on the other record; and patient safety, because an allergy recorded on one record is invisible on its twin (McCoy et al., 2013). Question for the class: has anyone found a problem whose data is already counted somewhere that nobody looks?

Reply to Classmate

Priya, your topic of incomplete discharge summaries is important, but I am not sure how you will count it. Is "incomplete" defined anywhere at your organization, such as a deficiency category in the record completion system? If it is, you may already have a monthly number. If not, defining it might become the project.

3

References

Just, B. H., Marc, D., Munns, M., & Sandefer, R. (2016). Why patient matching is a challenge: Research on master patient index (MPI) data discrepancies in key identifying fields. Perspectives in Health Information Management, 13(Spring), 1e.

McCoy, A. B., Wright, A., Kahn, M. G., Shapiro, J. S., Bernstam, E. V., & Sittig, D. F. (2013). Matching identifiers in electronic health records: Implications for duplicate records and patient safety. BMJ Quality & Safety, 22(3), 219-224. https://doi.org/10.1136/bmjqs-2012-001419

What the HI499 Unit 1 assignment asks for

The capstone's first discussion usually asks you to propose a problem from a real or composite health information setting and explain why it suits a ten-unit project. Expect to describe the problem, the data that would measure it and why it matters to the organization. Many prompts ask you to compare two or three candidates before settling on one, which shows judgment rather than enthusiasm. Feasibility carries weight here: data you can actually reach, one process you can study and a change visible within the term. A source on the problem's wider importance helps, though local evidence matters more. A question for classmates is normally part of the post, and replies should help a peer sharpen a topic rather than praise it. Keep any organization or patient details composite.

Inside the HI499 Unit 1 example

The post names its chosen problem and the monthly figure in the first sentence, then states the three questions it put to every candidate. Each rejected topic gets one paragraph that ends on the question it failed, so the survivor arrives with its reasons already set out. The highlighted sentence explains why the duplicate problem lasted: the merge log already records every confirmed pair and its source. A paragraph on the tool notes that it creates under a fifth of new records but a larger share of duplicates, has a single owner and closes its count monthly. Published work on mismatched demographic fields places the problem in a national context. The closing paragraph previews four lenses later units will use, and the reply asks a classmate whether incomplete discharge summaries have any existing deficiency category to count.

Where the points sit in the HI499 Unit 1 rubric

Capstone topic posts are generally graded on the clarity of the problem, its feasibility, its significance and participation. Clarity points require a problem stated in one sentence with a setting and, ideally, a number. Feasibility often carries the largest share: the grader looks for data the student can reach, a process narrow enough to change and a timeline that fits the term. Students lose points by choosing broad topics such as improving data quality, which cannot be measured or changed in ten units. Significance points reward a link between the local problem and its consequences for patients or the organization, supported by a source. Comparing candidates and explaining the choice can earn credit beyond the minimum. Participation points go to replies that ask a peer a specific, useful question about measurement or scope.

HI499 Unit 1 help: mistakes that cost points

A common weakness in Unit 1 is a topic chosen for interest without any data to measure it. Another is a problem so broad, like interoperability or coding quality, that no single change could move it within the course. Some posts describe the problem without saying who owns the process, which matters when a later unit asks for an implementation plan. Students also skip the comparison and present one idea as the obvious choice, which hides their reasoning. Replies that only encourage a classmate rarely earn participation credit. Citing national statistics without any local figure leaves the topic abstract. If you are weighing candidate problems for your own capstone, send the setting, the problems you are considering and any data you can access, and we can draft a post that tests each one and lands on a measurable topic.

Get an HI499 Unit 1 example written to your instructions

A line on your setting, workplace or composite, helps most here, along with the Unit 1 prompt and rubric. Candidate problems are chosen so that setting could actually count them, and replies come on request. Alternatives appear only where the prompt asks for a comparison. Delivery runs 24-48h, and a first custom sample carries no fee. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More HI499 papers and BS in Health Information Management samples

HI499 Unit 1 questions, answered

Where can I find a free HI499 Unit 1 sample paper?

The finished Unit 1 discussion post sits on this page; it compares three capstone problems and chooses duplicate records from online self-scheduling.

How do I choose a capstone topic in HI 499?

Test each candidate for data you can count now, a single process that produces most of the problem and a change visible before the term ends.

What makes a capstone problem feasible?

Accessible data, one process owner and a measure that closes monthly. The sample's merge log met all three.

Should I use national statistics for my topic?

Use them for context, but choose a problem with a local figure. The sample's 88 duplicates a month came from the department's own log.

What should a capstone discussion reply do?

Help a classmate measure or narrow the topic. The sample reply asks whether incomplete discharge summaries are already counted anywhere.