Depuración Corporal

Depuración Corporal brings together the software used to run a health and wellbeing centre and the services through which patients interact with it. Its scope spans clinical administration, day-to-day operations, billing, online sales and patient communication across several branches.

Staff work in an Office application with areas for administration, practitioners and nutrition. Patients and professionals have web and mobile experiences appropriate to their tasks. Behind those interfaces, shared services connect appointments, published patient information, messages, orders and notifications.

The platform is in production and continues to develop. Its current architecture replaces an ASP.NET MVC and AngularJS application with modern .NET services while preserving the established business behaviour and existing public routes.

The centre needs continuity between a patient's record, professional availability, treatment follow-up, purchases and conversations with staff. At the same time, information intended for the care team must remain separate from information deliberately shared with a patient.

The technical challenge was to modernise a substantial existing application while keeping its operational rules intact. Web, mobile and staff interfaces also needed to evolve at different speeds without each creating a separate version of the underlying business logic.

A working environment for the centre

Office brings together patient records, structured history, consultations, phased treatment records, documentation and consent signatures. Schedules, tasks, notes, equipment, stock records and product catalogues support the surrounding administrative work. Staff areas and permissions organise access according to responsibility.

Scheduling around real availability

Appointments are organised by professional and branch. Weekly working patterns, absences and consultation types determine availability. Google Calendar integration connects scheduling with external calendars. Online booking depends on each centre's actual configuration; the platform does not create availability from unconfigured hours.

Patient communication with deliberate publication

The patient-facing services provide access to appointments, published summaries, treatment information, recipes, messages and orders. A professional chooses the summary a patient can see rather than exposing the entire internal clinical record. Internal notes remain part of the staff workflow, and real-time notifications prompt each client to retrieve information through its own authenticated API.

Nutrition as a separate functional area

The nutrition module includes food and nutrient catalogues, structured assessments, consultation records, recipes and meal-plan editing. Its calculation engine uses configured reference values and deterministic rules. Conversational assistants help structure information; calculations remain the responsibility of that engine. The software supports the practitioner’s work.

Online sales and administrative follow-up

The store connects product selection, basket, addresses, discount codes, orders and hosted Stripe Checkout. Server-side calculation keeps prices consistent, while payment confirmation comes from the payment provider. Sales documents and order logistics have separate lifecycles, allowing preparation and dispatch to progress without recreating the issued document.

Modern services and continuing rollout

The solution separates the internal staff API, public patient API, web applications, mobile application and background notification worker. .NET, Blazor, SQL Server, MAUI and SignalR support those responsibilities, with Linux and Docker used for deployment.

The production platform continues to expand its patient web screens and professional-facing services. Space reservations for external collaborators remain a planned extension. This gradual approach lets the working centre and its digital services develop together.

Explore our business application development and integration services.