Before
Multiple platforms, multiple manual handoffs
Data and activities were split across tools. The secretariat had to re-enter information, check states and manually reconstruct a significant part of daily operations.
EMPV / Project02
Operating platform for a psychology center
Operations platform for a psychology practice
The problem was not booking. It was everything happening between one appointment and the next.
Patients, appointments, professionals, payments and administrative work lived across multiple tools. The secretariat had to re-enter information, manually check status and repeatedly reconstruct what had happened.
What we changedWe brought those handoffs into one operating flow.
System
One operational identity
Patients, professionals, appointments, settlement, packages and closure rules share one model, with server-side permissions and different views for each role.
01 / The problem
Centralize without losing separation and responsibility.
In a psychology center, putting everything in one database is not enough. Secretariat, professionals and management need different access, and private professional notes cannot simply become generic center data.
02 / The decision
One platform, explicit boundaries.
The design uses canonical patient and professional identities, center context, server-side authorization and audited corrections. Daily UX remains simple while rules and permissions stay authoritative in the backend.
03 / The system
Scheduling, sessions and administration in one flow.
Availability, booking, moving and cancelling sessions, closure, payment status, packages, the 48-hour rule, reminders, reports and authorized corrections are handled as one operating system.
04 / Architecture
Reuse mature foundations, build only the delta.
The technical direction starts from Frappe / ERPNext and Marley Healthcare, extending them with a dedicated layer where business rules, security or workflows cannot be represented correctly using native capabilities alone.