Prism

What it is

Prism is a Chrome browser extension, a companion API, and an operator console that work together to capture clinical data from veterinary practice management software (PIMS) without needing a vendor integration. The extension sits invisibly in a logged-in Chrome session and watches all network traffic between the PIMS front-end and its backend. Any response that contains clinical information — appointments, patients, client records, medical history — gets forwarded to the Prism API, which stores it, deduplicates it, and makes it available to the rest of DE. The operator console is the internal tool used by the DE team to classify and manage what gets captured.

The first PIMS Prism supports is Covetrus Pulse. The architecture is built so that adding a second practice management system later is a configuration change, not a rewrite.

Why it exists

PIMS vendor integrations are slow, politically expensive, and often unavailable entirely. A practice already has all its data — it is flowing through the browser every time a vet tech opens a patient record or checks the schedule. Prism captures that data at the source, with clinic consent, giving DE a working integration layer in days instead of months. This unblocks two concrete products that already have demand: Spotlight pre-appointment forms (which need an owner's email and phone before a visit) and AI-generated SOAP notes (which need the patient's history). Without Prism, both products require manual data exports or vendor cooperation. With Prism, they work automatically.

How it works

When a clinic installs Prism, a staff member visits a DE-hosted install page, which pairs the Chrome extension to that clinic's account via a one-time secure token. After pairing, the extension runs silently in the background whenever the PIMS is open. It uses Chrome's debugger protocol (the same interface developer tools use) to intercept every HTTP response from the practice management server. Responses that match the clinic's allowed domains are checked against a short deny-list — anything related to login, authentication, or session management is dropped. Anything else is added to a local queue in the browser and flushed to the Prism API roughly every ten seconds, or whenever the queue reaches fifty items.

The API receives these batches, authenticates the clinic by API key, runs a deduplication check (so identical payloads captured within an hour are stored only once), compresses each payload, and writes it to a dedicated Aurora MySQL database. Raw payloads are kept for ninety days and then permanently deleted. Every capture includes metadata — the URL, the HTTP method, the response status, and a timestamp — alongside the compressed body.

Phase 2, now live on staging, adds the Oracle Transformation Engine. Oracle reads the captured payloads and translates them into clean, structured records — appointment context, patient identity, client identity — using a versioned definition language that tells the system exactly which JSON fields to pull and how to interpret them. The Oracle was first proven end-to-end on 12 May 2026, successfully transforming real Covetrus Pulse whiteboard payloads into appointment context rows without any AI involvement. When a definition does not cover a payload perfectly, the system can invoke an AI repair loop to generate and evaluate candidate definitions, but that repair path is feature-flagged off until its safety gates are fully tested.

The operator console is the internal dashboard the DE team uses to install transform definitions, launch and stop experiments, and inspect audit trails. It is protected by a separate admin key and is not clinic-facing.

The parts

Where it fits