Physician-Led AI for Procedural Patient Education

Executive Summary

PrepQ is the only AI-powered procedural patient education platform built and governed by practicing physicians. While competitors rely on software engineers to train AI models on general medical text, PrepQ delivers content that has been written, reviewed, and validated by board-certified MDs and DOs before it reaches a single patient.

This document covers PrepQ's clinical governance framework, AI safety methodology, specialty society compliance posture, and HIPAA architecture. It is written for three audiences: compliance officers evaluating vendor risk, payers assessing clinical credibility, and healthcare system procurement teams making platform decisions.

1. The Problem with Tech-Only AI in Healthcare

The market for AI-assisted patient education has grown rapidly. Dozens of platforms now offer procedure prep content, prior authorization support, and clinical documentation assistance. The majority are built by technology companies staffed by engineers with no clinical background.

1.1 Algorithmic Accuracy Is Not Clinical Accuracy

Large language models are trained on broad datasets. They produce fluent, confident-sounding text. They also hallucinate drug interactions, misstate hold periods for anticoagulants, and confuse CPT codes with statistically similar but clinically different ones. An engineer reviewing output for coherence will not catch these errors. A physician reviewing for accuracy will.

The stakes are high. A patient told to stop their anticoagulant four days early before a spinal cord stimulator trial faces stroke risk. A patient given the wrong NPO instructions before a celiac plexus block faces aspiration risk. These are not edge cases. They are the everyday clinical decisions that procedural patient education must get right.

1.2 Liability Without Accountability

Tech-only platforms typically operate under broad disclaimers that their content is for informational purposes only and does not constitute medical advice. In practice, patients and providers use this content to make clinical decisions. When something goes wrong, liability flows to the practice, not the software vendor.

PrepQ is different. Licensed physicians have reviewed and are accountable for every clinical claim in the platform. This shifts the governance model from tech company disclaimed to physician certified, which meaningfully changes the risk profile for partner institutions.

1.3 Regulatory Risk Is Accelerating

The FDA, CMS, and state medical boards are all actively developing frameworks for AI in clinical settings. The direction of travel is clear: AI tools that provide clinical guidance will face increasing requirements for physician oversight, documented review processes, and audit trails. PrepQ is already operating at the standard regulators are moving toward. Most tech-only competitors are not.

2. PrepQ's Clinical Governance Framework

PrepQ operates under a formal two-physician governance structure. Both founders are clinically active. Their oversight is not advisory. It is operational.

2.1 Clinical Leadership

2.2 Content Review Process

Every procedure module on PrepQ goes through a structured review process before publication. Content is drafted against specialty society guidelines, reviewed for clinical accuracy by a physician with relevant training, reviewed for coding accuracy against current CMS and payer guidelines, and then approved for publication with the reviewing physician on record.

Substantive updates to clinical guidelines trigger a re-review of affected modules. PrepQ does not wait for a model retraining cycle to incorporate new guidance. When ASRA updates its anticoagulation guidelines or CMS changes a coverage policy, the relevant modules are flagged and updated within the review cycle.

2.3 Scope of Current Coverage

PrepQ covers procedures across three specialty categories, with 85 or more pain management procedures in current coverage:

• Pain management: spinal injections, nerve blocks, neuromodulation, sympathetic blocks, PNS (18 nerve-specific targets)
• Orthopedic procedures: joint injections, aspiration, fluoroscopic guidance
• Urology procedures: cystoscopy, urodynamics, prostate procedures
• Headache and neurology: Botox PREEMPT protocol, SPG block, trigger point injection
• Regional anesthesia: peripheral nerve blocks, thoracic paravertebral, pudendal

Each procedure module includes 14 clinical tabs covering Checklist, Anticoagulation, CPT Coding, Denial Management, ICD-10, Patient Education, Exercises, Imaging, Preference Card, Prior Authorization Letter, Research and Evidence, Sample Clinic Note, Sample Procedure Note, and Post-Procedure Instructions.

3. AI Safety Methodology

PrepQ uses AI as a drafting and synthesis tool. All AI-generated content is treated as a first draft, not a final output. A physician reviews and approves every clinical claim before it is published.

3.1 Human-in-the-Loop Architecture

The pipeline has three stages. First, AI models assist in drafting procedure content and structuring clinical data. Second, a board-certified physician reviews the draft against primary source guidelines, including ASRA, CMS coverage determinations, specialty society position statements, and peer-reviewed literature. Third, the reviewed and approved content is published with the reviewing physician's credentials on record.

End users see physician-certified content, not raw AI output.

3.2 Anticoagulation Safety

PrepQ's anticoagulation framework is built directly on ASRA Pain Medicine guidelines and stratifies every covered procedure into one of three risk tiers:

• High risk: Neuraxial and poorly compressible spaces including epidural steroid injections, intrathecal pump access, SCS implantation, adhesiolysis, and atlantoaxial joint injections
• Intermediate risk: Moderate bleeding consequence including medial branch blocks, RFA, sacroiliac procedures, stellate ganglion block, vertebroplasty, discography, and thoracic paravertebral block
• Low risk: Manageable bleeding consequence including joint injections, trigger point injections, peripheral nerve blocks, and all 18 nerve-specific PNS targets

3.3 CPT Coding Accuracy

PrepQ embeds CPT guidance reviewed by physicians familiar with the specific billing context of each procedure. For procedures with bundling rules, PrepQ flags the correct bundling approach rather than defaulting to separate billing that payers will deny.

4. HIPAA Architecture and PHI Handling

4.1 PHI-Free by Design

PrepQ's architecture eliminates the most common HIPAA risk in AI-assisted clinical tools: inadvertent transmission of protected health information to third-party AI providers. The platform does not require providers or patients to enter PHI to access procedure education content. No names, dates of birth, medical record numbers, or diagnosis codes tied to individual patients are required to use the platform's core functionality.

4.2 Active Security Controls

• HTTPS enforced across all endpoints with HSTS preload submitted to browser preload lists
• Content-Security-Policy header restricting script and resource origins
• Subresource Integrity hashes on all CDN-loaded scripts
• X-Frame-Options: DENY to prevent clickjacking
• X-Content-Type-Options: nosniff
• Referrer-Policy: strict-origin-when-cross-origin
• No PHI inputs required in the core clinical content layer

A formal security audit conducted in April 2026 produced a 27-finding remediation report. All critical and high findings were resolved within 48 hours.

5. Specialty Society Compliance

5.1 ASRA Pain Medicine

PrepQ's anticoagulation framework maps every covered procedure to ASRA Pain Medicine's classification system and generates recommendations consistent with the most recent published guidance. ASRA Pain Medicine's practice advisory on interventional pain procedures is the authoritative source for hold and restart recommendations.

5.2 CMS Coverage Determination Alignment

Prior authorization letter templates and ICD-10 guidance are written against CMS Local Coverage Determinations and major commercial payer policies. They are reviewed by physicians who understand the specific language payers require to approve coverage.

5.3 CME Accreditation

PrepQ is pursuing CME accreditation through the ACCME framework, in development. Partner societies identified for joint providership include the American Society of Regional Anesthesia and Pain Medicine, the American Academy of Pain Medicine, the American Society of Interventional Pain Physicians, the American Society for Pain and Neuroscience, the North American Neuromodulation Society, and the International Pain and Spine Intervention Society.

6. PrepQ vs. Tech-Only Platforms

The table below summarizes the key structural differences between PrepQ's physician-governed model and the tech-only AI tools most commonly evaluated alongside it.

7. Use Cases by Stakeholder

Hospital and Surgery Center Compliance Officers

PrepQ's physician oversight structure, formal review process, and HIPAA-by-design architecture provide the documentation layer that compliance officers require when evaluating patient education vendors.

Payers and Utilization Management Teams

Physician-authored prior authorization letters, accurate ICD-10 linkages, and denial management guidance reduce the back-and-forth that delays approvals and creates administrative burden for practices.

Healthcare System Procurement Teams

PrepQ's differentiator is not a claim. It is a governance structure with two named, licensed physicians and a documented review process, a defensible basis for vendor selection that can be represented to clinical leadership and legal counsel.

Interventional Practices

Accurate anticoagulation guidance reduces periprocedural bleeding risk. Physician-authored prior authorization letters improve approval rates. Correct CPT coding reduces denials. Post-procedure instructions written by physicians reduce patient calls and unnecessary emergency department visits.

8. Conclusion

The AI-in-healthcare market is consolidating around a simple question: who is accountable for clinical accuracy? Technology companies can build fast and scale quickly. They cannot practice medicine, sign their name to a clinical recommendation, or carry a medical license that regulators can hold accountable when something goes wrong.

PrepQ is built on the premise that physician oversight is not a compliance checkbox. It is the core product. Every procedure module, every anticoagulation recommendation, every prior authorization template, and every post-procedure instruction on PrepQ has a physician's name behind it.