User Guide
Built-In Safety Checks
How VetOS prevents dangerous mistakes before they happen — without slowing you down.
What you will learn
- •Understand the specific safety checks VetOS enforces: controlled substances, surgery prep, credentials, and more
- •Know exactly what you will see on screen when a check fails — and how to fix it
- •Learn about Break-Glass emergency access for after-hours situations
- •Understand how to request custom safety rules for your practice
What are safety checks?
Think of safety checks like guardrails on a mountain road. They do not slow you down when you are driving normally, but they stop you from going over the edge. VetOS has guardrails built into every critical workflow.
Before VetOS lets someone do something that could be risky — dispensing a controlled substance, starting anesthesia, prescribing a medication, overriding a billing code — it checks a few things first. Does this person have the right role and credentials? Have all the required pre-steps been completed? Is this drug appropriate for this species at this dosage?
If everything checks out, the action goes through instantly. You will not even notice the check happened. VetOS only stops you when something is genuinely wrong.
Real examples of safety checks in VetOS
Controlled substance dispensing: Before dispensing Schedule II through V medications, VetOS verifies that the prescribing veterinarian has a valid DEA number on file and that the dosage is within the expected range for the patient's species and weight. The WhoGot++ screen (in the Operations section of the sidebar) lets you instantly look up which patients received a specific drug, batch, or lot number — critical for recall situations.
Surgery preparation: Before a surgery can begin, VetOS walks through a checklist: owner consent confirmed, pre-anesthesia bloodwork on file, anesthesia plan documented, and surgical team assigned. You cannot skip these steps — VetOS will not let the surgery proceed until each one is checked off.
Clinical Decision Support: The CDS module (under Records in the sidebar) automatically checks for drug interactions when a new medication is prescribed. If a patient is already on a medication that could interact dangerously with the new one, VetOS flags it before the prescription is saved.
Role-based permissions: A receptionist cannot accidentally prescribe a medication or void a controlled substance log entry. VetOS enforces role boundaries invisibly — the buttons and options that someone does not have permission to use simply do not appear on their screen.
What you see when a check fails
When a safety check blocks an action, VetOS shows a clear message explaining exactly what is wrong and what needs to happen. For example: "This procedure requires pre-anesthesia bloodwork. Upload bloodwork results to the patient record to continue." Or: "DEA registration for Dr. Smith expired on 01/15/2026. Contact your administrator to update credentials."
The message always tells you what to do next. There is no guesswork, and the issue is always fixable by completing the missing step.
Break-Glass: emergency override access
What if it is 2 AM on a Saturday and an emergency patient comes in, but the on-call vet does not have the right permissions for a specific procedure? VetOS has a Break-Glass feature (under Compliance in the sidebar) that allows emergency overrides.
Break-Glass access is heavily logged. When someone uses it, VetOS records exactly who used it, when, why (they must enter a reason), and what they accessed. Practice managers and owners are automatically notified. This prevents abuse while still allowing your team to do what they need to do in an emergency.
Think of it like the emergency fire exit in a building — it is always available, but an alarm goes off when you use it.
Customizing safety checks for your practice
Every clinic has its own rules. Maybe you require a weight check before every anesthesia event. Maybe you want two-person signoff on controlled substance waste. Maybe you need to block scheduling outside business hours unless a manager approves it.
These custom rules can be added by your VetOS support team. Describe the rule in plain language, they configure and test it, and you approve before it goes live. Custom rules add new guardrails on top of the existing ones — they never remove safety checks or weaken the system.