Built inside live agency operations HIPAA-aware workflows No PHI in public examples
NEXUS HELIXHome care operating system
Menu

Billing and RCM module

From documentation to paid claim.

Coordinate NOA timing, 837I claim batch prep, 835 ERA reconciliation, DDE direct entry, PDGM HIPPS context, LUPA billing adjustment visibility, denial queue by CARC/RARC code, payment posting, and AR work queues — with no clean-claim or reimbursement guarantee.

app.nexushelix.io
Billing and RCMToday · demo · no PHI
Claims ready42
Clean claims97%
Denials open5
  • 837I batch readyBilling & RCMNow
  • 835 ERA to reconcileBilling & RCMToday
  • Denial to reworkBilling & RCM1d

Billing and RCM responsibilities

The page uses safe demo labels and shows the operational states that move work forward.

Workflow responsibilities

  • NOA readiness: TOB 32A submission, 5-calendar-day window from admission date, 1/30-day payment penalty per missed day
  • 837I electronic claim batch prep and 835 ERA reconciliation from clearinghouse or MAC
  • DDE direct data entry and MAC claim status follow-up for Medicare home health episodes
  • PDGM HIPPS code context: 432 clinical grouping combinations, 30-day payment period basis
  • Denial queue by CARC/RARC code with rework routing to documentation, authorization, or clinical team owner
  • LUPA billing adjustment visibility: episodes below visit threshold receive LUPA payment instead of full PDGM rate

Revenue-cycle workflow support only. No clean-claim rate, reimbursement guarantee, or payer outcome is claimed.

Role impact

  • Billers see NOA timing risk, claim status, denial queue by CARC/RARC code, and AR aging
  • Clinical teams see documentation holds that block claim submission and need QA or note completion
  • Owners and RCM leads see AR aging, denial trend, and service-line billing summary

Operational handoffs

Queue status is shown once in the hero product frame, then this page explains what each workflow does and where the work moves next.

Evaluator depth

This module page names the operational details an agency evaluator should expect before a demo.

Evaluator depth

What a premium billing and RCM module must prove

Home health billing buyers expect NOA timing, PDGM, LUPA awareness, DDE/837/835 language, clearinghouse readiness, denial categories, payment posting, and AR follow-up.

Specific workflow evidence

  • NOA five-calendar-day visibility and late-risk review
  • Documentation, authorization, EVV, and claim-readiness holds
  • 837/835, DDE, clearinghouse, ERA, denial, and AR workflow language
  • Private-pay invoice and Medicaid/managed-care handoffs for non-skilled work

Next-module handoff

Outputs become payment posting, denial follow-up, AR aging, QAPI billing trends, and leadership reporting.

Care-setting applicability

Skilled

Workflow coverage shown with demo-only public data and agency role context.

Non-skilled

Workflow coverage shown with demo-only public data and agency role context.

Private duty

Workflow coverage shown with demo-only public data and agency role context.

Multi-service

Workflow coverage shown with demo-only public data and agency role context.

Related modules

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.