Choosing an FDA Submission Testing Laboratory

A test report can either clarify a medical device submission or create a new round of FDA questions. The difference often begins before testing starts, when a manufacturer selects an FDA submission testing laboratory with the appropriate accreditation, technical scope, and familiarity with the device’s regulatory pathway.

For medical device teams, laboratory selection is not simply a procurement decision. It affects protocol development, sample planning, evidence quality, report usability, and the time required to resolve unexpected findings. A laboratory may be technically capable of running a test, yet still be a poor fit if its accredited scope does not cover the method, its documentation does not support the submission strategy, or its team does not understand the relevant device technology.

What an FDA Submission Testing Laboratory Must Support

FDA submissions rely on objective evidence that a device meets applicable safety and performance requirements. Depending on the device and intended use, that evidence may include electrical safety, electromagnetic compatibility, acoustic output, ultrasound image quality, biocompatibility, materials characterization, endoscope performance, human factors validation, or clinical safety and effectiveness data.

The testing laboratory should understand how its work fits into the larger evidence package. Its role is to execute defined methods accurately, document results clearly, and identify departures from the protocol or standard that require evaluation. The laboratory does not replace the manufacturer’s regulatory strategy or risk management process, but it should produce data that regulatory and quality teams can readily trace to the claims and requirements in the submission.

This is particularly relevant when testing is performed to consensus standards. A declaration of conformity, test report, and supporting records need to align with the exact edition of the standard, applicable collateral or particular standards, device configuration, and deviations. A report that cites a standard without explaining the test article or configuration may leave reviewers unable to determine whether the evidence applies to the commercial device.

Accreditation and FDA ASCA: What They Mean

ISO/IEC 17025 accreditation is a foundational consideration for an FDA submission testing laboratory. Accreditation indicates that a laboratory’s quality system and technical competence have been assessed for specified testing activities. It is not a blanket endorsement of every service a laboratory offers. Manufacturers should review the laboratory’s current accredited scope and confirm that the required method, measurement range, and device category are included.

For eligible medical device standards, FDA Accreditation Scheme for Conformity Assessment, or ASCA, recognition can add meaningful regulatory value. Under the FDA ASCA program, an accredited testing laboratory may conduct testing within its recognized scope and issue reports intended to support certain FDA device submissions. This can provide FDA with greater confidence in the laboratory’s conformity assessment process.

ASCA status should be evaluated with precision. It does not eliminate the need to select the correct standards, define the intended use, establish valid test conditions, or assess results against the device’s risk profile. It also does not apply to every test or every device. Manufacturers should confirm that both the laboratory and the specific standard are within the applicable ASCA scope before planning the project around ASCA testing.

Match Laboratory Capability to the Device, Not Just the Standard

Two laboratories may list the same IEC or ISO standard, but their experience with the specific device can be very different. That distinction matters when testing involves complex operating modes, transducers, patient-connected parts, software-controlled functions, accessories, or multiple power configurations.

For example, electrical safety testing for a patient monitor, diagnostic ultrasound system, and physiotherapy device may draw from related standards but require different fixture design, operating conditions, essential performance considerations, and interpretation of results. Ultrasound testing may require controlled measurements of acoustic power, intensity, beam characteristics, and image quality. Endoscope evaluation may involve optical performance, insertion tube considerations, leakage testing, or other device-specific requirements. The laboratory must be able to control and document the conditions that make each result meaningful.

Ask whether the laboratory has the equipment, personnel competence, and established procedures for the relevant technology. A generic test capability may be adequate for straightforward devices. For specialized systems, a laboratory with focused medical device experience can reduce uncertainty during protocol review and test execution.

Define the Test Article Before Samples Arrive

Many avoidable delays originate from an incomplete definition of the device under test. The laboratory needs to know what is being evaluated, which configuration represents the commercial product, and how the device should operate during testing.

This definition should address model numbers, software or firmware versions, accessories, power supplies, cables, patient-contacting components, packaging where applicable, and any regional variants. If the device is tested in a worst-case configuration, the technical basis for that selection should be documented. If multiple configurations are covered by one report, the manufacturer should be able to explain why the results extend across the product family.

Pre-test communication should also establish sample quantity, conditioning requirements, calibration needs, shipping constraints, and expected operating instructions. Devices that require clinical simulation, specialized consumables, trained operators, or controlled environmental conditions need additional planning. A lab cannot create a defensible test record from an inadequately configured sample.

Review Protocols for Submission Relevance

A protocol is more than a sequence of laboratory steps. It connects the applicable standard to the actual device, test equipment, acceptance criteria, and reportable data. Manufacturers should review protocols before formal execution, particularly for novel, high-risk, or technically complex devices.

The protocol should identify the standard and edition, test article identification, equipment and measurement methods, operating conditions, pass/fail criteria, and planned deviations. It should also state how anomalies will be handled. If a standard permits alternative methods or requires engineering judgment, the rationale should be captured before testing rather than reconstructed after results are available.

This review is especially valuable where essential performance is involved. Passing a general safety requirement may not be sufficient if a device loses a function necessary to achieve its intended medical purpose. The manufacturer’s risk management file, system requirements, and verification plan should inform how the laboratory evaluates relevant performance during normal and single-fault conditions.

Evaluate Report Quality, Not Only Turnaround Time

Fast scheduling has value, especially when a submission date is fixed. However, a short turnaround is useful only if the final report contains the detail needed for regulatory review. The report should clearly identify the test article, method, instrumentation, calibration status, test conditions, results, observations, deviations, and conclusion.

Traceability is central. A reviewer should be able to follow a result from the reported value back to the device configuration, protocol, test setup, and measurement system. Photographs, diagrams, tabulated data, and configuration records can be essential where setup affects the outcome. For failures or conditional results, the report should distinguish factual observations from the manufacturer’s subsequent engineering assessment.

Manufacturers should also understand the laboratory’s process for revisions. Minor administrative corrections are common. Changes to the device, software, test configuration, acceptance criteria, or method after completion may require partial or complete retesting. A disciplined change-control process protects the credibility of the final report, even when it adds time.

Build Time for Investigation and Retest

A testing schedule should include more than bench time. Device intake, setup review, conditioning, protocol approval, data analysis, report review, and corrective action can each affect the final date. This is most apparent when a device fails an initial test or produces borderline results.

An unexpected result is not automatically a laboratory problem or a product failure. It may reveal a configuration issue, an incorrect assumption about the applicable standard, a sample defect, or a genuine design concern. The appropriate response depends on the facts. Teams should allow time to investigate, document the cause, implement design changes when necessary, and determine whether retesting is required.

Early engagement helps prevent a submission-critical test from becoming a late-stage discovery. Sigma Scientific Services supports medical device manufacturers with standards-based safety and performance testing, including specialized acoustic, ultrasound, electrical, materials, endoscope, physiotherapy, clinical, and human factors evaluations.

The strongest laboratory relationship begins with a complete technical question: what device configuration is being submitted, which requirements apply, and what evidence must the report establish? When those answers are defined before samples enter the lab, testing becomes a controlled part of product verification rather than a last-minute obstacle to market access.