How to Prepare an ASCA Submission for FDA Review

A submission can be delayed by a single mismatch between the standard cited, the laboratory’s accreditation scope, and the test article actually evaluated. Knowing how to prepare an ASCA submission means managing those details before testing begins, not attempting to reconcile them when the premarket file is nearly complete.

FDA’s Accreditation Scheme for Conformity Assessment (ASCA) is intended to provide greater confidence in testing performed to eligible FDA-recognized consensus standards. For a device manufacturer, the practical value is clear: testing from an ASCA-accredited laboratory can support a more efficient FDA review when the applicable standard, test method, laboratory scope, and submission documentation are aligned.

Start With the ASCA Pathway and Device Claims

ASCA is not a substitute for determining the device’s regulatory pathway, establishing substantial equivalence, or demonstrating that all applicable performance requirements have been met. It is a conformity assessment framework for specific standards and testing areas. The manufacturer remains responsible for the overall premarket submission and for the adequacy of the evidence supporting the device’s intended use, indications, design, and risk controls.

Before requesting a quotation or shipping samples, identify the FDA-recognized consensus standards that apply to the device. Confirm the exact version recognized by FDA, the relevant clauses, and whether the standard is eligible under the ASCA program for the testing area at issue. Electrical safety and electromagnetic compatibility are common examples, but eligibility depends on the current program scope and the laboratory’s specific accreditation.

This distinction matters. A laboratory may be accredited to ISO/IEC 17025 and highly qualified to perform a test, while its ASCA accreditation scope may not cover the exact standard, edition, or test area planned for submission. Do not assume that an ASCA-accredited laboratory can issue ASCA documentation for every test it performs.

How to Prepare an ASCA Submission Before Testing Begins

The strongest ASCA submission package is built from a controlled test plan. Regulatory, quality, and engineering teams should agree on the device configuration and evidence strategy before the laboratory begins formal evaluation.

Confirm the exact test article configuration

Document the commercial configuration that the test article represents. This includes model numbers, firmware and software revisions, accessories, power supplies, patient-contacting components, cables, probes, transducers, and any optional configurations that affect the applicable standard.

For complex systems, one test article rarely represents every possible configuration without justification. A patient monitor with multiple modules, for example, may require a defined worst-case configuration for electrical safety or EMC evaluation. An ultrasound system may require specific probes, operating modes, output settings, and software versions for acoustic output and image-quality testing. The submission should make the relationship between the tested configuration and the device to be marketed unambiguous.

Changes made after testing can undermine the relevance of an otherwise complete report. Establish configuration control early and notify the laboratory promptly if hardware, software, labeling, or accessories change during the test program.

Define the applicable standard and clauses

A standard citation alone is not a test plan. Identify the clauses that apply, the clauses that are not applicable, and the rationale for any exclusions or alternative methods. This is particularly important when a standard includes conditional requirements based on device type, intended environment, applied parts, energy source, or patient population.

Provide the laboratory with the device description, intended use, risk-management information relevant to the test, instructions for use, labeling, and technical specifications. These inputs help the laboratory select appropriate operating modes and assess whether the test setup reflects normal use and reasonably foreseeable misuse where required.

If deviations from a standard are necessary, address them transparently. A deviation may be technically justified, but it should be assessed against the device’s risk controls and described consistently across the test report, declaration of conformity, and premarket submission. An unexplained discrepancy is more difficult to defend than a well-documented alternative approach.

Verify laboratory accreditation scope

Ask the laboratory to confirm that it is ASCA-accredited for the relevant testing area and standard. Review whether the specific edition and scope support the work planned. This step should occur before test authorization, particularly when the program includes multiple standards or combines testing disciplines such as electrical safety, acoustics, materials characterization, and human factors.

An FDA ASCA-accredited laboratory such as Sigma Scientific Services can help clarify whether a proposed test falls within its accredited scope. However, the manufacturer should retain the confirmation and incorporate it into its internal submission planning records.

Establish the test plan and acceptance criteria

The laboratory should receive a clear test request that identifies the standard, device configuration, required operating conditions, accessories, acceptance criteria, and anticipated submission use. For standards-based testing, acceptance criteria typically derive from the applicable standard. Device-specific requirements, risk controls, or predicate comparisons may also require supplemental evaluation.

Do not treat pre-compliance work and formal ASCA testing as interchangeable. Development testing is valuable for identifying failures early, but the final ASCA evaluation should be performed on controlled, representative articles under the agreed protocol. If pre-compliance results informed design decisions, retain them in the design history records, but do not present them as formal conformity evidence unless they meet the applicable requirements.

Build the FDA-Ready Documentation Package

The formal laboratory report is central to the submission, but it is not the only document that matters. The regulatory file should connect the report to the device, the declared standard, and the manufacturer’s conformity assessment.

For each eligible standard, ensure the ASCA documentation identifies the laboratory, its ASCA accreditation status, the standard and edition used, the tested device, test methods, results, deviations, and conclusions. FDA’s current ASCA guidance and any applicable templates should govern the format and required content of the ASCA Summary Test Report.

The manufacturer should review the report carefully before submission. Check model numbers, serial numbers, software versions, test dates, device descriptions, and referenced accessories against the submission’s device description. A report may be technically sound yet create review questions if it names a different firmware revision or omits an accessory described elsewhere in the 510(k), De Novo, PMA, or other premarket file.

The declaration of conformity should be equally precise. It should identify the FDA-recognized consensus standard, the applicable version, and the extent of conformity claimed. If only selected clauses apply, or if supplemental testing was performed outside the standard, state that clearly in the appropriate submission sections. Avoid broad claims of conformity that exceed the tested configuration or available evidence.

Avoid Common ASCA Submission Failures

Most preventable problems are administrative and technical alignment issues rather than laboratory execution failures. Four issues appear repeatedly:

• Testing is performed to an obsolete, non-recognized, or ineligible standard edition.
• The laboratory’s ASCA scope does not cover the exact test or standard cited in the submission.
• The tested article differs from the marketed device without a documented bridging rationale.
• The report, declaration of conformity, risk documentation, and device description use inconsistent terminology or configuration details.

These issues can be avoided through an early cross-functional review. Regulatory affairs should confirm the submission strategy, engineering should confirm the tested configuration, quality should maintain document control, and the laboratory should confirm the applicable method and accreditation scope. For devices with iterative development cycles, schedule this review before final verification articles are released.

Coordinate Changes Without Breaking the Evidence Chain

Post-test changes require a documented impact assessment. A minor labeling correction may have no effect on electrical safety or acoustic output evidence, while a software revision affecting power management, imaging modes, alarm behavior, or output settings may require additional analysis or retesting. The answer depends on the nature of the change, the standard requirements, and the risk impact.

Maintain traceability from the final device configuration to the laboratory test article. Preserve shipping records, photographs where appropriate, calibration information, test setup details, software revision records, and correspondence on deviations or retest decisions. This evidence helps support the submission and makes future change control more efficient.

A well-prepared ASCA submission does more than place an accredited report in a regulatory file. It shows that the device, the standard, the laboratory scope, and the conformity claim all describe the same controlled product. That alignment is the practical foundation for a clearer FDA review.