| Model Number |
ORG-9110A |
| Medical Device Problem Codes |
Unable to Obtain Readings (1516); Communication or Transmission Problem (2896)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
07/13/2026
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
The biomedical engineer (biomed) reported that the multiple patient receiver (org) was showing comm loss for all 8 receiver cards.Each receiver card successively going into comm loss throughout the day until they were all in comm loss.No patient harm was reported.
|
| |
|
Additional Manufacturer Narrative
|
|
The biomedical engineer (biomed) reported that the multiple patient receiver (org) was showing comm loss for all 8 receiver cards.Each receiver card successively going into comm loss throughout the day until they were all in comm loss.This device was a loner, and they had received the original device back but had not yet swapped it back in.Technical support (ts) recommended that he reboot the org, replace the ethernet cable, and move the device to a different network port.He later confirmed that making these changes did not resolve the issue.No patient harm was reported.Nihon kohden continues to investigate the reported event.Nihon kohden will submit a supplemental report in accordance with 21 cfr section 803.56 when additional information becomes available.
|
| |
|
Event or Problem Description
|
|
The biomedical engineer (biomed) reported that the multiple patient receiver (org) was showing comm loss for all 8 receiver cards.Each receiver card successively going into comm loss throughout the day until they were all in comm loss.No patient harm was reported.
|
| |
|
Additional Manufacturer Narrative
|
|
Details of complaint:
the biomedical engineer (biomed) reported that the multiple patient receiver (org) was showing comm loss for all 8 receiver cards.Each receiver card successively going into comm loss throughout the day until they were all in comm loss.This device was a loner, and they had received the original device back but had not yet swapped it back in.Technical support (ts) recommended that he reboot the org, replace the ethernet cable, and move the device to a different network port.He later confirmed that making these changes did not resolve the issue.No patient harm was reported.Investigation summary:
multiple attempts have been made to request additional information.However, there was no response received.As such, this complaint could not be confirmed, and the root cause of the reported issue could not be determined.No further investigation will be performed.Nk will continue to monitor and trend.Additional information:
b4 date of this report
g3 date received by manufacturer
g6 type of report
h2 if follow-up, what type?
h6 event problem and evaluation codes
h11 additional manufacturer narrative.
|
| |
|
Search Alerts/Recalls
|