July Saw 100+ Regulatory Developments. Which Ones Moved Your Regulatory Position?
There is a comforting assumption behind regulatory monitoring: if something important changes, we will find it.
For a long time, that was a reasonable assumption. Regulatory Affairs knew its authorities, its legislation and the sources worth following. A medical device team watched medical device regulation. Pharma watched the medicines authorities. Global teams followed the major jurisdictions and local teams kept an eye on what happened closer to home.
The challenge was keeping up.
That assumption is becoming harder to defend.
During July, Compliance Studio identified more than 100 regulatory developments across the areas we monitor. They came from the familiar places – FDA and European authorities, but also NMPA in China, PMDA and MHLW in Japan, CDSCO in India, Thai FDA, and other markets you probably need to stay up to date on.
Some were significant. Others were minor. Many would matter greatly to one company and not at all to another.
And some of the developments capable of affecting life-science products did not come from health regulators at all.
That is where things get interesting.
Your regulatory perimeter is getting bigger
A medical device is no longer necessarily governed only by medical device regulation.
Take an AI-enabled connected diagnostic device. Its regulatory position may begin with MDR or the relevant national medical device framework, but it does not end there. AI, cybersecurity and data regulation can affect the software and its operation. Chemicals legislation can affect materials. Environmental requirements can affect batteries and electronic components. Packaging legislation can create another layer of obligations.
The product has not changed. The regulatory perimeter around it has.
July offered examples of both sides of this development.
FDA proposed changes concerning pharmaceutical manufacturing registration, including requirements affecting certain foreign manufacturers supplying the US market. Japan continued to issue safety information and revised precautions for medicinal products. India continued developing its regulatory approach to Medical Device Software. Thailand and Japan strengthened regulatory cooperation covering pharmaceuticals, medical devices and advanced therapies.
These are developments most Regulatory Affairs teams would recognise as theirs to monitor.
But during the same period, developments were taking place across AI and cybersecurity policy. On 7 July, for example, the European Commission presented an Action Plan specifically addressing the intersection between advanced AI and cybersecurity. It is not medical device legislation and does not create a new medical-device obligation simply by being published. But for companies developing connected AI-enabled products, developments like this belong on the horizon because they can shape the regulatory environment around technologies embedded in those products.
This is the blind spot.
You can do an excellent job monitoring medical device regulation and still miss a regulation that affects your medical device.
Finding more is not the answer
AI is rapidly making regulatory monitoring easier. It can search more sources, find more developments and summarise them faster than any regulatory team could reasonably do manually.
That sounds like the solution until you receive 100 summaries.
A Regulatory Affairs team does not need to know everything that happened in July. It needs to know whether something happened that could change what it believes about a particular product.
For a conventional device sold in Sweden, perhaps none of those 100 developments matters. For an AI-enabled combination product sold across the EU, US, China, Japan, India and Thailand, several might.
The difference is not in the updates. It is in the Regulatory Position – the documented regulatory context for a specific product, organisation and market – against which they are assessed.
And that suggests that we may have been approaching regulatory monitoring from the wrong direction.
Instead of starting with everything that changed and asking Regulatory Affairs to determine what matters, start with the product.
What is it? What does it do? Which technologies and components does it contain? Where is it marketed? What role does the organisation have? Which regulatory frameworks have already been determined to apply?
Now there is something against which regulatory change can be assessed.
An update can be important, irrelevant, something to monitor, or a reason to reassess an existing regulatory decision. A development from a completely different regulatory domain can surface because it intersects with an attribute of the product.
That is a much more useful application of AI than producing another regulatory news feed.
What moved your position?
This is the thinking behind Regulatory Signals in Compliance Studio. The starting point is not the signal. It is the Regulatory Position.
Compliance Studio establishes the regulatory context around a product, organisation and market. Regulatory Signals monitors developments against that context to identify changes that may warrant attention.
The goal is not to read 100 updates every month. Nor is it to replace Regulatory Affairs judgement about what they mean.
It is to make sure that judgement is spent on the developments that deserve it – including the ones that come from outside the places Regulatory Affairs traditionally knows to look.
July brought more than 100 regulatory developments across the areas we monitor. August will bring more and the interesting number is not how many you found. It is how many moved your Regulatory Position.
Build your Regulatory Position in Compliance Studio and see regulatory change in the context of your product and market.
