LINAC Maintenance: Service Plans and Work Records
A LINAC maintenance plan uses equipment documents, service history and site conditions. Record preventive maintenance, fault intervention and clinical checks as separate scopes with named owners.
How is a LINAC maintenance plan defined?
A LINAC maintenance plan uses equipment documents, service history and site conditions. Record preventive maintenance, fault intervention and clinical checks as separate scopes; one schedule does not fit all equipment.
What information supports preventive maintenance?
Record the manufacturer and model, installation and service history, recurring faults, open issues, access window and site contact. The checklist and frequency should come from the relevant device documentation, service agreement and site requirements, rather than a generic blog schedule. Findings, work performed and follow-up actions should be recorded.
How does fault response differ from planned maintenance?
A fault request should describe when symptoms began, visible error information, the current device state and recent work. This helps the first assessment but does not amount to a definitive remote diagnosis. Urgency is evaluated with the hospital's operations team. Intervention, parts and third-party support may be separate work packages.
How should parts and warranty be handled?
Suitability for the specific device configuration, availability, condition, shipment and any manufacturer or service conditions must be checked for the actual part. A proposal should separate labour, parts, logistics and verification. “Original” or “compatible” alone does not promise suitability or a warranty outcome for a particular machine.
What records should follow a service visit?
The work order should identify the device, date, reason for the visit, tasks performed, observations, open items and owner of the next action. Acceptance or return-to-use decisions follow the authorised project and clinical responsibilities. Consistent records help identify recurring issues and revisit the service scope.
Which decisions connect a fault report to return to use?
Initial record: Note when the symptom began, visible error information, the current equipment state, recent work and the site contact. Do not put patient or treatment details in a public enquiry form. Follow the facility's own safety and clinical escalation route.
Technical work: The authorised service party records the investigation, parts inspected or changed, software or setting changes and unfinished work in a traceable work order. An error code alone does not prove the cause of a fault or the suitability of a proposed part.
Return to use: If an intervention could affect safety or dosimetry, the authorised medical physics and clinical team determines the required checks. Closing a service ticket is not the same decision as permitting patient treatments. The facility separately records its approval and any next check date.
How could an “uptime” figure be measured?
Before publishing a percentage, define the devices included, measurement period, planned service time used as the denominator, what counts as unplanned downtime, how scheduled maintenance is treated and the source of the data. A short period on one machine cannot describe an entire fleet or promise future performance. If these fields and a reviewer are missing, describe the service scope and recording method instead of promising a percentage.
Is the maintenance interval the same for every LINAC?
No. Model, manufacturer instructions, use and contract terms differ. Use the plan approved for the relevant device and site rather than applying a single interval to all systems.
What should I include in a service enquiry?
Provide the model, project country, service history, present problem or maintenance objective, access window and contact person. Do not put patient information or sensitive system data in a public web form; agree a private channel if needed.
Turn a service enquiry into a traceable work record
One “fault resolved” entry cannot explain the work and outstanding decisions. Separate the enquiry, technical intervention and clinical-return records. These fields can support a scope discussion with RF; the equipment and contract define the actual intervention and authority.
| Task / decision | Required input | Expected record | Scope boundary |
|---|---|---|---|
| Enquiry | Model, symptom, onset and previous intervention | Enquiry reference, institutional contact and initial assessment | No patient data or confidential access information |
| Intervention | Agreed scope and applicable technical documents | Findings, work, parts/settings and open items | One fault code is not a diagnosis |
| Technical handover | Work record and affected functions | Further checks and responsible parties | Closing service work does not release clinical use |
| Performance measurement | Equipment cohort, period and downtime definition | Numerator/denominator, exclusions and data source | No unmeasured uptime or response-time promise |
Illustrative use — not a record of an RF project. If an interruption time is recorded but planned maintenance treatment in the denominator is unspecified, percentages from two periods cannot be compared consistently. Fix the definition first. This guide publishes no RF uptime result or guaranteed service level.
Further reading
- IAEA guide to radiation safety in medical uses: provides a general framework for maintenance records, checks after work that may affect safety and facility responsibilities. Device-specific service instructions and local requirements also apply.
Related service
The LINAC maintenance service explains scope options. In a service enquiry, share the equipment model, objective or fault symptoms and access window; use a separate channel for sensitive data.
Let's talk about your radiotherapy project.
Installation, relocation, shielded doors or spare parts; tell us what you need and our technical team will get back to you.
Get a quote