EmpowerEHR wasn't designed by a product committee guessing at your workflow. It was built by a nurse, a Director of Nursing, and a guardian who couldn't find software that respected any of those roles.
Most electronic health records used by I/DD providers today started life somewhere else — a hospital, a skilled nursing facility, a generic behavioral health platform — and were bolted onto ICF/IID and HCBS waiver workflows after the fact. The result is software that documents a med pass fine, but treats a person-centered ISP, an MUI investigation, or a nursing delegation packet as an afterthought, if it's supported at all.
We didn't think that gap should exist. Not because it's a hard technical problem — it isn't — but because nobody building it had sat close enough to the work to notice it mattered.
EmpowerEHR started from the opposite direction: instead of retrofitting a generic chart, we built the chart around outcomes, supports, incident workflows, and delegation from day one — because those are the things that actually determine whether a person has a good day, and whether an agency survives its next survey.
Every major decision in EmpowerEHR was shaped by one of these vantage points — sometimes all four at once.
As a Registered Nurse and Certified Emergency Nurse, I've stood at the med cart wondering whether a status meant "held" or "refused," and read a vitals trend after it was too late to act on it. That's why the eMAR guides every pass with unambiguous statuses, and why vitals-based holds and PRN follow-ups are built into the workflow — not a note someone has to remember to write.
As the DON of an ICF/IID facility, I own the outcome when a delegation lapses, an MUI gets reported late, or an audit packet is missing a signature. Incident management, nursing delegation and competency tracking, and expiration alerting exist in EmpowerEHR because I needed them to exist before a survey found the gap for me.
My younger brother has Down syndrome and receives HCBS waiver services, and I'm his legal guardian. I've sat on the other side of the ISP table wanting to know his outcomes were real goals, not boilerplate — and wanting a faster, safer way to sign off than a fax. That's why person-centered ISPs, revision history, and tamper-evident remote e-signatures are core to the product, not an add-on.
Before any of the professional titles, I'm a brother and a caregiver. That's the perspective that keeps the other three honest — the reminder that every row in every table is a person having a day, not a data point. It's also why a secure Family Portal, so families can see how their loved one is doing and message the care team directly, is at the top of our roadmap.
Founder — Brother, Guardian, Caregiver
Adam is a Registered Nurse with a Master of Science in Nursing Education and board certification as a Certified Emergency Nurse, currently serving as Director of Nursing at an ICF/IID facility. He is also the legal guardian and brother of an adult with Down syndrome who receives HCBS waiver services — giving him a rare view of I/DD care from the clinical side, the compliance side, and the family side at once. Adam designed and built EmpowerEHR himself, from the data model up, because the system he needed for all three roles didn't exist yet.
Ohio DODD and Ohio ISP rules are where EmpowerEHR proved itself first — the state Adam knows best, as a DON living under those regulations every day. The product was built so each state's rules plug in as a jurisdiction definition, not a rewrite. If you're outside Ohio, we want to know where you are.
See our expansion roadmapEvery demo is led by someone who understands both sides of the chart — clinical and family. Bring your hardest questions.
Request a demo