Country selector
chevron arrow
Australia
Careers
Country Selector: Australia

EU Medical Device Regulation (MDR):

What do users need to know?

The EU’s new Medical Device Regulation has recently come into effect. As a result, hospitals need to be aware of the new regulations and ensure that the medical devices and medical device software they use are compliant. This will help secure the safety and efficacy of the medical device software they use and promote better patient outcomes. And rest assured, we have already made the Ascom Healthcare Platform compliant and certified for use in the areas affected by the new regulations. 

March 3, 2023

First a little background. On 26th May 2021, the EU implemented the Medical Device Regulation (EU) 2017/45 (MDR), which standardizes the legislation and updates the requirements around medical devices from the almost 30-year-old Medical Devices Directive 93/42/EEC (MDD). Among other topics, MDR specifically deals with software as a medical device, post-market surveillance and the obligations of the various stakeholders.

Close-up of female medical personnel in PPE looking at a monitor, there are other members of the staff in the blurred background

The Ascom Healthcare Platform: Certified for use

MDR  governs and regulates Ascom solutions in the areas of medical device integration, clinical decision support systems, and alarm management. As a result, we have made sure that our technology is certified in these areas, namely Digistat and several Unite modules: Unite Connect for Clinical Systems, Unite Axess for Smart Devices a,nd Unite View.

For any questions about how MDR is handled by the Ascom Healthcare Platform — or if you are investigating communication and collaboration software in your own environment — do not hesitate to contact us for more information or guidance.

Contact us

Download our white paper for more detail

We have also put together an in-depth white paper that focuses on how the new MDR deals with software as a medical device. After a brief introduction to the regulation, there is a summary of the new responsibilities for healthcare organizations. Topics include the requirements pre- and post-sale, what changes for the patients, and how healthcare organizations can better implement precautions. With this information, users should get a more hands-on perspective on how to manage software as a medical device and better navigate these first years of transition from the previous MDD.

Download white paper

Key MDR takeaways for hospitals and users

·        Definition — Medical device software is defined as any software intended to be used for diagnostic or therapeutic purposes.

·        Classification — Medical device software is classified based on its intended use and level of risk.

·        Compliance — Manufacturers of medical device software must demonstrate compliance with the MDR by obtaining a CE mark, which indicates that the software meets the necessary safety and performance requirements. If in doubt, ask your suppliers for their certification.

·        Clinical evaluation — MDR requires that medical device software undergo clinical evaluation to demonstrate its safety and effectiveness. Hospitals should be aware of the results of these evaluations when selecting and using medical device software.

·        Post-market surveillance — Manufacturers must monitor the performance of medical device software in the market and report any adverse events associated with its use. Equally, hospitals should report any adverse events they experience to the manufacturer.

·        Quality management system — MDR requires that manufacturers of medical device software implement a quality management system to ensure that the software is designed and developed in a consistent and controlled manner. Hospitals should be aware of the quality management systems in place for the medical device software they use.

Back to campaign overview