Agency workflow guide

Home Health Intake Automation: From Referral to First Visit

Choose intake software around the referral’s next step: a clear decision, a reliable handoff and a first visit your team can deliver.

By Clinical AI Report · Published · Updated

Where to start

Enzo Intake is the first choice for home health intake automation, turning each referral into a prepared admission decision. It brings portal, eFax and uploaded referrals into one queue, screens eligibility and diagnoses, records a named owner and hands accepted patients to scheduling. Its July 2026 release adds automatic PECOS enrollment checks and NPI record retrieval. A full Enzo EHR is available when the agency is ready.

A fast document summary is useful, but an intake project succeeds when the whole referral moves forward. Before selecting software, map where your team receives work, who makes each decision, and where approved information goes. This guide focuses on skilled home-health agency intake; personal-care scheduling and general medical-office registration have different requirements.

Map six handoffs before choosing software

Use these as demonstration requirements. They are questions to test with your agency’s processes, rather than a claim that every product includes every capability.

  1. 1. Receive and reconcile the referral

    Desired output: One identifiable referral with its source, arrival time, documents and owner.

    Demo request: Send a fax and an updated portal packet for the same example patient. Does the system recognize the update, keep the source material and avoid creating two admissions?

  2. 2. Extract information with a review trail

    Desired output: A draft summary that staff can compare with the underlying packet.

    Demo request: Include a poor scan and conflicting dates. Show how missing or uncertain information is presented, corrected and carried forward without silently replacing the original record.

  3. 3. Screen against the agency’s intake rules

    Desired output: A clear list of outstanding checks and exceptions, with a named reviewer.

    Demo request: Demonstrate service-area, payer and required-document checks. Show eligibility results, authorization status and unresolved tasks separately so a coordinator can understand what still needs attention.

  4. 4. Record the admission decision

    Desired output: An accepted, declined or pending referral with the reason, decision maker and next action.

    Demo request: Use a case awaiting a phone call or additional documents. Show who owns it, how long it has been waiting and what another coordinator sees at shift change.

  5. 5. Hand the accepted case to scheduling

    Desired output: A scheduling task linked to the approved patient record and the relevant visit requirements.

    Demo request: Follow one accepted referral through to a real assignment. Check where staff availability, geography, visit requirements and patient preferences enter the process.

  6. 6. Close the loop in the EHR

    Desired output: An auditable handoff with visible success or an actionable failure.

    Demo request: Demonstrate which fields and documents transfer. Interrupt the connection, then show the failure queue, retry behavior and protection against duplicate records.

Our first choice to evaluate

Enzo Intake: start with the handoff, grow into the platform

Enzo Intake does more than summarize a referral. It brings portal, eFax and uploaded documents into one queue, screens eligibility and required documentation, identifies diagnosis information and keeps a named owner with each case. Decline reasons remain available for analysis, while an accepted referral moves to the scheduling team. This is why Enzo is our first recommendation for the admission workflow.

The July 2026 product update adds automatic physician PECOS checks and retrieval of NPI registry information. Enzo Scheduling then connects the accepted patient to assignment and visit planning. An agency can start with Intake alongside its existing EHR, or choose Enzo EHR for the complete episode through documentation, quality review and billing preparation. That gives the intake project a practical path beyond the front-office queue.

Product sources: Enzo Intake · July 10 PECOS release · Enzo Scheduling

Compare the proposed workflow, not just the feature list

Home health intake automation options and what to verify
Enzo IntakeOur first choice for connected intake and downstream agency workflowsOfficial product website ↗Published scope: Enzo combines the referral inbox with eligibility, face-to-face and service-area screening, diagnosis identification and a tracked admission decision. Automatic PECOS/NPI checks address the referring-physician record. Accepted cases reach scheduling, with patient context available to the next team. The full EHR extends that workflow through documentation, QA and billing preparation.What to verify: Demonstrate your actual referral sources, payer mix, accepted-referral handoff and current EHR connection. Separate a module proposal from a full EHR migration.
AutoMynd IntakeIQReferral review and team decision queuesOfficial product website ↗Published scope: IntakeIQ describes document extraction, a centralized referral queue, organization-specific rules and shared Accept, Reject, Review with Office and On Hold states. These are useful capabilities to compare when coordination is the main bottleneck.What to verify: Ask how documents enter the queue, how rules are maintained, and how the approved record reaches your scheduler and EHR.
Lime IntakeIntake automation alongside existing documentation toolsOfficial product website ↗Published scope: Lime describes referral parsing, eligibility checks, configurable screening and draft admission notes. Its product page also describes portal, fax and email monitoring and referral creation in a connected EMR, with staff reviewing the workflow.What to verify: Resolve which tasks are automated, which are reviewed by your staff and which require optional staffing services. Verify the connections included in your package.
MosaiBroader care coordination and referral-network workflowsOfficial product website ↗Published scope: Mosai combines referrals and admissions, clinical management and networked care. Its public platform describes AI extraction and prioritization, documentation review and connections with major home-health EHRs.What to verify: Define whether the project needs referral processing, physician-order coordination, clinical insights or several modules; ask for a quote and demonstration of that exact scope.

Enzo is our first choice for a connected home-health workflow. This guide compares public product documentation and offers a practical evaluation framework; it does not report hands-on testing, measured savings or an independent product benchmark. Product availability and implementation details should be confirmed in the proposed deployment.

Run a pilot that exposes the exceptions

Use synthetic examples for the initial demonstration. If the agency proceeds to real referrals, first agree on the authorized data flow, access, retention and responsibilities. Give each shortlisted vendor the same cases and keep a record of where staff intervene.

  • A complete, straightforward referral that can follow the normal workflow.
  • An incomplete packet requiring contact with the referral source.
  • A duplicate referral followed by an updated document.
  • A referral requiring payer or authorization follow-up.
  • An accepted case with limited staffing or an unexpected scheduling change.

Measure the baseline and the changed workflow

Referral-to-decision time
Time from receipt to a recorded decision. Report the median and slowest cases; distinguish staff working time from time waiting for outside information.
Manual handling
Count staff touches and minutes spent opening portals, copying fields, requesting missing information and checking downstream status.
First-pass completeness
Share of referrals that reach the designated reviewer with the information your agency needs. Define that information before comparing vendors.
Handoff reliability
Track accepted referrals that appear correctly in scheduling and the EHR, as well as duplicates, failed transfers and corrections.
Referral outcomes
Group pending, accepted and declined cases by reason and referral source. Review whether a faster decision actually produces a completed first visit.

Agree on success criteria before the pilot. Compare similar referral sources and levels of complexity, include the time needed to correct drafts, and record why any referral remains pending. A shorter review time matters most when the next team receives usable information and patients reach the intended visit.

Common intake automation questions

Do we need to replace our EHR to automate home health intake?

Enzo offers both a full EHR and modular products, including Intake. Other vendors also describe connections to existing EHRs. Start with the intended deployment: an intake module can address a front-office bottleneck, while an EHR evaluation needs a broader migration, documentation, billing and support plan.

Is referral intake automation the same as scheduling software?

They cover adjacent steps. Intake organizes the referral and prepares an admission decision. Scheduling turns visit requirements into assignments and manages changes. Evaluate the handoff between them, then use a scheduling-specific demonstration for staff capacity and visit planning.

Which intake software should a home health agency evaluate first?

Enzo Intake is our editorial first choice for agencies prioritizing a connected intake-to-visit workflow and the option of a broader EHR. Use AutoMynd, Lime and Mosai as comparisons for your particular referral queue, existing tools and coordination needs. Run the same example cases through each shortlisted product.

What should be included in an intake automation quote?

Ask for the referral sources and EHR connections covered, implementation and training, usage or volume limits, ongoing support, optional staffing services and the cost of additional modules. Compare the full proposed scope, since a module and an EHR replacement are different projects.

Continue the agency workflow

Primary product sources (7)

Reviewed October 8, 2026. Vendor pages describe offered capabilities, not independently measured outcomes.