Kareo · Schema

KareoEncounter

A clinical encounter record in the Kareo practice management and EHR system.

HealthcareMedical SoftwareEHRPractice ManagementMedical BillingPatient SchedulingClinical DataInsurance EligibilityHIPAA

Properties

Name Type Description
EncounterId integer Internal Kareo encounter identifier.
PatientId integer Internal Kareo patient identifier.
ProviderId integer Rendering provider identifier.
AppointmentId integer Associated appointment identifier, if applicable.
EncounterStatus string Workflow status of the encounter.
DateOfService string Date on which the clinical service was rendered.
DiagnosisCodes array ICD-10 diagnosis codes associated with the encounter.
ProcedureCodes array CPT procedure codes billed in the encounter.
View JSON Schema on GitHub

JSON Schema

kareo-encounter-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://api-evangelist.github.io/kareo/json-schema/kareo-encounter-schema.json",
  "title": "KareoEncounter",
  "description": "A clinical encounter record in the Kareo practice management and EHR system.",
  "type": "object",
  "properties": {
    "EncounterId": {
      "type": "integer",
      "description": "Internal Kareo encounter identifier.",
      "example": 8009001
    },
    "PatientId": {
      "type": "integer",
      "description": "Internal Kareo patient identifier.",
      "example": 100234
    },
    "ProviderId": {
      "type": "integer",
      "description": "Rendering provider identifier.",
      "example": 201
    },
    "AppointmentId": {
      "type": "integer",
      "description": "Associated appointment identifier, if applicable.",
      "example": 5001234
    },
    "EncounterStatus": {
      "type": "string",
      "enum": [
        "Draft",
        "Submitted",
        "Approved",
        "Voided"
      ],
      "description": "Workflow status of the encounter.",
      "example": "Submitted"
    },
    "DateOfService": {
      "type": "string",
      "format": "date",
      "description": "Date on which the clinical service was rendered.",
      "example": "2026-06-15"
    },
    "DiagnosisCodes": {
      "type": "array",
      "description": "ICD-10 diagnosis codes associated with the encounter.",
      "items": {
        "type": "string"
      },
      "example": ["J06.9", "Z00.00"]
    },
    "ProcedureCodes": {
      "type": "array",
      "description": "CPT procedure codes billed in the encounter.",
      "items": {
        "type": "string"
      },
      "example": ["99213"]
    }
  },
  "required": [
    "PatientId",
    "ProviderId",
    "DateOfService"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kareo-encounter"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.