Model Number ORG-9110A |
Device Problems
Incorrect, Inadequate or Imprecise Result or Readings (1535); Output Problem (3005)
|
Patient Problems
No Known Impact Or Consequence To Patient (2692); No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 06/26/2020 |
Event Type
malfunction
|
Manufacturer Narrative
|
The biomedical engineer (bme) reported that the multiple patient receivers (orgs) were displaying sawtooth waveform intermittently.(b)(4) ts is currently working to resolve the issue and advised that it could be an environmental 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 Description
|
The biomedical engineer (bme) reported that the multiple patient receivers (orgs) were displaying sawtooth waveform intermittently.(b)(4) ts is currently working to resolve the issue and advised that it could be an environmental issue.No patient harm was reported.
|
|
Event Description
|
The biomedical engineer (bme) reported that the multiple patient receivers (orgs) were displaying sawtooth waveform intermittently.Nk ts is currently working to resolve the issue and advised that it could be an environmental issue.No patient harm was reported.
|
|
Manufacturer Narrative
|
Details of complaint: the biomedical engineer (bme) reported that the multiple patient receivers (orgs) were displaying sawtooth waveform intermittently.Nihon kohden technical support (nk ts) was working to resolve the issue and advised that it could be an environmental issue.No patient harm was reported.Investigation summary: nihon kohden technical support (nkts) asked the customer to provide information regarding the error messages present during the event.The customer stated they would collect the data and forward it to nk ts.Follow-ups to the customer resulted in no response.The root cause is undetermined due to the lack of information from the customer.The most likely cause was the facility's network environment.
|
|
Search Alerts/Recalls
|