Regulatory Open Forum

 View Only
  • 1.  Declaration of Conformity

    This message was posted by a user wishing to remain anonymous
    Posted 20-Apr-2023 09:25
    This message was posted by a user wishing to remain anonymous

    Hi all, 

    Wondering if US FDA requires us to have a Declaration of Conformity such as in the EU? I know that during the submission (510K) you do have to declare the recognized standards. 

    Also, if we do then can we combine both US and EU into one Declaration of Conformity?

    Thank you!



  • 2.  RE: Declaration of Conformity

    Posted 20-Apr-2023 16:50
    Edited by Kevin Randall 20-Apr-2023 16:52

    In short, no, the US FDA doesn't, as a general rule, require us to have a Declaration of Conformity (DoC) such as in the EU.  But the U.S. FDA does allow the voluntary use of a DoC in certain situations.  For example, in those situations where a 510(k) both a) relies on a voluntary/mandatory consensus standard; and b) the device conforms to all of the requirements of the applied consensus standard.  In other words, if there is any deviation in conformity with the applied consensus standard, then a DoC is not allowed by the FDA.

    At one time, such declarations were generally limited to an "Abbreviated 510(k)".  But nowadays, the way standards are used in Traditional 510(k)s vs. Abbreviated 510(k)s has, in my opinion, become basically the same.

    Further evidence of the voluntary nature of such DoCs for the FDA is that FDA may alternatively accept what the agency calls "general use" of consensus standards.  "General use" means situations where the Sponsor decides to apply a consensus standard, yet does not submit a DoC.  Such use could involve either full conformity or partial conformity with the applied standard.

    In contrast, every EU MDR / IVDR conformity assessment (except special scenarios like custom-made devices, investigational devices, Article 22 products, etc.) shall include a DoC drawn up in accordance with those European Regulations.

    Now, since the aforesaid U.S. DoCs and EU DoCs are both generally modeled after ISO 17050-1 / EN ISO 17050-1 as amended, it certainly wouldn't be hard to draw up a hybrid DoC that covers both jurisdictions.  But my personal preference is to not mix such declarations.  This is for document succinctness, easier revision control, and to avoid convolution between Europe's "EN" standards compared to the non-EN versions recognized by the U.S., and also because the basic legislative/statutory reasons/uses of DoCs in the U.S. are fundamentally different than their use for the EU.



    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2023 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 3.  RE: Declaration of Conformity

    Posted 20-Apr-2023 16:53

    Just fixed the 17050-1 typo.



    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2023 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 4.  RE: Declaration of Conformity

    Posted 21-Apr-2023 09:48

    Hello,

    Sorry Kevin, I have to sort of clarify declaration of conformity and circumstances you provided.

    - A Declaration of Conformity for the EU MDR 2017/745 follows Annex IV (and in the previous EU MDD); there is a defined structured there and expected content by Notified Bodies.  In fact, some Notified Bodies have a recommended structure they want companies to use.
    - A Declaration of Conformity to voluntary or recognised standards by the US FDA for use in premarket applications such as 510(k) is something different.  There is specific information related to conformity to a standard provided in the premarket application such as full/part compliance, accreditation by external parties, and other information.  This is not a post market document.  And it is not the same as a Declaration of Conformity in the EU, I do not believe a hybrid could be used as the content is completely different.
    - A Declaration of Conformity a company uses specific to their product would define product specifications, acceptance criteria, and how these were met for their product.  This could be done for the entire product line or say batch-to-batch or by lot.  This is typically something required by a customer or something by the product type, such as materials in the device or composition of the device.  This could potentially be combined with the Declaration of Conformity in the EU, but would definitely gain acceptance by your Notified Body (if using one).  In this case, could use ISO 17050-1 for the structure and content.
    - A Declaration of Conformity a supplier/vendor provides to a company for their raw materials, components, or product would define product specifications, acceptance criteria, and how these were met for their product.  From a supplier the ISO 17050-1 can definitely (and should be) used for the structure and content.  Keep in mind ISO 17050-1 is an international standard and not specific to medical devices, so this is used in many other industries.  The terms Certificate of Conformity or Certificate of Conformance are also used synonymously in a supplier of materials situation.  (There is also the Certificate of Analysis which is often used synonymously, but for me is different.)

    I do agree the Europe CE Mark and US FDA use of declaration of conformities should not be mixed.  These are two different regulatory approaches and used for different purposes.



    ------------------------------
    Richard Vincins ASQ-CQA, MTOPRA, RAC
    Vice President Global Regulatory Affairs
    ------------------------------



  • 5.  RE: Declaration of Conformity

    Posted 21-Apr-2023 10:52

    Hi Richard, many thanks for your clarifications.  I must have gotten you (and maybe others) confused.  Let me clarify:

    I think that most everyone knows that Annex IV of the EU MDR/IVDR prescribes the exact elements for an EU MDR/IVDR DoC.  But Anon isn't asking how to do an EU MDR/IVDR DoC, nor about what are the precise elements of an EU MDR/IVDR DoC.  Instead, Anon asked about combining a US DoC with an EU MDR DoC.  Accordingly, for such comparative purposes (U.S. vs. EU), it is for two reasons quite germane that an EU MDR/IVDR DoC it is fundamentally modeled after (not the same as, but modeled after) EN ISO 17050-1.  Specifically:

    a) EN ISO 17050-1 and Europe's common framework are the traditional basis that gave rise to Annex IV.  For example, the Blue Guide reminds us of that when it states, "...The standard EN ISO/IEC 17050-1 has been drawn up with the objective of providing the general criteria for the declaration of conformity...". Prior to EU MDR  Annex IV's prescription, notified body's used EN ISO 17050-1 as the basis for auditing MDD DoCs.  Again, it is correct that the exact requirements for an EU MDR/IVDR DoC are prescribed by Annex IV, but again that is not Anon's question.

    b) The U.S. FDA's stated policy is that, "...To certify conformance with a consensus standard, the submitter must submit a DOC...These elements of a DOC are consistent with ISO/IEC 17050-1..."

    Accordingly, my answer to Anon's question about the logistical aspect of combining a U.S. and EU DoC into a single document is certainly correct.  But again as I mentioned in my first post: Because of the fundamentally different statutory/legislative reasons for a U.S. vs. EU DoC, I don't recommend such a hybridized approach.

    On that note, I certainly agree with you that a U.S. DoC "is something different".  Specifically, see my initial post distinguishing the differences between the way the U.S uses DoCs [e.g., for the statutory purposes of section 510(k) of the FD&C Act] vs. the way the EU uses it (i.e., for EU MDR / IVDR conformity assessment).

    Your narrative, "[A U.S. DoC] is not a post market document" [emphasis added] seems to indicate that you are saying that an EU MDR/IVDR DoC is a post market document.  But that would be incorrect.  Instead, an EU MDR/UVDR DoC must be drawn up before placing the devices on the market.

    Regarding your use of the name 'Declaration of Conformity' for, "...a company uses specific to their product would define product specifications, acceptance criteria, and how these were met for their product...", my experience is that such a document is instead called a Certificate of Conformity (CoC), Certificate of Analysis (CoA), or something similar.  I've not heard of, or seen, such a document being called a 'Declaration of Conformity' though you must have.  But to avoid confusion with the more proper, conventional, and legislative use of 'Declaration of Conformity', I would recommend against using 'Declaration of Conformity' for a CoC/CoA.



    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2023 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------



  • 6.  RE: Declaration of Conformity

    Posted 24-Apr-2023 02:11

    Hi all

    To Kevin's point of DoC vs. CoC: my understanding is that a company, supplier, ... can declare something in writing. However, only some entity that is accredited can certify. Thus, a company issues a declaration, an accedited lab issues a type test certificate.

    Can you support this?



    ------------------------------
    Richard Jansky
    Head of RA / RM / QM
    Beringen
    Switzerland
    ------------------------------



  • 7.  RE: Declaration of Conformity

    Posted 24-Apr-2023 12:07

    I think both Richards have raised valid points regarding the various different kinds of declarations and certifications germane to the medical devices sector.  Richard J., I do agree with your important and correct (in my opinion) understanding that there is a proper distinction between "declaration" and "certification" (I give my further interpretations about that herein per your request).

    Ultimately, the precise context of each given scenario bears significantly on which vernacular is appropriate.  But also one's real-world tolerance (or lack thereof) for longstanding entrenched tradition, vs. the strictest proper interpretation of these matters.  Indeed, this thread reveals yet another example where there is tension between formally-established terminology vs. longstanding practice.  It can certainly be argued that the CoC/CoA terminology isn't the most correct language. On the other hand, it can also be argued that the CoC/CoA terminology isn't wrong either.  Complicating the issue is that many organizations and agencies alike have organically woven the CoC/CoA terms into their paradigms.

    For example, Richard V. and myself have made reference to manufacturer/supplier-sponsored CoA, CoC, etc. My experience is that the creation of such CoA/CoC by medical device manufacturers/suppliers is similar to analogous precedents from the pharmaceutical GMP sector like those modeled in the EMA Guideline on batch certification and in the EU GMP Guide Parts I & II.  This would not be the first time that I've seen pharma GMP concepts adapted into the medical device GMP sector. Some more organic medical device precedents include those from the IMDRF (formerly the GHTF) and ISO/TC 210, who both acknowledge the use of the CoA/CoC vernacular.  For example ISO/TC 210's guidance about the benefit of CoA/CoC for component (whether in-house or outsourced) traceability.

    I think an insightful reference echoing (maybe even giving rise to) this terminology dilemma is ISO / EN ISO 17000 (as amended, and as applicable, covering vocabulary and principles, hereinafter "ISO 17000").  Specifically, it fundamentally establishes the terms "attestation" (i.e., a statement, based on a decision following review, that fulfilment of specified requirements has been demonstrated [emphasis added]), and "statement of conformity" (a generic expression used to include all means of communicating that fulfilment of specified requirements has been demonstrated, and conveying assurance that the specified requirements have been fulfilled [emphasis added]), and "first-party attestation" (e.g., by a device manufacturer).  All of these, in my opinion, correlate with the CoA/CoC concepts.  For example, ISO 17000 says that, "...Instead of "assurance of conformity", the term "attestation" is used..." [emphasis added].  Then the standard goes on to clarify that "declaration" is first-party attestation, while "certification" (e.g., notified body type test certification; other agency electrical safety testing certification, etc.) is a third-party attestation (thus bridging us over to the aforesaid ISO 17050-1 "declaration").

    So, the longstanding "CoA" / "CoC" terms don't exactly fit nicely with these ISO 17000 terms.  Yet they aren't exactly wrong either (in my opinion).  Because of this, and of the entrenched precedents for the "CoA" / "CoC" terminology (indeed, time and time again, I've seen organizations into whose operating infrastructure these terms are deeply woven, such that we'd be clanging gongs to try and strike down that language), I'm not ready to abandon/retire those terms just yet.
      But when it becomes time to do that, I agree that the most standardized proper term is "declaration".



    ------------------------------
    Kevin Randall, ASQ CQA, RAC (Europe, U.S., Canada)
    Principal Consultant
    Ridgway, CO
    United States
    © Copyright 2023 by ComplianceAcuity, Inc. All rights reserved.
    ------------------------------