Booking, records and reminders — with the care data handled properly.

No. Clinical systems carrying formal NHS interoperability obligations are a specialist regulated category. What we build is the operational software around a practice — booking, client records, consent, reminders, payments — and we will tell you where that line sits for your setup.

Health data is special category data, so it needs a lawful basis under both Article 6 and Article 9, and the engineering has to match: access enforced in the data layer, an audit trail, defined retention with an actual stopping point, and encryption at rest and in transit. We build to that and document it. We are not your data protection officer.

Often, yes, and that is frequently the cheaper answer. We map what exists first — if the current system does the diary well and the gap is records and consent, replacing the diary is spending money on the part that already works.

Frequently not. For a small single-site practice an off-the-shelf product plus one integration is usually the right call. Bespoke starts earning its place when you have multiple sites, unusual constraints, or a way of working that no product handles without three workarounds.