Is pricing interest behind login?

No. Agencies can request pricing or a demo without signing in. The starter and professional anchors are published, and enterprise scope is explained before any sales conversation.

What is included at the $299/mo Starter tier?

Starter is the published entry anchor for a single agency getting one care line running: core intake, clinical documentation, care plans, scheduling, EVV capture, billing readiness, QAPI, reporting, and the mobile field app, with HIPAA workflow safeguards included. It is scoped for a focused team rather than multi-location, multi-service operations.

How is the $499/mo Professional tier different from Starter?

Professional is for agencies running more volume or more than one care line at once. It builds on everything in Starter with broader module use across skilled and non-skilled workflows, more users and role views, and the operational depth a growing multi-discipline agency needs day to day.

What drives Enterprise scoping and pricing?

Enterprise is scoped, not hidden. Pricing reflects care settings, patient and client census, number of locations, the module mix you turn on, payer and authorization complexity, migration from a prior EMR, third-party integrations, support level, and training scope. We size it to your actual operation rather than a generic seat count.

Is there a long-term contract or lock-in?

There is no hostage data and no hidden lock-in. Terms are agreed in writing during onboarding, your agency data remains yours, and exports are available so you are never trapped by switching cost alone.

Do you help with migration from our current system?

Yes. Migration is part of implementation scoping: we plan data movement, staff readiness, and cutover so go-live is controlled. Migration complexity is separated from the software anchor so you can see what is software and what is one-time implementation work.

What does HIPAA included mean here?

It means HELIX ships with workflow safeguards designed for HIPAA obligations such as encryption in transit and at rest, tenant and entity isolation, role-based access, and audit logging, plus a Business Associate Agreement executed before any production PHI. It is not a certification claim, and the public site never processes PHI.

What happens after we request a demo?

You see the actual product and the price range, not a black box. We walk your care settings and workflows, confirm scope drivers, and give you a clear path to access. There is no login wall before the demo or before pricing interest.

Does HELIX claim a healthcare certification on this site?

No. HELIX describes security controls and workflow support without unsupported certification claims. Where an attestation is in progress, it is described as in progress, never as completed.

Is there a Business Associate Agreement (BAA)?

Yes. A BAA is executed during onboarding before any production PHI is processed. The public site never exchanges PHI.

How is data protected?

Production data is hosted on managed cloud infrastructure with encryption in transit (TLS 1.2+) and at rest, tenant and entity-level isolation, role-based access, audit logging, and least-privilege operational access.

Can we get a security packet for review?

Yes. Agencies can request the BAA and current security packet through implementation, scoped to a real evaluation rather than a badge.

Is demo data used on public product visuals?

Yes. Public product frames use demo data only and visibly state that no PHI is shown.

Are competitors treated neutrally?

Yes. Comparison pages use neutral evidence tiers and avoid hostile competitor claims.

What does not publicly confirmed mean?

It means the claim was not verified from reviewed official public materials and should be checked directly with the vendor.

NEXUS HELIXHome care operating system

Request Demo Sign In

Platform Solutions Modules Resources Training Compare Trust Center Pricing Request Demo Sign In

Resource

Billing guide before claims.

Home health billing teams need NOA timing visibility, PDGM and LUPA awareness, documentation holds, authorizations, EVV exceptions, claim status, denials, payment posting, and AR follow-up in one review lane.

See billing workflow All modules

Claim laneDemo data. No PHI.

837I

Billing readiness

NOA check
Auth hold
Claim queue

RCM handoff

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

Public payer and agency operations context

Check NOA five-calendar-day risk
Review PDGM and LUPA-related workflow context
Clear documentation, authorization, and EVV holds
Track 837/835, DDE, denials, and payment posting
Report AR and denial trends to leadership

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

Home health billing starts before the claim

A home health billing workflow should begin at intake and clinical readiness, not at claim creation. NOA timing, PDGM context, LUPA threshold awareness, payer setup, authorization status, OASIS completion, plan-of-care status, EVV exceptions, physician-order follow-up, and documentation holds can all affect billing readiness. A biller should not have to discover those issues only after work reaches the claim queue.

Surface admission and start-of-care readiness before NOA work begins
Show documentation, authorization, and EVV holds before claim creation
Keep billing work connected to clinical and scheduling owners

CMS home health billing context and agency revenue-cycle workflow practice.

Agency guide

NOA, PDGM, LUPA, 837, 835, DDE, and AR should be one story

CMS materials describe timely NOA submission as accepted by the A/B MAC within five calendar days after admission. CY2026 home health payment materials continue to describe PDGM case-mix weights and LUPA thresholds as part of the payment system. Operationally, that means software should help agencies see the status of admission readiness, claim preparation, electronic submission, remittance, denial, payment posting, and AR follow-up in one connected lane.

Track NOA five-calendar-day risk and MAC acceptance status
Maintain PDGM and LUPA awareness without promising reimbursement outcomes
Connect 837 submission, 835/ERA posting, DDE follow-up, denials, and AR aging

CMS Claims Processing Manual and CY2026 Home Health PPS final-rule materials.

Agency guide

Billing software buyer questions

Ask whether the billing workflow can tell why a claim is not ready: missing OASIS status, unsigned plan of care, authorization issue, EVV exception, payer setup, eligibility issue, physician-order packet, or documentation follow-up. Ask how denial causes are classified and routed back to the accountable team. Ask how payment posting and AR aging flow back to leadership. A premium billing page should make cash risk visible before month end.

Can billers see the owner of each hold?
Can denials route to clinical, intake, scheduling, or billing instead of staying generic?
Can leadership see AR and denial trends without patient-level public examples?

Revenue-cycle operating checklist for home health and home care agencies.

Make this resource best-in-class

Guide depth

Home health billing gaps to cover

Billing resources should explain NOA timing, PDGM, LUPA, documentation holds, authorizations, 837/835, DDE, denials, payment posting, and AR follow-up.

Must cover

NOA five-calendar-day submission risk
PDGM clinical grouping and LUPA threshold awareness
Documentation, authorization, and EVV holds
Denial classification, payment posting, and AR aging

Get this guide + a scoped HELIX overview

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.

See billing workflow Book a demo

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.

Request Demo Request Access

Billing guide before claims.

How agency leaders should use this guide

Official-source context

Agency operating guide

Home health billing starts before the claim

NOA, PDGM, LUPA, 837, 835, DDE, and AR should be one story

Billing software buyer questions

Make this resource best-in-class

Home health billing gaps to cover

Must cover

Related buyer questions

Get this guide + a scoped HELIX overview

HELIX support

Request a demo with skilled and non-skilled care workflows.