On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses acquisition-not-ready conditions involving coils, connections, scanner readiness, accessories, configuration, or other externally verifiable acquisition-path problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Stop Clinical Acquisition
If acquisition hardware is unreliable, do not continue scanning a patient in an attempt to determine whether the problem clears. End the affected workflow safely and move the patient to another verified imaging option if necessary.
Expected outcome: No patient depends on unreliable acquisition hardware.
2. Confirm the Exact Reported Condition
Determine what staff mean by “not ready.” Record any displayed message exactly and identify whether the problem occurs with every exam, one coil, one patient setup, or one specific protocol.
Expected outcome: The problem is narrowed to the overall scanner or a particular acquisition setup.
3. Verify General Scanner Readiness
Confirm the Canon Vantage Orian has completed startup and is otherwise in its normal ready state. Check for unrelated system warnings that may prevent acquisition hardware from becoming available.
Expected outcome: No broader startup or system-readiness condition explains the complaint.
4. Inspect the Selected MRI Coil
Inspect the coil being used for visible damage, damaged housing, contamination, unusual wear, or compromised cable condition.
Do not use a visibly damaged MRI coil clinically.
Expected outcome: The coil is physically intact and appropriate for evaluation.
If damage is present, remove that accessory from service and retest the scanner using an approved known-good compatible coil when appropriate.
5. Verify Coil and Accessory Connections
Check that accessible coil connectors and other examination accessories are fully seated, properly positioned, and free of obvious damage or contamination.
Do not force connectors or manipulate internal contacts.
Expected outcome: All accessible acquisition-related connections are secure.
If reseating an approved external connection restores normal readiness, proceed to verification.
6. Compare With a Known-Good Compatible Coil
When appropriate, substitute another approved compatible coil or accessory known to work on the system.
This helps separate a scanner-level problem from an accessory-specific problem.
Expected outcome: The result identifies whether the issue follows the original coil/accessory or remains with the scanner.
If the problem follows one coil, remove that coil from service and document the finding.
7. Verify Exam Setup and Coil Selection
Review normal operator-visible exam setup to make sure the intended coil, patient orientation, exam selection, and other routine settings are appropriate.
Do not alter restricted configuration or calibration values.
Expected outcome: The examination configuration matches the connected hardware and intended workflow.
8. Inspect the Scan Environment
Verify no obvious loose accessory, misplaced cable, recently added equipment, or environmental change is interfering with the normal acquisition setup.
Expected outcome: The external scan environment is suitable and no obvious setup problem remains.
9. Perform a Controlled Functional Check
With a known-good external setup, verify that the acquisition hardware reaches the expected ready state and that an approved test workflow can proceed as appropriate.
Expected outcome: The system recognizes required acquisition hardware and becomes ready without recurring warnings.
If achieved, troubleshooting can stop.
10. Escalate Persistent Acquisition-Readiness Failures
If multiple known-good coils or setups fail, acquisition hardware remains unavailable, or the system repeatedly drops readiness, stop external troubleshooting.
Do not access RF cabinets, receiver electronics, gradient hardware, internal cabling, or restricted service functions.
Expected outcome: The system is removed from clinical service for qualified evaluation.
If the Problem Persists
Common external coil, connection, setup, accessory, and scanner-readiness causes have been ruled out. The remaining problem may involve the RF receive/transmit path, interface hardware, system control, acquisition electronics, configuration, or another service-level subsystem.
The MRI system should be:
- Removed from service
- Labeled Out of Service
- Sent for qualified repair or system evaluation
- Evaluated using appropriate Canon documentation and approved MRI test equipment
- Repaired or configured only by qualified personnel
After repair, complete applicable acquisition checks, image-quality verification, and manufacturer-required return-to-service testing.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A coil that appears physically intact can still be unreliable; compare with an approved known-good compatible coil before assuming a scanner-level failure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"MRI staff reported the Canon Vantage Orian would not indicate acquisition readiness with the selected imaging coil."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the condition followed one specific coil while a known-good compatible coil was recognized normally."
Resolution
What action was taken.
Example:
"Removed the affected coil from service, verified normal scanner readiness with the known-good coil, and returned the MRI system to service after functional verification."
Helpful Details to Include (If Known)
- Exact message displayed
- Coil or accessory in use
- Visible coil or cable condition
- Connector condition
- Known-good substitution result
- Protocol or exam involved
- Whether other coils worked
- Scanner readiness status
- Results before and after correction
- Final scanner and accessory status
Final Thought
Acquisition problems should be separated logically into accessory, connection, setup, and scanner-level causes before internal failure is assumed. Protect the patient, use known-good comparisons where appropriate, verify restored performance, and escalate persistent system-level failures with clear documentation.
That is successful troubleshooting.