# 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 Templates API version: 1.0.0 extends: openapi/elation-health-visit-note-templates-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_templates/'].get update: x-apievangelist-phrasing: intent: Find visit note templates (legacy endpoint) effect: read questions: - What visit note templates does my practice have, via the legacy endpoint? - Can I pull every note template with the older templates lookup? instructions: - text: Using the legacy lookup, find all visit note templates. - text: Show my practice's old-path note templates. method: generated generated: '2026-09-26' - target: $.paths['/visit_note_templates/{id}'].get update: x-apievangelist-phrasing: intent: Get a visit note template (legacy endpoint) effect: read questions: - Can I read a single visit note template on the legacy path? - Does the older template lookup return the template's content? instructions: - text: Open visit note template {id} using the legacy endpoint. slots: id: path.id - text: Show the content of that old-path note template. method: generated generated: '2026-10-01' - target: $.paths['/visit_note_templates/{id}'].delete update: x-apievangelist-phrasing: intent: Delete a visit note template (legacy endpoint) effect: destructive questions: - Is there a legacy call to delete a visit note template we no longer use? - Can I remove a note template through the original templates path? instructions: - text: Delete unused visit note template {id} with the legacy endpoint. slots: id: path.id - text: Remove that old-path note template. method: generated generated: '2026-10-01' - target: $.paths['/visit_note_templates/{id}'].patch update: x-apievangelist-phrasing: intent: Update a visit note template (legacy PATCH) effect: write questions: - Can I rename a visit note template with the legacy PATCH? - What's the older way to edit a template's content? instructions: - text: Using the legacy PATCH, rename visit note template {id} to {name}. slots: id: path.id name: requestBody.name - text: Replace the old-path template's content with {content}. slots: content: requestBody.content method: generated generated: '2026-10-01' - target: $.paths['/api/2.0/visit_note_templates/'].get update: x-apievangelist-phrasing: intent: List visit note templates in API 2.0 effect: read questions: - How do I list visit note templates by name in the 2.0 API? - Can API 2.0 show only templates my practice created? instructions: - text: List 2.0 visit note templates named {name}. slots: name: query.name - text: List API 2.0 templates created by practice {practice_created}, ordered by {order_by}. slots: practice_created: query.practice_created order_by: query.order_by method: generated generated: '2026-09-26' - target: $.paths['/api/2.0/visit_note_templates/'].post update: x-apievangelist-phrasing: intent: Create a visit note template in API 2.0 effect: write questions: - How do I create a new visit note template with the 2.0 API? - Are a name and content both required for a new note template? instructions: - text: In API 2.0, create a visit note template named {name} with content {content}. slots: name: requestBody.name content: requestBody.content - text: Add a 2.0 note template {name} owned by practice {practice_created}. slots: name: requestBody.name practice_created: requestBody.practice_created method: generated generated: '2026-09-26' - target: $.paths['/api/2.0/visit_note_templates/{id}/'].get update: x-apievangelist-phrasing: intent: Retrieve a visit note template in API 2.0 effect: read questions: - How do I retrieve one visit note template by ID in API 2.0? - Does a 2.0 template show which practice created it? instructions: - text: Retrieve API 2.0 visit note template {id}. slots: id: path.id - text: Get the content of 2.0 note template {id}. slots: id: path.id method: generated generated: '2026-09-26' - target: $.paths['/api/2.0/visit_note_templates/{id}/'].put update: x-apievangelist-phrasing: intent: Replace a visit note template in API 2.0 effect: write questions: - Can I replace a visit note template in full with a 2.0 PUT? - What must I resend to fully replace a note template? instructions: - text: Replace 2.0 visit note template {id} with name {name} and content {content}. slots: id: path.id name: requestBody.name content: requestBody.content - text: Overwrite API 2.0 note template {id} entirely as {name}. slots: id: path.id name: requestBody.name method: generated generated: '2026-09-26' - target: $.paths['/api/2.0/visit_note_templates/{id}/'].delete update: x-apievangelist-phrasing: intent: Delete a visit note template in API 2.0 effect: destructive questions: - How do I delete a visit note template in the 2.0 API? - Can I retire an outdated note template by its ID? instructions: - text: Delete API 2.0 visit note template {id}. slots: id: path.id - text: Retire outdated 2.0 note template {id}. slots: id: path.id method: generated generated: '2026-09-26' - target: $.paths['/api/2.0/visit_note_templates/{id}/'].patch update: x-apievangelist-phrasing: intent: Partially update a visit note template in API 2.0 effect: write questions: - Can I change just a template's name with a 2.0 PATCH? - Is there a partial update in API 2.0 for editing template content only? instructions: - text: Patch 2.0 visit note template {id} to be named {name}. slots: id: path.id name: requestBody.name - text: Partially update API 2.0 template {id} with new content {content}. slots: id: path.id content: requestBody.content method: generated generated: '2026-09-26'