V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryMDSAP
Compliance · The complete guide

MDSAP: Medical Device Single Audit Program Explained

In short

Understand the program’s scope, participating authorities, and practical connections between audit evidence, quality-system processes and medical device reporting.

4,166 words · ~19 min read
MDSAP: an auditor and a quality manager in cleanroom garments review records on a tablet beside a device assembly line
MDSAP lets one recognised audit cover the QMS requirements of several participating regulators.
On this page
  1. 01What MDSAP is—and what its audit scope means
  2. 02Why manufacturers use MDSAP: reuse evidence without losing scope
  3. 03Participating authorities: members, observers and affiliates
  4. 04Auditing Organizations: recognition and engagement checks
  5. 05MDSAP, ISO 13485 certification and FDA inspection compared
  6. 06Map quality-system evidence to sites, processes and reporting
  7. 07A practical lifecycle from scope agreement to follow-up
  8. 08US regulatory mapping: Part 820 and device reporting duties
  9. 09Evidence failure modes and controls that address them
  10. 10Readiness metrics: coverage, unresolved links and transfer exceptions
  11. 11Implementation checklist and recovery when evidence transfers fail
  12. 12How V5 supports batch-record evidence—and where people decide
On this page · 12 sections
  1. 1What MDSAP is—and what its audit scope means
  2. 2Why manufacturers use MDSAP: reuse evidence without losing scope
  3. 3Participating authorities: members, observers and affiliates
  4. 4Auditing Organizations: recognition and engagement checks
  5. 5MDSAP, ISO 13485 certification and FDA inspection compared
  6. 6Map quality-system evidence to sites, processes and reporting
  7. 7A practical lifecycle from scope agreement to follow-up
  8. 8US regulatory mapping: Part 820 and device reporting duties
  9. 9Evidence failure modes and controls that address them
  10. 10Readiness metrics: coverage, unresolved links and transfer exceptions
  11. 11Implementation checklist and recovery when evidence transfers fail
  12. 12How V5 supports batch-record evidence—and where people decide
AI · Explain it for MY operation

How does MDSAP apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What MDSAP is—and what its audit scope means

MDSAP, the Medical Device Single Audit Program, allows a recognized Auditing Organization to conduct a single regulatory audit of a medical device manufacturer that satisfies the relevant requirements of participating regulatory authorities.

FDA’s program description has four elements that define how to read that promise:

  • Medical device manufacturer: the subject is device manufacturing, not pharmaceutical, supplement, food or chemical manufacturing generally.
  • Recognized Auditing Organization: recognition within MDSAP matters; the definition does not describe an audit performed by just any external auditor.
  • Single regulatory audit: the shared activity is an audit of the manufacturer, rather than a separate product-authorization decision.
  • Relevant participating-authority requirements: “relevant” bounds the scope. It should not be read as a statement covering every market or every activity.

For operational control, keep three questions separate in the manufacturer’s records. This is a practical distinction, not an additional MDSAP rule:

  • Audit evidence: what manufacturer activities and requirements did the audit address, and what did the report conclude?
  • Market access: what decision or status applies to this product in the intended jurisdiction?
  • Internal readiness: can the team retrieve the records, explain the process and resolve outstanding evidence gaps?

Use separate fields for these answers rather than a single “approved” status. Linking each field to its supporting record helps prevent an audit result from being used to answer a different question during medical device development.

See participating authorities for jurisdiction status and the comparison with certification and inspection for neighboring terms and FDA’s use of reports.

02Why manufacturers use MDSAP: reuse evidence without losing scope

For MDSAP preparation, a shared evidence register can help teams organize quality-system records without treating every manufacturing scope as identical. As an internal planning practice, map each record to the sites, device families and jurisdictions it supports. Use requirements traceability to keep those relationships explicit: a shared procedure may support several combinations, while implementation records may apply to only one. Reuse depends on actual scope and record quality; it does not promise fewer audit days, lower costs or fewer findings.

Worked example: assume two sites each manufacture four device families, creating eight applicable site–family combinations. Six combinations have their planned evidence sets linked; two do not. Planned evidence coverage is 6 ÷ 8 × 100 = 75%, leaving two combinations open. The units are site–family combinations—not devices, audit tasks or regulatory requirements.

The next action is to assign owners to the two open combinations and examine whether apparently shared records actually cover both sites. Linking a record is not the same as establishing its adequacy. See the readiness metrics section for interpretation; this calculation is neither a conformity determination nor an official sampling method.

03Participating authorities: members, observers and affiliates

FDA’s international-partner listing distinguishes MDSAP members, official observers and affiliate members. These are participation categories in the medical-device audit program. Use the map below to identify the relevant authority, then assess the intended product and market separately.

JurisdictionFDA-listed member authorityProduct and acceptance boundary
AustraliaTherapeutic Goods AdministrationMedical-device audit context; check current Australian rules for the device and intended use of the report.
BrazilBrazil’s Agência Nacional de Vigilância SanitáriaMedical-device audit context; assess the Brazilian device route separately. See ANVISA (Brazil).
CanadaHealth CanadaMedical-device audit context; confirm the applicable Canadian product classification and submission requirements.
JapanJapan’s Ministry of Health, Labour and Welfare and Pharmaceuticals and Medical Devices AgencyMedical-device audit context; check the Japanese route and report acceptance for the intended submission.
United StatesU.S. Food and Drug AdministrationMedical-device audit context; see the comparison section for FDA’s qualified use of reports and the EPRC boundary.

Official observers

  • European Union (EU).
  • Singapore’s Health Sciences Authority (HSA).
  • United Kingdom’s Medicines and Healthcare products Regulatory Agency (MHRA).
  • The World Health Organization (WHO) Prequalification of In Vitro Diagnostics (IVDs) Programme.

Keep the WHO entry under its specific programme name in a jurisdiction map rather than assigning it a country or treating it as a national regulator.

Affiliate members

  • Argentina’s National Administration of Drugs, Foods and Medical Devices (ANMAT); Ministry of Health of Israel.
  • Kenya’s Pharmacy and Poisons Board; Republic of Korea’s Ministry of Food and Drug Safety (MFDS).
  • Federal Commission for Protection from Sanitary Risks (COFEPRIS) of Mexico; South African Health Products Regulatory Authority (SAHPRA); Taiwan Food and Drug Administration (TFDA).

As a practical jurisdiction-mapping control, do not use participation status as evidence of identical product classifications, submission routes or audit-report acceptance. Consult current local rules for those decisions. Record the product, intended market, proposed report use and responsible reviewer before relying on the participation map for submission planning.

For the US mapping, continue to US quality-system and reporting obligations, where binding provisions are distinguished from FDA’s program description.

04Auditing Organizations: recognition and engagement checks

As defined above, the Auditing Organization conducts the single regulatory audit. Recognition is part of FDA’s program description, not merely a manufacturer’s designation of a preferred audit vendor.

Before agreeing an engagement, use these practical purchasing and scope-control checks—not an official mandatory checklist:

  • Check the organization’s current MDSAP recognition rather than relying on an earlier proposal.
  • Identify proposed sites and activities, including any exclusions.
  • Agree the device families covered and resolve ambiguous product boundaries.
  • Confirm jurisdiction coverage against the manufacturer’s intended markets.
  • Specify deliverables, recipients and expected delivery arrangements.
  • Agree follow-up contacts, responsibilities and how outstanding questions will be handled.

Record these agreements in the engagement scope so purchasing, quality and site teams work from the same expectations. Carry them into the implementation and review checklist.

For program documents, start at FDA’s MDSAP page. Its December 18, 2025 update directs readers to the new MDSAP website managed by Australia’s Therapeutic Goods Administration.

05MDSAP, ISO 13485 certification and FDA inspection compared

These activities produce different records for different purposes. Refer to the program’s scope definition when deciding what an MDSAP report can support; do not treat the four activities below as interchangeable.

TermMain question it addressesHow to use the resulting record
MDSAP regulatory auditDoes a single audit by a recognized Auditing Organization satisfy relevant requirements of participating regulators?Use the audit report within its scope and the receiving authority’s acceptance conditions.
ISO 13485 certificationIs the quality management system certified against the named ISO 13485 standard?Use the certification record for its stated QMS scope, not as an FDA inspection record.
FDA inspectionWhat does FDA examine through agency oversight?Use the inspection record to understand the agency’s documented observations and communications.
Internal readiness reviewWhere does the organization’s own gap assessment identify preparation needs?Use the assessment to assign actions and track unresolved gaps.

For certification-focused preparation, see ISO 13485 readiness. The comparison above is practical terminology, not a statement of equivalence.

FDA’s statement on audit-report use says FDA may continue to accept MDSAP audit reports as a substitute for routine Agency inspections. “May” makes acceptance conditional rather than assured; “routine” limits the stated substitution. This is FDA’s program guidance, not a blanket exemption from oversight.

Firms with relevant Electronic Product Radiation Control (EPRC) activities remain subject to FDA inspection for those activities.

06Map quality-system evidence to sites, processes and reporting

Build an internal evidence map around the agreed audit scope: sites, device families and processes. Connect controlled process descriptions to execution records, quality decisions, complaints and follow-up actions. This is a practical organization method—not official MDSAP audit-model chapters, an audit sequence or a sampling prescription. Select records relevant to the operations being reviewed; the suggestions below are not universal legal requirements.

Test one manufacturing-record chain

For a sampled manufacturing record, ask four retrieval questions:

  • Which site, device family and process does it cover?
  • Which procedure version governed the work when it occurred?
  • Which execution records demonstrate what actually happened?
  • How are exceptions connected to subsequent quality decisions, relevant complaints and follow-up actions?

Organize the register by relationships

The following field names are illustrative internal-register fields, not official MDSAP forms or V5 database fields. Use stable identifiers to connect entries rather than relying on filenames alone.

Record groupIllustrative fields
Scope recordsscope_id, site, device_family, process
Evidence artifactsartifact_id, scope_id, source_system, source_record_id, version
Findings and actionsfinding_id, artifact_id, action_owner, decision_id, closure_evidence
Reporting decisionsdecision_id, complaint_id, rationale, reviewer, report_reference
Transfer exceptionstransfer_id, artifact_id, destination_acknowledgment, exception_status, owner

For MES–QMS integration, retain the originating system and record identifier, relevant version, scope relationship and destination acknowledgment. Reconcile the acknowledgment to the intended artifact; a successful transfer message alone does not establish that the correct version arrived.

An accessible file answers “can we open it?” A traceable artifact also answers “where did it originate, and why does it apply here?” Record unresolved links explicitly rather than treating file availability as contextual completeness. Use the failure modes and controls to investigate incomplete chains.

A Linked Audit Evidence Register

Audit Scope

Identifies the manufacturing and jurisdiction boundary.

  • scope_id
  • site_id
  • device_family_id
  • jurisdiction
  • scope_version

Evidence Artifact

Preserves record origin, version and scope relationship.

  • evidence_id
  • scope_id
  • source_system
  • source_record_id
  • record_version

Finding and Action

Connects an observation to accountable follow-up.

  • finding_id
  • evidence_id
  • action_owner
  • due_date
  • effectiveness_review_status

Reporting Decision

Connects complaint assessment, timing and submission reference.

  • complaint_id
  • evidence_id
  • awareness_date
  • reporting_role
  • decision_rationale
  • report_due_date
  • submission_reference

Transfer exception

Supports reconciliation before a controlled retry.

  • message_id
  • source_record_id
  • destination_record_id
  • acknowledgment_status
  • retry_status
Illustrative internal fields, not official program forms or V5 database fields.

07A practical lifecycle from scope agreement to follow-up

Treat preparation and follow-up as an internal coordination cycle, not an official MDSAP timetable. Dates depend on the agreed engagement and applicable program arrangements; this workflow does not prescribe certification periods, surveillance intervals or a fixed preparation duration.

  1. Turn scope agreement into an evidence boundary. Identify the sites, device families, processes and responsibilities covered by the engagement. Assign contacts who can explain each area and retrieve its records. The handoff is a shared evidence map, not merely a booked audit date.
  2. Use readiness review to expose unresolved records. Ask process owners to retrieve and explain the mapped evidence. Record missing links, conflicting versions and unanswered questions in an audit management action list, with an owner and next step. Carry unresolved issues forward explicitly rather than treating document collection as readiness.
  3. Connect audit discussion to actual evidence. Route each question to the responsible person and relevant record. Track requests and responses so that a verbal explanation can be followed back to its supporting evidence, including any limitations or unresolved discrepancies.
  4. Convert follow-up into accountable action. Preserve the auditor’s finding separately from the manufacturer’s immediate correction, longer-term action and effectiveness review. Assign owners and define how they will test whether actions addressed the identified problem. Completing an action and demonstrating its effectiveness are separate review decisions.

Revisit the evidence map when sites, device families, processes or responsibilities change. Use the Auditing Organization engagement checks described above to resolve scope questions before carrying earlier assumptions into the next engagement. Make affected evidence ownership explicit at each handoff.

From scope agreement to follow-up
  1. 1
    Define scopeIdentify sites, device families, jurisdictions and organizational roles.
  2. 2
    Agree EngagementConfirm recognition, coverage, deliverables and follow-up arrangements.
  3. 3
    Map evidenceConnect source records to scope and responsible owners.
  4. 4
    Test retrievalTrace selected records and assign unresolved evidence gaps.
  5. 5
    Support AuditConnect questions to identifiable records and responsible personnel.
  6. 6
    Address FindingsSeparate observations, corrections, actions and effectiveness review.
  7. 7
    Maintain coverageReassess links when scope, processes or responsibilities change.
A practical preparation workflow, not an official audit timetable or prescribed sequence.

08US regulatory mapping: Part 820 and device reporting duties

US binding regulation

Start with scope. 21 CFR 820.1(a) says the Quality Management System Regulation governs "the methods used in, and the facilities and controls used for, the design, manufacture, packaging, labeling, storage, installation, and servicing of all finished devices intended for human use." It adds that manufacturers engaged in any of those activities must establish and maintain a quality management system appropriate for their specific devices, and names contract sterilizers, relabelers, remanufacturers, repackers, specification developers and certain initial distributors as examples of manufacturers subject to the part. Section 820.10(a) then requires such a manufacturer to document a quality management system that complies with the applicable requirements of ISO 13485, incorporated by reference, and the other applicable requirements of Part 820. Section 820.10(b) lists linked US obligations for specific ISO 13485 clauses: unique device identification under part 830, traceability under part 821 where applicable, complaint reporting under part 803, and advisory notices under part 806. These are the US legal duties an MDSAP audit report may be used to inform; the program itself does not replace them.

The requirements below are binding US regulations, not MDSAP program guidance. 21 CFR 820.10(b)(3)(3)) directs manufacturers to notify FDA of complaints meeting Part 803 reporting criteria. It references ISO 13485 Clause 8.2.3, “Reporting to regulatory authorities”; that reference is not an independent interpretation of the standard here. For related quality-system context, see FDA QMSR.

Reporting roleProvisionTiming or submission point
Manufacturer21 CFR 803.50(a)When this provision applies, report to FDA no later than 30 calendar days after the day of receipt or awareness of the specified information, from any source.
Importer: deaths or serious injuries21 CFR 803.40(a)Report to FDA, with a copy to the manufacturer, as soon as practicable and no later than 30 calendar days after the specified receipt or awareness.
Device user facility21 CFR 803.10(a)(1)Individual adverse-event reports: no later than 10 work days after the day of awareness of a reportable event. This is not the manufacturer deadline.

Under 21 CFR 803.11(a), manufacturers and importers must submit individual adverse-event reports to FDA electronically, in accordance with §§ 803.12(a) and 803.20, unless granted an exemption under § 803.19.

Under 21 CFR 803.56, when a manufacturer subsequently obtains required information omitted from its initial report because it was unknown or unavailable, it must submit that supplemental information to FDA within 30 calendar days of receiving it.

Worked case 2: a reporting-clock handoff

Assume a manufacturer’s event falls under the 30-calendar-day provision above, the legally established awareness date is Day 0, and internal routing occurs on Day 12. The interval from Day 12 to Day 30 is 30 − 12 = 18 calendar days, not a new 30-day period. This calculation assumes reportability and legal awareness; it does not determine either.

As an operational practice, connect the decision rationale and submission record to the quality-system evidence map described above. Include the complaint identifier, reporting role, awareness-date basis, responsible reviewer, submission date and any supplemental-information follow-up. This makes the handoff reviewable without treating an internal routing timestamp as the legal clock’s starting point.

These examples do not enumerate every Part 803 reporting trigger or report type; check its current text for applicable criteria and other deadlines. For other jurisdictions, assess current local product classification, market-access and reporting requirements separately.

09Evidence failure modes and controls that address them

These are illustrative preparation risks, not measured finding frequencies or official MDSAP classifications. Use them to test whether records remain understandable across sites, functions and systems.

Failure modeWhat becomes difficult to demonstratePractical control
A record assigned to the wrong site or device familyWhether the evidence concerns the audited operations or products.Use explicit site and device-family scope identifiers through production context tagging.
A procedure without an identifiable applicable versionWhich instructions governed the activity when it occurred.Use version-aware references that identify the procedure revision applicable to the recorded activity.
An exception disconnected from its dispositionHow the exception was evaluated and why its disposition followed.Link the exception, supporting records and decision record.
An internal complaint handoff without preserved datesWhen information arrived and how it moved between responsible functions.Retain original receipt and subsequent handoff dates alongside the responsible functions.
A transferred record without a matching destination identifierWhether the destination record corresponds to the source.Reconcile source-to-destination identifiers and investigate unmatched records.

A polished folder is not an explainable record chain. A reviewer should be able to identify what happened, which scope it concerns and how the decision followed from the records—not infer those connections from filenames or folder placement.

Keep action status separate from evidence of effectiveness. Assign someone to check the changed process against the intended result, rather than closing an item solely because a document was uploaded. Carry that check into follow-up in the operational lifecycle.

10Readiness metrics: coverage, unresolved links and transfer exceptions

Use these proposed management measures to expose gaps, not to assign MDSAP compliance scores or official acceptance thresholds. Fix the reporting period and scope before comparing results; retain the site–family boundaries used in the site–family coverage example.

MeasureDefinition and unit
Evidence-item completeness (per combination)For each applicable site–family combination: retrievable planned evidence items ÷ all planned evidence items × 100 (%).
Unresolved evidence linksCount of expected links still missing, broken or ambiguous at the review date; no denominator.
Source events without reconciled destination statusSource events without a matched destination record ÷ source events attempted in the period × 100 (%); include rejected and unacknowledged events.
Open actionsCount at the review date, grouped by accountable owner and internal due date; flag overdue actions separately. No denominator.

Worked case 3: assume an evidence interface attempts to transfer 12 source events. Nine have matched destination records, one is rejected and two lack acknowledgment. Reconciliation accounts for 9 + 1 + 2 = 12 events, but three remain unresolved: 3 ÷ 12 × 100 = 25%. One event is one transfer unit, not one device or complaint. Accounting for every event does not mean every transfer succeeded.

Track interface status separately from quality or regulatory review status. Technical transfer completion does not establish that evidence content or the underlying reporting decision is correct. Use management review to examine trends and recurring exception causes; set local escalation criteria rather than universal green, amber or red thresholds.

11Implementation checklist and recovery when evidence transfers fail

Use this internal preparation checklist to make the evidence map usable by reviewers. It supports preparation; it does not replace applicable audit arrangements or regulatory requirements.

Confirm scope, ownership and retrieval

  • Confirm the sites and device families included in the map.
  • Distinguish relevant jurisdictions and organizational roles rather than applying one undifferentiated requirements list.
  • Agree the engagement scope and record exclusions or questions needing clarification.
  • Name an evidence owner and authoritative source system for each record group.
  • Test record retrieval, including access permissions and the relationships needed to interpret records.
  • Identify unresolved decisions and assign follow-up owners.
  • Review site, product, process, system and responsibility changes before treating the map as current.

Connect records without obscuring their origins

Across manufacturing, document control, laboratory, quality and complaint systems, prefer durable record identifiers and explicit relationships over copied filenames or uncontrolled spreadsheets. For example, link a manufacturing record to its laboratory result and quality decision without making an export the authoritative source. Apply this architecture to manufacturing–quality integrations, with ownership defined at both ends.

Recover failed transfers deliberately

  1. Preserve the source event and transfer error.
  2. Determine whether the destination already holds the record before attempting another transfer.
  3. Correct mapping or validation problems.
  4. Use a duplicate-safe retry or controlled manual transfer.
  5. Reconcile source and destination identifiers and record counts; investigate discrepancies.
  6. Assign a reviewer to the resolved exception and retain the resolution record.

Finally, select a record that crosses manufacturing, quality review and, where applicable, an exception or complaint decision. Test whether a reviewer can follow those links and retrieve the underlying records. Record unresolved questions and owners instead of concealing gaps with a consolidated export. This is a practical data-integrity check, not a compliance score.

For the bounded software role, see V5’s batch-record support. Keep scope, reportability and audit-acceptance decisions separate from record assembly.

12How V5 supports batch-record evidence—and where people decide

V5 Ultimate assembles batch-record evidence from the work order, its steps and step executions, alongside lab samples, QC check results, equipment used, checklists, electronic signatures and deviations. This assembly combines the records of work execution with the listed laboratory, quality-control, equipment and review-related components in the batch record.

For MDSAP preparation, use that assembly as review material, not an approval. A practical operating model keeps responsibility with designated people: they determine which evidence applies to the audit scope, evaluate its quality, make reporting decisions, approve records and authorize product release. Reviewers should distinguish a record being present from its content supporting the decision at hand. For example, an included QC result still needs evaluation against the applicable acceptance criteria; its inclusion alone does not resolve a deviation or justify releasing the batch.

Frequently asked questions

Q.Does joining MDSAP authorize a device for sale in every member market?+

Do not treat participation as permission to sell. FDA describes MDSAP as allowing a recognized Auditing Organization to conduct a single regulatory audit addressing participating authorities’ relevant requirements, not as a market authorization mechanism. Keep audit planning separate from market-entry planning: identify the device, intended use, destination, and applicable authorization route before committing to distribution. A practical starting point is a market-by-market medical device classification assessment, with authorization status tracked separately from audit status.

Q.Can FDA still inspect activities at a site that has an MDSAP audit report?+

Yes. FDA’s MDSAP page says FDA may accept MDSAP reports as a substitute for routine Agency inspections; that wording is not an unconditional inspection exemption. It also expressly states that firms with Electronic Product Radiation Control activities remain subject to FDA inspections for those activities. For practical QA audit planning, identify those activities separately and assign owners for their records rather than assuming the MDSAP report addresses every activity at the establishment.

Q.Does being listed as an observer or affiliate establish the same report acceptance as membership?+

Do not infer identical acceptance from a listing. FDA’s participation list distinguishes members, official observers, and affiliate members; for example, it lists the United Kingdom’s MHRA as an official observer. For each destination, check the authority’s current instructions on whether and how an MDSAP report can support the relevant process. A practical acceptance matrix should record the authority, intended use of the report, conditions, and review date. Keep MHRA planning distinct from assumptions about member-market acceptance.

Q.What should a manufacturer check before engaging an Auditing Organization?+

First, check that the organization is recognized for MDSAP: FDA’s program description specifically identifies an MDSAP recognized Auditing Organization as the audit provider. Then, as procurement practice, agree the proposed sites, activities, device families, destination markets, deliverables, and responsibilities for resolving scope questions. Ask how scope changes and record-access problems will be handled. Capture those agreements in the engagement documentation and audit management plan rather than relying on a quotation that merely says “MDSAP audit.”

Q.Can records from one manufacturing site demonstrate [readiness](/glossary/iso-13485-readiness) for another site or device family?+

Not by themselves. As a preparation practice, distinguish shared procedures from evidence that a particular site or device family actually follows them. A central complaint procedure may be common, while training, equipment, production history, and local responsibilities differ. Build a requirements traceability map connecting each preparation topic to the relevant location, product scope, and records. Where evidence is reused, document why it applies and what local confirmation remains necessary; do not treat a matching template as proof of matching execution.

Q.Does routing a complaint to regulatory affairs later create a new [reporting period](/glossary/21-cfr-803)?+

No. For the manufacturer reporting obligation in 21 CFR 803.50(a)), the timing language is tied to receipt or awareness of information, not its later arrival in regulatory affairs. Internal forwarding should therefore preserve the original receipt and awareness dates rather than substitute a departmental intake date. As a practical control, connect complaint intake to adverse event reporting with a named reviewer, prompt escalation, and a documented assessment of the applicable reporting deadline.

Q.How should a team handle an [evidence-transfer exception](/glossary/mes-qms-integration) when the destination has not acknowledged the record?+

As an operational control, keep the transfer unresolved until receipt and usability are confirmed, or an authorized reviewer documents another disposition. Preserve the source record, transfer identifier, timestamps, destination, and error details in the audit trail. Assign an owner to investigate, check for duplicates before retrying, and confirm that attachments and signatures remain associated with the record. A successful send message alone should not be treated as proof that the receiving team can retrieve and review the evidence.

Q.Can a complete [electronic batch record](/glossary/electronic-batch-record) determine audit acceptance or authorize product release?+

No. Record completeness is an input to review, not an audit-acceptance decision or permission to release product. V5 Ultimate assembles batch records using work orders, step executions, QC check results, electronic signatures, and deviations. That support does not replace the people responsible for evaluating exceptions, approving records, and authorizing batch release. As a practical check, distinguish three workflow statuses: record assembled, record reviewed, and release authorized. Do not let the first status stand in for the other two.

Primary sources

  • FDA: Medical Device Single Audit Program (MDSAP)
  • 21 CFR Part 820
  • 21 CFR Part 803 Medical device reporting
Software that covers MDSAP
V5 Ultimate Medical Device MES
Device history records built from signed steps at the workstation: component lots, configured step order, inspections, UDI and…
V5 Ultimate eQMS Software
Document control, CAPA, deviations, change control, training and audits in one platform, with a rollout plan agreed with you.
V5 Ultimate QMS for Manufacturing
V5 keeps deviations, corrective actions, controlled documents and training on the same platform as your batches and equipment.…
V5 Ultimate Audit Management Software
Plan the audit schedule for the year. Run internal, supplier, and third-party audits from one inbox. Evidence is hash-chained.…

Explore this topic

MDSAP sits inside this topic cluster in our glossary. Every neighbour is one click away.

Medical Device Regulatory
29 related entries

Device-specific rules, submissions and the standards that bind them.

21 CFR 82021 CFR 803FDA QMSRISO 13485ISO 14971IEC 62366ISO 10993IEC 62304IEC 60601510(k)PMADe NovoEU MDRIVDRNotified BodyPredicate DeviceTechnical FileCE MarkingDesign ControlsDesign VerificationHuman FactorsPMSMedWatchCustomer ComplaintUDIDHReDHRDMRDHF
Talk to us about MDSAP

Want to see how MDSAP could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
Medical Devices
Inside V5
  • → Score your compliance gap — then download the validation pack.
  • → Document control — one version in force, every change signed and explained.
  • → QMS — quality records next to the work they concern.
Related terms
  • → EU MDR
  • → 21 CFR 820
  • → 21 CFR 803
  • → FDA QMSR
  • → ISO 13485
  • → ISO 14971
  • → IEC 62366
  • → ISO 10993
  • → IEC 62304
  • → IEC 60601
  • → 510(k)
  • → PMA
  • → De Novo
  • → IVDR
  • → Notified Body

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC