A New Standards List Can Reopen Old Evidence Decisions

A standards register can be perfectly current while the product evidence behind it is already out of date.

FDA entered Recognition List 066 decisions in its Recognized Consensus Standards Database on May 25, 2026, and the agency's August 24 Federal Register notice formally announces the list. FDA also makes an important timing distinction: manufacturers may use a standard toward a declaration of conformity once it appears in the database, without waiting for the periodic Federal Register notice.

The list adds, withdraws, replaces, and revises standards across several medical device disciplines. Among the changes are newer editions of ISO 10993-1 for biological safety evaluation, ISO 10993-12 for sample preparation, ISO 20417 for information supplied by the manufacturer, cardiovascular-device standards, materials standards, and software and informatics entries.

Updating a standards spreadsheet is the easy part. The harder work is finding every design decision, protocol, supplier specification, test report, declaration of conformity, and submission plan that depends on one of those entries.

That work requires judgment. A newly recognized edition does not automatically invalidate prior testing or disturb an existing clearance. It can, however, change the evidence strategy for a device in development, a submission approaching filing, or the next modification to an authorized product.

List 066 changes more than the standards register

FDA recognizes consensus standards so manufacturers may use them to support parts of a premarket submission or another applicable regulatory requirement. Their use is generally voluntary unless a standard has been incorporated by reference into a regulation.

Recognition is also specific. FDA recognizes a particular edition, assigns a recognition number, and may recognize only part of a standard. The Supplemental Information Sheet, or SIS, records the scope, extent of recognition, transition information, and other details that determine how the standard may be used.

That distinction matters with List 066. A team cannot safely conclude that it is current because the standard named in a protocol appears somewhere in FDA's database. It needs to confirm:

• the exact edition used;
• the FDA recognition number;
• whether recognition is complete or partial;
• whether the device and testing fall within the recognized scope;
• whether an outgoing edition remains within a transition period; and
• whether FDA identifies additional documentation or limitations in the SIS.

FDA's Recognition List 066 notice is the formal announcement. The FDA Recognized Consensus Standards Database is where the team should confirm the current recognition record and SIS for each standard.

Start with FDA's recognition decision

A standards-development organization may publish a newer edition before FDA decides whether, when, or to what extent to recognize it. FDA's database may also reflect a recognition decision before the periodic Federal Register notice appears.

For regulatory planning, the FDA record controls the declaration-of-conformity strategy. The team should not rely on the standard's publication date, a laboratory's preferred edition, or a general statement that the company uses the "latest version."

Start by comparing the outgoing and incoming FDA records. Identify what changed in the recognized edition and whether the change affects a safety, performance, labeling, risk-management, testing, or documentation question relevant to the device.

This is not a clause-counting exercise. A short amendment can affect a critical method or acceptance decision, while a broad editorial revision may have little product impact. The assessment should explain the relationship between the changed content and the device's actual design, intended use, materials, interfaces, risks, and evidence.

Find every place the affected standard is being used

The same standard can have a different consequence depending on where the product sits in its lifecycle.

Products in development

For a device still in design and development, trace the new edition into design inputs, risk controls, test methods, acceptance criteria, supplier requirements, and verification or validation plans.

If testing has not started, adopting the new recognized edition may be straightforward. If protocols are approved, samples are built, or laboratory work is underway, the team needs a documented decision about whether to continue, amend the work, or add a focused bridge.

Bring the external laboratory into that decision early. The manufacturer remains responsible for the evidence even when another organization performs the testing. IntelaSolve's article on third-party testing data integrity explains why ownership of the protocol, raw data, deviations, and final report cannot be delegated with the test.

Submissions nearing filing or under review

FDA's guidance on the appropriate use of voluntary consensus standards explains how transition periods work. When FDA replaces a recognized standard, the older edition may remain acceptable for declarations of conformity until the transition date stated in the SIS.

That period is not permission to ignore the revised edition. FDA recommends a justification when the newer standard raises significant questions that the older edition did not address.

For a submission that has not yet been filed, compare the planned filing date with the SIS transition date. Confirm whether the supporting testing, declaration of conformity, and submission references will still be acceptable when FDA receives the application.

For a submission already under active review, FDA generally continues reviewing against the previously recognized edition. If the revised standard addresses a new safety or effectiveness issue relevant to the decision, FDA may request evidence addressing that issue or an alternative supported by scientific rationale.

The regulatory owner should document the active-review strategy instead of leaving it as an informal assumption between the project lead and reviewer.

Legally marketed devices

A new or revised recognized standard does not retroactively change a device's clearance or approval status. FDA's guidance is clear on that point.

Still, the update belongs in postmarket standards surveillance. The manufacturer should determine whether the new edition reveals a relevant safety issue, changes the accepted state of the art, affects a future modification, or alters the evidence expected for a new device that uses the marketed product as a predicate.

The result may be no immediate product action. That is a valid conclusion when it is based on a documented assessment. Silence is not the same thing.

Make one evidence decision for each affected product

A useful standards-impact record should connect the regulatory update to a defined product or product family. It should state:

1. The outgoing and incoming standards, editions, recognition numbers, and SIS references.
2. The affected products, models, accessories, and intended uses.
3. Where the standard appears in controlled records, including specifications, risk files, protocols, reports, supplier documents, labeling, and submissions.
4. The material differences between the editions that matter to the device.
5. The current evidence available and any limitations in its applicability.
6. The action selected, responsible owner, due date, and approval.
7. The trigger for reassessment, such as a design change, new submission, complaint trend, or transition-period deadline.

This record should link to the evidence it evaluates. A conclusion that says "no impact" without showing which products, clauses, tests, and risks were reviewed will not help the next person who has to defend the decision.

Do not turn every revision into automatic retesting

Retesting may be necessary when a changed method, acceptance criterion, device scope, or newly identified safety issue makes the existing evidence insufficient. It is not the only possible response.

Other supportable outcomes may include:

• continued use of the outgoing edition within its transition period;
• a documented gap assessment showing that existing evidence addresses the changed provisions;
• a focused supplemental test;
• a bridge between prior and new methods;
• revised labeling or risk documentation;
• a future-action commitment tied to a planned product change; or
• early discussion with FDA when the submission consequence remains uncertain.

The decision should follow the risk and evidence. It should not follow a blanket policy that every new edition requires a complete test program, or that prior testing is always good enough because it once supported clearance.

Keep the decision connected to the product lifecycle

Standards surveillance often begins in regulatory affairs, but the consequences travel through engineering, testing, quality, suppliers, labeling, manufacturing, and postmarket work.

When those functions use separate trackers, the standards decision becomes difficult to follow. Regulatory may update the recognized edition while an external laboratory works from an older protocol. Engineering may revise a specification without knowing that the same change affects a declaration of conformity. A postmarket reviewer may find a new safety issue without seeing the earlier gap assessment.

Connected compliance infrastructure changes that operating model. The standard, affected device, design output, risk control, test evidence, supplier requirement, submission reference, and later change can remain part of one traceable decision chain.

IntelaSolve's project-verified medical-device compliance platform is designed around the relationship among design controls, risk management, regulatory work, quality, manufacturing and operations, and postmarket evidence. It does not decide whether an older test remains acceptable. It gives the qualified team a controlled place to make that decision, approve it, and preserve the evidence behind it.

The broader QMSR inspection-readiness discussion is relevant here. A procedure showing that the company monitors standards is useful. The stronger evidence is the trail showing what the company found, which products it assessed, who decided, and what happened next.

A practical standards-impact workflow

Begin with the standards in List 066 that touch active products or development programs. Do not try to solve the entire corporate standards library in one meeting.

For each affected standard:

1. Confirm the FDA recognition record and SIS.
2. Identify every product and controlled record that cites the standard.
3. Separate products by lifecycle status: development, pre-submission, active review, or marketed.
4. Compare the changed provisions with the device's risks and existing evidence.
5. Select and approve a product-specific disposition.
6. Link the action to testing, documentation, submissions, suppliers, and change control.
7. Set a transition-date or product-change trigger for follow-up.

The best outcome is not always more testing. It is a decision that remains understandable after the project team has changed and the next submission is underway.