Kodjin Terminology API

The Terminology API from Kodjin — 1 operation(s) for terminology.

Operations 1

GET /terminology/ValueSet/clinical-findings/$expand GET /terminology/ValueSet/clinical-findings/$expand #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/kodjin:kodjin-terminology-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

OpenAPI Specification

kodjin-terminology-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Kodjin Terminology API
  version: '2026-10-14'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-14: 17 operation(s) read from 18 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Kodjin has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 21
    documentation: -4
    pages-with-code: 16
    pages-read: 18
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-14'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://docs.kodjin.com/kodjin-restful-api
  - https://docs.kodjin.com/uscdi_v3/onc-kodjin-restful-api
  - https://docs.kodjin.com/uscdi_v3/uscdi-clinical-notes-document-reference
  - https://docs.kodjin.com/uscdi_v3/app-client-registration
  - https://docs.kodjin.com/uscdi_v3/uscdi-observation-clinical-result
  - https://docs.kodjin.com/operation-resource-reindex
  - https://docs.kodjin.com/uscdi_v3/uscdi-clinical-tests-diagnostic-report
  - https://docs.kodjin.com/coded_data_types
  - https://docs.kodjin.com/authentication-authorization
  - https://docs.kodjin.com/smart-on-fhir-authorization
  - https://docs.kodjin.com/kodjin-search
  - https://docs.kodjin.com/versioning
  - https://docs.kodjin.com/everything-on-patient
  - https://docs.kodjin.com/operation-validate
  - https://docs.kodjin.com/operation-document
  - https://docs.kodjin.com/operation-apply-fhirpath
  - https://docs.kodjin.com/opeation-versions
  - https://docs.kodjin.com/operation-ips
servers:
- url: https://sandbox.fhir.elationemr.com
security:
- bearer: []
tags:
- name: Terminology
paths:
  /terminology/ValueSet/clinical-findings/$expand:
    get:
      operationId: get_terminology_ValueSet_clinical_findings_expand
      tags:
      - Terminology
      summary: GET /terminology/ValueSet/clinical-findings/$expand
      x-source: https://docs.kodjin.com/coded_data_types
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --location --request GET 'https://fhir.example.com/terminology/ValueSet/clinical-findings/$expand'\n Thus, coded data types in FHIR can be presented through a code , coding , or codeableConcept data type. \nCoding and CodeableConcept references a Code System that assigns codes representing the concepts in the system, such as LOINC or SNOMED. The Value Set defines a context in which a CodeSystem"
components:
  securitySchemes:
    bearer:
      type: http
      scheme: bearer