IDD EHR software and scheduling software are not the same thing
Agencies searching for "IDD EHR software" are usually trying to solve one of two completely different problems, and the distinction matters before you buy anything. One is the record of what happened to the people you support — service notes, plans, incidents, billing. The other is the record of your workforce — who is scheduled, who is certified, who actually clocked in, and who covers the shift when someone calls out. Most software does one of these well and the other badly, which is why most agencies end up running both.
What an EHR does in this sector
An electronic health record for IDD services is built around the person being supported. It holds the individual support plan, service notes written against that plan, progress toward goals, incident reports, medication records where applicable, and usually the billing submission that depends on all of it. Its unit of organisation is the person receiving services, and it is where your documentation and claims live.
What scheduling and workforce software does
Workforce software is built around your staff. It holds who is rostered at which home, what certifications they hold and when those expire, when they actually clocked in and out, who is approaching overtime, and what happened when a shift went uncovered. Its unit of organisation is the employee and the shift, and it is where your labour cost and coverage risk live.
Where agencies get caught out
Documentation systems generally include a calendar, and scheduling tools generally include a notes field, so it is easy to assume either one covers both jobs. In practice the gaps show up at the edges: a documentation system rarely knows that the person you just rostered has a lapsed certification or is about to cross an overtime threshold, and a generic scheduling tool has no concept of a sleep shift, a required staffing level per home, or an automated coverage offer at 2 AM.
The question worth asking a vendor
Rather than asking whether a product "does scheduling" or "does documentation", ask what happens at the moment of assignment. Does the system check certifications before allowing someone onto a shift? Does it show hours worked to date while the assignment is being made? Does it know the difference between an awake overnight and a sleep shift? Those answers separate a calendar from a coverage system, regardless of what category the product is sold under.
Which one DSPsystem is
DSPsystem is the workforce half, and deliberately only that half. It does not hold resident or client records, it does not store service notes or care plans, and it does not submit claims. It handles scheduling, certification enforcement, time tracking, call-out coverage, overtime visibility and staff compliance — and it is designed to sit alongside whatever documentation system you already use rather than replace it.
Why running both is usually the right answer
Replacing a documentation system is a serious project: it holds your historical records and your billing depends on it. Adding workforce software does not touch any of that, because the two systems own different data. That is why the common path is not migration but addition — keeping the documentation system that already works and fixing the staffing side separately.
Common questions
- Is DSPsystem an EHR?
- No. DSPsystem holds no resident or client records, no service notes and no care plans, and it does not submit claims. It is workforce operations software — scheduling, certifications, time tracking and coverage. If you need an electronic health record, you need a different category of product, and you will likely run it alongside this one.
- Do we have to replace our documentation system to use it?
- No, and most agencies do not. The two systems own different data — yours holds the record of services delivered, this holds the record of who worked and whether they were qualified. They operate independently, so adding one does not require migrating the other.
- Can it produce the staffing records an auditor asks for?
- It can answer the workforce half: who worked which shift, when they clocked in and out, what certifications they held on that date, and how a shift was covered when someone called out. The service documentation itself stays in your documentation system.
- Why not just use the calendar in our documentation system?
- You can, and for a single home it is often enough. It tends to stop working once no one person can hold every staff member's hours and certifications in their head, because a calendar shows you what was planned rather than checking whether the plan is allowed.
- What does it cost alongside an existing system?
- Pricing is per home, starting at $149 per home per month, rather than per user — so headcount changes do not move the bill. Because it does not replace your documentation system, the comparison is the cost of the platform against the coverage and overtime it prevents, not against your existing software spend.
See it with your own homes
A short walkthrough using your shift patterns — no commitment.
Request a demo