Healthcare · Moraph software

Home Health Logistics Planner

Plan visiting clinicians' routes and verify every home visit for EVV

Overview

What you are buying

Home Health Logistics Planner builds daily visit schedules and routes for visiting nurses, therapists and aides from the visits your plans of care require, the clinicians available and the travel between homes. At the visit, it captures the electronic visit verification data your state requires and sends it to the state's EVV aggregator where your state accepts alternate systems. Schedulers see missed and late visits as they happen, and every exception and correction keeps its reason for billing and audit.

The problem it solves

Most home health and personal care agencies plan visits on a whiteboard or in the scheduling module of their agency system, with routes worked out by each clinician. Travel time is guessed, last-minute changes are handled by phone, and nobody sees a missed visit until the end of the day. EVV adds a separate app and a stream of exceptions to correct before claims can go out, and the reasons behind each correction are hard to find when a state or payer asks.

  • Routes are planned by hand, so travel time and mileage vary widely
  • Late and missed visits are discovered after the patient has called
  • EVV exceptions pile up and hold up Medicaid claims
  • Corrections to visit records lack a clear reason and approver

Who uses it

  • Medicare-certified home health agencies
  • Personal care and home and community-based services agencies billing Medicaid
  • Schedulers and branch managers who plan the day's visits
  • Visiting nurses, therapists and home health aides
  • Billing and compliance staff who resolve EVV exceptions

Requirements it supports

21st Century Cures Act, Section 12006 electronic visit verification (42 U.S.C. 1396b(l))State Medicaid EVV requirements and aggregator specificationsMedicare Home Health Agency Conditions of Participation (42 CFR Part 484)HIPAA Privacy and Security Rules (45 CFR Parts 160 and 164)Fair Labor Standards Act rules for domestic service employment (29 CFR Part 552)

The product supports these requirements; meeting them remains your organization’s responsibility.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    The day's visit board

    Schedulers start from a live view of every visit in the branch, with late and missed visits flagged as they happen.

    VisitPatientClinicianWindowStatusEVV
    V-88213Patient 30417 (fictional)RN 0142 (fictional)08:00 to 10:00CompleteVerified
    V-88219Patient 51208 (fictional)PT 0067 (fictional)09:00 to 11:00In progressChecked in
    V-88224Patient 22975 (fictional)Aide 0310 (fictional)09:30 to 10:30LateNot checked in
    V-88230Patient 47731 (fictional)RN 0142 (fictional)11:00 to 13:00Scheduled
    V-88236Patient 60884 (fictional)OT 0029 (fictional)13:00 to 15:00Scheduled
    Schedulers start from a live view of every visit in the branch, with late and missed visits flagged as they happen.
  2. Step 2

    A clinician's route

    Each clinician's day is ordered to reduce travel between homes while keeping each patient's visit window.

    RN 0142 (fictional) · Example County branch

    Visits today
    5
    Planned drive time
    1 hour 40 minutes
    Planned miles
    46
    First visit
    08:00, Patient 30417 (fictional)
    Last visit ends
    16:15

    Visit order

    • Patient 30417 (fictional) · Skilled nursing · 08:00
    • Patient 47731 (fictional) · Wound care · 11:00
    • Patient 18820 (fictional) · Medication teaching · 12:45
    • Patient 39561 (fictional) · Start of care · 13:45
    • Patient 72290 (fictional) · Recertification · 15:30
    Each clinician's day is ordered to reduce travel between homes while keeping each patient's visit window.
  3. Step 3

    Re-planning after a cancellation

    When a visit is cancelled or added, the planner proposes changes, and the scheduler decides.

    ChangeClinicianPatientNew timeDrive time change
    Cancelled by patientPT 0067 (fictional)Patient 51990 (fictional)-25 min
    Urgent visit addedPT 0067 (fictional)Patient 64412 (fictional)14:00+15 min
    Moved laterPT 0067 (fictional)Patient 28035 (fictional)15:15+5 min
    Outside preferred windowPT 0067 (fictional)Patient 28035 (fictional)15:15Call patient to confirm
    When a visit is cancelled or added, the planner proposes changes, and the scheduler decides.
  4. Step 4

    An EVV visit record

    The six EVV data elements are captured at the visit, and anything outside expected bounds is flagged for review.

    Visit V-88224 · Patient 22975 (fictional)

    Service
    Personal care
    Provider
    Aide 0310 (fictional)
    Date
    Fictional sample date
    Check-in
    10:12
    Check-out
    11:05
    Location at check-in
    Outside expected distance from home address

    Exceptions

    • Check-in after the visit window
    • Location outside expected distance
    The six EVV data elements are captured at the visit, and anything outside expected bounds is flagged for review.
  5. Step 5

    Resolving an exception

    Each correction keeps the state's reason code, the note and the approver, before the visit is released for billing.

    Visit V-88224 · EVV exception

    1. Late check-in and location exceptions raisedMobile app
    2. Clinician note: patient was at a neighbor's home next doorAide 0310 (fictional)
    3. Correction entered with state reason code and noteEVV coordinator
    4. Correction approvedClinical manager
    5. Visit sent to state aggregator and acceptedSystem
    6. Marked ready for billingEVV coordinator
    Each correction keeps the state's reason code, the note and the approver, before the visit is released for billing.
  6. Step 6

    EVV status by payer

    Billing staff see which visits are verified, waiting for correction or rejected by the aggregator, by payer.

    PayerVisits this weekVerifiedOpen exceptionsAggregator rejections
    Example State Medicaid (fictional)412389194
    Example Health Plan (fictional)13813440
    Medicare home health2962960Not applicable
    Billing staff see which visits are verified, waiting for correction or rejected by the aggregator, by payer.

Workflows

The principal workflows

  1. Plan

    Visits required by each patient's plan of care or service plan are turned into a schedule, matched to clinicians with the right discipline, skills, availability and patient preferences.

    • Ordered visits and frequencies arrive from your agency system
    • Clinicians' availability, discipline, skills and home base are kept up to date
    • Patient visit windows, language and continuity preferences are applied
    • The planner proposes assignments and the order of visits for each clinician
    • A scheduler reviews, adjusts and publishes the schedule
  2. Route

    Each clinician's day is ordered to reduce travel between homes while keeping time windows, and recalculated when visits are added, cancelled or run long.

    • Routes are built from patient addresses and estimated travel times
    • Time windows and visit lengths by visit type are respected
    • Clinicians see their day and directions on their phone
    • Cancellations and urgent visits trigger a proposed re-plan for the scheduler
    • Planned and actual mileage are recorded for reimbursement
  3. Verify

    At each visit the clinician's app captures the six data elements EVV requires: the type of service, the individual receiving it, the date, the location, the person providing it, and the start and end times.

    • Clinician checks in on arrival and the location is recorded
    • Services performed are recorded against the visit
    • Clinician checks out and the visit times are recorded
    • Visits outside expected location or times are flagged as exceptions
    • Verified visits are sent to the state aggregator in the required format
  4. Resolve

    Late, missed and unverified visits appear to schedulers as they happen, and EVV exceptions are corrected with a reason code and approval before claims are released.

    • Late check-ins and missed visits alert the scheduler during the day
    • Exceptions are listed by type, clinician and payer
    • Corrections are entered with the state's reason code and a note
    • A supervisor approves corrections where your policy requires it
    • Visits are marked ready for billing once verification is complete

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Visiting clinician

Registered nurse, licensed practical nurse, physical, occupational or speech therapist, home health aide, personal care aide

Carries out the day's visits and records the information EVV requires at each one.

Sees

  • Their own schedule and route for the day and coming days
  • Visit details and directions for patients assigned to them
  • Their own EVV exceptions waiting for a note

Does

  • Checks in on arrival and out on leaving each visit
  • Records services performed
  • Adds a note explaining a late, short or relocated visit
  • Reports a cancellation or problem reaching a patient
  • Records mileage where your agency requires it

Cannot

  • See patients not assigned to them
  • Change their own schedule or visit times after check-out
  • Correct or approve EVV exceptions
Approvals
Nothing they record needs their own approval; corrections to their visits are entered by office staff and approved by a manager.
Notified about
Schedule changes, newly assigned visits, and requests for a note on an exception.

Scheduler

Scheduler, scheduling coordinator, staffing coordinator

Turns ordered visits into a workable schedule and keeps the day running as things change.

Sees

  • Ordered visits, clinicians' availability and qualifications for their branch
  • Proposed schedules and routes
  • The live visit board with late and missed visits

Does

  • Reviews, adjusts and publishes schedules and routes
  • Accepts or changes proposed re-plans after cancellations
  • Reassigns visits when a clinician is unavailable
  • Contacts patients and clinicians about late or missed visits
  • Records the reason a visit was missed

Cannot

  • Assign a visit to a clinician without the required discipline or a current license
  • Correct EVV data or release visits for billing
  • Change scheduling rules
Approvals
Overrides of scheduling rules, such as exceeding overtime limits, need clinical manager approval where you configure it.
Notified about
Late check-ins, missed visits, cancellations and visits not yet assigned.

Clinical manager

Clinical manager, director of nursing, rehabilitation manager

Makes sure ordered visits happen and approves changes to visit records.

Sees

  • Visit coverage against ordered frequencies for their patients
  • Missed visits and the reasons recorded
  • EVV corrections waiting for approval

Does

  • Approves or returns EVV corrections
  • Reviews missed visits and decides on follow-up
  • Approves scheduling rule overrides
  • Reviews continuity of care for patients with many clinicians

Cannot

  • Approve a correction they entered themselves
  • Change state reason codes or aggregator settings
  • Edit or delete entries in the audit trail
Approvals
Approves EVV corrections and scheduling overrides for their branch.
Notified about
Corrections waiting for approval, missed visits, and patients below their ordered visit frequency.

EVV and billing coordinator

EVV coordinator, billing specialist, revenue cycle coordinator

Gets every visit verified and accepted by the aggregator so it can be billed.

Sees

  • EVV status for every visit in their scope
  • Exceptions by type, payer and clinician
  • Aggregator acceptance and rejection responses

Does

  • Enters corrections with the state's reason code and a note
  • Requests notes from clinicians on exceptions
  • Resubmits rejected visits after correction
  • Marks verified visits ready for billing

Cannot

  • Approve their own corrections
  • Change schedules or assignments
  • Change aggregator settings
Approvals
Their corrections are approved by a clinical manager or another designated approver before resubmission.
Notified about
New exceptions, aggregator rejections, and corrections returned by the approver.

Branch director

Branch director, administrator, operations director

Oversees scheduling, visit completion and EVV performance across the branch.

Sees

  • All schedules, visits, exceptions and reports for the branch
  • Travel time and mileage trends
  • Scheduling rules and their change history

Does

  • Sets scheduling rules such as overtime limits and territories
  • Reviews branch performance with managers
  • Approves access for auditors
  • Prepares information for state surveys and payer audits

Cannot

  • Approve a correction they entered themselves
  • Edit or delete entries in the audit trail
  • See other branches unless granted
Approvals
Approves scheduling rule changes and auditor access for the branch.
Notified about
Branch-level backlogs of missed visits or exceptions above the level they set, and aggregator submission failures.

Auditor (read-only)

Compliance officer, internal auditor, state or payer auditor (under temporary access)

Reviews visit records, corrections and evidence without being able to change anything.

Sees

  • Visits, EVV records and corrections within the scope granted
  • Reports on exceptions and corrections
  • The audit trail

Does

  • Searches and reads records within their scope
  • Exports records and reports they have been given access to, with each export logged
  • Leaves review notes where your agency enables them

Cannot

  • Change, approve or delete anything
  • See records outside the scope and dates granted
  • Keep access after it expires
Approvals
Their access is approved by the branch director or an administrator, with a scope and an end date.
Notified about
Nothing by default; access granted and expiring is confirmed to the person who approved it.

Administrator

Application administrator, IT administrator

Manages users, roles, branches and interfaces on behalf of the agency.

Sees

  • Users, roles, branches and territories
  • Interface and aggregator connection status
  • The record of permission changes

Does

  • Adds and removes users, or maps them from single sign-on groups
  • Maintains aggregator connections and state reason code lists
  • Monitors interface errors
  • Runs access review reports

Cannot

  • Enter or approve EVV corrections
  • Change visit records
  • Grant themselves an operational role without branch director approval
Approvals
Role changes that grant access to patient details or approvals are approved by the branch director.
Notified about
Interface or aggregator failures, access reviews coming due, and accounts not used for a period your policy sets.

Permissions at a glance

ActionClinicianSchedulerClin managerEVV coordBranch dirAuditorAdmin
View schedules and routesOwn work onlyFullFullView onlyFullView onlyNo access
Publish schedulesNo accessFullFullNo accessFullNo accessNo access
Accept same-day re-plansNo accessFullFullNo accessFullNo accessNo access
Override scheduling rulesNo accessOwn work onlyApprovesNo accessApprovesNo accessNo access
Check in and out of visitsOwn work onlyNo accessNo accessNo accessNo accessNo accessNo access
Add notes to exceptionsOwn work onlyFullFullFullFullNo accessNo access
Enter EVV correctionsNo accessNo accessFullFullFullNo accessNo access
Approve EVV correctionsNo accessNo accessApprovesNo accessApprovesView onlyNo access
Release visits for billingNo accessNo accessNo accessFullFullView onlyNo access
Change scheduling rulesNo accessNo accessNo accessNo accessFullNo accessNo access
View audit trailNo accessNo accessView onlyView onlyView onlyView onlyView only
Manage users and rolesNo accessNo accessNo accessNo accessApprovesNo accessFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Separation is built in: nobody approves an EVV correction they entered, and clinicians cannot change the times of their own visits after check-out.
  • Roles are configured with you during implementation. You can rename them, create custom roles, and limit them by branch, territory, discipline or payer, so each team sees only the patients and visits it is responsible for.
  • Every permission change is recorded in the audit trail with who made it and when, and access review reports list each person's roles for periodic review by the branch director.
  • Staff sign in through your identity provider, and roles can follow its groups. State and payer auditors get temporary read-only access with a defined scope and an end date, rather than shared accounts.

Features

What it does

Schedule builder

Turns ordered visits into a proposed schedule matched by discipline, skills, availability, visit windows and patient preferences.

Route planning

Orders each clinician's visits to reduce travel between homes while respecting time windows and visit lengths.

Same-day re-planning

When a visit is cancelled or added, proposes changes for the scheduler to accept, with the affected clinicians and patients shown.

Clinician mobile app

The day's visits, directions, patient visit notes and check-in and check-out on the clinician's phone.

EVV capture

Records the six federally required EVV data elements at each visit, with location captured at check-in and check-out.

Aggregator submission

Sends verified visits to state EVV aggregators in the format each state specifies, where the state accepts alternate EVV systems.

Exception management

Lists visits with missing or mismatched EVV data, and records each correction with the state's reason code, note and approver.

Live visit board

Shows schedulers which visits are under way, late, missed or complete across the branch.

Continuity of care

Keeps track of which clinicians each patient has seen and favors consistent assignments where the patient prefers it.

Mileage records

Planned and actual miles per clinician and day, for mileage reimbursement and travel time records.

Clinician qualifications

Licenses, skills and required training kept with each clinician, so visits are only assigned to people qualified for them.

Audit trail

Who scheduled, changed, verified or corrected each visit, and when, with the reason for every correction.

Integrations

How it connects to your systems

Connects toHowWhat flows
Agency management or EHR systemPatients, ordered visits, frequencies and visit types from your home health or home care system, and completed visit status back to it.In: patients, addresses, orders and visit types. Out: scheduled and completed visits with EVV data.
State EVV aggregatorsVerified visits sent in the file or API format published by each state you serve, where the state allows agencies to use an alternate EVV system.Out: EVV visit records. In: acceptance and rejection responses.
Mapping and travel timeAddresses geocoded and travel times estimated through a mapping service agreed during implementation.Out: patient and clinician addresses for geocoding. In: coordinates and travel time estimates.
PayrollVisit hours, travel time and mileage exported for payroll and reimbursement.Out: hours, travel time and miles by clinician and day.
Human resourcesClinician records, licenses and training status from your HR or credentialing system.In: clinician details, disciplines, licenses and expiry dates.
Single sign-onOffice staff and clinicians sign in through your identity provider (SAML or OpenID Connect).In: user identity and group membership for role assignment.
Work APISchedules, visits, EVV status and exceptions available to your data warehouse and reporting tools through the Moraph Work API.Out: visits, routes, EVV records and exceptions.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Staff sign in through your identity provider, so your password and multi-factor policies apply on office computers and phones.

Role-based access

Clinicians see only their own patients and visits; office staff see their own branch.

Protected health information

Patient details on phones are limited to what the visit needs, and Moraph signs a business associate agreement with your organization.

Location only during visits

The app records a clinician's location at check-in and check-out, not continuously through the day.

Encryption and keys

Client data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Complete audit trail and residency

Every change, verification and correction is logged with the person and time and cannot be edited, and data stays in the hosting region you choose: the United States, the United Kingdom or Australia.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Visit completion

For schedulers and clinical managers

Scheduled, completed, late and missed visits for the day or period, with the reason recorded for each missed visit.

Break down by
Branch, Clinician, Discipline, Status, Missed visit reason
Delivered as
Live dashboard; scheduled email; CSV export
Used for
Recovering missed visits and spotting patterns by clinician or territory.

Unassigned and at-risk visits

For schedulers

Ordered visits not yet assigned, and assigned visits at risk because of availability, qualifications or travel.

Break down by
Branch, Discipline, Visit type, Due date
Delivered as
Live dashboard
Used for
Filling gaps in the schedule before visits are missed.

Coverage against orders

For clinical managers

Visits completed for each patient compared with the frequency ordered in the plan of care or service plan.

Break down by
Patient, Discipline, Branch, Period
Delivered as
Live dashboard; CSV export
Used for
Making sure patients receive the visits ordered for them.

EVV and billing

EVV status

For eVV and billing coordinators

Visits verified, with open exceptions, and accepted or rejected by the aggregator, by payer and state.

Break down by
Payer, State, Status, Branch
Delivered as
Live dashboard; scheduled email; CSV export
Used for
Clearing exceptions so visits can be billed.

Exceptions by type

For eVV coordinators, clinical managers and branch directors

EVV exceptions by type, such as late check-in, missing check-out or unexpected location, and by clinician.

Break down by
Exception type, Clinician, Discipline, Period
Delivered as
Live dashboard; CSV export
Used for
Targeting clinician coaching and fixing the causes of repeated exceptions.

Aggregator rejections

For eVV and billing coordinators

Visits rejected by a state aggregator, with the rejection reason and resubmission status.

Break down by
State, Rejection reason, Payer, Status
Delivered as
Live view; CSV export
Used for
Resubmitting rejected visits and fixing setup problems behind them.

Travel and workforce

Travel time and mileage

For branch directors and payroll

Planned and actual drive time and miles per clinician and day.

Break down by
Clinician, Branch, Territory, Period
Delivered as
Live dashboard; CSV export for payroll
Used for
Mileage reimbursement, travel time records and reviewing territory design.

Clinician workload

For schedulers and branch directors

Visits, visit hours and travel per clinician compared with their availability.

Break down by
Clinician, Discipline, Week, Branch
Delivered as
Live dashboard; CSV export
Used for
Balancing workload and planning hiring by territory.

Continuity of care

For clinical managers

The number of different clinicians each patient has seen in the period, by discipline.

Break down by
Patient, Discipline, Branch, Period
Delivered as
Live dashboard
Used for
Improving consistency of assignments where patients prefer familiar clinicians.

Compliance and audit

Corrections log

For compliance officers, branch directors and auditors

Every change to EVV data with the original and corrected values, reason code, note, who entered it and who approved it.

Break down by
Reason code, Entered by, Approved by, Payer, Date range
Delivered as
Live view; PDF and CSV export
Used for
Answering state and payer audits about how visit records were corrected.

Audit trail extract

For compliance officers and auditors

Who scheduled, changed, verified or corrected a selected visit, patient or period.

Break down by
Record, User, Action, Date range
Delivered as
On request in the product; CSV and PDF export
Used for
Providing evidence for surveys and audits without assembling it by hand.

Exports, access and evidence

  • Every report can be exported to CSV, and summary and evidence reports to PDF. Reports can be scheduled to arrive by email for the people entitled to see them.
  • Each report can be filtered and the filters saved, so a scheduler or branch director can keep their own views. Reports that need a different shape can be built in your own tools from the data described below.
  • Schedules, visits, EVV records and exceptions are available through the Moraph Work API, and can be delivered to your data warehouse or business intelligence tool.
  • Reports respect each viewer's role: clinicians see their own visits, office staff see their own branch, and auditors can be given read-only access to reports and the audit trail.
  • Compliance and audit reports can be run as of a past date and give the same result each time. Running and exporting a report is itself recorded in the audit trail.

Deployment

Where and how it runs

Moraph cloud

Hosted and operated by Moraph in the United States region. United Kingdom and Australia regions are available for organizations outside the US.

Mobile app

The clinician app runs on iOS and Android phones, managed or personal, according to your device policy.

With a managed service

Optionally run alongside a Moraph managed service for aggregator submission monitoring and application administration.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Data and interface mapping

We map patients, orders, visit types and clinicians from your agency system and agree the interface or file schedule. We need interface details and a contact from your agency system administrator.

State EVV setup

For each state you serve, we confirm whether alternate EVV systems are accepted, configure the aggregator format and support the state's testing and approval steps with your team.

Scheduling rules

Visit lengths, time windows, skills, territories, overtime limits and preference rules are configured to match how your branches schedule.

Addresses and territories

Patient and clinician addresses are checked and geocoded, and service territories set for each branch.

Pilot branch

One branch uses the planner and app first, and results are reviewed with schedulers and clinicians before other branches follow.

Training and go-live

Schedulers, managers and billing staff are trained on their workflows, and clinicians receive short guidance on the app.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • It is not certified or approved for EVV in every state. Some states require agencies to use the state-provided system, and others require each alternate system to pass testing; availability is confirmed state by state during implementation.
  • It does not submit claims to Medicare, Medicaid or other payers. It marks visits ready for billing in your agency or billing system.
  • It is not an electronic health record and does not capture clinical documentation such as OASIS assessments or visit notes beyond the services recorded for EVV.
  • Routes are proposals based on estimated travel times; traffic, weather and clinical needs mean schedulers and clinicians make the final decision.
  • Location capture depends on the clinician's phone having location services and a signal; visits without them become exceptions to resolve.
  • Decisions about corrections, reason codes and visit records are your agency's; the product records and enforces the approval steps you configure.
  • It does not calculate pay, overtime or wage-and-hour compliance; it exports hours, travel time and mileage for your payroll process.
  • Ordered visits and frequencies must come from your agency system; the planner does not create or change plans of care.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Load a sample day of anonymized visits for one branch and compare the proposed routes with how the day was actually run
  2. Cancel and add visits and review the re-plan the scheduler is offered
  3. Ask a clinician to check in and out of test visits on their own phone
  4. Confirm the EVV format and approval status for each state you serve
  5. Work an EVV exception from flag to approved correction and review the record it leaves
  6. Confirm role separation: who can enter, approve and release a correction

Questions

Frequently asked questions

Can we use it for EVV in our state?

It depends on the state. Some require the state-provided system and others accept alternate systems after testing. We confirm each state during implementation and support the approval steps with your team.

Does it track clinicians all day?

No. Location is recorded at check-in and check-out to verify the visit, not continuously.

Does it replace our agency management system?

No. Patients, orders and clinical documentation stay in your agency system; the planner schedules, routes and verifies visits and sends the results back.

Do you sign a business associate agreement?

Yes. Patient information is involved, so Moraph signs a business associate agreement with your organization.

How is it priced?

As a subscription, usually measured by the number of clinicians or visits, with implementation charged separately. See Working with Moraph for what drives a quotation.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the version you are evaluating.

Next steps

Evaluate Home Health Logistics Planner

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Home Health Logistics Planner guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Home Health Logistics Planner support guide.