About the client
The client operates diagnostic centres and works with an external laboratory partner for clinic booking, test ordering and results. Bookings, payments and order handling were largely manual, and the client had no in-house engineering team. It engaged FiftyFive Technologies to design and build a platform from the ground up that would let patients serve themselves and take the manual steps out of every order.
One booking, five systems
- Integrate several third-party APIs — the laboratory partner's booking and ordering APIs, Stripe, Airtable and AWS Location Service
- Orchestrate asynchronous steps in order: payment confirmation, slot reservation, order creation, then status and result polling
- Price bundled tests, add-ons and variable margins across sales channels
- Keep Stripe, the laboratory systems and Airtable consistent with one another
- Run high-frequency background jobs reliably, with logging and error handling.
What FiftyFive built
A dedicated four-person FiftyFive team — a solution architect, two backend engineers and a DevOps engineer — designed and built the platform and deployed it on AWS. The scope covered: the patient-facing booking flow: test catalogue, clinic search, appointment booking and online payment; a centralised API gateway in Express.js; modular services for booking, ordering, payments and data synchronisation; a Redis and Node-Cron workflow layer for background automation; a dynamic pricing engine with automated Stripe Checkout sessions; a resilient integration layer and containerised AWS deployment.
How the solution works
Booking and pricing
- Patients browse tests and locate clinics through AWS Location Service.
- The pricing engine calculates the cost of each test, bundle and add-on, applies fees and channel-specific margins, and creates a Stripe Checkout session.
- Each session carries reconciliation metadata so the payment can be matched to the order later.
API gateway and services
- All third-party calls pass through one Express.js gateway.
- Behind it, separate services handle booking, ordering, payments and data synchronisation, so a new test type or integration can be added without reworking the others.
Workflow automation
- Once a payment is confirmed, the order moves through slot reservation with the laboratory partner, order creation and status and result polling.
- Redis holds temporary data and queues the work; Node-Cron schedules the asynchronous and recurring jobs that drive each step and keep Stripe, the laboratory systems and Airtable in step.
Resilient integration
- The integration layer retries failed calls, refreshes access tokens and handles third-party API errors, with logging on background jobs so failures are visible rather than silent.
Data and deployment
- Order, sales and result data are consolidated in Airtable for the client's reporting.
- Services run in Docker containers on AWS.
Technology stack
What the solution enabled
Business transformation
Less manual effort
Faster turnaround
Automated order flow
70% less manual effort
Automating the booking lifecycle reduced the client's manual effort by 70%.
40% faster turnaround
Real-time order synchronisation improved booking-to-result turnaround by 40%.
One automated order flow
Payment, slot reservation, order creation and result tracking run without manual hand-offs.
Consolidated reporting data
Sales, orders and results are held in one place for the client's reporting.
FiftyFive Technologies built a self-service booking platform for a healthcare provider that runs diagnostic centres. Patients browse tests, find a clinic, book and pay online, while the platform automates the back office: payment confirmation, slot reservation with the laboratory partner, test order creation and result tracking. FiftyFive built an Express.js API gateway over modular Node.js services, a Redis and Node-Cron workflow layer, a dynamic pricing engine with Stripe Checkout and AWS deployment in Docker. The client reports a 70% reduction in manual effort and 40% faster booking-to-result turnaround.
Technical questions
How do you keep payments, laboratory orders and reporting data consistent?
FiftyFive Technologies attached reconciliation metadata to every Stripe Checkout session and ran scheduled Node-Cron synchronisation jobs, queued through Redis, that check status across Stripe, the laboratory partner's systems and Airtable. A shared integration layer retries failed calls and refreshes tokens, so a temporary outage at one provider does not leave an order half-processed.