For Health Systems
Physician-governed AI
for health systems.
Designed to align with HIPAA. BAA offered on request — none executed yet.
HarnessHealth provides the governance infrastructure — physician attestation, NPI identity layer, encrypted transport, FHIR connectors — that your AI deployment needs to satisfy legal, compliance, and clinical leadership.
Request a BAA and evaluation packageHow physician governance works at scale.
Three steps. Every clinical AI output in the network follows the same chain.
AI generates
The clinical AI produces a draft output — prior authorization letter, LMN, care plan, SOAP note. The output is tagged as unattested. It cannot leave the system without a physician signature.
Watch the gate hold a draft →Physician reviews
A licensed physician with an active, clean NPI receives the document in the ClinicalSwipe review queue. Designed for a 3–5 minute review. The physician approves, rejects, or modifies. Each action is NPI-bound and timestamped.
Open the reviewer app (sandbox) →Attestation is cryptographic
The signed document carries: the reviewing physician's NPI, timestamp, authority consumption token, and document hash. The record is hash-anchored and tamper-evident. If challenged, the full attestation chain is auditable.
Sign and verify a document yourself →Authority consumption tracking
Each physician has a daily review ceiling enforced by the system. A physician cannot rubber-stamp 500 documents in a day. The system flags and blocks over-attestation. This is the mechanism that prevents credential laundering at scale.
HIPAA-aligned by design, not by policy.
Factual status of each HIPAA compliance element. No marketing language.
| Requirement | How HarnessHealth addresses it | Status |
|---|---|---|
| BAA with covered entities | Offered to qualifying covered-entity partners; none executed yet | On request |
| PHI encryption at rest | Supabase AES-256 encryption | Live |
| PHI encryption in transit | TLS 1.3 via Vercel (SOC 2 Type II) | Live |
| Access controls | Row-level security in Supabase; policies audited September 2026 | Live |
| Audit logging | Every attestation event logged with NPI, timestamp, and document hash | Live |
| No PHI in AI training | No PHI is sent to any model provider; API calls carry no persistent retention | Live |
| Flat per-review physician fee | Same fee whether the physician signs or declines; never a percentage, never tied to referrals | Policy |
| FHIR R4-aligned output | Standards-aligned connectors; Redox loop live on SurgeonValue, SDK not yet released | Partial |
| Formal Security Risk Assessment | In process | In process |
| Penetration test report | In schedule | In process |
Integration path.
EHR integrations
Designed, not built. No EHR integration is live; the Redox sandbox loop on SurgeonValue is the only connector running.
- Epic (SMART on FHIR)
- Cerner / Oracle Health
- athenahealth
- eClinicalWorks
- ModMed
Live integrations
Running in production today.
- CMS NPPES NPI registry (real-time lookup; nothing stored)
- Supabase (auth and storage; Google sign-in)
- Redox sandbox loop (on SurgeonValue)
- Hashcare receipts (public registry, daily countersign)
- The hosted MCP server (CPT validation, prior-auth drafting, NPI lookup)
The footer.js embed
Health systems deploying HarnessHealth for affiliated practices add one line to each practice website. IT overhead: one line of JavaScript per site. No backend integration required for initial deployment.
<script
src="https://harnesshealth.ai/footer.js"
data-npi="[NPI]"
data-health-system="[YOUR_SYSTEM_ID]"
></script>After go-live
The cost nobody budgeted is the one that keeps compounding.
Mayo Clinic runs 128 clinical AI solutions with nearly 500 in the pipeline, and for about 70% of them Mayo is the legal manufacturer. Its chief AI implementation officer told Becker's on August 31, 2026: “The cost of maintaining these systems is far higher than I think any of us in the industry really thought” — compute, the specialized workforce to monitor and maintain, and the data infrastructure — and “if those engineers can never let go of the product because they're needed to maintain and oversee things like data drift, model drift … that starts to become a big challenge.” If that is Mayo, it is every health system.
A named human owns the output
The one part of the after-go-live burden that cannot be automated away is accountability for what the model produced. Here it is a specialty-matched, NPI-verified physician, priced per review — variable cost, not headcount.
What a review costs →The receipt is the audit trail
Every attested output is a dated record of what the model produced and what the physician did to it — a drift signal at the level of decisions. We do not monitor model internals; we make the decisions inspectable.
Verify a receipt →Who pays is still open
Mayo says the compensation question for AI-enabled care is unresolved and is funding tools with no line-of-sight ROI. A flat fee per review is the smallest unit of that answer — and the state laws now make the human review a requirement, not a preference.
The statutes and the sources →Source: Becker's Hospital Review, “Mayo AI chief: Maintenance costs are ‘far higher’ than expected,” August 31, 2026. Quoted for what it says about the industry; Mayo is not a customer or partner.
Built for the reimbursement environment
you are operating in.
Where a program requires a named clinician's oversight, the signature and the receipt are the documentation. The treating practice bills; HarnessHealth does not.
| Program | Relevance | Status |
|---|---|---|
| Remote Therapeutic Monitoring (RTM) | Paid per code for each 30-day period, and the amount varies by code and locality. RTM data may be reported by the patient. | Billed by the treating practice with the attested record. A surgeon cannot bill it on their own patient inside the global period. |
| Chronic Care Management (CCM) | Monthly care-management codes that need a billing practitioner and the patient consent | Not offered. It needs an enrolled billing practice, and none is enrolled yet. |
| CJR-X | Mandatory joint bundled payments; final rule July 2026, mandatory January 2028 | SurgeonValue built for it |
| Advance Care Planning (ACP) | CPT 99497 and 99498, billed by the clinician who holds the conversation | caregoals.com is a free planning form. It does not bill. |
Start in the sandbox. A BAA comes second.
Bring one synthetic or de-identified AI output to the ClinicalSwipe sandbox today — no account, no commitment. A BAA is offered to qualifying covered entities and none has been executed yet; requests below reach the founder directly, not a queue.