Maternal conditions appear on the newborn’s problem list after copy-forward from the obstetric record, with no infant clinical support. What should the facility coder do?
Select an answer to reveal the explanation.
Short Explanation
Mom’s problems do not automatically become the baby’s problems just because someone copy-pasted the chart. Spot the copy-forward clutter, clear what the newborn never had, and code only real infant conditions.
Full Explanation
When maternal conditions appear on the newborn’s problem list after copy-forward from the obstetric record with no infant clinical support, the facility coder should treat the copied maternal conditions as a documentation conflict and clear unsupported infant diagnoses before coding. Newborn abstracts at public hospitals must not inherit the mother’s diseases through EHR copy-forward. Coding maternal conditions on the newborn claim because they appear on the problem list fails without infant clinical support. Transferring maternal codes to the mother’s claim while leaving them on the newborn abstract as history still leaves false infant diagnoses if they remain coded. Reporting maternal conditions as hospital-acquired conditions on the newborn encounter misuses HAC concepts and invents infant hospital-acquired disease. Exam caveat: copy-forward maternal problems onto newborn records are documentation conflicts, not automatic newborn codes. Operational check: scrub newborn problem lists for maternal-only entries at the civic perinatal service, remove unsupported diagnoses from the infant abstract, and code only infant conditions. Work with IT/CDI to reduce obstetric-to-newborn copy-forward pollution in the EHR.