Browser application user interface

Abstract

To provide an electronic apparatus with a faster, more efficient method and an interface for managing health information and functions.SOLUTION: A method and interface optionally complement or replace other methods for managing health information and functions. The method and interface reduce a cognitive burden placed on a user and create a more efficient human-machine interface. For a battery-operated computing device, the method and interface conserve power and extend intervals between battery charges.SELECTED DRAWING: Figure 6A

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims priority to U.S. Patent Application No. 16 / 880,714, filed on May 21, 2020, and entitled "HEALTH APPLICATION USER INTERFACES", and U.S. Provisional Patent Application No. 62 / 856,061, filed on June 1, 2019, and entitled "HEALTH APPLICATION USER INTERFACES", the entire contents of each of which are hereby incorporated by reference in their entirety for all purposes.

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

Background Art

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

Summary of the Invention

[0004] However, some techniques for using electronic devices to manage health information and functions are generally cumbersome and inefficient. For example, some existing techniques use complex and time - consuming user interfaces that can involve 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 significant in battery - operated devices.

[0005] Accordingly, the present technology provides an electronic device having a faster and more efficient method and interface for managing health information and functions. Such a method and interface optionally complement or replace other methods for managing health information and functions. Such a method and interface reduces the cognitive burden on the user and creates a more efficient human-machine interface. In the case of a battery-operated computing device, such a method and interface conserves power and lengthens the battery charging interval.

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

[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 including a display device is described. In some embodiments, the one or more programs include displaying, via the display device, a first instance of a first user interface including a first notification that causes a 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 second instance of the first user interface includes the first notification according to a determination that a set of interaction criteria including criteria that are satisfied when the first data set is displayed is satisfied and a determination that a set of first removal criteria including a first criterion based on a first period is not satisfied; the second instance of the first user interface does not include the first notification according to a determination that the set of interaction criteria is satisfied and a determination that the set of first removal criteria is satisfied; the second instance of the first user interface includes the first notification according to a determination that the set of interaction criteria is not satisfied and a determination that a set of second removal criteria including a second criterion based on a second period longer than the first period is not satisfied; and the second instance of the first user interface does not include the first notification according to a determination that the set of interaction criteria is not satisfied and a determination that the set of second removal criteria is satisfied.

[0008] 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 including a display device is described. In some embodiments, the one or more programs include displaying, via the display device, a first instance of a first user interface including a first notification that causes a 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 second instance of the first user interface includes the first notification according to a determination that a set of interaction criteria including criteria satisfied when the first data set is displayed is satisfied and a determination that a set of first removal criteria including a first criterion based on a first period is not satisfied; the second instance of the first user interface does not include the first notification according to a determination that the set of interaction criteria is satisfied and a determination that the set of first removal criteria is satisfied; the second instance of the first user interface includes the first notification according to a determination that the set of interaction criteria is not satisfied and a determination that a set of second removal criteria including a second criterion based on a second period longer than the first period is not satisfied; and the second instance of the first user interface does not include the first notification according to a determination that the interaction criteria are not satisfied and a determination that the set of second removal criteria is satisfied.

[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, wherein the one or more programs cause, via the display device, a first instance of a first user interface including a first notification that causes a display of a first data set when selected, to be displayed, and after displaying the first instance of the first user interface, cause a second instance of the first user interface to be displayed, and according to a determination that a set of interaction criteria including criteria satisfied when the first data set is displayed is satisfied, and according to a determination that a set of first removal criteria including a first criterion based on a first period is not satisfied, the second instance of the first user interface includes the first notification, and according to a determination that the set of interaction criteria is satisfied, and according to a determination that the set of first removal criteria is satisfied, the second instance of the first user interface does not include the first notification, and according to a determination that the set of interaction criteria is not satisfied, and according to a determination that a set of second removal criteria including a second criterion based on a second period longer than the first period is not satisfied, the second instance of the first user interface includes the first notification, and according to a determination that the set of interaction criteria is not satisfied, and according to a determination that the set of second removal criteria is satisfied, 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 and means for displaying a first instance of a first user interface that includes a first notification that causes the display of a first data set when selected via the display device, and means for displaying a second instance of the first user interface after displaying the first instance of the first user interface, wherein the second instance of the first user interface includes the first notification according to a determination that a set of interaction criteria including criteria satisfied when the first data set is displayed is satisfied and a determination that a set of first removal criteria including a first criterion based on a first period is not satisfied, the second instance of the first user interface does not include the first notification according to a determination that the set of interaction criteria is satisfied and a determination that the set of first removal criteria is satisfied, the second instance of the first user interface includes the first notification according to a determination that the set of interaction criteria is not satisfied and a determination that a set of second removal criteria including a second criterion based on a second period longer than the first period is not satisfied, and the second instance of the first user interface does not include the first notification according to a determination that the set of interaction criteria is not satisfied and a determination that the set of second removal criteria is satisfied.

[0011] According to some embodiments, a method is described. In some embodiments, the method is executed in an electronic device comprising 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, via the display device, according to a determination that the type of data corresponding to the first health data is identified by user input, including a first representation of the first health data, and according to a determination that the type of data corresponding to the first health data is not identified by user input, a first region not including a representation of the first health data, and according to a determination that a set of first highlighting criteria is met, including a second representation of the first health data different from the first representation, and according to a determination that the set of first highlighting criteria is not met, a second region not including a second representation of the first health data, and displaying a first user interface including the above.

[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 receiving first health data, receiving a request to display a first user interface, and in response to receiving the request, via the display device, according to a determination that the type of data corresponding to the first health data is identified by user input, including a first representation of the first health data, and according to a determination that the type of data corresponding to the first health data is not identified by user input, a first region not including a representation of the first health data, and according to a determination that a set of first highlighting criteria is met, including a second representation of the first health data different from the first representation, and according to a determination that the set of first highlighting criteria is not met, a second region not including a second representation of the first health data, and instructions for displaying a first user interface including the above.

[0013] 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 including a display device is described. In some embodiments, the one or more programs are configured to receive first health data, receive a request to display a first user interface, and in response to receiving the request, via the display device, according to a determination that the type of data corresponding to the first health data has been identified by user input, include a first representation of the first health data, and according to a determination that the type of data corresponding to the first health data has not been identified by user input, not include a representation of the first health data, a first region; and according to a determination that a set of first highlighting criteria has been met, include a second representation of the first health data different from the first representation, and according to a determination that the set of first highlighting criteria has not been met, not include a second representation of the first health data, a second region, and display a first user interface including the above.

[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, and the one or more programs are configured to receive first health data, receive a request to display a first user interface, and in response to receiving the request, via the display device, according to a determination that the type of data corresponding to the first health data has been identified by user input, include a first representation of the first health data, and according to a determination that the type of data corresponding to the first health data has not been identified by user input, not include a representation of the first health data, a first region; and according to a determination that a set of first highlighting criteria has been met, include a second representation of the first health data different from the first representation, and according to a determination that the set of first highlighting criteria has not been met, not include a second representation of the first health data, a second region, and include instructions to display a first user interface including the above.

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

[0016] According to some embodiments, a method is described. In some embodiments, the method is executed in an electronic device comprising a display device. In some embodiments, the method comprises 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, via the display device, a first region corresponding to a first type of clinical health record, wherein if the first user interface does not include a graphical representation of a first clinical health record of the first type of clinical health record according to 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 text representation of the first clinical health record based on the clinical health record data, and according to a determination that the first clinical health meets the first set of graphing criteria, a first graphical representation of the first clinical health record based on the clinical health record data, a second region corresponding to a second type of clinical health record, wherein if the user interface does not include a graphical representation of a second clinical health record of the second type of clinical health record according to a determination that the second clinical health record of the second type of clinical health record does not meet a first set of graphing criteria, a second text representation of the second clinical health record based on the clinical health record data, and according to a determination that the second clinical health record meets the first set of graphing criteria, a second graphical representation of the second clinical health record based on the clinical health record data, and displaying a first user interface comprising the first region and the second region.

[0017] 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 including a display device is described. In some embodiments, the one or more programs are configured to receive clinical health record data corresponding to a particular health institution, receive a request to display a first user interface, and in response to receiving the request, via the display device, a first region corresponding to a first type of clinical health record, wherein, according to a determination that a first clinical health record of the first type of clinical health record does not meet a first set of graphing criteria, if the first user interface does not include a graphical representation of the first clinical health record, a first text representation of the first clinical health record based on the clinical health record data and, according to a determination that the first clinical health meets the first set of graphing criteria, a first graphical representation of the first clinical health record based on the clinical health record data, and a second region corresponding to a second type of clinical health record, wherein, according to a determination that a second clinical health record of the second type of clinical health record does not meet the first set of graphing criteria, if the user interface does not include a graphical representation of the second clinical health record, a second text representation of the second clinical health record based on the clinical health record data and, according to a determination that the second clinical health record meets the first set of graphing criteria, a second graphical representation of the second clinical health record based on the clinical health record data, and display a first user interface including the second region.

[0018] 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 including a display device is described. In some embodiments, the one or more programs are to receive clinical health record data corresponding to a particular health institution and receive a request to display a first user interface, and in response to receiving the request, via the display device, a first region corresponding to a first type of clinical health record, wherein, according to a determination that a first clinical health record of the first type of clinical health record does not meet a first set of graphing criteria, if the first user interface does not include a graphical representation of the first clinical health record, a first text representation of the first clinical health record based on the clinical health record data and, according to a determination that the first clinical health meets the first set of graphing criteria, a first graphical representation of the first clinical health record based on the clinical health record data, and a second region corresponding to a second type of clinical health record, wherein, according to a determination that a second clinical health record of the second type of clinical health record does not meet the first set of graphing criteria, if the user interface does not include a graphical representation of the second clinical health record, a second text representation of the second clinical health record based on the clinical health record data and, according to a determination that the second clinical health record meets the first set of graphing criteria, a second graphical representation of the second clinical health record based on the clinical health record data, and display a first user interface including the second region.

[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, wherein the one or more programs are configured to receive clinical health record data corresponding to a specific health institution, receive a request to display a first user interface, and in response to receiving the request, via the display device, a first region corresponding to a first type of clinical health record, wherein 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 meet a first set of graphing criteria, a first text representation of the first clinical health record based on the clinical health record data and, according to a determination that the first clinical health meets the first set of graphing criteria, a first graphical representation of the first clinical health record based on the clinical health record data; and a second region corresponding to a second type of clinical health record, wherein if the user interface does not include a graphical representation of the second clinical health record according to 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, a second text representation of the second clinical health record based on the clinical health record data and, according to a determination that the second clinical health record meets the first set of graphing criteria, a second graphical representation of the second clinical health record based on the clinical health record data, and display a first user interface including the second region.

[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, via the display device, a first region corresponding to a first type of clinical health record, wherein, according to a determination that a first clinical health record of the first type of clinical health record does not meet a first set of graphing criteria, if the first user interface does not include a graphical representation of the first clinical health record, a first text representation of the first clinical health record based on the clinical health record data, and according to a determination that the first clinical health meets the first set of graphing criteria, a first graphical representation of the first clinical health record based on the clinical health record data, and a second region corresponding to a second type of clinical health record, wherein, according to a determination that a second clinical health record of the second type of clinical health record does not meet the first set of graphing criteria, if the user interface does not include a graphical representation of the second clinical health record, a second text representation of the second clinical health record based on the clinical health record data, and according to a determination that the second clinical health record meets the first set of graphing criteria, a second graphical representation of the second clinical health record based on the clinical health record data, and means for displaying a first user interface including the second region.

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

[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 including a display device is described. In some embodiments, the one or more programs are configured to receive 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, receive a request to display a first user interface, in response to receiving the request, display, via the display device, a first user interface including a first representation based on the first clinical health record data for a first clinical health record of the first type of clinical health record, receive a first user input corresponding to a selection of the first representation while the first user interface is being displayed, in response to receiving the first user input, display, via the display device, a second user interface including a second representation different from the first representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record and a third representation different from the second representation and different from the first type of the first clinical health record for a second clinical health record of the first type of clinical health record, receive a second user input corresponding to a selection of the third representation while the second user interface is being displayed, and in response to receiving the second user input, display, via the display device, a third user interface including a fourth representation different from the first representation and different from the second representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record.

[0023] 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 including a display device is described. In some embodiments, the one or more programs are configured to receive 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, receive a request to display a first user interface, and in response to receiving the request, display via the display device a first user interface including a first representation based on the first clinical health record data for a first clinical health record of the first type of clinical health record; while the first user interface is being displayed, receive a first user input corresponding to a selection of the first representation; and in response to receiving the first user input, display via the display device a second user interface including a second representation different from the first representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record and a third representation different from the second representation and different from the first representation based on the first clinical health record data for a second clinical health record of the first type of clinical health record, where the second clinical health record of the first type is different from the first clinical health record of the first type; while the second user interface is being displayed, receive a second user input corresponding to a selection of the third representation; and in response to receiving the second user input, display via the display device a third user interface including a fourth representation different from the first representation and different from the second representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record.

[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, and the one or more programs are configured to receive 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, receive a request to display a first user interface, in response to receiving the request, display, via the display device, a first user interface including a first representation based on the first clinical health record data for a first clinical health record of the first type of clinical health record, receive a first user input corresponding to a selection of the first representation while the first user interface is being displayed, in response to receiving the first user input, display, via the display device, a second user interface including a second representation different from the first representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record and a third representation different from the second representation and different from the first representation based on the first clinical health record data for a second clinical health record of the first type of clinical health record, where the second clinical health record of the first type is different from the first clinical health record of the first type, receive a second user input corresponding to a selection of the third representation while the second user interface is being displayed, and in response to receiving the second user input, display, via the display device, a third user interface including a fourth representation different from the first representation and different from the second representation based on the first clinical health record data for the first clinical health record of the first type of clinical health record.

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

[0026] According to some embodiments, a method is described. In some embodiments, the method is executed in an electronic device comprising a display device, where the electronic device is associated with a first user account. In some embodiments, the method comprises receiving a request to display a first user interface, and in response to receiving the first request, displaying, via the display device, a first user interface comprising 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 the first user interface is being displayed; receiving a second user input corresponding to a selection of the first shared affordance; in response to receiving the first user input, displaying, via the display device, a second user interface comprising 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 comprising 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 the third user interface is being displayed; and in response to receiving the third user input, displaying, via the display device, a fourth user interface comprising a representation of 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 and comprising a display device is described. In some embodiments, the one or more programs are configured to receive a request to display a first user interface, and in response to receiving the first request, display, 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; while the first user interface is being displayed, receive a first user input corresponding to a selection of the first category affordance; receive a second user input corresponding to a selection of the first shared affordance; in response to receiving the first user input, display, via the display device, a second user interface including a representation of first health data associated with the first user account for a first category; in response to receiving the second user input, display, 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; while the third user interface is being displayed, receive a third user input corresponding to a selection of the second category affordance; and in response to receiving the third user input, display, via the display device, a fourth user interface including a representation of health data associated with the second user account for the first category.

[0028] 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 and comprising a display device is described. In some embodiments, the one or more programs are configured to receive a request to display a first user interface, and in response to receiving the first request, display, via the display device, a first user interface comprising a first portion including a first category affordance and a second portion including a first shared affordance corresponding to a second user account; receive a first user input corresponding to a selection of the first category affordance while the first user interface is being displayed; receive a second user input corresponding to a selection of the first shared affordance; in response to receiving the first user input, display, 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, display, 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; receive a third user input corresponding to a selection of the second category affordance while the third user interface is being displayed; and in response to receiving the third user input, display, via the display device, a fourth user interface including a representation of 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, wherein the one or more programs are configured to receive a request to display a first user interface, and in response to receiving the first request, display, via the display device, a first user interface including a first portion including first category affordances and a second portion including first shared affordances corresponding to a second user account; receive a first user input corresponding to a selection of the first category affordances while the first user interface is being displayed; receive a second user input corresponding to a selection of the first shared affordances; in response to receiving the first user input, display, 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, display, via the display device, a third user interface including a first portion including second category affordances corresponding to health data associated with the second user account for the first category; receive a third user input corresponding to a selection of the second category affordances while the third user interface is being displayed; and in response to receiving the third user input, display, via the display device, a fourth user interface including a representation of 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 in response to receiving the first request, via the display device, a first portion including a first category affordance and a second portion including a first shared affordance corresponding to a second user account, means for displaying a first user interface; while the first user interface is being displayed, means for receiving 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; in response to receiving the first user input, via the display device, means for displaying 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, via the display device, means for displaying 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; while the third user interface is being displayed, means for receiving a third user input corresponding to a selection of the second category affordance; and in response to receiving the third user input, via the display device, means for displaying a fourth user interface including a representation of 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 executed 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, and in response to receiving the request, at a first time, displaying, via the display device, a first notification comprising a first affordance to initiate a process for sharing, when selected, the health data associated with the first electronic device with a second electronic device, receiving a first user input corresponding to the selection of the first affordance while the notification is being displayed, 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 at a second time, displaying, via the display device, a second notification corresponding to the sharing of the health data, the second notification comprising a second affordance to initiate a process for ending, when selected, the sharing of the 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 including a display device is described. In some embodiments, the one or more programs receive a request to share health data associated with the first electronic device, and in response to receiving the request, at a first time, via the display device, display 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; receive a first user input corresponding to the selection of the first affordance while the notification is being displayed; in response to receiving the first user input, initiate a process for sharing the health data associated with the first electronic device with the second electronic device; after receiving the first user input, share the health data associated with the first electronic device with the second electronic device; and at a second time, via the display device, display 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 ending the sharing of the health data associated with the first electronic device with the second electronic device.

[0033] 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 including a display device is described. In some embodiments, the one or more programs receive a request to share health data associated with the first electronic device and, in response to receiving the request, at a first time, display, 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; receive a first user input corresponding to the selection of the first affordance while the notification is being displayed; in response to receiving the first user input, initiate a process for sharing health data associated with the first electronic device with the second electronic device; after receiving the first user input, share health data associated with the first electronic device with the second electronic device; and at a second time, display, 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 ending 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 receiving a request to share health data associated with the first electronic device and, in response to receiving the request, at a first time, displaying, 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; receiving a first user input corresponding to a selection of the first affordance while the notification is being displayed; 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 health data associated with the first electronic device with the second electronic device; and at a second time, displaying, 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 ending the sharing of 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, and in response to receiving the request, at a first time, via the display device, means for displaying a first notification including a first affordance for starting a process for sharing health data associated with the first electronic device with a second electronic device when selected, means for receiving a first user input corresponding to the selection of the first affordance while the notification is being displayed, means for starting a process for sharing health data associated with the first electronic device with the second electronic device in response to receiving the first user input, and after receiving the first user input, sharing health data associated with the first electronic device with the second electronic device and, at a second time, via the display device, means for displaying a second notification corresponding to the sharing of the health data, the second notification including a second affordance for starting a process for ending the sharing of the health data associated with the first electronic device with the second electronic device when selected.

[0036] The executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. The executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0037] Thus, the device is provided with a faster and more efficient method and interface for managing health information and functions, thereby increasing the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface can complement or replace other methods for managing health information and functions.

Brief Description of the Drawings

[0038] To better understand the various embodiments described, the following "Modes for Carrying Out the Invention" should be referred to in conjunction with the following drawings, and like reference numerals refer to corresponding parts throughout the following figures.

[0039]

Figure 1A

[0040]

Figure 1B

[0041]

Figure 2

[0042]

Figure 3

[0043]

Figure 4A

[0044]

Figure 4B

[0045]

Figure 5A

[0046]

Figure 5B

[0047]

Figure 5C

Figure 5D

[0048]

Figure 5E

Figure 5F

Figure 5G

Figure 5H

[0049]

Figure 6A

Figure 6B

Figure 6C

Figure 6D1

Figure 6D2

Figure 6D3

Figure 6D4

Figure 6E

Figure 6F

Figure 6G

Figure 6H

Figure 6I

Figure 6J

Figure 6K1

Figure 6K2

Figure 6L

Figure 6M1

Figure 6M2

Figure 6M3

Figure 6M4

Figure 6N

Figure 6O1

Figure 6O2

Figure 6P1

Figure 6P2

Figure 6Q

Figure 6R1

Figure 6R2

Figure 6S

Figure 6SA

Figure 6SB

Figure 6T1

Figure 6T2

Figure 6U

Figure 6V

Figure 6W

Figure 6X1

Figure 6X2

Figure 6Y

Figure 6Z

[0050]

Figure 7A

Figure 7B

[0051]

Figure 8A

Figure 8B

[0052]

Figure 9A

Figure 9B

[0053]

Figure 10A

Figure 10B

[0054]

Figure 11A

Figure 11B

Figure 11C

[0055]

Figure 12A1

Figure 12A2

Figure 12B1

Figure 12B2

Figure 12C

Figure 12D

Figure 12E

Figure 12F

Figure 12G

Figure 12H

Figure 12I

[0056]

Figure 13A

Figure 13B

Figure 13C

Figure 13D

Figure 13E

Figure 13F

Figure 13G

[0057]

Figure 14A

Figure 14B

[0058]

Figure 15A

Figure 15B

Figure 15C

Figure 15D

Figure 15E

Figure 15F

DETAILED DESCRIPTION OF THE INVENTION

[0059] The following description describes exemplary methods, parameters, etc. However, it should be recognized that such descriptions are not intended as limitations on the scope of the present disclosure, but rather as descriptions of exemplary embodiments.

[0060] There is a need for an electronic device that provides an efficient method and interface for managing health information and functions. For example, it is advantageous to provide health-related notifications in a timely manner and stop the display of useful notifications. In another example, it is advantageous to emphasize specific health-related information to the user. Such techniques can reduce the cognitive burden on the user for managing health information and functions, thereby increasing productivity. Further, such techniques can reduce the power of the processor and battery that would otherwise be wasted on redundant user input.

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

[0062] In the following description, terms such as "first", "second", etc. 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. For example, without departing from the scope of the various embodiments described, the first touch can be called the second touch, and similarly, the second touch can be called the first touch. Both the first touch and the second touch are touches, but they are not the same touch.

[0063] The terms used in the description of the various embodiments described herein are for the sole purpose of describing a particular embodiment and are not intended to be limiting. In the description of the various embodiments described and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" refers to any and all combinations of one or more of the associated listed items and is to be understood to include the same. The terms "includes", "including", "comprises", and / or "comprising", when used herein, specify the presence of the stated feature, integer, step, operation, element, and / or component, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0064] The term "if" is optionally interpreted to mean "when" or "upon", or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are optionally interpreted 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]", depending on the context.

[0065] Embodiments of electronic devices, user interfaces for such devices, and related 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 functionality and / or music player functionality. Exemplary embodiments of portable multifunctional devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as laptop or tablet computers having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad), are also used. Also, in some embodiments, it should be understood that the device is not a portable communication device but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad). 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 content (e.g., video data rendered or decoded by a display controller 156) to be displayed by transmitting data (e.g., image data or video data) over a wired or wireless connection to an integrated or external display generation component for visually generating the content.

[0066] In the following discussion, an electronic device including a display and a touch sensing surface will be described. 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 corresponds to one or more of various applications such as a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a game application, a telephone application, a video conferencing 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 executed on the device optionally use at least one common physical user interface device such as a touch sensing surface. One or more functions of the touch sensing surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each respective application. Thus, the common physical architecture of the device (such as a touch sensing surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

[0069] Attention is now directed to an embodiment of a portable device having a touch-sensing display. FIG. 1A is a block diagram showing a portable multifunctional device 100 having a touch-sensing display system 112 according to some embodiments. The touch-sensing display 112 may be referred to as a "touch screen" for convenience and may be known or referred to as a "touch-sensing display system". The device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more light sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 (e.g., a touch-sensing surface such as the touch-sensing display system 112 of the device 100) for detecting the intensity of contact on the device 100. The device 100 optionally includes one or more haptic output generators 167 for generating haptic output on the device 100 (e.g., generating haptic output on a touch-sensing surface such as the touch-sensing display system 112 of the device 100 or the touch pad 355 of the device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0070] In this specification and the claims, the term "intensity" of a contact on a touch-sensing surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensing surface, or a proxy for the force or pressure of a contact on the touch-sensing surface. The intensity of a contact has a range of values that includes at least four distinct values, and more typically, hundreds (e.g., at least 256) of 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-sensing surface are optionally used to measure the force at various points on the touch-sensing surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the 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-sensing surface. Alternatively, the size and / or change in size of the contact area detected on the touch-sensing surface, the capacitance and / or change in capacitance of the touch-sensing surface proximate to the contact, and / or the resistance and / or change in resistance of the touch-sensing surface proximate to the contact are optionally used as surrogates for the force or pressure of a contact on the touch-sensing surface. In some implementations, alternative measurements for the force or pressure of a contact are used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the alternative measurement). In some implementations, a proxy 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 is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of a contact as an attribute of a user input, a user can access additional device functions that would normally be inaccessible to the user on a device of reduced size with a limited area for displaying affordances (e.g., on a touch-sensing display) and / or receiving user input (e.g., via a touch-sensing display, a touch-sensing surface, or a physical / mechanical control such as a knob or button).

[0071] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensing surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, that will be detected by the user's sense of touch. For example, in a situation where the device or a component of the device is in contact with a touch-sensitive surface of the user (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or the component of the device. For example, movement of a touch-sensing surface (e.g., a touch-sensing display or a trackpad) may optionally be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even when there is no movement of the physical actuator button associated with the touch-sensing surface that has been physically pushed (e.g., displaced) by the user's action. As another example, movement of a touch-sensing surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensing surface, even if there is no change in the smoothness of the touch-sensing surface. Such interpretation of touch by the user is subject to the user's individual sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "up click", "down click", "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component of the device that produces the described sensory perception of a typical (or average) user.

[0072] Device 100 is merely an example of a portable multifunctional device, and it should be understood that device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of those components. The various components shown in FIG. 1A are implemented in a combination of hardware, software, or 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 also 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. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

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

[0075] The RF (radio frequency) circuit 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals or vice versa and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, such as, 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, and the like. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also called the World Wide Web, an intranet, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as with other devices. The RF circuit 108 optionally includes well-known circuits for detecting a near field Communication (NFC) field, such as by a short-range communication radio. Wireless communication optionally includes, but is not limited to only, Global System for Mobile Communications (GSM) for mobile communication, 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-HSPDA), Long Termevolution, LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth (registered trademark), Bluetooth Low Energy (BTLE (registered trademark)), Wireless Fidelity (Wi-Fi (registered trademark)) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX (registered trademark), protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed as of the filing date of this specification.

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

[0077] The I / O subsystem 106 couples input / output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to the peripheral device 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 devices or control devices. The one or more input controllers 160 receive electrical signals from and transmit electrical signals to 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 (or not coupled to any of) a pointer device such as a keyboard, an infrared port, a USB port, and a mouse. One or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of the speaker 111 and / or the microphone 113. One or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch sensing surface (e.g., a trackpad as part of a touch sensing 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) for tracking a user's gesture (e.g., a hand gesture) as an 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] As described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image", and U.S. Patent No. 7,657,849, which are hereby incorporated by reference in their entirety, a quick press of a push button optionally disengages the lock of the touch screen 112 or, optionally, initiates a process of unlocking the device using gestures on the touch screen. A longer press of the push button (e.g., 206) optionally turns the power to the device 100 on or off. 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] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or transmits electrical signals to the touch screen 112. The touch screen 112 displays a visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

[0081] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although in other embodiments other display technologies are also used. The touch screen 112 and the display controller 156 optionally use any of a plurality of touch sensing technologies, now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112, to detect contact and any movement or interruption thereof. In an exemplary embodiment, projection type mutual capacitance sensing technology, such as that found in the iPhone (registered trademark) and iPod Touch (registered trademark) from Apple Inc. of Cupertino, California, is used.

[0082] The touch-sensing display in some embodiments of the touch screen 112 is optionally similar to a multi-touch sensing touch pad as 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 hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, whereas the touch-sensing touch pad does not provide visual output.

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

[0084] The touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally touches 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 contact and gestures, but this may be less precise than stylus-based input because the contact area of the finger on the touch screen is larger. In some embodiments, the device converts rough input by the finger into an accurate pointer / cursor position or command for performing the action desired by the user.

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

[0086] The device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), 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 a light sensor controller 158 within I / O subsystem 106. The light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. The light sensor 164 cooperates with an imaging module 143 (also referred to as a camera module) to optionally capture a still image or video. In some embodiments, the light sensor is located on the back surface of device 100 opposite a touch screen display 112 on the front surface of the device, and thus the touch screen display is effective to be used as a viewfinder for obtaining still and / or video images. In some embodiments, the light sensor is disposed on the front surface of the device, and thus an image of the user is optionally obtained for a video conference and the user views other video conference participants on the touch screen 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), and thus a single light sensor 164 is used both for video conferencing and for obtaining still and / or video images together with the touch screen display.

[0088] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to a depth camera controller 169 within I / O subsystem 106. The depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine depth maps of various portions of an image captured by imaging module 143. In some embodiments, while a user is viewing other video conference participants on a touch screen display, an image of the user with depth information is optionally acquired for a video conference and a self-portrait image with depth map data is captured, and a depth camera sensor is disposed on the front face of device 100. In some embodiments, the depth camera sensor 175 is disposed on the back face of the device or on both the back and front faces 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 for acquiring still and / or video images with the 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 an intensity sensor controller 159 within I / O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric force sensors, optical force sensors, capacitive touch sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch sensing surface). The 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 sensing surface (e.g., touch sensing display system 112). In some embodiments, at least one contact intensity sensor is disposed on the back of device 100, on the opposite side of touch screen display 112 disposed on the front of device 100.

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

[0091] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 within I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert an electrical signal into a haptic output on the device), into linear movement. The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates haptic output on the device 100 that can be sensed by a user of the device 100. In some embodiments, at least one haptic output generator is juxtaposed with or proximate to a touch sensing surface (e.g., touch sensing display system 112) and optionally generates haptic output by moving the touch sensing surface in a vertical direction (e.g., in / out of the surface of device 100) or a horizontal direction (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is disposed on the back of device 100, opposite a touch screen display 112 disposed on the front of device 100.

[0092] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows an accelerometer 168 coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to an input controller 160 within the I / O subsystem 106. The accelerometer 168 functions as described, for example, 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 hereby incorporated by reference in their entirety. In some embodiments, information is displayed on the touch screen display in portrait or landscape view based on analysis of data received from one or more accelerometers. In addition to the 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 an application (or instruction set) 136. Further, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores a device / global internal state 157 as shown in FIGS. 1A and 3. The device / global internal state 157 includes one or more of an active application state indicating which application is active if there is a currently active application, a display state indicating which application, view, or other information occupies various regions of the touch screen display 112, a sensor state including information obtained from various sensors and input control devices 116 of the device, and position information regarding the position and / or orientation of the device.

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

[0095] The communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE (registered trademark), etc.) are adapted to couple to other devices either directly or indirectly via a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as or similar to and / or is adapted to the 30-pin connector used on iPod (registered trademark) devices (a trademark of Apple Inc.).

[0096] The contact / motion module 130 optionally detects contact with the touch screen 112 (in cooperation with the display controller 156) and other touch-sensing devices (e.g., a touch pad or a physical click wheel). The contact / motion module 130 performs various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting an event of a finger being lowered), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to the force or pressure of the contact), determining whether there is movement of the contact, tracking movement across the touch-sensing surface (e.g., detecting one or more events of a finger being dragged), and determining whether the contact has stopped (e.g., detecting an event of a finger being raised or an interruption of the contact). The contact / motion module 130 includes various software components for performing these various operations. The contact / motion module 130 receives contact data from the touch-sensing surface. Determining the movement of the contact point, represented by a 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 point. These operations are optionally applied to a single contact (e.g., contact with one finger) or multiple simultaneous contacts (e.g., "multi-touch" / contact with multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.

[0097] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., to determine whether the user has "clicked" on an icon). In some embodiments, at least one subset of the intensity thresholds is determined according to software parameters (e.g., the intensity thresholds can be adjusted without changing the physical hardware of the device 100, rather than being determined by the activation thresholds of specific physical actuators). For example, the mouse "click" threshold of a trackpad or touch screen display can be set to any of a wide range of default thresholds without changing the trackpad or touch screen display hardware. Additionally, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or adjusting multiple intensity thresholds at once with a system-level click "intensity" parameter).

[0098] The contact / motion module 130 optionally detects gesture inputs by the user. Different gestures on the touch-sensing surface have different contact patterns (e.g., the detected movement, timing, and / or intensity of the contact is different). Thus, gestures are optionally detected by detecting a specific 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 position (or substantially the same position) (e.g., the position of the icon) as the finger down event. As another example, detecting a finger swipe gesture on the touch-sensing surface includes detecting a finger down event, followed by detecting one or more finger drag events, and then followed by detecting a finger up (lift-off) event.

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

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

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

[0102] The text input module 134 is optionally a component of the graphic 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 that requires 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 location-based dialing, to the camera 143 as metadata for photos / videos, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map / navigation widgets).

[0104] The application 136 optionally includes the following modules (or sets of instructions) or subsets or supersets thereof. ● Contact module 137 (sometimes called an address book or contact list), ● Phone module 138, ● Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ● Training support module 142, ● 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, ● Widget module 149 that optionally includes one or more of weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widget 149-6, ● Widget creation module 150 for creating user-created widget 149-6, ● Search module 151, ● Video and music player module 152 that integrates the video player module and the music player module ● Memo module 153, ● Map module 154, and / or, ● Online video module 155.

[0105] Examples of other applications 136 optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA (registered trademark)-compatible applications, encryption, digital rights management, voice recognition, and voice replication.

[0106] In cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the contact module 137 is optionally used to add name(s) to the address book, delete name(s) from the address book, associate a phone number(s), an email address(es), a physical address(es), or other information with a name, associate an image with a name, classify and sort names, provide a phone number or email address to initiate and / or facilitate communication by phone 138, video conferencing module 139, email 140, or IM 141, etc., to manage the address book or contact list (e.g., stored in the internal state 192 of the contact module 137 application within the memory 102 or memory 370).

[0107] In cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the telephone module 138 is optionally used for input of a character sequence corresponding to a telephone number, access to one or more telephone numbers in the contact module 137, modification of an input telephone number, dialing of each telephone number, conducting a conversation, and call termination or hang-up when the conversation ends. As described above, the wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies.

[0108] In cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphic module 132, the text input module 134, the contact module 137, and the telephone module 138, the videoconference module 139 includes executable instructions for starting, executing, and ending a videoconference between the user and one or more other participants according to a user command.

[0109] In cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to a user command. In cooperation with the image management module 144, the email client module 140 facilitates the creation and sending of emails having still images or video images captured by the camera module 143.

[0110] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, the instant messaging module 141 includes executable instructions for inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting each instant message (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for instant messages based on telephone communication, or XMPP, SIMPLE, or IMPS for instant messages based on the Internet), receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages transmitted and / or received optionally include graphics, photos, audio files, video files, and / or other attached files supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone communication-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).

[0111] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 creates training (e.g., having time, distance, and / or calorie burn goals), communicates with a training sensor (sports device), receives training sensor data, calibrates sensors used to monitor the training, selects and plays music for the training, and includes executable instructions for displaying, storing, and transmitting training data.

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

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

[0114] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, the browser module 147 includes executable instructions for browsing the Internet according to user commands, including searching for, linking to, receiving, and displaying a web page or a portion thereof, as well as attached files and other files linked to the web page.

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

[0116] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and browser module 147, the widget module 149 is 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 optionally downloaded and used by the user, or a mini-application created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).

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

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

[0119] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, video and music player module 152 includes executable instructions that enable a user to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing video (e.g., on touch screen 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 (trademark of Apple Inc.).

[0120] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, memo module 153 includes executable instructions for creating and managing memos, to do lists, etc. according to user instructions.

[0121] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data regarding stores and other target locations near or at a particular location, and other location-based data) according to user instructions.

[0122] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 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 a particular online video, browse a particular online video, receive (e.g., by streaming and / or downloading), play (e.g., on the touch screen or on an external display connected via external port 124), send an email having a link to a particular online video, and perform other management of online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video. Additional explanation of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", the contents of which are hereby incorporated by reference in their entirety.

[0123] The modules and applications identified above each correspond to a set of executable instructions that perform one or more of the functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (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 may optionally be combined or otherwise reconfigured. For example, the video player module may optionally be combined with the music player module to form a single module (e.g., the video and music player module 152 of FIG. 1A). In some embodiments, the memory 102 optionally stores a subset of the modules and data structures identified above. Further, the memory 102 optionally stores additional modules and data structures not described above.

[0124] In some embodiments, the device 100 is a device in which the operation of a set of default functions in the device is performed only via the touch screen and / or touch pad. By using the touch screen and / or touch pad as the main input control device for the device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on the device 100 is optionally reduced.

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

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

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

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

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

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

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

[0132] The hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred when the touch-sensitive display 112 displays two or more views. A view is composed of control devices and other elements that a user can view on the display.

[0133] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, within which information is displayed and touch-based gestures occur. The application views (for each respective application) where touches are detected optionally correspond to a program level within the program hierarchy or view hierarchy of the application. For example, the lowest-level view where a touch is detected is optionally referred to as the hit view, and the set of events recognized as appropriate input is optionally determined based at least in part on the hit view of the initial touch that initiates a touch-based gesture.

[0134] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When the application has a plurality of hierarchically structured views, the hit view determination module 172 identifies the hit view as the lowest-level view within the hierarchy in which the sub-events are to be processed. In most situations, the hit view is the lowest-level view where the start sub-event (e.g., the first sub-event within a sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, this hit view typically receives all sub-events related to the same touch or input source as that identified as the hit view.

[0135] The active event recognition unit determination module 173 determines which view(s) within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views including the physical location of the sub-event are views that are actively involved, and thus determines that all views that are actively involved should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely limited to an area associated with one particular view, the upper-level views within the hierarchy continue to be views that are actively involved.

[0136] The event dispatcher module 174 dispatches event information to the event recognition unit (e.g., event recognition unit 180). In embodiments including the active event recognition unit determination module 173, the event dispatcher module 174 distributes event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information obtained by each event receiver 182 in the event queue.

[0137] In some embodiments, the operating system 126 includes the event sorter 170. Alternatively, the application 136-1 includes the event sorter 170. In still other embodiments, the event sorter 170 is an independent module or is part of another module stored in the memory 102 such as the touch / motion module 130.

[0138] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions for processing touch events that occur within respective views of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 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 processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorter 170. The event processing unit 190 optionally utilizes or invokes the data update unit 176, object update unit 177, or GUI update unit 178 to update the internal state 192 of the application. Alternatively, one or more of the application views 191 include one or more respective event processing units 190. Also, in some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included in respective application views 191.

[0139] Each event recognition unit 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from this event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparing unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution instructions 188 (optionally including sub-event distribution instructions).

[0140] The event receiving unit 182 receives event information from the event sorter 170. The event information includes sub-events, for example, information about a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information such as the position of the sub-event. When the sub-event is related to the 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 posture of the device).

[0141] The event comparison unit 184 compares the event information with the definition of a defined event or sub-event, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 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, the sub-events within an event (187) include, for example, a touch start, a touch end, a touch movement, a touch cancellation, and multiple touches. In one example, the definition of event 1 (187-1) is a double-tap on a displayed object. The double-tap includes, for example, a first touch (touch start) on the displayed object for a predetermined stage, a first lift-off (touch end) for the predetermined stage, a second touch (touch start) on the displayed object for the predetermined stage, and a second lift-off (touch end) for the predetermined stage. In another example, the definition of event 2 (187-2) is a drag on a displayed object. The drag includes, for example, a touch (or contact) on the displayed object for a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event processing units 190.

[0142] In some embodiments, event definition 187 includes the definition of events for each user interface object. In some embodiments, event comparison unit 184 performs a hit test to determine which user interface object is associated with the sub - event. For example, within an application view where three user interface objects are displayed on touch - sensitive display 112, when a touch is detected on touch - sensitive display 112, event comparison unit 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 processing unit 190, the event comparison unit uses the result of the hit test to determine which event processing unit 190 should be activated. For example, event comparison unit 184 selects the event processing unit associated with the sub - event and object that triggered the hit test.

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

[0144] If each event recognition unit 180 determines that a series of sub - events does not match any of the events in event definition 186, each event recognition unit 180 enters a state of event - impossible, event - failed, or event - ended, and then ignores the next sub - event of the touch - based gesture. In this situation, if there are other event recognition units that remain active for the hit view, that event recognition unit continues to track and process the sub - events of the ongoing touch - based gesture.

[0145] In some embodiments, each event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event distribution system should actively participate in executing sub-event distribution to the event recognition units involved. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how the event recognition units interact with each other or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub-events are distributed to various levels in the view hierarchy or program hierarchy.

[0146] In some embodiments, each event recognition unit 180 activates the event processing unit 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognition unit 180 distributes the event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and deferring sending) sub-events to each hit view. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with that flag captures the flag and executes a predefined process.

[0147] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about sub-events without activating the event processing unit. Instead, the sub-event distribution command distributes the event information to the event processing unit associated with a series of sub-events or to the view actively involved. The event processing unit associated with a series of sub-events or the view actively involved receives the event information and executes a predetermined process.

[0148] In some embodiments, data update unit 176 creates and updates data used in application 136-1. For example, data update unit 176 updates a phone number used in contact module 137 or stores a video file used in a video player module. In some embodiments, object update unit 177 creates and updates objects used in application 136-1. For example, object update unit 177 creates a new user interface object or updates the position of a user interface object. GUI update unit 178 updates the GUI. For example, GUI update unit 178 prepares display information and sends the display information to graphic module 132 for display on a touch-sensitive display.

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

[0150] The foregoing description regarding event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunctional device 100 using an input device, it being understood that not all of them are initiated on a touch screen. For example, movement of a mouse and pressing of a mouse button, movement of a contact such as a tap, drag, scroll on a touch pad, pen stylus input, movement of the device, spoken commands, detected eye movement, biometric input, and / or any combination thereof, optionally in association with a single or multiple presses or holding of a keyboard, are utilized as input corresponding to sub-events that define events to be optionally recognized.

[0151] FIG. 2 shows a portable multifunctional device 100 having a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as well as in other embodiments described below, the user can select one or more of those graphics by performing gestures on the graphics using, for example, one or more fingers 202 (not drawn to scale in the figure) or one or more styli 203 (not drawn to scale in the figure). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with the one or more graphics. In some embodiments, the gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, from left to right, upward and / or downward). In some implementations or situations, an unexpected contact with a graphic does not select that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon does not optionally select the corresponding application.

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

[0153] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding it down for a predefined period, to lock the device by pressing the button and releasing it before a predefined time has elapsed, and / or to unlock the device or initiate an unlock process. In alternative embodiments, device 100 also accepts verbal input via a 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 contact on the touch screen 112 and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.

[0154] FIG. 3 is a block diagram of an exemplary multi-functional device having a display and a touch sensing 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 business controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks or other communication interfaces 360, memory 370, and one or more communication buses 320 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes an input / output (I / O) interface 330 that includes a display 340, which is typically a touch screen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touch pad 355, a tactile output generator 357 that generates tactile outputs on device 300 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A), and a sensor 359 (e.g., a light, acceleration, proximity, touch sensing, and / or contact intensity sensor 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 the CPU(s) 310.In some embodiments, the memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in the memory 102 of the portable multifunctional device 100 (FIG. 1A). Further, the memory 370 optionally stores additional programs, modules, and data structures that do not exist in the memory 102 of the portable multifunctional device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, whereas the memory 102 of the portable multifunctional device 100 (FIG. 1A) optionally does not store these modules.

[0155] Each of the elements identified above in FIG. 3 is optionally stored in one or more of the memory devices described above. Each of the modules identified above corresponds to a set of instructions for performing the functions described above. The modules or programs (e.g., sets of instructions) identified above 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, the memory 370 optionally stores a subset of the modules and data structures identified above. Further, the memory 370 optionally stores additional modules and data structures not described above.

[0156] Next, attention is optionally directed to embodiments of a user interface that are implemented, for example, on the portable multifunctional device 100.

[0157] Figure 4A shows an exemplary user interface of a menu of applications on a portable multifunctional device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof. ● One or more signal strength indicators (s) 402 for wireless communication (s) such as cellular signal and Wi-Fi® signal, ● Time 404, ● Bluetooth® indicator 405, ● Battery status indicator 406, ● A tray 408 having icons of frequently used applications such as ○ An icon 416 of the phone module 138 labeled "Phone", optionally including an indicator 414 of the number of missed calls or voice mail 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 of the browser module 147 labeled "Browser", and ○ An icon 422 of the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod", and ● Icons of other applications such as ○ An icon 424 of the IM module 141 labeled "Message", ○ An icon 426 of the calendar module 148 labeled "Calendar", ○ An icon 428 of the image management module 144 labeled "Photos", ○ An icon 430 of the camera module 143 labeled "Camera", ○ An icon 432 of the online video module 155 labeled "Online Video", ○ An icon 434 of the stock price widget 149-2, labeled with "Stock Price", ○ An icon 436 of the map module 154, labeled with "Map", ○ An icon 438 of the weather widget 149-1, labeled with "Weather", ○ An icon 440 of the alarm clock widget 149-4, labeled with "Clock", ○ An icon 442 of the training support module 142, labeled with "Training Support", ○ An icon 444 of the memo module 153, labeled with "Memo", and ○ An icon 446 of the settings application or module, labeled with "Settings", which provides access to the settings for the device 100 and its various applications 136.

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

[0159] FIG. 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) having a touch sensing surface 451 (e.g., the tablet or touch pad 355 of FIG. 3) separate from the display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the touch sensing surface 451, and / or one or more tactile output generators 357 for generating tactile output to the user of the device 300.

[0160] Some of the following examples are given with reference to inputs on the touch screen display 112 (where the touch sensing surface and the display are combined), but in some embodiments, the device detects inputs on a touch sensing surface separate from the display shown in FIG. 4B. In some embodiments, the touch sensing surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) corresponding to the primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in FIG. 4B) with the touch sensing surface 451 at locations corresponding to each location on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462 and their movements) detected by the device on the touch sensing surface (e.g., 451 in FIG. 4B) are used by the device to operate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunctional device when the touch sensing surface is separate from the display. It should be understood that a similar method is optionally used for other user interfaces described herein.

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

[0162] FIG. 5A shows an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, the 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, the device 500 has a touch-sensitive display screen 504, hereinafter referred to as touch screen 504. Alternatively, or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of the device 500 can respond to the touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on the device 500.

[0163] Exemplary techniques for detecting and processing touch intensity can be found in related applications such as International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, published as International Patent No. WO / 2013 / 169849, "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", and International Patent Application No. PCT / US2013 / 069483, filed Nov. 11, 2013, published as International Patent No. WO / 2014 / 105276, "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 enable 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 enable the user to wear device 500.

[0165] FIG. 5B shows an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. 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). Additionally, 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 an input mechanism 506 and / or 508. The input mechanism 506 can optionally be, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 can optionally be a button.

[0166] In some examples, the input mechanism 508 can optionally be a microphone. The personal electronic device 500 can optionally include various sensors such as a GPS sensor 532, an accelerometer 534, a direction sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which can be operably 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 storing computer-executable instructions that, when executed by one or more computer processors 516, can cause the computer processor to execute 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 media can be any media that tangibly contains or stores computer-executable instructions for use by or connected to an instruction execution system, apparatus, or device. In some embodiments, the storage media is a transitory computer-readable storage media. In some embodiments, the storage media is a non-transitory computer-readable storage media. Non-transitory computer-readable storage media can 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 (registered trademark) technology, as well as persistent solid-state memories such as flash, solid-state drives. The personal electronic device 500 is not limited to the components and configurations of FIG. 5B and can include other or additional components in a plurality of configurations.

[0168] As used herein, the term "affordance" optionally refers to user interaction graphical user interface objects displayed on the display screens of devices 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] As used herein, the term "focus selector" refers to an input element that indicates the current part of the user interface with which the user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as the "focus selector," and thus while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), 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), the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 of FIG. 1A or touch screen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, the detected contact on the touch screen acts as the "focus selector," and thus 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 touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without movement of a corresponding cursor or movement of the contact on the touch screen display (e.g., by using the tab key or arrow keys to move the focus from one button to another), and in these implementations, the focus selector moves in accordance with the movement of the focus between various areas of the user interface. Regardless of the particular form the focus selector takes, the focus selector is generally a user interface element (or a contact on the touch screen display) that is controlled by the user (e.g., by indicating to the device the element of the user interface with which the user intends to interact) so as to communicate the user's intended interaction to the user interface.For example, while a press input is detected on a touch sensing surface (e.g., a touch pad or a touch screen), the position of a focus selector (e.g., a cursor, a contact, or a selection box) over the corresponding button indicates that the user intends to activate that corresponding button (as opposed to other user interface elements shown on the device's display).

[0170] As used in this specification and the claims, the term "characteristic strength" of a contact refers to the characteristics of that contact based on one or more strengths of the contact. In some embodiments, the characteristic strength is based on a plurality of strength samples. The characteristic strength is optionally based on a set of strength samples collected during a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) related to a predetermined number of strength samples, i.e., a predetermined event (e.g., after detecting the contact, before detecting the lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the strength of the contact, and / or before or after detecting a decrease in the strength of the contact). The characteristic strength of a contact is optionally based on one or more of the maximum value of the strength of the contact, the mean value of the strength of the contact, the average value of the strength of the contact, the top 10 percentile value of the strength of the contact, the median value of the strength of the contact, the top 90 percent value of the strength of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic strength (e.g., when the characteristic strength is the average of the strength of the contact over time). In some embodiments, the characteristic strength is compared to a set of one or more strength thresholds to determine whether an operation has been performed by a user. For example, a set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact having a characteristic strength that does not exceed the first threshold results in a first operation, a contact having a characteristic strength that exceeds the first threshold but does not exceed the second threshold results in a second operation, and a contact having a characteristic strength that exceeds the second threshold results in a third operation. In some embodiments, the comparison between the characteristic strength and one or more thresholds is not used to determine whether to perform a first operation or a second operation, but is used to determine whether to perform one or more operations (e.g., whether to perform each operation or whether to refrain from performing each operation).

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

[0172] In some embodiments, for the purpose of determining characteristic intensity, a portion of the gesture is specified. For example, the touch sensing surface optionally receives continuous swipe contacts that transition from a starting location to reach an ending location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the ending location is optionally based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the ending location) rather than the entire swipe contact. In some embodiments, optionally, a smoothing algorithm is applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of a non-weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate small increases or decreases in the intensity of the swipe contact for the purpose of determining the characteristic intensity.

[0173] The intensity of a contact on the touch sensing surface is optionally characterized relative to one or more intensity thresholds such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold typically corresponds to the intensity at which the device performs an operation associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold typically corresponds to the intensity at which the device performs an operation different from the operation associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact 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) is detected, the device moves the focus selector in accordance with the movement of the contact on the touch sensing surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent among various sets of user interface diagrams.

[0174] An increase in the characteristic strength of a contact from a strength below a light press strength threshold to a strength between the light press strength threshold and a deep press strength threshold may be referred to as an input of "light press". An increase in the characteristic strength of a contact from a strength below a deep press strength threshold to a strength above the deep press strength threshold may be referred to as an input of "deep press". An increase in the characteristic strength of a contact from a strength below a contact detection strength threshold to a strength between the contact detection strength threshold and the light press strength threshold may be referred to as a detection of a contact on the touch surface. A decrease in the characteristic strength of a contact from a strength above the contact detection strength threshold to a strength below the contact detection strength threshold may be referred to as a detection of a lift-off of the contact from the touch surface. In some embodiments, the contact detection strength threshold is zero. In some embodiments, the contact detection strength threshold is greater than zero.

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

[0176] Figures 5E - 5H show an increase in strength from below the light press strength threshold of Figure 5E (e.g., "IT L ") to the deep press strength threshold of Figure 5H (e.g., "IT DIt shows the detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 to an intensity exceeding 」). The gesture executed by contact 562 is detected on the touch sensing surface 560, and on the display user interface 570 including application icons 572A to 572D displayed within a predetermined region 574, a cursor 576 is displayed above the application icon 572B corresponding to App 2. In some embodiments, the gesture is detected on the touch sensing display 504. The intensity sensor detects the intensity of the contact on the touch sensing surface 560. The device determines that the intensity of contact 562 has reached a peak exceeding the intensity threshold of a deep press (e.g., 「IT D 」). Contact 562 is maintained on the touch sensing surface 560. In response to the detection of the gesture, in accordance with contact 562 having an intensity exceeding the intensity threshold of a deep press (e.g., 「IT D 」) during the gesture, as shown in FIGS. 5F to 5H, reduced-scale representations 578A to 578C (e.g., thumbnails) of the most recently opened documents for App 2 are displayed. In some embodiments, this intensity compared to one or more intensity thresholds is the characteristic intensity of the contact. Note that the intensity diagram for contact 562 is included in FIGS. 5E to 5H to assist the reader, not as part of the display user interface.

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

[0178] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes called "jitter", and the device defines or selects a hysteresis intensity threshold having a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of each contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and each operation is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., the "upstroke" of each press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and each operation is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact depending on the situation).

[0179] For ease of explanation, the description of an operation performed in response to a pressing input associated with a pressing input strength threshold, or a gesture including the pressing input, is optionally triggered in response to detecting any of an increase in the intensity of contact exceeding the pressing input strength threshold, an increase in the intensity of contact from an intensity below the hysteresis strength threshold to an intensity exceeding the pressing input strength threshold, a decrease in the intensity of contact below the pressing input strength threshold, and / or a decrease in the intensity of contact below the hysteresis strength threshold corresponding to the pressing input strength threshold. Further, in an example where the operation is described to be performed in response to detecting a decrease in the intensity of contact below the pressing input strength threshold, the operation is optionally performed in response to detecting a decrease in the intensity of contact below a hysteresis strength threshold corresponding to and lower than the pressing input strength 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 be launched (e.g., opened) on the device. In some embodiments, the downloaded application becomes an installed application by an installation program that extracts a program portion from the downloaded package and integrates the extracted portion with the operating system of the computer 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. ● An active application currently displayed on the display screen of the device being used by the application ● Background applications (or background processes) for which one or more processes for an application are being processed by one or more processors, although not currently being displayed, and ● Interrupted or suspended applications that are not running but are stored in memory (volatile and non-volatile respectively) and have state information 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 the state information for the application from the device's memory. Generally, opening a second application while a first application is open does not close the first application. When the second application is being displayed and the first application has its display terminated, the first application becomes a background application.

[0183] Next, attention is directed to embodiments of a user interface ("UI") and related processes implemented on an electronic device such as the portable multifunctional device 100, device 300, or device 500.

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

[0185] FIG. 6A shows a first electronic device 600 (e.g., a phone) that displays a lock user interface 604 via a touch sensing display device 602 at a first time (e.g., 9:45). In some embodiments, the first electronic device 600 includes one or more features of device 100, 300, or 500.

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

[0187] In some embodiments, notification 604a is issued by an activity process corresponding to an activity application (as indicated by icon 604aa). In some embodiments, the user interface element corresponding to the 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 at which notification 604a was issued (e.g., time 604ad indicating "now" which refers to 9:45), and (2) an explanation regarding the reason why notification 604a was issued (e.g., 604ac).

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

[0189] FIG. 6B shows a second electronic device 606 (e.g., a wristwatch) that displays a notification 610 via a touch-sensitive display device 608 at a second time (e.g., 10:24) after a first time. In some embodiments, the second electronic device 606 includes one or more features of the 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 an auditory process corresponding to an auditory application (such as that indicated by the icon 610a) running on the second electronic device 606. In some embodiments, the user interface element corresponding to the auditory 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 an explanation regarding the reason why the notification 610 was issued (e.g., 610b).

[0191] FIG. 6C shows a first electronic device 600 that displays a home user interface 612 via a touch sensing display device 602 at a third time after a 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 starting a health application and / or displaying a user interface of the health application.

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

[0193] Figures 6DA - 6DD illustrate a first electronic device 600 that displays a summary user interface 614 via a touch - sensing display device 602 at a fourth time after a third time. In some embodiments, the summary user interface 614 is a user interface of a health application. As shown in FIGS. 6DA - 6DD, the summary user interface 614 includes a plurality of regions with different affordances. The regions include a notification region (e.g., a notification region including a first notification affordance 616, a second notification affordance 618, and a third notification affordance 620), a logging region (e.g., a logging region including a logging affordance 622), a favorites region (e.g., a favorites region including 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 sixth favorites affordance 626f, and showing all health data affordances 628), a highlighting region (e.g., a highlighting region including a first highlighting affordance 630, a second highlighting affordance 632, and showing all highlighting affordances 634), a health record region (e.g., a health record region including a first health record affordance 636, a second health record affordance 638, and showing all record affordances 640), an education region, more information from the health region, and an app region.

[0194] In some embodiments, the notification area includes affordances of 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., notifications 604a and 604b as shown in FIG. 6A) or another electronic device (e.g., the second electronic device 606) linked to the first electronic device 600 or the account (e.g., notification 610 as shown in FIG. 6B), where both are logged into a single account or pairing, such as executed by a smartphone and a corresponding smartwatch. In such embodiments, the notification area is a place to display information associated with health-related notifications in one place that can be viewed after the health-related notifications are first 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 embodiments, the first notification affordance 616 corresponds to (e.g., includes information for) notification 610. In some embodiments, the second notification affordance 618 corresponds to (e.g., includes information for) notification 604a. In some embodiments, the third notification affordance 620 corresponds to (e.g., includes information for) notification 604b. As shown in FIG. 6DA, the notification affordances within the notification area are ordered by the date on which the corresponding notifications were first issued (e.g., the most recent notification is first, the next most recent notification is next, etc.).

[0196] In some embodiments, the notification affordance is removed from the notification area after a certain amount of time has elapsed. In some embodiments, the certain amount of time varies based on the amount of user interaction associated with each notification affordance, or data associated with the affordance. For example, a first notification affordance is removed more quickly than a second notification affordance if the first notification affordance (or the 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 embodiment, a first notification affordance is removed more quickly than a second notification affordance when the first notification affordance (or the notification corresponding to the first notification affordance) is displayed for a longer period of time than the second notification affordance (or the notification corresponding to the second notification affordance). In another embodiment, a first notification affordance is removed more quickly than a 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 the type of health data associated with the second notification affordance (or the notification corresponding to the second notification affordance). In another embodiment, a first notification affordance is removed more quickly than a 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. In another embodiment, a first notification affordance is removed more quickly than a second notification affordance if the 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 FIGS. 6F-6H.

[0197] The first notification affordance 616 includes an icon 616a representing an application (e.g., an auditory application) by which a notification (e.g., notification 610) corresponding to the first notification affordance 616 has been issued. The first notification affordance 616 includes a header that is visually distinguishable from the remainder of the first notification affordance 616, and the header includes a title 616b (indicating which first notification affordance 616 is relevant) and a time 616c (indicating the time at which the notification corresponding to the first notification affordance 616 was first 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 auditory use. In some embodiments, user interface elements related to auditory use include elements that are a particular pattern or color. As shown in FIG. 6DA, the first notification affordance 616 includes content 616d that is at least a portion of the content included in the notification corresponding to the first notification affordance 616 (in some embodiments).

[0198] The second notification affordance 618 includes an icon 618a that indicates 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 distinguishable from the remainder of the second notification affordance 618 (and visually distinguishable from the headers of the first notification affordance 616 and the third notification affordance 620), the header including a title 618b (indicating which second notification affordance 618 is relevant) and a time 618c (indicating the time at which the notification corresponding to the second notification affordance 618 was first 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 related to 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 embodiments).

[0199] The third notification affordance 620 includes an icon 620a that indicates 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 distinguishable from the rest of the third notification affordance 620 (and visually distinguishable from the headers of the first notification affordance 616 and the second notification affordance 618), the header including a title 620b (indicating which third notification affordance 620 is relevant) and a time 620c (indicating the time at which the notification corresponding to the third notification affordance 620 was first issued). In one embodiment, the header is visually distinguished from other elements by being a specific pattern or color corresponding to the CHR application. In some embodiments, user interface elements related to the CHR application include elements that are a specific pattern or color. As shown in FIG. 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 institution 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 embodiments, selection of a notification affordance causes a user interface of a health application to be displayed, the user interface being 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, the user interface including information from an auditory application (which may also be referred to as an auditory data room, as shown in FIG. 6E and further described below).

[0201] In some embodiments, the logging area includes affordances for recording data. For example, logging affordance 622 is related to recording of cycles. Logging affordance 622 includes an icon 622a representing a logging application (e.g., a cycle tracking application) corresponding to logging affordance 622. Logging affordance 622 also includes content 622b describing logging affordance 622 and indicating that the user has recorded information associated with the logging application. Logging affordance 622 also includes a graphic 622c indicating whether a logging criterion is met (e.g., when the logging criterion is not met, graphic 622c is a plus sign indicating that the user has not recorded the minimum number of times, and when the logging criterion is met, graphic 622c is a checkmark indicating that the user has recorded the minimum number of times). In some embodiments, logging affordance 622, when selected, causes a user interface to be displayed that enables the user to record a cycle. In other embodiments, the act of selecting logging affordance 622 causes a cycle to be recorded.

[0202] In some embodiments, a color or pattern associated with a portion of logging affordance 622 (e.g., the font color of the word "cycle tracking") is a specific color or pattern corresponding to the logging application. The specific color or pattern is, in some embodiments, used for at least a portion of user elements displayed within a health application corresponding to the logging application. In some embodiments, the specific color or pattern is visually different from colors / patterns used in other applications (e.g., an activity application, an auditory application, a CHR application, or other logging applications).

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

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

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

[0206] As shown in FIG. 6DA, the first favorite affordance 626a includes a timestamp of the health data 626ac (e.g., movement, exercise, and standing metrics) for the last period of time.

[0207] As shown in FIG. 6DB, the fourth favorite affordance 626d includes an icon 626da that is a smaller version of the icon 622a shown in FIG. 6DA. Such correspondence indicates that, in some embodiments, different user interface elements related to the same application include the same icon for representing the application. Icons 626ea and 626fa are further examples of icons corresponding to different applications. Additionally, in some embodiments, the title 626db is colored in the same way as "Cycle Tracking" within the content 622b, further indicating that both are related to the same application.

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

[0209] In some embodiments, the highlighted region includes a graphical representation of health data over a period of time identified by the health application. For example, a particular graphical representation is displayed when it meets the highlighting criteria and is not displayed when it does not meet the highlighting criteria. In some embodiments, the highlighting criteria are based on the differences between health data within the period, the time the user spent viewing a particular graphic, the user's interaction with a particular graphic or element of the interface 614, or any combination thereof.

[0210] FIG. 6DB shows an electronic device that displays a first highlighted affordance 630 within a highlighted area of a summary user interface 614 via a touch sensing display device 602. The first highlighted affordance 630 includes an icon 630a that indicates that the first highlighted affordance 630 is primarily related to a heart rate application (in some embodiments, the first highlighted affordance 630 is secondarily related to a second application (e.g., a training application) such that the first highlighted affordance 630 is based on data from the second application). In some embodiments, a portion of the first highlighted affordance 630 is visually distinct (e.g., in some embodiments, the font color of the title 630b is a specific color corresponding to the heart rate application) to identify that the first highlighted affordance 630 is primarily related to the heart rate application. The first highlighted affordance 630 also includes an explanation 630c for indicating the information represented by the first highlighted affordance 630 (e.g., a range of values reached during training, etc.).

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

[0212] FIG. 6DC shows an electronic device that displays a second highlighting affordance 632 within the highlighted area of the summary user interface 614 via a touch-sensitive display device 602. The second highlighting affordance 632 includes an icon 630a that indicates that the second highlighting affordance 632 is related to an ambient audio application. In some embodiments, a portion of the second highlighting affordance 632 is visually distinct (e.g., in some embodiments, the font color of the title 632b is a specific color corresponding to the ambient audio application) to identify that the second highlighting affordance 632 is related to the ambient audio application. The second highlighting affordance 632 also includes an explanation 632c for indicating the information represented by the second highlighting affordance 632 (e.g., how the average ambient audio level today 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 representation of today's average (e.g., 632d) and yesterday's average (e.g., 632e). As shown in FIG. 6DC, each of 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 embodiments, the graph represents the amount of a single health data metric compared over periods of the same length.

[0214] As described above, the highlighted area also includes showing all highlighting affordances 634. In some embodiments, selection of all highlighting affordances 634 causes a user interface corresponding to a health application, such as all highlighted user interfaces as shown in FIGS. 6MA - 6MD, to be displayed.

[0215] In some embodiments, 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 institution that has transmitted health record data regarding an account associated with the health application. For example, the first health record affordance 636 indicates correspondence with the XYZ Medical Center in Palo Alto, California (see 636d). In another embodiment, the second health record affordance 638 indicates correspondence with the ABC Emergency in San Jose, California (see 638d).

[0216] In some embodiments, each affordance within the health record area 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 within the health record area also includes an indication of when the most recent health record was received from the corresponding clinical institution (e.g., the first health record affordance 636 includes a time display 636b of 8:00 am, and the second health record affordance 638 includes a time display 638b of 6:00 am). In some embodiments, the affordances within the health record area are ordered based on when the most recent health record was received from the corresponding clinical institution (e.g., the first health record affordance 636 is above the second health record affordance 638 based on the most recent health record corresponding to the first health record affordance 636 received after the most recent health record corresponding to the second health record affordance 638). In other embodiments, the affordances within 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 generated before the second health record corresponding to the second health record affordance 638). In other embodiments, the affordances within the health record area are ordered based on a user-defined order, such as specifying primary and secondary institutions (e.g., the primary institution is above the secondary institution). In some embodiments, only the primary institution is represented within the health record area, and the secondary institution can be navigated to using all of the health record affordances 640. In some embodiments, selection of all of the health record affordances 640 causes the display of the user interface of the health application, which includes all of the health records received for the account associated with the health application (as shown in FIGS. 6OA - 6OB).

[0217] In some embodiments, each affordance within the health record area includes an indication of which records were received from which corresponding institutions. For example, the first health record affordance 636 includes an indication 636e indicating that health records corresponding to medications, test results, and other records were received from the XYZ Medical Center. In some embodiments, the indication 636e is ordered based on when the medical records were received (e.g., since a health record having health data corresponding to a medication was received more recently than a health record having health data corresponding to a test result, the medication is before the test result). In another embodiment, the second health record affordance 638 includes an indication 638e indicating that a health record corresponding to a medication was received from the ABC Emergency Treatment.

[0218] In some embodiments, the education area includes affordances that, when selected, cause the user interface to display educational content. In some embodiments, more information from the health area includes affordances that, when selected, cause the user interface to be displayed to configure the health application. In some embodiments, the app area includes affordances corresponding to different applications that are determined to be related to the account of 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 pertains (e.g., visually distinguishable affordances (e.g., bold text) indicate which section). In some embodiments, selection of a section of the health application to which the current user interface does not pertain (e.g., search affordance 642b in FIG. 6DD) causes display of the user interface corresponding to the selected section (e.g., when search affordance 642b is selected, the 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 display of the home interface of the selected section as shown in FIG. 6DA (e.g., summary user interface 614 as shown in FIG. 6DA and search user interface 684 as shown in FIGS. 6TA-6TB).

[0220] FIG. 6DA shows a first electronic device 600 that receives a user input 615 corresponding to a first notification affordance 616. In some embodiments, 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 embodiments, other forms of selection, such as a click using a mouse, can be used. In some embodiments, the user input 615 causes display, via the touch-sensitive display device 602, of a different user interface, such as the display of the environmental audio data chamber user interface 644 of the health application as shown in FIG. 6E.

[0221] FIG. 6E shows a first electronic device 600 that displays an environmental audio data room user interface 644 via a touch-sensitive display device 602 at a fifth time after a 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 having data indicative of noise levels detected by the device over a one-week period. In some embodiments, the data is stored at a location associated with the environmental audio application and can be viewed within the user interface of the environmental audio application.

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

[0223] As shown in FIG. 6E, the ambient audio data room user interface 644 includes the number of affordances in bottom text that indicate information shown by a graph. For example, there is a first affordance that shows the average over the entire week, a second affordance that shows the daily average over the entire week, a third affordance that shows the range over the entire week, and the number of noise notifications issued during the week by the ambient audio application. In some embodiments, selection of one of the affordances causes the graph to be changed to highlight the data within the graph corresponding 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 points to be inserted into each bar for each day within 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 causes a portion of the graph to be highlighted and a noise notification to be issued.

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

[0225] As shown in FIG. 6F, the summary user interface 614, as shown in FIG. 6DA, is scrolled down with respect to the summary user interface 614 (for example, the text "Summary" in the upper left and the account icon in the upper right are no longer displayed). FIG. 6F shows that after the first notification affordance 616 has been interacted with (for example, selected as shown in FIG. 6DA), the first notification affordance 616 is still displayed in the summary user interface 614. FIG. 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] FIG. 6G shows a first electronic device 600 that displays a summary user interface 614 via a touch-sensing display device 602 at a seventh time after a 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] FIG. 6G shows that even if the second notification affordance 618 and the third notification affordance 620 were received before the first notification affordance 616, the first notification affordance 616 is no longer displayed within the summary user interface 614. Such indicates that in some embodiments, there are interacted notification affordances that 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 within the summary user interface 614.

[0228] FIG. 6H shows a first electronic device 600 that displays a summary user interface 614 via a touch-sensing display device 602 at an eighth time after a seventh time. In some examples, the summary user interface 614 is redisplayed with respect to the touch-sensing display device 602 at the seventh time (as shown in FIG. 6G).

[0229] FIG. 6H shows that the third notification affordance 620 corresponding to the notification issued before the notification corresponding to the second notification affordance 618, and (2) any of the notification corresponding to the third notification affordance 620, the third notification affordance 620, the notification corresponding to the second notification affordance 618, and the second notification affordance 618 not being interacted with by the user, at least partially results in the third notification affordance 620 no longer being displayed in the summary user interface 614. Such indicates that when issued, non-interacted notification affordances are removed based on chronological order (e.g., older notification affordances are removed first). FIG. 6H shows that the second notification affordance 618 is still displayed within the summary user interface 614.

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

[0231] FIG. 6I shows a first electronic device 600 that displays an edit user interface 646 via a touch-sensing display device 602 at a ninth time after an eighth time. In some embodiments, the edit user interface 646 is a user interface of a health application that enables a user to add and / or remove favorites displayed in the favorites area of the summary user interface 614.

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

[0233] In a view corresponding to the existing data affordance 646a (as shown in FIG. 6I), the editing user interface 646 includes a representation of a health data type for which the account has at least some health data (e.g., the representation of the health data type is displayed when the health application has access to the 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 an embodiment, the editing user interface 646 within the view corresponding to the existing data affordance 646a does not include any representation for a health data type for which the account has no health data (e.g., the representation of the health data type is not displayed when the health application does not have access to the 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 any view, the selection of the representation of a health data type enables the user to view the stored data regarding the health data type from the summary user interface 614 by adding the favorite affordance of the health data type to the favorite area of the summary user interface 614. As shown in FIG. 6I, the representation of the health data type is shown as being selected by including a display that is visually distinguishable from other displays within the representation. For example, the representation 646c includes a display indicating that the favorite affordance of the health data type corresponding to the representation 646c is displayed within the favorite area of the summary user interface 614. In another example, the representation 646d includes a display indicating that the favorite affordance of the health data type corresponding to the representation 646c is not displayed within the favorite area of the summary user interface 614. As shown in FIG. 6I, the group of representations of the health data type is displayed via the edit user interface 646. For example, the edit user interface 646 includes a group of representations corresponding to activities, body measurements, and the heart, and each representation within the group of representations is related.

[0235] FIG. 6J shows a first electronic device 600 that displays the summary user interface 614 via the touch-sensitive display device 602 at a tenth time after a ninth time. In some embodiments, the summary user interface 614 is displayed in response to a user input corresponding to the selection of the execute button in the upper right of the edit user interface 646 (shown in FIG. 6I without user input). The summary user interface 614 as shown in FIG. 6J is scrolled down with respect to the summary user interface 614 as shown in FIG. 6H (for example, the logging affordance 622 is no longer displayed in FIG. 6J).

[0236] FIG. 6J shows a first electronic device 600 that receives a user input 627 corresponding to a second favorite affordance 626b. In some embodiments, the user input 627 is received via a touch sensing display device 602 and corresponds to a selection gesture (e.g., a tap) on the second favorite affordance 626b. In other embodiments, other forms of selection, such as a click using a mouse, can be used. In some embodiments, the user input 627 causes different user interfaces, such as the display of a step count data chamber user interface 648, to be displayed via the touch sensing display device 602, as shown in FIGS. 6KA-6KB.

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

[0238] In some embodiments, the step count data chamber user interface 648 is a user interface of a health application having information from an activity application. As shown in FIG. 6KA, the step count data chamber user interface 648 includes a graph 648a having a representation of health data associated with the number of steps taken in a day. In some embodiments, the health data is stored at a location associated with the activity application and can be viewed within the user interface of the activity application.

[0239] The step count data chamber user interface 648 further includes at the top time scale affordances indicating 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 indicating day is selected, and the graph shows the number of steps detected over one day. In some embodiments, the 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 chamber user interface 648 includes an emphasis section including an emphasis associated with the step count. As shown in FIG. 6KA, the step count data chamber user interface 648 includes a single emphasis (e.g., 648b) indicating how the step count increased over a given period. It should be recognized that other emphases may be included in the emphasis section. In some embodiments, identifying an emphasis for display within the step count data chamber user interface 648 includes a determination similar to that described above for the emphasis area. The step count data chamber user interface 648 further includes an explanation 648c regarding what the step count means and an additional affordance 468 for adding the step count to the favorite area within the summary user interface 614.

[0241] Referring to FIG. 6KB, the step count data chamber user interface 648 includes (1) a step count app section 648e having links to proposed apps related to the step count (e.g., a link to an app store or a link to an application installed on the first electronic device 600), (2) an option section 648f having various options related to the step count, and (3) an education section 648g having an affordance that, when selected, causes the user interface to display content related to the step count.

[0242] FIG. 6L shows a first electronic device 600 that displays a summary user interface 614 via a touch sensing display device 602 at a twelfth time after an eleventh time. In some embodiments, the summary user interface 614 is displayed in response to a user input corresponding to a return selection to a summary affordance in the upper left of a step data chamber user interface 648 (shown in FIG. 6KA without user input). The summary user interface 614 as shown in FIG. 6L is scrolled down with respect to the summary user interface 614 (e.g., the favorite region is no longer displayed and the highlighted region is displayed in FIG. 6L) as shown in FIG. 6J.

[0243] FIG. 6L shows a first electronic device 600 that receives a corresponding user input 635 to show all highlighted affordances 634. In some embodiments, the user input 635 is received via a touch sensing display device 602 and corresponds to a selection gesture (e.g., a tap) to show all highlighted affordances 634. In other embodiments, other forms of selection such as a click using a mouse can be used. In some embodiments, the user input 635 causes different user interfaces such as the display of an all-highlighted user interface 650 to be displayed via the touch sensing display device 602 as shown in FIGS. 6MA-6MD.

[0244] FIGS. 6MA-6MD show a first electronic device 600 that displays an all-highlighted user interface 650 via a touch sensing display device 602 at a thirteenth time after a twelfth time. In some embodiments, the all-highlighted user interface 650 is displayed in response to a user input corresponding to a selection of all highlighted affordances 634 in the summary user interface 614 as shown in FIG. 6L.

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

[0246] FIG. 6MB shows a first electronic device 600 that displays 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 specific color corresponding to the sleep application). The second highlight affordance 632 also includes an explanation 652c for indicating information shown by the third highlight affordance 652 (e.g., how the user slept on average 7 hours and 55 minutes this week).

[0247] As shown in FIG. 6MB, the third highlight affordance 652 includes a graph having 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 embodiments, the graph represents an average over a period (e.g., a week) divided into sub-periods (e.g., days).

[0248] FIG. 6MB shows a first electronic device 600 that displays a fourth highlighting affordance 654 via a touch-sensitive display device 602. The fourth highlighting affordance 654 includes an icon 654a indicating that the fourth highlighting affordance 654 is primarily related to a water application (in some embodiments, the fourth highlighting affordance 654 is secondarily related to a calendar application). In some embodiments, a portion of the fourth highlighting affordance 654 is visually distinguished to identify that the fourth highlighting affordance 654 is related to a water application (e.g., in some embodiments, the font color of the title 654b is a specific color corresponding to the water application). The fourth highlighting affordance 654 also includes an explanation 652c for indicating information represented by the fourth highlighting affordance 654 (e.g., how the user recorded water for 21 days in the last four weeks).

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

[0250] FIG. 6MC shows a first electronic device 600 that displays a fifth highlighting affordance 656 via a touch sensing display device 602. The fifth highlighting affordance 656 includes an icon 656a that indicates that the fifth highlighting affordance 656 is primarily related to a navigation application (in some embodiments, the fifth highlighting affordance 656 is secondarily related to a training application). In some embodiments, a portion of the fifth highlighting affordance 656 is visually distinct to identify that the fifth highlighting affordance 656 is primarily related to the navigation application (e.g., in some embodiments, the font color of the title 656b is a specific color corresponding to the navigation application). The fifth highlighting affordance 656 also includes an explanation 656c for indicating the information represented by the fifth highlighting affordance 656 (e.g., that the user has recorded a 3.1 mile run at an average pace of 8:51).

[0251] As shown in FIG. 6MC, the fifth highlighting affordance 656 includes a map 656d having a display within a map 656d of a running route. The fifth highlighting affordance 656 also includes text information related to running, including a distance measurement 656e (longer than the distance included in the explanation 656c), a duration 656f, and calories 656g.

[0252] Figure 6MC shows a first electronic device 600 that displays a sixth highlighting affordance 658 via a touch-sensing display device 602. The sixth highlighting affordance 658 includes an icon 658a indicating that the sixth highlighting affordance 658 is related to a training application. In some embodiments, a portion of the sixth highlighting affordance 658 is visually distinguishable to identify that the sixth highlighting affordance 658 is related to a training application (e.g., in some embodiments, the font color of the title 658b is a specific color corresponding to the training application). The sixth highlighting affordance 658 also includes an explanation 658c for indicating the information represented by the sixth highlighting affordance 658 (e.g., today the user burned a total of 6500 calories, etc.).

[0253] As shown in Figure 6MC, the sixth highlighting affordance 658 includes four different representations of different trainings recorded in a day. Each training includes an icon corresponding to the type of training, identification information (e.g., name) of the type of training, the length of time of each training, and an icon corresponding to the number of calories burned during each training. In some embodiments, the sixth highlighting affordance 658 represents multiple trainings of a day within a single highlighting having the heart rate data of the day.

[0254] FIG. 6MD shows a first electronic device 600 that displays a seventh highlighting affordance 660 via a touch-sensing display device 602. The seventh highlighting affordance 660 includes an icon 660a that indicates that the seventh highlighting affordance 660 is primarily related to a vital application. In some embodiments, a portion of the seventh highlighting affordance 660 is visually distinct (e.g., in some embodiments, the font color of the title 660b is a specific color corresponding to the vital application) to identify that the seventh highlighting affordance 660 is related to a vital application. Note that the seventh highlighting affordance 660 does not include an explanation indicating the information indicated by the seventh highlighting affordance 660, indicating that not all highlighting has such an explanation. As shown in FIG. 6MD, the seventh highlighting affordance 660 includes a graph 660c showing the beats per minute for the user over time, indicating how the beats per minute are reduced from the high point to the low point.

[0255] FIG. 6MD shows a first electronic device 600 that displays an eighth highlighting affordance 662 via a touch-sensing display device 602. The eighth highlighting affordance 662 includes an icon 662a that indicates that the eighth highlighting affordance 662 is related to an activity application. In some embodiments, a portion of the eighth highlighting affordance 662 is visually distinct (e.g., in some embodiments, the font color of the title 662b is a specific color corresponding to the activity application) to identify that the eighth highlighting affordance 662 is related to an activity application. The eighth highlighting affordance 662 also includes an explanation 662c for indicating the information indicated by the eighth highlighting affordance 662 (e.g., the user has obtained more steps today than is normally done during this time period).

[0256] As shown in FIG. 6MD, the eighth highlighting affordance 662 includes a graph 662d that compares the activity metrics for a day (e.g., the current day) to a previous average. For example, graph 662d includes a today's line 662h and a previous average line (including a first portion 662g and a second portion 662i). The today's line 662h indicates the number of steps the user has taken as of the current time when advancing one day. The previous average line indicates the number of steps the user has taken on average when advancing over several 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. Graph 662d also includes a text display regarding the number of steps today and a text display regarding the number of steps at this time averaged over several days prior to the current day. In some embodiments, the sixth highlighting affordance 658 represents an instantaneous update of information and an average over a period compared to today.

[0257] FIG. 6N shows a first electronic device 600 that displays a summary user interface 614 via a touch-sensitive display device 602 at a fourteenth hour after a thirteenth hour. In some embodiments, the summary user interface 614 is displayed in response to a user input corresponding to the selection of a summary affordance 642a within all highlighting user interfaces 650 (shown in FIG. 6MD without user input). The summary user interface 614 as shown in FIG. 6N is scrolled down with respect to the summary user interface 614 as shown in FIG. 6L (e.g., the highlighting area is no longer displayed and the health record area is displayed in FIG. 6N).

[0258] FIG. 6N shows a first electronic device 600 that receives a corresponding user input 641 to show all health record affordances 640. In some embodiments, the user input 641 is received via a touch-sensing display device 602 and corresponds to a selection gesture (e.g., a tap) that shows all health record affordances 640. In other embodiments, other forms of selection, such as a click using a mouse, can be used. In some embodiments, the user input 641 causes different user interfaces, such as the display of an all health data user interface 664, to be displayed via the touch-sensing display device 602, as shown in FIGS. 6OA through 6OB.

[0259] FIGS. 6OA through 6OB show a first electronic device 600 that displays an all health data user interface 664 via a touch-sensing display device 602 at a fifteenth time after a fourteenth time. In some embodiments, the all health data user interface 664 is displayed in response to a user input corresponding to the selection of all health record affordances 640 that show a summary user interface 614, as shown in FIG. 6N.

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

[0261] In the health record view, in some embodiments, all health data user interfaces 664 include 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 test results, representation 666f is for medications, representation 666g is for treatments). In such embodiments, the representations of health record types are alphabetically ordered (e.g., treatments before medications before test results before vaccinations before conditions before clinical vitals before allergies).

[0262] In some embodiments, each representation within the health record view includes an icon corresponding to the health record type (e.g., icon 666aa corresponds to allergies, icon 666ba corresponds to clinical vitals, icon 666ca corresponds to conditions, icon 666da corresponds to vaccinations, icon 666ea corresponds to test results, icon 666fa corresponds to medications, icon 666ga corresponds to procedures). In some embodiments, the user interface of a health application that includes user interface elements corresponding to health record types includes a version of the corresponding icon.

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

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

[0265] FIG. 6OA shows a first electronic device 600 that receives a user input 667 corresponding to the representation 666e. In some embodiments, the user input 667 is received via a touch-sensing display device 602 and corresponds to a selection gesture (e.g., a tap) on the representation 666e. In other embodiments, other forms of selection, such as a click using a mouse, can be used. In some embodiments, the user input 667 causes different user interfaces, such as the display of an inspection result data room user interface 668, to be displayed via the touch-sensing display device 602, as shown in FIGS. 6PA-6PB.

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

[0267] As shown in FIG. 6PA, the inspection result data room user interface 668 includes an icon 668a and a title 668b indicating this corresponding to the health record type "inspection result". In some embodiments, the user interface elements corresponding to the health record type "inspection result" include icons similar to the icon 668a.

[0268] As shown in FIG. 6PA, the inspection result data room user interface 668 includes a final update affordance 668c and an A-Z affordance 668d for switching between views of the inspection result data room user interface 668. For example, a user input corresponding to the selection of the final update affordance 668c causes the inspection result data room user interface 668 to display a first view, as shown in FIGS. 6PA-6PB. Similarly, a user input corresponding to the selection of the A-Z affordance 668d causes the inspection result data room user interface 668 to display a second view, as shown in FIG. 6Q.

[0269] As shown in FIGS. 6PA-6PB, the inspection result data room user interface 668 includes a plurality of regions (e.g., region 670 and region 672), and each region corresponds to a different date on which a health record within the region was generated (e.g., collected, taken, or otherwise created by a clinical institution). In some embodiments, the plurality of regions are ordered by date such that the region corresponding to the more recent date is before the region corresponding to the later date. For example, the inspection result data room user interface 668 includes region 670 (shown in FIG. 6PA and indicated as corresponding to March 29, 2019) higher (e.g., earlier) in the list than region 672 (shown in FIG. 6PB and indicated as corresponding to August 15, 2019).

[0270] In some embodiments, each region included in the inspection result data room user interface 668 includes one or more representations of a health record. 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 embodiments, the representations within the region are included in sub-regions corresponding to clinical institutions associated with the health records. For example, representations 670b and 670c are included in a sub-region corresponding to XYZ Medical Center, indicating that the health records corresponding to representations 670b and 670c were received (e.g., generated) from XYZ Medical Center. In another embodiment, representations 672b, 672c, and 672d are included in a sub-region corresponding to ABC Emergency, indicating that the health records corresponding to representations 672b, 672c, and 672d were received (e.g., generated) from ABC Emergency. Such things indicate that the test result data room user interface 668 can include representations from multiple clinical institutions.

[0272] In some embodiments, the representation of a health record within the test result data room user interface 668 includes an icon indicating the corresponding health record type (as described above). In some embodiments, the representation of a health record within the test result data room user interface 668 includes 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 date it is related to (e.g., March 29, 2019).

[0273] The information within representation 670b further includes a graph indicating the corresponding health record. The graph in representation 670b includes a plurality of displays of values (e.g., "125 MG / DL") included in the corresponding health record and a range defined for the values (e.g., the minimum and maximum values of 0 to 200). The plurality of displays includes a text display (e.g., text) and a graphical representation (e.g., a dot within a visual representation of the range). In some embodiments, a value is considered to meet a particular criterion (e.g., a criterion related to whether the value is acceptable, such as a criterion set by a regulatory agency) when the value is within the range. In some embodiments, the range is included in the corresponding health record. In other embodiments, this range is known by a health application such as provided by a remote source (such as a clinical institution).

[0274] FIG. 6PA shows a representation 670c that includes a graph showing corresponding health records. The graph in the representation 670c includes a plurality of displays of values (e.g., "6.3%") included in the corresponding health records and a range defined for the values (e.g., from 5.7 to 6.3 which are the minimum and maximum values). The plurality of displays includes a text display (e.g., text) and a graphical representation (e.g., a dot within a visual representation of the range). In some embodiments, a value is considered to meet a particular criterion (e.g., a criterion related to whether the value is acceptable such as a criterion set by a regulatory agency) when the value is within the range. In some embodiments, the range is included in the corresponding health record. In other embodiments, this range is known to the health application as provided by a remote source (such as a clinical institution).

[0275] FIG. 6PB shows a representation 672b that includes information from the corresponding health record. The information within the representation 672b includes a single display (e.g., a text display) of a value (e.g., "40%") included in the corresponding health record and does not include a display of a range defined for the value. In some embodiments, since the health application cannot identify a range of values (e.g., the corresponding health record does not include a range and / or the display does not provide a range), the information within the representation 672b does not include a graph (and / or a display of a range).

[0276] FIG. 6PB shows a representation 672c that includes information from the corresponding health record. The information within the representation 672c includes a single display (e.g., a text display) of a value (e.g., "negative") included in the corresponding health record. In some embodiments, since 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), the information in the representation 672b does not include a graph (and / or a display of a range) (e.g., two values are not graphed).

[0277] Figure 6PB shows a representation 672d that includes a graph showing corresponding health records. The graph in the representation 672d includes multiple displays of values (e.g., "4.5 trillion") included in the corresponding health record and a range defined for the values (e.g., 5.32 to 5.72 trillion, which are the minimum and maximum values). The multiple displays include a text display (e.g., text) and a graphical representation (e.g., dots within a visual representation of the range). In some embodiments, a value is considered to meet a particular criterion (e.g., a criterion related to whether the value is acceptable, such as a criterion set by a regulatory agency) when the value is within the range. In some embodiments, the range is included in the corresponding health record. In other embodiments, this range is known to a health application such as provided by a remote source (such as a clinical institution). Figure 6PB shows that while some representations can include a graph, other representations, even those corresponding to the same health record type, do not include a graph. Such results are due in part to health records that do not include a range and / or are binary in some embodiments.

[0278] Figure 6PA shows a first electronic device 600 that receives a user input 669 corresponding to an A-Z affordance 668d. In some embodiments, the user input 669 is received via a touch-sensing display device 602 and corresponds to a selection gesture (e.g., a tap) on the A-Z affordance 668d. In other embodiments, other forms of selection, such as a click using a mouse, can be used. In some embodiments, the user input 669 causes different views of the test result data room user interface 668 to be displayed via the touch-sensing display device 602, such as the A-Z view shown in Figure 6Q.

[0279] Figure 6Q shows a first electronic device 600 that displays an A-Z view of the test result data room user interface 668 via the touch-sensing display device 602 at a 17th time after a 16th time. In some embodiments, the A-Z view is displayed in response to a user input corresponding to a selection of the A-Z affordance 668d within the test result data room user interface 668, as shown in Figure 6PA.

[0280] As shown in FIG. 6Q, the A-Z view includes a final update affordance 668c and an A-Z affordance 668d for switching between views of the inspection result data chamber user interface 668. For example, user input corresponding to the selection of the final update affordance 668c causes the inspection result data chamber user interface 668 to display a first view, as shown in FIGS. 6PA - 6PB. Similarly, user input corresponding to the selection of the A-Z affordance 668d causes the inspection result data chamber user interface 668 to display a second view, as shown in FIG. 6Q.

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

[0282] FIG. 6Q shows a first electronic device 600 that receives a user input 675 corresponding to an affordance 674c. In some embodiments, the user input 675 is received via a touch-sensing display device 602 and corresponds to a selection gesture (e.g., a tap) on the affordance 674c. In other embodiments, other forms of selection, such as a click using a mouse, can be used. In some embodiments, the user input 675 causes a different user interface, such as the hemoglobin user interface 676 shown in FIGS. 6RA - 6RB, to be displayed via the touch-sensing display device 602.

[0283] Figures 6RA - 6RB illustrate a first electronic device 600 that displays a hemoglobin user interface 676 via a touch - sensing display device 602 at the 18th hour after the 17th hour. In some embodiments, the hemoglobin user interface 676 is displayed in response to a user input corresponding to the selection of affordance 674c within the test result data chamber user interface 668, as shown in FIG. 6Q. In some embodiments, the hemoglobin user interface 676 is displayed in response to a user input corresponding to the selection of affordance 670c within the test result data chamber user interface 668, as shown in FIG. 6PA. In some embodiments, the hemoglobin user interface 676 is a user interface of a health application having information based on a health record corresponding to hemoglobin A1C.

[0284] As shown in FIG. 6RA, the hemoglobin user interface 676 includes a graph having data indicative of values obtained from health records corresponding to hemoglobin A1C over a year. For example, the first health record can indicate that the result of the first hemoglobin A1C test was 6.3% (e.g., the first health record corresponds to affordance 680a), the second health record can indicate that the result of the second hemoglobin A1C test was 7.3% (e.g., the second health record corresponds to affordance 680b), and the third health record can indicate that the result of the third hemoglobin A1C test was 6% (e.g., the third health record corresponds to affordance 680c). Such health records cause the graph to include 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 embodiments, the graph also includes an expression 676cd that provides additional information regarding one of the health records within the graph. As shown in FIG. 6RA, the expression 676cd relates to the first health record. In some embodiments, the expression 676cd is related to the first health record in response to a user input on the expression 676cc and / or a selection of an affordance displayed on a different user interface 676 for causing the hemoglobin user interface 676 to be displayed, and the affordance corresponds to the health record associated with the indication 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 indicating different time scales (e.g., "W" indicating weeks, "M" indicating months, "Y" indicating years, and "5Y" indicating five years). As shown in FIG. 6RA, the time scale affordance indicating years is selected, causing the graph to show health records over a year. In some embodiments, the selection of a different time scale affordance changes the graph to show the health records detected over the selected time scale.

[0286] As shown in FIG. 6RA, the hemoglobin user interface 676 includes out-of-range affordances 678. Selection of the out-of-range affordances 678 causes the indication in the graph to be visually distinguished (e.g., highlighted) corresponding to values outside the defined range, as described above.

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

[0288] FIG. 6SA shows a first electronic device 600 that displays an inspection result recording user interface 682 via a touch-sensing display device 602 at a nineteenth time after an eighteenth time. In some embodiments, the inspection result recording user interface 682 is displayed in response to a user input corresponding to a selection of an affordance 680a within the hemoglobin user interface 676, as shown in FIG. 6RA. In some embodiments, the inspection result recording user interface 682 includes detailed information regarding a particular health record. In some embodiments, the detailed information includes the date when the particular health record was collected, the date when the particular health record was received by a health application, an alternative name for the particular health record (e.g., identified from any of the other health records associated with a remote source or an account of the health application), the clinical institution associated with the particular health record, and other information included in the particular health record.

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

[0290] As shown in FIGS. 6SA - 6SB, the XYZ Medical Center user interface 698 includes a plurality of regions (e.g., regions for different days), and each region corresponds to a different date on which a health record within the region was generated (e.g., collected, taken, or otherwise created by a clinical institution). In some embodiments, the plurality of regions are ordered by date such that the region corresponding to the more recent date is before the region corresponding to the later date. 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 (e.g., earlier) in the list than a region corresponding to November 2, 2018 (as shown in FIG. 6SC).

[0291] In some embodiments, each region included in the XYZ Medical Center user interface 698 includes one or more sub - regions, and each sub - region corresponds to a different health record type (e.g., allergies, medications, etc.) within the sub - region. In some embodiments, the plurality of sub - regions are alphabetically ordered (e.g., allergies before medications) (not shown).

[0292] In some embodiments, each sub-region included in the XYZ Medical Center user interface 698 includes one or more representations of health records. For example, sub-region 698a includes four separate representations of 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 the XYZ Medical Center instead of the ABC Emergency), and representation 698c (similar to 672c shown and described in FIG. 6PB but from the XYZ Medical Center instead of the ABC Emergency). FIGS. 6SA - 6SB show that while some representations can include graphs, other representations, even those corresponding to the same health record type, do not include graphs. Such results are due in part to health records that are non - range - inclusive and / or binary in some embodiments. FIGS. 6SA - 6SB show a user interface for a single clinical institution, and it should be recognized that similar techniques can be used for user interfaces having representations of health records from multiple clinical institutions.

[0293] FIG. 6TA shows a first electronic device 600 that displays a search user interface 684 via a touch - sensing display device 602 at the 20th hour after the 19th hour. In some embodiments, the search user interface 684 is displayed in response to user input corresponding to the selection of a search affordance 642b in any user interface of a 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 used to search for health applications. For example, when the first electronic device 600 receives a user input corresponding to a character string (e.g., user typing of a character string using a keyboard) along with the search area 684a (e.g., the insertion marker is located within the search area 684a) and a request to execute a search, the first electronic device 600 searches for data associated with the health application based on the character string, as shown in FIG. 6U and described further below.

[0295] As shown in FIG. 6TA, the search user interface 684 includes a group of four affordances: a shared health data affordance 684b, a health category affordance 684c, a health record affordance 684d, and a health content affordance 684g. In some embodiments, the search user interface 684 includes a smaller group of affordances, such as not including the shared health data affordance 684b when the first electronic device 600 has not received shared health data from another device.

[0296] In some embodiments, the affordance of the shared health data affordance 684b is related to other accounts linked to an account associated with the health application. In one embodiment, the link 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 the shared health data affordance 684b includes an affordance 684ba. In some embodiments, as shown in FIG. 6XA and described further below, the affordance 684ba is related to an account associated with "Little Apple Seed" such that selection of the affordance 684ba causes a user interface (e.g., a user interface that enables the user to view health data associated with the account associated with "Little Apple Seed") to be displayed.

[0297] In some embodiments, 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 enables 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 corresponding to an activity health data type (e.g., the type of health data corresponding to an activity). In some embodiments, the activity health data type corresponds to health data stored by an activity application. In another embodiment, the health category affordance 684c includes an affordance 684ck corresponding to a vital health data type (e.g., the type of health data corresponding to a vital). In some embodiments, the vital health data type corresponds to health data stored by a vital application.

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

[0299] In some embodiments, the affordance of the health record affordance 684d is related to the category of the health record as described above. For example, the health record affordance 684d represents a hierarchy of health records and enables the user to navigate to a specific 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., the type of health record). In some embodiments, the selection of the affordance 684de causes the display of a user interface, which includes the health record of the test result. The health record affordance 684d also includes an affordance related to a clinical institution (e.g., affordance 684h). The selection of the affordance related to the clinical institution causes the display of a user interface of the health application, which includes the health records collected by the clinical institution. The selection of the affordance related to all accounts (e.g., affordance 684dj) causes the display of a user interface of the health application, which includes all health records.

[0300] As shown in FIG. 6TB, the search user interface 684 includes an affordance 684e for viewing clinical documents. The selection of the affordance 684e causes the display of a user interface of the health application, which includes 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 cannot be analyzed (e.g., interpreted or read) by the health application (or a process related to the health application)). The selection of the affordance 684f causes the display of a user interface of the health application, which includes a representation of the health record that could not be analyzed by the health application (or a process related to the health application).

[0301] In some embodiments, the affordance of the health content 684g is related to a link to other health content. For example, the health content affordance 684g includes an affordance for viewing educational content. The selection of such an affordance causes the user interface of the health application to be displayed, and the user interface includes educational content. In another embodiment, the health content affordance 684g includes an affordance for viewing the above-described highlighting. The selection of such an affordance causes the user interface of the health application to be displayed, and the user interface includes one or more highlighted expressions.

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

[0303] In some embodiments, 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 an expression of blood pressure detected for a user associated with the account. In another embodiment, the second search result 684i includes health record data (e.g., a health record received by the first electronic device 600 from a clinical institution). As shown in FIG. 6U, the second search result 685i includes the blood pressure included in the health record.

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

[0305] In some embodiments, the search results include categories of health data determined to be related to a 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 heart category affordance 684ka, a vital affordance 684kb, and a clinical vial affordance 684kc. The categories of health data represent a hierarchy of health records and enable the user to navigate to specific health records via one or more user inputs. For example, the selection of an affordance corresponding to a category of health data causes the display of a user interface, and the user interface includes the health record corresponding to the category.

[0306] FIG. 6V shows a first electronic device 600 that displays an activity user interface 686 via a touch-sensing display device 602 at a twenty-second time after a twenty-first time. In some embodiments, the activity user interface 686 is displayed in response to a user input corresponding to a selection of an affordance 684ca within the search user interface 684.

[0307] As shown in FIG. 6V, the activity user interface 686 includes a representation of health data regarding activities for an account associated with a health application. For example, the activity user interface 686 includes a representation 686a having heart rate data during an intensity training.

[0308] FIG. 6W shows a first electronic device 600 that displays a vital user interface 688 via a touch-sensing display device 602 at a twenty-third time after a twenty-second time. In some embodiments, the vital 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 vital user interface 688 includes a representation of health data related to vitals for an account associated with a health application. For example, the activity user interface 686 includes a representation 688a having heart rate data during an intensity training. The 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 results are due to health data having a plurality of categories to which they are associated. For example, as shown in FIGS. 6V-6W, the heart rate during an intensity training is associated with both activity and vitals. In some embodiments, the health data has primary and secondary health categories.

[0310] Figures 6XA - 6XB illustrate a first electronic device 600 that displays a child search user interface 690 via a touch sensing display device 602 at a twenty - fourth time after a twenty - third time. In some embodiments, the child search user interface 690 and the user interfaces navigated from affordances included in the child search user interface 690 are read - only (compared to a search user interface 684 that, in some embodiments, enables a user to add / delete / edit data when navigating to data associated with an account of a health application). In some embodiments, the child search user interface 690 is displayed in response to a user input corresponding to a selection of an affordance 684ba within 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 accounts 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 Apple Seeds 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 Apple Seeds instead of an account associated with a health application), a health record affordance 692c (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 Apple Seeds 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., the shared health data affordance 684ba). In other embodiments, the child search user interface 690 includes a shared health data affordance for devices linked to the Little Apple Seeds account.

[0312] FIG. 6Y shows a first electronic device 600 that displays an activity user interface 694 via a touch-sensitive display device 602 at the 25th hour after the 24th hour. In some embodiments, 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] As shown in FIG. 6Y, the activity user interface 694 includes a representation of health data related to the activity for the Little Apple Seed account (as shown, for example, by indication 694a). For example, the activity user interface 694 includes a representation 694c having heart rate data during the Little Apple Seed's intensity training.

[0314] FIG. 6Z shows a first electronic device 600 that displays a vital user interface 696 via a touch-sensitive display device 602 at the 26th hour after the 25th hour. In some embodiments, the vital user interface 696 is displayed in response to a user input corresponding to the selection of a vital affordance within the child search user interface 690.

[0315] As shown in FIG. 6Z, the vital user interface 696 includes a representation of vital health data for the Little Apple Seed account (as shown, for example, by indication 696a). For example, the vital user interface 696 includes a representation 696c having heart rate data during the Little Apple Seed's intensity training. The representation 696c is an example where health data included in one category (e.g., vital) can be included in another category (e.g., activity). Such results are due to health data having a plurality of categories to which they are associated. For example, as shown in FIGS. 6Y-6Z, the heart rate during intensity training is associated with both activity and vital. In some embodiments, the health data has primary and secondary health categories.

[0316] FIGS. 7A-7B are flow diagrams showing a method for managing notifications using an electronic device, according to some embodiments. The method 700 is executed on a device having a display device (e.g., 100, 300, 500, 600, 606). Some operations of the 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 optionally communicates (e.g., via wired communication, wireless communication) with a display generation component and one or more input devices. 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. The one or more input devices are configured to receive an input such as a touch-sensing surface for receiving 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. Accordingly, the computer system can transmit data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device) and can receive input from the one or more input devices via a wired or wireless connection.

[0318] As described below, method 700 provides an intuitive way to manage notifications. The method reduces the user's cognitive burden during notification viewing and actions on the notifications, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, it saves power and extends the time between battery charges by enabling the user to view and act on notifications faster and more efficiently.

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

[0320] In some embodiments, the first notification includes first visual characteristics (704) (e.g., color (e.g., patterns within the headers of 616 including 616b and 616c, patterns within the headers of 618 including 618a, 618b, and 618c, and patterns within the headers of 620 including 620a, 620b, and 620c) (e.g., foreground color, background color, inclusion (or exclusion) of each icon)). In some embodiments, in accordance with a determination (706) that the first data set corresponds to a first application (e.g., is generated thereby), the first visual characteristics have a first value (e.g., blue). In some embodiments, in accordance with a determination (708) that the first data set corresponds to a second application, the first visual characteristics have a second value (e.g., red) different from the first value.

[0321] Specifying the visual quality (e.g., color) of a notification based on the corresponding application provides the user with feedback that helps identify the application. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0322] After displaying a first instance of a 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] According to a determination (712) that a set of interaction criteria including criteria that are satisfied when a first data set is displayed (e.g., displayed within a first instance of the first user interface, within a subsequent instance of the first user interface, on the electronic device, on a second electronic device that receives the same notification as the electronic device (e.g., because both are associated with the same user account)) is satisfied, and according to a determination that a set of first removal criteria including a first criterion based on a first period (e.g., a period that must not be exceeded to satisfy the first criterion, a period determined since the first data set was received or generated, a period determined since the notification corresponding to the first data set was first displayed, a non-zero period) is not satisfied (e.g., a set of criteria for managing the display of notifications corresponding to the interacted data), the second instance of the first user interface includes a first notification (FIGS. 6G-6H).

[0324] According to a determination that the set of first removal criteria is satisfied, and according to a determination that the set of first removal criteria is satisfied (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 a set of interaction criteria is not satisfied, and in accordance with a determination (716) that a set of second removal criteria including a second criterion based on a second period (e.g., a period that must not be exceeded to meet the second criterion, a period determined since the first data set was received or generated, a period determined since a notification corresponding to the first data set that is longer than the first period was first displayed) is not satisfied, a second instance of the first user interface includes the first notification (FIGS. 6G-6H). In some embodiments, the second period is not longer than the first period.

[0326] In accordance with a determination that a set of interaction criteria is not satisfied, and in accordance with a determination (718) that a set of second removal criteria is satisfied, a second instance of the first user interface does not include the first notification (FIGS. 6G-6H). In some embodiments, a notification is displayed (or redisplayed) within the first user interface over a period that changes based on whether the notification has been interacted with. In some embodiments, a non-interacted notification is displayed over a period that is longer than the period of an interacted notification.

[0327] Displaying the first notification based on whether a set of interaction criteria and a set of removal criteria are satisfied enables the user to view relevant notifications without providing unwanted notifications. By performing an operation when a set of conditions is satisfied without requiring further user input, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.

[0328] In some embodiments, before displaying a first instance of a first user interface, the electronic device receives a second data set from an external device (e.g., a smartwatch including one or more sensors (e.g., biometric sensors)), and the first data set corresponds to the second data set (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 data set is the first data set. In some embodiments, the second 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 second data set. In some embodiments, the second data set is sensor data from one or more sensors of the external device. In some embodiments, the second data set includes clinical health data (e.g., 604b) (e.g., medical records from a health institution, test results from a clinical trial examination).

[0329] In some embodiments, the electronic device includes a set of one or more sensors (e.g., biometric sensors). In some embodiments, before displaying a first instance of a 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, before displaying a first instance of a 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. In some embodiments, the list of first notifications is ordered (e.g., FIG. 6DA) based on chronological or reverse chronological order (e.g., based on an initial notification issuance time, based on the time when data generated or received when each notification was selected).

[0331] Ordering the first list based on a time series or reverse time series structure provides the user with feedback regarding the sequence in which notifications were generated. By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0332] In some embodiments, while displaying the first notification (e.g., within a first instance or a second instance of the first user interface), the electronic device receives a first input (e.g., 615) corresponding to the selection of the first notification. In some embodiments, in response to receiving the first input, the electronic device displays, via the first display device, a second user interface (e.g., 644) that includes (e.g., a 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, displays a first value (e.g., a first average) of the first data type, and a second affordance that, when selected, displays a second value (e.g., a second average based on a filter (e.g., a time filter, a source filter) different from the first average) of the first data type that is different from the first value (e.g., the average at 644 and the daily average affordance).

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

[0335] FIGS. 8A-8B are flow diagrams showing a method for managing the display of health-related information using an electronic device according to some embodiments. Method 800 is executed in a device having a display device (e.g., 100, 300, 500, 600). 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 optionally communicates (e.g., via wired communication, wireless communication) with a display generation component and one or more input devices. 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. The one or more input devices are configured to receive inputs such as a touch-sensitive surface for receiving 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) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device) and can receive inputs from the one or more input devices via a wired or wireless connection.

[0337] As will be described below, method 800 provides an intuitive way to manage the display of health-related information. The method reduces the user's cognitive burden when viewing health-related information, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, by enabling the user to operate more quickly and efficiently for viewing health-related information, power is saved and the time between battery charges is extended.

[0338] The electronic device receives (802) first health data (e.g., physical activities performed by the user, data detected via one or more biometric sensors) (see, e.g., 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 a first user interface (e.g., 614) (804).

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

[0341] In response to receiving the request, the electronic device displays (806), via a display device, a first user interface that includes a second region (e.g., a highlighted region within 614) (810) (e.g., a highlighted 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 according to a determination (816) that a first set of highlighting criteria has been met (e.g., the system determines that the representation corresponding to the health data should be displayed to the user) (e.g., a graphical representation comparing health data for a first health metric over a first period to health data for the first health metric over a second period that is different from the first period). In some embodiments, the representations displayed within the second region are not user-customizable / user-selectable. In some embodiments, the representations displayed in the second region include a comparison of health data corresponding to a period different from the period of the health data with the health data. The second region does not include a second representation of the first health data according to a determination (818) that the first set of highlighting criteria has not been 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 first health data based on a set of satisfied first highlighting criteria, the device can display relevant information and avoid using display space when the information is not relevant. By performing an operation when a set of conditions is satisfied without requiring further user input, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, by enabling the user to use the device more quickly and efficiently, the power consumption of the device is reduced and the battery life is improved.

[0343] In some embodiments, the health data includes health data for a first plurality of periods (e.g., days, weeks, months). In some embodiments, the first representation of the health data includes a first display (e.g., a text display, a graphical display, a display of a first metric (e.g., steps, miles, calories) of the health data corresponding to a first period (e.g., today) of the first plurality of periods, and a second display (e.g., a text display, a graphical display) of the health data corresponding to a second period (e.g., yesterday) of the first plurality of periods that is different from the first period. In some embodiments, the first representation includes a bar graph with today's value, compared to yesterday's value (e.g., 632).

[0344] Providing different instructions for different periods provides the user with feedback regarding the stored data corresponding to each period. By providing the user with improved visual feedback, the operability of the device is improved, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, by enabling the user to use the device more quickly and efficiently, the power consumption is reduced and the battery life of the device is improved.

[0345] In some embodiments, the 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 the week or month). In some embodiments, the second period of the first plurality of periods is a plurality of instances. In some embodiments, it is all instances of the repeating time interval available in the health data of the repeating time interval (e.g., multiple Mondays of multiple weeks, multiple mornings of multiple days). In some embodiments, the first display is the value of the health metric on Monday of the week, and the second display is the average value of the health metric for all Mondays (e.g., 662).

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

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

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

[0349] Displaying a display of health data based on the first and second body activity tracking sessions provides the user with feedback for both sessions using the display. By providing the user with improved visual feedback, the operability of the device is improved, (e.g., assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0350] In some embodiments, the first set of highlighting criteria includes factors selected from the group consisting of the relationship (e.g., a mathematical relationship (e.g., a difference)) between a first portion of health data (e.g., a portion corresponding to a first period (e.g., a day)) and a second portion of health data (e.g., a portion corresponding to a second period (e.g., a week)), the degree of user interaction with the health data, and the period during which the representation (e.g., any representation) of the health data is 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 are grouped together, heart rate related data are grouped together) (e.g., 660).

[0352] Note that the details of the processes described above with respect to method 800 (e.g., FIGS. 8A - 8B) are also applicable in a similar manner to the methods described hereinafter / above. For example, methods 700, 900, 1000, 1100, and 1400 optionally include one or more of the characteristics of the various methods described above with reference to method 800. For the sake of brevity, these details are not repeated hereinafter.

[0353] FIGS. 9A - 9B are flow diagrams showing a method for managing the display of clinical health record representations using an electronic device, according to some embodiments. Method 900 is executed in a device having a display device (e.g., 100, 300, 500, 600, 606). Some operations of 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 optionally communicates (e.g., via wired communication, wireless communication) with a display generation component and one or more input devices. 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. The one or more input devices are configured to receive inputs such as a touch-sensing surface for receiving 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. Accordingly, the computer system can transmit data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive inputs from the one or more input devices via a wired or wireless connection.

[0355] As will be described below, method 900 provides an intuitive method for managing 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. In the case of a battery-operated computing device, it saves power and extends the time between battery charges by enabling the user to access clinical health records faster and more efficiently.

[0356] The electronic device receives (902) clinical health record data corresponding to a specific health institution (e.g., XYZ Medical Center in 672a, 698). The electronic device receives a request (e.g., tap the first health record affordance 636 within the summary user interface 614) (e.g., a request to view all clinical health records of the 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) the 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 a first type of clinical health record (e.g., 668b, 698a, test result area). The first region includes a first text representation (e.g., 672b, 672c, 698b, 698c) for a first clinical health record based on the clinical health record data according to a determination (912) that the 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 does not include the range of the first clinical health record or (in some embodiments) includes binary information that does not achieve a benefit from graphing). The first user interface does not include a graphical representation (e.g., a non - text graphical representation) for the first clinical health record. The first region includes a first graphical representation (e.g., 672d within 668) (e.g., 670b and 670c within 698) for a first clinical health record based on the clinical health record data according to a determination (914) that the first clinical health meets the first set of graphing criteria (e.g., the first clinical health record includes the range of the first clinical health record and (in some embodiments) includes non - binary information that achieves a benefit from graphing).

[0358] In response to receiving the request, the electronic device displays (906), via a display device, a first user interface (910) that includes a second region (e.g., a different date range within 698, a medication region within 668) corresponding to a second type of clinical health record (e.g., a medication region). The second region includes a second textual representation of a second clinical health record based on clinical health record data according to a determination (916) that the second clinical health record of the second type of clinical health record does not meet a first set of graphing criteria (e.g., the second clinical health record does not include the range of the second clinical health record or (in some embodiments) includes binary information that does not achieve a benefit from graphing), and the user interface does not include a graphical representation of the second clinical health record. The second region includes a second graphical representation of a second clinical health record based on clinical health record data according 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 the range of the second clinical health record and (in some embodiments) includes non-binary information that achieves a benefit from graphing).

[0359] Displaying a textual or graphical representation of a health record provides the user with feedback regarding whether the health record meets graphing criteria and enables the user to access information related to the record more quickly and efficiently. By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors) making the user-device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0360] In some embodiments, a first set of graphing criteria for each clinical health record (e.g., a first clinical health record) is satisfied when the health data includes a range of data (e.g., a minimum and a maximum defining the range) for which each clinical health record (e.g., a data value corresponding to each clinical health record) is considered to meet a particular criterion (e.g., a criterion regarding whether the data value is acceptable, such as a criterion set by a regulatory agency) (e.g., 670b, 670c).

[0361] In some embodiments, a first set of graphing criteria for each clinical health recor...

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 first 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 non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the method of any one of claims 1 to 8.

10. 1. An electronic device comprising: A display device; one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 1 to 8.

11. 1. An electronic device comprising: A display device; and means for carrying out the method according to any one of claims 1 to 8.

12. 1. 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 having a display device, 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; 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; a non-transitory computer-readable storage medium comprising instructions, wherein 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.

13. 1. An electronic device comprising: A display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; wherein the one or more programs include: displaying via the display device a first instance of a first user interface including a first notification that, when selected, causes a first data set to be displayed; 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; 23. The electronic device, comprising: instructions for causing the second instance of the first user interface to not include the first notification in accordance with a determination that the interaction criteria is not met and in accordance with a determination that the second set of removal criteria is met.

14. 1. An electronic device comprising: 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 first data set to be displayed; means for 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; 23. The electronic device, comprising: instructions for causing the second instance of the first user interface to not include the first notification in accordance with a determination that the interaction criteria is not met and in accordance with a determination that the second set of removal criteria is met.

15. 1. A method comprising: In an electronic device having a display device, Receiving first health data; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: A first region, in response to a determination that a type of data corresponding to the first health data has been identified by user input, a first representation of the first health data; a first region that does not include the representation of the first health data in response to a determination that the type of data corresponding to the first health data is not identified by user input; and A second region, pursuant to a determination that a first set of highlighting criteria is satisfied, a second representation of the first health data that differs from the first representation; a second region that does not include the second representation of the first health data in accordance with a determination that the first set of highlighting criteria is not met.

16. the health data includes health data for a first plurality of time periods; the first representation of the health data comprising: a first display of the health data corresponding to a first time period of the first plurality of time periods; and a second display of the health data corresponding to a second time period of the first plurality of time periods different from the first time period; and 16. The method of claim 15, comprising:

17. the first period of the first plurality of periods corresponds to a particular instance of a recurring time interval; the second period of the first plurality of periods being a plurality of instances of the repeating time interval.

17. The method of claim 16.

18. the health data includes health data for a second plurality of time periods; the first representation of the health data includes a third display of the health data corresponding to a frequency of occurrence of a first health event within the second plurality of time periods.

18. The method according to any one of claims 15 to 17.

19. the health data includes a third plurality of time periods of health data; the first representation of the health data comprising: a fourth display of average values ​​of the health data for the third plurality of time periods; and a fifth indicia corresponding to the value of the health data for a first time period of the third plurality of time periods; and a sixth indicia corresponding to the 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 third plurality of time periods; and 19. The method of any one of claims 15 to 18, comprising:

20. The first representation is a seventh display corresponding to the first physical activity tracking session; and an eighth display corresponding to the second physical activity tracking session; and and a ninth display of the health data based on the first physical activity tracking session and the second physical activity tracking session.

21. 21. The method of any one of claims 15 to 20, wherein the first set of highlighting criteria comprises criteria based on factors selected from the group consisting of: a relationship between the first portion of the health data and the second portion of the health data, a degree of user interaction with the health data, and a duration for which the representation of the health data has been displayed.

22. the first expression is included in a first list of expressions; 22. The method of any one of claims 15 to 21, wherein the first list of representations is ordered based on a type of data of the health data.

23. 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 having a display device, the one or more programs including instructions for performing the method of any one of claims 15 to 22.

24. 1. An electronic device comprising: A display device; one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 15 to 22.

25. 1. An electronic device comprising: A display device; and means for carrying out the method according to any one of claims 15 to 22.

26. 1. 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 having a display device, the one or more programs comprising: receiving first health data; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: A first region, in response to a determination that a type of data corresponding to the first health data has been identified by user input, a first representation of the first health data; a first region that does not include the representation of the first health data in response to a determination that the type of data corresponding to the first health data is not identified by user input; and A second region, pursuant to a determination that a first set of highlighting criteria is satisfied, a second representation of the first health data that differs from the first representation; a second region that does not include the second representation of the first health data in accordance with a determination that the first set of highlighting criteria is not met.

27. 1. An electronic device comprising: A display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; wherein the one or more programs include: receiving first health data; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: A first region, in response to a determination that a type of data corresponding to the first health data has been identified by user input, a first representation of the first health data; a first region that does not include the representation of the first health data in response to a determination that the type of data corresponding to the first health data is not identified by user input; and A second region, pursuant to a determination that a first set of highlighting criteria is satisfied, a second representation of the first health data that differs from the first representation; a second region that does not include the second representation of the first health data in accordance with a determination that the first set of highlighting criteria is not met.

28. 1. An electronic device comprising: A display device; means for receiving first health data; means for receiving a request to display a first user interface; means for displaying the first user interface via the display device in response to receiving the request, the first user interface comprising: A first region, in response to a determination that a type of data corresponding to the first health data has been identified by user input, a first representation of the first health data; a first region that does not include the representation of the first health data in response to a determination that the type of data corresponding to the first health data is not identified by user input; and A second region, pursuant to a determination that a first set of highlighting criteria is satisfied, a second representation of the first health data that differs from the first representation; a second region that does not include the second representation of the first health data in accordance with a determination that the first set of highlighting criteria is not met.

29. 1. A method comprising: In an electronic device having a display device, 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 the first user interface via the display device, the first user interface comprising: a first region corresponding to a first type of clinical health record, a first textual representation for the first clinical health record based on the clinical health record data in accordance with a determination that a first clinical health record of the first type of clinical health record does not satisfy a first set of graphing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and 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 clinical health satisfies the first set of graphing criteria; a second field corresponding to a second type of clinical health record, a second textual representation for the second clinical health record based on the clinical health record data in accordance with a determination that a second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and 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.

30. 30. The method of claim 29, wherein the first set of graphing criteria is met for each clinical health record when the respective clinical health record corresponds to health data that includes a range of data.

31. 31. The method of any one of claims 29 to 30, wherein the first set of graphing criteria is not met for the respective clinical health record when the respective clinical health record corresponds to health data that is binary.

32. the first domain includes a plurality of representations of clinical health records; the plurality of representations are ordered primarily by date and secondarily by a health record type associated with a respective clinical health record of each representation of the plurality of representations; 32. The method of any one of claims 29 to 31.

33. the first region includes a second plurality of representations of clinical health records; the second plurality of representations being ordered primarily by health record type and secondarily by a date associated with a respective clinical health record of each representation of the second plurality of representations; 33. The method of any one of claims 29 to 32.

34. the first region includes a third plurality of representations of clinical health records corresponding respectively to clinical health records associated with a first date and a second date different from the first date, the third plurality of representations comprising: upon determining that the first user interface is a first interface type, by the first date; and ordered by the second date in accordance with a determination that the first user interface is of a second interface type different from the first interface type; 34. The method of any one of claims 29 to 33.

35. 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 having a display device, the one or more programs including instructions for performing the method of any one of claims 29 to 34.

36. 1. An electronic device comprising: A display device; one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 29 to 34.

37. 1. An electronic device comprising: A display device; and means for carrying out the method according to any one of claims 29 to 34.

38. 1. 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 having a display device, the one or more programs comprising: receiving clinical health record data corresponding to a particular health institution; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: a first region corresponding to a first type of clinical health record, a first textual representation for the first clinical health record based on the clinical health record data in accordance with a determination that a first clinical health record of the first type of clinical health record does not satisfy a first set of graphing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and 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 clinical health satisfies the first set of graphing criteria; a second field corresponding to a second type of clinical health record, a second textual representation for the second clinical health record based on the clinical health record data in accordance with a determination that a second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and and a second region including 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.

39. 1. An electronic device comprising: A display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; wherein the one or more programs include: receiving clinical health record data corresponding to a particular health institution; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: a first region corresponding to a first type of clinical health record, a first textual representation for the first clinical health record based on the clinical health record data in accordance with a determination that a first clinical health record of the first type of clinical health record does not satisfy a first set of graphing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and 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 clinical health satisfies the first set of graphing criteria; a second field corresponding to a second type of clinical health record, a second textual representation for the second clinical health record based on the clinical health record data in accordance with a determination that a second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and and a second area including 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.

40. 1. An electronic device comprising: 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; means for displaying the first user interface via the display device in response to receiving the request, the first user interface comprising: a first region corresponding to a first type of clinical health record, a first textual representation for the first clinical health record based on the clinical health record data in accordance with a determination that a first clinical health record of the first type of clinical health record does not satisfy a first set of graphing criteria, wherein the first user interface does not include a graphical representation of the first clinical health record; and 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 clinical health satisfies the first set of graphing criteria; a second field corresponding to a second type of clinical health record, a second textual representation for the second clinical health record based on the clinical health record data in accordance with a determination that a second clinical health record of the second type of clinical health record does not satisfy the first set of graphing criteria, wherein the user interface does not include a graphical representation of the second clinical health record; and and a second area including 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.

41. 1. A method comprising: In an electronic device having a display device, receiving clinical health record data; first clinical health record data corresponding to a first type of clinical health record; receiving said clinical health record data including second clinical health record data corresponding to a second type of clinical health record; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: displaying the first user interface including a first representation for a first clinical health record of the first type of clinical health record based on the first clinical health record data; receiving a first user input corresponding to a selection of the first representation while displaying the first user interface; In response to receiving the first user input, displaying a second user interface via the display device, a second representation for the first clinical health record of the first type based on the first clinical health record data, the second representation being different from the first representation; displaying the second user interface based on the first clinical health record data, the third representation being different from the second representation for a second clinical health record of the first type, 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 corresponding to a selection of the third representation while displaying the second user interface; In response to receiving the second user input, and displaying via the display device a third user interface including a fourth representation of the first clinical health record of the first type based on the first clinical health record data, the fourth representation being different from the first representation and different from the second representation.

42. 42. The method of claim 41, wherein the request to display the first user interface is received while displaying, via the display device, a fourth user interface including a fifth representation of a second clinical health record of the second type of clinical health record based on the second clinical health record data.

43. the fourth user interface includes a plurality of representations of a clinical health record; the plurality of representations are ordered primarily by date and secondarily by a health record type associated with a respective clinical health record of each representation of the plurality of representations; 43. The method of claim 42.

44. the second user interface includes a second plurality of representations of clinical health records; the second plurality of representations is ordered by date; 44. The method of any one of claims 41 to 43.

45. The first representation is a graphical display of the first clinical health record in response to a determination that a first set of graphical criteria is satisfied; 45. The method of any one of claims 41 to 44, not including a graphical display of the first clinical health record pursuant to a determination that a first set of graphical criteria is not met.

46. the first representation includes first details of the first clinical health record; the second representation includes first details of the first clinical health record and second details different from the first details; the fourth representation includes the first details, the second details, and a third detail of the first clinical health record, the third detail being different from the first and second details; 46. ​​The method of any one of claims 41 to 45.

47. the second user interface including a graphical representation of a first portion of the first clinical health record data; 47. The method of any one of claims 41 to 46.

48. The second user interface includes a first affordance, and the method further comprises: Receiving an input corresponding to a selection of the first affordance; 48. The method of claim 47, comprising: in response to receiving the input corresponding to a selection of the first affordance, visually distinguishing a portion of the graphical representation that corresponds to a first sub-portion of the first portion of the first clinical health record data that matches a first filter condition.

49. the first clinical health record of the first type of clinical health record is received from a first data source; the second clinical health record of the first type of clinical health record was received from a second data source different from the first data source; 49. The method of any one of claims 41 to 48.

50. 50. The method of any one of claims 41 to 49, wherein the fourth representation comprises a representation of a data source of the first clinical health record.

51. 51. The method of any one of claims 41 to 50, wherein the fourth representation includes an indication of a primary identifier of the first type of clinical health record and a secondary identifier of the first type of clinical health record.

52. 52. The method of any one of claims 41 to 51, wherein the fourth representation includes an indication of a first date corresponding to when the first clinical health record was received by the electronic device and an indication of a second date corresponding to when the first clinical health record was created.

53. 53. 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 having a display device, the one or more programs including instructions for performing a method according to any one of claims 41 to 52.

54. 1. An electronic device comprising: A display device; one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 41 to 52.

55. 1. An electronic device comprising: A display device; and means for carrying out the method according to any one of claims 41 to 52.

56. 1. 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 having a display device, the one or more programs comprising: receiving clinical health record data; first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: displaying the first user interface including a first representation for a first clinical health record of the first type of clinical health record based on the first clinical health record data; receiving a first user input corresponding to a selection of the first representation while displaying the first user interface; In response to receiving the first user input, displaying a second user interface via the display device, a second representation for the first clinical health record of the first type based on the first clinical health record data, the second representation being different from the first representation; displaying the second user interface based on the first clinical health record data, the third representation being different from the second representation for a second clinical health record of the first type, 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 corresponding to a selection of the third representation while displaying the second user interface; In response to receiving the second user input, and displaying, via the display device, a third user interface including a fourth representation for the first clinical health record of the first type of clinical health record based on the first clinical health record data, the fourth representation being different from the first representation and different from the second representation.

57. 1. An electronic device comprising: A display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; wherein the one or more programs include: receiving clinical health record data; first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record; Receiving a request to display a first user interface; In response to receiving the request, displaying the first user interface via the display device, the first user interface comprising: displaying the first user interface including a first representation for a first clinical health record of the first type of clinical health record based on the first clinical health record data; receiving a first user input corresponding to a selection of the first representation while displaying the first user interface; In response to receiving the first user input, displaying a second user interface via the display device, a second representation for the first clinical health record of the first type based on the first clinical health record data, the second representation being different from the first representation; displaying the second user interface based on the first clinical health record data, the third representation being different from the second representation for a second clinical health record of the first type, 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 corresponding to a selection of the third representation while displaying the second user interface; In response to receiving the second user input, and instructions for displaying, via the display device, a third user interface including a fourth representation of the first clinical health record of the first type based on the first clinical health record data, the fourth representation being different from the first representation and different from the second representation.

58. 1. An electronic device comprising: A display device; receiving clinical health record data; first clinical health record data corresponding to a first type of clinical health record; and second clinical health record data corresponding to a second type of clinical health record. means for receiving a request to display a first user interface; means for displaying, via the display device, the first user interface in response to receiving the request, the first user interface comprising: means for displaying the first user interface including a first representation for a first clinical health record of the first type of clinical health record based on the first clinical health record data; means for receiving, while displaying the first user interface, a first user input corresponding to a selection of the first representation; In response to receiving the first user input, a means for displaying a second user interface via the display device, a second representation for the first clinical health record of the first type based on the first clinical health record data, the second representation being different from the first representation; means for displaying the second user interface based on the first clinical health record data, the third representation being different from the second representation for a second clinical health record of the first type, the second clinical health record of the first type being different from the first clinical health record of the first type; means for receiving, while displaying the second user interface, a second user input corresponding to a selection of the third representation; In response to receiving the second user input, and means for displaying, via the display device, a third user interface including a fourth representation of the first clinical health record of the first type based on the first clinical health record data, the fourth representation being different from the first representation and different from the second representation.

59. 1. A method comprising:

1. An electronic device associated with a first user, the electronic device comprising a display device, Receiving a request to display a first user interface; In response to receiving the first request, displaying the first user interface via the display device, the first user interface comprising: a first portion including a first category affordance; a second portion including a first shared affordance corresponding to a second user account; and 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 displaying, in response to receiving the first user input, via the display device, a second user interface including a representation of the first health data associated with the first user account for the first category; displaying, via the display device, a third user interface in response to receiving the second user input; A first portion, displaying 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; 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 health data associated with the second user account for the first category.

60. 60. The method of claim 59, wherein the first health data associated with the first user account for the first category is also associated with the first user account for a second category.

61. 61. The method of any one of claims 59 to 60, wherein the fourth user interface does not include an option for modifying the representation of health data associated with the second user account for the first category.

62. receiving, while displaying the first user interface, a first set of inputs corresponding to a request to search health data accessible to the electronic device, the first set of inputs including one or more inputs corresponding to entering a search string; displaying a plurality of search results in response to receiving the set of inputs; a first set of one or more search results including a representation of second health data associated with the first user account, the second health data associated with the first user account being associated with a first source; and displaying the plurality of search results including a second set of one or more search results including a representation of third health data associated with the first user account, where the third health data associated with the first user account is associated with a second source different from the first source; and 62. The method of any one of claims 59 to 61, further comprising:

63. displaying the plurality of search results includes ceasing to display the first portion and the second portion of the first user interface.

63. The method of claim 62.

64. 64. The method of any one of claims 59 to 63, wherein the first user interface includes a third portion including a first health record affordance that, when selected, displays a representation of health data associated with the first user account received from a first external source.

65. the representation of health data associated with the first user account for the first category corresponds to health data that meets a set of formatting criteria; the third portion includes a first affordance, and the method further comprises: receiving a fourth user input corresponding to a selection of the first affordance; and and in response to receiving the fourth user input, displaying a set of health data that does not meet the set of formatting criteria.

65. The method of claim 64.

66. 66. 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 having a display device, the one or more programs including instructions for performing a method according to any one of claims 59 to 65.

67. 1. An electronic device associated with a first user account, comprising: A display device; one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 59 to 65.

68. 1. An electronic device associated with a first user account, comprising: A display device; Means for carrying out the method according to any one of claims 59 to 65; An electronic device comprising:

69. 1. 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, the one or more programs comprising: Receiving a request to display a first user interface; In response to receiving the first request, displaying the first user interface via the display device, the first user interface comprising: a first portion including a first category affordance; a second portion including a first shared affordance corresponding to a second user account; and 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; displaying, in response to receiving the first user input, via the display device, a second user interface including a representation of the first health data associated with the first user account for the first category; displaying, via the display device, a third user interface in response to receiving the second user input; A first portion, displaying 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; receiving a third user input corresponding to a selection of the second category affordance while displaying the third user interface; responsive to receiving the third user input, displaying via the display device a fourth user interface including a representation of health data associated with the second user account for the first category.

70. 1. An electronic device associated with a first user account, comprising: A display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; wherein the one or more programs include: Receiving a request to display a first user interface; In response to receiving the first request, displaying the first user interface via the display device, the first user interface comprising: a first portion including a first category affordance; a second portion including a first shared affordance corresponding to a second user account; and 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; displaying, in response to receiving the first user input, via the display device, a second user interface including a representation of the first health data associated with the first user account for the first category; displaying, via the display device, a third user interface in response to receiving the second user input; A first portion, displaying 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; receiving a third user input corresponding to a selection of the second category affordance while displaying the third user interface; responsive to receiving the third user input, displaying via the display device a fourth user interface including a representation of health data associated with the second user account for the first category.

71. 1. An electronic device associated with a first user account, comprising: A display device; means for receiving a request to display a first user interface; means for displaying, via the display device, the first user interface in response to receiving the request, the first user interface comprising: a first portion including a first category affordance; a second portion including a first shared affordance corresponding to a second user account; and While displaying the first user interface, receiving a first user input corresponding to a selection of the first category affordance; means for receiving a second user input corresponding to a selection of the first shared affordance; means for displaying, in response to receiving the first user input, 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; means for displaying, via the display device, a third user interface in response to receiving the second user input, the means comprising: A first portion, means for displaying 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, while displaying the third user interface, a third user input corresponding to a selection of the second category affordance; and means for displaying, in response to receiving the third user input, via the display device a fourth user interface including a representation of health data associated with the second user account for the first category.

72. 1. A method comprising: A first electronic device having a display device, 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 that includes a first affordance that, when selected, initiates a process for sharing 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 health data associated with the first electronic device with the second electronic device; after receiving the first user input; Sharing 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 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.

73. receiving a set of one or more inputs including an input corresponding to a selection of the second affordance while displaying the second notification; in response to receiving the one or more set of inputs, ceasing to share health data associated with the first electronic device with the second electronic device; and 73. The method of claim 72, further comprising:

74. sharing health data associated with the first electronic device with a third electronic device after receiving the first user input; continuing to share health data associated with the first electronic device with the third electronic device after receiving the one or more sets of inputs; 74. The method of claim 73, further comprising:

75. When the first notification is selected, causing the first electronic device to refrain from initiating a process for sharing health data associated with the first electronic device with the second electronic device; 75. The method of any one of claims 72 to 74, comprising a third affordance that causes the first electronic device to send a request to a fourth electronic device to accept health data associated with the first electronic device.

76. When the first notification is selected, causing the first electronic device to refrain from initiating a process for sharing health data associated with the first electronic device with the second electronic device; 76. The method of any one of claims 72 to 75, comprising a fourth affordance that causes the first electronic device to send a request to a fifth electronic device to accept health data associated with the first electronic device.

77. 77. The method of any one of claims 72 to 76, wherein the first electronic device is associated with a first user account and the second electronic device is associated with a second user account that is different from the first user account.

78. 80. 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 having a display device, the one or more programs including instructions for performing a method according to any one of claims 72 to 77.

79. A first electronic device, A display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 72 to 77.

80. A first electronic device, A display device; and means for performing the method of any one of claims 72 to 77.

81. 1. 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 having a display device, 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, display, at a first time, via the display device, a first notification that includes a first affordance that, when selected, initiates a process for sharing 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, initiate a process for sharing health data associated with the first electronic device with the second electronic device; after receiving the first user input; Sharing health data associated with the first electronic device with the second electronic device; displaying, via the display device, a second notification corresponding to the sharing of 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.

82. A first electronic device, A display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; wherein the one or more programs include: receiving a request to share health data associated with the first electronic device; in response to receiving the request, display, at a first time, via the display device, a first notification that includes a first affordance that, when selected, initiates a process for sharing 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, initiate a process for sharing health data associated with the first electronic device with the second electronic device; after receiving the first user input; Sharing health data associated with the first electronic device with the second electronic device; and displaying, via the display device, a second notification corresponding to the sharing of health data, the second notification including a second affordance that, when selected, initiates a process for terminating the sharing of health data associated with the first electronic device with the second electronic device.

83. A first electronic device, A display device; means for receiving a request to share health data associated with the first electronic device; means for displaying, at a first time, via the display device, in response to receiving the request, a first notification that includes a first affordance that, when selected, initiates a process for sharing health data associated with the first electronic device with a second electronic device; means for receiving a first user input corresponding to a selection of the first affordance while displaying the notification; means for initiating a process for sharing health data associated with the first electronic device with the second electronic device in response to receiving the first user input; after receiving the first user input; Sharing health data associated with the first electronic device with the second electronic device; and displaying via the display device a second notification corresponding to the sharing of 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.

Images