HarnessHealth

For Developers

Free pipes.
Paid brain.

The SolvingHealth SDK gives you FHIR connectors, EHR adapters, encrypted transport, PROM widgets, and patient matching — the open layer. The intelligence layer (encounter linking, billing optimization, physician attestation, the MCP server) is proprietary.

solvinghealth-sdk — the open layer — Fork it
  • FHIR R4 connectors (read/write)
  • EHR connector scaffolding (FHIR R4 client) — no live EHR integration
  • encrypted transport layer
  • PROM collection widgets (KOOS JR, HOOS JR, VAS, custom)
  • Patient matching algorithm
  • Billing code libraries (CPT, ICD-10, HCPCS)
  • Omaha System nursing documentation schema
  • FHIR to Omaha mapping
  • NPI lookup proxy (harnesshealth.ai/api/npi)
  • Model-agnostic: bring MedGemma, Claude, GPT, Gemini, or your own weights — see /medgemma

Repository: github.com/blainomd/solvinghealth-sdk

The intelligence layer — proprietary
ComponentPricing
chanio (site assistant)Included with the embed
Encounter linkingSurgeonValue Core/Pro ($199/$299 per month)
Billing optimization$20/encounter or subscription
Physician attestationFlat fee per review, $12–$100
MCP serverFree evaluation, licensing for production
Compliance scoringBy conversation

Three ways to integrate.

From a one-line embed to a full API integration to Claude Desktop. Pick the path that matches your use case.

Option 1

footer.js embed — one line

The fastest path. Add physician-governed AI to any healthcare website. Adds: chanio chat, patient intake, PROM collection, physician connection, ecosystem footer.

<script
  src="https://harnesshealth.ai/footer.js"
  data-npi="[YOUR_NPI_OR_PARTNER_NPI]"
  data-mode="patient"
></script>
Option 2

REST API

Not self-serve today. The governed chat bridge at solvinghealth.com/api/chat serves the ecosystem's own sites; no API keys are issued yet. The shape below is what a governed request looks like — an attested response carries the physician NPI, the timestamp, and the document hash. Want programmatic access in a pilot? Ask on /pilot.

# illustrative — not self-serve; no API keys are issued today (see /pilot)
curl -X POST https://solvinghealth.com/api/chat \
  -H "Authorization: Bearer [API_KEY]" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Patient reports 7/10 knee pain at rest for 3 days.",
    "npi": "[REVIEWING_PHYSICIAN_NPI]",
    "require_attestation": true,
    "specialty": "orthopedic_surgery"
  }'
Option 3

MCP Connector — Claude Desktop

Connect Claude to the hosted SolvingHealth MCP server — CPT validation, prior-auth drafting, NPI lookup, patient views. Remote MCP — no install, no API key for evaluation, no local process. One click below, or paste the config into your claude_desktop_config.json manually.

Add to Claude Desktop

Requires Claude Desktop v0.8 or later. The button opens Claude Desktop and pre-fills the harnesshealth MCP server — you approve it, and it's live.

{
  "mcpServers": {
    "harnesshealth": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://solvinghealth-mcp-production.up.railway.app/mcp"
      ]
    }
  }
}

Full connector setup at: harnesshealth.ai/connect

Pricing for builders.

No checkout on this site. The sandbox is free; production is a flat fee per review with terms that follow a BAA. Rates are published on clinicalswipe.com.

Sandbox

Any builder, researcher, or AI company evaluating the gate

$0
  • The SDK (free pipes)
  • MCP server in evaluation mode
  • Physician review of synthetic or de-identified outputs at clinicalswipe.com/sandbox
  • A verifiable receipt for every review
Most common
Production

AI companies shipping outputs that need a named human behind them

$12–$100 / review
  • Flat fee by document class, same for yes and no
  • Flat platform fee per completed review, disclosed up front
  • Specialty-matched, NPI-verified reviewer
  • Terms follow a BAA (none executed yet)
Health system

Governance committees deploying AI across affiliated practices

By conversation
  • BAA offered to qualifying covered entities
  • Governance documentation package
  • One-line embed per practice site
  • No EHR integration is live