OmniPod DASH Guide De L'utilisateur page 152

Understanding PDM and Pod Function 12
When the PDM cannot communicate with the Pod
When the PDM attempts to communicate with an active Pod that is in range,
communication usually occurs quickly.
The PDM cannot communicate with the Pod when:
• The PDM is, or has temporarily been, too far from the Pod; for example,
when you attend a meeting, leaving your PDM back at your desk.
• The PDM's battery has run down.
• There is too much outside interference (see "Omnipod DASH™ System
Notice Concerning Interference" on page 182).
For information about handling PDM-Pod communication problems, see
"Communication Errors" on page 120.
Pod deactivation
Deactivation unpairs a PDM and Pod from each other. Deactivation:
• Stops the current Pod's insulin delivery.
• Permanently silences any alarms from that Pod.
• Frees the PDM to activate a new Pod.
Note: Deactivation does not occur automatically when the Pod expires or runs
out of insulin. In these situations, you must still use the PDM to deactivate the
current Pod before the PDM can activate a new Pod.
Discarding a Pod
When the PDM cannot resolve a communication error, the PDM is unable to
deactivate the Pod. In this situation, the PDM asks if you want to 'discard' the Pod.
'Discarding' unpairs the PDM from that Pod but does not stop the Pod's insulin
delivery. Therefore, if you tell the PDM to 'discard' a Pod, be sure to remove and
dispose of the old Pod before activating a new Pod. To prevent the 'discarded' Pod
from sounding an alarm at a later time, follow the instructions for silencing a Pod
alarm on page 122. Otherwise, if a discarded Pod sounds an alarm, the alarm
stops after 15 hours.
135
Effective Date: 18OCT2020, PCO-000235