Integrate a diagnostic imaging (RIS/PACS) system with Provet Cloud referrals and worklists
domain: developers.provetcloud.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Subscribe to the "Diagnostic imaging worklist" webhook to be notified when a vet creates a new imaging referral
On receipt, fetch order details via GET /api/0.1/diagnosticimaging_worklist/[id]/ and referral specifics via GET /api/0.1/diagnosticimaging_referral/[id]/
Fetch related consultation and patient data via GET /api/0.1/consultation/[id]/?expose_patients and client details via GET /api/0.1/client/[id]/
Authenticate these calls using the OAuth 2.0 client credentials grant, since the integration layer isn't tied to a specific Provet user
Update the order's status back in Provet via PATCH /api/0.1/diagnosticimaging_worklist/[id]/ as the study progresses through the RIS/modality
Configure the image-archive (PACS) URL in Settings > Integrations > Diagnostic imaging Settings so Provet can append the patient id and show a "Show images of [patient]" button in the UI
Known gotchas
Creating a referral triggers both the "Diagnostic imaging worklist" and "Diagnostic imaging worklist update" webhooks - your handler must tolerate the update firing before the create has been processed
The PACS viewer URL pattern only works if the viewer accepts the patient id appended to a base URL; viewers with a different linking scheme need a translation layer
Referral deletes fire a separate "Diagnostic imaging worklist delete" webhook - don't assume all imaging webhooks represent new or updated orders
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?