Security and data protection
Medical records are special category data under UK GDPR. This page says, in plain terms, where they are kept, how they are read, who can see them and what is logged. It also says what NuvMed does not claim.
Where records are kept
- Hosted in the UK
- NuvMed and the records uploaded to it are hosted in the UK. Text sent to the AI provider named below is processed outside that host.
- Encrypted in transit
- Every connection from your browser to NuvMed is served over HTTPS.
- Originals kept
- The files you upload are stored as uploaded, so any page can be opened or downloaded exactly as it arrived.
How records are read
- Who processes the text
- Entries are written, and questions about a case answered, using OpenAI's API. OpenAI is a processor of the clinical content sent to it. No other third party receives record text.
- Identifiers removed before sending
- The claimant's name in each of the forms the records write it, their date of birth, NHS number, postcode, telephone number and email address, and the clinician and practice names, are replaced with placeholders before any text leaves the server, and put back in what you read. This is pseudonymisation, not anonymisation: the clinical content still goes, and a consultation history describes an identifiable person.
- What is not sent
- Uploaded files never leave the server. Only the text of the entries being written, or the entries matching a question you ask, is sent - never the whole bundle.
- Nothing unchecked is shown
- Every written entry is checked back against the record it came from: negations preserved, no number that is not in the entry, no word that cannot be traced to it. An entry that fails is shown as the original note instead, and labelled.
- Rules where rules are exact
- Dates, page numbers and the split into entries are taken from the document by rule, not generated by the model.
Who can see a case
- Your organisation only
- A case belongs to the organisation that created it. A request for any other organisation’s case is answered as if the case did not exist.
- Verified accounts
- Every account confirms its email address with a one-time code before it can sign in.
- Passwords hashed
- Passwords must meet length and character rules, and are stored only as salted hashes.
- Short sessions
- Sign-in lasts for the browser session. Close the browser and you are signed out.
What is recorded
- Audit trail
- Sign-ins, case creation, uploads, case and page views, file downloads, edits, flag decisions and exports are logged with who, when and from where.
- Reproducible reviews
- Each review records the model and the settings that produced it, so a chronology can be traced to the run that made it.
- Deletion
- An administrator can delete an account together with its cases and records.
What we do not claim
- We do not display security certifications NuvMed does not hold, and we do not borrow our infrastructure provider’s certificates as our own.
- “MedCo compliant” is not a claim software can make. MedCo accredits medical experts and registers MROs; it does not certify software.
- NuvMed does not publish an accuracy percentage. It shows its work instead: every entry is cited to its page, and every page it could not read is listed.
See how a case is handled end to end.
Every stage, from the identity check to the Word export.