Products that combine medicines, medical devices and software are challenging the rules used to approve health technologies and monitor patient safety.
Known as bioconvergence products, these systems may pair a drug with a sensor, an implant with an app, or diagnostic software with a treatment. Their mixed design can make it hard to decide which standards and review process should apply.
“Bioconvergence products blur the lines between drugs, devices and software, and with them, the rules for getting to market.”
Traditional Categories Begin to Overlap
Health regulators have long assessed drugs, devices and software through separate channels. Each category has its own evidence requirements, manufacturing controls and safety checks.
Medicines are generally evaluated through laboratory research and clinical trials. Medical devices are assessed according to their design, intended use and level of risk. Software may require checks covering accuracy, cybersecurity and updates.
A combined product can involve all three forms of oversight. For example, a medicine could use a connected injector that records doses through a mobile app. Its safety would depend on the drug, the injector and the software working as intended.
This overlap raises a basic regulatory question: Which part of the product should determine its approval route? The answer can affect review times, development costs and the evidence demanded from manufacturers.
Evidence Must Cover the Whole System
Testing each part separately may not show how a bioconvergence product performs in daily use. A safe medicine could still create risks if its delivery device fails. Accurate software could also cause harm if it sends incorrect instructions to connected hardware.
Regulators and developers may need to examine several linked issues:
- Clinical safety and effectiveness of the treatment
- Reliability and durability of the medical device
- Accuracy, privacy and security of the software
- Risks created when one part is updated or replaced
Software creates a special challenge because it can change after launch. A medicine’s chemical formula may remain fixed, while an app may receive frequent updates. Authorities must decide whether those changes require a fresh review.
Artificial intelligence can add another layer of uncertainty. If a system adjusts recommendations using new patient data, its future behavior may differ from the version first submitted for approval.
Industry Faces Cost and Timing Questions
Unclear classification can slow planning for companies. Developers need to know what studies to run, which regulator will lead the review and how quality standards will be enforced.
Large manufacturers may have teams that work across medical and digital regulation. Smaller companies may struggle with overlapping requirements, especially if authorities in different countries classify the same product in different ways.
Still, stricter review can protect patients and support trust. Faster approval is not useful if regulators lack enough evidence about cybersecurity, device failure or clinical outcomes.
A balanced system would provide early guidance while keeping safety standards intact. Joint reviews and a single lead authority could reduce conflicting requests without weakening oversight.
Responsibility Continues After Approval
Market authorization is only one stage. Connected products may require continuous monitoring for software errors, security threats and unexpected interactions between their parts.
Responsibility can also become divided. A drug company, device maker and software provider may each control different parts of one product. Regulators will need clear rules on who reports problems, issues recalls and pays for corrective work.
Bioconvergence could support more personalized and responsive care, but its success will depend on regulatory clarity. Authorities must create approval routes that assess each product as one connected system.
The next key developments will include clearer classification standards, shared evidence rules and stronger plans for post-market monitoring. Without those measures, promising health products could face delays, while poorly tested systems could expose patients to avoidable harm.
Senior Software Engineer with a passion for building practical, user-centric applications. He specializes in full-stack development with a strong focus on crafting elegant, performant interfaces and scalable backend solutions. With experience leading teams and delivering robust, end-to-end products, he thrives on solving complex problems through clean and efficient code.
