Aurora Health Care Completes System-Wide Conversion to Masimo SET Pulse Oximetry ...( Masimo provides Aurora with technol...),Health

Masimo provides Aurora with technology and sensor standardization across

its facilities - creating efficiencies and cost savings

IRVINE, Calif., July 31 /PRNewswire-FirstCall/ -- Masimo, the inventor of Pulse CO-Oximetry and Measure-Through-Motion-and-Low-Perfusion Pulse Oximetry, announced that Aurora Health Care has completed a system-wide conversion to Masimo SET pulse oximetry technology. The integrated health care provider with 13 hospitals and more than 100 clinics performed an independent evaluation of pulse oximetry technologies and chose Masimo over all other available technologies to unify patient monitoring capabilities across their entire network.

"The decision to convert all of our hospital and surgery facilities to Masimo SET pulse oximetry originally grew out of clinical preference in the Post Anesthesia Care Unit (PACU) and Neonatal Intensive Care Unit (NICU) because of Masimo's superior performance during the most challenging of patient conditions," stated Alan Gresch, Corporate Manager of Clinical Engineering, Aurora Health Care. "Performance preference soon gave way to clinical efficiencies and cost savings created by standardization to the Masimo SET technology platform. Now, in addition to better technology across the board, our staff no longer has to change sensors or monitors when patients are transferred between departments."

Aurora Health Care is a not-for-profit Wisconsin health care provider and a national leader in efforts to improve the quality of health care. Aurora offers care at sites in more than 90 communities throughout eastern Wisconsin, including 13 hospitals, more than 100 clinics and over 130 community pharmacies. Prior to their system-wide conversion, hospitals and surgery centers in the Aurora Health Care system struggled with pulse oximetry technology and sensor incompatibility issues.

"I've been sold on Masimo SET pulse oximetry ever since I first saw that it worked accurately on
'/>"/>