meditech Allergy API

openapi: 3.2.0
info:
  title: Meditech Expanse FHIR R4 Allergy API
  description: Meditech Expanse FHIR API enables standards-based interoperability for sharing patient data across healthcare systems. Supports TEFCA-aligned data exchange through the Traverse Exchange national network, connecting over 700 facilities across 41 US states. Built on HL7 FHIR R4 standards.
  version: 4.0.0
  contact:
    name: Meditech Support
    url: https://ehr.meditech.com/contact
  license:
    name: Proprietary
    url: https://ehr.meditech.com/privacy-policy
servers:
- url: https://{facility}.meditech.com/fhir/r4
  variables:
    facility:
      default: yourhospital
      description: Your Meditech facility subdomain
security:
- SMART_OAuth2:
  - patient/*.read
  - user/*.read
  - launch
tags:
- name: Allergy
  description: Allergy and intolerance records
paths:
  /Patient/{id}/AllergyIntolerance:
    get:
      operationId: getPatientAllergies
      summary: Get patient allergies and intolerances
      description: Retrieve allergy and intolerance records for a patient.
      tags:
      - Allergy
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      - name: clinical-status
        in: query
        schema:
          type: string
          enum:
          - active
          - inactive
          - resolved
      responses:
        '200':
          description: Bundle of AllergyIntolerance resources
          content:
            application/fhir+json:
              schema:
                $ref: '#/components/schemas/Bundle'
components:
  schemas:
    Bundle:
      type: object
      description: FHIR Bundle resource
      properties:
        resourceType:
          type: string
          enum:
          - Bundle
        id:
          type: string
        type:
          type: string
          enum:
          - searchset
          - collection
          - transaction
          - batch
          - history
        total:
          type: integer
        link:
          type: array
          items:
            type: object
            properties:
              relation:
                type: string
              url:
                type: string
        entry:
          type: array
          items:
            type: object
            properties:
              fullUrl:
                type: string
              resource:
                type: object
                additionalProperties: true
  securitySchemes:
    SMART_OAuth2:
      type: oauth2
      description: SMART on FHIR OAuth 2.0 authorization
      flows:
        authorizationCode:
          authorizationUrl: https://yourhospital.meditech.com/oauth/authorize
          tokenUrl: https://yourhospital.meditech.com/oauth/token
          scopes:
            patient/*.read: Read access to all patient-owned resources
            user/*.read: Practitioner read access to all resources
            launch: EHR launch context
            openid: OpenID Connect identity
            fhirUser: FHIR user claim
externalDocs:
  description: Meditech Interoperability Documentation
  url: https://ehr.meditech.com/ehr-solutions/meditech-interoperability
x-provenance:
  reviewed: '2026-07-27'
  origin: api-evangelist-derived
  publisher-published: false
  note: API Evangelist model of the US Core FHIR R4 profile MEDITECH states it supports. This is NOT a MEDITECH-published OpenAPI — MEDITECH publishes none. Its authoritative reference is the Greenfield API Explorer at https://greenfield.meditech.com/explorer/topic/welcome, which is publicly reachable but client-rendered and robots-disallowed, so it cannot be fetched or crawled — reconcile this file against it by hand. The {facility} server variable reflects MEDITECH's per-customer deployment model; real service base URLs are issued per organization. Paths, parameters, and response shapes here follow the FHIR R4 standard and have not been confirmed against a live MEDITECH endpoint. Validate every operation against the target facility's CapabilityStatement (/metadata) before building on it.
  verify-against: https://greenfield.meditech.com/explorer/api
  endpoint-directory: https://greenfield.meditech.com/explorer/endpoints
  scope-list: https://greenfield.meditech.com/explorer/scope
  sandbox-registration: https://ehr.meditech.com/ehr-solutions/greenfield-workspace