How to Prepare an FDA ASCA Submission Correctly

A test report can be technically sound and still create avoidable FDA questions if it is not tied to the right recognized standard, test method, accreditation scope, and submission documentation. To prepare an FDA ASCA submission effectively, regulatory and engineering teams need to make those decisions before testing begins, not while the submission is being assembled.

The FDA Accreditation Scheme for Conformity Assessment (ASCA) is intended to provide greater confidence in test reports for eligible medical device standards and test methods. It does not replace device-specific regulatory analysis, risk management, or the need to demonstrate substantial equivalence or safety and effectiveness. It does provide a structured path for submitting certain standards-based testing performed by an FDA ASCA-accredited laboratory.

Start With FDA ASCA Eligibility, Not the Test Plan

The first question is not whether a device needs electrical, acoustic, ultrasound, biocompatibility, or performance testing. The first question is whether the specific standard and test method are eligible under the current ASCA program and whether they apply to the device under review.

FDA ASCA applies only to standards and test methods included in the program’s recognized scope. A laboratory’s ASCA accreditation is also limited to its approved scope. An ISO or IEC standard may be broadly relevant to the device but still fall outside the available ASCA scope, or the particular edition recognized by FDA may differ from the edition referenced in an existing protocol.

This is where a pre-test standards review prevents rework. The manufacturer should identify the intended submission type, device classification, applicable FDA-recognized consensus standards, test method editions, and product configurations to be evaluated. The laboratory should then confirm that the requested work falls within its active ASCA accreditation scope.

For example, an electrical safety evaluation may involve IEC 60601-1 and applicable collateral or particular standards. A diagnostic ultrasound device may also require evaluation of acoustic output, output display information, image quality, transducer performance, and device-specific software functions. ASCA applicability should be determined at the level of each proposed standard and test activity, rather than assumed from the device category alone.

Define the Device Configuration Before Testing

An ASCA submission depends on traceability. FDA reviewers need to understand precisely what device was tested and whether that unit represents the device described in the marketing submission. A report that identifies only a product family name, without clear configuration control, can create questions about applicability.

Before samples are shipped, document the intended commercial configuration. This should include model numbers, accessories, probes or transducers, power supplies, software and firmware versions, patient-contacting components where relevant, and critical design variants. If multiple configurations are represented by a worst-case sample, the technical rationale must be established in advance.

Worst-case selection is often appropriate, but it must be defensible. The highest output setting may be worst case for acoustic emissions. The largest conductive surface or highest applied voltage may be worst case for electrical testing. A configuration with a particular cable, accessory, or environmental operating mode may drive electromagnetic compatibility performance. There is no universal worst case across all standards.

The test article should also be controlled through the full evaluation. Record the sample receipt condition, serial number, calibration status where applicable, preconditioning, modifications, failures, retesting, and final disposition. These details support the report’s chain of evidence and help regulatory teams reconcile the tested device with the design history and risk management files.

Build a Test Plan That Matches the Submission Claim

A laboratory protocol should not be treated as a stand-alone engineering document. It should reflect the regulatory claim the manufacturer intends to make. That means aligning the test plan with the declaration of conformity, the applicable standard edition, the intended use, and the device’s risk controls.

Before work starts, resolve four areas that commonly cause problems:

• The exact FDA-recognized consensus standard and edition being cited
• The applicable clauses, test methods, and acceptance criteria
• Any deviations, exclusions, or justified alternative methods
• The relationship between test results and the device risk management documentation

A deviation is not automatically disqualifying. Some devices require a modified setup, an alternative measurement approach, or a justified exclusion because a clause does not apply to the technology. The issue is whether the deviation is transparent, scientifically justified, and assessed for its regulatory impact. Undocumented deviations are far more difficult to defend than deliberate, well-supported ones.

Test planning should also account for interdependent evidence. Electrical safety, EMC, usability engineering, software documentation, clinical evaluation, and performance testing may each address separate requirements, yet the conclusions must be consistent. If a labeling instruction used in human factors validation differs from the instruction evaluated in a performance protocol, the submission can become internally misaligned.

What to Include When You Prepare an FDA ASCA Submission

The ASCA-specific documentation should be assembled alongside, not after, the laboratory testing package. For eligible testing, manufacturers generally rely on an FDA ASCA Summary Test Report and an appropriate declaration of conformity as part of their FDA submission. The exact content and placement should follow the current FDA guidance and the submission type.

The ASCA Summary Test Report should accurately identify the accredited laboratory, the applicable standard and test method, the device tested, the results, and any relevant limitations. It should not overstate the scope of testing. A passing result for one configuration or one standard does not establish compliance with every applicable requirement for the product family.

A well-organized submission package typically connects several records: the summary test report, full laboratory report where required or requested, declaration of conformity, risk management references, device description, labeling, and other supporting performance data. Consistency among these documents matters as much as the individual results.

Pay close attention to dates and document control. Accreditation status, laboratory scope, standard editions, sample configuration, and report revisions should be traceable to the period in which testing occurred. If a report is revised after testing, the reason for revision should be clear. Administrative corrections and substantive changes should not be treated the same way.

Select an ASCA Laboratory for Scope and Technical Fit

ASCA accreditation is specific. A laboratory may be accredited for certain standards and test methods but not others. Manufacturers should evaluate the laboratory’s current ASCA scope, ISO/IEC 17025 accreditation, technical experience with the device category, measurement capability, and ability to support the required test configurations.

Technical fit is especially important for specialized devices. Diagnostic ultrasound systems may require expertise in acoustic power, thermal and mechanical index-related measurements, output display verification, and image quality evaluation. Patient monitors, ECG equipment, endoscopes, catheters, and physiotherapy systems each introduce different safety and performance considerations. A lab that understands the relevant standards can identify configuration gaps before they become report deficiencies.

Commercial responsiveness also affects submission readiness. A fast quotation is useful, but the more meaningful measure is whether the laboratory asks the right technical questions at the outset. Sigma Scientific Services provides FDA ASCA-accredited and ISO/IEC 17025-accredited testing within a focused medical device scope, helping teams establish the standards, samples, and documentation needed before the test schedule is committed.

Manage Changes During and After Testing

Device development rarely stops while compliance testing is underway. Firmware updates, supplier changes, enclosure revisions, accessory substitutions, and labeling changes can all affect the relevance of completed results. The manufacturer should operate a clear change-control process during testing and before submission.

Not every change requires full retesting. The required response depends on the nature of the change, the standard involved, the tested configuration, and the risk assessment. A cosmetic housing revision may have no impact on applicable electrical or acoustic results. A change to a power-management circuit, transducer assembly, patient-contacting material, or operating software may require a documented impact assessment and possibly targeted or complete retesting.

The key is to avoid silently bridging from a tested unit to an untested commercial device. If engineering determines that existing evidence remains applicable, that decision should be recorded with a technical rationale. If the change affects an ASCA test report, involve the laboratory early to determine whether the report can be supplemented, whether a new test article is needed, or whether the ASCA documentation must be revised.

Common Causes of Avoidable FDA Questions

Many submission issues originate in ordinary project handoffs. Regulatory affairs may cite a standard edition that differs from the one used in the laboratory report. Engineering may release a software build after testing without documenting its impact. A declaration of conformity may claim full conformance while the report contains unaddressed deviations or exclusions.

These issues are preventable when regulatory, quality, and engineering teams review the evidence as one package. A final submission readiness review should compare device identifiers, intended use, standard editions, test conclusions, sample configurations, labeling references, and risk-control claims across every relevant document.

The most useful time to engage an ASCA-accredited laboratory is before testing starts, when standards selection, device configuration, and protocol scope can still be corrected without disrupting the submission schedule. That early alignment turns testing from a late-stage document collection exercise into evidence that is ready to withstand regulatory review.