openclaw
← All products
Compliance & Legal

hipaa-doc-intake

HIPAA-compliant medical-intake extractor. **All inference is LOCAL Qwen.** PHI never leaves the clinic network.

Available plan
Practice
HIPAA-compliant medical-intake — single practice, on-prem
subscription monthly · Get plan →
Source on GitHub

API quickstart

After purchase, you'll receive an API key (ock_...) by email. Call the endpoint below with that key as the bearer token.

Request fields
  • form_text — string — full intake form content
curl -X POST -H 'Authorization: Bearer ock_xxx' \
     -H 'Content-Type: application/json' \
     -d '{"form_text": "Patient Name: Jane Doe\nDOB: 1985-03-12\nMRN: 100234\nPresenting concern: Persistent cough..."}' \
     https://openclawapi.vercel.app/v1/hipaa-doc-intake/run
Model: claude-sonnet-4-6. Quota enforced per plan.

Launch kit

hipaa-doc-intake — launch kit

1-liner

HIPAA-compliant medical-intake extractor. All inference is LOCAL Qwen. PHI never leaves the clinic network.

Tweet hook

OpenAI / Anthropic API: not HIPAA-compliant without a BAA. Most BAAs priced for hospital scale, not 4-doctor clinics.

Built it on local Qwen. PHI never touches the cloud. Hard-coded refusal: app won't start if LLM URL isn't local.

$499/mo/practice 🧵

Reddit (specialized)

  • r/medicine: "HIPAA-friendly intake automation"
  • r/dentistry: same

Cold-email ICP

Solo + small medical / dental / mental-health practices. Pull from NPI registry + state medical-board directories.

Cold-email template

Subject: HIPAA intake without the BAA gymnastics

Hi Dr. {last} — for {practice name}.

OpenAI's BAA is enterprise-priced. Local Qwen for intake extraction
is HIPAA-compliant by architecture: PHI never leaves your network.

$499/mo per practice. Free 30-day pilot. We install Qwen on your
existing server (or supply hardware for $2.5K).

ROI: 2-3 hours/day staff time saved on data entry.

SEO content

  1. "HIPAA-compliant AI intake — what 'compliant' actually means"
  2. "Why most AI medical-records tools aren't HIPAA-friendly"
  3. "On-prem Qwen for clinics — setup guide"

Documentation

hipaa-doc-intake

HIPAA-compliant document intake + structured extraction for small medical practices. All inference is local Qwen. PHI never leaves the clinic's network.

Why this exists

OpenAI / Anthropic / Google APIs are not HIPAA-compliant for general use without a Business Associate Agreement (BAA). Most BAAs are priced for hospital-system scale.

Small practices (1-10 providers) can't afford BAA overhead. They either (a) avoid AI tools entirely or (b) violate HIPAA by sending PHI to cloud LLMs.

This product solves it: Qwen 30B running on the clinic's own server. PHI never leaves the network. Compliant by architecture.

Pricing

  • $499/mo per practice — up to 5 providers
  • $1,499/mo — multi-location practice (up to 25 providers)
  • Setup $2,500 one-time — install Qwen on clinic server, configure scanner integration, train staff

The TAM here is enormous: 200K+ small US practices, most are running on paper or first-generation EMRs.

Hard-coded compliance

extract.py REFUSES to start if HIPAA_LOCAL_LLM_URL doesn't resolve to a local-network address (localhost, 10.x, 192.168.x). This is a belt-and-suspenders layer of defense — the operator could still misconfigure the underlying network, but the application itself won't speak to a non-local LLM.

Run

cd C:\openclaw-products\hipaa-doc-intake
python -m venv .venv
.\.venv\Scripts\activate
pip install -e .

# LM Studio with qwen3-30b-a3b-2507 must be running locally

hipaadoc intake form-1042.txt --out extracted/1042.json

Roadmap

  • Vision-extraction (currently text-only); use local Qwen-VL
  • EMR push (Epic, Athena, eClinicalWorks integration)
  • Insurance-card OCR pipeline
  • Audit log of every extraction (for HIPAA accounting-of-disclosures)
  • At-rest encryption for the SQLite cache
  • Operator dashboard for review-before-send to EMR