MDALL, MDEL, Recalls, and Safety Alerts: What Canadian Device Distributors Should Keep in the Product File

If your team distributes, imports, or onboards medical devices into the Canadian market, the supplier brochure or your internal SKU record is rarely enough on its own. Before ordering, reordering, or refreshing a product file, your team often wants a dated, source-backed record of what was checked in the public Health Canada surfaces — Medical Devices Active Licence Listing (MDALL), Medical Device Establishment Licence (MDEL), recalls, and safety alerts — together with the public-source gaps that warrant a supplier follow-up.

This article walks through what each Health Canada surface tells you, what to capture in the product file, and what supplier follow-up questions naturally fall out of the check.

Why a Canadian product file needs public-source evidence

If a customer, an auditor, a supplier-quality reviewer, or your own RA / QA reviewer asks what was checked on this device line, a dated public-source record is what you reach for. The record does not eliminate risk and does not authorize anything by itself. It shows which public sources were consulted, the search keys that were used, and what was visible on the searched-on date — so the qualified team can run their own review faster and with cleaner citations.

The check is most useful at predictable moments: before placing a purchase order on a new device line, before reordering a SKU after time has passed, during product onboarding, during periodic supplier review, when a customer asks for the regulatory evidence behind a device, before signing a distribution or sourcing agreement, or when refreshing the product file at a planned cadence.

MDALL — device-level licence evidence

The Medical Devices Active Licence Listing (MDALL) is Health Canada's licence-level surface. It is the relevant database for Class II, III, and IV medical devices, and it helps purchasers verify whether the manufacturer of a Class II / III / IV device holds an active medical device licence.

For each device line, the product-file record should capture:

• Device name and trade name as listed.
• Licence holder (legal entity).
• Licence number.
• Device class (II / III / IV).
• Licence status (active or otherwise).
• Searched-on date.
• Search keys used (manufacturer name, licence number, trade name, device-class filter).
• Source URL — the MDALL search surface.

Safe boundary. An MDALL match is not a final marketability determination. The licence holder named on the MDALL record may be the manufacturer or, in some cases, an authorized representative; the model or configuration your team is sourcing may differ from the device entry under the licence. The qualified RA / QA, regulatory, legal, supplier-quality, procurement, or responsible-person reviewer treats the MDALL record as one input, not as a sign-off.

MDEL — establishment-level evidence

The Medical Device Establishment Licence (MDEL) applies to certain Canadian importers and distributors and to manufacturers of Class I devices. MDEL is establishment-level, not product-level. A distributor must not treat an MDEL match as proof that a specific Class II / III / IV product is licensed — that proof comes from the MDALL record described above.

For each transaction, the product-file record should capture:

• MDEL holder name (legal entity).
• MDEL number.
• Activity type if surfaced (importer, distributor, Class I manufacturer).
• Status.
• Searched-on date.
• Whether the MDEL holder's role matches the role expected for this transaction (the importer of record may be a different legal entity from the distributor your team actually contracts with).

If the MDEL holder name on the public record does not match the entity that will physically import or distribute the device into Canada, that is itself a supplier follow-up question (see below) — not an automatic disqualifier.

Health Canada recalls and safety alerts

Health Canada publishes recalls and safety alerts centrally. For each device line in the product file, the check should sweep recalls and safety alerts for the manufacturer, the product family, and any closely related device line under the same licence holder.

A visible recall does not automatically mean the exact configuration or lot your team is purchasing is affected. Recalls scope to specific products, configurations, lots, or serial ranges; the public record names the scope, but matching that scope to the units arriving on your loading dock typically requires confirmation with the supplier. A surfaced recall therefore most often becomes a supplier follow-up question, not a stop-ship.

For each recall hit, the product-file record should capture:

• NID or recall identifier (where Health Canada exposes one).
• Posted date.
• Product / manufacturer named on the record.
• Hazard summary in Health Canada's published wording.
• Status (active or closed, where shown).
• Whether supplier confirmation is needed for the configuration or lot that the buyer would receive, and the question to ask.

Advisories, safety communications, and vigilance surfaces

Health Canada also publishes advisories and safety communications, and maintains a vigilance / incident-reporting surface for medical devices. The product-file record should note what was checked on these surfaces and what was — and was not — visible on the searched-on date.

The honest framing here matters more than the count. Public vigilance / incident-reporting surfaces have limitations and may not capture every device problem, supplier communication, or reportable event. Absence of a public record does not mean absence of risk. A clean vigilance result is a public-data observation on a specific date, not a clean bill of health.

What to keep in the product file

A practical, source-backed product-file record for one device line, on one searched-on date, generally includes:

• Product name (and trade name, if different).
• Manufacturer / licence holder name.
• Model / SKU / catalog number.
• Country (Canada, for this record).
• MDALL result — licence number, holder, trade name, device class, status, searched-on date, source URL.
• MDEL result where relevant — holder name, MDEL number, activity, status, role match, searched-on date, source URL.
• Recalls and safety alerts result — each row with NID, posted date, product / manufacturer, hazard summary, status, supplier-confirmation needed yes/no.
• Advisories result — each row with date and topic, or an explicit "none surfaced" with the searched-on date.
• Public-source gaps — what was searched, where the public surface is known to under-report (vigilance), and where the buyer's record-of-truth must come from the supplier rather than from a public database.
• Supplier follow-up questions — the list your team will email the manufacturer or distributor.
• Searched-on date for each surface.
• Source URLs — every page consulted.
• Reviewer name or analyst note.
• A verbatim limitation statement (see "What this record is not", below).

Supplier follow-up questions worth asking

The check usually surfaces a small set of questions for the supplier. Examples that often fall out:

• Please confirm the Health Canada medical device licence number for this product / model / configuration.
• Please confirm whether the model or SKU we are sourcing is covered by the licence record we found, or whether a different licence applies to this configuration.
• Please confirm whether recall NID [number] (posted [date]) affects the configuration, lot, or serial range we would receive.
• Please confirm whether there are any field corrections, advisories, or customer notices not yet visible in the Health Canada public record.
• Please confirm the Canadian importer or distributor of record for this transaction, and the corresponding MDEL holder.
• Please confirm the country of origin and any updates to the labelled compatible accessories list since the licence was last updated.

What this product-file record is not

• Not legal advice.
• Not a final regulatory classification.
• Not a final marketability determination.
• Not a safety guarantee.
• Not a compliance certificate.
• Not an import authorization.
• Not a substitute for the qualified RA / QA, regulatory, legal, supplier-quality, procurement, or responsible-person review at your organization. Final decisions remain with that qualified professional. The record's job is to organize the public evidence cleanly and surface the gaps; the decision is the customer's.

How TrueMedDevice fits in

The $199 Public Regulatory Status Snapshot for Canada is a single dated PDF, prepared by an analyst, scoped to one product, one company, Canada only, one dated report. Delivery is two business days. The deliverable includes what was checked, what matched, what did not clearly match, the visible red flags (with their Health Canada-published wording), the missing-or-uncertain section, the supplier follow-up questions, the source appendix with every URL and search key used, and the verbatim limitation statement.

The Snapshot is research and review support for your team. It does not replace your qualified reviewer.

Request the Canada illustrative sample or start a check

FAQ

Is MDALL the same as MDEL?

No. MDALL is the Medical Devices Active Licence Listing — a licence-level surface for Class II / III / IV devices, anchored to the manufacturer or licence holder. MDEL is the Medical Device Establishment Licence — an establishment-level surface that applies to Canadian importers and distributors, and to manufacturers of Class I devices. The two records answer different questions and should both appear in the product file when applicable.

Does an MDEL prove a specific product is licensed?

No. MDEL is establishment-level. A surfaced MDEL confirms that the named importer, distributor, or Class I manufacturer holds an active establishment licence — it does not confirm that any specific Class II / III / IV product is licensed. Product-level licensing for those classes is what MDALL surfaces. Treat MDEL and MDALL as complementary records, not interchangeable ones.

Does a visible Health Canada recall mean we cannot buy the product?

Not by itself. Recalls scope to specific configurations, lots, or serial ranges. A recall surfaced for the manufacturer or product family raises a supplier follow-up question — does this recall affect the configuration or lot our team would receive? — that the supplier can usually answer in writing. The qualified RA / QA, supplier-quality, or procurement reviewer decides whether to proceed, hold, or escalate.

What if no public recall or advisory appears for the device?

"No public record found" means no record surfaced under the search keys used on the searched-on date. It does not mean no event occurred, no risk is present, or that the supplier has nothing to disclose. Public databases lag; advisories and vigilance surfaces have known limitations. Note the absence on the dated record, ask the supplier whether anything is in flight that has not yet been published, and let the qualified reviewer take it from there.

Should this dated check be kept with the PO or with the product file?

Either, depending on how your team organizes evidence. Many distributors keep the dated record attached to the product file (so it persists across reorders) and link to it from the PO record. The point is that the dated record exists, is reproducible from its search keys and source URLs, and is retrievable when a customer, auditor, or internal reviewer asks what was checked.

Can TrueMedDevice run the check for one SKU?

Yes. The Canada Public Regulatory Status Snapshot is scoped to one product, one company, Canada only, one dated report at $199 per Snapshot. A different SKU, model, or country is a separate Snapshot. Reviewing the same device in both Canada and the US means two reports, with the boundary against mixing jurisdictions kept explicit.