eduKateSG · Why Science?
Follow one audit across several regulatory systems
Use FDA’s MDSAP resources through participating authorities, recognized Auditing Organizations, scope, process tasks, jurisdiction-specific requirements, findings, certificates and oversight.
Medical-device manufacturers often serve several countries, each with its own regulatory authority. The Medical Device Single Audit Program creates a shared audit approach so one recognized audit can address relevant quality-system requirements across participating jurisdictions.
FDA’s current MDSAP pages, procedures and forms show a carefully governed program. Recognized Auditing Organizations conduct audits, while participating authorities retain their own legal powers and decide how to use the resulting reports.
Did you know? “Single audit” does not mean “single law.” The audit model combines common process tasks with country-specific requirements, so the report must preserve which jurisdiction and requirement each conclusion addresses.
This guide supports audit and international-regulation literacy. It does not certify a manufacturer or replace an official audit.
Chapter index
Chapters 1–9: authorities, organizations and audit scope
- 1. MDSAP uses one coordinated audit program
- 2. Participating authorities remain sovereign
- 3. Auditing Organizations need recognition
- 4. The manufacturer defines a complete audit scope
- 5. The audit approach follows linked processes
- 6. Jurisdiction-specific requirements are included
- 7. Audit duration is calculated
- 8. Evidence comes from records and practice
- 9. Nonconformities are graded
Chapters 10–17: tasks, findings, certificates and follow-up
- 10. Immediate threats require escalation
- 11. The audit report preserves the route
- 12. Certificates have defined content
- 13. Surveillance supports continuing confidence
- 14. Unannounced or special audits can occur
- 15. Regulatory authorities can use reports differently
- 16. Current organization status should be checked
- 17. A complete MDSAP receipt keeps every boundary
A single audit becomes meaningful when its scope, authority, evidence and findings remain visible. A recognized Auditing Organization can conduct one regulatory audit designed to satisfy relevant requirements of participating authorities. This makes international cooperation inspectable.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about mdsap uses one coordinated audit program? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for mdsap uses one coordinated audit program. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for mdsap uses one coordinated audit program, its identifier or version context, and one limit that must remain visible.
MDSAP lets a recognized Auditing Organization assess requirements of participating regulatory authorities in one audit program. Australia, Brazil, Canada, Japan and the United States use MDSAP outputs under their own laws, policies and regulatory decisions. It also separates the auditor’s work from each authority’s legal powers.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about participating authorities remain sovereign? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for participating authorities remain sovereign. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for participating authorities remain sovereign, its identifier or version context, and one limit that must remain visible.
One audit route does not mean every country has identical law or identical regulatory decisions. Application, assessment, authorization and continuing oversight determine whether an organization can conduct recognized MDSAP audits. Consistent task sequences help evidence travel across borders.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about auditing organizations need recognition? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for auditing organizations need recognition. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for auditing organizations need recognition, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Define the actors
4. The manufacturer defines a complete audit scope
The report is strongest when sites, processes, jurisdictions and nonconformities can be traced. Legal manufacturer, sites, outsourced processes, device categories, activities and jurisdictions establish what the audit covers. A clear certificate never replaces the underlying audit scope and status.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about the manufacturer defines a complete audit scope? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for the manufacturer defines a complete audit scope. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for the manufacturer defines a complete audit scope, its identifier or version context, and one limit that must remain visible.
A single audit becomes meaningful when its scope, authority, evidence and findings remain visible. Management, measurement and improvement, design and development, production and service controls, purchasing and device-event reporting are examined through tasks. This makes international cooperation inspectable.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about the audit approach follows linked processes? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for the audit approach follows linked processes. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the audit approach follows linked processes, its identifier or version context, and one limit that must remain visible.
MDSAP lets a recognized Auditing Organization assess requirements of participating regulatory authorities in one audit program. Audit tasks point to participating authority requirements so a shared process can still identify different legal obligations. It also separates the auditor’s work from each authority’s legal powers.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about jurisdiction-specific requirements are included? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for jurisdiction-specific requirements are included. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for jurisdiction-specific requirements are included, its identifier or version context, and one limit that must remain visible.
One audit route does not mean every country has identical law or identical regulatory decisions. Site headcount, tasks, device risk, design responsibility, sterilization and other factors can affect planned audit time. Consistent task sequences help evidence travel across borders.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about audit duration is calculated? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for audit duration is calculated. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for audit duration is calculated, its identifier or version context, and one limit that must remain visible.
The report is strongest when sites, processes, jurisdictions and nonconformities can be traced. Auditors review procedures, records, interviews and observations to determine whether requirements are implemented effectively. A clear certificate never replaces the underlying audit scope and status.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about evidence comes from records and practice? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for evidence comes from records and practice. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for evidence comes from records and practice, its identifier or version context, and one limit that must remain visible.
A single audit becomes meaningful when its scope, authority, evidence and findings remain visible. The MDSAP grading system considers the quality-management-system clause and recurrence or escalation rules to express significance consistently. This makes international cooperation inspectable.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about nonconformities are graded? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for nonconformities are graded. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for nonconformities are graded, its identifier or version context, and one limit that must remain visible.
MDSAP lets a recognized Auditing Organization assess requirements of participating regulatory authorities in one audit program. Potential public-health threats or serious concerns can trigger prompt reporting to participating authorities under program procedures. It also separates the auditor’s work from each authority’s legal powers.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about immediate threats require escalation? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for immediate threats require escalation. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for immediate threats require escalation, its identifier or version context, and one limit that must remain visible.
One audit route does not mean every country has identical law or identical regulatory decisions. Scope, sites, products, tasks, evidence, findings and conclusions should allow regulators to understand what the audit established. Consistent task sequences help evidence travel across borders.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about the audit report preserves the route? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for the audit report preserves the route. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for the audit report preserves the route, its identifier or version context, and one limit that must remain visible.
The report is strongest when sites, processes, jurisdictions and nonconformities can be traced. Certification documents identify the organization, manufacturer, scope, sites, recognition statement and validity details. A clear certificate never replaces the underlying audit scope and status.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about certificates have defined content? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for certificates have defined content. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for certificates have defined content, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Track regulatory use
13. Surveillance supports continuing confidence
A single audit becomes meaningful when its scope, authority, evidence and findings remain visible. Initial certification is followed by surveillance and recertification activities rather than a one-time permanent status. This makes international cooperation inspectable.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about surveillance supports continuing confidence? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for surveillance supports continuing confidence. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for surveillance supports continuing confidence, its identifier or version context, and one limit that must remain visible.
MDSAP lets a recognized Auditing Organization assess requirements of participating regulatory authorities in one audit program. Program rules allow additional audit activity when concerns, changes or authority needs justify it. It also separates the auditor’s work from each authority’s legal powers.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about unannounced or special audits can occur? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for unannounced or special audits can occur. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for unannounced or special audits can occur, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Track regulatory use
15. Regulatory authorities can use reports differently
One audit route does not mean every country has identical law or identical regulatory decisions. FDA may consider MDSAP audit reports when planning oversight, but the program does not remove FDA inspection or enforcement authority. Consistent task sequences help evidence travel across borders.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about regulatory authorities can use reports differently? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for regulatory authorities can use reports differently. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for regulatory authorities can use reports differently, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Track regulatory use
16. Current organization status should be checked
The report is strongest when sites, processes, jurisdictions and nonconformities can be traced. Authorization, recognition, scope and availability can change, so the official list matters at the time an audit is arranged. A clear certificate never replaces the underlying audit scope and status.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about current organization status should be checked? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for current organization status should be checked. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for current organization status should be checked, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Track regulatory use
17. A complete MDSAP receipt keeps every boundary
A single audit becomes meaningful when its scope, authority, evidence and findings remain visible. Record manufacturer and sites, devices and activities, jurisdictions, audit type and dates, Auditing Organization status, team, duration, tasks, evidence, nonconformities, grading, corrections, certificate and regulatory follow-up. This makes international cooperation inspectable.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about a complete mdsap receipt keeps every boundary? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for a complete mdsap receipt keeps every boundary. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a complete mdsap receipt keeps every boundary, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
One audit is trustworthy when its full scope travels with the result
MDSAP shows how shared methods can reduce duplicated work without erasing legal differences. The practical reading skill is to keep the auditing organization, manufacturer sites, tasks, findings and participating authority requirements attached.
Save the current Auditing Organization authorization, manufacturer legal name, sites and outsourced processes, products and activities, participating jurisdictions, audit type and dates, duration calculation, team, sampled records, completed tasks, evidence, findings and grades, corrections and corrective actions, certificate scope and dates, special reporting and regulator follow-up.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Audit scope | Defines sites, products and jurisdictions | What is excluded? |
| Audit task | Connects process to requirements | Which authority requirement applies? |
| Nonconformity | Records unmet requirement and evidence | How was significance graded? |
| Certificate | Summarises recognized scope and status | Is it current and complete? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA MDSAP Overview — accessed 25 October 2026.
- FDA MDSAP Audit Procedures and Forms — accessed 25 October 2026.
- FDA MDSAP Assessment Procedures and Forms — accessed 25 October 2026.
- FDA Auditing Organization Availability — accessed 25 October 2026.
- FDA MDSAP International Regulations — accessed 25 October 2026.