Health Canada: Drug, Device and Natural Health Product Regulation

Health Canada is Canada’s federal health department. For manufacturers, its name identifies the institution—not a product’s regulatory status, a site’s authorised activities or the adequacy of a quality system.

This article addresses Canadian manufacturing and supply questions involving drugs, medical devices and natural health products. It does not extend those frameworks to every food, supplement, chemical or export market. Start with the product category, activity and destination rather than assuming that a familiar commercial label settles regulatory scope.

In operational practice, good manufacturing practice concerns manufacturing controls; a quality management system organises responsibilities, procedures and records. Device readers can explore the audit context through MDSAP; natural health product readers can distinguish product identification through the NPN glossary.

Optional operational controls—such as review checklists and evidence indexes—help teams apply these categories without becoming law themselves. Software can support that work; accountable people review evidence, approve decisions and release product.

Start with product classification, then identify the legal entity and proposed activity. The table is a manufacturer’s review aid: its questions help organise an applicability assessment, rather than establish licence eligibility or exemptions. Keep binding provisions, official guidance and internal review procedures separately labelled in that assessment.

For Canadian health products, Food and Drugs Act section 21.321 excludes natural health products from the meaning of therapeutic product specifically in sections 21.31 and 21.32. This is a provision-specific exclusion, not a product-wide exclusion from the Act.

For practical classification review, record intended use, composition and presentation together: does the proposed claim match the formulation and label? Then ask which legal entity will perform each proposed activity. For NHP terminology, see the NHPD glossary entry. Connect the assessment to regulatory change control so a changed claim, formulation, presentation or operating arrangement prompts review of the earlier scope decision.

At the cross-border checkpoint, assess Canadian questions separately from foreign-market documents included in the dossier. Identify each document’s jurisdiction and purpose before using it in a Canadian assessment. For example, keep UK MHRA context distinct from the Canadian review; foreign legal requirements are outside this article’s scope.

For Canadian drugs, check the current Food and Drug Regulations for submission-pathway applicability, product authorisation conditions and the treatment of proposed changes. Building on the authorisation distinctions above, organise the dossier around questions reviewers need to resolve. The matrix below is an illustrative working tool, not a prescribed submission checklist.

Keep separate fields for application reference, document revision, submission status, decision reference and authorised scope. Link each matrix entry to its supporting document and owner; record pending questions explicitly rather than allowing an application reference to stand in for a decision.

A practical handoff assigns technical owners to prepare controlled documents, regulatory reviewers to assess applicability, and designated humans to approve the submission package. Preserve the reviewed package as a defined revision set through document control.

Connect specification management with change control: when a formulation, label or manufacturing document changes after review, identify affected dossier entries, reconcile specifications and supporting studies, and route the revised package for renewed review before submission.

For Canadian drugs, check the current Food and Drug Regulations for Drug Establishment Licence (DEL) applicability, activity coverage, exemptions, drug GMP obligations and changes affecting an establishment’s scope. The following is an illustrative review method, not a statement of licence eligibility or a statutory checklist.

Build an activity register that keeps proposed work distinguishable from the current authorisation:

Assess controlled procedures, training evidence, equipment status, supplier records, quality agreements and batch documentation against the applicable obligations. Select evidence for the activity under review rather than treating these categories as universally mandatory documents.

Worked case: contract testing and a manufacturing change

Assume a Canadian drug batch uses contract testing and a manufacturing step is proposed for another site. Units of analysis are the batch and site activity. The draft testing request names the proposed site, but the quality agreement names the original site. The unresolved decision is whether the proposed arrangement can proceed within the applicable authorisation scope and quality arrangements.

1. Identify the mismatch in change control, linking the batch, affected site activity and testing request.
2. Preserve the affected records and version history, including the existing agreement and draft instructions.
3. Assign regulatory affairs the scope review. Assign supplier quality ownership of qualification evidence for the laboratory’s proposed work.
4. Have the agreement owner prepare revisions addressing sample transfer, methods, result approval and exception communication; reconcile them with controlled procedures and testing instructions.
5. Have quality review the resulting evidence through batch record review, recording missing information and dependencies.
6. Obtain an accountable human disposition identifying what remains unresolved and whether further action is needed before implementation; do not presume a licence outcome.

For Canadian medical devices, use the official Medical Devices Regulations as the regulatory reference. Check current operative provisions for applicability rather than assigning licence obligations from a product description alone. A practical review separates classification, device-licence applications, establishment activities, quality-system certificate questions, distribution records, complaint handling and incident reporting.

The following is a manufacturer-controlled review structure, not a statement that every record or licence applies to every device. Keep each decision attached to its own review object.

Treat MDSAP as a distinct audit-program topic. Check current Canadian programme applicability before drawing a licensing conclusion; do not substitute an audit record for the product and establishment scope review.

Worked case: product reference, unresolved importer scope

Assume an imported medical device has a product-authorisation reference, but the importer’s activity scope remains unresolved. The unit of analysis is the product–organisation–activity relationship, not the product reference alone. This example proposes an internal control, not a legal shipment rule.

1. Match the model and device identifier to the product reference, then match the importer’s legal identity and receiving site to the shipment records.
2. Record the unresolved question precisely: whether the proposed import activity falls within applicable establishment provisions and whether the organisation’s records address that scope.
3. Escalate to the regulatory owner. Document the applicable provisions, supporting records and conclusion rather than inferring permission from the product reference.
4. Document a human shipment decision: proceed if the review supports it, or retain the internal hold pending resolution. Link the decision to the shipment and distribution record.

For Canadian medical devices within its scope, section 52(1) requires manufacturers, importers and distributors each to maintain a distribution record for each device. In this case, connect device identifiers and destination records for traceability; UDI is a related identifier topic. Route complaints and incident signals to the post-market assessment process discussed below.

For Canadian natural health products, check the current Natural Health Products Regulations for product classification, product- and site-licence applicability, activity scope, responsible parties and GMP obligations. Keep the Act-level scope distinction above in view.

As an operational practice, assemble intended use, ingredient identity, formulation revision, label claims, responsible organisations and proposed site activities into a review record. These are review inputs, not a legal definition of an NHP.

Worked case: unchanged formula, changed claim and packager

Assume the formula is unchanged, a label claim is revised and the contract packager changes. The units of analysis are product revision and site activity. A practical review separates the questions:

• Product revision: identify affected artwork, claim-support documents, product specifications and licence records. Assign regulatory affairs to assess applicable Canadian provisions and quality to reconcile revision links. Use a focused label-claim review; unchanged composition alone does not resolve the change decision.
• Site activity: identify the proposed packaging location, activity description, contract, packaging instructions and site-licence records. Assign supplier quality and regulatory affairs to assess the Canadian provisions relevant to that organisation and activity. Connect the contract-manufacturing handoff to technology transfer records.
• Decision: record each assessment, reviewer, rationale and affected document revision before implementation. Determine whether a new licence or amendment is necessary from the applicable provisions; do not presume the outcome.

For Canadian NHPs, section 86(1) prohibits sale unless labelling and packaging accord with the Regulations. Operationally, linking new artwork to an old product revision can conceal an unreviewed claim; attaching packaging evidence to the wrong site can misdirect the packager assessment. Label control and site-specific evidence links address different risks.

Use this illustrative manufacturer-controlled workflow to connect the product-specific reviews above. It is an operational design recommendation, not a prescribed Canadian regulatory procedure. Assign an accountable owner at each handoff; unresolved questions return to that owner rather than disappearing between departments.

For example, assume a manufacturer revises a product’s formulation. Link that product revision to the corresponding specification revision, the manufacturing activity at the applicable site, a supporting batch record, and the approval decision. The change owner identifies affected relationships; the approver evaluates whether the linked evidence supports the proposed revision.

Record existence is not record relevance. A completed record for another product, superseded revision or different site activity may not support the decision at hand. Check product identity, revision, scope and decision date together. Preserve the evidence versions considered at that date, rather than silently replacing them with current documents.

Connect change control and audit trail review to these relationships: identify who changed a link, what changed, why, and whether the decision needs reconsideration. Humans remain responsible for approval and release decisions.

Read the accompanying workflow diagram as an illustrative operational sequence and the later data-model diagram as its record structure. Neither represents a mandated Canadian system.

A practical post-market workflow keeps the incoming complaint or safety signal, its assessment, the reporting decision and any corrective action as distinct, linked records. This is an operational design recommendation, not a statement of Canadian reporting requirements. For drug pharmacovigilance, retaining the original account separately helps reviewers distinguish reported facts from later interpretations.

Proposed intake fields are: product identifier; lot or serial reference where relevant; event location; awareness date; event description; reporter contact; responsible assessor; and linked distribution information. Preserve the initial account and identify subsequent corrections or follow-up information rather than silently replacing it.

For Canadian drugs, medical devices and natural health products, assess reporting applicability separately against the relevant current framework. Check product category, the organisation’s role, event circumstances and applicable timing; do not use a shared deadline or universal reporting threshold. Record the basis for the adverse-event reporting decision and the reviewer responsible.

Turn uncertainty into a tracked assessment question: identify the missing fact, assign an owner, set a review point and name an escalation route to the responsible safety or regulatory reviewer. An incomplete account is not, by itself, a supported conclusion that no report is needed.

Keep the assessment decision separate from evidence that a communication was submitted or acknowledged; preserve both where relevant. Hand off suspected quality defects to quality investigation, systemic causes to corrective and preventive action (CAPA), and potentially affected stock to recall-readiness review. Linked distribution records and lot genealogy help scope that review without predetermining the recall decision. Assign ownership at each handoff so referral does not become silent closure.

For a manufacturer managing Canadian-market products, the following is an illustrative integration design, not a statement of Health Canada requirements. Before exchanging data, assign owners: master-data stewards for product identifiers, regulatory staff for legal entities and authorisation references, site management for activity mappings, and document control for revisions. Link each reference to its authoritative record.

Enterprise resource planning can hold product and transaction references; laboratory systems, test evidence; quality systems, assessments and actions; and controlled-document repositories, approved versions. Shared identifiers connect these roles without making every system authoritative for every field. Material master data controls address mismatched product identifiers before evidence becomes attached to the wrong product.

Recover the relationship, then reassess its consequences

Example exceptions include stale authorisation references, duplicate event records, missing attachments and an interface failure after a source record changes. Use a controlled recovery sequence:

1. Isolate the exception and flag dependent records for review.
2. Retain the source record and its change history.
3. Determine which assessments, approvals or other decisions used the affected relationship.
4. Reconcile identifiers, document versions, attachments and duplicate links against authoritative records.
5. Obtain accountable approval of the correction.
6. Verify the renewed handoff at the receiving system, including completeness and duplicate handling.

Data integrity depends on preserving original and corrected relationships, with reasons and approvers. In ERP integration reconciliation, distinguish successful transmission from correct receiving-system content. Keep reconciliation status separate from the substantive regulatory or quality decision: repairing a link does not approve the evidence it connects.

Software can organise this proposed workflow, but the manufacturer retains accountable human review and approval; a system status is not a compliance certification.

Illustrative data model: Product ↔ Legal entity/site/activity ↔ Authorisation reference; Product ↔ Transaction/test evidence ↔ Assessment/action ↔ Approved document revision.

These are illustrative readiness failure modes, not a ranking of Health Canada findings or claims about inspection frequency. The controls below are proposed industry-practice checks for manufacturers, not legal requirements or official guidance.

Implementation checklist

• Confirm product and activity scope against the applicability assessment.
• Assign accountable owners, including responsibility for external handoffs.
• Reconcile current references through document control, rather than trusting saved links.
• Test evidence retrieval with someone other than the record author; this makes inspection readiness observable.
• Inspect unresolved exceptions through deviation management; use root-cause analysis for recurring handoff failures rather than repeatedly replacing missing files.
• Document the review decision, remaining restrictions, responsible reviewer and follow-up actions.

Rehearse exception recovery

Use a simulated broken supplier-document link for an affected product. Follow the product to its responsible organisation, assigned activity, expected evidence and recorded decision. Ask the owner to recover the correct revision, preserve the broken-link history and assess which decisions relied on it. If recovery changes a system mapping, route that change through change control. Have a human reviewer approve the reconciliation and record whether the earlier decision stands or needs reassessment. Capture retrieval obstacles and unresolved questions as rehearsal results, without predicting an inspection outcome.

Use these proposed operational measures to direct decisions across Canadian product portfolios, not to score compliance. Link scope uncertainties to the quality risk register. Targets and escalation thresholds remain organisation-defined.

For each population, report counts and ageing. Choose elapsed business time from the recorded opening date, using a documented business calendar; retain that date through reassignment. Define stale-reference criteria before counting.

Compare inflow, completed reviews and remaining work over the same period and scope. Rising intake with stable completion and ageing suggests demand pressure; falling completions and older remaining work suggest resolution problems. Review decision-pending cases separately so completed reviews do not conceal unresolved decisions.

At management review, ask: which unresolved item could change the product, activity or decision scope, who owns it, and what evidence would resolve it?