Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect
Back to About
Patient Protect editorial mark

Collective editorial voice · Editorial Team

Patient Protect Editorial Team

Reviewed by the founders · Published under editorial standards

“Every post under this byline is reviewed by a CTO, a CSO, and a CEO before it publishes. No post reflects one person's view — and none is filler.”

The Patient Protect Editorial Team publishes original guidance, breach coverage, research, and product commentary under a single collective byline. Every post carrying this attribution has passed through review by the company's Chief Technology Officer, Chief Security Officer, and Chief Executive Officer — or by researchers working on the Secure Care Research Institute program.

Posts under this byline draw on three deep sources of expertise. Joseph A. Perrin (CTO) brings federal-grade infrastructure security experience, having designed the zero-trust architecture that protects the Patient Protect platform. Angie Perrin, RDH (CSO) brings more than a decade of direct clinical practice and Certified HIPAA Consultant credentialing. Alexander Perrin (CEO) brings twenty years of enterprise SaaS and platform architecture, and directs the company's research program through the Secure Care Research Institute.

The editorial program covers HIPAA compliance operations, healthcare cybersecurity, breach analysis, OCR enforcement, business associate risk, and the operational reality of independent healthcare practices. Every published claim is either sourced from primary regulation, publicly available breach intelligence, verified vendor documentation, or Patient Protect's own research. Speculation, unattributed statistics, and industry generalities do not appear under this byline.

Coverage runs across three permanent surfaces: the Patient Protect blog for long-form operational guidance and vendor analysis, HIPAA Pulse for daily healthcare breach and enforcement intelligence, and the Secure Care Research Institute for peer-facing research. Cross-referencing between the three is intentional — the blog explains what to do, HIPAA Pulse explains what just happened, and SCRI explains the underlying economics.

Editorial standards

  • Every factual claim has a primary source — regulation, published research, verified vendor documentation, or Patient Protect's own reporting.
  • Every regulatory citation names the specific rule (45 CFR reference, HHS guidance document, OCR resolution agreement, or state statute).
  • Every statistic includes methodology or a linked source. Industry averages without attribution do not appear.
  • Every breach analysis names the actual reporting outlet and links to the primary account.
  • Claims about competitor products use published evaluation frameworks, not unverifiable assertions.
  • Posts are dated and updated when the underlying reality changes; corrections are appended visibly.
  • Speculation is labeled. Opinion pieces are labeled. Research is labeled. Product claims are testable.
  • No emoji, no exaggeration, no fear-driven language. Independence is served by clarity, not alarm.

Who reviews the work

The three named reviewers behind every Editorial Team post.

No content publishes under the Editorial Team byline without review by at least two of the three. Deep technical or clinical topics route to the corresponding domain reviewer.

Recent Editorial Team posts

Latest work under the collective byline.

HIPAA compliance overview for telehealth providers covering video platform security and remote PHI access
Compliance Operations·2026-05-25

HIPAA Compliance for Telehealth Providers: The Complete 2026 Guide

Everything telehealth clinicians need to know about HIPAA compliance — platform BAAs, home office security, session recordings, multi-state practice, and the step-by-step path to full compliance after the end of COVID-era enforcement discretion.

Corrections and editorial contact

Errors get corrected visibly.

If a Patient Protect Editorial Team post contains a factual error, we correct it and note what changed. Rewriting the record silently is not an editorial practice we consider defensible. Send corrections, source questions, or interview requests to info@patient-protect.com.

For editorial commentary on healthcare-security research, breach economics, or independent-practice compliance operations, editors and reporters can reach any of the three named reviewers through their LinkedIn profiles linked from the individual bios above.