Skip to content
Eden Engine

FHIR Terminology Server Capabilities (tx.fhir.org R4)

fhirtx/capabilities

The CapabilityStatement of the public HL7 FHIR Terminology Server (tx.fhir.org, FHIR R4): server software and version, FHIR version 4.0.1, supported formats, the resources it serves and the terminology operations it supports ($lookup, $validate-code, $expand, $translate and others). Typical size is 4 KB. Takes no input. HL7 FHIR terminology server data served by Eden Engine; not an official HL7 product.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.

Data source

HL7 FHIR Terminology Server (tx.fhir.org)

Source: HL7 FHIR Terminology Server (tx.fhir.org). Contains content from LOINC (http://loinc.org); LOINC is copyright Regenstrief Institute, Inc. and the LOINC Committee and is available under the license at http://loinc.org/license. Served by Eden Engine; not an official HL7 product.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "fhirtx/capabilities" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "fhirtx/capabilities" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "fhirtx/capabilities", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "fhirtx/capabilities", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

ChargePrice
Per call
$0.0026
Updated
Oct 21, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "required": [
    "resourceType"
  ],
  "properties": {
    "rest": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": true
      }
    },
    "format": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "software": {
      "type": "object",
      "additionalProperties": true
    },
    "fhirVersion": {
      "type": "string"
    },
    "resourceType": {
      "type": "string",
      "description": "CapabilityStatement."
    },
    "implementation": {
      "type": "object",
      "additionalProperties": true
    }
  },
  "description": "A FHIR CapabilityStatement.",
  "additionalProperties": true
}