Skip to content

Home Care Management

Home care visits verified at both ends, with the unbillable hours totalled.

The short answer

Home Care Management is an Odoo app for home care and domiciliary agencies. Check-in and check-out are readonly datetimes stamped when they happen, each with its own location, and verification is computed from having both. The board then totals the duration of the visits that failed, so a compliance percentage arrives as hours a payer will not fund. Care plans, caregivers and the visit round sit alongside.

Request this module

Last updated

What it is for

Electronic visit verification is not paperwork for its own sake. A payer funds a visit that was verified and refuses one that was not, so a caregiver whose phone was flat has not merely missed a step, they have worked an unpaid hour. The number we usually have is a compliance percentage, which is the wrong unit. It sounds like a pass. What the finance director is actually asking is how many hours the missing part adds up to, and what those hours were worth.

Platform
Odoo
Category
Field service
Works with
Odoo 18 · Odoo 19
Technical name
home_care
Status
Direct from webbox
Pricing
Paid

What is inside it

  1. 01

    Verification

    check_in and check_out are readonly datetimes stamped when they happen, each with its own location. The verified flag is computed and stored from having both, so a visit either carries the evidence or it does not.

  2. 02

    Care plans

    A client has a care plan, and a visit references it and records which of its tasks were completed. That turns a visit note from a paragraph into something a supervisor can audit.

  3. 03

    The round

    Missed rate and completion rate stay separate figures. A visit the client called off and a visit nobody attended are different problems with different fixes, and reporting completion alone cannot tell them apart.

  4. 04

    The board

    Six tiles led by unbillable hours, because hours are what get refused. Schedule variance sits alongside, separating a visit that ran long from a visit that never happened. Each tile opens the visits it counted.

What it looks like in practice

  1. The call is worked but only one end is stamped

    A caregiver arrives and the check-in is stamped with its location. The handset dies before the end of the call, so no check-out ever lands.

    Verification is computed and stored from having both stamps, so this visit is unverified and therefore unbillable. The board totals the duration of every visit in that state instead of reporting a pass rate and leaving the arithmetic to somebody else.

    Unbillable hours
    5.1
    EVV compliance
    88%
    Visits in the period
    31

    Figures from the module's own demo data, on a fresh install. Install with demo data, open the board and click the first tile.

    VerificationThe board

  2. A cancelled call and an unattended call are not the same miss

    Two calls in the same week did not happen. The client called one off, and nobody turned up to the other.

    Missed rate and completion rate are computed separately, and the visit list carries state and verification status on every row, so the two cases can be filtered apart rather than netted off against each other.

    Missed rate
    6.5%
    Completion rate
    80.6%

    Figures from the module's own demo data, on a fresh install. On a demo install, open Visits and group by state.

    The roundThe board

  3. A family asks whether the shower actually happened

    A supervisor is asked what was done on one particular call, and the only record of it is free text in a note field.

    The care plan holds the tasks and the visit references the plan, recording which of those tasks were completed, so what was meant to happen and what was recorded sit on the same thread.

    Behaviour of the shipped code.

    Care plansVerification

What it deliberately does not do

No state EVV aggregator
Verification is captured and enforced here. Transmitting it to Sandata, HHAeXchange or a state aggregator is a separate integration.
No payroll or billing
Unbillable hours are computed. Turning billable hours into an invoice or a pay run is somebody else's model.
No caregiver mobile app
Check-in and check-out happen in Odoo's responsive backend. There is no offline native client and no GPS enforcement.
No rostering optimiser
Visits carry a scheduled window and a caregiver. Building the week's rota is not attempted.

Questions

Can I install this on Odoo Online?
No. Odoo Online cannot install modules that contain Python, so this runs on Odoo.sh or a self-hosted instance. Check the versions listed above for the series and edition it is verified against.
Will it file our verification with a state aggregator?
No. Verification is captured and enforced inside Odoo, and the unbillable hours are computed from it, but nothing is transmitted to Sandata, HHAeXchange or any state aggregator. That is a separate integration, and each aggregator asks for a different format and a different transport.
Do caregivers get a phone app?
No native client ships with the module. Check-in and check-out happen in Odoo's own responsive backend, so there is no offline queue and no GPS enforcement at the door. The location stored against each stamp is what the browser reported at the moment the stamp was taken.
How is access split, and does it respect multi-company?
Two groups. Home Care User works visits and clients, while Home Care Manager reaches care plans, caregivers and configuration. Record rules fence clients, care plans, visits and caregivers by company, so a database running several branches keeps each branch's round to itself.

Have something to build?

Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.

Start a project Browse services
  • Free scoping call
  • Reply within 1 business day
  • No lock-in