Stedi · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Stedi Healthcare Coordination of benefits API

2 actions 2 updates phrasing extends openapi/stedi-coordination-of-benefits-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Stedi's API. It is a proposal applied on top of the contract, not a document Stedi publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 2

$.info
$.paths['/coordination-of-benefits'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Stedi Healthcare Coordination of benefits API
  version: 1.0.0
extends: openapi/stedi-coordination-of-benefits-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 1
- target: $.paths['/coordination-of-benefits'].post
  update:
    x-apievangelist-phrasing:
      intent: Check coordination of benefits
      effect: read
      questions:
      - How can I find out whether a patient has other insurance that should pay first?
      - Can I check which plan is primary when a patient is covered by more than one payer?
      - Does a coordination of benefits check work for dependents on a subscriber's plan?
      instructions:
      - text: Run a coordination of benefits check with payer {tradingPartnerServiceId} for subscriber {subscriber}.
        slots:
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
          subscriber: requestBody.subscriber
      - text: Check for overlapping coverage for dependent {dependent} of subscriber {subscriber}.
        slots:
          dependent: requestBody.dependent
          subscriber: requestBody.subscriber
      - text: Find out which plan is primary for encounter {encounter} from provider {provider}.
        slots:
          encounter: requestBody.encounter
          provider: requestBody.provider
      method: generated
      generated: '2026-09-26'