IMDNA provides scientific, technical, documentation, and non-regulatory support for organizations moving molecular assays, qPCR/RT-qPCR technologies, research reagents, controls, immunoassays, laboratory products, and IVD-development programs from research or development toward a defined commercial product. Support can include product-definition review, intended-use alignment, technical-file organization, analytical evidence packages, manufacturing and QC documentation, labeling and instructions-for-use support, risk and gap review, QMS documentation readiness, submission-support document organization, commercialization planning, OEM/private-label transfer, and technical assistance through product transition.
Commercialization is not simply a marketing step. Product claims, intended use, design, performance evidence, manufacturing controls, labels, instructions, quality records, and regulatory pathway should remain technically consistent with one another. IMDNA can help build and organize that scientific evidence base while the product owner retains responsibility for regulatory strategy, legal interpretation, formal submissions, communications with authorities, market authorization, and final commercial claims.
FDA device classification and premarket pathways depend fundamentally on the device type and intended use. IMDRF likewise frames device safety and performance around the performance intended by the manufacturer. Before regulatory documentation is assembled, the product concept, user, specimen, workflow, output, claims, and technical configuration should therefore be internally consistent.
Define exactly what is being commercialized: assay, reagent, control, kit, instrument, software component, accessory, service-supported product, or integrated system.
Clarify the intended user, setting, analyte or target, specimen, measurement, purpose, and claims the product owner intends to support.
Align formulation, target design, components, controls, instruments, software, packaging, labels, and manufacturing configuration with the intended product.
Identify which analytical, technical, manufacturing, usability, stability, clinical, or other evidence may be relevant to the intended commercial pathway.
Define product-owner, manufacturer, OEM/private-label, laboratory, distributor, regulatory, quality, and technical responsibilities before launch.
Support can begin with an early research assay, a technically mature RUO product, an OEM program, a transferred technology, or a product owner preparing a more formal regulatory-development pathway.
Help organize product description, components, target/analyte, assay principle, platform, user workflow, specimen or research material, controls, package configuration, storage, and technical limitations.
Review technical documents for consistency between the stated intended use and the actual assay design, evidence, labeling, instructions, and product-development stage.
Help organize publicly available FDA, WHO, IMDRF, or other authority information relevant to product classification and possible pathways for discussion with qualified regulatory professionals.
Compare available development, analytical, manufacturing, QC, labeling, stability, risk, and quality documents with the planned technical-document structure and identify missing evidence.
Organize product descriptions, design/development data, analytical studies, manufacturing information, QC, stability, labeling, instructions, risk documentation, and supporting references into a structured technical package.
Support compilation of analytical verification/validation data including precision, agreement, linearity, detection capability, specificity, interference, matrix effects, robustness, and multiplex performance as relevant.
Support manufacturing instructions, batch records, raw-material traceability, in-process controls, lot-specific QC, packaging, labeling, change history, and technology-transfer documentation.
Help organize scientifically accurate product description, component information, storage, workflow, controls, limitations, performance summaries, and intended-use wording for customer/regulatory review.
Support document control, training materials, change documentation, supplier/material records, complaint/feedback routing concepts, CAPA tools, and other quality-document organization where relevant to the project.
Help assemble scientific questions, device/product description, technical background, study plans, comparison tables, and supporting documents for review by the product owner's regulatory team before authority interaction.
Support transfer of specifications, branding configuration, packaging, manufacturing, QC, technical documentation, lot traceability, and responsibility matrices for commercial supply arrangements.
Continue with lot changes, technical inquiries, product updates, troubleshooting, documentation revisions, manufacturing scale-up, and controlled product improvements after commercialization.
IMDNA's support framework connects product definition with technical evidence, documentation, manufacturing readiness, gap resolution, and commercial transition.
A well-organized technical package should allow a reviewer or product-development team to trace how the intended use connects to product design, performance evidence, manufacturing, risk controls, labeling, and lifecycle management.
Product name, owner, manufacturer, configuration, model or version, components, commercial roles, and jurisdiction-specific administrative information where applicable.
Scientific principle, target/analyte, reagents, instrument, software, specimen, workflow, controls, accessories, packaging, and technical characteristics.
Intended user, use environment, sample or specimen, purpose, population where applicable, output, and claims supported by the evidence package.
Verification/validation reports, precision, sensitivity, specificity, detection capability, comparison, interference, robustness, stability, and other relevant studies.
Manufacturing process, materials, suppliers, in-process controls, lot QC, release criteria, traceability, packaging, labeling, storage, and change controls.
Risk-management outputs, design/development rationale, critical technical decisions, failure modes, mitigation evidence, and change history where applicable.
Product labels, outer packaging, instructions for use, limitations, warnings, storage, interpretation, technical performance, and manufacturer/distributor information as applicable.
Document control, training, supplier records, complaints/feedback, CAPA, changes, post-market or post-launch technical observations, and other ongoing records where applicable.
FDA assigns devices to regulatory classes according to the controls necessary to provide reasonable assurance of safety and effectiveness. Different products may follow different pathways. IMDNA can help organize technical information around a pathway identified by the product owner and qualified regulatory advisors, but does not select or authorize a regulatory pathway.
| FDA Pathway / Status | General Concept | Potential IMDNA Technical Support |
|---|---|---|
| Research Use Only (RUO) | For IVD products genuinely in the laboratory research phase, labeling/distribution should remain consistent with research use and not represent the product as an approved or cleared diagnostic product. | RUO technical description, labeling consistency, research instructions, manufacturing/QC documentation, technical support. |
| 510(k) | A premarket submission used to demonstrate substantial equivalence to a legally marketed predicate device, where applicable. | Product description, predicate-comparison technical tables, analytical evidence organization, manufacturing/labeling support, study-document preparation. |
| De Novo | A risk-based classification pathway for certain novel devices without a legally marketed predicate when general controls or general and special controls can provide reasonable assurance of safety/effectiveness. | Technical background, device description, risk/evidence organization, analytical study support, supporting-document package. |
| PMA | FDA's most stringent device premarket application, used for applicable Class III devices and based on sufficient valid scientific evidence of safety and effectiveness. | Technical and analytical documentation support within IMDNA expertise; formal PMA strategy and submission responsibility remain with the applicant/regulatory team. |
| WHO IVD Prequalification | For eligible IVDs, WHO prequalification may involve product dossier review, manufacturing-site inspection, and labeling review. | Dossier organization, analytical/manufacturing evidence compilation, labeling/IFU technical support, documentation gap assessment. |
For molecular products, regulatory and commercialization documentation should be grounded in the actual analytical behavior of the assay. The required evidence depends on intended use and pathway, but common technical questions include specificity, precision, low-level detection, interference, reproducibility, controls, matrix effects, and performance after multiplex integration.
Document assay target regions, primer/probe rationale, sequence inclusivity/exclusivity, cross-reactivity assessment, and relevant variants or related organisms where appropriate.
Organize within-run, between-run, operator, instrument, lot, site, or day-to-day variability studies according to the intended technical claim.
Support LOD, low-positive, LoB/LoQ where applicable, or other low-level performance evidence appropriate to the assay.
Compile cross-reactivity, endogenous/exogenous interference, inhibition, matrix, carryover, contamination, and other relevant studies.
Document target competition, channel separation, multiplex-vs-singleplex behavior, internal-control balance, weak-target sensitivity, and panel-specific performance.
Document positive, negative, process, extraction, internal amplification, calibrator, reference, or other controls used to support product performance.
Organize shelf-life, in-use, freeze-thaw, transport, excursion, container, or other stability evidence supporting storage and handling claims.
Compile lot-specific QC, reference-lot comparison, manufacturing variability, and functional release-testing data as applicable.
Document comparability or bridging when instrumentation, software, reagents, manufacturing sites, or analytical workflows change.
IMDRF's 2024 labeling principles provide an international framework for clear, consistent labeling of medical devices and IVDs. FDA also ties device regulation closely to intended use and labeling. Technical claims should therefore not extend beyond what the underlying evidence package can support.
Keep product name, model/version, kit components, assay configuration, and brand identity consistent across labels, IFU, website, technical files, and manufacturing documents.
Align intended-use language with product design, sample/specimen, target, performance studies, instructions, and commercial materials.
Ensure analytical-performance statements correspond to defined study data and do not imply broader performance than was evaluated.
Link temperature, shelf life, in-use period, freeze-thaw, or other handling claims to appropriate supporting evidence.
Document known analytical, biological, matrix, sequence, workflow, or interpretation limitations relevant to product use.
Where the product is appropriately RUO, maintain research-use language consistently across labeling, distribution, technical information, and marketing.
WHO's IVD prequalification program emphasizes a clear, complete, well-organized product dossier. Its current procedure includes dossier review, manufacturing-site inspection, and labeling review for applicable products. IMDRF provides harmonized essential principles and labeling frameworks that can help product teams organize evidence for global commercialization discussions.
Organize documentation so reviewers can locate product information, performance evidence, manufacturing, QMS, labeling, and supporting records efficiently.
Connect summary claims to the detailed reports, raw-data summaries, protocols, specifications, and controlled documents that support them.
Ensure product name, version, formulation, instrument, software, labels, IFU, and performance evidence refer to the same commercial configuration.
Identify missing sections, unsigned reports, uncontrolled drafts, inconsistent claims, outdated specifications, or absent supporting evidence before formal review.
Ensure the manufacturing process and QC package correspond to the product configuration described in the dossier.
Ensure labels and IFU match the intended use, performance data, storage conditions, limitations, components, and product identity described elsewhere.
For applicable finished medical-device manufacturers, FDA's QMSR became effective February 2, 2026 and incorporates ISO 13485:2016 by reference. FDA states that the QMSR applies to finished device manufacturers intending commercial distribution. This requirement should not be assumed for every IMDNA research product, but it becomes relevant when the commercial product and manufacturer fall within the regulated medical-device framework.
Help organize documents, records, process maps, training, supplier information, change controls, CAPA tools, manufacturing records, and other quality materials for review by the responsible organization.
Support technical capture of product inputs, outputs, development evidence, design changes, verification/validation data, and technical rationale where applicable.
Organize critical supplier, raw-material, component, oligonucleotide, enzyme, antibody, packaging, and contract-manufacturing information.
Support master instructions, batch records, lot traceability, in-process checks, lot QC, deviation records, packaging, labeling, and release documentation.
Track formulation, supplier, process, instrument, assay, software, label, packaging, and manufacturing changes and associated technical evidence.
Help organize technical evidence and document availability while formal compliance determinations and inspections remain with authorized parties.
| Area | Questions to Ask | Potential IMDNA Support |
|---|---|---|
| Product Definition | Is the commercial configuration clearly defined and frozen enough for evidence generation? | Product map, configuration summary, version alignment. |
| Intended Use / Claims | Do claims match the assay design and available evidence? | Technical consistency review, evidence-to-claim mapping. |
| Analytical Evidence | Are the relevant performance characteristics adequately studied? | Gap matrix, study-plan support, report organization. |
| Manufacturing | Can the commercial process reproducibly produce the same configuration used in performance studies? | Manufacturing-process documentation, scale-up, lot QC, transfer support. |
| Stability / Packaging | Are storage, shelf-life, transport, and packaging claims supported? | Stability-study support, packaging documentation, claim alignment. |
| Labels / IFU | Are the product, intended use, instructions, limitations, storage, and claims internally consistent? | Technical drafting, cross-checking, artwork/IFU support. |
| QMS / Records | Are required quality and manufacturing documents controlled and traceable? | Document organization, templates, record maps, readiness support. |
| Commercial Supply | Are lot traceability, packaging, labeling, supply continuity, technical support, and change notification defined? | OEM/private-label manufacturing, QC, logistics-support documentation, lifecycle support. |
IMDNA provides scientific, technical, commercialization, documentation, analytical-evidence, manufacturing-readiness, labeling-support, quality-documentation, technology-transfer, and non-regulatory support based on the needs of each project. Support may include assistance with product-definition review, intended-use consistency, publicly available pathway information, documentation gap assessment, technical-file/dossier organization, analytical evidence packages, manufacturing/QC documentation, labeling and IFU technical content, QMS documentation readiness, pre-submission support packages, OEM/private-label transition, and ongoing technical support.
Where appropriate, IMDNA may help generate or organize scientific and technical evidence, manufacturing documents, analytical studies, QC records, product specifications, labels, instructions, stability information, transfer documents, and other materials that the product owner's regulatory or quality team may use as part of a broader commercialization program.
IMDNA is not a regulatory affairs firm, law firm, governmental authority, notified body, certification body, accreditation body, or market-authorization authority unless a specific qualified third-party professional is separately engaged under a defined written scope. IMDNA does not independently provide legal opinions, determine the final regulatory pathway, act as the official regulatory applicant or sponsor unless expressly authorized and qualified to do so, guarantee clearance/approval, or represent that technical documentation alone establishes regulatory compliance.
The product owner, sponsor, applicant, or responsible manufacturer remains responsible for determining regulatory classification and pathway; intended-use and commercial claims; applicable clinical, analytical, manufacturing, QMS, registration, listing, labeling, vigilance, post-market, and submission requirements; formal communications with regulatory authorities; submission certification and signatures; and obtaining any required clearance, approval, authorization, licensing, certification, or registration.
IMDNA may coordinate with a customer's regulatory, quality, legal, clinical, or other qualified experts by providing the scientific and technical documentation within IMDNA's area of expertise.
References to FDA, WHO, IMDRF, ISO, or other authorities and standards organizations are provided as general informational and technical frameworks only. They do not imply endorsement, approval, affiliation, certification, or sponsorship of IMDNA or its services.
The following sources support the general concepts of product classification, premarket pathways, IVD intended use, RUO positioning, device quality systems, global essential principles, labeling, and dossier organization. Their formal applicability depends on product category, intended use, jurisdiction, and regulatory pathway.
Tell IMDNA about your product, intended use, development stage, assay technology, target/analyte, manufacturing configuration, analytical evidence, stability data, labels, IFU, quality documentation, proposed market, OEM/private-label structure, and commercialization goals. Our scientific and technical team can help organize a commercialization-support plan covering documentation gaps, analytical evidence, manufacturing/QC records, labeling technical content, dossier structure, technology transfer, and ongoing product support.