Errors sorted by origin, not by severity, is what the Week 5 audit in this HLTH 2120 sequence produces, with a claim about which entry point causes most of them. Searches like "hlth 2120 week 5 assignment example", "hlth2120 week 5 sample" and "hlth 2120 week 5 example" land here.
What a finished HLTH 2120 Week 5 data quality audit looks like
Three to five pages organized around a classification rather than a walkthrough. The opening states the record set, its size and its purpose, all described or supplied by the prompt rather than drawn from a live system. Then the categories: entry error, missing value, inconsistent format, stale value and duplication, each defined so a reader could sort a new case correctly. Findings appear as counts within that set, with two or three instances rendered generically. A chart shows distribution across categories. The analysis paragraph names the entry point behind the largest category and argues why the design invites that particular mistake. Two corrective proposals close it, one aimed at the interface and one at the process. Nothing in it reports a number the prompt did not supply.
How a HLTH 2120 Week 5 example is structured
Classification first, findings second, cause third, fix last. Because the categories govern everything after them, they are defined before a single finding appears, and they are written so that a case falls into exactly one. The findings section runs category by category in a fixed order, most frequent first, each block giving its count, the fields involved and a generic instance showing what the defect looks like on the page. The chart follows the same order so nothing has to be re-read. The causal argument is a section of its own and names one entry point, not four. Corrective proposals come last, split into an interface change and a process change, each saying what it would prevent. A note on the limits of the audit precedes the references.
The record set, described
Size, source and purpose of the set under audit, written as a described or instructor supplied collection. No live extract, no employer file, no real people anywhere in it.
Categories that do not overlap
Five definitions written so a single defect lands in one category only. Overlapping categories are the flaw that makes every count printed afterward meaningless.
Findings in order of frequency
One block per category carrying its count, the fields involved and a generic instance showing what the defect looks like when somebody opens the record.
The chart
A titled figure showing distribution across categories in the same order as the findings, referenced from the text rather than left standing on its own page.
One entry point, argued
The largest category traced back to a specific moment of capture, with the argument saying what about that moment makes the error likely rather than merely possible.
Interface fix, process fix
Two proposals deliberately different in kind, each naming the category it would shrink and what it would cost the people doing the work every day.
Where marks go in HLTH 2120 Week 5
The classification row is where this assignment is really scored. Categories that overlap let one defect be counted twice, and a grader who spots a single instance of that discounts every number after it. Second comes the causal step, and it is what separates an audit from an inventory: naming an entry point and explaining what about it produces the error. Rubrics also look for proportion, so a chart that goes unreferenced in the prose, or a count that disagrees with the chart, costs more than it appears it should. The weakest submissions propose more training as the fix for every category, which reads as no analysis at all. An audit reporting totals without saying which category each defect fell into gives up the credit it was built to earn.
Get a HLTH 2120 Week 5 example written to your instructions
The desk builds this audit from the described or instructor supplied record set your Week 5 prompt provides, with categories defined, counts tabulated, chart titled and the causal argument written out. The opening piece is free, finished within 24-48h. Live extracts from a workplace system are never used, and never reconstructed from memory either.
HLTH 2120 Week 5 questions, answered
What if my prompt supplies the data set?
That is the usual case, and it makes the sample better. Send the file or the description along with the rubric and the audit gets written against those actual records, with categories fitted to what is really in them. Where no set is supplied, the example runs on a described collection built for teaching, which carries the same structure and the same argument.
Are five categories required?
No. Four to six is what the length supports, and some prompts name their own scheme, in which case that scheme governs. What matters is that the definitions are exclusive and that they are written before any counting happens. Categories invented while sorting tend to overlap, and overlapping categories undermine every count that follows them.
Does the audit need a statistical test?
Not at this level. Undergraduate rubrics here ask for accurate counts, a clear proportion across categories and an argument about origin. Adding a test without the design to support it usually costs points rather than earning them. The sample presents distribution plainly and spends its analytical effort on the causal section, which is where the reading actually gets applied.