Skip to main content
Talk to our team +1 (844) 685-2295
Integrations

Bring your own tools, AI assistants, and pipelines.

API keys, OAuth, and MCP share one workspace-scoped view of patients, encounters, notes, and codes, with PHI staying inside the boundary.

Three ways in

API key, OAuth, or MCP. Same scope and audit trail.

API keys

Workspace-scoped REST keys. Per-key scopes, full audit log.

  • Workspace-scoped, never cross-tenant
  • Per-key scopes for read, write, and admin paths
  • Audit log on every issued, rotated, or revoked key
Read API docs

OAuth

OAuth 2.0 for delegated third-party access.

  • Authorization code flow with PKCE
  • Granular scope review before consent
  • Refresh and revocation from Settings
Open Settings

MCP

Nextvisit runs a Model Context Protocol server. Typed tools, same workspace scope.

  • Claude, ChatGPT, local LLMs
  • Typed tools for patients, encounters, notes, codes
  • Same workspace scope as API keys and OAuth
Read MCP guide
MCP

An open standard for AI assistants on the chart.

Assistants read structured data through typed tools, instead of a one-off integration per product.

Nextvisit exposes the workspace as an MCP server. An assistant connects once and reads patients, encounters, notes, and codes through typed tools, under the same workspace scope as API keys and OAuth.

A clinician can point Claude, ChatGPT, or a local model at the workspace and ask questions against real chart data. Tool calls return structured JSON.

Sample MCP tool call
// Assistant invokes a Nextvisit MCP tool
query_encounters({
  patient_id: "pat_018f...c1",
  range: { from: "2026-01-01", to: "2026-05-01" },
  include: ["note", "codes", "peer_review"]
})

// Returns
{
  "encounters": [
    {
      "id": "enc_a1b2",
      "date": "2026-04-18T14:32:00Z",
      "status": "signed",
      "codes": ["F33.1", "F41.1"],
      "note": "..."
    }
  ]
}

Illustrative shape, not the verified call signature. Read the MCP server guide for the endpoint URL, the live tool list, and connection steps for Claude, ChatGPT, and local LLM clients.

API

Bearer auth over HTTPS.

Generate the key under Settings, Tools and AI, then call any documented endpoint.

curl: list signed encounters for a patient
# List signed encounters for a patient over a date range
curl -sS \
  -H "Authorization: Bearer nv_live_8f2c...41a" \
  -H "Accept: application/json" \
  "https://api.nextvisit.ai/v1/encounters?patient_id=pat_018f...c1&status=signed&from=2026-01-01"

# Response (truncated)
{
  "data": [
    {
      "id": "enc_a1b2",
      "signed_at": "2026-04-18T14:42:11Z",
      "provider_id": "prv_77a3",
      "codes": ["F33.1", "F41.1"]
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjUwfQ"
}

Illustrative endpoint and key shape. The live API reference covers pagination, rate limits, and the full resource list.

Free integrations

Bring your own recorder.

Pocket and Plaud notes flow in at no license fee.

Pocket

The heypocket.com hardware recorder posts each recording on completion. AriaMD generates a note in the assigned template, like a live session.

Say the patient name and date of birth in the first minute.

Plaud AI

Plaud AI pin and Plaud Note recordings sync into the workspace. Useful if you already carry one for personal capture.

Same convention: name and DOB at the top of the recording.

See the four ways to start a note on the how-it-works page

EHR

Notes, codes, and bundles out to the EHR.

FHIR R4 and HL7 v2 cover most stacks. Partner integrations cover the rest. Copy-out plus fax handles the long tail. Destination list, bundle layout, and live push state are on the features page.

See EHR integration on the features page

See it on your workflow

One mock visit, one note in your template.

We run a mock session, draft the note, and show the claim. No slides.

Book a demo Talk to sales
Live in 2 weeks or less BAA signed by default

Popular pages

Try , , ,