# 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 Vendor Integrations API
  version: 1.0.0
extends: openapi/elation-health-lab-vendor-integrations-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_vendor_integrations/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a lab vendor integration (legacy endpoint)
      effect: read
      questions:
      - Can I check one lab vendor hookup through the legacy integrations path?
      - Does the older lookup show whether a lab integration allows printing?
      instructions:
      - text: Open lab vendor integration {id} using the legacy endpoint.
        slots:
          id: path.id
      - text: Show the orders and results status of old-path lab integration {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendor_integrations/{id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a lab vendor integration (legacy PUT)
      effect: write
      questions:
      - How do I resend a whole lab vendor integration via the legacy PUT?
      - Can the older full update switch which lab vendor a practice is wired to?
      instructions:
      - text: With the legacy PUT, replace lab integration {id} to link practice {practice} with lab vendor {lab_vendor}.
        slots:
          id: path.id
          practice: requestBody.practice
          lab_vendor: requestBody.lab_vendor
      - text: Rewrite old-path lab integration {id} with results status {results_status} and orders status {orders_status}.
        slots:
          id: path.id
          results_status: requestBody.results_status
          orders_status: requestBody.orders_status
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendor_integrations/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Remove a lab vendor integration (legacy endpoint)
      effect: destructive
      questions:
      - Is there a legacy way to disconnect a lab vendor from my practice?
      - What happens if I delete a lab integration on the original path?
      instructions:
      - text: Delete lab vendor integration {id} with the legacy endpoint.
        slots:
          id: path.id
      - text: Disconnect the old-path lab hookup {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendor_integrations/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Patch a lab vendor integration (legacy PATCH)
      effect: write
      questions:
      - Can I turn printing on or off for a lab integration with the legacy PATCH?
      - What's the older way to change only a lab hookup's results status?
      instructions:
      - text: Using the legacy PATCH, set allow print to {allow_print} on lab integration {id}.
        slots:
          id: path.id
          allow_print: requestBody.allow_print
      - text: Patch old-path lab integration {id} so results status is {results_status}.
        slots:
          id: path.id
          results_status: requestBody.results_status
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendor_integrations/'].get
  update:
    x-apievangelist-phrasing:
      intent: Find lab vendor integrations (legacy endpoint)
      effect: read
      questions:
      - Which labs is my practice connected to, according to the legacy search?
      - Can I find every practice wired to a given lab vendor with the older lookup?
      instructions:
      - text: Using the legacy lookup, find lab integrations for practice {practice}.
        slots:
          practice: query.practice
      - text: Find old-path integrations with lab vendor {lab_vendor}.
        slots:
          lab_vendor: query.lab_vendor
      method: generated
      generated: '2026-09-26'
- target: $.paths['/lab_vendor_integrations/'].post
  update:
    x-apievangelist-phrasing:
      intent: Connect a lab vendor (legacy endpoint)
      effect: write
      questions:
      - How do I connect my practice to a lab vendor through the legacy endpoint?
      - What statuses must I set when creating a lab integration the old way?
      instructions:
      - text: Via the legacy endpoint, connect practice {practice} to lab vendor {lab_vendor} with orders status {orders_status} and results status {results_status}.
        slots:
          practice: requestBody.practice
          lab_vendor: requestBody.lab_vendor
          orders_status: requestBody.orders_status
          results_status: requestBody.results_status
      - text: 'Create an old-path lab hookup for {lab_vendor} that allows printing: {allow_print}.'
        slots:
          lab_vendor: requestBody.lab_vendor
          allow_print: requestBody.allow_print
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendor_integrations/'].get
  update:
    x-apievangelist-phrasing:
      intent: List lab vendor integrations in API 2.0
      effect: read
      questions:
      - How do I list every lab vendor integration in the 2.0 API?
      - Can API 2.0 filter lab integrations to one practice and sort them?
      instructions:
      - text: List 2.0 lab vendor integrations for practice {practice} ordered by {order_by}.
        slots:
          practice: query.practice
          order_by: query.order_by
      - text: List API 2.0 integrations with lab vendor {lab_vendor}, {limit} per page.
        slots:
          lab_vendor: query.lab_vendor
          limit: query.limit
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendor_integrations/'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a lab vendor integration in API 2.0
      effect: write
      questions:
      - How do I set up a new lab vendor integration with the 2.0 API?
      - Are orders status and results status both required for a new lab integration?
      instructions:
      - text: In API 2.0, integrate practice {practice} with lab vendor {lab_vendor}, orders status {orders_status}, results status {results_status}.
        slots:
          practice: requestBody.practice
          lab_vendor: requestBody.lab_vendor
          orders_status: requestBody.orders_status
          results_status: requestBody.results_status
      - text: Create a 2.0 lab integration for {lab_vendor} with printing set to {allow_print}.
        slots:
          lab_vendor: requestBody.lab_vendor
          allow_print: requestBody.allow_print
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendor_integrations/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Retrieve a lab vendor integration in API 2.0
      effect: read
      questions:
      - How do I retrieve one lab vendor integration by ID in API 2.0?
      - Can I see when a 2.0 lab integration was created?
      instructions:
      - text: Retrieve API 2.0 lab vendor integration {id}.
        slots:
          id: path.id
      - text: Get the lab vendor and practice on 2.0 integration {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendor_integrations/{id}/'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a lab vendor integration in API 2.0
      effect: write
      questions:
      - Can I replace a lab vendor integration in full with a 2.0 PUT?
      - Which fields does a full lab integration replacement require?
      instructions:
      - text: 'Replace 2.0 lab integration {id}: practice {practice}, lab vendor {lab_vendor}, orders {orders_status}, results {results_status}.'
        slots:
          id: path.id
          practice: requestBody.practice
          lab_vendor: requestBody.lab_vendor
          orders_status: requestBody.orders_status
          results_status: requestBody.results_status
      - text: Overwrite API 2.0 lab integration {id} for vendor {lab_vendor}.
        slots:
          id: path.id
          lab_vendor: requestBody.lab_vendor
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendor_integrations/{id}/'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a lab vendor integration in API 2.0
      effect: destructive
      questions:
      - How do I delete a lab vendor integration in the 2.0 API?
      - Can I stop sending lab orders to a vendor by removing the integration?
      instructions:
      - text: Delete API 2.0 lab vendor integration {id}.
        slots:
          id: path.id
      - text: Remove 2.0 lab hookup {id} from my practice.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/lab_vendor_integrations/{id}/'].patch
  update:
    x-apievangelist-phrasing:
      intent: Partially update a lab vendor integration in API 2.0
      effect: write
      questions:
      - Can I change only the orders status on a lab integration with a 2.0 PATCH?
      - Is there a partial update in API 2.0 for a lab integration's print setting?
      instructions:
      - text: Patch 2.0 lab integration {id} with orders status {orders_status}.
        slots:
          id: path.id
          orders_status: requestBody.orders_status
      - text: Partially update API 2.0 lab integration {id} to allow print {allow_print}.
        slots:
          id: path.id
          allow_print: requestBody.allow_print
      method: generated
      generated: '2026-09-26'