API Evangelist conversational phrasing for Elation Health Visit Note Types 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 Visit Note Types API
  version: 1.0.0
extends: openapi/elation-health-visit-note-types-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['/visit_note_types/'].get
  update:
    x-apievangelist-phrasing:
      intent: List visit note types (legacy endpoint)
      effect: read
      questions:
      - What visit note types can clinicians pick from, per the legacy endpoint?
      - Can I see all visit note templates on the original path?
      instructions:
      - text: List visit note types from the legacy endpoint.
      - text: Show every visit note type on the old path.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/visit_note_types/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a visit note type (legacy endpoint)
      effect: read
      questions:
      - Can I look up one visit note type on the legacy path?
      - Does the original endpoint say whether a note type counts as an office visit?
      instructions:
      - text: Get visit note type {id} from the legacy endpoint.
        slots:
          id: path.id
      - text: Show one visit note type's details on the old path.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/visit_note_types/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a visit note type (legacy endpoint)
      effect: destructive
      questions:
      - How do I remove a visit note type using the legacy endpoint?
      - Can I retire an unused visit note type through the original path?
      instructions:
      - text: Delete visit note type {id} via the legacy endpoint.
        slots:
          id: path.id
      - text: Retire an unused note type on the old path.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/visit_note_types/:id'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update a visit note type (legacy PATCH)
      effect: write
      questions:
      - Can I rename a visit note type with the legacy PATCH?
      - How do I set a SNOMED code on a visit note type through the old path?
      instructions:
      - text: Patch the legacy visit note type to be named {name}.
        slots:
          name: requestBody.name
      - text: Set SNOMED code {snomed} on a note type using the old endpoint.
        slots:
          snomed: requestBody.snomed_code
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/visit_note_types/'].get
  update:
    x-apievangelist-phrasing:
      intent: List visit note types (v2.0)
      effect: read
      questions:
      - How do I search visit note types by name in the 2.0 API?
      - Can I list only the note types my practice created in version 2.0?
      instructions:
      - text: List v2.0 visit note types named {name}.
        slots:
          name: query.name
      - text: List 2.0 visit note types with practice_created {practice_created}.
        slots:
          practice_created: query.practice_created
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/visit_note_types/'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a visit note type (v2.0)
      effect: write
      questions:
      - How do I add a new visit note type in version 2.0?
      - Can I set the display rank of a new note type in the 2.0 API?
      instructions:
      - text: Create v2.0 visit note type {name}.
        slots:
          name: requestBody.name
      - text: Add 2.0 note type {name} at rank {rank} flagged as an office visit {mu}.
        slots:
          name: requestBody.name
          rank: requestBody.rank
          mu: requestBody.is_mu_office_visit
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/visit_note_types/{id}/'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a visit note type (v2.0)
      effect: read
      questions:
      - Which 2.0 call fetches a single visit note type?
      - What rank and SNOMED code does a v2.0 note type have?
      instructions:
      - text: Get v2.0 visit note type {id}.
        slots:
          id: path.id
      - text: Retrieve note type {id} from the 2.0 API.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/visit_note_types/{id}/'].put
  update:
    x-apievangelist-phrasing:
      intent: Replace a visit note type (v2.0 PUT)
      effect: write
      questions:
      - Can I fully replace a visit note type in version 2.0?
      - Which 2.0 call overwrites every note type field?
      instructions:
      - text: Replace v2.0 visit note type {id} with name {name}.
        slots:
          id: path.id
          name: requestBody.name
      - text: Overwrite 2.0 note type {id} with SNOMED code {snomed}.
        slots:
          id: path.id
          snomed: requestBody.snomed_code
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/visit_note_types/{id}/'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a visit note type (v2.0)
      effect: destructive
      questions:
      - What's the 2.0 way to delete a visit note type?
      - Can I remove a note type nobody uses in version 2.0?
      instructions:
      - text: Delete v2.0 visit note type {id}.
        slots:
          id: path.id
      - text: Remove note type {id} with the 2.0 endpoint.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/2.0/visit_note_types/{id}/'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update some visit note type fields (v2.0)
      effect: write
      questions:
      - Can I change only the rank of a visit note type in the 2.0 API?
      - Which v2.0 call renames a note type without resending the rest?
      instructions:
      - text: Patch v2.0 visit note type {id} rank to {rank}.
        slots:
          id: path.id
          rank: requestBody.rank
      - text: Rename 2.0 note type {id} to {name}.
        slots:
          id: path.id
          name: requestBody.name
      method: generated
      generated: '2026-09-26'