tebra-mcp-server

Create Encounter

tebra_create_encounter

Create a medical encounter in Tebra with ICD-10 diagnoses and CPT procedures, generating billable service lines. Returns the new encounter ID.

Instructions

Create a new encounter (superbill) in Tebra with diagnoses and procedures. Each procedure becomes a service line carrying up to 4 ICD-10 diagnosis codes (from the encounter-level diagnoses array, or per-procedure diagnosisCodes). practiceName or practiceId is strongly recommended — Tebra requires the practice on most accounts. Returns the created encounter ID.

Input Schema

TableJSON Schema

Name	Required	Description
`caseId`	No	Optional patient case ID to bill under
`diagnoses`	Yes	Encounter-level diagnosis codes; the first 4 are applied to each service line
`patientId`	Yes	Tebra patient ID
`practiceId`	No	Practice ID (alternative to practiceName)
`procedures`	Yes	Array of procedures; each becomes one service line
`providerId`	Yes	Rendering provider ID
`serviceDate`	Yes	Date of service (ISO 8601, e.g. 2026-03-25)
`practiceName`	No	Practice name (strongly recommended; required by Tebra on most accounts)
`authorizationId`	No	Optional authorization number to link
`encounterStatus`	No	Initial encounter status (default 'Draft'; 'Approved' triggers billing)
`serviceLocationId`	No	Optional service location ID
`placeOfServiceCode`	No	Optional place of service code (e.g. 11 for office)

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.6.0Sep 21, 2026

changedInput schema / properties / authorizationId / description

Previous value: -"Optional authorization ID to link"New value: +"Optional authorization number to link"

addedInput schema / properties / caseId

Added value: +{
+  "description": "Optional patient case ID to bill under",
+  "type": "string"
+}

changedInput schema / properties / diagnoses / description

Previous value: -"Array of diagnosis codes"New value: +"Encounter-level diagnosis codes; the first 4 are applied to each service line"

changedInput schema / properties / diagnoses / items / properties / description / description

Previous value: -"Diagnosis description"New value: +"Diagnosis description (informational only — not sent to Tebra)"

changedInput schema / properties / diagnoses / items / required

Previous value: -[
-  "code",
-  "description"
-]New value: +[
+  "code"
+]

addedInput schema / properties / encounterStatus

Added value: +{
+  "description": "Initial encounter status (default 'Draft'; 'Approved' triggers billing)",
+  "enum": [
+    "Draft",
+    "Submitted",
+    "Approved"
+  ],
+  "type": "string"
+}

addedInput schema / properties / placeOfServiceCode

Added value: +{
+  "description": "Optional place of service code (e.g. 11 for office)",
+  "type": "string"
+}

addedInput schema / properties / practiceId

Added value: +{
+  "description": "Practice ID (alternative to practiceName)",
+  "type": "string"
+}

addedInput schema / properties / practiceName

Added value: +{
+  "description": "Practice name (strongly recommended; required by Tebra on most accounts)",
+  "type": "string"
+}

changedInput schema / properties / procedures / description

Previous value: -"Array of procedure codes"New value: +"Array of procedures; each becomes one service line"

addedInput schema / properties / procedures / items / properties / diagnosisCodes

Added value: +{
+  "description": "Optional per-line ICD-10 codes (max 4; overrides encounter-level diagnoses)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / procedures / items / properties / modifiers / description

Previous value: -"CPT modifiers (e.g. [\"-25\", \"-59\"])"New value: +"CPT modifiers (e.g. [\"25\", \"59\"])"

addedInput schema / properties / procedures / items / properties / unitCharge

Added value: +{
+  "description": "Optional unit charge in dollars (defaults to fee schedule)",
+  "type": "number"
+}

changedInput schema / properties / providerId / description

Previous value: -"Tebra provider ID"New value: +"Rendering provider ID"

addedInput schema / properties / serviceLocationId

Added value: +{
+  "description": "Optional service location ID",
+  "type": "string"
+}

First observedv0.2.5Jun 14, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral context: each procedure becomes a service line with diagnosis mapping, the practice requirement on most accounts, and the return of the created encounter ID. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler. The primary purpose is front-loaded, followed by the critical service-line behavior and the practice requirement, then the return value. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with no output schema, the description covers the essential behavior: creation, service-line structure, diagnosis mapping, and practice requirement. It doesn't explicitly mention error conditions or default status, but the schema covers the 'Draft' default and enum options. The description is adequate for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all parameters are documented. The description adds meaning beyond the schema by explaining how diagnoses and procedures interact (encounter-level diagnoses applied per service line, per-procedure override) and the strong recommendation for practice identification. This helps the agent understand the intent behind parameter combinations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Create a new encounter (superbill) in Tebra with diagnoses and procedures.' It uses a specific verb and resource, and distinguishes itself from sibling tools like tebra_update_encounter_status or tebra_get_encounter by focusing on creation. The mention of 'superbill' adds domain specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (when you need to create an encounter) but does not explicitly state when not to use it or mention alternatives. It gives parameter-level guidance (practiceName/practiceId strongly recommended) but lacks tool-selection context compared to sibling operations. No exclusions or alternative tool names are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Create Encounter

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools