

FDA · EU MDR · Health Canada
A clear pathway from first questions to clearance, and a plan for the changes that come after it.
Talk to Cosm
Whether your product is a device, its classification, the right pathway and the evidence a reviewer will expect. Includes Breakthrough Device designation requests when your technology qualifies.
Questions FDA can answer, a package that supports them, and a plan to use the feedback to reduce avoidable review questions later.
What is an FDA Pre-Sub? →Planning, writing and submitting, including the software, cybersecurity and human factors sections reviewers look at closely.
Deciding when a change needs a new 510k, documenting the ones that do not, and Predetermined Change Control Plans (PCCPs) for planned AI/ML updates.
PCCP guide →We prepare CEPs, CERs, PMCF plans and reports, PMS reports, PSURs and SSCPs for medical device software and AI, and run literature and safety searches. We agree the scope, fee and schedule for each project, with no recurring retainer or monthly minimum.
Clinical evaluation →




Timing depends on your device, the pathway and the evidence you already have.
Device status, classification and pathway.
A written plan your team can follow.
Questions and a package FDA can answer.
Written feedback, and a meeting if you ask for one.
Testing, software, cybersecurity and human factors, scoped to the pathway.
510k, De Novo or EU technical documentation, assembled and submitted.
Answers to reviewer questions, then change control and PCCPs.
No recurring retainer or monthly minimum.

FDA guidance now covers how AI-enabled device software should be described, tested and changed over time, including Predetermined Change Control Plans (PCCPs).
We help you plan model changes up front, write the PCCP, and document data management, performance testing and transparency the way reviewers look for them.
AI/ML SaMD topic page →
Wearables, wellness apps and clinical decision support software can sit close to the line between a consumer product and a medical device. Small wording changes can move a product across it.
We help you decide where your product sits, word your claims to match, and plan for the point where a device pathway makes sense.
For cyber devices, section 524B of the FD&C Act requires an SBOM, a plan for postmarket vulnerabilities and evidence of secure design.
FDA's premarket cybersecurity guidance sets out what the submission should contain. We help you build that file alongside development, not at the end.
Looking for current FDA guidance on 510k, De Novo, Pre-Subs and PCCPs? Visit the FDA topic page →
Writing your first PCCP? Start with the PCCP guide →

Talk it through with Cosm.
Talk to Cosm