| Course | HIM 452 Quality Management in Health Care |
|---|---|
| Topic | Topic 2 |
| Paper type | Abstraction judgment log |
| Length | About 980 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 452 Topic 2
Six Contestable Charts, Six Decisions: An Abstraction Judgment Log for Ironwood's NTSV Cesarean Measure
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-452: Quality Management in Health Care
Topic 2 Assignment
[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.
Six Contestable Charts, Six Decisions: An Abstraction Judgment Log for Ironwood's NTSV Cesarean Measure
Why Keep a Judgment Log
Ironwood Community Hospital's two perinatal abstractors review every birth that might belong in the NTSV cesarean measure. Most charts are straightforward. A few are not, and on those the abstractors have sometimes made different choices, each defensible from part of the record. A narrative account of abstraction practice would say that abstractors follow the specification carefully, which is true and useless. This log instead records the contestable decisions themselves: the data element, the chart evidence that made it contestable, the choice each abstractor made and the text or definition that should have settled it. The six rows below come from one quarter's review, in which the two abstractors worked 40 of the same charts independently and disagreed on six.
The Log
Table 1
Contestable Decisions From One Quarter's Review
| Element | Chart evidence | Abstractor A | Abstractor B | What should settle it | Decision |
|---|---|---|---|---|---|
| Number of previous live births | Prenatal history: one prior pregnancy ending in stillbirth at 30 weeks | 1 | 0 | A stillbirth is not a live birth | 0; the birth belongs in the NTSV population |
| Number of previous live births | Prior delivery at 22 weeks; infant lived four hours | 0 | 1 | Any birth showing signs of life is a live birth, regardless of gestational age | 1; the birth is excluded |
| Gestational age | Delivery note: 37 weeks 0 days; nursing admission note: 36 weeks 6 days, recorded the evening before | 37 | 36 | The specification's source priority for gestational age at delivery | 37; term, included |
| Gestational age | Two dating ultrasounds in the prenatal record give different due dates; delivery note uses the later one | 38 | 39 | The delivery record's value, not the abstractor's recalculation | 38, as documented at delivery |
| Presentation | Admission note: vertex; operative note: frank breech found at cesarean | Vertex | Breech | Presentation as documented at delivery, reflected in the assigned codes | Breech; excluded if the abnormal presentation code is assigned |
| Method of delivery | Delivery note: vacuum attempted, then cesarean | Vaginal | Cesarean | The method by which the baby was born | Cesarean |
What the Rows Teach
The two parity rows are the most instructive, because they turn on a definition, not a reading of the chart. The measure counts previous live births, and the definition of a live birth used in vital statistics is a birth showing any evidence of life, such as breathing or a heartbeat, regardless of the length of the pregnancy (World Health Organization, 2016). A stillbirth at 30 weeks is therefore not a live birth, and the woman remains nulliparous for the measure; an infant born at 22 weeks who lived for four hours is a live birth, and the woman is not. Abstractor A counted the stillbirth as a previous birth, a natural reading of obstetric shorthand, and Abstractor B counted the 22-week infant as not viable, a natural clinical reading. Both natural readings were wrong for the measure.
The gestational age rows show a different lesson: when the record contains two values, the abstractor does not choose the one that seems more accurate, but the one the specification's rules for abstraction designate (The Joint Commission, 2024). Recalculating gestational age from ultrasound dates is clinical judgment, which abstraction does not permit. The presentation row shows how the measure's code-based exclusions depend on what the clinician documented at delivery, and the method row shows that a failed attempt at vaginal delivery does not change how the baby was born.
Agreement Before and After
Across the 40 shared charts, the abstractors agreed on inclusion in the NTSV population in 34, or 85%, and on the final measure outcome, cesarean or not within the population, in 36, or 90%. McHugh (2012) cautions that percentage agreement overstates reliability when chance agreement is high and that kappa should accompany it for categorical judgments; for the inclusion decision, where about two-thirds of charts were included, kappa was 0.66, moderate agreement. After the two abstractors reviewed this log together and added its six rules to their abstraction guide, a second sample of 40 charts produced agreement on inclusion in 38, or 95%, with kappa of 0.89.
What the Log Cannot Settle
Some contestable charts cannot be settled by any rule, because the record lacks the fact the rule needs. In the quarter reviewed, one delivery record gave no gestational age at all, and the prenatal record ended six weeks before delivery. The abstractors cannot calculate gestational age themselves, and the specification allows a value of unable to determine, which removes the birth from the population. Using it here would have been correct and would also have removed a first-time mother's cesarean from the measure for a documentation reason. The better response was a request to the delivering physician to complete the delivery record, which the quality team made before the abstraction deadline, and which the physician answered within a day.
The log records such cases separately, as documentation gaps rather than abstraction decisions, and they are reported monthly to the obstetric department. Over time they show where the delivery record template needs a required field, which is more useful than any number of abstraction rules, because it fixes the source rather than the reading of it.
How the Log Is Used
The log is now a standing document. Each disagreement found in the quarterly double review is added as a row, with the settling rule, and the abstraction guide is updated from it. When a row cannot be settled from the specification, the question goes to the measure steward's question-and-answer service, and the answer is recorded with its date. New abstractors read the log before they begin, because it teaches the contestable cases faster than the specification manual does. And the log feeds back to documentation: two of the six rows arose because the labor admission history did not distinguish previous live births from previous pregnancies, and the obstetric nursing template now asks for each separately.
References
McHugh, M. L. (2012). Interrater reliability: The kappa statistic. Biochemia Medica, 22(3), 276-282. https://doi.org/10.11613/BM.2012.031
The Joint Commission. (2024). Specifications manual for Joint Commission national quality measures. The Joint Commission.
World Health Organization. (2016). International statistical classification of diseases and related health problems (10th rev., 5th ed.). World Health Organization.
What the HIM 452 Topic 2 instructions ask for
The Topic 2 instructions in HIM-452 ask students to examine judgment in quality measure abstraction. Weak submissions describe abstraction as following the specification. The assignment rewards logs that record specific contestable decisions: the data element, the chart evidence that made it contestable, the choices different abstractors made and the definition or rule that should have settled it. Students should explain what the rows teach, measure agreement before and after the log is used, distinguish decisions from documentation gaps that require a clinician's input and describe how the log becomes part of training and documentation improvement.
Inside the HIM 452 Topic 2 example
The finished log is a table of decisions rather than a narrative about abstraction. Each row names the data element, the chart evidence that made it contestable, the choice each abstractor made and the specification text that should have settled it. Typical rows include two different arrival times in the emergency record, a documented reason for withholding a medication written only in a nursing note, and a condition charted as possible on one day and ruled out on the next. Where the abstraction notes settle the question, the log quotes the rule and marks the abstractor who departed from it. Where the notes are silent, the log says so and records the local convention adopted in their place, with the date it was agreed. Rows are counted by element at the end.
Reading the HIM 452 Topic 2 rubric
Faculty grading the judgment log reward decisions tied to their settling rule. Excellent logs show real ambiguity in the record and name the definition that resolves it, such as the vital statistics definition of a live birth. Credit goes to recognizing that abstractors may not recalculate clinical values and must use the designated source. The rubric values measured improvement in agreement with appropriate statistics and a clear separation of abstraction decisions from missing documentation. The highest level feeds the log back into templates, so the source improves rather than only the reading of it.
Common HIM 452 Topic 2 mistakes, and how to avoid them
Treating abstraction as copying is the error behind most lost marks on this log. A paper reporting only the final values each abstractor entered shows agreement or its absence without showing why, and the why is the entire exercise. Rows missing the chart evidence ask a reader to trust a summary of a conflict nobody can see. Drafts that settle every disagreement by preference, without quoting the abstraction notes, turn a specification question into an opinion. Many versions never separate judgment from missing documents, so a misfiled consent form gets logged as abstractor error and the retraining that follows fixes nothing. A log with no count by element cannot say where the next improvement effort belongs, which leaves the department retraining everyone equally and learning little from it.
Get an HIM-452 Topic 2 example written to your instructions
Send the HIM-452 Topic 2 instructions, your classroom rubric and the measure or chart scenario the assignment supplies. We write a custom example to those criteria, with contested decisions logged row by row, chart evidence reproduced, the governing abstraction note beside each and disagreements counted by element, in 24 to 48 hours. The first one costs nothing.
More HIM 452 papers and BS in Health Information Management samples
- HIM 452 Topic 1: Measure Provenance Map
- HIM 452 Topic 3: Denominator Code List Review
- HIM 452 Topic 4: Comorbidity Capture Review
- HIM 452 Topic 5: Pdsa Result Dq Post
- HIM 452 Topic 6: Submission Obligations Calendar
- HIM 452 Topic 7: Re-abstraction Validation Report
- HIM 452 Topic 8: Clinician Score Briefing
- HIM 430 Topic 2: Stewardship Role Charter
- HIM 200 Topic 2: Legal Record Boundary Memo
- HIM 425 Topic 2: Workload Staffing Model
- HIM 310 Topic 2: Diagnosis Hierarchy Analysis
HIM 452 Topic 2 questions, answered
Is abstraction really a matter of judgment?
More than most people expect. Specifications define each data element carefully, yet charts contain conflicting times, hedged diagnoses and information recorded in unexpected places. Abstractors must decide which entry governs, and two trained people can reasonably choose differently. The published abstraction notes resolve many of those questions, which is why the log quotes them, but some remain open and a department has to settle them locally.
Should the log use real charts?
No. The example uses composite, de-identified charts built to show typical conflicts, and it states that on its first page. If your assignment asks you to work from records at a site, follow the privacy rules your instructions and the site set, and remove anything that could identify a patient, a clinician or the facility before it appears in a paper.
Does the log replace an agreement rate?
An agreement rate says how often two abstractors matched; the log says where and why they did not. The rate is a single figure, useful for tracking over time, while the log is diagnostic. Where a classroom wants the two together, the log usually comes first, because a rate without the decisions behind it cannot tell a supervisor what to change.
Where can I find a free HIM 452 Topic 2 sample paper?
The complete log is on this page, with why keep a log, six decisions in a table, what the rows teach, agreement before and after, what the log cannot settle and how it is used. Send your measure for a free worked log.
Is a woman with a prior stillbirth nulliparous in HIM 452 Topic 2?
Yes for this measure. It counts previous live births, and a stillbirth is not a live birth, so she has none and her birth belongs in the NTSV population.