Systems and methods for displaying aggregated health records

Abstract

To provide a method for displaying aggregated health records on an electronic device.SOLUTION: A method includes receiving a request to display health records for a user while an electronic device is associated with one health care provider and displaying categories of health records in response to receiving a first request, and selection of a category while the device is associated with the health care provider causes the device to display health records of the category from the health care provider. The method also includes receiving a second request to display health records for the user while the device is associated with two health care providers, and selection of a category while the device is associated with both health care providers causes the device to display health records in the category selected from both health care providers.SELECTED DRAWING: Figure 7A

Description

[Technical field]

[0001] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for displaying aggregated health records. [Background technology]

[0002] Healthcare providers may provide patients with paper copies of health records. Paper copies of health records are easily lost and deteriorated. Some digitalized healthcare providers provide patients with electronic copies of health records. However, current methods for displaying health records on electronic devices are outdated, cumbersome, and inefficient. For example, some existing methods use complex and time-consuming user interfaces that may provide users with only a limited amount of health records despite multiple key presses or key entries. In addition, the methods take longer than necessary, thereby wasting energy. The latter problem is particularly critical in battery-operated devices.

[0003] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users. Summary of the Invention

[0004] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for displaying aggregated health records. Such methods and interfaces optionally complement or replace other methods for displaying health records. Such methods and interfaces reduce the number, extent, and / or type of inputs from a user, reducing the cognitive burden on the user and creating a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0005] The above deficiencies and other problems associated with user interfaces for electronic devices (e.g., having a touch-sensitive surface) are reduced or eliminated by the devices of the present disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, a tablet computer, or a handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory for performing a number of functions. In some embodiments, a user interacts with the GUI primarily through stylus and / or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functionality optionally includes image editing, drawing, presenting, word processing, spreadsheet creation, game playing, making phone calls, video conferencing, emailing, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note taking, and / or digital video playback, and executable instructions to perform those functionality are optionally contained on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0006] According to some embodiments, a method is performed on an electronic device comprising a display and one or more input devices. The method includes receiving, via the one or more input devices, a first request to view health records for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider. The method also includes displaying a representation of a plurality of health record categories on the display in response to receiving the first request to view health records for the first user. The representation of the plurality of health record categories includes a first representation of a first category of the plurality of categories, where selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider. The representation of the plurality of health record categories also includes a second representation of a second category of the plurality of categories, where selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider. The method also includes receiving, after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider, a second request to display health records for the first user via the one or more input devices. The method also includes displaying the representation of the plurality of health record categories on the display in response to receiving the second request to display health records for the first user. The representations of the plurality of health record categories include a first representation of a first category of the plurality of categories, where selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider.The representation of the plurality of health record categories also includes a second representation of a second category of the plurality of categories, where selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider.

[0007] According to some embodiments, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to receive, via the one or more input devices, a first request to display health records for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider. The instructions also cause the electronic device to display a representation of a plurality of health record categories on the display in response to receiving the first request to display health records for the first user. The representation of the plurality of health record categories includes a first representation of a first category of the plurality of categories, where selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider. The representation of the plurality of health record categories also includes a second representation of a second category of the plurality of categories, where selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider. The instructions, when executed, also cause the electronic device to receive, via the one or more input devices, a second request to display health records for the first user after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider. The instructions also cause the device to display on the display a representation of the plurality of health record categories in response to receiving the second request to display health records for the first user.The representation of the plurality of health record categories includes a first representation of a first category of the plurality of categories, where selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider. The representation of the plurality of health record categories also includes a second representation of a second category of the plurality of categories, where selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider.

[0008] According to some embodiments, a method is performed on an electronic device comprising a display and one or more input devices. The method includes receiving, via the one or more input devices, a request to display health record summary information for the first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type. The method also includes displaying the health record summary information for the first user on the display, including simultaneously displaying the plurality of health record items in response to receiving the request. The plurality of health record items include a first health record item of a first type at a first date, where the health record summary information does not include the plurality of health record items of the first type at a date earlier than the first date. The plurality of health record items also include a second health record item of a second type at a second date different from the first date, where the health record summary information does not include the plurality of health record items of the second type at a date earlier than the second date.

[0009] According to some embodiments, a non-transitory computer readable storage medium stores one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to receive, via the one or more input devices, a request to display health record summary information for a first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type. The instructions also cause the device to display the health record summary information for the first user on the display, including simultaneously displaying the plurality of health record items, in response to receiving the request. The plurality of health record items include a first health record item of a first type at a first date, where the health record summary information does not include the plurality of health record items of the first type at a date earlier than the first date. The plurality of health record items also include a second health record item of a second type at a second date different from the first date, where the health record summary information does not include the plurality of health record items of the second type at a date earlier than the second date.

[0010] According to some embodiments, a method is executed on an electronic device comprising a display and one or more input devices. The method includes displaying a first representation of a first health condition of a plurality of ongoing health conditions of the user as indicated by health record information from the one or more healthcare providers while the electronic device is associated with the one or more healthcare providers of the user. The method also includes receiving, while displaying the first representation of the first ongoing health condition, a request to mark the first ongoing health condition as inactive for the user via the one or more input devices. The method also includes receiving, after receiving the request to mark the first ongoing health condition as inactive, a request to display ongoing health conditions for the user via the one or more input devices. In response to receiving the request to display ongoing health conditions for the user, the method also includes simultaneously displaying on the display a second representation of a second ongoing health condition of the user from the plurality of ongoing health conditions as indicated by health record information from the one or more healthcare providers and a third representation of a third ongoing health condition of the user from the plurality of ongoing health conditions as indicated by health record information from the one or more healthcare providers, without displaying the first representation of the first ongoing health condition of the user as an active health condition.

[0011] According to some embodiments, a non-transitory computer-readable storage medium stores one or more programs, which when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device, the electronic device associated with one or more healthcare providers, to receive a request via the one or more input devices to mark a first ongoing health condition as inactive for the user while displaying the first representation of the first ongoing health condition. The instructions also cause the electronic device to receive a request via the one or more input devices to display an ongoing health condition for the user after receiving the request to mark the first ongoing health condition as inactive. The instructions also cause the electronic device, in response to receiving the request to display the ongoing health condition for the user, to simultaneously display on the display a second representation of a second ongoing health condition of the user from the multiple ongoing health conditions indicated by the health record information from the one or more healthcare providers and a third representation of a third ongoing health condition of the user from the multiple ongoing health conditions indicated by the health record information from the one or more healthcare providers, without displaying the first representation of the first ongoing health condition of the user as an active health condition.

[0012] In some embodiments, the electronic device includes a display, one or more input devices, one or more processors, and a memory storing one or more programs. The one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions to perform or cause the operation of any of the methods described herein. According to some embodiments, a computer-readable storage medium stores therein instructions that, when executed by an electronic device comprising a display and one or more input devices, cause the device to perform or cause the operation of any of the methods disclosed herein. According to some embodiments, a graphical user interface on an electronic device comprising a display, one or more input devices, a memory, and one or more processors executing one or more programs stored in the memory includes one or more of the elements displayed in any of the methods disclosed herein, which are updated in response to an input as described in any of the methods disclosed herein. According to some embodiments, the electronic device includes a display, one or more input devices, and means for performing or causing the operation of any of the methods disclosed herein. According to some embodiments, an information processing apparatus for use in an electronic device having a display and one or more input devices includes means for performing or causing the operations of any of the methods disclosed herein.

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

[0014] This provides devices with faster, more efficient methods and interfaces for displaying aggregated health records, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for displaying aggregated health records. [Brief description of the drawings]

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

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

[0017] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

[0018] [Diagram 2] 1 illustrates a portable multifunction device having a touch screen according to some embodiments.

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

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

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

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

[0023] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.

[0024] [Figure 6A] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6B] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6B-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6C] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6D] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6E] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6E-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6F] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6G] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6H] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6H-1]1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6I] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6J] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6J-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6K] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6K-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6L] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6L-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6M] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6M-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6N] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6O] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6O-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6P] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6P-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6Q] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments. [Figure 6Q-1] 1 illustrates an example user interface for viewing aggregated health records according to some embodiments.

[0025] [Figure 7A] FIG. 1 is a flow diagram illustrating a process for displaying aggregated health records according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a process for displaying aggregated health records according to some embodiments. [Figure 7C] FIG. 1 is a flow diagram illustrating a process for displaying aggregated health records according to some embodiments. [Figure 7D] FIG. 1 is a flow diagram illustrating a process for displaying aggregated health records according to some embodiments. [Figure 7E] FIG. 1 is a flow diagram illustrating a process for displaying aggregated health records according to some embodiments. [Figure 7F] FIG. 1 is a flow diagram illustrating a process for displaying aggregated health records according to some embodiments.

[0026] [Figure 8A] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8B] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8B-1] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8C]1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8C-1] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8D] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8E] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8F] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8G] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8H] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8I] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8J] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8K] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8L] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8M] 1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments. [Figure 8N]1 illustrates an example dashboard user interface for viewing aggregated health records according to some embodiments.

[0027] [Figure 9A] FIG. 1 is a flow diagram of a process for displaying a dashboard user interface with aggregated health records according to some embodiments. [Figure 9B] FIG. 1 is a flow diagram of a process for displaying a dashboard user interface with aggregated health records according to some embodiments. [Figure 9C] FIG. 1 is a flow diagram of a process for displaying a dashboard user interface with aggregated health records according to some embodiments. [Figure 9D] FIG. 1 is a flow diagram of a process for displaying a dashboard user interface with aggregated health records according to some embodiments.

[0028] [Figure 10A] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10B] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10C] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10D] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10E] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10F] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10G] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10H] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10I] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10J] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10K] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10L] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10M] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10N] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10O]1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10P] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 10Q] 1 illustrates an example user interface for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments.

[0029] [Figure 11A] FIG. 1 is a flow diagram illustrating a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 11B] FIG. 1 is a flow diagram illustrating a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 11C] FIG. 1 is a flow diagram illustrating a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 11D] FIG. 1 is a flow diagram illustrating a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. [Figure 11E] FIG. 1 is a flow diagram illustrating a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0031] There is a need for an electronic device that provides an efficient method and interface for displaying aggregated health records in a common interface. Using such a common interface can avoid the risk that a user can only view a portion of the health records relevant to a given concern or question in the interface. Using such a common interface also improves a user's efficiency in viewing the user's health records by reducing the need to navigate multiple user interfaces to view the health records displayed in the interface. Such techniques can reduce the cognitive burden on a user accessing the user's health records, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0032] 1A-1B, 2, 3, 4A-4B, and 5A-5B below describe an exemplary device that performs the techniques for displaying aggregated health records. FIGS. 6A-6Q-1 show an exemplary user interface for displaying aggregated health records. FIGS. 7A-7F are flow diagrams illustrating a method for displaying aggregated health records according to some embodiments. The user interfaces of FIGS. 6A-6Q-1 are used to illustrate the processes described below, including the processes of FIGS. 7A-7F. FIGS. 8A-8N show an exemplary dashboard user interface for displaying aggregated health records. FIGS. 9A-9D are flow diagrams illustrating a method for displaying a dashboard user interface with aggregated health records according to some embodiments. The user interfaces of FIGS. 8A-8N are used to illustrate the processes described below, including the processes of FIGS. 9A-9D. FIGS. 10A-10Q show an exemplary user interface for displaying a health record manager that allows a user to specify the status of a particular health record. 11A-11E are flow diagrams illustrating a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to some embodiments. The user interfaces of FIGS. 10A-10Q are used to illustrate the processes described below, including the processes of FIGS. 11A-11E.

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

[0034] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments described and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It is also to be understood that the term "and / or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. The term "if" is further interpreted to mean "when" or "upon," or "in response to determining" or "in response to detecting," depending on the context, as appropriate.

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

[0036] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptop or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touchscreen displays and / or touchpads).

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

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

[0039] The various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

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

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

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

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

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

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

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

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

[0048] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

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

[0050] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or transmits electrical signals from touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

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

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

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

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

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

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

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

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

[0060] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to an input controller 160 within I / O subsystem 106. The proximity sensor 166 optionally functions as described in U.S. Patent Application 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 incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

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

[0062] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed on the touchscreen display in portrait or landscape view based on analysis of data received from the one or more accelerometers. Device 100 optionally includes a magnetometer (not shown), in addition to accelerometer(s) 168, and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0081] In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 contains executable instructions for creating workouts (e.g., having time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor the workouts, selecting and playing music for workouts, and displaying, storing, and transmitting the workout data.

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

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

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

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

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

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

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

[0089] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 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, as well as executable instructions for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

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

[0091] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device's attitude).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0134] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

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

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

[0137] The memory 518 of the personal electronic device 500 can include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, can, for example, cause the computer processors to perform the techniques described below, including processes 700, 900, and 1100 (FIGS. 7A-7F, 9A-9D, and 11A-11E). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium 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 technology, as well as resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

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

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

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

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

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

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

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

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

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

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

[0148] 6A-6Q-1 show exemplary user interfaces for displaying aggregated health records to a user, according to some embodiments. For convenience, the health record is described herein as the user's health record. However, the health record may also be the health record of a family member or other individual associated with the user of the exemplary user interface. The user interfaces in those figures are used to illustrate the processes described below, including the processes in FIGS. 7A-7F.

[0149] Although some of the examples below are described with reference to input on a touch screen display (combining a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from display 450, as shown in FIG. 4B. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, an audio interface, or other suitable interface. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is, optionally, a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., an enantiomeric center of the respective contact or a point associated with the respective contact), or an enantiomeric center of two or more contacts detected on touch-sensitive display system 112. However, similar operations are performed on a device having display 450 and a separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying a user interface described below, optionally with a focus selector.

[0150] 6A-6Q-1 illustrate exemplary user interfaces for viewing a user's aggregated health records, according to some embodiments. The user interfaces of FIGS. 6A-6Q-1 allow a user to review the user's health records from one or more healthcare providers. Such user interfaces present the user's health records in an organized manner that allows the user to quickly and efficiently browse the user's health records. More specifically, the health records of FIGS. 6A-6Q-1 are categorized into a number of categories. In the illustrated embodiment, such categories include allergies, clinical documentation, test results, medications, and health conditions. However, in alternative embodiments, additional or different categories or groupings may be utilized to categorize the health records. The user interfaces also present existing health records and updates to new health records in an organized manner that integrates existing health records and updates to existing health records and new health records.

[0151] In one embodiment, to obtain the user's health information for display in the exemplary user interfaces shown in FIGS. 6A-6Q-1, the user accesses one or more user interfaces ("onboarding user interfaces") not shown herein to begin, continue, or complete an onboarding process with a healthcare provider. In some embodiments, the user accesses the user interface by interacting with the healthcare provider affordance 5302 while the user interface shown in FIG. 6A or a similar user interface is displayed on the display 112. The user may periodically access the onboarding user interface to begin an onboarding process for a new healthcare provider, to review information about an existing healthcare provider for which the user has completed an onboarding process, to contact the healthcare provider, to update information about the healthcare provider, or to remove a healthcare provider. Once the onboarding process with the healthcare provider is completed, the device 100 obtains access to the user's health record from the healthcare provider and displays the healthcare provider's health record on the display 112. In some embodiments, the device 100 displays the user interface shown in FIG. 6A on the display 112 in response to determining that the onboarding process is completed. In other embodiments, the onboarding user interface includes a toolbar 5029 having a health data affordance 5029A as shown in Figure 6A. In such embodiments, the user interacts with the health data affordance 5029A to access Figure 6A.

[0152] FIG 6A illustrates an embodiment displaying representations of a user's health record categories from one or more healthcare providers. FIG 6A includes category representations 5006A, 5006B, 5006C, 5006D, and 5006E, as well as all records representation 5006F associated with all of the user's health records. In the illustrated embodiment, category representation 5006A is associated with allergy health records, category representation 5006B is associated with clinical documents, category representation 5006C is associated with lab results, category representation 5006D is associated with medications, and category representation 5006E is associated with health conditions. Each of category representations 5006A-5006E is an affordance that includes text indicating that such affordance is associated with health records from a particular category. Each of category representations 5006A-5006E is selectable by a user to view the user's health records from the associated category. In some embodiments, the category representations 5006A-5006E also include a description of the corresponding category, a summary of the health records included in the corresponding category, or other information related to the corresponding category. For example, the category representation 5006E may include information summarizing the user's different ongoing health conditions. The all records representation 5006F is an affordance that includes text indicating that such affordance is associated with all health records. The all records representation 5006F is selectable by the user to view all health records of the user. FIGS. 6A-6B illustrate detecting a tap gesture (e.g., a tap gesture with contact 5502 in FIG. 6A ) on an affordance (medication category representation 5006D) and displaying health records (e.g., medication records 5018A and 5018B in FIG. 6B ) corresponding to the health record category associated with the affordance in response to the tap gesture.

[0153] 6B shows a display of health records associated with the medication category representation 5006D shown in FIG. 6A. More specifically, medication records 5018A and 5018B (ABC and DEF medications) are displayed. In the illustrated embodiment, medication records 5018A and 5018B are health records of medications taken by a user and include text identifying the name of the medication (ABC and DEF medications, respectively), the healthcare provider who prescribed the medication (Alpha Health Care in both records), and the date the medication was prescribed (October 1, 2017 and September 1, 2017, respectively). The healthcare provider may be the name of one or more physicians, a medical organization such as a home healthcare organization or hospital group, or a designation of a particular facility or location where treatment was provided, such as a particular hospital or clinic. In other embodiments, text or images may be displayed within the medication records 5018A and 5018B that represent further information about the medication, such as the pharmacist who prescribed the medication, the refill or expiration date of the medication, instructions or affordances for refilling the medication, dosage, instructions, warnings, side effects, active ingredients, an image of the medication, a fact sheet about the medication, or any other suitable information. In the illustrated embodiment, the medication records 5018A and 5018B are arranged in order by the most recent prescription date. In other embodiments, the medication records 5018A and 5018B are arranged to list daily medications before other medications, alphabetically, or in another suitable medication classification order. FIG. 6B also shows health record affordance 5304, which is an affordance to view the category representations 5006A-5006E shown in FIG. 6A (allergies, clinical documentation, lab results, medications, and health condition categories, respectively). In this regard, FIG. 6B further illustrates detecting a tap gesture with contact 5504 on health record affordance 5304 to display category representations 5006A-5006E of FIG. 6C.

[0154] In FIG. 6B, medication records 5018A and 5018B (for ABC and DEF medications) are both health records provided by Alpha Health Care. In some embodiments of FIGS. 6A-6Q-1, if a user has completed an onboarding process with more than one healthcare provider, medication records containing information about medications provided by all of the user's healthcare providers are displayed simultaneously on the display 112. In this regard, FIG. 6B-1 illustrates another embodiment in which a user has completed an onboarding process with Alpha Health Care and Beta Health Care. In FIG. 6B-1, in response to detecting a tap gesture involving contact 5502 on the category representation 5006D of FIG. 6A, medication records 5018C and 5018D prescribed by Beta Health Care (for GHI and JKL medications, respectively) are displayed simultaneously with medication records 5018A and 5018B prescribed by Alpha Health Care. In this manner, a user can view all of the user's prescriptions from the user's healthcare providers in one interface. In the illustrated embodiment, the medication records 5018A-5018D are categorized by prescription date. In other embodiments, the medication records included in Figures 6A-6Q-1 may be categorized by healthcare provider, by medical condition treated, or in any other suitable manner.

[0155] FIG 6B-1 also illustrates detecting a tap gesture with contact 5504' on the health record affordance 5304 to display the category representations 5006A-5006E of FIG 6C (Allergies, Clinical Document, Lab Results, Medication, and Condition categories, respectively). FIG 6C illustrates redisplaying the category representations 5006A-5006E in response to detecting a tap gesture with contact 5504 or 5504' on the health record affordance 5304. FIG 6C further illustrates detecting a tap gesture with contact 5506 on the category representation 5006B associated with clinical documents to display representations 5015A-5015C of three subcategories of clinical documents (X-ray Image, CT Scan, and Ultrasound Image subcategories, respectively) of FIG 6D.

[0156] FIG. 6D illustrates representations 5015A-5015C of subcategories of clinical documents as well as a representation 5017A of all clinical documents. In the illustrated embodiment, the subcategory representation 5015A is associated with X-ray images, the subcategory representation 5015B is associated with CT scan images, and the subcategory representation 5015C is associated with ultrasound images. As illustrated in FIG. 6D, each of the subcategory representations 5015A-5015C is an affordance that includes text indicating that such affordance is associated with health records from a particular subcategory of clinical documents. The representation 5017A of all clinical documents is an affordance that includes text indicating that such affordance is associated with all health records of clinical documents. Furthermore, each of the subcategory representations 5015A-5015C is selectable by a user to view the user's clinical documents from the associated subcategory. In the illustrated embodiment, the subcategories of the clinical documents category are formed based on the type of clinical documents. In other embodiments, clinical documents captured during different time periods (such as one year, three months, one month, or another time period) are grouped into different clinical document subcategories based on such time periods. In further embodiments, the subcategories of the user's health records are subcategorized based on other suitable means of categorizing the user's health records. FIG. 6D further illustrates detecting a tap gesture with contact 5508 on the subcategory representation 5015A associated with an X-ray image to display X-ray records 5016A and 5016B of FIG. 6E. FIG. 6E illustrates a display of health records associated with the subcategory representation 5015A (e.g., the subcategory of "X-ray images" of FIG. 6D). More specifically, X-ray records 5016A and 5016B are displayed. In the illustrated embodiment, X-ray records 5016A and 5016B are records of the user's X-ray images and include text identifying the provider who ordered or performed the X-ray exam (Dr. Doe and Alpha Health Care in both records). In the embodiment shown in Figure 6E, both the physician (which may be the physician ordering or reviewing the x-ray images) and the facility are identified as the provider. In this manner, both the healthcare professional and the organization or facility associated with the health record may be identified within the health record.In other embodiments, multiple physicians may be listed to identify the physician ordering the x-ray or reviewing the x-ray. In such embodiments, both the organization and facility of the healthcare provider are identified as providing further information to the user. X-ray records 5016A and 5016B each further include text identifying the date the x-ray image was taken (October 1, 2017 and September 1, 2017, respectively) and an image file 5036A or 5036B that contains a photograph of the x-ray image. In some embodiments, the user may tap one of image files 5036A or 5036B to overlay a full screen image of the x-ray image, zoom in on the photograph of the x-ray image, or obtain further information about the x-ray image, such as the radiologist's notes or diagnosis.

[0157] Similar to FIG. 6B, in FIG. 6E, both X-ray records 5016A and 5016B are health records provided by Alpha Health Care. FIG. 6E-1 illustrates an alternative embodiment in which a user has completed an onboarding process with Alpha Health Care and Beta Health Care. In FIG. 6E-1, in response to detecting a tap gesture with contact 5508 on the subcategory representation 5015A (X-ray Images subcategory) of FIG. 6D, an X-ray record 5016C from Beta Health Care is displayed simultaneously with X-ray records 5016A and 5016B from Alpha Health Care. In such a manner, similar to the user interface of FIG. 6C-1, a user can view all of the user's X-ray images from the user's healthcare providers in one interface. In the illustrated embodiment, the x-ray record 5016C includes text identifying the provider (Dr. Smith and Beta Health Care), the date such x-ray image was taken (September 15, 2017), and an image file 5036C containing a photograph of the x-ray image. Although not shown in Figure 6E-1, in one embodiment, health records from different subcategories of clinical documents from both Alpha Health Care and Beta Health Care may be displayed within a single user interface by a user selecting, for example, the representation of all clinical documents 5017A shown in Figure 6D.

[0158] 6E and 6E-1 respectively show detecting a tap gesture with contact 5510 or 5510' on clinical document affordance 5307 to display subcategory representations 5015A-C (X-ray image, CT scan, and ultrasound image) of FIG. 6F. FIG. 6F shows redisplaying subcategories 5015A-C in response to detecting a tap gesture with contact 5510 or 5510' on clinical document affordance 5308. In some embodiments, the user may select subcategory representation 5015B or subcategory representation 5015C to view health records belonging to such other health record subcategories. In the illustrated embodiment, the user performs a tap gesture with contact 5512 on health record affordance 5304 to view category representations 5006A-E (Allergy, Clinical Document, Lab Results, Medication, and Condition categories, respectively) of FIG. 6G. FIG. 6G illustrates redisplaying category representations 5006A-5006E in response to detecting a tap gesture with contact 5512 on health record affordance 5304 (eg, shown in FIG. 6F).

[0159] FIG. 6G also illustrates detecting a tap gesture with contact 5514 on all record representations 5006F to simultaneously display health records from different categories in FIG. 6H. FIG. 6H illustrates displaying health records from multiple health record categories. In the illustrated embodiment, medication records and x-ray records are displayed simultaneously and categorized by date. More specifically, FIG. 6H illustrates simultaneously displaying medication records 5018A and 5018B (ABC and DEF medications) and x-ray records 5016A and 5016B for x-ray images taken on October 1, 2017 and September 1, 2017. In the illustrated embodiment, the health records are grouped based on the date of visit to a healthcare provider. Medication records 5018A and x-ray records 5016A are displayed within a first group of health records from a visit to Alpha Health Care on October 1, 2017. Medication records 5018B and x-ray records 5016B are displayed within a second group of health records from a visit to Alpha Health Care on September 1, 2017. In the illustrated embodiment, the health records are displayed in different colors to distinguish between different categories of health records. Medication records 5018A and 5018B are displayed in a first color representing medications and x-ray records 5016A and 5016B are displayed in a second color representing clinical documentation. In an alternative embodiment, x-ray records 5018A and 5018B are displayed in a color representing a subcategory of x-ray images. In other embodiments, health records may be displayed within groups based on any characteristic, such as time period, visit date, provider (if more than one provider is onboarded as described with respect to FIG. 6H-1), health record category, health record category, health record subcategory, severity of condition, or any other suitable criteria, or may be displayed with a color assigned based on such characteristics. Characteristics such as health care provider may be further divided or differentiated by organization, physician, facility, or location. In this manner, the groups within which health records are displayed and the color of such health records may be used to allow a user to quickly distinguish between health records having different characteristics.In other embodiments, when only display groups and colors are used, health records that meet a common criteria may be displayed in a particular font, in a particular location, with a particular icon, with a particular graphic element, or otherwise with particular visual characteristics so that a user can distinguish health records by more than two available criteria.

[0160] In FIG. 6H, x-ray records 5016A and 5016B of x-ray images taken on October 1, 2017 and September 1, 2017, and medication records 5018A and 5018B (ABC and DEF medications) are all health records provided by Alpha Health Care. FIG. 6H-1 illustrates an alternative embodiment in which a user has completed an onboarding process with Alpha Health Care and Beta Health Care. In FIG. 6H-1, in response to detecting a tap gesture with contact 5514 on the all records representation 5016F of FIG. 6G, both medication record 5018C (GHI medication) and x-ray record 5016C of an x-ray image ordered on September 15, 2017 are obtained from Beta Health Care and displayed simultaneously with medication record 5018A and x-ray record 5016A from Alpha Health Care. In FIG. 6H-1 , medication record 5018C and x-ray record 5016C are displayed in one group and represent health records for a visit to Beta Health Care on September 15, 2017. In the illustrated embodiment, medication record 5018C and x-ray record 5016C are health records for a visit on September 15, 2017 and are newer than medication record 5018B and x-ray record 5016B, which are health records for a visit on September 1, 2017. Thus, medication record 5018C and x-ray record 5016C are displayed on display 112 instead of or before medication record 5018B and x-ray record 5016B. In one embodiment, the user performs a swipe gesture (not shown) to view older health records, such as medication record 5018B and x-ray record 5016B. In other embodiments, display 112 displays health records from three or more visits simultaneously.

[0161] Figures 6H and 6H-1 further illustrate detecting a tap gesture with contact 5516 or 5516', respectively, on health record affordance 5304 to display category representations 5006A-5006E (allergies, clinical documentation, lab results, medications, and health condition categories, respectively) of Figure 6I. Figure 6I illustrates redisplaying category representations 5006A-5006E in response to detecting a tap gesture with contact 5516 or 5516' on health record affordance 5304. Figure 6I also illustrates detecting a tap gesture with contact 5518 on category representation 5006E to view health records 5020A, 5020B, and 5020C of Figure 6J.

[0162] FIG. 6J illustrates displaying health records 5020A, 5020B, and 5020C of a user. In the illustrated embodiment, health record 5020A is a health record that includes information regarding the user's cholesterol level, the date the user's cholesterol was measured, and the name of the health care provider who measured the user's cholesterol level. In some embodiments, the value of the user's cholesterol level is displayed in an enlarged font, underlined, highlighted, or otherwise formatted to emphasize the user's cholesterol level. In some embodiments, the value of the user's cholesterol level is also displayed in a color that indicates where the user's cholesterol level falls within a cholesterol level range. For example, the value of the user's cholesterol level may be displayed in green if the user's cholesterol level is below 200 mg / dL, in yellow if the user's cholesterol level is between 200 mg / dL and 300 mg / dL, and in red if the user's cholesterol level is above 300 mg / dL. In one embodiment, the value of the current cholesterol value is displayed within a range of values. The numerical value indicates the severity of the user's cholesterol level, and the numerical range indicates the normality or severity of the health condition. Similar numerical values ​​and numerical ranges may be used for other health conditions of the user to indicate the normality or severity of any condition. Graphical representations of such values ​​and ranges are also available. In the illustrated embodiment, health condition record 5020B is a health record that includes information about the user's chronic migraines, medications prescribed to the user, prescription dates, and the name of the health care provider who provided the prescription to the user. Similarly, health condition record 5020C is a health record that includes information about the user's anxiety disorder, medications prescribed to the user, prescription dates, and the name of the health care provider who provided the prescription to the user.

[0163] In FIG. 6J, health condition records 5020A-C (cholesterol level, chronic migraine headaches, and anxiety disorder, respectively) are all health records provided by Alpha Health Care. FIG. 6J-1 illustrates an alternative embodiment in which a user has completed an onboarding process with Alpha Health Care and Beta Health Care. In FIG. 6J-1, in response to detecting a tap gesture with contact 5518 on the category representation 5006E (health condition category) of FIG. 6I, health condition record 5020D from Beta Health Care is displayed simultaneously with health condition records 5020A-C. Health condition record 5020D, like health condition records 5020B and 5020C, is a health record that includes information regarding medications prescribed to treat the health condition, the dates the medications were prescribed to the user, and the name of the healthcare provider who provided the prescription to the user. In some embodiments, each health record also includes further information about each health condition, such as a description of the health condition, symptoms, associated health conditions, treatment options, lifestyle recommendations, and other suitable information about each health condition. In some embodiments, each health record is an affordance that a user may select to view further information about the corresponding health condition. In this regard, FIGS. 6J and 6J-1 also illustrate detecting a tap gesture involving contact 5520 or 5520′, respectively, on health record 5020A to display such further information in FIG. 6K or 6K-1.

[0164] FIG. 6K illustrates displaying further information regarding health record 5020A (user's cholesterol level). As shown in FIG. 6K, cholesterol representation 5021A is displayed, including an indication of the user's current cholesterol level and an indication of where in the cholesterol level range the user's current cholesterol level falls. More specifically, cholesterol representation 5021A visually indicates that the user's current cholesterol level is within the range of 240 mg / dL-300 mg / dL, and thus falls within the range between high cholesterol (240 mg / dL) and very high cholesterol (300 mg / dL). In the illustrated embodiment, cholesterol representation 5021B is also displayed on display 112. As further shown in FIG. 6K, cholesterol representation 5021B is displayed, including a bar graph of the user's cholesterol level over time, with each bar representing a measurement of the user's cholesterol level. In the illustrated embodiment, different bars representing cholesterol levels falling within different ranges are displayed in different colors. In other embodiments, further representations of the user's current and past cholesterol levels are displayed. FIG. 6K also illustrates displaying within health condition records 5030B and 5030C past health records of the user's cholesterol levels on September 1, 2016 and January 1, 2016, respectively. Past health records, as used herein, are health records other than the current health record of any particular health information. For example, a medication record that includes information about medications that are no longer prescribed to the user is a past health record. Further examples of past records are shown at least in FIG. 8D and FIG. 8E and described in the following paragraphs. In the illustrated embodiment, the past health records are also color-coded based on the severity of the user's health condition compared to the normal health condition. In the illustrated embodiment, the cholesterol level measured on January 1, 2016 is less than 200 mg / dL and is assigned a first color (e.g., green), while the cholesterol level measured on September 1, 2016 is greater than 300 mg / dL and is assigned a second color (e.g., red). In other embodiments, different colors representing different severity levels of the user's health condition are assigned to different cholesterol level ranges.

[0165] FIG. 6K-1 illustrates displaying further information regarding health condition records 5020A from both Alpha Health Care and Beta Health Care. In the illustrated embodiment, past health records 5030D obtained from Beta Health Care on September 15, 2017 are displayed along with past health records 5030B and 5030C (the user's cholesterol levels measured on September 1, 2016 and January 1, 2016, respectively) of FIG. 6K above. In the illustrated embodiment, the user's cholesterol level measured on September 15, 2017 is between 200 mg / dL and 300 mg / dL and is assigned a third color (e.g., orange). Additionally, cholesterol representation 5021B includes a bar graph of the user's past cholesterol levels obtained from both Alpha Health Care and Beta Health Care.

[0166] 6L-6Q-1 show user interfaces for displaying notification of updates made to a user's health record on device 100. The updates to the user's health record may include updates to the user's existing health record or a new health record. Similar to FIG. 6A, FIG. 6L shows displaying category representations 5006A-5006E (Allergies, Clinical Documents, Lab Results, Medications, and Conditions categories, respectively) after updates to the user's health record have been received by device 100. In the illustrated embodiment, three updates have been received by device 100 but have not yet been reviewed by the user. To notify the user of the three updates, an all updates badge 5104 is displayed with all health records representation 5006F, and category updates badges 5106A, 5106B, and 5106C are displayed with category representations 5006B, 5006D, and 5006E, respectively. In the illustrated embodiment, all updates badge 5104 is a circle containing a count of all updates to the user's health record. Similarly, category update badges 5106A, 5106B, and 5106C are circles containing the number of updates to the health records in the health record category associated with category representations 5006B, 5006D, and 5006E, respectively. In the illustrated embodiment, all update badges 5104 indicate that three updates to the health records have been received but not yet confirmed, and category updates 5106A-5106C each indicate that one update to the health record in the corresponding health record category has been received but not yet confirmed. Figures 6K and 6K-1 further illustrate detecting a tap gesture with contact 5521 or 5521', respectively, on health status affordance 5306, which is the affordance for the user to select to return to the user interface shown in Figures 6J and 6J-1, respectively.

[0167] FIG. 6L illustrates one embodiment of an update badge indicating an update to a user's health record; other text, symbols, graphics, or displayed effects of any size, shape, color, or design may be used as the update badge to indicate an update or number of updates. For example, the update badge may be a highlighted or blinking category representation, or may display the time or date of the update. In some embodiments, the all updates badge 5104 and the category update badges, such as the category update badges 5106A-5106C (indicating updates to clinical documentation, medication, and health records, respectively), are not displayed simultaneously. In one or more such embodiments, only the category update badges are displayed on the display 112. In one or more such embodiments, only the all updates badges 5104 are displayed on the display 112. In some embodiments, a summary or portion of the content of the update is displayed on or with the update badge. In one embodiment, the update badge is a separate affordance from the category affordance, and the user selects the update badge to display the updated health record or a summary or portion of the updated health record. FIG. 6L further illustrates detecting a tap gesture with contact 5522 on category update badge 5106C to display updates to health record 5020A of FIG. 6M.

[0168] In some embodiments of FIGS. 6L-6Q-1, in addition to or instead of the update badge, the user may receive notification of all updates via on-screen alerts, text messages, or audio or video notifications. In one embodiment, such notifications may be based on whether a particular health record has been designated as high urgency by the user or a healthcare provider. In one embodiment, the device 100 may be preconfigured or configurable by the user to set one or more thresholds for one or more types of health records. If an update is received for a health record that has a particular result, measurement, value, reading, or other measurable aspect that exceeds or meets the set threshold, one or more notifications to the user are automatically generated on the device 100. In some embodiments, the method of notification may vary based on the severity of the particular result, measurement, value, reading, or other measurable aspect, or based on the type or number of thresholds. For example, a text message may be generated for some updates, and an audible alarm may be generated for other updates that is repeated periodically or at increasingly shorter intervals until the user completes the requested action. In one embodiment, updates that are less urgent or do not exceed a set threshold do not trigger the generation of a notification.

[0169] FIG. 6L-1 illustrates an alternative embodiment of FIG. 6L after the user has completed the onboarding process with both Alpha Health Care and Beta Health Care. As shown in FIG. 6L-1, by including two healthcare providers instead of the single one in FIG. 6L, four updates are displayed instead of the three updates of FIG. 6L. In the illustrated embodiment, the all updates badge 5104 indicates that a total of four updates have been received but not yet reviewed, the category updates badge 5106A indicates that two updates to clinical records have been received but not yet reviewed, the category updates badge 5106B indicates that one update to medication records has been received but not yet reviewed, and the category updates badge 5106C indicates that one update to health records has been received but not yet reviewed. FIG. 6L-1 further illustrates detecting a tap gesture with contact 5522′ on the category updates badge 5106C to display updates to health records 5020A of FIG. 6M-1.

[0170] 6M and 6M-1 illustrate displaying an update to the health record 5020A (the user's cholesterol level) in response to detecting a tap gesture involving contact 5522 or 5522', respectively, on the category update badge 5106C. In the illustrated embodiments, the user's cholesterol level has been updated to reflect a new cholesterol measurement performed by Alpha Health Care on December 1, 2017. In the illustrated embodiments, a health record update badge 5140 is displayed with the health record 5020A to indicate that the health record 5020A has been updated. The health record 5020A is displayed in a color that indicates the severity of the user's cholesterol level. In the illustrated embodiments, a recommendation affordance 5240A is displayed with the health record 5020A, which includes a recommended action to see a doctor. In some embodiments, the recommendation affordance is a recommendation to exercise, change the user's diet, or engage in other appropriate activities to lower the user's cholesterol level. In some embodiments, the recommendation affordance 5240A includes content indicating the importance of the update or severity of the user's condition. In one or more of such embodiments, the user may self-specify the importance of certain types of health records as well as updates to certain types of health records. For example, the user may specify all updates to the user's cholesterol level as urgent updates. In one or more of such embodiments, the user may specify the importance of certain types of health records based on the amount of positive or negative change in the user's health condition. For example, the user may specify the importance of updates to the user's cholesterol level based on the amount of change in the user's cholesterol level. In other embodiments, the health care provider may specify the importance of certain updates. Although the description of Figures 6M and 6M-1 above is directed to updates and recommendations based on the user's cholesterol, the above paragraphs also apply to other types of health records. For example, if the user has received a new serum iron measurement, a recommendation affordance may be displayed on the display 112 encouraging the user to modify the user's diet to increase their iron sources.

[0171] 6M and 6M-1 further illustrate detecting a tap gesture with contact 5524 or 5524' on recommendation affordance 5240A, which includes recommendations based on the user's cholesterol level, to display calendar affordance 5241 of FIG. 6N. More specifically, FIG. 6N illustrates the display of calendar affordance 5241 overlaid on the user interface shown in FIG. 6M or 6M-1. FIG. 6N also illustrates detecting a tap gesture with contact 5526 on the date January 8 on calendar affordance 5241. In this manner, the user may select a date to make an appointment with a physician that matches the recommendation displayed in recommendation affordance 5240A. Further affordances may be utilized to select a time for the appointment or to display or enter further information regarding the appointment. In some embodiments, calendar affordance 5241 or further affordances display a date and time based on the user's availability and the physician's appointment availability.

[0172] 6O and 6O-1, respectively, show displaying updates to the recommended affordance 5240A. In the illustrated embodiments, the recommended affordance 5240A for the health record 5020A has been updated to include text indicating the date of the appointment and the name of the doctor the user will be meeting with. In some embodiments, the device 100 specifies a time to display a notice reminding the user of the upcoming appointment or otherwise notifying them. FIGS. 6O and 6O-1 also show detecting a tap gesture with contact 5527 or 5527′, respectively, on the health record affordance 5304 to display any remaining updates to the health record of FIGS. 6P and 6P-1, respectively.

[0173] 6P and 6P-1 show a display of category representations 5006A-5006E (allergies, clinical documentation, lab results, medications, and health condition categories, respectively) and the remaining updates for the user's health record. In the embodiment of FIG. 6P where the user has onboarded only one healthcare provider, the all updates badge 5104, which shows the total number of updates received by the device 100 but has not yet been reviewed by the user, is updated from three updates to two updates to indicate the remaining number of updates that the user has not yet reviewed. The category updates badge 5106C, which was previously displayed in the representation category 5006E (health condition category) of FIG. 6L, is no longer displayed because the user has reviewed the updates to the health condition record 5020A. Similarly, in the embodiment of FIG. 6P-1 where there are more updates because the user has onboarded two healthcare providers, the all updates badge 5104 is updated from four updates to three updates to indicate the remaining number of updates that the user has not yet reviewed. Similar to Figure 6P, the category update badge 5106C previously displayed in the representation category 5006E of Figure 6L-1 is no longer displayed because the user has confirmed the update to health record 5020A. Figures 6P and 6P-1, respectively, further illustrate detecting a tap gesture with contact 5528 or 5528', respectively, on the all updates badge 5104 to display Figure 6Q or 6Q-1, respectively.

[0174] FIG. 6Q and FIG. 6Q-1 each display updates to multiple types of health records. The illustrated embodiment of FIG. 6Q displays a first update to a new medication record 5018E for a new prescription for ABC drug prescribed by Alpha Health Care on December 1, 2017, and a second update to a new x-ray record 5016D for an x-ray taken at Alpha Health Care on December 1, 2017, along with update badges 5142 and 5144, respectively. In some embodiments, the health record update badges for updates to existing health records and health record update badges for updates to new health records have different symbols, shapes, sizes, text fonts, text colors, or other visual differences to help a user distinguish between updates to existing health records and updates to new health records. FIG. 6Q-1 also shows displaying a medication record 5018E for ABC drug, a health record 5020A for the user's cholesterol level, and an x-ray record 5016D for an x-ray image ordered on December 1, 2017. In addition to the update to the new medication record 5018E and the update to the new x-ray record 5016D from Alpha Health Care on December 1, 2017, FIG. 6Q-1 includes an update from Beta Health Care and thus displays a third update to a new x-ray record 5016E taken at Beta Health Care on November 15, 2017 along with a health record update badge 5146.

[0175] 7A-7F are flow diagrams illustrating a method for displaying aggregated health records using an electronic device according to some embodiments. FIGS. 7A-7F are flow diagrams illustrating a method for displaying aggregated health records of a user using, for example, the user interfaces of FIGS. 6A-6Q-1. As described with reference to FIGS. 6A-6Q-1, method 700 can be utilized to display aggregated health records from one or more health records from multiple healthcare providers of a user. Method 700 is performed on a device (e.g., devices 100, 300, 500 shown in FIGS. 1, 3, and 5A, respectively). In one such embodiment, display 112 is a touch screen display, with a touch-sensitive surface on or integrated into display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, an audio interface, or other suitable interface. Some operations in method 700 are optionally combined. Furthermore, the order of some operations is optionally changed.

[0176] As described below, the method 700 provides an intuitive way to view aggregated health records obtained from a user's healthcare providers. The method 700 also provides an intuitive way to simultaneously view aggregated health records obtained from a user's multiple healthcare providers. This method reduces the cognitive burden on a user as the user views the user's health records obtained from one or more of the user's healthcare providers, creating a more efficient human-machine interface. The method also improves user efficiency by simultaneously displaying health records obtained from multiple healthcare providers. For battery-operated computing devices, allowing a user to review health records obtained from a healthcare provider or multiple healthcare providers faster and more efficiently conserves power and extends the time between battery charges.

[0177] Similar to FIGS. 6A-6Q-1, method 700 may be used to allow a user to visualize health records in a common interface. Using such a common interface may avoid the risk that a user may only be able to view a portion of health information relevant to a given concern or question. For example, a user may not realize that blood tests have been performed by two different providers for a given condition, providing inaccurate information to a hospital or other subsequent provider. In such cases, device 100 may still be used to store health records across multiple providers and allow the user to view them in a common interface, providing the user with a readily available source of comprehensive information about the user's health, even as the user moves or changes providers. Many traditional health care providers discard health records after a period of time in which the patient does not see such health care provider, and such information may be lost forever. Such health records may contain important historical health information and baseline data that are essential for the subsequent diagnosis and treatment of disease. Additionally, the use of such a common interface may avoid the need for a user to use device 100 to retrieve data from various locations on device 100 or other websites, portals, and other sources to piece together information regarding a particular health condition, at the risk of that information being overlooked, not immediately available, or only available after extensive electronic searching using device 100. Furthermore, by storing such health records on device 100 and providing a single interface that allows a user to view and browse all of such health records, a user may avoid the need for a user to use device 100 to communicate with multiple health care providers over voice calls (often with long hold times), two-way telephone systems, voicemail, email, and other electronic messaging platforms in order to piece together health records from multiple sources.The interface shown in FIG. 6B-1 replaces half a day or more of device 100 use required to piece together the above information with a few clicks on device 100 by the user, resulting in significant savings in previously wasted bandwidth, battery life and energy.

[0178] 7A-7F are flow diagrams illustrating a method for displaying an aggregated health record of a user using, for example, the user interface of FIGS. 6A-6Q-1. As described with reference to FIGS. 6A-6Q-1, method 700 can be utilized to display aggregated health records from one or more health records from multiple healthcare providers of a user. Method 700 is performed on a device (e.g., 100, 300, 500). In one such embodiment, display 112 is a touch screen display, with a touch-sensitive surface on or integrated into display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, an audio interface, or other suitable interface. Some operations in method 700 are optionally combined. Furthermore, the order of some operations is optionally changed.

[0179] Similar to FIGS. 6A-6Q-1, one or more embodiments of method 700 illustrated in FIGS. 7A-7F and described below may be used to allow a user to visualize health records in a common interface. Using such a method may avoid the risk that a user may only be able to view a portion of health information relevant to a given concern or question. For example, a user may not realize that blood tests were performed by two different providers for a given condition, providing inaccurate information to a hospital or other subsequent provider. Similarly, using this method on a device such as device 100 to store health records across multiple providers and allow the user to view them in a common interface may provide the user with a readily available source of comprehensive information regarding the user's health, even as the user moves or changes providers. Many traditional health care providers discard health records after a period of time in which the patient does not see such health care provider, and such information may be lost forever. Such health records may contain important historical health information and baseline data that are essential for the subsequent diagnosis and treatment of disease. Additionally, the use of such methods may avoid the need for a user to use a device, such as device 100, to retrieve data from various locations on such device or on other websites, portals, and other sources to piece together information regarding a particular health condition, at the risk of that information being overlooked, not immediately available, or only available after extensive electronic searching using the device. Moreover, by storing and displaying such health records on a device, such as device 100, using such methods and providing a single interface through which a user can view and browse all of such health records, a user may avoid the need to use the device to communicate with multiple health care providers over voice calls (often with long hold times), two-way telephone systems, voicemail, email, and other electronic messaging platforms in order to piece together health records from multiple sources.The half-day or more of use of such devices required to piece together the aforementioned information can be replaced with the use of such methods requiring only a few clicks on the device by the user, resulting in significant savings in previously wasted bandwidth, battery life and energy.

[0180] In some embodiments, while device 100 is associated with a first healthcare provider and not associated with a second healthcare provider, device 100 receives (702) a first request to view a user's health record via one or more input devices. In some embodiments, the request to view the health record is automatically sent to device 100 when the user completes an onboarding process with a healthcare provider. In some embodiments, the user selects health data affordance 5029A shown in FIG. 6A or an affordance displayed within the onboarding user interface to request device 100 to view the user's health record. In some embodiments, the request to view the health record is a request to view health records of multiple users, such as family health records.

[0181] In response to receiving a first request to view health records for a first user, device 100 displays (704) representations of a plurality of health record categories on display 112. Figure 6A, for example, shows five health record categories (e.g., category representations 5006A-5006E).

[0182] The representation of the plurality of categories includes a first representation of a first category of the plurality of categories (706). FIG. 6A, for example, illustrates a category representation 5006D associated with the user's medications. Further, upon selecting the first representation of the first category while the device 100 is associated with a first healthcare provider and not associated with a second healthcare provider, the device 100 displays on the display 112 a plurality of health records in the first category from the first healthcare provider (706). In the embodiment illustrated in FIG. 6B, the user is associated with only Alpha Health Care and not Beta Health Care. FIG. 6B illustrates an embodiment in which, for example, only medication records 5018A-5018B (ABC and DEF medications) from only Alpha Health Care are displayed on the device 100.

[0183] The plurality of representations also includes a second representation of a second category of the plurality of categories (708). FIG. 6I, for example, shows a category representation 5006E associated with a health condition of the user. Further, upon selecting the second representation of the second category while the device 100 is associated with the first healthcare provider and not associated with the second healthcare provider, the device 100 displays on the display 112 a plurality of health condition records in the second category from the first healthcare provider (708). FIG. 6J, for example, shows two health condition records 5020A and 5020B (cholesterol level and chronic migraine) in response to detecting the tap gesture shown in FIG. 6I on the category representation 5006E.

[0184] In some embodiments, a first type of health record is displayed in a first color and a second type of health record is displayed in a second color different from the first color (718). FIG. 6H, for example, shows x-ray records 5016A and 5016B (ordered on Oct. 1, 2017 and Sept. 1, 2017, respectively) displayed in a first color and medication records 5018A and 5018B (ABC and DEF medications) displayed in a second color. Different types of health records are displayed in different colors to help a user distinguish between health records that belong to different categories (or subcategories). In some embodiments where multiple health records that belong to different categories are displayed simultaneously, a user may determine which category (or subcategory) a health record belongs to based solely on color. In other embodiments where multiple records from different healthcare providers are displayed simultaneously, a user may also distinguish between different health records from different healthcare providers based solely on color. Additionally, displaying different types of health records in different colors also reduces user error (such as misidentifying a health record or not being able to identify a health record) when a user browses the user's health records. The above enhances device usability and makes the user device interface more efficient by allowing a user to distinguish between different types of health records based on color. The method also improves user efficiency by allowing a user to identify health records by the color assigned to the health record type. For battery-operated computing devices, allowing a user to browse the user's health records faster and more efficiently conserves power and extends the time between battery charges.

[0185] In some embodiments, device 100 displays on display 112 first content summarizing the first category and a first category information affordance associated with the first category, and selecting the first category information affordance causes device 100 to display (720) additional content associated with the first category not included in the first content on display 112. In some embodiments, category representation 5006E (Health Condition category) of FIG. 6I includes an overview affordance that includes content summarizing the user's particular health condition. Additionally, device 100, in response to detecting user selection of the overview affordance, displays additional information about the user's health condition, such as causes of the health condition, ways to identify symptoms of the health condition, non-pharmaceutical treatments for alleviating the health condition, as well as other useful information about the health condition.

[0186] In some embodiments, the device 100 also displays on the display 112 second content summarizing the second category and a second category information affordance for the second category, and selecting the second category information affordance causes the device 100 to display on the display 112 additional content associated with the second category not included in the second content (720). In some embodiments, the category representation 5006B (Clinical Document category as shown in FIG. 6G) includes an overview affordance including content summarizing allergies suffered by the user. In addition, in response to detecting a user selection of the overview affordance, the device 100 displays additional information regarding allergies suffered by the patient, such as methods for reducing or preventing triggering of the particular allergy, non-pharmaceutical treatments for relieving symptoms of the allergy, as well as other useful information regarding the allergy. Content including descriptions of the health record categories is provided along with the category representation. This method improves user efficiency by allowing the user to make an informed selection of health record categories based on descriptions of different health record categories. The method also enhances usability of the device and makes the user device interface more efficient by assisting the user in making appropriate inputs and reducing the number of unnecessary inputs caused by the user selecting an incorrect health record category. For battery-operated computing devices, allowing the user to browse the user's health record faster and more efficiently conserves power and extends the time between battery charges.

[0187] In some embodiments, a first category of multiple health records are displayed in chronological order (722). FIG. 6B-1, for example, shows medication records 5018A-5018B (ABC and DEF medications) arranged based on prescription date. In some embodiments, a second category of multiple health records are displayed in chronological order (722). FIG. 6J, for example, shows health condition records 5020A-5020C (associated with cholesterol levels, chronic migraines, and anxiety disorders, respectively) arranged based on prescription dates of medications prescribed for that health condition. Presenting the health records in chronological order allows the user to browse the user's health records based on date, improving user efficiency. For battery-operated computing devices, allowing the user to browse the user's health records faster and more efficiently conserves power and increases the time between battery charges.

[0188] In some embodiments, the device 100 detects a selection of a first representation of a first category while the device 100 is associated with a first healthcare provider (724). FIG. 6I, for example, shows a tap gesture with contact 5518 on the category representation 5006E (health condition category). In some embodiments, in response to detecting a selection of a first representation of a first category while the device 100 is associated with a first healthcare provider display, the device 100 displays a first representation of a first health record of a plurality of health records in the first category from the first healthcare provider on the display 112 (724). FIG. 6J, for example, shows a health condition record 5020A including a cholesterol level of a user measured by Alpha Health Care on October 1, 2017. The first representation of the first health record includes a numerical value within a numerical range, the numerical value being indicative of a health condition of the first user, and the numerical range being indicative of a normal numerical range for the health condition (724). The health record 5020A shown in FIG. 6J includes a value for the user's cholesterol level, which is 269 mg / dL. In some embodiments, the health record 5020A also includes a value representing a range of cholesterol, such as 0-400 mg / dL. This method reduces the cognitive burden on the user by providing the user with a numerical value that allows the user to determine the severity of the health condition based on the numerical value, creating a more efficient human-machine interface. This method also improves the user's efficiency by allowing the user to quickly identify the severity of the health condition from the numerical value. For battery-operated computing devices, allowing the user to more quickly and efficiently identify the severity of the health condition, the medical records associated with the health condition, as well as the health condition over time, conserves power and increases the time between battery charges.

[0189] In some embodiments, the device 100 displays (726) the numerical value in a color selected based on the severity of the first user's health condition. In some embodiments, the value of the user's cholesterol level is displayed in green if the value is less than 200 mg / dL, in yellow if the value is between 200 mg / dL and 300 mg / dL, and in red if the value is greater than 300 mg / dL. Displaying the numerical value based on the severity of the user's health condition allows the user to determine the severity of the health condition without complex knowledge of how to read the numerical value, creating a more efficient human-machine interface. This method also improves the user's efficiency by allowing the user to quickly identify the severity of the health condition based on the color associated with the numerical value. In the case of a battery-operated computing device, allowing the user to identify the severity of the health condition faster and more efficiently conserves power and increases the time between battery charges.

[0190] In some embodiments, the device 100 displays a second representation of a second health record of the first category of multiple health records from the first healthcare provider, the second representation of the second health record including a graph showing the first user's condition over a period of time (728). FIG. 6K, for example, shows a cholesterol representation 5021B in response to detecting a tap gesture on the health record 5020A (the user's cholesterol level) shown in FIG. 6J. The cholesterol representation 5021B is a bar graph of the user's cholesterol level over time. This method also reduces the cognitive burden on the user by providing the user with an image of the user's medical record that provides the user with information about the user's condition over time, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify the user's health condition over time in one common interface without having to navigate multiple user interfaces. For battery-operated computing devices, enabling a user to more quickly and efficiently identify the user's health status over time conserves power and extends the time between battery charges.

[0191] In some embodiments, the plurality of health records in a first category from a first healthcare provider includes a first health record in a first category from a first healthcare provider and a second health record in the first category from the first healthcare provider 730. Figure 6B, for example, shows two medication records 5018A and 5018B (ABC and DEF medications) obtained from Alpha Health Care.

[0192] In some embodiments, the plurality of health records in the second category from the first healthcare provider includes a third health record in the second category from the first healthcare provider and a fourth health record in the second category from the first healthcare provider (730). Figure 6E, for example, shows two x-ray records 5016A and 5016B (ordered on October 1, 2017 and September 1, 2017, respectively) obtained from Alpha Health Care.

[0193] In some embodiments, the first health record in the first category from the first healthcare provider and the third health record in the second category from the first healthcare provider are records of a first visit to the first healthcare provider (730). Figures 6B and 6E, for example, show that medication record 5018A (ABC medication) and x-ray record 5016A are records of a visit to Alpha Health Care on October 1, 2017.

[0194] In some embodiments, the second health record in the first category from the first healthcare provider and the fourth health record in the second category from the first healthcare provider are records of a second visit to the first healthcare provider (730). Figures 6B and 6E, for example, show that medication record 5018B (DEF medication) and x-ray record 5016B are records of a visit to Alpha Health Care on September 1, 2017.

[0195] In some embodiments, in response to receiving a first request to display health records for a first user, device 100 simultaneously displays the first health record and the third health record in a first group on display 112, the first group being identified by a first date of the first visit on display 112 (730). FIG. 6H illustrates, for example, grouping medication record 5018A (ABC medication) and x-ray record 5016A into a first group and simultaneously displaying medication record 5018A and x-ray record 5016A on display 112.

[0196] In some embodiments, in response to receiving a first request to display health records for a first user, the device 100 simultaneously displays the second health record and the fourth health record on the display 112 in a second group, the second group being identified on the display 112 by a second date of the second visit, the first date being different from the second date (730). FIG. 6H illustrates, for example, grouping the medication record 5018B (DEF medication) and the X-ray record 5016B into the second group. A further medication record 5018B and the X-ray record 5016B are simultaneously displayed on the display 112. This method reduces the cognitive burden on the user as the user views the health records by grouping the health records based on appointment dates with the healthcare provider, and by arranging the different groups based on appointment dates. Optionally, if the health records are from multiple healthcare providers, the health records are grouped by healthcare provider and appointment date, and the groups are arranged by appointment date. Optionally, the method reduces the cognitive burden on the user when viewing the health records by displaying health records belonging to different categories in different colors to help the user distinguish between different health record categories. Optionally, the method also reduces the cognitive burden on the user when viewing the health records by displaying update badges along with updates to the health records, each of which creates a more efficient human-machine interface. The method also improves user efficiency by allowing the user to identify health records based on appointment dates with a health care provider and based on different appointment dates with different health care providers. The method also improves user efficiency by allowing the user to view different health records from different health care providers in a common interface, making the user device interface more efficient. For battery-operated computing devices, allowing the user to browse the user's health records faster and more efficiently conserves power and extends the time between battery charges.

[0197] In some embodiments, a first health record in a first category from a first healthcare provider and a second health record in a first category from a first healthcare provider are displayed in a first color 732. Figure 6H, for example, shows a medication record 5018A (ABC medication) and an x-ray record 5016A ordered on October 1, 2017 in a first color.

[0198] In some embodiments, a third health record in the second category from the first healthcare provider and a fourth health record in the second category from the first healthcare provider are displayed in a second color (732) that is different from the first color. FIG. 6H, for example, shows medication records 5018B (DEF medications) and x-ray records 5016B ordered on September 1, 2017 in a second color that is different from the first color. Displaying different health record categories in different colors allows a user to quickly distinguish between different health records, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to identify health records based on color. For battery-operated computing devices, allowing a user to browse the user's health records faster and more efficiently conserves power and increases the time between battery charges.

[0199] In some embodiments, the device 100 receives (734) an update to a first health record in a first category from a first healthcare provider. FIG. 6L, for example, illustrates receiving multiple updates from Alpha Health Care (e.g., an update to a clinical document category representation 5006B, an update to a medication category representation 5006D, and an update to a health condition category representation 5006E). In some embodiments, the device 100 displays a first update badge associated with the first health record in the first group on the display 112, and the first update badge and the first health record are displayed simultaneously in a first area of ​​the display 112. For example, FIG. 6L illustrates a category update badge 5106C and a category representation 5006E in an area of ​​the display 112. In some embodiments, the category update badge 5106C is attached to the category representation 5006E. This method reduces the cognitive burden on the user by allowing the user to identify which health record has been updated, creating a more efficient human-machine interface. The method also improves user efficiency by allowing the user to quickly identify which health records have been updated. In the case of battery-operated computing devices, allowing the user to more quickly and efficiently identify updated health records conserves power and extends the time between battery charges.

[0200] In some embodiments, the device 100 displays a third representation of a third health record of the first category of the plurality of health records from the first healthcare provider, the third representation of the third health record including an image showing the medical record of the first user (736). In some embodiments, an x-ray image associated with an x-ray record, such as x-ray record 5016A (ordered on October 1, 2017) of FIG. 6E, is displayed in response to a user selection of the x-ray image. In some embodiments, such as FIG. 6E, where x-ray record 5016A includes an image file 5036A of the x-ray image, selecting image file 5036A causes device 100 to enlarge image file 5036A. This method reduces the cognitive burden on the user by providing the user with an image of the user's medical record and creates a more efficient human-machine interface by allowing the user to quickly access the health status associated with the medical record. For battery-operated computing devices, allowing the user to quickly and efficiently access the user's health status conserves power and increases the time between battery charges.

[0201] In some embodiments, device 100 receives an update to a health record in a first health record category (738). FIG. 6L, for example, illustrates receiving multiple updates from Alpha Health Care (e.g., an update to a clinical document category representation 5006B, an update to a medication category representation 5006D, and an update to a health condition category representation 5006E). In some embodiments, after receiving the update to the health record in the first category, in response to receiving at least one of a first request to view the health record for the first user and a second request to view the health record for the first user, device 100 displays a second update badge associated with the first category on display 112, and the second update badge and the first representation of the first category are simultaneously displayed in a first area of ​​display 112 (738). FIG. 6M, for example, illustrates medication records 5020A-C (associated with the user's cholesterol level, chronic migraine headaches, and anxiety disorder, respectively) in response to detecting a gesture on category representation 5006E of FIG. 6L. FIG. 6M also shows a health record update badge 5140 with the health record 5020A to indicate that the health record 5020A has been updated. This method reduces the cognitive burden on the user by allowing the user to identify which health records have been updated, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing the user to more quickly and efficiently identify updated health records conserves power and extends the time between battery charges.

[0202] In some embodiments, the second update badge is visually associated (740) with the first representation of the first category. For example, FIG. 6L shows a category update badge 5106C and a category representation 5006E (health condition category) in one area of ​​the display 112. In some embodiments, the category update badge 5106C is attached to the category representation 5006E. This method reduces the cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health record, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing the user to more quickly and efficiently identify updated health records conserves power and increases the time between battery charges.

[0203] In some embodiments, selecting a first representation of a first category while the device 100 is associated with a first health care provider causes the device 100 to display a representation of the health record in the first health record category on the display 112, with a second update badge visually associated with the representation of the health record in the first health record category (742). FIG. 6M, for example, shows a health record update badge 5140 and a health condition record 5020A (associated with the user's cholesterol level) in the same region. In one or more embodiments, the health record update badge 5140 is attached to the health condition record 5020A. This method reduces the cognitive burden on the user by allowing the user to identify which categories include updates to the user's health record. This method reduces the cognitive burden on the user by allowing the user to identify which categories include updates to the user's health record, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing users to identify updated health records faster and more efficiently conserves power and extends the time between battery charges.

[0204] In some embodiments, the second update badge includes the content of the update to the health record on the second update badge (744). In some embodiments, the content of the update, such as a summary of the update, is displayed on an update badge, such as, for example, a category update badge 5106A, 5106B, or 5106C, a health record update badge 5140, or an all updates badge 5104 shown in FIGS. 6L and 6M. This method reduces the cognitive burden on the user by allowing the user to identify the content of the update or a summary of the content of the update without performing further action, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify changes in health status associated with the updated health record. For battery-operated computing devices, allowing the user to identify changes in the user's health status more quickly and efficiently conserves power and increases the time between battery charges.

[0205] In some embodiments, device 100 receives a request to select a second update badge via one or more input devices (746). In some embodiments, all update badges 5104 and category update badges 5106A-5106C (each shown in FIG. 6L) shown in FIG. 6L include an update affordance, which is an affordance that the user selects to view updates to the corresponding health record. FIG. 6L illustrates, for example, a tap gesture with contact 5522 on category update badge 5106C. In some embodiments, device 100 displays (746) updates to this health record in the first health record category on display 112 in response to receiving the request to select the second update badge. FIG. 6M illustrates, for example, an update to health record 5020A (the user's cholesterol level health record) in response to detecting the tap gesture illustrated in FIG. 6L. As illustrated in FIG. 6M, health record 5020A has been updated to show the user's cholesterol level as of December 1, 2017. The method reduces the cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health record. The method reduces the cognitive burden on the user by allowing the user to access updates to the health record by selecting an update badge, creating a more efficient human-machine interface. The method also improves user efficiency by allowing the user to easily access the updates by selecting the update badge. For battery-operated computing devices, allowing the user to access updated health records faster and more efficiently conserves power and extends the time between battery charges.

[0206] In some embodiments, device 100 simultaneously displays (748) the updates to the health record and a recommended affordance associated with the health record. FIG. 6M, for example, illustrates simultaneously displaying health record 5020A (a health record of the user's cholesterol level) and recommended affordance 5240A. In some embodiments, device 100 receives (748) a request to select a recommended affordance via one or more input devices. FIG. 6M, for example, illustrates a tap gesture with contact 5524 on recommended affordance 5240A. In some embodiments, device 100 displays a recommended action on display 112 in response to receiving the request to select a recommended affordance, the recommended action being based on the updates to the health record (748). FIG. 6N, for example, illustrates a calendar affordance 5241 in response to the gesture illustrated in FIG. 6M. In the illustrated embodiment, the recommended action is to schedule an appointment with a doctor. In some embodiments, content describing or explaining the recommended action is also displayed with the recommendation affordance 5240A. FIG. 6M shows a recommendation affordance 5240A that includes text of a recommended action, for example, to see a doctor. This method reduces the cognitive burden on the user by providing a recommendation without user input, creating a more efficient human-machine interface. This method also improves user efficiency by automatically providing the user with a way to respond. In the case of battery-operated computing devices, power is conserved and the time between battery charges is increased by allowing the user to more quickly and efficiently determine whether and how to respond to updates to the user's health record.

[0207] In some embodiments, the recommendation is a recommendation to schedule an appointment with a first healthcare provider (750). In such embodiments, displaying the recommended action includes simultaneously displaying the recommended action and a scheduling affordance (750). FIG. 6N illustrates, for example, a calendar affordance 5241 in response to the gesture illustrated in FIG. 6M. In the illustrated embodiment, the recommended action is to schedule an appointment with a doctor. This method reduces the cognitive burden on the user by providing recommendations without user input, creating a more efficient human-machine interface. This method also improves user efficiency by automatically providing the user with a method of response. In the case of a battery-operated computing device, power is conserved and the time between battery charges is increased by enabling the user to more quickly and efficiently determine whether and how to respond to updates to the user's health record.

[0208] In some embodiments, device 100 receives (752) an update to a health record in a first health record category. FIG. 6L illustrates, for example, receiving multiple updates from Alpha Health Care (e.g., an update to a clinical document category representation 5006B, an update to a medication category representation 5006D, and an update to a health condition category representation 5006E). In some embodiments, device 100, in response to receiving the update to the health record, displays (752) a notification of the update on display 112 pursuant to a determination that the importance of the update is greater than a threshold. For example, recommendation affordance 5240A of FIG. 6M includes the text "URGENT!" indicating the importance of the change in cholesterol to the user. In some embodiments, the notification of the update and the importance of the update overlay a portion of display 112 even when the user interface illustrated in FIGS. 6A-6Q-1 is not displayed on the display. In one or more embodiments, the notification is a text-based notification.

[0209] The device 100 ceases displaying the notification of the update on the display 112 in accordance with the determination that the importance of the update is less than the threshold (752). In some embodiments, if the user's cholesterol level has not significantly changed or improved or does not meet the threshold for providing a notification regarding the update, the recommendation affordance 5240A of FIG. 6M or FIG. 6M-1 is not displayed on the display 112. This method reduces the cognitive burden on the user by notifying the user of an important update, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to determine whether an update is an important update based on the presence or absence of a notification. In the case of a battery-operated computing device, power is conserved and the time between battery charges is increased by allowing the user to more quickly and efficiently determine whether an update is an important update.

[0210] After displaying the representations of the multiple health record categories and after being associated with the second healthcare provider, device 100 receives a second request via one or more input devices to view health records for the first user (710). In some embodiments, if the user has completed an onboarding process with multiple healthcare providers, the user requests device 100 to view health records obtained from more than one healthcare provider.

[0211] After device 100 processes the user's request to view health records obtained from two or more healthcare providers, device 100 receives a second request from the user to view the user's health record. In response to receiving the second request to view the first user's health record, device 100 displays (712) representations of a plurality of health record categories on display 112. FIG. 6A, for example, shows five category representations 5006A-5006E (for allergies, clinical documentation, lab results, medications, and health conditions, respectively).

[0212] The representation of the plurality of categories includes a first representation of a first category of the plurality of categories (714). FIG. 6A, for example, shows a category representation 5006D (medication category) associated with the user's medications. Furthermore, upon selecting the first representation of the first category while the device 100 is associated with the first healthcare provider and the second healthcare provider, the device 100 displays on the display 112 one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider (714). FIG. 6B-1, for example, shows an alternative embodiment of FIG. 6B. In the embodiment of FIG. 6B-1, the user has completed the onboarding process with both Alpha Health Care and Beta Health Care. In this embodiment, a gesture involving contact 5502 on the category representation 5006D shown in FIG. 6A, or a gesture selecting a similar category representation 5006D, while device 100 is associated with Alpha Health Care and Beta Health Care, causes device 100 to display medication records obtained from both Alpha Health Care and Beta Health Care. In this regard, FIG. 6B-1 illustrates medication records 5018A and 5018B (ABC and DEF medications) from Alpha Health Care, and two medication records 5018C and 5018D (GHI and JKL medications) from Beta Health Care, in response to detecting a tap gesture on the category representation 5006D shown in FIG. 6A.

[0213] The representation of the plurality of health record categories also includes a second representation of a second category of the plurality of categories 716. Figure 6I, for example, shows a category representation 5006E (health condition category) associated with a health condition of the user.

[0214] Further, selecting the second representation of the second category while the device 100 is associated with the first and second healthcare providers causes the device 100 to display on the display 112 one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider (716). FIG. 6J-1, for example, illustrates an alternative embodiment of FIG. 6J. In the embodiment of FIG. 6J-1, the user has completed an onboarding process with both Alpha Health Care and Beta Health Care. In this embodiment, a gesture involving contact 5518 on the category representation 5006E (health condition category) shown in FIG. 6I, or a similar gesture selecting the category representation 5006E while the device 100 is associated with Alpha Health Care and Beta Health Care, causes the device 100 to display health condition records obtained from both Alpha Health Care and Beta Health Care (716). In this regard, FIG. 6J-1 shows health condition records 5020A-5020C (cholesterol levels, chronic migraines and anxiety disorders) from Alpha Health Care and health condition record 5020D (arthritis) from Beta Health Care in response to detecting a tap gesture on the category representation 5006E shown in FIG. 6I.

[0215] In some embodiments, device 100 receives (754) a first selection of a first representation of a first category via one or more input devices. Figure 6C, for example, shows a tap gesture with contact 5506 on category representation 5006B (the Clinical Document category).

[0216] In some embodiments, in response to receiving the first selection, device 100 displays (754) representations of multiple subcategories of the first health records category on display 112. For example, Figure 6D shows subcategory representations 5015A-C (X-ray images, CT scans, and ultrasound images subcategories, respectively) in response to detecting a tap gesture on category representation 5006B (the clinical documents category) shown in Figure 6C.

[0217] In some embodiments, the plurality of health record subcategories includes a first representation of a first subcategory of a first category (754). FIG. 6D illustrates a subcategory representation 5015A (X-ray images subcategory) in response to detecting a tap gesture on the category representation 5006B illustrated in FIG. 6C, for example. In the illustrated embodiment, the representation of the subcategory 5015A is associated with X-ray images. Further, upon selecting the first representation of the first subcategory of the first category, the device 100 displays on the display 112 a plurality of health records in the first subcategory of the first category from the first healthcare provider (754). FIG. 6E illustrates X-ray records 5016A and 5016B (ordered on October 1, 2017 and September 1, 2017, respectively) in response to detecting a tap gesture on the subcategory representation 5015A illustrated in FIG. 6D, for example.

[0218] In some embodiments, the plurality of health record subcategories includes a second representation of a second subcategory of the first category (754). FIG. 6D, for example, illustrates a subcategory representation 5015A (X-Ray Images subcategory) in response to detecting a tap gesture with contact 5506 on the category representation 5006B (Clinical Documents category) illustrated in FIG. 6C. Further, selection of the second representation of the second subcategory 5015B of the first category (CT Scan subcategory, FIG. 6D) causes the device 100 to display on the display 112 a plurality of health records of the second subcategory of the first category from the first healthcare provider (754). FIG. 6E-1 illustrates displaying X-ray records 5016A and 5016B obtained from Alpha Health Care and X-ray record 5016C obtained from Beta Health Care in response to detecting a tap gesture on the subcategory representation 5015A illustrated in FIG. 6D. In a similar embodiment where a tap gesture on the subcategory representation 5015B is detected and the user has completed the onboarding process with both Alpha Health Care and Beta Health Care, health records of CT scans obtained from both Alpha Health Care and Beta Health Care are displayed on the display 112. Organizing the user's health records into multiple subcategories (and further subcategory levels) of a category and providing only the health records that belong to that subcategory (or further subcategory levels) in a common user interface avoids the need for the user to navigate through all of the health records of a category to find a particular health record, thereby reducing the time the user spends searching for health records. Reducing the time the user spends searching for health records allows the user to use the device faster and more efficiently, reduces the device's power usage, and improves battery life.

[0219] In some embodiments, the plurality of health records in the first category from the second healthcare provider includes a fifth health record in the first category from the second healthcare provider (756). FIG. 6H-1, for example, shows a medication record 5018C (GHI medication) obtained from Beta Health Care. In some embodiments, the plurality of health records in the second category from the second healthcare provider includes a sixth health record in the second category from the second healthcare provider (756). FIG. 6H-1, for example, shows an x-ray record 5016C obtained from Beta Health Care. In some embodiments, the fifth health record in the first category from the second healthcare provider and the sixth health record in the second category from the second healthcare provider are records of a third visit to the second healthcare provider (756). FIG. 6H-1, for example, shows that the medication record 5018C and the x-ray record 5016C were both obtained during a visit to Beta Health Care on September 15, 2017. In some embodiments, in response to receiving the second request to display the health records for the first user, the device 100 simultaneously displays the fifth health record and the sixth health record on the display 112 in a third group, the third group being identified on the display 112 by a third date of a third visit to the second healthcare provider, and the first group, the second group, and the third group being simultaneously displayed on the display 112 (756). FIG. 6H-1, for example, illustrates the simultaneous display of a medication record 5018C and an x-ray record 5016C, both of which were obtained during a visit to Beta Health Care on September 15, 2017. FIG. 6H-1 also illustrates the simultaneous display of the first and third groups of health records (health records obtained during a visit to Alpha Health Care on October 1, 2017 and health records obtained during a visit to Beta Health Care on September 15, 2017). In some embodiments, when the size of the display 112 is large, the device 100 displays the health records of the first group, the second group, and the third group simultaneously.The method reduces the cognitive burden on a user when viewing health records from multiple health providers by grouping the health records based on the appointment dates the user has with the health care provider and by ordering the different groups based on appointment dates. The method also improves user efficiency by allowing the user to identify health records based on appointment dates with the health care provider. For battery-operated computing devices, allowing the user to browse the user's health records faster and more efficiently conserves power and extends the time between battery charges.

[0220] In some embodiments, in response to receiving a first request to view health records for the first user, the device 100 displays (758) on the display 112 first content identifying the identity and location of the first healthcare provider. FIG. 6B, for example, displays medication records 5018A and 5018B (ABC and DEF medications). Each medication record 5018A and 5018B identifies Alpha Health Care as the healthcare provider who prescribed the corresponding medication. In some embodiments, each medication record includes further information about the corresponding medication, such as dosage, medication taking instructions, the name of the physician who prescribed the medication, the location of Alpha Health Care, the location of the nearest pharmacy to pick up or refill the medication, a medication fact sheet, the date the medication is scheduled to run out, and other suitable content providing information about the medication. In some embodiments, in response to receiving a second request to view health records for the first user, the device 100 displays (758) on the display 112 second content identifying the identity and location of the second healthcare provider. FIG. 6J, for example, displays health condition records 5020A and 5020B (cholesterol level and chronic migraine headaches). Each health condition record 5020A and 5020B identifies Alpha Health Care as the health care provider who prescribed the medication for the corresponding health condition. In some embodiments, each health condition record includes further information about the corresponding health condition, such as the location of Alpha Health Care. This method improves user efficiency by allowing the user to obtain information about the health care provider without contacting the health care provider. This method also enhances device usability and makes the user device interface more efficient by allowing the user to identify the location and other information about the provider without performing further input. This method also reduces strain on existing networks and reduces the amount of communication between the user and the health care provider. For battery-operated computing devices, allowing the user to browse the user's health records faster and more efficiently conserves power and increases the time between battery charges.

[0221] In some embodiments, selecting a first representation of a first category while device 100 is associated with a first healthcare provider and not associated with a second healthcare provider causes device 100 to display on display 112 past health records associated with the first category from the first healthcare provider, where the past health records associated with the first category include a plurality of health records of the first category from the first healthcare provider (760). Figure 6K illustrates, for example, past health records of a user's cholesterol level obtained from Alpha Health Care (e.g., cholesterol representations 5030B-5030C of the user's cholesterol level measured on September 1, 2016 and January 1, 2016) in response to detecting the gesture illustrated in Figure 6J.

[0222] In some embodiments, selecting a second representation of the second category while the device 100 is associated with the first healthcare provider and not associated with the second healthcare provider causes the device 100 to display on the display 112 past health records associated with the second category from the first healthcare provider, where the past health records associated with the second category include a plurality of health records of the second category from the first healthcare provider (760). FIG. 6J, for example, shows health condition records 5020A-C (cholesterol level, chronic migraine headaches, and anxiety disorder, respectively). In some embodiments, if the user selects health condition record 5020B, past health records of the user's migraine history are displayed.

[0223] In some embodiments, selecting the first representation of the first category while the device 100 is associated with the first healthcare provider and the second healthcare provider causes the device 100 to display on the display 112 past health records associated with the first category from the first healthcare provider and the second healthcare provider, where the past health records associated with the first category include one or more health records of the first category from the first healthcare provider and one or more health records of the first category from the second healthcare provider (760). FIG. 6K-1 illustrates, for example, past health records of the user's cholesterol level obtained from Alpha Health Care (e.g., cholesterol representations 5030B-5030C of the user's cholesterol level measured on September 1, 2016 and January 1, 2016) and past health records of the user's cholesterol level obtained from Beta Health Care (e.g., cholesterol representation 5030D of the user's cholesterol level measured on September 15, 2015) in response to detecting the gesture shown in FIG.

[0224] In some embodiments, selecting a second representation of the second category while the device 100 is associated with the first and second healthcare providers causes the device 100 to display on the display 112 past health records associated with the second category from the first and second healthcare providers, where the past health records associated with the second category include one or more health records of the second category from the first healthcare provider and one or more health records of the second category from the second healthcare provider (760). In some embodiments, FIG. 6J illustrates, for example, health condition records 5020A-C (cholesterol level, chronic migraine headaches, and anxiety disorder, respectively). In some embodiments, if the user selects health condition record 5020B, past health records of the user's migraine history obtained from both Alpha Health Care and Beta Health Care are displayed. This method reduces the number of inputs required to obtain past health records and creates a more efficient human-machine interface by allowing the user to access the past records by selecting a health record, thereby allowing the user to access the user's past health records associated with that health record. In this manner, the user can easily access the user's past health records by selecting the health record, improving user efficiency. For battery-operated computing devices, allowing the user to view the user's past health records faster and more efficiently conserves power and extends the time between battery charges.

[0225] It should be understood that the particular order described for the operations in Figures 7A-7F is merely exemplary, and the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that the details of the processes (e.g., Figures 7A-7F) described above with respect to method 700 are also applicable in a similar manner to the methods described below. For example, methods 900 and 1100 optionally include one or more of the characteristics of the various methods described above with reference to method 700. For example, the method for displaying aggregated health records described above with reference to 700 is optionally used by method 900 to display current and past health records within a dashboard user interface. Similarly, the method for displaying aggregated health records described above with reference to 700 is optionally used by method 1100 to display health records of specific health states that a user can designate as active or inactive within a health record manager. For the sake of brevity, these details will not be repeated below.

[0226] 8A-8N illustrate an exemplary dashboard user interface with aggregated health records according to some embodiments. FIGS. 8A-8N enable a single dashboard view of a comprehensive overview of a user's current health care data to be displayed using health records obtained from each of such user's health care providers. For convenience, the health record is described herein as a health record of the user of device 100. However, the health record may also be a family or other personal health record associated with the user of the exemplary user interface. For purposes of FIGS. 8A-8N, the user has completed an onboarding process with Alpha Health Care and Beta Health Care or has health records from Alpha Health Care and Beta Health Care that are managed, stored on device 100, or accessible by device 100 using the dashboard user interfaces of FIGS. 8A-8N. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 9A-9D.

[0227] Although some of the examples below are described with reference to input on a touch screen display (combining a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from display 450, as shown in FIG. 4B. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, an audio interface, or other suitable interface. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is, optionally, a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., an enantiomeric center of the respective contact or a point associated with the respective contact), or an enantiomeric center of two or more contacts detected on touch-sensitive display system 112. However, similar operations are performed on a device having display 450 and a separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying a user interface described below, optionally with a focus selector.

[0228] 8A-8N show a health record summary displayed within the dashboard that includes information derived from the user's current health record, such information hereinafter referred to as health record summary information. Current health record, as used herein, refers to any health record of health information that is newer than other health records stored on or accessible by the device 100 that are managed using the dashboard user interface of FIGS. 8A-8N. The dashboard user interface of FIGS. 8A-8N also allows the user to view information about the user's health record at different levels of detail. More specifically, the dashboard first displays a health record summary that includes health record summary information, and then allows the user to interact with the dashboard to drill down and access further information not included in the health record summary. Similarly, the user may also interact with the dashboard to review the user's past health record. As the device 100 receives updates to existing health records or updates to new health records, the health record summary displayed in the dashboard is updated periodically such that the user is presented with health record summary information based on the most recent health records, but is not presented with past health records that are out of date or that may no longer be otherwise relevant.

[0229] 8A shows category representations 5006A-5006E (allergy, clinical documentation, lab results, medication, and health condition categories, respectively) and a health record summary representation 7005. The health record summary representation 7005 is an affordance that includes text indicating that such affordance is associated with a health record summary. The health record summary representation 7005 is selectable by a user to view the health record summary. FIGS. 8A-8B show detecting a tap gesture with contact 7502 on the health record summary representation 7005 of FIG. 8A and displaying the health record summary on the display 112 within the dashboard of FIG. 8B in response to the tap gesture.

[0230] FIG. 8B illustrates displaying a health record summary dashboard on the display 112, including health record summary information including multiple types of health records. The health records in the illustrated embodiment are current health records obtained from both Alpha Health Care and Beta Health Care. In the illustrated embodiment, all current health records are displayed for each category of health records, regardless of which healthcare provider the current health records are from. In this manner, the user's most current health information is displayed within the dashboard. In the illustrated embodiment, the health indicator summary includes health indicator records 7012A-7012C, medication records 7014A-7014C, and health condition records 7016A-7016D. FIG. 8B also illustrates displaying health indicator affordance 7011A, medication affordance 7011B, and health condition affordance 7011C. In the illustrated embodiment, health indicator affordance 7011A, medication affordance 7011B, and health status affordance 7011C are selectable by the user to view the user's past health indicator record, medication record, and health status record, respectively.

[0231] In the embodiment shown in FIG. 8B, health indicator records 7012A-7012C are displayed in alphabetical order based on the type of health indicator record within a group with health indicator affordance 7011A. Health indicator record 7012A includes a current measurement of the user's blood pressure measured by Beta Health Care on November 1, 2017. In the illustrated embodiment, the November 1, 2017 measurement is the user's most recent blood pressure measurement from both Alpha Health Care and Beta Health Care. In some embodiments, if past health records of the user's blood pressure level measured prior to November 1, 2017 are available, the user can access such past health records by selecting health indicator affordance 7011A. Health indicator record 7012B includes a current measurement of the user's cholesterol level measured by Alpha Health Care on October 1, 2017. Health indicator record 7012C includes a current measurement of the user's serum iron level measured by Alpha Health Care on October 1, 2017.

[0232] In the embodiment shown in Figure 8B, medication records 7014A-7014C are displayed in alphabetical order based on medication type within a group with medication affordance 7011B. Medication health records 7014A-7014C are the user's current prescriptions for ABC, DEF, and GHI medications, respectively. Each medication health record 7014A-7014C also identifies the prescription date for the corresponding medication and the healthcare provider who prescribed the medication.

[0233] In the embodiment shown in Figure 8B, health condition records 7016A-7016D are displayed in alphabetical order based on health condition type within a group with health condition affordance 7011C. Health condition records 7016A-7016D are health records for the user's current health conditions: anxiety, asthma, high cholesterol, and migraines, respectively. In some embodiments, health condition records 7016A-7016B and 7016D also include information about medications recently prescribed for the corresponding health conditions (anxiety, asthma, and migraines), even if these medications are individually identified within a medication group.

[0234] While the embodiment shown in FIG. 8B shows ten health records in the health record summary, in other embodiments, the health record summary may include a different number of the user's current health records. Additionally, in some embodiments, not all of the current health records included in the health record summary are displayed simultaneously on the display 112. In one or more of such embodiments, the user performs a gesture to scroll through the current health records displayed in the health record summary. While the health records displayed in the illustrated embodiment are grouped by category and arranged in alphabetical order, in other embodiments, the health records may be grouped or ordered by date, provider, similarity, severity, associated biological function or system (e.g., all cardiac measurements followed by all endocrine measurements), or based on any other suitable criteria. In one embodiment, the order in which the health records are displayed can be changed by the user or provider (e.g., a primary care physician). FIG. 8B also shows detecting a tap gesture with contact 7503 on the health record affordance 5304 to return to the user interface shown in FIG. 8A.

[0235] FIG. 8B-1 is an alternative embodiment of a healthcare summary dashboard displayed in response to detecting a tap gesture with contact 7502 on the health record summary representation 7005 of FIG. 8A. FIG. 8B-1 includes healthcare summary information shown as pictorial representations of health records. More specifically, FIG. 8B-1 shows a health indicator record 7012A (blood pressure level) and a health indicator record 7012B (cholesterol level). In the illustrated embodiment, the health indicator record 7012A includes a chart 7712 showing the user's blood pressure level (140 / 90 mmHg) within a blood pressure level range. In the illustrated embodiment, the numerical value of the user's blood pressure level is located on the chart 7712 near where the measured blood pressure falls within this range. In this way, the chart 7712 may indicate where the user's blood pressure level falls relative to a blood pressure level range that indicates the normality or severity of the user's blood pressure. In some embodiments, the health indicator record 7012A also includes a legend or other explanation of how to interpret the chart 7712 or information regarding the significance of the user's blood pressure level to help the user evaluate the user's blood pressure level.

[0236] Health indicator record 7012B includes a bar graph 7714 that indicates the user's cholesterol level (269 md / dL) within a cholesterol level range. In the illustrated embodiment, the numerical value of the user's cholesterol level is located on chart 7714 adjacent to the location of the measured cholesterol within the range. In the illustrated embodiment, the bar containing the numerical value of the user's cholesterol level is displayed in a color that indicates the normality or severity of the user's cholesterol level. For example, the bar may be green, yellow, or red if the user's cholesterol level is below 200 mg / dL, between 200 mg / dL and 300 mg / dL, or above 300 mg / dL, respectively.

[0237] In the embodiment shown in FIG. 8B-1, the health indicator record 7012A includes a blood pressure level displayed in text with a larger font than other text displayed in the health indicator record 7012A. In this manner, important information, such as test measurements or laboratory results, may be highlighted to emphasize such information to the user. Similarly, in the health indicator record 7012B, the user's cholesterol level measurement is also displayed in a larger font to help the user identify the most recent measurement of the user's cholesterol level. In other embodiments, the text containing the user's health indicator measurement is highlighted, displayed in a different color, bolded, italicized, or otherwise suitably formatted to allow the user to quickly identify the user's health indicator value. FIG. 8B-1 also illustrates detecting a tap gesture with contact 7504 on the health record affordance 5304 to return to the user interface shown in FIG. 8A.

[0238] The device 100 periodically receives updates to the user's health record. FIG. 8C illustrates displaying a dashboard of a health record summary including updates to the health indicator record 7012A of FIG. 8B including the user's blood pressure measurement. As shown in FIG. 8C, the health indicator record 7052A (blood pressure level measured on December 1, 2017) is displayed in the health record summary in place of the health indicator record 7012A of FIG. 8B including the user's previous blood pressure measurement (blood pressure level measured on November 1, 2017). In addition, an update badge 7141A is displayed with the health indicator record 7052A to indicate that the health indicator record 7052A is an updated health record and to draw the user's attention to the health indicator record 7052A. FIG. 8C also illustrates detecting a tap gesture with contact 7505 on the health record affordance 5304 to return to the user interface shown in FIG. 8A.

[0239] FIG. 8C-1 illustrates an alternative embodiment of the dashboard of FIG. 8C. In the illustrated alternative embodiment, the device 100 has not received the health indicator record 7052A including the new blood pressure measurement shown in FIG. 8C. However, the device 100 has received the health indicator record 7052B including a newer cholesterol measurement than the health indicator record 7012B shown in FIG. 8B. Thus, FIG. 8C-1 illustrates that the health indicator record 7052B is displayed in the health record summary instead of the health indicator record 7012B shown in FIG. 8B. In some embodiments, an update may affect multiple health records displayed in the health record summary. In such an embodiment, all affected health records displayed in the health record summary may be updated. In the illustrated embodiment, the health condition record 7016C (high cholesterol) of FIG. 8B is also updated along with the health condition record 7056C to reflect the user's current cholesterol measurement. Additionally, update badges 7141B and 7141C are displayed with the health indicator record 7052B and the health condition record 7056C to indicate the update and to draw the user's attention to the corresponding health records. Figure 8C-1 further illustrates detecting a tap gesture with contact 7506 on the health indicator record 7052B and displaying the health record archive 7058 of Figure 8D in response to the tap gesture.

[0240] FIG. 8D illustrates one embodiment of a health record archive 7058 that includes past health records of the user's cholesterol level. The health record archive is a user interface for displaying past health records. In the illustrated embodiment, the health record archive 7058 includes a health indicator record 7052B that includes a current measurement of the user's cholesterol level, a health indicator record 7012B that was displayed in the health record summary shown in FIG. 8B before the device 100 received the health indicator record 7052B, and additional health indicator records 7056A-7056C. The health indicator records 7056A-7056C include measurements of the user's cholesterol level measured by Alpha Health Care or Beta Health Care on September 15, 2017, September 1, 2016, and January 1, 2016. A graph 7021 of the user's cholesterol level over time is also displayed within the health record archive 7058. The graph 7021 includes a number of bars each showing a different measurement of the user's cholesterol level associated with the health indicator records 7052B, 7012B, and 7056A-7056C. The bars may be displayed in a color that indicates the normality of the user's cholesterol level. For example, bars showing cholesterol level measurements below 200 mg / dL may be displayed in a first color, bars showing cholesterol level measurements between 200 mg / dL and 300 mg / dL may be displayed in a second color, and bars showing cholesterol level measurements above 300 mg / dL may be displayed in a third color. The health indicator records 7052B, 7012B, and 7056A-7056C and the graph 7021 provide the user with information regarding the user's cholesterol level over time. FIG. 8D also illustrates detecting a tap gesture involving contact 7507 on the health record summary affordance 5308 to display the user's health record summary dashboard of FIG. 8E.

[0241] Figure 8E illustrates an embodiment of the health record summary dashboard shown in Figure 8C-1 after the user views the new health record 7052B (cholesterol level) update in Figure 8C-1. In Figure 8E, the update badges 7141B and 7141C (shown in Figure 8C-1) are no longer displayed because the user has already confirmed the new health record 7052B update. Figure 8E further illustrates detecting a tap gesture with contact 7508 on the medication affordance 7011B and displaying the health record archive 7057 of Figure 8F in response to the tap gesture.

[0242] 8F illustrates one embodiment of a health record archive 7057 that includes a past health record of a user's medications. In the illustrated embodiment, the health record archive 7057 includes current medication records 7014A-7014C (for ABC, DEF, and GHI medications, respectively) and past medication records 7015A-7015D. Past medication records 7015A are expired prescriptions for currently prescribed GHI medications. Past medication records 7015A also include the prescription period for the expired prescriptions and the name of the healthcare provider who prescribed the medication. Past medication records 7015B-7015D are health records for medications that the user has stopped taking (for LMN, RST, and XYZ medications, respectively). In the illustrated embodiment, the past medication records 7015A-7015D are displayed in gray, in a smaller or lighter font, or in a different color than the current medication records 7014A-7014C to help the user distinguish between medications that the user is currently taking and medications that are past due. In some embodiments, the past medication records 7015A and the current medication records 7014C, both of which contain information about the GHI medication, are not displayed simultaneously in the health record archive. In some embodiments, the user selects the current medication record for a medication (such as an ABC medication) to access past medication records for the same medication that the user may have taken in the past or at a different dose. FIG. 8F further illustrates detecting a tap gesture involving contact 7509 on the medication record 7014A and displaying more information about the ABC medication of FIG. 8G in response to the tap gesture.

[0243] FIG. 8G shows displaying a fact sheet corresponding to the medication record 7014A including instructions, warnings, and active ingredients for the ABC medication. In other embodiments, additional information about the ABC medication may also be displayed, such as information about the pharmacy dispensing the medication, alternative sources for dispensing the medication (such as pharmacy benefit managers), copay information, insurance coverage information, available generics, a refill or expiration date for the medication, instructions or affordances for refilling the medication, dosage, side effects, or an image of the medication. Historical medication records 7015E and 7015F including expired prescriptions for the ABC medication are displayed in different colors to indicate that these prescriptions are no longer valid. FIG. 8G further shows detecting a tap gesture involving contact 7510 on the medication archive affordance 5310 to view the health record archive 7057 shown in FIG. 8F.

[0244] Similar to FIG. 8C-1, FIG. 8H also displays an embodiment of a health record summary dashboard after receiving updates to a user's health record. Health records provided by a healthcare provider may be incomplete. An incomplete health record is one that is missing information that would allow a user to properly understand the health record, such as a hospital visit date, a doctor's name, a prescription date, or other information. A health record may be flagged as incomplete by a healthcare provider, directly by a user, or automatically by device 100 in response to a determination that a field in the received health record that is expected for the type of health record received is missing. Such a determination by device 100 may be made by parsing the health record, automatically searching for a particular string, querying a header file for a particular health record, determining that a required field is missing or that the number of fields in such a health record received is less than the expected number, or any other suitable method.

[0245] In the embodiment shown in FIG. 8H, a new medication record 7014D update for JKL medication and a new health condition record 7016E update for arthritis are displayed in the health record summary with update badges 7141D and 7141E, respectively. Both the medication record 7014D and the health condition record 7016E identify the name of the healthcare provider who prescribed the medication and the name of the medication (JKL medication), but the prescription date is missing from both the medication record 7014D and the health condition record 7016E. In the illustrated embodiment, incomplete affordances 7020A and 7020B are displayed simultaneously with the update badges 7141D and 7141E to notify the user of the update to the user's health record and to inform the user that information is missing from the health record that is being updated. The incomplete affordances 7020A and 7020B are affordances that the user selects to obtain more information about the incomplete health record.

[0246] FIG. 8H further illustrates detecting a tap gesture with contact 7511 on the incomplete affordance 7020A on the medication record 7014D (JKL medication) and, in response to the tap gesture, displaying a notification 7250 of FIG. 8I regarding information missing from the medication record 7014D of FIG. 8H. In the illustrated embodiment, the notification 7250 is overlaid on the health record summary dashboard shown in FIG. 8H. The notification 7250 includes text indicating that the prescription date for the JKL medication is missing from the medication record 7014D of FIG. 8H. The notification 7250 also includes an edit affordance 7152 and an ignore affordance 7153. In some embodiments, the user can recognize the missing information (such as the prescription date missing from the medication record 7014D and the arthritis health record 7016E of FIG. 8H) and fill in the missing information. The user interacts with the edit affordance 7152 to edit or add information regarding the JKL medication, such as the prescription date. In this regard, Figure 8I also shows detecting a tap gesture with contact 7512 on edit affordance 7152. After the user adds information about the incomplete JKL drugs, the user selects ignore affordance 7153.

[0247] In response to the user selecting ignore affordance 7153 and device 100 determining that the missing information has been provided by the user, device 100 removes the display of notification 7020A from medication record 7014D (JKL medication) of FIG. 8H. Device 100 also removes the display of notification 7020B from health record 7016E of FIG. 8H because notification 7020B is an indication that health record 7016E (arthritis) was incomplete for the same reason (missing prescription date for JKL medication). In other embodiments, if device 100 determines that the user did not enter the missing correct information or if the user selected ignore affordance 7153 without entering any information, the incomplete affordances 7020A and 7020B of FIG. 8H remain displayed with medication record 7014D and health record 7016E, respectively.

[0248] Similar to FIG. 8H, FIG. 8J also displays a health record summary after receiving updates to the user's health record. There may be cases where the device 100 determines that no information is missing from the health record, but that the authenticity or accuracy of the health record should be verified by the user. The device 100 may make such a determination in response to determining that the information in the health record is unexpected or does not fall within a predetermined range of values, contains data that differs significantly from data contained in previous health records, is from a health care provider from whom the user has not received a health record for an extended period of time, or for any other suitable reason. In yet other embodiments, the device 100 determines that a health record should be verified if it is deemed inconsistent or contradictory to other health records.

[0249] In the embodiment shown in FIG. 8J, updates for a new medication record 7054B (DEF medication) and a new health record 7056A (anxiety disorder) have been received with the latest prescription date for the DEF medication and are displayed with update badges 7141F and 7141G, respectively. Although no information is missing from either medication record 7054B or health record 7056A, device 100, verification affordances 7022A and 7022B are simultaneously displayed with update badges 7141F and 7141G to inform the user that the user should verify health records 7054B and 7056A, respectively. Verification affordances 7022A and 7022B are affordances that the user selects to obtain more information about the health records that the user has been requested to verify.

[0250] FIG. 8J further illustrates detecting a tap gesture with contact 7514 on the verification affordance 7022B and, in response to the tap gesture, displaying the notification 7252 of FIG. 8K regarding the information in the health record 7056A (anxiety disorder) that the user was requested to verify. In one embodiment, the notification 7252 is overlaid on the health record summary dashboard of FIG. 8J as shown in FIG. 8K. The notification 7252 includes text requesting the user to confirm that DEF medication was prescribed for the anxiety disorder. The notification 7252 includes a confirmation affordance 7155 and a mark as inaccurate affordance 7154. The user interacts with the confirmation affordance 7155 to confirm that the corresponding health record is accurate. Alternatively, the user interacts with the mark as inaccurate affordance 7154 to indicate that the information is inaccurate. FIG. 8K further illustrates detecting a tap gesture with contact 7516 on the confirmation affordance 7155. In some embodiments, in response to detecting a tap gesture with contact 7516 on confirmation affordance 7155, device 100 designates the information in both medication record 7054B (DEF medications) and health condition record 7056A shown in FIG. 8J as accurate and removes verification affordances 7022A and 7022B from the health record summary dashboard shown in FIG. 8J.

[0251] Similar to Figure 8J, Figure 8L also displays a health record summary after receiving an update to a user's health record. In the embodiment shown in Figure 8L, a new medication record 7014E update for XYZ medication prescribed by Omega Health Care is received and displayed with an update badge 7161F. If no information is missing from the health record 7014E, but the device 100 determines that the user has never been prescribed the medication by Omega Health Care, a verification badge 7122C is displayed to notify the user that the user should verify the accuracy of the health record 7014E.

[0252] FIG. 8L further illustrates detecting a tap gesture with contact 7518 on the verification affordance 7122C and, in response to the tap gesture, displaying a notification 7253 of FIG. 8M regarding the information of the health record 7014E (XYZ medication) of FIG. 8L that the user was requested to verify. In the illustrated embodiment, the notification 7253 is overlaid on the health record summary dashboard of FIG. 8L as shown in FIG. 8M. The notification 7253 includes text requesting the user to confirm that XYZ medication was prescribed by Omega Health Care on January 15, 2018. The notification 7253 also includes a confirmation affordance 7155 and a mark as incorrect affordance 7154. FIG. 8M further illustrates detecting a tap gesture from the user with contact 7520 on the mark as incorrect affordance 7154. In some embodiments, in response to detecting a tap gesture involving contact 7520 on the mark-as-incorrect affordance 7154, device 100 designates medication record 7014E as inaccurate and removes medication record 7014E from the health record overview dashboard of FIG. 8N. As shown in FIG. 8N, medication record 7014E of FIG. 8L is no longer displayed in the health record overview. In some embodiments, the health record marked as inaccurate by the user remains included in the health record archive. In this regard, the user can interact with medication affordance 7011B of FIG. 8N to confirm medication record 7014E.

[0253] 9A-9D are flow diagrams illustrating a method for displaying a dashboard user interface with aggregated health records using an electronic device according to some embodiments. More specifically, FIGS. 9A-9D are flow diagrams illustrating a method for displaying a user's current and past health records using, for example, the user interfaces of FIGS. 8A-8N. As described with reference to FIGS. 8A-8N, method 900 can be utilized to display a dashboard user interface for displaying a user's current and past health records. Method 900 is performed on a device (e.g., devices 100, 300, 500 shown in FIGS. 1, 3, and 5A, respectively). In one such embodiment, display 112 is a touchscreen display, with a touch-sensitive surface on or integrated into display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, an audio interface, or other suitable interface. Some operations in method 900 are optionally combined. Furthermore, the order of some operations is optionally changed.

[0254] As described below, the method 900 provides an intuitive way to display a dashboard user interface with a user's aggregated health records. The method 900 also provides an intuitive way to display a user's current and past health records. This method reduces the cognitive burden on the user as the user browses the current and past health records, creating a more efficient human-machine interface. For battery-operated computing devices, allowing the user to browse the user's current and past health records faster and more efficiently conserves power and extends the time between battery charges.

[0255] Method 900 also provides an intuitive way to display a representation of a particular health condition of a user to indicate the severity of such condition. The method reduces the cognitive burden on the user by allowing the user to determine the severity of a particular health condition from a displayed representation of the health condition, creating a more efficient human-machine interface. The method improves user efficiency by reducing the time required for the user to understand the severity of the user's health condition. For battery-operated computing devices, allowing the user to understand the severity of the user's health condition more quickly and efficiently conserves power and extends the time between battery charges.

[0256] While associated with health data for a first user that includes a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type, device 100 receives a request via one or more input devices to display health record summary information for the user (902). Figure 8A, for example, illustrates detecting a tap gesture involving contact 7502 on health record summary representation 7005.

[0257] In response to receiving the request, the device 100 displays (904) on the display health record summary information for the first user, including displaying multiple health record items simultaneously. Figure 8B, for example, illustrates displaying a health record summary including health indicator records 7012A-C (blood pressure levels, cholesterol levels, and serum iron levels), medication records 7014A-C (ABC medications, DEF medications, and GHI medications, respectively), and health condition records 7016A-D (anxiety disorders, asthma, high cholesterol, and migraines, respectively) in response to detecting a tap gesture with contact 7502 on the health record summary representation 7505 shown in Figure 8A.

[0258] The plurality of health record items includes a first health record item of a first type for a first date, where the health record summary information does not include a plurality of health record items of the first type for dates prior to the first date (906). FIG. 8B, for example, illustrates displaying health indicator record 7012A (blood pressure level) within the health record summary. Health indicator record 7012A includes a measurement of the user's blood pressure that was taken on November 1, 2017. Previous measurements of the user's blood pressure are not included in the health record summary.

[0259] In some embodiments, the first health record item includes a representation of the severity of the first user's condition (908). FIG. 8B-1 also illustrates displaying a health indicator record 7012A (blood pressure level) within the health record summary. In the illustrated embodiment, the health indicator record 7012A includes a chart 7712 showing the user's blood pressure level within a blood pressure level range. This method reduces the cognitive burden on the user by providing the user with a representation (such as an image, graph, or chart) that allows the user to determine the severity of the health condition based on the representation, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify the severity of the condition from the representation. In the case of a battery-operated computing device, allowing the user to identify the severity of the condition faster and more efficiently conserves power and increases the time between battery charges.

[0260] In some embodiments, the first health record item includes a representation of the first user's condition over a period of time (910). FIG. 8D, for example, shows displaying a graph 7021, which is a graph of the user's cholesterol levels over a two-year period. In some embodiments, the health indicator record 7012A (blood pressure level) of FIG. 8B also includes a graph 7021. Providing a graph of the user's condition over time allows the user to determine if the user's condition has changed over time without having to navigate multiple user interfaces to access data showing the user's condition over different time periods, reducing the cognitive burden on the user and creating a more efficient human-machine interface. For battery-operated computing devices, allowing the user to more quickly and efficiently identify the user's condition over time conserves power and increases the time between battery charges.

[0261] The plurality of health record items also includes a second health record item of a second type with a second date different from the first date, where the health record summary information does not include the plurality of health record items of the second type with dates prior to the second date (912). FIG. 8B, for example, shows displaying a medication record 7014A. The medication record 7014A is a health record of a user's prescription for ABC drug prescribed to the user on October 1, 2017. Prescriptions for ABC drug with dates prior to October 1, 2017 are not included in the health record summary.

[0262] In some embodiments, the health data for the first user includes a plurality of health record items of a third type different from the first type and the second type (914). FIG. 8B, for example, illustrates displaying health condition record 7016D. Health condition record 7016D is a health record for a migraine condition of the user. In some embodiments, the device 100 simultaneously displays (914) the first health record item, the second health record item, and a third health record item of a third type for a third date in the health record summary information. FIG. 8B, for example, illustrates simultaneously displaying health indicator record 7012A (blood pressure level), medication record 7014A (ABC medication), and health condition record 7016D (migraine) in the health record summary. Further, in some embodiments, the health record summary information does not include a plurality of health record items of the third type for a date prior to the third date (914). Health condition record 7016D includes information regarding ABC medication prescribed to the user on October 1, 2017. Prior health conditions related to the user's migraine condition are not included in the health record summary. Similarly, medication record 7014C of FIG. 8B is a health record of the user's prescription for a GHI drug prescribed to the user on September 15, 2017. Prescriptions for GHI drugs dated prior to September 15, 2017 are also not included in the health record summary. Displaying multiple types of health records in a common interface allows a user to browse multiple types of health records without having to navigate between multiple user interfaces, creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to browse the user's records faster and more efficiently conserves power and extends the time between battery charges.

[0263] In some embodiments, the health data includes health data associated with multiple healthcare providers of the first user, the first health record item being associated with a first healthcare provider of the multiple healthcare providers, and the second health record item being associated with a second healthcare provider of the multiple providers (916). FIG. 8B shows, for example, that a health indicator record 7012A (blood pressure level) was obtained from Beta Health Care and a medication record 7014A (ABC medications) was obtained from Alpha Health Care. Displaying multiple health records from multiple healthcare providers in a common interface allows a user to browse records from different healthcare providers without having to navigate between multiple user interfaces, creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to browse the user's health records faster and more efficiently conserves power and increases the time between battery charges.

[0264] In some embodiments, the plurality of health record items includes a fourth health record item of a fourth type on a fourth date, where the first health record item and the fourth health record item are associated with a first healthcare provider, and the first date and the fourth date are dates of a first and second visit to the first healthcare provider (918). FIG. 8B, for example, shows a health indicator record 7012A (blood pressure level) and a health condition record 7016B (asthma). Both health records were obtained from Beta Health Care. Further, the health indicator record 7012A was obtained during a visit to Beta Health Care on November 1, 2017, and the health condition record 7016B was obtained during a visit to Beta Health Care on September 15, 2017. Displaying the multiple health records obtained on different dates in a common interface allows a user to browse the health records obtained on different dates without having to navigate between multiple user interfaces, creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to browse their health records faster and more efficiently conserves power and extends the time between battery charges.

[0265] In some embodiments, the device 100 receives (920) a third health record item of the first type for a third date that is later than the first date after displaying the health record including the first health record item and the second health record item. The device 100 receives the health indicator record 7052A (blood pressure level measured on December 1, 2017) shown in FIG. 8C after displaying the health record summary shown in FIG. 8B (including a medication record 7014A for ABC drug prescribed on October 1, 2017 and a health indicator record 7012A for blood pressure measured on November 1, 2017). However, the health indicator record 7052A was received before the device 100 displayed the health record summary shown in FIG. 8C. In some embodiments, the device 100 receives (920) a second request to display health record summary information for the first user via one or more input devices after receiving the third health record item. In some embodiments, the user interface shown in Figure 8A is displayed on the display 112 once the device 100 receives the health indicator record 7052A. In such embodiments, the user performs a gesture similar to the tap gesture shown in Figure 8A (involving contact on the health record summary representation 7005) to view the health record summary shown in Figure 8C.

[0266] Further, in some embodiments, in response to receiving the second request, the device 100 displays (920) an updated health record summary for the first user on the display 112, including simultaneously displaying the second health record item and the third health record item without displaying the first health record item. FIG. 8C illustrates an updated health record summary including, for example, health indicator record 7052A (blood pressure level). Health indicator record 7052A includes a measurement of the user's blood pressure measured on December 1, 2017. Health indicator record 7012A includes a measurement of the user's blood pressure measured on an earlier date. After receiving the more recent measurement of the user's blood pressure, the device 100 displays health indicator record 7052A in place of health indicator record 7012A in the updated health record summary. Displaying a health record summary that is updated over time to include updates to the user's existing health record allows the user to access the user's updates in a common interface to obtain the user's most current health record without navigating multiple user interfaces. The method also reduces the cognitive burden on the user by allowing the user to access their current health records through the health record overview, creating a more efficient human-machine interface. The method improves user efficiency by allowing the user to access their current health records through the health record overview. For battery-operated computing devices, allowing the user to view the user's current health records faster and more efficiently conserves power and extends the time between battery charges.

[0267] In some embodiments, the device 100 receives a new health record item of health data for the first user after displaying the health record including the first health record item and the second health record item, the new health record item having a date later than the first date and the second date (922). In some embodiments, the device 100 receives the medication record 7014D (JKL Drugs) shown in FIG. 8H before displaying the medication record 7014D in the medication record summary shown in FIG. 8H. In some embodiments, the device 100 receives a third request to display health record summary information for the first user via one or more input devices after receiving the new health record item (922). In some embodiments, the user interface shown in FIG. 8A is displayed on the display 112 at the time the device 100 receives the medication record 7014D. In such embodiments, the user performs a gesture similar to the tap gesture shown in FIG. 8A to view the health record summary shown in FIG. 8H.

[0268] In some embodiments, in response to receiving the third request, the device 100 displays (922) an updated health record summary for the first user on the display, including simultaneously displaying the first health record item, the second health record item, and the new health record item. FIG. 8H illustrates displaying an updated health record summary including, for example, health indicator record 7012A (blood pressure level), medication record 7014A (ABC medication), and medication record 7014D (JKL medication). Displaying a health record summary that is updated over time to include the user's new health records allows the user to access the user's updates in a common interface to obtain the user's most current health record without navigating multiple user interfaces. This method also reduces the cognitive burden on the user by allowing the user to access the current health record through the health record summary, creating a more efficient human-machine interface. This method improves the user's efficiency by allowing the user to access the user's current health record through the health record summary. For battery-operated computing devices, allowing a user to view their current health records faster and more efficiently conserves power and extends the time between battery charges.

[0269] In some embodiments, the device (100) receives (924) a first request via one or more input devices to display a first type of multiple health record items not displayed in the overview. FIG. 8C-1, for example, shows a tap gesture with contact 7506 on health indicator record 7052B (cholesterol level). In some embodiments, the device (100) displays (924) on the display a first type of multiple health record items with dates earlier than the first date in response to receiving the first request to display a first type of multiple health record items not displayed in the overview. FIG. 8D, for example, shows displaying health indicator records 7056A-7056C (cholesterol level) in response to detecting the tap gesture shown in FIG. 8C-1. Health indicator records 7056A-7056C include measurements of the user's cholesterol level taken by employees of Alpha Health Care or Beta Health Care on September 15, 2017, September 1, 2016, and January 1, 2016. Health indicator records 7056A-7056C all predate health indicator record 7052B. Additionally, none of health indicator records 7056A-7056C are displayed in health indicator record 7012B (cholesterol level) shown in FIG. 8H. By allowing a user to access the user's past health records via a health record summary, the method reduces the number of inputs required to retrieve past health records, creating a more efficient human-machine interface. By allowing a user to access the user's past health records via a health record summary, the method improves user efficiency. For battery-operated computing devices, allowing a user to view the user's past health records faster and more efficiently conserves power and increases the time between battery charges.

[0270] In some embodiments, in response to receiving a first request to display a plurality of health record items of a first type not displayed in the overview, the device (100) displays (926) a health record archive for the first user on the display 112, including simultaneously displaying a health record item of the first type for a most recent date and one or more of the plurality of health record items of the first type for dates prior to the first date. FIG. 8D illustrates, for example, simultaneously displaying a health indicator record 7052B including the user's most recent cholesterol measurement, measured on December 1, 2017, and health indicator records 7056A-7056C including previous measurements of the user's cholesterol level. By simultaneously displaying the user's current and past health records, it is not necessary to navigate multiple user interfaces to obtain both the user's current health record and the user's past health records. This method reduces the cognitive burden on the user by allowing the user to view the user's current and past health records within one user interface, creating a more efficient human-machine interface. The method improves user efficiency by allowing a user to view the user's current and past health records without having to navigate different user interfaces to view the current and past health records. For battery-operated computing devices, allowing a user to view the user's current and past health records faster and more efficiently conserves power and extends the time between battery charges.

[0271] In some embodiments, the device 100 displays (928) a fourth health record item of the first type in the health record archive on the display 112 in response to receiving a first request to display a plurality of health record items of the first type not displayed in the overview. FIG. 8D illustrates displaying a graph 7021 of the user's cholesterol level over time in response to detecting a tap gesture, for example, as shown in FIG. 8C-1. In some embodiments, the fourth health record item includes (928) a representation of a health indicator measured on a fourth date prior to the first date. The graph 7021 includes current and previous measurements of the user's cholesterol level. In other embodiments, one or more of the health indicator records 7056A-7056C (cholesterol levels) shown in FIG. 8D also include a representation (such as a bar graph or scale) of the user's previous cholesterol level. Displaying a representation of past health indicators may free up communication systems, reduce bandwidth on the network, and conserve energy, since the user may be able to determine the user's health indicators over time without contacting the user's healthcare provider. For battery-operated computing devices, allowing a user to obtain historical information about the user's health indicators faster and more efficiently conserves power and extends the time between battery charges.

[0272] In some embodiments, after displaying the health record summary information including the first health record and the second health record, the device 100 receives (930) a third health record item of a third type having a third date that is later than the first date and the second date. The health condition record 7016E (JKL medication) of FIG. 8H was received by the device 100 after the device 100 received the health index record 7012A (blood pressure level) and medication record 7014A (ABC medication) of FIG. 8B. The health condition record 7016E includes information regarding the user's arthritis condition and information regarding the JKL medication prescribed to the user on November 15, 2017. The date of the health condition record 7016E is later than the health index record 7012A (November 1, 2017) and the medication record 7014A (October 1, 2017). In some embodiments, in response to the request to view the health record summary information, the device 100 updates the health record summary information to include the third health record item, and the first health record item, the second health record item, and the third health record item are simultaneously displayed in the health record summary information (930). As shown in FIG. 8N, the health indicator record 7012A (e.g., the first health record item), the medication record 7014A (e.g., the second health record item), and the health condition record 7016E (e.g., the third health record item) are simultaneously displayed in the health record summary. Displaying a health record summary that includes multiple types of health records allows a user to view multiple types of health records in a common interface without having to navigate between multiple user interfaces, reducing the cognitive burden on the user and creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to access multiple types of health records from a common interface. For battery-operated computing devices, allowing a user to view the user's current health records faster and more efficiently conserves power and increases the time between battery charges.

[0273] In some embodiments, in response to a request to display the health record summary information, the device 100 displays (932) an incomplete record affordance in the health record summary information pursuant to a determination that a health record item of health data for the first user is incomplete. FIG. 8H illustrates, for example, displaying the incomplete affordance 7020A with the medication record 7014D (JKL meds) after determining that information is missing from the medication record 7014D. This method reduces the number of mistakes made due to the user relying on records with missing information. This method reduces the cognitive burden on the user by identifying to the user the health records with missing information. This method improves the user's efficiency by allowing the user to optionally ignore records with missing information when reviewing the user's health record. For battery-operated computing devices, allowing the user to review the user's health record faster and more efficiently conserves power and increases the time between battery charges.

[0274] In some embodiments, the device 100 receives (934) a user verification of the accuracy of a health record item of the health record items displayed within the health record summary information via one or more input devices. FIG. 8K illustrates, for example, detecting a tap gesture with contact 7516 on a confirmation affordance 7155 that confirms that the DEF medication was prescribed for the anxiety disorder. In response to receiving the user verification of the accuracy of the health record item, the device 100 provides (934) the user verification to a healthcare provider associated with the health record item. In some embodiments, in response to detecting the user's input illustrated in FIG. 8J, the device 100 automatically notifies Alpha Health Care that the DEF medication was verified by the user as a medication the user is taking to treat the user's anxiety disorder. This method reduces the cognitive burden on the user by allowing the user to verify the accuracy of the health record. This method improves the efficiency of the user by allowing the user to verify the accuracy of a particular health record without waiting for verification from a healthcare provider. The method also reduces the need to request the healthcare provider to verify the health record, thereby reducing the bandwidth required to send the request to the healthcare provider's electronic system. The method also reduces the burden on the healthcare provider's electronic system to process the request, thereby reducing the power consumption of the electronic system. By automatically notifying the healthcare provider's electronic system that the health record from the healthcare provider has been verified by the user, the need for the healthcare provider to contact the user or the user's device (through the electronic system or through other telecommunication means) to verify the accuracy or completeness of the health record is reduced. This frees up the communication system, reduces network bandwidth, and saves energy.

[0275] In some embodiments, the device 100 receives a first user instruction via one or more input devices indicating that a health record item among the health record items included in the health record summary information is inaccurate (936). FIG. 8M illustrates, for example, detecting a tap gesture with contact 7520 on the mark-as-inaccurate affordance 7154 to mark the medication record 7014E (XYZ medication) of FIG. 8L as inaccurate. In some embodiments, the device 100, in response to receiving the first user instruction, removes the health record item from the health record summary information, and the health record item is not included in the health record summary information after removal from the health record summary information (936). FIG. 8N illustrates an updated health record summary after, for example, the tap gesture illustrated in FIG. 8M is performed. As illustrated in FIG. 8N, the medication record 7014E of FIG. 8L is not displayed in the updated health record summary. This method reduces the cognitive burden on the user by allowing the user to ignore the inaccurate or incomplete health record. The method improves user efficiency by reducing the time a user spends reviewing inaccurate or incomplete records. For battery-operated computing devices, allowing a user to review their health records faster and more efficiently conserves power and extends the time between battery charges. The method also reduces the number of user errors that occur due to the user relying on incomplete or inaccurate health records.

[0276] In some embodiments, the device 100, in response to receiving the first user instruction, automatically sends a request for updated information on the health record item from the healthcare provider's computer system without further user input (938). In some embodiments, when the device 100 detects an interaction with the inaccuracy and mark affordance 7154 of FIG. 8K, it designates the health record as an inaccurate health record and automatically sends a request to the healthcare provider for the health record. By automatically notifying the healthcare provider's electronic system that the health record from the healthcare provider is inaccurate, the need for the user to manually contact the healthcare provider (using the device or other telecommunication means) to request the healthcare provider to update the inaccurate health record is reduced. This frees up the communication system, reduces network bandwidth, and saves energy. Furthermore, updated information may be received from the healthcare provider before the user has the option to update the missing information. For battery-operated computing devices, faster and more efficient updates of inaccurate health records conserve power and increase the time between battery charges.

[0277] In some embodiments, device 100 receives (940) information updating a first health record item via one or more input devices. FIG. 8I, for example, shows a user making an edit to health index record 7014D (JKL Medication). In some embodiments, device 100 receives the edit to health index record 7014D after the user performs a tap gesture shown in FIG. 8I with contact 7512 on edit affordance 7152 of FIG. 8I. In some embodiments, device 100 receives (940) a second request to display health record summary information for the first user after receiving the information updating the first health record item. In some embodiments, the user selects health record summary representation 7005 to view the health record summary after editing health index record 7014D. In other embodiments, a tap gesture with contact on edit affordance 7152 or ignore affordance 7153 of FIG. 8I is also configured as a request to display the health record summary. In some embodiments, in response to receiving a request to display health record summary information for the first user, the device 100 displays (940) an updated health record summary for the first user, including simultaneously displaying an updated first health record item and a second health record item that reflects the change to the first health record item. FIG. 8J illustrates an updated health record summary, for example, including information about a medication record 7014D that was previously missing from the health record summary illustrated in FIG. 8H. Displaying updates to a health record in a common interface with other current health records allows a user to view the user's current health record in a common interface without having to navigate between different user interfaces to obtain updates to different health records, creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to browse the user's health record faster and more efficiently conserves power and increases the time between battery charges.

[0278] It should be understood that the particular order described for the operations in Figures 9A-9D is merely exemplary, and the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, details of the processes (e.g., Figures 9A-9D) described above with respect to method 900 are also applicable in a similar manner to the methods described above and below. For example, methods 700 and 1100 optionally include one or more of the characteristics of the various methods described above with reference to method 900. For example, the method for displaying a health record summary including a current health record in another user interface and the method for displaying past records described above with reference to 900 are optionally used by method 700 to display the aggregated health record, and optionally used by method 1100 to display the health record in a health record manager. For the sake of brevity, these details will not be repeated below.

[0279] 10A-10Q illustrate an example health record manager, according to some embodiments. More specifically, FIGs. 10A-10Q illustrate displays of a health record manager that allow a user to specify and manage the status of activities associated with a particular health record. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGs. 11A-11E.

[0280] Although some of the examples below are described with reference to input on a touch screen display (combining a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from display 450, as shown in FIG. 4B. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, an audio interface, or other suitable interface. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is, optionally, a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., an enantiomeric center of the respective contact or a point associated with the respective contact), or an enantiomeric center of two or more contacts detected on touch-sensitive display system 112. However, similar operations are performed on a device having display 450 and a separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying a user interface described below, optionally with a focus selector.

[0281] In one or more embodiments of FIGS. 10A-10Q, an active health record, as used herein, is a health record designated by a user or a health care provider as a current health record and is associated with an ongoing medical condition of the user being treated by a health care provider or associated with a health condition currently being monitored by the user. For example, in one embodiment, an active health record may be the user's latest miscellaneous health records, such as blood test results from the user's most recent annual physical or other recent visit to a health care provider, and the user's current prescription records. In another embodiment, an active health record may be the latest record of a particular health condition, such as blood pressure and cholesterol levels, that the user is monitoring. In another embodiment, an active health record may be only health records associated with acute or chronic health conditions for which the user is actually being treated by a health care provider. In yet another embodiment, an active health record may be any health record that is not older than a period of time set by the user or automatically determined by the device 100. In one embodiment, all health records are designated as active when they are first received by the device 100 from a health care provider. However, in the illustrated embodiment, the user may designate any health record as active.

[0282] In one or more embodiments of FIGS. 10A-Q, an inactive health record, as used herein, is any health record other than an active health record. Optionally, a health record designated by a user as inactive is hidden in a dashboard user interface of the health record manager but displayed in other user interfaces of the health record manager that include more detailed information about the user's health record, while an active health record is displayed in the dashboard user interface of the health record manager. The status of a health record may be changed by a user from active to inactive, such as when the user's asthma symptoms are eliminated. Similarly, the status of a health record may be changed by a user from inactive to active, such as when the user's asthma symptoms reoccur. In one embodiment, in response to a change in the status of a health record from active to inactive, a notification is automatically generated by the device 100 and sent to the user's healthcare provider. Similarly, in response to a change in the status of a health record from inactive to active, a notification is automatically generated by the device and sent to the user's healthcare provider.

[0283] The health record manager also allows the user to set reminders to perform various tasks related to a particular health record. Reminders may be used, for example, to remind the user to take medications prescribed to the user at a given time, to refill medications prescribed to the user, or to track upcoming appointments with a doctor or other health care professional. Although the embodiments of Figures 10A-10Q are described in the context of managing health records, and more specifically health condition records, in some embodiments, representations of health information other than health records may be used to manage a user's health information. Similarly, other health record categories may be used to manage a user's health information, such as lab records, clinical records, or allergy records.

[0284] Similar to FIG. 8B, FIG. 10A illustrates displaying a health record summary dashboard on display 112 that includes health record summary information including multiple types of health records. The health records in the illustrated embodiment are current health records obtained from both Alpha Health Care and Beta Health Care. In the illustrated embodiment, the health indicator summary includes health indicator records 9012A-9012C (blood pressure, cholesterol level, and serum iron level, respectively), medication records 9014A-9014D (ABC drugs, DEF drugs, GHI drugs, and LMN drugs, respectively), and health condition records 9016A-9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively). FIG. 10A also illustrates displaying health indicator affordance 9011A, medication affordance 9011B, and health condition affordance 9011C. In the illustrated embodiment, health index affordance 9011A, medication affordance 9011B, and health condition affordance 9011C are selectable by the user to view a health index archive, a medication archive, and a health condition archive, respectively. In the embodiment shown in Figures 10A-10Q, the health index archive, the medication archive, and the health condition archive are each health record archives that include current and past health records belonging to the corresponding category.

[0285] In the embodiment shown in FIG. 10A, health indicator records 9012A-C are displayed in alphabetical order based on the type of health indicator record. Health indicator record 9012A includes a current measurement of the user's blood pressure, measured by Beta Health Care on November 1, 2017. Health indicator record 9012B includes a current measurement of the user's cholesterol level, measured by Alpha Health Care on October 1, 2017. Health indicator record 9012C includes a current measurement of the user's serum iron level, measured by Alpha Health Care on October 15, 2017.

[0286] In the embodiment shown in Figure 10A, the medication records 9014A-9014D are displayed in alphabetical order based on medication type. The medication health records 9014A-9014D are the user's current prescriptions for ABC, DEF, GHI, and LMN medications, respectively. Each medication health record 9014A-9014D also identifies the prescription date for the corresponding medication and the healthcare provider who prescribed the medication.

[0287] In the embodiment shown in FIG. 10A, the health condition records 9016A-D are displayed in alphabetical order based on the type of health condition. The health condition records 9016A-D each include information about the user's current health condition, including anxiety, asthma, high cholesterol, and migraines. In some embodiments, the health condition records 9016A-D also include information about medications recently prescribed for the corresponding health conditions (anxiety, asthma, high cholesterol, and migraines), even if these medications are individually identified within a medication group. FIG. 10A further illustrates detecting a tap gesture involving contact 9502 on the health condition affordance 9011C and displaying the health condition archive 9058 of FIG. 10B in response to the tap gesture.

[0288] 10B illustrates one embodiment of a health archive 9058 that includes health records of a user's health conditions and a status toggle for designating the health records as active or inactive. In the illustrated embodiment, health archive 9058 includes health records 9016A-9016D (anxiety disorder, asthma, high cholesterol, and migraines, respectively). In the illustrated embodiment, health record 9016A includes information regarding the user's anxiety disorder, medications prescribed to treat the user's anxiety disorder (DEF medications), date of first diagnosis, and the next scheduled visit to Alpha Health Care for the user's anxiety disorder. Health record 9016B includes information regarding the user's asthma, medications prescribed to treat the user's asthma (GHI medications), date of first diagnosis, and the next scheduled visit to Beta Health Care for the user's asthma. Health condition record 9016C includes information regarding the user's high cholesterol, the measured cholesterol level and the date of the cholesterol test, medications prescribed to treat the user's high cholesterol (LMN drugs), the date of initial diagnosis, and the next scheduled visit to Alpha Health Care for the user's high cholesterol. Health condition record 9016D includes information regarding the user's migraines, medications prescribed to treat the user's migraines (ABC drugs), the date of initial diagnosis, and the next scheduled visit to Alpha Health Care for the user's migraines. In other embodiments, health condition record 9016A-9016D each includes additional information regarding the corresponding health condition, such as the name of a medication previously prescribed for that health condition, the name of a doctor or other health care professional the user sees for that health condition, a list of symptoms for that health condition, and other useful information related to that health condition.

[0289] 10B, health condition records 9016A-9016D (anxiety disorder, asthma, high cholesterol, and migraines, respectively) also include status toggles 9022A-9022D, respectively, which are affordances that a user may interact with to specify the status of a particular health condition. In the illustrated embodiment, status toggles 9022A-9022D each allow a user to designate the corresponding health condition as active or inactive. In other embodiments, health condition records 9016A-9016D each also include other types of status toggles that allow a user to specify other states, such as setting a reminder to take medication for the corresponding health condition, setting a reminder to see a doctor regarding that health condition, or setting an option to receive notifications or updates regarding that health condition.

[0290] In some embodiments, the status toggles 9022A-D (for anxiety disorders, asthma, high cholesterol, and migraines, respectively) are not displayed in the health condition archive 9058. In one or more of such embodiments, the health condition archive 9058 includes a status designation affordance (not shown), which is an affordance that the user interacts with to access the status toggles 9022A-D. For example, in response to detecting a gesture to select the status designation affordance, the device 100 overlays another user interface including the status toggles 9022A-D over the portion of the user interface displayed in FIG. 10B. In other embodiments, the status toggles are displayed with the corresponding health records in a health record summary to allow the user to designate the status of a particular health condition without having to drill down into the health condition archive 9058. In yet another embodiment, the user selects an individual health condition record, such as one of health condition records 9016A-9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively), to display a respective status toggle 9022A, 9022B, 9022C, or 9022D for such health condition record. In one or more of such embodiments, after the user interacts with a status toggle displayed in the health record summary, a notification similar to the notification requesting the user to confirm the change in status of the corresponding health condition is displayed. In such an embodiment, device 100 changes the status of the health condition after detecting an input confirming the change in status of the health condition to avoid accidental input.

[0291] In the illustrated embodiment, status toggles 9022A-C (for anxiety disorder, asthma, and high cholesterol, respectively) indicate that the corresponding health condition is active. FIG. 10B further illustrates detecting a swipe gesture involving contact 9602 on status toggle 9022D (for migraine) and moving the contact from location 9602A to location 9602B to desi...

Claims

1. 1. A method comprising: In an electronic device having a display and one or more input devices, receiving, via the one or more input devices, a first request to view a health record for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider; In response to receiving the first request to view a health record for the first user, displaying on the display a representation of a plurality of health record categories, the representation of the plurality of health record categories comprising: a first representation of a first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider; a second representation of a second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider; and and receiving, after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider, a second request to view a health record for the first user via the one or more input devices; In response to receiving the second request to view a health record for the first user, displaying a representation of the plurality of health record categories on the display, the representation of the plurality of health record categories comprising: a first representation of the first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider; a second representation of the second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider; and and The method includes:

2. receiving, via the one or more input devices, a first selection of the first representation of the first category; Responsive to receiving the first selection, displaying on the display a representation of a plurality of subcategories of the first health record category, the representation of the plurality of subcategories of the first health record category comprising: a first representation of a first subcategory of the first category, where selecting the first representation of the first subcategory of the first category causes the electronic device to display on the display a plurality of health records of the first subcategory of the first category from the first healthcare provider; a second representation of a second subcategory of the first category, where selecting the second representation of the second subcategory of the first category causes the electronic device to display on the display a plurality of health records of the second subcategory of the first category from the first healthcare provider; and and The method of claim 1 further comprising:

3. The method of claim 1 or 2, wherein a first type of health record is displayed in a first color and a second type of health record is displayed in a second color different from the first color.

4. displaying a representation of the plurality of health record categories on the display; displaying on the display first content summarizing the first category and a first category information affordance associated with the first category, wherein selecting the first category information affordance causes the electronic device to display on the display further content associated with the first category not included in the first content; displaying on the display second content summarizing the second category and a second category information affordance for the second category, where selecting the second category information affordance causes the electronic device to display on the display further content associated with the second category not included in the second content; The method of claim 1 , further comprising:

5. the plurality of health records in the first category are displayed in chronological order; the plurality of health records in the second category are displayed in chronological order; 5. The method according to any one of claims 1 to 4.

6. the plurality of health records in the first category from the first healthcare provider includes a first health record in the first category from the first healthcare provider and a second health record in the first category from the first healthcare provider; the plurality of health records in the second category from the first health care provider includes a third health record in the second category from the first health care provider and a fourth health record in the second category from the first health care provider; the first health record of the first category from the first health care provider and the third health record of the second category from the first health care provider are records of a first visit to the first health care provider; the second health record of the first category from the first health care provider and the fourth health record of the second category from the first health care provider are records of a second visit to the first health care provider; The method further comprising: responsive to receiving the first request to display health records for the first user, simultaneously displaying the first health record and the third health record on the display in a first group, the first group being identified on the display by a first date of the first visit; responsive to receiving the first request to display health records for the first user, simultaneously displaying the second health record and the fourth health record on the display in a second group, the second group being identified on the display by a second date of the second visit, the first date being different from the second date; The method of claim 1 , further comprising:

7. the plurality of health records in the first category from the second health care provider includes a fifth health record in the first category from the second health care provider; the plurality of health records in the second category from the second health care provider includes a sixth health record in the second category from the second health care provider; the fifth health record in the first category from the second health care provider and the sixth health record in the second category from the second health care provider are records of a third visit to the second health care provider; The method further includes, in response to receiving the second request to display a health record for the first user, simultaneously displaying the fifth health record and the sixth health record on the display in a third group; the third group being identified on the display by a third date of the third visit to the second healthcare provider; the first group, the second group and the third group are displayed simultaneously on a display. The method according to claim 6.

8. the first health record in the first category from the first health care provider and the second health record in the first category from the first health care provider are displayed in a first color; the third health record of the second category from the first health care provider and the fourth health record of the second category from the first health care provider are displayed in a second color different from the first color. The method according to claim 6 or 7.

9. receiving updates to the first health record in the first category from the first health care provider; displaying on the display a first update badge associated with the first health record of the first group, the first update badge and the first health record being displayed simultaneously within a first area of ​​the display; The method of any one of claims 6 to 8, further comprising:

10. in response to receiving the first request to view a health record for the first user, displaying first content on the display identifying an identity and location of the first health care provider; in response to receiving the second request to view a health record for the first user, displaying second content on the display identifying an identity and location of the second health care provider; The method of claim 1 , further comprising:

11. Detecting a selection of the first representation of the first category while the electronic device is associated with the first healthcare provider; displaying on the display a first representation of a first health record of the plurality of health records in the first category from the first health care provider in response to detecting a selection of the first representation of the first category while the electronic device is associated with the first health care provider; the first representation of the first health record includes a numerical value within a numerical range; The numerical value indicates a health condition of the first user, and the numerical range indicates a normal numerical range regarding the health. And, The method of any one of claims 1 to 10, comprising:

12. The method of claim 11 , further comprising displaying the numerical value in a color selected based on the severity of the health condition of the first user.

13. 13. The method of claim 1, further comprising displaying a second representation of a second health record of the plurality of health records in the first category from the first healthcare provider, the second representation of the second health record including a graph showing the first user's status over a period of time.

14. 14. The method of claim 1, further comprising: displaying a third representation of a third health record of the first category from the first healthcare provider, the third representation of the third health record comprising an image showing a medical record of the first user.

15. receiving an update to a health record in the first health record category; displaying a second update badge associated with the first category on the display in response to receiving at least one of the first request to view the health record for the first user and the second request to view the health record for the first user after receiving the updates to the health record in the first category, wherein the second update badge and the first representation of the first category are simultaneously displayed within a first region of the display; 15. The method of claim 1, further comprising:

16. The method of claim 15 , wherein a second update badge is visually associated with the first representation of the first category.

17. 17. The method of claim 15 or 16, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider causes the device to display a representation of the health record in the first health record category on the display, and the second update badge is visually associated with the representation of the health record in the first health record category.

18. 18. The method of claim 15, wherein displaying the second update badge on the display includes displaying content of the update to the health record on the second update badge.

19. receiving a request via the one or more input devices to select the second updated badge; displaying on the display the updates to the health records in the first health record category in response to receiving the request to select the second update badge; 19. The method of any one of claims 15 to 18, further comprising:

20. Displaying the updates to the health record on the display includes simultaneously displaying the updates to the health record and a recommended affordance associated with the health record, the method comprising: receiving a request via the one or more input devices to select the recommended affordance; in response to receiving the request to select the recommended affordance, displaying a recommended action on the display, the recommended action being based on the update to the health record; and 20. The method of claim 19, further comprising:

21. 21. The method of claim 20, wherein the recommendation is a recommendation to schedule an appointment with the first healthcare provider, and displaying the recommended action includes simultaneously displaying the recommended action and a scheduling affordance.

22. receiving an update to a health record in the first health record category; in response to receiving the update to the health record; displaying a notification of the update on the display in accordance with a determination that the importance of the update is greater than a threshold; and ceasing to display the notification of the update on the display in accordance with a determination that the importance of the update is less than the threshold; and 22. The method of any one of claims 1 to 21, further comprising:

23. selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display past health records associated with the first category from the first healthcare provider, the past health records associated with the first category including the plurality of health records in the first category from the first healthcare provider; selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display past health records associated with the second category from the first healthcare provider, the past health records associated with the second category including the plurality of health records in the second category from the first healthcare provider; selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display past health records associated with the first category from the first healthcare provider and the second healthcare provider, the past health records associated with the first category including the one or more health records in the first category from the first healthcare provider and the one or more health records in the first category from the second healthcare provider; selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display past health records associated with the second category from the first healthcare provider and from the second healthcare provider, the past health records associated with the second category being one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider.

23. The method of any one of claims 1 to 22.

24. 1. An electronic device comprising: A display and one or more input devices; one or more processors; Memory, and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: receiving, via the one or more input devices, a first request to view a health record for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider; In response to receiving the first request to view a health record for the first user, displaying on the display a representation of a plurality of health record categories, the representation of the plurality of health record categories comprising: a first representation of a first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider; a second representation of a second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider; and and receiving, after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider, a second request to view a health record for the first user via the one or more input devices; In response to receiving the second request to view a health record for the first user, displaying a representation of the plurality of health record categories on the display, the representation of the plurality of health record categories comprising: a first representation of the first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider; a second representation of the second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider; and and An electronic device comprising:

25. A non-transitory computer-readable storage medium storing one or more programs that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to: receiving, via the one or more input devices, a first request to view a health record for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider; In response to receiving the first request to view a health record for the first user, displaying on the display a representation of a plurality of health record categories, the representation of the plurality of health record categories comprising: a first representation of a first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider; a second representation of a second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider; and and receiving, after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider, a second request to view a health record for the first user via the one or more input devices; In response to receiving the second request to view a health record for the first user, displaying a representation of the plurality of health record categories on the display, the representation of the plurality of health record categories comprising: a first representation of the first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider; a second representation of the second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider; and and A non-transitory computer-readable storage medium comprising instructions for executing

26. 1. An electronic device comprising: A display and one or more input devices; means for receiving, via the one or more input devices, a first request to view a health record for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider; means for displaying on the display a representation of a plurality of health record categories in response to receiving the first request to view a health record for the first user, the representation of the plurality of health record categories comprising: a first representation of a first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider; a second representation of a second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider; and and means for receiving, after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider, a second request to view a health record for the first user via the one or more input devices; means for displaying a representation of the plurality of health record categories on the display in response to receiving the second request to view a health record for the first user, the representation of the plurality of health record categories comprising: a first representation of the first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider; a second representation of the second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider; and and 1. An electronic device comprising:

27. 1. An information processing apparatus for use in an electronic device having a display and one or more input devices, comprising: means for receiving, via the one or more input devices, a first request to view a health record for a first user while the electronic device is associated with a first healthcare provider and not associated with a second healthcare provider; means for displaying on the display a representation of a plurality of health record categories in response to receiving the first request to view a health record for the first user, the representation of the plurality of health record categories comprising: a first representation of a first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the first category from the first healthcare provider; a second representation of a second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and not associated with the second healthcare provider causes the electronic device to display on the display a plurality of health records in the second category from the first healthcare provider; and and means for receiving, after displaying the representation of the plurality of health record categories and after the electronic device is associated with the second healthcare provider, a second request to view a health record for the first user via the one or more input devices; means for displaying a representation of the plurality of health record categories on the display in response to receiving the second request to view a health record for the first user, the representation of the plurality of health record categories comprising: a first representation of the first category of the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the first category from the first healthcare provider and one or more health records in the first category from the second healthcare provider; a second representation of the second category of the plurality of categories, wherein selecting the second representation of the second category while the electronic device is associated with the first healthcare provider and the second healthcare provider causes the electronic device to display on the display one or more health records in the second category from the first healthcare provider and one or more health records in the second category from the second healthcare provider; and and An information processing device comprising:

28. 1. An electronic device comprising: A display and one or more input devices; one or more processors; Memory, and one or more programs stored in the memory and 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 1 to 23.

29. 24. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to perform the method of any one of claims 1 to 23.

30. 1. An electronic device comprising: A display and one or more input devices; Means for carrying out any of the methods according to claims 1 to 23; An electronic device comprising:

31. 1. An information processing apparatus for use in an electronic device having a display and one or more input devices, comprising:

24. A method for performing a method according to claim 1, Information processing device.

32. 1. A method comprising: In an electronic device having a display and one or more input devices, receiving, via the one or more input devices, a request to display health record summary information for a first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type; In response to receiving the request, displaying health record summary information regarding the first user on the display; a first health record item of the first type for a first date, wherein the health record summary information does not include a plurality of health record items of the first type for a date prior to the first date; a second health record item of the second type for a second date different from the first date, the health record summary information not including a plurality of health record items of the second type for a date prior to the second date; and displaying multiple health record items simultaneously, including The method includes:

33. 33. The method of claim 32, wherein the health data for the first user includes a plurality of health record items of a third type different from the first type and the second type, and displaying health record summary information further includes simultaneously displaying the first health record item, the second health record item, and a third health record item of the third type for a third date, and wherein health record summary information does not include a plurality of health record items of the third type for dates prior to the third date.

34. 34. The method of claim 32 or 33, wherein the health data includes health data associated with multiple healthcare providers of the first user, the first health record item being associated with a first healthcare provider of the multiple healthcare providers and the second health record item being associated with a second healthcare provider of the multiple providers.

35. 35. The method of any one of claims 32 to 34, wherein the plurality of health record items includes a fourth health record item of a fourth type on a fourth date, the first health record item and the fourth health record item are associated with a first healthcare provider, and the first date and the fourth date are dates of first and second visits to the first healthcare provider.

36. after displaying the health record including the first health record item and the second health record item; receiving a third health record item of the first type for a third date that is later than the first date; receiving, after receiving the third health record item, a second request via the one or more input devices to display health record summary information for the first user; displaying updated health record summary information for the first user on the display in response to receiving the second request, the display including simultaneously displaying the second health record item and the third health record item without displaying the first health record item; 36. The method of any one of claims 32 to 35, further comprising:

37. after displaying the health record including the first health record item and the second health record item; receiving a new health record entry of the health data for the first user, the new health record entry having a date that is later than the first date and the second date; receiving, after receiving the new health record entry, a third request via the one or more input devices to display health record summary information for the first user; displaying updated health record summary information for the first user on the display in response to receiving the third request, the display including simultaneously displaying the first health record item, the second health record item, and the new health record item; 37. The method of any one of claims 32 to 36, further comprising:

38. while displaying health record summary information regarding the first user on the display; receiving, via the one or more input devices, a first request to view the plurality of health record items of the first type not displayed in the overview; displaying on the display a plurality of health record items of the first type dated before the first date in response to receiving the first request to display the plurality of health record items of the first type not displayed in the summary; and 38. The method of any one of claims 32 to 37, further comprising:

39. displaying a health record archive for the first user on the display in response to receiving the first request to display the plurality of health record items of the first type not displayed in the overview, further comprising simultaneously displaying a most recently dated health record item of the first type and one or more of the plurality of health record items of the first type dated prior to the first date.

39. The method of claim 38.

40. displaying a fourth health record item of the first type in a health record archive on a display in response to receiving the first request to display the plurality of health record items of the first type not displayed in the overview, the fourth health record item including a representation of a health metric measured on a fourth date prior to the first date.

40. The method of claim 39.

41. after displaying the health record summary information including the first health record and the second health record; receiving a third health record item of a third type for a third date that is later than the first date and the second date; updating the health record summary information to include the third health record item in response to a request to view the health record summary information, wherein the first health record item, the second health record item, and the third health record item are simultaneously displayed within the health record summary information; 41. The method of any one of claims 32 to 40, further comprising:

42. 42. The method of any one of claims 32 to 41, wherein the first health record entry includes a representation of a severity of the first user's condition.

43. 43. The method of any one of claims 32 to 42, wherein the first health record entry includes a representation of the first user's condition over a period of time.

44. and in response to the request to display health record summary information, pursuant to a determination that a health record entry of the health data for the first user is incomplete, displaying an incomplete record affordance within the health record summary information.

44. The method of any one of claims 32 to 43.

45. receiving a user verification, via the one or more input devices, of accuracy of a health record item of the plurality of health record items displayed in the health record summary information; in response to receiving the user verification of the accuracy of the health record item, providing the user verification to a health care provider associated with the health record item; 45. The method of any one of claims 32 to 44, further comprising:

46. receiving a first user indication via the one or more input devices indicating that a health record item of the plurality of health record items included in the health record summary information is inaccurate; in response to receiving the first user instruction, removing the health record item from the health record summary information, wherein the health record item is not included in the health record summary information after removal from the health record summary information; and 46. ​​The method of any one of claims 32 to 45, further comprising:

47. 47. The method of claim 46, comprising, in response to receiving the first user instruction, automatically sending a request for updated information regarding the health record item from a health care provider computer system without further user input.

48. receiving information via the one or more input devices to update the first health record item; receiving a second request to display health record summary information for the first user after receiving the information updating the first health record entry; displaying an updated health record summary for the first user in response to receiving the request to display health record summary information for the first user, the updated first health record entry reflecting changes to the first health record entry and the second health record entry simultaneously; 48. The method of any one of claims 32 to 47, further comprising:

49. 1. An electronic device comprising: A display and one or more input devices; one or more processors; Memory, and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: receiving, via the one or more input devices, a request to display health record summary information for a first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type; In response to receiving the request, displaying health record summary information regarding the first user on the display; a first health record item of the first type for a first date, wherein the health record summary information does not include a plurality of health record items of the first type for a date prior to the first date; a second health record item of the second type for a second date different from the first date, the health record summary information not including a plurality of health record items of the second type for a date prior to the second date; and displaying multiple health record items simultaneously, including An electronic device that contains instructions for executing the

50. A non-transitory computer-readable storage medium storing one or more programs that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to: receiving, via the one or more input devices, a request to display health record summary information for a first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type; In response to receiving the request, displaying health record summary information regarding the first user on the display; a first health record item of the first type for a first date, wherein the health record summary information does not include a plurality of health record items of the first type for a date prior to the first date; a second health record item of the second type for a second date different from the first date, the health record summary information not including a plurality of health record items of the second type for a date prior to the second date; and displaying multiple health record items simultaneously, including An electronic device that includes instructions to execute the following:

51. 1. An electronic device comprising: A display and one or more input devices; means for receiving, via the one or more input devices, a request to display health record summary information for the first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type; means for displaying health record summary information regarding the first user on the display in response to receiving the request, said displaying comprising: a first health record item of the first type for a first date, wherein the health record summary information does not include a plurality of health record items of the first type for a date prior to the first date; a second health record item of the second type for a second date different from the first date, the health record summary information not including a plurality of health record items of the second type for a date prior to the second date; and displaying a plurality of health record items simultaneously, An electronic device comprising:

52. 1. An information processing apparatus for use in an electronic device having a display and one or more input devices, comprising: means for receiving, via the one or more input devices, a request to display health record summary information for the first user while the electronic device is associated with health data for the first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type; means for displaying health record summary information regarding the first user on the display in response to receiving the request, said displaying comprising: a first health record item of the first type for a first date, wherein the health record summary information does not include a plurality of health record items of the first type for a date prior to the first date; a second health record item of the second type for a second date different from the first date, the health record summary information not including a plurality of health record items of the second type for a date prior to the second date; and displaying a plurality of health record items simultaneously, An electronic device comprising:

53. 1. An electronic device comprising: A display and one or more input devices; one or more processors; Memory, and one or more programs stored in the memory and 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 32 to 48.

54. 50. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to perform the method of any one of claims 32 to 48.

55. 1. An electronic device comprising: A display and one or more input devices; Means for carrying out any of the methods according to claims 32 to 48; An electronic device comprising:

56. 1. An information processing apparatus for use in an electronic device having a display and one or more input devices, comprising:

49. A method for performing a method according to any one of claims 32 to 48, Information processing device.

57. 1. A method comprising: In an electronic device having a display and one or more input devices, displaying a first representation of a first ongoing health condition of a plurality of ongoing health conditions of the user as indicated by health record information from one or more healthcare providers of the user while the electronic device is associated with the one or more healthcare providers of the user, the plurality of ongoing health conditions including a second ongoing health condition and a third ongoing health condition; receiving, while displaying the first representation of the first ongoing health condition, a request via the one or more input devices to mark the first ongoing health condition as inactive for the user; receiving, after receiving the request to mark the first ongoing health condition as inactive, a request to display an ongoing health condition for the user via the one or more input devices; in response to receiving the request to display an ongoing health condition for the user, simultaneously displaying on the display a second representation of the second ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers and a third representation of the third ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers, without displaying the first representation of the first ongoing health condition of the user as an active health condition; The method includes:

58. and in response to receiving the request to mark the first ongoing health condition as inactive, displaying a visual indication on the display that the first ongoing health condition is inactive.

58. The method of claim 57.

59. in response to receiving the request to display the plurality of ongoing health conditions of the user; a visual indication that the first ongoing health state is inactive; and the second ongoing health status of the user; and the third ongoing health status of the user; and 59. The method of claim 57 or 58, further comprising simultaneously displaying on the display.

60. receiving, after receiving the request to mark the first ongoing health condition as inactive, a second request to mark the first ongoing health condition as active via the one or more input devices; in response to receiving the second request to mark the first health condition as active, updating the first representation of the first ongoing health condition to indicate that the first ongoing health condition is active; and receiving a second request to display the plurality of ongoing health conditions for the user after updating the first representation of the first ongoing health condition as active; in response to receiving the second request to display the plurality of ongoing health conditions for the user, simultaneously displaying on the display the representation of the updated first ongoing health condition, the second representation of the second ongoing health condition, and the third representation of the third ongoing health condition; 60. The method of any one of claims 57 to 59, further comprising:

61. and in response to receiving the request to mark the first ongoing health condition as inactive, transmitting information indicating an inactive status of the first ongoing health condition to a computer system associated with a health care provider associated with the first ongoing health condition.

61. The method of any one of claims 57 to 60.

62. receiving, after receiving an update to the first ongoing health status, a third request via the one or more input devices to display an ongoing health status for the user; and in response to receiving the third request to display the plurality of ongoing health conditions for the user; the updated first ongoing health state representation; and the second representation of the second ongoing health condition; and the third representation of the third ongoing health condition; and simultaneously displaying on said display; 62. The method of any one of claims 57 to 61, further comprising:

63. and in response to receiving the update to the first ongoing health condition, marking the first ongoing health condition as an active health condition.

63. The method of claim 62.

64. and in response to receiving the update for the first ongoing health condition, transmitting the update to a computer system associated with a health care provider associated with the first ongoing health condition.

64. The method of claim 62 or 63.

65. and in response to determining a set of dates associated with the second ongoing health condition, displaying on the display a notification regarding the second ongoing health condition on each date of the set of dates.

65. The method of any one of claims 57 to 64.

66. 66. The method of claim 65, wherein the set of dates associated with the second ongoing health condition includes a first date, the first date being a date on which a prescription for the second ongoing health condition is scheduled to be refilled, and the notification includes a reminder to refill the prescription.

67. 67. The method of claim 65 or 66, further comprising predicting a date when a remaining amount of a prescription drug for the second ongoing health condition will be below a threshold, wherein the set of dates associated with the second ongoing health condition includes a second date, the second date being the date when the prescription drug is predicted to be below a threshold, and the notification includes a reminder to refill the prescription drug.

68. 68. The method of claim 67, further comprising requesting a refill of the prescription from a health care provider of the one or more health care providers on the second date, the health care provider being associated with the second ongoing health condition.

69. receiving an update to a remaining amount of a prescription for the second ongoing health condition via the one or more input devices; and displaying a notification to refill the prescription on the display in response to a determination that the remaining amount of the prescription is less than a threshold value; 69. The method of any one of claims 65 to 68, further comprising:

70. 70. The method of any one of claims 65 to 69, wherein the set of dates associated with the second ongoing health condition includes a third date, the third date being a date on which a visit to a health care provider of the one or more health care providers is scheduled, the health care provider being associated with the second ongoing health condition.

71. displaying a first reminder affordance on the display associated with the second ongoing health condition; and receiving, while displaying the first reminder affordance, a request to select the first reminder affordance via the one or more input devices; 71. The method of any one of claims 65 to 70, further comprising: displaying a first reminder affordance on the display associated with the second ongoing health condition, and receiving, while displaying the first reminder affordance, a request to select the first reminder affordance via the one or more input devices; 71. The method of any one of claims 65 to 70, further comprising:

72. pursuant to determining that the reminder associated with the second ongoing health condition is also associated with a time of day; displaying on the display a notification regarding the reminder associated with the second ongoing health condition at the time; and 72. The method of any one of claims 67 to 71, further comprising:

73. 73. The method of claim 72, wherein the reminder associated with the second ongoing health condition is a periodic reminder associated with a prescribed time interval for the user to take a prescribed medication for the second ongoing health condition, and the notification is a reminder to take a prescribed amount of the prescription medication.

74. the notification includes a second reminder affordance associated with the reminder, and the method further comprises: receiving a request via the one or more input devices to select the second reminder affordance; responsive to receiving the request to select the second reminder affordance, calculating a remaining amount of the prescription; displaying a second notification on the display regarding the second ongoing health condition in accordance with a determination that the remaining amount of the prescription is less than a threshold, the second notification being a reminder to refill the prescription; 74. The method of claim 73, further comprising:

75. the user is a patient and the electronic device is a patient device; displaying the first representation of the first ongoing health condition on the display of the patient device while the patient device is associated with one or more healthcare providers of the patient; receiving a request from the patient via the one or more input devices to mark the first ongoing health condition as inactive for the patient while displaying the representation of the first ongoing health condition on the patient device; receiving a request from the patient via the one or more input devices to display an ongoing health condition for the patient after receiving the request from the patient to mark the first ongoing health condition as inactive; in response to receiving the request from the patient to display an ongoing health condition for the patient, simultaneously displaying the second representation of the second ongoing health condition and the third representation of the third ongoing health condition on the display of the patient device without displaying the representation of the first ongoing health condition.

75. The method of any one of claims 57 to 74.

76. 1. An electronic device comprising: A display and one or more input devices; one or more processors; Memory, and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: displaying a first representation of a first health condition of a plurality of ongoing health conditions of the user as indicated by health record information from one or more health care providers of the user while the electronic device is associated with the one or more health care providers of the user, the plurality of ongoing health conditions including a second ongoing health condition and a third ongoing health condition; receiving, while displaying the first representation of the first ongoing health condition, a request via the one or more input devices to mark the first ongoing health condition as inactive for the user; receiving, after receiving the request to mark the first ongoing health condition as inactive, a request to display an ongoing health condition for the user via the one or more input devices; in response to receiving the request to display an ongoing health condition for the user, simultaneously displaying on the display a second representation of the second ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers and a third representation of the third ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers, without displaying as active the first representation of the first ongoing health condition of the user; containing instructions for carrying out Electronic devices.

77. A non-transitory computer-readable storage medium storing one or more programs that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to: displaying a first representation of a first health condition of a plurality of ongoing health conditions of the user as indicated by health record information from one or more health care providers of the user while the electronic device is associated with the one or more health care providers of the user, the plurality of ongoing health conditions including a second ongoing health condition and a third ongoing health condition; receiving, while displaying the first representation of the first ongoing health condition, a request via the one or more input devices to mark the first ongoing health condition as inactive for the user; receiving, after receiving the request to mark the first ongoing health condition as inactive, a request to display an ongoing health condition for the user via the one or more input devices; in response to receiving the request to display an ongoing health condition for the user, simultaneously displaying on the display a second representation of the second ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers and a third representation of the third ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers, without displaying as active the first representation of the first ongoing health condition of the user; A non-transitory computer-readable storage medium comprising instructions for executing

78. 1. An electronic device comprising: A display and one or more input devices; means for displaying a first representation of a first health condition of a plurality of ongoing health conditions of the user as indicated by health record information from one or more health care providers while the electronic device is associated with one or more health care providers of the user, the plurality of ongoing health conditions including a second ongoing health condition and a third ongoing health condition; means for receiving, while displaying the first representation of the first ongoing health condition, a request to mark the first ongoing health condition as inactive for the user via the one or more input devices; means for receiving, after receiving the request to mark the first ongoing health condition as inactive, a request to display an ongoing health condition for the user via the one or more input devices; means for, in response to receiving the request to display an ongoing health condition for the user, simultaneously displaying on the display a second representation of the second ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers and a third representation of the third ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers, without displaying as active the first representation of the first ongoing health condition of the user; An electronic device comprising:

79. 1. An information processing apparatus for use in an electronic device having a display and one or more input devices, comprising: means for displaying a first representation of a first health condition of a plurality of ongoing health conditions of the user as indicated by health record information from one or more health care providers while the electronic device is associated with one or more health care providers of the user, the plurality of ongoing health conditions including a second ongoing health condition and a third ongoing health condition; means for receiving, while displaying the first representation of the first ongoing health condition, a request to mark the first ongoing health condition as inactive for the user via the one or more input devices; means for receiving, after receiving the request to mark the first ongoing health condition as inactive, a request to display an ongoing health condition for the user via the one or more input devices; means for, in response to receiving the request to display an ongoing health condition for the user, simultaneously displaying on the display a second representation of the second ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers and a third representation of the third ongoing health condition of the user from the plurality of ongoing health conditions indicated by health record information from the one or more healthcare providers, without displaying as active the first representation of the first ongoing health condition of the user; An information processing device comprising:

80. 1. An electronic device comprising: A display and one or more input devices; one or more processors; Memory, and one or more programs stored in the memory and 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 57 to 75.

81. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to perform the method of any one of claims 57 to 75.

82. 1. An electronic device comprising: A display and one or more input devices; Means for carrying out any of the methods according to claims 57 to 75; An electronic device comprising:

83. 1. An information processing apparatus for use in an electronic device having a display and one or more input devices, comprising:

76. A method for performing a method according to any one of claims 57 to 75, Information processing device.

Images