On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots unavailable barcode scanning or patient-identification workflow caused by scanner, connection, configuration, workflow, or communication problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Prevent Identification Errors
Do not allow a barcode or patient-ID problem to create an incorrect patient association.
If the identification workflow is unreliable, stop electronic association through the affected pathway and follow the facility's approved alternate patient-identification and documentation process.
Expected outcome: Patient measurements cannot be inadvertently assigned to the wrong patient while troubleshooting proceeds.
2. Confirm the Exact Failure
Determine whether:
- The barcode scanner has no response
- The scanner activates but does not read a barcode
- A scanned ID appears but is not accepted
- The patient lookup function is unavailable
- The patient-ID field cannot be accessed
- The entire patient-assignment workflow is missing
- The failure affects one monitor or multiple monitors
Record any exact displayed message.
Expected outcome: The failure is clearly defined as scanner-related, workflow-related, or communication-related. If the workflow functions normally during repeated testing, troubleshooting can stop after verification.
3. Verify Basic Monitor Operation
Confirm the Portrait VSM is operating normally and can obtain local vital-sign measurements.
Check for broader touchscreen, application, or system-response problems that might make the ID workflow appear unavailable.
Expected outcome: The monitor is responsive and the issue is isolated to patient identification. If the entire interface is unstable, remove the monitor from service for broader evaluation.
4. Inspect the Barcode Scanner and Cable
If an external scanner is used, inspect:
- Scanner housing
- Cable
- Connector
- Strain relief
- Accessible scanning window
- Signs of contamination or impact damage
Disconnect and reconnect the scanner using its intended connection.
Expected outcome: The scanner is securely connected and physically intact. If reseating restores normal scanning, repeat several test scans and troubleshooting can stop.
5. Test With a Known-Good Barcode
Use an approved test barcode or other non-patient test identifier appropriate for the facility workflow.
Check whether the scanner:
- Activates
- Reads consistently
- Enters the expected characters
- Sends the scan to the correct field
Avoid testing with a real patient's identity unless required by approved workflow.
Expected outcome: The scanner consistently reads valid test data. If it does, investigate workflow or backend acceptance rather than scanner hardware.
6. Substitute a Known-Good Scanner
If the scanner is externally replaceable, connect a known-good compatible scanner.
If the known-good scanner works immediately, retest the suspect scanner on another compatible monitor when practical.
Expected outcome: The failure either follows the scanner or remains with the Portrait VSM. If the scanner is confirmed defective, replace it and troubleshooting can stop after final verification.
7. Verify the Patient-ID Workflow on the Monitor
Confirm the expected patient-identification function is available within the authorized operating configuration.
Check for:
- Logged-in versus logged-out workflow differences
- Missing patient-selection controls
- Incorrect operational profile
- Obvious configuration changes
- Required network-dependent workflow being unavailable
Do not modify protected configuration without authorization.
Expected outcome: The correct patient-ID workflow is available. If an authorized configuration correction restores the function, verify it and troubleshooting can stop.
8. Determine Whether the Failure Is Local or Facility-Wide
Check another Portrait VSM using the same patient-ID workflow.
If multiple monitors are affected, determine whether they share:
- The same network area
- The same backend patient-data service
- The same configuration deployment
- A common recent infrastructure change
Expected outcome: The scope of the problem is identified. A multi-device failure should be escalated as a likely infrastructure or application issue rather than treated as multiple independent scanner failures.
9. Verify Network Availability When Required
If patient lookup or ID validation depends on network connectivity, confirm the monitor shows expected network availability and that other network-dependent functions behave normally.
Clinical Engineering may verify accessible network connection status but should not make unapproved network or security changes.
Expected outcome: Network-dependent patient identification is available. If local network restoration resolves the workflow, repeat the identification test and troubleshooting can stop.
10. Verify Complete Patient-ID Workflow
Using an approved test workflow, confirm:
- Scanner reads the test identifier
- The correct field receives the information
- Patient lookup or identification proceeds
- The monitor does not associate the test with an unintended patient
- The workflow remains available after normal navigation
Expected outcome: Patient identification works consistently from scan through acceptance. Troubleshooting can stop.
11. Escalate if the Workflow Remains Unavailable
If the scanner, connections, monitor operation, configuration, and accessible network status are verified but the patient-ID workflow remains unavailable, stop external troubleshooting.
Expected outcome: The issue is escalated to the appropriate Clinical Engineering, IT, integration, application-support, or vendor resource based on the failure scope.
If the Problem Persists
Common external causes involving scanner condition, cables, connections, local workflow, configuration, and basic network availability have been ruled out.
The remaining issue may involve monitor software, internal USB or scanner interfaces, patient-data services, authentication, middleware, EMR integration, network infrastructure, or centralized configuration.
If the fault appears local to one monitor and compromises reliable patient association, the device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate GE Healthcare documentation and approved test equipment
- Repaired or configured only by qualified personnel
If multiple monitors are affected, coordinate with the appropriate IT, integration, application, or vendor support team rather than altering devices independently.
Before return to service, verify the complete patient-identification workflow from scanner input through correct patient association.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
When patient identification is unreliable, prevent incorrect chart association by using the facility's approved alternate identification and documentation process.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Portrait VSM barcode scanner would not enter patient identification information."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found that the scanner cable connection was intermittent and a known-good scanner operated normally on the monitor."
Resolution
What action was taken.
Example:
"Replaced the defective scanner, verified repeated barcode entry and correct patient-ID workflow with approved test data, and returned the monitor to service."
Helpful Details to Include (If Known)
- Exact patient-ID or scanner message
- Whether the scanner activated
- Whether barcode data appeared
- Scanner and cable condition
- Connection used
- Known-good scanner results
- Whether manual patient-ID entry worked
- Network status
- Whether other monitors were affected
- Patient lookup behavior
- Configuration or profile observed
- Results of final workflow testing
- Final device status
Final Thought
Protect correct patient identification first, isolate the scanner from workflow and network causes methodically, verify the complete identification path before assuming internal failure, escalate shared-system problems appropriately, and document the findings clearly.
That is successful troubleshooting.