Lab reports in the patient file: integration versus attachments
2026-10-28 · MedSlay
Every patient arrives with reports. A folder of printouts from the last three labs, a photograph on WhatsApp, a PDF a relative forwarded that morning. The doctor reads them, makes a decision, and hands them back. A year later, when the same patient returns, nobody can say what the numbers were.
Clinic software usually offers one of two answers: integrate with labs so results arrive directly, or attach the reports to the patient's file. Both have a place. Here is what each actually gives you.
What a lab integration really means
A lab integration is a direct connection between your software and a laboratory's system. You order a test, the lab runs it, and the result arrives in the patient's record as structured data: each value in its own field, with the reference range beside it, ready to be plotted against last time.
That is genuinely useful, with three conditions:
- It only covers the labs you are connected to. Patients in India use whichever lab is nearest, cheapest or their insurer prefers. A result from any other lab arrives on paper anyway.
- Every lab is a separate project. Each connection has to be built, tested and maintained, by the software vendor and the lab together.
- It does nothing for the reports patients bring with them, which in most OPDs are the majority.
For a hospital with an in-house lab, integration is often worth it. For a clinic whose patients test all over town, it covers a fraction of the reports that actually cross the desk.
What attachments give you instead
Attaching means storing the report itself, a scan, a photo or a PDF, in the patient's file, against the visit it belongs to. It works for every lab, every format, and every report a patient walks in with.
What it does not give you on its own is structured values: a scanned page is a picture of a number, not a number. The doctor still reads it. But it is a picture that will still be there next year, filed where the next doctor will look, and that is more than most clinics have today.
Questions to ask before paying for either
- Which labs are actually connected? Ask for the list, and compare it with where your patients go.
- What happens to reports from other labs? If the answer is "scan them", you need good attachments anyway.
- Which formats are accepted? Photos from a phone are how most reports arrive. PDF alone is not enough.
- Can a report be tied to a visit, or does it go into a general pile on the patient?
- Who uploaded it, and when? If a report goes missing or the wrong one is filed, you need to know.
Filing a report so it can be found next year
The habit matters more than the software:
- Attach it during the visit, not at the end of the day, while the patient and the report are both in front of you.
- File it against the visit where it was reviewed, so the record shows what the doctor saw when they decided.
- Give it a title a stranger would understand: the test and the date, not "report 3".
- Return the original to the patient. The file holds a copy; the patient keeps their paper.
- Note the important values in the clinical note as well, so the finding is readable without opening the file.
Where MedSlay helps
In MedSlay a report is uploaded straight into the patient's record as a JPG, PNG or PDF, so a photo from a phone works as well as a scan. Each report can be linked to the visit where it was reviewed, and the record shows who uploaded it and when. In the IPD, reports can be attached at each round on the daily chart.
Where a practice has switched it on, the doctor can also ask the AI to read the reports attached to a visit and draft a revised clinical summary from what they show. It needs the patient's consent, it runs a limited number of times a day per patient, and it is advisory: the draft is saved as a new version for the doctor to check and confirm, never as the final word. MedSlay does not offer direct lab integrations today; it is built on the attachment side of this choice, because that is where most reports are.