Skip to main content
Case Study

Real redaction for real clinicians.

How the British Society of Echocardiography uses Redactr to strip patient data from clinical reports before they enter their accreditation platform. Permanently.

Customer

British Society of Echocardiography

Sector

Medical Accreditation

Sign up free Watch the walkthrough

Background

The UK standard for echocardiography accreditation.

Founded in 1990 and registered as a charity, BSEcho supports over 5,000 members across the UK, Ireland, and 30 other countries. Its membership includes cardiac physiologists, cardiologists, clinical scientists, intensivists, radiologists, and anaesthetists.

BSEcho Logbook is the platform candidates use to build and submit their portfolios for accreditation assessment. It was built by ECS Software Consulting Ltd., a UK-based software consultancy. Logbook supports six accreditation pathways, from TTE and TOE to stress, critical care, congenital, and Level 1. Each requires candidates to document real clinical cases with supporting report evidence.

The Challenge

Medical reports contain patient data. That's the point.

Every echocardiography report submitted through Logbook is a real clinical document. It contains the information that makes it clinically useful: the patient's name, date of birth, NHS number, referring clinician, GP surgery details, and the scan findings. That data is there because it has to be.

The risk isn't a visible name on a PDF. It's the data that stays in the file after you think it's gone. BSEcho needed a solution that removed it completely, so every document on the platform was clean at the byte level. Not just the surface.

Watch the BSEcho Logbook × Redactr integration walkthrough

How It Works

Five steps from upload to submission.

  1. Step 1

    Upload

    The candidate uploads their echocardiography report PDF to the case in Logbook.

  2. Step 2

    Suggest

    Logbook prompts the candidate to run Redactr Suggest. The uk-medical agent reads the document and returns a list of suggested redactions.

  3. Step 3

    Review

    The candidate reviews each suggestion. They can dismiss any they disagree with, or add manual redactions to any area of the document.

  4. Step 4

    Redact

    The candidate runs Redactr Redact. The API applies full-depth redaction to every selected region, permanently removing the data from the file.

  5. Step 5

    Submit

    The candidate attaches the redacted report to their case and submits it for assessment. The assessor sees the clinical work. Nothing else.

Ready to build with Redactr?

No credit card required. Hard stops at your limit, never a surprise bill.

Start with 100 free pages Read the docs

Redactr Features

The tools behind the workflow.

Suggest API

The uk-medical agent reads clinical documents in full and returns suggestions for sensitive fields. It understands context, not just named fields.

Redact API

Permanent, full-depth redaction. Redactr removes the data from the file entirely. Not covered, not hidden.

Manual Redactions

Candidates can mark any area of a document for redaction — in addition to or instead of the agent's suggestions.

UI Libraries

Logbook embeds the suggest and redact workflow directly using Redactr's frontend libraries.

0

Patient records retained

5,000+

BSEcho members

6

Accreditation pathways supported

Ready to build with Redactr?

No credit card required. Hard stops at your limit, never a surprise bill.

Start with 100 free pages Read the docs