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.
Last reviewed June 15, 2026. Operational workflow context only — not legal, clinical, billing, or compliance advice.
How agency leaders should use this guide
Treat this page as an operating-readiness worksheet, not legal, clinical, billing, payer, or compliance advice.
Use the guide to name the workflow owner, the upstream inputs, the downstream handoffs, and the software proof you need to see before changing systems. For each topic, ask which department owns the work today, where handoffs break, what evidence is needed before billing or leadership review, and what the agency needs visible without exposing PHI.
HELIX public examples stay demo-safe. The goal is to help owners, administrators, clinical leaders, schedulers, billers, and QAPI teams evaluate whether an EMR can organize the work, surface blockers, and route follow-up. Final regulatory, payer, clinical, coding, billing, and compliance decisions remain with the agency and its qualified advisors.
Name the accountable department and owner
Identify the work queue, evidence, deadline, and handoff
Ask for no-PHI product proof before implementation scope is accepted
Official-source context
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
Agency operating guide
Use this section to turn the topic into practical evaluation criteria, workflow ownership, and implementation questions for a home health or home care agency.
Agency guide
PDGM, NOA, and LUPA are operating signals
PDGM groups care into 30-day payment-period context, while LUPA thresholds and NOA timeliness create operational watch points for billing teams. CMS CY2026 materials describe PDGM case-mix weights and LUPA thresholds as part of the home health payment system. For agencies, the practical need is visibility: who owns the intake, OASIS, authorization, scheduling, documentation, and claim steps that determine whether billing can move forward cleanly.
Use PDGM and LUPA as workflow awareness, not public reimbursement promises
Make the NOA owner and acceptance status visible
Keep clinical, scheduling, and billing blockers in the same review lane
CMS CY2026 Home Health PPS and home health billing materials.
Agency guide
NOA timeliness needs a real queue
CMS claim-processing guidance states that a timely-filed NOA is submitted to and accepted by the A/B MAC within five calendar days after admission. That makes the operational queue important: admission date, start-of-care readiness, payer/MAC context, acceptance status, late-risk flag, and follow-up ownership all need to be visible. A checklist hidden in a binder does not protect the agency when the responsible team cannot see what is due.
Count five calendar days from the admission/start-of-care timing context
Track submitted, accepted, returned, corrected, and late-risk states
Route missing prerequisites before the deadline becomes a payment problem
CMS Medicare Claims Processing Manual, Chapter 10, home health NOA guidance.
Agency guide
How software should support billing readiness
A PDGM/NOA/LUPA software guide should show how the billing team gets readiness from upstream work: OASIS status, plan-of-care progress, physician-order packet, authorization status, EVV exceptions, documentation completion, and claim submission response. Denials and AR follow-up should feed the same loop so repeated causes become training or QAPI topics. The goal is operational visibility; the agency remains responsible for payer submissions and regulatory decisions.
Show readiness blockers by owner and due date
Connect claim status and ERA/835 response to denial and payment-posting follow-up
Report repeated issues to QAPI or training without exposing PHI
Agency billing workflow model anchored to CMS public payment and claims context.
Make this resource best-in-class
Guide depth
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
Related buyer questions
PDGM home health softwareNOA home health five day ruleLUPA home health billing
Official sources
Verify the regulatory specifics directly at the official source. This page is operating-readiness context, not advice.
Want this guide and the relevant HELIX workflow walkthrough by email? Leave a work email — no sales call required, and you can see the product and the $299/mo starting price without a login wall.
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 care workflows.
Walk through intake, documentation, care plans, scheduling, EVV, authorizations, billing, QAPI, reporting, and mobile workflows without routing through a login wall.