API Evangelist conversational phrasing for Elation Health Document Tags 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 Document Tags API
  version: 1.0.0
extends: openapi/elation-health-document-tags-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 10
- target: $.paths['/document_tags/'].get
  update:
    x-apievangelist-phrasing:
      intent: List document tags (legacy endpoint)
      effect: read
      questions:
      - What document tags exist in my practice, per the legacy endpoint?
      - Can I see all tags used to label chart documents on the original path?
      instructions:
      - text: List document tags from the legacy endpoint.
      - text: Show every chart document tag on the old path.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/document_tags/'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a document tag (legacy endpoint)
      effect: write
      questions:
      - How do I add a new tag for labeling documents through the legacy endpoint?
      - Can I attach a code and code type to a document tag the old way?
      instructions:
      - text: Create legacy document tag {value} described as {description}.
        slots:
          value: requestBody.value
          description: requestBody.description
      - text: Add an old-endpoint document tag {value} with code {code} of type {code_type}.
        slots:
          value: requestBody.value
          code: requestBody.code
          code_type: requestBody.code_type
      method: generated
      generated: '2026-09-26'
- target: $.paths['/document_tags/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a document tag (legacy endpoint)
      effect: read
      questions:
      - How do I look up one document tag by id on the legacy path?
      - What code and concept name does a tag carry on the original endpoint?
      instructions:
      - text: Get legacy document tag {id}.
        slots:
          id: path.id
      - text: Show document tag {id} from the older endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/document_tags/{id}/'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a document tag (legacy PUT)
      effect: write
      questions:
      - Can I overwrite a whole document tag with the legacy PUT?
      - Which legacy call resends every field of a document tag?
      instructions:
      - text: Replace legacy document tag {tag} with value {value}.
        slots:
          tag: path.id
          value: requestBody.value
      - text: Overwrite old-endpoint tag {tag} in full with concept name {concept}.
        slots:
          tag: path.id
          concept: requestBody.concept_name
      method: generated
      generated: '2026-10-01'
- target: $.paths['/document_tags/{id}/'].patch
  update:
    x-apievangelist-phrasing:
      intent: Change a document tag's code (legacy PATCH)
      effect: write
      questions:
      - Can I update just a document tag's code with the legacy PATCH?
      - How do I change a tag's description on the unversioned path without resending it?
      instructions:
      - text: Patch legacy document tag {tag} to code {code}.
        slots:
          tag: path.id
          code: requestBody.code
      - text: Change the description of tag {tag} to {description} on the old endpoint.
        slots:
          tag: path.id
          description: requestBody.description
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/2.0/document_tags/'].get
  update:
    x-apievangelist-phrasing:
      intent: List document tags (v2.0)
      effect: read
      questions:
      - How do I search document tags by value in the 2.0 API?
      - Can I list only practice-created document tags in version 2.0?
      instructions:
      - text: List v2.0 document tags with value {value}.
        slots:
          value: query.value
      - text: List 2.0 document tags with code {code}.
        slots:
          code: query.code
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/document_tags/'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a document tag (v2.0)
      effect: write
      questions:
      - How do I create a document tag with a SNOMED result code in version 2.0?
      - What is required to add a document tag in the 2.0 API?
      instructions:
      - text: Create v2.0 document tag {value}.
        slots:
          value: requestBody.value
      - text: Add 2.0 document tag {value} with SNOMED result code {snomed}.
        slots:
          value: requestBody.value
          snomed: requestBody.snomed_result_code
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/document_tags/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a document tag (v2.0)
      effect: read
      questions:
      - How do I fetch a single document tag in the 2.0 API?
      - Does the v2.0 document tag show its SNOMED result code?
      instructions:
      - text: Get v2.0 document tag {id}.
        slots:
          id: path.id
      - text: Retrieve document tag {id} from the 2.0 API.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/document_tags/{id}/'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a document tag (v2.0 PUT)
      effect: write
      questions:
      - Can I fully replace a document tag in version 2.0?
      - Which 2.0 call overwrites every document tag field?
      instructions:
      - text: Replace v2.0 document tag {id} with value {value}.
        slots:
          id: path.id
          value: requestBody.value
      - text: Overwrite 2.0 tag {id} with context {context}.
        slots:
          id: path.id
          context: requestBody.context
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/document_tags/{id}/'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update some document tag fields (v2.0)
      effect: write
      questions:
      - Can I change only a document tag's context in the 2.0 API?
      - Which v2.0 call renames a tag without resending the rest?
      instructions:
      - text: Patch v2.0 document tag {id} value to {value}.
        slots:
          id: path.id
          value: requestBody.value
      - text: Set the concept name of 2.0 tag {id} to {concept}.
        slots:
          id: path.id
          concept: requestBody.concept_name
      method: generated
      generated: '2026-09-26'