A newborn chart at a health-system nursery contains a maternal complication diagnosis clearly belonging to the mother's record. What should the coder do?
Select an answer to reveal the explanation.
Short Explanation
Wrong-chart documentation is a filing error, not a coding opportunity. If mom's complication landed on the baby's chart, you stop and route a correction — you do not code maternal disease as a newborn diagnosis. Integrity first, then coding.
Full Explanation
A newborn chart at a health-system nursery that contains a maternal complication diagnosis clearly belonging to the mother's record is wrong-chart documentation. The coder should flag it for correction through the proper amendment workflow rather than coding the maternal condition on the newborn. Maternal conditions are not reported as newborn diagnoses merely because an EHR cross-contamination placed them on the infant's chart. Transferring the newborn codes onto the mother's account to keep charts synchronized mixes two patients' abstracts. Deleting the newborn encounter until all maternal diagnoses are copied over destroys a legitimate newborn record. Exam caveat: perinatal coding distinguishes maternal and newborn code sets; identity and chart integrity errors must be fixed before coding either account. Operational check for civic nurseries: verify each diagnosis belongs to the newborn, escalate maternal bleed-through via HIM amendment processes, and code only newborn-appropriate conditions after correction. This discipline protects patients, supports accurate public reporting for municipal hospitals, and keeps the coded abstract defensible when auditors compare codes to the authenticated record.