| Catalog Number |
MS20026 |
| Medical Device Problem Codes |
No Apparent Adverse Event (3189); Patient Data Problem (3197)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
11/28/2023
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
The investigation has just started; results will be provided in a follow-up report.H3 other text : ongoing.
|
| |
|
Event or Problem Description
|
|
It was reported that a nurse was attempting to document an administered medication dose to a specific patient record but noticed after entering the information into the innovian system that the information was recorded for a different patient instead.It was verified that only the recording of information went wrong; the patients have received correct medications.
|
| |
|
Additional Manufacturer Narrative
|
|
Device logs were provided however, they were corrupted and could not be opened.Therefore, investigation could not be performed, and root cause could not be determined.Note that that the innovian solution suite (including innovian critical care and innovian perioperative care) reached the end of service (eos) january 31, 2020, and end of life (eol) december 31, 2021.Additionally, the instructions for use for innovian critical care cautions users that it is not to be used for patient monitoring or diagnostic purposes.Always refer to the primary source of clinical data.A query of the complaint database show this as an isolated case.
|
| |
|
Event or Problem Description
|
|
It was reported that a nurse was attempting to document an administered medication dose to a specific patient record but noticed after entering the information into the innovian system that the information was recorded for a different patient instead.It was verified that only the recording of information went wrong; the patients have received correct medications.
|
| |
|
Search Alerts/Recalls
|