CN108969888B - Wearable cardioverter defibrillator system using security tag to upload configuration data - Google Patents

Abstract

A Wearable Cardioverter Defibrillator (WCD) system configured to wirelessly exchange data with an access device distinct from the WCD system, the access device comprising a Near Field Communication (NFC) reader, a peripheral processor, and an Access Wireless Communication Module (AWCM).

Description

Wearable cardioverter defibrillator system using security tag to upload configuration data

Technical Field

The present invention relates to a cardioverter-defibrillator (WCD) system, and more particularly, to a wearable cardioverter-defibrillator (WCD) system.

Background

When a person suffers from some type of cardiac arrhythmia, the result may be a reduction in blood flow to various parts of the body. Some arrhythmias may even lead to Sudden Cardiac Arrest (SCA). SCA can lead to death very quickly, for example within 10 minutes, unless temporary treatment is performed.

Some people have an increased risk of SCA. High risk persons include patients with heart attacks or previous SCA attacks. These people are often advised to receive an Implantable Cardioverter Defibrillator (ICD). ICDs are surgically implanted in the chest and the patient's Electrocardiogram (ECG) is continuously monitored. If certain types of arrhythmias are detected, the ICD delivers a shock through the heart.

After considering the increased risk of SCA, and prior to receiving an ICD, these people are sometimes given a Wearable Cardioverter Defibrillator (WCD) system. (early versions of such systems were referred to as wearable cardiac defibrillator systems.) WCD systems typically included a harness, vest, or other garment that the patient would wear. The WCD system includes a defibrillator and electrodes coupled to a harness, vest, or other garment. The external electrodes may then make good electrical contact with the patient's skin when the patient wears the WCD system, and thus may help determine the patient's ECG. If a shockable arrhythmia is detected, the defibrillator passes the patient's body, and thus delivers an appropriate shock through the heart.

The WCD system may be in electronic communication with other devices. However, challenges may arise from inadvertent or even malicious communication, such as when the WCD system is programmed.

Disclosure of Invention

This specification presents examples of Wearable Cardioverter Defibrillator (WCD) systems, storage media and methods of storing programs, the use of which can help overcome problems and limitations of the prior art.

In an embodiment, a Wearable Cardioverter Defibrillator (WCD) system includes a processor, a memory, a wireless communication module (DWCM), and an NFC tag that stores information about how an access device can wirelessly access the DWCM. An access device, such as a defibrillator configurator with an NFC reader, may read the NFC tag of the WCD system (if it has sufficient permission to do so). After reading, the access device will know how to wirelessly address the DWCM, thus downloading from the operating installation or updated configuration data, software updates, or request memory. The use of NFC tags requires close proximity, which prevents inadvertent programming of the wrong WCD system, as well as malicious attack on the WCD system.

Other advantages include no need for manual input of connection data, and no need for a physical cable in all embodiments. The physical cables are for wired connections that require physical connection to the defibrillator configurator. This limits the configuration workflow due to physical limitations and the risk of tripping that occurs. Furthermore, manual entry of connection data is disadvantageous because it is safe and easy to use. Manually entering addresses and passwords presents a security concern because the addresses and passwords need to be in a human readable format, which may be inappropriately shared with others. In addition, the workflow of manually entering data is cumbersome and error prone.

Accordingly, the present invention is directed to an improved Wearable Cardioverter Defibrillator (WCD) system. In accordance with one embodiment of the invention, a Wearable Cardioverter Defibrillator (WCD) system configured to wirelessly exchange data with an access device different from the WCD system, the access device including a Near Field Communication (NFC) reader, a peripheral processor, and an Access Wireless Communication Module (AWCM), the WCD system comprising: a support structure configured to be worn by a patient; a power source; an energy storage module configured to be charged from the power source so as to store an electrical charge; a discharge circuit coupled to the energy storage module, the discharge circuit controllable to wear the support structure on the patient while discharging the stored charge through the patient; a defibrillator memory configured to store a program; a defibrillator processor; an NFC tag having a tag memory in which access data is stored, the NFC tag configured to receive a wireless interrogation wave from the NFC reader, the NFC tag further configured to wirelessly transmit a backscattered wave in response to the received interrogation wave reader, the backscattered wave encoding the access data, wherein the NFC reader of the access device is capable of receiving the backscattered wave, a peripheral processor of the access device is capable of generating verification data from the encoded access data, and the AWCM is capable of transmitting the verification data and configuration data; and a Defibrillator Wireless Communication Module (DWCM) cooperating with the defibrillator processor, the DWCM configured to wirelessly receive the verification data and configuration data transmitted by the AWCM, wherein: the defibrillator processor is configured to generate the received verification data to store the received configuration data in the defibrillator memory in response to determining that the backscattered encoded access data has been received from the memory; and the defibrillator processor thus becomes configured to run the stored program in accordance with the stored configuration data to generate a certain decision to shock or not shock, and to control the discharge circuit to discharge the charge in response to the certain decision to shock.

According to one embodiment of the invention, the access device is disposed in a peripheral housing; and is

The peripheral housing is at a distance of at most 10 "from the NFC tag when the NFC tag receives the wireless interrogation waves from the NFC reader and wirelessly transmits the backscattered waves.

According to one embodiment of the invention, the authentication data comprises access data or a hash of the access data.

According to one embodiment of the invention, the verification data includes a network address of the DWCM.

According to one embodiment of the invention, the backscattered encoded access data is encrypted.

According to an embodiment of the invention, the tag memory is further configured to store a tag password; and the NFC tag is further configured not to backscatter the encoded access data unless the interrogation wave also encodes the tag password.

In accordance with one embodiment of the invention, the WCD system has been assigned a sequence number: and the tag password is or is related to the serial number.

In accordance with one embodiment of the invention, the DWCM has been assigned a network address; and the DWCM does not transmit the network address in response to the AWCM's query signal.

In accordance with one embodiment of the present invention, the defibrillator memory further stores previous configuration data prior to receiving the verification data; and the defibrillator processor is configured to run the program in accordance with the stored configuration data to produce a decision to shock or not shock, and to control the discharge circuit to discharge the charge in response to the decision to shock.

In accordance with one embodiment of the invention, the received configuration data can be stored in the defibrillator memory only when it is received by the DWCM before the expiration of the timeout period after transmission of the backscatter wave.

In accordance with an embodiment of the present invention, the NFC tag is further configured to receive another wireless interrogation wave from another NFC reader, to decode updated tag data from the other wireless interrogation wave, and to store the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the NFC tag is further configured to receive another wireless interrogation wave from the NFC reader, to decode updated tag data from the other wireless interrogation wave, and to store the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the DWCM is further configured to wirelessly receive updated tag data from the AWCM; and the defibrillator processor is further configured to store the updated tag data in the tag memory in place of the access data.

According to an embodiment of the invention, the WCD system further comprises: a defibrillator housing, the defibrillator processor and the NFC tag being located within the defibrillator housing; and a service port in the defibrillator housing having a contact node electrically coupled with the defibrillator processor, and wherein the defibrillator processor is further configured to store updated tag data received via the contact node in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the defibrillator memory is further configured to store backup data; and the defibrillator processor is further configured to store the backscatter data already stored in the defibrillator memory in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the DWCM is further configured to wirelessly receive backup data capable of being stored in the defibrillator memory.

According to one embodiment of the invention, the WCD system further comprises: a defibrillator housing, the defibrillator processor and the NFC tag being located within the defibrillator housing; and a service port in the defibrillator housing having a contact node electrically coupled with the defibrillator processor, and wherein the defibrillator processor is further configured to receive backup data storable in the defibrillator memory via the contact node.

In accordance with one embodiment of the invention, a non-transitory computer readable storage medium storing one or more programs which, when executed by at least one defibrillator processor of a Wearable Cardioverter Defibrillator (WCD) system, the Wearable Cardioverter Defibrillator (WCD) system configured to wirelessly exchange data with an access device different from the WCD system, the access device including a Near Field Communication (NFC) reader, a peripheral processor, and an Access Wireless Communication Module (AWCM), the WCD system comprising: a support structure configured to be worn by a patient; a power source; an energy storage module configured to be charged from the power source so as to store an electrical charge; a discharge circuit coupled to the energy storage module, the discharge circuit controllable to wear the support structure on the patient while discharging the electrical charge through the patient; a defibrillator memory configured to store a program and configuration data; a defibrillator processor; an NFC tag having a tag memory in which access data is stored; and a Defibrillator Wireless Communication Module (DWCM), the one or more programs causing operations comprising: the defibrillator processor executing the stored program in accordance with the stored configuration data to generate a first decision to shock or not shock; the defibrillator processor controlling the discharge circuit to discharge the charge in response to a first determination of a shock; the NFC tag then receives a wireless interrogation wave from the NFC reader; the NFC tag then wirelessly transmits backscattered waves encoding the access data in response to the received wireless interrogation waves, wherein the backscattered waves are receivable by an NFC reader of the access device, authentication data is generated from the encoded access data by a peripheral processor of the access device, and the AWCM is capable of transmitting the authentication data and updated configuration data; the DWCM then wirelessly receives the validation data and updated configuration data sent by the AWCM; determining whether the received validation data has been generated from the backscattered encoded access data; the defibrillator processor storing the received updated configuration data in the defibrillator memory in place of the configuration data in response to determining that the received verification data has been generated from the backscattered encoded access data; the defibrillator processor then re-runs the stored program in accordance with the stored configuration data to generate a second decision to shock or not shock; and the defibrillator processor controls the discharge circuit to discharge the stored charge in response to a second determination of a shock.

According to one embodiment of the invention, the authentication data comprises access data or a hash of the access data.

According to one embodiment of the invention, the verification data includes a network address of the DWCM.

According to one embodiment of the invention, the backscattered encoded access data is encrypted.

According to one embodiment of the invention, the tag memory further stores a tag password; and the NFC tag does not backscatter the encoded access data unless the interrogation wave also encodes the tag password.

In accordance with one embodiment of the invention, the WCD system has been assigned a serial number; and the tag password is or is related to the serial number.

In accordance with one embodiment of the invention, the DWCM has been assigned a network address, and the DWCM does not send the network address in response to the AWCM's query signal.

In accordance with one embodiment of the invention, the received configuration data can be stored in the defibrillator memory only when it is received by the DWCM before the expiration of the timeout period after transmission of the backscatter wave.

According to one embodiment of the invention, the NFC tag further receives another wireless interrogation wave from another NFC reader, decodes updated tag data from the other wireless interrogation wave, and stores the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the NFC tag further receives another wireless interrogation wave from the NFC reader, decodes updated tag data from the other wireless interrogation wave, and stores the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the DWCM further wirelessly receives updated tag data from the AWCM; and the defibrillator processor further stores the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the defibrillator memory further stores backup data; and the defibrillator processor further stores the backscatter data already stored in the defibrillator memory in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the DWCM further wirelessly receives backup data stored in the defibrillator memory.

In accordance with one embodiment of the invention, a method for a Wearable Cardioverter Defibrillator (WCD) system configured to wirelessly exchange data with an access device different from the WCD system, the access device including a Near Field Communication (NFC) reader, a peripheral processor, and an Access Wireless Communication Module (AWCM), the WCD system comprising: a support structure configured to be worn by a patient; a power source; an energy storage module configured to be charged from the power source so as to store an electrical charge; a discharge circuit coupled to the energy storage module, the discharge circuit controllable to wear the support structure on the patient while discharging the electrical charge through the patient; a defibrillator memory configured to store a program and configuration data; a defibrillator processor; an NFC tag having a tag memory in which access data is stored; and a Defibrillator Wireless Communication Module (DWCM), the method comprising:

the defibrillator processor executing the stored program in accordance with the stored configuration data to generate a first decision to shock or not shock; the defibrillator processor controlling the discharge circuit to discharge the charge in response to a first determination of a shock; the NFC tag then receives a wireless interrogation wave from the NFC reader; the NFC tag then wirelessly transmits backscattered waves encoding the access data in response to the received wireless interrogation waves, wherein the backscattered waves are receivable by an NFC reader of the access device, authentication data is generated from the encoded access data by a peripheral processor of the access device, and the AWCM is capable of transmitting the authentication data and updated configuration data; the DWCM then wirelessly receives the validation data and updated configuration data sent by the AWCM; determining whether the received validation data has been generated from the backscattered encoded access data; the defibrillator processor storing the received updated configuration data in the defibrillator memory in place of the configuration data in response to determining that the received verification data has been generated from the backscattered encoded access data; the defibrillator processor then re-runs the stored program in accordance with the stored configuration data to generate a second decision to shock or not shock; and the defibrillator processor controls the discharge circuit to discharge the stored charge in response to a second determination of a shock.

According to one embodiment of the invention, the access device is disposed in a peripheral housing; and the peripheral housing is at a distance of at most 10 "from the NFC tag when the NFC tag receives a wireless interrogation wave from the NFC reader and wirelessly transmits the backscattered wave.

According to one embodiment of the invention, the authentication data comprises access data or a hash of the access data.

According to one embodiment of the invention, the verification data includes a network address of the DWCM.

According to one embodiment of the invention, the backscattered encoded access data is encrypted.

According to one embodiment of the invention, the tag memory further stores a tag password; and the NFC tag does not backscatter the encoded access data unless the interrogation wave also encodes the tag password.

In accordance with one embodiment of the invention, the WCD system has been assigned a serial number; and the tag password is or is related to the serial number.

In accordance with one embodiment of the invention, the DWCM has been assigned a network address; and the DWCM does not transmit the network address in response to the AWCM's query signal.

In accordance with one embodiment of the invention, the received configuration data can be stored in the defibrillator memory only when it is received by the DWCM before the expiration of the timeout period after transmission of the backscatter wave.

According to one embodiment of the invention, the NFC tag further receives another wireless interrogation wave from another NFC reader, decodes updated tag data from the other wireless interrogation wave, and stores the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the NFC tag further receives another wireless interrogation wave from the NFC reader, decodes updated tag data from the other wireless interrogation wave, and stores the updated tag data in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the DWCM further wirelessly receives updated tag data from the AWCM; and the defibrillator processor further stores the updated tag data in the tag memory in place of the access data.

In accordance with one embodiment of the present invention, the WCD system further comprises a defibrillator housing, the defibrillator processor and the NFC tag located within the defibrillator housing; the WCD system further comprises a service port in the defibrillator housing having a contact node electrically coupled with the defibrillator processor; and the defibrillator processor further stores updated tag data received via the contact node in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the defibrillator memory further stores backup data; and the defibrillator processor further stores the backscatter data already stored in the defibrillator memory in the tag memory in place of the access data.

In accordance with an embodiment of the present invention, the DWCM further wirelessly receives backup data stored in the defibrillator memory.

In accordance with one embodiment of the present invention, the WCD system further comprises a defibrillator housing, the defibrillator processor and the NFC tag located within the defibrillator housing; the WCD system further comprises a service port in the defibrillator housing having a contact node electrically coupled with the defibrillator processor; and the defibrillator processor further receives backup data stored in the defibrillator memory via the contact nodes.

These and other features and advantages of the present invention will become more apparent in view of the embodiments described and illustrated in this disclosure, i.e., from this written description and the accompanying drawings. This disclosure generally reflects the preferred embodiments of the invention. However, the attentive reader will note that some aspects of the disclosed embodiments extend beyond the scope of the claims. To the extent that the disclosed embodiments do extend beyond the scope of the claims, they are considered supplementary background information and do not constitute a definition of the claimed invention.

Drawings

Fig. 1 is a diagram of elements of an example Wearable Cardioverter Defibrillator (WCD) system made in accordance with an embodiment;

fig. 2 is a diagram illustrating example elements of an external defibrillator (such as example elements belonging to the WCD system of fig. 1 and including an NFC tag according to an embodiment);

fig. 3 is a diagram of example elements of an external defibrillator (such as the external defibrillator of fig. 2 and manufactured according to an embodiment) and elements of an access device during wireless communication between the external defibrillator and the access device;

fig. 4 is a diagram of example operations that occur when uploading configuration data to the external defibrillator of fig. 3 according to an embodiment;

fig. 5 is a flowchart illustrating a method of the external defibrillator of fig. 3 according to an embodiment for performing the operations of fig. 4;

fig. 6 is a diagram of example operations that occur when a software update is uploaded to the external defibrillator of fig. 3 according to an embodiment;

fig. 7 is a flowchart for explaining a method of the external defibrillator of fig. 3 according to an embodiment of performing the operations of fig. 6;

fig. 8 is a diagram of example operations that occur when action data of the external defibrillator of fig. 3 is downloaded, according to an embodiment;

fig. 9 is a flowchart for explaining a method of the external defibrillator of fig. 3 according to an embodiment of performing the operations of fig. 8;

fig. 10 is a diagram illustrating example elements of an external defibrillator, such as the external defibrillator of fig. 3, in an embodiment in which an NFC tag receives and stores updated data directly from a trusted NFC reader;

fig. 11 is a diagram illustrating example elements of an external defibrillator, such as the external defibrillator of fig. 3, in an embodiment in which the NFC tag receives and stores updated data directly from a trusted programming device;

fig. 12 is a diagram illustrating example elements of an external defibrillator, such as the external defibrillator of fig. 3, in an embodiment in which an NFC tag can receive and store updated data via a wired service port; and

fig. 13 is a diagram illustrating example elements of an external defibrillator, such as the external defibrillator of fig. 3, in an embodiment in which the NFC tag can receive backup data stored in a memory of the external defibrillator;

Detailed Description

As already mentioned, the present description is directed to a Wearable Cardioverter Defibrillator (WCD) system, a storage medium storing a program, and a method. Embodiments are now described in more detail.

A Wearable Cardioverter Defibrillator (WCD) system made in accordance with an embodiment has multiple elements. These elements may be provided separately as modules that may be interconnected, or may be combined with other elements, etc.

An element of the WCD system may be a support structure configured to be worn by a patient. The support structure may be any structure suitable for wearing, such as a harness, vest, semi-vest-e.g. on the left side of the torso, which positions the electrodes on opposite sides of the heart, one or more straps configured to be worn horizontally or possibly vertically on the shoulder, another garment, etc. The support structure may be embodied as a single element or as multiple elements. For example, the support structure may have: a top member resting against the shoulder for ensuring that the defibrillation electrode is in place for defibrillation; and a bottom member resting on the buttocks for carrying most of the weight of the defibrillator. A single element embodiment may have a band that surrounds at least the torso. Other embodiments may be attached to the patient using adhesive material or in another manner, without encircling any part of the body. Other examples are possible.

Fig. 1 illustrates elements of a WCD system made in accordance with an embodiment as it may be worn by a patient 82. A patient, such as patient 82, may also be referred to as a person and/or a wearer because the patient wears elements of the WCD system.

In fig. 1, a general support structure 170 is shown relative to the body of the patient 82 and thus also relative to his or her heart 85. The structure 170 may be a harness, vest, half-vest, one or more straps or clothing, etc., as described above. Structure 170 may be implemented as a single element or as multiple elements, etc. The structure 170 may be worn by the patient 82, but the manner in which it is worn is not depicted, as the structure 170 is only generally and in fact partially conceptually depicted in fig. 1. That is, fig. 1 is only for illustrating a concept with respect to the support structure 170, and is not construed as being limited thereto.

A WCD system according to an embodiment is configured to defibrillate a patient wearing it by delivering charge to the patient's body in the form of one or more pulsed electrical shocks. Fig. 1 shows a sample external defibrillator 100 and sample defibrillation electrodes 104, 108 coupled to the external defibrillator 100 via electrode leads 105. The defibrillator 100 and defibrillation electrodes 104, 108 are coupled to a support structure 170. Thus, many of the elements of the defibrillator 100 may be coupled to the support structure 170 accordingly. When the defibrillation electrodes 104, 108 make good electrical contact with the body of the patient 82, the defibrillator 100 can apply a brief, intense electrical pulse 111 through the body via the electrodes 104, 108. The pulse 111 (also referred to as a defibrillation shock or a therapeutic shock) is intended to pass through and restart the heart 85 in an effort to save the life of the patient 82. The pulse 111 may also include one or more pacing pulses, and so on.

A WCD system according to an embodiment includes a Near Field Communication (NFC) tag. NFC tags typically include a tag antenna, a tag processor and a tag memory and operate according to the principles of RFID (radio frequency identification). The NFC tag may be located anywhere in the WCD system. The preferred location is near an electronic component, such as a processor, memory, etc., whose contents may be updated. Thus, in fig. 1, NFC tag 191 is disposed within external defibrillator 100, sometimes referred to as a secure NFC tag 191.

In fig. 1, an access device 141 is shown in communication with an external defibrillator 100. The access device 141 may be a programmer of the defibrillator 100, an accessory of a WCD system, a peripheral device, a base station configured to receive motion data generated by the defibrillator 100 and stored in a memory of the defibrillator, a computer, a general purpose communication device such as a mobile smartphone, a laptop computer, a tablet loaded with an appropriate application, or the like. The access device 141 may include a peripheral processor capable of communicating with the NFC tag 191, an Access Wireless Communication Module (AWCM), and a Near Field Communication (NFC) reader. In addition and depending on its structure, the access device 141 may include a user interface with input and output devices, such as a keyboard, touch screen, buttons and other actuators, microphone, speaker, and the like.

In this example, it should be observed that two communication links (comink) are established between the access device 141 and the defibrillator 100, namely an RFID communication link 198 and a data communication link 148. It should also be observed that in fig. 1, distances are not necessarily drawn to scale; in practice, the access device 141 may be closer to the defibrillator 100 than suggested by the figures to the communication links 198, 148 to be established, taking into account the size of the patient 82. Further, communication links 198, 148 may be established and used when patient 82 is not wearing support structure 170 or any other element of the WCD system.

The NFC tag 191 may be used to help pair the external access device 141 with the defibrillator 100. External defibrillators benefit from connections with other devices for receiving configuration data and updating and downloading data.

For patient safety reasons, it is important to prevent or avoid this type of error where a peripheral device may be connected to the wrong defibrillator. These risks are increased when the connections are wireless connections. In an embodiment, such risk is mitigated by using NFC tags to pair elements to communicate. In an embodiment or version, NFC tag 191 is capable of storing connection and security data for defibrillator 100. The access device 141 reads the connection and security data as a key for knowing how to connect to a particular defibrillator 100. Because NFC technology requires the tag and reader to be in close proximity, the user can reasonably be sure that the correct defibrillator is being connected to the peripheral device.

Prior art defibrillators typically decide whether to defibrillate based on the patient's ECG signal. However, the external defibrillator 100 may initiate defibrillation (or stop defibrillation) based on various inputs, with ECG being just one of them.

Thus, it should be understood that a signal, such as a physiological signal containing physiological data, is obtained from the patient 82. While the patient may be considered to also be the "user" of the WCD system, this is not a requirement. That is, for example, a user of a Wearable Cardioverter Defibrillator (WCD) may include an individual (or group of individuals) of a clinician, such as a doctor, nurse, Emergency Medical Technician (EMT), or other similar location. The specific context of these and other related terms in these descriptions should be interpreted accordingly.

The WCD system may optionally include an external monitoring device 180. The device 180 is referred to as an "external" device because it may be provided as a stand-alone device, e.g., not within the housing of the defibrillator 100. The apparatus 180 may be configured to sense or monitor at least one local parameter. The local parameters may be parameters of the patient 82, or parameters of the WCD system, or parameters of the environment, as will be described later in this document. The device 180 may include one or more sensors or sensors configured to present one or more physiological inputs from one or more patient parameters that it senses.

Optionally, the device 180 is physically coupled to the support structure 170. Additionally, the device 180 may be communicatively coupled with other elements coupled to the support structure 170. Such communication may be implemented by a communication module as would be deemed appropriate by one skilled in the art in light of the present description.

Fig. 2 is a diagram illustrating elements of an external defibrillator 200 manufactured according to an embodiment. These elements may be included, for example, in the external defibrillator 100 of fig. 1. The elements shown in fig. 2 may be disposed in a housing 201, which may also be referred to as a casing 201.

The external defibrillator 200 is intended for a patient who will wear it, such as the patient 82 of fig. 1. The defibrillator 200 may also include a user interface 270 for a user 282. User 282 may be patient 82, also referred to as wearer 82. Or user 282 may be a live local rescuer, such as a bystander or trained person who may provide assistance. Alternatively, user 282 may be a remotely trained caregiver communicating with the WCD system.

The user interface 270 may be manufactured in any number. The user interface 270 may include output devices for communicating with a user, which may be visual, auditory, or tactile. For example, the output device may be a light or screen to display sensed, detected, and/or measured content, and provide visual feedback to the rescuer 282 for their resuscitation attempt, and the like. Another output device may be a speaker, which may be configured to emit voice prompts or the like. Sounds, images, vibrations, and anything that user 282 may perceive may also be referred to as human-perceptible indications. The user interface 270 may also include an input device for receiving input from a user. Such input devices may additionally include various controls, such as buttons, keyboards, touch screens, microphones, and the like. The input device may be a kill switch, which is sometimes referred to as a "live-man" switch. In some embodiments, actuating the kill switch may prevent an imminent delivery of a shock.

The defibrillator 200 may include an internal monitoring device 281. The device 281 is referred to as an "internal" device because it is incorporated within the housing 201. The monitoring device 281 may sense or monitor patient parameters, such as patient physiological parameters, system parameters, and/or environmental parameters, all of which may be referred to as patient data. In other words, internal monitoring device 281 may be complementary to or an alternative to external monitoring device 180 of fig. 1. Assigning which system parameters are to be monitored by which monitoring device may be done according to design considerations. The device 281 may include one or more sensors configured to present one or more physiological inputs from one or more patient parameters it senses. Of course, the device 281 is disposed on and over the ECG port 219.

Patient physiological parameters include, for example and without limitation, those that may be helpful in detecting whether a patient requires a shock via a wearable defibrillation system, optionally plus their medical history and/or event history. Examples of such parameters include the patient's ECG, blood oxygen level, blood flow, blood pressure, blood perfusion, pulsatile changes in light transmission or reflective properties of perfused tissue, heart sounds, heart wall motion, breathing sounds and pulse. Accordingly, the monitoring device may include one or more sensors configured to acquire patient physiological signals. Examples of such sensors include electrodes to detect ECG data, perfusion sensors, pulse oximeters, doppler devices to detect blood flow, cuffs to detect blood pressure, optical sensors, illumination detectors and possibly sources to detect color changes of tissue, motion sensors, devices capable of detecting heart wall motion, sound sensors, devices with microphones, SpO2 sensors, etc. It should be appreciated that such sensors may help detect the patient's pulse and may therefore also be referred to as pulse detection sensors, pulse sensors, and pulse rate sensors. Pulse detection is also taught at least in U.S. patent No.8,135,462 to Physio-Control, which is incorporated herein by reference in its entirety. Furthermore, other ways of performing pulse detection may be implemented by those skilled in the art. In this case, the sensor comprises a suitable sensor, and the physiological input is a measurement of the patient parameter by the sensor. For example, suitable sensors for heart sounds may include a microphone or the like.

In some embodiments, the local parameter is a trend that may be detected in the monitored physiological parameter of patient 282. Trends may be detected by comparing parameter values at different times. Parameters for which detected trends may particularly assist in cardiac rehabilitation programs include: a) cardiac function (e.g., ejection fraction, stroke volume, cardiac output, etc.); b) heart rate variability during rest or exercise; c) heart rate distribution during measurement of movement and activity, e.g. from accelerometer signals and from adaptive rate pacemaker techniques; d) heart rate trends; e) perfusion, e.g. from SpO2 or CO 2; f) respiratory function, respiratory rate, etc.; g) exercise, activity level; and so on. Once a trend is detected, it may be stored and/or reported over a communication link, possibly accompanied by an alert. From this report, a physician monitoring the progress of patient 282 will know that it is not an improved or worsening condition.

Patient status parameters include recorded aspects of patient 282, such as motion, posture, whether they have recently spoken, plus possibly what they have spoken, and the like, optionally plus a history of parameters. Alternatively, one of the monitoring devices may include a position sensor, such as a Global Positioning System (GPS) position sensor. Such sensors may detect position, plus velocity may be detected as the rate of change of position over time. Many motion detectors output a motion signal that is indicative of the motion of the detector and thus of the patient's body. Patient status parameters can be very helpful in narrowing the determination of whether SCA is actually occurring.

A WCD system manufactured according to an embodiment may include a motion detector. In an embodiment, the motion detector may be implemented within monitoring device 180 or monitoring device 281. Such a motion detector may be configured to detect motion events. In response, the motion detector may present or generate motion detection input from the detected motion event that may be received by a subsequent device or function. It may be convenient to define a movement event, such as a change in movement from a baseline movement or rest, etc. Such a motion detector may be made in many ways known in the art, for example by using an accelerometer. In this case, the patient parameter is motion, the sensor comprises a motion detector, and the physiological input is a motion measurement.

System parameters of the WCD system may include system identification, battery status, system date and time, self-test reports, incoming data records, records of episodes and interventions, and the like.

The environmental parameters may include ambient temperature and pressure. The humidity sensor may provide information as to whether it is likely to rain. The estimated patient position may also be considered as an environmental parameter. If the monitoring device 180 or 281 includes a GPS position sensor as described above, the patient position may be inferred.

The defibrillator 200 generally includes a defibrillation port 210, such as a receptacle in the housing 201. Defibrillation port 210 includes electrical nodes 214, 218. Leads of defibrillation electrodes 204, 208 (e.g., lead 105 of fig. 1) may be inserted into defibrillation port 210 so as to make electrical contact with nodes 214, 218, respectively. Conversely, defibrillation electrodes 204, 208 can also be continuously connected to defibrillation port 210. Either way, defibrillation port 210 may be used to direct the charge already stored in energy storage module 250 to the wearer via the electrodes. The charge will be a shock for defibrillation, pacing, etc.

The defibrillator 200 may optionally also have an ECG port 219 in the housing 201 for insertion of sensing electrodes 209, also referred to as ECG electrodes and ECG leads. Conversely, sensing electrode 209 can also be continuously connected to ECG port 219. Sensing electrodes 209 are sensors of a type that can help sense ECG signals (e.g., 12 lead signals, or signals from a different number of leads), particularly if they make good electrical contact with the patient's body. Sensing electrodes 209 may be attached to the interior of support structure 170 for making good electrical contact with the patient, similar to defibrillation electrodes 204, 208.

Optionally, the WCD system according to an embodiment further comprises a fluid capable of automatic deployment between the electrode and the patient's skin. The fluid may be electrically conductive, for example by including an electrolyte, for better electrical contact between the electrode and the skin. Electrically, when a liquid is deployed, the electrical impedance between the electrodes and the skin decreases. Mechanically, the fluid may be in the form of a low viscosity gel so that it does not run off after deployment. Fluid may be used for both defibrillation electrodes 204, 208 and sensing electrode 209.

The fluid may be initially stored in a fluid reservoir (not shown in fig. 2) that can be coupled to the support structure. In addition, the WCD system according to an embodiment further includes a fluid deployment mechanism 274. The fluid deployment mechanism 274 may be configured to release at least some fluid from the reservoir and be deployed near one or both patient locations to which the electrodes are configured to attach to the patient. In some embodiments, prior to discharging, fluid deployment mechanism 274 is activated in response to receiving an activation signal AS from processor 230.

In some embodiments, the defibrillator 200 further includes a sensor that includes a measurement circuit 220. If provided, the measurement circuit 220 senses one or more electrophysiological signals of the patient from the ECG port 219. Even if the defibrillator 200 lacks the ECG port 219, the measurement circuit 220 can instead obtain a physiological signal through the nodes 214, 218 when the defibrillation electrodes 204, 208 are connected to the patient. In these cases, the physiological input reflects an ECG measurement. The parameter may be an ECG, which may be sensed as a voltage difference between the electrodes 204, 208. Further, the parameter may be an impedance that can be sensed between the electrodes 204, 208 and/or the connections of the ECG port 219. The sensing impedance is particularly useful for detecting whether these electrodes 204, 208 and/or sensing electrode 209 make good electrical contact with the patient's body. When available, these patient physiological signals may be sensed. The measurement circuitry 220 may then present or generate information about them as physiological inputs, data, other signals, and the like. More strictly speaking, the information provided by the measurement circuit 220 is output therefrom, but this information may be referred to as an input because it is received as an input by a subsequent device or function.

The defibrillator 200 further includes a processor 230, which is also a known defibrillator processor. The processor 230 may be implemented in a variety of ways. Such approaches include, by way of example and not limitation, digital and/or analog processors, such as microprocessors and Digital Signal Processors (DSPs); a controller, such as a microcontroller; software running in the machine; programmable circuitry such as Field Programmable Gate Arrays (FPGAs), Field Programmable Analog Arrays (FPAAs), Programmable Logic Devices (PLDs), Application Specific Integrated Circuits (ASICs), any combinations of one or more of these, and the like.

Processor 230 may include or have access to non-volatile memory for storing machine-readable and machine-executable instructions. Instructions, which may also be referred to as "software," generally provide functionality by performing methods as disclosed herein or as understood by those of skill in the art in view of the disclosed embodiments. In some embodiments, as a convention used herein, an instance of software may be referred to as a "module" and other similar terms. Generally, where introduced as a module, sets of instructions are provided to provide or implement the particular functionality. The embodiments of the modules and functions delivered are not limited by the embodiments set forth herein.

The processor 230 may be considered to have a plurality of modules. One such module may be detection module 232. The detection module 232 may include a Ventricular Fibrillation (VF) detector. The patient-sensed ECG from the measurement circuit 220 may be used as a physiological input, data, or other signal that may be used by the VF detector to determine whether the patient is experiencing VF. Detecting VF is useful because VF results in SCA. The detection module 232 may also include a Ventricular Tachycardia (VT) detector or the like.

Another such module in the processor 230 may be a suggestion module 234 that generates suggestions of what to do. The suggestion may be based on the output of the detection module 232. There may be many types of suggestions depending on the embodiment. In some embodiments, the advisory is a shock/no shock determination that the processor 230 may make, for example, via the advisory module 234. The shock/no-shock determination may be made by executing a stored shock advisory algorithm. A shock advisory algorithm may make a shock/no-shock determination from one or more ECG signals acquired according to an embodiment and determining whether a shock criterion is met. The determination may be made from a rhythm analysis or other aspect of the acquired ECG signal.

In some embodiments, when a shock is determined, a charge is delivered to the patient. Transporting the charge is also referred to as discharging. Shocks may be used for defibrillation, pacing, etc.

Processor 230 may include additional modules for other functions, such as other modules 236. In addition, if an internal monitoring device 281 is actually provided, it may be partially operated by the processor 230 or the like.

The defibrillator 200 optionally further includes a memory 238, which may also be referred to as defibrillator memory 238. The memory 238 may work in conjunction with the processor 230, for example, as described above. The memory 238 may be implemented in a number of ways. Such approaches include, by way of example and not limitation, volatile memory, non-volatile memory (NVM), Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media, optical storage media, smart cards, flash memory devices, any combination of these, and the like. Thus, the memory 238 is a non-transitory storage medium. If provided, the memory 238 may include programs for the processor 230 that the processor 230 can read and execute. More specifically, the program may include a set of instructions in code that processor 230 is capable of executing when read. The performance is achieved through physical manipulations of physical quantities and may result in functions, operations, procedures, actions, and/or methods to be performed, and/or processors causing other devices or elements or blocks to perform the functions, operations, procedures, actions, and/or methods. The programs may operate on the inherent needs of the processor 230 and may also include protocols and manners in which decisions may be made by the suggestion module 234. Additionally, the memory 238 may store prompts for the user 282 (if the user is a local rescuer). In addition, the memory 238 may store data. The data may include patient data, system data, and environmental data, such as learned by internal monitoring device 281 and external monitoring device 180. The data may be stored in memory 238 before being transmitted out of defibrillator 200 or after being received by defibrillator 200.

In an embodiment, the defibrillator 200 may also include an NFC tag 291. Tag 291 may be similar to tag 191, and more detailed embodiments are described later in this document.

The defibrillator 200 may also include a power supply 240. To provide portability to the defibrillator 200, the power supply 240 typically includes a battery. Such batteries are typically implemented as rechargeable or non-rechargeable battery packs. Sometimes, a combination of rechargeable and non-rechargeable battery packs is used. Other embodiments of power supply 240 may include an AC power cover, energy storage capacitors, and the like, available for AC power. In some embodiments, the power supply 240 is controlled by the processor 230. Appropriate components may be included to provide charging or to replace the power supply 240.

Defibrillator 200 further includes an energy storage module 250, which may thus be coupled to the support structure of the WCD system. Module 250 is where some electrical energy can be temporarily stored in the form of an electrical charge in preparation for discharge to apply a shock. In an embodiment, the module 250 may be charged from the power supply 240 to an amount of energy controlled by the processor 230. In a typical embodiment, module 250 includes a capacitor 252, which may be a single capacitor or a system of capacitors, or the like. In some embodiments, the energy storage module 250 includes a device exhibiting high power density, such as a supercapacitor. As described above, the capacitor 252 may store energy in the form of a charge for delivery to the patient.

The defibrillator 200 further includes a discharge circuit 255 when the decision is to shock, the processor 230 may be configured to control the discharge circuit 255 to discharge the charge stored in the energy storage module 250 through the patient. When so controlled, the circuit 255 may allow the energy stored in the module 250 to be released to the nodes 214, 218 and from there also to the defibrillation electrodes 204, 208 so as to cause a shock to be delivered to the patient. The circuit 255 may include one or more switches 257. The switch 257 may be made in a variety of ways, such as by an H-bridge or the like. The circuit 255 may also be controlled through a user interface 270.

The defibrillator 200 may optionally include a communication module 290, also referred to as a Defibrillator Wireless Communication Module (DWCM) 290. The DWCM 290 may be configured to establish one or more wireless communication links with other devices, such as the access device 141, which may belong to an entity such as a remote assistance center \ Emergency Medical Service (EMS). Module 290 may also include an antenna, portions of a processor, and other sub-elements deemed necessary by one skilled in the art. In this way, data and commands, such as patient data, event information, attempted therapy, CPR performance, system data, environmental data, and the like, may be communicated. Further, a communication module may be provided for wired communication with other components, peripheral devices, and the like.

Defibrillator 200 may optionally include other elements.

Returning to fig. 1, in an embodiment, one or more elements of the WCD system shown are customized for patient 82. Such customization may include a number of aspects. For example, the support structure 170 may be mounted to the body of the patient 82. For another example, a baseline physiological parameter of the patient 82 may be measured, such as a heart rate of the patient 82 at rest, while walking, a motion detector output while walking, and so forth. Such baseline physiological parameters may be used to customize the WCD system to make its diagnosis more accurate, as patients vary from one body to another. Of course, such parameters may be stored in a memory of the WCD system, e.g., by access device 141 or the like.

A programming interface may be made according to an embodiment that receives such measured baseline physiological parameters. Such a programming interface may automatically input baseline physiological parameters as well as other data in the WCD system.

Fig. 3 is a diagram of example elements of an external defibrillator 300 (such as the external defibrillator of fig. 2 and manufactured according to an embodiment) and elements of an access device 341 (such as the access device of fig. 1) during wireless communication between the external defibrillator 300 and the access device 341.

The external defibrillator 300 includes a defibrillator housing 301 containing therein the elements shown in this example. Defibrillator 300 thus includes defibrillator processor 330, defibrillator memory 338, Defibrillator Wireless Communication Module (DWCM)390, and NFC tag 391, all of which may be made as previously described for defibrillator processor 230, defibrillator memory 238, communication module 290, and NFC tag 291. NFC tag 391 may have a tag memory 392 that stores data 393 and optionally also a tag password 394. Access data 393 may be required for accessing DWCM 390.

The defibrillator memory 338 may be configured to store at least one program 332 and configuration data 333. The defibrillator processor 330 may be configured to run a program 332 in accordance with the stored configuration data 333 to generate a shock or no shock decision. The decision may be generated, for example, from the suggestion module 234 plus other inputs. During this time, a number of such decisions may be made, such as a first decision, a second decision, and so on.

Defibrillator processor 330 may also be configured to control the discharge circuit of the WCD system in response to the generated decision to discharge the charge. Of course, if updated configuration data has been stored in the defibrillator memory 338 in place of the configuration data 333, the defibrillator processor 330 may run the program 332 according to such stored updated configuration data, rather than for generating subsequent decisions. Alternatively, if the updated program is already stored in the defibrillator memory 338 in place of the program 332, the defibrillator processor 330 may run the updated program according to the configuration data 333 or according to any stored updated configuration data to make subsequent decisions.

The defibrillator memory 338 may be configured to further store the motion data 334. Action data 334 may be generated by the operation of the WCD system and include historical data, notifications, etc. of patients, operations, and events.

The access device 341 may be a defibrillator configurator of the type used by a clinician. Access device 341 may be used, for example, to provide software updates, to provide updated configuration data for configuration settings for a particular WCD, for a particular patient, and so forth. The access device 341 includes a peripheral housing 306 containing the elements as shown. Access device 341 includes at least NFC reader 342, peripheral processor 340, and Access Wireless Communication Module (AWCM) 343. It may also have a user interface, etc.

External defibrillator 300 may be configured to wirelessly exchange data with access device 341. The wireless exchange may be over RFID communication link 398 and data communication link 348, which can be communication links 198, 148. The communication links 398, 348 may be characterized as being conducted over the air interface 302.

For the RFID communication link 398, the NFC reader 342 may be configured to transmit the wireless interrogation wave 344. The NFC tag operates by using the RFID principle, for example, the NFC tag 391 may wirelessly utilize energy from the NFC reader 342. The NFC tag 391 may be configured to receive the interrogation wave 344 from the NFC reader 342 and to wirelessly transmit backscattered waves 395 in response to the received interrogation wave 344. Because of the use of NFC technology, these exchanges over RFID communication link 398 do not occur over long distances, thereby better protecting the wrong WCD system from being programmed. In fact, when NFC tag 391 receives wireless interrogation wave 344 from NFC reader 342 and wirelessly transmits backscattered wave 395, peripheral housing 306 is short distance from NFC tag 391. The peripheral housing 306 has a distance 307 from the defibrillator housing 301. If, preferably, an NFC tag 391 is provided within the defibrillator housing 301, the distance 307 is short, may be up to 10 ", and in practice is about 1" or less.

Backscattered waves 395 may encode access data 393 and be received by NFC reader 342 of access device 341. In some embodiments, assuming access device 341 thus learns access data 393, peripheral processor 340 may generate validation data for addressing DWCM 390. More specifically, as shown within peripheral processor 340, encoded access data 393 is received, pursuant to operation 345. Pursuant to a subsequent operation 349, verification data is generated from the received encoded access data 393. Thus, the verification data may be generated from the encoded access data 393 backscattered by the NFC tag 391 and received by the NFC reader 342. The authentication data may include access data 393, a hash of access data 393, and the like. It may include the network address of the DWCM, the key used to address the DWCM390, and so on. If the validation data is identical to the access data, then operations 349 other than local access memory data need not be performed, at least temporarily, before sending the access data.

When the access data is backscattered, various measures may be taken to protect the access data 393. First, since the NFC tag already uses RFID-type technology at low power, the threat may only come from very close range listeners, which is a factor that can be controlled. Second, the backscattered encoded access data may be encrypted. Third, the NFC tag 391 may be readable only by a password. For example, tag memory 392 may be further configured to store a tag password 394; in addition, the NFC tag 391 may be configured not to backscatter the encoded access data 393 unless the interrogation wave 344 also encodes the tag password 394. In such an embodiment, the WCD system may have been assigned a serial number, and tag password 394 may be, or be associated with, the serial number. In this case, the serial number may be used to ensure that a particular access device (e.g., a defibrillator configurator) has permission to connect with a particular defibrillator. This can be done by: the serial number is provided to a secure website where the user has been authenticated and authorized to grant the appropriate security key permission to devices for communicating with the WCD system. Thus, the NFC tag will store unique data only about the defibrillator on that particular patient. The only defibrillator configurator that has given the necessary security data for a particular defibrillator on a particular patient can be allowed to connect. This constitutes another layer of security that prevents rogue defibrillator configurators from maliciously attacking the defibrillator 300.

An advantage of an embodiment is that the DWCM390 does not need to transmit its key or network address to any interrogating peripheral. In particular, the DWCM390 may be assigned a network address and not transmit the network address in response to the query signal of the AWCM 343. In fact, DWCM390 may remain silent and, unless properly addressed, will not broadcast its presence, address, or anything else. Other devices are not even aware that a nearby DWCM390 has a wireless connection until the NFC tag is successfully read.

In an embodiment, the AWCM 343 may properly address the defibrillator 300 and its DWCM390 by sending the verification data it generated in operation 349. This may occur in data communication link 348. The AWCM may further send updated configuration data, such as software updates or updates to software patches, or downloaded memory requests, in wave 346.

The DWCM390 may cooperate with the defibrillator processor 330. The DWCM390 may receive the waves 346 transmitted by the AWCM along with the verification data therewith. If it is determined that the received verification data has been generated from the backscattered encoded access data 393, the defibrillator processor 330 may react accordingly. For example, the defibrillator processor 330 may be further configured to cause the DWCM390 to transmit a reply wave 399 with an acknowledgement for establishing the data communication link 348.

The data communication link 348 may be established in a variety of ways and using a variety of wireless protocols. An example protocol in this is WiFi. NFC tag 391 may store an IP address, an SSID, and a password. This data will be used to set up the secure WiFi network. Disconnection of either party from the network may result in a WiFi network drop, in which case the NFC tag needs to be read again in case the access device 341 does not store the data. The data on the NFC tag may also be encrypted with a symmetric or asymmetric key to protect against malicious users attempting to read the information.

Another such example protocol is bluetooth. NFC tag 391 may contain a MAC address and a security key. This information is available to access device 341 for pairing or connecting with defibrillator 300. In some embodiments, when two devices become unpaired or disconnected, neither device stores data about the pairing to allow repair. The NFC tag 391 needs to be read again in order to pair or connect with a new device. The data on NFC tag 391 may also be encrypted again with a symmetric or asymmetric key to protect against malicious users attempting to read the information.

In some embodiments, if the wave 346 encodes updated configuration data, the defibrillator processor 330 may be further configured to store the received updated configuration data in the defibrillator memory 338 in place of the configuration data 333. This may be the initially received configuration data or it may be used for updating. When configuration data is initially received, either no configuration data is stored, or standard configuration data is stored. In this case, the defibrillator processor 330 is configured to store the received configuration data in the defibrillator memory, and the defibrillator processor thus becomes configured to run a program in accordance with the stored configuration data to produce a certain decision of shock or no shock, and to control the discharge circuit to discharge the charge in response to the certain decision of shock. When the received configuration data is an update, this means that the defibrillator memory 338 also stores the previous configuration data, and the defibrillator processor 330 is configured to run the program 332 according to the stored previous configuration data in order to make the previous decision to shock or not shock. The defibrillator processor 330 is further configured to control the discharge circuit to discharge the charge in response to a previous determination of a shock.

In some embodiments, if the wave 346 encodes an updated program, the defibrillator processor 330 may be further configured to store the received updated program in the defibrillator memory 338 in place of the program 332. This may be for the originally received program, as well as for the updates being installed. Such WCD systems use secure NFC tags to upload software.

In some embodiments, if the wave 346 encodes a request for a memory download, the defibrillator processor 330 may be further configured to cause the action data 334 to be encoded in the reply wave 399. Such WCD systems use secure NFC tags to allow data requests from memory.

Examples are now described. The devices and/or systems mentioned in this document perform functions, processes, and/or methods. The functions, processes and/or methods may be performed by one or more devices comprising logic circuitry. Such devices may alternatively be referred to as computers, and the like. It may be a stand-alone device or part of a computer, such as a general purpose computer or a device with one or more additional functions. The logic circuitry may include a processor and a non-transitory computer-readable storage medium, such as a memory of the type described elsewhere in this document. Generally, programs are preferably implemented and described as various interconnected distinct software modules or features, simply for convenience. These, along with data, are referred to individually and also collectively as software. In some cases, the combination of software and hardware is referred to as a hybrid of firmware.

Further, methods and algorithms are described below. The methods and algorithms may not be inherently related to any particular logical device or other apparatus. Rather, they are advantageously implemented by a program for use with a computing machine, such as a general purpose computer, a special purpose computer, a microprocessor, a processor, such as the processor described elsewhere in this document, and so forth.

The detailed description includes at least one flowchart, display image, algorithm, and symbolic representation of the operation of a program within a computer readable medium. An economy is realized by using a set of flow charts to describe both the procedure and the method. Thus, while the flow diagrams depict methods in block diagram form, they also depict processes. The method is now described.

In some embodiments, the configuration data is uploaded and stored for use in the WCD system. Examples of such uploads are now described in connection with fig. 3, 4 and 5.

Fig. 4 is a diagram of example operations that occur when uploading configuration data to the external defibrillator 300 of fig. 3. The upload may be from access device 441, which may be as previously described for access device 341. For example, access device 441 may be configured to perform operations 345, 349 previously described. It may also establish communication links 498, 448 similar to communication links 398, 348 over air interface 302.

Fig. 5 shows a flow chart 500 for describing a method according to an embodiment. According to operation 510, the defibrillator processor may run a program according to the stored configuration data to generate a first decision to shock or not shock. At a subsequent time, operation 510 proceeds, a second decision may be made, and so on. Sometimes, such a decision may be characterized as the previous one, e.g. if it was made from the previous configuration data, etc.

According to another operation 520, it is determined what the decision of operation 510 is. If the decision is a shock, then according to another operation 530, the discharge circuit may be controlled by the defibrillator processor to discharge the charge as described above. Execution may then return to operation 510.

If at operation 520 it is decided not to shock, according to another operation 540 it is determined whether the NFC tag 391 has received a wireless interrogation wave from an NFC reader. The NFC reader may be an NFC reader 342. If not, execution may return to operation 510.

The situation where a wireless interrogation wave 444 is indeed received can be seen in fig. 4. As previously described, in some embodiments, the interrogation wave 444 may further encode a tag password 394 of the NFC tag 391. In fact, the tag password (whatever it is) encoded by the interrogation wave 444 will be checked against the tag password 394 stored in the tag memory 392 of the NFC tag 391 to verify validity. This check for validity is conceptually illustrated by the dashed lines 394 through 394 with question marks.

Returning to fig. 5, if a wireless interrogation wave has indeed been received at operation 540, then according to another operation 550, the backscattered wave may be wirelessly transmitted by the NFC tag. The backscattered waves may encode access data stored in the tag memory. If the NFC tag requires a password, this backscattering may be configured to occur only when a valid tag password has been sent.

Fig. 4 shows backscattered waves 495 encoding access data 393 stored in tag memory 392. Thereafter, operations 345, 349 may be performed by access device 441 and wave 446, similar to wave 346, may be transmitted. As described above, the wave 446 may encode verification data 496 and updated configuration data 439.

Returning to fig. 5, only operations 345, 349 are shown to indicate in what order they are performed after operation 550. These operations 345, 349 are shown in dashed lines to indicate that they are not part of flowchart 500.

After operation 550, in accordance with another operation 560, it may be determined whether the validation data and updated configuration data transmitted by the AWCM have been wirelessly received by the DWCM. Otherwise, execution may return to operation 510.

In some embodiments, the DWCM will only wait for a limited time for verification data and updated configuration data to increase security. For example, after the backscattered wave is transmitted at operation 550, a timeout period may begin. The timeout period may be very short, such as 1 second. In such embodiments, the received configuration data can only be stored in the defibrillator memory when received by the DWCM before the timeout period expires.

If so, according to another operation 570, it may be determined whether received authentication data has been generated from the backscattered encoded access data. This operation may service external defibrillator 300 to authenticate access device 441. (in FIG. 4, this authentication operation is conceptually illustrated with a dashed line marked with a question mark from the validation data 496 to the access data 393). As previously described, in some embodiments, the verification data is the same as the access data. In FIG. 5, at operation 570, if the answer is no, execution may return to operation 510.

If at operation 570 the answer is yes, then according to another operation 580 the defibrillator processor stores the received updated configuration data in the defibrillator memory in response to determining that the received verification data has been generated from the backscattered encoded access data and, of course, in response to the fact that the received updated program was transmitted and received. Such storage may replace the previous configuration data stored therein. (FIG. 4 also shows that updated configuration data 439 of wave 446 is stored in memory 338 in place of the previous configuration data 338.) execution may then return to operation 510 to make a second decision, and so on.

In some embodiments, one or more programs are uploaded and stored for use in the WCD system. Examples of such uploads are now described in connection with fig. 3, 6 and 7.

Fig. 6 is a diagram of example operations that occur when a program is uploaded to the external defibrillator 300 of fig. 3. The upload may be from access device 641, which may be as previously described for access device 341. For example, the access device 641 may be configured to perform operations 345, 349 previously described. It may also establish communication links 698, 648 similar to communication links 398, 348 over air interface 302.

Fig. 7 shows a flow chart 700 for describing a method according to an embodiment. According to operation 710, the defibrillator processor may run a program according to the stored configuration data to generate a first decision to shock or not shock. At a subsequent time, operation 710 proceeds, a second decision may be made, and so on. Sometimes, such a decision may be characterized as the previous, e.g., if it was made by a program of the previous, etc.

According to another operation 720, it is determined what the decision of operation 710 is. If the decision is a shock, then according to another operation 730, the discharge circuit may be controlled by the defibrillator processor to discharge the charge as described above. Execution may then return to operation 710.

If at operation 720 it is decided not to shock, according to another operation 740 it is determined whether the NFC tag 391 has received a wireless interrogation wave from an NFC reader. Otherwise, execution may return to operation 710.

The situation where the wireless interrogation wave 644 is indeed received can be seen in fig. 6. As previously described, in some embodiments, the interrogation wave 644 may further encode a tag password 394 of the NFC tag 391. In fact, the tag password (whatever it is) encoded by the interrogation wave 644 will be checked against the tag password 394 stored in the tag memory 392 of the NFC tag 391 to verify validity. This check for validity is conceptually illustrated by the dashed lines 394 through 394 with question marks.

Returning to fig. 7, if a wireless interrogation wave has indeed been received at operation 740, then according to another operation 750, the backscattered wave may be wirelessly transmitted by the NFC tag. The backscattered waves may encode access data stored in the tag memory. If the NFC tag requires a password, this backscattering may be configured to occur only when a valid tag password has been sent.

Fig. 6 shows a backscattered wave 695 encoding access data 393 stored in tag memory 392. Thereafter, operations 345, 349 may be performed by the access device 641 and a wave 646 similar to the wave 346 may be transmitted. As described above, wave 646 may encode authentication data 696 and updated program 637.

Returning to fig. 7, only operations 345, 349 are shown to indicate in what order they are performed after operation 750. These operations 345, 349 are shown in dashed lines to indicate that they are not part of flowchart 700.

After operation 750, it may be determined whether the validation data and updated procedures sent by the AWCM have been wirelessly received by the DWCM, according to another operation 760. Otherwise, execution may return to operation 710. As with operation 550, for operation 750, the DWCM may wait only for a limited time for authentication data and new programs to increase security. In such embodiments, the received program can only be stored in the defibrillator memory when it is received by the DWCM before the timeout period expires.

If the answer at operation 750 is yes, then according to another operation 770, it may be determined whether received authentication data has been generated from the backscattered encoded access data. This operation may service the external defibrillator 300 to authenticate the access device 641. (in FIG. 6, this authentication operation is conceptually illustrated with a dashed line from the verification data 696 to the access data 393 with a question mark). As previously described, in some embodiments, the verification data is the same as the access data. In FIG. 7, in operation 770, if the answer is no, execution may return to operation 710.

If at operation 770 the answer is yes, then according to another operation 780 the defibrillator processor stores the received updated program in the defibrillator memory in response to determining that the received verification data has been generated from the backscattered encoded access data and of course in response to the fact that the received updated program was transmitted and received. Such storage may replace the previous program stored therein. (FIG. 6 also shows that updated program 637 of wave 646 is stored in memory 338 in place of previous program 332.) execution may then return to operation 710 to make a second decision, and so on.

In some embodiments, the action data is downloaded and stored in the WCD system for review. Such action data may include: shock/no shock decision; inputs for running programs, such as configuration data; a value of a physiological parameter of the patient that can be sensed by one of the sensors; an identification number that has been assigned to the patient; WCD system status data such as power level of a power supply, etc. In summary, these data may correspond to the history of monitoring and treating the patient. Examples of such downloads are now described in connection with fig. 3, 8 and 9.

Fig. 8 is a diagram of example operations that occur when motion data is downloaded from the external defibrillator 300 of fig. 3. The download may occur from access device 841, which may occur as previously described for access device 341. For example, the access device 841 may be configured to perform the operations 345, 349 previously described. It may also establish communication links 898, 848 similar to communication links 398, 348 over air interface 302.

Fig. 9 shows a flowchart 900 for describing a method according to an embodiment. In accordance with operation 910, the defibrillator processor may run a program in accordance with the stored configuration data to generate a first decision to shock or not shock. At a subsequent time, operation 910 proceeds, a second decision may be made, and so on.

According to another operation 915, motion data may be stored in the defibrillator memory, the motion data relating to at least one of the first decision and an input for running the program.

According to another operation 920, it is determined what the decision of operation 910 is. If the decision is a shock, then according to another operation 930, the discharge circuit may be controlled by the defibrillator processor to discharge the charge as described above. Execution may then return to operation 910.

If at operation 920, it is decided not to shock, according to another operation 940, it is determined whether the NFC tag 391 has received a wireless interrogation wave from an NFC reader. Otherwise, execution may return to operation 910.

The situation where a wireless interrogation wave 844 is indeed received can be seen in fig. 8. As previously described, in some embodiments, the interrogation wave 844 may further encode a tag password 394 of the NFC tag 391. In fact, the tag password (whatever it is) encoded by the interrogation wave 844 will be checked against the tag password 394 stored in the tag memory 392 of the NFC tag 391 to verify validity. This check for validity is conceptually illustrated by the dashed lines 394 through 394 with question marks.

Returning to fig. 9, if a wireless interrogation wave has indeed been received at operation 940, then according to another operation 950, the backscattered wave may be wirelessly transmitted by the NFC tag. The backscattered waves may encode access data stored in the tag memory. If the NFC tag requires a password, this backscattering may be configured to occur only when a valid tag password has been sent.

Fig. 8 shows backscattered wave 895 encoding access data 393 stored in tag memory 392. Thereafter, operations 345, 349 may be performed by access device 841 and wave 846 may be transmitted similar to wave 346. As described above, wave 846 may encode a request for verification data 896 and action data 334.

Returning to FIG. 9, only operations 345, 349 are shown to indicate in what order they are performed after operation 950. These operations 345, 349 are shown in dashed lines to indicate that they are not part of flowchart 900.

After operation 950, in accordance with another operation 960, it may be determined whether the validation data and the request sent by the AWCM have been wirelessly received by the DWCM. Otherwise, execution may return to operation 910. As with operation 550, for operation 950, the DWCM may wait only for a limited time for authentication data and new programs to increase security. In such embodiments, the request can only be accepted if it is received by the DWCM before the timeout period expires.

If the answer at operation 950 is yes, then according to another operation 970, it may be determined whether received authentication data has been generated from the backscattered encoded access data. This operation may service the external defibrillator 300 to authenticate the access device 841. (in FIG. 8, this authentication operation is conceptually illustrated with a dashed line from verification data 896 to access data 393 labeled with a question mark). As previously described, in some embodiments, the verification data is the same as the access data. In FIG. 9, at operation 970, if the answer is no, execution may return to operation 910.

If the answer is yes at operation 970, the DWCM may wirelessly transmit at least a portion of the action data 334 in response to the request and in response to determining that the received authentication data has been generated from the backscattered encoded access data, in accordance with another operation 999. (FIG. 8 also shows a reply wave 899, encoding motion data 334 similar to wave 399.) execution may then return to operation 910, make a second decision, and so on.

The tag memory 392 of the NFC tag 391 may be programmed in different ways. This example approach is now described.

Fig. 10 is a diagram of example elements of an external defibrillator 1000, such as the external defibrillator of fig. 2 and manufactured according to an embodiment. Fig. 10 also shows a trusted NFC reader 1042 that can be used to program the NFC tag 1091 by establishing an RFID communication link 1098.

The external defibrillator 1000 includes a defibrillator housing 1001 containing the elements shown in this example. Defibrillator 1000 thus includes defibrillator processor 1030, defibrillator memory 1038, Defibrillator Wireless Communication Module (DWCM)1090, and NFC tag 1091, all of which may be made as previously described for similar elements of fig. 3. Similarly, the NFC tag 1091 may have a tag memory 1092 that stores the data fetch 1093 and, optionally, also a tag password 1094. Access data 1093 may be needed for accessing DWCM 1090. Additionally, defibrillator memory 1038 can be configured to store at least one program 1032 and configuration data 1033 and action data 1034.

In some embodiments, NFC reader 1042 is an NFC reader of access device 1041, which may be as described for access device 341. In this application, the access device 1041 is used as a programming device. However, in other embodiments, NFC reader 1042 is simply another NFC reader that is used only to become NFC tag 1091 and is independent of access device 1041. For example, the NFC reader 1042 may be a stand-alone device, which is why the access device 1041 is shown in dashed lines in fig. 10.

In such embodiments, NFC reader 1042 may send other wireless interrogation waves encoding the updated tag data. It should be appreciated that this updated tag data may even be the initial tag data intended to be stored in the tag memory 1092. In such embodiments, the NFC tag 1091 may be configured to receive another wireless interrogation wave to decode updated tag data from the other wireless interrogation wave and store the updated tag data in the tag memory 1092. The updated tag data may include access data and/or a tag password that can be stored in place of existing access data and/or a tag password.

Fig. 11 is a diagram of example elements of an external defibrillator 1100, such as the external defibrillator of fig. 2 and manufactured according to an embodiment. Fig. 11 also shows a trusted programming device 1104 that may be used to program NFC tag 1191.

The external defibrillator 1100 includes a defibrillator housing 1101 in which the elements shown in this example are contained. Defibrillator 1100 thus includes defibrillator processor 1130, defibrillator memory 1138, Defibrillator Wireless Communication Module (DWCM)1190, and NFC tag 1191, all of which may be made as previously described with respect to similar elements of fig. 3. Similarly, the NFC tag 1191 may have a tag memory 1192 that stores data 1193 and optionally also a tag password 1194. Access data 1193 may be needed for access to DWCM 1190. Additionally, defibrillator memory 1138 can be configured to store at least one program 1132 and configuration data 1133.

In some embodiments, programming device 1104 is as described for access device 341. The programming device 1104 may include an AWCM 1143, which may be like the AWCM 343. In this way, programming device 1104 can establish a data communication link 1148 with NFC tag 1191. Programming device 1104 may also optionally include an NFC reader and, as such, may establish an optional RFID communication link 1198 with NFC tag 1191.

In such embodiments, the AWCM 1143 may transmit wirelessly updated tag data. The updated tag data may even be the initial tag data intended to be stored in the tag memory 1192. In such embodiments, DWCM 1190 may be further configured to wirelessly receive the transmitted updated tag data from the AWCM. The updated tag data may include access data and/or a tag password that can be stored in the tag memory 1192 in place of the existing access data and/or tag password. More specifically, the defibrillator processor 1130 may also be configured to store the received updated tag data in the tag memory 1192. In some embodiments, the path of the updated tag data for this update operation may be shown in fig. 11 by two arrows 1181, 1182.

Fig. 12 is a diagram of example elements of an external defibrillator 1200, such as the external defibrillator of fig. 2 and manufactured according to an embodiment. The external defibrillator 1200 includes a defibrillator housing 1201 which contains the elements shown in this example. Defibrillator 1200 thus includes defibrillator processor 1230, defibrillator memory 1238, Defibrillator Wireless Communication Module (DWCM)1290, and NFC tag 1291, all of which can be made as previously described for similar elements of fig. 3. Similarly, NFC tag 1291 can have a tag memory 1292 that stores data access 1293 and optionally also a tag password 1294. Access data 1293 may be needed for accessing DWCM 1290. Additionally, the defibrillator memory 1238 can be configured to store at least one program 1232 and configuration data 1233.

The external defibrillator 1200 further includes a service port 1270 in the defibrillator housing 1201. The service port 1270 has a contact node 1272 that is electrically coupled to the defibrillator processor 1230. For example, the service port 1270 may be a port for a USB plug, a port for a serial or parallel cable, or the like. Contact node 1272 may be one of the metal contacts of such a port.

In such embodiments, the updated tag data may be received via the contacts node 1272. The updated tag data may include access data and/or a tag password that can be stored in the tag memory 1292 in place of the existing access data and/or tag password. More specifically, defibrillator processor 1230 may also be configured to store the updated tag data received via contact node 1272 in tag memory 1292. In some embodiments, the path of the updated tag data for this update operation may be shown in fig. 12 with two arrows 1281, 1282. This will prevent malicious users from wirelessly reconfiguring NFC tags in an attempt to use the device for their own purposes.

In some embodiments, the data stored in the tag memory 1392 is only allowed to change through a wired connection through the service port 1272, rather than a wireless connection such as that shown in fig. 10.

In some embodiments, it may be desirable for the external defibrillator to discontinue use of the key (symmetrical or asymmetrical). In this case, the device will be able to update its NFC tag with data encrypted using the new key. The new key may be received wirelessly or by wire from a trusted source or stored in the device as a backup, as shown in one example below.

In some embodiments, the NFC tag may be programmed by data backed up in the defibrillator memory. This can be for the original programming as well as for the case of tag memory corruption. An example is now described.

Fig. 13 is a diagram of example elements of an external defibrillator 1300, such as the external defibrillator of fig. 2 and manufactured according to an embodiment. The external defibrillator 1300 includes a defibrillator housing 1301 that contains the elements as shown in this example. The defibrillator 1300 thus includes a defibrillator processor 1330, a defibrillator memory 1338, a Defibrillator Wireless Communication Module (DWCM)1390, and an NFC tag 1391, all of which can be made as previously described for similar elements of fig. 3. Similarly, NFC tag 1391 may have a tag memory 1392 that stores access data 1393 and, optionally, also a tag password 1394. Access data 1393 may be needed for accessing DWCM 1390. Additionally, defibrillator memory 1338 may be configured to store at least one program 1332, configuration data 1333, and backup data 1335 for backing up NFC tag 1391.

In such embodiments, the defibrillator processor 1330 may also be configured to store the backup data 1335 in the tag memory 1392 that is already stored in the defibrillator memory 1338. In some embodiments, the path of the updated tag data for this update operation may be illustrated in FIG. 13 by two arrows 1381, 1382. This backup data 1335 may include access data and/or a tag password that can be stored in the tag memory 1392 in place of existing access data and/or a tag password.

For such embodiments, backup data 1335 may become stored in defibrillator memory 1338 in a number of ways. In many of these embodiments, the backup data 1335 is thus pre-stored in the defibrillator memory 1338 by the defibrillator processor 1330 via the use of the internally connected arrow 1379. And for these embodiments, the defibrillator processor 1330 may receive the backup data 1335 in a number of ways.

For the first example, DWCM 1390 may be further configured to receive backup data wirelessly, as shown in fig. 11, and defibrillator processor 1330 may receive backup data 1335 therefrom according to a path similar to that shown by arrow 1181. From there, the backup data 1335 will be stored in the defibrillator memory 1338 via arrow 1379.

For a second example, the external defibrillator 1300 may have a service port (not shown) in its housing 1301 similar to the service port 1270 of fig. 12, with contact nodes similar to the contact nodes 1272. In this second example, the defibrillator processor 1330 may be further configured to receive the backup data 1335 via the contact nodes according to a path similar to that shown by arrow 1182. From there, the backup data 1335 will be stored in the defibrillator memory 1338 via arrow 1379.

In the above method, each operation may be performed as an affirmative step to be performed, or cause something to occur that is stated to be able to occur. Such may occur through the entire system or device or simply one or more components thereof. It will be appreciated that the methods and operations may be implemented in numerous ways, including using the systems, devices, and embodiments described above. Further, the order of operations is not limited to that shown, and different orders are possible according to different embodiments. Examples of such alternate ordering may include overlapping, interleaving, interrupting, reordering, adding, preparing, complementing, synchronizing, reversing, or other different ordering, unless the context dictates otherwise. Further, in some embodiments, new operations may be added, or separate operations may be modified or deleted. The added operations may be, for example, operations referred to primarily from describing different systems, apparatus, devices, or methods.

Those skilled in the art will be able to practice the invention in light of the present specification as a whole. The detailed information is included to provide a thorough understanding. In other instances, well-known aspects have not been described in order not to unnecessarily obscure the description. Furthermore, any reference to any prior art in this specification is not, and should not be taken as, an acknowledgment or any form of suggestion that such prior art forms part of the common general knowledge in any country or any field.

This description includes one or more examples, but this fact does not limit how the invention may be implemented. Indeed, the examples, versions or embodiments of the invention may be implemented in accordance with what is described or in varying ways, and with other present or future technologies as well. Other such embodiments include combinations and subcombinations of the features described herein, including, for example, embodiments equivalent to the following: features are provided or applied in a different order than described in the embodiments; extracting a single feature from one embodiment and inserting the feature into another embodiment; removing one or more features from an embodiment; or removing features from an embodiment and adding features extracted from another embodiment while providing features incorporated in such combinations and subcombinations.

As used herein, the phrase "configured to" and/or "to be configured to" refers to one or more actual states of construction and/or configuration that substantially correlate to the physical characteristics of the elements or features preceding those phrases, and thus far beyond merely describing the intended use. Any such elements or features may be implemented in a variety of ways, beyond any examples shown in this document, as would be apparent to one of ordinary skill in the art upon reading this disclosure.

Patent applications, whether any and all parents, grandparents, great grandparents, etc., mentioned in this document or in the application data sheet ("ADS") of this patent application, are incorporated by reference herein as originally published, including any priority claims made in those applications and any material incorporated by reference, provided that such subject matter is not inconsistent herewith.

In this specification, a single reference numeral may be used consistently to refer to a single item, aspect, element or process. Moreover, further efforts may be made in the drafting of this specification to use similar but not identical reference numerals to denote other versions or embodiments of the same or at least similar or related items, aspects, elements or processes. Such further effort is not required, but nonetheless is unnecessary in order to expedite the understanding of the reader, where not required. Even if made in this document, such further effort might not be entirely consistent across all versions or embodiments that might be realized by the present specification. Thus, the description controls when items, aspects, elements or processes are defined other than their reference numerals. Any similarity in reference numerals may be used to infer similarity in text, rather than to obfuscate text or other contextually indicated aspects.

The disclosure, which may be referred to elsewhere as "3330.2," is intended to be illustrative and not limiting as to the scope of the appended claims. The claims herein define certain combinations and subcombinations of elements, features and steps or operations that are regarded as novel and nonobvious. Other claims may be presented in this or a related document for other such combinations and subcombinations. These claims are intended to include within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. The terms used herein, including in the claims, are generally intended as "open" terms. For example, the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," and the like. If a particular number is attributed to a claim recitation, that number is the minimum value, but not the maximum value, unless otherwise specified. For example, when the claims recite "a" or "an" item, it means that it can have one or more of the elements or items.

The claimed invention may be better understood in view of the embodiments described and illustrated in this disclosure. However, the attentive reader will note that some aspects of the disclosed embodiments extend beyond the scope of the claims of this document. To the extent that such aspects do not depart from the scope of the claims in this document, they are to be considered as additional background information for the purpose of facilitating a better understanding of the invention, and not as an admission that the invention itself is entitled to the same purpose. However, these aspects may constitute the definition of the invention itself for another related document.

Claims (30)

1. A Wearable Cardioverter Defibrillator (WCD) system configured to wirelessly exchange data with an access device different from the WCD system, the access device including a Near Field Communication (NFC) reader, a peripheral processor, and an Access Wireless Communication Module (AWCM), the WCD system comprising:

a support structure configured to be worn by a patient;

a power source;

an energy storage module configured to be charged from the power source so as to store an electrical charge;

a discharge circuit coupled to the energy storage module, the discharge circuit controllable to wear the support structure on the patient while discharging the stored charge through the patient;

a defibrillator memory configured to store a program;

a defibrillator processor;

an NFC tag having a tag memory in which access data is stored, the NFC tag configured to receive a wireless interrogation wave from the NFC reader, the NFC tag further configured to wirelessly transmit a backscattered wave in response to the received interrogation wave reader, the backscattered wave encoding the access data, wherein the NFC reader of the access device is capable of receiving the backscattered wave, a peripheral processor of the access device is capable of generating verification data from the encoded access data, and the AWCM is capable of transmitting the verification data and configuration data; and

a Defibrillator Wireless Communication Module (DWCM) cooperating with the defibrillator processor, the DWCM configured to wirelessly receive verification data and configuration data transmitted by the AWCM, wherein:

the defibrillator processor is configured to generate the received verification data to store the received configuration data in the defibrillator memory in response to determining that the backscattered encoded access data has been received from the memory; and is

The defibrillator processor thus becomes configured to run the stored program in accordance with the stored configuration data to generate a certain decision to shock or not shock, and to control the discharge circuit to discharge the charge in response to the certain decision to shock.

2. The WCD system of claim 1, wherein:

the access device is disposed in a peripheral housing; and is

The peripheral housing is at a distance of at most 10 "from the NFC tag when the NFC tag receives the wireless interrogation waves from the NFC reader and wirelessly transmits the backscattered waves.

3. The WCD system of claim 1, wherein the authentication data comprises access data or a hash of access data.

4. The WCD system of claim 1, wherein the authentication data comprises a network address of the DWCM.

5. The WCD system of claim 1, wherein the backscattered encoded access data is encrypted.

6. The WCD system of claim 1, wherein:

the tag memory is further configured to store a tag password; and is

The NFC tag is further configured not to backscatter the encoded access data unless the interrogation wave also encodes the tag password.

7. The WCD system of claim 6, wherein:

the WCD system has been assigned a serial number; and is

The tag password is or is related to the serial number.

8. The WCD system of claim 1, wherein:

the DWCM has been assigned a network address; and is

The DWCM does not send the network address in response to the AWCM's query signal.

9. The WCD system of claim 1, wherein:

the defibrillator memory further storing previous configuration data prior to receiving the verification data; and is

The defibrillator processor is configured to run the program in accordance with the stored configuration data to generate a certain decision to shock or not shock, and to control the discharge circuit to discharge the charge in response to the certain decision to shock.

10. The WCD system of claim 1, wherein the received configuration data is storable in the defibrillator memory only when received by the DWCM before expiration of a timeout period after transmission of the backscatter wave.

11. The WCD system of claim 1, wherein the NFC tag is further configured to receive another wireless interrogation wave from another NFC reader, to decode updated tag data from the other wireless interrogation wave, and to store the updated tag data in the tag memory in place of the access data.

12. The WCD system of claim 1, wherein the NFC tag is further configured to receive another wireless interrogation wave from the NFC reader, to decode updated tag data from the other wireless interrogation wave, and to store the updated tag data in the tag memory in place of the access data.

13. The WCD system of claim 1, wherein:

the DWCM further configured to wirelessly receive updated tag data from the AWCM; and is

The defibrillator processor is further configured to store the updated tag data in the tag memory in place of the access data.

14. The WCD system of claim 1, further comprising:

a defibrillator housing, the defibrillator processor and the NFC tag being located within the defibrillator housing; and

a service port in the defibrillator housing having a contact node electrically coupled with the defibrillator processor, and wherein the defibrillator processor is further configured to store updated tag data received via the contact node in the tag memory in place of the access data.

15. The WCD system of claim 1, wherein:

the defibrillator memory is further configured to store backup data; and is

The defibrillator processor is further configured to store the backscatter data already stored in the defibrillator memory in the tag memory in place of the access data.

16. The WCD system of claim 15, wherein the DWCM is further configured to wirelessly receive backup data capable of being stored in the defibrillator memory.

17. The WCD system of claim 15, further comprising:

a defibrillator housing, the defibrillator processor and the NFC tag being located within the defibrillator housing; and

a service port in the defibrillator housing having a contact node electrically coupled with the defibrillator processor, and wherein the defibrillator processor is further configured to receive backup data storable in the defibrillator memory via the contact node.

18. A non-transitory computer readable storage medium storing one or more programs which, when executed by at least one defibrillator processor of a Wearable Cardioverter Defibrillator (WCD) system, the Wearable Cardioverter Defibrillator (WCD) system configured to wirelessly exchange data with an access device different from the WCD system, the access device including a Near Field Communication (NFC) reader, a peripheral processor, and an Access Wireless Communication Module (AWCM), the WCD system comprising:

a support structure configured to be worn by a patient;

a power source;

an energy storage module configured to be charged from the power source so as to store an electrical charge;

a discharge circuit coupled to the energy storage module, the discharge circuit controllable to wear the support structure on the patient while discharging the electrical charge through the patient;

a defibrillator memory configured to store a program and configuration data;

a defibrillator processor;

an NFC tag having a tag memory in which access data is stored; and

a Defibrillator Wireless Communication Module (DWCM), the one or more programs resulting in operations comprising:

the defibrillator processor executing the stored program in accordance with the stored configuration data to generate a first decision to shock or not shock;

the defibrillator processor controlling the discharge circuit to discharge the charge in response to a first determination of a shock;

the NFC tag then receives a wireless interrogation wave from the NFC reader;

the NFC tag then wirelessly transmits backscattered waves encoding the access data in response to the received wireless interrogation waves, wherein the backscattered waves are receivable by an NFC reader of the access device, authentication data is generated from the encoded access data by a peripheral processor of the access device, and the AWCM is capable of transmitting the authentication data and updated configuration data;

the DWCM then wirelessly receives the validation data and updated configuration data sent by the AWCM;

determining whether the received validation data has been generated from the backscattered encoded access data;

the defibrillator processor storing the received updated configuration data in the defibrillator memory in place of the configuration data in response to determining that the received verification data has been generated from the backscattered encoded access data;

the defibrillator processor then re-runs the stored program in accordance with the stored configuration data to generate a second decision to shock or not shock; and is

The defibrillator processor controls the discharge circuit to discharge the stored charge in response to a second determination of a shock.

19. The medium of claim 18, wherein the authentication data comprises access data or a hash of access data.

20. The medium of claim 18, wherein the validation data comprises a network address of the DWCM.

21. The medium of claim 18, wherein the backscattered encoded access data is encrypted.

22. The medium of claim 18, wherein:

the tag memory further stores a tag password; and is

The NFC tag does not backscatter the encoded access data unless the interrogation wave also encodes the tag password.

23. The medium of claim 22, wherein:

the WCD system has been assigned a serial number; and is

The tag password is or is related to the serial number.

24. The medium of claim 18, wherein:

the DWCM has been assigned a network address, and

the DWCM does not send the network address in response to the AWCM's query signal.

25. The medium of claim 18, wherein the received configuration data can be stored in the defibrillator memory only when received by the DWCM before expiration of a timeout period after transmission of the backscatter wave.

26. The medium of claim 18, wherein the NFC tag further receives another wireless interrogation wave from another NFC reader, decodes updated tag data from the other wireless interrogation wave, and stores the updated tag data in the tag memory in place of the access data.

27. The medium of claim 18, wherein the NFC tag further receives another wireless interrogation wave from the NFC reader, decodes updated tag data from the other wireless interrogation wave, and stores the updated tag data in the tag memory in place of the access data.

28. The medium of claim 18, wherein:

the DWCM further wirelessly receiving updated tag data from the AWCM; and is

The defibrillator processor further stores the updated tag data in the tag memory in place of the access data.

29. The medium of claim 18, wherein:

the defibrillator memory further stores backup data; and is

The defibrillator processor further stores backscatter data already stored in the defibrillator memory in the tag memory in place of the access data.

30. The medium of claim 29, wherein the DWCM further wirelessly receives backup data stored in the defibrillator memory.

Images