Identification
Available manufacturer, model, identifier and configuration.
MRI TECHNICAL SUPPORT
Technical support for MRI systems
An MRI service request requires a coordinated view of the system, its configuration, the observed behaviour and the operating conditions. We collect the available information to identify the necessary checks and define a technical scope suited to the case.
APPROACH
From observed behaviour to a defined activity
Manufacturer, model, identifier and configuration help identify the system; messages, issue frequency and recent activities describe the context of the report. Keeping these details separate avoids premature conclusions.
The first assessment can clarify which information is missing and which checks should be considered. Timing, parts, access and method are confirmed only after this assessment and are not implicit in the initial request.
Technical communications must not contain health data, patient information or credentials. Only the information required to identify the system and describe the issue is relevant.
Report
Observed behaviour, messages, frequency and conditions in which it occurs.
Assessment
Identification of the checks and information still required.
Scope
Definition of activities, access, dependencies and materials to confirm.
PREPARE THE REQUEST
Useful information makes the issue easier to interpret
A chronological description is often more useful than a proposed diagnosis: when the issue first appeared, under which conditions, whether it is continuous or intermittent and which recent activities took place.
Photographs or technical extracts can be considered only when relevant and free from unnecessary data. Any file transfer should use a suitable channel agreed in advance.
- System identifier and configuration
- Messages reported by the system
- Issue conditions and frequency
- Recent technical activities
- Contact and access conditions
PATHWAY
Four steps before confirmation
The pathway is adapted to the system and available operating conditions.
- 01
Identify
Confirm the system, configuration and technical contact.
- 02
Describe
Organise symptoms, messages, conditions and recent events.
- 03
Assess
Identify checks, dependencies and missing information.
- 04
Define
Confirm activities, materials, access and responsibilities.
USEFUL QUESTIONS
Before getting started
Can the fault be established from the first message?
The first message frames the report. Diagnosis and the required activity depend on checks for the specific case.
Are parts and timing already included in the request?
No. Requirements, availability and timing are confirmed after the available information has been assessed.
Which information should I not send?
Do not send health data, patient information, credentials or content unnecessary for handling the technical request.
Have a system or project to discuss?
Tell us what support you need, where the facility is located and what matters most to you. Let’s start there.