Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect
Back to About
Joseph A. Perrin

Joseph A. Perrin

Co-founder & Chief Technology Officer

LinkedIn

Joseph A. Perrin is the co-founder and Chief Technology Officer of Patient Protect. He has spent more than thirty-six years building communications technology, databases, and secure infrastructure — including a former CTO role in government-health technology — the disciplines that produced the earliest Patient Protect tools and, years later, the modern platform.

The technical lineage matters. When the idea for Patient Protect first took shape in 2016, some of the pieces already existed inside Joe's prior work. Secure messaging became one of the earliest Patient Protect tools. Secure referrals followed after the team watched patient information move between offices through paper trails and other insecure workflows. What began as targeted point solutions inside real practices became the substrate the current platform was built on: a compliance and security architecture where documentation is a byproduct of doing the work securely, not a substitute for it.

The full security stack he designed for the current platform — zero-trust architecture, encryption at rest, TLS 1.3 in transit, session-vault isolation, fail2ban intrusion response, SMS-based two-factor authentication, an Altcha proof-of-work challenge layer, browser-fingerprinting defense against credential-stuffing and session-hijacking, AppSensor integration, and continuous audit logging — is documented on the security page. The same architectural patterns he applied to protect government-sensitive systems now protect the patient data of independent clinical practices.

His methodology contribution runs deeper than any single component. Patient Protect's risk-analysis model, threat-modeling framework, and Business Associate contract-review process reflect the discipline of environments where documentation alone was never sufficient. He works on ongoing platform hardening, vulnerability response, and the continuous review of every new component that enters the Patient Protect data path.

Current focus

  • Security architecture across all Patient Protect modules
  • Encryption, session management, and audit logging infrastructure
  • Third-party integration and Business Associate technical review
  • Continuous hardening against credential-stuffing and session-hijacking

Areas of expertise

  • Zero-trust architecture and network segmentation for regulated environments
  • Encryption standards for data at rest and in transit, and session security
  • Intrusion detection and automated defensive response
  • Multi-factor authentication and identity assurance for clinical workforces
  • Threat modeling and risk-analysis methodology for healthcare data environments
  • Business Associate Agreement contract review and third-party risk assessment
  • Federal and government-adjacent healthcare infrastructure security
  • Ongoing platform vulnerability response, hardening, and evidence preservation

Credentials & experience

  • Secure Infrastructure Architect — Federal & Clinical Healthcare Systemsprofessional experience
  • Zero-Trust Architecture — Platform Design and Implementationprofessional experience

Authored guides

Published by Joseph A. Perrin

10 guides on Patient Protect.

Best HIPAA compliance software for HRT and TRT clinics in 2026
Compliance Operations·2026-09-11

Best HIPAA Compliance Software for HRT and TRT Clinics (2026)

HRT/TRT clinics layer DEA Schedule III controlled-substance tracking, compounding pharmacy BAAs, lab workflow, telehealth, and state board scrutiny on top of HIPAA. The 7 features that distinguish HRT/TRT-fit compliance tools.

Best HIPAA compliance software for GLP-1 weight management clinics in 2026
Compliance Operations·2026-09-08

Best HIPAA Compliance Software for GLP-1 Clinics (2026)

GLP-1 weight management clinics layer state board overlay, 503A compounding pharmacy BAAs, lab order workflows, marketing-heavy patient acquisition, and membership-based long-term care on top of HIPAA. The 7 features that distinguish GLP-1-fit compliance tools.

AI medical scribe HIPAA compliance buyer's framework covering Abridge, DAX, Suki, and category evaluation
Security & Threats·2026-08-18

AI Medical Scribes and HIPAA: A 2026 Buyer's Framework

Abridge, DAX Copilot, Suki, Heidi, Nuance Dragon, DeepScribe, Augmedix, AWS HealthScribe — the AI scribe category exploded in 2026. The 10-question framework that determines whether the vendor you pick is HIPAA-compliant or just HIPAA-marketed.

HIPAA incident response plan template for independent healthcare practices
Security & Threats·2026-07-31

HIPAA Incident Response Plan Template (2026)

The nine sections we build a HIPAA incident response plan around, how the breach-determination decision actually flows, and the template practices use — written by independent providers, not by Fortune 500 CISOs.

Network firewall comparison for HIPAA compliance in independent healthcare practices
Security & Threats·2026-06-26

Best Firewalls for HIPAA Compliance (2026)

HIPAA does not name a firewall. It names the controls a firewall must enforce. Six options ranked for independent practices — SonicWall, Fortinet, Cisco Meraki, pfSense, Palo Alto, WatchGuard.

Business Associate Agreement red flags that independent healthcare practices miss before signing
Compliance Operations·2026-04-05

Top 6 BAA Red Flags Every Independent Practice Misses

The six clauses in a Business Associate Agreement that determine whether the contract actually protects the practice or just satisfies the HIPAA box-check. What to read for before signing.