Medico-legal · SK Medical

From booking a medical expert to a delivered, invoiced report, in one pipeline instead of a chain of phone calls.

Booking a medical expert for an injured claimant and getting the report back meant phone calls, paper diaries and Word documents, with nothing joining the booking to the report to the invoice.

Talk to us about something similarAll case studies
ClientSK Medical
SectorMedico-legal
WhenLive, V1; rebuild on the Prolink platform planned
Used byMedical experts, medical reporting organisations and solicitor agencies, the back office, and external API consumers
Plugs intoGRIP, Proclaim, MedCo, Bott and Co medhub API, Google Maps, Postmark
AINone. This one runs on rules, not models.
What we built

Availability, booking, the report itself, and everything that has to happen when it is published.

A drag-and-drop expert availability calendar with live status counters, search across client, solicitor and case reference, and batch slot creation.
A map-based search and booking journey from claimant postcode, specialism, distance and date window, honouring each agency's expert inclusions, exclusions and tiers.
A structured report writer driven by an admin-maintained library of question groups, questions and canned answers with merge fields, plus dedicated injury sections.
Publish-time orchestration that generates the invoices, the compliance CSV, the report and guidance PDFs and the delivery bundle pushed to the agency.
Expert onboarding by professional registration number into a pending account, due-diligence document uploads and admin activation.
A fee engine with per-expert, per-specialism and per-agency schedules, generating PDF invoices so no report goes out unbilled.
orchestration

One click at publish

Invoices, the compliance file, the PDFs and the delivery bundle, including the platform fee, from one action.

resilience

Self-healing delivery

Payloads stored, retried on a schedule, escalated by email on final failure, with a raw audit view in both portals.

no-code

Reports experts can change

A three-level question library with merge fields lets non-developers change what every report asks.

How it plugs in

Pushed to the agencies that commission the work.

Appointments and reports go to the reporting organisations' own systems, each through its own channel, with every push logged and retried.

The applicationGRIPProclaimMedCoBott and Co medhub APIGoogle Maps
job A retry queue regenerates and re-posts failed submissions, and after the third failure stops and emails a person
job A report chaser finds attended appointments still awaiting a report and emails each expert their outstanding count
job File-drop processors watch for new and rearranged appointments and documents and push them to a partner's API
What changed

The manual chain of phone calls, diaries and Word documents became a single self-service pipeline from booking to a delivered, invoiced report, with each published report billed automatically.

one detail only this project hasExperts sign in with their professional registration number rather than an email, and sign the licence agreement on screen at first login, with the signature embedded into a stored PDF.
Something similar?

A booking process that lives in a paper diary?

Book a walkthroughRequest a callback