FDA Medical Device Academy

Archive for FDA

8 success tips for the first 30 minutes of an FDA inspection

Posted by Susan Christie on September 25, 2013

The author presents an 8 item action plan and discussion for getting your FDA inspection off to a good start, beginning when the FDA enters your facility. When an FDA inspector arrives at the reception desk of your facility, the last thing that you want is a Keystone Kops scenario with people running around in a panic and keeping the inspector waiting. This is your first opportunity to make a professional impression, and you never want to give an inspector the impression that you have something to hide. What happens during the first 30 minutes of arrival is critical. While medical device inspections are often announced several days in advance, there is no obligation for the Agency to do so. Therefore, your team needs training and a plan. This training should involve more than just reading the Quality System Inspection Technique (QSIT) manual (http://bit.ly/QSITManual), and conducting a mock FDA inspection. Last year, Rob Packard wrote a blog about “10 FDA Inspection Strategies that Don’t Work” (http://bit.ly/QSITmistakes), but the following activities need to be executed in the first 30 minutes to ensure your next inspection starts smoothly.

The FDA Inspection: 8 Immediate Actions to Take

1. Receptionist-Personnel Contacts (Time Zero)

I once witnessed a receptionist sarcastically comment to an inspector that people must be thrilled when they walk in the door. That was not a great start to the inspection. Ensure that your receptionist and additional personnel who may sit at the desk are trained, understand what to do, and know-how to behave when an FDA inspector(s) arrives. This exercise should not cause panic. You need a simple work instruction located at the reception desk and a list of key staff members to contact immediately. The head of the Quality department, or Management Representative, is usually the first call.

2. Have Chain of Command in Place (Time = 1 minute)

DO NOT keep the inspector waiting in the lobby. Have a communication chain in place to ensure that other appropriate personnel is available in the event that the first point of contact cannot be reached. It is reasonable to ask the inspector to return at a later date ONLY if all individuals with the technical expertise to participate in the inspection are not on-site, or are out of the country. The agent will decide whether to honor this request, but the expectation is that there is always someone with whom they can work with. Never make this request to put off the inevitable.

3. Ask To See Inspector Credentials (Time = 2 minutes)

Ask to see the inspector’s credentials, and ensure that you give them more than a cursory glance. This is important to avoid allowing an imposter posing as an Agency employee from gaining access to your business. While a rare occurrence, it has been known to happen. Some investigators are officers of the Public Health Service and may be in uniform. However, even these officers are not required to wear a uniform for all visits. Note: Section 5.1.1.2 of the FDA Investigations Operations Manual (http://bit.ly/FDAIOM) instructs inspectors to provide their credentials to top management, but copying of official credentials is not allowed.

4. Escort Inspector to Inspection Room (Time = 5 minutes)

Make sure that you can have the inspector escorted to a suitable room with the respective hosts within five minutes of arrival. This will involve ensuring that it is clearly understood by all administrative staff and key management that any other meeting may need to be curtailed, or moved immediately to another location to provide an appropriate space for the inspection. Providing substandard accommodations, such as a very cold or warm room, is not a good strategy for shortening the inspection time, and is a ploy easily recognized by the Agency, though not appreciated. Note: Rob Packard taught an audio seminar earlier this year, where the use of inspection war rooms was covered in more detail—including a diagram with a proposed layout for the room (http://bit.ly/FDAInspectionSeminar).

5. Ready the FDA Inspection War Room (Time = 10 minutes)

Immediately after your inspection room is identified, you need to prepare your backroom or “war room.” This room should be located near the inspection room and set up at a moment’s notice with staff who can expertly execute their respective roles. You will need a mode of communication between the inspection and war rooms, runners to retrieve documents and records in the shortest time possible, as well as a technical individual to review these documents to ensure that they are appropriate and accurate before being provided to the inspector. This room should be ready within ten minutes of arrival.

6. Ensure You Have Emergency Supplies & Copies (Time = 15 minutes)

Your war room will need supplies. You should have a mobile cart equipped with inspection supplies ready and waiting at all times. Suggestions for the contents of your war room cart include a laptop, projector, staplers, staples, pens, blank folders, a label maker, and a stamp for “uncontrolled copies.” Your supplies need to make it to the war room within 15 minutes of arrival.

7. Ready the Frequently Requested Documents (Time = 25 minutes)

Don’t wait for the inspector to tell you which documents are invariably requested at the outset of any inspection. This includes, but is not limited to, the organizational chart, an index of all procedures, CAPA log, and your nonconformance logs for medical devices—all dating back to the last inspection. This doesn’t mean that you should offer these documents to the inspector. You want to prepare these before they are requested so that they can be provided quickly, but you should keep the copies in the war room until the inspector requests each document and record. Copies of these records and documents should be stamped and ready within 25 minutes of arrival.

8. Relax (Time = 30 minutes)

It sounds as though this process is a race against time. It is not. No one engaging with the inspector should be running in and out of the room, gasping for breath, or sweating profusely from the effort. Keeping the inspector waiting can be perceived as a stall tactic, perhaps arousing suspicion that you are creating records “on the fly” in the war room (definitely not a strategy that I recommend), or that you are having difficulty locating the requested documents, and are not in control of your Quality Management System (QMS). The most important aspect is to manage your QMS so that you are always ready for an inspection at a moment’s notice. If you prepare in advance, you shouldn’t need to do anything more than ask if the inspector would like coffee before the inspection begins.

Please Connect With Medical Device Academy on Social Media

Tags: FDA, FDA inspection

Posted in: FDA

How to Utilize CAPA Training To Avoid FDA 483 Citations

Posted by Susan Christie on August 15, 2013

The author discusses how formal CAPA training can help solve the four most common CAPA deficiencies and help avoid FDA 483 citations.

Corrective And Preventive Action (CAPA) is considered to be one of the most critical processes in a Quality Management System (QMS). CAPAs prevent nonconformities from recurring, as well as identify potential problems that may occur within the QMS.

Both the Code of Federal Regulations (21 CFR 820.100) and the ISO 13485 Standard (8.5.2 and 8.5.3, respectively) include similar requirements for establishing and maintaining a compliant CAPA process. The concept seems pretty straightforward, right?

Then why do so many companies struggle with this process and go into panic mode during FDA inspections and Notified Body audits?

CAPA process deficiencies have long been the number one Good Manufacturing Practice (GMP) violation cited in FDA Warning Letters. Therefore, providing trained experts to teach the CAPA process is well worth the investment to provide your employees with the expertise needed to implement a sustainable, effective, and compliant process. Support from top management is a must for success.

7 Reasons Why There is LIttle Support for the CAPA Process

Managers view CAPA as a necessary evil and apply minimum effort and resources to complete the required paperwork.
All complaints, audit findings, shop floor nonconformities, etc., go straight into the CAPA system, resulting in what is known as “Death by CAPA.” There are hundreds of CAPAs to be dealt with, but the CAPAs languish and quickly become a mountain of overdue records.
The lack of ability to conduct effective root cause analysis results in, at best, a band-aid solution, and recurrence of the same issues time and again.
There is no risk-based or prioritization process that provides a triage for determining when a CAPA is appropriate, and how to classify its criticality.
CAPA forms are either too restrictive, such as using “yes/no” questions, thereby stemming the creative flow of process thinking or, too open-ended, leaving the CAPA owner with little guidance for getting to the exact root cause.
Trending and metrics that would highlight quality issues before they become complaints are lacking, so most CAPAs are last-minute reactions to a crisis, instead of proactive improvement projects.
Senior management has not allocated sufficient time and resources to CAPA owners to develop expertise, and clearly do not understand the nuances of FDA compliance, the ISO Standard, and the responsibilities of CAPA ownership.

Consequences of an Ineffective CAPA System: FDA 483 Citations Are Possible

FDA 483 observations, Warning Letters, and loss of your ISO 13485 certification are possible consequences of failing to manage your CAPA process. Imagine explaining to your customers why you lost your certification, and why they should keep you as a trusted supplier. That is not a conversation you want to have.

A weak CAPA process allows nonconformities to recur, results in manufacturing downtime, requires to rework, and ends with the scrapping of product or lost customers. The consequences of a weak CAPA process negatively impact your company’s financial strategy and goals.

To prevent an increase in the cost of poor quality, your business cannot remain static. You need to improve and adopt best practices. Your CAPA process is a systematic way to make those improvements happen.

Characteristics of an Effective CAPA system?

Easy to follow the procedure
Defined CAPA inputs
Risk assessment and prioritization
Root-cause investigation tools
A well-defined action plan
Metrics to track progress
Communication of information and status
Effectiveness checks
Management support and escalation

What to Expect from Formal CAPA Training

Death by Powerpoint is not training. Effective CAPA training requires hands-on participation in working through root-cause analysis with an expert. One of the best training tools is case studies based upon recent 483 observations. A CAPA training course should teach you how to:

Accurately identify the cause of problems
Prioritize your corrective and preventive actions using a risk-based approach
Implement an appropriate corrective and/or preventive action, and
Verify the effectiveness of your actions

CAPA training should teach you how to reduce the length and number of investigations. Training will also help you master current problem-solving methodologies to identify true root causes, utilizing facts, instead of guesswork or opinion. The proper identification of the exact root cause of a problem is critical because otherwise, your CAPA plan will fail to fix real problems.

Not all formal training needs to be in-person. Face-to-face training can be supplemented with more cost-effective training of concepts using webinars and recorded presentations. Interactive training is needed to supplement this training so that students can practice what they learn.

How Training Solves Common CAPA Deficiencies

The four most common CAPA deficiencies are:

Inadequate procedures
Incomplete investigations
Overdue actions, and
Failure to perform an effectiveness check

Each of these deficiencies is addressed directly by CAPA training. Formal CAPA training reviews each of the requirements for your CAPA process, and trainers will often share samples of CAPA procedures, and CAPA forms that they wrote and found to be effective. Learning multiple root cause investigation techniques, and practicing them using the case study technique, ensure that CAPAs are thoroughly investigated, rather than identifying superficial symptoms.

CAPA metrics are introduced during training to ensure that the CAPA process owner knows best practices for monitoring and analyzing the process. Finally, CAPA training includes specific examples of what is and what is not, a proper technique for performing an effectiveness check.

Results After Formal CAPA Training

The best reason for making formal CAPA training available to the people responsible for CAPAs are the results you will experience after the training. For example:

Elimination of hundreds of overdue CAPAs
Reduction in nonconformities, scrap, rework and customer complaints
Lower overall costs associated with quality problems
Better FDA inspection and Notified Body outcomes, and
Safer products for your customer

If you are interested in learning more about CAPA, click here to register for Medical Device Academy’s Risk-Based CAPA webinar.

Tags: CAPA, CAPA training, FDA 483

Posted in: CAPA, FDA

FDA Advice for Regulatory Submissions

Posted by Rob Packard on September 21, 2012

This blog reviews the importance of planning and communication with the FDA related to firms’ regulatory submissions. For the past two days, I was fortunate enough to attend a training seminar hosted by the FDA in Washington, DC. This was a “free” seminar (i.e., – travel expenses only). The session was split into two rooms. One room focused on drug regulations, and the other focused on device regulations. As my strength is a device, I spent most of my time listening to the speakers on the drug-side. Throughout the training, there was one common theme that was repeated by the speakers: Come Early, Be Loud, and Stay Late.

“Come Early”

The speakers recommend that companies plan their submissions well in advance and talk to the appropriate FDA project manager about their plans before starting clinical studies.

“Be Loud”

The speakers recommend that companies communicate with as many people as they can at FDA to ensure they have identified all the critical issues to address in the study design.

“Stay Late”

The speakers recommend that companies think ahead so that if (or when) things don’t go as planned, the clinical study results can be salvaged. In simple and more practical terms, every speaker emphasized the importance and value of consulting with the FDA, instead of guessing what type of data will be needed for submission. One of the other participants brought this up at lunch on the first day. He mentioned an example where the FDA agreed with a company on specific data that would be required for acceptance of an NDA. The company did exactly what the FDA said, and then the FDA requested more data. He later described another case where the FDA specified data, and the company refused to comply—but the FDA granted approval. This other participant and I both agreed that most companies are afraid to ask the FDA for agreement on what data is required because the company may not like the FDA’s answer.

My personal belief is that the FDA is better at identifying what data will be required than most companies because they have a broader perspective than companies do. There will always be exceptions, but my recommendation is to ask FDA’s opinion whenever you have a question—just ensure you do your homework before you ask an inane question that is already in their guidance documents. I believe this advice also applies to every regulatory agency in the world.

Tags: FDA regulatory submissions

Posted in: FDA

How to request FDA Device Classification information – 513(g) Alternative

Posted by Rob Packard on September 11, 2012

This blog provides a five-step process on how to request FDA device classification information. A screenshot of the FDA website for each step is included.

If your company is currently registering with the US FDA, you are probably reviewing the guidance document this month for the FY2013 user fees. On pages six and seven, there is a table of these fees, but you might have overlooked 513(g). Section 513(g) is a provision in the law that allows companies to request device classification information from the FDA.

For example, if your company was developing a new product, and you were having difficulty identifying the regulatory pathway, 513(g) is your friend. In my opinion, these fees are modest: $5,061 = Standard Fee, and $2,530 = Small Business Fee (updated for FY 2022). Most consultants will charge at least ten hours of consulting to identify the regulatory pathway for a company. I would charge quite a bit less because it takes me a lot less than ten hours. I still think the FDA’s pricing is a good deal because getting information directly from the source is always more valuable than an “expert.”

The US FDA has published a guidance document explaining the process for 513(g) requests. This guidance document was released on April 6, 2012 (updated in 2019). The guidance explains what information companies need to provide in order to submit a 513(g) request. The guidance also has a fantastic list of FDA resources on page five. These are the very same resources that the “experts” use—including yours truly.

Just as any good lawyer tries to avoid asking questions that they don’t already know the answer to, I recommend that you first try using these resources yourself. Once you think you know the answer, your request for classification information will be easier to organize.

Here’s how I would proceed to request FDA device classification information:

Step 1 – Are there similar devices on the market?

Identify another device similar to yours. If you can’t do this, you need serious help. You need a similar device that is already sold on the market to use as a predicate device. If you cannot identify a predicate, then you can’t use the 510(k) process—or you don’t know your competition. Either way, there are challenges to overcome. For example, if you are trying to launch a new topical adhesive made from cyanoacrylate—”Dermabond” might be the first predicate device that comes to mind.

Step 2 – Search the Registration Database for FDA Device Classification

Use the registration and listing database on the FDA website to find the company that manufacturers the device. The link for this is #4 on my helpful links page (updated). This link also will provide you with connections to the classification database—which you can use to find the classification for any device. However, the registration and listing database is less likely to lead you astray. When I type “Dermabond” into the field for the proprietary device name, I get a list of five different product listings.

Step 3 – Select one of the competitor links to identify the FDA Device Classification

Clicking on any one of these five will take you to a listing page for the corresponding company. On that page, you will find the three-letter product code that identifies the device classification and the applicable regulations for that device.

Step 4 – Your found the FDA Device Classification

Clicking on the three-letter product code (i.e., – “MPN” in our Dermabond example) takes you to the Product Classification page. This is where you will find that Dermabond, and other tissue adhesives, are Class II devices that require a 510(k) submission. Also, the Product Classification page identifies an applicable guidance document to follow for design verification and validation testing. This is also called the “Special Controls Document.”

Step 5 – TheTPLC Report lists all the recent 510(k) submissions

Click on the “TPLC Product Code Report” link. This link will provide you with a report of all the 510(k) ‘s recently granted to your competitors, problems customers have experienced with their products, and recalls for the past five years. This is extremely valuable information as a design input—as well as competitive information for your marketing team.

tplc total product life cycle report for mpn How to request FDA Device Classification information 513(g) Alternative

TPLC Report for Product Code “MPN” – Topical Adhesive

Tags: Device Classification, FDA

Posted in: FDA

10 FDA Inspection Strategies that DON’T Work

Posted by Rob Packard on August 30, 2012

If you were just notified of an FDA inspection and you don’t think you are ready, using tricks to hide your problems is a huge mistake. I have heard a few recommendations over the years for “secrets” to hide those problems. In this post, I share my favorite “secrets”–and why they DON’T work.

Here are my top 10 ways to make an FDA inspection worse:

10. Stalling when the investigator makes a request – This just irritates investigators. At best, the investigator will use the waiting time to identify additional documents to sample or to review the information you have provided more closely. At worst, the investigator will accuse the company of not cooperating with the inspection, and the investigator may return the following week with several more team members to help them. Whenever this occurred during a third-party audit that I conducted, I would move onto another area and interview someone. However, before I left the person that was slow to respond, I provided the person with a list of documents and records that I expected to be waiting for me upon my return. In extreme cases, I had to bluntly tell the management representative that I needed documentation more quickly. As an instructor, I teach auditors techniques for coping with this tactic.

9. Suggesting records for the investigator to sample – This is specifically forbidden in the case of third-party inspections and audits. The FDA has work instructions for identifying sample sizes, and samples are supposed to be selected randomly. In reality, samples are rarely random, and usually, the investigator is following a trail to a specific lot, part number, etc. When clients offered me samples, I tried to be polite and review the record they provided. However, I also would request several other records or follow a trail, as I have indicated above. Another approach I often use is to focus on high-risk items (i.e., – a risk-based approach to sampling). In general, you can expect the FDA investigators to sample more items than a registrar–and sample sizes are often statistically derived if the number of records is sufficiently large. When sample sizes are quite small, I recommend sampling 100% of the records since the previous inspection/audit. This is not always possible for third-party auditors, but internal auditors often can achieve this.

8. Outsourcing processes to subcontractors – The FDA recently reinstated the requirement for contract manufacturers and contract sterilizers to be registered with the FDA by October 1, 2012. Therefore, hiding manufacturing problems from the FDA by outsourcing manufacturing is increasingly more difficult to do. In addition, the FDA focuses heavily on supplier controls and validation of outsourced processes. Therefore, an investigator will identify high-risk processes performed by subcontractors and request documentation of process validation by that supplier. If the company does not have the validation reports, this could quickly escalate to a 483, and possibly a visit to the subcontractor.

7. Trying to correct problems during the inspection – This is what I like to call the document creation department. At one company I worked for, we noticed a mistake across several of the procedures and made a change overnight between the first and second days of the audit. When the auditor asked for the procedures in the morning, he asked, “Is the ink dry yet?” The auditor then proceeded to request records that demonstrated compliance with the newly minted procedures. As you might have guessed, this resulted in several nonconformities. When clients attempt to correct problems found by an investigator, the investigator typically will respond with the following statement, “I applaud you for taking immediate action to contain and correct the problem. However, you still need to perform an investigation of the root cause and develop a corrective action plan to prevent a recurrence. To do this investigation properly may take several days.” I also teach auditors to memorize this phrase.

6. Writing a letter to file – When companies make minor design changes, one of the most common approaches is to “write a letter to file.” This phrase indicates that the design team is adding a memo to the Design History File (DHF) that justifies why design validation is not required or why regulatory notification/approval is not required. The FDA used to publish a decision tree to help companies make these decisions. In fact, such a decision tree is still part of the Canadian significant change document. The FDA recently withdrew a draft document that eliminated many perceived opportunities to utilize the “letter to file” approach. However, the FDA will still issue a 483 to a company if the investigator can identify a change that required validation that was not done, or a 510(k) that was not submitted for a design change. In fact, the FDA looks explicitly for these types of issues when an investigator is doing a “for cause” inspection after a recall or patient death.

5. Shut it down – Not running a production line that has problems is an ideal strategy for hiding problems. However, the FDA and auditors will simply be forced to spend more time sampling and reviewing records of the problematic production line. If you need to shut a line down, ensure everything is identified as nonconforming, and carefully segregate rejected product from good product. You should also use these problem lines as an opportunity to show off your investigation skills and your ability to initiate CAPAs. If you simply forgot to validate a piece of equipment, or do some maintenance, take your lumps and keep production running. If you are a contract manufacturer, never shut it down without notifying the customer. If you do not tell your customer, you will get a complaint related to on-time delivery and a 483.

4. Storing all records off-site – I first heard about this tactic during an auditor course I was co-teaching. During the course, we had many reasons why the company should be able to provide the records in a timely manner. However, I have experienced this first-hand as a third-party auditor. When this happens, I do three things: 1) increase my sampling of records that are available, 2) carefully review supplier controls and supplier evaluation of the storage facility (assuming it is outsourced), and 3) verify that the company has a systematic means for tracking the location (i.e., – pallet and box) for every record sent to storage. FDA investigators will simply move along to another record and follow-up on their earlier request with a second visit, or a request to send a copy of the document to them after the inspection.

3. Identifying information as confidential – A company can claim information is confidential and may not be shared with the public. Still, very little information is “confidential” concerning the FDA or Notified Bodies. Therefore, this strategy rarely works. In fact, this will enrage most FDA investigators. In training courses, I train auditors to ask the auditee to redact confidential information. For example, a CAPA log may have confidential information in the descriptions, but the trend data on opening and closing dates are never confidential.

2. The FDA is not allowed to look at those records – Although this statement is technically true for internal audit reports and management reviews, the FDA always says that they can access this information through the CAPA system. What the FDA means is that there should always be evidence of CAPAs from internal audits and management reviews. If there is not, then this will quickly become a 483. Another person I met tells the story that when they agreed to share the management review records with the investigator, the inspector rarely issued a 483. When they refused to share the management review with the FDA, the inspection went quite badly from that point forth. I don’t agree with being vindictive, but it happens.

1. Show me where that is required – This is just silly. Investigators and auditors are trained on the regulations, while you are educated on your procedures. Spend your time and effort, figuring out how your procedures meet the regulations in some way. Challenging the investigator excites the investigator. We all like a challenge–and we rarely lose. One auditee tried this approach with me in front of their CEO. This experience allowed me to show off that I had memorized the clause in question–and the corresponding guidance document sections. I think the CEO realized quickly that the management representative was not qualified.

My final advice is to do your best to help the investigator do their job, and treat every 483 as “just an opportunity to improve.” Just ensure you submit a response in 14 days, or you will receive a Warning Letter too!

Tags: FDA inspection

Posted in: FDA

But What About FDA Regulations?

Posted by Rob Packard on June 1, 2011

The author writes that when you are auditing, you should always read the FDA regulations again to ensure accuracy.

I hear this question, or a question with similar wording, quite frequently when I am auditing. Typically, the question is in response to a better way to do something that seems simple and efficient. Most people seem to approach regulatory requirements with the approach of…let’s bury the regulator in paperwork. While it’s true that auditors expect a certain amount of paperwork with each regulatory requirement, they frequently accept a broader range of documentation than people realize (i.e., one page can be enough).

For example, a design control procedure could be a one-page flowchart that references forms and work instructions, or twelve separate documents, with a minimum length of ten pages and a maximum of forty pages per document. As long as the procedure has sufficient detail for personnel performing these tasks, and all the required elements are included, ISO clauses 7.3.1-7.3.7. An auditor should identify the process as conforming.

However, some people are FDA inspectors looking for NONCONFORMITY!

In the case of inspectors, it is critical to present your information in such a way that it is easy for the inspector to see how you meet the requirements of the regulations. One of the best ways to do that is to reference the requirements directly in your procedures.

For those that prefer finesse try to organize information following the regulations. For example, if I am writing a procedure for an ISO registration audit, I write the procedure to specifically address the ISO sub-clauses. I might even use a document control number like SOP-73 for my “Design and Development” procedure.

In my previous blog posting, http://bit.ly/AuditHours, I suggested a slight change to the scheduling of internal audits. To ensure this meets FDA requirements, the key is to READ THE REGULATIONS AGAIN. Concerning internal auditing, the applicable FDA regulation is 21 CFR 820.22:

“Each manufacturer shall establish procedures for quality audits and conduct such audits to assure that the quality system is in compliance with the established quality system requirements and to determine the effectiveness of the quality system. Quality audits shall be conducted by individuals who do not have direct responsibility for the matters being audited. Corrective action (s), including a reaudit of deficient matters, shall be taken when necessary. A report of the results of each quality audit, and reaudit(s) where taken, shall be made and such reports shall be reviewed by management having responsibility for the matters audited. The dates and results of quality audits and reaudits shall be documented.”

The above requirement is quite vague concerning how many auditors and how many days must be spent auditing. These are the variables I suggested changing in my previous blog http://bit.ly/AuditHours. The FDA regulation 21 CFR 820.22 is specific, however, with regard to documenting the “reaudit” of any deficiencies found during an audit. This prescriptive requirement can be met by reviewing previous audit findings of all audits with the audit program manager during the audit preparation process. The audit program manager can facilitate the assignment of which auditor will reaudit each discovery. This may require a few more minutes of audit preparation, but this should not measurably impact the overall time allocated to an audit.

I do this out of habit when I am performing internal audits on behalf of clients, but if I am auditing the internal audit process of a client—now I’ll remember to point out this additional requirement that is specific to the FDA and not included in the ISO Standard. This is why we should always READ THE REGULATIONS AGAIN.

Tags: auditing, FDA regulations

Posted in: FDA