API Evangelist conversational phrasing for Stedi Healthcare Claim submission API

# 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 Claim submission API
  version: 1.0.0
extends: openapi/stedi-claim-submission-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: 8
- target: $.paths['/change/medicalnetwork/institutionalclaims/v1/raw-x12-submission'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit an 837I institutional claim in X12
      effect: write
      questions:
      - How do I send a hospital (837I institutional) claim that I already have as raw X12?
      - Can I submit institutional claims in X12 EDI format and still protect against duplicates with an idempotency key?
      instructions:
      - text: 'Submit this 837I institutional claim X12: {x12}.'
        slots:
          x12: requestBody.x12
      - text: Send raw X12 institutional claim {x12} with idempotency key {key}.
        slots:
          x12: requestBody.x12
          key: header.Idempotency-Key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/change/medicalnetwork/institutionalclaims/v1/submission'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit an 837I institutional claim as JSON
      effect: write
      questions:
      - How do I file a hospital or facility claim using JSON in Stedi?
      - What information do I need to submit an 837I institutional claim to a payer?
      - Can I include the attending physician when sending an institutional claim?
      instructions:
      - text: Submit an institutional claim to payer {tradingPartnerServiceId} for subscriber {subscriber}.
        slots:
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
          subscriber: requestBody.subscriber
      - text: File an 837I facility claim with claim details {claimInformation} to payer {tradingPartnerServiceId}.
        slots:
          claimInformation: requestBody.claimInformation
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
      - text: Send an institutional claim with attending physician {attending}.
        slots:
          attending: requestBody.attending
      method: generated
      generated: '2026-09-26'
- target: $.paths['/change/medicalnetwork/professionalclaims/v3/raw-x12-submission'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit an 837P professional claim in X12
      effect: write
      questions:
      - Can I submit a professional 837P claim that's already formatted as X12 EDI?
      - Which endpoint accepts raw X12 for physician office claims?
      instructions:
      - text: 'Submit this 837P professional claim X12: {x12}.'
        slots:
          x12: requestBody.x12
      - text: Send raw X12 professional claim {x12} using idempotency key {key}.
        slots:
          x12: requestBody.x12
          key: header.Idempotency-Key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/change/medicalnetwork/professionalclaims/v3/submission'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit an 837P professional claim as JSON
      effect: write
      questions:
      - How do I submit a doctor's office claim to an insurance payer using JSON?
      - What billing provider and subscriber details does an 837P professional claim require?
      - Can I list a supervising or referring provider on a professional claim?
      instructions:
      - text: Submit a professional claim to payer {tradingPartnerServiceId} billed by {billing}.
        slots:
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
          billing: requestBody.billing
      - text: File an 837P claim for subscriber {subscriber} with service details {claimInformation}.
        slots:
          subscriber: requestBody.subscriber
          claimInformation: requestBody.claimInformation
      - text: Send a professional claim with referring provider {referring}.
        slots:
          referring: requestBody.referring
      method: generated
      generated: '2026-09-26'
- target: $.paths['/dental-claims/raw-x12-submission'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit an 837D dental claim in X12
      effect: write
      questions:
      - Can I send a dental claim that's already in 837D X12 format?
      - Which endpoint takes raw EDI for dental claims?
      instructions:
      - text: 'Submit this 837D dental claim X12: {x12}.'
        slots:
          x12: requestBody.x12
      - text: Send raw X12 dental claim {x12} with idempotency key {key}.
        slots:
          x12: requestBody.x12
          key: header.Idempotency-Key
      method: generated
      generated: '2026-09-26'
- target: $.paths['/dental-claims/submission'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit an 837D dental claim as JSON
      effect: write
      questions:
      - How do I submit a dental claim to an insurer using JSON?
      - Can a dental claim include an assistant surgeon?
      instructions:
      - text: Submit a dental claim to payer {tradingPartnerServiceId} for subscriber {subscriber}.
        slots:
          tradingPartnerServiceId: requestBody.tradingPartnerServiceId
          subscriber: requestBody.subscriber
      - text: File an 837D claim billed by {billing} with procedures {claimInformation}.
        slots:
          billing: requestBody.billing
          claimInformation: requestBody.claimInformation
      - text: Send a dental claim that lists assistant surgeon {assistantSurgeon}.
        slots:
          assistantSurgeon: requestBody.assistantSurgeon
      method: generated
      generated: '2026-09-26'
- target: $.paths['/export/pdf'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a CMS-1500 PDF by claim business ID
      effect: read
      questions:
      - Can I get a printable CMS-1500 form for a claim using its correlation ID?
      - Is there a way to get the claim form PDF with only the form data for printing on pre-printed forms?
      instructions:
      - text: Download the CMS-1500 PDF for claim business ID {businessId}.
        slots:
          businessId: query.businessId
      - text: Get the CMS-1500 for business ID {businessId} with background set to {background}.
        slots:
          businessId: query.businessId
          background: query.background
      method: generated
      generated: '2026-09-26'
- target: $.paths['/export/{transactionId}/1500/pdf'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a CMS-1500 PDF by transaction ID
      effect: read
      questions:
      - How do I get the CMS-1500 claim form PDF for a professional claim from its transaction ID?
      - What does a submitted 837P claim look like as a paper CMS-1500 form?
      instructions:
      - text: Download the CMS-1500 form for claim transaction {transactionId}.
        slots:
          transactionId: path.transactionId
      - text: Get the data-only CMS-1500 PDF for transaction {transactionId} with background {background}.
        slots:
          transactionId: path.transactionId
          background: query.background
      method: generated
      generated: '2026-09-26'