How do you separate the data of two veterinary practices?
In the cloud, what really prevents one veterinary practice from accessing another practice’s data? The answer depends above all on the architecture.
Pierre Bony
President, co-founder and CTO
In your veterinary practice management software, what really prevents you from one day coming across the data of the practice next door?
But with cloud, SaaS, or fully web-based software… the question becomes much more interesting. Because behind the word “cloud” are very different architectures.
One database shared by several practices
In some cases, several practices share the very same database. This is known as logical separation: every piece of data — client, animal, invoice, consultation entry… — must be correctly linked to your practice’s identifier.
CoreFactor’s choice for VetCoreSolution®
We made a different choice: a dedicated database for each practice. In technical terms, this is known as “mono-tenant”.
Why this choice? Because strict data isolation is not a minor technical detail. It is a decision about architecture, security, and responsibility.
And of course… everything is encrypted. But that is a topic for another TechNote! 😉
