Abstracting from the Inpatient Record
Key Takeaways
- Inpatient abstraction requires review of the full record, not one note in isolation.
- Provider documentation supports reportable diagnoses, while ancillary data can support timing, treatment, and procedure details.
- Conflicts between discharge summary, progress notes, operative reports, and results require reconciliation or query.
- Abstraction captures data elements that affect coding, quality reporting, grouping, and record integrity.
What to Abstract
Inpatient records are longitudinal. Review the history and physical, ED record, admission orders, progress notes, consults, operative reports, anesthesia records, procedure notes, pathology, radiology, lab trends, medication administration, nursing notes, respiratory therapy notes, discharge summary, and discharge disposition.
Provider documentation is required to establish most reportable diagnoses. Ancillary documentation can support facts such as a lab value, imaging result, medication given, ventilator use, timing of a condition, or whether a service occurred. Do not turn an abnormal result into a diagnosis unless the provider documents its clinical significance or clarification supports it.
Abstract the data elements that affect coding: admission reason, final diagnoses, secondary conditions meeting UHDDS criteria, procedures and dates, approach, devices, discharge disposition, POA status, complications, comorbidities, newborn or obstetric details, payer-required fields, and attending or operating provider.
Discharge summaries are important, but they are not the only source. An operative report may provide the only reliable approach and body part. A medication record may show treatment that helps determine whether a documented condition affected care. A nursing note may support increased monitoring, but it usually does not establish a provider diagnosis.
When sources conflict, stop and reconcile. If progress notes call a condition acute but the discharge summary omits it, determine whether it resolved, was ruled out, or was accidentally left off. A compliant query is appropriate when the answer affects code assignment and is clinically supported.
Good abstraction protects data quality. It prevents coding from a problem list alone, catches procedures missing from the discharge summary, supports POA decisions, and creates a defensible trail for DRG validation, audit review, and quality reporting.
A sodium level is abnormal throughout the stay, but no provider documents hyponatremia or clinical significance. What is the best coding action?
Which source is usually the best place to confirm the PCS approach, body part, device, and procedure objective for a surgery?
A discharge summary lists status post knee replacement from five years ago. The condition did not affect treatment, monitoring, length of stay, or current care. How should it generally be handled?