In short
- A caregiver coordination app lets a patient's network of family, friends and paid carers share tasks, a calendar, messages and updates, while the patient, or the person acting for them, decides what each member can see.
- When a provider or plan runs the app, HIPAA lets it share information directly relevant to a family member's or friend's involvement in care, usually after the patient agrees or has a chance to object, so the app has to record that choice per person.
- Medicare now pays for caregiver training and, in the GUIDE dementia model, for care navigation, caregiver support and respite, which gives the clinical team a reason to work inside the same app as the family.
A caregiver coordination app gives everyone who helps a patient at home one shared place to work: a list of care tasks people can take on, a calendar, messages, reminders and updates on how the patient is doing. The patient, or the person who manages the network for them, decides who joins and what each person sees. Most of the design work goes into the roles and permissions, the rules on sharing health information with family, and the link to the clinical team. That link is what makes a group chat part of a care plan.
This is a different problem from proxy access in a patient portal. Proxy access lets one person act inside the provider's portal on the patient's behalf. A coordination app serves a whole network, most of whom will never need the medical record. Our article on caregiver proxy access covers the portal side.
Who uses a caregiver coordination app?
Start with the roles, because every screen and every permission follows from them. A typical network has:
- The patient, who may also own the network, or may not be able to manage it.
- A network owner, often a spouse or adult child, who invites people and sets what they see.
- An inner circle of close family who see more detail, such as health updates and appointments.
- A wider group of friends and neighbors who help with practical tasks like meals, lifts and shopping.
- Paid carers, who need task lists and handover notes but not family conversations.
- Clinical staff at the provider or plan, who see the network's activity for their own patients and can step in.
One worked example: we rebuilt a white-label platform for a digital health company in Australia that lets healthcare organizations launch branded apps for patients, carers and family networks. It has five user roles: Captain (the network owner), Admin, Helper, Inner-Circle Helper and the broader Helper Network of family and friends. It runs as React Native apps for iOS and Android plus a web dashboard, and six apps have launched on it. The partnership started in 2017, with 14 specialists across the engagement.
What features does a care network need?
- A roster of care tasks that anyone invited can see and accept, so work is spread across the network instead of falling on one person.
- Tasks that repeat on a schedule, with an end date, and a default list of common household tasks to start from.
- A visibility switch on each task or note, so some items stay within the inner circle.
- A shared calendar of appointments and tasks, with reminders to the person who accepted each one.
- Messages organized by topic, with attachments, so a conversation about medications does not get lost in one about the weekend roster.
- Regular check-ins on how the patient is doing, which the clinical team can see and act on.
- Education content matched to the patient's needs and the tasks the network has taken on.
- A way to belong to more than one network, since the same person may help a parent and a neighbor.
The Australian platform covers most of this list: a roster of tasks family and friends accept, tasks with repeat options and an inner-circle-only toggle, chat with attachments, a calendar with task management, a network switcher, care needs screening at sign-up that builds a supportive care plan, and regular risk assessments (PROMs) that trigger education and guidance from clinical experts when needs at home change.
What health information can a provider share with the family?
When a HIPAA covered entity, such as a provider or health plan, offers the app, the sharing rules in 45 CFR 164.510(b) apply. A covered entity may disclose to a family member, other relative, close personal friend, or any other person the patient identifies, the protected health information directly relevant to that person's involvement in the patient's care or payment for it. How it decides depends on the situation:
- If the patient is present and has capacity, the covered entity may share after getting the patient's agreement, after giving the patient a chance to object without an objection, or when it reasonably infers from the circumstances that the patient does not object.
- If the patient is not present, or cannot agree or object because of incapacity or an emergency, the covered entity may use professional judgment to decide whether sharing is in the patient's best interests, and then share only what is directly relevant to the person's involvement.
- After the patient's death, it may share relevant information with family and others who were involved in care, unless that conflicts with a prior preference the patient expressed and the covered entity knows about.
Each of these maps to something the app records. Store, per network member, what the patient agreed to share, when, and who recorded it. Let the patient object to sharing with a specific person, and act on that at once. Scope clinical updates to what each person's role in care needs, so the friend who drives to appointments sees the appointment, not the lab results. When the patient lacks capacity, record who made the decision and on what basis.
Who offers the app matters. If a provider or plan runs it, the vendor building and hosting it is usually handling PHI on their behalf. We sign a BAA before anyone on our team sees PHI.
How does the app connect to the clinical team?
Medicare programs now pay for work with caregivers, which gives providers a reason to bring their staff into the app instead of leaving the family on its own.
Caregiver training
Medicare Part B covers caregiver training when the training focuses on the patient's health and treatment goals, set with their provider, and the patient needs a caregiver's help for treatment to succeed, according to Medicare.gov. Topics include giving medications, helping with daily tasks, safe patient movement, communicating with the patient, managing the condition, preventing bedsores and infections, and wound care. The caregiver can get individual or group sessions without the patient present, if the provider decides it fits the treatment plan. After the Part B deductible, the patient pays 20% of the Medicare-approved amount.
CMS's CY 2024 rule created payment for this training and listed who may furnish it: physicians, nurse practitioners, clinical nurse specialists, certified nurse-midwives, physician assistants, clinical psychologists, and physical therapists, occupational therapists and speech-language pathologists. The training must be part of the patient's individualized treatment plan or therapy plan of care. The CY 2025 rule allowed these services to be furnished via telehealth. In an app, that means scheduling training sessions, running them by video, and keeping a record linked to the treatment plan.
The GUIDE dementia model
CMS's GUIDE model, which began July 1, 2024 and runs for eight years, tests comprehensive dementia care for Medicare patients and their caregivers. Participants assign patients and caregivers to care navigators, offer caregiver training and support services, screen patients and caregivers for psychosocial and health-related social needs, and run a 24/7 support line. Medicare pays for respite of up to $2,500 a year per eligible patient, including in-home care, adult day programs and facility-based respite. A GUIDE participant needs software that links the care navigator, the family network and respite bookings in one record.
Care plans in chronic care management
CMS's chronic care management booklet lists caregiver assessment among the possible parts of the comprehensive care plan, and says to give patients and caregivers a copy of the care plan when needed. It also calls for a way for patients and caregivers to communicate with practitioners by phone and through secure messaging or a portal. A coordination app that shows the family the parts of the care plan they help with fits that requirement well.
How should permissions work?
- The network belongs to the patient. The owner role can manage it, but the patient's own choices about sharing come first whenever they have capacity.
- Permissions attach to the role and can be narrowed as well as widened per person and per item.
- Removing someone takes effect at once on every device, including cached data on their phone.
- Clinical staff join as their own role. In the systems we build, each clinician sees only their own patients.
- Keep a history of who was invited, removed or given wider access, and by whom, so a disputed decision can be traced.
- Push notifications and lock-screen previews should carry no health detail. Show "You have a new update" and the rest after sign-in.
Should you build, white-label or buy?
There are three routes. A consumer app the family downloads is fast to start but sits outside your care team and your data. A white-label platform gives each organization its own branded app on a shared foundation. A custom build fits a single program with unusual rules, such as a GUIDE participant's navigator workflow.
White-label is worth a close look if you serve several organizations or programs. On the Australian platform, each organization gets its own logos and colors, and a super admin sets which features each copy has. The work that made it reusable came first: discovery, a user flow and a full specification, which did not exist before the rebuild, and 10 versions of the Home page tested with users before the final direction. Whichever route you take, test with real caregivers early, on their own phones and in the places they will use the app.
Before launch, we run a penetration test, because a network app invites many people who are not employees into a system that holds health information.
Planning a caregiver app?
Talk to an engineer at Onix Health about your care network, its roles and its link to your clinical team. Onix Systems has built software since 2000 and has 370+ engineers. Our free five-day technical audit ends with a written report on your design, permissions and data flows.
Sources
- 45 CFR 164.510: uses and disclosures requiring an opportunity to agree or object (Cornell LII)
- Medicare.gov: caregiver training services coverage
- CMS Innovation Center: Guiding an Improved Dementia Experience (GUIDE) Model
- CMS fact sheet: CY 2024 Physician Fee Schedule final rule
- CMS fact sheet: CY 2025 Physician Fee Schedule final rule
- CMS MLN909188: Chronic Care Management Services (June 2025)