Health application user interface

Abstract

The present disclosure generally relates to health-related user interfaces, such as health application user interfaces. In some embodiments, user interfaces for managing health-related data are described. In some embodiments, user interfaces for viewing health data are described. In some embodiments, user interfaces related to sharing health data are described.

Description

[0001] This application is a divisional application of patent application No. 202080039662.3, filed on May 29, 2020, entitled "Health Application User Interface".

[0002] Cross-references to related applications

[0003] This application claims priority to U.S. Patent Application No. 16 / 880,714, entitled "HEALTH APPLICATION USER INTERFACES", filed May 21, 2020, and U.S. Provisional Patent Application No. 62 / 856,061, entitled "HEALTH APPLICATION USER INTERFACES", filed June 1, 2019, the contents of each of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0004] This disclosure relates in general to computer user interfaces, and more specifically to technologies and user interfaces for managing health information and functions. Background Technology

[0005] Electronic devices collect, store, and access users' health-related information. These devices provide users with the ability to manage health information and related functions using electronic devices. Summary of the Invention

[0006] However, some technologies used to manage health information and functions with electronic devices are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may involve multiple keystrokes or button presses. These technologies require more time than necessary, resulting in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0007] Therefore, this technology provides electronic devices with faster and more efficient methods and interfaces for managing health information and functions. Such methods and interfaces can optionally supplement or replace other methods for managing health information and functions. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-machine interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging sessions.

[0008] A method is described according to some embodiments. In some embodiments, the method is performed at an electronic device having a display device. In some embodiments, the method includes: displaying via the display device a first instance of a first user interface including a first notification, the first notification causing the display of a first set of data when selected; and after displaying the first instance of the first user interface, displaying a second instance of the first user interface, wherein: based on determining that a set of interaction criteria is met, the set of interaction criteria including criteria met when the first set of data has been displayed, and based on determining that a first set of removal criteria is not met, the first set of removal criteria including a first criterion based on a first time period, the second instance of the first user interface includes the first notification; based on determining that the set of interaction criteria is met and based on determining that the first set of removal criteria is met, the second instance of the first user interface does not include the first notification; based on determining that the set of interaction criteria is not met and based on determining that a second set of removal criteria is not met, the second instance of the first user interface includes the first notification; and based on determining that the set of interaction criteria is not met and based on determining that the second set of removal criteria is met, the second instance of the first user interface does not include the first notification.

[0009] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: displaying, via the display device, a first instance of a first user interface including a first notification, the first notification causing the display of a first set of data when selected; and, after displaying the first instance of the first user interface, displaying a second instance of the first user interface, wherein: based on determining that a set of interaction criteria is met, including criteria met when the first set of data has been displayed, and based on determining that a first set of removal criteria is not met, including a first criterion based on a first time period, the second instance of the first user interface includes the first notification; based on determining that the set of interaction criteria is met and based on determining that the first set of removal criteria is met, the second instance of the first user interface does not include the first notification; based on determining that the set of interaction criteria is not met and based on determining that a second set of removal criteria is not met, including a second criterion based on a second time period greater than the first time period, the second instance of the first user interface includes the first notification; and based on determining that the set of interaction criteria is not met and based on determining that the second set of removal criteria is met, the second instance of the first user interface does not include the first notification.

[0010] According to some embodiments, a transient computer-readable storage medium is described, the transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: displaying via the display device a first instance of a first user interface including a first notification, the first notification causing the display of a first set of data when selected; and after displaying the first instance of the first user interface, displaying a second instance of the first user interface, wherein: based on determining that a set of interaction criteria is met, the set of interaction criteria including criteria met when the first set of data has been displayed, and based on determining that a first set of removal criteria is not met, the first set of removal criteria including a first criterion based on a first time period, the second instance of the first user interface includes the first notification; based on determining that the set of interaction criteria is met and based on determining that the first set of removal criteria is met, the second instance of the first user interface does not include the first notification; based on determining that the set of interaction criteria is not met and based on determining that a second set of removal criteria is not met, the second instance of the first user interface includes the first notification; and based on determining that the set of interaction criteria is not met and based on determining that the second set of removal criteria is met, the second instance of the first user interface does not include the first notification.

[0011] An electronic device is described according to some embodiments. In some embodiments, the electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: displaying a first instance of a first user interface including a first notification via the display device, the first notification causing the display of a first set of data when selected; and displaying a second instance of the first user interface after displaying the first instance of the first user interface, wherein: the second instance of the first user interface includes the first notification if a set of interaction criteria is satisfied, the set of interaction criteria including criteria satisfied when the first set of data has been displayed, and a first set of removal criteria is not satisfied, the first set of removal criteria including a first criterion based on a first time period; the second instance of the first user interface does not include the first notification if the set of interaction criteria is satisfied and the first set of removal criteria is satisfied; the second instance of the first user interface includes the first notification if the set of interaction criteria is not satisfied and a second set of removal criteria is not satisfied, the second set of removal criteria including a second criterion based on a second time period greater than the first time period; and the second instance of the first user interface does not include the first notification if the set of interaction criteria is not satisfied and the second set of removal criteria is satisfied.

[0012] According to some embodiments, an electronic device is described. In some embodiments, the electronic device includes: a display device; means for displaying via the display device a first instance of a first user interface including a first notification, the first notification causing the display of a first set of data when selected; and means for displaying a second instance of the first user interface after displaying the first instance of the first user interface, wherein: based on determining that a set of interaction criteria is met, the set of interaction criteria including criteria met when the first set of data has been displayed, and based on determining that a first set of removal criteria is not met, the first set of removal criteria including a first criterion based on a first time period, the second instance of the first user interface includes the first notification; based on determining that the set of interaction criteria is met and based on determining that the first set of removal criteria is met, the second instance of the first user interface does not include the first notification; based on determining that the set of interaction criteria is not met and based on determining that a second set of removal criteria is not met, the second instance of the first user interface includes the first notification; and based on determining that the set of interaction criteria is not met and based on determining that the second set of removal criteria is met, the second instance of the first user interface does not include the first notification.

[0013] A method is described according to some embodiments. In some embodiments, the method is performed at an electronic device having a display device. In some embodiments, the method includes: receiving first health data; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first region: including a first representation of the first health data based on determination that a data type corresponding to the first health data has been identified by a user; and excluding a representation of the first health data based on determination that a data type corresponding to the first health data has not been identified by a user; and a second region: including a second representation of the first health data, different from the first representation, based on determination that a first set of highlight criteria has been met; and excluding a second representation of the first health data based on determination that the first set of highlight criteria has not been met.

[0014] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: receiving first health data; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: a first region: including a first representation of the first health data based on determination that a data type corresponding to the first health data has been identified by user input; and excluding a representation of the first health data based on determination that a data type corresponding to the first health data has not been identified by user input; and a second region: including a second representation of the first health data, different from the first representation, based on determination that a first set of feed criteria has been met; and excluding a second representation of the first health data based on determination that the first set of feed criteria has not been met.

[0015] According to some embodiments, a transient computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: receiving first health data; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: a first region: including a first representation of the first health data based on determination that a data type corresponding to the first health data has been identified by user input; and excluding a representation of the first health data based on determination that a data type corresponding to the first health data has not been identified by user input; and a second region: including a second representation of the first health data, different from the first representation, based on determination that a first set of feed criteria has been met; and excluding a second representation of the first health data based on determination that the first set of feed criteria has not been met.

[0016] According to some embodiments, an electronic device is described. In some embodiments, the electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving first health data; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first area: including a first representation of the first health data based on determination that a data type corresponding to the first health data has been identified by user input; and excluding a representation of the first health data based on determination that a data type corresponding to the first health data has not been identified by user input; and a second area: including a second representation of the first health data different from the first representation based on determination that a first set of feed criteria has been met; and excluding a second representation of the first health data based on determination that the first set of feed criteria has not been met.

[0017] According to some embodiments, an electronic device is described. In some embodiments, the electronic device includes: a display device; means for receiving first health data; means for receiving a request to display a first user interface; and means for displaying the first user interface via the display device in response to receiving the request, the first user interface including: a first area: including a first representation of the first health data based on a determination that a data type corresponding to the first health data has been entered by the user; and excluding a representation of the first health data based on a determination that a data type corresponding to the first health data has not been entered by the user; and a second area: including a second representation of the first health data, different from the first representation, based on a determination that a first set of feed criteria has been met; and excluding a second representation of the first health data based on a determination that the first set of feed criteria has not been met.

[0018] A method is described according to some embodiments. In some embodiments, the method is performed at an electronic device having a display device. In some embodiments, the method includes: receiving clinical health record data corresponding to a specific health institution; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first area corresponding to a first type of clinical health record, wherein the first area includes: a first textual representation of the first clinical health record based on the clinical health record data, based on a determination that the first clinical health record in the first type of clinical health record fails to meet a first set of drawing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and a first graphical representation of the first clinical health record based on the clinical health record data, based on a determination that the first clinical health record meets the first set of drawing criteria; and a second area corresponding to a second type of clinical health record, wherein the second area includes: a second textual representation of the second clinical health record based on the clinical health record data, based on a determination that the second clinical health record in the second type of clinical health record fails to meet the first set of drawing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and a second graphical representation of the second clinical health record based on the clinical health record data, based on a determination that the second clinical health record meets the first set of drawing criteria.

[0019] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, one or more procedures include instructions for performing the following operations: receiving clinical health record data corresponding to a specific health institution; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via a display device, the first user interface including: a first area corresponding to a first type of clinical health record, wherein the first area includes: a first textual representation of the first clinical health record based on the clinical health record data, based on the determination that the first clinical health record in the first type of clinical health record fails to meet a first set of drawing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and a first graphical representation of the first clinical health record based on the clinical health record data, based on the determination that the first clinical health record meets the first set of drawing criteria; and a second area corresponding to a second type of clinical health record, wherein the second area includes: a second textual representation of the second clinical health record based on the clinical health record data, based on the determination that the second clinical health record in the second type of clinical health record fails to meet the first set of drawing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and a second graphical representation of the second clinical health record based on the determination that the second clinical health record meets the first set of drawing criteria.

[0020] According to some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, one or more procedures include instructions for performing the following operations: receiving clinical health record data corresponding to a specific health institution; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via a display device, the first user interface including: a first area corresponding to a first type of clinical health record, wherein the first area includes: a first textual representation of the first clinical health record based on the clinical health record data, based on the determination that the first clinical health record in the first type of clinical health record fails to meet a first set of drawing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and a first graphical representation of the first clinical health record based on the clinical health record data, based on the determination that the first clinical health record meets the first set of drawing criteria; and a second area corresponding to a second type of clinical health record, wherein the second area includes: a second textual representation of the second clinical health record based on the clinical health record data, based on the determination that the second clinical health record in the second type of clinical health record fails to meet the first set of drawing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and a second graphical representation of the second clinical health record based on the determination that the second clinical health record meets the first set of drawing criteria.

[0021] An electronic device is described based on some implementation schemes. In some embodiments, the electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving clinical health record data corresponding to a specific health institution; receiving a request to display a first user interface; and, in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first area corresponding to a first type of clinical health record, wherein the first area includes: a first textual representation of the first clinical health record based on the clinical health record data, based on a determination that the first clinical health record in the first type of clinical health record fails to meet a first set of drawing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and a first graphical representation of the first clinical health record based on the clinical health record data, based on a determination that the first clinical health record meets the first set of drawing criteria; and a second area corresponding to a second type of clinical health record, wherein the second area includes: a second textual representation of the second clinical health record based on the clinical health record data, based on a determination that the second clinical health record in the second type of clinical health record fails to meet the first set of drawing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and a second graphical representation of the second clinical health record based on the clinical health record data, based on a determination that the second clinical health record meets the first set of drawing criteria.

[0022] According to some embodiments, an electronic device is described. In some embodiments, the electronic device includes: a display device; means for receiving clinical health record data corresponding to a specific health institution; means for receiving a request to display a first user interface; and means for displaying the first user interface via the display device in response to receiving the request, the first user interface including: a first area corresponding to a first type of clinical health record, wherein the first area includes: a first text representation of the first clinical health record based on the clinical health record data, based on the determination that the first clinical health record in the first type of clinical health record fails to meet a first set of drawing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and a first graphical representation of the first clinical health record based on the clinical health record data, based on the determination that the first clinical health record meets the first set of drawing criteria; and a second area corresponding to a second type of clinical health record, wherein the second area includes: a second text representation of the second clinical health record based on the clinical health record data, based on the determination that the second clinical health record in the second type of clinical health record fails to meet the first set of drawing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and a second graphical representation of the second clinical health record based on the determination that the second clinical health record meets the first set of drawing criteria.

[0023] A method is described according to some embodiments. In some embodiments, the method is performed at an electronic device having a display device. In some embodiments, the method includes: receiving clinical health record data, the clinical health record data including: first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; receiving a request to display a first user interface; in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; receiving first user input corresponding to a selection of the first representation when displaying the first user interface; in response to receiving the first user input: displaying a second user interface via the display device, the second user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; receiving first user input corresponding to a selection of the first representation when displaying the first user interface; and in response to receiving the first user input: displaying a second user interface via the display device, the second user interface including: a first representation of a first type of clinical health record based on the first clinical health record data. A second representation of a first clinical health record in a clinical health record, wherein the second representation is different from the first representation; and a third representation of a second clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the third representation is different from the second representation, and the second clinical health record of the first type is different from the first clinical health record of the first type; receiving a second user input corresponding to a selection of the third representation when displaying the second user interface; and in response to receiving the second user input: displaying a third user interface via a display device, the third user interface including a fourth representation of the first clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the fourth representation is different from the first representation, and wherein the fourth representation is different from the second representation.

[0024] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: receiving clinical health record data, the clinical health record data including: first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; receiving a request to display a first user interface; in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; receiving first user input corresponding to a selection of the first representation when displaying the first user interface; and in response to receiving the first user input: displaying a second user interface via the display device, the second user interface including: based on the first clinical health record data... The second representation of a first clinical health record in a first type of clinical health record, wherein the second representation is different from the first representation; and a third representation of a second clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the third representation is different from the second representation, and the second clinical health record of the first type is different from the first clinical health record of the first type; receiving a second user input corresponding to a selection of the third representation when displaying the second user interface; and in response to receiving the second user input: displaying a third user interface via a display device, the third user interface including a fourth representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the fourth representation is different from the first representation, and wherein the fourth representation is different from the second representation.

[0025] According to some embodiments, a transient computer-readable storage medium is described, the transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: receiving clinical health record data, the clinical health record data including: first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; receiving a request to display a first user interface; in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; receiving first user input corresponding to a selection of the first representation when displaying the first user interface; and in response to receiving the first user input: displaying a second user interface via the display device, the second user interface including: based on the first clinical health record data... The second representation of a first clinical health record in a first type of clinical health record, wherein the second representation is different from the first representation; and a third representation of a second clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the third representation is different from the second representation, and the second clinical health record of the first type is different from the first clinical health record of the first type; receiving a second user input corresponding to a selection of the third representation when displaying the second user interface; and in response to receiving the second user input: displaying a third user interface via a display device, the third user interface including a fourth representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the fourth representation is different from the first representation, and wherein the fourth representation is different from the second representation.

[0026] According to some embodiments, an electronic device is described. In some embodiments, the electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving clinical health record data, the clinical health record data including: first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; receiving a request to display a first user interface; in response to receiving the request, displaying the first user interface via the display device, the first user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; receiving first user input corresponding to a selection of the first representation when displaying the first user interface; and in response to receiving the first user input: displaying via the display device. A second user interface comprising: a second representation of a first clinical health record in a first type of clinical health record based on first clinical health record data, wherein the second representation is different from the first representation; and a third representation of a second clinical health record in a first type of clinical health record based on first clinical health record data, wherein the third representation is different from the second representation, and the second clinical health record of the first type is different from the first clinical health record of the first type; receiving second user input corresponding to a selection of the third representation when displaying the second user interface; and, in response to receiving the second user input: displaying a third user interface via a display device, the third user interface comprising a fourth representation of a first clinical health record in a first type of clinical health record based on first clinical health record data, wherein the fourth representation is different from the first representation, and wherein the fourth representation is different from the second representation.

[0027] According to some embodiments, an electronic device is described. In some embodiments, the electronic device includes: a display device; means for receiving clinical health record data, the clinical health record data including: first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; means for receiving a request to display a first user interface; means for displaying the first user interface via the display device in response to receiving the request, the first user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; means for receiving a first user input corresponding to a selection of the first representation when displaying the first user interface; and means for displaying a second user interface via the display device in response to receiving the first user input, the second user interface including: a first representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data; means for receiving a first user input corresponding to a selection of the first representation when displaying the first user interface; and means for displaying a second user interface via the display device in response to receiving the first user input, the second user interface including: a first clinical health record data corresponding to a selection of the first clinical health record in a first type of clinical health record; means for receiving a first user input corresponding to a selection of the first clinical health record in a first type of clinical health record ... receiving a first user input corresponding to a selection of the first clinical health record in a first type of clinical health record; and means for receiving a first user input corresponding to a selection of the first clinical health record in a first type of clinical health record; and means for receiving a first user input corresponding to a selection of the first clinical health record in a first type of clinical health record; and means for receiving a first user input corresponding to a selection of the first clinical health record in a first type of clinical health record; and means for receiving a first user input corresponding to a selection The system includes: recording data for a second representation of a first clinical health record in a first type of clinical health record, wherein the second representation differs from the first representation; and recording data for a third representation of a second clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the third representation differs from the second representation, and the second clinical health record of the first type differs from the first clinical health record of the first type; means for receiving a second user input corresponding to a selection of the third representation when displaying a second user interface; and means for displaying a third user interface via a display device in response to receiving the second user input, the third user interface including a fourth representation of a first clinical health record in a first type of clinical health record based on the first clinical health record data, wherein the fourth representation differs from the first representation, and the fourth representation differs from the second representation.

[0028] A method is described according to some implementations. In some implementations, the method is performed at an electronic device having a display device, wherein the electronic device is associated with a first user account. In some embodiments, the method includes: receiving a request to display a first user interface; in response to receiving the first request, displaying the first user interface via a display device, the first user interface including: a first portion including a first category of capability representation; and a second portion including a first shared capability representation corresponding to a second user account; while displaying the first user interface: receiving first user input corresponding to a selection of the first category of capability representation; and receiving second user input corresponding to a selection of the first shared capability representation; in response to receiving the first user input, displaying a second user interface via a display device, the second user interface including a representation of first health data associated with the first user account of the first category; in response to receiving the second user input, displaying a third user interface via a display device, the third user interface including: a first portion including a second category of capability representation corresponding to health data associated with the second user account of the first category; while displaying the third user interface, receiving third user input corresponding to a selection of the second category of capability representation; and in response to receiving the third user input, displaying a fourth user interface via a display device, the fourth user interface including a representation of health data associated with the second user account of the first category.

[0029] In some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having a display device associated with a first user account. In some embodiments, one or more procedures include instructions for performing the following operations: receiving a request to display a first user interface; in response to receiving the first request, displaying the first user interface via a display device, the first user interface including: a first portion including a first category of capability representation; and a second portion including a first shared capability representation corresponding to a second user account; while displaying the first user interface: receiving first user input corresponding to a selection of the first category of capability representation; and receiving second user input corresponding to a selection of the first shared capability representation; in response to receiving the first user input, displaying a second user interface via a display device, the second user interface including a representation of first health data associated with the first user account of the first category; in response to receiving the second user input, displaying a third user interface via a display device, the third user interface including: a first portion including a second category of capability representation corresponding to health data associated with the second user account of the first category; while displaying the third user interface, receiving third user input corresponding to a selection of the second category of capability representation; and in response to receiving the third user input, displaying a fourth user interface via a display device, the fourth user interface including a representation of health data associated with the second user account of the first category.

[0030] In some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having a display device associated with a first user account. In some embodiments, one or more procedures include instructions for performing the following operations: receiving a request to display a first user interface; in response to receiving the first request, displaying the first user interface via a display device, the first user interface including: a first portion including a first category of capability representation; and a second portion including a first shared capability representation corresponding to a second user account; while displaying the first user interface: receiving first user input corresponding to a selection of the first category of capability representation; and receiving second user input corresponding to a selection of the first shared capability representation; in response to receiving the first user input, displaying a second user interface via a display device, the second user interface including a representation of first health data associated with the first user account of the first category; in response to receiving the second user input, displaying a third user interface via a display device, the third user interface including: a first portion including a second category of capability representation corresponding to health data associated with the second user account of the first category; while displaying the third user interface, receiving third user input corresponding to a selection of the second category of capability representation; and in response to receiving the third user input, displaying a fourth user interface via a display device, the fourth user interface including a representation of health data associated with the second user account of the first category.

[0031] According to some embodiments, an electronic device associated with a first user account is disclosed. In some embodiments, the electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a request to display a first user interface; and, in response to receiving the first request, displaying the first user interface via the display device, the first user interface including: a first portion including a first category of display representation; and a second portion including a first shared display representation corresponding to a second user account; and, when displaying the first user interface: receiving a first user input corresponding to a selection of the first category of display representation; and receiving a second user input corresponding to a selection of the first shared display representation. The user input is received twice; in response to receiving a first user input, a second user interface is displayed via a display device, the second user interface including a representation of first health data associated with a first user account of a first category; in response to receiving a second user input, a third user interface is displayed via a display device, the third user interface including: a first portion including: a second category indication corresponding to the health data associated with the second user account of the first category; when displaying the third user interface, receiving a third user input corresponding to a selection of the second category indication; and in response to receiving a third user input, a fourth user interface is displayed via a display device, the fourth user interface including a representation of health data associated with the second user account of the first category.

[0032] According to some implementation plans, electronic devices associated with the first user account have been disclosed. In some embodiments, the electronic device includes: a display device; means for receiving a request to display a first user interface; means for displaying the first user interface via the display device in response to receiving the first request, the first user interface including: a first portion including a first category of capability representation; and a second portion including a first shared capability representation corresponding to a second user account; means for performing the following operations when displaying the first user interface: receiving a first user input corresponding to a selection of the first category of capability representation; and receiving a second user input corresponding to a selection of the first shared capability representation; means for displaying a second user interface via the display device in response to receiving the first user input, the second user interface including a representation of first health data associated with the first user account of the first category; means for displaying a third user interface via the display device in response to receiving the second user input, the third user interface including: a first portion including a second category of capability representation corresponding to health data associated with the second user account of the first category; means for receiving a third user input corresponding to a selection of the second category of capability representation when displaying the third user interface; and means for displaying a fourth user interface via the display device in response to receiving the third user input, the fourth user interface including a representation of health data associated with the second user account of the first category.

[0033] A method is described according to some embodiments. In some embodiments, the method is performed at a first electronic device having a display device. In some embodiments, the method includes: receiving a request to share health data associated with the first electronic device; in response to receiving the request, displaying a first notification via the display device at a first time, the first notification including a first power indication, which, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; receiving first user input corresponding to the selection of the first power indication when displaying the notification; in response to receiving the first user input, initiating a process for sharing the health data associated with the first electronic device with the second electronic device; and after receiving the first user input: sharing the health data associated with the first electronic device with the second electronic device; and displaying a second notification corresponding to the sharing of the health data at a second time via the display device, the second notification including a second power indication, which, when selected, initiates a process for ending the sharing of the health data associated with the first electronic device with the second electronic device.

[0034] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a first electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: receiving a request to share health data associated with the first electronic device; in response to receiving the request, displaying a first notification via the display device at a first instant, the first notification including a first power indication, which, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; receiving first user input corresponding to the selection of the first power indication when displaying the notification; in response to receiving the first user input, initiating a process for sharing the health data associated with the first electronic device with the second electronic device; and after receiving the first user input: sharing the health data associated with the first electronic device with the second electronic device; and at a second instant, displaying a second notification corresponding to the sharing of the health data via the display device, the second notification including a second power indication, which, when selected, initiates a process for terminating the sharing of the health data associated with the first electronic device with the second electronic device.

[0035] According to some embodiments, a transient computer-readable storage medium is described, the transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device having a display device. In some embodiments, the one or more programs include instructions for performing the following operations: receiving a request to share health data associated with the first electronic device; in response to receiving the request, displaying a first notification via the display device at a first time, the first notification including a first power indication, which, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; receiving first user input corresponding to the selection of the first power indication when displaying the notification; in response to receiving the first user input, initiating a process for sharing the health data associated with the first electronic device with the second electronic device; and after receiving the first user input: sharing the health data associated with the first electronic device with the second electronic device; and at a second time, displaying a second notification corresponding to the sharing of the health data via the display device, the second notification including a second power indication, which, when selected, initiates a process for ending the sharing of the health data associated with the first electronic device with the second electronic device.

[0036] A first electronic device is described according to some embodiments. In some embodiments, the first electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a request to share health data associated with the first electronic device; in response to receiving the request, displaying a first notification via the display device at a first time, the first notification including a first power indication, which, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; receiving first user input corresponding to the selection of the first power indication when displaying the notification; in response to receiving the first user input, initiating a process for sharing the health data associated with the first electronic device with a second electronic device; and after receiving the first user input: sharing the health data associated with the first electronic device with the second electronic device; and at a second time, displaying a second notification corresponding to the sharing of the health data via the display device, the second notification including a second power indication, which, when selected, initiates a process for ending the sharing of the health data associated with the first electronic device with the second electronic device.

[0037] According to some embodiments, a first electronic device is described. In some embodiments, the first electronic device includes: a display device; means for receiving a request to share health data associated with the first electronic device; means for displaying a first notification via the display device in response to receiving the request, the first notification including a first power indication that, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; means for receiving first user input corresponding to the selection of the first power indication when displaying the notification; means for initiating a process for sharing the health data associated with the first electronic device with a second electronic device in response to receiving the first user input; and means for performing the following operations after receiving the first user input: sharing the health data associated with the first electronic device with the second electronic device; and displaying a second notification via the display device in response to the sharing of the health data, the second notification including a second power indication that, when selected, initiates a process for ending the sharing of the health data associated with the first electronic device with the second electronic device.

[0038] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0039] Therefore, faster and more efficient methods and interfaces are provided for managing health information and functions in devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used for managing health information and functions. Attached Figure Description

[0040] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein similar reference numerals indicate corresponding parts in all the drawings.

[0041] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some embodiments.

[0042] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0043] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

[0044] Figure 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0045] Figure 4A An exemplary user interface for a menu on an application on a portable multifunction device, according to some implementation schemes, is shown.

[0046] Figure 4B An exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display is shown according to some embodiments.

[0047] Figure 5A A personal electronic device according to some implementation schemes is shown.

[0048] Figure 5B This is a block diagram illustrating a personal electronic device according to some implementation schemes.

[0049] Figures 5C-5D Exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments are shown.

[0050] Figures 5E-5H Exemplary components and user interfaces of a personal electronic device according to some implementation schemes are shown.

[0051] Figures 6A-6Z An exemplary user interface related to viewing health data using an electronic device is shown according to some implementation schemes.

[0052] Figures 7A-7B This is a flowchart illustrating a method for managing notifications using electronic devices according to some implementation schemes.

[0053] Figures 8A-8B This is a flowchart illustrating a method for displaying health-related information using electronic devices, according to some implementation schemes.

[0054] Figures 9A-9B This is a flowchart illustrating a method for managing the representation of clinical health records using electronic devices, according to some implementation schemes.

[0055] Figures 10A-10B This is a flowchart illustrating a method for managing the representation of clinical health records using electronic devices, according to some implementation schemes.

[0056] Figures 11A-11C This is a flowchart illustrating a method for displaying health-related information for managing various user accounts using electronic devices, according to some implementation schemes.

[0057] Figure 12AA-Figure 12I An exemplary user interface related to viewing health data using an electronic device is shown according to some implementation schemes.

[0058] Figures 13A-13G An exemplary user interface related to sharing health data using electronic devices is shown according to some implementation schemes.

[0059] Figures 14A-14B This is a flowchart illustrating methods related to sharing health data according to some implementation schemes.

[0060] Figures 15A-15F An exemplary user interface related to viewing health data using an electronic device is shown according to some implementation schemes. Detailed Implementation

[0061] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0062] Electronic devices need to provide effective methods and interfaces for managing health information and functions. For example, providing timely health-related notifications and stopping the display of useless notifications is beneficial. Similarly, highlighting certain health-related information for users is advantageous. Such technologies can reduce the cognitive burden on users managing health information and functions, thereby improving productivity. Furthermore, such technologies can reduce processor power and battery power wasted in other ways on redundant user input.

[0063] under Figures 1A-1B , Figure 2 , Figure 3 , Figures 4A-4B and Figures 5A-5H A description of an exemplary device for performing management event notifications is provided. Figures 6A-6Z An exemplary user interface related to viewing health data using an electronic device is shown according to some implementation schemes. Figures 7A-7B This is a flowchart illustrating a method for managing notifications using electronic devices according to some implementation schemes. Figures 8A-8B This is a flowchart illustrating a method for displaying health-related information using electronic devices, according to some implementation schemes. Figures 9A-9B This is a flowchart illustrating a method for managing the representation of clinical health records using electronic devices, according to some implementation schemes. Figures 10A-10B This is a flowchart illustrating a method for managing the representation of clinical health records using electronic devices, according to some implementation schemes. Figures 11A-11C This is a flowchart illustrating a method for displaying health-related information for managing various user accounts using electronic devices, according to some implementation schemes. Figures 6A-6Z The user interface in the document is used to illustrate the process described below, including Figures 7A-7B , Figures 8A-8B , Figures 9A-9B , Figures 10A-10B , Figures 11A-11C The process in. Figure 12AA-Figure 12I An exemplary user interface related to viewing health data using an electronic device is shown according to some implementation schemes. Figures 13A-13G An exemplary user interface related to sharing health data using electronic devices is shown according to some implementation schemes. Figures 14A-14B This is a flowchart illustrating methods related to sharing health data according to some implementation schemes. Figures 13A-13G The user interface in the document is used to illustrate the process described below, including Figures 14A-14B The process in. Figures 15A-15F An exemplary user interface related to viewing health data using an electronic device is shown according to some implementation schemes.

[0064] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

[0065] The terminology used in the description of the various embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various embodiments and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “includes”, “including”, “comprises”, and / or “comprising”, when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0066] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "at," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" may optionally be interpreted as meaning "in response to determination..." or "in response to detection [the stated condition or event]."

[0067] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). In some embodiments, the electronic device is a computer system that communicates with a display generating component (e.g., via wireless or wired communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, “display” content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) to an integrated or external display generating component via a wired or wireless connection to visually generate content.

[0068] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0069] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camcorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0070] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0071] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0072] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on smaller devices with limited physical space, such smaller devices being used (e.g., on a touch-sensitive display) to display power indications and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0073] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's movement does not move. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of a user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception of a typical (or ordinary) user.

[0074] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

[0075] Memory 102 optionally includes high-speed random access memory and also optionally includes non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls other components of device 100 to access memory 102.

[0076] Peripheral interface 118 can be used to couple the device's input and output peripherals to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0077] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks and other devices, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE...). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

[0078] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to peripheral interface 118 for processing. Audio data is optionally retrieved by peripheral interface 118 from and / or transmitted to memory 102 and / or RF circuitry 108. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headphone or a headset with both output (e.g., a single-ear or dual-ear headphone) and input (e.g., a microphone).

[0079] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / send electrical signals to the other input control device 116. The other input control device 116 optionally includes physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some alternative embodiments, input controller 160 is optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., Figure 2 Optionally, 208) includes an increase / decrease button for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push-button (e.g., Figure 2(Ref. 206 in the original text). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking user gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

[0080] A quick press of the push button optionally disengages the touchscreen 112 from its lock or optionally initiates a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) optionally powers the device 100 on or off. The function of one or more buttons is optionally user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0081] The touch-sensitive display 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or sends electrical signals to the touchscreen 112. The touchscreen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0082] Touchscreen 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or haptic contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction set in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) and translate the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the contact point between touchscreen 112 and the user corresponds to the user's finger.

[0083] Touchscreen 112 optionally employs LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that from Apple Inc. (Cupertino, California). and iPod The technology used.

[0084] In some embodiments of the touchscreen 112, the touch-sensitive display optionally resembles the multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0085] In some embodiments, the touchscreen 112 has a touch-sensitive display as described in the following patent applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive”. (6) U.S. Patent Application No. 11 / 038,590 entitled “Input Devices”; (7) U.S. Patent Application No. 11 / 228,758 entitled “Virtual Input Device Placement On A Touch Screen User Interface”, filed September 16, 2005; (8) U.S. Patent Application No. 11 / 228,700 entitled “Operation Of A Computer With A Touch Screen Interface”, filed September 16, 2005; (9) U.S. Patent Application No. 11 / 228,737 entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”, filed September 16, 2005; and (10) U.S. Patent Application No. 11 / 367,749 entitled “Multi-Functional Hand-Held Device”, filed March 3, 2006. The full text of all these applications is incorporated herein by reference.

[0086] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally interact with touchscreen 112 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

[0087] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. Optionally, the touchpad is a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

[0088] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0089] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensor within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0090] The device 100 optionally also includes one or more depth camera sensors 175. Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 may optionally be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information are optionally acquired for video conferencing while the user views other video conferencing participants on a touchscreen display, and selfies with depth map data are captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the position of depth camera sensor 175 may be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen display for both video conferencing and still image and / or video image acquisition.

[0091] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1AA contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0092] The device 100 optionally also includes one or more proximity sensors 166. Figure 1A A proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, the proximity sensor is turned off and the touchscreen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0093] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0094] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "Methods and Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of device 100.

[0095] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or orientation.

[0096] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0097] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to… (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0098] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0099] In some implementations, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., determining whether the user has “clicked” an icon). In some implementations, at least a subset of the intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some specific implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set (e.g., by adjusting the individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level clicks on the “intensity” parameter).

[0100] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0101] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, and non-limitingly includes text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0102] In some implementations, the graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes from an application or the like to specify the graphic to be displayed, and, if necessary, also receives coordinate data and other graphic attribute data, and then generates screen image data for output to the display controller 156.

[0103] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0104] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).

[0105] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to phone 138 for use in location-based dialing; to camera 143 as image / video metadata; and to applications that provide location-based services, such as weather desktop apps, local yellow pages desktop apps, and map / navigation desktop apps).

[0106] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

[0107] • Contacts module 137 (sometimes called address book or contact list);

[0108] • Telephone module 138;

[0109] • Video conferencing module 139;

[0110] • Email client module 140;

[0111] • Instant Messaging (IM) module 141;

[0112] Fitness support module 142;

[0113] • Camera module 143 for still images and / or video images;

[0114] • Image management module 144;

[0115] • Video player module;

[0116] Music player module;

[0117] • Browser module 147;

[0118] • Calendar module 148;

[0119] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6;

[0120] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0121] • Search module 151;

[0122] • Video and music player module 152, which combines a video player module and a music player module;

[0123] • Notepad module 153;

[0124] • Map module 154; and / or

[0125] • Online video module 155.

[0126] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, Java-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0127] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in the application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and so on.

[0128] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0129] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0130] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0131] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0132] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0133] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for: capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

[0134] Incorporating the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0135] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0136] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0137] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, desktop applet module 149 is optionally a micro-application downloaded and used by a user (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a user-created micro-application (e.g., user-created desktop applet 149-6). In some embodiments, the desktop applet includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop applet includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! desktop applet).

[0138] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

[0139] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

[0140] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions allowing users to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0141] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do items, etc., according to user instructions.

[0142] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0143] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following actions: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0144] Each of the above modules and applications corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores subgroups of the aforementioned modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0145] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push-buttons, dials, etc.) on device 100 can be optionally reduced.

[0146] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main menu, home menu, or root menu. In such embodiments, a touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

[0147] Figure 1B This is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0148] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information should be delivered.

[0149] In some implementations, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or ready to be displayed by the application 136-1, a state queue for enabling the user to return to the previous state or view of the application 136-1, and a repeat / undo queue for the user's previous actions.

[0150] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral device interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

[0151] In some implementations, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other implementations, peripheral device interface 118 transmits event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0152] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

[0153] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that the user can see on the display.

[0154] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events identified as correct input is optionally determined at least in part based on the hit view of the initial touch that initiates a touch-based gesture.

[0155] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0156] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0157] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0158] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another embodiment, event classifier 170 is a standalone module or part of another module (such as contact / motion module 130) stored in memory 102.

[0159] In some implementations, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0160] The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0161] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0162] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting off the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0163] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

[0164] In some implementations, the definition of the corresponding event (187) also includes a delay action that delays the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

[0165] When the corresponding event recognizer 180 determines that the sub-event sequence does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0166] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0167] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

[0168] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined procedure.

[0169] In some implementations, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some implementations, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the location of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on touch-sensitive display.

[0170] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other implementations, they are included in two or more software modules.

[0171] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0172] Figure 2A portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0173] Device 100 optionally also includes one or more physical buttons, such as a "home" or menu button 204. As previously described, menu button 204 is optionally used to navigate to any application 136 of a set of applications optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touchscreen 112.

[0174] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0175] Figure 3This is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one mentioned above)) are described. Figure 1A The contact strength sensor 165 is described above. The memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 (… Figure 1A The memory 102 may optionally not store these modules.

[0176] Figure 3Each of the elements described above is optionally stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to an instruction set for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subgroup of the modules and data structures described above. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0177] Now let’s turn our attention to the implementation of the user interface, which is optionally implemented on, for example, a portable multifunction device 100.

[0178] Figure 4A An exemplary user interface for an application menu on a portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof:

[0179] • Signal strength indicator 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0180] • Time 404;

[0181] Bluetooth indicator 405;

[0182] • Battery status indicator 406;

[0183] • Tray tray 408 with icons for commonly used applications, such as:

[0184] ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages;

[0185] ○ An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails;

[0186] ○ The icon 420 labeled "Browser" in browser module 147; and

[0187] ○ The icon 422 marked "iPod" for the video and music player module 152 (also known as the iPod module 152, a trademark of Apple Inc.); and

[0188] • Icons of other applications, such as:

[0189] ○The icon 424 of the IM module 141 marked as "Message";

[0190] ○The calendar module 148 has an icon 426 labeled "Calendar";

[0191] ○ The icon 428 of the image management module 144 is labeled "Photo".

[0192] ○ The icon 430 of camera module 143, which is labeled "camera";

[0193] ○ The icon 432 of the online video module 155, which is marked as "Online Video";

[0194] ○ The icon 434 in the Stock Market Desktop Mini Program 149-2 that is marked as "Stock Market";

[0195] ○The icon 436 of the map module 154 that is labeled "map";

[0196] ○ The icon 438 in the Weather desktop mini-program 149-1 that is marked as "Weather";

[0197] ○ The icon 440 in the alarm clock desktop mini-program 149-4 that is marked as "clock";

[0198] ○ The icon 442 of the fitness support module 142 is labeled "fitness support";

[0199] ○ The icon 444 labeled "Notepad" in Notepad module 153; and

[0200] ○ The icon 446, labeled "Settings," is used to set the settings of the device 100 and its various applications 136.

[0201] It should be pointed out that, Figure 4A The icon labels shown are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be optionally used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0202] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices (e.g., tablets or touchpads 355) Figure 3An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

[0203] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450)). Figure 4B The spindle corresponding to 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the middle, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figure 4B 451) and the display of a multi-functional device (e.g., Figure 4B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may optionally be used for other user interfaces described herein.

[0204] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0205] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figures 1A to 4B Some or all of the features described herein. In some embodiments, device 500 has a touch-sensitive display 504, referred to below as touchscreen 504. As an alternative to or complement to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface operations on device 500.

[0206] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International Patent Application Serial No. PCT / US2013 / 040061, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0207] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0208] Figure 5B An exemplary personal electronic device 500 is illustrated. In some embodiments, device 500 may include a reference. Figure 1A , Figure 1B and Figure 3 Some or all of the components described herein. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to display 504, which may have touch-sensitive components 522 and optionally have an intensity sensor 524 (e.g., a contact intensity sensor). Furthermore, I / O portion 514 may be connected to communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may optionally be a rotatable input device or a pressable input device and a rotatable input device. In some examples, input mechanism 508 may optionally be a button.

[0209] In some examples, the input mechanism 508 is optionally a microphone. The personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which are operatively connected to the I / O section 514.

[0210] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform, for example, the techniques described below, including processes 700-1100. Figures 7A-7B , Figures 8A-8B , Figures 9A-9B , Figures 10A-10B , Figures 11A-11C ) and 1400 ( Figures 14A-14BA computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0211] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 ( Figure 1A , Figure 3 and Figures 5A to 5B A user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[0212] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of enabling direct interaction with user interface elements on the touchscreen display) Figure 1A The touch-sensitive display system 112 or Figure 4AIn some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0213] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted away, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase and / or before or after contact intensity decreases). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0214] Figure 5C This demonstrates the use of multiple intensity sensors 524A-524D to detect multiple contacts 552A-552E on a touch-sensitive display 504. Figure 5C It also includes an intensity graph, which shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some embodiments, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some implementations, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. Figure 5DThe diagram illustrates the allocation of cumulative intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some specific implementations, each contact j is assigned a corresponding intensity Ij according to a predefined mathematical function Ij = A·(Dj / ΣDi), which is a portion of the cumulative intensity A, where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i = 1 to the last) from the center of force. Reference operations can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5C-5D The operation described above. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine the intensity of a single characteristic (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included within... Figures 5C-5D This is intended to assist readers.

[0215] In some implementations, a portion of the gesture is identified to determine the characteristic intensity. For example, a touch-sensitive surface optionally receives a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position is optionally based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0216] Optionally, the contact intensity on a touch-sensitive surface is characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0217] An increase in contact intensity from below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact intensity from below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact intensity from below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0218] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0219] Figures 5E-5HThe detection of gestures is shown, including gestures involving contact 562 with an intensity ranging from less than... Figure 5E The light press intensity threshold (e.g., "IT") L The intensity of ”) increases to higher than Figure 5H The deep press intensity threshold (e.g., "IT") D The intensity of the press input corresponds to the strength of the press. On the user interface 570, which includes application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed above the application icon 572B corresponding to application 2, the gesture performed by contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines the intensity of the contact 562 within a deep press intensity threshold (e.g., "IT"). D The intensity reaches its peak value above 562. Contact is maintained on the touch-sensitive surface 560. In response to a detected gesture, and based on the intensity increasing to a deep press intensity threshold (e.g., "IT") during the gesture... D The above contact 562 displays the scale representation 578A-578C (e.g., thumbnails) of the document recently opened for application 2, such as... Figures 5F-5H As shown. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in... Figures 5E-5H This is intended to assist readers.

[0220] In some implementations, the display of icons 578A-578C includes animation. For example, icon 578A might initially appear near application icon 572B, such as... Figure 5F As shown, as the animation progresses, icon 578A moves upwards, and icon 578B appears near application icon 572B, as shown. Figure 5G As shown in the diagram. Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H As shown in the diagram. This indicates that 578A-578C form an array above icon 572B. In some implementations, the animation progresses according to the intensity of contact 562, such as... Figures 5F-5G As shown, where 578A-578C appear and increase with the intensity of contact 562 towards the pressure threshold (e.g., "IT"). D The animation progresses upwards as it increases in intensity. In some implementations, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5E to 5H The aforementioned operations.

[0221] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0222] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0223] As used herein, "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched on the device (e.g., become open). In some implementations, the downloaded application becomes an installed application using an installer that extracts program portions from the downloaded software package and integrates the extracted portions with the computer system's operating system.

[0224] As used herein, the terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is optionally any of the following types of applications:

[0225] • The currently active application displayed on the screen of the device that is using the application;

[0226] • Background applications (or background processes) that are not currently displayed but whose one or more processes are being handled by one or more processors; and

[0227] • A suspended or hibernating application that is not running but has state information stored in memory (both volatile and non-volatile) that can be used to resume application execution.

[0228] As used herein, the term "closed application" refers to a software application that does not retain state information (e.g., the state information of a closed application is not stored in the device's memory). Therefore, closing an application includes stopping and / or removing the application's process and removing the application's state information from the device's memory. Generally, opening a second application while the first application is running does not close the first application. When the second application is displayed and the first application stops displaying, the first application becomes a background application.

[0229] Now let’s turn our attention to the implementation of user interfaces (“UIs”) and associated processes on electronic devices (such as portable multifunction devices 100, 300 or 500).

[0230] Figures 6A-6Z Exemplary user interfaces related to viewing health data are illustrated according to some implementation schemes. The user interfaces in these figures are used to illustrate the processes described below, including… Figures 7A-7B , Figures 8A-8B , Figures 9A-9B , Figures 10A-10B and Figures 11A-11C The process in.

[0231] Figure 6A The image depicts a first electronic device 600 (e.g., a telephone) displaying a locked user interface 604 via a touch-sensitive display device 602 at a first time (e.g., 9:45). In some examples, the first electronic device 600 includes one or more features of devices 100, 300, or 500.

[0232] In some examples, locking the user interface 604 involves the user interface displayed when the first electronic device transitions out of an inactive mode. For example... Figure 6A The depicted lock user interface 604 includes multiple notifications (e.g., notification 604a and notification 604b) issued by a process executed on the first electronic device 600 (e.g., causing the first electronic device 600 to display them).

[0233] In some examples, notification 604a is issued by the active procedure corresponding to the active application (as indicated by icon 604aa). In some examples, the user interface elements corresponding to the active application will include icon 604aa (or some variation of icon 604aa, such as a smaller or larger version of icon 604aa). Figure 6A The notice 604a described includes (1) the time when the notice 604a is issued (e.g., time 604ad, which indicates “now”, refers to 9:45) and (2) a description of why the notice 604a is issued (e.g., 604ac).

[0234] In some examples, notification 604b is issued by a CHR process corresponding to a Clinical Health Record (CHR) application (as indicated by icon 604ba). In some examples, user interface elements corresponding to a CHR application will include icon 604ba (or some variant of icon 604ba, such as smaller or larger versions of icon 604ba). Figure 6A As depicted, Notice 604b includes (1) the time when Notice 604b is issued (e.g., time 604bd, which indicates “8:00 AM”) and (2) a description of why Notice 604b is issued (e.g., 604bc).

[0235] Figure 6B The description depicts a second electronic device 606 (e.g., a watch) displaying notification 610 via a touch-sensitive display device 608 at a second time (e.g., 10:24) following a first time. In some examples, the second electronic device 606 includes one or more features of devices 100, 300, 500, or 600.

[0236] In some examples, notification 610 is issued (e.g., displayed by the second electronic device 606) by a listening process corresponding to a listening application (as indicated by icon 610a) executed on the second electronic device 606. In some examples, the user interface elements corresponding to the listening application will include icon 610a (or some variation of icon 610a, such as a smaller or larger version of icon 610a). Figure 6B As depicted, Notice 610 includes a description of why Notice 610 is issued (e.g., 610b).

[0237] Figure 6C The illustration depicts a first electronic device 600 displaying a main user interface 612 via a touch-sensitive display device 602 at a third time following a second time. The main user interface 612 includes multiple icons, each corresponding to a different application. For example, the main user interface 612 includes a health icon 612a to launch a health application and / or display the user interface of that application.

[0238] Figure 6C The illustration depicts a first electronic device 600 receiving user input 613 corresponding to a health icon 612a. In some examples, user input 613 is received via a touch-sensitive display device 602 and corresponds to a selection of the health icon 612a (e.g., a tap gesture on the health icon 612a). In other examples, other forms of input may be used, such as a click via a mouse. In some examples, user input 613 causes a different user interface to be displayed via the touch-sensitive display device 602, such as the display of a user interface for a health application, as... Figure 6DA What is depicted.

[0239] Figure 6DA-Figure 6DD The illustration depicts a first electronic device 600 displaying a summary user interface 614 via a touch-sensitive display device 602 at a fourth time, following a third time. In some examples, the summary user interface 614 is the user interface of a health application. Figure 6DA-Figure 6DD The depicted summary user interface 614 includes multiple areas with different display representations, including notification areas (e.g., notification areas including first notification display representation 616, second notification display representation 618, and third notification display representation 620), login areas (e.g., login areas including login display representation 622), and favorites areas (e.g., favorites display representations 626a, 626b, 626c, 626d, 626e ... The system includes a collection area (626f) and displays all health data (628), a highlight area (e.g., a highlight area including a first highlight area (630), a second highlight area (632), and displays all highlight areas (634), a health record area (e.g., a health record area including a first health record area (636), a second health record area (638), and displays all records (640), an education area, an "Get More from Health" area, and an application area.

[0240] In some examples, the notification area includes a display of health-related notifications posted / displayed by a device associated with an account logged into the health application. For example, health-related notifications may originate from a first electronic device 600 (e.g., notifications 604a and 604b, such as...). Figure 6A The described or linked (e.g., login to a single account or pairing, such as using a smartphone and a corresponding smartwatch) link to either the first electronic device 600 or another electronic device (e.g., the second electronic device 606) of the account (e.g., notification 610, such as...). Figure 6B(As depicted). In such examples, a notification area is a location used to display information associated with a health-related notification, which can be viewed after the initial display of the health-related notification.

[0241] As discussed above, the notification area includes a first notification enablement representation 616, a second notification enablement representation 618, and a third notification enablement representation 620. In some examples, the first notification enablement representation 616 corresponds to notification 610 (e.g., including information from notification 610). In some examples, the second notification enablement representation 618 corresponds to notification 604a (e.g., including information from notification 604a). In some examples, the third notification enablement representation 620 corresponds to notification 604b (e.g., including information from notification 604b). Figure 6DA The notification display in the depicted notification area can be sorted by the date the corresponding notification was first published (e.g., the most recent notification is first, the next most recent notification is next, etc.).

[0242] In some examples, a notification indicator is removed from the notification area after a specific amount of time. In some examples, the specific amount of time varies based on the amount of user interaction associated with the corresponding notification indicator or data related to the indicator. For example, when a first notification indicator (or the notification corresponding to the first notification indicator) is interacted with by the user and a second notification indicator is not interacted with by the user, the first notification indicator is removed faster than the second notification indicator. Similarly, when a first notification indicator (or the notification corresponding to the first notification indicator) is displayed for a longer amount of time than a second notification indicator (or the notification corresponding to the second notification indicator), the first notification indicator is removed faster than the second notification indicator. Furthermore, when a first notification indicator (or the notification corresponding to the first notification indicator) is associated with a type of health data that is more frequently viewed (or interacted with) by the user than the type of health data associated with the second notification indicator (or the notification corresponding to the second notification indicator), the first notification indicator is removed faster than the second notification indicator. For example, when a first notification indication (or a notification corresponding to the first notification indication) has more information (e.g., more detailed information) or more important information (e.g., as defined by a health application) than a second notification indication (or a notification corresponding to the second notification indication), the first notification indication is removed faster than the second notification indication. Similarly, when data corresponding to the first notification indication is viewed on another device (e.g., device 608), the first notification indication is removed faster than the second notification indication (e.g., even if the first notification indication is not interacted with on device 600). Relative to Figures 6F-6H Further discussion is needed on such removal criteria.

[0243] The first notification display 616 includes an icon 616a indicating that a notification corresponding to the first notification display 616 (e.g., notification 610) was published by an application (e.g., a listening application) represented by icon 616a. The first notification display 616 includes a header visually distinct from the rest of the first notification display 616, comprising a title 616b (indicating the content addressed by the first notification display 616) and a time 616c (indicating the time when the notification corresponding to the first notification display 616 was initially published). In one example, the header is visually distinct from the rest of the first notification display 616 by being a specific pattern or color corresponding to the listening application. In some examples, user interface elements associated with the listening application will include elements with a specific pattern or color. Figure 6DA As shown, the first notification enablement representation 616 includes content 616d, which (in some examples) is at least a portion of the content included in the notification corresponding to the first notification enablement representation 616.

[0244] The second notification display 618 includes an icon 618a indicating that a notification corresponding to the second notification display 618 (e.g., notification 604a) was published by the application (e.g., the active application) represented by the icon 618a. The second notification display 618 includes a header that is visually distinct from the rest of the second notification display 618 (and visually distinct from the headers of the first notification display 616 and the third notification display 620), the header including a title 618b (indicating the content addressed by the second notification display 618) and a time 618c (indicating the time when the notification corresponding to the second notification display 618 was initially published). In one embodiment, the header is visually distinguished from other elements by being a specific pattern or color corresponding to the active application. In some examples, user interface elements associated with the active application will include elements with a specific pattern or color. Figure 6DA The depicted second notification enablement representation 618 includes content 618d, which (in some examples) is at least a portion of the content included in the notification corresponding to the second notification enablement representation 618.

[0245] The third notification display 620 includes an icon 620a indicating that a notification corresponding to the third notification display 620 (e.g., notification 604b) was published by an application (e.g., a CHR application) represented by icon 620a. The third notification display 620 includes a header that is visually distinct from the rest of the third notification display 620 (and visually distinct from the headers of the first notification display 616 and the second notification display 618), the header including a title 620b (indicating the content addressed by the third notification display 620) and a time 620c (indicating the time when the notification corresponding to the third notification display 620 was initially published). In one embodiment, the header is visually distinguished from other elements by being a specific pattern or color corresponding to the CHR application. In some examples, user interface elements associated with the CHR application will include elements with a specific pattern or color. Figure 6DA The depicted third notification capability representation 620 includes an icon 620d and content 620e, the content (in some examples) being at least a portion of the content included in a notification corresponding to the third notification capability representation 620. In some examples, icon 620d corresponds to the clinical institution that generated the notification associated with the third notification capability representation 620. In such examples, icon 620d differs from icon 620a.

[0246] In some examples, the selection of a notification enable symbol causes the display of a user interface for a health application associated with that application. For instance, selecting a first notification enable symbol 616 causes the display of a user interface for the health application, which includes information from a listening application (sometimes referred to as a listening data room, such as...). Figure 6E (As described and discussed further below).

[0247] In some examples, the login area includes an indication of login data. For example, login indication 622 relates to a login cycle. Login indication 622 includes an icon 622a representing the login application (e.g., a cycle tracking application) corresponding to login indication 622. Login indication 622 also includes content 622b that describes login indication 622 and indicates the last time the user has logged in with information associated with the login application. Login indication 622 also includes a graphic 622c indicating whether login criteria have been met (e.g., when login criteria are not met, graphic 622c is a plus sign indicating the minimum number of times the user has not logged in; when login criteria are met, graphic 622c is a check mark indicating the minimum number of times the user has logged in). In some examples, when login indication 622 is selected, a user interface is displayed that allows the user to log in to the cycle. In other examples, the action of selecting login indication 622 causes the cycle to be logged in.

[0248] In some examples, the color or pattern associated with a portion of the login functionality representation 622 (e.g., the font color of the words "cycle tracking") is a specific color or pattern corresponding to the login application. In some examples, the specific color or pattern is used on at least a portion of user elements displayed in the health application that correspond to the login application. In some examples, the specific color or pattern is visually different from the colors / patterns used in other applications (e.g., activity applications, listening applications, CHR applications, or other login applications).

[0249] In some examples, the collection area includes an indication of health-related data that the user has designated as one of their collections (e.g., Figure 6I (As depicted and discussed below). In some examples, prior to user indication of a favorite, the favorites area includes one or more predefined power representations corresponding to health-related data that the system has determined the user will favorite (e.g., based on the user's device, user interactions, default favorites, or any combination thereof).

[0250] As described above, the collection area includes a first collection indicator 626a, a second collection indicator 626b, a third collection indicator 626c, a fourth collection indicator 626d, a fifth collection indicator 626e, and a sixth collection indicator 626f, and displays all health data indicator 628. The first collection indicator 626a, the second collection indicator 626b, and the third collection indicator 626c correspond to health data from the active application, as indicated, for example, by icon 626aa.

[0251] In some examples, at least a portion of each favorite display is visually distinct to represent the corresponding application (e.g., in some examples, the font color of the header 626ab corresponds to the active application). In some examples, elements that make each favorite display visually distinct are consistent across different user interface elements (e.g., if color is a visually distinct element, other user interface elements corresponding to the active application will include the same color) (e.g., in some examples, the header in the second notification display 618 is the same color as the font color of "Active" in the first favorite display 626a).

[0252] like Figure 6DA The depicted first collection energy representation 626a includes a timestamp of the last updated health data 626ac (e.g., movement, exercise, and standing measurements).

[0253] like Figure 6DB The depicted fourth collection representation 626d includes icon 626da, which is Figure 6DAA smaller version of icon 622a is depicted. This correspondence shows that, in some examples, different user interface elements associated with the same application include the same icon used to represent that application. Icons 626ea and 626fa are further examples of icons corresponding to different applications. Furthermore, in some examples, the title 626db is colored similarly to "Cycle Tracking" in content 622b to further indicate that both relate to the same application.

[0254] In some implementations, displaying all health data (representation 628) enables the display of a user interface that includes a representation of all health data corresponding to an account associated with the health application. Examples of such a user interface are shown in... Figure 12AA-Figure 12AB Described in the text.

[0255] In some examples, the feed area includes a graphical representation of health data over a period of time, as identified by the health application. For example, a particular graphical representation is displayed if it meets the feed criteria, and not displayed if it does not. In some examples, the feed criteria are based on differences between health data over a time period, the time a user spends viewing a particular graphic, user interaction with a particular graphic or element of interface 614, or any combination thereof.

[0256] Figure 6DB An electronic device is depicted displaying a first feed display 630 in a feed area of ​​a summary user interface 614 via a touch-sensitive display device 602. The first feed display 630 includes an icon 630a indicating that the first feed display 630 primarily relates to a heart rate application (in some examples, the first feed display 630 secondarily relates to a second application (e.g., a fitness application), such that the first feed display 630 is based on data from the second application). In some examples, a portion of the first feed display 630 is visually distinguishable to identify that the first feed display 630 primarily relates to a heart rate application (e.g., in some examples, the font color of the title 630b is a specific color corresponding to the heart rate application). The first feed display 630 also includes a description 630c indicating information displayed by the first feed display 630 (e.g., a range of values ​​achieved during exercise).

[0257] like Figure 6DB The depicted first summary energy display 630 includes a graph 630d showing the heart rate during exercise. Graph 630d includes a minimum indicator 630e indicating the minimum heart rate during exercise, and a maximum indicator 630f indicating the maximum heart rate during exercise. Such indicators are determined by comparing heart rates at different times corresponding to a period of exercise to identify the minimum and maximum values.

[0258] Figure 6DC An electronic device is depicted displaying a second feed power indicator 632 in a feed area of ​​a summary user interface 614 via a touch-sensitive display device 602. The second feed power indicator 632 includes an icon 630a indicating that the second feed power indicator 632 relates to an ambient audio application. In some examples, a portion of the second feed power indicator 632 is visually distinguishable to identify that the second feed power indicator 632 relates to an ambient audio application (e.g., in some examples, the font color of the title 632b is a specific color corresponding to an ambient audio application). The second feed power indicator 632 also includes a description 632c indicating the information displayed by the second feed power indicator 632 (e.g., how today's average ambient audio level is 4 dB higher than yesterday's average).

[0259] like Figure 6DC The depicted second summary, representation 632, includes a chart with today's average representation (e.g., 632d) and yesterday's average representation (e.g., 632e). Figure 6DC The depicted average representations for today and yesterday, each include a graphical representation of the average and a textual representation of the average. In some examples, the graphs represent quantities of a single health data measure compared across time periods of equal length.

[0260] As discussed above, the feed area also includes a display of all feed indicators 634. In some examples, selecting to display all feed indicators 634 causes a user interface corresponding to a health application to be displayed, such as displaying... Figure 6MA-Figure 6MD All the feed user interfaces depicted.

[0261] In some examples, the health record area includes a corresponding indication (e.g., a first health record indication 636 and a second health record indication 638) for each clinical facility that has sent health record data about the account associated with the health application. For example, the first health record indication 636 indicates that it corresponds to XYZ Medical Center in Palo Alto, CA (see 636d). Similarly, the second health record indication 638 indicates that it corresponds to ABC Emergency Center in San Jose, CA (see 638d).

[0262] In some examples, each power indicator in the health record area includes an indication that the power indicator corresponds to a title of the health record (e.g., title 636a and title 638a). Figure 6DCAs depicted, each indicator in the health record area also includes an indication of when the most recent health record from the corresponding clinical institution was received (e.g., the first health record indicator 636 includes an 8:00 AM time indication 636b, and the second health record indicator 638 includes a 6:00 AM time indication 638b). In some examples, the indicators in the health record area are sorted based on when the most recent health record from the corresponding clinical institution was received (e.g., based on the most recent health record corresponding to the first health record indicator 636 received after the most recent health record corresponding to the second health record indicator 638, with the first health record indicator 636 above the second health record indicator 638). In other examples, the indicators in the health record area are sorted based on when a health record update was initially published / generated for the account (e.g., based on the first health record corresponding to the first health record indicator 636 generated before the second health record corresponding to the second health record indicator 638, with the first health record indicator 636 above the second health record indicator 638). In other examples, the display in the health records area is sorted based on a user-defined order, such as specifying primary and secondary institutions (e.g., primary institutions above secondary institutions). In some examples, only primary institutions are displayed in the health records area, where secondary institutions can be navigated to use the display of all health records display 640. In some examples, selecting to display all health records display 640 causes the user interface of the health application to be displayed, which includes all health records received for the account associated with the health application (e.g., ...). Figures 6OA-6OB (As depicted).

[0263] In some examples, each indicator in the health record area includes an indication of which records have been received from the corresponding institution. For example, the first health record indicator 636 includes indication 636e, which indicates that health records corresponding to medications, laboratory results, and other records have been received from XYZ Medical Center. In some examples, indication 636e is ordered based on when the health records were received (e.g., medications before laboratory results, because receiving a health record with health data corresponding to medications is more recent than receiving a health record with health data corresponding to laboratory results). As another example, the second health record indicator 638 includes indication 638e, which indicates that a health record corresponding to medications has been received from ABC Emergency Services.

[0264] In some examples, the education zone includes a power indicator that, when selected, causes the user interface to display educational content. In some examples, the "Get More from Health" zone includes a power indicator that, when selected, causes the user interface to display for configuring the health application. In some examples, the application zone includes power indicators corresponding to different applications identified as being associated with an account linked to the health application.

[0265] like Figure 6DD The depicted summary user interface 614 includes a pair of indicator symbols (e.g., summary indicator symbol 642a and search indicator symbol 642b) at the bottom of the summary user interface 614 to indicate which part of the health application the current user interface relates to (e.g., visually distinct indicator symbols (e.g., bold) indicate which part). In some examples, selection is made for a part of the health application that is not currently involved in the user interface (e.g., Figure 6DD The search capability indicator 642b) causes the user interface corresponding to the selected portion to be displayed (e.g., if search capability indicator 642b is selected, the user interface corresponding to the search portion is displayed, such as...). Figure 6TA - Figure 6TB (As depicted). In some examples, selecting the power indication corresponding to the part involving the current user interface causes the main interface of the selected part to be displayed (e.g., as shown). Figure 6DA The outline user interface 614 described is used for the outline section, and as shown in the figure. Figure 6TA-Figure 6TB The search user interface described is 684.

[0266] Figure 6DA The illustration depicts a first electronic device 600 receiving user input 615 corresponding to a first notification enablement display 616. In some examples, user input 615 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the first notification enablement display 616. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, user input 615 causes different user interfaces to be displayed via the touch-sensitive display device 602, such as the display of an ambient audio data room user interface 644 in a health application. Figure 6E What is depicted.

[0267] Figure 6E The illustration depicts a first electronic device 600 displaying an ambient audio data room user interface 644 via a touch-sensitive display device 602 at a fifth time, following a fourth time. In some examples, the ambient audio data room user interface 644 is a user interface for a health application that displays information from the ambient audio application. Figure 6EThe depicted ambient audio data room user interface 644 includes graphs displaying data indicating the noise levels detected by the device throughout the week. In some examples, the data is stored in a location associated with the ambient audio application and can be viewed within the user interface of the ambient audio application.

[0268] The ambient audio data room user interface 644 also includes time scale indicators at the top (e.g., "D" for day, "W" for week, "M" for month, and "Y" for year). Figure 6E The depicted time-scale energy representation indicating the week is selected such that the graph indicates the noise level detected over the entire week. In some examples, selecting a different time-scale energy representation causes the graph to change to indicate the noise level detected over the entire selected time scale.

[0269] like Figure 6E The depicted ambient audio data room user interface 644 includes multiple indicator representations at the bottom that indicate information depicted by the charts in text. For example, there is a first indicator representing the average for the entire week, a second indicator representing the daily average for the entire week, and a third indicator representing the range for the entire week and the number of noise notifications issued by the ambient audio application throughout the week. In some examples, selecting one of the indicator representations causes the chart to be modified to highlight the data in the chart corresponding to the selected indicator representation. For example, selecting the average indicator representation causes a line indicating the average value to be inserted into the chart. Similarly, selecting the daily average indicator representation causes a point to be inserted in each bar for each day in the chart to indicate the average value for that day. Furthermore, selecting the range indicator representation causes a portion of the chart to be highlighted, where the minimum and maximum values ​​of the range occur throughout the week. And, selecting the noise notification indicator representation causes a portion of the chart to be highlighted, which causes noise notifications to be issued.

[0270] Figure 6F The description depicts a first electronic device 600 displaying a summary user interface 614 via a touch-sensitive display device 602 at a sixth time, following a fifth time. In some examples, in response to ambient audio data, the user interface 644 (which in...) is displayed... Figure 6E The user input corresponding to the selection of the back button in the upper left corner (described as having no user input) is displayed in summary user interface 614.

[0271] like Figure 6F The described summary user interface 614 is relative to, for example Figure 6DA The depicted summary user interface 614 scrolls down (for example, the text "Summary" in the upper left and the account icon in the upper right are no longer displayed). Figure 6F The first notification enablement representation 616 is described as interacting (e.g., as...). Figure 6DA After the depicted (selected) option is selected, the first notification display 616 is still displayed in the summary user interface 614. Figure 6F The second notification display 618 and the third notification display 620 are also depicted and are still displayed in the summary user interface 614.

[0272] Figure 6G The illustration depicts a first electronic device 600 displaying a summary user interface 614 via a touch-sensitive display device 602 at a seventh time, following a sixth time. In some examples, the summary user interface 614 is displayed in response to user input corresponding to a re-display of the summary user interface 614.

[0273] Figure 6G The description shows that even if the second notification enablement representation 618 and the third notification enablement representation 620 are received before the first notification enablement representation 616, the first notification enablement representation 616 will no longer be displayed in the summary user interface 614. This illustrates that in some examples, the interactive notification enablement representation is removed in a shorter time compared to the non-interactive notification enablement representation. Figure 6G The second notification enablement display 618 and the third notification enablement display 620 are still displayed in the summary user interface 614.

[0274] Figure 6H The illustration depicts a first electronic device 600 displaying a summary user interface 614 via a touch-sensitive display device 602 at an eighth time, following a seventh time. In some examples, the summary user interface 614 is redisplayed relative to the touch-sensitive display device 602 at the seventh time (e.g., ...). Figure 6G (As depicted).

[0275] Figure 6H The third notification enablement 620 is depicted no longer displayed in the summary user interface 614, at least in part because (1) the notification corresponding to the third notification enablement 620 was published before the notification corresponding to the second notification enablement 618, and (2) the notification corresponding to the third notification enablement 620, the third notification enablement 620, the notification corresponding to the second notification enablement 618, and the second notification enablement 618 have not been interacted with by the user. This illustrates the removal of notification enablements that have not yet been interacted with based on chronological order upon publication (e.g., removing older notification enablements first). Figure 6H The second notification display 618 is still displayed in the summary user interface 614.

[0276] Figure 6HThe illustration depicts a first electronic device 600 receiving user input 625 corresponding to an editable display 624. In some examples, the user input 625 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the editable display 624. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, the user input 625 causes a different user interface to be displayed via the touch-sensitive display device 602, such as displaying an editable user interface 646, as... Figure 6I What is depicted.

[0277] Figure 6I The image depicts a first electronic device 600 displaying an editing user interface 646 via a touch-sensitive display device 602 at a ninth time, following an eighth time. In some embodiments, the editing user interface 646 is a user interface that allows a user to add and / or remove health applications from their collections to be displayed in the collection area of ​​the summary user interface 614.

[0278] like Figure 6I The depicted editing user interface 646 includes an existing data display representation 646a and all display representations 646b for switching between views of the editing user interface 646. For example, user input corresponding to a selection of the existing data display representation 646a causes the editing user interface 646 to display the existing data view, such as... Figure 6I As depicted and discussed below. Similarly, user input corresponding to the selection of all power indicators 646b causes the editing user interface 646 to display all data views (not shown), which include all possible health data types for adding and / or removing from the favorites area.

[0279] In the view corresponding to the existing data display representation 646a (e.g.) Figure 6I As depicted, the edit user interface 646 includes a representation of a health data type for which the account has at least some health data (e.g., a representation of the health data type is displayed when the health application has access to the health data of the account's health data type (e.g., at least some health data of the health data type already exists for the account)). In such an example, in the view corresponding to the existing data capability representation 646a, the edit user interface 646 does not include any representation of a health data type for which the account does not have health data (e.g., a representation of the health data type is not displayed when the health application cannot access the health data of the account's health data type (e.g., health data of the health data type does not exist for the account)).

[0280] In any view, selecting a representation of the health data type causes the collection display of the health data type to be added to the collection area of ​​the summary user interface 614, thereby allowing the user to view the stored data of the health data type from the summary user interface 614. For example... Figure 6I The depicted representation of health data types is indicated by a visually distinct indication compared to other indications within the representation. For example, representation 646c includes an indication that a favorite health data type representation corresponding to representation 646c will be displayed in the favorites area of ​​the summary user interface 614. Similarly, representation 646d includes an indication that a favorite health data type representation corresponding to representation 646c will not be displayed in the favorites area of ​​the summary user interface 614. Figure 6I The depicted representation group shows health data types displayed via an editable user interface 646. For example, the editable user interface 646 includes a set of representations corresponding to activity, body measurements, and heart function, where each representation within the set is related.

[0281] Figure 6J The description depicts a first electronic device 600 displaying a summary user interface 614 via a touch-sensitive display device 602 at a tenth time, following a ninth time. In some examples, this is in response to an editable user interface 646 (which in... Figure 6I The user selects the corresponding user input (as depicted in the image where there is no user input) and displays a summary user interface 614. For example... Figure 6J The described summary user interface 614 is relative to, for example Figure 6H The outline user interface 614 is depicted. Scrolling down (for example, the login display 622 is no longer displayed) Figure 6J middle).

[0282] Figure 6J The illustration depicts a first electronic device 600 receiving user input 627 corresponding to a second collection indicator 626b. In some examples, the user input 627 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the second collection indicator 626b. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, the user input 627 causes a different user interface to be displayed via the touch-sensitive display device 602, such as displaying a step count data user interface 648, as... Figure 6KA - Figure 6KB What is depicted.

[0283] Figure 6KA - Figure 6KBThe image depicts a first electronic device 600 displaying a step count data chamber user interface 648 via a touch-sensitive display device 602 at an eleventh time after a tenth time. In some examples, the step count data chamber user interface 648 is displayed in response to user input corresponding to a selection of a second collection indicator 626b in the summary user interface 614, such as... Figure 6J What is depicted.

[0284] In some examples, the step count data user interface 648 is a user interface for a health application that displays information from the activity application. For example... Figure 6KA The depicted step data user interface 648 includes a chart 648a showing a representation of health data associated with steps taken throughout the day. In some embodiments, the health data is stored in a location associated with the active application and can be viewed within the active application's user interface.

[0285] The step count data user interface 648 also includes a time scale display at the top indicating different time scales (e.g., "D" for days, "W" for weeks, "M" for months, and "Y" for years). Figure 6KA The depicted time-scale energy representation indicating the day is selected such that the graph indicates the number of steps detected throughout the day. In some examples, selecting a different time-scale energy representation causes the graph to change to indicate the number of steps detected throughout the entire selected time scale.

[0286] The step count data user interface 648 includes a feed section that includes a feed associated with the step count. For example... Figure 6KA The depicted step count data room user interface 648 includes a single feed (e.g., 648b) that describes how the number of steps increases over a period of time. It should be appreciated that other feeds may be included in the feed section. In some examples, identifying which feeds to display in the step count data room user interface 648 includes a determination similar to that discussed above for feed areas. The step count data room user interface 648 also includes content indicating the number of steps and a description 648c of adding an indication 468 so that the steps are added to a collection area in the summary user interface 614.

[0287] See Figure 6KB The step count data user interface 648 includes (1) a step count application section 648e having links to suggested applications related to step count (e.g., links to an app store or to an application installed on the first electronic device 600), (2) an options section 648f having various options related to step count; and (3) an education section 648g having an ability indicator that, when selected, causes the user interface to display content related to step count.

[0288] Figure 6L The first electronic device 600 is depicted displaying a summary user interface 614 via a touch-sensitive display device 602 at a twelfth time following an eleventh time. In some examples, in response to a step count data display user interface 648 (which in... Figure 6KA The user input corresponding to the selection shown in the upper left corner (as depicted in the image without user input) returns to the summary display, showing the summary user interface 614. (For example...) Figure 6L The described summary user interface 614 is relative to, for example Figure 6J The described summary user interface 614 scrolls down (e.g., the favorites area is no longer displayed and the feed area is...). Figure 6L (as shown in the image).

[0289] Figure 6L The illustration depicts a first electronic device 600 receiving user input 635 corresponding to a display of all feeds functionality 634. In some examples, user input 635 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the display of all feeds functionality 634. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, user input 635 causes a different user interface to be displayed via the touch-sensitive display device 602, such as displaying an all feeds user interface 650, as... Figure 6MA-Figure 6MD What is depicted.

[0290] Figure 6MA-Figure 6MD The illustration depicts a first electronic device 600 displaying a full feed user interface 650 via a touch-sensitive display device 602 at a thirteenth time following a twelfth time. In some examples, the full feed user interface 650 is displayed in response to user input corresponding to a selection of the display full feed indication 634 in the summary user interface 614, such as... Figure 6L What is depicted.

[0291] In some examples, the All Feed User Interface 650 is the user interface of the health application, which has a list of feeds currently identified by the account's health application (e.g., the identification is based on the determination discussed above regarding feed areas, such that not all generated feeds are included in the All Feed User Interface 650 (e.g., only feeds that meet the display criteria are displayed in the All Feed User Interface 650). Figure 6MA The first electronic device 600 is depicted displaying a first feed power indicator 630 and a second feed power indicator 632, which are also displayed in the feed area of ​​the summary user interface 614 and discussed above.

[0292] Figure 6MBA first electronic device 600 is depicted displaying a third feed display 652 via a touch-sensitive display device 602. The third feed display 652 includes an icon 652a indicating that the third feed display 652 relates to a sleep application. In some examples, a portion of the third feed display 652 is visually distinguishable to identify that the third feed display 652 relates to a sleep application (e.g., in some examples, the font color of the title 652b is a specific color corresponding to the sleep application). A second feed display 632 also includes a description 652c indicating the information displayed by the third feed display 652 (e.g., how the user sleeps an average of 7 hours and 55 minutes this week).

[0293] like Figure 6MB The depicted third summary diagram 652 includes a chart showing how much sleep a user gets each day. The chart also includes a mean line 652e to visually indicate the average over a week. In some examples, the chart represents the average over a time period (e.g., a week) divided into sub-time periods (e.g., days).

[0294] Figure 6MB A first electronic device 600 is depicted displaying a fourth feed display 654 via a touch-sensitive display device 602. The fourth feed display 654 includes an icon 654a indicating that the fourth feed display 654 primarily relates to the Water application (in some examples, the fourth feed display 654 secondarily relates to the Calendar application). In some examples, a portion of the fourth feed display 654 is visually distinguishable to identify that the fourth feed display 654 relates to the Water application (e.g., in some examples, the font color of the header 654b is a specific color corresponding to the Water application). The fourth feed display 654 also includes a description 652c indicating the information displayed by the fourth feed display 654 (e.g., how the user logged into Water 21 days in the past 4 weeks).

[0295] like Figure 6MB The fourth summary display 654, as depicted, includes a calendar 654d with a daily representation, indicating whether the user is logged in for the corresponding day. Figure 6MB The depiction of 654f visually distinguishes it from other representations (e.g., 654e, indicating that a user logged into Water on the day corresponding to 654f and did not log into Water on the day corresponding to 654e). In some examples, calendar 654d represents the frequency of a single health data metric compared across time periods of equal length.

[0296] Figure 6MCA first electronic device 600 is depicted displaying a fifth feed display 656 via a touch-sensitive display device 602. The fifth feed display 656 includes an icon 656a indicating that the fifth feed display 656 primarily relates to a navigation application (in some examples, the fifth feed display 656 secondarily relates to a fitness application). In some examples, a portion of the fifth feed display 656 is visually distinguishable to identify that the fifth feed display 656 primarily relates to a navigation application (e.g., in some examples, the font color of the title 656b is a specific color corresponding to a navigation application). The fifth feed display 656 also includes a description 656c indicating the information displayed by the fifth feed display 656 (e.g., such as a user logging into a 3.1-mile run at an average pace of 8:51).

[0297] like Figure 6MC The depicted fifth summary energy representation 656 includes a map 656d, in which an indication of the running route is provided. The fifth summary energy representation 656 also includes textual information about the run, including a distance measurement 656e (which is greater than the distance included in description 656c), a duration 656f, and calories 656g.

[0298] Figure 6MC A first electronic device 600 is depicted displaying a sixth feed display 658 via a touch-sensitive display device 602. The sixth feed display 658 includes an icon 658a indicating that the sixth feed display 658 relates to a fitness application. In some examples, a portion of the sixth feed display 658 is visually distinguishable to identify that the sixth feed display 658 relates to a fitness application (e.g., in some examples, the font color of the title 658b is a specific color corresponding to a fitness application). The sixth feed display 658 also includes a description 658c indicating the information displayed by the sixth feed display 658 (e.g., such as the user burned a total of 6500 calories today).

[0299] like Figure 6MC The depicted sixth feed representation 658 includes four distinct representations of different workouts recorded throughout the day. Each workout includes an icon corresponding to the workout type, identification information for the workout type (e.g., name), the duration of the workout, and the number of calories burned during the workout. In some examples, the sixth feed representation 658 represents multiple workouts throughout the day within a single feed containing health data for the day.

[0300] Figure 6MDA first electronic device 600 is depicted displaying a seventh feed display 660 via a touch-sensitive display device 602. The seventh feed display 660 includes an icon 660a indicating that the seventh feed display 660 primarily relates to a vital signs application. In some examples, a portion of the seventh feed display 660 is visually distinguishable to identify that the seventh feed display 660 relates to a vital signs application (e.g., in some examples, the font color of the title 660b is a specific color corresponding to a vital signs application). It should be noted that the seventh feed display 660 does not include a description indicating the information displayed by the seventh feed display 660, indicating that not all feeds have such a description. Figure 6MD The seventh summary representation 660 includes a graph 660c depicting the user's heart rate per minute over time, showing how the heart rate per minute decreases from a high point to a low point.

[0301] Figure 6MD The first electronic device 600 is depicted displaying an eighth feed display 662 via a touch-sensitive display device 602. The eighth feed display 662 includes an icon 662a indicating that the eighth feed display 662 relates to an active application. In some examples, a portion of the eighth feed display 662 is visually distinguishable to identify that the eighth feed display 662 relates to an active application (e.g., in some examples, the font color of the title 662b is a specific color corresponding to the active application). The eighth feed display 662 also includes a description 662c indicating the information displayed by the eighth feed display 662 (e.g., such as the user has taken more steps than typically taken at this time of day).

[0302] like Figure 6MD The depicted eighth summary energy representation 662 includes a chart 662d that compares a day's (e.g., today's) activity metric to a previous average. For example, chart 662d includes a today line 662h and a previous average line (including a first portion 662g and a second portion 662i). The today line 662h depicts the number of steps a user has taken as time has progressed up to the current time within a day. The previous average line depicts the number of steps a user has taken as the average time has progressed over several days prior to the current date. The first portion 662g represents the time up to the current time, and the second portion 662i represents the time since the current time. Chart 662d also includes textual indications about the number of steps taken today and the number of steps taken over several days prior to the current date. In some embodiments, the sixth summary energy representation 658 represents an average value with instantaneous information updates over a period of time compared to today.

[0303] Figure 6NThe image depicts a first electronic device 600 displaying a summary user interface 614 via a touch-sensitive display device 602 at a fourteenth time following a thirteenth time. In some examples, this is in response to the display of all feed user interfaces 650 (which in...) Figure 6MD If the user input is not specified in the diagram (as depicted in the diagram), a summary display of the user interface 614 is shown corresponding to the selection in the summary display of 642a. Figure 6N The described summary user interface 614 is relative to, for example Figure 6L The described summary user interface 614 scrolls down (e.g., the feed area is no longer displayed and the health record area is...). Figure 6N (as shown in the image).

[0304] Figure 6N The illustration depicts a first electronic device 600 receiving user input 641 corresponding to a display of all health records on a health record display 640. In some examples, user input 641 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the display of all health records on the health record display 640. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, user input 641 causes different user interfaces to be displayed via the touch-sensitive display device 602, such as a user interface 664 displaying all health data, as shown below. Figures 6OA-6OB What is depicted.

[0305] Figures 6OA-6OB The image depicts a first electronic device 600 displaying a user interface 664 of all health data via a touch-sensitive display device 602 at a fifteenth time following a fourteenth time. In some examples, the user interface 664 of all health data is displayed in response to user input corresponding to a selection of the display all health records enablement display 640 in the summary user interface 614, such as... Figure 6N What is depicted.

[0306] In some examples, the All Health Data User Interface 664 is the user interface of a health application, which has a list of health data received for the account. For example... Figure 6OA The depicted health data user interface 664 includes a total data display 664a and a health record display 664b for switching between views of the total health data user interface 664. For example, user input corresponding to a selection of the total data display 664a causes the total health data user interface 664 to display all data views, such as... Figure 12AA As depicted. Similarly, user input corresponding to the selection of the health record display 664b causes the user interface 664 to display a health record view (such as...). Figures 6OA-6OB(As depicted), which includes all health records received for the account. In some examples, in response to the selection to display all health records enablement 640, a health records view is displayed instead of an all data view. In such examples, in response to an all health data enablement (e.g., all health data enablement 628, such as...) Figure 6DB The option (as depicted) displays a view of all data instead of a health record view.

[0307] In the health record view, in some examples, all health data user interfaces 664 include representations of health record types (e.g., representation 666 for allergies, 666b for clinical vital signs, 666c for illnesses, 666d for immunity, 666e for lab results, 666f for medications, and 666g for surgery). In such examples, the representations of health record types are ordered alphabetically (e.g., allergies, then clinical vital signs, then illnesses, then immunity, then lab results, then medications, then surgery).

[0308] In some examples, each representation in the health record view includes an icon corresponding to the health record type (e.g., icon 666aa corresponds to allergies, icon 666ba to clinical vital signs, icon 666ca to a condition, icon 666da to immunity, icon 666ea to laboratory results, icon 666fa to medications, and icon 666ga to surgery). In some examples, the user interface of a health application that includes user interface elements corresponding to health record types will include versions of the corresponding icons.

[0309] In some examples, each representation in the health record view includes a list of information corresponding to the respective health record type. For example, representation 666a corresponding to allergies includes a list of items that the health record has indicated the user associated with the account has an allergic reaction to (e.g., pollen, mold, avocado, and shellfish). In some examples, the list of information is sorted based on recentity (e.g., items most recently identified for a health record type are sorted before (e.g., above) items not recently identified for that health record type). In some examples, all health data user interfaces 664 in the health record view will include a representation of the health record type even if no health record of that type exists.

[0310] like Figure 6OB The depicted health data user interface 664 includes an external power indicator 666h. Selection of the external power indicator 666h causes the user interface of the health application to be displayed, which includes information from one or more external sources (e.g., sources outside the first electronic device 600). Figure 6OB The depicted health data user interface 664 includes an unreadable data capability representation 666i. The selection of the unreadable data capability representation 666i causes the user interface of the health application to be displayed, which includes a representation of health records that cannot be parsed by processes associated with the health application.

[0311] Figure 6OA The diagram depicts a first electronic device 600 receiving user input 667 corresponding to representation 666e. In some examples, user input 667 is received via touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on representation 666e. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, user input 667 causes a different user interface to be displayed via touch-sensitive display device 602, such as a user interface 668 displaying laboratory results data, as... Figure 6PA-Figure 6PB What is depicted.

[0312] Figure 6PA-Figure 6PB The illustration depicts a first electronic device 600 displaying a laboratory results data room user interface 668 via a touch-sensitive display device 602 at a sixteenth time following a fifteenth time. In some examples, the laboratory results data room user interface 668 is displayed in response to user input corresponding to a selection of representation 666e in the all health data user interface 664, such as... Figure 6OA As depicted. In other examples, in response to user input corresponding to a notification in summary user interface 614 indicating that laboratory results (e.g., and no other health record type) have been updated, laboratory results data room user interface 668 is displayed. In other examples, in response to using, as Figure 6TB The depicted search user interface 684 searches for laboratory results and displays the power indication of the laboratory results data room user interface 668 corresponding to the search results.

[0313] like Figure 6PA The depicted laboratory results data room user interface 668 includes an icon 668a and a title 668b corresponding to and indicating the health record type "laboratory results". In some examples, the user interface element corresponding to the health record type "laboratory results" includes an icon similar to icon 668a.

[0314] like Figure 6PAThe depicted laboratory results data room user interface 668 includes a last-updated energy display 668c and an A-to-Z energy display 668d for switching between views of the laboratory results data room user interface 668. For example, user input corresponding to a selection of the last-updated energy display 668c causes the laboratory results data room user interface 668 to display a first view, such as... Figure 6PA-Figure 6PB As depicted. Similarly, user input corresponding to the selection of the A to Z energy representation 668d causes the laboratory results data interface 668 to display a second view, such as... Figure 6Q What is depicted.

[0315] like Figure 6PA-Figure 6PB The depicted laboratory results data room user interface 668 includes multiple areas (e.g., areas 670 and 672), each area corresponding to a different date on which the health record within that area was generated (e.g., collected, obtained, or otherwise created by a clinical institution). In some examples, the multiple areas are sorted by date such that areas corresponding to more recent dates precede those corresponding to later dates. For example, the laboratory results data room user interface 668 includes a list of areas 672 (which is indicated to correspond to August 15, 2019) (e.g., ...). Figure 6PB The depicted higher (e.g., preceding) region 670 (which is indicated to correspond to March 29, 2019) (as shown) Figure 6PA (As depicted).

[0316] In some examples, each area included in the laboratory results data room user interface 668 includes one or more representations of health records. For example, area 670 includes two representations of two separate health records: representation 670b and representation 670c. As another example, area 672 includes three representations: representation 672b, representation 672c, and representation 672d.

[0317] In some examples, representations within a region are included in sub-regions corresponding to the clinical institution associated with the health record. For example, representations 670b and 670c are included in a sub-region corresponding to XYZ Medical Center, indicating that the health records corresponding to representations 670b and 670c were received from (e.g., generated by) XYZ Medical Center. Similarly, representations 672b, 672c, and 672d are included in a sub-region corresponding to ABC Emergency Center, indicating that the health records corresponding to representations 672b, 672c, and 672d were received from (e.g., generated by) ABC Emergency Center. This illustrates that the laboratory results data room user interface 668 may include representations from multiple clinical institutions.

[0318] In some examples, the representation of health records in the laboratory results data room user interface 668 includes icons indicating the corresponding health record type (as discussed above). In some examples, the representation of health records in the laboratory results data room user interface 668 includes information corresponding to the respective health record. For example, the information in 670b includes the word "collected," indicating that the corresponding health record was collected on the associated date (e.g., March 29, 2019).

[0319] The information in representation 670b also includes a chart showing the corresponding health record. The chart in representation 670b includes multiple indications of the value included in the corresponding health record (e.g., “125 mg / DL”) and the range defined for that value (e.g., 0 to 200, which are the minimum and maximum values). These multiple indications include textual indications (e.g., text) and graphical representations (e.g., dots in a visual representation of the range). In some examples, when the value is within this range, the value is considered to meet a specific criterion (e.g., criteria related to whether the value is acceptable, such as criteria set by the governing body). In some examples, the range is included in the corresponding health record. In other examples, the range is known to the health application, such as being provided by a remote source (e.g., a clinical facility).

[0320] Figure 6PA A representation 670c is depicted, which includes a graph showing the corresponding health record. The graph in representation 670c includes multiple indications of the value included in the corresponding health record (e.g., "6.3%") and a range defined for that value (e.g., 5.7 to 6.3, which are the minimum and maximum values). These multiple indications include textual indications (e.g., text) and graphical representations (e.g., dots in a visual representation of the range). In some examples, when the value is within this range, the value is considered to meet a specific criterion (e.g., criteria related to whether the value is acceptable, such as criteria set by the governing body). In some examples, the range is included in the corresponding health record. In other examples, the range is known to the health application, such as being provided by a remote source (e.g., a clinical institution).

[0321] Figure 6PB Representation 672b depicts information including information from a corresponding health record. The information in representation 672b includes a single indication (e.g., a textual indication) of a value (e.g., “40%”) included in the corresponding health record, and does not include an indication of a range defined for that value. In some examples, the information in representation 672b does not include a chart (and / or an indication of a range) because the health application cannot recognize the range of the value (e.g., the corresponding health record does not include the range and / or the institution has not yet provided the range).

[0322] Figure 6PBA representation 672c depicts information including information from the corresponding health record. The information in representation 672c includes a single indication (e.g., a text indication) of a value included in the corresponding health record (e.g., "negative"). In some embodiments, the information in representation 672b does not include a graph (and / or an indication of a range) because the value is less than the minimum number of possible values ​​for the corresponding health record (in some examples, the minimum number of possible values ​​is three; e.g., binary values ​​will not be plotted).

[0323] Figure 6PB Representation 672d is depicted, which includes a graph showing the corresponding health record. The graph in representation 672d includes a value included in the corresponding health record (e.g., "4.5 trillion") and multiple indications of a range defined for that value (e.g., 5.32 trillion to 5.72 trillion, which are the minimum and maximum values). These multiple indications include textual indications (e.g., text) and graphical representations (e.g., dots in a visual representation of the range). In some examples, when the value is within this range, the value is considered to meet a specific criterion (e.g., criteria related to whether the value is acceptable, such as criteria set by a governing body). In some examples, the range is included in the corresponding health record. In other examples, the range is known to the health application, such as being provided by a remote source (e.g., a clinical institution). Figure 6PB Some representations are shown that may include charts, while others do not, even representations corresponding to the same health record type. In some examples, this is because some health records do not include ranges and / or are binary values.

[0324] Figure 6PA The illustration depicts a first electronic device 600 receiving user input 669 corresponding to an A-Z display 668d. In some examples, the user input 669 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the A-Z display 668d. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, the user input 669 causes different views of the laboratory results data room user interface 668 to be displayed via the touch-sensitive display device 602, such as... Figure 6Q The A to Z views depicted in the figure.

[0325] Figure 6Q The illustration depicts a first electronic device 600 displaying an A-Z view of a laboratory results data room user interface 668 via a touch-sensitive display device 602 at a seventeenth time following a sixteenth time. In some examples, the A-Z view is displayed in response to user input corresponding to a selection of the A-Z display representation 668d in the laboratory results data room user interface 668, such as... Figure 6PA What is depicted.

[0326] like Figure 6Q The depicted A-to-Z views include the last updated energy display 668c and A-to-Z energy display 668d for switching between views on the laboratory results data room user interface 668. For example, user input corresponding to the selection of the last updated energy display 668c causes the laboratory results data room user interface 668 to display a first view, such as... Figure 6PA-Figure 6PB As depicted. Similarly, user input corresponding to the selection of the A to Z energy representation 668d causes the laboratory results data interface 668 to display a second view, such as... Figure 6Q What is depicted.

[0327] like Figure 6Q The depicted A-Z view includes a list of energy representations for different laboratory results, each energy representation corresponding to a different type of laboratory result. In some examples, the list of energy representations is ordered alphabetically by the corresponding type of laboratory result for each energy representation (e.g., cholesterol energy representations (e.g., energy representation 674a) precede creatine energy representations (e.g., energy representation 674b)). In some examples, each energy representation in the list includes an indication of multiple health records associated with the corresponding type of laboratory result. For example, "12" in energy representation 674a indicates that the health system has received 12 health records corresponding to cholesterol.

[0328] Figure 6Q The illustration depicts a first electronic device 600 receiving user input 675 corresponding to an indicator 674c. In some examples, user input 675 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the indicator 674c. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, user input 675 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a hemoglobin user interface 676, etc. Figure 6RA-Figure 6RB What is depicted.

[0329] Figure 6RA-Figure 6RB The image depicts a first electronic device 600 displaying a hemoglobin user interface 676 via a touch-sensitive display device 602 at an eighteenth time following a seventeenth time. In some examples, the hemoglobin user interface 676 is displayed in response to user input corresponding to a selection of an indicator 674c in a laboratory results data room user interface 668, such as... Figure 6Q As depicted. In some examples, in response to user input corresponding to a selection of the indicator 670c in the laboratory results data user interface 668, the hemoglobin user interface 676 is displayed, such as... Figure 6PAAs depicted. In some examples, the hemoglobin user interface 676 is the user interface of a health application that has information based on health records corresponding to hemoglobin A1C.

[0330] like Figure 6RA The depicted hemoglobin user interface 676 includes a graph with data indicating values ​​obtained from health records corresponding to hemoglobin A1C throughout the year. For example, a first health record might indicate a first hemoglobin A1C test result of 6.3% (e.g., the first health record corresponds to indicator 680a), a second health record might indicate a second hemoglobin A1C test result of 7.3% (e.g., the second health record corresponds to indicator 680b), and a third health record might indicate a third hemoglobin A1C test result of 6% (e.g., the third health record corresponds to indicator 680c). Using such health records, the graph includes indications for the first health record (e.g., 676cc), the second health record (e.g., 676ca), and the third health record (e.g., 676cb). In some examples, the graph also includes a representation of 676cd, which provides additional information about one of the health records in the graph. Figure 6RA The depiction indicates that 676cd relates to a first health record. In some examples, in response to user input on indication 676cc and / or selection of an indication on a different user interface, the hemoglobin user interface 676 is displayed, indicating that 676cd relates to a first health record, the indication corresponding to the health record associated with indication 676cc (e.g., as shown in the image). Figure 6PA The depicted power indicator is 670c.

[0331] like Figure 6RA The depicted hemoglobin user interface 676 includes a time scale indicator at the top indicating different time scales (e.g., "W" indicates week, "M" indicates month, "Y" indicates year, and "5Y" indicates 5 years). Figure 6RA The depicted time-scale energy representation indicating the year is selected such that the graph indicates health records throughout the year. In some examples, selecting a different time-scale energy representation causes the graph to change to indicate health records detected throughout the selected time scale.

[0332] like Figure 6RA The depicted hemoglobin user interface 676 includes an out-of-range power indication 678. Selecting the out-of-range power indication 678 causes indicators in the graph to be visually distinguished (e.g., highlighted) corresponding to values ​​outside the defined range, as discussed above.

[0333] Figure 6RAThe illustration depicts a first electronic device 600 receiving user input 681 corresponding to a power indicator 680a. In some examples, user input 681 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the power indicator 680a. In other examples, other forms of selection may be used, such as clicking with a mouse. In some examples, user input 681 causes different user interfaces to be displayed via the touch-sensitive display device 602, such as... Figure 6SA The user interface for recording laboratory results is depicted in Figure 682.

[0334] Figure 6SA The image depicts a first electronic device 600 displaying a laboratory results recording user interface 682 via a touch-sensitive display device 602 at a nineteenth time following an eighteenth time. In some examples, the laboratory results recording user interface 682 is displayed in response to user input corresponding to a selection of an indication display 680a in the hemoglobin user interface 676, such as... Figure 6RA As depicted. In some examples, the laboratory results recording user interface 682 includes detailed information about a specific health record. In some examples, the detailed information includes the date the specific health record was collected, the date the specific health record was received by the health application, an alternative name for the specific health record (e.g., identified from any other health record from a remote source or associated with an account in the health application), the clinical institution associated with the specific health record, and other information included in the specific health record.

[0335] Figure 6SA-Figure 6SB The image depicts a first electronic device 600 displaying an XYZ Medical Center user interface 698 via a touch-sensitive display device 602. In some examples, the XYZ Medical Center user interface 698 is displayed in response to user input corresponding to a selection of a first health record enablement display 636 in the health record area of ​​the summary user interface 614, such as... Figure 6DC What is depicted.

[0336] like Figure 6SA-Figure 6SB The depicted XYZ Medical Center user interface 698 includes multiple regions (e.g., regions representing different days), each region corresponding to a different date on which health records within that region were generated (e.g., collected, obtained, or otherwise created by a clinical institution). In some examples, the multiple regions are sorted by date such that regions corresponding to more recent dates precede regions corresponding to later dates. For example, the XYZ Medical Center user interface 698 includes regions in the list that correspond to November 2, 2018 (e.g., regions corresponding to more recent dates). Figure 6SC The area depicted (e.g., prior to it) corresponds to March 29, 2019 (such as...). Figure 6SB (As depicted).

[0337] In some implementations, each area included in the XYZ Medical Center user interface 698 comprises one or more sub-areas, each sub-area corresponding to a different type of health record within the sub-area (e.g., allergies, medications, etc.). In some examples, multiple sub-areas are ordered alphabetically (e.g., allergies before medications) (not shown).

[0338] In some implementations, each sub-region included in the XYZ Medical Center user interface 698 comprises one or more representations of health records. For example, sub-region 698a includes four representations of four separate health records, such as representation 670b (also as...). Figure 6PA As depicted and described), it indicates 670c (also as Figure 6PA (as depicted and described), represents 698b (similar to...) Figure 6PB The 672b described and stated (but from XYZ Medical Center, not ABC Emergency) and the 698c (similar to...) Figure 6PB The 672c described and mentioned, but from XYZ Medical Center, not ABC Emergency Department. Figure 6SA-Figure 6SB The diagram shows some representations that may include charts, while others do not, even representations corresponding to the same health record type. In some examples, this is because some health records do not include ranges and / or are binary values. Although Figure 6SA-Figure 6SB A user interface for a single clinical facility is described, but it should be recognized that similar techniques can be used for user interfaces that represent health records from multiple clinical facilities.

[0339] Figure 6TA The image depicts a first electronic device 600 displaying a search user interface 684 via a touch-sensitive display device 602 at a twentieth time following a nineteenth time. In some examples, the search user interface 684 is displayed in response to user input corresponding to a selection of a search enablement representation 642b in any user interface of a health application, such as a summary user interface 614.

[0340] like Figure 6TA The depicted search user interface 684 includes a search area 684a for inserting search queries to search for health applications. For example, when the first electronic device 600 receives user input corresponding to a string (e.g., user-typed strings from the keyboard) and a request to perform a search while focusing on the search area 684a (e.g., an insertion mark is located within the search area 684a), the first electronic device 600 searches for data associated with the health application based on that string, such as... Figure 6U As described and discussed further below.

[0341] like Figure 6TAThe search user interface 684, as depicted, includes four sets of capability representations: shared health data capability representation 684b, health category capability representation 684c, health record capability representation 684d, and health content capability representation 684g. In some examples, when the first electronic device 600 is not receiving shared health data from another device, the search user interface 684 includes fewer sets of capability representations, such as excluding shared health data capability representation 684b.

[0342] In some examples, the sharing of health data enables the use of 684b, which enables the linking of other accounts to accounts associated with the health application. In one example, the link involves a connection between two accounts, such that health data recorded for one account can be sent to the other account. For example, Figure 6TA A shared health data power representation 684b is described, including a power representation 684ba. In some examples, the power representation 684ba relates to an account associated with "Little Appleseed," such that selecting the power representation 684ba causes the display of a user interface for the account associated with "Little Appleseed" (e.g., a user interface allowing the user to view health data associated with the account associated with "Little Appleseed"), such as... Figure 6XA As described and discussed below.

[0343] In some examples, the health category power representation 684c relates to categories of health data types. Specifically, the health category power representation 684c represents a hierarchical structure of health data, allowing a user to navigate to specific health data through one or more user inputs. For example, the health category power representation 684c includes a power representation 684ca corresponding to an active health data type (e.g., a health data type corresponding to active activities). In some implementations, the active health data type corresponds to health data stored by an active application. As another example, the health category power representation 684c includes a power representation 684ck corresponding to a vital signs health data type (e.g., a health data type corresponding to vital signs). In some examples, the vital signs health data type corresponds to health data stored by a vital signs application.

[0344] In some examples, the selection of the power representation for the health category power representation 684c causes the user interface of the health application to be displayed, which includes health data associated with the corresponding health data type, such as... Figure 6V-Figure 6W As described and discussed below.

[0345] In some implementations, the power representation of health record power representation 684d relates to the category of health records, as discussed above. For example, health record power representation 684d represents a hierarchical structure of health records, allowing a user to navigate to a specific health record via one or more user inputs. For example, health record power representation 684d includes power representation 684de corresponding to laboratory results (e.g., the type of health record). In some examples, selection of power representation 684de causes a user interface to be displayed that includes laboratory result health records. Health record power representation 684d also includes power representations relating to clinical institutions (e.g., power representation 684h). Selection of a power representation associated with a clinical institution causes a user interface for a health application to be displayed that includes health records collected by the clinical institution. Selection of a power representation associated with all accounts (e.g., power representation 684dj) causes a user interface for a health application to be displayed that includes all health records.

[0346] like Figure 6TB The depicted search user interface 684 includes an indication of power 684e for viewing clinical documents. Selection of the indication of power 684e causes the user interface of the health application, which includes the clinical documents, to be displayed. Figure 6TB The depicted search user interface 684 includes an indication representation 684f for viewing unreadable data (e.g., data that the health application (or processes associated with the health application) cannot parse (e.g., interpret or read). Selection of the indication representation 684f causes the user interface of the health application to be displayed, which includes a representation of health records that cannot be parsed by the health application (or processes associated with the health application).

[0347] In some examples, the health content power representation 684g includes a power representation for viewing educational content. Choosing such a power representation causes a user interface for a health application to be displayed, which includes educational content. As another example, the health content power representation 684g includes a power representation for viewing the feeds discussed above. Choosing such a power representation causes a user interface for a health application to be displayed, which includes one or more feed representations.

[0348] Figure 6U The description depicts a first electronic device 600 displaying a search user interface 684 via a touch-sensitive display device 602 at a twenty-first time after a twenty-second time. In some embodiments, the search user interface 684 is displayed in response to a user request to search for a string entered into the search area 684a (e.g., ...). Figure 6U (As depicted). For example, Figure 6U This describes a scenario where a user has entered "blood pressure" into search area 684a, causing a health application to display search results corresponding to the search for "blood pressure." In some examples, the user requesting the search string causes the search results to be replaced (e.g., stopped from being displayed). Figure 6TA-Figure 6TB The four sets of display representations in the search user interface 684 depicted in the figure.

[0349] In some examples, search results include data from various sources. For instance, the first search result 684h includes health data (e.g., health data detected by the first electronic device 600 or another device linked to or associated with an account of the first electronic device 600 or a health application). Figure 6U As depicted, the first search result 684h includes a representation of blood pressure detected for a user associated with an account. Similarly, the second search result 684i includes health record data (e.g., health records received by the first electronic device 600 from, for example, a clinical institution). Figure 6U The second search result 685i described includes blood pressure data from health records.

[0350] In some examples, search results include categories of feeds identified as related to the string. For example, Figure 6U The search results are described as including cardiac feed energy representations 685ja (e.g., energy representations associated with feeds related to the heart) and vital signs feed energy representations 685jb (e.g., energy representations associated with feeds related to vital signs). In some examples, the selection of feed energy representations causes a user interface of the health application to be displayed, which includes one or more feed representations associated with the corresponding category of the feed.

[0351] In some examples, search results include categories (684k) identified as health data associated with strings. These categories correspond to the health category energy representation 684c discussed above. For example, Figure 6U The search results are depicted as including cardiac category energy representation (684kb), vital signs energy representation (684kb), and clinical vital signs energy representation (684kc). The categories of health data represent a hierarchical structure of health records, allowing users to navigate to specific health records via one or more user inputs. For example, selecting the energy representation corresponding to a category of health data causes a user interface to be displayed, which includes the health records corresponding to that category.

[0352] Figure 6VThe first electronic device 600 is depicted displaying an active user interface 686 via a touch-sensitive display device 602 at a twenty-second time following a twenty-first time. In some examples, the active user interface 686 is displayed in response to user input corresponding to a selection of an enable representation 684ca in a search user interface 684.

[0353] like Figure 6V The depicted activity user interface 686 includes a representation of health data related to the activity of an account associated with the health application. For example, the activity user interface 686 includes a representation 686a with heart rate data during strength training.

[0354] Figure 6W The first electronic device 600 is depicted displaying a vital signs user interface 688 via a touch-sensitive display device 602 at a twenty-third time following a twenty-second time. In some examples, the vital signs user interface 688 is displayed in response to user input corresponding to a selection of the power indicator 684ck in the search user interface 684.

[0355] like Figure 6W The depicted vital signs user interface 688 includes representations of health data related to the vital signs of an account associated with the health application. For example, the activity user interface 686 includes a representation 688a of heart rate data during strength training. Representation 688a is an example of health data included in one category (e.g., vital signs) that may be included in another category (e.g., activity). This results in health data having multiple categories associated with it. For example, heart rate data during strength training (e.g., heart rate data during strength training) Figure 6V-Figure 6W The data depicts both activity and vital signs. In some examples, health data has primary and secondary health categories.

[0356] Figures 6XA-6XB The image depicts a first electronic device 600 displaying a child search user interface 690 via a touch-sensitive display device 602 at a twenty-fourth time, following a twenty-third time. In some examples, the child search user interface 690 and the user interface navigating from the indication included in the child search user interface 690 are read-only (unlike the search user interface 684, which in some examples allows the user to add / remove / edit data when navigating to data associated with an account in the health application). In some examples, the child search user interface 690 is displayed in response to user input corresponding to a selection on the indication 684ba in the search user interface 684.

[0357] In some examples, the child search user interface 690 is a version of the search user interface 684 used to link to accounts associated with the health application. For example... Figures 6XA-6XB The depicted child search user interface 690 includes a search area 692a (similar to search area 684a in search user interface 684, except that search area 692a searches for data corresponding to an account associated with Little Appleseed rather than the Health app), a health category indicator 692b (similar to health category indicator 684c in search user interface 684, except that health category indicator 692b is associated with data corresponding to an account associated with Little Appleseed rather than the Health app), a health record indicator 692c (similar to health record indicator 684d in search user interface 684, except that health record indicator 692c is associated with data corresponding to an account associated with Little Appleseed rather than the Health app), and a health content indicator 692e (similar to health content indicator 684g in search user interface 684). In some examples, the child search user interface 690 does not include a shared health data indicator (e.g., shared health data indicator 684ba). In other examples, the child search user interface 690 includes a display of shared health data for devices linked to LittleAppleseed accounts.

[0358] Figure 6Y The first electronic device 600 is depicted displaying an active user interface 694 via a touch-sensitive display device 602 at a twenty-fifth time, following a twenty-fourth time. In some examples, the active user interface 694 is displayed in response to user input corresponding to a selection of an active enable representation in the child search user interface 690.

[0359] like Figure 6Y The depicted activity user interface 694 includes a representation of health data related to the activity of the Little Appleseed account (e.g., as shown in instruction 694a). For example, the activity user interface 694 includes a representation 694c with heart rate data during strength training for Little Appleseed.

[0360] Figure 6Z The first electronic device 600 is depicted displaying a vital signs user interface 696 via a touch-sensitive display device 602 at a twenty-sixth time, following a twenty-fifth time. In some examples, the vital signs user interface 696 is displayed in response to user input corresponding to a selection of a vital signs indication in a child search user interface 690.

[0361] like Figure 6ZThe depicted vital signs user interface 696 includes representations of health data related to the vital signs of a Little Appleseed account (e.g., as shown in indication 696a). For example, the vital signs user interface 696 includes a representation 696c of heart rate data during strength training for Little Appleseed. Representation 696c is an example of health data included in one category (e.g., vital signs) that may be included in another category (e.g., activity). This results in health data having multiple categories with which it is associated. For example, heart rate data during strength training (e.g., heart rate data during strength training) Figures 6Y-6Z The data depicts both activity and vital signs. In some examples, health data has primary and secondary health categories.

[0362] Figures 7A-7B This is a flowchart illustrating a method for managing notifications using an electronic device according to some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500, 600, 606) having a display device. Some operations in method 700 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0363] In some embodiments, the electronic device (e.g., 600, 606) is a computer system. The computer system optionally communicates with a display generating component and one or more input devices (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface for receiving user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generating component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0364] As described below, Method 700 provides an intuitive way to manage notifications. This method reduces the cognitive burden on users of viewing and acting on notifications, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to view and act on notifications faster and more efficiently, saving power and increasing the time between battery charging.

[0365] The electronic device displays (702) a first instance (e.g., 614, such as) of a first user interface including a first notification (e.g., 616, 618, 620) (e.g., a notification indication) via a display device. Figure 6DA The first notification, when selected, causes a first set of data (e.g., 644) to be displayed immediately (e.g., notification data, data generated or received (e.g., from an external device); health data; sensor data; biometric data; physical activity data; clinical data).

[0366] In some embodiments, the first notification includes a first visual attribute (704) (e.g., color (e.g., a pattern depicted in header 616 including 616b and 616c, a pattern in header 618 including 618a, 618b and 618c, and a pattern in header 620 including 620a, 620b and 620c) (e.g., foreground color, background color, including (or excluding) corresponding icons). In some embodiments, it is determined according to (706) that the first set of data corresponds to a first application (e.g., generated by the first application), and the first visual attribute has a first value (e.g., blue). In some embodiments, it is determined according to (708) that the first set of data corresponds to a second application, and the first visual attribute has a second value different from the first value (e.g., red).

[0367] Based on the visual quality (e.g., color) of the notifications specified by the corresponding application, feedback is provided to help users identify the application. Providing users with improved visual feedback enhances device operability and makes the user device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0368] After displaying a first instance of the first user interface, the electronic device displays (710) (e.g., in response to input corresponding to a request to display the first user interface) a second instance of the first user interface (e.g., 614, as...). Figure 6G (As depicted).

[0369] According to (712), a set of interaction criteria (a set of criteria related to whether the first set of data has been interacted with (e.g., via the selection of the first notification) is satisfied, including criteria that are satisfied when the first set of data has been displayed (e.g., displayed in a first instance of the first user interface, displayed in a subsequent instance of the first user interface, displayed on an electronic device, displayed on a second electronic device receiving the same notification as the electronic device (e.g., because both are associated with the same user account)). Furthermore, according to the determination that a first set of removal criteria (e.g., a set of criteria governing the display of notifications corresponding to the data that has been interacted with) is not satisfied, the first set of removal criteria includes a first criterion based on a first time period (e.g., a time period that must exceed the time period required to satisfy the first criterion; a time period determined from when the first set of data is received or generated; a time period determined from when the notification corresponding to the first set of data is first displayed; a non-zero time period). The second instance of the first user interface includes the first notification (…). Figures 6G-6H ).

[0370] Based on the determination that the set of interaction criteria (714) is met and based on the determination that the first set of removal criteria is met, the second instance of the first user interface does not include the first notification. Figures 6G-6H ).

[0371] According to (716), it is determined that the first set of interaction criteria is not met and according to the determination that the second set of removal criteria (e.g., a set of criteria for managing the display of notifications corresponding to data that has not yet been interacted with) is not met, the second set of removal criteria includes a second criterion based on a second time period (e.g., a time period that must exceed to meet the second criteria; a time period determined from when the first set of data is received or generated; a time period determined from when the notification corresponding to the first set of data is first displayed), the second instance of the first user interface includes the first notification ( Figures 6G-6H In some implementations, the second time period is shorter than the first time period.

[0372] Based on the determination that (718) the set of interaction criteria was not met and based on the determination that the second set of removal criteria was met, the second instance of the first user interface does not include the first notification. Figures 6G-6H In some implementations, the notification is displayed (or redisplayed) in the first user interface for a period of time, which varies depending on whether the notification has been interacted with. In some implementations, notifications that have not yet been interacted with are displayed for a longer period than notifications that have been interacted with.

[0373] Displaying the first notification based on whether the set of interaction criteria and removal criteria are met allows users to view relevant notifications without being presented with unwanted ones. Performing actions when a set of conditions have been met and no further user input is required enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0374] In some embodiments, prior to displaying a first instance of the first user interface, the electronic device receives a second set of data from an external device (e.g., a smartwatch including one or more sensors, such as biometric sensors), where the first set of data corresponds to the second set of data (e.g., 610). In some embodiments, the external device and the electronic device are paired (e.g., both devices are associated with the same user account and have a persistent relationship). In some embodiments, the second set of data is the first set of data. In some embodiments, the second set of applications is included in the first set of data. In some embodiments, the first set of data is derived from the second set of data (e.g., calculations are based on the second set of data). In some embodiments, the second set of data is sensor data from one or more sensors of the external device. In some embodiments, the second set of data includes clinical health data (e.g., 604b) (e.g., medical records from a health institution; test results from a clinical testing laboratory).

[0375] In some embodiments, the electronic device includes a set of one or more sensors (e.g., biometric sensors). In some embodiments, prior to displaying a first instance of the first user interface, the electronic device receives (e.g., detects) a third set of data (e.g., 604a) via the set of one or more sensors. In some embodiments, the first set of data corresponds to the third set of data. In some embodiments, the third set of data is the first set of data. In some embodiments, the third set of data is included in the first set of data. In some embodiments, the first set of data is derived from the third set of data (e.g., calculated based on the third set of data). In some embodiments, prior to displaying the first instance of the first user interface, the electronic device displays a second user interface (e.g., any user interface other than the summary tab of a health application, such as a lock screen) that includes a second notification corresponding to the third set of data. In some embodiments, the second user interface differs from the first user interface. In some embodiments, the second notification includes the same content as the first notification.

[0376] In some implementations, the first notification is included in a first notification list. In some implementations, the first notification list is sorted based on chronological order or reverse chronological order (e.g., based on the time the initial notification was published; based on the time when data was generated or received when the corresponding notification was selected). Figure 6DA ).

[0377] Sort the first list based on a chronological or reverse chronological order structure to provide the user with feedback on the sequence in which notifications are generated. Providing the user with improved visual feedback enhances device operability and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0378] In some embodiments, upon displaying the first notification (e.g., in a first or second instance of the first user interface), the electronic device receives a first input (e.g., 615) corresponding to a selection of the first notification. In some embodiments, in response to receiving the first input, the electronic device displays a second user interface (e.g., 644) via a first display device (e.g., which includes a first set of data). In some embodiments, the first set of data corresponds to a first application, and the second user interface includes additional data and / or information from the first application.

[0379] In some implementations, the first set of data corresponds to a first data type (e.g., biometric data, sensor data). In some implementations, the second user interface includes: a first indicator that, when selected, causes the display of a first value (e.g., a first average value) of the first data type; and a second indicator that, when selected, causes the display of a second value of the first data type that is different from the first value (e.g., a second average value based on a filter (e.g., a time filter, a source filter) different from the first average value) (e.g., the average value and daily average value indicator in 644).

[0380] It should be noted that the above is relative to method 700 (e.g., Figures 7A to 7B The details of the process described herein also apply in a similar manner to the methods described below. For example, methods 800, 900, 1000, 1100, and 1400 optionally include one or more features of the various methods described above with reference to method 700. For the sake of brevity, these details will not be repeated below.

[0381] Figures 8A-8BThis is a flowchart illustrating a method for displaying health-related information using an electronic device, according to some embodiments. Method 800 is performed at a device (e.g., 100, 300, 500, 600) having a display device. Some operations in method 800 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0382] In some embodiments, the electronic device (e.g., 600) is a computer system. The computer system optionally communicates with a display generating component and one or more input devices (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generating component to visually generate content (e.g., using a display device), and can receive input via wired or wireless connections from one or more input devices.

[0383] As described below, method 800 provides an intuitive way to manage the display of health-related information. This method reduces the cognitive burden on users viewing health-related information, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to view health-related information faster and more efficiently, saving power and increasing the time between battery charging sessions.

[0384] The electronic device receives (802) first health data (e.g., physical activity performed by the user; data detected via one or more biometric sensors) (e.g., see 626b). In some embodiments, the first health data is received over a period of time. In some embodiments, the first health data is received together as a set.

[0385] The electronic device receives (804) a request (e.g., 613) to display a first user interface (e.g., 614) (e.g., a request to view the summary tab of a health application, such as the user tapping the icon of the health application or the user tapping the power indicator of the summary tab).

[0386] In response to a received request, the electronic device displays (806) a first user interface (e.g., 614) via a display device, including a first area (e.g., the favorites area in 614) (808) (e.g., the favorites portion). If, according to (812), it is determined that the data type corresponding to the first health data (e.g., activity, ambient noise, etc.) has been identified by user input (e.g., the user has favorited the data type), the first user area includes a first representation of the first health data (e.g., 626a) (e.g., the number of steps taken that day). If, according to (814), it is determined that the type of data corresponding to the first health data has not yet been identified by user input (e.g., the user has not favorited the data type), the first user area does not include a representation of the first health data.

[0387] In response to a received request, the electronic device displays (806) a first user interface including a second region (e.g., a feed area in 614) (810) (e.g., a feed portion) via a display device. If, according to (816), a first set of feed criteria (e.g., the system determines that a representation corresponding to health data should be displayed to the user) is satisfied, the second region includes a second representation (e.g., 630, 632, 652, 654, 656, 658, 660, 662) of the first health data, which differs from the first representation (e.g., a graphical representation comparing health data of a first health metric within a first time period with health data of a first health metric within a second time period different from the first time period). In some embodiments, the representation displayed in the second region is not user-customizable / user-selectable. In some embodiments, the representation displayed in the second region includes a comparison of health data with health data corresponding to a time period different from the time period of the health data. If, according to (818), the first set of feed criteria is not satisfied (e.g., the system determines that a representation corresponding to health data should not be displayed to the user), the second region does not include a second representation of the first health data.

[0388] The second representation, based on meeting the first set of feed criteria including the first health data, enables the device to display relevant information and avoid using display space when the information is irrelevant. Performing operations when a set of conditions has been met without further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0389] In some embodiments, the health data includes health data for a first plurality of time periods (e.g., days, weeks, months). In some embodiments, the first representation of the health data includes: a first indication (e.g., a text indication, a graphical indication, an indication of a first metric (e.g., steps, miles, calories)) corresponding to health data for a first time period (today) within the first plurality of time periods; and a second indication (e.g., a text indication, a graphical indication) corresponding to health data for a second time period (e.g., yesterday) different from the first time period within the first plurality of time periods. In some embodiments, the first representation includes a bar chart having today's value compared to yesterday's value (e.g., 632).

[0390] Providing different indicators for different time periods offers users feedback on the stored data corresponding to those time periods. Improved visual feedback enhances device operability and makes the user interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0391] In some implementations, the first time period in the first plurality of time periods corresponds to a specific instance of a cyclic time interval (e.g., a specific hour of a day, a specific day of a week, or a specific day of a month). In some implementations, the second time period in the first plurality of time periods consists of multiple instances. In some implementations, all instances of the cyclic time interval are available in the health data for the cyclic time interval (multiple Mondays over several weeks, multiple mornings over several days). In some implementations, the first indicator is the value of a health metric for a Monday in a week, and the second indicator is the average of the health metrics for all Mondays (e.g., 662).

[0392] In some implementations, the health data includes health data for a second plurality of time periods (e.g., days, weeks, months). In some implementations, the first representation of the health data includes a third indication (e.g., 654) of the health data corresponding to the frequency of occurrence (e.g., as a rate, as a percentage, as a fraction (e.g., 4 days in the previous week)) of a first health event (e.g., a health-related event) within the plurality of second plurality of time periods (e.g., days, weeks, years).

[0393] In some embodiments, the health data includes health data for a third plurality of time periods (e.g., daily, weekly, monthly). In some embodiments, a first representation of the health data includes: a fourth indication of the average value of health data for the third plurality of time periods (e.g., a weekly average); a fifth indication corresponding to the value of health data within a first time period (e.g., a day within a week) of the third plurality of time periods; and a sixth indication corresponding to the value of health data within a second time period (e.g., a day within a week) of the third plurality of time periods, the second time period being different from the first time period (e.g., 652).

[0394] In some embodiments, the first indication includes a seventh indication corresponding to a first physical activity tracking session (e.g., a first workout). In some embodiments, the first indication includes an eighth indication corresponding to a second physical activity tracking session. In some embodiments, the first and second physical activity tracking sessions are different types of workouts (e.g., running and swimming). In some embodiments, the first and second physical activity tracking sessions correspond to the same time period (e.g., the same day, the same week, the same month). In some embodiments, a ninth indication of health data (e.g., total calories burned, average pace) is based on the first and second physical activity tracking sessions (e.g., 658).

[0395] Displaying indicators based on health data from both the first and second physical activity tracking sessions provides the user with feedback on both sessions. Providing improved visual feedback enhances device operability and makes the user interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0396] In some implementations, the first set of feed criteria includes criteria based on factors selected from a group consisting of: the relationship (e.g., mathematical relationship (e.g., difference)) between a first portion of health data (e.g., a portion corresponding to a first time period (e.g., a day)) and a second portion of health data (e.g., a second time period (e.g., a week)), the degree of user interaction with the health data, and the duration for which a representation of the health data (e.g., any representation) has been displayed (e.g., on an electronic device).

[0397] In some implementations, the first representation is included in the list of first representations. In some implementations, the list of first representations is ordered (e.g., 660) based on the data type of the health data (e.g., physical activity data is grouped together; cardiac-related data is grouped together).

[0398] It should be noted that the above description is relative to the process described in method 800 (e.g., Figures 8A-8B The details of the methods described above / below are also applicable in a similar manner. For example, methods 700, 900, 1000, 1100, and 1400 optionally include one or more features of the various methods described above with reference to method 800. For the sake of brevity, these details will not be repeated below.

[0399] Figures 9A-9B This is a flowchart illustrating a method for managing the display of clinical health records using electronic devices, according to some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500, 600, 606) having a display device. Some operations in method 900 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0400] In some embodiments, the electronic device (e.g., 600, 606) is a computer system. The computer system optionally communicates with a display generating component and one or more input devices (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface for receiving user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generating component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0401] As described below, method 900 provides an intuitive way to manage the display of clinical health record representations. This method reduces the cognitive burden on users accessing clinical health records, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to access clinical health records faster and more efficiently saves power and increases the time between battery charging sessions.

[0402] The electronic device receives (902) clinical health record data corresponding to a specific health institution (e.g., XYZ Medical Center in 672a, 698). The electronic device receives (904) a request to display a first user interface (e.g., 668, 698) (e.g., 667, tapping the first health record display 636 in the summary user interface 614) (e.g., a request to view all clinical health records of XYZ Medical Center).

[0403] In response to receiving a request, the electronic device displays (906) a first user interface (e.g., 668, 698) via a display device. The first user interface includes a first region (e.g., 672, 698a) (908) corresponding to a first type of clinical health record (e.g., 668b, 698a, laboratory results region). If it is determined (912) that the first clinical health record in the first type of clinical health record fails to meet a first set of drawing criteria (e.g., the first clinical health record (1) does not include the scope of the first clinical health record, or (2) includes binary information (which does not benefit the drawing in some examples)), the first region includes a first textual representation of the first clinical health record based on the clinical health record data (e.g., 672b, 672c, 698b, 698c), wherein the first user interface does not include a graphical representation of the first clinical health record (e.g., a non-text graphical representation). According to (914), the first clinical health record is determined to meet the first set of drawing criteria (e.g., the first clinical health record includes the range of the first clinical health record and includes non-binary information (which is beneficial from drawing in some examples), and the first region includes a first graphical representation of the first clinical health record based on the clinical health record data (e.g., 672d in 668) (e.g., 670b and 670c in 698).

[0404] In response to receiving a request, the electronic device displays (906) a first user interface via a display device, the first user interface including a second region (e.g., different date ranges in 668, drug region in 698) corresponding to a second type of clinical health record (e.g., a drug area) (910). Based on (916), if it is determined that a second clinical health record in the second type of clinical health record fails to meet a first set of drawing criteria (e.g., the second clinical health record (1) does not include the scope of the second clinical health record, or (2) includes binary information (which does not benefit drawing in some examples)), the second region includes a second textual representation of the second clinical health record based on the clinical health record data, wherein the user interface does not include a graphical representation of the second clinical health record. Based on (918), if it is determined that the second clinical health record meets the first set of drawing criteria (e.g., the second clinical health record includes the scope of the second clinical health record and includes non-binary information (which benefits drawing in some examples), the second region includes a second graphical representation of the second clinical health record based on the clinical health record data.

[0405] Displaying textual or graphical representations of health records provides users with feedback on whether the records meet mapping standards and allows them to access record-related information more quickly and effectively. Providing improved visual feedback enhances device operability and makes the user interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0406] In some implementations, when a corresponding clinical health record (e.g., a first clinical health record) corresponds to health data that includes a range of data, a first set of drawing criteria is satisfied for the corresponding clinical health record (e.g., the first set of drawing criteria includes criteria satisfied when the clinical health record includes a range of clinical health records) (e.g., defining minimum and maximum values ​​of the range, wherein data values ​​corresponding to the corresponding clinical health record are considered to meet specific criteria (e.g., criteria related to whether data values ​​are acceptable, such as criteria set by the governing body)) (e.g., 670b, 670c).

[0407] In some implementations, when the corresponding clinical health record (e.g., the first clinical health record) corresponds to binary (e.g., health data with binary status (positive or negative, up or down, prescribed or not prescribed)), a first set of drawing criteria is not met for the corresponding clinical health record (e.g., the first set of drawing criteria includes criteria that are met when the clinical health record includes non-binary digital data) (e.g., 698c).

[0408] In some implementations, the first region includes multiple representations of clinical health records (e.g., text representations). In some implementations, the multiple representations are primarily sorted by date (e.g., date-to-time order, date-to-reverse-time order), and secondarily by the health record type associated with each clinical health record in each of the multiple representations. In some implementations, record types include medications, laboratory results, symptoms, diseases, and treatments.

[0409] First, the records are sorted by date, then by health record type, providing users with feedback on the corresponding date order and record type. Providing improved visual feedback enhances device operability and makes the user interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0410] In some implementations, the first region includes a second plurality of representations of clinical health records (e.g., text representations). In some implementations, the second plurality of representations are primarily ordered by health record type, and secondarily by the date associated with each clinical health record in each representation of the second plurality of representations (e.g., date-to-time order, date-to-reverse-time order). In some implementations, health record types include medications, laboratory results, symptoms, diseases, and treatments.

[0411] First, the records are sorted by health record type, then by date, providing users with feedback on the corresponding record type and the date order of the records. Providing users with improved visual feedback enhances device operability and makes the user interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0412] In some embodiments, the first region includes a third plurality of representations (e.g., text representations) of the clinical health record, each representation corresponding to a clinical health record associated with a first date (e.g., the date the record was received (e.g., by an electronic device)) and a second date different from the first date (e.g., the date corresponding to a health event in the clinical health record (e.g., when a test was performed, when a prescription was written)). In some embodiments, the third plurality of representations are sorted by the first date based on whether the first user interface is a user interface of a first interface type (e.g., a summary user interface). In some embodiments, the third plurality of representations are sorted by the second date based on whether the first user interface is a user interface of a second interface type different from the first interface type (e.g., a user interface for a specific type of health data).

[0413] It should be noted that the above description is relative to the process described in method 900 (e.g., Figures 9A to 9B The details of the above methods can also be applied in a similar manner. For example, methods 700, 800, 1000, 1100, and 1400 optionally include one or more features of the various methods described above with reference to method 900. For the sake of brevity, these details will not be repeated below.

[0414] Figures 10A-10B This is a flowchart illustrating a method for managing the display of clinical health records using el...

Claims

1. A method for sharing health data, comprising: At the first electronic device having a display device: Receive a request to share health data associated with the first electronic device; In response to receiving the request, a first notification is displayed via the display device at a first time, the first notification including a first power indication, which, when selected, initiates a process for sharing health data associated with the first electronic device with a second electronic device; When the notification is displayed, a first user input corresponding to the selection of the first indication is received; In response to receiving the first user input, a process is initiated for sharing health data associated with the first electronic device with the second electronic device; as well as After receiving the first user input: Sharing health data associated with the first electronic device with the second electronic device; and In response to detecting that a predefined amount of time has elapsed since the start of sharing health data associated with the first electronic device with the second electronic device, a second notification corresponding to the sharing of health data is displayed via the display device at a second time. The second notification includes a second enable signal, which, when selected, initiates the process of ending the sharing of health data associated with the first electronic device with the second electronic device and causes the second electronic device to delete the health data associated with the first electronic device from its memory.

2. The method according to claim 1, further comprising: When the second notification is displayed, a set of one or more inputs is received, the set of one or more inputs including inputs corresponding to the selection of the second indication; as well as In response to receiving the set of one or more inputs, the sharing of health data associated with the first electronic device with the second electronic device is stopped.

3. The method according to claim 2, further comprising: After receiving the first user input, the health data associated with the first electronic device is shared with the third electronic device; as well as After receiving the set of one or more inputs, continue to share the health data associated with the first electronic device with the third electronic device.

4. The method according to any one of claims 1-2, wherein the first notification includes a third indication, the third indication being selected as follows: This causes the first electronic device to abandon the process of initiating the sharing of health data associated with the first electronic device with the second electronic device; and This causes the first electronic device to abandon its request to the fourth electronic device to receive health data associated with the first electronic device.

5. The method according to any one of claims 1-2, wherein the first notification includes a fourth indication, the fourth indication being selected as follows: This causes the first electronic device to abandon the process of initiating the sharing of health data associated with the first electronic device with the second electronic device; and This causes the first electronic device to transmit a request to the fifth electronic device to receive health data associated with the first electronic device.

6. The method according to any one of claims 1-2, wherein the first electronic device is associated with a first user account, and the second electronic device is associated with a second user account different from the first user account.

7. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device having a display device, the one or more programs including instructions for performing the following operations: Receive a request to share health data associated with the first electronic device; In response to receiving the request, a first notification is displayed via the display device at a first time, the first notification including a first power indication, which, when selected, initiates a process for sharing health data associated with the first electronic device with a second electronic device; When the notification is displayed, a first user input corresponding to the selection of the first indication is received; In response to receiving the first user input, a process is initiated for sharing health data associated with the first electronic device with the second electronic device; as well as After receiving the first user input: Sharing health data associated with the first electronic device with the second electronic device; and In response to detecting that a predefined amount of time has elapsed since the start of sharing health data associated with the first electronic device with the second electronic device, a second notification corresponding to the sharing of health data is displayed via the display device at a second time. The second notification includes a second enable signal, which, when selected, initiates the process of ending the sharing of health data associated with the first electronic device with the second electronic device and causes the second electronic device to delete the health data associated with the first electronic device from its memory.

8. The computer-readable storage medium of claim 7, wherein the one or more programs include instructions for performing the following operations: When displaying the second notification, a set of one or more inputs is received, the set of one or more inputs including inputs corresponding to the selection of the second display representation; and In response to receiving the set of one or more inputs, the sharing of health data associated with the first electronic device with the second electronic device is stopped.

9. The computer-readable storage medium of claim 8, wherein the one or more programs include instructions for performing the following operations: After receiving the first user input, the health data associated with the first electronic device is shared with the third electronic device; and After receiving the set of one or more inputs, continue to share the health data associated with the first electronic device with the third electronic device.

10. The computer-readable storage medium according to any one of claims 7-8, wherein the first notification includes a third indication, the third indication being selected as follows: This causes the first electronic device to abandon the process of initiating the sharing of health data associated with the first electronic device with the second electronic device; and This causes the first electronic device to abandon its request to the fourth electronic device to receive health data associated with the first electronic device.

11. The computer-readable storage medium according to any one of claims 7-8, wherein the first notification includes a fourth indication, the fourth indication being selected as follows: This causes the first electronic device to abandon the process of initiating the sharing of health data associated with the first electronic device with the second electronic device; and This causes the first electronic device to transmit a request to the fifth electronic device to receive health data associated with the first electronic device.

12. The computer-readable storage medium according to any one of claims 7-8, wherein the first electronic device is associated with a first user account, and the second electronic device is associated with a second user account different from the first user account.

13. A first electronic device, comprising: Display devices; One or more processors; and The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: Receive a request to share health data associated with the first electronic device; In response to receiving the request, a first notification is displayed via the display device at a first time, the first notification including a first power indication, which, when selected, initiates a process for sharing health data associated with the first electronic device with a second electronic device; When the notification is displayed, a first user input corresponding to the selection of the first indication is received; In response to receiving the first user input, a process is initiated for sharing health data associated with the first electronic device with the second electronic device; as well as After receiving the first user input: Sharing health data associated with the first electronic device with the second electronic device; and In response to detecting that a predefined amount of time has elapsed since the start of sharing health data associated with the first electronic device with the second electronic device, a second notification corresponding to the sharing of health data is displayed via the display device at a second time. The second notification includes a second enable signal, which, when selected, initiates the process of ending the sharing of health data associated with the first electronic device with the second electronic device and causes the second electronic device to delete the health data associated with the first electronic device from its memory.

14. The first electronic device of claim 13, wherein the one or more programs include instructions for performing the following operations: When displaying the second notification, a set of one or more inputs is received, the set of one or more inputs including inputs corresponding to the selection of the second display representation; and In response to receiving the set of one or more inputs, the sharing of health data associated with the first electronic device with the second electronic device is stopped.

15. The first electronic device of claim 14, wherein the one or more programs include instructions for performing the following operations: After receiving the first user input, the health data associated with the first electronic device is shared with the third electronic device; and After receiving the set of one or more inputs, continue to share the health data associated with the first electronic device with the third electronic device.

16. The first electronic device according to any one of claims 13-14, wherein the first notification includes a third power indication, the third power indication being selected as follows: This causes the first electronic device to abandon the process of initiating the sharing of health data associated with the first electronic device with the second electronic device; and This causes the first electronic device to abandon its request to the fourth electronic device to receive health data associated with the first electronic device.

17. The first electronic device according to any one of claims 13-14, wherein the first notification includes a fourth power indication, the fourth power indication being selected as follows: This causes the first electronic device to abandon the process of initiating the sharing of health data associated with the first electronic device with the second electronic device; and This causes the first electronic device to transmit a request to the fifth electronic device to receive health data associated with the first electronic device.

18. The first electronic device according to any one of claims 13-14, wherein the first electronic device is associated with a first user account, and the second electronic device is associated with a second user account different from the first user account.

19. A first electronic device, comprising: Display devices; and Apparatus for performing the method according to any one of claims 1-6.

20. A computer program product comprising one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs comprising instructions for performing the method according to any one of claims 1-6.

Images