Discuss your projectReferrals, results, reminders, and reporting that work the same way across every hospital, even when acquired hospitals still run different practice systems. Specialty cases come back to the referring vet with records attached, and leadership sees the whole group in one set of numbers.
Illustration of a specialty referral application built by Baybloom for a veterinary group: cases moving from referral to specialty care to results sent back to the referring hospital.
COOs, operations directors, and medical and practice leaders of veterinary groups that run general practice, specialty, and emergency hospitals under one organization. Each hospital’s practice information management system keeps the medical record, appointments, and invoices. The work between hospitals, such as referrals, results, ordering, and group reporting, runs on phone calls, email, and exports that someone merges by hand.
The workflow
The steps we see most often in this kind of operation.
What we build
Track each referral from general practice to specialty or emergency hospital with history, images, and status visible to both sides until results go back.
Pull results from reference labs, analyzers, and imaging reads, route them to the responsible doctor, and flag anything unreviewed before the client calls asking.
Report revenue, visits, active clients, and doctor productivity by hospital and region, using one set of definitions across every practice system the group runs.
Track usage and par levels per hospital, order from an approved catalog through distributor portals, and show leadership spend by hospital and category.
Apply group rules for wellness visits, vaccines, and lapsed clients across hospitals, assign call lists to each front desk, and record outcomes against the patient.
Give clients one place for forms, referral status, records requests, and messages, connected to the hospital they visit rather than a separate app per location.
Your first release
How the work runs
We start with the people doing the work and the systems around it, then write down the first release: what it includes, what it leaves for later, the integration decisions, and the acceptance criteria. Nothing is built until that scope is agreed.
We build in releases you can review as the work takes shape, using realistic data. Every release carries tests, a security review, and documentation. Integrations are tested against real records, with exceptions visible.
Your team receives the documentation, the runbooks, and the training to run the system, and we stay on for continued engineering when you want it.
Scope and price
Every project is priced from a written scope. These are the factors that move it most.
Each practice information management system offers different data access, from full APIs to scheduled exports, and every system in the group needs a separate connection and mapping.
General practice, specialty, and emergency hospitals work differently, so each type adds workflow rules, roles, and rollout support for its teams.
Agreeing on what counts as a visit, an active client, or revenue across hospitals takes discovery with finance and operations before any numbers can be trusted.
Routing results and orders depends on which labs, imaging systems, and distributors the hospitals use and what interfaces each one provides.
Veterinary group with general practice and specialty hospitals
In many veterinary groups, general practices refer cases to the specialty hospital by phone and email, and the discharge summary goes back only when someone remembers. A first release turns each referral into a tracked case with the history attached, a responsible person, and a due date, visible to both hospitals. Results route to the right doctor, and the summary returns to the referring vet from the case record. Specialty leaders see which practices refer and where cases wait. Group reporting across the different practice systems, with shared definitions of a visit and revenue, can come next.
Questions
What leaders in this industry ask us first.
The practice system stays the record of appointments, medical notes, and invoices at each hospital. We build the workflows between hospitals and the group reporting, and connect to each system for the data those workflows need.
Yes. The shared workflow and reporting records sit in one place, and each practice system gets a dedicated connection and field mapping. A hospital can migrate to the group’s standard system later without changing the workflow its staff use.
What the software stores, where it runs, who can see it, and how long records are kept are agreed in writing with the group before anything is built. Access is limited by hospital and role, and every view and change is logged.
Each referral is a case shared between the referring and receiving hospitals. When results, imaging reports, or a discharge summary are added, the referring vet is notified and can open them from a link or the referring vet portal, so nobody has to remember to send them.
Yes, and that is often the reason to start. Revenue, visits, active clients, and staffing are defined once, pulled from each practice system, and reconciled, so leadership compares hospitals on the same terms while system migrations continue.
Most practice systems send reminders already. Custom work usually applies group rules on top: which vaccines and wellness visits are due, which clients have lapsed, and which hospital should call, with outcomes recorded against the patient.
The hospital is added with its local settings and roles, a connection is set up for its practice system if the group has not seen that system before, and it appears in referrals and reporting alongside the others.