Medical Device Regulation Robots: Compliance and Use in Care
The distinction between the Medical Device Regulation (MDR) and the Machinery Regulation determines liability when deploying robots. werob provides the legally secure path for operators of medical facilities.
Station 4. 03:15 AM. The night shift prepares the medication round. An autonomous transport robot delivers the sealed boxes directly to the nursing station, while staff gain time for direct patient interaction. Is it a pure logistics system or already a medical device under EU Regulation 2017/745 (MDR)? The answer determines the administrative effort and legal protection of the operator. werob supports experts in navigating facilities through this complexity by automatically analyzing workflows, while final decision-making authority remains with the specialist staff, who consider both the MDR and the upcoming EU Machinery Regulation 2023/1230.
Key Takeaways
- 1The intended purpose determines whether a robot falls under the MDR or the Machinery Regulation.
- 2As of January 20, 2027, the new EU Machinery Regulation 2023/1230 is mandatory for all new installations.
- 3Automated medication rounds enable annual cost relief of €92,000 per location.
Classification of the Medical Device Regulation for Robots
Care operators must precisely determine when a robot is legally classified as a medical device. According to EU Regulation 2017/745 (MDR), the manufacturer's intended purpose is decisive. If the system is designed for the diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of diseases, the MDR applies. This applies, for example, to surgical robots or highly specialized exoskeletons in rehabilitation.
In contrast, service robots that perform logistical tasks, such as transporting laundry, food, or medications, typically fall under the EU Machinery Regulation. This distinction is critical because the MDR imposes significantly higher requirements on clinical evaluation and quality management. werob supports you in making this classification legally sound already in the planning phase. Through analysis of projects across more than 30 industries, our Spec Engine immediately identifies which regulatory hurdles are relevant for your specific workflow. This prevents costly misclassifications in hardware selection and ensures long-term operation.
The EU Machinery Regulation 2023/1230 as the New Standard
While the Medical Device Regulation applies to specialized equipment, a different date comes into focus for the broad mass of service robots: January 20, 2027. On this day, the new EU Machinery Regulation 2023/1230 becomes binding. It replaces the old Machinery Directive and sets stricter requirements for cybersecurity and conformity assessment, particularly for autonomous mobile robots (AMR).
For operators, this means that many Asian OEMs without a local conformity assessor could lose market access in the EU. werob acts here as the decisive systems integrator in Europe, paving the compliance path for these hardware partners. We rank more than 44 OEM partners not only by technical performance, but primarily by their regulatory future viability. When you invest in robotics today, werob ensures that systems will be legally operated even after January 2027. This includes compliance with ISO 13482 for personal care robots, which governs safe contact between humans and machines. Without this certification, facilities risk operating bans from care authorities or occupational health insurance providers.
Economics and Cost Relief in Care
Compliance is not an end in itself, but the basis for measurable economic success. In the care industry, margins are tight and skilled labor shortages are chronic. A legally sound implemented robot relieves staff of unproductive walking routes and logistics tasks. werob has validated through live operations at leading European care home operators that cost relief per location is significant.
Specifically, automating the medication round leads to significant annual cost relief per location. The mere transport of laundry and consumables saves further substantial budgets annually. These figures are based on reducing overtime and redirecting specialist staff to core care activities. werob's commercial model is outcome-focused: outcome-only means you only pay once the robot is in productive operation. Within eight weeks, we bring the technology from specification to live operation, including all necessary interfaces into your software stack.
Integration into Operator Stack: PointClickCare and MatrixCare
A robot operating in isolation creates new administrative burden instead of reducing it. True efficiency emerges from seamless integration into existing systems like PointClickCare or MatrixCare. werob provides pre-built connectors that make the robot an integral part of the digital care process. When a medication order is triggered in the system, the robot automatically receives the transport task.
This connectivity is also relevant under the Medical Device Regulation when data flows occur between the robot and medical databases. werob ensures these interfaces comply with GDPR requirements, IEC 62443, as well as SOC 2 Type II and ISO 27001. Our live cockpit monitors the entire fleet in real-time using a four-dimensional traffic light system: hardware status, infrastructure availability, regulatory compliance, and specification fulfillment. You always have proof for audits or inspections by care authorities, with each finding linked directly to the corresponding documentation section via complete source traceability. Integration occurs not through time-intensive custom programming, but via our standardized platform layer, reducing rollout time to just five days from quote to final configuration.
ISO 13482: Safety in Direct Contact
In medical facilities and care homes, physical space is often limited and interaction with vulnerable people is unavoidable. This is where ISO 13482 applies, which sets specific safety requirements for personal care robots. This standard is closely linked to the Machinery Regulation and forms the foundation for safe operation in occupied areas. A robot not certified to ISO 13482 or whose deployment scenario violates this standard poses significant liability risk.
werob examines during supplier matching whether the selected hardware meets these requirements for your specific floor plan. We do not view the robot in isolation, but the entire system including environmental sensors and emergency stop concepts. Since werob is hardware-agnostic, we are not bound to any manufacturer. We select from over 280 ranked robots the exact model that meets your safety specifications. This is particularly important for night operations where robots must autonomously change floors and use elevators also frequented by residents. Our expertise ensures that acceptance by the relevant authorities runs smoothly.
The Path to Robot Deployment in Eight Weeks
At werob, the process from initial idea to first robot on the ward is optimized to eight weeks. While traditional processes require months for analysis, our Spec Engine supports consultants in translating workflows into specifications in just 48 hours. Simply describe to us the shift, tasks, and spatial conditions. We deliver the technical equivalent including regulatory classification regarding MDR or Machinery Regulation.
After specification comes supplier matching, where we test 44+ OEMs against your requirements. Within five days you receive a binding quote. Since werob already operationally manages over 200 robots across 11 European countries, we have the necessary experience to identify infrastructure pitfalls in advance. The entire rollout takes only eight weeks from authorization to live operation – an efficiency that even a Big Four consulting partner confirmed by reducing commercial due diligence from three weeks to five days. This speed promise is unique in the market and is backed by our outcome-only model. You are not investing in hardware experiments, but in functioning processes that immediately contribute to relieving your budget.
Future Security Through the werob Cockpit
After implementation begins the fleet management phase. The werob Cockpit provides a central control unit for all deployed systems, regardless of manufacturer. This is a decisive advantage over single-OEM solutions that lock you into a closed ecosystem. In the Cockpit you not only see where a robot is located, but also receive proactive alerts for regulatory changes or necessary maintenance.
Given the dynamic development of EU legislation, such as the upcoming EU AI Act, this central monitoring layer is your insurance against obsolescence. Should a software component of a robot fall under new high-risk AI regulations, werob delivers the necessary update or corresponding documentation via the platform. This significantly reduces complexity for your IT department and compliance managers. We operate the operations layer so you can focus on care quality. As an AI-native workspace for the entire due diligence workflow, werob is the partner for scalable automation in the European healthcare market.
Regulatory Compliance as Competitive Advantage
The Medical Device Regulation and the new Machinery Regulation 2023/1230 are not barriers, but guidelines for a professional robotics strategy. Those who set the right course today and rely on a hardware-agnostic systems integrator like werob not only secure significant cost advantages but also long-term operating permits. The complexity of regulatory requirements across all 9 due diligence workstreams is completely addressed by our platform layers.
Avoid vendor lock-in and the risk of non-compliant hardware. The path to automation in care leads through precise specification and seamless integration into your existing software stack. Start the process now and benefit from our experience across over 35,000 projects. In just 48 hours we clarify whether your project falls under the MDR and which hardware delivers the best performance for your location.
Comparison: MDR vs. Machinery Regulation for Robots
| Criterion | Medical Device Regulation (MDR) | EU Machinery Regulation 2023/1230 |
|---|---|---|
| Primary Purpose | Medical (diagnosis, therapy) | Logistics, service, cleaning |
| Certification | Notified Body (Class Im, IIa, IIb, III) | Self-declaration or conformity assessment |
| Example Robots | Surgical robot, rehab exoskeleton | Transport robot, cleaning robot |
| Relevant Standards | ISO 13485, IEC 60601 | ISO 13482, ISO 12100 |
| Liability Focus | Patient safety & clinical benefit | Operational safety & occupational health |
FAQ
- When is a robot classified as a medical device under MDR?
- A robot is classified as a medical device when the manufacturer intends it to fulfill specific medical purposes such as treating or monitoring diseases. Pure transport robots for medications without dosing functions typically fall under the Machinery Regulation.
- What changes with the EU Machinery Regulation 2023/1230?
- The regulation tightens requirements for cybersecurity and risk assessment for autonomous systems. From January 2027 onwards, all robots placed on the market in the EU must meet these stricter criteria, which is particularly relevant for imports from non-EU countries.
- What is the role of ISO 13482 in care?
- ISO 13482 is the harmonized standard for personal care robots. It defines safety requirements for human-robot interaction in public and private spaces and is essential for acceptance by care authorities.
- Can werob integrate robots into PointClickCare?
- Yes, werob provides pre-built connectors for PointClickCare, MatrixCare and other common healthcare systems. This enables automated task assignment directly from care documentation.
- How high is the cost savings from robots in care?
- The verified cost relief is significant and includes both medication rounds and general transport tasks per location. These values result from reduced unproductive working time for specialist staff.
- What does werob's outcome-only model mean?
- Outcome-only means the operator incurs no upfront costs for hardware or consulting. Payments only become due once the system is in productive operation and defined performance targets are achieved.