Veti capabilities and limits
Distinguish product learning, live records, proposals, clinical assistants and allowance.
Platform · VetConnect · Last verified:
Veti uses different sources for different questions. A documented product operation does not prove direct Veti execution support or user authorization.
| Request | Source and expected result |
|---|---|
| “How do I create a paper prescription in VetConnect?” | Published guide for the correct app/language with source link |
| “Show Luna's last examination” | Authorized current records with same-name identity checks |
| “Prepare tomorrow's appointment for this patient” | Real options and reviewable proposal for a supported action |
| “Organize examination notes into fields” | Writer suggestions for clinical review |
| “Assess these findings” | Analyzer output, not a confirmed diagnosis |
| “Turn dictation into text” | Supported-field text; save/sign separately |
Scope a product question
Name app, screen and goal. Platform, VetConnect and PetConnect differ in controls/authority. Veti should separate shared concepts from client-specific steps. Open source links and check app/language.
Public documentation does not currently publish API reference. Do not treat product guidance as integration endpoints/code. When no published source exists, Veti should state the limit instead of fabricating a tutorial from private tools.
Clinical access and actions
Role, clinic, patient/customer connection, record state and plan can affect access. Reading grants no write/sign/delete. Pet owners do not gain clinical or stock/finance editing.
Supported proposals expose targets/fields. For an unsupported action, use the normal product path; insisting grants no access. Veti does not sign examinations; the clinician signs in the clinical interface. Full Access is a preference for server-eligible automatic actions; protected financial and other review requirements remain.
Allowance and pending accounting
Read your plan, period/renewal, usage and any extra account in personal Veti usage. Clinic seat count differs from your allowance. Plan names do not promise fixed hours or identical task cost.
Usage updates may await accounting. Refresh current state; missing/failed reads do not mean zero. Use offered eligible plan/extra usage options rather than bypassing role/quota checks.
Missing controls
New Live voice entry is disabled on ordinary production surfaces; dictation remains separate. Platform chat attachment menu is not a general upload path. Use file/diagnostic/prescription workflows. A name, source module or guide does not establish enabled access.
Verify an answer
Check source, app, state conditions, fields/units and result-verification step. Product explanation is not today's patient information. Preserve “prepared” versus “applied”. Conversation recovery, clinical assistants.