For veterinary practices
We are looking for three veterinary practices to help us design a product for clinics
University of Wisconsin Veterinary Care runs its hospital laboratory on VetSci, and our software also runs for other clients, including Maine DOT and NIEHS. Your first step is a thirty-minute conversation about how your practice keeps its records.
We are designing a product for veterinary clinics, together with three practices. It would keep records, transcripts, and results on the same Dataverse platform that diagnostic and hospital laboratories use. A design partner gets a say in what it does, the first configuration, and a founding price when it ships. Tell us how your practice keeps its records today.
Talk with an expert What a design partner gets →
A conversation takes thirty minutes on Microsoft Bookings and lands on an expert’s calendar.
01Who this is for
Practices that send work to a diagnostic laboratory
We want to hear from veterinary practices and clinics that see the patient, write the notes, draw the sample, and wait for the laboratory’s result. You may be a practice owner, a practice manager, or a veterinarian who orders from a laboratory every week.
A design partner lets us watch how its records are kept and tells us where the design is wrong.
Running a veterinary hospital or diagnostic laboratory? VetSci is our LIMS for those laboratories, and it runs in production today.
02The problem
The visit, the notes, and the result live in three places
The visit is recorded in the practice system. The notes are typed up after the appointment, from memory or from a recording. The laboratory result arrives as a PDF, an email, or a login to a portal, and someone attaches it or retypes it into the record.
The laboratory holds a full record of the same sample, including who submitted it, what was ordered, what was found, and who signed it out. The practice sees one page of it, so the sample’s story is told twice, by two systems that do not share it.
That is the problem we are designing for. The three practices will tell us whether the design is right.
03A design partner
What a design partner gets
Gets
A say, first
A say in what the product does, the first configuration when it exists, and a founding price when it ships.
Starts with
Conversations and visits
The product is still being designed, so a partnership starts with conversations and visits to your practice.
We work with practices the way we work with laboratories, in four phases called Understand, Build, Adopt, and Sustain. A design partnership sits in Understand, our on-site analysis of how the work is done. We start in the practice, watching how records are kept, before anything is built. How we work describes each phase.
We will set a release date once there is a working result, and we name a design partner only with its permission.
04Platform
The same platform as the laboratory
LabSci is a configurable laboratory platform built natively on Microsoft Dataverse and the Power Platform. VetSci, the veterinary solution on that platform, runs the veterinary hospital laboratory at University of Wisconsin Veterinary Care today.
The practice product is being designed on the same platform, so that a practice and the laboratory it sends work to stand on the same ground. What the connection between them does is one of the things the three practices will decide.