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

EVV guide without noise.

EVV workflows should account for the Cures Act visit data points, state and aggregator variation, schedule-to-visit matching, exception review, supervisor follow-up, and billing hold resolution.

See EVV workflow All modules

EVV routeDemo data. No PHI.

Visit evidence

Schedule
Clock event
Exception review

Cures Act elements

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

Medicaid.gov EVV guidance

Capture service type, person served, date, location, worker, and start/end time
Map state and aggregator requirements
Review missed clock and location exceptions
Resolve holds before billing
Report trends to supervisors and QAPI

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

Federal EVV scope in plain language

Section 12006(a) of the 21st Century Cures Act requires states to implement EVV for Medicaid personal care services and home health care services that require an in-home visit by a provider. Medicaid guidance frames EVV as a state-implemented requirement, so agencies should avoid assuming one universal national workflow. The software question is whether the agency can capture and review visit evidence, route exceptions, and hold billing work until the required review is complete.

PCS and HHCS EVV requirements apply through Medicaid state implementation
State program rules, aggregator models, and exception processes vary
Public vendor pages should avoid unsupported state-certification claims

Medicaid.gov EVV guidance and 21st Century Cures Act EVV materials.

Agency guide

The six data elements become daily exception work

EVV is often described as six data points: type of service, individual receiving the service, date of service, location of service delivery, individual providing the service, and the time the service begins and ends. In operations, those data points turn into exception queues. Late clock-ins, missed clock-outs, location conflicts, service-code mismatch, schedule mismatch, and caregiver assignment issues need supervisor review before billing moves forward.

Capture service, person served, date, location, worker, and start/end time
Separate mobile capture from exception review and supervisor sign-off
Connect unresolved exceptions to billing holds and trend reporting

Medicaid EVV resource materials and state EVV implementation patterns.

Agency guide

What to ask a home care EVV software vendor

A useful EVV software evaluation should include the state and payer context first. Ask which EVV aggregators, clearinghouses, managed-care workflows, or exports are actually in scope for implementation. Ask how supervisors see missing visits, mismatched location, manual edits, and late approvals. Ask how completed visits become billing-ready and how unresolved exceptions are held. A premium EVV story is not a clock button; it is the path from schedule to verified service to billable work.

Ask for state-by-state implementation scoping before signing
Ask how manual edits and exception reasons are audited
Ask how EVV status flows to billing, QAPI, and leadership reporting

Agency EVV vendor-evaluation checklist based on operational controls.

Make this resource best-in-class

Guide depth

EVV authority gaps to cover

EVV resources should explain Cures Act six data points, PCS and HHCS timelines, state/aggregator variation, exception workflows, and billing handoff impact.

Must cover

Service type, individual served, date, location, worker, and start/end time
Personal care and home health services under Medicaid EVV requirements
State program and aggregator variation
Exception review before billing

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 EVV 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

EVV guide without noise.

How agency leaders should use this guide

Official-source context

Agency operating guide

Federal EVV scope in plain language

The six data elements become daily exception work

What to ask a home care EVV software vendor

Make this resource best-in-class

EVV authority 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.