PDGM, NOA, and LUPA workflow guide for home health agencies
Home health billing readiness depends on operational visibility into PDGM grouping context, 30-day payment periods, NOA timing, LUPA threshold awareness, documentation holds, claim status, denial follow-up, and AR work queues.
Skilled home healthPersonal carePrivate dutyEVV + schedulingBilling + agency operations
CMS home health prospective payment, PDGM, NOA, and LUPA public guidance
Confirm admission and start-of-care readiness before NOA work begins
Track NOA five-calendar-day risk and MAC acceptance status
Review PDGM grouping context and LUPA threshold awareness
Clear OASIS, plan-of-care, authorization, and documentation holds
Connect denial categories, payment posting, and AR follow-up
Make this resource best-in-class
Best-resource upgrade
PDGM, NOA, and LUPA detail agencies search for
This guide gives billing leaders a practical map of how PDGM grouping context, NOA timeliness, LUPA threshold awareness, documentation holds, and claim follow-up should move through software work queues.
Must cover
NOA five-calendar-day risk and acceptance status
PDGM 30-day period workflow context
LUPA threshold awareness before claim readiness
OASIS, plan-of-care, authorization, and documentation holds
Denial and AR follow-up ownership
Search intent
PDGM home health softwareNOA home health five day ruleLUPA home health billing
HELIX support
HELIX supports operational visibility and workflow management. It does not provide legal, payer, clinical, or compliance advice.
Does HELIX provide legal, payer, clinical, or compliance advice?
No. HELIX provides workflow software and operational tooling. Agencies remain responsible for regulatory and payer obligations.
Are resource pages certification claims?
No. Resource pages explain operational workflow context and avoid unsupported certification or outcome claims.
See HELIX in action
Request a demo with skilled and non-skilled EMR workflows.
Walk through intake, documentation, care plans, scheduling, EVV, authorizations, billing, QAPI, reporting, and mobile workflows without routing through a login wall.