Introduction: Two Agencies, Two Feature Sets, One Shared Core
Most lists of home care software features describe a single type of agency. Then they get sold to another. A Medicare-certified skilled nursing facility documents physician-ordered nursing visits under the federal Conditions of Participation. A non-medical agency schedules personal care shifts. The rules are different. But both run on the same operational core: client and caregiver records; scheduling and matching; a caregiver mobile app with visit capture; care plans and point-of-care documentation; payroll and billing; and family communication. That shared core is substantial enough that most custom software development for home care starts here, before either agency type’s specific rules come into play.
This checklist starts with that shared core. Then it marks exactly where skilled and non-medical requirements diverge, rather than averaging them. It closes with the features agencies commonly buy and rarely use, a useful contrast to the caregiver app itself, which is the product’s core and its EVV capture device, and the reason most caregiver app development work pays off immediately where these secondary features don’t. The goal is simple: ship the features that actually carry the business first.
The Caregiver Mobile App
The caregiver app is the product’s core. It’s also the EVV capture device. Get this right, and everything else works better.
Visit Capture That Works Everywhere
Caregivers clock in and out, with location captured at both points. A telephony fallback covers clients without a smartphone. A fixed device option covers the home itself. These aren’t backup options. They’re the difference between serving a client in the suburbs and one in a rural home with no signal. Design for all three from day one.
Offline by Default
Homes often have poor signal. A caregiver should never have to choose between finishing a task and recording it. That means full offline capture, with a clear sync model behind it. The office also needs visibility into which visits haven’t synced yet. An unsynced visit is an unverified visit. In many states, it’s unbillable too.
The Shift, the Tasks, and the Client
Caregivers need today’s schedule, with addresses and directions. They need the care plan tasks for that visit. They need to confirm each task as it’s done, add care notes, and see client-specific instructions. This screen has to work for someone standing in a kitchen. Not someone sitting at a desk.
Change of Condition and Escalation
Caregivers need a fast way to flag that something has changed. It should route to a real person. It should confirm receipt. And it should escalate if nobody responds. The caregiver is often the only person in the home. Their observations are some of the most valuable data the agency gets.
Scheduling, Matching, and Open Shifts
Scheduling is where good intentions meet real constraints. Overtime is one of them, and it deserves to be treated as a first-class part of the scheduling logic, not an afterthought at payroll.
Matching needs to account for certification and skill level, authorized service type and hours, geography, travel time between visits, availability, and language. Client preferences matter too. In someone’s home, though, these preferences often function as requirements.
Continuity of caregiver should be an explicit scheduling goal. It shapes the client’s experience. It’s also one of the better predictors of whether a caregiver stays with the agency.
Projected weekly hours need to be visible the moment a coordinator makes an assignment. That way, they can see if a shift is about to create overtime, instead of finding out at payroll. This single feature has a direct, measurable effect on margin. That view lives in the coordinator console delivered through custom web application development.
Open shift management matters too. Caregivers should be able to self-claim shifts from the app. The system should also broadcast open shifts to qualified, available staff. Call-offs happen daily. Fill rate is both a revenue number and a client-experience number.
Shift models need to be represented properly: hourly visits, live-in, 24-hour arrangements, split shifts, and overnight care. Forcing all of these into a standard hourly visit record just creates payroll problems later, built on a strong scheduling console.
Authorization awareness closes the loop. A schedule that would exceed authorized hours should get flagged before it’s published, not after the visits are already delivered.
Care Plans and Point-of-Care Documentation
Care planning looks different depending on the agency type. Non-medical and skilled care need to stay clearly separated here.
For non-medical care, the plan is task-based. It covers assistance with daily living, homemaking, and companionship. Tasks get scheduled against specific visits. Completion is confirmed right at the point of care, with a note added wherever something needs saying.
For skilled care, the plan of care originates from physician or allowed-practitioner orders. It follows the comprehensive assessment. It needs discipline-specific documentation for nursing and therapies, plus aide assignments with written instructions. Verbal order capture matters too. So does the relationship between an order and the plan it feeds. Neither should be handled as free text.
Both care types need versioning. A care plan changes as a client’s needs change. The agency should be able to show exactly what was in effect on any given date.
Assessment and reassessment scheduling needs reminders built in. A required reassessment should never be discovered as overdue.
Documentation itself needs to be designed for the person actually doing it. Picture a caregiver completing a visit note on a phone, in poor light, after a demanding shift. That’s the realistic case. Form design should assume it, not treat it as the exception.
Payroll and Billing Features
This is the money layer, and it needs to be accurate. What agencies actually need is a pay rules engine, not a simple hourly rate field. Rates can vary by client and service type. Add shift and weekend differentials. Add holiday pay. Overtime has to be calculated across a full week, even when that week spans several clients and payers. Then there’s mileage, travel time between visits, and training or meeting time.
Travel time deserves particular attention. Time spent traveling between clients during the workday is generally compensable. That means the schedule and the route aren’t just logistics. They’re inputs to a wage calculation.
Live-in and sleep-time arrangements need their own rules. They shouldn’t get approximated as long hourly shifts. Because pay rules like these carry real legal risk, agencies should work with employment counsel to confirm how they apply.
Payroll export should work with whatever system the agency already runs, with a review and approval step before anything leaves. Payroll errors are one of the most reliable causes of turnover in this workforce. Getting this right isn’t just about accuracy. It’s a retention feature.
On the billing side, agencies need multi-payer support. That covers Medicaid programs and managed care, private pay with invoices, cards on file, and statements sent to a family member elsewhere. It also covers long-term care insurance documentation packages, plus VA and area agency programs.
Authorization tracking against delivered hours closes the loop. It needs the same warning-before-delivery discipline the scheduler relies on.
Family Portal and Communication
Families need visibility into care, without stepping on the client’s own rights. This is where access design and client preference deserve real care.
At a minimum, families should see schedule visibility: who’s coming and when. Visit confirmation. Completed tasks. Care notes written in plain language a family member can actually understand, not clinical shorthand.
Secure messaging with the office matters too. There should be a clear way to raise a concern, one that produces a record instead of a voicemail nobody follows up on.
For private-pay families, the portal needs invoices, payments, and statements. It also needs to handle a common case: the person paying isn’t always the person receiving care.
Access levels should be configured per person, with a record of who authorized what. Family structures are complicated. Capacity varies. Powers of attorney and guardianship determine who’s entitled to see what. A single shared family login just isn’t an access model.
The client’s own preferences about what gets shared should carry real weight in this design. A person receiving care in their own home has legitimate views on who sees their information, and those views deserve respect.
Notification preferences should respect people’s time. A family wants to know about a real change. Not every routine visit.
Where Skilled and Non-Medical Genuinely Diverge
This is where the two agency types stop sharing a feature set.
The skilled side adds a substantial layer. It starts with a comprehensive assessment, including OASIS. Physician and allowed-practitioner orders drive the plan of care. Documentation needs to be discipline-specific. Care coordination requirements come into play, along with quality assessment and performance improvement, and infection prevention. Aide training and competency need tracking too, with periodic on-site supervisory visits. Clinical record requirements cover content, retention, and patient access.
Billing works entirely differently on the skilled side. Payment is episodic, calculated under the Patient-Driven Groupings Model on 30-day periods. A Notice of Admission is required at the start of care. Value-based purchasing adjustments apply on top of that. All of this changes through annual rulemaking, which turns it into an ongoing maintenance commitment, not a one-time build.
The non-medical side has its own layer that skilled agencies simply don’t need. Private-pay retail billing is one piece. Long-term care insurance documentation is another. Shift models get more complex. The family portal also does more work here, functioning as a sales and retention tool, not just a communication channel.
An agency running both business lines needs both layers. That’s why the honest question at scoping time isn’t which features to include. It’s whether one platform should serve both businesses at all.
Final Thoughts
The pattern holds across all sections. There’s a shared operational core: records, scheduling, the caregiver app, documentation, payroll and billing, family communication. Then there’s a divergent layer, shaped entirely by whether an agency runs skilled care, non-medical care, or both.
Agencies that build their requirements this way, shared core plus the layer their specific business actually needs, end up with a specification they can evaluate honestly. Agencies that write one list covering both skilled and non-medical operations usually end up somewhere worse. The platform serves neither side as well as a focused one would.
If you’re defining requirements for a home care platform, separating the shared core from the skilled or non-medical layer your agency actually runs is what turns a feature list into a scope you can cost. That’s the work worth doing before a single line of code gets written, and it’s the kind of thing NewAgeSysIT helps agencies get right from the start. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.
