Biosecurity

Biosecurity Plan:

As required by the Canadian Biosafety Standards, the University has developed a Biosecurity Plan that outlines physical, personnel, and pathogen control requirements, emergency response procedures, and provides guidance to ensure research using pathogens and toxins at Western is conducted in compliance with all rules and regulations that govern the use of biological agents and toxins. For more specific information, please see Biosecurity Requirements for Facilities using Biological Agents.

Frequently Asked Questions

What is biosecurity?

Biosecurity is measures that are designed to prevent the loss, theft, misuse, diversion, or intentional release of regulated materials (e.g. pathogens and toxins) and other related assets (e.g., personnel, equipment, non-infectious material, animals, and sensitive information).

Who is involved in biosecurity decisions?

The Biosafety Committee has representation from many areas on campus, including Western Special Constable Service, emergency response and research. The Committee meets regularly to discuss issues involving biological agents. Their role is to ensure that biological agents are used in a lawful manner and that the University meets the biosecurity requirements outlined by the Public Health Agency of Canada and the Canadian Food Inspection Agency.

What are the biosecurity requirements at Western?

All Faculty, Staff and Students working in biological laboratories need to follow the Biosecurity Requirements Using Biological Agents document, which requires measures such as labeling of samples, protecting samples locking them away, and accompanying visitors in the laboratory or facility.  There are additional requirements for laboratories using biological toxins. For example, there may limit the amount of a toxin that can be kept on hand.

Where do I get more information?

For more information, including additional details on Western’s Biosecurity Plan, please see Biosafety or contact the Biological Safety Officer at biosecurity@uwo.ca.

Published on  and maintained in Cascade CMS.