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 8 APIs on the APIs.io network, including Allergy API, Capability API, Condition API, and 5 more. Tagged areas include Company, EHR, 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 📡 Source on GitHub

50.9/100 developing ▬ flat Agent 40/100 agent ready Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0

9 APIs 1 MCP Servers

CompanyEHRHealthcareFHIRHL7Interoperability

Kin Score

Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0

Composite quality — 50.9/100 · developing

Contract Quality 6.1 / 21

Developer Ergonomics 10.4 / 17

Access Clarity 8.5 / 17

Operational Transparency 1.7 / 11

Contract Governance 2.2 / 10

Discoverability 6.9 / 9

Regulatory Posture 11.4 / 15

Agent readiness — 40/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

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.

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/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/meditech: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 9

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

Open Collections 10

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

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Rate Limits 1

Documented rate limits and quota policies.

JSON Schema 1

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

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

WellKnown

WellKnown

MCPServer

LLMsTxt

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
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
- EHR
- Healthcare
- FHIR
- HL7
- Interoperability
accessModel:
  pricing: unknown
  onboarding: request
  trial: false
  try_now: false
  public: false
  label: Unknown pricing · Registration request required
  confidence: high
  source:
  - https://ehr.meditech.com/ehr-solutions/greenfield-workspace
  - https://greenfield.meditech.com/explorer/topic/welcome
  generated: '2026-07-27'
  method: manual
  note: 'MEDITECH publishes no API pricing, no plan tiers, and no rate limits. Sandbox access and the ability to execute calls
    against a real EHR require a Greenfield Workspace registration request (an iFiller form) that MEDITECH reviews — it is
    not self-serve signup. The reference documentation itself, however, IS publicly reachable at greenfield.meditech.com/explorer
    without a login. The catch: it is an Angular single-page app that renders entirely client-side, and the host serves robots.txt
    with `Disallow: /`. So the docs are readable by a human with a browser but invisible to crawlers, to indexes, and to any
    AI agent that fetches URLs or respects robots — machine-undiscoverable rather than access-controlled.'
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:
  - EHR
  - Healthcare
  - FHIR
  - HL7
  image: https://raw.githubusercontent.com/api-evangelist/meditech/refs/heads/main/image.png
  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:
  - 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:
  - 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: MCPServer
  url: mcp/meditech-mcp.yml
- 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

APIs 9

Open Collections 10

MCP Servers 1

Pricing Plans 1

Rate Limits 1

Semantic Vocabularies 1

Spectral Rules 1

JSON Schema 1

Security Posture 4

Scopes 1

Agentic Access 1

Get Started 4

Documentation 5

Agent Surfaces 6

Design & Contract 7

Build 2

Access & Security 8

Operate 3

Commercial 3

Company 3

Other 13

Source (apis.yml)