NEXUS HELIX platform
HELIX connects intake, documentation, care plans, scheduling, EVV, authorizations, billing, QAPI, reporting, and mobile field workflows in one workspace — so skilled and non-skilled care run on a single clinical documentation and workflow platform instead of two disconnected systems. See the product and the price before you talk to anyone.
Each handoff is visible before it becomes a staffing, documentation, billing, or quality problem.
One connected flow from the first referral to a clean claim and a quality review — no rekeying between disconnected tools.
A referral lands in intake and becomes a patient or client record. Skilled visits drive OASIS-E2 and clinical documentation; non-skilled visits drive personal care and private-duty plans. Care plans set the orders, scheduling fills the calendar against availability and coverage, and EVV captures each visit. Authorizations are tracked against units, billing and revenue cycle turn completed work into clean claims, QAPI watches quality signals, reporting rolls it up for leadership, and the mobile app keeps field staff in sync the whole way.
Most agencies are forced to run a clinical EMR and a separate home-care system. HELIX is built so both live in the same workspace with shared records, scoped queues, and one source of truth.
Skilled home health, personal care, private duty, and multi-service agencies share intake, scheduling, EVV, billing, and reporting — while each care setting still gets workflows, role views, and queues scoped to how that team actually works. Leadership sees the whole agency without stitching exports together.
HELIX is the care-at-home clinical documentation and workflow layer of a broader operating system: product proof, permissions, workflow queues, and reporting are designed as connected operating views.
Runs on NEXUS OS
Click any module to move real work - intake, scheduling, EVV, clinical, and revenue - inside one tenant-isolated record. Demo data only - no patient, payer, claim, or staff identifiers.
Public product frames use demo data only and visibly state that no PHI is shown — you can see how the workspace behaves before any sales call.
Census, revenue holds, location rollups, QAPI follow-up
Priorities, staffing pressure, billing risk
AdministratorOperational queues, permissions, reports, implementation tasks
Team ownership, review cadence, agency controls
DON / Clinical ManagerOASIS-E2 work, skilled notes, care plans, QAPI trends
Clinical review, follow-up, documentation quality
SchedulerVisits, shifts, availability, missed visits, authorization limits
Coverage gaps and schedule changes
Biller / RCM LeadAuthorization holds, EVV exceptions, NOA timing, claim readiness, AR queues
Billing handoffs and follow-up work
Field Clinician / CaregiverDaily worklist, OASIS timepoint assignments, EVV tasks, care-plan instructions
Field documentation and task completion
NEXUS HELIX coordinates referral intake, OASIS-E2 documentation across all seven timepoints (SOC, ROC, recertification, transfer, SCIC, resumption, discharge), 485 plan-of-care and physician order tracking, skilled visit notes by discipline, authorizations, NOA and claim readiness, PDGM episode visibility, LUPA awareness, QAPI follow-up, and discharge planning in one agency workflow layer.
Coordinate client intake, task-based care plans, caregiver schedules, 21st Century Cures Act EVV exception review, supervisor follow-up, missed-visit tracking, Medicaid waiver and managed-care billing handoffs, and private-pay workflows — without forcing non-skilled operations into a skilled-only EMR model.
Coordinate recurring shift templates, caregiver availability and coverage-gap recovery, private-pay service plans and invoice review, missed-visit follow-up, supervisor notes, client communication posture, and billing handoffs from a single operational view — without blending private-duty with skilled or Medicaid-funded workflows.
Coordinated agency workflows for skilled home health, personal care, private duty, and location-level visibility — without three separate systems. Keep census segmented by care setting, service-line reporting separated by payer and program, role-based permissions aligned across clinical and billing teams, and shared QAPI and reporting visible to owners and administrators.
Straight answers to what buyers ask before shortlisting an EMR.
Yes. HELIX runs skilled home health and non-skilled home care — personal care, private duty, and multi-service agencies — in the same workspace, so you do not run two disconnected systems. Each care setting gets scoped queues, role views, and workflows using demo-only examples.
HELIX follows the care lifecycle as one connected flow: intake and referral, OASIS and clinical documentation, care plans, scheduling, EVV capture, authorizations, billing and revenue cycle, QAPI, reporting, and the mobile field app. Each handoff is visible before it becomes a staffing, documentation, billing, or quality problem.
HELIX is the care-at-home clinical documentation and workflow layer of a broader operating system. Product proof, permissions, workflow queues, and reporting are designed as connected operating views rather than bolt-on modules, so leadership sees one source of truth across the agency.
HELIX captures the six 21st Century Cures Act EVV data elements and routes exceptions to supervisor review before billing. Specific state EVV aggregator connections and any third-party integrations are confirmed during implementation scoping rather than claimed generically on this page.
Implementation is scoped around agency readiness, care settings, module mix, payer workflows, migration needs, training owners, and stabilization. Those factors set the timeline, and we plan a controlled go-live rather than a fixed one-size date.
Production data is hosted on managed cloud infrastructure with encryption in transit and at rest, tenant and entity-level isolation, role-based access, and audit logging. A Business Associate Agreement is executed before any production PHI. This describes workflow safeguards, not a certification claim, and the public site never processes PHI.
Yes. You can see the product and the price range before talking to anyone. Public product frames use demo data only and visibly state that no PHI is shown, and there is no login wall before a demo or pricing interest.
See HELIX in action
Walk through intake, documentation, care plans, scheduling, EVV, authorizations, billing, QAPI, reporting, and mobile workflows without routing through a login wall.