MEDITECH

MEDITECH (Medical Information Technology, Inc.) is an electronic health record vendor serving community hospitals and health systems, primarily through its MEDITECH Expanse platform. Its API program is delivered through the Greenfield Workspace — a registration-gated developer environment where approved app developers get interactive documentation and a sandbox to execute APIs against a real MEDITECH EHR. Published surfaces are US Core FHIR R4 (view-only patient-facing data, USCDI v1, DSTU2/R4 compatible) and FHIR Scheduling APIs. MEDITECH also operates Traverse Exchange, its national data exchange network and TEFCA on-ramp, connecting 700+ facilities across 41 US states plus Canadian deployments.

MEDITECH publishes 9 API contracts indexed on the APIs.io network, including Allergy API, Capability API, Condition API, and 6 more. Tagged areas include Company, Electronic Health Records, Healthcare, FHIR, and HL7.

The MEDITECH catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

MEDITECH’s developer surface includes authentication, developer portal, documentation, API reference, signup flow, getting-started guide, engineering blog, and 47 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

43.6/100 developing ▬ flat Agent 32/100 agent ready Front door AI 2/6 trace Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 published contract 2 Agent Skills

Company Electronic Health Records Healthcare FHIR HL7 Interoperability

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 43.6/100 · developing

Contract Quality 5.9 / 21

Developer Ergonomics 9.8 / 17

Access Clarity 8.5 / 17

Operational Transparency 1.7 / 11

Contract Governance 1.0 / 10

Discoverability 5.6 / 9

Regulatory Posture 7.2 / 15

Agent readiness — 32/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/meditech/"><img src="https://apis.io/badge/meditech/card.svg" alt="MEDITECH on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

3 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 27.6 — up to +18.1 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points
Contract Governance scores 9.8 — up to +10.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/meditech/apis.yml: open an issue on github.com/api-evangelist/meditech to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Medical Technology (certified health IT, FDA-authorized AI devices)	standard	53.7	-	-
Payer Interoperability (CAQH CORE, X12, Da Vinci, WEDI)	standard	53.7	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

MEDITECH Expanse FHIR API

MEDITECH's FHIR API surface for Expanse, exposed to approved developers through the Greenfield Workspace. US Core FHIR R4 provides view-only access to patient-facing data after ...

meditech Allergy API

Allergy and intolerance records

meditech Capability API

FHIR server capability

meditech Condition API

Problem list and diagnoses

meditech Diagnostic API

Diagnostic reports (lab, radiology, pathology)

meditech Encounter API

Clinical encounters and visits

meditech Medication API

Medication requests and prescriptions

meditech Observation API

Vital signs and laboratory results

meditech Patient API

US Core Patient resources

Scroll for all 9

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Meditech Expanse FHIR R4 Allergy API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Capability API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Condition API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Diagnostic API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Encounter API

OPEN COLLECTION

Meditech Expanse FHIR R4 API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Medication API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Observation API

OPEN COLLECTION

Meditech Expanse FHIR R4 Allergy Patient API

OPEN COLLECTION

Scroll for all 9

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

meditech-patient-clinical-summary

AGENT SKILL

meditech-patient-record-search

AGENT SKILL

MEDITECH API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Meditech Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Meditech Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Meditech Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Meditech Context

16 classes · 6 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

MEDITECH — jsonschema rules

6 rules · 4 warnings 2 info

SPECTRAL

OpenAPI Overlays 8

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Meditech Allergy Api Overlay

2 actions · update · meditech-allergy-api-openapi.yml

GENERATED

Meditech Capability Api Overlay

1 action · update · meditech-capability-api-openapi.yml

GENERATED

Meditech Condition Api Overlay

2 actions · update · meditech-condition-api-openapi.yml

GENERATED

Meditech Diagnostic Api Overlay

2 actions · update · meditech-diagnostic-api-openapi.yml

GENERATED

Meditech Encounter Api Overlay

2 actions · update · meditech-encounter-api-openapi.yml

GENERATED

Meditech Medication Api Overlay

2 actions · update · meditech-medication-api-openapi.yml

GENERATED

Meditech Observation Api Overlay

2 actions · update · meditech-observation-api-openapi.yml

GENERATED

Meditech Patient Api Overlay

5 actions · update · meditech-patient-api-openapi.yml

GENERATED

Scroll for all 8

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

Meditech FHIR R4 Patient

16 properties

JSON SCHEMA

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Meditech Authentication

oauth2 · 1 scheme

SECURITY

Meditech Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Meditech Vulnerability Disclosure

Hackerone

SECURITY

Meditech Trust Center

ONC Health IT Certification (2015 Edition Cures Update)

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Meditech Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Meditech Agentic Access

10 operations

10 operations · 0 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Portal

SignUp

GettingStarted

Sandbox

Documentation 5

Reference material describing how the API behaves

Documentation

APIReference

OpenAPI

JSONSchema

Documentation

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

Errors

JSONLDContext

ErrorCatalog

Lifecycle

Conventions

DataModel

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

PostmanCollection

PostmanCollection

OpenCollection

OpenCollection

Access & Security 8

Authentication, authorization, and security posture

DomainSecurity

Authentication

Authentication

OAuthScopes

Scopes

Authentication

TrustCenter

Compliance

Scroll for all 8

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Plans

Plans

TermsOfService

TermsOfService

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 13

Properties that don't map to a standard resource type

CapabilityStatement

Endpoints

Resources

HL7Interfaces

Interoperability

Overlay

Overlay

Overlay

Overlay

Overlay

Overlay

Overlay

Overlay

Scroll for all 13

Source (apis.yml)

aid: meditech
name: MEDITECH
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
specificationVersion: '0.23'
description: MEDITECH (Medical Information Technology, Inc.) is an electronic health record vendor serving community hospitals
  and health systems, primarily through its MEDITECH Expanse platform. Its API program is delivered through the Greenfield
  Workspace — a registration-gated developer environment where approved app developers get interactive documentation and a
  sandbox to execute APIs against a real MEDITECH EHR. Published surfaces are US Core FHIR R4 (view-only patient-facing data,
  USCDI v1, DSTU2/R4 compatible) and FHIR Scheduling APIs. MEDITECH also operates Traverse Exchange, its national data exchange
  network and TEFCA on-ramp, connecting 700+ facilities across 41 US states plus Canadian deployments.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/meditech.png
url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/apis.yml
tags:
- Company
- Electronic Health Records
- Healthcare
- FHIR
- HL7
- Interoperability
tags_raw:
- Company
- EHR
- Healthcare
- FHIR
- HL7
- Interoperability
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
x-capabilities:
  reviewed: '2026-08-06'
  source: https://greenfield-prod-apis.meditech.com/v2/uscore/STU6/metadata
  previously_reviewed: '2026-07-27'
  previous_source: https://ehr.meditech.com/ehr-solutions/greenfield-workspace-resources
  write_access: two-resources-only
  note: 'IMPORTANT for anyone evaluating MEDITECH for agent or integration work. Read from MEDITECH''s own FHIR CapabilityStatement
    on 2026-08-06, not inferred from documentation: the Greenfield developer program exposes 33 resources, and exactly TWO
    of them accept writes — Communication (create) and QuestionnaireResponse (create, update). Everything else is read and
    search only. In particular: Appointment supports read and search-type but NEITHER create NOR update, and Patient supports
    read and search-type with NO create. So there is no supported public path to book an appointment, reschedule one, or register
    a patient. A read-only grant is the expected outcome of applying, not a sign of applying to the wrong program. CORRECTION:
    this block previously stated MEDITECH exposes NO write surface at all. That was inferred from the Greenfield resources
    page rather than read from the contract. It was wrong in detail — a narrow write surface does exist — though the practical
    conclusion for scheduling and patient creation is unchanged. See conformance/meditech-greenfield-conformance.yml for the
    full resource and interaction table.'
  contract_vs_marketing: The Greenfield resources page lists FHIR Scheduling as "coming soon" and Expanse-only, while the
    live CapabilityStatement already exposes Appointment for read and search. The published contract and the marketing page
    disagree; the contract is the one an integrator can act on.
  surfaces:
  - name: FHIR Patient Access API (DSTU2)
    access: read-only
    workflow: patient-facing
    data: Common Clinical Data Set
    availability: all customers
    docs: https://greenfield.meditech.com/explorer/topic/patient-health-data
  - name: FHIR Patient Access API (R4 / US Core)
    access: read-only
    workflow: patient-facing
    data: USCDI R4
    availability: all customers
    docs: https://greenfield.meditech.com/explorer/topic/USCore-patient-health-data
  - name: HL7v2 Outbound Interfaces
    access: read-only
    workflow: outbound only (ADT, lab results, medications, orders)
    availability: all customers
    docs: https://ehr.meditech.com/hl7-outbound-list-for-greenfield
  - name: FHIR Scheduling APIs
    access: not yet available
    status: coming soon
    availability: MEDITECH Expanse customers only
    note: MEDITECH's marketing describes Expanse scheduling write-back (Argo-Scheduling, FHIR STU3 — retrieve slots, book
      visits, manage provider availability) and partners such as Luma Health have shipped it. That is delivered through customer-sponsored
      or formal-partner integration at the hospital, NOT through self-serve Greenfield access. Greenfield itself still lists
      FHIR Scheduling as "coming soon".
x-provenance:
  reviewed: '2026-07-27'
  reviewed_by: Kin Lane
  openapi_origin: api-evangelist-derived
  note: The OpenAPI definitions in this repo are API Evangelist models of the US Core FHIR R4 profile that MEDITECH states
    it supports. They are NOT MEDITECH-published contracts — MEDITECH does not publish an OpenAPI. Its authoritative reference
    is the Greenfield API Explorer at https://greenfield.meditech.com/explorer, which is publicly reachable but client-rendered
    and robots-disallowed, so it cannot be fetched or crawled — it has to be read in a browser. The `{facility}` server template
    reflects the per-customer deployment model; actual service base URLs are issued per organization. Authentication, scopes,
    and agentic-access artifacts here are derived FROM these models, so they inherit the same derived provenance. Treat all
    of it as a starting scaffold to reconcile against the Explorer, not as an authoritative interface contract.
  authoritative_reference: https://greenfield.meditech.com/explorer/topic/welcome
  explorer_sections:
  - https://greenfield.meditech.com/explorer/topic/welcome
  - https://greenfield.meditech.com/explorer/topic/patient-health-data
  - https://greenfield.meditech.com/explorer/topic/USCore-patient-health-data
  - https://greenfield.meditech.com/explorer/api
  - https://greenfield.meditech.com/explorer/endpoints
  - https://greenfield.meditech.com/explorer/scope
  - https://greenfield.meditech.com/explorer/authorization
  - https://greenfield.meditech.com/explorer/status-codes
  explorer_sections_note: Route list confirmed from the Explorer's shipped Angular bundle (main.*.js), not guessed. /explorer/endpoints
    and /explorer/scope are the two that matter most for reconciliation — they are MEDITECH's own endpoint directory and scope
    list, and should supersede the derived scopes/ and openapi/ artifacts in this repo once someone transcribes them.
apis:
- aid: meditech:meditech-api
  name: MEDITECH Expanse FHIR API
  tags:
  - Electronic Health Records
  - Healthcare
  - FHIR
  - HL7
  tags_raw:
  - EHR
  - Healthcare
  - FHIR
  - HL7
  humanURL: https://ehr.meditech.com/ehr-solutions/greenfield-workspace
  baseURL: https://{facility}.meditech.com/fhir/r4
  properties:
  - url: https://greenfield.meditech.com/explorer/topic/welcome
    type: Documentation
  - url: https://greenfield.meditech.com/explorer/endpoints
    type: Endpoints
  - url: https://greenfield.meditech.com/explorer/scope
    type: Scopes
  - url: https://greenfield.meditech.com/explorer/authorization
    type: Authentication
  - url: https://greenfield.meditech.com/explorer/status-codes
    type: Errors
  - url: https://ehr.meditech.com/ehr-solutions/greenfield-workspace
    type: SignUp
  description: MEDITECH's FHIR API surface for Expanse, exposed to approved developers through the Greenfield Workspace. US
    Core FHIR R4 provides view-only access to patient-facing data after the patient authorizes the requesting app (USCDI v1,
    DSTU2/R4 compatible, patient workflows only). Separate FHIR Scheduling APIs support user and patient workflows for Expanse
    customers. Service base URLs are issued per customer facility.
- aid: meditech:meditech-allergy-api
  name: meditech Allergy API
  description: Allergy and intolerance records
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Allergy
  properties:
  - type: OpenAPI
    url: openapi/meditech-allergy-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-capability-api
  name: meditech Capability API
  description: FHIR server capability
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Capabilities
  tags_raw:
  - Capability
  properties:
  - type: OpenAPI
    url: openapi/meditech-capability-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-condition-api
  name: meditech Condition API
  description: Problem list and diagnoses
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Condition
  properties:
  - type: OpenAPI
    url: openapi/meditech-condition-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-diagnostic-api
  name: meditech Diagnostic API
  description: Diagnostic reports (lab, radiology, pathology)
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Diagnostics
  tags_raw:
  - Diagnostic
  properties:
  - type: OpenAPI
    url: openapi/meditech-diagnostic-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-encounter-api
  name: meditech Encounter API
  description: Clinical encounters and visits
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Encounter
  properties:
  - type: OpenAPI
    url: openapi/meditech-encounter-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-medication-api
  name: meditech Medication API
  description: Medication requests and prescriptions
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Medication
  properties:
  - type: OpenAPI
    url: openapi/meditech-medication-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-observation-api
  name: meditech Observation API
  description: Vital signs and laboratory results
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Observation
  properties:
  - type: OpenAPI
    url: openapi/meditech-observation-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
- aid: meditech:meditech-patient-api
  name: meditech Patient API
  description: US Core Patient resources
  humanURL: https://greenfield.meditech.com/explorer/topic/welcome
  baseURL: https://{facility}.meditech.com/fhir/r4
  tags:
  - Patients
  tags_raw:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/meditech-patient-api-openapi.yml
  - type: Documentation
    url: https://greenfield.meditech.com/explorer/api
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
common:
- type: AgenticAccess
  url: agentic-access/meditech-agentic-access.yml
- type: DomainSecurity
  url: security/meditech-domain-security.yml
- type: Conformance
  url: conformance/meditech-greenfield-conformance.yml
- type: CapabilityStatement
  url: conformance/meditech-greenfield-capabilitystatement.json
- type: WellKnown
  url: well-known/meditech-greenfield-smart-configuration.json
- type: Authentication
  url: authentication/meditech-greenfield-oauth.yml
- type: Authentication
  url: authentication/meditech-authentication.yml
- type: OAuthScopes
  url: scopes/meditech-scopes.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/meditech
- url: https://greenfield.meditech.com/
  type: Portal
- url: https://www.meditech.com/
  type: Website
- url: https://greenfield.meditech.com/explorer/topic/welcome
  type: Documentation
- url: https://greenfield.meditech.com/explorer/api
  type: APIReference
- url: https://greenfield.meditech.com/explorer/endpoints
  type: Endpoints
- url: https://greenfield.meditech.com/explorer/scope
  type: Scopes
- url: https://greenfield.meditech.com/explorer/authorization
  type: Authentication
- url: https://greenfield.meditech.com/explorer/status-codes
  type: Errors
- url: https://ehr.meditech.com/ehr-solutions/greenfield-workspace
  type: SignUp
- url: https://ehr.meditech.com/ehr-solutions/how-to-work-in-the-greenfield-workspace
  type: GettingStarted
- url: https://ehr.meditech.com/ehr-solutions/greenfield-workspace-resources
  type: Resources
- url: https://ehr.meditech.com/hl7-outbound-list-for-greenfield
  type: HL7Interfaces
- url: https://ehr.meditech.com/ehr-solutions/meditech-interoperability
  type: Interoperability
- url: https://blog.meditech.com/
  type: Blog
- url: https://ehr.meditech.com/contact
  type: Support
- url: https://ehr.meditech.com/privacy-policy
  type: PrivacyPolicy
- url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/openapi/_original/meditech-fhir-openapi.yml
  type: OpenAPI
- url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-schema/meditech-patient-schema.json
  type: JSONSchema
- url: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/json-ld/meditech-context.jsonld
  type: JSONLDContext
- url: collections/meditech-fhir.postman_collection.json
  type: PostmanCollection
- url: collections/meditech-fhir.opencollection.json
  type: OpenCollection
- type: WellKnown
  url: well-known/meditech-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/meditech-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/meditech-llms.txt
- type: Overlay
  url: overlays/meditech-allergy-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-capability-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-condition-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-diagnostic-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-encounter-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-medication-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-observation-api-overlay.yaml
- type: Overlay
  url: overlays/meditech-patient-api-overlay.yaml
- type: ErrorCatalog
  url: errors/meditech-problem-types.yml
- type: Lifecycle
  url: lifecycle/meditech-lifecycle.yml
- type: ChangeLog
  url: changelog/meditech-changelog.yml
- type: TrustCenter
  url: security/meditech-trust-center.yml
- type: Compliance
  url: security/meditech-trust-center.yml
- type: Sandbox
  url: sandbox/meditech-sandbox.yml
- type: Conventions
  url: conventions/meditech-conventions.yml
- type: DataModel
  url: data-model/meditech-data-model.yml
- type: Plans
  url: plans/meditech-plans-pricing.yml
- type: RateLimits
  url: rate-limits/meditech-rate-limits.yml
- type: AgentSkill
  url: skills/_index.yml
- url: https://home.meditech.com/en/d/restapiresources/pages/apidoc.htm
  type: Documentation
- url: https://home.meditech.com/en/d/restapiresources/pages/apiterms.htm
  type: TermsOfService
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
created: '2026-05-04'
modified: '2026-08-14'
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 26
  pass: local-v1

MEDITECH API — frequently asked questions

Does MEDITECH have an API?

Yes. APIs.io lists 9 APIs from MEDITECH, including MEDITECH Expanse FHIR API, meditech Allergy API and meditech Capability API, and 6 more.

Is there an OpenAPI specification for the MEDITECH API?

Yes. APIs.io indexes 8 OpenAPI specifications for MEDITECH, each linked for download from this page.

How do I authenticate with the MEDITECH API?

MEDITECH documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Meditech Authentication.

Is the MEDITECH API ready for AI agents?

MEDITECH has a Kin Score of 43.6 out of 100 (developing) and an Agent Readiness score of 32.3 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/meditech"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/meditech/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/meditech/evidence"

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.

GitHub Google LinkedIn

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