Security guidance should meet a practice where it is.
HIPAAWorks helps small healthcare practices understand their HIPAA Security Rule gaps, decide what to address first, and keep a clear record of the work they do next.
years of cybersecurity and IT-risk work in healthcare, from hospital compliance teams to two-provider practices.
Same rule, far fewer resources.
I spent twenty years in cybersecurity and IT risk before I built this, most of it inside healthcare organizations of every size. I have sat across the table from hospital compliance teams with dedicated staff and multi-year budgets. I have also sat across from a two-provider practice where the person responsible for security also checks patients in at the front desk. Both are held to the same rule.
Small medical, dental, therapy, and specialty practices hold sensitive information and carry the same responsibilities under the HIPAA Security and Privacy Rules as much larger organizations. The law lets an organization weigh its size, capabilities, and costs when choosing reasonable and appropriate safeguards. That flexibility changes how a practice does the work, and the work itself stays: understand its risks, protect patient information, train its workforce, manage vendor relationships, and document what it has done.
Year after year, almost everyone I met already believed security mattered. What they struggled with was turning a broad legal requirement into a step their practice could take this month, and then having something to show for it later.
Security work competes with the work of running a practice.
Large health systems can assign this work to compliance, legal, privacy, and IT departments. In a smaller practice it falls to one person who already has other jobs, usually the practitioner, the office manager, or a front-desk lead, and they fit it in around patient care, billing, staffing, and everything else that keeps a practice open. People understand why the follow-up matters. It slips because the week has no room left for it.
Every dollar spent on security is a dollar not spent on payroll, clinical systems, or supplies, so these decisions are hard. An electronic health record vendor or an outsourced IT provider can protect part of the environment, but the practice still needs its own risk analysis across every system that touches patient information. Each billing service, cloud tool, or messaging platform it adds brings another agreement to manage and another set of safeguards to understand. Training has to hold up through staff turnover and a full calendar, so one orientation session isn't enough. Work that exists only as a verbal policy, or as a decision one person remembers, is hard to keep up and harder to demonstrate months later without a written, dated record.
Too many tools I encountered added another layer of jargon, or produced a report that went stale the day it was downloaded. With HIPAAWorks I wanted plain-language questions, severity-tiered gaps, practical remediation guidance, and a dated evidence trail that grows as the practice does the work.
A proposed rule would make expectations more specific.
The current HIPAA Security Rule is still in effect and unchanged. In January 2025, HHS published a proposal that shows where federal expectations may be heading. If it is finalized substantially as written, it would remove the distinction between required and addressable implementation specifications. It would also add specific expectations for encryption, multi-factor authentication, technology asset inventories, network maps, vulnerability scanning, penetration testing, incident recovery, and written documentation. You can read the HHS proposal overview directly.
The federal regulatory agenda currently lists July 2027 as the projected date for final action. That date can move, and the proposal can still change before it is final, so treat July 2027 as a planning signal rather than a deadline. I have written more about what that means for a small practice .
You don't have to predict the final rule to start. A current risk analysis, stronger access controls, a basic inventory of systems and vendors, regular workforce training, and better documentation are worth doing under today's rule, and they leave a practice better prepared if the requirements change.
Built for how a small practice actually runs.
A few principles guide how I built HIPAAWorks and how I keep changing it. I write in plain language, so people can see what is being asked and why without first translating legal or technical terms. Guidance should fit the tools a practice already uses and give the team a realistic place to start. Finding a gap starts the work; the notes, decisions, status changes, and supporting evidence that follow let a practice show later what it found and what it did about it. And I am clear about limits: no software can replace a practice's judgment or promise a regulatory outcome. HIPAAWorks supports the process, and the organization reviews and attests to its own work.
“Security is not a small job, and I don't pretend it is. I want the next step to be clear enough that a busy practice will take it.”
I still check every part of the product against that. What a practice usually needs is help deciding what to do next and a way to keep a record of the work as it goes, and that is what I am building.
Josh - Founder, HIPAAWorks
See what your practice may need to address next.
The free Quick Check asks seven plain-language questions and gives you an initial view of potential gaps. It takes about five minutes and does not require a card.
Start your free Quick Check