|
The software product mentioned in this medwatch report may not be, by definition, a medical device; however, cerner has chosen to file this medwatch report in order to voluntarily notify the fda of a malfunction associated with this software product.The company's filing of this medwatch report does not signify cerner's belief or understanding that medical device reports are required to be filed for products such as cerner's ignite apis for millennium®, nor are these products currently actively regulated by the fda.This report documents information related to an issue identified with functionality included in cerner's millennium ignite apis for millennium® allergies, cerner ignite apis for millennium, medication clinical decision support, seamless exchange.The issue involves cerner millennium ignite apis and affects users that utilize the allergies, cerner ignite apis for millennium, medication clinical decision support, seamless exchange to enable external applications to integrate into the millennium platform.In cerner millennium, when a snomed ct allergy was supplied for an allergy substance and a mapping did not exist between the selected snomed ct and a multum allergy category, the drug allergies saved to millennium with snomed ct nomenclature do not generate alerts.When the mapping was not found, a corresponding snomed ct nomenclature was used to add the allergy to millennium.A snomed ct allergy substance does not qualify for drug-allergy interaction checking, resulting in a possible patient care impact if a clinician were to prescribe a drug that interacts with the snomed ct allergy.Patient care could be adversely affected, if clinicians not being aware that the drug-allergy interaction checking was not occurring, prescribe a drug that does not properly trigger a drug allergy alert on the patient's profile.This issue could result in serious injury and patient care delay.Cerner has not received communication on any adverse patient events as a result of this issue.
|
