VEvetnio
vetmanager

Export clinical note to VetManager

Adds the supplied note to the consultation's VetManager visit as a new AI note ("AI-anteckning"). The consultation must be linked to a visit, either by opening Vetnio from that visit or through the create-visit endpoint. Exporting the same text again replays the first result; edited text adds another note.

Errors: 400 when the consultation is not linked or the note is empty; 401 when the caller must sign in to VetManager again; 403 when the visit's access belongs to another visit; 404 when the visit no longer exists; 409 when the visit is locked.

post/workspaces/{workspaceId}/consultations/{consultationId}/vetmanager/export

Request

  • Base URL
    https://vetnio.com/api/v2
  • URL
    https://vetnio.com/api/v2/workspaces/{workspaceId}/consultations/{consultationId}/vetmanager/export
  • Auth
    HTTP bearer

Path parameters

workspaceIdstring required

Identifier of the clinic (workspace), as returned by GET /workspaces. The key's user must be a member of the clinic, or an admin of the organization it belongs to.

Example:furunculotic-loud-chihuahua
consultationIdstring required

Identifier of the consultation (UUID), as returned when it was created or by GET /workspaces/{workspaceId}/consultations. It must belong to the clinic in workspaceId.

Example:a1b2c3d4-e5f6-7890-abcd-ef1234567890

Request body

clinicalNotestring required

The note to write: HTML, plain text, or a structured note serialised as a JSON object. It is converted to plain text and must not be empty.

Example request

{
  "clinicalNote": "<p><strong>Anamnes</strong><br>Hälta vänster bak sedan två veckor.</p>"
}

Response

The created note.

status'ok' required

Always ok on success.

vetmanagerEventIdnumber nullable required

Id of the AI note created in VetManager, or null when VetManager did not return one.

Example response

{
  "status": "ok",
  "vetmanagerEventId": 990001
}

Changes

No recorded changes to this operation across all 1 revision of this API.