03.11.2014 Views

Anaphylaxis in Schools 3rd Edition

Anaphylaxis in Schools 3rd Edition

Anaphylaxis in Schools 3rd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

child/school with an ep<strong>in</strong>ephr<strong>in</strong>e auto-<strong>in</strong>jector which is not expired (parents should keep a log of<br />

expiry dates and replace outdated auto-<strong>in</strong>jectors).<br />

• Should complete an <strong>Anaphylaxis</strong> Emergency Plan which has the child’s photograph and allergy<br />

<strong>in</strong>formation, emergency contact numbers, emergency protocol, signature of a parent/guardian and, if<br />

required, the signature of the child’s physician. (See Appendix D.)<br />

• Should provide consent which allows school staff to use an ep<strong>in</strong>ephr<strong>in</strong>e auto-<strong>in</strong>jector when they<br />

consider it necessary <strong>in</strong> an allergic emergency.<br />

• Should not sign a waiver absolv<strong>in</strong>g the school of responsibility if ep<strong>in</strong>ephr<strong>in</strong>e was not <strong>in</strong>jected.<br />

• For food-allergic children, should provide non-perishable foods (<strong>in</strong> case child’s lunch is forgotten at<br />

home) and safe snacks for special occasions.<br />

• Should communicate with school staff about field trip arrangements.<br />

• Should meet with foodservice staff to <strong>in</strong>quire about allergen management policies and menu items,<br />

if their child is to eat foods prepared at the school.<br />

Consensus Statement<br />

Children at Risk<br />

Allergic children who have been diagnosed as be<strong>in</strong>g at risk of anaphylaxis should:<br />

• Have an auto-<strong>in</strong>jector with their name on it, kept <strong>in</strong> a readily accessible location which is unlocked.<br />

• Carry their own auto-<strong>in</strong>jector when age appropriate, usually by the age of 6 or 7.<br />

• Refra<strong>in</strong> from eat<strong>in</strong>g if they do not have an auto-<strong>in</strong>jector with them.<br />

• Be very cautious about eat<strong>in</strong>g foods prepared by others.<br />

• Not share foods or utensils.<br />

• Wash hands with soap and water before and after meals.<br />

• Wear medical identification, such as a MedicAlert ® bracelet which clearly identifies their allergy, or a<br />

special badge <strong>in</strong> the case of very young children <strong>in</strong> the nursery sett<strong>in</strong>g.<br />

• Inform someone (preferably an adult) immediately after accidental exposure to an allergen or as<br />

soon as symptoms occur.<br />

School Community<br />

• All school staff should be aware of children who have an allergy that may trigger an anaphylactic<br />

reaction and be prepared to treat them <strong>in</strong> accordance with the emergency protocol. Information<br />

about children with life-threaten<strong>in</strong>g allergies should be readily available. Many teachers keep a<br />

copy of their students’ <strong>Anaphylaxis</strong> Emergency Plans <strong>in</strong> their “day book”; this is where important<br />

<strong>in</strong>formation is organized for substitute teachers.<br />

• School staff must consult with the parent before post<strong>in</strong>g the child’s plan. It should be kept <strong>in</strong> areas<br />

which are accessible to staff, while respect<strong>in</strong>g the privacy of the child (e.g. office, staff room, lunch<br />

room or cafeteria). Older children are often more reluctant to have their plan posted <strong>in</strong> the classroom<br />

where it is visible to all.<br />

<strong>Anaphylaxis</strong> <strong>in</strong> <strong>Schools</strong> & Other Sett<strong>in</strong>gs<br />

Copyright © 2005-2014 Canadian Society of Allergy and Cl<strong>in</strong>ical Immunology 17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!