API Evangelist conversational phrasing for Elation Health Lab Vendors API

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Elation Health Lab Vendors API
  version: 1.0.0
extends: openapi/elation-health-lab-vendors-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: 12
- target: $.paths['/lab_vendors/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a lab vendor (legacy endpoint)
      effect: read
      questions:
      - How do I look up one lab vendor by id on the legacy path?
      - Does the original endpoint say whether a lab supports electronic results?
      instructions:
      - text: Get legacy lab vendor {id}.
        slots:
          id: path.id
      - text: Show lab vendor {id} from the older endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendors/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a lab vendor (legacy PUT)
      effect: write
      questions:
      - Can I overwrite a lab vendor's names and integration flags with the legacy PUT?
      - Which legacy call fully replaces a lab vendor record?
      instructions:
      - text: Replace legacy lab vendor {id} with name {name} and display name {display_name}.
        slots:
          id: path.id
          name: requestBody.name
          display_name: requestBody.display_name
      - text: Overwrite old-endpoint lab vendor {id}, setting orders integration to {orders}.
        slots:
          id: path.id
          orders: requestBody.orders_integration_available
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendors/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a lab vendor (legacy endpoint)
      effect: destructive
      questions:
      - How do I remove a lab vendor using the legacy endpoint?
      - Can I delete a lab my practice added but no longer uses via the original path?
      instructions:
      - text: Delete legacy lab vendor {id}.
        slots:
          id: path.id
      - text: Remove lab vendor {id} via the old endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendors/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Change a lab vendor's integration flags (legacy)
      effect: write
      questions:
      - Can I toggle results integration on a lab vendor with the legacy PATCH?
      - How do I change a lab vendor's default compendium on the unversioned path?
      instructions:
      - text: Patch legacy lab vendor {id} so results integration is {results}.
        slots:
          id: path.id
          results: requestBody.results_integration_available
      - text: Set the default compendium of lab vendor {id} to {compendium} on the old endpoint.
        slots:
          id: path.id
          compendium: requestBody.default_compendium
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendors/'].get
  update:
    x-apievangelist-phrasing:
      intent: Find lab vendors (legacy endpoint)
      effect: read
      questions:
      - How do I search lab vendors by name on the legacy endpoint?
      - Can the original lab vendor search show only labs my practice created?
      instructions:
      - text: Find legacy lab vendors named {name}.
        slots:
          name: query.name
      - text: Search the old endpoint for practice-created lab vendors ({practice_created}).
        slots:
          practice_created: query.practice_created
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendors/'].post
  update:
    x-apievangelist-phrasing:
      intent: Add a lab vendor (legacy endpoint)
      effect: write
      questions:
      - How do I add a new lab vendor through the legacy endpoint?
      - What integration flags must I set when creating a lab vendor the old way?
      instructions:
      - text: Create legacy lab vendor {name} displayed as {display_name}.
        slots:
          name: requestBody.name
          display_name: requestBody.display_name
      - text: Add lab {name} on the old endpoint with results integration {results}.
        slots:
          name: requestBody.name
          results: requestBody.results_integration_available
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendors/'].get
  update:
    x-apievangelist-phrasing:
      intent: List lab vendors (v2.0)
      effect: read
      questions:
      - Which lab vendors are available to my practice in the 2.0 API?
      - Can I page through version 2.0 lab vendors filtered by name?
      instructions:
      - text: List v2.0 lab vendors named {name}.
        slots:
          name: query.name
      - text: List 2.0 lab vendors, {limit} per page, ordered by {order_by}.
        slots:
          limit: query.limit
          order_by: query.order_by
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendors/'].post
  update:
    x-apievangelist-phrasing:
      intent: Add a lab vendor (v2.0)
      effect: write
      questions:
      - How do I create an in-house lab vendor in the 2.0 API?
      - Can I add a bidirectional lab vendor in version 2.0?
      instructions:
      - text: Create v2.0 lab vendor {name} displayed as {display_name}.
        slots:
          name: requestBody.name
          display_name: requestBody.display_name
      - text: Add 2.0 lab {name} marked in-house {in_house}.
        slots:
          name: requestBody.name
          in_house: requestBody.is_in_house
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendors/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a lab vendor (v2.0)
      effect: read
      questions:
      - How do I fetch a single lab vendor with its compendiums in the 2.0 API?
      - Does the v2.0 lab vendor record show its bidirectional connections?
      instructions:
      - text: Get v2.0 lab vendor {id}.
        slots:
          id: path.id
      - text: Retrieve lab vendor {id} from the 2.0 API with its compendiums.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendors/{id}/'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a lab vendor (v2.0 PUT)
      effect: write
      questions:
      - Can I fully replace a lab vendor record in version 2.0?
      - Which 2.0 call overwrites every lab vendor field?
      instructions:
      - text: Replace v2.0 lab vendor {id} with name {name} and display name {display_name}.
        slots:
          id: path.id
          name: requestBody.name
          display_name: requestBody.display_name
      - text: Overwrite 2.0 lab vendor {id} with compendiums {compendiums}.
        slots:
          id: path.id
          compendiums: requestBody.compendiums
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendors/{id}/'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a lab vendor (v2.0)
      effect: destructive
      questions:
      - How do I delete a lab vendor through the 2.0 API?
      - Can I remove an unused lab vendor in version 2.0?
      instructions:
      - text: Delete v2.0 lab vendor {id}.
        slots:
          id: path.id
      - text: Remove lab vendor {id} with the 2.0 endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendors/{id}/'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update some lab vendor fields (v2.0)
      effect: write
      questions:
      - Can I change only a lab vendor's display name in the 2.0 API?
      - Which v2.0 call flips a lab vendor to bidirectional without resending everything?
      instructions:
      - text: Patch v2.0 lab vendor {id} display name to {display_name}.
        slots:
          id: path.id
          display_name: requestBody.display_name
      - text: Mark 2.0 lab vendor {id} bidirectional {bidi}.
        slots:
          id: path.id
          bidi: requestBody.is_bidi
      method: generated
      generated: '2026-09-26'