<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dana Kiser on Medium]]></title>
        <description><![CDATA[Stories by Dana Kiser on Medium]]></description>
        <link>https://medium.com/@dsplifetm?source=rss-59240668aabf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s6ZLrTiTSEd8IGHRB-O_dA.jpeg</url>
            <title>Stories by Dana Kiser on Medium</title>
            <link>https://medium.com/@dsplifetm?source=rss-59240668aabf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:24:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dsplifetm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[When Staff Resist Better Documentation: Managing the Friction That Comes With Compliance Technology]]></title>
            <link>https://medium.com/@dsplifetm/when-staff-resist-better-documentation-managing-the-friction-that-comes-with-compliance-technology-baa20984699e?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/baa20984699e</guid>
            <category><![CDATA[staffing]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ehr-software]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[daily-notes]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 00:53:52 GMT</pubDate>
            <atom:updated>2026-08-25T00:53:52.522Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SDsCpQQG4fHTud9uMp_Hpg.png" /></figure><p>Introducing a new documentation and compliance platform should make work easier.</p><p>Eventually, it usually does.</p><p>But anyone who has introduced a new system in a residential, day support, community engagement, or other licensed human-services setting knows there can be an uncomfortable period between <strong>“This will make us better”</strong> and <strong>“This is just how we do things now.”</strong></p><p>That period is friction.</p><p>When an organization moves from paper forms, Word documents, text messages, scattered files, or a less organized electronic system to a platform like <strong>CareHub</strong>, staff are asked to document in a new way. They may have required fields and deadlines. Missing information becomes easier to see. Supervisors can more easily check whether documentation was completed correctly and on time.</p><p>If AI-assisted tools are part of the new process, some employees may resist because they do not want to learn another tool.</p><p>The technology often gets blamed.</p><p>But the technology is not always the real problem.</p><p>Sometimes the problem is that the new system adds something the old system did not:</p><p><strong>Accountability.</strong></p><h3>“The Old Way Was Easier”</h3><p>You will hear this.</p><p>You may hear:</p><ul><li>“The old system was faster.”</li><li>“I don’t understand this app.”</li><li>“I don’t have time to do all of this.”</li><li>“It has too many questions.”</li><li>“Why do we have to change?”</li><li>“I’ve always done my notes this way.”</li><li>“The other system worked fine.”</li><li>“I don’t like using AI.”</li><li>“This is too much documentation.”</li></ul><p>Some of these concerns may be valid.</p><p>Organizations should listen when staff report real technical problems, repeated information, confusing steps, accessibility concerns, or training gaps.</p><p>But leaders also need to tell the difference between a <strong>system problem</strong> and a <strong>change problem</strong>.</p><p>They are not the same.</p><p>A system problem requires fixing the system.</p><p>A change problem requires leadership.</p><p>Sometimes, “The old way was easier” really means:</p><p><strong>The old way allowed me to do less.</strong></p><h3>Compliance Technology Changes What Can Be Seen</h3><p>A strong documentation system does more than store notes.</p><p>It creates visibility.</p><p>Supervisors can see missing documentation and incomplete answers. They can identify patterns. They can check whether staff are addressing outcomes, health and safety needs, supports, risks, and other required parts of an individual’s plan.</p><p>This visibility may feel uncomfortable to employees who were used to a system where incomplete documentation was harder to find.</p><p>That is one reason resistance to compliance technology can become emotional.</p><p>The conversation may seem to be about software.</p><p>It may really be about expectations.</p><p>If the old process allowed someone to write a short note at the end of the day, skip required information, enter information late, or depend on someone else to find mistakes, a system designed to prevent those practices will feel more strict.</p><p>That does not mean the new system is bad.</p><p>It may mean the system is doing exactly what it was designed to do.</p><h3>Documentation Is Part of Care</h3><p>Licensed providers need to repeat this until it becomes part of the workplace culture:</p><p><strong>If the service is required, the documentation is required.</strong></p><p>Documentation is not an optional office task to complete when there is extra time.</p><p>It is part of providing a compliant service.</p><p>Direct Support Professionals provide the hands-on care that helps individuals stay healthy, safe, involved, and supported. That work is extremely important.</p><p>The documentation of that work matters too.</p><p>A provider must be able to show what services were delivered, what supports were provided, whether known risks were addressed, how the individual took part in services, whether goals were addressed, and whether important events occurred.</p><p>That record protects the individual.</p><p>It protects the DSP.</p><p>It protects the provider.</p><p>It also helps the organization show compliance when regulators, licensing specialists, support coordinators, guardians, auditors, or other authorized people review services.</p><p><strong>Good care and good documentation are not competing priorities.</strong></p><p>They belong together.</p><h3>“I Don’t Have Time” Needs Context</h3><p>Time is one of the most common complaints about documentation changes.</p><p>That is why organizations should measure it.</p><p>In CareHub, the median daily note takes about <strong>five minutes</strong> of actual working time. Half of all notes take about <strong>three to nine minutes</strong>. This measures the time someone is actively working on the note. It does not count time when the screen is open but no one is working.</p><p>That difference matters.</p><p>If a note truly took 30 or 40 minutes every shift, leaders should review the process.</p><p>But five to nine minutes to document a shift in a regulated service setting is not an unreasonable expectation.</p><p>The alternative may include incomplete records, missing documentation, late corrections, staff reminders, compliance problems, repayment risk, licensing citations, or an inability to show that required services occurred.</p><h3>Ask the Better Question</h3><p>Many leaders measure the wrong thing.</p><p>The better question is usually not how long one note takes. It is <strong>how many notes one person writes during a shift.</strong></p><p>Across organizations, the median Direct Support Professional completes <strong>one note per shift</strong>. The average is between two and three notes. At the ninetieth percentile, the number is six.</p><p>For most staff, the total documentation time for an entire shift is about five minutes. This is important when someone says they do not have time. In many cases, five minutes is the honest answer.</p><p>But not always.</p><p>One organization we work with has about <strong>five notes per staff member per shift</strong>. On its busiest days, the number reaches 13. The time for each note was normal, but the total workload was not.</p><p>Five minutes per note may be reasonable. Twenty-five minutes of documentation every shift is a real workload question that deserves a real answer.</p><p>Those staff members were not necessarily resisting accountability. They were handling five times the usual documentation volume, and no one had measured it.</p><p><strong>This is the difference leaders need to understand.</strong> If you measure only time per note, a high-volume program may look like a program full of complaints. If you measure notes per person per shift, you can quickly see whether you have a change problem or a workload problem.</p><p>One problem requires leadership.</p><p>The other requires fixing the schedule or caseload.</p><h3>The Real Cost Is Not the Five Minutes</h3><p>Sometimes leaders spend more time tracking down one missing note than the employee would have needed to complete it correctly.</p><p>The data supports this.</p><p>About <strong>two-thirds of notes are completed on the same day</strong> as the shift they describe. That is the healthy majority and shows what a working system can look like.</p><p>But about <strong>one in seven notes is completed more than a week</strong> after the shift it describes.</p><p>Consider what that means.</p><p>A note written eight or 20 days later is based on memory. It may be less accurate and harder to defend during a record review. Nearly every late note also creates extra work: a supervisor notices it, someone sends a reminder, a manager follows up, compliance staff track it, and a conversation may be needed.</p><p>Multiply that by dozens of staff and hundreds of shifts.</p><p>That is where poor documentation habits become expensive. The cost is not the five minutes needed to write the note. The cost is the extra work created when the note is late or missing.</p><h3>AI Will Make Some Staff Uncomfortable</h3><p>AI creates another type of resistance.</p><p>Some employees are interested right away.</p><p>Others are skeptical.</p><p>Some worry they are doing something wrong by using AI assistance. Others believe the technology makes their jobs more complicated. Some simply do not want to change a routine they have followed for years.</p><p>The adoption numbers show this clearly. When AI assistance is available in CareHub, it is used on about <strong>three percent of notes</strong>. About 97 out of every 100 notes are still written completely by hand, even when the tool is available.</p><p>Leaders sometimes assume staff will use AI too much and need to be stopped.</p><p>In practice, the opposite is more common.</p><p>Most staff do not use it.</p><p>The answer is not to tell staff that AI will do their jobs for them.</p><p>It should not.</p><p>Instead, explain what the tool is designed to do.</p><p>A responsible AI documentation tool can help staff organize information, find missing details, improve clarity, and create more complete notes.</p><p>But the DSP is still responsible for the content of the note.</p><p>The employee must still document what actually happened.</p><p>AI cannot invent a community outing that did not happen.</p><p>It cannot say an outcome was addressed when it was not.</p><p>It cannot replace professional judgment.</p><p>It should never be used to create false documentation.</p><p>The goal is not fake documentation.</p><p>The goal is <strong>better documentation with helpful technology</strong>.</p><h3>Stop Negotiating About Every Complaint</h3><p>This may be one of the hardest lessons for provider leaders.</p><p>When a new system is introduced, every complaint cannot become a vote on whether the organization should keep using it.</p><p>Listen to feedback.</p><p>Absolutely.</p><p>Fix real problems.</p><p>Definitely.</p><p>Provide more training when needed.</p><p>Of course.</p><p>But once leaders decide that a system is appropriate, works properly, meets compliance needs, and is necessary, employees need to understand that using it is part of the job.</p><p>Otherwise, organizations teach staff an unhealthy lesson:</p><p><strong>If I complain long enough, leadership will remove the expectation.</strong></p><p>That creates a serious problem.</p><p>The more important the compliance requirement, the less negotiable it should be.</p><h3>Make the Expectation Clear</h3><p>Implementation is easier when employees know exactly what is expected.</p><p>Do not rely on:</p><p>“We showed everyone how to use it.”</p><p>Instead, define the standard.</p><p>For example:</p><p>Documentation must be completed in CareHub.</p><p>Documentation must be completed within the organization’s required timeframe.</p><p>Required sections cannot be intentionally skipped.</p><p>AI assistance may be used according to company policy, but staff must check the accuracy of everything they submit.</p><p>Technical problems must be reported quickly. They should not be used later as an explanation for missing documentation.</p><p>Staff who need more training should ask for help.</p><p>Repeated failure to complete required documentation will be treated as a performance issue, not a personal preference about technology.</p><p>That last point matters.</p><p>At some point, refusing to use the required documentation system is no longer a training issue.</p><p>It becomes an accountability issue.</p><h3>Train, Support, Then Hold People Accountable</h3><p>A fair implementation process should have three stages.</p><h3>1. Train</h3><p>Show employees how to use the system.</p><p>Do not simply give them a login.</p><p>Demonstrate the full documentation process from beginning to end.</p><p>Show them what a good note looks like.</p><p>Show them common mistakes.</p><p>Let them practice.</p><h3>2. Support</h3><p>Give staff reasonable time to adjust.</p><p>Create simple instructions.</p><p>Identify someone who can answer questions.</p><p>Fix real software problems.</p><p>Offer more training to employees who need it.</p><p>Listen carefully enough to tell the difference between a valid concern and resistance to change.</p><p>Measure before reaching a conclusion. One afternoon of real data about time per note and notes per person per shift can tell you more than a month of debate.</p><h3>3. Hold People Accountable</h3><p>This is the stage organizations sometimes avoid.</p><p>Once an employee has been trained, has access to the system, has received support, and understands the expectation, continued failure to comply must have consequences.</p><p>Otherwise, the organization is allowing each employee to decide which requirements they will follow.</p><p>Licensed providers cannot operate that way.</p><h3>Protect Your Leadership Team’s Time</h3><p>Documentation problems tend to move upward.</p><p>A DSP does not complete a note.</p><p>A supervisor notices.</p><p>A manager sends a reminder.</p><p>The employee says the app did not work.</p><p>Someone investigates.</p><p>Another reminder is sent.</p><p>The note is still missing.</p><p>Compliance becomes involved.</p><p>Administration becomes involved.</p><p>Now four people have spent time on a task that would have taken the original employee about <strong>five minutes</strong>.</p><p>This is how leadership teams become overwhelmed.</p><p>The answer is not more chasing.</p><p>The answer is a better accountability system.</p><p>Set clear deadlines.</p><p>Use automatic reminders when possible.</p><p>Monitor completion.</p><p>Track patterns.</p><p>Address repeated problems through supervision and performance management.</p><p>Do not create a workplace where managers must repeatedly beg employees to complete basic job duties.</p><p>That is not sustainable.</p><h3>Resistance Does Not Always Mean the Change Is Wrong</h3><p>One of the biggest mistakes leaders make during a technology rollout is assuming that resistance proves they made the wrong decision.</p><p>Sometimes resistance points to problems that need to be fixed.</p><p>But sometimes resistance simply means the organization is changing.</p><p>Change is uncomfortable.</p><p>A documentation system that creates clearer expectations, improves visibility, finds missing information, and increases accountability will feel different from a system that allowed those problems to stay hidden.</p><p>That friction may actually show progress.</p><p>The goal is not to make every employee love the software.</p><p>The goal is to give good employees the tools they need to succeed while making sure the organization meets its responsibilities to the people it supports.</p><h3>Compliance Has to Win</h3><p>Human-services providers have a serious responsibility.</p><p>We are trusted with people’s health, safety, dignity, rights, services, and quality of life.</p><p>The care individuals receive will always matter most.</p><p>But providers must also be able to show that the care happened and that services were delivered according to the individual’s plan and applicable rules.</p><p>Compliance cannot be treated as optional because someone prefers the old system.</p><p>Technology will keep changing.</p><p>AI will keep changing.</p><p>Documentation systems will keep changing.</p><p>The organizations that succeed will not always be the ones with employees who never complain about change.</p><p>They will be the ones whose leaders listen to valid concerns, provide good training, fix real problems, set clear expectations, and then confidently say:</p><p><strong>This is the standard now.</strong></p><p>At the end of the day, a licensed provider cannot build its compliance program around what is most convenient for staff.</p><p>It must build that program around what protects the people receiving services and keeps the organization able to serve them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=baa20984699e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Quiet Cybersecurity Problem in DD Waiver Software]]></title>
            <link>https://medium.com/@dsplifetm/the-quiet-cybersecurity-problem-in-dd-waiver-software-2c6420788b4b?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c6420788b4b</guid>
            <category><![CDATA[dd-waiver]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[ehr]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Tue, 19 May 2026 20:47:25 GMT</pubDate>
            <atom:updated>2026-05-19T20:51:17.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-Yurde1IxBx-OP0lpN4Mg.png" /></figure><h3>A developer’s take on what most EHRs settle for, and what the next generation should look like</h3><p>I am the developer behind CareHub, the compliance and operations platform built for DBHDS-licensed residential providers. I spend my days writing code that handles some of the most sensitive data that exists, the documentation we keep on the individuals our providers support. Diagnoses, behavior plans, medication histories, guardianship records, incident reports, and in many cases photo or video documentation.</p><p>When I look at the broader software landscape in the intellectual and developmental disabilities space, I see something that does not get talked about enough. A lot of the platforms our field has relied on for the last fifteen to twenty years were architected before modern web security practices were standard. Providers and surveyors are used to how those platforms behave, but the underlying technical foundation has not aged well, and most people running residential programs have never been told what questions to ask their software vendors.</p><p>This is a piece on what I have learned building CareHub, and what I think every IDD provider should understand about the technology that holds their data.</p><h3>The legacy stack problem</h3><p>If you pull back the cover on most established EHR platforms in the IDD space, you will often find a few things that engineers like me consider warning signs. Custom-built authentication systems instead of modern identity infrastructure. Server-rendered pages with limited session protections. Database designs where access control lives in application code rather than at the database layer. Audit logs that exist but are not comprehensive. Encryption at rest that depends on whatever the hosting provider happens to offer.</p><p>None of this is necessarily a violation of HIPAA on its face. HIPAA is a floor, not a ceiling, and a platform can technically meet the Security Rule while still being meaningfully less secure than what is achievable with modern tooling. That gap between the legal minimum and what is technically possible is where the risk actually lives.</p><p>The HIPAA Journal’s year-end reporting on 2025 makes the point in numbers. Roughly 57 million individuals were affected by healthcare data breaches last year, and 76 percent of OCR enforcement actions cited risk analysis failures. Network servers and email accounts remain the most commonly breached locations for protected health information. The DD waiver world sits inside that risk profile, even if the breaches that make headlines tend to come from hospitals and large health systems.</p><h3>What an attack actually looks like</h3><p>Let me walk through a realistic scenario, because abstract architecture talk is hard to weigh against everyday operations.</p><p>A direct support professional at a residential provider opens an email that looks like it came from their employer. The email says their timesheet needs to be reviewed before payroll cuts off, and there is a link. The link leads to a page that looks identical to the platform’s login screen, and the staff member enters their username and password. This is a textbook credential phishing attack, and it happens to healthcare workers constantly. The breach reports from 2025 are filled with these stories.</p><p>Here is how that attack plays out against a typical legacy platform. The attacker now has working credentials. They log in from somewhere far away, often a different state or country. The platform has no geolocation context tied to the login, so nothing flags. Session controls are loose, so the attacker has hours or days of access. The user account they compromised may have visibility into multiple homes because access is granted at the application level and the developers chose to be generous with reads to keep performance fast. The audit log records that the user logged in, but does not record that an unusual access pattern occurred, because the platform was not designed to look for one. By the time anyone notices, the attacker has pulled bulk records on dozens of individuals.</p><p>Now consider the same attack against a platform built with the security model I am going to describe in the next section. The phished credentials hit a multifactor authentication challenge at login, and the attacker does not have the staff member’s phone. Even if they did get past that, the geolocation check on clock-in fails because they are not physically at the home the staff member is assigned to. Even if they had somehow defeated both of those layers, the database itself only returns records for the homes and individuals that staff member is currently assigned to, and only for the shifts they are actively working. The audit log captures the unusual access pattern and is structured to make detection straightforward.</p><p>No platform is unbreachable. The right way to think about security is in layers, where each layer catches what the previous one missed. Legacy platforms in our space tend to have one or two layers. Modern platforms can have five or six without making the system harder to use.</p><h3>What HIPAA actually asks for, and where most platforms stop</h3><p>The HIPAA Security Rule is broken into administrative, physical, and technical safeguards. The technical safeguards are where software vendors carry the most direct responsibility. Access controls, audit controls, integrity controls, transmission security, and authentication.</p><p>Most established platforms in our space can check each of those boxes in a literal sense. They have user accounts with passwords. They log certain actions. They use HTTPS. They have backup procedures. From a contract and BAA perspective, that is usually enough.</p><p>What is missing in many cases is the deeper layer. Are user accounts truly individualized, or are direct support professionals sharing a login on a shared device because the platform makes it inconvenient to do otherwise? Are audit logs comprehensive enough to reconstruct exactly who saw what record at what time, or do they only capture certain events? Is multifactor authentication actually enforced, or is it an option that nobody turns on? Is data access governed at the database level, or is it just a matter of which buttons the application chooses to show?</p><h3>The risk analysis requirement everyone underestimates</h3><p>OCR’s enforcement priorities deserve special attention here. In 2025, 76 percent of OCR enforcement actions cited risk analysis failures. That number is staggering, and it reflects a specific compliance gap that almost every provider I talk to is exposed to without realizing it.</p><p>The HIPAA Security Rule, specifically 45 CFR 164.308, requires a covered entity to conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information. The word “thorough” is doing a lot of work in that regulation. OCR has been clear that a generic template downloaded from a compliance vendor does not meet the requirement. A real risk analysis identifies where ePHI lives, what threats exist, how likely those threats are, what the impact would be, and what controls are in place to mitigate them. It is updated when systems change, and it is documented.</p><p>Most providers I have seen have a risk analysis document that someone filled out three years ago and has not touched since. The document references systems that have been replaced, lists threats in generic terms, and contains no real assessment of probability or impact. If OCR opens an investigation after a breach, that document is the first thing they ask for, and a generic version is what triggers the penalty even if the breach itself was relatively contained.</p><p>Here is where the architecture connects to the compliance pressure. You cannot conduct a real risk analysis on a platform whose vendor cannot tell you exactly where data is stored, how it is encrypted, who can access it, and how access is logged. Vague answers from a vendor become vague entries in your risk analysis, and vague entries are what OCR is penalizing. The technical clarity of a modern platform is not just a security benefit. It is a compliance defense.</p><h3>How we built CareHub differently</h3><p>I am going to be specific about the security architecture behind CareHub, because the architecture is the whole point. I am not going to name the specific vendors or open-source components we use under the hood, because the principles are what matter, not the brand names. What I will tell you is the design decisions, what each one prevents, and how providers benefit from them.</p><h3>Access control enforced at the data layer</h3><p>In most older platforms, the rules about who can see what record live inside the application code. The application decides, based on the logged-in user, which queries to run and which records to return. The database itself will hand over anything the application asks for. This is the standard approach for legacy software, and it has a major weakness. If there is a bug anywhere in the application, or if a developer takes a shortcut for performance reasons, the wrong records can leak.</p><p>CareHub uses a different model. Access rules are enforced at the data layer itself, one level below the application. When any request comes in to read a record, the data layer independently checks whether that user is permitted to see that specific record, based on their current shift assignments, their role, and their relationship to the home and individual. The application cannot override this. A bug in the application cannot bypass it. Even an administrator running ad hoc queries is bound by the same rules.</p><p>The attack class this stops is called broken access control. It sits at the top of the OWASP Top 10 for a reason. Broken access control is what lets a healthcare worker in one department pull records from a completely unrelated department because the application forgot to check. Putting the rules at the data layer means the rules keep working even when the application makes mistakes.</p><h3>Modern authentication, individualized for every user</h3><p>Every direct support professional, supervisor, and administrator has their own account. Multifactor authentication is a real option that we can require for administrative accounts, not a setting hidden three menus deep. Sessions are managed with current best practices, including short-lived access tokens that can be revoked instantly if a device is lost or a staff member leaves.</p><p>The practical implication is that we can give every staff member their own credentials without that being a hassle, which removes the incentive providers have historically had to share logins on a tablet at the home. Shared logins are an audit trail killer. When everyone is logging in as “house phone,” it becomes impossible to reconstruct what actually happened on a shift.</p><h3>Geolocation verification for clock-in</h3><p>Shift documentation is tied to where the staff member actually is when they clock in. This is partly an EVV compliance feature, but it has a security benefit that I think gets undervalued. Credential sharing becomes much harder when the system is also checking whether you are physically at the home you claim to be working at. An attacker with phished credentials who tries to log in from another state hits a wall the moment they try to start a shift.</p><h3>Audit trails built into the data model</h3><p>Every meaningful action in CareHub writes an audit record. Who, what, when, from where, and what the value was before and after. This is one of the conventions I enforce on every feature I build. It is not optional and it is not bolted on, which I will come back to in a moment.</p><h3>Encryption at rest and in transit by default</h3><p>Data in transit is protected with current transport security standards. Data at rest is encrypted using managed key infrastructure, which means that even someone with raw access to the underlying storage cannot read the records. This is not a feature we had to remember to turn on. It is the default state of the infrastructure we build on.</p><h3>Independently audited infrastructure underneath</h3><p>The hosting and data infrastructure we build on top of maintain SOC 2 Type II compliance, which is independently audited every year against a defined set of controls covering security, availability, processing integrity, confidentiality, and privacy. We inherit those controls and build on top of them rather than trying to reproduce them from scratch. When a surveyor or a managed care organization asks about our compliance posture, the answer chains down to infrastructure that is held to standards comparable to what modern financial services run on.</p><h3>Audit trails deserve their own conversation</h3><p>I want to come back to audit trails because they are the single most underappreciated security control in our field. When DBHDS opens an investigation, when a family raises a concern, when a managed care organization questions a billing record, the audit log is what answers the question. And most platforms in our space have audit logs that look fine on a vendor demo and fall apart the first time you actually need them.</p><p>A useful audit log captures the user identity, the exact timestamp, the action type, the target record identifier, the value before the change, the value after the change, the IP address of the request, and the session identifier. It captures reads as well as writes, because reading a record can be just as significant as changing one. It is append-only, which means past entries cannot be modified or deleted by anyone, including administrators. It is retained for at least six years to align with HIPAA documentation expectations, and longer for records related to specific incidents.</p><p>The test for whether your current platform meets this bar is simple. Ask the vendor to produce a complete list of every action taken against one specific individual’s record over a defined time period, including every staff member who viewed the record without changing it. If the vendor cannot do this within a few hours, or if the answer involves caveats about which actions are captured and which are not, you have an audit trail problem.</p><p>The medication administration record is where this matters most. A surveyor asking who logged a medication, when, and what the original entry was before it was edited should get a complete answer in seconds. If the answer requires the vendor to dig into raw logs, or if before-and-after values are not captured, the platform is not giving you what HIPAA and DBHDS expect.</p><h3>What this means for a provider</h3><p>Most agency directors will not care about the specific technical mechanisms behind any of this. That is the right call. Those are my problems. What providers should care about is what this architecture lets them do in practice.</p><p>They can give every staff member their own account without that being a hassle, because the system is fast and the login flow is modern. They can trust that if a supervisor needs to reconstruct what happened on a shift two months ago, the audit trail will actually have the answer. They can answer DBHDS surveyor questions about access controls without crossing their fingers. They can let their guardians and case managers know, honestly, that the system holding their loved one’s records is built on infrastructure that is held to the same standards as the platforms running modern financial services.</p><p>It also changes the conversation with state agencies. When DBHDS or DMAS or a managed care organization asks about technical safeguards, the answer is no longer a vague reference to the vendor’s compliance posture. It is a specific description of where data lives, how it is encrypted, who can access it, and how every action is logged. That clarity feeds directly back into the risk analysis that OCR will eventually ask to see.</p><h3>Questions worth asking your current vendor</h3><p>If you are running on an established EHR and you are wondering how it stacks up, here is what I would ask, framed in plain language.</p><p>Where is our data stored, and is it encrypted at rest. Not whether it is backed up. Whether the actual storage is encrypted such that someone with raw access to the hardware could not read it.</p><p>How is access to records controlled, and where is that control enforced. Application-only access control is much weaker than access control enforced at the data layer.</p><p>What does the audit log actually capture, and can we get a complete export of every action taken against our records for any time period. Include reads, not just writes.</p><p>Is multifactor authentication available, is it enforced for administrative accounts, and what does the recovery flow look like if a staff member loses access.</p><p>What is the vendor’s underlying infrastructure, and what compliance certifications do their providers hold. SOC 2 Type II from a hosting provider is meaningful. A vague reference to HIPAA compliance is not.</p><p>If you were the subject of an OCR investigation tomorrow, what specific information could the vendor produce to support our risk analysis. The right answer here is concrete documents, not reassurance.</p><p>If you get clean, specific answers to those questions, you are in good hands. If the answers feel like marketing language, that is worth paying attention to.</p><h3>The point</h3><p>I am not writing this to argue that every provider needs to switch platforms tomorrow. Switching a documentation system is a serious project, and there are providers running on older platforms who are doing excellent work for the people they support. The point is that the technology under our field has quietly moved on, and a new generation of platforms can offer real, measurable improvements in how the data of vulnerable people is protected.</p><p>The next time you are evaluating a software vendor, ask about the architecture. The right vendor will be happy to answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c6420788b4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virginia’s Care Workforce Crisis Is Not a Staffing Problem. It’s a Math Problem.]]></title>
            <link>https://medium.com/@dsplifetm/virginias-care-workforce-crisis-is-not-a-staffing-problem-it-s-a-math-problem-bdecd4bb3bff?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdecd4bb3bff</guid>
            <category><![CDATA[dsp]]></category>
            <category><![CDATA[medicaid]]></category>
            <category><![CDATA[virginia]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Sun, 03 May 2026 14:32:55 GMT</pubDate>
            <atom:updated>2026-05-03T14:43:16.173Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxX5LHhS0vPf9lZ0GanBdw.png" /></figure><p>Virginia’s personal care providers are sounding the alarm, and every DSP, group home operator, sponsored residential provider, in-home support team, and DD provider in the Commonwealth knows exactly what they are talking about.</p><p>This is not an isolated staffing issue. It is not a temporary hiring problem. It is not something that can be solved with a few more job postings, a pizza party, or another reminder that the work is meaningful.</p><p>The work is meaningful. That has never been the question.</p><p>The question is whether Virginia’s care system is funded in a way that allows meaningful work to be sustainable.</p><p>Since 2019, Virginia’s minimum wage has climbed 76%.</p><p>Medicaid reimbursement has increased roughly 40%.</p><p>That gap does not close itself.</p><p>It closes when caregivers leave for jobs that pay more and demand less. It closes when one staff member is left trying to cover what should have been two-person support. It closes when a family member misses work because services fell through. It closes when a provider who wants to pay better simply cannot make the numbers work.</p><p>It also closes in quieter ways that do not always make headlines.</p><p>It closes when an experienced DSP decides they cannot keep doing this work for the pay being offered. It closes when a provider delays opening another bed because there is no realistic staffing plan. It closes when a supervisor spends the weekend covering shifts instead of reviewing documentation, coaching staff, or improving quality. It closes when families who were promised community-based supports are left wondering why the services exist on paper but not in real life.</p><p>And it is not just personal care.</p><p>The setting may be different, but the math is the same.</p><p>Personal care agencies, DD residential providers, sponsored residential homes, group homes, in-home support providers, day support providers, and community-based teams are all working inside the same pressure cooker. Labor costs rise. Insurance costs rise. Compliance expectations rise. Training requirements rise. Documentation requirements rise. Technology costs rise. Administrative demands rise.</p><p>But reimbursement does not rise at the same pace.</p><p>That is the problem.</p><p>Wages have to go up. They should go up. Direct support professionals and caregivers are doing essential, human, physically demanding, emotionally demanding work. They help people bathe, eat, take medication, communicate, regulate, attend appointments, stay safe, and live with dignity in their homes and communities.</p><p>They are not simply “helpers.”</p><p>They are the people who notice when someone is not acting like themselves. They are the people who recognize early signs of illness, distress, abuse, neglect, depression, aspiration risk, falls, medication side effects, behavioral changes, and environmental dangers. They are the people who help someone get through a difficult morning, a medical appointment, a family visit, a community outing, or a crisis that no one else sees.</p><p>They support people through ordinary moments and life-changing moments.</p><p>They protect dignity in private spaces.</p><p>They make community living possible.</p><p>But providers cannot pay workers with values statements.</p><p>They pay workers with reimbursement.</p><p>And when reimbursement lags behind labor costs, the system forces providers into an impossible position. They are expected to recruit, retain, train, supervise, document, comply, report, audit, and improve quality while absorbing every new cost increase along the way.</p><p>That is not a business model.</p><p>That is survival mode.</p><p>For DD residential providers, it shows up as open shifts.</p><p>For sponsored residential providers, it shows up as placement instability.</p><p>For in-home support teams, it shows up as families waiting, worrying, and rearranging their lives.</p><p>For supervisors and QIDPs, it shows up as late nights, weekend paperwork, constant follow-up, and the never-ending fear that one missed note or one incomplete form could become a licensing issue.</p><p>For DSPs, it shows up as burnout.</p><p>For individuals with disabilities, it shows up as disruption in the supports they depend on.</p><p>And for providers, it shows up in the constant tension between doing what is right and surviving financially.</p><p>That tension is exhausting.</p><p>Most providers did not enter this field because they wanted to run a high-margin business. They entered because they care about people. They understand the responsibility of supporting someone’s life, health, safety, choices, rights, routines, and relationships. They know that behind every authorization, every service plan, and every billing code is a real person who needs reliable support.</p><p>But caring deeply does not erase payroll.</p><p>It does not erase overtime.</p><p>It does not erase regulatory risk.</p><p>It does not erase the cost of background checks, onboarding, annual training, insurance, vehicles, rent, utilities, food, supplies, software, administrative staff, and quality oversight.</p><p>Virginia cannot build a stable care system on unstable math.</p><p>We cannot keep asking providers to meet higher expectations with reimbursement rates that do not reflect the true cost of care. We cannot talk about community integration, choice, dignity, and person-centered supports while the workforce holding that system together is stretched past the breaking point.</p><p>The people still showing up deserve more than praise.</p><p>They deserve rates that support living wages.</p><p>They deserve systems that reduce administrative burden.</p><p>They deserve tools that make compliance easier instead of heavier.</p><p>They deserve a funding structure that recognizes care work as skilled work, necessary work, and life-sustaining work.</p><p>They also deserve honesty.</p><p>If Virginia wants people with disabilities to live safely in their communities, then the providers delivering those supports have to be financially viable. If Virginia wants families to have real options, then those options have to be staffed. If Virginia wants providers to meet licensing standards, documentation standards, incident reporting requirements, person-centered planning expectations, and quality improvement obligations, then the system has to acknowledge the cost of doing all of that well.</p><p>Compliance is not free.</p><p>Quality is not free.</p><p>Staff retention is not free.</p><p>A stable care system is not free.</p><p>At DSPlife, we built CareHub because we saw one piece of this crisis up close. Providers are already fighting rising labor costs, staffing shortages, regulatory pressure, and Medicaid rate limitations. They should not also be losing money, time, and staff morale to compliance paperwork that can be made simpler.</p><p>CareHub will not fix Medicaid reimbursement.</p><p>It will not solve the wage gap by itself.</p><p>It will not magically create DSPs in a market where every provider is competing for the same limited workforce.</p><p>But it can help providers stop bleeding time on documentation. It can help teams stay audit-ready. It can help reduce the daily administrative drag that pulls leaders, QIDPs, and DSPs away from the actual work of supporting people.</p><p>That matters because administrative burden has a cost too.</p><p>Every hour a supervisor spends chasing missing notes is an hour not spent coaching staff. Every hour spent hunting for forms is an hour not spent improving services. Every confusing documentation process increases the chance that good staff feel overwhelmed, frustrated, or unsupported. Every audit scramble adds stress to a system that is already carrying too much.</p><p>In a healthier system, technology should not be another burden.</p><p>It should give time back.</p><p>It should make documentation clearer.</p><p>It should help providers see what is missing before it becomes a problem.</p><p>It should support the people doing the work, not punish them with more clicks, more confusion, and more disconnected processes.</p><p>Because in this environment, every saved hour matters.</p><p>Every retained DSP matters.</p><p>Every clean audit matters.</p><p>Every provider who stays open matters.</p><p>Every family that keeps reliable support matters.</p><p>Every individual who avoids disruption matters.</p><p>Virginia’s personal care providers are right to sound the alarm. DD providers should be part of that conversation too. The workforce crisis is not isolated to one service line. It is a system-wide warning sign.</p><p>The warning is clear: the people delivering care cannot keep absorbing the difference between what services cost and what the system reimburses.</p><p>At some point, the gap becomes too wide.</p><p>At some point, good providers leave the field.</p><p>At some point, families lose options.</p><p>At some point, individuals with disabilities lose stability.</p><p>And when that happens, the cost does not disappear. It simply moves somewhere else. It moves to families. It moves to hospitals. It moves to crisis systems. It moves to emergency placements. It moves to people who deserved consistent support long before the system reached a breaking point.</p><p>The question is not whether caregivers deserve better pay.</p><p>They do.</p><p>The question is not whether providers should be accountable.</p><p>They should.</p><p>The question is whether Virginia is willing to fund the care system it says it values.</p><p>Because we cannot keep praising caregivers while underfunding their work.</p><p>We cannot keep demanding quality while ignoring the cost of quality.</p><p>We cannot keep saying community-based care matters while making it harder for community-based providers to survive.</p><p>And until that answer changes, providers will keep doing what they have always done: showing up, stretching thin, solving impossible problems, and carrying the weight of a system that cannot afford to lose them.</p><h3>Connect With DSPlife</h3><p>If you enjoyed this story, follow along for more plain-language breakdowns of systems that impact people with disabilities.</p><p>For super fun stickers and helpful downloads, visit the Etsy shop: <a href="https://www.etsy.com/shop/DSPlifeShop">https://www.etsy.com/shop/DSPlifeShop</a>. Check this one out!: <a href="https://dsplifeshop.etsy.com/listing/4327747933">https://dsplifeshop.etsy.com/listing/4327747933</a></p><p>Facebook page: <a href="https://www.facebook.com/profile.php?id=61584711986267">https://www.facebook.com/profile.php?id=61584711986267</a></p><p>Websites: <a href="http://www.mydsplife.com/">www.mydsplife.com</a> | <a href="http://www.carehub.mydsplife.com/">www.carehub.mydsplife.com</a> | traininghub.mydsplife.com</p><p>Subscribe so you do not miss future posts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdecd4bb3bff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People Who Grow Too Fast Will Ultimately Crash]]></title>
            <link>https://medium.com/women-write/people-who-grow-too-fast-will-ultimately-crash-65bb210c9b40?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/65bb210c9b40</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[business-growth]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 10:05:14 GMT</pubDate>
            <atom:updated>2026-02-10T10:05:14.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*DT3LOk9t2KkjpJLPpXlDAA@2x.jpeg" /></figure><p>Bad business people rarely look like villains. They do not wear masks, and they do not announce their shortcuts. Most of the time, they look successful. They build fast, scale loudly, and broadcast growth and wins, while the rules quietly become optional behind the scenes. Taxes are delayed, W-2 forms go out late or not at all, compliance becomes a suggestion, and staff are treated like expenses instead of people. Somehow, they keep winning, at least for a while.</p><p>Legitimate businesses operate in a completely different reality. They track everything, meet deadlines, follow labor laws, document accurately, and invest in the unglamorous infrastructure that keeps a company safe. They pay for accounting, legal support, training, audits, and systems because they understand that responsibility has a cost. They move slower not because they are inefficient, but because they are building something that can survive.</p><p>The unfair advantage of cutting corners is real. When payroll taxes are skipped or filings are delayed, there is more cash in the short term. When regulations are ignored, expansion happens faster. When workers are underpaid, misclassified, or pushed beyond reasonable limits, margins look impressive on paper. The unethical operator can look like a brilliant entrepreneur, even though they are often borrowing from consequences that simply have not arrived yet.</p><p>Gatekeeping makes the imbalance worse. The same people cutting corners often control access by hoarding contracts, blocking opportunities, and keeping newcomers confused. Fair competition threatens shortcuts, so complexity becomes a weapon. The public sees the winners and assumes they earned it cleanly, without seeing what was sacrificed to get there.</p><p>Rapid growth feeds that illusion. People who grow too fast rarely realize they are building on sand. Revenue spikes, new hires pour in, locations multiply, and social media fills with milestones. It feels like momentum, but momentum without structure is simply speed toward a wall. When growth happens faster than systems can support it, cracks form immediately. Payroll becomes rushed, hiring gets sloppy, training is shortened or skipped, compliance turns reactive instead of intentional, and documentation becomes an afterthought. At first, nothing breaks in a dramatic way. Small mistakes get patched, deadlines are pushed, and corners are cut with the promise that it will be fixed later. Because money is still coming in, it can look like everything is working.</p><p>Fast growth magnifies everything. A minor process flaw becomes a major financial leak, a single bad hire becomes a pattern repeated across multiple teams, and one missed requirement can become an investigation that consumes leadership attention for months. What was manageable at a small scale becomes chaos when multiplied. Sloppy foundations do not reveal themselves when conditions are easy. They reveal themselves under pressure, and rapid growth creates constant pressure.</p><p>Another quiet difference between fragile companies and durable ones is how leadership thinks about risk. Some CEOs keep risk on the back burner of their minds, vaguely aware it exists but unwilling to engage with it until something major forces their hand. They operate reactively, responding only after a crisis happens, a complaint escalates, a regulator intervenes, or a key employee walks out. By the time they act, the damage is already done, and every response feels urgent, expensive, and destabilizing.</p><p>Reactive leadership creates a false sense of efficiency in calm periods, but it leaves the organization exposed. Problems are allowed to grow unnoticed, warning signs are dismissed as isolated issues, and near misses go undocumented. When something finally breaks, the response is rushed and emotional, driven by fear instead of clarity, and focused on damage control rather than root causes.</p><p>Prepared leaders think differently. They understand that risk is not a future problem but a constant condition of doing business. Instead of avoiding it, they measure it, track it, and plan for it. They ask where the pressure points are, what would happen if a key system failed, what staff are quietly compensating for behind the scenes, and which issues could escalate if ignored. This kind of awareness does not slow a company down. It stabilizes it.</p><p>The businesses that scale responsibly spend time doing unglamorous work because they understand that boring systems are what keep a company alive. They build payroll processes that do not depend on one person’s memory, create clear policies, train leaders instead of hoping people figure it out, track compliance as a routine practice rather than a panic response, and audit what is happening so problems are corrected while they are still small. None of this looks exciting, and none of it makes for flashy posts, but it prevents disasters that would otherwise be inevitable.</p><p>Fast growing companies often skip that phase because it feels like slowing down. They ask why they should pause when revenue is climbing, why they should invest in structure when things seem fine, and why they should hire operations, HR, or compliance support when sales are booming. What they do not realize is that growth without infrastructure is borrowing stability from the future. Eventually, the debt comes due.</p><p>When it does, the symptoms are predictable. Employees burn out because the workload expands faster than training, support, and staffing. Errors pile up because processes were never designed to handle volume. Cash flow becomes unpredictable because the business is running on constant urgency instead of reliable planning. Reputation starts slipping as clients feel inconsistency and staff turnover becomes visible. Regulators notice patterns, vendors lose patience, and small complaints accumulate until someone with authority decides to look closer.</p><p>The crash rarely arrives in one dramatic moment. It arrives in layers that are easy to dismiss at first, like a lawsuit that feels inconvenient, an audit that feels unfair, a mass resignation that feels unexpected, or a funding problem that seems temporary. Those layers stack until the business that once looked unstoppable can no longer hold itself up.</p><p>And the people who have been carrying the company are rarely the ones who stay for the collapse.</p><p>The strongest staff eventually do the math. They realize they are doing the work of multiple roles while being paid for one, and they recognize that the stress they have accepted is not matched by loyalty in return. They watch leadership celebrate growth while ignoring workload, training gaps, and compensation that does not reflect responsibility. They get tired of being the fixer, the stabilizer, and the person who always makes it work.</p><p>At first, they try to communicate. They ask for support, clarity, better staffing, fair pay, or at least a realistic plan. When those requests are met with excuses or vague promises, they stop asking. When high performers stop asking, they are already halfway out the door. They leave for something better, and better takes many forms. Sometimes it is another company that respects their time and pays them what they are worth. Sometimes it is their own business, built from the lessons they learned while watching someone else grow too fast without taking care of the people doing the work. Either way, the outcome is the same. The company loses the very people who made the growth possible.</p><p>That is when the unraveling accelerates. The work does not disappear when good staff leave. It transfers to whoever remains, creating another wave of burnout and turnover. Culture shifts from pride to survival, then from survival to resentment, and finally to disengagement. Clients feel it. Families notice it. Mistakes increase. Oversight increases. The organization becomes reactive at the exact moment it needs stability.</p><p>People ultimately want peace and satisfaction in their work. They want to feel competent, supported, and fairly compensated. They want to go home without carrying unresolved chaos in their bodies. They want to believe that effort leads to growth, not just for company revenue, but for their own lives. When a workplace cannot offer that, the best people will not stay to be depleted by it.</p><p>In the short term, ethical businesses can look like they are being punished. They absorb higher costs, move slower, and watch louder operators surge ahead while calling shortcuts a strategy. From the outside, it can seem like doing things the right way is a disadvantage.</p><p>So yes, nice guys may finish last, especially in the beginning when speed and spectacle are rewarded more than stability.</p><p>But they are usually still standing when the noise fades.</p><p>They last because they build with care instead of urgency, with systems instead of shortcuts, and with people instead of expendable labor. They understand that treating staff well is not generosity, but strategy, and that paying people what they are worth is an investment in continuity. They choose sustainability over ego and integrity over optics, even when no one is applauding.</p><p>While flashier companies cycle through burnout, turnover, audits, and public reckoning, ethical businesses quietly compound trust. Their employees stay because their work has boundaries and meaning. Their clients stay because consistency feels safer than chaos. Their leaders sleep because they are not waiting for the other shoe to drop.</p><p>Nice guys may not win the race to the spotlight, but they win the race that actually matters. In business, longevity is the real measure of success, and the leaders who prioritize preparedness, fairness, and respect tend to be the ones still standing long after fast growth has burned everything else out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65bb210c9b40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/women-write/people-who-grow-too-fast-will-ultimately-crash-65bb210c9b40">People Who Grow Too Fast Will Ultimately Crash</a> was originally published in <a href="https://medium.com/women-write">Women Write</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Development: Building Software That Can Actually Keep Up With Reality]]></title>
            <link>https://medium.com/women-write/agile-development-building-software-that-can-actually-keep-up-with-reality-c56cc6bf0938?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c56cc6bf0938</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[carehub]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 07:22:36 GMT</pubDate>
            <atom:updated>2026-02-06T07:22:36.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aECBaw2gZpuq9VBQpiLgog.png" /></figure><p>Software rarely fails because developers don’t know how to code. It fails because reality changes faster than the plan, and most plans are built as if the world will politely stand still.</p><p>Requirements evolve, users behave differently than expected, regulations shift, budgets tighten, and timelines move. The moment a product meets the real world, it starts collecting information the original spec could not predict, so agile development exists for a simple reason: it is cheaper to learn continuously than to discover late that you built the wrong thing.</p><p>Agile is not a framework, a buzzword, or a calendar full of meetings. At its core, it is a disciplined way of working that prioritizes learning quickly, delivering value early, and responding intelligently to change, while still holding teams accountable for quality and outcomes.</p><h3>The Problem Agile Was Designed to Solve</h3><p>Traditional “waterfall” development assumes you can define every requirement upfront, build everything in sequence, and deliver a finished product at the end. That model can work when the problem is stable and well understood, such as rebuilding a system you already run, or implementing requirements that are fixed by law and unlikely to move.</p><p>In most software, though, stability is the exception. A long planning phase creates the feeling of certainty, but it often produces the wrong kind of certainty, because teams become confident in documentation instead of evidence. Stakeholders approve pages of requirements they have not experienced in practice, and by the time a detailed specification is written, approved, staffed, and built, it is frequently outdated.</p><p>Agile development emerged as a response to this mismatch between rigid planning and dynamic environments. It accepts that software is a learning process, where you are not only building features but also discovering what users need, what they actually do, and what constraints the system must survive.</p><p>The Agile Manifesto, published in 2001, emphasized four priorities that reshaped how teams approach work. It values individuals and interactions over rigid processes and tools, prioritizes working software over excessive documentation, emphasizes collaboration with customers rather than strict contract negotiation, and supports responding to change instead of blindly following a fixed plan. These principles do not reject planning or documentation; they reject the idea that plans should be followed when evidence clearly suggests a better path.</p><p>That last point matters more than most people realize. A plan is useful until it stops being useful, and agile treats the plan as a tool, not a promise.</p><h3>What Agile Development Actually Looks Like</h3><p>Agile development breaks work into small, manageable increments that can be built, tested, and evaluated quickly. The point is not simply speed; it is reducing the size of each commitment so the team can get feedback, course correct, and avoid the compounding cost of being wrong.</p><p>Instead of delivering everything at once, teams deliver in short cycles, often called iterations or sprints. Each cycle produces something usable, even if it is not yet complete, because usable means it can be evaluated by real people in a real context. Sometimes it is polished, sometimes it is rough, but it is concrete enough to reveal what is working and what is not.</p><p>Agile work typically starts with a clear outcome rather than a long feature list. Teams ask what problem they are solving and how they will know it is solved, then build the smallest practical version that allows learning, because learning is what shapes the next cycle.</p><p>This approach helps teams validate assumptions early, detect problems before they become expensive, incorporate user feedback continuously, and adjust priorities based on real world data. Over time, agile shifts success metrics away from whether a plan was followed and toward whether the right problem was solved.</p><p>In practical terms, it means teams spend less time debating hypothetical requirements and more time observing what happens when a real user tries to complete a real task. It also means quality is not postponed until the end, because testing, review, and improvement happen throughout the work.</p><h3>Why Agile Is Often Misunderstood</h3><p>Agile is frequently mistaken for a lack of structure, when in reality it requires more discipline, not less. When a team cannot hide behind a long timeline, they have to be clear about what they are delivering, why they are delivering it, and what tradeoffs they are making.</p><p>Because plans are flexible, teams must communicate clearly, document decisions intentionally, and hold themselves accountable for outcomes rather than intentions. Good agile teams are not improvising; they are running a tight feedback system.</p><p>Agile is also surrounded by myths. Some people assume it means there are no deadlines, no documentation, constant chaos, or that developers make all decisions. None of that is accurate. Agile can include deadlines, especially when tied to compliance, funding, or contractual commitments, and it can include documentation when systems affect safety, billing, audits, or regulated operations. What agile removes is the illusion that certainty can be manufactured upfront, and it replaces that illusion with short term clarity and continuous reassessment.</p><p>Structure still exists, but it adapts as understanding increases. Teams plan, deliver, measure, and adjust, then repeat, and the cycle itself becomes the structure.</p><h3>Agile Beyond Software</h3><p>While agile originated in software development, its principles apply far beyond code, because uncertainty is not unique to programming. Any environment that involves humans, workflow, policy, and real time decision making will encounter change, and the cost of mismatch can be high.</p><p>Healthcare systems, education platforms, service delivery organizations, and compliance driven operations increasingly rely on agile methods to reduce risk and improve outcomes. If software does not align with how staff work, documentation quality drops. If the tool is rigid, people create workarounds. If updates come slowly, the organization absorbs pain until the next major release, which is often too late to help.</p><p>Agile thinking helps because it encourages building with the field, not for the field. It treats frontline feedback as operational data, and it invites iteration before bad habits harden into permanent processes.</p><h3>When Agile Works Best</h3><p>Agile excels when requirements are unclear or evolving, when users need to interact with solutions early, when feedback loops exist, and when risk must be managed incrementally. It is especially effective in environments where compliance, usability, and real world constraints matter more than theoretical perfection.</p><p>Agile is less effective when work is entirely predictable, repeatable, and fixed in scope, although even those teams often borrow agile practices to reduce delivery risk, such as breaking work into smaller milestones and validating progress more frequently. The most important factor is not the label; it is whether the approach fits the reality of the work.</p><h3>Agile Is a Responsibility, Not a Shortcut</h3><p>Agile development is not a way to move faster by cutting corners. It is a commitment to transparency, learning, and accountability, and it asks teams to tell the truth early instead of discovering the truth late.</p><p>Teams working in agile environments cannot hide behind long timelines or vague deliverables. Progress is visible, decisions are revisited, assumptions are tested in the open, and that visibility can feel uncomfortable when stakeholders are used to certainty. That discomfort is also a strength, because it forces clarity.</p><p>Agile requires mature prioritization. You cannot do everything at once, so you choose what matters most, deliver it, evaluate it, and decide what comes next. Done well, this protects users and teams alike by preventing endless building without validation, reducing rework, and creating a steady rhythm of improvement.</p><h3>The Real Value of Agile</h3><p>Agile does not promise perfection. It promises adaptability, and in a world where change is constant and certainty is rare, the ability to respond thoughtfully is more valuable than the ability to predict accurately.</p><p>That principle is exactly why DSPlife CareHub was built, and you can find it at carehub.mydsplife.com.</p><p>CareHub applies agile development principles to environments where flexibility is rarely built into the software. In compliance driven and human services settings, tools are often rigid, slow to update, and disconnected from how work actually happens, which creates a familiar pattern: staff end up doing the same work twice, once to support people and once to satisfy the system, while supervisors spend more time chasing documentation than strengthening supports.</p><p>CareHub was designed to evolve alongside providers rather than force providers to adapt to outdated systems. The goal is practical, focusing on documentation that is easier to complete correctly, workflows that match the daily realities of residential and community based services, and compliance that can be achieved through good systems rather than constant reminders.</p><p>Instead of locking users into fixed workflows, CareHub grows through continuous feedback from the people using it daily. Features are built, tested, refined, and expanded based on real operational needs, not assumptions made years earlier, and updates are incremental and intentional so improvements land without disrupting compliance or daily operations.</p><p>That difference is not cosmetic. In regulated environments, change has to be controlled, because you cannot break a workflow staff rely on to document supports, and you cannot introduce a new process that creates errors in service delivery notes or incident reporting. An agile approach, applied responsibly, improves systems in small, testable steps so stability is preserved while capability expands.</p><p>This is what resilience looks like in practice. Regulations change, documentation expectations shift, provider needs evolve, new staff need onboarding, and existing staff need tools that reduce mistakes. Rather than requiring a complete overhaul, CareHub adjusts through controlled iterations that reduce risk and support continuity, creating software that works today and keeps working as reality changes tomorrow.</p><h3>The Problem Agile Was Designed to Solve</h3><p>Traditional “waterfall” development assumes you can define every requirement upfront, build everything in sequence, and deliver a finished product at the end. That model can work when the problem is stable and well understood, such as rebuilding the same system you already run or implementing requirements that are fixed by law and unlikely to move.</p><p>Most software problems are not like that.</p><p>A long planning phase creates the feeling of certainty, but it often produces the wrong kind of certainty. Teams become confident in documentation instead of evidence. Stakeholders approve pages of requirements that they have not experienced in practice. Meanwhile, the environment keeps shifting. By the time a detailed specification is written, approved, staffed, and built, it is frequently already outdated.</p><p>Agile development emerged as a response to this mismatch between rigid planning and dynamic environments. It accepts that software is a learning process. You are not only building features. You are discovering what users need, what they actually do, and what constraints the system must survive.</p><p>The Agile Manifesto, published in 2001, emphasized four priorities that reshaped how teams approach work. It values individuals and interactions over rigid processes and tools. It prioritizes working software over excessive documentation. It emphasizes collaboration with customers rather than strict contract negotiation. It supports responding to change instead of blindly following a fixed plan. These principles do not reject planning or documentation. They reject the idea that plans should be followed when evidence clearly suggests a better path.</p><p>That last part matters. A plan is useful until it is not. Agile treats the plan as a tool, not a promise.</p><h3>What Agile Development Actually Looks Like</h3><p>Agile development breaks work into small, manageable increments that can be built, tested, and evaluated quickly. It reduces the size of each commitment so the team can get feedback and course correct before the cost of being wrong becomes painful.</p><p>Instead of delivering everything at once, teams deliver in short cycles, often called iterations or sprints. Each cycle produces something usable, even if it is not yet complete. Usable does not always mean polished. It means the work can be evaluated by real people in a real context, even if it still needs refinement.</p><p>Agile work typically starts with a clear outcome rather than a long feature list. The team asks what problem they are solving and how they will know it is solved. Then they build the smallest practical version that allows learning. That learning shapes the next cycle.</p><p>This approach allows teams to validate assumptions early, detect problems before they become expensive, incorporate user feedback continuously, and adjust priorities based on real world data. Agile shifts success metrics from whether a plan was followed to whether the right problem was solved.</p><p>In practical terms, it means teams spend less time debating hypothetical requirements and more time observing what happens when a real user tries to complete a real task. It means quality is not postponed until the end. Testing, review, and improvement happen throughout the work.</p><h3>Why Agile Is Often Misunderstood</h3><p>Agile is frequently mistaken for a lack of structure. In reality, it requires more discipline, not less. When a team cannot hide behind a long timeline, they have to be clear about what they are delivering, why they are delivering it, and what tradeoffs they are making.</p><p>Because plans are flexible, teams must communicate clearly, document decisions intentionally, and hold themselves accountable for outcomes rather than intentions. Good agile teams are not improvising. They are running a tight feedback system.</p><p>Agile is often misunderstood. Some believe it means there are no deadlines, no documentation, constant chaos, or that developers make all decisions. None of these are accurate. Agile can include deadlines, especially when tied to compliance, funding, or contractual commitments. Agile can include documentation, especially when systems affect safety, billing, audits, or regulated operations. Agile does not remove responsibility. It makes responsibility visible.</p><p>What agile does replace is rigid long term commitments with short term clarity and continuous reassessment. Structure still exists, but it adapts as understanding increases. Teams plan, deliver, measure, and adjust, then repeat. The cycle is the structure.</p><h3>Agile Beyond Software</h3><p>While agile originated in software development, its principles apply far beyond code because uncertainty is not unique to programming. Any environment that involves humans, workflow, policy, and real time decision making will encounter change.</p><p>Healthcare systems, education platforms, service delivery organizations, and compliance driven operations increasingly rely on agile methods to reduce risk and improve outcomes. In these settings, the cost of mismatch is real. If software does not align with how staff work, documentation quality drops. If the tool is rigid, people create workarounds. If updates come slowly, the organization absorbs the pain until the next major release.</p><p>Agile thinking helps because it encourages building with the field, not for the field. It treats frontline feedback as operational data. It invites iteration before bad habits harden into permanent processes.</p><p>The core idea remains the same. Learn fast. Deliver value. Adjust before mistakes become systemic.</p><h3>When Agile Works Best</h3><p>Agile excels when requirements are unclear or evolving, when users need to interact with solutions early, when feedback loops exist, and when risk must be managed incrementally. It is especially effective in environments where compliance, usability, and real world constraints matter more than theoretical perfection.</p><p>Agile is less effective when work is entirely predictable, repeatable, and fixed in scope. In those cases, a more linear approach may be sufficient. Even then, many teams still borrow agile practices to reduce delivery risk, such as breaking work into smaller milestones and validating progress more frequently.</p><p>The most important factor is not the label. It is whether the approach fits the reality of the work. If change is likely, agile reduces the cost of change. If change is unlikely, agile can still improve transparency and delivery, but it may not be necessary to apply every ritual.</p><h3>Agile Is a Responsibility, Not a Shortcut</h3><p>Agile development is not a way to move faster by cutting corners. It is a commitment to transparency, learning, and accountability. It asks teams to tell the truth early instead of discovering the truth late.</p><p>Teams working in agile environments cannot hide behind long timelines or vague deliverables. Progress is visible. Decisions are revisited. Assumptions are tested in the open. That visibility can feel uncomfortable, especially when stakeholders are used to certainty, but it is also what makes agile powerful.</p><p>Agile also requires mature prioritization. You cannot do everything at once. You choose what matters most, deliver it, and evaluate it. Done well, this protects both users and teams. It prevents endless building without validation. It reduces rework. It creates a steady rhythm of improvement.</p><h3>The Real Value of Agile</h3><p>Agile does not promise perfection. It promises adaptability.</p><p>In a world where change is constant and certainty is rare, the ability to respond thoughtfully is more valuable than the ability to predict accurately. Agile development works not because it eliminates planning, but because it respects reality.</p><p>That principle is exactly why DSPlife CareHub was built. You can find it at carehub.mydsplife.com. DSPlife CareHub is available at carehub.mydsplife.com and reflects an intentional decision to apply agile development in environments where change, compliance, and daily operational reality intersect.</p><p>CareHub applies agile development principles to environments where flexibility is rarely built into the software. In compliance driven and human services settings, tools are often rigid, slow to update, and disconnected from how work actually happens. Staff end up doing the same work twice, once to support people and once to satisfy the system. Supervisors end up chasing documentation instead of strengthening supports. When that happens, software becomes a burden rather than a tool.</p><p>CareHub was designed to evolve alongside providers rather than force providers to adapt to outdated systems. The goal is practical. Make documentation easier to complete correctly. Make workflows match the daily realities of residential and community based services. Make compliance something that can be achieved through good systems instead of constant reminders.</p><p>Instead of locking users into fixed workflows, CareHub grows through continuous feedback from the people using it daily. Features are built, tested, refined, and expanded based on real operational needs, not assumptions made years earlier. Updates are incremental and intentional, allowing improvements without disrupting compliance or daily operations.</p><p>That difference is not cosmetic. In regulated environments, change has to be controlled. You cannot break a workflow that staff rely on to document supports. You cannot introduce a new process that creates errors in service delivery notes or incident reporting. An agile approach, applied responsibly, makes improvements in small, testable steps so the system remains stable while it gets better.</p><p>This is what resilience looks like in practice. Regulations change. Documentation expectations shift. Provider needs evolve. New staff need training. Existing staff need tools that reduce mistakes. Rather than requiring a complete system overhaul, CareHub adjusts in controlled iterations that reduce risk and support continuity.</p><p>Agile development, when applied responsibly, creates systems that stay useful over time. CareHub is an example of what happens when agile principles are paired with real world accountability. The result is not just software that works today, but software that can keep working as reality changes tomorrow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c56cc6bf0938" width="1" height="1" alt=""><hr><p><a href="https://medium.com/women-write/agile-development-building-software-that-can-actually-keep-up-with-reality-c56cc6bf0938">Agile Development: Building Software That Can Actually Keep Up With Reality</a> was originally published in <a href="https://medium.com/women-write">Women Write</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Didn’t Need RESEA. I Needed Virginia to Stop Wasting My Time.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">It&#x2019;s not real reemployment support. It&#x2019;s mandatory compliance, and Virginians are tired of it.</p><p class="medium-feed-link"><a href="https://medium.com/@dsplifetm/i-didnt-need-resea-i-needed-virginia-to-stop-wasting-my-time-124a2920595d?source=rss-59240668aabf------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@dsplifetm/i-didnt-need-resea-i-needed-virginia-to-stop-wasting-my-time-124a2920595d?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/124a2920595d</guid>
            <category><![CDATA[unemployment]]></category>
            <category><![CDATA[fired]]></category>
            <category><![CDATA[re-employment]]></category>
            <category><![CDATA[unemployment-insurance]]></category>
            <category><![CDATA[virginia]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 15:37:03 GMT</pubDate>
            <atom:updated>2026-01-28T15:37:03.865Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why We Built CareHub (and Why It Matters for Residential Providers)]]></title>
            <link>https://medium.com/women-write/why-we-built-carehub-and-why-it-matters-for-residential-providers-eb44a8ec9623?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb44a8ec9623</guid>
            <category><![CDATA[residential-service]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[group-home-software]]></category>
            <category><![CDATA[dsp-life]]></category>
            <category><![CDATA[daily-notes]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Sat, 17 Jan 2026 10:16:02 GMT</pubDate>
            <atom:updated>2026-01-17T10:16:02.872Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>A residential first documentation and EHR platform built to simplify daily notes, strengthen oversight, and keep providers compliance ready without the chaos.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*acY40Gzt_B2fndu7QbJ_9A.png" /></figure><p>A residential first documentation and EHR platform built to simplify daily notes, strengthen oversight, and keep providers compliance ready without the chaos.</p><p><strong>A residential first documentation platform built to simplify compliance, support DSPs, and protect providers.</strong></p><p>Residential and IDD services run on trust. Families trust providers with the most important thing they have, the safety and well being of someone they love. Providers trust their teams to show up, follow plans, and deliver supports with consistency and care. Teams trust that the work being done every day is captured accurately so the individual’s story is clear, consistent, and defensible.</p><p>That last part matters more than people realize.</p><p>Documentation is not just a task on a checklist. It is proof of care. It is the paper trail that protects the individual, the staff, and the provider. It is what connects one shift to the next, helps leaders spot patterns early, and gives support coordinators and families confidence that services are truly happening.</p><p>And yet, documentation has become one of the biggest stressors in residential services, and it should not be.</p><p>Too many providers are stuck using systems that were never designed around how residential homes actually function. The result is predictable. Staff struggle to complete documentation correctly during a real shift. Workflows take too many clicks and too much hunting. Missed notes show up late, after gaps have already become compliance risks. Incident follow up ends up scattered across forms, tasks, emails, and off system tracking. Supervisors spend too much time policing documentation instead of leading services.</p><p>CareHub exists because residential providers deserve something better.</p><p>CareHub is part of the DSPlife™ Technology Platform, the documentation and EHR platform built for residential providers. It is custom designed to simplify documentation, streamline compliance, and give providers the tools they actually need.</p><h3>The Problem: Legacy EHRs Weren’t Built for Residential</h3><p>Most EHR platforms used in residential and IDD services were built for clinical or multi service environments first, then adapted for homes. Residential programs were not the priority, and it shows.</p><p>When a system is designed for clinics, billing driven workflows, or multi department medical documentation, residential staff end up trying to force daily living supports into a framework that does not fit. That is when documentation becomes confusing, inconsistent, and stressful.</p><p>That is also when providers start relying on workarounds.</p><p>They build cheat sheets. They create unofficial templates. They train staff repeatedly, then retrain after turnover, then retrain again. They do end of month clean up. They chase missing notes. They print things “just in case.” They keep side spreadsheets because they do not trust that the system will show them what they need, when they need it.</p><p>It becomes a full time job just to manage the documentation system.</p><p>And none of this is because residential teams do not care.</p><p>It is because the tools were not designed for the work.</p><h3>Residential Documentation Is Not “Clinical Notes”</h3><p>Group homes and sponsored homes are not clinics. Residential services are routines, relationships, and real life supports delivered around the clock. Documentation should reflect that reality.</p><p>Residential work is messy in the best way. It is cooking dinner while teaching safety skills. It is supporting hygiene while respecting dignity and choice. It is helping someone get dressed for work while coaching independence and emotional regulation. It is noticing a subtle change in mood or sleep and documenting it before it becomes a crisis. It is de escalating behaviors, following a plan, and then capturing what actually happened in a way that makes sense to the next staff member and to leadership.</p><p>A residential note has to communicate real life. It has to be clear enough that a new DSP can step in and understand what happened. It has to be strong enough that leadership can defend the services. It has to be organized enough that, if someone asks a hard question later, the record answers it.</p><p>When a system feels like a maze, documentation becomes the thing that gets squeezed into the last ten minutes, pushed to “later,” or completed with minimal detail because the interface is exhausting.</p><p>That is not a staff problem. That is a design problem.</p><h3>The Solution: CareHub Is Residential First by Design</h3><p>CareHub is residential first, built to match how group homes actually operate.</p><p>That means it supports the rhythm of a home. It respects that staff are moving, assisting, redirecting, coaching, cleaning, cooking, transporting, administering meds, and responding to real time needs. The system needs to make documentation possible in that reality.</p><p>CareHub is built around how residential teams actually work:</p><p>Shift based documentation.</p><p>Routines and daily supports.</p><p>Handoff communication.</p><p>Real world compliance expectations.</p><p>It is simple, guided, and fast, so staff actually complete it.</p><p>CareHub is not trying to make residential providers act like clinics. It is doing the opposite. It is honoring residential work and giving it the right structure.</p><h3>Built to Prevent Compliance Gaps</h3><p>CareHub does not wait for you to “find problems later.” It helps you catch issues while you can still fix them.</p><p>That includes:</p><p>Missed notes.</p><p>Incomplete follow up.</p><p>Documentation that lacks required elements.</p><p>When expectations are visible and documentation is organized, teams can focus on what matters, delivering supports, maintaining safety, and building consistency. Compliance becomes a daily standard, not an emergency scramble.</p><p>This matters because gaps do not stay small. A few missed notes can turn into a pattern. A pattern can turn into questions. Questions can turn into corrective action. Providers should not be living in constant fear because their system makes it hard to keep up.</p><p>CareHub is designed so the system helps you see what needs attention, early, while it is still manageable.</p><h3>Built to Reduce Admin Burden</h3><p>With traditional EHRs, residential success often depends on constant configuration, rebuilding workflows, retraining staff, and cleanup.</p><p>CareHub reduces that overhead by making residential workflows the default, so providers can focus on services, not system management.</p><p>Instead of spending your time digging through screens, correcting avoidable mistakes, and cleaning up documentation after the fact, you get tools that support oversight and accountability without creating extra work.</p><p>That is the difference between a system that demands labor, and a system that gives time back.</p><h3>Person Centered Plans That Truly Align With WaMS</h3><p>One of the most critical gaps in residential documentation today is the disconnect between the Person Centered Plan and what lives in WaMS. Providers are often forced to duplicate information, translate language manually, or rebuild plans inside systems that do not truly align with waiver requirements.</p><p>CareHub is being built to solve that problem directly.</p><p>CareHub will allow providers to build a Person Centered Plan that is fully complementary to WaMS, not competing with it and not creating double work. The structure of the plan is designed to mirror waiver expectations so that goals, outcomes, supports, and services align cleanly with what is authorized and reflected in WaMS.</p><p>This means providers are not rewriting the same information in multiple places. Instead, the Person Centered Plan becomes a living document that connects directly to daily documentation, progress tracking, and service delivery.</p><p>Goals written in the plan connect to what staff are documenting daily. Supports outlined in the plan match what is authorized. Progress notes actually show movement toward outcomes instead of existing in isolation.</p><p>CareHub is designed so the plan supports WaMS, and WaMS supports the plan, without providers having to play translator between systems.</p><p>The result is less duplication, clearer oversight, and documentation that tells one consistent story from authorization to service delivery to outcomes.</p><p>This is not about replacing WaMS. It is about respecting it, aligning with it, and finally giving providers a tool that works alongside it instead of against it.</p><h3>Smart Feature: Daily Notes with Built In Rephrase</h3><p>One of the most practical features in CareHub is the smart rephrase option within Daily Notes.</p><p>Not every staff member writes the same way. Some struggle with punctuation, grammar, or person centered language. Some are incredible DSPs who support people beautifully, but writing has never been their strength. Providers still need notes that are clear, professional, and compliance ready.</p><p>CareHub’s built in rephrase helps staff submit stronger documentation automatically by improving:</p><p>Punctuation and readability.</p><p>Person centered language.</p><p>Professional, compliance ready wording.</p><p>It is not about making notes fancy. It is about making notes usable, defensible, and consistent.</p><p>And consistency is everything. When notes are consistent, leadership can review faster, trends are easier to spot, and audits stop feeling like an ambush.</p><h3>Pricing That Makes Sense: Stop Paying Per User</h3><p>Legacy EHRs often charge per user, which punishes you for hiring more staff.</p><p>Some systems charge up to $150 per user per month. With a typical group home staff of 8 to 12 people, that can become $1,200 to $1,800 per home, per month, before you even factor in turnover, onboarding, and the reality that residential staffing has to flex.</p><p>This pricing model creates a silent pressure to limit accounts, share logins, or restrict access, and none of that supports quality.</p><p>CareHub is priced per home, not per user.</p><p>That means unlimited users per home. Add as many staff as you need without watching your bill climb. It supports adequate staffing, simplifies budgeting, and keeps costs predictable.</p><p>Predictable costs make it easier for providers to plan, expand, and invest in quality without feeling punished for staffing appropriately.</p><h3>Everything You Need, Built for Residential Roles</h3><h3>Person Centered Plans That Align With WaMS</h3><p>CareHub is expanding beyond daily documentation. A major piece of residential compliance is the Person Centered Plan, and providers need a plan that is not only person centered on paper, but also structured in a way that supports real authorization workflows.</p><p>CareHub is being built so providers can create a Person Centered Plan that is fully complimentary to WaMS. The goal is simple. When you build the plan, it is organized to match what providers and support coordinators are already working with in WaMS, so services, goals, and documentation connect cleanly instead of living in separate worlds.</p><p>When the plan, the service details, and daily documentation are aligned, providers spend less time translating paperwork and more time actually delivering supports.</p><p>CareHub includes the tools residential teams actually depend on:</p><p>Daily Documentation, daily notes, incident reporting, and progress tracking in a clean, organized format.</p><p>Leadership Dashboards, see what needs attention at a glance without digging through paper or multiple systems.</p><p>Compliance Workflows, built in workflows aligned with regulatory expectations so you can stay audit ready.</p><p>Team Coordination, share updates, track tasks, and support smooth communication between shifts.</p><p>Mobile Friendly Access, staff can document from tablets, phones, or computers wherever they work.</p><p>Secure and HIPAA Compliant, protected data, role based access, and reliable uptime so documentation is safe and available.</p><p>It is designed for every role in residential services:</p><p>Direct Support Professionals documenting daily activities, incidents, and care notes quickly and easily.</p><p>Program Managers monitoring homes, reviewing documentation, tracking compliance, and managing staff responsibilities.</p><p>Provider Leadership accessing dashboards, reports, and oversight tools to ensure quality and compliance across locations.</p><p>When the system supports each role, providers stop relying on memory, sticky notes, and side conversations to keep the home running.</p><h3>Built by Providers, for Providers</h3><p>CareHub was not created to be flashy. It was created to be useful.</p><p>Unlike generic healthcare software, CareHub was designed from the ground up by people who understand residential services. Every feature addresses real challenges that group homes, sponsored residential, and supported living programs face daily.</p><p>CareHub keeps DBHDS, DMAS and Medicaid waiver expectations in mind from the start. Documentation workflows are structured to meet regulatory standards without creating extra work. Providers do not have to choose between “easy for staff” and “strong for oversight.” You can have both.</p><h3>The Bottom Line</h3><p>We are not trying to “integrate” into the existing residential documentation problem.</p><p>We are replacing it.</p><p>If you are using a legacy EHR that was not designed for residential services, or you are still operating on paper or spreadsheets, CareHub is the upgrade.</p><p>Better for staff.</p><p>Better for oversight.</p><p>Better for compliance.</p><p>Better for your budget.</p><p>CareHub is live at carehub.mydsplife.com.</p><p>If you have been waiting for a residential first way to document, organize, and protect your services, this is it.</p><p>And if you are ready to see what residential documentation looks like when the system is finally built for the job, explore CareHub and make the switch.</p><h3>Connect With DSPlife</h3><p>If you enjoyed this story, follow along for more plain-language breakdowns of systems that impact people with disabilities.</p><p>For super fun stickers and helpful downloads, visit the Etsy shop: <a href="https://www.etsy.com/shop/DSPlifeShop">https://www.etsy.com/shop/DSPlifeShop</a>. Check this one out!: <a href="https://dsplifeshop.etsy.com/listing/4327747933">https://dsplifeshop.etsy.com/listing/4327747933</a></p><p>Facebook page: <a href="https://www.facebook.com/profile.php?id=61584711986267">https://www.facebook.com/profile.php?id=61584711986267</a></p><p>Websites: <a href="http://www.mydsplife.com/">www.mydsplife.com</a>; www.carehub.mydsplife.com</p><p>Subscribe so you do not miss future posts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb44a8ec9623" width="1" height="1" alt=""><hr><p><a href="https://medium.com/women-write/why-we-built-carehub-and-why-it-matters-for-residential-providers-eb44a8ec9623">Why We Built CareHub (and Why It Matters for Residential Providers)</a> was originally published in <a href="https://medium.com/women-write">Women Write</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HB243 and Virginia’s “Corporate Welfare Tax”: a new way to bill employers for poverty]]></title>
            <link>https://medium.com/@dsplifetm/hb243-and-virginias-corporate-welfare-tax-a-new-way-to-bill-employers-for-poverty-7a40eaa4c4db?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a40eaa4c4db</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[benefits]]></category>
            <category><![CDATA[law]]></category>
            <category><![CDATA[virginia]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Wed, 14 Jan 2026 13:40:07 GMT</pubDate>
            <atom:updated>2026-01-14T13:40:07.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbWOGwqjmgbvp-yrVuG68A.png" /></figure><p>Last Wednesday morning, Gov. Glenn Youngkin walked into Richmond with what amounts to his closing argument: Virginia has landed record business investment, record job growth, and record revenue, so it’s time for another round of tax cuts. His message was simple: Virginians should keep more of what they earn.</p><p>Now zoom out and look at what’s also on the table this session.</p><p>HB243 would create a new “Corporate Welfare Tax” aimed at large employers, meaning companies averaging 500 or more employees. The idea is as blunt as the name: if a large employer has Virginia employees who rely on certain means-tested federal benefits, the state would tax the employer based on the value of those benefits.</p><p>That’s not a vibe. That’s the mechanism.</p><h3>What HB243 would do</h3><p>Under HB243, “qualified federal benefits” include programs like SNAP (food assistance), school breakfast and lunch program meals for an employee or their dependents, certain housing assistance payments, and Medicaid medical assistance expenditures for the employee or their dependents.</p><p>The bill imposes a tax on each large employer equal to 100% of those qualified benefits received by that employer’s Virginia-resident employees in a taxable year.</p><p>To make it work, HB243 sets up a matching system. Large employers would submit quarterly employment rosters, and the state would compare those rosters against identifying information connected to benefit use in order to calculate the bill.</p><p>The bill also adds a related rule: employers wouldn’t be allowed to ask an applicant whether they receive these benefits.</p><h3>What happens when the employee quits or gets fired?</h3><p>Under the structure of the bill, the tax is tied to benefits received during the year by people who are your employees at the time those benefits are attributed and matched. If someone separates, whether they quit or are terminated, they would eventually fall off your quarterly roster going forward. But the employer wouldn’t get refunded for the months the person worked there. The liability would still be based on whatever qualified benefits were matched to that employee during the time they were employed in the taxable year.</p><p>That detail matters because it shapes behavior. If a worker’s situation makes them more likely to use assistance, the employer has a financial reason to avoid hiring them, reduce their hours, or push the role into contracting, because the bill doesn’t distinguish between the reason for benefit use and the employer’s direct control over it.</p><h3>Why this feels like socialist ideology</h3><p>I’m not using “socialism” as a cheap insult. I’m using it the way everyday people use it, when government stops focusing on broad, predictable rules and starts engineering outcomes by moving costs around through taxes and centralized systems.</p><p>HB243 essentially says: if your workers need help paying for food, healthcare, housing, or school meals, the state will treat that need as your financial liability.</p><p>Instead of debating the real drivers, cost of living, housing supply, healthcare costs, workforce pipelines, local wage pressure, this approach tries to solve it by creating a new invoice. And once you turn benefit use into an employer tax bill, the incentives change fast.</p><h3>The unintended consequences aren’t hard to predict</h3><p>If a tax is tied to benefit use at 100%, businesses will adapt. Not because they’re evil, but because they have to.</p><p>That can look like cutting hours to keep workers from qualifying for certain supports, leaning harder on part-time, seasonal, or contract labor, outsourcing to avoid crossing thresholds, automation replacing entry-level roles, and hiring hesitancy in exactly the communities that need opportunity.</p><p>Beyond economics, there’s a trust problem. A state-run system that matches employer rosters to benefit use raises the obvious questions: Who has access to that data? How often is it wrong? How do you fix errors? What does it do to employee privacy and morale?</p><p>That ripple effect is also where the “this doesn’t affect me” argument starts to fall apart.</p><h3>How this would affect small businesses</h3><p>On paper, HB243 only applies to large employers. That detail is often used to reassure small businesses that they’re exempt.</p><p>In practice, small businesses don’t exist in a vacuum. Policies aimed at large employers almost always ripple outward.</p><p>First, competition for labor changes. If large employers face a new tax tied to benefit use, they will try to offset that cost. That can mean squeezing wages, benefits, or hours at the lower end, slowing hiring, or changing scheduling. Small businesses then get pulled into a tighter labor market, competing for the same workers without the same capital or pricing power.</p><p>Second, costs get passed down the supply chain. Small businesses rely on large employers as vendors, distributors, landlords, logistics providers, and service partners. When a large company absorbs a new cost, it rarely eats it quietly. Prices go up, contracts get renegotiated, and fees get passed along.</p><p>Third, growth becomes riskier. Small businesses hovering near expansion have to think twice about scaling if the state is building new systems that attach liability to employment relationships. Even if you are nowhere near 500 employees, you start planning for the direction of travel.</p><p>Finally, administrative creep is real. Once the state normalizes roster matching and benefit-based liability for employers, the question in the business community becomes less about whether it could expand and more about when.</p><h3>The quiet push toward 1099 labor</h3><p>One of the least talked-about side effects of bills like HB243 is how they encourage the shift from W-2 employees to 1099 independent contractors.</p><p>When a tax is tied to employees and their benefit usage, businesses look for ways to reduce exposure. Reclassifying roles, outsourcing work, or restructuring positions as independent contractor arrangements becomes more attractive, not because it’s better for workers, but because it limits liability.</p><p>That matters for small businesses in two ways. It changes the labor market you’re competing in, and it normalizes misclassification pressure. Even responsible employers who want stable W-2 jobs feel squeezed when competitors or upstream partners lean heavily on contractors to keep costs down.</p><p>More 1099s doesn’t mean fewer people need help. It usually means less stability, more income volatility, and higher reliance on the very safety-net programs this bill is trying to penalize.</p><p>That same squeeze shows up clearly in one sector most people forget to include in “business” conversations.</p><h3>How this affects Medicaid waiver services and residential service providers</h3><p>Medicaid waiver services and residential providers sit in a uniquely vulnerable position under HB243, even if many are not technically considered “large employers.” The reason is simple: the entire workforce that keeps waiver services running is low-margin, labor-intensive, and already operating inside a public funding structure that does not flex easily.</p><p>Direct support professionals, program managers, nurses, and residential staff are often paid through rates set or capped by the state. Providers cannot simply raise prices to offset new costs or market pressures. When policies increase the financial risk of employing W-2 staff, waiver providers do not have room to absorb it.</p><p>If large employers in other sectors begin cutting hours, shifting to part-time schedules, or pushing workers into 1099 arrangements to avoid benefit-linked liability, waiver providers will feel the impact immediately. The labor pool shrinks. Turnover increases. Competition for staff intensifies, even though waiver reimbursement rates stay the same.</p><p>There is also a direct Medicaid paradox built into HB243. Medicaid is one of the benefits used to calculate the tax. That means the state is effectively treating Medicaid utilization as a cost failure of the employer, even when wages are constrained by state-controlled reimbursement. In residential services, the state sets the rates, regulates staffing ratios, and then penalizes employers when staff rely on Medicaid. The system ends up taxing providers for conditions the system itself created.</p><p>Residential providers are also structurally exposed to the employee-separation problem. DSP turnover is already high. If a staff member works for a provider for part of the year and uses Medicaid or other qualifying benefits during that time, the employer exposure still exists for that period. For high-turnover industries like residential services, that creates ongoing liability tied to instability the provider cannot fully control.</p><p>The long-term risk is that policies like this accelerate consolidation. Smaller, mission-driven residential providers struggle to compete, while larger multi-state operators with legal teams and contracting models adapt more easily. That reduces local choice, weakens community-based services, and runs counter to the stated goals of HCBS and person-centered care.</p><p>In short, Medicaid waiver services are caught in the squeeze. The state wants stable staffing, continuity of care, and reduced reliance on crisis systems, but policies that make W-2 employment riskier without raising reimbursement rates push providers in the opposite direction.</p><p>With that backdrop, it’s easier to see why employers are also watching the labor-policy bills moving alongside HB243.</p><h3>Where Right to Work comes into this</h3><p>Virginia is a Right to Work state, which generally means workers cannot be required to join a union or pay union dues as a condition of employment. HB243 itself does not change Right to Work law, but it operates in the same labor-policy space and pushes pressure in a similar direction.</p><p>At the same time, lawmakers have introduced a separate bill this session that directly targets Right to Work protections by seeking to weaken or repeal them. That proposal would allow union membership or dues to become a condition of employment in certain circumstances, fundamentally changing how employment relationships work in Virginia.</p><p>Taken together, these two ideas point in the same direction. One increases the cost and risk of traditional W-2 employment through taxation tied to benefit usage. The other reduces employee choice by changing the rules around union participation. Different mechanisms, same outcome: more government involvement in the employer–employee relationship.</p><p>For employers, especially those operating across multiple states, this combination creates uncertainty. Right to Work has long been part of Virginia’s pitch as a predictable place to hire and grow. When that foundation starts to shift, businesses reassess expansion plans, location decisions, and long-term hiring strategies.</p><p>For workers, the impact is just as real. Policies that make full-time employment more expensive for employers while simultaneously reducing flexibility around representation don’t magically raise wages. They often result in fewer opportunities, slower hiring, and more pressure toward contract-based or short-term work.</p><p>That brings the conversation back to the bigger question: where is Virginia headed.</p><h3>The bigger context: a fully Democratic Richmond</h3><p>This bill is landing as Abigail Spanberger prepares to take office as governor and Democrats control both chambers of the General Assembly. That combination matters, because bills that used to be symbolic can suddenly become serious.</p><p>In that environment, business owners aren’t just looking at HB243 in isolation. They’re looking at a direction of travel. A new tax that re-prices W-2 employment, proposals that change core labor rules, and a broader affordability agenda built on mandates and cross-subsidies can add up to a tougher operating climate.</p><p>If you’re a small employer, the fear isn’t only that you get hit today. The fear is that the policy logic spreads. Thresholds drop. Reporting expands. “Large employer” rules become “most employers.” And Virginia’s reputation for being predictable gets replaced by a sense that everything is up for redesign.</p><p>This is where the contrast with Youngkin’s closing argument becomes unavoidable.</p><h3>This clashes directly with the “Virginia is open for business” pitch</h3><p>Youngkin is arguing Virginia’s best path forward is growth, investment, and tax relief, letting families and businesses keep more of what they earn.</p><p>HB243 argues the opposite: expand the state’s role by creating a new tax enforced through ongoing roster submissions and benefit matching to pressure employer behavior.</p><p>Those two visions don’t coexist comfortably.</p><h3>If Virginia wants higher wages, this isn’t the cleanest way to get there</h3><p>I understand the frustration behind HB243. Nobody wants a system where full-time work still leaves people needing help to cover basics.</p><p>But punishing employers through a benefit-based tax isn’t the same thing as fixing affordability.</p><p>If lawmakers want to move the needle in a way that doesn’t boomerang, they should be asking harder questions about housing supply and zoning barriers, childcare access, workforce development that actually fits employers’ needs, healthcare costs that keep climbing, and tax policy that attracts jobs instead of chasing them away.</p><p>Because a state can’t tax its way into prosperity if the policy scares off the very employers who build the job base.</p><h3>Bottom line</h3><p>HB243 may be framed as corporate accountability, but it operates like government trying to re-price the labor market through a centralized tax-and-match system.</p><p>That’s why so many people hear it and say this is socialist ideology.</p><p>And if Virginia’s goal is a stronger middle class, more jobs, and more opportunity, this bill points us in the opposite direction.</p><h3>Connect With DSPlife</h3><p>If you enjoyed this story, follow along for more plain-language breakdowns of systems that impact people with disabilities.</p><p>For super fun stickers and helpful downloads, visit the Etsy shop: <a href="https://www.etsy.com/shop/DSPlifeShop">https://www.etsy.com/shop/DSPlifeShop</a>. Check this one out!: <a href="https://dsplifeshop.etsy.com/listing/4327747933">https://dsplifeshop.etsy.com/listing/4327747933</a></p><p>Facebook page: <a href="https://www.facebook.com/profile.php?id=61584711986267">https://www.facebook.com/profile.php?id=61584711986267</a></p><p>Website: www.mydsplife.com</p><p>Subscribe so you do not miss future posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a40eaa4c4db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virginia’s Community Living Waiver Isn’t Just About Eligibility. It’s About Scarcity.]]></title>
            <link>https://medium.com/@dsplifetm/virginias-community-living-waiver-isn-t-just-about-eligibility-it-s-about-scarcity-49219d31c4f0?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/49219d31c4f0</guid>
            <category><![CDATA[waitlist]]></category>
            <category><![CDATA[medicaid]]></category>
            <category><![CDATA[waiver-services]]></category>
            <category><![CDATA[community-living]]></category>
            <category><![CDATA[intellectual-disabilities]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 01:42:31 GMT</pubDate>
            <atom:updated>2026-01-13T01:42:31.235Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3aDa7M0gxyOb-qRn9JcK4A.png" /></figure><p>One of the most misunderstood parts of Virginia’s developmental disability system is the Community Living (CL) Waiver. People hear the words Community Living and assume it works like a standard benefit. They think that if a person qualifies, services will start soon after.</p><p>Families often hear, “If your loved one qualifies, services will be there.” That sounds comforting, but it leaves out a key detail.</p><p>In Virginia, meeting the requirements for the CL Waiver does not automatically mean you will get it. Eligibility answers the question, “Could this person receive CL if it were available?” It does not answer, “When will CL actually start?”</p><h4>The truth: CL Waiver slots are limited</h4><p>Virginia does not have unlimited CL Waiver slots. The state funds a set number of slots each year through the budget. When those slots are already taken, other eligible people have to wait, sometimes for years, even if their situation is serious.</p><p>This is where many families get stuck. A person can qualify, have clear documentation of their needs, and truly need residential or 24/7 support, but still not get the CL Waiver until a slot opens up.</p><p>Eligibility is the requirement. A slot is the opening. Without the opening, services cannot start.</p><h4>What the numbers look like this year</h4><p>For the current fiscal year, Virginia authorized a limited expansion of the Community Living Waiver. State budget documents and DBHDS slot allocation materials show that 172 new CL Waiver slots were funded statewide for this year. These are not 172 openings sitting empty at once. They are phased in and distributed across Community Services Boards over the course of the fiscal year.</p><p>In the prior fiscal year, FY 2025, Virginia funded and assigned approximately 150 Community Living Waiver slots statewide. As with other years, those slots were distributed across CSBs and assigned based on priority criteria rather than evenly across the waiting list.</p><p>To put these numbers in context, Virginia has thousands of people on the IDD Waiver Waiting List. That means only a small fraction of people waiting will receive a new CL slot in a given year, even when the state does add funding. Most people will remain waiting unless they meet Priority One or emergency criteria, or a slot becomes available because someone exits the waiver.</p><p>This is why families may hear that “slots were added this year” and still see no movement in their own situation. Slot growth happens in small increments compared to the size of the waiting list, and the slots are assigned based on priority rules.</p><h4>What a waiver slot actually is</h4><p>A waiver slot is more than just approval for services. It is a promise of funding. It means Virginia is committing state and federal Medicaid dollars to support one person, usually at a high level of intensity.</p><p>The total number of CL slots is decided through the state budget. Providers cannot create slots. Support Coordinators cannot guarantee one. Families cannot request a slot on demand. Even if a provider has capacity and wants to help, the provider still needs the slot to be active and authorized before services can begin.</p><p>When all slots are filled, the system pauses even if the need is still there. That pause is not personal. It is structural.</p><h4>Why the state can cap it at all</h4><p>The CL Waiver is a Medicaid waiver. That word matters because waivers work differently than some other Medicaid benefits.</p><p>Some programs act like an entitlement. If you qualify, you get the benefit. Waivers are not built that way. A waiver is an agreement where the federal government allows a state to run a program with special rules. One of those rules is that the state can set a maximum number of people it will serve.</p><p>Virginia can tell the federal government, “We will serve this many people under the CL Waiver.” Once that number is approved, Virginia cannot go above it unless it gets more authority and more funding. Without those changes, the state has to manage access through a waiting list.</p><p>That is why families can do everything right and still be told to wait. It is not because the need is not real. It is because the program is built to match the budget.</p><h4>Every CL slot is a long term financial promise</h4><p>The CL Waiver is a major support package. For many people, it includes 24/7 residential services, staff across all shifts, medical and behavioral supports, transportation, daily supervision, and ongoing oversight. It often also includes planning and coordination requirements that take time for both families and providers.</p><p>So when Virginia funds a CL slot, it is not saying it can help for a short time. It is making a long term commitment that can last years or even decades.</p><p>That is why states are careful about adding slots. It is not a one time cost. It is an ongoing obligation.</p><h4>The General Assembly controls growth, not need</h4><p>The number of CL slots only increases when funding is added through the state budget. That usually means the Governor proposes it, the General Assembly approves it, and the final budget includes it.</p><p>Need alone does not automatically create more slots.</p><p>Virginia can have a growing waiting list, a shortage of residential options, and areas with few providers, and still add only a limited number of slots because the decision is financial and political, not just clinical.</p><h4>The waiting list is statewide and priority based</h4><p>When there is no CL slot available, people are placed on Virginia’s IDD Waiver Waiting List. Local Community Services Boards help with screening and paperwork, but the waiting list is statewide.</p><p>Virginia does not give out CL slots based only on how long someone has been waiting.</p><p>Instead, slots are offered based on priority categories. These can include risk of homelessness, caregiver death or inability to continue care, abuse or neglect, and serious medical or behavioral risks.</p><p>This is not because everyone else is fine. It is because when a program is capped, the system has to focus first on the most urgent situations.</p><h4>Highest need does not mean guaranteed</h4><p>The CL Waiver is meant for people with the most intensive support needs, including 24/7 supervision and residential services. But even that does not override the cap.</p><p>Many people assume that if someone clearly needs residential placement, the system will find a way. Families often make plans based on that assumption, only to learn that a slot is still required.</p><p>In reality, the system can only offer what has already been funded.</p><p>Emergency slots exist, but they are limited and have strict rules. They are not available for every family in crisis.</p><h4>Why this matters for families and providers</h4><p>For families, misunderstanding how the CL Waiver works can lead to false hope, delayed planning, and decisions made in a crisis. It can also lead to burnout, because families may be providing round the clock support for long periods with limited relief.</p><p>For providers, it can create confusion about admissions and capacity. A provider might have an open bed, staff, and licensing, but still cannot admit someone without a state assigned waiver slot.</p><p>The main barrier is not provider willingness. It is the state’s control of slots.</p><h4>A practical timeline from waitlist to services</h4><p>People often ask, “What happens next?” The process can feel like a black box, so it helps to understand the usual stages. Timeframes vary by situation and locality, but the sequence is fairly consistent. The key is to understand that the process has two big phases. The waiting list phase, and the slot activation phase.</p><p>Step 1. First contact and screening with the local CSB</p><p>Most families start with their local Community Services Board. The CSB collects basic information, reviews records, and determines whether the person appears likely to meet the developmental disability criteria to be placed on the IDD Waiver Waiting List. Families may be asked to provide medical records, school records, psychological evaluations, or prior service documentation.</p><p>Step 2. Getting officially added to the statewide waiting list</p><p>Once the screening requirements are met, the person is added to the statewide waiting list. From this point forward, the family should keep documentation updated because changes in living situation, caregiver stability, and safety risk can affect priority.</p><p>Step 3. Priority category and ongoing updates</p><p>Virginia uses priority categories, so the CSB will document whether the person meets urgent criteria. If circumstances change, such as caregiver health declines, housing becomes unstable, safety risks increase, or there is abuse or neglect, the family should report those changes to the CSB so the record reflects the current level of risk.</p><p>Step 4. VIDES assessment to confirm developmental disability eligibility</p><p>Before the SIS assessment occurs, Virginia requires completion of the Virginia Individual Developmental Eligibility Survey, commonly called VIDES. This assessment is used to confirm that the person meets the state’s definition of a developmental disability for waiver purposes.</p><p>VIDES looks at areas such as age of onset, functional limitations, and how the disability affects major life activities. It is not a service planning tool. It is an eligibility gate.</p><p>Step 5. SIS assessment to measure support intensity</p><p>Once VIDES eligibility is established, the Supports Intensity Scale, often called the SIS, may be completed or updated. The SIS looks at the person’s support needs across daily life areas. It does not measure intelligence. It measures the level of support required to be safe, healthy, and successful.</p><p>Step 6. Tier or level assignment that connects to funding</p><p>After the SIS and related reviews are completed, the person may receive a level or tier that reflects support intensity. This matters because waiver funding and provider rates are tied to support intensity. A higher tier generally signals a higher level of daily support need.</p><p>Step 7. Slot offer and waiver enrollment steps</p><p>When a slot becomes available and the person is selected based on priority rules, the family is notified. This is when the finish line starts to come into view. Paperwork moves faster here because the system is preparing to activate funding.</p><p>Step 8. Choosing a licensed provider and starting intake</p><p>Once the slot is offered, the family can work with a licensed provider for the services they need. For residential support, this is the point where the provider’s intake begins. The provider gathers records, completes health and safety reviews, develops risk supports, and plans staffing.</p><p>Step 9. Service planning and the official start of services</p><p>Before services begin, the team finalizes the person centered plan and service plan details. The provider confirms service authorizations and start dates. When the start date is active and the provider is authorized to bill, services can begin. That is the true finish line.</p><h4>What families and guardians can do while waiting</h4><p>Being on the waiting list can feel like nothing is happening. In reality, the system is driven by documentation and priority rules, so the most effective thing a family can do is stay connected to the right people and keep the record current.</p><p>Who to contact first</p><p>The main point of contact is the local Community Services Board. The CSB is where waiting list status is maintained, changes are documented, and urgent need criteria are reviewed. If a family has a Support Coordinator or case manager, that person can also help communicate changes, gather records, and keep assessments current.</p><p>What to do while you are waiting</p><p>Keep the file updated. If anything changes, report it to the CSB. Changes that matter include caregiver illness or inability to continue care, housing instability, safety incidents, emergency room visits, inpatient stays, worsening behavior risks, or any concern related to abuse, neglect, or exploitation.</p><p>Ask clearly about urgent need and emergency options. If a situation becomes unsafe or unstable, ask the CSB what criteria apply for Priority One status and for emergency consideration.</p><p>What Virginia generally means by Priority One</p><p>Priority One is meant for people who are expected to need waiver services within one year and who meet specific urgent criteria. Priority One can include situations such as immediate jeopardy to health and safety because an unpaid primary caregiver has a serious long term physical or psychiatric condition that limits their ability to provide care and there are no other unpaid caregivers available. It can also include immediate risk to health or safety due to behaviors that cannot be managed at home even with arranged supports, or medical and physical care needs that cannot be managed at home even with arranged supports. Priority One may also apply when a person is living in an institutional setting and has a viable discharge plan, or when a young adult is leaving school services and transitioning to adult life within the specified age rules.</p><p>If any of these situations might fit, ask the CSB what documentation is needed and whether a Critical Needs Summary is required so the case can be considered properly when slots are reviewed.</p><p>Use the waiting time to prepare for the slot offer stage. Slot offers often come with a fast timeline. Families can reduce delays by keeping records organized, keeping contact information updated, and writing a simple support needs summary that explains supervision needs, medical supports, behavior supports, communication needs, and what keeps the person safe.</p><p>Talk to licensed providers early, even if the slot is not yet offered. A provider cannot start services without a slot, but a family can still learn the provider’s intake requirements, typical timelines, and what information the provider will need.</p><p>The goal during the waiting list phase is not to wait quietly. The goal is to keep the record accurate, make sure risk is documented, and be ready when the system finally offers a slot.</p><h4>The takeaway</h4><p>Virginia’s Community Living Waiver is based on eligibility, but it is also financially capped. It is priority based rather than time based, and it depends on decisions made in the state budget.</p><p>Knowing this does not make the system easier. But it does make it clearer, and clarity helps families plan, document changes, and understand what to push for at each stage.</p><p>Clarity matters when families are making life changing plans, and when providers are trying to build services in communities that truly need them.</p><p>The CL Waiver is not only about care. It is also about how many people Virginia has decided it can fund at one time.</p><p>And that number is limited.</p><h3>Connect With DSPlife</h3><p>If you enjoyed this story, follow along for more plain-language breakdowns of systems that impact people with disabilities.</p><p>For super fun stickers and helpful downloads, visit the Etsy shop: <a href="https://www.etsy.com/shop/DSPlifeShop">https://www.etsy.com/shop/DSPlifeShop</a>. Check this one out!: <a href="https://dsplifeshop.etsy.com/listing/4327747933">https://dsplifeshop.etsy.com/listing/4327747933</a></p><p>Facebook page: <a href="https://www.facebook.com/profile.php?id=61584711986267">https://www.facebook.com/profile.php?id=61584711986267</a></p><p>Website: <a href="http://www.mydsplife.com/">www.mydsplife.com</a></p><p>Subscribe so you do not miss future posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49219d31c4f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Waitlist Isn’t a Line. It’s a Service Gap.]]></title>
            <link>https://medium.com/@dsplifetm/the-waitlist-isnt-a-line-it-s-a-service-gap-c51032bc5e10?source=rss-59240668aabf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c51032bc5e10</guid>
            <category><![CDATA[developmental-disability]]></category>
            <category><![CDATA[disability-services]]></category>
            <category><![CDATA[residential-service]]></category>
            <category><![CDATA[virginia-group-home]]></category>
            <category><![CDATA[virginia]]></category>
            <dc:creator><![CDATA[Dana Kiser]]></dc:creator>
            <pubDate>Mon, 12 Jan 2026 13:26:50 GMT</pubDate>
            <atom:updated>2026-01-12T13:26:50.312Z</atom:updated>
            <content:encoded><![CDATA[<h3>What it feels like to build a licensed provider service in Virginia while you’re told to wait “a year or more.”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lVfSUOiUED4dsXS23HDT9w.png" /></figure><p>I expected paperwork.</p><p>I expected background checks, policies, inspections, training requirements, fire drills, med records, incident response plans … the whole alphabet soup of compliance that comes with doing residential services the right way.</p><p>What I didn’t expect was the quiet part: the waiting.</p><p>Not a “we’re reviewing your application this week” kind of waiting. More like: <em>you’re in queue, and because your service category isn’t considered a priority, you may be on a waitlist for a year or longer once preliminary review happens.</em></p><p>That sentence doesn’t just land on a provider.</p><p>It lands on families. Support coordinators. Hospitals. DSPs working short-staffed. And most of all, it lands on people with disabilities who don’t have the luxury of waiting for the system to catch up.</p><h3>The service desert isn’t dramatic. It’s daily.</h3><p>When people hear “service desert,” they picture a map with big empty spaces.</p><p>In real life, it looks like this:</p><p>A person ready to leave a higher level of care… but no placement available.</p><p>A family doing heroic-level caregiving… with burnout building quietly for months.</p><p>A support coordinator calling every provider they know… and hearing the same answer: “We’re full.”</p><p>A provider trying to open capacity… and getting stuck behind timelines that don’t match real-world need.</p><p>Nothing about that is theoretical. It’s not a statistic. It’s a calendar that fills up with emergency problem-solving because the stable option isn’t there.</p><h3>“Non-priority” doesn’t mean “not needed.”</h3><p>I understand why systems triage. Agencies have limited staff. Some services are urgent by definition. Some categories get fast-tracked.</p><p>But here’s the part that stings: residential support for people with developmental disabilities can be <em>both</em> essential and treated like it can wait.</p><p>You can call it “non-priority.”</p><p>Families call it, “We can’t do this alone anymore.”</p><p>Providers call it, “We’re ready to serve, but we can’t get through the door.”</p><p>And people receiving services call it a thousand other things (usually without the exact words) because what they feel is the outcome: instability, transitions, and the constant sense that support depends on luck.</p><h3>The hidden cost of waiting is what happens in the meantime.</h3><p>When there aren’t enough homes, pressure shifts elsewhere:</p><p>Hospitals become holding areas.</p><p>Crisis services become routine.</p><p>Families become unpaid staffing plans.</p><p>DSPs become stretched thin, and then blamed for burnout that was structurally guaranteed.</p><p>And every “temporary solution” becomes another month that someone’s life isn’t truly theirs. It’s just managed.</p><p>That’s the part I can’t ignore.</p><p>Because I’m not trying to open a group home to check a box.</p><p>I’m trying to build something that creates stability where stability is currently scarce.</p><h3>So what do you do when the state tells you to wait?</h3><p>You build anyway.</p><p>You build policies that are actually usable, not just “compliant.”</p><p>You build documentation systems that protect the individual and the staff.</p><p>You build training that doesn’t overwhelm people on Day 1.</p><p>You build a culture where “we’re short today” doesn’t become the personality of the whole program.</p><p>And you keep preparing like you’re opening tomorrow, even if the timeline says otherwise, because when approval finally comes, the community doesn’t get a warm-up period. They need capacity immediately.</p><p>That’s why I’ve been building DSPlife Collaborative with my husband, and why he’s developing CareHub: an online compliance and documentation system designed specifically for residential services. Not to add more paperwork. To make the paperwork make sense.</p><p>Because the truth is: good care can get undermined by messy systems.</p><p>And messy systems can ruin good staff.</p><h3>If we want different outcomes, we have to name the bottleneck.</h3><p>There are a lot of conversations happening about waitlists — waiver waitlists, staffing shortages, housing availability.</p><p>But there’s another waitlist that matters too:</p><p>The waitlist for providers who want to open services responsibly, and are ready to be held accountable, but can’t get reviewed in a timeframe that reflects the need on the ground.</p><p>If we want more safe, stable residential options, we have to treat provider capacity as part of the solution, not as something that can sit in queue indefinitely while communities scramble.</p><h3>I’m still building. I’m still waiting. And I’m still not backing down.</h3><p>I don’t share this for sympathy.</p><p>I’m sharing it because this is what the system feels like from the provider side when you’re trying to do it right, and the timeline doesn’t match the urgency in people’s lives.</p><p>If you’re a family member sitting in uncertainty: I see you.</p><p>If you’re a DSP holding everything together on a hard shift: I see you.</p><p>If you’re a support coordinator trying to place someone and running out of options: I see you.</p><p>And if you’re a policymaker or administrator reading this: I’m asking you to look closely at what “waitlist” actually means in real time, because time is the one resource the people affected don’t get back.</p><h3>If this resonates…</h3><p>If you’ve experienced a service desert (as a family, DSP, provider, or support coordinator), I’d genuinely love to hear what it looked like for you. Comment your experience — or share this with someone who needs to understand why “just wait” isn’t a plan.</p><h3>Connect With DSPlife</h3><p>If this helped you, follow along for more plain-language breakdowns of systems that impact people with disabilities.</p><p>For super fun stickers and helpful downloads, visit the Etsy shop: <a href="https://www.etsy.com/shop/DSPlifeShop">https://www.etsy.com/shop/DSPlifeShop</a></p><p>Facebook page: <a href="https://www.facebook.com/profile.php?id=61584711986267">https://www.facebook.com/profile.php?id=61584711986267</a></p><p>Interested in a compliace application that is made just for residential services? Check out CareHub! Our first application built by my husband :) www.carehub.mydsplife.com. Peruse our main website as well at www.Mydsplife.com.</p><p>Oh, and… Subscribe so you do not miss future posts. 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c51032bc5e10" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>