Browser Application User Interface

Abstract

To provide electronic devices with faster, more efficient methods and interfaces for managing health information and functions.SOLUTION: A method comprises: displaying, via a display device, a first instance of a first user interface including a first notification that causes display of a first data set when selected; and after displaying the first instance of the first user interface, displaying a second instance of the first user interface. The method determines whether or not the second instance includes the first notification on the basis of whether or not a set of interaction criteria including a criterion that is met when the first data set has been displayed and a set of removal criteria are met.SELECTED DRAWING: Figure 7A

Description

[Technical field]

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

[0002] The present disclosure relates generally to computer user interfaces, and more specifically to techniques and user interfaces for managing health information and functions. [Background technology]

[0003] Electronic devices collect, store, and access health-related information about a user. Such devices provide users with the ability to manage their health information and corresponding functions using the electronic devices. Summary of the Invention

[0004] However, some techniques for managing health information and functions using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that can include multiple key presses or keystrokes. Existing techniques take more time than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0005] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing health information and functions. Such methods and interfaces optionally complement or replace other methods for managing health information and functions. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0006] According to some embodiments, a method is described. In some embodiments, the method is performed in an electronic device comprising a display device. In some embodiments, the method comprises: displaying, via the display device, a first instance of a first user interface including a first notification that, when selected, causes a display of a first data set; and, after displaying the first instance of the first user interface, displaying a second instance of the first user interface, wherein the second instance of the first user interface includes the first notification in accordance with a determination that a set of interaction criteria is satisfied including criteria that are satisfied when the first data set is displayed, and in accordance with a determination that a first set of removal criteria is not satisfied including a first criterion based on a first time period. and in accordance with a determination that the set of interaction criteria are met and in accordance with a determination that the first set of removal criteria are met, the second instance of the first user interface does not include the first notification, in accordance with a determination that the set of interaction criteria are not met and in accordance with a determination that a second set of removal criteria including a second criterion based on a second period longer than the first period are not met, the second instance of the first user interface includes the first notification, in accordance with a determination that the interaction criteria are not met and in accordance with a determination that the second set of removal criteria are met, the second instance of the first user interface does not include the first notification.

[0007] In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs comprise: displaying, via the display device, a first instance of a first user interface including a first notification that, when selected, causes a display of a first data set; and displaying, after displaying the first instance of the first user interface, a second instance of the first user interface, wherein the second instance of the first user interface selects the first notification in accordance with a determination that a set of interaction criteria is satisfied including criteria that are satisfied when the first data set is displayed and in accordance with a determination that a first set of removal criteria is not satisfied including a first criterion based on a first time period. and in accordance with a determination that the set of interaction criteria are met and in accordance with a determination that the first set of removal criteria are met, the second instance of the first user interface does not include the first notification, in accordance with a determination that the set of interaction criteria are not met and in accordance with a determination that a second set of removal criteria including a second criterion based on a second period longer than the first period are not met, the second instance of the first user interface includes the first notification, in accordance with a determination that the set of interaction criteria are not met and in accordance with a determination that the second set of removal criteria are met, the second instance of the first user interface does not include the first notification.

[0008] In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs comprise: displaying, via the display device, a first instance of a first user interface including a first notification that, when selected, causes a display of a first data set; and displaying, after displaying the first instance of the first user interface, a second instance of the first user interface, wherein the second instance of the first user interface is configured to remove the first data set from the first data set in accordance with a determination that a set of interaction criteria is satisfied including criteria that are satisfied when the first data set is displayed and in accordance with a determination that a first set of removal criteria is not satisfied including a first criterion based on a first time period. The second instance of the first user interface includes the first notification, and in accordance with a determination that the set of interaction criteria are met and in accordance with a determination that the first set of removal criteria are met, the second instance of the first user interface does not include the first notification, and in accordance with a determination that the set of interaction criteria are not met and in accordance with a determination that a second set of removal criteria including a second criterion based on a second period longer than the first period are not met, the second instance of the first user interface includes the first notification, and in accordance with a determination that the interaction criteria are not met and in accordance with a determination that the second set of removal criteria are met, the second instance of the first user interface does not include the first notification.

[0009] 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 comprising: displaying, via the display device, a first instance of a first user interface including a first notification that when selected causes a display of a first data set; and displaying, after displaying the first instance of the first user interface, a second instance of the first user interface; and, following a determination that a set of interaction criteria is satisfied including criteria that are satisfied when the first data set is displayed, a first set of removal criteria is satisfied including a first criterion based on a first time period. According to a determination that the second instance of the first user interface does not include the first notification, the second instance of the first user interface includes the first notification, and according to a determination that the set of interaction criteria are met, and according to a determination that the first set of removal criteria are met, the second instance of the first user interface does not include the first notification, the set of interaction criteria are not met, and according to a determination that a second set of removal criteria including a second criterion based on a second period longer than the first period is not met, the second instance of the first user interface includes the first notification, and according to a determination that the set of interaction criteria are not met, and according to a determination that the second set of removal criteria are met, the second instance of the first user interface does not include the first notification.

[0010] 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 that when selected causes a display of a first data set, and means for displaying a second instance of the first user interface after displaying the first instance of the first user interface, the second instance of the first user interface being configured to display the first data set in response to a determination that a set of interaction criteria is satisfied including criteria that are satisfied when the first data set is displayed and in response to a determination that a first set of removal criteria is not satisfied including a first criterion based on a first time period. The second instance of the first user interface includes the first notification, and in accordance with a determination that the set of interaction criteria are met, and in accordance with a determination that the first set of removal criteria are met, the second instance of the first user interface does not include the first notification, and in accordance with a determination that the set of interaction criteria are not met, and in accordance with a determination that a second set of removal criteria including a second criterion based on a second period longer than the first period is not met, the second instance of the first user interface includes the first notification, and in accordance with a determination that the set of interaction criteria are not met, and in accordance with a determination that the second set of removal criteria are met, the second instance of the first user interface does not include the first notification.

[0011] According to some embodiments, a method is described. In some embodiments, the method is performed in an electronic device that includes a display device. In some embodiments, the method comprises receiving first health data, receiving a request to display a first user interface, and in response to receiving the request, displaying via the display device the first user interface including a first region that includes a first representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has been identified by the user input and that does not include the representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has not been identified by the user input, and a second region that includes a second representation of the first health data different from the first representation in accordance with a determination that a first set of highlighting criteria has been met and that does not include the second representation of the first health data in accordance with a determination that the first set of highlighting criteria has not been met.

[0012] In some embodiments, a non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs comprise instructions for receiving first health data and receiving a request to display a first user interface, and in response to receiving the request, displaying, via the display device, the first user interface including a first region including a first representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has been identified by user input and not including the representation of the first health data in accordance with a determination that a type of data 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 in accordance with a determination that a first set of highlighting criteria has been met and not including the second representation of the first health data in accordance with a determination that the first set of highlighting criteria has not been met.

[0013] In some embodiments, a transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs comprise instructions for receiving first health data and receiving a request to display a first user interface, and in response to receiving the request, displaying via the display device the first user interface including a first region including a first representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has been identified by user input and not including the representation of the first health data in accordance with a determination that a type of data 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 in accordance with a determination that a first set of highlighting criteria has been met and not including the second representation of the first health data in accordance with a determination that the first set of highlighting criteria has not been met.

[0014] 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 receiving a request to receive first health data and display a first user interface, and in response to receiving the request, displaying via the display device the first user interface including a first region including a first representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has been identified by the user input and not including the representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has not been identified by the user input, and a second region including a second representation of the first health data different from the first representation in accordance with a determination that a first set of highlighting criteria has been met and not including the second representation of the first health data in accordance with a determination that the first set of highlighting criteria has not been met.

[0015] 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, in response to receiving the request, via the display device, a first region that includes a first representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has been identified by user input and that does not include a representation of the first health data in accordance with a determination that a type of data corresponding to the first health data has not been identified by user input, and a second region that includes a second representation of the first health data different from the first representation in accordance with a determination that a first set of highlighting criteria has been met and that does not include the second representation of the first health data in accordance with a determination that the first set of highlighting criteria has not been met.

[0016] According to some embodiments, a method is described. In some embodiments, the method is performed in an electronic device comprising a display device. In some embodiments, the method includes receiving clinical health record data corresponding to a particular health institution, receiving a request to display a first user interface, and in response to receiving the request, displaying via the display device a first region corresponding to a first type of clinical health record, where if the first user interface does not include a graphical representation of the first clinical health record, in accordance with a determination that the first clinical health record of the first type of clinical health record does not meet a first set of graphing criteria, a first textual representation for the first clinical health record based on the clinical health record data, and a first graphical representation based on the clinical health record data, in accordance with a determination that the first clinical health record meets a first set of graphing criteria. and a second region corresponding to a second type of clinical health record, wherein if the user interface does not include the graphical representation for the second clinical health record in accordance with a determination that the second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria, the second region includes: a second textual representation for the second clinical health record based on the clinical health record data; and a second graphical representation for the second clinical health record based on the clinical health record data in accordance with a determination that the second clinical health record satisfies the first set of graphing criteria.

[0017] In some embodiments, a non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs include a program for receiving clinical health record data corresponding to a particular health institution, receiving a request to display a first user interface, and, in response to receiving the request, displaying, via the display device, a first region corresponding to a first type of clinical health record, where if the first user interface does not include a graphical representation of the first clinical health record, the first clinical health record of the first type does not meet a first set of graphing criteria, and a first textual representation of the first clinical health record based on the clinical health record data, where if the first user interface does not include a graphical representation of the first clinical health record, the first clinical health record of the first type does not meet a first set of graphing criteria. displaying a first user interface including a first region including a first graphical representation for the first clinical health record and a second region corresponding to a second type of clinical health record, the second region including a second textual representation for the second clinical health record based on the clinical health record data and a second graphical representation for the second clinical health record based on the clinical health record data in accordance with a determination that the second clinical health record satisfies the first set of graphing criteria if the user interface does not include the graphical representation for the second clinical health record in accordance with a determination that the second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria.

[0018] In some embodiments, a transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs include a step of: receiving clinical health record data corresponding to a particular health institution; receiving a request to display a first user interface; and, in response to receiving the request, displaying, via the display device, a first region corresponding to a first type of clinical health record, where if the first user interface does not include a graphical representation of the first clinical health record, the first clinical health record of the first type does not meet a first set of graphing criteria; and, in accordance with a determination that the first clinical health record of the first type does not meet a first set of graphing criteria, displaying a first textual representation of the first clinical health record based on the clinical health record data; and, in accordance with a determination that the first clinical health record meets a first set of graphing criteria, the first user interface includes a first textual representation of the first clinical health record based on the clinical health record data. displaying a first user interface including a first region including a first graphical representation for the first clinical health record and a second region corresponding to a second type of clinical health record, the second region including a second textual representation for the second clinical health record based on the clinical health record data and a second graphical representation for the second clinical health record based on the clinical health record data in accordance with a determination that the second clinical health record satisfies the first set of graphing criteria if the user interface does not include the graphical representation for the second clinical health record in accordance with a determination that the second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria.

[0019] 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 receiving clinical health record data corresponding to a particular health institution and receiving a request to display a first user interface, and in response to receiving the request, displaying, via the display device, a first region corresponding to a first type of clinical health record, where if the first user interface does not include a graphical representation of the first clinical health record according to a determination that the first clinical health record of the first type of clinical health record does not satisfy a first set of graphing criteria, a first textual representation for the first clinical health record based on the clinical health record data and the first clinical health record. displaying a first user interface including a first region including a first graphical representation for the first clinical health record based on the clinical health record data in accordance with a determination that the first set of graphing criteria is met, and a second region corresponding to a second type of clinical health record, wherein if the user interface does not include the graphical representation for the second clinical health record in accordance with a determination that the second clinical health record of the second type of clinical health record does not meet the first set of graphing criteria, the second region including a second textual representation for the second clinical health record based on the clinical health record data and a second graphical representation for the second clinical health record based on the clinical health record data in accordance with a determination that the second clinical health record meets the first set of graphing criteria.

[0020] 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 particular health institution, means for receiving a request to display a first user interface, and in response to receiving the request, displaying via the display device a first region corresponding to a first type of clinical health record, where if the first user interface does not include a graphical representation of the first clinical health record, in accordance with a determination that the first clinical health record of the first type of clinical health record does not satisfy a first set of graphing criteria, a first textual representation for the first clinical health record based on the clinical health record data, and in accordance with a determination that the first clinical health record satisfies a first set of graphing criteria. and a second region corresponding to a second type of clinical health record, wherein if the user interface does not include the graphical representation for the second clinical health record in accordance with a determination that the second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria, the second region includes: a second textual representation for the second clinical health record based on the clinical health record data; and a second graphical representation for the second clinical health record based on the clinical health record data in accordance with a determination that the second clinical health record satisfies the first set of graphing criteria.

[0021] According to some embodiments, a method is described. In some embodiments, the method is performed in an electronic device comprising a display device. In some embodiments, the method includes receiving 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, via the display device, the first user interface including a first representation based on the first clinical health record data, for the first clinical health record of the first type of clinical health record; receiving, while displaying the first user interface, a first user input corresponding to a selection of the first representation; and in response to receiving the first user input, displaying, via the display device, a first representation based on the first clinical health record data, for the first clinical health record of the first type of clinical health record. displaying a second user interface including a second representation based on the first clinical health record data for a second clinical health record of the first type, the second representation being different from the first representation, and a third representation based on the first clinical health record data for a second clinical health record of the first type, the third representation being different from the second representation and where 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 while displaying the second user interface corresponding to a selection of the third representation; and in response to receiving the second user input, displaying via the display device the third user interface including a fourth representation based on the first clinical health record data for the first clinical health record of the first type, the fourth representation being different from the first representation and different from the second representation.

[0022] In some embodiments, a non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs include: receiving 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, via the display device, a first user interface including a first representation based on the first clinical health record data, for the first clinical health record of the first type of clinical health record; receiving, while displaying the first user interface, a first user input corresponding to a selection of the first representation; and in response to receiving the first user input, displaying, via the display device, a first user interface including a first representation based on the first clinical health record data, for the first clinical health record of the first type of clinical health record. displaying a second user interface including a second representation based on the first clinical health record data for a second clinical health record of the first type, the second representation being different from the first representation, and a third representation based on the first clinical health record data for a second clinical health record of the first type, the third representation being different from the second representation and the second clinical health record of the first type being different from the first clinical health record of the first type; receiving a second user input while displaying the second user interface corresponding to a selection of the third representation; and in response to receiving the second user input, displaying via the display device the third user interface including a fourth representation based on the first clinical health record data for the first clinical health record of the first type, the fourth representation being different from the first representation and different from the second representation.

[0023] In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display device is described. In some embodiments, the one or more programs include: receiving 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, via the display device, a first user interface including a first representation based on the first clinical health record data, for the first clinical health record of the first type of clinical health record; receiving, while displaying the first user interface, a first user input corresponding to a selection of the first representation; and in response to receiving the first user input, displaying, via the display device, a first clinical health record data corresponding to a selection of the first representation, for the first clinical health record of the first type of clinical health record. displaying a second user interface including a second representation based on the first clinical health record data for a second clinical health record of the first type, the second representation being different from the first representation, and a third representation based on the first clinical health record data for a second clinical health record of the first type, the third representation being different from the second representation and different from the first clinical health record of the first type; receiving a second user input while displaying the second user interface corresponding to a selection of the third representation; and in response to receiving the second user input, displaying via the display device the third user interface including a fourth representation based on the first clinical health record data for the first clinical health record of the first type, the fourth representation being different from the first representation and different from the second representation.

[0024] 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 include: receiving 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, via the display device, a first user interface for the first clinical health record of the first type of clinical health record, the first representation based on the first clinical health record data; receiving, while displaying the first user interface, a first user input corresponding to a selection of the first representation; and in response to receiving the first user input, displaying, via the display device, a first user interface for the first clinical health record of the first type of clinical health record, the first representation based on the first clinical health record data. displaying a second user interface including, for a first clinical health record of the first type of clinical health record, a second representation based on the first clinical health record data, the second representation different from the first representation, and for a second clinical health record of the first type of clinical health record, the third representation different from the second representation and different from the first clinical health record of the first type; receiving a second user input while displaying the second user interface corresponding to a selection of the third representation; and in response to receiving the second user input, displaying via the display device the third user interface including a fourth representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record, the fourth representation different from the first representation and different from the second representation.

[0025] 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 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, and in response to receiving the request, displaying, via the display device, a first user interface including a first representation based on the first clinical health record data, for the first clinical health record of the first type of clinical health record, means for receiving, while displaying the first user interface, a first user input corresponding to a selection of the first representation, and in response to receiving the first user input, displaying, via the display device, a first clinical health record data corresponding to a selection of the first representation, for the first clinical health record of the first type of clinical health record. and a third representation based on the first clinical health record data for a second clinical health record of the first type, the second representation being different from the first representation, and a third representation based on the first clinical health record data for a second clinical health record of the first type, the third representation being different from the second representation and where the second clinical health record of the first type is different from the first clinical health record of the first type; means for receiving a second user input while displaying the second user interface corresponding to a selection of the third representation; and means for displaying, in response to receiving the second user input, via the display device, the third user interface including a fourth representation based on the first clinical health record data for the first clinical health record of the first type, the fourth representation being different from the first representation and different from the second representation.

[0026] According to some embodiments, a method is described. In some embodiments, the method is executed in an electronic device comprising a display device, the electronic device being associated with a first user account. In some embodiments, the method includes receiving a request to display a first user interface, and in response to receiving the first request, displaying via the display device the first user interface including a first portion including a first category affordance and a second portion including a first shared affordance corresponding to a second user account, while displaying the first user interface, receiving a first user input corresponding to a selection of the first category affordance, receiving a second user input corresponding to a selection of the first shared affordance, and in response to receiving the first user input, displaying via the display device a first user interface including a first portion including a first category affordance and a second portion including a first shared affordance corresponding to a second user account. displaying a second user interface including a representation of the selected first health data, in response to receiving the second user input, via the display device a third user interface including a first portion including a second category affordance corresponding to health data associated with the second user account for the first category, receiving a third user input corresponding to a selection of the second category affordance while displaying the third user interface, and in response to receiving the third user input, displaying a fourth user interface via the display device including a representation of the health data associated with the second user account for the first category.

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

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

[0029] 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 receiving a request to display a first user interface, and in response to receiving the first request, displaying via the display device the first user interface including a first portion including a first category affordance and a second portion including a first shared affordance corresponding to a second user account, receiving a first user input corresponding to a selection of the first category affordance while displaying the first user interface, receiving a second user input corresponding to a selection of the first shared affordance, and in response to receiving the first user input, , displaying via the display device a second user interface including a representation of first health data associated with the first user account for the first category; in response to receiving the second user input, displaying via the display device a third user interface including a first portion including a second category affordance corresponding to health data associated with the second user account for the first category; receiving a third user input corresponding to a selection of the second category affordance while displaying the third user interface; and in response to receiving the third user input, displaying via the display device a fourth user interface including a representation of the health data associated with the second user account for the first category.

[0030] 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, means for receiving a request to display a first user interface, and means for displaying, via the display device in response to receiving the first request, the first user interface including a first portion including a first category affordance and a second portion including a first shared affordance corresponding to a second user account, and means for receiving, while displaying the first user interface, a first user input corresponding to a selection of the first category affordance and a second user input corresponding to a selection of the first shared affordance, and means for displaying, via the display device, a first user input corresponding to a selection of the first shared affordance, in response to receiving the first user input, a first user input corresponding to a selection of the first shared affordance for the first category. means for displaying a second user interface including a representation of first health data associated with the second user account for 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 affordance corresponding to health data associated with the second user account for the first category, means for receiving a third user input corresponding to a selection of the second category affordance while 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 the health data associated with the second user account for the first category.

[0031] According to some embodiments, a method is described. In some embodiments, the method is performed in a first electronic device comprising a display device. In some embodiments, the method comprises: receiving a request to share health data associated with the first electronic device; in response to receiving the request, displaying, at a first time, via the display device, a first notification including a first affordance that, when selected, initiates a process for sharing health data associated with the first electronic device with a second electronic device; while displaying the notification, receiving a first user input corresponding to a selection of the first affordance; in response to receiving the first user input, initiating a process for sharing health data associated with the first electronic device with the second electronic device; after receiving the first user input, sharing the health data associated with the first electronic device with the second electronic device; and in a second time, displaying, via the display device, a second notification corresponding to sharing the health data, the second notification including a second affordance that, when selected, initiates a process for terminating sharing of health data associated with the first electronic device with the second electronic device.

[0032] In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device comprising a display device is described. In some embodiments, the one or more programs comprise receiving a request to share health data associated with the first electronic device; and in response to receiving the request, displaying, at a first time, via the display device, a first notification including a first affordance that, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; receiving a first user input corresponding to a selection of the first affordance while 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; after receiving the first user input, sharing the health data associated with the first electronic device with the second electronic device; and displaying, at a second time, via the display device, a second notification corresponding to sharing of the health data, the second notification including a second affordance that, when selected, initiates a process to terminate sharing of the health data associated with the first electronic device with the second electronic device.

[0033] In some embodiments, a temporary computer readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device comprising a display device is described. In some embodiments, the one or more programs comprise: receiving a request to share health data associated with the first electronic device, and in response to receiving the request, displaying, at a first time, via the display device, a first notification including a first affordance that, when selected, initiates a process for sharing the health data associated with the first electronic device with a second electronic device; receiving, while displaying the notification, a first user input corresponding to a selection of the first affordance; 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; after receiving the first user input, sharing the health data associated with the first electronic device with the second electronic device; and displaying, at a second time, via the display device, a second notification corresponding to sharing the health data, the second notification including a second affordance that, when selected, initiates a process for terminating the sharing of the health data associated with the first electronic device with the second electronic device.

[0034] According to some embodiments, a first electronic device is described. 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 comprising: receiving a request to share health data associated with the first electronic device; in response to receiving the request, displaying, at a first time, via the display device, a first notification including a first affordance that, when selected, initiates a process for sharing the health data associated with the first electronic device with the second electronic device; receiving, while displaying the notification, a first user input corresponding to a selection of the first affordance; 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; after receiving the first user input, sharing the health data associated with the first electronic device with the second electronic device; and displaying, at a second time, via the display device, a second notification corresponding to the sharing of the health data, the second notification including a second affordance that, 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 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, in response to receiving the request, a first notification via the display device at a first time, the first notification including a first affordance 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, while displaying the notification, a first user input corresponding to a selection of the first affordance, means for initiating, in response to receiving the first user input, a process for sharing the health data associated with the first electronic device with the second electronic device, and means for sharing the health data associated with the first electronic device after receiving the first user input, and means for displaying, in a second time, via the display device, a second notification corresponding to the sharing of the health data, the second affordance that, when selected, initiates a process for terminating the sharing of the health data associated with the first electronic device with the second electronic device.

[0036] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0037] Thus, devices are provided with faster, more efficient methods and interfaces for managing health information and functions, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for managing health information and functions. [Brief description of the drawings]

[0038] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0039] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

[0040] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing in accordance with some embodiments.

[0041] [Diagram 2] 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

[0042] [Diagram 3] 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0043] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0044] [Figure 4B] 1 illustrates an exemplary user interface of a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0045] [Figure 5A] 1 illustrates a personal electronic device according to some embodiments.

[0046] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0047] [Figure 5C] 1 illustrates example components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments. [Figure 5D] 1 illustrates example components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments.

[0048] [Figure 5E] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments. [Figure 5F] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments. [Figure 5G] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments. [Figure 5H] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments.

[0049] [Figure 6A] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6B] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6C] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6D1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6D2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6D3] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6D4] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6E] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6F] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6G] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6H] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6I] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6J] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6K1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6K2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6L] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6M1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6M2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6M3] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6M4]1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6N] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6O1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6O2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6P1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6P2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6Q] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6R1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6R2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6S] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6SA] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6SB] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6T1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6T2]1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6U] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6V] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6W] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6X1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6X2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6Y] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 6Z] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments.

[0050] [Figure 7A] FIG. 1 is a flow diagram illustrating a method for managing notifications using an electronic device according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a method for managing notifications using an electronic device according to some embodiments.

[0051] [Figure 8A] FIG. 1 is a flow diagram illustrating a method for managing the display of health-related information using an electronic device according to some embodiments. [Figure 8B] FIG. 1 is a flow diagram illustrating a method for managing the display of health-related information using an electronic device according to some embodiments.

[0052] [Figure 9A] FIG. 1 is a flow diagram illustrating a method for managing display of a clinical health record representation using an electronic device according to some embodiments. [Figure 9B] FIG. 1 is a flow diagram illustrating a method for managing display of a clinical health record representation using an electronic device according to some embodiments.

[0053] [Figure 10A] FIG. 1 is a flow diagram illustrating a method for managing display of a clinical health record representation using an electronic device according to some embodiments. [Figure 10B] FIG. 1 is a flow diagram illustrating a method for managing display of a clinical health record representation using an electronic device according to some embodiments.

[0054] [Figure 11A] FIG. 1 is a flow diagram illustrating a method for managing the display of health-related information for different user accounts using an electronic device according to some embodiments. [Figure 11B] FIG. 1 is a flow diagram illustrating a method for managing the display of health-related information for different user accounts using an electronic device according to some embodiments. [Figure 11C] FIG. 1 is a flow diagram illustrating a method for managing the display of health-related information for different user accounts using an electronic device according to some embodiments.

[0055] [Figure 12A1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12A2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12B1] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12B2] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12C] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12D] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12E] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12F] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12G] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12H] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 12I] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments.

[0056] [Figure 13A] 1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments. [Figure 13B] 1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments. [Figure 13C] 1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments. [Figure 13D] 1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments. [Figure 13E] 1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments. [Figure 13F]1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments. [Figure 13G] 1 illustrates an exemplary user interface for sharing health data using an electronic device according to some embodiments.

[0057] [Figure 14A] FIG. 1 is a flow diagram illustrating a method for sharing health data according to some embodiments. [Figure 14B] FIG. 1 is a flow diagram illustrating a method for sharing health data according to some embodiments.

[0058] [Figure 15A] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 15B] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 15C] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 15D] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 15E] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. [Figure 15F] 1 illustrates an exemplary user interface for viewing health data using an electronic device according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0059] The following description sets forth example methods, parameters, etc., however, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of example embodiments.

[0060] There is a need for electronic devices that provide efficient methods and interfaces for managing health information and functions. For example, it is advantageous to provide timely health-related notifications and suppress the display of useful notifications. In another example, it is advantageous to highlight certain health-related information to a user. Such techniques can reduce the cognitive burden on a user of managing health information and functions, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that is otherwise wasted on redundant user input.

[0061] In the following, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of an exemplary device for performing the technique of managing event notifications. FIGS. 6A-6Z illustrate an exemplary user interface for viewing health data using an electronic device, according to some embodiments. FIGS. 7A-7B are flow diagrams illustrating a method for managing notifications using an electronic device, according to some embodiments. FIGS. 8A-8B are flow diagrams illustrating a method for managing display of health-related information using an electronic device, according to some embodiments. FIGS. 9A-9B are flow diagrams illustrating a method for managing display of clinical health record representations using an electronic device, according to some embodiments. FIGS. 10A-10B are flow diagrams illustrating a method for managing display of clinical health record representations using an electronic device, according to some embodiments. FIGS. 11A-11C are flow diagrams illustrating a method for managing display of health-related information for various user accounts using an electronic device, according to some embodiments. The user interfaces of Figures 6A-6Z are used to illustrate the processes described below, including the processes of Figures 7A-7B, 8A-8B, 9A-9B, 10A-10B, and 11A-11C. Figures 12AA-12I illustrate example user interfaces for browsing health data using an electronic device, according to some embodiments. Figures 13A-13G illustrate example user interfaces for sharing health data using an electronic device, according to some embodiments. Figures 14A-14B are flow diagrams illustrating a method for sharing health data, according to some embodiments. The user interfaces of Figures 13A-13G are used to illustrate the processes described below, including the processes of Figures 14A-14B. Figures 15A-15F illustrate example user interfaces for browsing health data using an electronic device, according to some embodiments.

[0062] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first touch can be called a second touch, and a second touch can be called a first touch, without departing from the scope of various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

[0063] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments described and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that as used herein, the term "and / or" refers to and includes any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of 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.

[0064] The term "if" is interpreted, optionally, depending on the context, to mean "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" is interpreted, optionally, depending on the context, to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]."

[0065] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes causing the content (e.g., video data rendered or decoded by display controller 156) to be displayed by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate the content.

[0066] In the following discussion, we describe an electronic device that includes a display and a touch-sensitive surface, however, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0067] The device typically supports a variety of applications, such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a videoconferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0068] The 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 features of the touch-sensitive surface, and corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each application. In this manner, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

[0069] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 having a touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 may be conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0070] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​including at least four distinct values, and more typically including hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact, are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement for the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units that correspond to the surrogate measurement). In some implementations, the surrogate measurement for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of contact as an attribute of user input allows a user access to additional device functionality that may not otherwise be accessible by a user on devices of reduced size that have limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0071] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a 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., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user feels a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0072] It is understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in FIG. 1A may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

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

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

[0075] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. The RF circuitry 108 optionally communicates by wireless communication with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well known circuitry for detecting near field Communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is 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, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LDO), and other standard cellular technologies.Examples of technologies that may be used include, but are not limited to, wireless technology (IoT), wireless LAN (LAN), wireless LAN (LANG ... The present invention may use any of a number of communications standards, protocols, and technologies, including Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols not yet developed as of the filing date of this application.

[0076] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives an electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data, and transmits the audio data to the peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral such as an output-only headphone or a headset with both an output (e.g., one-ear or binaural headphones) and an input (e.g., a microphone).

[0077] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a 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 / send electrical signals from / to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system in communication 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 trackpad 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 a user's 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.

[0078] A quick press of the push button optionally disengages the lock on the touch screen 112 or optionally initiates the process of unlocking the device using a gesture on the touch screen, as described in U.S. Patent Application Serial No. 11 / 322,549, filed December 23, 2005, “Unlocking a Device by Performing Gestures on an Unlock Image,” U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0079] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or transmits electrical signals from touchscreen 112. Touchscreen 112 displays visual output to the user. This 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.

[0080] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or breaking of contact) on touchscreen 112 and translates the detected contacts into interactions 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 point of contact between touchscreen 112 and the user corresponds to the user's finger.

[0081] Touchscreen 112 optionally uses LCD (Liquid Crystal Display), LPD (Light Emitting Polymer Display), or LED (Light Emitting Diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a number of now known or later developed touch sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

[0082] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication No. 2002 / 0015024A1, each of which is incorporated by reference herein in its entirety. However, whereas touchscreen 112 displays visual output from device 100, a touch-sensitive touchpad does not provide visual output.

[0083] The touch-sensitive display in some embodiments of the touch screen 112 may be any of the touch-sensitive displays described in U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller," (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen," (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices," (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices," and (5) U.S. patent application Ser. No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input No. 11 / 228,758, filed Sep. 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface," (7) U.S. Patent Application No. 11 / 228,700, filed Sep. 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. Patent Application No. 11 / 228,737, filed Sep. 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent Application No. 11 / 367,749, filed Mar. 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entirety.

[0084] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. A user optionally contacts the touch screen 112 using any suitable object or appendage, such as a stylus, finger, etc. In some embodiments, the user interface is designed to primarily handle finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touch screen. In some embodiments, the device translates the rough finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

[0086] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0087] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back side of device 100, as opposed to touchscreen display 112, which is on the front side of the device, so that the touchscreen display is effective for use as a viewfinder for acquisition of still and / or video images. In some embodiments, the light sensor is located on the front of the device so that an image of the user is obtained, optionally for videoconferencing, and the user sees other videoconference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both videoconferencing and capturing still and / or video images, along with the touchscreen display.

[0088] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also called camera module), depth camera sensor 175 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that an image of the user with depth information is optionally obtained for a video conference and to capture a selfie image with depth map data while the user is viewing other video conference participants on a touch screen display. In some embodiments, depth camera sensor 175 is located on the back of the device, or on the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing) such that the depth camera sensor 175 is used for both video conferencing and capturing still and / or video images, in conjunction with a touch screen display.

[0089] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112 located on the front of device 100.

[0090] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to an input controller 160 within I / O subsystem 106. The proximity sensor 166 optionally functions as described in U.S. patent application Ser. No. 11 / 241,839, "Proximity Detector In Handheld Device," Ser. No. 11 / 240,788, "Proximity Detector In Handheld Device," Ser. No. 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," Ser. No. 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and Ser. No. 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0091] Apparatus 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0092] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “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 the touchscreen display in portrait or landscape view based on analysis of data received from the one or more accelerometers. In addition to accelerometer 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the location and orientation (e.g., vertical or horizontal) of device 100.

[0093] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / 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 applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates which applications, views, or other information are occupying various regions of touchscreen display 112; sensor state, which includes information obtained from the device's various sensors and input control devices 116; and location information regarding the location and / or orientation of the device.

[0094] Operating system 126 (e.g., Darwin®, RTXC®, LINUX®, UNIX®, OS X®, iOS®, WINDOWS®, or an embedded operating system such as VxWorks®) includes various software components and / or drivers that control and manage common system tasks (e.g., memory management, control of storage devices, power management, etc.) and facilitate communication between various hardware and software components.

[0095] The communications module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and 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 couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors that are the same as or similar to and / or compatible with the 30-pin connector used on iPod® (a trademark of Apple Inc.) devices.

[0096] Contact / motion module 130 optionally detects contact with touch screen 112 (in cooperation with display controller 156) and other touch-sensing devices (e.g., a touchpad or a physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact occurs (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across 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 up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact. These actions are, optionally, applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on a touchpad.

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

[0098] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

[0099] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, characters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

[0100] In some embodiments, graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including, as appropriate, coordinate data and other graphic characteristic data, from an application or the like, and then generates screen image data for output to display controller 156.

[0101] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0102] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0103] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as photo / video metadata, and to applications that provide location-based services, such as a weather widget, a local yellow pages widget, and a maps / navigation widget).

[0104] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ● Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141, ● Training support module 142, A camera module 143 for still and / or video images, ● Image management module 144, ●Video player module, ●Music player module, ● Browser module 147, ● Calendar module 148, ● a widget module 149, optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; ● A widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0105] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0106] In conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the contacts module 137 is used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in the memory 102 or memory 370), including, optionally, adding a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with a name, associating an image with a name, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141, and the like.

[0107] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct a conversation, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0108] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 contains executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with user commands.

[0109] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In conjunction with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0110] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0111] In conjunction with the RF circuitry 108, touch screen 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, the training support module 142 contains executable instructions for creating workouts (e.g., having time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor the workouts, selecting and playing music for the workouts, and displaying, storing, and transmitting the workout data.

[0112] In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting still images or video from memory 102.

[0113] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 contains executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0114] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0115] In cooperation with the RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 contains executable instructions for creating, displaying, modifying, and storing calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) in accordance with user instructions.

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

[0117] In conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the widget creator module 150 is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

[0118] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, search module 151 contains executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user commands.

[0119] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play pre-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 videos (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.).

[0120] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user instructions.

[0121] In conjunction with RF circuitry 108, touch screen 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 used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

[0122] In conjunction with touchscreen 112, display controller 156, contact / 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, online video module 155 includes instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos rather than email client module 140. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11 / 968,067, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007, the contents of which are incorporated by reference in their entireties herein.

[0123] Each of the above-identified modules and applications corresponds to a set of executable instructions that perform one or more of the functions previously described and methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0124] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

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

[0126] 1B is a block diagram illustrating example components for event processing according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 137-151, 155, 380-390 discussed above).

[0127] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 of application 136-1. Event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view(s) that are displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) is currently active, and application internal state 192 is used by event sorter 170 to determine which application view 191 the event information is delivered to.

[0128] In some embodiments, application internal state 192 includes additional information such as one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow a user to return to a previous state or view of application 136-1, and redo / undo cues of previous actions taken by the user.

[0129] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0130] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and / or for a predetermined duration).

[0131] In some embodiments, event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173.

[0132] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

[0133] Another aspect of a user interface associated with an application is the 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 respective application) in which the touch is detected optionally corresponds to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which the touch is detected is optionally referred to as a hit view, and the set of events that are recognized as suitable inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0134] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchical manner, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest level view in which an initiating sub-event (e.g., the first sub-event in a sub-event sequence that forms an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source as identified as the hit view.

[0135] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0136] Event dispatcher module 174 dispatches the event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 182 in an event queue.

[0137] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0138] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each including instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updaters 176, object updaters 177, GUI updaters 178, and / or event data 179 received from event sorter 170. Event handlers 190 optionally utilize or call data updaters 176, object updaters 177, or GUI updaters 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0139] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of metadata 183 and event delivery instructions 188 (optionally including sub-event delivery instructions).

[0140] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. 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 a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device's attitude).

[0141] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events in an event (187) include, for example, touch start, touch end, touch move, touch cancel, and multiple touches. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object for a given phase (touch start), a first lift off (touch end) for a given phase, a second touch on a displayed object for a given phase (touch start), and a second lift off (touch end) for a given phase. In another example, a definition of event 2 (187-2) is a drag on a displayed object. A drag includes, for example, a touch (or contact) on a displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0142] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, when a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed 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 respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0143] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0144] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event disabled, event failed, or event finished state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch gesture.

[0145] In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or are enabled to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in a view or programmatic hierarchy.

[0146] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predefined process.

[0147] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs a predetermined process.

[0148] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions 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 the touch-sensitive display.

[0149] In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0150] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 with input devices, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple presses or holds of a keyboard, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0151] FIG. 2 illustrates portable multifunction device 100 having touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upwards and / or downwards), and / or rolling of a finger in contact with device 100 (right to left, left to right, upwards and / or downwards). In some implementations or situations, accidental contact with a graphic does not select that graphic: for example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0153] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on / off and locking the device, volume control button 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external port 124 for docking / charging. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predefined period of time, to lock the device by pressing and releasing the button before the predefined time has elapsed, and / or to unlock the device or initiate an unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100.

[0154] FIG. 3 is a block diagram of an exemplary multifunction device having 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 computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial 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 that interconnect these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A) that generates tactile output on device 300, and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor 165 described above with reference to FIG. 1A). 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 magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0155] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0156] Attention is now directed to embodiments of a user interface, optionally implemented, for example, on portable multifunction device 100.

[0157] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. 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: signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi® signals; ●Time 404, ●Bluetooth (registered trademark) indicator 405, ● Battery status indicator 406, Tray 408 with icons of frequently used applications, such as: ○ An icon 416 for the phone module 138, labeled “Phone”, optionally including an indicator 414 of the number of missed calls or voicemail messages; ○ An icon 418 of the email client module 140, labeled “Mail”, optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the Browser module 147, labeled "Browser"; and ○ An icon 422 of the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages"; ○ Icon 426 of the Calendar module 148, labeled "Calendar", ○ Icon 428 of the image management module 144, labeled "Photos"; ○ An icon 430 of the camera module 143, labeled “camera”; ○ Icon 432 of the online video module 155, labeled "Online Video"; Icon 434 of Stock Price Widget 149-2, labeled "Stock Price" ○ Icon 436 of the map module 154, labeled "Map"; ○ Icon 438 of weather widget 149-1, labeled "Weather"; ○ Icon 440 of alarm clock widget 149-4, labeled "Clock"; ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ An icon 444 of the Notes module 153, labeled "Notes"; and ○ A settings application or module icon 446 labeled “Settings,” which provides access to settings for the device 100 and its various applications 136 .

[0158] 4A are merely exemplary. For example, icon 422 for video and music player module 152 may be labeled "Music" or "Music Player," although other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application that corresponds to that particular application icon.

[0159] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3) that has a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451 and / or one or more tactile output generators 357 that generate a tactile output to a user of device 300.

[0160] Although some of the following examples are given with reference to input on touch screen display 112 (wherein the touch-sensitive surface and display are combined), in some embodiments the device detects input on a touch-sensitive surface that is separate from the display shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, user input (e.g., contacts 460 and 462 and their movements) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0161] In addition, although the following examples are given primarily with reference to finger input (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a contact) followed by movement of a cursor along the path of the swipe (e.g., instead of a contact movement). As another example, a tap gesture is optionally replaced with a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting a contact and then stopping detection of the contact). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or a mouse and finger contacts are optionally used simultaneously.

[0162] FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of a contact (e.g., a touch) being applied. The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

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

[0164] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. 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, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0165] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. The device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 514 can be connected to a display 504, which can have a touch-sensing component 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, Near Field Communication (NFC), cellular, and / or other wireless communication techniques. The device 500 can include input mechanisms 506 and / or 508. The input mechanism 506 is optionally, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 is optionally a button.

[0166] 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 may be operatively connected to the I / O section 514.

[0167] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer readable storage media that store computer executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform techniques described below, including, for example, processes 700-1100 (FIGS. 7A-7B, 8A-8B, 9A-9B, 10A-10B, 11A-11C) and 1400 (FIGS. 14A-14B). A computer readable storage medium may 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 embodiments, the storage medium is a transient computer readable storage medium. In some embodiments, the storage medium is a non-transitory computer readable storage medium. A non-transitory computer readable storage medium may include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray technology, as well as resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0168] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.

[0169] The term "focus selector" as used herein refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other location marker, the cursor acts as the "focus selector," such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the "focus selector," such that when an input (e.g., a press input by contact) 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, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on a touchscreen display (e.g., by using a tab key or arrow keys to move focus from one button to another), and in these implementations the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the particular form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with).For example, positioning of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (and not another user interface element shown on the device's display).

[0170] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples, i.e., a set of intensity samples collected during a predefined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predefined event (e.g., after detecting a contact, before detecting a lift-off of the contact, before or after detecting the start of movement of the contact, before detecting an end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of a contact is optionally based on one or more of a maximum intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, a top 10th percentile value of the intensity of the contact, a half maximum intensity value of the contact, a 90th percentile value of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to forego performing the respective action).

[0171] FIG. 5C illustrates detecting multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram showing the current intensity measurements of the intensity sensors 524A-524D versus intensity units. In this example, the intensity measurements of the intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of the intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity. FIG. 5D illustrates assigning aggregate intensities to the 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 aggregate intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of a total intensity A according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to FIGS. 5C-5D can be performed using electronic devices similar or identical to device 100, 300, or 500. 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 a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity diagrams are not part of the displayed user interface, but are included in FIGS. 5C-5D as an aid to the reader.

[0172] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start location to an end location, at which point the intensity of the contacts increases. In this example, the characteristic intensity of the contacts at the end location is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contacts prior to determining the characteristic intensity of the contacts. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate small increases or decreases in the intensity of the swipe contacts for purposes of determining the characteristic intensity.

[0173] The intensity of the contact on the touch-sensitive surface is optionally characterized against 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 action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., above a nominal contact-detection intensity threshold below which the contact is not detected), the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent among the various sets of user interface diagrams.

[0174] An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detecting a lift-off of the contact from 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.

[0175] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed by a respective contact (or contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold followed by a decrease in intensity of the respective contact below the press input intensity threshold, where the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input intensity threshold (e.g., an "upstroke" of the respective press input).

[0176] 5E-5H show the intensity threshold of the light press in FIG. 5E (e.g., “IT L ") to the intensity threshold of the deep press in Figure 5H (e.g., "IT D5 illustrates detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 to an intensity above a deep press intensity threshold (e.g., "IT 1"). The gesture performed by contact 562 is detected on touch-sensitive surface 560, and cursor 576 is displayed over application icon 572B corresponding to app2 on display user interface 570, which includes application icons 572A-572D displayed within predetermined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device detects when the intensity of contact 562 exceeds a deep press intensity threshold (e.g., "IT D Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, a deep press intensity threshold (e.g., “IT D "), reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents are displayed to app2 for contact 562, as shown in FIGS. 5F-5H. In some embodiments, this intensity, which is compared to one or more intensity thresholds, is a characteristic intensity of the contact. Note that the intensity diagrams for contact 562 are not part of the displayed user interface, but are included in FIGS. 5E-5H as an aid to the reader.

[0177] In some embodiments, the display of representations 578A-578C includes an animation. For example, as shown in FIG. 5F, representation 578A is first displayed adjacent to application icon 572B. As the animation progresses, as shown in FIG. 5G, representation 578A moves upward and representation 578B is displayed adjacent to application icon 572B. Then, as shown in FIG. 5H, representation 578A moves upward and representation 578B moves upward toward representation 578A and representation 578C is displayed adjacent to application icon 572B. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. 5F-5G, as the intensity of contact 562 approaches a deep press intensity threshold (e.g., "ITD Representations 578A-578C appear and move upward as the intensity increases toward "intensity." In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using electronic devices similar or identical to device 100, 300, or 500.

[0178] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of each contact above the pressure input intensity threshold, followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., an "upstroke" of each pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0179] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or a gesture including a press input, are optionally triggered in response to detecting any of an increase in the intensity of a contact above the press input intensity threshold, an increase in the intensity of a contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of a contact below the press input intensity threshold, and / or a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0180] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., device 100, 300, and / or 500) and is ready to run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0181] As used herein, the terms "open application" or "running application" refer to a software application that has retained 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 one of the following types of applications: ● the active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and - Suspended or hibernated applications that are not running but have state information stored in memory (volatile and non-volatile respectively) and that can be used to resume execution of the application.

[0182] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application is taken off the display, the first application becomes a background application.

[0183] Attention is now directed to embodiments of user interfaces (“UI”) and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0184] Figures 6A-6Z illustrate example user interfaces for viewing health data, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the processes in Figures 7A-7B, 8A-8B, 9A-9B, 10A-10B, and 11A-11C.

[0185] 6A illustrates a first electronic device 600 (e.g., a phone) displaying a lock user interface 604 via a touch-sensitive display device 602 at a first time (e.g., 9:45). In some implementations, the first electronic device 600 includes one or more features of devices 100, 300, or 500.

[0186] In some implementations, the locked user interface 604 relates to a user interface that is displayed when the first electronic device transitions out of an inactive mode. As shown in FIG. 6A, the locked user interface 604 includes multiple notifications (e.g., notification 604a and notification 604b) issued by a process running on the first electronic device 600 (e.g., displayed by the first electronic device 600).

[0187] In some embodiments, notification 604a was issued by an activity process corresponding to an activity application (as indicated by icon 604aa). In some embodiments, a user interface element corresponding to an activity application includes icon 604aa (or some variant of icon 604aa, such as a smaller or larger version of icon 604aa). As shown in FIG. 6A, notification 604a includes (1) the time that notification 604a was issued (e.g., time 604ad indicating "now", referring to 9:45), and (2) a description (e.g., 604ac) of why notification 604a was issued.

[0188] In some examples, notification 604b was issued by a clinical health record (CHR) process corresponding to a CHR application (as indicated by icon 604ba). In some examples, a user interface element corresponding to a CHR application includes icon 604ba (or some variant of icon 604ba, such as a smaller or larger version of icon 604ba). As shown in FIG. 6A, notification 604b includes (1) the time that notification 604b was issued (e.g., time 604bd indicating "8:00 AM"), and (2) a description (e.g., 604bc) of why notification 604b was issued.

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

[0190] In some embodiments, the notification 610 is issued (e.g., displayed by the second electronic device 606) by a hearing process corresponding to a hearing application (as indicated by icon 610a) running on the second electronic device 606. In some embodiments, the user interface element corresponding to the hearing application includes the icon 610a (or some variant of the icon 610a, such as a smaller or larger version of the icon 610a). As shown in FIG. 6B, the notification 610 includes a description (e.g., 610b) of why the notification 610 was issued.

[0191] 6C shows the first electronic device 600 displaying a home user interface 612 via the touch-sensitive display device 602 at a third time after the second time. The home user interface 612 includes a plurality of icons, each icon corresponding to a different application. For example, the home user interface 612 includes a health icon 612a for initiating a health application and / or displaying a user interface of the health application.

[0192] 6C illustrates the first electronic device 600 receiving a user input 613 corresponding to a health icon 612a. In some implementations, the user input 613 is received via the 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 implementations, other forms of input, such as a click via a mouse, may be used. In some implementations, the user input 613 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a display of a user interface for a health application, as shown in FIG. 6DA.

[0193] 6DA-6DD illustrate first electronic device 600 displaying summary user interface 614 via touch-sensitive display device 602 at a fourth time after the third time. In some implementations, summary user interface 614 is a user interface of a health application. As shown in FIGS. 6DA-6DD, summary user interface 614 includes multiple regions including different affordances, including a notification region (e.g., a notification region including first notification affordance 616, second notification affordance 618, and third notification affordance 620), a logging region (e.g., a logging region including logging affordance 622), a favorites region (e.g., a first favorites affordance 626a, a second favorites affordance 626b, a third favorites affordance 626c, a fourth favorites affordance 626d, a fifth favorites affordance 626e, a fifth favorites affordance 626f, a fifth favorites affordance 626g, a fifth favorites affordance 626h, a fifth favorites affordance 626i, a fifth favorites affordance 626j, a fifth favorites affordance 626j, a fifth favorites affordance 626k ... a favorites area including a first highlight affordance 626e, a sixth favorite affordance 626f and showing all health data affordances 628), a highlights area (e.g., a highlight area including a first highlight affordance 630, a second highlight affordance 632 and showing all highlight affordances 634), a health records area (e.g., a health records area including a first health record affordance 636, a second health record affordance 638 and showing all records affordances 640), an education area, more information from the health area, and an apps area.

[0194] In some examples, the notification area includes affordances for health-related notifications issued / displayed by a device associated with an account logged into the health application. For example, the health-related notifications can be from the first electronic device 600 (e.g., notification 604a and notification 604b as shown in FIG. 6A) or another electronic device (e.g., second electronic device 606) linked (e.g., both logged into a single account or pairing such as performed by a smartphone and a corresponding smartwatch) to either the first electronic device 600 or the account (e.g., notification 610 as shown in FIG. 6B). In such examples, the notification area is a place to display information associated with the health-related notification in one place that can be viewed after the health-related notification is initially displayed.

[0195] As described above, the notification area includes a first notification affordance 616, a second notification affordance 618, and a third notification affordance 620. In some implementations, the first notification affordance 616 corresponds to (e.g., includes information on) the notification 610. In some implementations, the second notification affordance 618 corresponds to (e.g., includes information on) the notification 604a. In some implementations, the third notification affordance 620 corresponds to (e.g., includes information on) the notification 604b. As shown in FIG. 6DA, the notification affordances in the notification area are ordered by the date the corresponding notification was first issued (e.g., the most recent notification is first, the next most recent notification is next, etc.).

[0196] In some examples, the notification affordances are removed from the notification area after a certain amount of time has elapsed. In some examples, the certain amount of time varies based on the amount of user interaction associated with the respective notification affordance or data related to the affordance. For example, a first notification affordance is removed more quickly than a second notification affordance when the first notification affordance (or a notification corresponding to the first notification affordance) is interacted with by the user and the second notification affordance is not interacted with by the user. In another example, the first notification affordance is removed more quickly than the second notification affordance when the first notification affordance (or a notification corresponding to the first notification affordance) is displayed for a longer period of time than the second notification affordance (or a notification corresponding to the second notification affordance). In another example, the first notification affordance is removed more quickly than the second notification affordance if the first notification affordance (or the notification corresponding to the first notification affordance) is associated with a type of health data that is viewed (or interacted with) by the user more than a type of health data associated with the second notification affordance (or the notification corresponding to the second notification affordance). In another example, the first notification affordance is removed more quickly than the second notification affordance if the first notification affordance (or the notification corresponding to the first notification affordance) has more information (e.g., more detailed information) or more important information (e.g., as defined by a health application) than the second notification affordance (or the notification corresponding to the second notification affordance). In another example, the first notification affordance is removed more quickly than the second notification affordance if data corresponding to the first notification affordance is viewed on another device (e.g., device 608) (e.g., even if the first notification affordance is not interacted with on device 600). Such removal criteria are further described with respect to Figures 6F-6H.

[0197] The first notification affordance 616 includes an icon 616a indicating that a notification (e.g., notification 610) corresponding to the first notification affordance 616 has been issued by an application (e.g., an auditory application) represented by the icon 616a. The first notification affordance 616 includes a header that is visually distinguishable from the remainder of the first notification affordance 616, the header including a title 616b (indicating which first notification affordance 616 is relevant) and a time 616c (indicating the time when the notification corresponding to the first notification affordance 616 was originally issued). In one embodiment, the header is visually distinguished from the remainder of the first notification affordance 616 by being a particular pattern or color corresponding to an auditory application. In some embodiments, user interface elements associated with an auditory application include elements that are a particular pattern or color. As shown in FIG. 6DA, the first notification affordance 616 includes content 616d that is (in some embodiments) at least a portion of the content included in the notification corresponding to the first notification affordance 616.

[0198] The second notification affordance 618 includes an icon 618a indicating that a notification (e.g., notification 604a) corresponding to the second notification affordance 618 has been issued by an application (e.g., an activity application) represented by the icon 618a. The second notification affordance 618 includes a header that is visually distinct from the remainder of the second notification affordance 618 (and visually distinct from the headers of the first notification affordance 616 and the third notification affordance 620), and the header includes a title 618b (indicating which second notification affordance 618 is relevant) and a time 618c (indicating the time when the notification corresponding to the second notification affordance 618 was originally issued). In one embodiment, the header is visually distinguished from other elements by being a particular pattern or color corresponding to the activity application. In some embodiments, user interface elements associated with the activity application include elements that are a particular pattern or color. As shown in FIG. 6DA, the second notification affordance 618 includes content 618d that is at least a portion of the content included in the notification corresponding to the second notification affordance 618 (in some implementations).

[0199] The third notification affordance 620 includes an icon 620a indicating that a notification (e.g., notification 604b) corresponding to the third notification affordance 620 has been issued by an application (e.g., a CHR application) represented by the icon 620a. The third notification affordance 620 includes a header that is visually distinct from the remainder of the third notification affordance 620 (and visually distinct from the headers of the first notification affordance 616 and the second notification affordance 618), and the header includes a title 620b (indicating which third notification affordance 620 is relevant) and a time 620c (indicating the time when the notification corresponding to the third notification affordance 620 was originally issued). In one embodiment, the header is visually distinguished from other elements by being a particular pattern or color corresponding to the CHR application. In some embodiments, the user interface elements associated with the CHR application include elements that are a particular pattern or color. 6DA, the third notification affordance 620 includes an icon 620d and (in some embodiments) content 620e that is at least a portion of the content included in the notification corresponding to the third notification affordance 620. In some embodiments, the icon 620d corresponds to the clinical organization that generated the notification associated with the third notification affordance 620. In such an example, the icon 620d is different from the icon 620a.

[0200] In some examples, selection of the notification affordance causes a user interface of a health application to be displayed, where the user interface is associated with the corresponding application. For example, selection of the first notification affordance 616 causes a user interface of a health application to be displayed, where the user interface includes information from a hearing application (sometimes referred to as the hearing data room, as shown in FIG. 6E and described further below).

[0201] In some embodiments, the logging area includes an affordance for recording data. For example, the logging affordance 622 is associated with recording a cycle. The logging affordance 622 includes an icon 622a that represents a logging application (e.g., a cycle tracking application) that corresponds to the logging affordance 622. The logging affordance 622 also includes content 622b that describes the logging affordance 622 and indicates that the user has recorded information associated with the logging application. The logging affordance 622 also includes a graphic 622c that indicates whether the logging criteria have been met (e.g., when the logging criteria are not met, the graphic 622c is a plus sign indicating that the user has not recorded the minimum number of times, and when the logging criteria are met, the graphic 622c is a check mark indicating that the user has recorded the minimum number of times). In some embodiments, the logging affordance 622, when selected, causes a user interface to be displayed that allows the user to record a cycle. In other embodiments, the act of selecting the logging affordance 622 causes a cycle to be recorded.

[0202] In some embodiments, a color or pattern associated with a portion of the logging affordance 622 (e.g., the font color of the words "Cycle Tracking") is a particular color or pattern that corresponds to the logging application. The particular color or pattern is used for at least a portion of the user elements displayed within the health application that corresponds to the logging application in some embodiments. In some embodiments, the particular color or pattern is visually distinct from the color / pattern used in other applications (e.g., an activity application, a hearing application, a CHR application, or other logging applications).

[0203] In some examples, the favorites area includes affordances for health-related data that the user has indicated as one of his or her favorites (as shown in FIG. 6I and described below). In some examples, before the user has indicated a favorite, the favorites area includes one or more default affordances that correspond to health-related data that the system has determined the user to like (e.g., based on devices owned by the user, user interactions, default favorites, or any combination thereof).

[0204] As described above, the favorites area includes a first favorites affordance 626a, a second favorites affordance 626b, a third favorites affordance 626c, a fourth favorites affordance 626d, a fifth favorites affordance 626e, and a sixth favorites affordance 626f to show all health data affordances 628. The first favorites affordance 626a, the second favorites affordance 626b, and the third favorites affordance 626c correspond to health data from the activity application, for example, as indicated by icon 626aa.

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

[0206] As shown in FIG. 6DA, a first favorite affordance 626a includes a timestamp of the last hour of health data 626ac (e.g., mobility, exercise, and standing indicators).

[0207] As shown in FIG. 6DB, the fourth favorite affordance 626d includes icon 626da, which is a smaller version of icon 622a shown in FIG. 6DA. Such correspondence indicates that, in some embodiments, different user interface elements associated with the same application include the same icon to represent the application. Icon 626ea and icon 626fa are further examples of icons that correspond to different applications. Additionally, in some embodiments, title 626db is colored similarly to "Cycle Tracking" in content 622b to further indicate that both relate to the same application.

[0208] In some implementations, the all health data affordance 628 causes a user interface to be displayed that includes a representation of all health data corresponding to the account associated with the health application. Examples of such user interfaces are shown in Figures 12AA-AB.

[0209] In some examples, the highlighting region includes a graphical representation of the health data over a time period identified by the health application. For example, a particular graphical representation is displayed when the highlighting criteria are met and is not displayed when the highlighting criteria are not met. In some examples, the highlighting criteria are based on differences between the health data over the time period, the amount of time the user spends looking at a particular graphic, the user's interaction with a particular graphic or element of the interface 614, or any combination thereof.

[0210] 6DB illustrates an electronic device displaying a first highlight affordance 630 within a highlight region of a summary user interface 614 via a touch-sensitive display device 602. The first highlight affordance 630 includes an icon 630a indicating that the first highlight affordance 630 is primarily associated with a heart rate application (in some examples, the first highlight affordance 630 is secondarily associated with a second application (e.g., a workout application) such that the first highlight affordance 630 is based on data from the second application). In some examples, a portion of the first highlight affordance 630 is visually distinct to identify that the first highlight affordance 630 is primarily associated with a heart rate application (e.g., in some examples, the font color of the title 630b is a particular color that corresponds to a heart rate application). The first highlighting affordance 630 also includes a description 630c to indicate the information indicated by the first highlighting affordance 630 (e.g., the range of values ​​reached during training, etc.).

[0211] 6DB, the first highlight affordance 630 includes a graph 630d having a representation of the heart rate during a workout. The graph 630d includes a minimum indication 630e indicating a minimum value of the heart rate during the workout and a maximum indication 630f indicating a maximum value of the heart rate during the workout. Such indications are determined by comparing the heart rate at different times during a period corresponding to the workout to identify the minimum and maximum.

[0212] 6DC illustrates an electronic device displaying a second highlight affordance 632 within a highlight region of a summary user interface 614 via a touch-sensitive display device 602. The second highlight affordance 632 includes an icon 630a indicating that the second highlight affordance 632 is related to an ambient audio application. In some embodiments, a portion of the second highlight affordance 632 is visually distinct to identify that the second highlight affordance 632 is related to an ambient audio application (e.g., in some embodiments, the font color of the title 632b is a particular color corresponding to an ambient audio application). The second highlight affordance 632 also includes a description 632c to indicate the information indicated by the second highlight affordance 632 (e.g., how today's average ambient audio level is 4 dB higher than yesterday's average, etc.).

[0213] As shown in FIG. 6DC, the second highlighting affordance 632 includes a graph having a today's average representation (e.g., 632d) and a yesterday's average representation (e.g., 632e). As shown in FIG. 6DC, each of the today's average representation and yesterday's average representation includes a graphical representation of the average and a textual representation of the average. In some examples, the graph represents the amount of a single health data metric compared over time periods of the same length.

[0214] As described above, the highlight region also includes showing all highlight affordance 634. In some implementations, selection of all highlight affordance 634 causes a user interface corresponding to a health application to be displayed, such as an all highlight user interface as shown in FIGS.

[0215] In some examples, the health record area includes affordances (e.g., a first health record affordance 636 and a second health record affordance 638) corresponding to each clinical entity that has submitted health record data for an account associated with the health application. For example, the first health record affordance 636 may indicate that it corresponds to XYZ Medical Center in Palo Alto, California (see 636d). In another example, the second health record affordance 638 may indicate that it corresponds to ABC Urgent Care in San Jose, California (see 638d).

[0216] In some examples, each affordance in the health record region includes a title (e.g., title 636a and title 638a) indicating that the affordance corresponds to a health record. As shown in FIG. 6DC, each affordance in the health record region also includes an indication of when the most recent health record was received from the corresponding clinical institution (e.g., first health record affordance 636 includes a time indication 636b of 8:00 AM, and second health record affordance 638 includes a time indication 638b of 6:00 AM). In some examples, the affordances in the health record region are ordered based on when the most recent health record was received from the corresponding clinical institution (e.g., first health record affordance 636 is above second health record affordance 638 based on the most recent health record corresponding to first health record affordance 636 being received after the most recent health record corresponding to second health record affordance 638). In other examples, the affordances in the health record area are ordered based on when the health record update was first issued / generated for the account (e.g., the first health record affordance 636 is above the second health record affordance 638 based on the first health record corresponding to the first health record affordance 636 being generated before the second health record corresponding to the second health record affordance 638). In other examples, the affordances in the health record area are ordered based on a user-defined order, such as specifying a primary and secondary institution (e.g., the primary institution precedes the secondary institution). In some examples, only the primary institution is represented in the health record area, and the secondary institutions can be navigated using the all health records affordance 640. In some examples, selection of the all health records affordance 640 causes a user interface of the health application to be displayed, where the user interface includes all health records received for the account associated with the health application (as shown in FIGS. 6OA-6OB).

[0217] In some examples, each affordance in the health records area includes an indication of which records have been received from the corresponding institution. For example, the first health records affordance 636 includes an indication 636e indicating that health records corresponding to medications, lab results, and other records were received from XYZ Medical Center. In some examples, the indications 636e are ordered based on when the medical records were received (e.g., medications come before lab results because the health records with health data corresponding to medications were received more recently than the health records with health data corresponding to lab results). In another example, the second health records affordance 638 includes an indication 638e indicating that health records corresponding to medications were received from ABC Urgent Care.

[0218] In some examples, the education domain includes an affordance that, when selected, causes a user interface to display educational content. In some examples, the more information from health domain includes an affordance that, when selected, causes a user interface to display a health application. In some examples, the apps domain includes affordances that correspond to different applications that are determined to be associated with an account for the health application.

[0219] As shown in FIG. 6DD, the summary user interface 614 includes a pair of affordances (e.g., summary affordance 642a and search affordance 642b) at the bottom of the summary user interface 614 to indicate the section of the health application to which the current user interface is related (e.g., a visually distinct affordance (e.g., bold) indicates which section). In some embodiments, selection of a section of the health application to which the current user interface is not related (e.g., search affordance 642b in FIG. 6DD) causes a user interface corresponding to the selected section to be displayed (e.g., when search affordance 642b is selected, a user interface corresponding to the search section is displayed, as shown in FIGS. 6TA-6TB). In some embodiments, selection of an affordance corresponding to a section related to the current user interface causes a home interface for the selected section to be displayed (e.g., summary user interface 614 as shown in FIG. 6DA and search user interface 684 as shown in FIGS. 6TA-6TB).

[0220] 6DA illustrates a first electronic device 600 receiving a user input 615 that corresponds to a first notification affordance 616. In some examples, the 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 affordance 616. In other examples, other forms of selection, such as clicking using a mouse, may be used. In some examples, the user input 615 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a display of an environmental audio data room user interface 644 of a wellness application, as shown in FIG. 6E.

[0221] 6E illustrates the first electronic device 600 displaying an environmental audio data room user interface 644 via the touch-sensitive display device 602 at a fifth time after the fourth time. In some embodiments, the environmental audio data room user interface 644 is a user interface of a health application having information from an environmental audio application. As shown in FIG. 6E, the environmental audio data room user interface 644 includes a graph with data showing noise levels detected by the device over a week. In some embodiments, the data is stored in a location associated with the environmental audio application and is viewable within the user interface of the environmental audio application.

[0222] The ambient audio data room user interface 644 further includes time scale affordances at the top that indicate different time scales (e.g., "D" for days, "W" for weeks, "M" for months, and "Y" for years). As shown in FIG. 6E, the time scale affordance indicating weeks is selected, causing the graph to show the detected noise levels over a week. In some embodiments, selection of a different time scale affordance changes the graph to show the detected noise levels over the entire selected time scale.

[0223] As shown in FIG. 6E, the environmental audio data room user interface 644 includes a number of affordances at the bottom text that indicate the information shown by the graph. For example, there is a first affordance that indicates an average over the entire week, a second affordance that indicates a daily average over the entire week, and a third affordance that indicates a range over the entire week and the number of noise notifications issued by the environmental audio application in the week. In some embodiments, selection of one of the affordances causes the graph to change to highlight data in the graph that corresponds to the selected affordance. For example, selection of the average affordance can cause a line to be inserted into the graph showing the average. In another embodiment, selection of the daily average affordance can cause a point to be inserted into each bar for each day in the graph to show the average for each day. In another embodiment, selection of the range affordance can cause a portion of the graph to be highlighted, where the minimum and maximum of the range occurred over the entire week. In another embodiment, selection of the noise notification affordance can cause a portion of the graph to be highlighted and a noise notification to be issued.

[0224] 6F shows the first electronic device 600 displaying summary user interface 614 via the touch-sensitive display device 602 at a sixth time after the fifth time. In some examples, summary user interface 614 is displayed in response to a user input corresponding to selection of the back button at the top left of ambient audio data room user interface 644 (shown in FIG. 6E without user input).

[0225] The summary user interface 614 as shown in Figure 6F is scrolled down to the summary user interface 614 as shown in Figure 6DA (e.g., the text "Summary" at the top left and the account icon at the top right are no longer displayed). Figure 6F shows that the first notification affordance 616 is still displayed in the summary user interface 614 after it is interacted with (e.g., selected as shown in Figure 6DA). Figure 6F also shows that the second notification affordance 618 and the third notification affordance 620 are also still displayed within the summary user interface 614.

[0226] 6G shows the first electronic device 600 displaying the summary user interface 614 via the touch-sensitive display device 602 at a seventh time after the sixth time. In some embodiments, the summary user interface 614 is displayed in response to a user input corresponding to a redisplay of the summary user interface 614.

[0227] 6G shows that the first notification affordance 616 is no longer displayed in the summary user interface 614, even though the second notification affordance 618 and the third notification affordance 620 were received before the first notification affordance 616. Such indicates that in some implementations, some interacted notification affordances are removed in a shorter time than non-interacted notification affordances. FIG. 6G shows that the second notification affordance 618 and the third notification affordance 620 are still displayed in the summary user interface 614.

[0228] 6H shows first electronic device 600 displaying summary user interface 614 via touch-sensitive display device 602 at an eighth time after the seventh time. In some implementations, summary user interface 614 is re-displayed on touch-sensitive display device 602 at the seventh time (as shown in FIG. 6G).

[0229] 6H illustrates that the third notification affordance 620 is no longer displayed in the summary user interface 614 due, at least in part, to (1) the notification corresponding to the third notification affordance 620 that was issued before the notification corresponding to the second notification affordance 618, and (2) none of the notification corresponding to the third notification affordance 620, the third notification affordance 620, the notification corresponding to the second notification affordance 618, or the second notification affordance 618 being interacted with by the user. As such, notification affordances that are not interacted with are removed based on chronological order when issued (e.g., older notification affordances are removed first). FIG. 6H illustrates that the second notification affordance 618 is still displayed within the summary user interface 614.

[0230] 6H illustrates a first electronic device 600 receiving a user input 625 that corresponds to an edit affordance 624. In some examples, the user input 625 is received via the touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the edit affordance 624. In other examples, other forms of selection, such as clicking using a mouse, may be used. In some examples, the user input 625 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a display of an edit user interface 646, as shown in FIG. 6I.

[0231] 6I shows the first electronic device 600 displaying an editing user interface 646 via the touch-sensitive display device 602 at a ninth time after the eighth time. In some implementations, the editing user interface 646 is a user interface of a health application that allows a user to add and / or remove favorites displayed in a favorites area of ​​the summary user interface 614.

[0232] As shown in FIGURE 6I, the edit user interface 646 includes an existing data affordance 646a and an all affordance 646b for switching between views of the edit user interface 646. For example, a user input corresponding to a selection of the existing data affordance 646a causes the edit user interface 646 to display the existing data view, as shown in FIGURE 6I and described below. Similarly, a user input corresponding to a selection of the all affordance 646b causes the edit user interface 646 to display an all data view (not shown), including all possible health data types, for adding and / or removing from the favorites area.

[0233] In a view corresponding to existing data affordance 646a (as shown in FIG. 6I ), edit user interface 646 includes representations of health data types for which the account has at least some health data (e.g., the representations of the health data types are displayed when the health application has access to health data of the health data type for the account (e.g., there is at least some health data of the health data type stored in the account)). In such examples, edit user interface 646 in a view corresponding to existing data affordance 646a does not include any representations for health data types for which the account does not have health data (e.g., the representations of the health data types are not displayed when the health application does not have access to health data of the health data type for the account (e.g., there is no health data of the health data type stored in the account)).

[0234] In either view, selection of a representation of a health data type allows a user to view stored data related to the health data type from the summary user interface 614 by causing a favorites affordance for the health data type to be added to a favorites area of ​​the summary user interface 614. As shown in FIG. 6I, a representation of a health data type is indicated as being selected by including an indication that is visually distinguishable from other indications in the representation. For example, representation 646c includes an indication that the favorites affordance for the health data type corresponding to representation 646c is displayed in the favorites area of ​​the summary user interface 614. In another example, representation 646d includes an indication that the favorites affordance for the health data type corresponding to representation 646c is not displayed in the favorites area of ​​the summary user interface 614. As shown in FIG. 6I, a group of representations of health data types are displayed via the edit user interface 646. For example, edit user interface 646 includes a group of representations corresponding to activity, physical measurements, and cardiac, where each representation in the group of representations is related.

[0235] Figure 6J illustrates the first electronic device 600 displaying summary user interface 614 via the touch-sensitive display device 602 at a tenth time after the ninth time. In some implementations, the summary user interface 614 is displayed in response to a user input corresponding to a selection of a execute button at the top right of the edit user interface 646 (shown in Figure 6I without user input). The summary user interface 614 as shown in Figure 6J is scrolled down relative to the summary user interface 614 (e.g., the logging affordance 622 is no longer displayed in Figure 6J), as shown in Figure 6H.

[0236] 6J illustrates the first electronic device 600 receiving a user input 627 that corresponds to the second favorite affordance 626b. In some examples, the user input 627 is received via the touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the second favorite affordance 626b. In other examples, other forms of selection, such as clicking using a mouse, may be used. In some examples, the user input 627 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a display of a step count data room user interface 648, as shown in FIGS. 6KA-6KB.

[0237] 6KA-6KB show first electronic device 600 displaying step data lab user interface 648 via touch-sensitive display device 602 at an eleventh time after the tenth time. In some implementations, step data lab user interface 648 is displayed in response to a user input corresponding to selection of second favorite affordance 626b of summary user interface 614, as shown in FIG.

[0238] In some examples, the step data room user interface 648 is a user interface of a health application with information from an activity application. As shown in FIG. 6KA, the step data room user interface 648 includes a graph 648a with a representation of health data associated with the number of steps for a day. In some examples, the health data is stored in a location associated with the activity application and is viewable within the user interface of the activity application.

[0239] The step count data room user interface 648 further includes time scale affordances at the top that indicate different time scales (e.g., "D" for day, "W" for week, "M" for month, and "Y" for year). As shown in FIG. 6KA, the time scale affordance for day is selected, causing the graph to show the number of steps detected over the course of a day. In some embodiments, selection of a different time scale affordance changes the graph to show the number of steps detected over the entire selected time scale.

[0240] The step count data room user interface 648 includes a highlight section that includes highlights associated with the steps. As shown in FIG. 6KA, the step count data room user interface 648 includes a single highlight (e.g., 648b) that indicates how the step count has increased over a period of time. It should be appreciated that other highlights may be included in the highlight section. In some embodiments, identifying a highlight for display in the step count data room user interface 648 includes similar determinations as described above for the highlight area. The step count data room user interface 648 further includes an explanation 648c of what the step count means and an additional affordance 468 for adding the step count to a favorites area in the summary user interface 614.

[0241] Referring to FIG. 6KB, the step count data room user interface 648 includes (1) a step count apps section 648e with links to suggested apps related to steps (e.g., links to an app store or links to applications installed on the first electronic device 600), (2) an options section 648f with various options related to steps, and (3) an education section 648g with affordances that, when selected, cause the user interface to display content related to steps.

[0242] FIG 6L illustrates the first electronic device 600 displaying summary user interface 614 via touch-sensitive display device 602 at a twelfth time after the eleventh time. In some implementations, summary user interface 614 is displayed in response to a user input corresponding to a back selection for the summary affordance at the top left of step count data room user interface 648 (shown in FIG 6KA without user input). Summary user interface 614 as shown in FIG 6L is scrolled down relative to summary user interface 614 as shown in FIG 6J (e.g., the favorites area is no longer displayed and the highlighted area is displayed in FIG 6L).

[0243] 6L illustrates first electronic device 600 receiving corresponding user input 635 to indicate all highlight affordances 634. In some examples, user input 635 is received via touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) that indicates all highlight affordances 634. In other examples, other forms of selection, such as clicking using a mouse, may be used. In some examples, user input 635 causes a different user interface to be displayed via touch-sensitive display device 602, such as a display of all highlight user interface 650, as shown in FIGS. 6MA-6MD.

[0244] 6MA-6MD show first electronic device 600 displaying all highlighting user interface 650 via touch-sensitive display device 602 at a thirteenth time after the twelfth time. In some implementations, all highlighting user interface 650 is displayed in response to a user input corresponding to a selection of all highlighting affordance 634 in summary user interface 614, as shown in FIG.

[0245] In some implementations, the all highlights user interface 650 is a user interface of the health application having a list of highlights currently identified by the health application for the account (e.g., the identifying is based on the determination described above with respect to the highlight area, such that not all generated highlights are included in the all highlights user interface 650 (e.g., only highlights that meet the display criteria are displayed in the all highlights user interface 650)). FIG. 6MA shows the first electronic device 600 displaying the first highlight affordance 630 and the second highlight affordance 632, also displayed within the highlight area of ​​the summary user interface 614 described above.

[0246] FIG. 6MB illustrates a first electronic device 600 displaying a third highlight affordance 652 via a touch-sensitive display device 602. The third highlight affordance 652 includes an icon 652a indicating that the third highlight affordance 652 is related to a sleep application. In some embodiments, a portion of the third highlight affordance 652 is visually distinct to identify that the third highlight affordance 652 is related to a sleep application (e.g., in some embodiments, the font color of the title 652b is a particular color corresponding to a sleep application). The second highlight affordance 632 also includes a description 652c to indicate information indicated by the third highlight affordance 652 (e.g., how the user slept an average of 7 hours and 55 minutes this week, etc.).

[0247] As shown in FIG. 6MB, a third highlight affordance 652 includes a graph with a representation of how much the user slept each day of the week. The graph also includes an average line 652e that visually indicates the weekly average. In some implementations, the graph represents an average over a period (e.g., week) divided into sub-periods (e.g., days).

[0248] FIG. 6MB illustrates a first electronic device 600 displaying a fourth highlight affordance 654 via a touch-sensitive display device 602. The fourth highlight affordance 654 includes an icon 654a indicating that the fourth highlight affordance 654 is primarily associated with a water application (in some embodiments, the fourth highlight affordance 654 is secondarily associated with a calendar application). In some embodiments, a portion of the fourth highlight affordance 654 is visually distinct to identify that the fourth highlight affordance 654 is associated with a water application (e.g., in some embodiments, the font color of the title 654b is a particular color that corresponds to a water application). The fourth highlight affordance 654 also includes instructions 652c to indicate information indicated by the fourth highlight affordance 654 (e.g., how the user logged water for 21 days in the last four weeks, etc.).

[0249] As shown in FIG. 6MB, the fourth highlight affordance 654 includes a calendar 654d having a representation of each day with an indication of whether the user logged water on each day. As shown in FIG. 6MB, representation 654f is visually distinct from several other representations (e.g., representation 654e indicating that the user logged water on the day corresponding to representation 654f and did not log water on the day corresponding to representation 654e). In some implementations, calendar 654d represents the frequency of a single health data indicator compared over a period of the same length.

[0250] FIG. 6MC illustrates a first electronic device 600 displaying a fifth highlight affordance 656 via a touch-sensitive display device 602. The fifth highlight affordance 656 includes an icon 656a indicating that the fifth highlight affordance 656 is primarily associated with a navigation application (in some embodiments, the fifth highlight affordance 656 is secondarily associated with a workout application). In some embodiments, a portion of the fifth highlight affordance 656 is visually distinct to identify that the fifth highlight affordance 656 is primarily associated with a navigation application (e.g., in some embodiments, the font color of the title 656b is a particular color that corresponds to a navigation application). The fifth highlight affordance 656 also includes a description 656c to indicate information indicated by the fifth highlight affordance 656 (e.g., the user logged a 3.1 mile run at an average pace of 8:51).

[0251] 6MC, the fifth highlight affordance 656 includes a map 656d with a representation within the map 656d of a running route. The fifth highlight affordance 656 also includes textual information about the run, including a distance measurement 656e (in addition to the distance included in the description 656c, but longer), a duration 656f, and calories 656g.

[0252] 6MC illustrates a first electronic device 600 displaying a sixth highlight affordance 658 via a touch-sensitive display device 602. The sixth highlight affordance 658 includes an icon 658a indicating that the sixth highlight affordance 658 is associated with a workout application. In some examples, a portion of the sixth highlight affordance 658 is visually distinct to identify that the sixth highlight affordance 658 is associated with a workout application (e.g., in some examples, the font color of the title 658b is a particular color corresponding to a workout application). The sixth highlight affordance 658 also includes a description 658c to indicate information indicated by the sixth highlight affordance 658 (e.g., the user burned a total of 6,500 calories today, etc.).

[0253] 6MC, the sixth highlight affordance 658 includes four different representations of different workouts logged for a day. Each workout includes an icon corresponding to the type of workout, an identification (e.g., name) of the type of workout, the length of time of the respective workout, and an icon corresponding to the number of calories burned during the respective workout. In some examples, the sixth highlight affordance 658 represents multiple workouts for a day within a single highlight with heart rate data for the day.

[0254] FIG. 6MD illustrates a first electronic device 600 displaying a seventh highlight affordance 660 via a touch-sensitive display device 602. The seventh highlight affordance 660 includes an icon 660a indicating that the seventh highlight affordance 660 is primarily associated with a vitals application. In some examples, a portion of the seventh highlight affordance 660 is visually distinct to identify that the seventh highlight affordance 660 is associated with a vitals application (e.g., in some examples, the font color of the title 660b is a specific color corresponding to the vitals application). Note that the seventh highlight affordance 660 does not include a description indicating the information indicated by the seventh highlight affordance 660 indicating that not all highlights have such a description. As illustrated in FIG. 6MD, the seventh highlight affordance 660 includes a graph 660c showing beats per minute for a user over time, showing how beats per minute are reduced from a high point to a low point.

[0255] 6MD illustrates a first electronic device 600 displaying an eighth highlight affordance 662 via a touch-sensitive display device 602. The eighth highlight affordance 662 includes an icon 662a indicating that the eighth highlight affordance 662 is associated with an activity application. In some examples, a portion of the eighth highlight affordance 662 is visually distinct to identify that the eighth highlight affordance 662 is associated with an activity application (e.g., in some examples, the font color of the title 662b is a particular color that corresponds to an activity application). The eighth highlight affordance 662 also includes a description 662c to indicate information indicated by the eighth highlight affordance 662 (e.g., the user has taken more steps today than is typically done for this time of day, etc.).

[0256] As shown in FIG. 6MD, the eighth highlight affordance 662 includes a graph 662d that compares an activity metric for a day (e.g., the current day) to a previous average value. For example, the graph 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 shows the user's steps as they progressed through the day up to the current time. The previous average line shows the user's steps as they progressed on average over the days prior to the current day. The first portion 662g represents the time up to the current time, and the second portion 662i represents the time after the current time. The graph 662d also includes a textual display of the steps for today and the steps for this time averaged over the days prior to the current day. In some implementations, the sixth highlight affordance 658 represents a momentary update of the information and an average over a period of time compared to today.

[0257] Figure 6N illustrates first electronic device 600 displaying summary user interface 614 via touch-sensitive display device 602 at a fourteenth time after the thirteenth time. In some implementations, summary user interface 614 is displayed in response to a user input corresponding to selection of summary affordance 642a in all highlighting user interface 650 (shown in Figure 6MD without user input). Summary user interface 614 as shown in Figure 6N is scrolled down relative to summary user interface 614 (e.g., the highlighting region is no longer displayed and the health record region is displayed in Figure 6N) as shown in Figure 6L.

[0258] 6N illustrates first electronic device 600 receiving corresponding user input 641 to indicate all health records affordance 640. In some examples, user input 641 is received via touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) to indicate all health records affordance 640. In other examples, other forms of selection may be used, such as clicking using a mouse. In some examples, user input 641 causes a different user interface to be displayed via touch-sensitive display device 602, such as a display of all health data user interface 664, as shown in FIGS. 6OA-6OB.

[0259] 6OA-6OB show the first electronic device 600 displaying an all health data user interface 664 via the touch-sensitive display device 602 at a fifteenth time after the fourteenth time. In some examples, the all health data user interface 664 is displayed in response to a user input corresponding to a selection of the all health records affordance 640 that shows the summary user interface 614, as shown in FIG.

[0260] In some examples, all health data user interface 664 is a user interface of a health application having a list of health data received for an account. As shown in FIG. 6OA, all health data user interface 664 includes all data affordance 664a and health record affordance 664b for switching between views of all health data user interface 664. For example, a user input corresponding to a selection of all data affordance 664a causes all health data user interface 664 to display an all data view, as shown in FIG. 12AA. Similarly, a user input corresponding to a selection of health record affordance 664b causes all health data user interface 664 to display a health record view including all health records received for an account (as shown in FIGS. 6OA-6OB). In some examples, in response to a selection of all health records affordance 640, the health record view is displayed instead of the all data view. In such examples, in response to a selection of an all health data affordance (e.g., all health data affordance 628 as shown in FIG. 6DB), the all data view is displayed instead of the health record view.

[0261] In the health record view, the all health data user interface 664, in some embodiments, includes representations of health record types (e.g., representation 666 is for allergies, representation 666b is for clinical vitals, representation 666c is for conditions, representation 666d is for vaccinations, representation 666e is for lab results, representation 666f is for medications, and representation 666g is for treatments). In such embodiments, the representations of health record types are ordered alphabetically (e.g., allergies before treatments, before medications, before lab results, before vaccinations, before conditions, before clinical vitals).

[0262] In some examples, each representation in the health record view includes an icon corresponding to a health record type (e.g., icon 666aa corresponds to an allergy, icon 666ba corresponds to clinical vitals, icon 666ca corresponds to a condition, icon 666da corresponds to an vaccination, icon 666ea corresponds to a lab result, icon 666fa corresponds to a medication, and icon 666ga corresponds to a procedure). In some examples, a user interface of a health application that includes user interface elements corresponding to a health record type includes a version of the corresponding icon.

[0263] In some examples, each representation within a health record view includes a list of information corresponding to a respective health record type. For example, a representation 666a corresponding to allergies includes a list of items for which health records indicate that the user associated with the account is allergic (e.g., pollen, mold, avocado, and shellfish). In some examples, the list of information is ordered based on recency (e.g., items more recently identified for a health record type are ordered before (e.g., above) items more previously identified for the health record type). In some examples, the all health data user interface 664 within a health record view includes a representation of a health record type, even if no health records exist for that health record type.

[0264] As shown in Figure 6OB, all health data user interface 664 includes an external affordance 666h. Selection of the external affordance 666h causes a user interface of a health application to be displayed, the user interface including information from one or more external sources (e.g., sources external to first electronic device 600). As shown in Figure 6OB, all health data user interface 664 includes a non-readable data affordance 666i. Selection of the non-readable data affordance 666i causes a user interface of a health application to be displayed, the user interface including a representation of a health record that cannot be parsed by a process associated with the health application.

[0265] FIG 6OA illustrates a first electronic device 600 receiving a user input 667 that corresponds to representation 666e. In some embodiments, the user input 667 is received via the touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on representation 666e. In other embodiments, other forms of selection may be used, such as clicking using a mouse. In some embodiments, the user input 667 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a display of a lab results data lab user interface 668, as shown in FIGS. 6PA-6PB.

[0266] 6PA-6PB show the first electronic device 600 displaying a test results data lab user interface 668 via the touch-sensitive display device 602 at a sixteenth time after the fifteenth time. In some examples, the test results data lab user interface 668 is displayed in response to a user input corresponding to a selection of a representation 666e in the all health data user interface 664, as shown in FIG. 6OA. In other examples, the test results data lab user interface 668 is displayed in response to a user input corresponding to a notification representation in the summary user interface 614 indicating that a test result (e.g., no other health record types) has been updated. In other examples, the test results data lab user interface 668 is displayed in response to searching for test results using a search user interface 684 as shown in FIG. 6TB and selecting an affordance corresponding to the test results data lab user interface 668 in the search results.

[0267] 6PA, the lab results data room user interface 668 includes an icon 668a and a title 668b that corresponds to and indicates the health record type "lab results." In some embodiments, a user interface element that corresponds to the health record type "lab results" includes an icon similar to icon 668a.

[0268] As shown in FIGURE 6PA, the lab results data lab user interface 668 includes a last updated affordance 668c and an AZ affordance 668d for switching between views of the lab results data lab user interface 668. For example, a user input corresponding to a selection of the last updated affordance 668c causes the lab results data lab user interface 668 to display a first view, as shown in FIGURES 6PA-6PB. Similarly, a user input corresponding to a selection of the AZ affordance 668d causes the lab results data lab user interface 668 to display a second view, as shown in FIGURE 6Q.

[0269] As shown in FIGS. 6PA-6PB, the lab results data lab user interface 668 includes multiple regions (e.g., region 670 and region 672), each corresponding to a different date on which the health records in the region were generated (e.g., collected, taken, or otherwise created by a clinical institution). In some examples, the multiple regions are ordered by date, such that regions corresponding to more recent dates are before regions corresponding to later dates. For example, the lab results data lab user interface 668 includes region 670 (shown to correspond to March 29, 2019) (as shown in FIG. 6PA) that is higher (e.g., earlier) in the list than region 672 (shown to correspond to August 15, 2019) (as shown in FIG. 6PB).

[0270] In some embodiments, each region included in lab results data lab user interface 668 includes one or more representations of health records. For example, region 670 includes two representations of two separate health records, representation 670b and representation 670c. In another embodiment, region 672 includes three representations, representation 672b, representation 672c, and representation 672d.

[0271] In some examples, the representations in the area are included in sub-areas corresponding to clinical organizations associated with the health records. For example, representation 670b and representation 670c are included in a sub-area corresponding to XYZ Medical Center, indicating that the health records corresponding to representation 670b and representation 670c were received (e.g., generated) from XYZ Medical Center. In another example, representation 672b, representation 672c, and representation 672d are included in a sub-area corresponding to ABC Urgent Care, indicating that the health records corresponding to representation 672b, representation 672c, and representation 672d were received (e.g., generated) from ABC Urgent Care. Such indicates that the lab results data room user interface 668 can include representations from multiple clinical organizations.

[0272] In some examples, the representations of the health records in the lab results data lab user interface 668 include an icon indicating the corresponding health record type (as described above). In some examples, the representations of the health records in the lab results data lab user interface 668 include information corresponding to each health record. For example, the information in 670b includes the word "Collected," indicating that the corresponding health record was collected on the relevant date (e.g., March 29, 2019).

[0273] The information in representation 670b further includes a graph showing the corresponding health record. The graph in representation 670b includes multiple indications of a value (e.g., "125 MG / DL") contained in the corresponding health record and a range defined for the value (e.g., 0 to 200 with a minimum and maximum value). The multiple indications include textual indications (e.g., text) and graphical representations (e.g., dots in a visual representation of the range). In some examples, a value is considered to meet a particular criterion (e.g., a criterion related to whether a value is acceptable, such as a criterion set by a governing body) when the value is within the range. In some examples, the range is contained in the corresponding health record. In other examples, the range is known by the health application, such as provided by a remote source (e.g., a clinical organization).

[0274] FIG. 6PA illustrates representation 670c including a graph showing a corresponding health record. The graph in representation 670c includes multiple indications of a value (e.g., "6.3%") included in the corresponding health record, and a range defined for the value (e.g., 5.7 to 6.3 with minimum and maximum values). The multiple indications include textual indications (e.g., text) and graphical representations (e.g., dots within a visual representation of the range). In some examples, a value is considered to meet a particular criterion (e.g., a criterion related to whether a value is acceptable, such as a criterion set by a governing body) when the value is within the range. In some examples, the range is included in the corresponding health record. In other examples, the range is known by the health application, such as provided by a remote source (e.g., a clinical organization).

[0275] 6PB shows representation 672b 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 the value. In some examples, the information in representation 672b does not include a graph (and / or an indication of the range) because the health application cannot identify a range of values ​​(e.g., the corresponding health record does not include a range and / or the indication does not provide a range).

[0276] 6PB shows representation 672c including information from a corresponding health record. The information in representation 672c includes a single indication (e.g., a textual indication) of the value (e.g., "not") included in the corresponding health record. In some embodiments, the information in representation 672b does not include a graph (and / or an indication of a range) (e.g., binary values ​​are not graphed) because, in some embodiments, the value is less than the minimum number of possible values ​​for the corresponding health record (in some embodiments, the minimum number of possible values ​​is 3).

[0277] FIG. 6PB illustrates representation 672d including a graph showing the corresponding health record. The graph in representation 672d includes a plurality of indications of a value included in the corresponding health record (e.g., “4.5 trillion”) and a range defined for the value (e.g., 5.32 to 5.72 trillion with minimum and maximum values). The plurality of indications includes a textual indication (e.g., text) and a graphical representation (e.g., dots within a visual representation of the range). In some examples, a value is considered to meet a particular criterion (e.g., a criterion related to whether a value is acceptable, such as a criterion set by a governing body) when the value is within the range. In some examples, the range is included in the corresponding health record. In other examples, the range is known by the health application, such as provided by a remote source (e.g., a clinical organization). FIG. 6PB illustrates that while some representations may include a graph, other representations, even representations corresponding to the same health record type, do not include a graph. Such a result, in some examples, is due to a portion of the health record not including a range and / or being binary.

[0278] 6PA shows a first electronic device 600 receiving a user input 669 that corresponds to an AZ affordance 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 AZ affordance 668d. In other examples, other forms of selection can be used, such as clicking using a mouse. In some examples, the user input 669 causes a different view of the lab results data lab user interface 668 to be displayed via the touch-sensitive display device 602, such as the AZ view shown in FIG. 6Q.

[0279] 6Q illustrates the first electronic device 600 displaying an AZ view of the lab results data lab user interface 668 via the touch-sensitive display device 602 at a 17th time after the 16th time. In some examples, the AZ view is displayed in response to a user input corresponding to a selection of an AZ affordance 668d in the lab results data lab user interface 668, as shown in FIG.

[0280] As shown in Figure 6Q, the AZ view includes a last update affordance 668c and an AZ affordance 668d for switching between views of the lab results data lab user interface 668. For example, a user input corresponding to a selection of the last update affordance 668c causes the lab results data lab user interface 668 to display a first view, as shown in Figures 6PA-6PB. Similarly, a user input corresponding to a selection of the AZ affordance 668d causes the lab results data lab user interface 668 to display a second view, as shown in Figure 6Q.

[0281] As shown in FIG. 6Q, the AZ view includes a list of affordances for different test results, with each affordance corresponding to a different type of test result. In some examples, the list of affordances is ordered alphabetically by each affordance's corresponding type of test result (e.g., a cholesterol affordance (e.g., affordance 674a) precedes a creatine affordance (e.g., affordance 674b)). In some examples, each affordance in the list of affordances includes an indication of the number of health records associated with the corresponding type of test result. For example, "12" in affordance 674a indicates that the health system has received 12 health records corresponding to cholesterol.

[0282] FIGURE 6Q illustrates first electronic device 600 receiving user input 675 corresponding to affordance 674c. In some examples, user input 675 is received via touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on affordance 674c. In other examples, other forms of selection may be used, such as clicking using a mouse. In some examples, user input 675 causes a different user interface to be displayed via touch-sensitive display device 602, such as hemoglobin user interface 676 shown in FIGS. 6RA-6RB.

[0283] 6RA-6RB show the first electronic device 600 displaying a hemoglobin user interface 676 via the touch-sensitive display device 602 at an eighteenth time after the seventeenth time. In some examples, the hemoglobin user interface 676 is displayed in response to a user input corresponding to a selection of an affordance 674c in the lab results data lab user interface 668, as shown in FIG. 6Q. In some examples, the hemoglobin user interface 676 is displayed in response to a user input corresponding to a selection of an affordance 670c in the lab results data lab user interface 668, as shown in FIG. 6PA. In some examples, the hemoglobin user interface 676 is a user interface of a health application having health record-based information corresponding to hemoglobin A1C.

[0284] As shown in FIG. 6RA, the hemoglobin user interface 676 includes a graph with data showing values ​​obtained from health records corresponding to hemoglobin A1C over a one-year period. For example, a first health record can indicate that a first hemoglobin A1C test result was 6.3% (e.g., the first health record corresponds to affordance 680a), a second health record can indicate that a second hemoglobin A1C test result was 7.3% (e.g., the second health record corresponds to affordance 680b), and a third health record can indicate that a third hemoglobin A1C test result was 6% (e.g., the third health record corresponds to affordance 680c). With such health records, the graph includes indications regarding 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 676cd that provides additional information about one of the health records in the graph. As shown in FIG. 6RA, the representation 676cd relates to a first health record. In some examples, the representation 676cd relates to the first health record in response to a user input on the representation 676cc and / or a selection of an affordance displayed in a different user interface 676 to cause a hemoglobin user interface 676 to be displayed, the affordance corresponding to the health record associated with the instruction 676cc (e.g., affordance 670c shown in FIG. 6PA).

[0285] As shown in FIG. 6RA, the hemoglobin user interface 676 includes time scale affordances at the top that indicate different time scales (e.g., "W" for weeks, "M" for months, "Y" for years, and "5Y" for five years). As shown in FIG. 6RA, the time scale affordance that indicates years is selected, causing the graph to show health records over a one-year period. In some examples, selection of a different time scale affordance changes the graph to show detected health records over the entire selected time scale.

[0286] 6RA, the hemoglobin user interface 676 includes an out-of-range affordance 678. Selection of the out-of-range affordance 678 causes indications in the graph to be visually distinct (e.g., highlighted) corresponding to values ​​outside the defined range, as described above.

[0287] 6RA illustrates a first electronic device 600 receiving a user input 681 that corresponds to an affordance 680a. In some examples, the user input 681 is received via a touch-sensitive display device 602 and corresponds to a selection gesture (e.g., a tap) on the affordance 680a. In other examples, other forms of selection can be used, such as clicking using a mouse. In some examples, the user input 681 causes a different user interface to be displayed via the touch-sensitive display device 602, such as a test result record user interface 682 shown in FIG. 6SA.

[0288] 6SA illustrates the first electronic device 600 displaying a test result record user interface 682 via the touch-sensitive display device 602 at a 19th time after the 18th time. In some examples, the test result record user interface 682 is displayed in response to a user input corresponding to a selection of an affordance 680a in the hemoglobin user interface 676, as shown in FIG. 6RA. In some examples, the test result record user interface 682 includes detailed information about the particular health record. In some examples, the detailed information includes the date when the particular health record was collected, the date when the particular health record was received by the health application, an alternative name for the particular health record (e.g., as identified from either a remote source or other health records associated with the health application account), a clinical institution associated with the particular health record, and other information included in the particular health record.

[0289] 6SA-6SB illustrate a first electronic device 600 displaying an XYZ Medical Center user interface 698 via a touch-sensitive display device 602. In some implementations, the XYZ Medical Center user interface 698 is displayed in response to a user input corresponding to a selection of a first health record affordance 636 in a health record area of ​​the summary user interface 614, as shown in FIG.

[0290] As shown in FIGS. 6SA-6SB, the XYZ Medical Center user interface 698 includes multiple regions (e.g., regions for different days), each region corresponding to a different date on which the health records in the region were generated (e.g., collected, taken, or otherwise created by a clinical institution). In some examples, the multiple regions are ordered by date, such that regions corresponding to more recent dates are before regions corresponding to later dates. For example, the XYZ Medical Center user interface 698 includes a region corresponding to March 29, 2019 (as shown in FIG. 6SB) that is higher in the list (e.g., earlier) than a region corresponding to November 2, 2018 (as shown in FIG. 6SC).

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

[0292] In some examples, each sub-area included in the XYZ Medical Center user interface 698 includes one or more representations of health records. For example, sub-area 698a includes four representations of four separate health records, such as representation 670b (also shown and described in FIG. 6PA), representation 670c (also shown and described in FIG. 6PA), representation 698b (similar to 672b shown and described in FIG. 6PB, but from XYZ Medical Center instead of ABC Urgent Care), and representation 698c (similar to 672c shown and described in FIG. 6PB, but from XYZ Medical Center instead of ABC Urgent Care). FIGS. 6SA-6SB show that some representations can include graphs, while other representations, even those corresponding to the same health record type, do not include graphs. Such results, in some examples, result from portions of the health records that do not include ranges and / or are binary. It should be appreciated that while FIGS. 6SA-6SB show user interfaces for a single clinical institution, similar techniques can be used for user interfaces having representations of health records from multiple clinical institutions.

[0293] 6TA illustrates the first electronic device 600 displaying a search user interface 684 via the touch-sensitive display device 602 at a twentieth time after the nineteenth time. In some implementations, the search user interface 684 is displayed in response to a user input corresponding to a selection of a search affordance 642b in any user interface of the health application, such as the summary user interface 614.

[0294] As shown in FIG. 6TA, the search user interface 684 includes a search area 684a for inserting a search query to use to search for a health application. For example, when the first electronic device 600 receives user input corresponding to a string (e.g., a user typing the string using a keyboard) along with the search area 684a (e.g., an insertion marker is located within the search area 684a) and a request to perform a search, the first electronic device 600 searches for data associated with the health application based on the string, as shown in FIG. 6U and further described below.

[0295] 6TA, the search user interface 684 includes four groups of affordances: a shared health data affordance 684b, a health categories affordance 684c, a health records affordance 684d, and a health content affordance 684g. In some implementations, the search user interface 684 includes fewer groups of affordances, such as not including the shared health data affordance 684b, if the first electronic device 600 has not received shared health data from another device.

[0296] In some examples, the affordance of shared health data affordance 684b is associated with another account that is linked with the account associated with the health application. In one example, the linking includes a connection between two accounts such that health data recorded for one account is sent to the other account. For example, FIG. 6TA shows that shared health data affordance 684b includes affordance 684ba. In some examples, as shown in FIG. 6XA and described below, affordance 684ba is associated with the account associated with “Little Appleseed” such that selection of affordance 684ba causes a user interface for the account associated with “Little Appleseed” to be displayed (e.g., a user interface that allows a user to view health data associated with the account associated with “Little Appleseed”).

[0297] In some examples, the affordances of the health category affordance 684c are related to categories of health data types. Specifically, the health category affordance 684c represents a hierarchy of health data and allows a user to navigate to specific health data via one or more user inputs. For example, the health category affordance 684c includes an affordance 684ca that corresponds to an activity health data type (e.g., a type of health data corresponding to an activity). In some examples, the activity health data type corresponds to health data stored by an activity application. In another example, the health category affordance 684c includes an affordance 684ck that corresponds to a vial health data type (e.g., a type of health data corresponding to a vital). In some examples, the vial health data type corresponds to health data stored by a vial application.

[0298] In some embodiments, selection of the affordance of the health category affordance 684c causes a health application user interface to be displayed, the user interface including health data associated with each health data type, as shown in FIGS. 6V-6W and described below.

[0299] In some examples, the affordances of the health record affordance 684d are related to categories of health records, as described above. For example, the health record affordance 684d represents a hierarchy of health records, allowing a user to navigate to a particular health record via one or more user inputs. For example, the health record affordance 684d includes an affordance 684de corresponding to a test result (e.g., a type of health record). In some examples, selection of the affordance 684de causes a user interface to be displayed, where the user interface includes the health records of the test results. The health record affordance 684d also includes an affordance related to a clinical institution (e.g., affordance 684h). Selection of the affordance related to the clinical institution causes a user interface of a health application to be displayed, where the user interface includes health records collected by the clinical institution. Selection of an affordance related to all accounts (e.g., affordance 684dj) causes a user interface of a health application to be displayed, where the user interface includes all health records.

[0300] As shown in FIG. 6TB, the search user interface 684 includes an affordance 684e for viewing clinical documents. Selection of affordance 684e causes a user interface of a health application to be displayed, the user interface including the clinical documents. As shown in FIG. 6TB, the search user interface 684 includes an affordance 684f for viewing non-readable data (e.g., data that the health application (or a process associated with the health application) cannot parse (e.g., interpret or read). Selection of affordance 684f causes a user interface of the health application to be displayed, the user interface including a representation of a health record that could not be parsed by the health application (or a process associated with the health application).

[0301] In some examples, the affordances of the health content affordances 684g are associated with links to other health content. For example, the health content affordances 684g include an affordance for viewing educational content. Selection of such an affordance causes a user interface of a health application to be displayed, the user interface including the educational content. In another example, the health content affordances 684g include an affordance for viewing highlights as described above. Selection of such an affordance causes a user interface of a health application to be displayed, the user interface including one or more highlight representations.

[0302] FIG 6U illustrates the first electronic device 600 displaying a search user interface 684 via the touch-sensitive display device 602 at a twenty-first time after the twentieth time. In some examples, the search user interface 684 is displayed (as shown in FIG 6U) in response to a user request to search for a string entered in the search field 684a. For example, FIG 6U illustrates a user entering "blood pressure" into the search field 684a to cause search results corresponding to a search for "blood pressure" using a health application to be displayed. In some examples, the user request to search for a string replaces (e.g., stops displaying) the group of four affordances in the search user interface 684 shown in FIGS 6TA-6TB.

[0303] In some examples, the search results include data from different sources. For example, the first search result 684h includes health data (e.g., health data detected by the first electronic device 600 or another device linked to either the first electronic device 600 or an account associated with the health application). As shown in FIG. 6U, the first search result 684h includes a representation of blood pressure detected for a user associated with the account. In another example, the second search result 684i includes health record data (e.g., health records received by the first electronic device 600, for example, from a clinical institution). As shown in FIG. 6U, the second search result 685i includes blood pressure included in the health record.

[0304] In some examples, the search results include categories of highlights determined to be associated with the string. For example, FIG. 6U shows that the search results include a heart highlight affordance 685ja (e.g., an affordance associated with highlights associated with the heart) and a vitals highlight affordance 685jb (e.g., an affordance associated with highlights associated with vitals). In some examples, selection of the highlight affordance causes a user interface of a health application to be displayed, where the user interface includes one or more highlight representations associated with each category of highlights.

[0305] In some examples, the search results include categories of health data determined to be associated with the character string (684k). Such categories correspond to the health category affordances 684c described above. For example, FIG. 6U shows that the search results include a cardiac category affordance 684ka, a vitals affordance 684kb, and a clinical vial affordance 684kc. The health data categories represent a hierarchy of health records and allow a user to navigate to a particular health record via one or more user inputs. For example, selection of an affordance corresponding to a health data category causes a user interface to be displayed, where the user interface includes the health records corresponding to the category.

[0306] 6V illustrates the first electronic device 600 displaying an activity user interface 686 via the touch-sensitive display device 602 at a twenty-second time after the twenty-first time. In some implementations, the activity user interface 686 is displayed in response to a user input corresponding to a selection of an affordance 684ca in the search user interface 684.

[0307] 6V, the activity user interface 686 includes a representation of health data related to an activity for an account associated with the health application. For example, the activity user interface 686 includes a representation 686a with heart rate data during a strength workout.

[0308] 6W illustrates the first electronic device 600 displaying a vitals user interface 688 via the touch-sensitive display device 602 at a twenty-third time after the twenty-second time. In some examples, the vial user interface 688 is displayed in response to a user input corresponding to a selection of an affordance 684ck within the search user interface 684.

[0309] As shown in FIG. 6W, the vitals user interface 688 includes a representation of health data associated with vitals for an account associated with the health application. For example, the activity user interface 686 includes a representation 688a with heart rate data during strength training. Representation 688a is an example where health data included in one category (e.g., vitals) can be included in another category (e.g., activity). Such a result results from health data having multiple categories with which they are associated. For example, as shown in FIGS. 6V-6W, heart rate during strength training is associated with both activity and vitals. In some examples, the health data has primary and secondary health categories.

[0310] 6XA-6XB show the first electronic device 600 displaying a child search user interface 690 via the touch-sensitive display device 602 at a twenty-fourth time after the twenty-third time. In some examples, the child search user interface 690 and the user interfaces navigated from the affordances included in the child search user interface 690 are read-only (compared to the search user interface 684, which in some examples allows a user to add / remove / edit data when navigating to data associated with an account in a health application). In some examples, the child search user interface 690 is displayed in response to a user input corresponding to a selection of an affordance 684ba in the search user interface 684.

[0311] In some embodiments, the child search user interface 690 is a version of the search user interface 684 for an account linked to an account associated with a health application. As shown in FIGS. 6XA-6XB, the child search user interface 690 includes a search area 692a (similar to the search area 684a in the search user interface 684, except that the search area 692a searches for data corresponding to Little Appleseed instead of an account associated with a health application), a health category affordance 692b (similar to the health category affordance 692c in the search user interface 684, except that the health category affordance 692b is associated with data corresponding to Little Appleseed instead of an account associated with a health application), a health record affordance 684c (similar to the health record affordance 684d in the search user interface 684, except that the health record affordance 692c is associated with data corresponding to Little Appleseed instead of an account associated with a health application), and a health content affordance 692e (similar to the health content affordance 684g in the search user interface 684). In some embodiments, the child search user interface 690 does not include a shared health data affordance (e.g., shared health data affordance 684ba). In other embodiments, the child search user interface 690 includes a shared health data affordance for a device that is linked to a Little Appleseed account.

[0312] 6Y illustrates the first electronic device 600 displaying an activity user interface 694 via the touch-sensitive display device 602 at a twenty-fifth time after the twenty-fourth time. In some implementations, the activity user interface 694 is displayed in response to a user input corresponding to a selection of an activity affordance within the child search user interface 690.

[0313] 6Y, activity user interface 694 includes a representation of health data related to activity for Little Appleseed's account (e.g., as indicated by instruction 694a). For example, activity user interface 694 includes a representation 694c with heart rate data during Little Appleseed's strength training.

[0314] 6Z illustrates first electronic device 600 displaying vitals user interface 696 via touch-sensitive display device 602 at a twenty-sixth time after the twenty-fifth time. In some implementations, vitals user interface 696 is displayed in response to a user input corresponding to a selection of a vital affordance within child search user interface 690.

[0315] As shown in FIG. 6Z, vitals user interface 696 includes a representation of health data related to vitals for a Little Appleseed account (e.g., as indicated by instruction 696a). For example, vitals user interface 696 includes representation 696c having heart rate data during strength training for Little Appleseed. Representation 696c is an example where health data included in one category (e.g., vitals) can be included in another category (e.g., activity). Such a result results from health data having multiple categories with which they are associated. For example, as shown in FIGS. 6Y-6Z, heart rate during strength training is associated with both activity and vitals. In some examples, the health data has primary and secondary health categories.

[0316] 7A-7B are flow diagrams illustrating a method for managing notifications using an electronic device, according to some embodiments. Method 700 is performed on a device having a display device (e.g., 100, 300, 500, 600, 606). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0317] In some embodiments, the electronic device (e.g., 600, 606) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and one or more input devices. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user 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. Thus, the computer system can transmit data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from the one or more input devices over a wired or wireless connection.

[0318] As described below, method 700 provides an intuitive way to manage notifications. The method reduces the cognitive burden on the user when viewing and acting on notifications, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to view and act on notifications more quickly and efficiently conserves power and extends the time between battery charges.

[0319] The electronic device displays (702) via the display device a first instance of a first user interface (e.g., 614 shown in FIG. 6DA) that includes a first notification (e.g., 616, 618, 620) (e.g., a notification affordance) that, when selected, causes a first data set (e.g., 644) (e.g., notification data, data generated or received (e.g., from an external device) at a first time, health data, sensor data, biometric data, physical activity data, clinical data) to be displayed.

[0320] In some embodiments, the first notification includes a first visual characteristic (704) (e.g., color (e.g., shown as a pattern in the header of 616 including 616b and 616c, a pattern in the header of 618 including 618a, 618b, and 618c, and a pattern in the header of 620 including 620a, 620b, and 620c) (e.g., a foreground color, a background color, an inclusion (or exclusion) of a respective icon). In some embodiments, pursuant to a determination (706) that the first data set corresponds to (e.g., was generated by) a first application, the first visual characteristic has a first value (e.g., a blue color). In some embodiments, pursuant to a determination (708) that the first data set corresponds to a second application, the first visual characteristic has a second value (e.g., a red color) that is different from the first value.

[0321] Specifying the visual quality (e.g., color) of notifications based on their corresponding application provides the user with feedback that helps identify the application. Providing improved visual feedback to the user may improve usability of the device, make the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and reduce power usage and improve the device's battery life by allowing the user to use the device more quickly and efficiently.

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

[0323] In accordance with a determination (712) that a set of interaction criteria (a set of criteria regarding whether the first data set has been interacted with (e.g., via selection of the first notification)) has been met, including criteria that are met when the first data set is 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 that receives the same notifications as the electronic device (e.g., because both are associated with the same user account)), and in accordance with a determination that a first set of removal criteria (e.g., a set of criteria by which display of a notification corresponding to the interacted data is governed) has not been met, including a first criterion based on a first time period (e.g., a time period that must be exceeded to satisfy the first criterion, a time period determined from when the first data set was received or generated, a time period determined from when the notification corresponding to the first data set was first displayed, a non-zero time period). The second instance of the first user interface includes the first notification (FIGS. 6G-6H).

[0324] In accordance with a determination that the first set of removal criteria have been met, and in accordance with a determination that the first set of removal criteria have been met (714), the second instance of the first user interface does not include the first notification (FIGS. 6G-6H).

[0325] In accordance with a determination that the set of interaction criteria has not been met, and in accordance with a determination (716) that a second set of removal criteria (e.g., a set of criteria by which display of a notification corresponding to non-interacted data is governed) that includes a second criterion based on a second time period (e.g., a time period that must be exceeded to satisfy the second criterion, a time period determined from when the first data set was received or generated, a time period determined from when a notification corresponding to the first data set was initially displayed that is longer than the first time period), the second instance of the first user interface includes the first notification (FIGS. 6G-6H). In some embodiments, the second time period is not longer than the first time period.

[0326] Following a determination that the set of interaction criteria is not met and following a determination that the second set of removal criteria is met (718), the second instance of the first user interface does not include the first notification (FIGS. 6G-6H). In some embodiments, notifications are displayed (or re-displayed) within the first user interface for a period of time that varies based on whether the notification has been interacted with. In some embodiments, notifications that have not been interacted with are displayed for a longer period of time than notifications that have been interacted with.

[0327] Displaying a first notification based on whether a set of interaction criteria and a set of removal criteria are met allows a user to view relevant notifications without providing undesired notifications. Taking an action when a set of conditions are met without requiring further user input enhances usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0328] In some embodiments, prior to displaying the first instance of the first user interface, the electronic device receives a second dataset from an external device (e.g., a smart watch including one or more sensors (e.g., biometric sensors)), the first dataset corresponding to the second dataset (e.g., 610). In some embodiments, the external device is in a paired relationship with the electronic device (e.g., both devices are associated with the same user account and have a persistent relationship). In some embodiments, the second dataset is the first dataset. In some embodiments, the second dataset is included in the first dataset. In some embodiments, the first dataset is derived from (e.g., calculated based on) the second dataset. In some embodiments, the second dataset is sensor data from one or more sensors of the external device. In some embodiments, the second dataset includes clinical health data (e.g., 604b) (e.g., medical records from a health institution, test results from a clinical laboratory test).

[0329] In some embodiments, the electronic device includes a set of one or more sensors (e.g., biometric sensors). In some embodiments, prior to displaying the first instance of the first user interface, the electronic device receives (e.g., detects) a third data set (e.g., 604a) via the set of one or more sensors. In some embodiments, the first data set corresponds to the third data set. In some embodiments, the third data set is the first data set. In some embodiments, the third data set is included in the first data set. In some embodiments, the first data set is derived from (e.g., calculated based on) the third data set. 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 a summary tab of a health application, such as a lock screen) that includes a second notification corresponding to the third data set. In some embodiments, the second user interface is different from the first user interface. In some embodiments, the second notification includes the same content as the first notification.

[0330] In some embodiments, the first notification is included in a list of first notifications, which in some embodiments is ordered based on chronological or reverse chronological order (e.g., based on initial notification publication time, based on the time the data to be displayed when the respective notification is selected was generated or received) (e.g., FIG. 6DA).

[0331] Ordering the first list based on a chronological or reverse-chronological structure provides the user with feedback regarding the sequence in which the notifications were generated. Providing improved visual feedback to the user improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0332] In some embodiments, while displaying the first notification (e.g., in the 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 the first display device (e.g., including the first data set). In some embodiments, the first data set corresponds to a first application, and the second user interface includes additional data and / or information from the first application.

[0333] In some embodiments, the first data set corresponds to a first data type (e.g., biometric data, sensor data). In some embodiments, the second user interface includes a first affordance that, when selected, causes a first value of the first data type (e.g., a first average) to be displayed, and a second affordance that, when selected, causes a second value of the first data type that is different from the first value (e.g., a second average based on a different filter (e.g., time filter, source filter) than the first average) (e.g., average at 644 and daily average affordances).

[0334] It should be noted that the details of the processes (e.g., FIGS. 7A-7B) described above with respect to method 700 are also applicable in an analogous manner to the methods described below / above. For example, methods 800, 900, 1000, 1100, and 1400 optionally include one or more of the features of the various methods described above with reference to method 700. For the sake of brevity, these details will not be repeated below.

[0335] 8A-8B are flow diagrams illustrating a method for managing the display of health-related information using an electronic device, according to some embodiments. Method 800 is performed on a device (e.g., 100, 300, 500, 600) having a display device. Some operations of method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0336] In some embodiments, the electronic device (e.g., 600) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and one or more input devices. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user 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. Thus, the computer system can transmit data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from the one or more input devices over a wired or wireless connection.

[0337] As described below, the method 800 provides an intuitive way to manage the display of health-related information. The method reduces the cognitive burden on the user when viewing health-related information, thereby creating a more efficient human-machine interface. For battery-operated computing devices, it conserves power and extends the time between battery charges by allowing the user to act on the viewing of health-related information more quickly and efficiently.

[0338] The electronic device receives (802) first health data (e.g., physical activity performed by a 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.

[0339] The electronic device receives a request (e.g., 613) (e.g., a request to view a summary tab of a health application, such as a user tapping on an icon for the health application or a user tapping on an affordance for the summary tab) and displays (804) a first user interface (e.g., 614).

[0340] In response to receiving the request, the electronic device displays (806) via the display device a first user interface (e.g., 614) including a first region (e.g., a favorites region in 614) (808) (e.g., a favorites section). The first user region includes a first representation (e.g., 626a) of the first health data (e.g., number of steps taken during a current day) pursuant to a determination (812) that a type of data (e.g., activity, environmental noise, etc.) corresponding to the first health data has been identified by user input (e.g., the user selected a type of data). The first user region does not include a representation of the first health data pursuant to a determination (814) that a type of data corresponding to the first health data has not been identified by user input (e.g., the user did not select a type of data).

[0341] In response to receiving the request, the electronic device displays (806) via the display device a first user interface including a second region (e.g., a highlight region in 614) (810) (e.g., a highlight section). The second region includes a second representation (e.g., 630, 632, 652, 654, 656, 658, 660, 662) of the first health data that is different from the first representation (e.g., a graphical representation comparing health data for the first health indicator over a first time period to health data for the first health indicator over a second time period that is different from the first time period) pursuant to a determination (816) that the first set of highlighting criteria is met (e.g., the system determines that a representation corresponding to the health data should be displayed to the user). 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 the health data to health data corresponding to a time period that is different from the time period of the health data. The second region does not include the second representation of the first health data pursuant to a determination (818) that the first set of highlighting criteria is not met (e.g., the system determines that the representation corresponding to the health data should not be displayed to the user).

[0342] By including a second representation of the first health data based on the set of first highlighting criteria being met, the device can display relevant information and avoid using display space when the information is not relevant. Taking an action when a set of conditions is met without requiring further user input enhances usability of the device, making the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing power usage and improving battery life of the device by allowing the user to use the device more quickly and efficiently.

[0343] In some embodiments, the health data includes a first plurality of time periods (e.g., day, week, month) of health data. In some embodiments, the first representation of the health data includes a first display (e.g., text display, graphical display, a display of a first measure (e.g., steps, miles, calories) of the health data corresponding to a first time period (e.g., today) of the first plurality of time periods, and a second display (e.g., text display, graphical display) of the health data corresponding to a second time period (e.g., yesterday) of the first plurality of time periods that is different from the first time period. In some embodiments, the first representation includes a bar graph with today's values ​​compared to yesterday's values ​​(e.g., 632).

[0344] Providing different instructions for different time periods provides the user with feedback regarding the stored data corresponding to each time period. Providing improved visual feedback to the user improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0345] In some embodiments, a first period of the first plurality of periods corresponds to a particular instance of the repeating time interval (e.g., a particular time of day, a particular day of a week, or a month). In some embodiments, a second period of the first plurality of periods is a plurality of instances. In some embodiments, all of the instances of the repeating time interval available in the health data (e.g., multiple Mondays of multiple weeks, multiple mornings of multiple days). In some embodiments, the first indication is the value of the health index for a Monday of the week and the second indication is the average value of the health index for all Mondays (e.g., 662).

[0346] In some embodiments, the health data includes a second plurality of time periods (e.g., days, weeks, months) of health data. In some embodiments, the first representation of the health data includes a third indication of the health data corresponding to a frequency (e.g., as a ratio, as a percentage, as a portion (e.g., last week to 4 days)) of occurrence of the first health event (e.g., health-related event) within the second plurality of time periods (e.g., days, weeks, years) (e.g., 654).

[0347] In some embodiments, the health data includes a third plurality of time periods (e.g., days, weeks, months) of health data. In some embodiments, the first representation of the health data includes a fourth indication of an average value of the health data for the third plurality of time periods (e.g., weekly average), a fifth indication (e.g., day of week) corresponding to a value of the health data for a first time period of the third plurality of time periods, and a sixth indication (e.g., day of week) corresponding to a value of the health data for a second time period of the third plurality of time periods that is different from the first time period of the plurality of time periods (e.g., 652).

[0348] In some embodiments, the first representation includes a seventh indication corresponding to the first physical activity tracking session (e.g., first workout). In some embodiments, the first representation includes an eighth indication corresponding to the 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 physical activity tracking session and the second physical activity tracking session correspond to the same time period (e.g., same day, same week, same month). In some embodiments, a ninth indication of the health data (e.g., total calories burned, average pace) is based (e.g., 658) on the first physical activity tracking session and the second physical activity tracking session.

[0349] Displaying a representation of the health data based on the first and second physical activity tracking sessions uses the representation to provide feedback to the user about both sessions. Providing improved visual feedback to the user improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0350] In some embodiments, the first set of highlighting criteria includes criteria based on factors selected from the group consisting of a relationship (e.g., a mathematical relationship (e.g., difference)) between a first portion of the health data (e.g., a portion corresponding to a first time period (e.g., a day)) and a second portion of the health data (e.g., a portion corresponding to a second time period (e.g., a week)), a degree of user interaction with the health data, and a period of time during which a representation (e.g., any representation) of the health data was displayed (e.g., on an electronic device).

[0351] In some embodiments, the first representation is included in a list of first representations. In some embodiments, the list of first representations is ordered based on the type of data of the health data (e.g., physical activity data is grouped together, heart rate related data is grouped together) (e.g., 660).

[0352] It should be noted that the details of the processes (e.g., FIGS. 8A-8B) described above with respect to method 800 are also applicable in an analogous manner to the methods described below / above. For example, methods 700, 900, 1000, 1100, and 1400 optionally include one or more of the features of the various methods described above with reference to method 800. For the sake of brevity, these details will not be repeated below.

[0353] 9A-9B are flow diagrams illustrating a method for managing display of clinical health record representations using an electronic device, according to some embodiments. The method 900 is performed on a device (e.g., 100, 300, 500, 600, 606) having a display device. Some operations of the method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0354] In some embodiments, the electronic device (e.g., 600, 606) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and one or more input devices. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user 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. Thus, the computer system can transmit data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from the one or more input devices over a wired or wireless connection.

[0355] As described below, the method 900 provides an intuitive way to manage clinical health record representations. The method reduces the cognitive burden on the user when accessing clinical health records, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to access clinical health records faster and more efficiently conserves power and extends the time between battery charges.

[0356] The electronic device receives (902) clinical health record data corresponding to a particular health institution (e.g., XYZ Medical Center at 672a, 698). The electronic device receives (904) a request (e.g., tapping 667, on a first health record affordance 636 in the summary user interface 614) (e.g., a request to view all clinical health records for XYZ Medical Center) and displays (904) a first user interface (e.g., 668, 698).

[0357] In response to receiving the request, the electronic device displays (906) a first user interface (e.g., 668, 698) via a display device. The first user interface includes (908) a first region (e.g., 672, 698a) corresponding to the first type of clinical health record (e.g., 668b, 698a, lab results region). The first region includes a first textual representation (e.g., 672b, 672c, 698b, 698c) for the first clinical health record based on the clinical health record data according to a determination (912) that a first clinical health record of the first type of clinical health record does not meet a first set of graphing criteria (e.g., the first clinical health record (1) does not include a range of the first clinical health record or (2) includes binary information (in some embodiments, does not achieve benefit from graphing)), and the first user interface does not include a graphical representation (e.g., a non-textual graphical representation) for the first clinical health record. The first area includes a first graphical representation (e.g., 672d in 668) for the first clinical health record based on the clinical health record data pursuant to a determination (914) that the first clinical health record meets a first set of graphing criteria (e.g., the first clinical health record includes a range of the first clinical health record and includes non-binary information (which in some embodiments would benefit from graphing)).

[0358] In response to receiving the request, the electronic device displays (906) via the display device a first user interface including (910) a second region (e.g., different date ranges in 698, medication region in 668) corresponding to a second type of clinical health record (e.g., medication region). The second region includes a second textual representation for the second clinical health record based on the clinical health record data pursuant to a determination (916) that a second clinical health record of the second type of clinical health record does not meet the first set of graphing criteria (e.g., the second clinical health record (1) does not include a range of the second clinical health record or (2) includes binary information (in some embodiments, does not achieve benefit from graphing)), and the user interface does not include a graphical representation for the second clinical health record. The second area includes a second graphical representation for the second clinical health record based on the clinical health record data pursuant to a determination (918) that the second clinical health record meets the first set of graphing criteria (e.g., the second clinical health record includes a range of the second clinical health record and includes non-binary information (which in some embodiments would benefit from graphing)).

[0359] Displaying a textual or graphical representation of the health record provides feedback to the user as to whether the health record meets the graphing criteria and allows the user to access information related to the record more quickly and efficiently. Providing improved visual feedback to the user improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0360] In some embodiments, if the respective clinical health record (e.g., a first clinical health record) corresponds to health data that includes data in a range (e.g., minimum and maximum values ​​that define a range, the data values ​​corresponding to the respective clinical health record are deemed to meet certain criteria (e.g., criteria regarding whether the data values ​​are acceptable, such as criteria set by a governing body)), a first set of graphing criteria for the respective clinical health record is met (e.g., the first set of graphing criteria includes criteria that are met when the clinical health record includes a range of the clinical health record) (e.g., 670b, 670c).

[0361] In some embodiments, if the respective clinical health record (e.g., the first clinical health record) corresponds to health data that is binary (e.g., has a binary state (positive or negative, up or down, defined or undefined)), then the first set of graphing criteria for the respective clinical health record is not met (e.g., the first set of graphing criteria includes criteria that are met when the clinical heal...

Claims

1. 1. A method comprising: In an electronic device having a display device, displaying via the display device a first instance of a first user interface including a first notification that when selected causes a display of a first data set; displaying a second instance of the first user interface after displaying the first instance of the first user interface; pursuant to a determination that a set of interaction criteria are satisfied, the set of interaction criteria including criteria satisfied when the first data set is displayed, and pursuant to a determination that a first set of removal criteria are not satisfied, the first criterion including a first criterion based on a first time period, the second instance of the first user interface including the first notification; in response to a determination that the set of interaction criteria is satisfied and in response to a determination that the first set of removal criteria is satisfied, the second instance of the first user interface does not include the first notification; in response to a determination that the set of interaction criteria are not satisfied and in response to a determination that a second set of removal criteria are not satisfied, the second set including second criteria based on a second period of time that is longer than the first period of time, the second instance of the first user interface including the first notification; The method, wherein in accordance with a determination that the set of interaction criteria is not satisfied and in accordance with a determination that the second set of removal criteria is satisfied, the second instance of the first user interface does not include the first notification.

2. receiving a second data set from an external device prior to displaying the first instance of the first user interface, the first data set corresponding to the second data set; The method of claim 1 further comprising:

3. The method of claim 2 , wherein the second data set comprises clinical health data.

4. The electronic device includes a set of one or more sensors, and the method further comprises: prior to displaying the first instance of the first user interface; receiving a third data set via the set of one or more sensors, the first data set corresponding to the third data set; and displaying a second user interface including a second notification corresponding to the third data set, the second user interface being different from the first user interface; The method according to claim 1 , comprising:

5. the first notification is included in a first list of notifications, the first list of notifications being ordered based on a chronological or reverse chronological order; 5. The method according to any one of claims 1 to 4.

6. the first notification includes a first visual characteristic; In response to a determination that the first data set corresponds to a first application, the first visual characteristic has a first value; In response to a determination that the first data set corresponds to a second application, the first visual characteristic has a second value different from the first value.

6. The method according to any one of claims 1 to 5.

7. receiving a first input corresponding to a selection of the first notification while displaying the first notification; in response to receiving the first input, displaying via the display device a second user interface including the first data set; The method of claim 1 , further comprising:

8. the first data set corresponds to a first data type, and the second user interface comprises: a first affordance that, when selected, causes a first value of the first data type to be displayed; a second affordance that, when selected, causes a second value of the first data type to be displayed that is different from the first value; and The method of claim 7, comprising:

9. A computer program causing a computer to execute a method according to any one of claims 1 to 8.

10. An electronic device, comprising: A memory for storing a computer program according to claim 9; and one or more processors capable of executing the computer programs stored in the memory, wherein the electronic device is configured to communicate with a display device.

11. An electronic device configured to communicate with a display device, the electronic device comprising means for performing a method according to any one of claims 1 to 8.

Images