Fine data update sharing

By establishing a transaction-based health data update system between user equipment, the problems of low efficiency of health data sharing and difficulty in privacy control are solved, and resource conservation and user experience improvement are achieved.

CN119032404APending Publication Date: 2024-11-26APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033919.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-06-03
Filing Date
2023-04-04
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The prior art is difficult to realize the update and sharing of health data between user equipment, resulting in large demand for data transmission, waste of resources and difficulty in controlling user privacy.

Method used

By establishing a transaction-based system between user devices, users can choose which types of health data to share, and use cloud storage services for secure storage and update management, and use authorized identifiers and unique identifiers for fine control, generation and delivery. Trend notifications related to health data.

Benefits of technology

Reduces network traffic and resource consumption, improves user privacy control, extends device battery life, reduces notification fatigue, and improves user experience and device operability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032404A_ABST
    Figure CN119032404A_ABST
Patent Text Reader

Abstract

Techniques for identifying points of change in health data are described herein. The health data during the first time sub-window is compared to health data from the second time sub-window. The health data is evaluated relative to a set of change point criteria to determine that the first change is a first change point in the health data. A notification is generated that includes information about the change point and information about the second change point.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Non-Provisional Application No. 17 / 831,989, filed on June 3, 2022, which claims the benefit of U.S. Provisional Application No. 63 / 330,572, filed on April 13, 2022, and U.S. Provisional Application No. 63 / 197,957, filed on June 7, 2021. The contents of these patent applications are hereby incorporated by reference herein in their entirety for all purposes. Background Art

[0003] Electronic devices, especially portable electronic user devices, are rapidly becoming popular in modern society. Such devices can be used to collect and store personal information about the user, such as health data. Summary of the invention

[0004] A system of one or more computers may be configured to perform the action by having software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform a specific operation or action in operation. One or more computer programs may be configured to perform the action by including instructions that, when executed by a data processing device, cause the device to perform a specific operation or action. An overall aspect includes a computer-implemented method. The computer-implemented method includes: in response to a first user input at a first user device, identifying a second user associated with a second user device to receive a health data update associated with the first user of the first user device. The computer-implemented method also includes: in response to a second user input at the first user device, identifying an authorized identifier set, each of which represents a type of health data update to be shared with the second user device. The computer-implemented method also includes: generating a sharing request identifying the authorized identifier set and a unique identifier identifying the second user. The computer-implemented method also includes: sharing information associated with the sharing request with the second user device. Other embodiments of this aspect include corresponding computer systems, devices, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method.

[0005] Another general aspect includes another computer-implemented method. The computer-implemented method includes: receiving a sharing request at a first user device associated with a first user, the sharing request being associated with sharing health data of a second user associated with a second user device with the first user device. The computer-implemented method also includes: requesting transaction data stored by the server from a server. The computer-implemented method also includes: in response to requesting the transaction data, receiving a first transaction package from the server, the first transaction package including a first one or more health data updates associated with the health data of the second user. The computer-implemented method also includes: extracting the first one or more health data updates from the first transaction package. The computer-implemented method also includes: populating the user interface of the first user device with information associated with the first one or more health data updates. Other embodiments of this aspect include corresponding computer systems, devices, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method.

[0006] Another general aspect includes another computer-implemented method. The computer-implemented method includes: determining a first change point in a first type of health data. The computer-implemented method also includes: determining a second change point in a second type of health data related to the first type of health data. The computer-implemented method also includes: based on determining that the first change point satisfies a first set of notification criteria, generating a notification including first information associated with the first change point. The computer-implemented method also includes: based on determining that the second change point satisfies a second set of notification criteria, including in the notification second information associated with the second change point. Other embodiments of this aspect include corresponding computer systems, apparatuses, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method.

[0007] Another general aspect includes another computer-implemented method. The computer-implemented method includes: accessing first health data of a first data type collected during a time window. The computer-implemented method also includes: comparing a first quantity of the first health data associated with a first time subwindow of the time window with a second quantity of the first health data associated with a second time subwindow of the time window to identify a first change in the first health data. The computer-implemented method also includes: determining that the first change is a first change point in the first health data based on a first evaluation of the first quantity and the second quantity of the first health data relative to a first change point criterion set. The computer-implemented method also includes: generating a notification including information about the first change point. The computer-implemented method also includes: when a second evaluation of the second health data relative to a second change point criterion set indicates a second change point, including information about the second change point in the second health data in the notification. Other embodiments of this aspect include corresponding computer systems, apparatuses, and computer programs recorded on one or more computer storage devices, all configured to perform the actions of the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Block diagrams and flow charts illustrating exemplary processes for sharing health data updates between user devices according to at least one example are illustrated.

[0009] Figure 2 A flow diagram is illustrated showing a process for sharing health data updates between user devices according to at least one example.

[0010] FIG. 3A to FIG. 3E Exemplary user interfaces presented on user devices for sharing health data updates between user devices according to various examples are illustrated.

[0011] Figure 4 A diagram showing a graph for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example is illustrated.

[0012] Figure 5 A flow diagram of a process for sharing health data updates between user devices according to at least one example is illustrated.

[0013] Figure 6 A flow diagram of a process for sharing health data updates between user devices according to at least one example is illustrated.

[0014] Figure 7 A flow diagram is illustrated showing a process for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example.

[0015] Figure 8 A flow diagram is illustrated showing a process for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example.

[0016] Fig. 9 A flow diagram is illustrated showing a process for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example.

[0017] Fig.10 An exemplary architecture or environment configured to implement techniques related to sharing health data updates between user devices and identifying changes to the health data according to at least one example is illustrated.

[0018] Fig.11 An electronic device for implementing techniques related to sharing health data updates between user devices and identifying changes to health data according to at least one example is illustrated.

[0019] Fig.12 A simplified block diagram including components of an exemplary electronic device for implementing techniques related to sharing health data updates between user devices and identifying changes to health data is illustrated according to at least one example.

[0020] Fig.13 A simplified diagram including exemplary electronic devices for implementing techniques related to sharing health data updates between user devices and identifying changes to the health data is illustrated according to at least one example.

[0021] Fig.14 Exemplary electronic devices for implementing techniques related to sharing health data updates between user devices and identifying changes to health data according to at least one example are illustrated. DETAILED DESCRIPTION

[0022] In the following description, various examples will be described. For the purpose of explanation, many specific configurations and details are set forth in order to provide a thorough understanding of the examples. However, it will also be apparent to those skilled in the art that some examples may be implemented without these specific details. In addition, well-known features may be omitted or simplified to avoid confusing the described examples.

[0023] Examples of the present disclosure relate to methods, systems, devices, and computer-readable media, among other things, that provide mechanisms for establishing and maintaining a connection for automatically sharing health data updates between user devices. Unlike conventional sharing arrangements, the techniques described herein enable fine-grained user control over what data types are shared and with whom. For example, a user can select from a set of predefined health data types that may include types related to data generated using sensors of the user device or sensors of one or more related devices, types related to data derived from an instance of the user's health record, and / or types related to data entered by the user. When a sharing request is transmitted to a recipient device, if the request is accepted, the user of the recipient device can see which specific data types will be shared.

[0024] Once the sharing request has been accepted, the initiating user device can collect specific data types for a given period, bundle them together into a single transaction for a given period, and share these data types with a cloud-based storage service. The cloud-based storage service that can be implemented by the service provider can provide secure storage of transactions in a storage area accessible to the initiating user device and the recipient user device. When updates are transmitted from multiple user devices (e.g., smart phones and tablets) associated with the transmitting user, the recipient user device can use predefined logic to select which transaction is most appropriate. In some examples, this can include comparing the recency of the transaction, whether the transaction includes health data exported from accessory devices such as smart watches, the version of the application on the user device that collects health data, etc. The recipient user device can then download the transaction and retrieve the health data update. As described herein, using a transaction-based system for sharing health updates can ensure that the initiating user and the recipient user are viewing a complete and consistent view of the health data being shared. Conventional sharing techniques that do not utilize such a transaction-based system (such as the system described herein) may cause some data to be obsolete or inconsistent, and the user may not be aware of it. This can lead to a poor user experience, not to mention the risk of users taking health-related actions using inconsistent or stale health data.

[0025] Depending on the data changes compared to other health data updates, the recipient user device can trigger notifications related to the health data update. These notifications can indicate that a new health data update is available, identify changes in the health data, identify whether the health data indicates a trend in one direction or another, and indicate any other aspects of the health data update.

[0026] In some examples, the initiating user device may process the (e.g., raw or post-processed) health data on the device to determine whether data of a particular data type represents a trend, while also including information about the trend in the health data update. In some examples, the recipient device may process the health data to determine whether there is a trend. For a particular data type, the rules for determining the existence of a trend may be specific. In some examples, correlations between data types may be maintained so that when a notification about a first trend in a first data type is triggered, the system may determine whether a second trend in a second related data type may be triggered in the near future. This determination may enable the generation and delivery of a single notification about a trend, rather than generating and delivering a first notification about a first trend now and generating and delivering a second notification about a second trend in the near future. In some examples, this may be referred to as an opportunistic notification, which may reduce network traffic while also improving the user experience on the device by reducing the possibility of notification fatigue. In some examples, notifications about trends may also be managed by calling a backoff period, which determines whether the change points in the data are too close together and / or in the same direction. In this example, the system may prohibit the generation of new notifications.

[0027] Now turn to the first specific example, in which an initiating user device can transmit an offer to share a health data update with a recipient user device associated with a recipient user. The health update can be associated with the initiating user. The process of generating the offer can be managed by an application executed on the initiating user device. For example, a user selection user interface can be presented at the initiating user device. The user interface can be used by the initiating user to select a recipient user to receive health data updates from a set of users. Once selected, an authorization identifier user interface can be presented at the initiating user device. The user interface can be used by the initiating user to authorize which types of data will be shared with the recipient user device. Once identified, the initiating user device can store an authorization identifier that identifies each data type in association with the identifier of the recipient user. The authorization identifier can be used to capture the correct data for sharing and generate a sharing request to be transmitted to the recipient user device using the identifier. If the recipient user (using the recipient user device) accepts the sharing request, the initiating user device can receive a confirmation that can trigger a routine to start collecting health data updates. In some examples, the initiating user device can bundle health data updates for different data types into a single transaction for a given time period (e.g., one hour, several hours, one day, one week, one month, several months, one year, several years, etc.). The transaction can then be transmitted to the cloud-based storage service and thereby stored in a storage area accessible to the receiving user device. The receiving user device can obtain transactions from the cloud-based storage service in any suitable manner and at any suitable cadence.

[0028] Now turn to the second specific example, in which a receiving user device may receive a sharing request from an initiating user device. The sharing request may constitute an offer to share a specific type of health data update provided by an initiating user (associated with an initiating user device) to a receiving user (associated with a receiving user device). Once the sharing request has been accepted, such as indicated by the receiving user via an acceptance user interface, the receiving user device may request transaction data associated with the initiating user from a cloud-based storage service. In response to the request, the receiving user device may receive the requested transaction data, which may include health data updates associated with the initiating user. In some examples, the receiving user device may download multiple transaction packages, each of which is uniquely identified. For example, an initiating user may operate more than one user device associated with the same user profile. In this example, a first initiating user device (e.g., a smart phone) may generate a first transaction package including a first health data update, and a second initiating user device (e.g., a tablet) may generate a second transaction package including a second health data update. The receiving user device may download two transaction packages and use a set of prioritization rules to select one transaction package for use. Once the recipient user device has selected which transaction package to use, the recipient user device can extract the health data update from the transaction package. Thereafter, the recipient user device can generate a notification related to the update, populate the user interface of the recipient user device with information about the update, and perform any other suitable operations related to the update.

[0029] Now turn to the third specific example, in which a user device can be used to identify changes in health data maintained or otherwise tracked by a user device, and determine whether to notify a user associated with the user device (and health data) of these changes. The changes of interest here relate to changes in data patterns over time. For example, a user is accustomed to walking X steps every day, and in the last ten days, the number of steps is significantly less than X steps. Changes in data can be referred to as change points. When constituting changes in patterns, change points can be referred to as trends. The user device can determine whether to notify the user of change points and / or trends depending on multiple factors. For example, if a change point appears too close to an earlier change point in the same data type, the user device can prohibit the generation of a notification. If the change point is in the same direction as the previous change point notified, the user device can also prohibit the transmission of another notification. In some examples, the user device can also look for opportunities to transmit notifications about related data that have not yet but may constitute a trend within a given time period. In this example, the user device can decide to bundle updates into a single notification.

[0030] Now turn to the fourth specific example, in which a user device can be used to identify changes in health data over time (e.g., during a defined time window), and determine whether to notify a user associated with the user device (and health data) of these changes. Similar to the previous example, changes in health data can be the result of changes in user behavior. First, the user device can collect or otherwise access health data. For example, the user device may include an onboard sensor that collects at least a portion of the health data, and the user device may obtain another portion of the health data from an accessory device that includes a sensor for collecting health data. In some examples, the user device may obtain health data from devices associated with different users, for example, using the health update sharing technology described herein. In any case, once the user device has access to health data (which may include various data types (e.g., steps, stairs, exercise minutes, standing minutes, heart rate, etc.), the user device can evaluate the health data using various dynamically sized time sub-windows, which are shorter than the time window. Evaluating health data may include: evaluating health data according to a first set of change point criteria. The first change point criterion set can be used to identify the change point in the data, for example, dividing the time window into two sub-windows, each sub-window representing sufficiently different data values. For example, for a specific data type, such as walking steps, the first sub-window can be a pre-change point sub-window that identifies that the user usually walks an average of about 5,000 steps per day, and the second sub-window can be a post-change point sub-window that identifies that the user usually walks an average of about 7,000 steps per day. The change point can be defined as the time between the two sub-windows. In some examples, the first change point criterion set can also include a minimum threshold, which can correspond to medical relevance. For example, the minimum threshold can represent the minimum difference between the data in the two sub-windows, and the minimum threshold can be specific to the data type, time period, and / or whether the criterion is being evaluated as the first change point or the second change point. Therefore, in addition to the change point criterion including statistical metrics, the change point criterion can also include a minimum threshold. These thresholds can be determined by medical professionals (e.g., using empirical methods) to indicate medically relevant changes. Therefore, the minimum threshold can ensure that the change is medically relevant to the user, and the statistical metric can ensure that the change is statistically relevant. When registering a change point, the user device can generate a notification about the change point and can then determine whether there are other changes in the health data that should be included in the notification. This can include determining whether there are other change points for other data types based on a first set of change point criteria. The user device can also look for change points for other data types based on a second set of change point criteria. The second set of change point criteria can be looser than the first set of change point criteria.The second change point criteria set may also include one or more minimum thresholds, which may be specific to the data type, time period, and / or whether the change point is a first change point or a second change point related to the first change point. In this way, the second change point criteria set may be used to identify data that tends toward a change point under the first change point criteria set but will not otherwise satisfy the first change point criteria set. Evaluating other data types in this way may enable the user to be opportunistically notified of health updates of related different data types, even when one or more data types are less indicative of a trend (e.g., not as far as indicated by the first data type). In some examples, satisfying the first change point criteria set based on the first data type may mean that the first change point should be explicitly notified to the user, while satisfying the second change point criteria set with respect to the second data type may mean that the user should be notified of the second change point as long as the user device has already notified the user of the first change point. Therefore, once the user device has identified a data type that satisfies the first change point criteria set, the user device will look for other data types that satisfy the second change point criteria set, which may be opportunistically included with notifications about the first change point.

[0031] The examples described herein solve many technical problems and provide many technical improvements. In some examples, these improvements additionally improve the functions of various components of the systems in which these technologies are implemented. Compared with conventional systems, the technology described herein provides sharing of health data updates in a way that minimizes network traffic. For example, instead of sharing all health data generated or otherwise obtained from the initiating user device as in conventional systems, the technology described herein provides a method for users to choose what data will be shared at the data type level. Compared with traditional methods, this results in much smaller data transmission requirements. Additionally, because the technology described herein allows customized sharing, the resources dedicated to storing health data updates at the initiating user device, cloud-based storage services, and recipient user devices are all reduced. In addition, since users can choose what health data to share, users maintain control of their privacy because this involves sensitive data. When sharing does occur, data is shared between user devices (and cloud-based storage services) in a way that cloud-based storage services cannot read health data, let alone associate health data with specific users to which they belong.

[0032] Additionally, since the technology described herein reduces the number of relevant data type trend notifications provided to the user, the user device realizes additional technical improvements, including extending battery life, reducing bandwidth usage, and saving memory. In some examples, displaying fewer notifications can reduce the impact of alarm fatigue, thereby making the delivery of notifications more meaningful. In addition, the displayed notifications may include optional user interface objects with visual characteristics based on health-related data, which can provide users with feedback on the data types included in the health-related data. Providing improved visual feedback enhances the operability of the device and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), thereby additionally, by enabling the user to use the device more quickly and efficiently, to reduce power usage and extend the battery life of the device.

[0033] Turning now to the accompanying drawings, Figure 1 A block diagram 102 and a flow chart illustrating a process 100 for sharing health data updates between user devices according to at least one example are illustrated. Diagram 102 includes one or more user devices 104 (referred to herein as multiple user devices 104 and a user device 104). Specifically, diagram 102 indicating a computer architecture that can be used to implement the techniques described herein includes an initiating user device 104 (1) and a recipient user device 104 (2). Both user devices 104 (1) and 104 (2) are illustrated as handheld portable user devices, such as smart phones. As described herein, the exemplary user device 104 can be any suitable user device, such as a smart phone, a tablet computer, a media player, a laptop computer, a wearable device, etc. In some examples, the user device 104 can include one or more applications, which can include customized algorithms and other logic to implement the performance of at least some of the techniques described herein. The user device 104 can also include a storage medium for storing computer executable instructions (e.g., instructions that make up the application) and other data such as described herein. The user device 104 can be operated by a user.

[0034] Diagram 102 also includes a service provider 106, which is any suitable combination of computing devices such as one or more server computers. The service provider 106 may include virtual resources capable of performing the functions described with respect to the service provider 106. For example, the service provider 106 may include one or more different servers and / or services dedicated to handling different aspects of processing user requests related to sharing health data updates, identifying trends, etc. The service provider 106 may maintain a profile for the user. For example, the service provider 106 may maintain a user profile related to the digital services provided by the service provider (e.g., messaging, cloud backup, music streaming, health, fitness, contacts, data services, etc.).

[0035] Figure 1 , Figure 2 and Figures 5 to 9 Exemplary flow charts showing processes 100, 200, 500, 600, 700, 800, and 900 according to at least several examples are illustrated. These processes and any other processes described herein are illustrated as logical flow charts, each operation of which represents a series of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations can represent computer-executable instructions stored on one or more non-transitory computer-readable storage media, which perform the operations when executed by one or more processors. Generally speaking, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform specific functions or implement specific data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and / or in parallel to implement the described processes.

[0036] Additionally, part, any or all of the processes described herein may be performed under the control of one or more computer systems that are configured with specific executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) that is executed jointly on one or more processors by hardware or a combination thereof. As described above, the code may be stored on a non-transitory computer-readable storage medium, such as in the form of a computer program that includes a plurality of instructions that may be executed by one or more processors.

[0037] Process 100 begins at block 108 with initiating user device 104(1) generating a sharing request based on authorization identifier 110. As part of generating the sharing request, initiating user device 104(1) may present user selection interface 112. User selection interface 112 may present authorization identifier 110, which may identify a corresponding health data type. For example, authorization identifier 110 may include ID A, ID B, and ID N, which may correspond to any suitable number of authorization identifiers 110 that identify any suitable number of health data types. In the illustrated example, the user has selected authorization identifiers 110 corresponding to ID A and ID N. This may mean that the user intends to share the type of information represented by ID A and ID N. User selection interface 112 may identify additional information about the data type, including, for example, a title, description, starting location, sensitivity level, etc. User selection interface 112 may also provide functionality to identify and select a recipient user to receive health data updates represented by the selected authorization identifier 110. User selection interface 112 may also include a share button 114. Selection of the share button 114 may cause the initiating user device 104 ( 1 ) to generate a share request as described herein based on the selected authorization identifier 110 and transmit the share request to the recipient user device 104 ( 2 ), as discussed next.

[0038] At block 116, process 100 includes receiving, by a recipient user device 104(2), a sharing request from an initiating user device 104(1), and accepting the sharing request. Information about the sharing request may be used to populate an accept user interface 118 on the recipient user device 104(2). The accept user interface 118 may be used to present information about a particular authorization identifier 110(1) (and a corresponding data type, including a description, examples, etc.) that the initiating user intends to share with the recipient user. In this manner, the recipient user may decide whether to accept (or reject) the sharing request. The accept user interface 118 may also include an accept button 122 that may be used to accept the sharing request. In some examples, the accept user interface 118 may also include a reject button for rejecting the sharing request and / or a modify button for suggesting an alternative sharing request. For example, the recipient user may decide that they want to receive updates about a data type that is not represented by the particular authorization identifier 110(1). The recipient user may use the accept user interface 118 to transmit a reverse request to the initiating user device 104(1). At the initiating user device 104(1), the initiating user may accept, reject, and / or suggest modifications to the reverse request. In some examples, the acceptance user interface 118 may provide the recipient user with functionality to transmit "share back" updates regarding the same or different data types.

[0039] At block 124, process 100 includes the initiating user device 104(1) generating a transaction package based on the authorization identifier 110(1). Block 124 may be performed after the initiating user device 104(1) has received confirmation that the recipient user device 104(2) has accepted the terms of the sharing request. Generating the transaction package may include the initiating user device 104(1) creating a summary of the health data updates as they are recorded. Each summary of the health data updates may include a health data block and metadata that may be used to determine how to present the health data block. After the initiating user device 104(1) has generated the updates, the updates may be bundled together into a single transaction package.

[0040] At box 126, process 100 includes: transmitting the transaction package to service provider 106. Specifically, the initiating user device 104(1) can transmit the transaction package to the service provider 106, including a summary of the health data updates of the data type identified by the authorization identifier. The service provider 106 can host a cloud-based storage service. For example, the transaction can be transmitted to the cloud-based storage service and stored by the service provider 106 in a storage area associated with the account profile of the initiating user. The transaction-based approach can be useful when the storage area includes health data updates for the initiating user collected and generated from different user devices (e.g., the initiating user device 104(1) and other user devices associated with the initiating user, such as a watch, smart phone, tablet, laptop, etc.).

[0041] At block 128, process 100 includes the recipient user device 104(2) requesting a transaction package from the service provider 106. As described herein, the recipient user device 104(2) may use a predefined routine to determine which transaction package to request from the service provider 206 because multiple transaction packages may be available at a given time. For example, the recipient user device 104(2) may examine transaction metadata associated with each transaction package to determine whether one transaction package is preferred over another transaction package. In some examples, the transaction metadata may include information such as, for example, a timestamp of transaction generation, whether the transaction originated from a user device paired with a smartwatch, a static identifier of the user device used to generate the summary, and the like.

[0042] At box 130, process 100 includes: the recipient user device 104 (2) extracts data from the transaction package to populate a user interface with the health data update. In some examples, the health data update can be used to populate a user interface within an application (e.g., an application dedicated to the user's health) or other suitable location. The health data update can be used to trigger any suitable notification to alert the recipient user to the new health update. In some examples, certain health data updates can trigger more intrusive alerts. For example, if the health data update indicates that the initiating user may be experiencing a heart attack, the health data update can be presented as a prominent pop-up type alert 132. On the other hand, if the health data update indicates that the initiating user has completed a fitness goal for a full week (e.g., exercising for 30 minutes) (e.g., a type of health summary or highlights 134), the health data update may not be prominently presented, or otherwise added to the dashboard / user interface without specifically notifying the recipient user. Other types of health data updates 136 may also be presented using the user interface as a notification or in any other suitable manner.

[0043] Now turn to Figure 2 , which illustrates a flow chart showing a process 200 for sharing health data updates between user devices according to at least one example. Process 200 can be performed by an initiating user device 104(1), a receiving user device 104(2), and a service provider 106. Process 200 is a variation of process 100, which includes: Figure 2 Shown and in Figure 1 The various functions performed by the various components are described in more detail in the accompanying drawings.

[0044] Process 200 may begin at (1) with initiating user device 104(1) identifying users and categories to be shared. The users may be associated with contact information on initiating user device 104(1). In some examples, the users may be associated with the user of initiating user device 104(1) in other ways. For example, the user of (1) may be a social media contact of the user of initiating user device 104(1). The categories may identify selected categories and / or types of health data and may correspond to authorized identifiers. In some examples, (1) may be performed by initiating user device 104(1) using an application resident on initiating user device 104(1).

[0045] At (2), process 200 includes initiating user device 104(1) generating a sharing request. The sharing request may be based on the information collected at (1). For example, the sharing request may identify a user and which category of health data the user of initiating user device 104(1) intends to share with the user identified at (1).

[0046] At (3), process 200 includes the initiating user device 104(1) transmitting the sharing request to the service provider 106. This may be performed using a messaging service, a notification service, or other suitable communication connection between the initiating user device 104(1) and the service provider 106. After receiving the sharing request, at (4), process 200 includes the service provider 106 transmitting the sharing request to the recipient user device 104(2). In some examples, prior to transmitting to the recipient user device 104(2), the service provider 106 may record information from the sharing request to indicate that the user of the initiating user device 104(1) intends to share with the user of the recipient user device 104(2).

[0047] At (5), process 200 includes recipient user device 104(2) accepting the sharing request. This may include the user of recipient user device 104(2) accepting the sharing request using a user interface presented at recipient user device 104(2). In some examples, the user interface may enable the user of recipient user device 104(2) to modify the sharing request and / or generate a similar sharing request to be transmitted to the user of initiating user device 104(1).

[0048] At (6), process 200 includes: the recipient user device 104(2) transmits the confirmation to the service provider 106. Based on receiving the confirmation, at (7), process 200 includes: the service provider 106 generates a storage area. The generated storage area can be associated with the user of the initiating user device 104(1) and include a dedicated space for storing health data from the user of the initiating user device 104(1), which dedicated space has been shared with the recipient user device 104(2). In some examples, the recipient user device 104(2) can also receive the confirmation including information about the storage area (e.g., the storage area uniform resource locator), etc. In some examples, existing data synchronization services can be used to implement writing and reading data from the storage area, etc. For example, each user of the recipient user device 104(2) and the initiating user device 104(1) can access a cloud-based storage system, which can be used, among other things, to back up data from the recipient user device 104(2) and the initiating user device 104(1). This cloud-based storage can also be used to share health data, as described herein.

[0049] At (8), process 200 includes: service provider 106 transmits a confirmation to initiating user device 104(1). The confirmation may indicate that recipient user device 104(2) has accepted the sharing request. In some examples, the confirmation may also include information about the storage area (e.g., a URL or other resource locator) that initiating user device 104(1) may use to access the storage area.

[0050] At (9), process 200 includes: initiating user device 104(1) collecting health data. This may include: using sensors of initiating user device 104(1) to collect health data, generating health data based on input from a user of initiating user device 104(1), obtaining health data from one or more external sources such as an electronic medical record (EMR) system configured to store a user's personal health record, obtaining health data from an accessory device such as a watch or other auxiliary sensor, etc. The EMR may store different versions of the user's personal health record, which versions may be processed on the initiating user device 104(1), and insights from that processing may constitute "collected health data."

[0051] At (10), process 200 includes: initiating user device 104(1) generating a health update for each category. The health data update can be generated based on the category identified in the sharing request. In some examples, the health data update can include health data updates for other categories because they relate to other sharing requests accepted by other users. The health update can include content (e.g., a summary of the health data update) and metadata for presenting the content. The receiving user device 104(2) can use the metadata to decide how to present the summary.

[0052] At (11), process 200 includes: initiating user device 104(1) generating a transaction including health updates. These can be the health updates generated at (10). The transaction can include multiple health updates bundled together in a single transaction. In some examples, transactions are generated periodically in response to certain triggers (e.g., when new data comes in, when a target / threshold is met, etc.) and in any other suitable manner. For example, the logic can be configured to look for updates and generate transactions every hour, every few hours, every day, every few days, every week, etc. Generating the transaction can include generating transaction metadata describing various aspects of the transaction. For example, such metadata can include a timestamp, a version of the application used to generate the update, whether the initiating user device 104(1) is paired with an accessory device, a source identifier of the initiating user device 104(1), and any other suitable information.

[0053] At (12), process 200 includes initiating user device 104(1) transmitting the transaction to service provider 106. At (13), process 200 includes service provider 106 storing the transaction in a previously created storage area. In some examples, at (12), initiating user device 104(1) may also transmit a notification about the transaction to recipient user device 104(2). In other examples, initiating user device 104(1) may not notify recipient user device 104(2) of the new transaction. Instead, recipient user device 104(2) may check the storage area for updates.

[0054] At (14), process 200 includes the recipient user device 104(2) requesting a transaction. This may include the recipient user device 104(2) requesting any new transactions stored in the storage area. In some examples, the recipient user device 104(2) may read the transaction metadata to determine which of multiple transactions to download. There may be multiple transactions because other user devices associated with the user of the initiating user device 104(1) may also upload transactions that include health data. The recipient user device 104(2) may distinguish between these transactions to ensure a consistent and functional experience for users with multiple user devices.

[0055] At (15), process 200 includes the recipient user device 104(2) receiving the transaction. This may include the service provider 106 transmitting the selected transaction to the recipient user device 104(2).

[0056] At (16), process 200 includes the recipient user device 104(2) updating the user interface to include the health update from the transaction. This may include the recipient user device 104(2) extracting the health update (including the summary and metadata) from the transaction. The metadata may then be used by the recipient user device 104(2) to present the summary.

[0057] Now turn to FIG. 3A to FIG. 3E , these figures illustrate exemplary user interfaces 300(1)-300(5) presented on a user device 104 for sharing health data updates between user devices according to at least one example. In some examples, the user interfaces 300(1)-300(5) may be presented on a recipient user device 104(2) or an initiating user device 104(1), depending on the user context. FIG. 3A to FIG. 3E In the embodiment of the present invention, user interfaces 300(1), 300(2), 300(3), and 300(4) may be presented on the initiating user device 104(1), while user interface 300(5) may be presented on the receiving user device 104(2). User interfaces 300(1) to 300(5) may be presented using an application on the user device 104.

[0058] Figure 3A A user interface 300(1) on an initiating user device 104(1) is depicted. The user interface 300(1) may be referred to as a user selection user interface because the user interface may enable the user of the initiating user device 104(1) to select a user with whom to share health data updates from a user list 302, as described herein. In some examples, the user interface 300(1) may enable the user of the initiating user device 104(1) to search for a user using a search bar and input elements (e.g., a keyboard, voice input, etc.). In some examples, the user list 302 may be pre-populated with suggested users. The suggested users may be identified by the initiating user device 104(1) using any appropriate technique. For example, the suggested users may be users identified as being part of the same household as the user, being in the user's contacts, being a caregiver, or otherwise being likely to accept a sharing request from the user of the initiating user device 104(1). As illustrated, the user of the initiating user device 104(1) has selected a user identified by "Nick Rivera," depicted by an image, and having an associated telephone number. Any of this information may constitute a user identifier (e.g., identification information that may be used to generate a sharing request). In the illustrated version, the user of initiating user device 104(1) has selected user "Nick Rivera," as shown by selector 304. This is the user to whom health updates will be provided for sharing.

[0059] Figure 3BA user interface 300(2) on an initiating user device 104(1) is depicted. The user interface 300(2) may be referred to as an authorization identifier user interface because the user interface may enable a user of the initiating user device 104(1) to identify a set of authorization identifiers 306 to control which health data updates are to be shared with the recipient user device 104(2). In some examples, an additional user interface may be presented that includes an option for the user of the initiating user device 104(1) to view a list of suggested topics that may be shared and to view all topics that may be shared. In some examples, other user interfaces may be presented to identify other sets of authorization identifiers. For example, the user interface 300(2) may be for health data updates of the type "activity and mobility" (e.g., fitness, training, mobility, and other similar types of health data topics), and the user interface may be one of many user authorization identifier user interfaces (e.g., the user interface 300(2) is one of five such interfaces). Other user authorization identifier user interfaces may include user authorization identifier user interfaces for “basic health measurements” (e.g., weight, blood oxygen, respiratory rate, blood sugar, insulin, and other similar health data topics), “heart health” (e.g., resting heart rate, heart rate variability, heart rate, electrocardiogram, and other similar health data topics), “cycle tracking” (e.g., cycle prediction, fertility prediction, menstruation, sexual activity, and other similar health data topics), “lab results” (e.g., a list of lab results obtained from the user's health record that can be selected one by one or all, and may include an option to share future updates), “heart alerts” (e.g., irregular heart rhythm, low blood pressure, and other similar health data topics), and any other type of health data update. Figure 3B As shown, the set of authorization identifiers 306 may include a set of selector-type user interface elements, each element corresponding to an activity and mobility health data topic (e.g., activity, aerobic fitness, steps, walking smoothness, exercise, and other similar health data topics). In this example, the user has selected the "activity" and "steps" selectors. In this way, the user may intend to share updates about these health data types. Once the selector set is selected, the user can select the next button 308. As described above, this can cause the initiating user device 104 (1) to present one of the other user authorization identifier user interfaces to allow the user to select other health data types for sharing. Once all selections have been made, the initiating user device 104 (1) can present the user interface 300 (3).

[0060] Figure 3CA user interface 300(3) on an initiating user device 104(1) is depicted. The user interface 300(3) may be referred to as a sharing request user interface because the user interface may enable the user of the initiating user device 104(1) to review what health data types will be shared and with whom. In this example, the user interface 300(3) identifies the user "Nick Rivera" 310 and an overview 314 of health data types, each of which has been selected using an authorization identifier selector. The user of the initiating user device 104(1) may select a review button 316 to review what health data updates will be shared. Once the user is satisfied with what health data will be shared and with whom, the user may select a share button 318. This may cause the initiating user device 104(1) to generate a sharing request to be transmitted to a recipient user device 104(2) (e.g., Nick Rivera's user device) for further review by the user of the recipient user device 104(2).

[0061] Figure 3D A user interface 300(4) on a recipient user device 104(2) is depicted. The user interface 300(4) may be referred to as an acceptance user interface because the user interface may enable a user of the recipient user device 104(2) (e.g., Nick Rivera) to accept or reject a sharing request initiated by a user of the initiating user device 104(1) (e.g., Tiffany Smith). The user interface 300(4) may include a summary list 320 of what health data updates Tiffany intends to share. The summary list 320 may correspond to a summary of the health data updates 314 presented in the user interface 300(3) on the initiating user device 104(1). This may enable the user of the recipient user device 104(2) to review what information the user of the initiating user device 104(1) intends to share. If acceptable, the user of the recipient user device 104(2) may select an accept button 322. If the user of the recipient user device 104(2) does not want to receive the health data updates, they may select a reject button 324. In this example, the user of the recipient user device 104 ( 2 ) has selected the accept button 322 .

[0062] Figure 3EA user interface 300(5) on a recipient user device 104(2) is depicted. The user interface 300(5) may be referred to as a health data summary user interface because the user interface may enable a user of the initiating user device 104(1) (e.g., Tiffany) to view a summary of what health data updates the user of the initiating user device 104(1) (e.g., Nick) will see. Specifically, the user interface 300(5) identifies that the health data belongs to "Tiffany Smith" and includes information for communicating with the user and / or otherwise interacting with the user. The user interface 300(5) also includes summaries 326(1) and 326(2), each of which may correspond to a type of health data update that has been shared with the user of the recipient user device 104(2). In this example, the summary 326(1) may correspond to the number of steps that Tiffany has walked in the last week. In some examples, selection of the summary 326(1) may enable the user to view additional details about a particular type of health data update. The summary 326(2) may correspond to Tiffany's progress in completing a set of health-related goals (e.g., a move goal, an exercise goal, and a stand goal). The summary 326(2) may also include a graphical indicator corresponding to the set of health-related goals. In some examples, selection of a particular summary 326 may enable a user to view additional details about a particular type of health data update. The user interface 300(5) may be slightly modified and presented on the recipient user device 104(2). Specifically, when the health data updates are transmitted to the recipient user device 104(2), they may be in the form shown in the user interface 300(5).

[0063] Figure 4A diagram 400 showing graphs 402 and 404 for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example is illustrated. For illustrative purposes, diagram 400 is used to demonstrate techniques for identifying patterns in health data over time and for determining notifications associated with the patterns. For example, these patterns may indicate trends in health data (e.g., inflection points or change points associated with an increase, decrease, or even some indication of steady state in measured data). A user device may be used to determine these trends based on actual health data, and also determine whether to notify a user of the user device and / or a user of a device with which the user has shared his or her health data. For example, an initiating user device 104(1) may process the health data of its user and decide whether to notify the user of the initiating user device 104(1) of information about the trend, and may also transmit a notification to a recipient user device 104(2) (e.g., if a sharing relationship has been established, as described elsewhere herein). For data types that are related or otherwise associated, as described herein, a user device may determine whether to include an immature notification with a current mature notification. In some examples, the determination may depend at least in part on whether an immature notification is likely to mature within a certain period of time (e.g., data indicates that the user is trending in a certain direction and is likely to continue to do so). Such opportunistic determinations may reduce the overall number of notifications delivered to the user, which may reduce alert fatigue and improve the user experience.

[0064] Graph 402 corresponds to a first data type 406 and includes measurements of data of the first data type 406 along the Y axis within a time period defined along the X axis. Similarly, graph 404 corresponds to a second data type 408 and includes measurements of data of the second data type 408 along the Y axis within a time period defined along the X axis. The time periods in graphs 402 and 404 may be the same. In some examples, the first data type 406 and the second data type 408 may be related in some way. For example, the first data type 406 may represent the number of user steps, and the second data type 408 may represent the number of exercise minutes. Other exemplary associations may include, for example, heart rate and exercise, insulin levels and calories burned, heart rate and steps, and any other association between at least two health data types. In some examples, these associations may include more than two health data types. These associations may be direct or inverse. For example, an increase in the number of steps may be associated with an increase in the number of exercise minutes, or a decrease in the number of steps may be associated with a higher resting heart rate. In any case, the techniques described herein may be used to make opportunistic notification determinations for associated or otherwise related data types.

[0065] Chart 402 indicates that between 1 / 1 / 2021 and 3 / 1 / 2021, the health data collected for the first data type 406 is relatively constant, as evidenced by the first average 410. However, between 3 / 1 / 2021 and 4 / 1 / 2021, the magnitude of the collected data begins to increase, as evidenced by the first change 412. The technology described herein can compare the first change 412 in the time period between 3 / 1 and 4 / 1 with the first threshold 422 to determine whether the first change point 424 has been registered. The first threshold 422 can be specific to the first data type 406. If the increase in data has exceeded the first threshold 422 within the defined time period, the user device can determine the change point 424 (e.g., the inflection point at which the magnitude of the health data begins to increase). Such changes in data over a period of time can indicate a trend. Users associated with the first data type 406 may be interested in understanding the trend. Therefore, the user device can generate a notification to be presented to the user. In order to optimize resources and minimize the overload of notifications on users, the user device can also check whether any related data types indicate a trend. Figure 404 represents such an inspection.

[0066] Graph 404 indicates that between 1 / 1 / 2021 and 3 / 1 / 2021, the health data collected for the second data type 408 was relatively constant, as evidenced by a second average 426. However, between 3 / 1 / 2021 and 4 / 1 / 2021, the amount of data collected began to increase, as evidenced by a second change 428. The techniques described herein can determine whether the second change 428 during the time period between points 430 and 432 is sufficient to exceed a second threshold 434. In this example, the second change 428 during only these points does not meet or exceed the second threshold 434. However, the user device can continue to analyze the health data of the second data type to determine a predicted value 436. The predicted value 436 can represent the difference between the current average at 432 and the total threshold amount required to qualify for notification. If the user device determines with a relative confidence that the user is likely to meet a second threshold 434 within a predefined amount of time (e.g., one hour, more than one hour, one day, more than one day, one week, more than one week, one month, more than one month, etc.) beyond the current date, the user device may generate a notification 408 regarding a trend in the second data type and include the trend in a notification 406 regarding a trend in the first data type.

[0067] Figure 5 A flow chart of a process 500 for sharing health data updates between user devices according to at least one example is illustrated. The process 500 may specifically correspond to a method for initiating a sharing request to share health data updates with other associated users. Fig.10 )Whether in the wearable electronic device 1005( Fig.10 )、User equipment 1002( Fig.10 ), or the service provider computer 1004 ( Fig.10 ) or in any suitable combination of the foregoing devices, can be performed Figure 5 Thus, while process 500 is described as being performed by a user device, it should be understood that other user devices (eg, wearable user devices) or a server may perform process 500 with limited adjustments.

[0068] Process 500 begins at block 502 with a first user device receiving a first user input at the first user device. The first user input may be input by the first user, and the first user input may identify a second user. In some examples, the first user input may be input by a first user, such as in user interface 300(1)( Figure 3A ) or the like. The first user device is an example of an initiating user device 104(1).

[0069] At block 504 , process 500 includes the first user device identifying a second user associated with the second user device to receive health data updates associated with the first user of the first user device. In some examples, block 504 may be performed in response to block 502 being performed.

[0070] At block 506, process 500 includes: the first user device receiving a second user input at the first user device. The second user input may be input by the first user. In some examples, the second user input may be input by the first user, such as in user interface 300(2)( Figure 3B ) and other user interfaces to receive second user input.

[0071] At box 508, process 500 includes: the first user device identifies a set of authorization identifiers, each authorization identifier representing a type of health data update to be shared with the second user device. In some examples, box 508 can be performed in response to box 506 being executed. The second user input may include a set of inputs for selectively identifying individual authorization identifiers. In this way, the first user can have a fine level of control over which type of health data updates can be shared with the second user. In some examples, each authorization identifier in the set of authorization identifiers can correspond to a health topic. In some examples, the health data update can be based on health data collected or generated by the first user device or at least one of the accessory devices of the first user device.

[0072] At block 510, process 500 includes: the first user device generating a sharing request identifying a set of authorized identifiers and a unique identifier identifying a second user. In some examples, block 510 can be based at least in part on information about the second user and the identified set of authorized identifiers. In some examples, process 500 can further include: before or as part of generating the sharing request (e.g., user interface 300(3)( Figure 3C )) presents a summary of the authorized identifier set and the second user. In some examples, the unique identifier may include a shared identifier that can be used to upload and download data from the server.

[0073] At block 512, process 500 includes the first user device sharing information associated with the sharing request with the second user device. In some examples, the shared information may be based on user input received at a user interface such as user interface 300(3). In some examples, sharing the information associated with the sharing request with the second user device may include transmitting the information to a server. The information may be configured to enable the server to transmit the sharing request to the second user device. In some examples, process 500 may further include receiving a message indicating that the second user accepts the sharing request, which message may be proxied by the server or using other means.

[0074] In some examples, process 500 may further include: the first user device generates a set of health data updates based at least in part on the set of authorization identifiers, and combines the set of health data updates into a transaction. In some examples, these additional actions can be performed after the second user has accepted the sharing request. In some examples, each health update in the set of health updates can include source data and update metadata. In some examples, a transaction can include a set of health updates and transaction metadata. The update metadata can be used by the second user device to determine the display of the set of health updates, and the transaction metadata can be used by the second user device to select between different transactions.

[0075] In some examples, process 500 may further include: before generating the set of health data updates, detecting, by the first user device, the occurrence of a triggering event. The triggering event may include at least one of the following: opening of a health application on the first user device, collection of a type of health data associated with the set of authorized identifiers, collection of a certain amount of health data associated with the set of authorized identifiers, achievement of a health-based goal associated with the set of authorized identifiers, or a trend in health data associated with the set of authorized identifiers. In this way, the first user device can check for updates when triggered.

[0076] In some examples, process 500 may further include: the first user device transmitting information associated with the transaction to the server to enable the server to store the transaction according to a storage area associated with the unique identifier identifying the second user.

[0077] In some examples, process 500 may further include: the first user device generates different sharing requests that identify different authorization identifier sets and different unique identifiers that identify third users of the third user device, and the first user device transmits information associated with the different sharing requests to the server. The information may be configured to enable the server to transmit the different sharing requests to the third user device. In some examples, the different authorization identifier sets may be different from the authorization identifier set.

[0078] Figure 6 A flow chart of a process 600 for sharing health data updates between user devices according to at least one example is illustrated. The process 600 may specifically correspond to a method for receiving and accepting a sharing request to share health data updates with other associated users. Fig.10 )Whether in the wearable electronic device 1005( Fig.10 )、User equipment 1002( Fig.10 ), or the service provider computer 1004 ( Fig.10 ) or in any suitable combination of the foregoing devices, can be performed Figure 6 Thus, while process 600 is described as being performed by a user device, it should be understood that other user devices (eg, wearable user devices) or a server may perform process 600 with limited adaptation.

[0079] Process 600 begins at block 602 with a first user device receiving a sharing request associated with sharing health data. The first user device may be associated with a first user, and the sharing request may be associated with sharing health data of a second user associated with a second user device with the first user device. In this example, the first user device is an example of a recipient user device 104(2), and the second device is an example of an initiating user device 104(1). In some examples, the request may include a unique identifier of the first user.

[0080] At block 604, process 600 includes: requesting, by a first user device, transaction data associated with health data. The transaction data may be stored by a server (e.g., service provider computer 1004). In some examples, process 600 may further include: detecting, by the first user device, an occurrence of a triggering event prior to requesting the transaction. The triggering event may include: at least one of opening a health application on the first user device, detecting that a time condition has been met, etc. In some examples, the first user device may request the transaction data periodically.

[0081] At block 606, process 600 includes: the first user device receiving a first transaction package from the server, the first transaction package including first one or more health data updates associated with health data of the second user. In some examples, block 606 may be performed in response to the first user device requesting the transaction data. In some examples, the server and / or the first user device may select the first transaction package from a set of transaction packages stored by the server. In some examples, selecting one of the first transaction package or the second transaction package as the selected transaction package may be based at least in part on the transaction selection rule set. This may include performing at least one of the following: (i) determining collection time information of each of the first transaction package and the second transaction package based at least in part on transaction metadata associated with each of the first transaction package and the second transaction package, respectively; (ii) determining application version information of each of the first transaction package and the second transaction package based at least in part on transaction metadata associated with each of the first transaction package and the second transaction package, respectively; (iii) determining accessory device information of each of the first transaction package and the second transaction package based at least in part on transaction metadata associated with each of the first transaction package and the second transaction package, respectively; or (iv) determining device identifier information associated with each of the second user device and the third user device used to collect the first transaction and the second transaction package based at least in part on transaction metadata associated with each of the first transaction package and the second transaction package, respectively. In some examples, (i), (ii), (iii), and (iv) may represent a set of transaction selection rules that may be prioritized. For example, where possible, the user device may first prefer recently submitted transactions (e.g., transactions submitted within the last 72 hours), second may prefer transactions created on newer versions of the health application (e.g., as determined via a build tag of the health application), third may prefer transactions created on devices with a paired wearable usage device, and finally may prefer devices with lower static source identifiers (e.g., preferring newer devices).

[0082] In some examples, the goal of this logic can be to provide a consistent and functional experience for users with multiple devices. In some examples, the logic can ensure some results, such as preventing the originating user device from jumping between different recipient user devices when more than one recipient user device is used interchangeably. Additionally, this approach can prevent old originating user devices from "blocking" newer data from appearing, and allow transactions with new features (from new versions of software) to be prioritized where possible.

[0083] At block 608, process 600 includes: the first user device extracting first one or more health data updates from the first transaction bundle. Extracting the first one or more health data updates may include: receiving a notification about the health update and requesting specific data from the server. In some examples, the first user device receives a health update that includes a health data blob and metadata that can be used by the first user device to present the health update.

[0084] At block 610, process 600 includes the first user device populating a user interface of the first user device with information associated with the first one or more health data updates. This may be performed using metadata received with the first one or more health data updates and logic in the health application.

[0085] In some examples, process 600 further includes: in response to requesting transaction data, receiving a second transaction package from the server, the second transaction package including a second one or more health data updates associated with health data of a second user associated with a third user device. In this example, process 600 may further include: selecting one of the first transaction package or the second transaction package as the selected transaction package based at least in part on the transaction selection rule set. In this example, extracting the first one or more health data updates from the first transaction package may include: extracting the selected one or more health data updates from the selected transaction package. In this example, populating the user interface of the first user device with information associated with the first one or more health data updates may include: populating the user interface of the first user device with information associated with the selected one or more health data updates.

[0086] Figure 7 A flow chart illustrating a process 700 for identifying changes in health data and providing an opportunistic notification to a user device according to at least one example is illustrated. Process 700 may specifically correspond to a method in which a first user device identifies a trend in health data, decides whether to notify a user of the trend, and decides whether to notify a user of the trend in the related health data. Health application 1010 ( Fig.10 )Whether in the wearable electronic device 1005( Fig.10 )、User equipment 1002( Fig.10 ), or the service provider computer 1004 ( Fig.10 ) or in any suitable combination of the foregoing devices, can be performed Figure 7 Thus, while process 700 is described as being performed by a user device, it should be understood that other user devices (eg, wearable user devices) or a server may perform process 700 with limited adaptation.

[0087] Process 700 begins at block 702 with a first user device receiving a health data update associated with a first type of health data and a second type of health data. The first user device can be associated with a first user. The health data update can correspond to any type of health data described herein. For example, the health data update can relate to data collected by the first user device, collected by an accessory user device, received from an electronic health record system, and the like. In some examples, the first health data of the first type of health data is collected by at least one of a handheld user device or a wearable user device.

[0088] At box 704, process 700 includes: the first user device determines whether an update of the first type of health data is equal to a change point. Determining whether the update constitutes a change point may include: evaluating the health data according to one or more change point criteria. For example, this may include evaluating the importance, absolute change, etc. of the health data within a time window. This may include a predefined minimum P value for the change point. The time window may include multiple time periods, and the evaluation may include evaluating the current time period relative to one or more other time periods. If the answer at box 704 is no, process 700 returns to box 702 to receive additional health data updates. If the answer at box 704 is yes, process 700 continues to box 706. In some examples, the first change point may include a change in the first type of health data within a given time period.

[0089] In some examples, determining the first change point may include comparing first health data of a first type of health data from a first time period to second health data of the first type of health data from a second time period overlapping the first time period.

[0090] In some examples, process 700 may include, after determining the first change point and before determining the second change point, selecting the second type of health data for evaluation based at least in part on a predefined correlation between the first type of health data and the second type of health data.

[0091] At box 706, process 700 includes: the first user device determines whether the update of the second type of health data is equal to a change point. The determination can be similar to box 704. In some examples, the second type of health data can be related to the first type of health data. In some examples, the determination at 706 can be triggered by the determination at 704. In some examples, the criteria for determining the second type of health data can be different, at least because the determination at 706 is performed after box 704 based on a particular type of health data and based on other factors. For example, determining whether an update constitutes a change point may include: evaluating the health data according to one or more change point criteria. If the answer at box 706 is no, process 700 returns to box 702 to receive additional health data updates. If the answer at box 706 is yes, process 700 continues to box 708.

[0092] In some examples, determining a first change point in a first type of health data may include determining the first change point based on a first threshold, and determining a second change point in a second type of health data may include determining the second change point based on a second threshold. The first threshold may be an absolute threshold, and the second threshold is a relative threshold. In some examples, the relative threshold may depend at least in part on a first change point occurring before the second change point. In some examples, the first change point in a first type of health data may include determining the first change point at a first time. In some examples, determining a second change point in a second type of health data may include determining the second change at a second time after the first time.

[0093] In some examples, the first type of health data and the second type of health data may be associated with a single user profile and indicate the health of a user associated with the single user profile.

[0094] At box 708, process 700 includes: the first user device determines whether the first change point satisfies the first set of notification criteria. This may include determining whether the first change point is sufficient to notify the user. In some examples, the change point may include any inflection point in the data, and boxes 708 and 714 may be performed to determine whether the inflection point constitutes a sufficiently significant change to notify the user. In some examples, the first change point may satisfy all notification criteria, for example, the data indicates that a threshold has been exceeded within a time period indicating a significant change. If the answer at box 708 is no, process 700 proceeds to box 710 and generation of notifications is prohibited. If the answer at box 708 is yes, process 700 proceeds to box 712.

[0095] In some examples, the first set of notification criteria may include a recency criterion that defines a time threshold between transmitting notifications associated with the first type of health data and a trend criterion that defines a condition under which a directional change in a trend in the first type of health data will trigger a notification.

[0096] In some examples, determining that the first change point satisfies the first set of notification criteria may include determining that the first change point satisfies the first set of notification criteria at a first time. In some examples, determining that the second change point satisfies the second set of notification criteria may include determining that the second change point is likely to occur within a threshold amount of time after the first time.

[0097] At block 712, process 700 includes: generating, by the first user device, a notification associated with the first change point. The notification may identify the data type, the direction of the trend (e.g., upward, downward, etc.), and any other details about the trend (e.g., a time window for evaluating the trend, a suggestion to continue the trend or reverse the trend, etc.). In some examples, block 712 may include: generating, based on determining that the first change point satisfies the first set of notification criteria, a notification including first information associated with the first change point.

[0098] At box 714, process 700 includes: the first user device determines whether the second change point satisfies the second set of notification criteria. In some examples, based on determining that the second change point satisfies the second set of notification criteria, box 714 may include second information associated with the second change point in the notification. The second information may be related to the second change point. In some examples, box 714 may include: determining whether the second change point is sufficient to notify the user. In some examples, the change point may include any inflection point in the data, and boxes 708 and 714 may be performed to determine whether the inflection point constitutes a sufficiently significant change to notify the user. In some examples, the second set of notification criteria may be related to the first set of notification criteria. For example, the second set of notification criteria may consider whether the second change point satisfies the threshold requirement or whether the threshold requirement may be satisfied within a given time period (e.g., within a short time period). In this way, the second set of notification criteria may consider whether both the first change point and the second change point should be notified to the user, even if the first change point is the only change point that is fully mature and can be used for notification.

[0099] In some examples, the first set of notification criteria may be independent of the second type of health data, and the second set of notification criteria may be dependent on the first type of health data.

[0100] If the answer at block 714 is no, process 700 proceeds to block 710 and generation of notifications is disabled. If the answer at block 714 is yes, process 700 proceeds to block 716.

[0101] At block 716, process 700 includes the first user device including information about the second change in the notification. This may include adding information about the second trend in the notification.

[0102] At block 718, process 700 includes transmitting the notification. This may include presenting the notification at the first user device and / or transmitting the notification to the second user device.

[0103] Figure 8 A flow chart illustrating a process 800 for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example is illustrated. Process 800 may specifically correspond to a method in which a first user device identifies a trend in health data, decides whether to notify a user of the trend, and decides whether to notify a user of trends in other health data. Health application 1010 ( Fig.10 )Whether in the wearable electronic device 1005( Fig.10 )、User equipment 1002( Fig.10 ), or the service provider computer 1004 ( Fig.10 ) or in any suitable combination of the foregoing devices, can be performed Figure 8 Thus, while process 800 is described as being performed by a user device, it should be understood that other user devices (eg, wearable user devices) or a server may perform process 800 with limited adaptation.

[0104] Process 800 begins at box 802 with the user device identifying an initial time window for evaluating the user's health data. The initial time window may be predefined by the user device and / or by a service provider such as service provider computer 1004. In some examples, the time window may correspond to a time period in which the user's health data will be evaluated. For example, the time window may correspond to one month, two months, three months, four months, five months, six months, seven months, eight months, twelve months, two years, and any other suitable period. In some examples, the time window may have a suitable length that can identify actual insights in the form of data trends. For example, if the time window is too short, the amount of data collected may be too small to identify trends with any appropriate degree of certainty. In some examples, more than one time window may be used. For example, process 800 may be performed on a short time window (e.g., four weeks) and repeated on a long time window (e.g., twenty-six weeks). In some examples, certain data types may be evaluated in one window, but not in another window. In some examples, all data types may be evaluated in two windows.

[0105] At box 804, process 800 includes: the user device accesses various types of health data obtained during the time window. The health data can be accessed from a database on the user device that stores the health data. The health data can be collected by the user device, received from different user devices and / or accessory devices, and collected using any other suitable method (e.g., from an electronic health record (EHR) computer system associated with the user). In some examples, the health data can be organized by data type so that each data type can be evaluated independently of other data types. Therefore, accessing various types of health data can include: individually and independently accessing various types of health data from one or more sources. In some examples, the user device can process the health data to some extent after accessing the health data. For example, this can include alignment, normalization, removing outliers, and performing any other data correction post-processing actions.

[0106] At box 806, process 800 includes: the user device determines whether the health data meets the first change point criterion set. In some examples, the change point criterion set may correspond to a statistical metric set, and a threshold may be applied to the statistical metric set to classify and compare the same type of health data. In some examples, the user device may use a dynamically adjustable window to evaluate different sub-portions of the health data within a larger time window. For example, continuing the example above, the time window may be approximately four weeks, and the dynamically adjustable time window may initially be set to five days, but then may be increased, decreased, and / or moved throughout the time window to evaluate different portions of the health data that may meet the first change point criterion set. As part of determining whether the health data meets the first change point criterion set, the user device may evaluate the health data in the dynamically adjustable time window with the goal of dividing the window into a pre-change point sub-window and a post-change point sub-window, where the change point is located at a time between the pre-change point sub-window and the post-change point sub-window. The first change point criterion set may indicate what difference must exist in the health data in order to identify the change point between two sub-windows of the time period.

[0107] In some examples, the first set of criteria may correspond to a Welch's t-test (or other similar tests such as a Student's t-test) indicating statistical significance between two data sets (e.g., a subwindow before a change point and a subwindow after a change point), an effect size determination indicating the magnitude of the relative change between the data in the two subwindows, and any other statistical or other criteria for evaluating whether the user's health data indicates consistent changes in one direction or another. In some examples, the first set of change point criteria may represent a rigorous test for determining whether a change point exists in the health data. In other words, in order to meet the first set of change point criteria, the differences in the health data may have to be larger and / or exist for a longer period of time than the other set of change point criteria described herein (e.g., the second set of change point criteria of box 814). As described herein, the first set of change point criteria may also include a minimum threshold value, which may represent the amount of change in the data required to be medically relevant. The minimum threshold value may be determined by a medical professional and / or using modeling of previous use cases. Each data type may be associated with its own minimum threshold, which may also depend on the length of the time period being considered and whether the data is being evaluated as an initial change point (e.g., possibly a higher threshold) or a secondary change point (e.g., possibly a lower threshold). The minimum threshold may be hard-coded.

[0108] If the answer at block 806 is no, process 800 continues to block 808. At block 808, process 800 includes the user device prohibiting the generation of notifications about the change point. Block 808 may essentially mean that because no change point was identified at block 804, the user device does not need to generate a notification.

[0109] At box 810, process 800 includes: the user device defines a new time window for evaluating the user's health data. The new time window can be a new dynamically adjustable time window, as described herein. In some examples, the time window can be a new time window compared to the initial time window. For example, the initial time window can be four weeks, and the new time window can be twenty-six weeks. After box 810, process 800 includes: the user device accesses various types of health data obtained during the time window (e.g., the new window this time). Loops 804, 806, 808, 810 and back to 804 can be repeated iteratively until all health data of the user (e.g., different data types) have been evaluated across different windows using the first change point criterion set. If during any of these iterative loops, the answer at 806 is yes, process 800 proceeds to box 812.

[0110] At block 812, process 800 includes the user device generating a notification about the first change point. The notification may include information about the change point, such as a textual description of how the data changed, the date the change point occurred, a graphical depiction of the data corresponding to the change point, and any other information about the change point. The notification may include a payload of data and metadata to enable the notification to be appropriately presented on a display screen of the user device.

[0111] At box 814, process 800 includes: the user device determines whether the health data satisfies a second set of change point criteria. In some examples, the second set of change point criteria may correspond to the first set of change point criteria, but differ from the first set of change point criteria in terms of strictness. For example, the second set of change point criteria may represent a more relaxed criterion than the first set of change point criteria. In other words, health data that meets the first set of change point criteria will always meet the second set of change point criteria, but health data that meets the second set of change point criteria may not meet the first set of change point criteria. When it has been found that health data of the first data type meets the first set of change point criteria, the evaluation at box 814 may be health data of other data types that may be related to the first data type. For example, assuming that the evaluation at box 806 indicates that the user has increased her number of steps so that the user device has identified a change point in the step data type, box 814 can check all other data types to identify whether any other data types are also trending upward (e.g., exercise minutes, etc.), even if other data types lag behind the step data. This is why the second set of change point criteria can have a lower threshold than the first set of change point criteria.

[0112] In practice, the evaluation at box 814 will look for change points under less stringent criteria than the first set of change point criteria, so that notifications about these change points are then generated to be included with the notifications generated at 812. Therefore, if the answer at box 814 is yes, process 800 proceeds to box 816. At box 816, process 800 includes: the user device generates notifications about the second change point. These notifications can represent data types that have met the second set of change point criteria. The notification can be combined with the notification generated at box 812 and provided by the user device for presentation at the user device (e.g., display screen) as a single notification at box 818. If the answer at box 814 is no, process 800 continues directly to box 818 and passes the notification about the first change point generated at 812, without including any other notifications about any other change points together with the notification from 812.

[0113] Fig. 9A flow chart illustrating a process 900 for identifying changes in health data and providing opportunistic notifications to a user device according to at least one example is illustrated. Process 900 may specifically correspond to a method in which a first user device identifies a trend in health data, decides whether to notify a user of the trend, and decides whether to notify a user of trends in other health data. Health application 1010 ( Fig.10 )Whether in the wearable electronic device 1005( Fig.10 )、User equipment 1002( Fig.10 ), or the service provider computer 1004 ( Fig.10 ) or in any suitable combination of the foregoing devices, can be performed Fig. 9 Thus, although process 900 is described as being performed by a user device, it should be understood that other user devices (eg, wearable user devices) or a server may perform process 900 with limited adaptation.

[0114] Process 900 begins at block 902 with a user device accessing first health data of a first data type collected during a time window. In some examples, the time window may be at least one of about one month or about six months. In some examples, the first health data and the second health data may be collected by one or more sensors of the user device, collected by one or more sensors of a different user device and shared with the user device, collected by one or more sensors of an accessory user device and shared with the user device, accessed from a memory such as a database on the user device, accessed from a cloud-based storage service, and obtained in any other suitable manner.

[0115] At box 904, process 900 includes: the user device compares a first quantity of first health data associated with a first time subwindow of the time window with a second quantity of the first health data associated with a second time subwindow of the time window to identify a first change in the first health data.

[0116] In some examples, process 900 may further include: the user device iteratively evaluating health data from sub-windows of different sizes within the time window to define a first time sub-window and a second time sub-window.

[0117] At block 906, process 900 includes: the user device determines that the first change is a first change point in the first health data. This may include determining based on a first evaluation of the first amount and the second amount of the first health data relative to a first change point criteria set. In some examples, when the first health data indicates an upward trend or a downward trend, the first change point may include a data point in the first time window.

[0118] At block 908 , process 900 includes the user device generating a notification including information about the first change point.

[0119] At box 910, process 900 includes: the user device includes information about a second change point in the second health data in a notification when a second evaluation of the second health data relative to a second set of change point criteria indicates a second change point. In some examples, the first change point may be statistically correlated with the second change point. In some examples, the notification may include one or more graphical elements corresponding to at least one of the first change point or the second change point. In some examples, the first health data and the second health data may be associated with the user. In this example, the first change point and the second change point may be related to the user's health-related behavior.

[0120] In some examples, the second health data may be a second data type different from the first data type and collected during a time window. In some examples, the first change point criterion set may include a first threshold set, and the second change point criterion set may include a second threshold set different from the first threshold set. In some examples, the first threshold set may be looser than the second threshold set. In some examples, the first change point criterion set may include a first statistical significance criterion (e.g., a first P value determined using a T test) and a first statistical value criterion (e.g., a first effect size value), and the second change point criterion set may include a second statistical significance criterion (e.g., a second P value determined using a T test) and a second statistical value criterion (e.g., a second effect size value). In some examples, the statistical significance criteria between the first set and the second set may be different, and the statistical value criteria between the first set and the second set may be the same. As described herein, the second change point criterion set may also include a minimum threshold value that may represent the amount of change in the data required to be medically relevant.

[0121] In some examples, a first change point criterion in the first change point criterion set is unique to the first data type, and a second change point criterion in the first change point criterion set is common to a corresponding third change point criterion in the second change point criterion set.

[0122] In some examples, process 900 may further include: the user device provides a notification for presentation at a display of the user device. In some examples, process 900 may further include: after providing the notification for presentation at the display of the user device, prohibiting the generation of additional notifications for a fixed period of time. The fixed time period may correspond to a cool-down period during which the user device prohibits notifying the user of changes in data of a particular data type. This can be used to ensure that users do not get too many notifications, especially when they change their behavior in a sufficiently consistent and significant way that notifications can be triggered more frequently (e.g., increasing their daily step count by 1,000 times per day for a week).

[0123] In some examples, process 900 may further include: the user device compares a third amount of the first health data associated with a third time subwindow of the time window with a fourth amount of the first health data associated with a fourth time subwindow of the time window to identify a third change in the first health data. In this example, process 900 may further include: the user device determines that the third change is a third change point in the first health data based on a third evaluation of the third amount and the fourth amount of the first health data relative to the first change point criterion set. In this example, process 900 may further include: the user device selects between the first change point and the third change point based on the corresponding magnitudes of the first change and the third change. For example, since both the first change point and the third change point can indicate that the user has experienced a statistically significant change in behavior during the time window, the user device can select a change point with a larger magnitude as the selected change point to notify the user. In this example, generating a notification may include: generating a notification including information about the selected change point.

[0124] In some examples, using the health update sharing techniques described herein, the first health data can be shared with different user devices for processing. For example, process 900 may include: a first user device associated with a first user collects the first health data. In this example, accessing the first health data at box 902 may include: receiving the first health data from the first user device by a second user device associated with a second user. In this example, process 900 may further include: providing a notification for presentation at the second user device. In this example, process 900 may further include: the second user device requests the first health data on behalf of the first user from a cloud-based server storing the first health data.

[0125] Fig.10An exemplary architecture or environment 1000 configured to implement techniques related to sharing of health data updates between user devices according to at least one example is illustrated. In some examples, the exemplary architecture 1000 can be further configured to enable a user device 1002 (e.g., user device 104), a service provider computer 1004 (e.g., service provider 106), and a wearable electronic device 1005 (e.g., an exemplary accessory device) to share information. In some examples, these devices can be connected via one or more networks 1008 and / or 1006 (e.g., via Bluetooth, WiFi, the Internet, etc.). In the architecture 1000, one or more users can manage, control, or otherwise utilize the wearable electronic device 1005 via one or more networks 1006 using the user device 1002. Additionally, in some examples, the wearable electronic device 1005, the service provider computer 1004, and the user device 1002 can be configured or otherwise constructed as a single device. For example, the wearable electronic device 1005 and / or the user device 1002 can be configured to implement the examples described herein as a single computing unit, performing the examples described above and below without describing other devices.

[0126] In some examples, the networks 1006, 1008 may include any one or combination of many different types of networks, such as a wired network, the Internet, a wireless network, a cellular network, a satellite network, other private networks and / or public networks, or any combination thereof. Although the illustrated example shows a user device 1002 accessing a service provider computer 1004 via the network 1008, the described techniques may be equally applicable to instances where the user device 1002 interacts with the service provider computer 1004 via a landline, via a public telephone booth, or in any other manner. It is also noted that the described techniques may be applied in other client / server arrangements (e.g., set-top boxes, etc.) as well as in non-client / server arrangements (e.g., locally stored applications, peer-to-peer configurations, etc.).

[0127] As described above, the user device 1002 can be configured to collect and / or manage user activity data that may be received from the wearable electronic device 1005. In some examples, the wearable electronic device 1005 can be configured to provide the user's health, fitness, activity, and / or medical data to a third party or first party application (e.g., a service provider computer 1004). In turn, the data can be used by the user device 1002 to identify trends and / or for sharing. The user device 1002 can be any type of computing device, such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a laptop computer, a desktop computer, a thin client device, a tablet computer, a wearable device, etc. In some examples, the user device 1002 can communicate with the service provider computer 1004 and / or the wearable electronic device 1005 via the network 1008, 1006 or via other network connections.

[0128] In an exemplary configuration, the user device 1002 may include at least one memory 1014 and a processing unit (or processor) 1016. The processor 1016 may be implemented in hardware, computer executable instructions, firmware, or a combination thereof as appropriate. The computer executable instructions or firmware implementation of the processor 1016 may include computer executable instructions or machine executable instructions written in any suitable programming language to perform the various functions described. The user device 1002 may also include a geographic location device (e.g., a global positioning system (GPS) device, etc.) for providing and / or recording geographic location information associated with the user device 1002. In some examples, the wearable user device 1005 may also include a geographic location device for providing and / or recording geographic location information associated with the wearable user device 1005.

[0129] The memory 1014 can store program instructions that can be loaded and executed on the processor 1016 and data generated during the execution of these programs. Depending on the configuration and type of the user device 1002, the memory 1014 can be a volatile memory (such as a random access memory (RAM)) and / or a non-volatile memory (such as a read-only memory (ROM), flash memory, etc.). The user device 1002 may also include additional removable storage devices and / or non-removable storage devices 1026, including but not limited to magnetic storage devices, optical disks, and / or tape storage devices. The disk drive and its associated non-transitory computer-readable medium can provide a non-volatile storage device for computer-readable instructions, data structures, program modules, and other data for the computing device. In some specific implementations, the memory 1014 may include a variety of different types of memory, such as static random access memory ("SRAM"), dynamic random access memory ("DRAM"), or ROM. Although the volatile memory described herein may be referred to as RAM, any volatile memory that will not retain the data stored therein after being unplugged from the host and / or power supply is appropriate.

[0130] Removable and non-removable memory 1014 and additional storage device 1026 are examples of non-transient computer-readable storage media. For example, non-transient computer-readable storage media may include volatile or non-volatile, removable or non-removable media, which are implemented by any method or technology to store information such as computer-readable instructions, data structures, program modules or other data. Memory 1014 and additional storage device 1026 are examples of non-transient computer storage media. Additional types of computer storage media that may be present in user device 104 may include, but are not limited to: phase change RAM (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital video disk (DVD) or other optical storage device, cassette, tape, disk storage device or other magnetic storage device, or any other medium that can be used to store the desired information and can be accessed by user device 1002. Any combination of the above should also be included in the scope of non-transient computer-readable storage media. Alternatively, the computer-readable communication medium may include computer-readable instructions, program modules, or other data transmitted within a data signal such as a carrier wave or other transmission means. However, as used herein, computer-readable storage media does not include computer-readable communication media.

[0131] The user device 1002 may also include a communication connection 1028 that allows the user device 1002 to communicate with a data repository, another computing device or server, a user terminal, and / or other devices via the network 1008, 1006. The user device 1002 may also include an I / O device 1030, such as a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, an operating system 1032, and / or one or more applications or services for implementing the features disclosed herein, including the health application 1010(1). In some examples, the health application 1010(1) may be configured to implement the features described herein. As described in detail with reference to subsequent figures, the wearable user device 106 may include a memory that includes a similar health application 1010(2) that can be accessed by one or more processors of the wearable user device 106. The service provider computer 1004 may also include a memory 1042 that includes the health application 1010(3). In this manner, the techniques described herein may be implemented by any one or a combination of more than one of computing devices (eg, wearable user device 1005 , user device 1002 , or service provider computer 1004 ).

[0132] The service provider computer 1004 may also be any type of computing device, such as, but not limited to, a mobile phone, a smart phone, a PDA, a laptop computer, a desktop computer, a thin client device, a tablet computer, a wearable device, a server computer, a virtual machine instance, etc. In some examples, the service provider computer 1004 may communicate with the user device 1002 and / or the wearable user device 1005 via the network 1008 , 1006 or via other network connections.

[0133] In an exemplary configuration, the service provider computer 1004 may include at least one memory 1042 and one or more processing units (or processors) 1044. The processor 1044 may be implemented in hardware, computer executable instructions, firmware, or a combination thereof, as appropriate. The computer executable instructions or firmware implementation of the processor 1044 may include computer executable instructions or machine executable instructions written in any suitable programming language to perform the various functions described.

[0134] The memory 1042 can store program instructions that can be loaded and executed on the processor 1044 and data generated during the execution of these programs. Depending on the configuration and type of the service provider computer 1004, the memory 1042 can be a volatile memory (such as RAM) and / or a non-volatile memory (such as ROM, flash memory, etc.). The service provider computer 1004 may also include additional removable storage devices and / or non-removable storage devices 1046, including but not limited to magnetic storage devices, optical disks and / or tape storage devices. Disk drives and their associated non-transient computer-readable media can provide non-volatile storage devices for computer-readable instructions, data structures, program modules and other data for computing devices. In some specific implementations, the memory 1042 may include a variety of different types of memory, such as SRAM, DRAM or ROM. Although the volatile memory described herein may be referred to as RAM, any volatile memory that will not retain the data stored therein after being unplugged from the host and / or power supply is appropriate. Removable and non-removable memory 1042 and additional storage devices 1046 are additional examples of non-transient computer-readable storage media.

[0135] The service provider computer 1004 may also contain communication connections 1048 that allow the service provider computer 1004 to communicate with a data repository, another computing device or server, a user terminal, and / or other devices via the networks 1008, 1006. The service provider computer 1004 may also include I / O devices 1050, such as a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, a speaker, a printer, and the like.

[0136] Turning to the contents of memory 1042 in more detail, memory 1042 may include an operating system 1052 and / or one or more applications or services for implementing the features disclosed herein, including health application 1010 (3).

[0137] The examples described herein may take the form of, be incorporated into, or operate with a suitable wearable electronic device. An example of such a device is Fig.11, and in the form of a wearable mechanism 1100. As shown, the mechanism 1100 can be worn on the wrist of the user and fixed to the wrist by a band. The mechanism 1100 can have various functions, including but not limited to: keeping time; monitoring the physiological signals of the user and providing health-related information based at least in part on these signals; communicating with other electronic devices (via wired or wireless means), which can be different types of devices with different functions: providing alerts to the user, which prompts can include audio, tactile, visual and / or other sensory outputs, any or all of which can be synchronized with each other; visually depicting data on a display; collecting data from one or more sensors that can be used to initiate, control or modify the operation of the device; determining the location of a touch on the surface of the device and / or the amount of force applied to the device, and using either or both as input; accepting voice input to control one or more functions; accepting tactile input to control one or more functions; and so on.

[0138] Alternative examples of suitable electronic devices include phones; tablet computing devices; portable media players; etc. Other suitable electronic devices may include laptops / notebook computers, personal digital assistants, touch screens, input-sensitive tablets or surface tablets, etc.

[0139] In some examples, electronic devices can accept various bands, strips, or other retaining mechanisms (collectively referred to as "bands"). These bands can be removably connected to the electronic device via lugs received in recesses or other holes in the device. The lugs can be part of the band, or can be separate (and / or independent) from the band. Generally speaking, the lugs can lock into the recesses of the electronic device, thereby maintaining the connection between the band and the device. The user can release the locking mechanism to allow the lugs to slide out or otherwise move out of the recesses. In some examples, the recesses can be formed in the band, and the lugs can be attached or incorporated into the device.

[0140] The user can change the combination of bands and electronic devices, allowing the two categories to be mixed and matched. It should be understood that devices with other forms and / or functions may include similar recesses and may releasably mate with lugs and / or bands incorporating lugs. In this way, an ecosystem of bands and devices can be envisioned, where each band and device can be compatible with each other. As another example, a single band may be used to connect to a device; in such an example, the band may include an electrical interconnect that allows the two devices to send signals to each other and thereby interact with each other.

[0141] In many examples, electronic devices can keep time and display time, essentially acting as a watch or the like. The time can be displayed in analog or digital format, depending on the device, its settings, and (in some cases) the user's preferences. Typically, the time is displayed on a digital display stack that forms part of the exterior of the device.

[0142] The display stack may include a cover element, such as a cover glass, that covers the display. The cover glass need not be formed of glass, but glass is an option; it may be formed of sapphire, zirconium oxide, aluminum oxide, chemically strengthened glass, hardened plastic, etc. Likewise, the display may be a liquid crystal display, an organic light emitting diode display, or any other suitable display technology. In addition to other elements, in some examples, the display stack may include a backlight.

[0143] The device may also include one or more touch sensors to determine the location of a touch on the cover glass. The touch sensor may be incorporated into or on the display stack to determine the location of the touch. The touch sensor may be self-capacitive in some examples, mutual-capacitive in other examples, or a combination thereof.

[0144] Similarly, the device may include a pressure sensor to determine the amount of force applied to the cover glass. The force sensor may be a capacitive sensor in some examples and a strain sensor in other examples. In either example, the force sensor is typically transparent and made of a transparent material, or is located below or away from the display so as not to interfere with the view of the display. The force sensor may, for example, take the form of two capacitor plates separated by silicone or other deformable material. As the capacitor plates move closer together under the action of an external force, the change in capacitance can be measured and the external force value is related to the change in capacitance. In addition, by comparing the relative capacitance changes from the force sensor or from multiple points on the force sensor, one or more locations where the force is applied can be determined. In one example, the force sensor may take the form of a pad extending below the periphery of the display. Depending on the example, the pad may be segmented or integral.

[0145] Electronic devices can also provide alerts to users. Alerts can be generated in response to: a change in device status (one example is low power); the device receiving information (such as receiving a message); communication between the device and another mechanism / device (such as a second type of device notifying the device that a message is waiting or a communication is in progress); the operating state of an application (such as as part of a game or when an appointment on a calendar is approaching) or the operating state of an operating system (such as when the device is turned on or off); etc. The number and types of alert triggers are varied.

[0146] The alarm may be auditory, visual, tactile, or a combination thereof. A tactile actuator may be housed within the device and may move linearly to generate a tactile output (although in alternative examples, the tactile actuator may be rotary or any other type). A speaker may provide the auditory component of the alarm, and the above-mentioned display may provide the visual alarm component. In some examples, a dedicated light, display, or other visual output component may be used as part of the alarm.

[0147] The auditory, tactile, and / or visual components of the alert may be synchronized to provide an overall experience to the user. One or more components may be delayed relative to other components to produce a desired synchronization between them. The components may be synchronized so that they are perceived substantially simultaneously; as an example, the initiation of the tactile output may be slightly earlier than the auditory output because the tactile output may take longer to be perceived than the audio. As another example, the tactile output (or portion thereof) may be initiated substantially before the auditory output, but at a weaker or even subthreshold level, so that the wearer can receive the auditory output.

[0148] Fig.12 An exemplary schematic diagram of a wearable electronic device 1200 is depicted. The wearable electronic device 1200 may be an example of a wearable user device 805. Fig.12 As shown, device 1200 includes one or more processing units 1202 configured to access memory 1204 having instructions stored thereon.

[0149] Both removable and non-removable memory 1204 are examples of non-transient computer-readable storage media. For example, non-transient computer-readable storage media may include volatile or non-volatile, removable or non-removable media, which are implemented by any method or technology to store information such as computer-readable instructions, data structures, program modules or other data. Memory 1204 is an example of non-transient computer storage media. Additional types of computer storage media that may be present in user device 104 may include, but are not limited to: phase change RAM (PRAM), SRAM, DRAM, RAM, ROM, EEPROM, flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital video disc (DVD) or other optical storage devices, cassettes, tapes, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required information and can be accessed by user device 1200. Any combination of the above should also be included in the scope of non-transient computer-readable storage media. Alternatively, a computer-readable communication medium may include computer-readable instructions, program modules or other data sent in a data signal such as a carrier or other transmission means. However, as used herein, computer-readable storage media does not include computer-readable communication media.

[0150] The instructions or computer program may be configured to perform one or more of the operations or functions described with respect to the device 1200 (e.g., health application 1010(2)). For example, the instructions may be configured to control or coordinate the operation of various components of the device. Such components include, but are not limited to, a display 1206, one or more input / output components 1208, one or more communication channels 1210, one or more sensors 1212, a speaker 1214, a microphone 1216, a battery 1218, a wireless power source 1220, a biosensor 1222, and / or one or more tactile feedback devices 1224. In some examples, the speaker and microphone may be combined into a single unit and / or may share a common port through the housing of the device.

[0151] Fig.12 The processing unit 1202 may be implemented as any electronic device capable of processing, receiving, or sending data or instructions. For example, the processing unit 1202 may include one or more of the following: a microprocessor, a central processing unit (CPU), an application specific integrated circuit (ASIC), a digital signal processor (DSP), or a combination of such devices. As described herein, the term "processor" is intended to cover a single processor or processing unit, multiple processors, multiple processing units, or one or more other appropriately configured computing elements.

[0152] like Fig.12 As shown, the device 1200 may also include one or more acoustic elements, including a speaker 1214 and / or a microphone 1216. The speaker 1214 may include drive electronics or circuitry and may be configured to generate an audible sound or sound signal in response to a command or input. Similarly, the microphone 1216 may also include drive electronics or circuitry and may be configured to receive an audible sound or sound signal in response to a command or input. The speaker 1214 and the microphone 1216 may be acoustically coupled to a port or opening in the housing that may allow acoustic energy to pass through but may prevent liquid and other debris from entering.

[0153] Exemplary electronic devices can communicate with other electronic devices via wired connections or wirelessly. Data can be transferred between devices, allowing one device to relay information to another device; control another device; use another device's sensors, outputs and / or inputs; and the like. Fig.13A user 1300 is depicted wearing a first electronic device 1302, with a second electronic device 1304 in a pocket. Data can be sent wirelessly between the electronic devices 1302, 1304, allowing the user 1300 to receive, view, and interact with data from the second device 1304 via the first electronic device 1302. Thus, the user 1300 can access some or all of the functionality of the second device via the first electronic device 1302 without actually interacting directly with the second device 1304. In some examples, the second electronic device 1304 can be an example of a user device 802. The first electronic device 1302 can be an example of a wearable user device 805.

[0154] In addition, electronic devices 1302, 1304 can not only cooperate to share data, but also share functionality. For example, one of the two devices can combine sensors, applications or functions that another device lacks. An electronic device lacking such functions can request these capabilities from another device, which can be wirelessly shared with the requesting device. Therefore, multiple devices can operate together to provide extended functions, software, access, etc. between two devices and ultimately provide to users. As a non-limiting example, electronic device 1302 may not be able to make or receive calls, and second device 1304 may be able to perform these operations. Nevertheless, a user can make and / or receive calls through first device 1302, and the first device can use second device 1304 to actually make or receive calls.

[0155] As another non-limiting example, the electronic device 1302 can communicate wirelessly with a nearby sales terminal, thereby allowing the user to quickly and efficiently conduct transactions, such as selling, purchasing, or returning merchandise. The electronic device can use near-field communication technology to perform these and other functions.

[0156] As described above, a strip can be connected to two electronic devices and can serve as a wired communication path between the two devices. As another example, the devices can communicate wirelessly, allowing one device to relay information from a second device to a user. This latter example can be particularly useful when the second device is inaccessible.

[0157] Certain examples may include one or more biometric sensors to measure certain physiological characteristics of the user. For example, the device may include a photoplethysmography sensor to determine the user's heart rate or blood oxygen level. The device may also or alternatively include electrodes for measuring the user's body impedance, which may allow the device to estimate body fat percentage, electrical activity of the body, body impedance, and the like. Also included are blood pressure, UV exposure, and the like. Depending on the sensors incorporated into or associated with the electronic device, various user characteristics may be measured and / or estimated, allowing different health data to be provided to the user. In some examples, the sensed biometric data may be used in part to determine the user's historical activity data, current activity data, and / or predict the user's activity data.

[0158] Some examples can charge wirelessly. For example, an inductive charging base can send power to an inductive receiver within a device to charge the device's battery. In addition, by changing the inductive field between the device and the base, data can be transferred between the two. As a simple non-limiting example, when the device is placed on the base, this can be used to wake the base from a low-power sleep state to an active charging state. Other wireless charging systems (e.g., near-field magnetic resonance and radio frequency) can also be used. Alternatively, the device can also use wired charging achieved through electrodes.

[0159] In some examples, the device may include a rotational input, which may take the form of a crown with a stem. The crown and stem may be rotated to provide the rotational input. The rotation of the stem and / or crown may be sensed optically, electrically, magnetically, or mechanically. Additionally, in some examples, the crown and stem may also move laterally, thereby providing a second type of input to the device.

[0160] Likewise, an electronic device may include one or more buttons. The button(s) may be pressed to provide another input to the device. In various examples, the button may be a dome switch, a rocker switch, an electrical contact, a magnetic switch, etc. In some examples, the button may be waterproof or otherwise sealed to protect from environmental influences.

[0161] Various examples may include or otherwise incorporate one or more motion sensors. A motion sensor may detect motion of a device and provide, modify, stop, or otherwise affect a state, output, or input of a device or associated application based at least in part on the motion. As non-limiting examples, movement may be used to silence a device or acknowledge an alarm generated by the device. Example motion sensors include accelerometers, gyro sensors, magnetometers, GPS sensors, distance sensors, and the like. Some examples may use a GPS sensor to facilitate or enable location and / or navigation assistance.

[0162] Certain examples may incorporate ambient light sensors. Ambient light sensors may allow a device to sense the brightness of its environment and adjust certain operating parameters accordingly. For example, an electronic device may modify the brightness of a display in response to the sensed ambient light. As another example, an electronic device may turn off a display if little or no light is sensed for a period of time.

[0163] These and other functions, operations, and capabilities of the electronic device will become apparent upon reading the entire specification.

[0164] Some examples of wearable electronic devices may include one or more sensors that can be used to calculate health indicators or other health-related information. As an example, a wearable electronic device can be used as a wearable health assistant that provides health-related information (in real time or non-real time) to a user, an authorized third party, and / or an associated monitoring device.

[0165] Fig.12 An exemplary electronic device 1200 having one or more biometric sensors is depicted. The electronic device 1200 may be an example of a wearable user device 805. Fig.12 As shown, a series of light sources and photodetectors 1251 to 1254 can be arranged on the back of the device 1200. In one example, the light sources 1251 to 1253 are formed by light emitting diode (LED) elements, which are configured to emit light into a part of the wearer's body (e.g., a wrist). The photodetector 1254 is shared between multiple light sources 1251 to 1253 and is configured to receive light reflected from the body. The photodetector can be formed by a photodiode material, which is configured to generate a signal based at least in part on the received light. In a specific implementation, the signal generated by the photodetector 1254 is used to calculate a health indicator associated with the wearer. In some cases, the light sources 1251 to 1253 and the photodetector 1254 form a photoplethysmography (PPG) sensor. The first light source 1251 may include, for example, a green LED, which may be suitable for detecting blood perfusion in the wearer's body. The second light source 1252 may include, for example, an infrared LED, which may be suitable for detecting changes in the water content or other characteristics of the body. The third light source 1253 can be a similar type or a different type of LED element, depending on the sensing configuration. The optical (e.g., PPG) sensor can be used to calculate various health indicators, including but not limited to heart rate, breathing rate, blood oxygen level, blood volume estimation, blood pressure, or a combination thereof. One or more of the light sources 1251 to 1253 and the photodetector 1254 can also be used for optical data transmission with a base or other device. Although Fig.12One example is depicted, but the number of light sources and / or photodetectors may be different in different examples. For example, another example may use more than one photodetector. Another example may also use more than one photodetector. Fig.12 Fewer or more light sources as depicted in the examples.

[0166] In addition, if Fig.14 As shown, device 1400 includes a plurality of electrodes 1431, 1432, 1433, 1434 located on or near an outer surface of device 1400. In this example, device 1400 includes a first electrode 1431 and a second electrode 1432 located on or near a back surface of device body 1410. In this example, first electrode 1431 and second electrode 1432 are configured to make electrical contact with the skin of a user wearing device 1400. In some cases, first electrode 1431 and second electrode 1432 are used to make electrical measurements or receive electrical signals from the user's body. In addition, as shown in FIG. Fig.14 As shown, the device 1400 may include a third electrode 1433 and a fourth electrode 1434 located on or near the periphery of the housing of the device body 1410. In this example, the third electrode 1433 and the fourth electrode 1434 are configured to be contacted by one or more fingers of the wearable device 1400 or the user interacting with the device. In some cases, the third electrode 1433 and the fourth electrode 1434 are also used to perform electrical measurements or receive electrical signals from the user's body. In some cases, the first electrode 1431, the second electrode 1432, the third electrode 1433, and the fourth electrode 1434 are all used to perform a measurement or a series of measurements that can be used to calculate another health indicator of the user's body. The health indicators that can be calculated using electrodes include, but are not limited to, heart function (ECG, EKG), water content, body fat ratio, skin galvanic response resistance, and combinations thereof.

[0167] exist Fig.14 In the depicted configuration, the electronic device 1400 includes one or more holes in the housing 1410. Light sources 1451 to 1454 can be disposed in each hole. In one example, each light source 1451 to 1453 is implemented as a light emitting diode (LED). In this example, one or more sensors are formed using four holes, three light sources 1451 to 1453 and a single detector 1454. Other examples can include any number of light sources. For example, in some examples, two light sources can be used.

[0168] The light sources may operate within the same wavelength range of light, or the light sources may operate within different wavelength ranges of light. As an example, when two light sources are used, one of the light sources may emit light within the visible wavelength range, while the other light source may emit light within the infrared wavelength range. When four light sources are used, two light sources may emit light within the visible wavelength range, while the other two light sources may emit light within the infrared wavelength range. For example, in one example, at least one light source may emit light within a wavelength range associated with the color green, while another light source may emit light within the infrared wavelength range. When it is necessary to measure a physiological parameter of a user, the light source emits light to the user's skin, and the optical sensor senses the amount of reflected light. In some cases, a modulation pattern or sequence may be used to turn the light source on and off and sample or sense the reflected light.

[0169] Hereinafter, additional terms are described to facilitate understanding of the present disclosure.

[0170] Clause 1. A computer-implemented method, the method comprising:

[0171] In response to a first user input at a first user device, identifying a second user associated with a second user device to receive a health check associated with the first user of the first user device.

[0172] Health data update;

[0173] In response to a second user input at the first user device, identifying a set of authorized identifiers, each set of authorized identifiers representing health data to be shared with the second user device

[0174] The type of update;

[0175] generating a sharing request identifying the set of authorized identifiers and a unique identifier identifying the second user; and

[0176] Information associated with the sharing request is shared with the second user equipment.

[0177] Clause 2. The computer-implemented method of Clause 1, wherein each authorized identifier in the set of authorized identifiers corresponds to a health subject.

[0178] Clause 3. The computer-implemented method of Clause 1, further comprising: receiving a message indicating that the second user accepts the sharing request.

[0179] Clause 4. A computer-implemented method according to clause 1, wherein sharing the information associated with the sharing request with the second user device includes: transmitting the information to a server, wherein the information is configured to enable the server to transmit the sharing request to the second user device.

[0180] Clause 5. The computer-implemented method of clause 1, further comprising:

[0181] generating a set of health data updates based at least in part on the set of authorized identifiers; and

[0182] The health data update sets are grouped into transactions.

[0183] Clause 6. The computer-implemented method of Clause 5, further comprising: detecting an occurrence of a triggering event prior to generating the set of health data updates.

[0184] Clause 7. A computer-implemented method according to Clause 6, wherein the triggering event includes at least one of the following: opening of a health application on the first user device, collection of a type of health data associated with the authorized identifier set, collection of a certain amount of health data associated with the authorized identifier set, achievement of a health-based goal associated with the authorized identifier set, or a trend in health data associated with the authorized identifier set.

[0185] Clause 8. The computer-implemented method of Clause 5, further comprising transmitting information associated with the transaction to a server to enable the server to store the transaction according to a storage area associated with the unique identifier identifying the second user.

[0186] Clause 9. The computer-implemented method of Clause 5, wherein each health data update in the set of health data updates comprises source data and update metadata, and wherein the transaction comprises the set of health data updates and transaction metadata.

[0187] Clause 10. A computer-implemented method according to clause 9, wherein the update metadata is usable by the second user device to determine display of the set of health data updates, and the transaction metadata is usable by the second user device to select between different transactions.

[0188] Clause 11. The computer-implemented method of Clause 1, wherein the unique identifier comprises a shared identifier that can be used to upload and download data from a server.

[0189] Clause 12. The computer-implemented method of clause 1, further comprising:

[0190] generating different sharing requests identifying different sets of authorized identifiers and different unique identifiers identifying a third user of a third user device; and

[0191] Information associated with the different sharing request is transmitted to a server, the information being configured to enable the server to transmit the different sharing request to the third user device.

[0192] Clause 13. The computer-implemented method of Clause 12, wherein the different set of authorization identifiers is different than the set of authorization identifiers.

[0193] Clause 14. The computer-implemented method of Clause 1, wherein the health data update is based on health data collected or generated by at least one of the first user device or an accessory device of the first user device.

[0194] Clause 15. The computer-implemented method of Clause 14, wherein the first user device comprises a handheld user device and the accessory device comprises a wearable user device.

[0195] Clause 16. One or more non-transitory computer-readable storage devices, the one or more non-transitory computer-readable storage devices comprising computer-executable instructions, which, when executed by a computer system, cause the computer system to perform the method described in clauses 1 to 15.

[0196] Clause 17. A system, comprising:

[0197] one or more memories for storing computer-executable instructions; and

[0198] One or more processors configured to access the one or more memories and execute the computer-executable instructions to perform the method according to any of clauses 1 to 15.

[0199] Clause 18. A computer-implemented method, the method comprising:

[0200] receiving, at a first user device associated with a first user, a sharing request associated with sharing health data of a second user associated with a second user device with the first user device;

[0201] requesting from the server transaction data stored by the server;

[0202] receiving, in response to requesting the transaction data, a first transaction package from the server, the first transaction package including first one or more health data updates associated with the health data of the second user;

[0203] extracting the first one or more health data updates from the first transaction packet; and

[0204] A user interface of the first user device is populated with information associated with the first one or more health data updates.

[0205] Clause 19. The computer-implemented method of Clause 18, wherein the sharing request includes a unique identifier of the first user.

[0206] Clause 20. A computer-implemented method according to clause 18, the method further comprising: receiving a second transaction package from the server in response to requesting the transaction data, the second transaction package including a second one or more health data updates associated with the health data of the second user associated with a third user device.

[0207] Clause 21. The computer-implemented method of clause 20, further comprising:

[0208] One of the first transaction bundle or the second transaction bundle is selected as the selected transaction bundle based at least in part on a set of transaction selection rules, and wherein:

[0209] Extracting the first one or more health data updates from the first transaction package includes:

[0210] extracting the selected one or more health data updates from the selected transaction package; and

[0211] Populating the user interface of the first user device with information associated with the first one or more health data updates includes populating the user interface of the first user device with information associated with the selected one or more health data updates.

[0212] Clause 22. The computer-implemented method of Clause 21, wherein selecting one of the first transaction bundle or the second transaction bundle as the selected transaction bundle based at least in part on the set of transaction selection rules comprises performing at least one of:

[0213] determining collection time information for each of the first transaction bundle and the second transaction bundle based at least in part on transaction metadata respectively associated with each of the first transaction bundle and the second transaction bundle;

[0214] determining application version information for each of the first transaction bundle and the second transaction bundle based at least in part on the transaction metadata associated with each of the first transaction bundle and the second transaction bundle, respectively;

[0215] determining accessory device information for each of the first transaction bundle and the second transaction bundle based at least in part on the transaction metadata associated with each of the first transaction bundle and the second transaction bundle, respectively; or

[0216] Device identifier information associated with each of the second user device and the third user device used to collect the first transaction and the second transaction bundle is determined based at least in part on the transaction metadata associated with each of the first transaction bundle and the second transaction bundle, respectively.

[0217] Clause 23. One or more non-transitory computer-readable storage devices, the one or more non-transitory computer-readable storage devices comprising computer-executable instructions, which, when executed by a computer system, cause the computer system to perform the method described in clauses 18 to 22.

[0218] Clause 24. A system, comprising:

[0219] one or more memories for storing computer-executable instructions; and

[0220] One or more processors configured to access the one or more memories and execute the computer-executable instructions to perform the method according to any of clauses 18 to 22.

[0221] Clause 25. A computer-implemented method, the method comprising:

[0222] determining a first change point in the health data of a first type;

[0223] determining a second change point in a second type of health data related to the first type of health data;

[0224] generating a notification including first information associated with the first change point based on determining that the first change point satisfies a first set of notification criteria; and

[0225] Based on determining that the second change point satisfies a second set of notification criteria, second information associated with the second change point is included in the notification.

[0226] Clause 26. A computer-implemented method according to Clause 25, wherein determining the first change point includes: comparing first health data of the first type of health data from a first time period with second health data of the first type of health data from a second time period, and the second time period overlaps with the first time period.

[0227] Clause 27. The computer-implemented method of Clause 25, wherein the first change point comprises a change in the first type of health data over a given time period.

[0228] Clause 28. A computer-implemented method according to Clause 25, the method further comprising: after determining the first change point and before determining the second change point, selecting the second type of health data for evaluation based at least in part on a predefined correlation between the first type of health data and the second type of health data.

[0229] Clause 29. The computer-implemented method of Clause 25, wherein the first set of notification criteria is independent of the second type of health data and the second set of notification criteria is dependent on the first type of health data.

[0230] Clause 30. The computer-implemented method of clause 25, wherein:

[0231] Determining the first change point in the first type of health data includes: determining the first change point according to a first threshold; and

[0232] Determining the second change point in the second type of health data includes: determining the second change point according to a second threshold.

[0233] Clause 31. The computer-implemented method of Clause 30, wherein the first threshold is an absolute threshold and the second threshold is a relative threshold.

[0234] Clause 32. The computer-implemented method of Clause 31, wherein the relative threshold depends at least in part on the first change point occurring before the second change point.

[0235] Clause 33. The computer-implemented method of Clause 25, further comprising: providing the notification for presentation at a user device.

[0236] Clause 34. The computer-implemented method of Clause 25, wherein first health data of the first type of health data is collected by at least one of a handheld user device or a wearable user device.

[0237] Clause 35. A computer-implemented method according to clause 25, wherein the first set of notification criteria includes a recency criterion and a trend criterion, wherein the recency criterion defines a time threshold between transmitting notifications associated with the first type of health data, and the trend criterion defines a condition under which a directional change in a trend in the first type of health data will trigger a notification.

[0238] Clause 36. The computer-implemented method of Clause 25, the method further comprising: based on determining that the second change point does not satisfy the second set of notification criteria, prohibiting the second information associated with the second change point from being included in the notification.

[0239] Clause 37. The computer-implemented method of Clause 25, wherein the first type of health data and the second type of health data are associated with a single user profile and are indicative of health of a user associated with the single user profile.

[0240] Clause 38. The computer-implemented method of clause 25, wherein:

[0241] Determining the first change point in the first type of health data includes: determining the first change point at a first time; and

[0242] Determining the second change point in the second type of health data includes: determining the second change point at a second time after the first time.

[0243] Clause 39. The computer-implemented method of clause 25, wherein:

[0244] Determining that the first change point satisfies the first set of notification criteria includes: determining at a first time that the first change point satisfies the first set of notification criteria, and

[0245] Determining that the second change point satisfies the second set of notification criteria includes determining that the second change point is likely to occur within a threshold amount of time after the first time.

[0246] Clause 40. One or more non-transitory computer-readable storage devices, the one or more non-transitory computer-readable storage devices comprising computer-executable instructions, which, when executed by a computer system, cause the computer system to perform the method described in clauses 25 to 39.

[0247] Clause 41. A system, comprising:

[0248] one or more memories for storing computer-executable instructions; and

[0249] One or more processors configured to access the one or more memories and execute the computer-executable instructions to perform a method according to any of clauses 25 to 39.

[0250] Clause 42. A computer-implemented method, the method comprising:

[0251] accessing first health data of a first data type collected during a time window;

[0252] comparing a first quantity of the first health data associated with a first time subwindow of the time window with a second quantity of the first health data associated with a second time subwindow of the time window to identify a first change in the first health data;

[0253] determining, based on a first evaluation of the first quantity and the second quantity of the first health data relative to a first set of change point criteria, that the first change is a first change point in the first health data;

[0254] generating a notification including information about the first change point; and

[0255] When a second evaluation of the second health data relative to a second set of change point criteria indicates a second change point, information about the second change point in the second health data is included in the notification.

[0256] Clause 43. The computer-implemented method of clause 42, wherein the second health data is of a second data type and is collected during the time window, the second data type being different from the first data type.

[0257] Clause 44. The computer-implemented method of Clause 43, wherein the first set of change point criteria includes a first set of thresholds and the second set of change point criteria includes a second set of thresholds different from the first set of thresholds.

[0258] Clause 45. The computer-implemented method of Clause 44, wherein the second set of thresholds is more relaxed than the first set of thresholds.

[0259] Clause 46. A computer-implemented method according to Clause 42, wherein the first set of change point criteria includes a first statistical significance criterion and a first statistical value criterion, and the second set of change point criteria includes a second statistical significance criterion and a second statistical value criterion.

[0260] Clause 47. The computer-implemented method of Clause 42, wherein the time window comprises at least one of approximately one month or approximately six months.

[0261] Clause 48. A computer-implemented method according to Clause 42, the method further comprising: iteratively evaluating portions of the first health data from sub-windows of different sizes within the time window to define the first time sub-window and the second time sub-window.

[0262] Clause 49. The computer-implemented method of clause 42, wherein the first change point comprises a data point in the first time window when the first health data indicates an upward trend or a downward trend.

[0263] Clause 50. The computer-implemented method of Clause 42, wherein the first change point is statistically correlated with the second change point.

[0264] Clause 51. The computer-implemented method of Clause 42, further comprising: providing the notification for presentation at a display of a user device.

[0265] Clause 52. The computer-implemented method of Clause 51, further comprising: prohibiting generation of additional notifications for a fixed period of time after providing the notification for presentation at the display of the user device.

[0266] Clause 53. The computer-implemented method of Clause 42, wherein the notification comprises one or more graphical elements corresponding to at least one of the first change point or the second change point.

[0267] Clause 54. The computer-implemented method of clause 42, wherein the first health data and the second health data are collected by one or more sensors of a user device, and wherein the computer-implemented method is performed by the user device.

[0268] Clause 55. A computer-implemented method according to Clause 42, wherein a first change point criterion in the first change point criterion set is unique to the first data type, and a second change point criterion in the first change point criterion set is common to a corresponding third change point criterion in the second change point criterion set.

[0269] Clause 56. The computer-implemented method of clause 42, further comprising:

[0270] comparing a third quantity of the first health data associated with a third time subwindow of the time window with a fourth quantity of the first health data associated with a fourth time subwindow of the time window to identify a third change in the first health data;

[0271] determining, based on a third evaluation of the third quantity and the fourth quantity of the first health data relative to the first set of change point criteria, that the third change is a third change point in the first health data; and

[0272] A selection is made between the first change point and the third change point based on respective magnitudes of the first change and the third change, and wherein generating the notification comprises generating the notification including information about the selected change point.

[0273] Clause 57. A computer-implemented method according to Clause 42, wherein the first health data and the second health data are associated with a user, and wherein the first change point and the second change point are related to changes in health-related behavior of the user.

[0274] Clause 58. A computer-implemented method according to clause 42, wherein the first health data is collected by a first user device associated with a first user, and wherein accessing the first health data includes: receiving the first health data from the first user device by a second user device associated with a second user.

[0275] Clause 59. The computer-implemented method of Clause 58, further comprising: providing the notification for presentation at the second user device.

[0276] Clause 60. The computer-implemented method of clause 58, wherein receiving the first health data from the first user device comprises: the second user device requesting the first health data on behalf of the first user from a cloud-based server storing the first health data.

[0277] Clause 61. One or more non-transitory computer-readable storage devices, the one or more non-transitory computer-readable storage devices comprising computer-executable instructions, which, when executed by a computer system, cause the computer system to perform the method described in clauses 42 to 60.

[0278] Clause 62. A system, comprising:

[0279] one or more memories for storing computer-executable instructions; and

[0280] One or more processors configured to access the one or more memories and execute the computer-executable instructions to perform a method according to any of clauses 42 to 60.

[0281] Exemplary methods and systems for managing user equipment connections are described above. Some or all of these systems and methods may, but need not, be at least partially comprised of, for example, at least Figures 1 to 14. Although many examples are described above with reference to personal, activity and / or health-related information, it should be understood that these techniques can be used to manage any type of user information or non-user information (e.g., any type of data). In addition, various non-limiting examples are described in the foregoing description. For the purpose of explanation, many specific configurations and details are set forth in order to provide a thorough understanding of the examples. However, it should also be apparent to those skilled in the art that some examples can be implemented without these specific details. In addition, well-known features are sometimes omitted or simplified to prevent confusion with the examples described herein.

[0282] Various examples can be further implemented in a variety of operating environments, in some cases, operating environments can include one or more user computers, computing devices or processing devices that can be used to operate any of a plurality of applications. User equipment or client devices can include any of many general personal computers, such as desktop computers or laptop computers running standard operating systems, and cellular devices, wireless devices and handheld devices that run mobile software and can support multiple networking protocols and instant messaging protocols. Such a system can also include multiple workstations that run a variety of commercially available operating systems and are used for purposes such as development and database management in any of other known applications. These devices can also include other electronic devices, such as virtual terminals, thin clients, game systems and other devices that can communicate via a network.

[0283] Most examples utilize at least one network familiar to those skilled in the art to support communications using any of a variety of commercial protocols such as TCP / IP, OSI, FTP, UPnP, NFS, CIFS, and AppleTalk. The network can be, for example, a local area network, a wide area network, a virtual private network, the Internet, an intranet, an extranet, a public switched telephone network, an infrared network, a wireless network, and any combination thereof.

[0284] In the example of utilizing a web server, the web server can run any of a variety of server or middle-tier applications, including HTTP servers, FTP servers, CGI servers, data servers, Java servers, and business application servers. The server can also execute programs or scripts to respond to requests from user devices, such as by executing one or more application programs, which can be implemented as one or more scripts or programs written in any programming language, such as C, C# or C++ or any scripting language such as Perl, Python or TCL and their combinations. One or more servers may also include a database server, including but not limited to and Those commercially available.

[0285] Environment can include various data storage repositories and other memory and storage media, as discussed above. These can reside in various locations, such as on a storage medium local to one or more computers or on a storage medium away from any or all computers on a network (and / or reside in one or more computers). In a specific set of examples, information can reside in a storage area network (SAN) familiar to those skilled in the art. Similarly, any necessary files for performing functions belonging to a computer, server or other network device can be stored locally and / or remotely as needed. In the case where the system includes a computerized device, each such device can include hardware elements that can be electrically coupled via a bus, including, for example, at least one central processing unit (CPU), at least one input device (e.g., mouse, keyboard, controller, touch screen or keypad) and at least one output device (e.g., display device, printer or speaker). Such systems can also include one or more storage devices, such as disk drives, optical storage devices and solid-state storage devices such as RAM or ROM, as well as removable media devices, memory cards, flash memory cards, etc.

[0286] Such devices may also include a computer-readable storage medium reader, a communication device (e.g., a modem, a network card (wireless or wired), an infrared communication device, etc.) and a working memory as described above. A computer-readable storage medium reader may be connected to or configured to receive a non-transient computer-readable storage medium representing a remote, local, fixed and / or removable storage device, and a storage medium for temporarily and / or more permanently containing, storing, sending and retrieving computer-readable information. Systems and various devices typically also include a plurality of software applications, modules, services or other elements located within at least one working memory device, including an operating system and an application such as a client application or a browser. It should be understood that alternative examples may have many variations described above. For example, custom hardware may also be used, and / or specific elements may be implemented in hardware, software (including portable software, such as applets), or both. In addition, connections with other computing devices such as network input / output devices may be employed.

[0287] Non-transitory storage media and computer-readable media for containing code or portions of code may include any suitable media known or used in the art, including storage media, such as but not limited to volatile and non-volatile, removable and non-removable media, which may be implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, DVD or other optical storage devices, cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by system devices. Based at least in part on the disclosure and teachings provided herein, a person of ordinary skill in the art will understand other ways and / or methods for implementing the various examples.

[0288] Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the present disclosure as set forth in the claims.

[0289] Other variations are within the spirit of the present disclosure. Thus, while the disclosed technology is susceptible to various modifications and alternative constructions, certain illustrative examples thereof are shown in the drawings and have been described in detail above. However, it should be understood that it is not intended to limit the present disclosure to the particular forms disclosed, but on the contrary, it is intended to cover all modifications, alternative constructions, and equivalent forms that fall within the spirit and scope of the present disclosure as defined by the appended claims.

[0290] The use of the terms "one" and "an" and "the" and similar indicators in the context of describing the disclosed examples (especially in the context of the following claims) will be interpreted as covering the singular and plural, unless otherwise stated or clearly contradicted by the context. Unless otherwise noted, the terms "comprising", "having", "including" and "containing" should be understood as open terms (e.g., meaning "including but not limited to"). The term "connected" is interpreted as being partially or completely included, attached or joined together even if there are intervening things. Unless otherwise stated herein, the description of the numerical range herein is only intended to be used as a simple method of referring to each individual value falling within the range individually, and each individual value is incorporated into the specification as if quoted separately in this article. All methods described herein can be performed in any suitable order, unless otherwise stated herein or otherwise clearly contradicted by the context. Unless otherwise stated, the use of any and all examples or exemplary language (e.g., "such as") provided herein is only intended to better illustrate the examples of the present disclosure, and will not limit the scope of the present disclosure. Any language in the specification should not be interpreted as indicating that any undeclared element is essential to the practice of the present disclosure.

[0291] Unless specifically stated otherwise, disjunctive language such as the phrase "at least one of X, Y, or Z" is understood in context as generally used to present an item, term, etc., which may be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is generally not intended to, and should not, imply that certain examples require that at least one of X, at least one of Y, or at least one of Z each be present.

[0292] Preferred examples of the present disclosure are described herein, including the best mode known to the inventor for carrying out the present disclosure. After reading the foregoing description, variations of those preferred examples may become apparent to those of ordinary skill in the art. The inventor expects that the technical staff will appropriately adopt such variations, and the inventor intends to practice the present disclosure in a manner different from that specifically described herein. Therefore, as permitted by applicable law, the present disclosure includes all modifications and equivalents of the subject matter recorded in the claims attached to the present disclosure. In addition, unless otherwise noted herein or clearly contradictory to the context, the present disclosure includes any combination of all possible variations of the above-mentioned elements.

[0293] All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

[0294] As described above, one aspect of the present technology is to share health data updates between user devices, which may include storing some aspect of the data on a server. The present disclosure contemplates that, in some instances, these collected data may include personally identifiable information (PII) data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, health record data, or any other identification information or personal or health information.

[0295] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to provide a family member or friend with a view of health data updates. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0296] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Users can easily access such policies and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should be carried out after receiving the informed consent of the user. Additionally, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices for different types of personal data should be maintained in each country.

[0297] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to advertising delivery services or other services related to health record management, the technology of the present invention may be configured to allow a user to choose to "opt in" or "opt out" to participate in the collection of personal information data at any time during or after registration for the service. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that the user's personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.

[0298] In addition, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and data deletion. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. Where appropriate, de-identification can be facilitated by removing specific identifiers (e.g., date of birth), controlling the amount or characteristics of stored data (e.g., collecting location data at the city level rather than the address level), controlling how the data is stored (e.g., aggregating data across users), and / or other methods.

[0299] Therefore, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A computer-implemented method, the method comprising: include: accessing first health data of a first data type collected during a time window; comparing a first quantity of the first health data associated with a first time subwindow of the time window with a second quantity of the first health data associated with a second time subwindow of the time window to identify a first change in the first health data; determining, based on a first evaluation of the first quantity and the second quantity of the first health data relative to a first set of change point criteria, that the first change is a first change point in the first health data; generating a notification including information about the first change point; as well as When a second evaluation of the second health data relative to a second set of change point criteria indicates a second change point, information about the second change point in the second health data is included in the notification.

2. A computer-implemented method according to claim 1, wherein the second health data belongs to a second data type and is collected during the time window, the second data type is different from the first data type, wherein the first change point criterion set includes a first threshold set and the second change point criterion set includes a second threshold set different from the first threshold set, and wherein the second threshold set is more relaxed than the first threshold set.

3. A computer-implemented method according to claim 1, wherein the first change point criterion set includes a first statistical significance criterion and a first statistical value criterion, and the second change point criterion set includes a second statistical significance criterion and a second statistical value criterion. 4 . The computer-implemented method of claim 1 , wherein the time window comprises at least one of approximately one month or approximately six months.

5. The computer-implemented method of claim 1 , further comprising: include: Portions of the first health data from sub-windows of different sizes within the time window are iteratively evaluated to define the first time sub-window and the second time sub-window. 6 . The computer-implemented method of claim 1 , wherein when the first health data indicates an upward trend or a downward trend, the first change point comprises a data point in the first time sub-window.

7. One or more non-transitory computer-readable storage devices comprising computer-executable instructions that, when executed by one or more processors of a computer system, cause the computer system to perform operations comprising: accessing first health data of a first data type collected during a time window; comparing a first quantity of the first health data associated with a first time subwindow of the time window with a second quantity of the first health data associated with a second time subwindow of the time window to identify a first change in the first health data; determining, based on a first evaluation of the first quantity and the second quantity of the first health data relative to a first set of change point criteria, that the first change is a first change point in the first health data; generating a notification including information about the first change point; as well as When a second evaluation of the second health data relative to a second set of change point criteria indicates a second change point, information about the second change point in the second health data is included in the notification.

8. The one or more non-transitory computer-readable storage devices of claim 7, wherein the first change point is statistically correlated with the second change point.

9. The one or more non-transitory computer-readable storage devices of claim 1, further comprising additional computer-executable instructions that, when executed by the one or more processors, cause the computer system to perform additional operations including: providing the notification for presentation at a display of a user device; and Generating additional notifications is inhibited for a fixed period of time after providing the notification for presentation at the display of the user device.

10. The one or more non-transitory computer-readable storage devices of claim 7, wherein the notification includes one or more graphical elements corresponding to at least one of the first change point or the second change point.

11. The one or more non-transitory computer-readable storage devices of claim 7, wherein the first health data and the second health data are collected by one or more sensors of a user device.

12. One or more non-transitory computer-readable storage devices according to claim 7, wherein a first change point criterion in the first change point criterion set is unique to the first data type, and a second change point criterion in the first change point criterion set is common to a corresponding third change point criterion in the second change point criterion set.

13. The one or more non-transitory computer-readable storage devices of claim 7, further comprising additional computer-executable instructions that, when executed by the one or more processors, cause the computer system to perform additional operations including: comparing a third quantity of the first health data associated with a third time subwindow of the time window with a fourth quantity of the first health data associated with a fourth time subwindow of the time window to identify a third change in the first health data; determining, based on a third evaluation of the third quantity and the fourth quantity of the first health data relative to the first set of change point criteria, that the third change is a third change point in the first health data; as well as A selection is made between the first change point and the third change point based on respective magnitudes of the first change and the third change, and wherein generating the notification comprises generating the notification including information about the selected change point.

14. The one or more non-transitory computer-readable storage devices of claim 7, wherein the first health data is collected by a first user device associated with a first user, wherein accessing the first health data include: The first health data is received from the first user device by a second user device associated with a second user, and wherein receiving the first health data from the first user device includes: the second user device requests the first health data on behalf of the first user from a cloud-based server storing the first health data.

15. A computer system, wherein the computer system include: a memory configured to store computer-executable instructions; and A processor configured to access the memory and execute the computer executable instructions to at least perform the following operations: accessing first health data of a first data type collected during a time window; comparing a first quantity of the first health data associated with a first time subwindow of the time window with a second quantity of the first health data associated with a second time subwindow of the time window to identify a first change in the first health data; determining, based on a first evaluation of the first quantity and the second quantity of the first health data relative to a first set of change point criteria, that the first change is a first change point in the first health data; generating a notification including information about the first change point; as well as When a second evaluation of the second health data relative to a second set of change point criteria indicates a second change point, information about the second change point in the second health data is included in the notification.