Sick Notes and Medical Certificates: Altered PDFs in Absence Management

This article is a snapshot – content was accurate as of November 2026 (code examples tested against the API as of October 2026). The product evolves actively; specific counts, examples, and detection rules may have changed since publication – see the changelog for the current state.
A sick note that reaches HR as a PDF gets read like any other document: the name, the dates, the healthcare professional’s details, whether the period it covers matches the absence on the rota. Whether the file is still the one the practice produced is a separate question, and reading the page cannot answer it. A file-level check answers only that question, and its result is a reason for a human conversation, never a finding about the employee.
This is for HR operations, absence-management and payroll leads deciding what to do when a note looks off: how notes arrive as files, what a file check adds, what it never looks at, and how to fit it into an absence process without turning it into blanket screening.
How sick notes reach HR as files
Under GOV.UK’s sick leave guidance, an employee who has been ill for more than 7 days in a row, non-working days included, needs to give the employer a fit note; for 7 days or less, no fit note is needed. The fit note guidance for employers notes that a fit note may be printed out or sent digitally to the employee, and says the employer can take a copy for its records while the employee keeps the original.
Whatever the rules, the copy HR holds usually comes through the employee:
- A file forwarded by email or uploaded to the HR system. The employee received the note digitally and passed it on.
- A scan of a paper note. Printed by the practice, scanned on a home printer or at the office.
- A phone photo saved as a PDF. Often the quickest route for someone who is unwell.
Most routes run through a device the employee controls, and usually that means nothing more than a note being passed along.
What an altered note looks like in an absence process
When a note has been changed, it usually shows up as a mismatch that matters to the process: a longer absence period, dates covering a different stretch of time, or a different name. The question is whether the note in the file is the note that was issued.
Not every change is dishonest. An employee may correct a date the practice got wrong, or black out a detail they did not want to share with their employer. A modified result reports that the file was changed. It does not say who changed it or why, and your process should not guess.
Why reading the page misses a later edit
Page-level review still matters. The GOV.UK employer guidance says a fit note without the healthcare professional’s signature or name ‘should not be accepted as it may not be genuine’. That is a check on what the page shows.
A note changed after it was issued can still show everything a complete note should: the practice details, the professional’s name, the signature. Screen review and text extraction both see the file as it is now, and neither can compare the submission with an original the reviewer never held.
What a file-level check adds
HTPBE? looks only at the file’s structure. It does not read the note, the diagnosis or any medical detail, and it says nothing about whether the employee was ill. It answers one question: does this PDF show evidence of being changed after it was created? The answer comes back as one of three verdicts (the medical certificate tamper detection page covers this document type).
| Verdict | What it means | What HR does |
|---|---|---|
intact | No modification was detected in the file | Handle the absence as your policy says |
modified | The file carries structural evidence that it was changed after it was created | Follow up with the employee; the result is a reason to ask, not a conclusion |
inconclusive | HTPBE? cannot confirm the file as an untouched original | Handle the absence as your policy says; the result neither flags nor clears the note |
Scanned, photographed and office-exported notes often come back inconclusive. That is normal for this document type, not a warning sign – and not a clearance either: the page checks your policy already requires still apply.
A modified result is a reason to follow up: ask the employee first, and if a question remains, contact the issuer through the established route. It is not proof of misconduct, and it must never be the sole basis for disciplinary action, pay decisions or dismissal. The employee should have a way to explain or contest it. The API makes the same point in every result: usage_caution.safe_for_automated_adverse_decision is always false.
What the file check does not do
HTPBE? is a structural PDF tamper-detection check, not a medical or employment check. It does not:
- read the diagnosis, the fitness-for-work advice or any other medical content;
- say whether the employee was ill, or whether the absence was justified;
- confirm that the practice or the healthcare professional exists, or that the note appears in the issuer’s records;
- say who changed a file or why.
Content that was false from the start carries no evidence of a later edit. intact means no modification was detected, not that the document is genuine. Whether a note was properly issued is a question only the issuer can answer.
Where it fits in an absence process
Most notes need nothing more than the normal process, and trusting them by default is the right starting point. A file check is a proportionate extra step for the cases that warrant one, not a screen for every absence. A workable sequence:
- Start from what the policy already requires. Check only documents your absence policy already requires the employee to provide, and only where the document type justifies it. If you only need the length of an absence, you may not need the medical certificate at all – the ICO’s guidance on sickness and injury records says employers should not use sickness records when they only need to know how long an absence lasted.
- Check that file, and only that file. The result is one input among several.
- Follow up as people, not as a system. On
modified, talk to the employee. If a question remains, the issuer is the authority on whether the note is theirs; occupational health can complement that conversation, not replace it. In the US, the Department of Labor’s FMLA fact sheet sets the limits for leave covered by the FMLA: only a human resources professional, a leave administrator, a management official or a health care provider may contact the employee’s health care provider, and only to authenticate or clarify the certification. The employee’s direct supervisor may never do so, and once the employer has a complete and sufficient certification it may not request additional information from the provider. Under the ADA, 29 CFR 1630.14(c)(1) requires medical information obtained from employees through medical examinations or inquiries to be kept confidential, on separate forms and in separate medical files. - Let the employee respond. Record their explanation with the result and decide on the whole picture, never on the verdict alone.
This check sits later in the employment relationship than pre-hire document checks, which deal with documents a candidate submits before they join. If the absence turns into an injury claim, the questions shift to insurers and wage records – see altered medical and wage documents in workers’ compensation. The payer-side counterpart, where insurers review pharmacy and prior-authorisation PDFs, is covered in medical claims document checks.
Data handling before you add the check
Health information is special-category data. Before adding this check, confirm your lawful basis and the employment-law condition, update your appropriate policy document and employee privacy notice, and consider a DPIA. Rules on what employers may request differ by country. Take advice from your data protection officer or counsel. The ICO also says consent is unlikely to be an appropriate basis for sickness records, and that records holding details of an illness should be kept apart from less sensitive information where possible.
For employee medical documents, use the API (files are fetched, analysed and not stored) or an on-premise deployment, not the website uploader.
With the API, serve the note from private storage through a short-lived presigned URL with a neutral object name – never a public or shared link. The presigned URL walkthrough shows the set-up.
Pass a neutral original_filename, such as a reference number, not the employee’s name or condition. It is stored and returned with the result; without it the API takes the file name from the end of the URL when there is one, so keep the object name neutral too.
Frequently asked questions
Does HTPBE? tell us whether the employee was ill?
No. HTPBE? looks only at the file’s structure. It does not read the note, the diagnosis or any medical detail, and it says nothing about whether the employee was ill. It answers one narrow question about the PDF – whether it shows evidence of being changed after it was created.
Should an inconclusive result on a sick note worry us?
No. Scanned, photographed and office-exported notes often come back inconclusive. That is normal for this document type, not a warning sign – and not a clearance either. Handle the absence as your policy already says, including the checks it already requires on the note itself.
Can we take disciplinary action on a modified result?
No. A modified result is a reason to follow up – first by asking the employee, then, if needed, with the issuer through the established route. It is not proof of misconduct and must never be the sole basis for disciplinary action, pay decisions or dismissal. The employee should have a way to explain or contest it.
Adding the check to your absence process
If your HR system already stores the notes your policy requires, the API documentation covers authentication, the request and the full result, including usage_caution.