21 CFR 820 QSR Documentation
Mark Kaganov | April 26, 201021 CFR 820 documentation structure may be developed as outlined in the Guidelines for Developing Quality Manuals (ISO 10013 Standard). This standard recommends using a three-level structure. In practice, many companies use four-level documentation model that includes records. 4-level quality management system is shown below:
Manual (level 1), 21 CFR 820 Procedures (level 2), Instructions (level 3), and QMS Records (level 4)
Actually, the documentation structure for a medical device manufacturer starts from the policy, required by section 820.20 (a). The policy, among others, defines the regulations and standards that a company intends to comply with. If you choose to use this approach, your quality management system will have five levels, similar to the structure below:
21 CFR 820 Policy – level 1
Quality Manual – level 2
Operating Procedures – level 3
Instructions – level 4
Quality Records – level 5
21 CFR 820 – Naming your documents
As you may have noticed, the titles of the documents in the structure above are quite short. Various medical device manufacturers use different conventions for their document titles. For example, one of my customers titled their quality manual as “Quality Management System Quality Manual.”
Regulated industries, including medical device manufacturers, are known for calling the 2nd-level documents “Standard Operating Procedures” or SOPs. Do these companies have “Non-standard Operating Procedures”, so these long titles differentiate them? Since a short name identifies a document, I really cannot justify long names for documents. I preach 21 CFR 820 management system optimization and reduction of waste in all elements of management systems. I invite you too not to make things more difficult than they have to be to deliver the message.
Numbering your 21 CFR 820 documents
It is not a specific requirement of the 21 CFR 820 or any other regulation or standard to uniquely number a part or a document. It is a common-sense measure and a worldwide practice in any documentation system, to give a document or a component a number and a title, and to identify its revision level. As long document titles that we discussed earlier, document numbering formats very often are also an opportunity for optimization.
One of my clients runs a small company of some 120 employees. Their documentation control procedure prescribed two numeration systems that dependent on the type of a document. 21 CDR 820 QMS documents had numbers like XX-XXX, and production parts required part number format as XXXXXX-XXX. One of the drawings had a number 000076-003. Folks on the floor called it “seventy six.”
One can certainly use these long-long numbers, but is it practical? So far I did not meet a single company that could justify such an approach. When I audited this client, the organization had less than 200 documents. There were no indications that the company will significantly grow. Therefore, to use document number format allowing hundreds of thousands of numbers could hardly be justified. The most unreadable part numbers I had to deal with was at a mid size medical device manufacturer with 13-digit alpha-numeric part number format! Try to write those in your audit report!
I hope it is clear that when extensive part numbers are not justified, we do not have to use them. If you build helicopters or space probes, you, no doubt, will need millions of parts and therefore will need long document part numbers. If not, make your life easy and stay away from all those zeros. The most practical system I worked with used a three-digit format for their part numbers. 502, 503, 204, and so on. The system worked just fine!
Part Number designators
Another debatable issue with the part-numbering is part number designation. Some management systems associate a part number with a particular part type. For example, 20-xxx indicates a procedure, 30-xxx indicates a drawing, P-xxx indicates a policy-level document, and so on. My experience with a number of 21 CFR 820 medical device manufacturers has convinced me in the benefits of a “no designation” system. Three of my clients’ systems that used P/N designators have failed. Just recently, one of my customers reported that they ran out of range in their part numbering format.
The QMS initially permitted for identifying paint color through a two-digit extension within the part number. While the company grew, the number of paint options increased beyond expectations and eventually the company needed more than 99 colors. This resulted in the document number format not being able to support the requirements.
To get around this issue, there is a simple solution – a “no designation” system. Document numbers in such systems are simply assigned unique numbers. Areas of use, materials, suppliers, and other attributes are not reflected in part numbers. Moving in this direction, you can simplify your system even more. I worked with a company that did not use document No’s at all. That documentation system used just document names followed by their revision numbers, like Process Validation Protocol AB.
If you are working on your 21 CFR 820 quality management system, check out our 21 CFR 820 Quality Assurance consulting services.