A biomedical service report is the legal record of what you did to a piece of medical equipment. If it is not written down, it did not happen — and Joint Commission, DNV, and CMS surveyors will ask to see it.
The problem most new BMETs run into is not knowing what is required vs. what is just nice to have. This guide walks through the fields a defensible report includes, the order that makes it readable, and a worked example you can use as a template.
The eight fields every service report needs
Across hospital systems, ISOs, and AEM programs, the same core fields show up. If your report has these eight, you have what a surveyor needs:
- Date and time of service
- Technician name and credentials
- Customer / facility / department
- Device identity — manufacturer, model, serial number, asset tag (or control number)
- Reason for service — PM, repair, incoming inspection, recall, user error
- Findings — what you observed, including readings and error codes
- Action taken — parts replaced, calibrations performed, tests run, with results
- Outcome — back in service, removed from service, awaiting parts
Structure your report so it can be skimmed
Reports are rarely read end-to-end. A nurse manager wants to know if the pump is back in service. A risk manager wants to know what failed. A surveyor wants to know that you followed the OEM procedure. Put the answer to each of those questions in its own labeled section.
A reliable order: Customer Info → Device Info → Reason → Findings → Action Taken → Test Results → Outcome → Parts/Labor. Avoid burying the outcome in a paragraph of narrative.
Write findings and actions in past tense, with measurements
Replace vague language ("checked the pump", "looked okay") with specifics ("Verified flow rate at 125 mL/hr per OEM spec; measured 124.6 mL/hr — within ±5% tolerance"). Numbers, tolerances, and OEM references are what make a report defensible.
If you used a test device, log its name, model, and last calibration date. If you replaced a part, log the part number and lot number.
Worked example
Reason for service: Scheduled annual PM per OEM service manual rev. 4.
Findings: Device powered on without error. ECG, SpO2, NIBP, and temperature modules passed self-test. Battery held 4h 12min on internal power (OEM spec: ≥ 4h). Alarm volume tested at 60dB minimum per IEC 60601-1-8. No physical damage to housing, cables, or accessories.
Action taken: Cleaned exterior with hospital-approved wipes. Verified firmware rev. K.21.04 — current. Performed electrical safety test using Fluke ESA620 (cal date 2026-02-14): chassis leakage 12 µA (limit 100 µA), ground resistance 0.08 Ω (limit 0.2 Ω). Replaced NIBP cuff hose (PN 989803160881) due to minor cracking.
Outcome: PM complete. Device returned to service. Next PM due: 2027-03-28.
PM — IntelliVue MX800 Patient Monitor — SN US41902847
Three things that make reports fail an audit
- Missing test equipment calibration date — surveyors will ask for it.
- Outcome ambiguity — "appears to be working" is not an outcome. Use "returned to service" or "removed from service pending parts".
- No reference to OEM procedure when one exists — if the manufacturer publishes a PM procedure, your report needs to reference it.
Speeding this up without cutting corners
The fastest BMETs are not writing less — they are writing the same things every time, in the same order, with templates that pre-fill the boilerplate. TESSA was built around this idea: capture the variable details (device, findings, action, parts), and the report structure is generated for you in the order surveyors expect.