The idea began in Chicago in 2016. Patient Protect LLC followed in 2018. For years, we developed secure communications, referrals, and compliance tools alongside independent practices before bringing that work together in the commercial platform released in 2026.
Patient Protect is commercially new. The work behind it is not.
Patient Protect began around a family dinner table in Chicago. Angie Perrin was seeing independent practices held to serious privacy and security obligations without the people or infrastructure available to a hospital. Joe Perrin had spent decades building communications technology, databases, and secure systems for healthcare and government. Alex Perrin saw that the problem was not the absence of another compliance document. It was the absence of a system small practices could actually operate.
Patient Protect LLC was formed in 2018. For the next several years, we deployed early software and consulting largely at no cost through confidential arrangements with independent practices. That gave us something a rushed launch could not: time to see where workflows broke, what practices misunderstood, and which tools held up in daily use.
In 2024, we began consolidating that work into one modern platform. In early 2026, Patient Protect became commercially available.
The idea
The problem becomes visible and the first concepts take shape.
Patient Protect LLC
The company is formally established and the earliest tools begin working inside practices.
Field development
Software and consulting are deployed, observed, and repeatedly rebuilt.
One platform
The accumulated tools and learning are brought into a unified system.
Commercial release
Patient Protect begins accepting commercial customers.
Angie brought the lived reality of the practice. Joe brought the security architecture. Alex brought the product, research, and commercial framework. Patient Protect required all three.
Co-founder & Chief Security Officer
An RDH since 2013 and an adjunct dental instructor, Angie has spent fifteen years inside independent practices. Her understanding of how patient information actually moves through an office shapes Patient Protect’s clinical-risk methodology, workforce training, and practice implementation.
Full profile
Co-founder & Chief Technology Officer
Joe has spent more than 36 years building communications technology, databases, and secure infrastructure across healthcare and government environments. He designed Patient Protect’s technical foundation and the secure messaging and referral tools that preceded the current platform.
Full profile
Co-founder & Chief Executive Officer
Alex spent two decades leading growth and strategy across enterprise technology and digital advertising. He saw how Angie’s practice experience and Joe’s technical work could become a broader system, and led Patient Protect’s product direction, research program, market development, and commercial launch.
Full profilePatient Protect’s history is visible in the work: its legal formation, years of field development, published research, open data, free public tools, and the platform itself.
2018
Patient Protect LLC
Legal formation in Chicago, Illinois. Beginning of confidential field deployments with independent practices.
2018–2024
Field development
Early software and consulting deployed at no cost through confidential arrangements. The tools were observed, revised, and repeatedly rebuilt inside real practices.
2025
Research and open breach data
Secure Care Research Institute working papers on SSRN, plus the machine-readable Healthcare Breach Dataset under CC BY 4.0.
2026
Public HIPAA tools and infrastructure
Free tools for independent practices: the Patient Protect Score, entity determination, ePHI data flow mapper, breach dashboard, HIPAA Response tracker.
2026
HIPAA Foundations and Signal
Nineteen-module workforce training curriculum (five modules free), and Patient Protect Signal — a free iOS app for breach alerts, regulatory developments, and practice-level compliance tools.
2026
Commercial platform
Public security architecture (zero-trust, AES-256-GCM at rest, TLS 1.3 in transit, AppSensor, immutable audit logging) and the commercial release itself.
01
Compliance documentation and operational security are different disciplines. Both matter. Patient Protect adds ongoing risk management, diagnostics, encrypted workflows, incident readiness, and evidence preservation — and can work alongside an existing compliance partner or serve as the practice’s primary platform.
02
When compliance support costs more than an independent practice can reasonably sustain, many practices go without it. Patient Protect starts at $39 a month because protection that excludes the most resource-constrained practices fails the people who need it most.
03
HIPAA risk analysis and risk management are ongoing responsibilities, not annual paperwork. Patient Protect continuously evaluates the practice’s environment because its people, vendors, systems, and risks keep changing.
Many compliance partners perform valuable policy, documentation, and training work. Patient Protect can strengthen that foundation with operational security, or provide the full compliance system itself.
We built Patient Protect toward the strongest defensible security posture under the current rule and toward the direction later reflected in HHS’s proposed Security Rule modifications. Those modifications remain proposed, not final.
Authority in this category should come from precision, not aggression.
The Secure Care Research Institute examines the economic and operational consequences of healthcare data exposure. Its working papers, breach dataset, and quarterly analysis inform Patient Protect’s product direction and public tools.
That work currently includes two SSRN working papers and the State of Compliance series. SSRN papers are working papers, not peer-reviewed publications. Methods, sources, and limitations are published alongside the work.
Every practice we protect is someone’s medical history staying private. Someone’s mental health records staying sealed. Someone’s child’s dental records staying out of the wrong hands.
That is what this is actually about.
