Client work, published with permission.
The story separates what can be stated publicly from what must stay confidential, and links outcomes to approved evidence.
The problem being explored
Clinical and admin staff used several scheduling systems at once. Updates were missed, appointments were booked twice and time was lost checking one calendar against another.
What made delivery difficult
The provider needed one trustworthy view of every appointment that reflected each change straight away, without altering the systems underneath.
- Leave the source systems alone. Each system had to keep working exactly as before.
- Near-real-time. A change in any system had to show up for staff almost immediately.
- No lost or duplicate data. Conflicts had to be handled when several systems or people changed the same appointment.
- Sensitive information. Appointment and patient details needed healthcare-grade protection.
Connect product thinking to implementable decisions
We led the design and delivery of the platform.
- Solution architecture and technical leadership
- Adapters
- The event pipeline,
- Access control, auditing and logging
- Delivery automation,
- Runbooks and dashboards
How the work was shaped
The work maps to seven stages of our delivery lifecycle, from Discovery to Closure & Handover.
- Discovery. We mapped each source system, how it could be reached and what staff needed.
- Delivery Planning. Phased deliveries got working parts to users early.
- Build & Test. Light adapters for each system, time-stamped change events, fixed conflict rules and regular reconciliation.
- UAT & Launch Readiness. Releases tested by representative groups of staff before full cut-over.
- Operational Readiness. Monitoring, alerts, dashboards and runbooks were ready before cut-over.
- Hypercare. After cut-over, the team watched sync health and resolved conflicts.
- Closure & Handover. The client's team took over, with runbooks and dashboards in place.
Technology and structure
OneSync sits between the scheduling systems and the staff who use them.
- Adapters for each system. Each one listens for changes, or checks for them where it cannot listen.
- One data model. A shared way of describing an appointment, whichever system it came from.
- An event pipeline. Carries each change through in near real time.
- Conflict handling and reconciliation. Settles clashing changes by fixed rules and catches anything missed.
- One view for staff. Every appointment from every system, in one place.
- Monitoring dashboards. Sync health, delay and errors, visible to the team running it.
Risk, assurance and release boundaries
The controls protect sensitive information and keep the data trustworthy.
- Encryption in transit. All data moves over encrypted connections.
- Encrypted storage. Sensitive fields are stored encrypted.
- Role-based access. Staff see only what their role allows.
- Audit logging. Every change can be traced.
- Alerting. The team is told quickly when sync slows down or fails.
- Automated tests and staged releases. Run before every production change.
What can be stated publicly
The provider got a production platform that keeps appointments in sync across its systems while each system works as before.
- One view for staff. No more switching between tools or checking calendars against each other.
- Fewer clashes. Near-real-time sync and reconciliation reduced appointment conflicts and manual fixes.
- Earlier releases. Phased delivery and automated testing led to earlier-than-expected releases and smoother rollouts across clinical teams.
- Ready to grow. A reusable adapter and event framework makes adding new scheduling systems faster and lower risk.
What transfers to the next programme
What we carry into similar work.
- Respect the systems you connect to. Keeping each source system unchanged made the project safer and easier to agree.
- Decide the conflict rules early. Clear, fixed rules for clashing changes made the results predictable.
- Build the second integration into the first. A reusable adapter pattern turns the next system into a smaller job.