Keep your PIMS. Close the gaps around it.

Software that works on top of the practice management system your practice already runs. It keeps you compliant with the CMA's Order, runs checks in the background that flag what was missed, gives you practice numbers you can rely on, and takes admin such as rota changes and email filing off your desk. It is not another PIMS, and your team keeps working in the one they know.

No. Praxis connects to the system you have, with no migration. Because your price lists, pathways and checks are kept in Praxis rather than in the PIMS, they also stay with you if your practice ever decides to change system.

The board works out your dates from the size of your business and shows, duty by duty, what Praxis can evidence: published price lists, written estimates and bills, written-prescription offers and requests, and the attestation evidence. Duties Praxis cannot see are listed as yours to tick. It is evidence, not legal advice. In development, and labelled as such: a complaints log that follows each complaint from the first email to its resolution.

Assistant-proposed changes wait for a person's approval. Direct clinician actions, such as editing an appointment in Calendar, run after their own checks. Reading and writing are separate permissions. A write is reported done only once Praxis has read it back from your system; a clinical form that still needs you to save it is labelled prepared. Connecting a system does not give anything unrestricted access.

Twelve product integrations are currently connectable — ezyVet, Provet Cloud, Covetrus Pulse, Shepherd, Vetspire, Navetor, DaySmart Vet, VetPort, Rhapsody, Dogbyte, Instinct and Solvit. ezyVet uses the Store-packaged page transport; Provet Cloud has a server-side OAuth integration plus the Store's bounded 0.2 browser-session read catalogue; Covetrus Pulse, Shepherd, Vetspire, Navetor, DaySmart Vet, VetPort, Rhapsody, Dogbyte and Instinct are browser-only page transports with no server API at all; Solvit uses its server-side API transport. The Store item itself packages only ezyVet, Provet Cloud, Covetrus Pulse, Shepherd, Vetspire, Navetor, DaySmart Vet, VetPort, Rhapsody, Dogbyte and Instinct. Their capabilities are not interchangeable — Covetrus Pulse reads context only, and Shepherd files notes only, per section, reporting each section as prepared rather than confirmed. Repository mocks prove software behavior, not live-vendor readiness. Current live evidence covers ezyVet rota create/edit/cancel and Provet read-only catalogue access; this page claims no live-vendor evidence for Covetrus Pulse, Shepherd, Vetspire, Navetor, DaySmart Vet, VetPort, Rhapsody, Dogbyte, Instinct or Solvit, and clinical-note or invoice write readiness requires separate authorised evidence.

Data export, erasure, permissions and documented retention support your practice’s privacy processes. Processing locations depend on the deployment and services you connect. Ask us for the hosting, AI provider and data-processing details for your practice, including any external assistant you choose to use.

Where reading free text needs it: Scribe drafts the consultation note, and email intake reads an email to find the patient it is about. The checks, the CMA board and the price-list watch are rules over your own records, with no model involved. A model never writes to your PIMS on its own.

No. Not on audio, not on transcripts, not on notes — and not on pseudonymised copies of them either, which is the usual loophole. There is no setting to check because there is nothing to opt out of.

Recorded audio is processed in your browser first, then uploaded for transcription. What is stored, for how long, and which processors are involved is documented in full rather than summarised.

An owner is a third party who never signed up for anything. We provide the notice text and consent wording for your waiting room, and a route for an owner to request deletion of a recording of their own voice.