Operations Platform
Veterinary Management and Reporting Platform
Operational workflows for veterinary services, testing, and reporting
- Role
- Full-stack developer
- Visibility
- Confidential case study
Overview
A business platform that runs veterinary service operations: user management, test and report workflows, orders and requisitions, tasks, payments, and client records.
Business problem
Veterinary service operations involve many connected records: the animals and sites being served, the tests requested, the reports produced, the orders and requisitions that authorise work, and the payments that close the loop. Handling these across spreadsheets and disconnected tools makes it hard to see the status of any single case.
The platform brings those workflows into one system so that internal staff and external users each see the records relevant to them, work moves through defined stages, and history is preserved for reporting.
Users and workflow
Internal users manage services, tests, orders, tasks, and reporting. External users interact with the records that belong to them, such as requisitions, reports, and payments.
A typical flow starts with a requisition or order, moves through task activities and testing, produces a report, and ends with payment and archived history.
- Internal and external user management
- Veterinary services
- Test and report workflows
- Wells and orders
- Requisitions
- Task activities
- Opportunities
- Reports and history
- Payments
- Client management
My role and contributions
Worked as a full-stack developer within a team. The list below describes the areas I contributed to; it is scoped to what I worked on and does not represent the entire platform.
- Implemented backend REST endpoints and Entity Framework Core data access for operational modules including orders, requisitions, and task activities.
- Built React and TypeScript screens for record management, list and detail views, and status-driven workflows.
- Worked on report and history features that read across multiple related entities.
- Investigated and fixed production defects, and maintained existing modules as requirements changed.
Technical stack
- C#
- ASP.NET Core
- REST APIs
- Entity Framework Core
- SQL Server
- React
- TypeScript
Architecture
Clients
- Internal staff web app
- External user web app
Frontend
- React
- TypeScript
- REST client
API
- ASP.NET Core Web API
- Validation
- Authorisation by user type
Data
- Entity Framework Core
- SQL Server
Technical challenges
Two audiences on one data model
Internal and external users need different views of overlapping records. Rather than duplicating screens, the API exposes the same resources with authorisation rules that decide which fields and actions are available to each user type.
Status-driven workflows
Requisitions, tests, and reports each move through statuses that unlock or block later steps. Keeping those transitions consistent between the API and the UI required the rules to live server-side, with the frontend reflecting rather than deciding state.
Design and engineering decisions
Entity Framework Core for the primary data layer
The domain has many related entities and frequent schema evolution. EF Core migrations and LINQ queries kept the data layer readable and made changes safer than hand-written SQL for the majority of operations.
Typed API contracts
Request and response models are explicit DTOs rather than entity types, which keeps the database schema out of the public contract and lets the frontend rely on stable shapes.
Results and lessons learned
- Delivered operational modules that run day-to-day veterinary service workflows in one system.
- Established a pattern of explicit DTOs and server-side status rules that later modules followed.
- Reinforced the value of keeping authorisation logic close to the data rather than in the UI.
Quantified business metrics are not published for this engagement; the results above describe delivered functionality and engineering outcomes.
Related
More case studies
Travel Management Platform
A business application for travel operations covering tours and groups, reservations, invoices, tasks, and integrations with external services and payment providers.
- C#
- ASP.NET Core
- REST APIs
- SQL Server
- JavaScript
Property Records Platform
A property records application built on a .NET 8 API using Clean Architecture, SQL Server, and multi-tenancy, with a React and TypeScript frontend.
- C#
- .NET 8
- ASP.NET Core Web API
- Clean Architecture
- Multi-tenancy