Emergency assistance response

PRIORITY INFORMATION

0001This application is a Non-Provisional Application of U.S. Provisional Application No. 63/128,931, filed Dec. 22, 2020, the contents of which are herein incorporated by reference.

TECHNICAL FIELD

0002The present disclosure relates generally to apparatuses, non-transitory machine-readable media, and methods associated with emergency assistance response.

BACKGROUND

0003Memory resources are typically provided as internal, semiconductor, integrated circuits in computers or other electronic systems. There are many different types of memory, including volatile and non-volatile memory. Volatile memory can require power to maintain its data (e.g., host data, error data, etc.). Volatile memory can include random access memory (RAM), dynamic random-access memory (DRAM), static random-access memory (SRAM), synchronous dynamic random-access memory (SDRAM), and thyristor random access memory (TRAM), among other types. Non-volatile memory can provide persistent data by retaining stored data when not powered. Non-volatile memory can include NAND flash memory, NOR flash memory, and resistance variable memory, such as phase change random access memory (PCRAM) and resistive random-access memory (RRAM), ferroelectric random-access memory (FeRAM), and magnetoresistive random access memory (MRAM), such as spin torque transfer random access memory (STT RAM), among other types.

0004Electronic systems often include a number of processing resources (e.g., one or more processing resources), which may retrieve instructions from a suitable location and execute the instructions and/or store results of the executed instructions to a suitable location (e.g., the memory resources). A processing resource can include a number of functional units such as arithmetic logic unit (ALU) circuitry, floating point unit (FPU) circuitry, and a combinatorial logic block, for example, which can be used to execute instructions by performing logical operations such as AND, OR, NOT, NAND, NOR, and XOR, and invert (e.g., NOT) logical operations on data (e.g., one or more operands). For example, functional unit circuitry may be used to perform arithmetic operations such as addition, subtraction, multiplication, and division on operands via a number of operations.

BRIEF DESCRIPTION OF THE DRAWINGS

0005<figref idref="DRAWINGS">FIG. 1</figref> is a diagram representing an example system for emergency assistance response in accordance with a number of embodiments of the present disclosure.

0006<figref idref="DRAWINGS">FIGS. 2A-2C</figref> are flow diagrams representing example methods for emergency assistance response in accordance with a number of embodiments of the present disclosure.

0007<figref idref="DRAWINGS">FIG. 3</figref> is a functional diagram representing a wearable device and a processing resource in communication with a memory resource having instructions written thereon in accordance with a number of embodiments of the present disclosure.

0008<figref idref="DRAWINGS">FIG. 4</figref> is another diagram representing an example system for emergency assistance response including a wearable device and processing resources in communication with memory resources in accordance with a number of embodiments of the present disclosure.

0009<figref idref="DRAWINGS">FIG. 5</figref> is another flow diagram representing an example method for emergency assistance response in accordance with a number of embodiments of the present disclosure.

DETAILED DESCRIPTION

0010Apparatuses, machine-readable media, and methods related to monitoring health data and associated emergency assistance responses are described. Health related events can occur at any time. For instance, falls, blood glucose level spikes, blood pressure issues, etc. may occur when someone is alone or unable to get to a telephone. Some alert systems allow for a user to push a button and reach emergency services if the user needs help. However, such systems may not allow for automatic alerts (e.g., with little or no user interaction), tracking of health events, or communication with other health monitoring sensors, such as blood glucose monitors, heartrate monitors, or blood pressure monitors, among others.

0011Examples of the present disclosure can utilize a wearable device that is in communication with a control center, an application (e.g., an application downloaded on a mobile device or other computing device), a health data sensor, other devices (e.g., mobile devices of emergency contacts), a cloud storage service, or any combination thereof to work together as an emergency assistance response system to appropriately respond to an emergency or potential emergency. For instance, a wearer of the wearable device may experience an emergency, and the emergency assistance response system can determine an appropriate response.

0012Examples of the present disclosure can include a system comprising a non-transitory machine-readable medium comprising a first processing resource in communication with a memory resource having instructions executable to receive, at the first processing resource, first signaling from a second processing resource configured to monitor health data and track, at the first processing resource, the received first signaling. The instructions can be executable to identify, at the first processing resource or a different, third processing resource, output data representative of abnormal health data based on the tracked received first signaling and transmit the output data to a fourth processing resource of a wearable device.

0013The system can include the wearable device comprising the fourth processing resource to receive, at the fourth processing resource, the output data representative of the abnormal health data, provide a prompt via a user interface to a wearer of the wearable device associated with the abnormal health data, determine a response to the abnormal health data based on a reply or non-reply from the wearer via the user interface, and transmit the response to the first processing resource.

0014In the following detailed description of the present disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how one or more embodiments of the disclosure can be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the embodiments of this disclosure, and it is to be understood that other embodiments can be utilized and that process, electrical, and structural changes can be made without departing from the scope of the present disclosure.

0015It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” can include both singular and plural referents, unless the context clearly dictates otherwise. In addition, “a number of,” “at least one,” and “one or more” (e.g., a number of memory devices) can refer to one or more memory devices, whereas a “plurality of” is intended to refer to more than one of such things. Furthermore, the words “can” and “may” are used throughout this application in a permissive sense (i.e., having the potential to, being able to), not in a mandatory sense (i.e., must). The term “include,” and derivations thereof, means “including, but not limited to.” The terms “coupled,” and “coupling” mean to be directly or indirectly connected physically or for access to and movement (transmission) of commands and/or data, as appropriate to the context.

0016The figures herein follow a numbering convention in which the first digit or digits correspond to the figure number and the remaining digits identify an element or component in the figure. Similar elements or components between different figures can be identified by the use of similar digits. For example, <b>110</b> can reference element “<b>10</b>” in <figref idref="DRAWINGS">FIG. 1</figref>, and a similar element can be referenced as <b>310</b> in <figref idref="DRAWINGS">FIG. 3</figref>. As will be appreciated, elements shown in the various embodiments herein can be added, exchanged, and/or eliminated so as to provide a number of additional embodiments of the present disclosure. In addition, the proportion and/or the relative scale of the elements provided in the figures are intended to illustrate certain embodiments of the present disclosure and should not be taken in a limiting sense.

0017<figref idref="DRAWINGS">FIG. 1</figref> is a diagram representing an example system <b>100</b> for emergency assistance response in accordance with a number of embodiments of the present disclosure. The system <b>100</b> can include a cloud storage service <b>102</b>, an application <b>104</b>, such as an application downloaded on a mobile device or associated with a website, a sensor <b>106</b>, a monitoring center <b>108</b>, and a wearable device <b>110</b>. While one sensor <b>106</b> is illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, more or fewer sensors may be a part of the system <b>100</b>.

0018The cloud storage service <b>102</b> can include cloud storage that allows a user (e.g., a wearer of the wearable device) to save data securely online so that it can be accessed anytime from any location and shared with those who are granted permission. The cloud storage service <b>102</b> may also allow a user to back up data to facilitate recovery off-site. The cloud storage service <b>102</b> can be in communication with the wearable device <b>110</b> and the application <b>104</b>, which can also be in communication with one another.

0019The wearable device <b>110</b> can include, but is not limited to, a watch, a necklace, a ring, a wearable monitor, pendant, waterproof device, or other device that may be wearable. The wearable device <b>110</b> can include a processing resource in communication with a memory device to execute instructions. For instance, a wearer may fall and push a button on the wearable device <b>110</b> to call for help. The processing resource of the wearable device <b>110</b> can receive this request, write it the memory resource and communicate the request the application <b>104</b> and/or the monitoring center <b>108</b>. The wearable device <b>110</b> can also transmit data to the cloud storage service <b>102</b> for storage and/or later retrieval. The wearable device <b>110</b> can also receive data from the sensor <b>106</b>, which will be discussed further herein. In some examples, the wearable device <b>110</b> can include geolocation services (e.g., global positioning services (GPS)), such that the wearable device <b>110</b> can be located by a third party (e.g., for deployment of emergency services).

0020The application <b>104</b> may be a mobile application, website application, or desktop application and may include a computer program or software application designed to run on a mobile device or other computing device. The application <b>104</b> can receive data from the sensor <b>106</b>, as will be discussed further herein, as well as sharing data with the wearable device <b>110</b>, the monitoring center <b>108</b>, and the cloud storage service <b>102</b>. In some examples, the application <b>104</b> can be accessed via a user device, and data may be manually input. For instance, a user may input a desired ambulance service, insurance information, allergies, etc., such that the data is available to the monitoring center to aid in decision making for an emergency assistance response decision for or with the user.

0021The monitoring center <b>108</b> can be a staffed monitoring center (e.g., staffed 24 hours per day, 7 days per week) to receive communications from the wearable device <b>110</b> and/or the application <b>104</b>. For instance, a user who falls while wearing the wearable device <b>110</b> may press a button that calls the monitoring center <b>108</b>, or the application <b>104</b> may receive an indication from the wearable device <b>110</b> that the user has fallen and notify the monitoring center <b>108</b>. In some examples, the monitoring center <b>108</b> can include a non-transitory machine-readable medium comprising a processing resource in communication with a memory resource having instructions executable to receive communication from the wearable device <b>110</b>, the application <b>104</b>, or both. Decisions at the monitoring center <b>108</b> may be made by trained responders, at the non-transitory machine-readable medium, or a combination thereof.

0022The sensor <b>106</b> can include a sensor to monitor health data. Examples may include, but are not limited to, heartrate monitors, blood pressure monitors, glucose monitors, oxygen level monitors, kidney function monitors, respiratory monitors, insulin pumps, or temperature sensors, among others. The sensor <b>106</b> can communicate collected data to the application <b>104</b>, the wearable device <b>110</b>, or both. For instance, if the sensor <b>106</b> detects an abnormal heartrate, an alert may be sent to the wearable device <b>110</b> to alert the wearer, and the data may also be sent to the application <b>104</b> for tracking. In some examples, the data can be transmitted from the wearable device <b>110</b> or the application <b>104</b> to the cloud storage service <b>102</b> for further storage. In some examples, the wearable device <b>110</b> can include a sensor on the wearable device (e.g., a built-in heartrate monitor, a temperature sensor, etc.).

0023<figref idref="DRAWINGS">FIGS. 2A-2C</figref> are flow diagrams representing example methods for emergency assistance response in accordance with a number of embodiments of the present disclosure. <figref idref="DRAWINGS">FIG. 2A</figref> illustrates an example method flow in which a wearer of a wearable device, such as the wearable device <b>110</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref> falls and presses a button on the wearable device to connect to a monitoring center, such as the monitoring center <b>108</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref>.

0024At <b>211</b>, the wearer falls, and at <b>212</b>, the wearer activates an emergency assistance response. This can include pushing a button, tapping something on a user interface of the wearable device, or some other triggering of a particular input on the wearable device. At <b>213</b>, the wearer is connected to the monitoring center.

0025A responder at the monitoring center may speak or send a message to the wearer via the wearable device requesting a response. The responder may be a human responder, a program such as a trained machine learning model (e.g., artificial intelligence (AI)), or a combination thereof. If, at <b>214</b>, the wearer is able to respond to the responder, for instance via voice or messaging via the wearable device, the responder can evaluate at <b>219</b> whether a professional emergency service is needed. For instance, if the responder determines the wearer has broken his or her leg, an evaluation may indicate an ambulance is necessary.

0026If, at <b>219</b>, it is determined professional emergency services are needed, such emergency services can be dispatched at <b>222</b>. For instance, the responder can send an ambulance to the location of the wearer using the geolocation services of the wearable device or based on information provided by the wearer. In addition, at <b>223</b>, a family member and/or emergency contact can be contacted and provided with appropriate information. For instance, family members and/or emergency contacts, along with their contact information, can be entered into the application and made available to responders when an emergency assistance request is made. At <b>221</b>, the fall can be tracked, recorded, and saved at the application and/or the cloud storage service for future reference.

0027If, at <b>219</b>, it is determined emergency services are not needed, a family member and/or emergency contact may still be contacted at <b>220</b>. For instance, if it is determined that the wearer has fallen and twisted his or her ankle, but is otherwise okay, the responder can contact one or more predetermined emergency contacts (e.g., pre-loaded into the application) and make him or her aware of the situation. Again, at <b>221</b>, the fall can be tracked, recorded, and saved at the application and/or the cloud storage service for future reference.

0028If, at <b>214</b>, it is determined that the wearer cannot respond, the responder can attempt, at <b>215</b>, to call or communicate with the wearer via his or her personal phone or other device (e.g., mobile phone, landline, tablet with messaging, etc.). If, at <b>216</b>, the wearer responds (e.g., answers a phone call), the method returns to <b>219</b> for an evaluation of the situation. If, at <b>216</b>, the wearer does not respond, emergency contacts can be notified at <b>217</b>. If, at <b>218</b>, the emergency contacts are reached, the method returns to <b>219</b> for evaluation. If, at <b>218</b>, the emergency contacts are not reachable, the fall history is recorded at <b>221</b>. In such instances, emergency services may be dispatched to the location of the wearer, for instance, at <b>222</b>.

0029<figref idref="DRAWINGS">FIG. 2B</figref> illustrates an example method flow in which a wearer of a wearable device, such as the wearable device <b>110</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref>, falls and an automatic emergency assistance response commences. At <b>224</b>, the wearer falls, and at <b>225</b> the wearable device provides an alarm, prompt, or other notification to the wearer. For instance, the alarm, prompt, or other notification may include an audible alarm or notification, a vibration, a notification or prompt via a user interface of the wearable device, or a voice call via the wearable device or an associated mobile device. The alarm, prompt, or other notification can request confirmation from the wearer regarding whether he or she needs emergency assistance.

0030At <b>228</b>, no action is taken if the wearer provides confirmation that he or she does not need emergency assistance. For instance, no emergency services are deployed, no emergency contacts are notified, and the alarm, prompt, or other notification is disabled. At <b>230</b>, the wearable device automatically (e.g., with little or no user interaction) contacts emergency services (e.g., calls <b>911</b>) if the wearer positively confirms in response to the alarm, prompt, or other notification that he or she needs emergency services.

0031If, at <b>226</b>, the wearer does not deactivate the alarm, prompt, or other notification and/or the wearable device detects or senses the wearer is immobile (e.g., via sensors in/on or in communication with the wearable device), the method also proceeds to <b>230</b>, where emergency services are automatically contacted (e.g., via the wearable device or the application). For instance, if the wearer does not deactivate the alarm, prompt, or other notification within a threshold time period (e.g., one minute), and a sensor of the wearable device determines the wearable device is immobile emergency services are automatically contacted at <b>230</b> (e.g., “911” is called). In some examples, the alarm, prompt, or other notification may be deactivated within the threshold time period, and the wearer may indicate he or she does not need help. In such an example, no action is taken at <b>228</b>. In some instances, the alarm, prompt, or other notification may be deactivated within the threshold time period, but the user may indicate he or she does need help. In such an example, emergency services can be contacted at <b>230</b>.

0032At <b>231</b>, family members and emergency contacts are notified, and at <b>232</b>, the fall history is recorded, for instance at a cloud storage service. While a fall is described with respect to <figref idref="DRAWINGS">FIGS. 2A and 2B</figref>, other incidents may result in a user triggering an input of the wearable device or an automatic response.

0033<figref idref="DRAWINGS">FIG. 2C</figref> illustrates an example in which a wearer of a wearable device, such as the wearable device <b>110</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref> suffers an abnormal health event detected by a sensor such as the sensor <b>106</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref>. The example illustrated in <figref idref="DRAWINGS">FIG. 2C</figref> includes the use of a single sensor, in this example a glucose monitor, but more than one sensor may be present, and different types of sensors may be present (e.g., heartrate monitor, oxygen level monitor, etc.).

0034At <b>234</b>, a sensor detects that an abnormal health event has occurred, in this example, a blood glucose level falling outside of a normal, threshold range. At <b>235</b>, a wearer of a wearable device is alerted. In addition, a family member or emergency contact may also be notified. For instance, family members or emergency contacts may be added, along with their contact information, via an application in communication with the wearable device. At <b>235</b>, the wearer and the family member or emergency contact can be prompted for a response regarding whether or not he or she needs emergency assistance.

0035If, at <b>236</b>, the wearer dismisses the alert within a threshold time period, for instance he or she swipes away a notification within eight hours, no action is taken at <b>237</b>. At <b>236</b>, the wearer's dismissal may act as the confirmation that no help is requested, or a separate confirmation can be received at the wearable device that the wearer does not need emergency assistance. At <b>245</b>, the abnormal health data (e.g., high glucose level) is recorded and stored, for instance at a cloud storage service in communication with the wearable device and/or application.

0036If, at <b>238</b>, the wearer dismisses the alert within the threshold time, but also indicates that emergency assistance is needed, emergency services can be dispatched at <b>249</b>. For instance, a responder at a monitoring center, whether a person, a machine learning model, or a combination thereof, can dispatch emergency services to a location of the wearable device based on communication from the wearer and/or geolocation services on the wearable device. At <b>250</b>, the family or emergency contacts can be notified, and at <b>245</b>, the abnormal health data and response can be tracked and stored, for instance with a cloud storage service.

0037At <b>239</b>, if the wearable device does not receive input from the wearer in response to the alert provided at <b>235</b> (e.g., the wearer does not dismiss the alert), an alarm or other notification can be transmitted, at <b>240</b>, to the wearable device at regular intervals, for instance, every hour for a threshold amount of time. If the wearer responds to one of those reminder alerts, the method proceeds to either <b>236</b> or <b>238</b>, as appropriate. However, if at <b>241</b>, the wearer does not dismiss or deactivate the alert after the threshold time period (e.g., 24 hours), the wearer can be connected to the monitoring center at <b>242</b>. For instance, a staffed or unstaffed (e.g., using machine learning models) monitoring center can be alerted, and at <b>243</b>, a user device associated with the wearable device can be contacted at <b>243</b>. For instance, a personal phone number provided previously via the application can be called or a text message can be sent.

0038If, at <b>244</b>, the wearer answers his or her phone, responds to a text, etc., a responder at the monitoring center can evaluate whether a professional emergency service is needed at <b>246</b>. For instance, based on the abnormal health data, event history tracked and stored in the cloud storage service, and a conversation with the wearer, it may be determined that no emergency assistance is necessary. In such an example, the abnormal health data and response is tracked and stored at <b>245</b>. If, however, at <b>246</b>, it is determined that emergency assistance is needed, emergency services can be dispatched to the wearer's location at <b>249</b>, a family member or emergency contact can be notified at <b>250</b>, and the abnormal health data and response can be tracked and stored at <b>245</b>.

0039If, at <b>244</b>, the wearer does not answer his or her phone, responds to a text, etc., a responder at the monitoring center can contact the family member or emergency contact at <b>248</b>. If, at <b>247</b>, the family member or emergency contact is reached, the method can proceed to evaluation of whether professional emergency services are needed at <b>246</b>. If, at <b>247</b>, the family member or emergency contact cannot be reached, the method can proceed to dispatch of emergency services to a location of the wearer (e.g., a location of the wearable device based on geolocation services) at <b>249</b>.

0040<figref idref="DRAWINGS">FIG. 3</figref> is a functional diagram representing a wearable device <b>310</b> and a processing resource <b>354</b> in communication with a memory resource <b>356</b> having instructions <b>358</b>, <b>360</b>, <b>362</b>, <b>364</b> written thereon in accordance with a number of embodiments of the present disclosure. In some examples, the processing resource <b>354</b> and memory resource <b>356</b> comprise a first system <b>352</b>, and together with wearable device <b>310</b>, comprise a second system <b>353</b>. The second system <b>353</b>, in some examples, may include more or fewer elements including, for instance, a cloud storage service, a monitoring center, and/or a sensor. For example, the system <b>353</b> may be analogous or similar to the system <b>100</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref>.

0041The first system <b>352</b> illustrated in <figref idref="DRAWINGS">FIG. 3</figref> can be a server or a computing device (among others) and can include the processing resource <b>354</b>. The system <b>352</b> can further include the memory resource <b>356</b> (e.g., a non-transitory MRM), on which may be stored instructions, such as instructions <b>358</b>, <b>360</b>, <b>362</b>, <b>364</b>. Although the following descriptions refer to a processing resource and a memory resource, the descriptions may also apply to a system with multiple processing resources and multiple memory resources. In such examples, the instructions may be distributed (e.g., stored) across multiple memory resources and the instructions may be distributed (e.g., executed by) across multiple processing resources. In some examples, the first system <b>352</b> can comprise a mobile, website, or desktop application.

0042The memory resource <b>356</b> may be an electronic, magnetic, optical, or other physical storage device that stores executable instructions. Thus, the memory resource <b>356</b> may be, for example, non-volatile or volatile memory. For example, non-volatile memory can provide persistent data by retaining written data when not powered, and non-volatile memory types can include NAND flash memory, NOR flash memory, read only memory (ROM), Electrically Erasable Programmable ROM (EEPROM), Erasable Programmable ROM (EPROM), and Storage Class Memory (SCM) that can include resistance variable memory, such as phase change random access memory (PCRAM), three-dimensional cross-point memory, resistive random access memory (RRAM), ferroelectric random access memory (FeRAM), magnetoresistive random access memory (MRAM), and programmable conductive memory, among other types of memory. Volatile memory can require power to maintain its data and can include random-access memory (RAM), dynamic random-access memory (DRAM), and static random-access memory (SRAM), among others.

0043In some examples, the memory resource <b>356</b> is a non-transitory MRM comprising Random Access Memory (RAM), an Electrically-Erasable Programmable ROM (EEPROM), a storage drive, an optical disc, and the like. The memory resource <b>356</b> may be disposed within a controller and/or computing device. In this example, the executable instructions <b>358</b>, <b>360</b>, <b>362</b>, <b>364</b> can be “installed” on the device. Additionally, and/or alternatively, the memory resource <b>356</b> can be a portable, external or remote storage medium, for example, that allows the system to download the instructions <b>358</b>, <b>360</b>, <b>362</b>, <b>364</b> from the portable/external/remote storage medium. In this situation, the executable instructions may be part of an “installation package”. As described herein, the memory resource <b>356</b> can be encoded with executable instructions for an emergency assistance response.

0044The instructions <b>358</b>, when executed by a processing resource such as the processing resource <b>354</b> (herein after referred to as the “first processing resource <b>354</b>”), can include instructions to receive at the first processing resource <b>354</b>, first signaling from a second processing resource configured to monitor health data. For instance, the second processing resource can comprise a sensor communicatively coupled to the wearable device <b>310</b> and the non-transitory machine readable medium <b>356</b> to monitor the health data of a wearer of the wearable device <b>310</b>. For instance, the sensor can include a heartrate monitor, glucose monitor, or other health data monitor that can transmit a notification to the wearable device <b>310</b> or an application <b>352</b> in communication with the sensor and the wearable device <b>310</b>. For instance, the second processing resource of the sensor can transmit the first signaling to the first processing resource and a fourth processing resource of the wearable device <b>310</b>.

0045The instructions <b>360</b>, when executed by a processing resource such as the first processing resource <b>354</b>, can include instructions to track, at the first processing resource <b>354</b>, the received first signaling. For instance, if a wearer receives health data at the first processing resource <b>354</b>, such received data can be tracked via the application and/or tracked and stored in a cloud computing service coupled to the application and wearable device. Tracking the health data may allow for pattern recognition of abnormal health data or events and may be useful to a responder when determining an emergency assistance response.

0046The instructions <b>361</b>, when executed by a processing resource such as the first processing resource <b>354</b>, can include instructions to identify, at the first processing resource or a different, third processing resource, output data representative of abnormal health data based on the tracked received first signaling. For instance, if the received health data indicates an elevated heartrate or abnormal (e.g., above threshold) glucose level, the output data can include an alert to transmit to the wearable device indicating emergency assistance may be needed.

0047For instance, the instructions <b>364</b>, when executed by a processing resource such as the first processing resource <b>354</b>, can include instructions to transmit the output data to a fourth processing resource of a wearable device. A prompt, alarm, or other alert can be transmitted to the wearable device for input from the wearer to determine whether emergency assistance is needed or requested based on the abnormal health data.

0048The wearable device <b>310</b> can receive, at the fourth processing resource, the output data representative of the abnormal health data. The output data may present itself as a badge on a wearable device, an audible alarm, a physical notification, etc. For instance, the wearable device <b>310</b> can provide a prompt via a user interface to a wearer of the wearable device <b>310</b> associated with the abnormal health data. For instance, the wearable device <b>310</b> may audibly ask the wearer if he or she needs emergency assistance, or a badge may be presented for the wearer to ignore, engage, or dismiss. In some examples, additional information may be requested from the user via the wearable device <b>310</b>. For instance, the wearer may be prompted via the user interface.

0049A determination, for instance, via the fourth processing resource of the wearable device <b>354</b> or the application, can be made with respect to a response to the abnormal health data based on a reply or non-reply from the wearer via the user interface. For instance, it can be determined that the response is a request for help in response to the reply including confirmation of the request for help within a threshold period of time. For instance, a wearer may press a confirmation button or badge, or he or she may provide verbal confirmation that help is requested/needed.

0050In some instances, it can be determined that the response is not a request for help in response to the reply including confirmation, within the threshold period of time, that no action is requested. For example, a wearer may swipe away a badge displayed on a user interface of the wearable device <b>310</b> indicating her or she is not requesting help, or the wearer may reply by voice or text that emergency assistance is not requested or needed.

0051The response, in some instances, can be determined to be unknown in response to a non-reply. An unknown response may prompt follow-up alerts to the wearable device <b>310</b> or communication with family or emergency contacts of the wearer. For instance, the wearable device <b>310</b> can provide a follow-up prompt within a predetermined time period and via the user interface of the wearable device <b>310</b> in response to the non-reply. If the wearer responds at that time, an emergency assistance response can be determined based on the wearer's response. In some examples, the wearable device <b>310</b> can determine the response is a request for help if there is another non-reply after the follow-up prompt, or after a threshold time period or number of follow-up prompts. For instance, if after ten prompts, the wearer does not respond, emergency assistance can be sent to the location of the wearer (e.g., based on geolocation services on the wearable device <b>310</b>) and/or family and emergency contacts can be notified. Such contacts may be entered, along with other information such as insurance, preferred hospitals and doctors, etc. via the application.

0052The wearable device <b>310</b> can transmit the response to the first processing resource <b>354</b>. The first processing resource <b>354</b> may execute instructions for tasks or notifications. For instance, when contacting a family member or emergency contact, the first processing resource can transmit the response received from the wearable device <b>310</b> to a fifth processing resource associated with a user device of a family member or an emergency contact of the wearer. In some examples, the first processing resource <b>354</b> to transmit the response received from the wearable device <b>310</b> to a sixth processing resource associated with a monitoring center. For instance, a responder at a monitoring center can aid in an emergency assistance response decision using the health data, tracked and stored health data (e.g., stored with a cloud storage service), and input from the wearer, family, or emergency contacts.

0053<figref idref="DRAWINGS">FIG. 4</figref> is another diagram representing an example system <b>467</b> for emergency assistance response including a wearable device <b>410</b> and processing resources <b>454</b>, <b>466</b>, <b>470</b> in communication with memory resources <b>456</b>, <b>468</b>, <b>472</b> in accordance with a number of embodiments of the present disclosure. The memory resources <b>456</b>, <b>468</b>, <b>472</b> can include instructions thereon that are executable by their respective processing resources <b>454</b>, <b>466</b>, <b>470</b> to perform actions with respect to an emergency assistance response. The system <b>467</b>, in some examples, may be analogous to systems <b>100</b> and/or <b>353</b> described with respect to <figref idref="DRAWINGS">FIGS. 1 and 3</figref>.

0054The wearable device <b>410</b> can include the processing resource <b>454</b> (herein after referred to as the “first processing resource <b>454</b>”) in communication with the memory resource <b>456</b> (herein after referred to as the “first memory resource <b>456</b>”) or other storage. The wearable device <b>410</b> can receive, at the first processing resource <b>454</b>, a request for emergency assistance. This request can include the first processing resource <b>454</b> receiving indication of triggering of a particular input on the wearable device <b>410</b>. For instance, a wearer may push a button on the wearable device <b>410</b> indicating he or she needs help (e.g., emergency assistance).

0055In some examples, the request for emergency assistance comprises detection of, by the first processing resource <b>454</b> or a sensor in communication with the first processing resource <b>454</b>, a health event. For instance, an oxygen level monitor may transmit a low oxygen level to the wearable device <b>410</b> and display the level, an alert, or another notification/query regarding emergency assistance needs. While a low oxygen level is used herein as an example health events, other health events are possible including indications of abnormal health data (e.g., high glucose level, high blood pressure, etc.). In some examples, the wearable device <b>410</b> may have a built-in sensor in communication with the first processing resource <b>454</b> to detect a health event (e.g., a fall sensor, immobility sensor, etc.).

0056The wearable device <b>410</b> can transmit the request to the second processing resource <b>466</b> in communication with the second memory resource <b>468</b> of the non-transitory machine-readable medium <b>408</b>, for instance located at a monitoring center, which can receive the request and route the request to an emergency contact, an emergency service, or both.

0057The non-transitory machine-readable medium <b>404</b> that includes the third processing resource <b>470</b> in communication with the third memory resource <b>472</b> can track the request and an associated response. For instance, the third processing resource <b>470</b> may be associated with a mobile, website, or desktop application in communication with the wearable device and can collect and track health data and events. The application and/or the wearable device <b>410</b> may also transmit health data to a cloud storage service for tracking and/or storage. Tracking the data can be useful for future emergency assistance requests, for instance. In some instances, the wearable device <b>410</b> can transmit the request directly to the third processing resource <b>470</b> for tracking.

0058In some examples, the third processing resource <b>470</b> can receive second signaling from the third processing resource <b>470</b> configured to monitor health data. For instance, a sensor such as the aforementioned oxygen level monitor, may transmit an indication of abnormal health data to the third processing resource <b>470</b> for tracking.

0059In some examples, the non-transitory machine readable medium <b>408</b>, the second non-transitory machine readable medium <b>404</b>, or both, can include instructions executable to transmit an alert, a request for response, or both, to the wearable device <b>410</b> in response to the request for emergency assistance. For instance, a wearer may fall and push a button on the wearable device <b>410</b> indicating he or she needs help (e.g., emergency assistance). In response an alert, a request for response, or both can be sent to the wearable device <b>410</b>. An alert, for instance, can include an audible alarm, badge display, or message, among others. A request for response can include, for instance, a badge that must be displayed to clear the request or a prompt to confirm that emergency assistance is indeed requested. If such confirmation is received, emergency assistance may be deployed or a responder at a monitoring center in communication with the wearable device <b>410</b> may further communicate with the wearer.

0060<figref idref="DRAWINGS">FIG. 5</figref> is another flow diagram representing an example method <b>575</b> for emergency assistance response in accordance with a number of embodiments of the present disclosure. The method <b>575</b> can be performed by a system such as the systems described with respect to <figref idref="DRAWINGS">FIGS. 1, 3, and 4</figref>.

0061At <b>576</b>, the method <b>575</b> can include receiving, at a first processing resource, first signaling from a second processing resource configured to monitor health data. For instance, the first processing resource can receive data from a sensor that is monitoring health data of a wearer, such as a heartrate, blood pressure, blood glucose levels, insulin pump levels, kidney functions, or other monitored health functions. In some examples, more than one sensor may be in communication with the first processing resource.

0062In some examples, the first signaling, for instance, can be representative of abnormal health data. For instance, a user may be experiencing higher-than-normal (e.g., above a threshold) blood pressure. In one example, the first signaling is received at an application that a wearer of a wearable device has customized with applicable personal health data thresholds (e.g., threshold blood pressure, blood glucose levels, etc.), as well as other individual information such as family contacts, emergency contacts, insurance information, allergies, physician contact information, preferred healthcare providers, etc. In some examples, the wearable device may receive the first signaling, as well.

0063At <b>578</b>, the method <b>575</b> can include transmitting, from the first processing resource, second signaling to a third processing resource of a wearable device, a prompt displayed via a user interface. For instance, if the first signaling is abnormal health data, that information can be transmitted to the wearable device for the wearer to see and evaluate. In some examples, transmitting the second signaling can include triggering an audible alarm, visual alarm, physical alarm, or any combination thereof via the wearable device. For instance, if the wearer's blood pressure is higher than a threshold, an alarm may sound, and the user may determine emergency assistance is needed. He or she may trigger an input on the wearable device to request assistance.

0064The method <b>575</b>, at <b>580</b>, can include transmitting a request for emergency assistance to a fourth processing resource, an emergency contact, or both, in response to receiving a help request response from the third processing resource within a first threshold time period. For instance, an application may receive the help request via the wearable device and transmit the request to a monitoring center, family member, or emergency contact. In some examples, the wearable device may be in communication with the monitoring center, and the monitoring center may receive the request simultaneously with the application. For instance, the fourth processing resource can be part of a monitoring center that provides additional assessments when determining an emergency assistance response.

0065At <b>582</b>, the method <b>575</b> can include writing event data associated with the first signaling to a memory resource in communication with the first processing resource in response to receiving a no help request response from the third processing resource within the first threshold time period. For instance, if the wearer confirms he or she does not need help by dismissing the alert or communicating with a monitoring center that no help is needed, the request is dismissed, tracked, and stored. In some instances, the tracking and/or storing occurs with cloud storage service.

0066At <b>584</b>, the method <b>575</b> can include transmitting, from the first processing resource, a second prompt displayed via the user interface in response to receiving no response from the third processing resource within the first threshold time period. For example, if the wearer does not respond to the prompt, he or she will be notified again regarding the abnormal health data. If he or she responds that no help is needed, the request is dismissed, tracked, and stored.

0067The method <b>575</b>, at <b>586</b>, can include transmitting the request for emergency assistance to the fourth processing resource, an emergency contact, or both in response to receiving no response from the third processing resource within a second threshold time period in response to the second prompt. For instance, if the wearer does not respond to the second prompt, emergency assistance may be deployed to the location of the wearer, which may be determined using geolocation services on the wearable device. The abnormal health data and associated response can be tracked and stored. For instance, regardless of the response, the method <b>575</b> can include tracking at the first processing resource and storing at the memory resource or other storage (e.g., a cloud storage service), the first signaling and the help request, no help request, or non-response, as well as any associated response (e.g., deployed emergency assistance, contacted family, etc.).

0068In some examples, the method <b>575</b> can include receiving, at the first processing resource, third signaling from a fifth processing resource configured to monitor different health data, and transmitting, from the first processing resource, fourth signaling to the third processing resource of the wearable device, a different prompt associated with the different health data and displayed via the user interface. In such examples, more than one sensor may monitor health data for a wearer. For instance, a user may have a blood glucose monitor and an insulin pump providing health data to the wearable device and/or associated application. The wearer can be prompted via the wearable device and/or or the application of abnormal health data from each of the different sensors. Health data from both sensors may be tracked and stored to aid future emergency assistance response decisions.

0069Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that an arrangement calculated to achieve the same results can be substituted for the specific embodiments shown. This disclosure is intended to cover adaptations or variations of one or more embodiments of the present disclosure. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. The scope of the one or more embodiments of the present disclosure includes other applications in which the above structures and processes are used. Therefore, the scope of one or more embodiments of the present disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.

0070In the foregoing Detailed Description, some features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the disclosed embodiments of the present disclosure have to use more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.