ISO 10993 and Toxicology
Senior support on endpoint justification, toxicological framing, chemistry-linked biological evaluation, or specialized scientific review.
This page is for experienced specialists interested in carefully scoped project-based collaboration. Associate experts are considered where a client project benefits from additional domain-specific depth.
Projects are scoped, qualified, and coordinated through MedDev Advisory. When a scope needs additional depth, vetted specialists may contribute specific regulatory, quality, scientific, or technical expertise.
The standard is direct, hands-on experience. I only consider specialists who can demonstrate real regulatory or scientific depth in the specific area they want to support.
These are the areas where specialist support may be relevant. Inclusion here does not mean constant hiring or automatic project flow.
Senior support on endpoint justification, toxicological framing, chemistry-linked biological evaluation, or specialized scientific review.
Specialists with real Technical File, GSPR, CER-adjacent, PMCF/PMS, or notified body remediation depth where the scope goes beyond core biocompatibility writing.
Hands-on experience with 510(k), De Novo, PMA, reviewer questions, or submission architecture in areas complementary to biocompatibility documentation.
Experienced contributors for ISO 13485, ISO 14971, change-control, CAPA, or risk-file integration where project scope requires stronger system alignment.
Selective support for systematic literature review, CER-adjacent analysis, PMCF-related writing, or evidence synthesis connected to device safety and performance.
For professionals with direct, practical CDSCO experience in classification, pathway planning, documentation readiness, or submission execution.
I am looking for people who have actually prepared, reviewed, or defended the kind of work they claim. General interest without real project history is not enough.
Good collaboration depends on precision, structure, and strong written reasoning. In this field, wording quality affects regulatory risk directly.
Client-sensitive work requires discretion, clear conflict boundaries, and comfort operating under NDA or restricted-scope review conditions.
Project-based work only functions when expectations, scope, and deadlines are handled cleanly. Slow or ambiguous communication is a non-starter.
I review your background, domain fit, and whether the expertise matches the kind of work likely to arise.
If the fit looks credible, we discuss scope boundaries, working style, confidentiality expectations, and likely collaboration conditions.
For real opportunities, I define what part of the work needs specialist support and whether the collaboration is the right match.
Any collaboration is set project-by-project with defined responsibilities, timing, and communication expectations.
Use this form if you want to be considered for project-based collaboration. The more concrete your regulatory scope, device classes, and documentation experience, the easier it is to assess fit properly.
Your next step will appear here.