System and method for displaying aggregated health records

Abstract

To provide a faster and more efficient method and interface for displaying aggregated health records on electronic devices. [Solution] The method includes: receiving a request to display health records about a user while the device is associated with one healthcare provider; displaying health record categories in response to receiving the first request; selecting a category while the device is associated with a healthcare provider and causing the device to display health records of that category from the healthcare provider; receiving a second request to display the user's health records while the device is associated with two healthcare providers; selecting a category while the device is associated with both healthcare providers and causing the device to display health records of the selected category from both healthcare providers.

Description

Technical Field

[0001] This disclosure relates generally to computer user interfaces and more specifically to techniques for displaying aggregated health records.

Background Art

[0002] Healthcare providers may provide patients with paper copies of health records. Paper copies of health records are prone to being lost and deteriorating. Some digitized healthcare providers provide patients with electronic copies of health records. However, current methods for displaying health records on electronic devices are old, cumbersome, and inefficient. For example, some existing methods use complex and time-consuming user interfaces where, even with multiple key presses or entries, only a limited amount of health records may be provided to the user. In addition, those methods take more time than necessary, thereby wasting energy. The latter problem is particularly significant in battery-operated devices.

[0003] It should be well understood that the use of personally identifiable information should comply with privacy policies and practices that meet or exceed industry or government requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize the risk of unintended or unauthorized access or use, and the nature of the permitted use should be clearly disclosed to the user.

Summary of the Invention

[0004] Therefore, this technology provides electronic devices with a faster and more efficient method and interface for displaying aggregated health records. Such a method and interface optionally complements or replaces other methods for displaying health records. Such a method and interface reduces the number, extent, and / or type of user input, alleviates the cognitive burden on the user, and generates a more efficient human-machine interface. In the case of battery-operated computing devices, such a method and interface conserves power and extends the interval between battery charges.

[0005] The above-mentioned defects 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 this disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or 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 “touchscreen” or “touchscreen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger touch and gestures on the touch-sensitive surface. In some embodiments, the functions are optional and include image editing, drawing, presentation, word processing, spreadsheet creation, gameplay, making phone calls, video conferencing, sending emails, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note-taking, and / or digital video playback. The executable instructions for performing those functions are optional and may be contained in a non-temporary computer-readable storage medium or in other computer program products configured to be executed by one or more processors.

[0006] According to some embodiments, the method is performed on an electronic device comprising a display and one or more input devices. The method includes receiving a first request via one or more input devices to display health records relating to a first user while the electronic device is associated with a first healthcare provider and not with a second healthcare provider. The method also includes displaying representations of a plurality of health record categories on the display in response to receiving the first request to display health records relating to a first user. The representations of the plurality of health record categories include a first representation of a first category among the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with a first healthcare provider and not with a second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display. The representation of multiple health record categories also includes a second representation of a second category among the multiple categories, wherein the electronic device is associated with a first healthcare provider and, while not associated with a second healthcare provider, the selection of the second representation of the second category causes the electronic device to display multiple health records of the second category from the first healthcare provider on the display. The method also includes, after displaying the representation of multiple health record categories and after the electronic device has been associated with a second healthcare provider, receiving a second request via one or more input devices to display health records for a first user. The method also includes, in response to receiving a second request to display health records for a first user, displaying the representation of multiple health record categories on the display. A representation of multiple health record categories includes a first representation of a first category among multiple categories, wherein selecting the first representation of the first category while the electronic device is associated with a first healthcare provider and a second healthcare provider causes the electronic device to display on its display 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.The representation of multiple health record categories also includes a second representation of a second category among the multiple categories, wherein selecting the second representation of the second category while the electronic device is associated with a first healthcare provider and a second healthcare provider causes the electronic device to display on its display 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.

[0007] According to some embodiments, a non-temporary computer-readable storage medium stores one or more programs, and when one or more programs are executed by one or more processors of an electronic device having a display and one or more input devices, the electronic device includes instructions that cause the electronic device to receive a first request via one or more input devices to display health records relating to a first user while the electronic device is associated with a first healthcare provider and not with a second healthcare provider. The instructions also cause the electronic device to display representations of a plurality of health record categories on the display in response to receiving the first request to display health records relating to a first user. The representations of a plurality of health record categories include a first representation of a first category among the plurality of categories, wherein selecting the first representation of the first category while the electronic device is associated with a first healthcare provider and not with a second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display. The representation of multiple health record categories also includes a second representation of a second category among the multiple categories, wherein the electronic device is associated with a first healthcare provider and, while not associated with a second healthcare provider, the selection of the second representation of the second category causes the electronic device to display multiple health records of the second category from the first healthcare provider on its display. The instruction also, when executed, causes the electronic device to receive a second request via one or more input devices to display health records for a first user after displaying the representation of multiple health record categories and after the electronic device has been associated with a second healthcare provider. The instruction also causes the device to display the representation of multiple health record categories on its display in response to receiving the second request to display health records for a first user.A representation of multiple health record categories includes a first representation of a first category among the multiple categories, wherein selecting the first representation of the first category while the electronic device is associated with a first healthcare provider and a second healthcare provider causes the electronic device to display 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 on the display. A representation of multiple health record categories also includes a second representation of a second category among the multiple categories, wherein selecting the second representation of the second category while the electronic device is associated with a first healthcare provider and a second healthcare provider causes the electronic device to display 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 on the display.

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

[0009] According to some embodiments, a non-temporary computer-readable storage medium stores one or more programs, and when one or more programs are executed by one or more processors of an electronic device having a display and one or more input devices, the electronic device includes instructions causing the electronic device to receive a request via one or more input devices to display health record summary information about a first user while the electronic device is associated with health data about a first user, which 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. The instructions also cause the device to display the health record summary information about the first user on the display in response to the receipt of the request, including displaying the plurality of health record items simultaneously. The plurality of health record items include a first health record item of a first type for a first date, wherein the health record summary information does not include a plurality of health record items of a first type for a date earlier than the first date. The plurality of health record items also include a second health record item of a second type for a second date different from the first date, wherein the health record summary information does not include a plurality of health record items of a second type for a date earlier than the second date.

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

[0011] According to some embodiments, a non-temporary computer-readable storage medium stores one or more programs, and when one or more programs are executed by one or more processors of an electronic device having a display and one or more input devices, the electronic device receives a request via one or more input devices to mark a first ongoing health state as inactive for this user while the electronic device is displaying a first representation of a first ongoing health state. The instruction also causes the electronic device to receive a request via one or more input devices to display an ongoing health state for the user after receiving the request to mark the first ongoing health state as inactive. The instruction also causes the electronic device to simultaneously display on the display, in response to receiving the request to display an ongoing health state for the user, a second representation of a second ongoing health state of the user from a plurality of ongoing health states indicated by health record information from one or more healthcare providers, and a third representation of a third ongoing health state of the user from a plurality of ongoing health states indicated by health record information from one or more healthcare providers, without displaying the first representation of the user's first ongoing health state as an active health state.

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

[0013] The executable instructions that perform these functions are contained in a non-temporary computer-readable storage medium or other computer program product configured to be executed by one or more processors, at the discretion of the user.

[0014] Therefore, devices will be provided with faster and 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 can complement or replace other methods for displaying aggregated health records. [Brief explanation of the drawing]

[0015] To better understand the various embodiments described, the following “Modes for Carrying Out the Invention” should be referenced in conjunction with the following drawings, and similar reference numbers throughout the following drawings refer to the corresponding parts.

[0016] [Figure 1A] This is a block diagram showing a portable multifunctional device having a touch-sensitive display according to several embodiments.

[0017] [Figure 1B] This is a block diagram showing exemplary components for event handling according to several embodiments.

[0018] [Figure 2] This shows a portable multifunctional device having a touchscreen according to several embodiments.

[0019] [Figure 3] This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to several embodiments.

[0020] [Figure 4A] This shows an exemplary user interface for an application menu on a portable multifunction device according to several embodiments.

[0021] [Figure 4B] This document illustrates an exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display, according to several embodiments.

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

[0023] [Figure 5B] It is a block diagram showing a personal electronic device according to some embodiments.

[0024] [Figure 6A] Shows an exemplary user interface for displaying an aggregated health record according to some embodiments. [Figure 6B] Shows an exemplary user interface for displaying an aggregated health record according to some embodiments. [Figure 6B-1] Shows an exemplary user interface for displaying an aggregated health record according to some embodiments. [Figure 6C] Shows an exemplary user interface for displaying an aggregated health record according to some embodiments. [Figure 6D] Shows an exemplary user interface for displaying an aggregated health record according to some embodiments. [Figure 6E] Shows an exemplary user interface for displaying an aggregated health record according to some embodiments. <00所求的翻译结果为:

[0022] [Figure 5A] 展示了根据一些实施方式的个人电子设备。 ;

[0023] [Figure 5B] 是展示根据一些实施方式的个人电子设备的框图。

[0024] [Figure 6A] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6B] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6B-1] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6C] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6D] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6E] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6E-1] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6F] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6G] 展示了用于显示根据一些实施方式的汇总健康记录의示例性用户界面。 [Figure 6H] 展示了用于显示根据一些实施方式的汇总健康记录的示例性用户界面。 [Figure 6H-1]This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6I] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6J] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6J-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6K] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6K-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6L] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6L-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6M] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6M-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6N] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6O] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6O-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6P] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6P-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6Q] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments. [Figure 6Q-1] This document illustrates an exemplary user interface for displaying aggregated health records according to several embodiments.

[0025] [Figure 7A] This flowchart illustrates a process for displaying aggregated health records according to several embodiments. [Figure 7B] This flowchart illustrates a process for displaying aggregated health records according to several embodiments. [Figure 7C] This flowchart illustrates a process for displaying aggregated health records according to several embodiments. [Figure 7D] This flowchart illustrates a process for displaying aggregated health records according to several embodiments. [Figure 7E] This flowchart illustrates a process for displaying aggregated health records according to several embodiments. [Figure 7F] This flowchart illustrates a process for displaying aggregated health records according to several embodiments.

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

[0027] [Figure 9A] This is a flowchart of the process for displaying a dashboard user interface with aggregated health records according to several embodiments. [Figure 9B] This is a flowchart of the process for displaying a dashboard user interface with aggregated health records according to several embodiments. [Figure 9C] This is a flowchart of the process for displaying a dashboard user interface with aggregated health records according to several embodiments. [Figure 9D] This is a flowchart of the process for displaying a dashboard user interface with aggregated health records according to several embodiments.

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

[0029] [Figure 11A] This flowchart illustrates a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to several embodiments. [Figure 11B] This flowchart illustrates a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to several embodiments. [Figure 11C] This flowchart illustrates a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to several embodiments. [Figure 11D] This flowchart illustrates a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to several embodiments. [Figure 11E] This flowchart illustrates a method for displaying a health record manager that allows a user to specify the status of a particular health record, according to several embodiments. [Modes for carrying out the invention]

[0030] The following description includes exemplary methods, parameters, etc. However, it should be noted that such descriptions are not intended to limit the scope of this disclosure, but rather are provided as descriptions of exemplary embodiments.

[0031] There is a need for an efficient method and electronic device that provides an interface for displaying aggregated health records within a common interface. Using such a common interface avoids the risk that a user may only be able to view a portion of their health records related to a particular concern or question. The use of such a common interface also improves user efficiency when viewing their health records by reducing the need to navigate multiple user interfaces to view the health records displayed within the interface. Such technology can reduce the cognitive burden on users accessing their health records, thereby improving productivity. Furthermore, such techniques can reduce processor and battery power that would normally be wasted on redundant user input.

[0032] Figures 1A-1B, 2, 3, 4A-4B, and 5A-5B below describe exemplary devices that perform techniques for displaying aggregated health records. Figures 6A-6Q-1 show exemplary user interfaces for displaying aggregated health records. Figures 7A-7F are flowcharts showing methods for displaying aggregated health records according to several embodiments. The user interfaces in Figures 6A-6Q-1 are used to illustrate processes described later, including the processes in Figures 7A-7F. Figures 8A-8N show exemplary dashboard user interfaces for displaying aggregated health records. Figures 9A-9D are flowcharts showing methods for displaying dashboard user interfaces with aggregated health records according to several embodiments. The user interfaces in Figures 8A-8N are used to illustrate processes described later, including the processes in Figures 9A-9D. Figures 10A-10Q show exemplary user interfaces for displaying a health record manager that allows a user to specify the status of a particular health record. Figures 11A to 11E are flowcharts illustrating methods for displaying a health record manager that allows a user to specify the status of a particular health record, according to several embodiments. The user interfaces in Figures 10A to 10Q are used to illustrate the processes described later, including the processes in Figures 11A to 11E.

[0033] In the following description, terms such as “first,” “second,” etc., are used to describe various elements, but these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the various embodiments described, the first touch may be called the second touch, and similarly, the second touch may be called the first touch. Both the first touch and the second touch are touches, but they are not the same touch.

[0034] The terminology used in the descriptions of the various embodiments described herein is intended solely to describe specific embodiments and is not intended to be limiting. In the descriptions of the various embodiments and the accompanying claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless otherwise explicitly stated in the context. Furthermore, as used herein, the term “and / or” should be understood to refer to and include any one or more of the related enumerated items and all possible combinations thereof. The term “if” is further interpreted, optionally, as in the context, to mean “when” or “upon,” or “in response to determining” or “in response to detecting.”

[0035] The phrase "if" can be interpreted, at will, depending on the context, as "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" can be interpreted, at will, depending on the context, as "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, which also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc., Cupertino, California. 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 a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0037] The following discussion describes electronic devices including displays and touch-sensitive surfaces. However, it should be understood that electronic devices optionally include one or more other physical user interface devices such as physical keyboards, mice, and / or joysticks.

[0038] The device typically supports a variety of applications, including drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0039] Various applications running on this device optionally utilize at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or modified on an application-by-application basis and / or within each application. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally supports a variety of applications with intuitive and transparent user interfaces for the user.

[0040] Here, we turn our attention to embodiments of portable devices equipped with touch-sensitive displays. Figure 1A is a block diagram of a portable multifunction device 100 having a touch-sensitive display system 112 according to several embodiments. The touch-sensitive display 112 may be conveniently referred to as a “touchscreen” and may 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), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 (e.g., touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100) that detect the intensity of contact on Device 100. Device 100 optionally includes one or more tactile output generators 167 that generate tactile outputs on Device 100 (for example, on touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100 or the touchpad 355 of Device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0041] In this specification and in the claims, the term “strength” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact on the touch-sensitive surface (e.g., finger contact), or a proxy for the force or pressure of contact on the touch-sensitive surface. The strength of contact has a range of values, including at least four distinct values, and more typically, including several hundred (e.g., at least 256) distinct values. The strength of contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the 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., weighted average) to determine the estimated force of contact. Similarly, the 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-sensing surface, the capacitance and / or change in the touch-sensing surface adjacent to the contact, and / or the resistance and / or change in the touch-sensing surface adjacent to the contact may optionally be used as a substitute for the force or pressure of the contact on the touch-sensing surface. In some implementations, the substitute measurement for the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some implementations, the substitute measurement for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of contact as an attribute of user input, it becomes possible to enable user access to additional device functions that would normally be inaccessible to the user on a reduced-size device where the 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 control unit such as a knob or button) is limited.

[0042] As used herein and in the claims, the term “tactile output” means a physical displacement of the device relative to its previous position, 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, which will be detected by the user through the user’s sense of touch. For example, in a situation where the device or a component of the device is in contact with the touch-sensitive surface of the user (e.g., the user’s fingers, palm, or other part of their 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 the physical properties of the device or a component of the device. For example, the movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user’s action. As another example, movement of a touch-sensitive surface may be interpreted or perceived by the user as "roughness" of that surface, even if there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch depend on the user's personal sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception of a typical (or average) user.

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

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

[0046] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 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 circuit 108 optionally includes well-known circuits for performing these functions, which include, but are not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, subscriber identity module (SIM) cards, and memory. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as with other devices. The RF circuit 108 optionally includes a well-known circuit for detecting a near-field communication (NFC) field by a short-range communication radio, etc. Wireless communication is optionally not limited to this, but includes 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-HSPADA), and long-term evolution.Bluetooth evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth®, Bluetooth Low Energy (BTLE®), Wireless Fidelity (Wi-Fi®) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX®, Email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), Instant messaging (e.g., Extensible Messaging and Presence Protocol) Using any of several communication standards, protocols, and technologies, including the XMPP protocol, the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including a communication protocol not yet developed as of the filing date of this specification.

[0047] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts this audio data into an electrical signal, and transmits this electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. 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 this audio data to the peripheral interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or RF circuit 108 by the peripheral interface 118. In some embodiments, the audio circuit 110 further includes a headset jack (e.g., 212 in Figure 2). The headset jack provides an interface between the audio circuit 110 and detachable audio input / output peripherals such as output-only headphones or headsets that have both output (e.g., headphones for one or both ears) and input (e.g., a microphone).

[0048] The I / O subsystem 106 connects input / output peripherals on device 100, such as the touchscreen 112 and other input control devices 116, to the peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical 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. One or more input controllers 160 receive electrical signals from / transmit electrical signals to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally connected to (or not connected to) one or more of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., 208 in Figure 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206 in Figure 2).

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

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

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

[0052] The touchscreen 112 optionally uses LCD (liquid crystal display) technology, LPD (polymer light-emitting display) technology, or LED (light-emitting diode) technology, but other display technologies may also be used in other embodiments. The touchscreen 112 and the display controller 156 optionally, but not limited to, use any of several currently known or future-developed touch sensing technologies, including 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 the touchscreen 112, to detect contact and any movement or interruption thereof. In exemplary embodiments, projected mutual capacitive sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

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

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

[0055] The touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user optionally touches the touchscreen 112 using any suitable object or attachment, such as a stylus or finger. In some embodiments, the user interface is designed to primarily handle finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​the finger on the touchscreen. In some embodiments, the device translates coarse finger input into a precise pointer / cursor position or command to perform an action desired by the user.

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

[0057] Device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within the portable device.

[0058] The device 100 also optionally includes one or more optical sensors 164. Figure 1A shows optical sensors coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensors 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The optical sensors 164 receive light from the environment projected through one or more lenses and convert that light into data representing an image. The optical sensors 164 work in conjunction with an imaging module 143 (also called a camera module) to optionally capture still images or video. In some embodiments, the optical sensors are located on the back of the device 100, opposite to the touchscreen display 112 on the front of the device, so that the touchscreen display can be effectively used as a viewfinder for acquiring still images and / or video images. In some embodiments, the light sensor is located on the front of the device, so that the user's image is optionally acquired for video conferencing, and the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (for example, by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both video conferencing and acquiring still and / or video images, together with the touchscreen display.

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

[0060] The device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows a proximity sensor 166 coupled to a peripheral interface 118. Alternatively, the proximity sensor 166 is optionally coupled to an input controller 160 in the I / O subsystem 106. The proximity sensor 166 may optionally function as described in U.S. Patent Applications 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 as a whole. In some embodiments, the proximity sensor turns off and disables the touchscreen 112 when the multifunction device is positioned near the user's ear (for example, when the user is making a phone call).

[0061] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component, and / or electromechanical devices that convert energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). The contact intensity sensor 165 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on device 100 that can be sensed by the user of device 100. In some embodiments, at least one tactile output generator is located on or near a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward from the surface of device 100) or horizontally (e.g., forward / backward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back surface of device 100, opposite to the touchscreen display 112 located on the front surface of device 100.

[0062] The device 100 also optionally includes one or more accelerometers 168. Figure 1A shows an accelerometer 168 coupled to a peripheral interface 118. Alternatively, the accelerometer 168 is optionally coupled to an input controller 160 in the I / O subsystem 106. The 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 as a whole. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on an analysis of data received from one or more accelerometers. Device 100 optionally includes, in addition to one or more accelerometers 168, a magnetometer (not shown), and a GPS (or GLONASS or other global navigation system) receiver (not shown) for acquiring information regarding the position and orientation of Device 100 (e.g., portrait or landscape).

[0063] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Furthermore, in some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) stores a device / global internal state 157, as shown in Figures 1A and 3. The device / global internal state 157 includes one or more of the following: an active application state indicating which application is active, if there is an application currently active; a display state indicating which applications, views, or other information occupy different areas of the touchscreen display 112; a sensor state including information obtained from various sensors and input control devices 116 of the device; and position information relating to the location and / or orientation of the device.

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

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

[0066] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger being lowered), determining the intensity of the contact (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more events of a finger being dragged), and determining whether contact has stopped (e.g., detecting a finger being lifted or an interruption of contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, represented by a series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions can be optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the 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 (for example, whether the user has "clicked" on an icon). In some embodiments, at least one subset of the intensity thresholds is determined according to a software parameter (for example, the intensity thresholds can be adjusted without changing the physical hardware of device 100, rather than being determined by the activation threshold of a particular physical actuator). For example, the mouse "click" threshold for a trackpad or touchscreen display can be set to one of a range of default thresholds without changing the trackpad or touchscreen display hardware. In addition, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (for example, by adjusting individual intensity thresholds and / or multiple intensity thresholds at once using a system-level click "intensity" parameter).

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

[0069] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for altering the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). In this specification, the term “graphics” includes, but is not limited to, any object that can be displayed to the user, including characters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[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 from an application or the like, as needed, specifying the graphics to be displayed along with coordinate data and other graphic characteristic data, and then generates screen image data to output to the display controller 156.

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

[0072] The text input module 134 is optionally a component of the 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 applications that require text input).

[0073] The GPS module 135 determines the device's location and provides this information for use in various applications (for example, to the telephone 138 for location-based dialing, to the camera 143 as image / video metadata, and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map / navigation widgets).

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

[0075] Examples of other applications 136 that may be 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, speech recognition, and speech duplication.

[0076] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the contact module 137 is used to manage an address book or contact list (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including optionally adding names(s) to the address book, deleting names(s) from the address book, associating names(s) to telephone numbers(s) or email addresses(s) or physical addresses(s) or other information with names, associating images with names, categorizing and sorting names, and providing telephone numbers or email addresses to initiate and / or facilitate communication via telephone 138, video conferencing module 139, email 140, or IM 141.

[0077] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the telephone module 138 is optionally used for inputting character sequences corresponding to telephone numbers, accessing one or more telephone numbers in the contact module 137, modifying entered telephone numbers, dialing each telephone number, conducting conversations, and ending or hanging up a call when a conversation is finished. As previously mentioned, wireless communication optionally uses one of several communication standards, protocols, and technologies.

[0078] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, the video conferencing module 139 includes executable commands for starting, running, and ending video conferences between the user and one or more other participants in accordance with user commands.

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

[0080] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable commands for inputting character sequences corresponding to instant messages, modifying previously entered characters, sending each instant message (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephone-based instant messaging, or XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). In this specification, “instant messaging” refers to both telephone-based messaging (e.g., messages sent using SMS or MMS) and internet-based messaging (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0081] In conjunction with the RF circuit 108, touchscreen 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 includes executable commands for creating training (e.g., having time, distance, and / or calorie burn targets), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor training, selecting and playing music for training, and displaying, storing, and transmitting training data.

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

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

[0084] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the browser module 147 includes executable commands for browsing the Internet according to user commands, including searching, linking, 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 circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable commands for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar entries, to-do lists, etc.) according to user commands.

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

[0087] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creation module 150 is used by the user to optionally create widgets (for example, to turn a user-specified portion of a web page into a widget).

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

[0089] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music player module 152 includes executable commands that enable the 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 commands for displaying, presenting, or otherwise playing video (for example, on the touchscreen 112 or on an external display connected via the 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 touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the memo module 153 includes executable commands for creating and managing memos, to-do lists, etc., according to user commands.

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

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

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

[0094] In some embodiments, device 100 is a device in which the operation of a default set of functions in the device is performed solely through a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on device 100 is optionally reduced.

[0095] A default set of functions, performed only through the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to the main menu, home menu, or root menu. 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] Figure 1B is a block diagram showing exemplary components for event processing according to several embodiments. In some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) includes an event sorter 170 (e.g., within the operating system 126) and each application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

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

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

[0099] The event monitor 171 receives event information from the peripheral interface 118. The event information includes information about sub-events (for example, user touch on the touch-sensitive display 112 as part of a multi-touch gesture). The peripheral interface 118 transmits information received from the I / O subsystem 106, or from sensors such as the proximity sensor 166, one or more accelerometers 168, and / or the microphone 113 (via the audio circuit 110). The information received by the peripheral interface 118 from the I / O subsystem 106 includes information from the touch-sensitive display 112 or the touch-sensitive surface.

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

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

[0102] The hit view determination module 172 provides a software procedure for determining where in one or more views a sub-event occurred when the touch-sensitive display 112 displays two or more views. A view consists of control devices and other elements that the user can see on the display.

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

[0104] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views arranged in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchy from which the sub-events should be processed. In most situations, the hit view is the lowest-level view from which the 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 the hit view determination module 172, this hit view typically receives all sub-events related to the same touch or input source that identified it as the hit view.

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

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

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

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

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

[0110] The event receiving unit 182 receives event information from the event sorter 170. The event information includes information about sub-events, such as touches or the movement of touches. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, an event includes the 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 called the device's orientation).

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

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

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

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

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

[0116] In some embodiments, each event recognition unit 180 activates an event handler 190 associated with an event when one or more specific sub-events of an event are recognized. In some embodiments, each event recognition unit 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and delaying sending) the sub-events to the respective hit view. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event handler 190 associated with that flag captures the flag and executes a default process.

[0117] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about a sub-event without activating an event handler. Instead, the sub-event distribution command distributes event information to an event handler associated with a set of sub-events, or to a view that is actively involved. The event handler associated with the set of sub-events or the view that is actively involved receives the event information and performs predetermined processing.

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

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

[0120] The above discussion regarding the processing of user touch events on a touch-sensitive display also applies to other forms of user input for operating a multifunctional device 100 having input devices, and it will be understood that not all of these user inputs necessarily begin on a touchscreen. For example, mouse movement and mouse button presses, touch movements such as taps, drags, and scrolls on a touchpad, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof may be optionally used as inputs corresponding to sub-events that define the events to be recognized.

[0121] Figure 2 shows a portable multifunctional device 100 having a touchscreen 112 according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, and in other embodiments described below, the user can select one or more of the graphics by making gestures on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with that one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward, and / or downward), and / or rotations of the finger in contact with the device 100 (from right to left, left to right, upward, and / or downward). In some implementations or situations, accidental contact with a graphic does not constitute a selection of that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon does not arbitrarily select the corresponding application.

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

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

[0124] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, according to some embodiments. Device 300 does not need to be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), game system, or 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. The communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, the display 340 is typically a touchscreen display. The 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 that generates tactile output on device 300 (for example, similar to the tactile output generator 167 described above with reference to Figure 1A), and a sensor 359 (for example, an optical, acceleration, proximity, touch-sensing, and / or contact intensity sensor similar to the contact intensity sensor 165 described above with reference to Figure 1A). The memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores programs, modules, and data structures similar to, or subsets thereof, that are stored in the memory 102 of the portable multifunction device 100 (Figure 1A).Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of the portable multifunction device 100. For example, memory 370 of device 300 optionally stores the 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 the portable multifunction device 100 (Figure 1A) optionally does not store these modules.

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

[0126] Next, we turn our attention to an optional embodiment of a user interface that may be implemented, for example, on a portable multi-functional device 100.

[0127] Figure 4A shows an exemplary user interface of an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof. • Signal strength indicators (single or multiple) for wireless communication (single or multiple) such as cellular signals and Wi-Fi signals 402, ·Time 404, • Bluetooth indicator 405, • Battery status indicator 406, Tray 408 contains icons for frequently used applications, as shown below. ○Optionally including an indicator 414 for the number of missed calls or voicemail messages, an icon 416 labeled "Telephone" for the telephone module 138, ○Optionally including an indicator 410 of the number of unread emails, an icon 418 labeled "Mail" for the email client module 140, ○ Icon 420 for browser module 147, labeled "Browser", and ○ Icon 422 for the video and music player module 152, also known as the iPod (trademark of Apple Inc.) module 152, labeled "iPod", and • Icons of other applications, such as the following: ○ Icon 424 for IM module 141, labeled "Message" ○ Icon 426 for calendar module 148, labeled "Calendar", ○ Icon 428 for image management module 144, labeled "Photo" ○ Icon 430 for camera module 143, labeled "Camera" ○ Icon 432 for 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" ○ Icon 444 for memo module 153, labeled as "Memo", and ○ An icon 446 labeled "Settings" for a settings application or module, which provides access to settings for device 100 and its various applications 136.

[0128] Please note that the icon labels shown in Figure 4A are for illustrative purposes only. For example, the icon 422 for the video and music player module 152 may display "Music" or "Music Player," and other labels may be used optionally for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to that application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0129] Figure 4B shows an exemplary user interface on a device (e.g., device 300 in Figure 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in Figure 3) separate from the 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) for detecting the intensity of contact on the touch-sensitive surface 451, and / or one or more tactile output generators 357 for generating tactile output to the user of device 300.

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

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

[0132] Figure 5A shows an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., Figures 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter referred to as touchscreen 504. Alternatively, or in addition to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of the applied contact (e.g., touch). One or more intensity sensors on touchscreen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 500 may respond to touches based on the intensity of the touch, meaning that touches of different intensity may invoke different user interface behaviors 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, “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on 8 May 2013 and published as International Patent No. WO / 2013 / 169849, and International Patent Application No. PCT / US2013 / 069483, “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on 11 November 2013 and published as International Patent No. WO / 2014 / 105276.

[0134] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The 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, the device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow the device 500 to be attached to, for example, a hat, eyewear, earrings, necklace, shirt, jacket, bracelet, watch band, chain, trousers, belt, shoes, wallet, backpack, etc. These attachment mechanisms allow the user to wear the device 500.

[0135] Figure 5B shows an exemplary personal electronic device 500. In some embodiments, the device 500 may include some or all of the components described with respect to Figures 1A, 1B, and 3. The device 500 has a bus 512 that operably connects an I / O section 514 to one or more computer processors 516 and memory 518. The I / O section 514 may be connected to a display 504, which may have a touch-sensing component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, the I / O section 514 may 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 may include input mechanisms 506 and / or 508. The input mechanism 506 may optionally be, for example, a rotatable input device or a pressable and rotatable input device. In some examples, the input mechanism 508 may optionally be a button.

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

[0137] The memory 518 of the personal electronic device 500 may include one or more non-temporary computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, can cause the computer processors to execute techniques described below, including processes 700, 900, and 1100 (Figures 7A-7F, 9A-9D, and 11A-11E). The computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or connected to an instruction execution system, apparatus, or device. In some examples, the storage medium is a temporary computer-readable storage medium. In some examples, the storage medium is a non-temporary computer-readable storage medium. The non-temporary computer-readable storage medium may include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray® technology, as well as resident solid-state memory such as flash and solid-state drives. The personal electronic device 500 is not limited to the components and configurations shown in Figure 5B, and may include other or additional components in multiple configurations.

[0138] In this specification, the term "affordance" refers to user-interactive graphical user interface objects that are optionally displayed on the display screens of devices 100, 300, and / or 500 (Figures 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute affordances.

[0139] As used herein, the term “focus selector” refers to an input element that indicates the current part of the user interface that the user is interacting with. In some implementations, including a cursor or other location marker, the cursor acts as a “focus selector,” and therefore, when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in Figure 3 or touch-sensitive surface 451 in Figure 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, including a touchscreen display that enables direct interaction with user interface elements on the touchscreen display (e.g., touch-sensitive display system 112 in Figure 1A or touchscreen 112 in Figure 4A), detected contact on the touchscreen acts as a “focus selector,” and therefore, when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one area of ​​the user interface to another without the movement of a corresponding cursor or touch on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or touch on the touchscreen display) that is controlled by the user to communicate the user's intended interaction through the user interface (e.g., by indicating to the device the user interface element in which the user intends to interact).For example, the position of a focus selector (e.g., cursor, touch, or selection box) over a corresponding button while pressure input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (rather than other user interface elements displayed on the device's display).

[0140] As used herein and in the claims, the term “characteristic intensity” of a contact refers to the characteristics of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a set of intensity samples collected over a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of movement of contact, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the top 10 percentile value of the contact intensity, the maximum half value of the contact intensity, the maximum 90 percent value of the contact intensity, etc. In some embodiments, the duration of contact is used when determining characteristic intensity (for example, when characteristic intensity is the average intensity of contact over time). In some embodiments, characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action has been performed by the user. For example, a set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity exceeding the second threshold results in a third action. In some embodiments, the comparison between characteristic intensity and one or more thresholds is not used to determine whether a first action should be performed or a second action should be performed, but rather to determine whether one or more actions should be performed at all (for example, whether each action should be performed or whether each action should be refrained from).

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

[0142] The intensity of contact on the touch-sensitive surface is optionally characterized with respect to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to the 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 the intensity at which the device performs an action different from the action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact with a characteristic intensity below the light press intensity threshold (e.g., above the nominal contact detection intensity threshold below which contact is no longer detected) is 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. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface diagrams.

[0143] An increase in the characteristic intensity of contact from an intensity below a light pressure intensity threshold to an intensity between the light and deep pressure intensity thresholds is sometimes referred to as a "light pressure" input. An increase in the characteristic intensity of contact from an intensity below a deep pressure intensity threshold to an intensity above a deep pressure intensity threshold is sometimes referred to as a "deep pressure" input. An increase in the characteristic intensity of contact from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold is sometimes referred to as the detection of contact on the touch surface. A decrease in the characteristic intensity of contact from an intensity above a contact detection intensity threshold to an intensity below a contact detection intensity threshold is sometimes referred to the detection of contact lift-off 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 the detection of a gesture including each press input, or in response to the detection of each press input performed by each (or more) contact, and each press input is detected at least in part on the detection of an increase in the intensity of the contact (or more) above a press input intensity threshold. In some embodiments, each action is performed in response to the detection of an increase in the intensity of each contact above a press input intensity threshold (e.g., a "downstroke" of each press input). In some embodiments, a press input includes an increase in the intensity of each contact above a press input intensity threshold, followed by a decrease in the intensity of the contact below the press input intensity threshold, and each action is performed in response to the detection of a decrease in the intensity of each contact below the press input threshold (e.g., an "upstroke" of each press input).

[0145] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, which may be referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship with a press input intensity threshold (for example, the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of each contact above the press input intensity threshold, followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and each action is performed in response to the detection of a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (for example, an “upstroke” of each press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from below a hysteresis intensity threshold to above a press input intensity threshold, and optionally a decrease in contact intensity to below the hysteresis intensity, and each action is performed in response to the detection of a press input (e.g., depending on the situation, an increase in contact intensity or a decrease in contact intensity).

[0146] For the sake of clarity, the description of an action performed in response to a press input associated with a press input intensity threshold, or a gesture involving a press input, is optionally triggered in response to the detection of any of the following: an increase in contact intensity above the press input intensity threshold, an increase in contact intensity from below the hysteresis intensity threshold to above the press input intensity threshold, a decrease in contact intensity below the press input intensity threshold, and / or a decrease in contact intensity below the hysteresis intensity threshold corresponding to the press input intensity threshold. Furthermore, in examples where an action is described to be performed in response to the detection of a decrease in contact intensity below the press input intensity threshold, the action is optionally performed in response to the detection of a decrease in contact intensity below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0147] Next, we will focus on embodiments of user interfaces ("UI") and related processes implemented on electronic devices such as portable multifunction device 100, device 300, or device 500.

[0148] Figures 6A to 6Q-1 show exemplary user interfaces for displaying aggregated health records to a user, according to some embodiments. For convenience, the health records are described herein as the user's health records. However, the health records may be those of family members or other individuals 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 shown in Figures 7A to 7F.

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

[0150] Figures 6A to 6Q-1 show exemplary user interfaces for displaying a user's aggregated health records, according to some embodiments. The user interfaces in Figures 6A to 6Q-1 allow a user to view their health records from one or more healthcare providers. Such user interfaces present the user's health records in a systematic manner, enabling the user to quickly and efficiently browse their health records. More specifically, the health records in Figures 6A to 6Q-1 are categorized into several categories. In the illustrated embodiments, such categories include allergies, clinical documents, test results, medications, and health status. However, in alternative embodiments, health records may be categorized using further or different categories or groupings. The user interface also presents existing health records and updates to existing and new health records in a systematic manner, integrating existing and new health records.

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

[0152] Figure 6A shows one embodiment of displaying representations of a user's health record categories from one or more healthcare providers. Figure 6A includes category representations 5006A, 5006B, 5006C, 5006D, and 5006E, as well as all record representations 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 test results, category representation 5006D is associated with medications, and category representation 5006E is associated with health conditions. Each of the category representations 5006A to 5006E is an affordance that includes text indicating that such an affordance is associated with health records from a particular category. Each of the category representations 5006A to 5006E is selectable by the user to view the user's health records from the associated category. In some embodiments, category expressions 5006A to 5006E also include a description of the corresponding category, an overview of the health records included in the corresponding category, or other information relating to the corresponding category. For example, category expression 5006E may include information summarizing another ongoing health condition of the user. All record expressions 5006F are affordances that include text indicating that such affordances are associated with all health records. All record expressions 5006F are selectable by the user to view all of the user's health records. Figures 6A to 6B illustrate the detection of a tap gesture (e.g., a tap gesture with contact 5502 in Figure 6A) on an affordance (medication category expression 5006D) and the display of health records corresponding to the health record category associated with the affordance (e.g., medication records 5018A and 5018B in Figure 6B) in response to the tap gesture.

[0153] Figure 6B shows a display of health records associated with the drug category representation 5006D shown in Figure 6A. More specifically, drug records 5018A and 5018B (ABC drugs and DEF drugs) are displayed. In the illustrated embodiment, drug records 5018A and 5018B are health records of drugs taken by the user and include text identifying the names of the drugs (ABC drugs and DEF drugs, respectively), the healthcare provider that prescribed the drugs (Alpha Health Care in both records), and the date the drugs were prescribed (October 1, 2017 and September 1, 2017, respectively). The healthcare provider may be one or more physicians, the name of a medical organization such as a home healthcare organization or hospital group, or a designation of a specific facility or location where treatment was performed, such as a specific hospital or clinic. In other embodiments, medication records 5018A and 5018B may display text or images representing further information about the medication, such as the prescribing pharmacist, the expiration date or expiration date of the medication, instructions or affordances for replenishing the medication, dosage, instructions, warnings, side effects, active ingredients, images of the medication, fact sheets about the medication, or any other suitable information. In the illustrated embodiment, medication records 5018A and 5018B are arranged in chronological order from the most recent prescription date. In other embodiments, medication records 5018A and 5018B are arranged so that daily medications are listed before other medications, alphabetically, or in another appropriate medication classification order. Figure 6B also shows health record affordance 5304, which is an affordance for viewing the category representations 5006A-5006E shown in Figure 6A (allergy, clinical documentation, laboratory results, medication, and health status categories, respectively). In this regard, Figure 6B further shows that a tap gesture accompanied by contact 5504 on the health record affordance 5304 is detected to display the category representations 5006A to 5006E in Figure 6C.

[0154] In Figure 6B, medication records 5018A and 5018B (ABC and DEF medications) are both health records provided by Alpha Health Care. In some embodiments of Figures 6A-6Q-1, if the user has completed the onboarding process with two or more healthcare providers, 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, Figure 6B-1 shows another embodiment in which the user has completed the onboarding process with Alpha Health Care and Beta Health Care. In Figure 6B-1, in response to the detection of a tap gesture with contact 5502 on the category representation 5006D in Figure 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 way, the user can view all of their prescriptions from their healthcare providers in a single interface. In the illustrated embodiment, drug records 5018A to 5018D are classified by prescription date. In other embodiments, the drug records included in Figures 6A to 6Q-1 may be classified by healthcare provider, by medical condition being treated, or by any other preferred method.

[0155] Figure 6B-1 also shows that detecting a tap gesture with contact 5504' on health record affordance 5304 displays the category representations 5006A-5006E in Figure 6C (allergy, clinical document, test results, medication, and health status categories, respectively). Figure 6C shows that in response to detecting a tap gesture with contact 5504 or 5504' on health record affordance 5304, the category representations 5006A-5006E are redisplayed. Figure 6C further shows that detecting a tap gesture with contact 5506 on category representation 5006B associated with a clinical document displays the representations 5015A-5015C of the three subcategories of the clinical document in Figure 6D (X-ray image, CT scan, and ultrasound image subcategories, respectively).

[0156] Figure 6D shows the subcategory representations 5015A-5015C of clinical documents and the representation 5017A for all clinical documents. In the illustrated embodiment, subcategory representation 5015A is associated with X-ray images, subcategory representation 5015B is associated with CT scan images, and subcategory representation 5015C is associated with ultrasound images. As shown in Figure 6D, each of the subcategory representations 5015A-5015C is an affordance that includes text indicating that such an affordance is associated with a health record from a particular subcategory of clinical documents. The representation 5017A for all clinical documents is an affordance that includes text indicating that such an affordance is associated with all health records of clinical documents. Furthermore, each of the subcategory representations 5015A-5015C is selectable by the user to view the user's clinical documents from the relevant subcategory. In the illustrated embodiment, the subcategories of clinical document categories are formed based on the type of clinical document. In other embodiments, clinical documents acquired over different periods (such as one year, three months, one month, or another period) are grouped into different clinical document subcategories based on such periods. In further embodiments, subcategories of a user's health records are subdivided based on other preferred means of classifying the user's health records. Figure 6D further illustrates the detection of a tap gesture with contact 5508 on a subcategory representation 5015A associated with an X-ray image to display the X-ray records 5016A and 5016B in Figure 6E. Figure 6E shows the display of a health record associated with a subcategory representation 5015A (e.g., the "X-ray Image" subcategory in Figure 6D). More specifically, the X-ray records 5016A and 5016B are displayed. In the illustrated embodiments, the X-ray records 5016A and 5016B are records of the user's X-ray images and include text identifying the provider that ordered or performed the X-ray examination (in both records, Dr. Doe and Alpha Health Care). 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 providers. In this way, both the healthcare professionals and organizations or facilities associated with the health record can be identified within the health record itself.In other embodiments, multiple physicians may be listed to identify the physician ordering the X-ray or the physician reviewing the X-ray. In such embodiments, both the healthcare provider's organization and facilities 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 containing a photograph of the X-ray image. In some embodiments, the user may tap one of the image files 5036A or 5036B to overlay a full-screen image of the X-ray image, zoom in on a photograph of the X-ray image, or obtain further information about the X-ray image, such as radiologist's notes or diagnosis.

[0157] Similar to Figure 6B, in Figure 6E, both X-ray records 5016A and 5016B are health records provided by Alpha Health Care. Figure 6E-1 shows an alternative embodiment in which the user has completed the onboarding process with Alpha Health Care and Beta Health Care. In Figure 6E-1, in response to detecting a tap gesture with contact 5508 on the subcategory representation 5015A (X-ray image subcategory) in Figure 6D, the X-ray record 5016C from Beta Health Care is displayed simultaneously with the X-ray records 5016A and 5016B from Alpha Health Care. In such a manner, similar to the user interface in Figure 6C-1, the user can view all of their X-ray images from their healthcare providers in a single interface. In the illustrated embodiment, the X-ray record 5016C includes text identifying the provider (Dr. Smith and Beta Health Care), the date on which such X-ray images were 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 the user selecting, for example, a representation 5017A of all clinical documents shown in Figure 6D.

[0158] Figures 6E and 6E-1 show, respectively, the detection of a tap gesture with contact 5510 or 5510' on clinical document affordance 5307 to display the subcategory representations 5015A-5015C (X-ray images, CT scans, and ultrasound images) in Figure 6F. Figure 6F shows the redisplay of subcategories 5015A-5015C in response to the detection of 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 the category representations 5006A-5006E (allergy, clinical documents, test results, medication, and health status categories, respectively) in Figure 6G. Figure 6G shows that in response to the detection of a tap gesture accompanied by contact 5512 on the health record affordance 5304 (shown, for example, in Figure 6F), the category representations 5006A to 5006E are redisplayed.

[0159] Figure 6G also shows how a tap gesture with contact 5514 on all record representations 5006F can be detected to simultaneously display health records from different categories in Figure 6H. Figure 6H shows the display of 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, Figure 6H shows the simultaneous display of medication records 5018A and 5018B (ABC medications and DEF medications) and X-ray records 5016A and 5016B of X-ray images taken on October 1, 2017 and September 1, 2017. In the illustrated embodiment, health records are grouped based on the date of visit to the healthcare provider. Medication records 5018A and X-ray records 5016A are displayed within the first group of health records from the visit to Alpha Health Care on October 1, 2017. Medication record 5018B and X-ray record 5016B are displayed within a second group of health records from the visit to Alpha Health Care on September 1, 2017. In the illustrated embodiment, health records are displayed in different colors to distinguish health records of different categories. Medication records 5018A and 5018B are displayed in a first color representing medication, 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 period, visit date, provider (if more than one provider is onboarded, as described with respect to Figure 6H-1), health record category, health record subcategory, severity of condition, or any other preferred criterion, or may be displayed in colors assigned based on such characteristics. Characteristics of healthcare providers, etc., may be further divided or distinguished by organization, physician, facility, or location. In this way, health records can be grouped together and colored to allow users to quickly distinguish between health records with different characteristics.In other embodiments, when only display groups and colors are used, health records that meet a common criterion may be displayed in a specific font, in a specific location, with a specific icon, with a specific graphic element, or otherwise with a specific visual feature, so that the user can distinguish health records on three or more available criteria.

[0160] In Figure 6H, the X-ray records 5016A and 5016B of the X-ray images taken on October 1, 2017 and September 1, 2017, and the medication records 5018A and 5018B (ABC and DEF medications) are all health records provided by Alpha Health Care. Figure 6H-1 shows an alternative embodiment in which the user has completed the onboarding process with Alpha Health Care and Beta Health Care. In Figure 6H-1, in response to the detection of a tap gesture with contact 5514 on all record representations 5016F in Figure 6G, both the medication record 5018C (GHI medication) and the X-ray record 5016C of the X-ray image ordered on September 15, 2017, are acquired from Beta Health Care and displayed simultaneously with the medication record 5018A and X-ray record 5016A from Alpha Health Care. In Figure 6H-1, drug record 5018C and X-ray record 5016C are displayed in a single group, representing a health record from a visit to Beta Health Care on September 15, 2017. In the illustrated embodiment, drug record 5018C and X-ray record 5016C are health records from a visit on September 15, 2017, and are newer than drug record 5018B and X-ray record 5016B, which are health records from a visit on September 1, 2017. Therefore, drug record 5018C and X-ray record 5016C are displayed on display 112 in place of or before drug 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 drug 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 the detection of tap gestures accompanied by contact 5516 or 5516' on health record affordance 5304, respectively, to display category representations 5006A-5006E in Figure 6I (allergy, clinical documentation, test results, medication, and health status categories, respectively). Figure 6I shows the redisplay of category representations 5006A-5006E in response to the detection of a tap gesture accompanied by contact 5516 or 5516' on health record affordance 5304. Figure 6I also shows the detection of a tap gesture accompanied by contact 5518 on category representation 5006E to view health status records 5020A, 5020B, and 5020C in Figure 6J.

[0162] Figure 6J shows the display of user health records 5020A, 5020B, and 5020C. In the illustrated embodiment, health record 5020A is a health record that includes information about the user's cholesterol level, the date the user's cholesterol was measured, and the name of the healthcare provider who measured the user's cholesterol level. In some embodiments, the user's cholesterol level value is displayed in a larger font, underlined, highlighted, or otherwise formatted to emphasize the user's cholesterol level. In some embodiments, the user's cholesterol level value is also displayed in color to indicate where the user's cholesterol level falls within a cholesterol level range. For example, the user's cholesterol level value may be displayed in green if the user's cholesterol level is less than 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 current cholesterol value is displayed within a numerical range. Numerical values ​​indicate the severity of the user's cholesterol levels, and numerical ranges indicate 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 represent the normality or severity of any condition. Graphical representations of such values ​​and ranges are also available. In the illustrated embodiment, health record 5020B is a health record that includes information about the user's chronic migraines, medications prescribed to the user, the prescription date, and the healthcare provider that provided the prescription to the user. Similarly, health record 5020C is a health record that includes information about the user's anxiety disorder, medications prescribed to the user, the prescription date, and the name of the healthcare provider that provided the prescription to the user.

[0163] In Figure 6J, health status records 5020A-5020C (cholesterol levels, chronic migraines, and anxiety disorders, respectively) are all health records provided by Alpha Health Care. Figure 6J-1 shows an alternative embodiment in which the user has completed the onboarding process with Alpha Health Care and Beta Health Care. In Figure 6J-1, in response to detecting a tap gesture with contact 5518 on the category representation 5006E (health status category) in Figure 6I, health status record 5020D from Beta Health Care is displayed simultaneously with health status records 5020A-5020C. Health status record 5020D, like health status records 5020B and 5020C, is a health record that includes information on medications prescribed to treat the health condition, the date the medications were prescribed to the user, and the name of the healthcare provider that provided the prescription to the user. In some embodiments, each health status record also includes further information relating to each health status, such as a description of the health status, symptoms, related health conditions, treatment options, lifestyle recommendations, and other relevant information relating to each health status. In some embodiments, each health status record is an affordance that the user selects to view further information relating to the corresponding health status. In this regard, Figures 6J and 6J-1 also show that a tap gesture accompanied by contact 5520 or 5520', respectively, on a health status record 5020A can be detected to display such further information as shown in Figure 6K or Figure 6K-1.

[0164] Figure 6K shows the display of further information regarding the health record 5020A (user's cholesterol level). As shown in Figure 6K, a cholesterol representation 5021A is displayed, which includes a display of the user's current cholesterol level and a display of where the user's current cholesterol level falls within the cholesterol level range. More specifically, the cholesterol representation 5021A visually indicates that the user's current cholesterol level is in the range of 240 mg / dL to 300 mg / dL, and therefore falls within the range between high cholesterol (240 mg / dL) and very high cholesterol (300 mg / dL). In the illustrated embodiment, a cholesterol representation 5021B is also displayed on the display 112. As further shown in Figure 6K, a cholesterol representation 5021B is displayed which includes a bar graph of the user's cholesterol level over time, with each bar representing a measured value of the user's cholesterol level. In the illustrated embodiment, different bars representing cholesterol levels belonging to different ranges are displayed in different colors. In other embodiments, further representations of the user's current and past cholesterol levels are displayed. Figure 6K also shows that past health records of the user's cholesterol levels on September 1, 2016, and January 1, 2016, respectively, are displayed within health status records 5030B and 5030C. As used herein, past health records are any health records other than the current health record for any particular health information. For example, a medication record containing information about medications that are no longer prescribed to the user is a past health record. Further examples of past records are shown in at least Figures 8D and 8E and described in the following paragraphs. In the illustrated embodiment, past health records are also color-coded based on the severity of the user's health condition compared to normal health. 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] Figure 6K-1 shows the display of further information regarding health status records 5020A from both Alpha Health Care and Beta Health Care. In the illustrated embodiment, the historical health record 5030D obtained from Beta Health Care on September 15, 2017, is displayed together with the historical health records 5030B and 5030C from Figure 6K above (the user's cholesterol levels measured on September 1, 2016 and January 1, 2016, respectively). 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). Furthermore, the cholesterol representation 5021B includes a bar graph of the user's historical cholesterol levels obtained from both Alpha Health Care and Beta Health Care.

[0166] Figures 6L to 6Q-1 show a user interface for displaying notifications of updates made to the user's health record on device 100. Updates to the user's health record may include updates to the user's existing health record or updates to a new health record. Similar to Figure 6A, Figure 6L shows the display of category representations 5006A to 5006E (allergy, clinical documentation, test results, medication, and health status 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 confirmed by the user. To notify the user of the three updates, all update badges 5104 are displayed together with all health record representations 5006F, and category update badges 5106A, 5106B, and 5106C are displayed together with category representations 5006B, 5006D, and 5006E, respectively. In the illustrated embodiment, all update badges 5104 are circles containing the total number of updates to the user's health record. Similarly, category update badges 5106A, 5106B, and 5106C are circles containing the number of updates for 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 for a health record have been received but not yet confirmed, and category updates 5106A-5106C each indicate that one update for a health record in the corresponding health record category has been received but not yet confirmed. Figures 6K and 6K-1 further illustrate the detection of tap gestures accompanied by contact 5521 or 5521' on the health status affordance 5306, which is an affordance that the user selects to return to the user interface shown in Figures 6J and 6J-1, respectively.

[0167] Figure 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 can be used as update badges to indicate an update or the number of updates. For example, an update badge may be a highlighted or flashing category representation, or it may display the time or date of the update. In some embodiments, all update badges 5104 and category update badges such as category update badges 5106A-5106C (indicating updates to clinical document records, medication records, and health status records, respectively) are not displayed simultaneously. In one or more such embodiments, only category update badges are displayed on the display 112. In one or more such embodiments, only all update badges 5104 are displayed on the display 112. In some embodiments, a summary or part of the content of the update is displayed on or with the update badge. In one embodiment, the update badge is an affordance separate from the category affordance, and the user selects the update badge to view the updated health record or a summary or part of the updated health record. Figure 6L further illustrates the detection of a tap gesture with contact 5522 on the category update badge 5106C to display an update to the health record 5020A in Figure 6M.

[0168] In some embodiments of Figures 6L-6Q-1, in addition to or instead of update badges, the user may receive notifications 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 urgent by the user or healthcare provider. In one embodiment, device 100 may be pre-configured or configurable by the user to set one or more thresholds for one or more types of health records. When an update is received for a health record having a particular result, measurement, value, reading, or other measurable aspect that exceeds a set threshold or meets a criterion, one or more notifications to the user are automatically generated on device 100. In some embodiments, the notification method 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, text messages may be generated for some updates, and audible alarms may be generated for others, which are repeated periodically or at progressively shorter intervals until the user completes the requested action. In one embodiment, updates that are not urgent or do not exceed a set threshold do not trigger the generation of a notification.

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

[0170] Figures 6M and 6M-1 show that an update to the health record 5020A (user's cholesterol level) is displayed in response to the detection of a tap gesture accompanied by contact 5522 or 5522', respectively, on the category update badge 5106C. In each illustrated embodiment, the user's cholesterol level has been updated to reflect a new cholesterol measurement performed by Alpha Health Care on December 1, 2017. In each illustrated embodiment, 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 indicating the severity of the user's cholesterol level. In each illustrated embodiment, a recommendation affordance 5240A, which includes the recommended action of seeing a doctor, is displayed with the health record 5020A. In some embodiments, the recommendation affordance is a recommendation that suggests exercising, changing the user's diet, or engaging in other appropriate activities that would lower the user's cholesterol level. In some embodiments, the recommendation affordance 5240A includes content indicating the importance of an update or severity of the user's condition. In one or more such embodiments, the user may specify the importance of a particular type of health record, as well as updates to that particular type of health record. For example, the user may specify all updates to their cholesterol level as urgent updates. In one or more such embodiments, the user may specify the importance of a particular type of health record based on the positive or negative change in the user's health condition. For example, the user may specify the importance of an update to their cholesterol level based on the change in their cholesterol level. In other embodiments, the healthcare provider may specify the importance of a particular update. The description of Figures 6M and 6M-1 above relates to updates and recommendations based on the user's cholesterol, but 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 can be displayed on the display 112 advising the user to change their diet to increase their iron sources.

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

[0172] Figures 6O and 6O-1 show the display of updates to the recommended affordance 5240A, respectively. In each illustrated embodiment, the recommended affordance 5240A for the health record 5020A is updated to include text indicating the date of the appointment and the name of the doctor the user is scheduled to see. In some embodiments, the device 100 displays a notification reminding the user of the upcoming appointment or specifies a time to be notified in another way. Figures 6O and 6O-1 also show the detection of a tap gesture accompanied by contact 5527 or 5527' on the health record affordance 5304 to display any remaining updates to the health record, as shown in Figures 6P and 6P-1, respectively.

[0173] Figures 6P and 6P-1 show the display of category representations 5006A-5006E (allergy, clinical documentation, test results, medication, and health status categories, respectively) and the remaining updates for the user's health record. In the embodiment of Figure 6P where the user has onboarded only one healthcare provider, the total number of updates received by device 100 is shown, but all update badges 5104 that have not yet been confirmed by the user are updated from 3 updates to 2 updates, indicating the remaining number of updates that the user has not yet confirmed. In the representation category 5006E (health status category) in Figure 6L, the category update badge 5106C that was previously displayed is no longer displayed because the user has confirmed the update for health status record 5020A. Similarly, in the embodiment of Figure 6P-1 where there are more updates because the user has onboarded two healthcare providers, all update badges 5104 are updated from 4 updates to 3 updates, indicating the remaining number of updates that the user has not yet confirmed. Similar to Figure 6P, the category update badge 5106C previously displayed in representation category 5006E in Figure 6L-1 is no longer displayed because the user has confirmed the update to the health record 5020A. Figures 6P and 6P-1 further show that detecting a tap gesture accompanied by contact 5528 or 5528' on the full update badge 5104, respectively, displays Figure 6Q or 6Q-1, respectively.

[0174] Figures 6Q and 6Q-1 display updates to multiple types of health records, respectively. The embodiment of Figure 6Q shown displays a first update to a new medication record 5018E for a new prescription of ABC medication prescribed by Alpha Health Care on December 1, 2017, and a second update to a new X-ray record 5016D of 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 badge for updates to existing health records and the health record update badge for updates to new health records have different symbols, shapes, sizes, text fonts, text colors, or other visual differences to make it easier for the user to distinguish between updates to existing and new health records. Figure 6Q-1 also shows the display of the ABC medication record 5018E, the user's cholesterol level health status record 5020A, and the X-ray record 5016D of an X-ray image ordered on December 1, 2017. In addition to the update for the new medication record 5018E and the update for the new X-ray record 5016D from Alpha Health Care on December 1, 2017, Figure 6Q-1 includes an update from Beta Health Care, and therefore displays the third update for the new X-ray record 5016E taken at Beta Health Care on November 15, 2017, along with the health record update badge 5146.

[0175] Figures 7A to 7F are flowcharts illustrating methods for displaying aggregated health records using electronic devices according to several embodiments. Figures 7A to 7F are flowcharts illustrating methods for displaying a user's aggregated health records using, for example, the user interface shown in Figures 6A to 6Q-1. As described with reference to Figures 6A to 6Q-1, Method 700 can be used to display aggregated health records from one or more health records of a user from multiple healthcare providers. Method 700 is performed on a device (e.g., devices 100, 300, and 500 shown in Figures 1, 3, and 5A, respectively). In one such embodiment, the display 112 is a touchscreen display, and the touch-sensitive surface is on or incorporated into the display 112. In some embodiments, the display 112 is separated from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, a voice interface, or other preferred interface. Some operations in Method 700 are optionally combined. Furthermore, the order of some operations can be optionally changed.

[0176] As described below, Method 700 provides an intuitive method for displaying aggregated health records obtained from a user's healthcare providers. Method 700 also provides an intuitive method for simultaneously displaying aggregated health records obtained from multiple healthcare providers of a user. This method reduces the cognitive burden on the user when viewing the user's health records obtained from one or more healthcare providers, creating a more efficient human-machine interface. This method also improves user efficiency by simultaneously displaying health records obtained from multiple healthcare providers. For battery-powered computing devices, power is saved and battery charging intervals are extended by allowing the user to access health records obtained from one or more healthcare providers more quickly and efficiently.

[0177] Similar to Figures 6A to 6Q-1, Method 700 allows users to visualize their health records in a common interface. Using such a common interface avoids the risk that users may only be able to view a portion of their health information regarding a particular concern or question. For example, a user may not realize that blood tests have been performed by two different providers for a certain condition, resulting in inaccurate information being provided to a hospital or other subsequent provider. In such cases, using Device 100 to store health records across multiple providers and making them accessible to the user in a common interface provides the user with an easily accessible source of comprehensive health information, even if the user moves or changes providers. Many traditional healthcare providers discard health records after a period of time when the patient does not see such a healthcare provider, so such information may be lost forever. Such health records may contain important historical health information and baseline data that are essential for the diagnosis and treatment of subsequent diseases. In addition, using such a common interface avoids the need for users to use device 100 to retrieve data from various locations on device 100 or on other websites, portals, and other information sources, and to piece together information about a particular health condition, at the risk that the information may be overlooked, not immediately available, or only available after a lengthy electronic search using device 100. Furthermore, by storing such health records on device 100 and providing a single interface that allows users to view and browse all such health records, users can avoid the need to use device 100 to communicate with multiple healthcare providers via 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 Figure 6B-1 replaces the use of device 100, which previously required more than half a day to synthesize the aforementioned information, with just a few clicks on device 100 by the user, resulting in significant savings in bandwidth, battery life, and energy that were previously wasted.

[0178] Figures 7A to 7F are flowcharts illustrating a method for displaying a user's aggregated health record using, for example, the user interface shown in Figures 6A to 6Q-1. As illustrated with reference to Figures 6A to 6Q-1, Method 700 can be used to display an aggregated health record from one or more health records of a user from multiple healthcare providers. Method 700 is performed on a device (e.g., 100, 300, 500). In one such embodiment, the display 112 is a touchscreen display, and the touch-sensing surface is on or incorporated into the display 112. In some embodiments, the display 112 is separated from the touch-sensing surface. In other embodiments, the process described herein may be implemented using a device having a physical user interface, a voice interface, or other preferred interface. Some operations in Method 700 are optionally combined. Furthermore, the order of some operations can be optionally changed.

[0179] Similar to Figures 6A to 6Q-1, one or more embodiments of Method 700, illustrated in Figures 7A to 7F and described below, can be used to visualize health records in a common interface. Using such a method avoids the risk that a user may only be able to view a portion of the health information relating to a particular concern or question. For example, a user may not realize that blood tests have been performed by two different providers for a certain condition, providing inaccurate information to a hospital or other subsequent provider. Similarly, by using this method on a device such as Device 100 to store health records across multiple providers and making them accessible to the user in a common interface, a readily available source of comprehensive health information can be provided to the user, even if the user moves or changes providers. Many traditional healthcare providers discard health records after a period of time when the patient does not see such healthcare provider, so such information may be lost forever. Such health records may contain important historical health information and baseline data that are essential for the diagnosis and treatment of subsequent diseases. In addition, by using such a method, users can avoid the need to use a device such as device 100 to retrieve data from various locations on such device or on other websites, portals and other information sources, and piece together information about a particular health condition at the risk that the information may be overlooked, not immediately available, or only available after a long electronic search using the device. Furthermore, by storing and displaying such health records on a device such as device 100 using such a method, and providing a single interface that allows users to view and browse all such health records, users can avoid the need to use the device to communicate with multiple healthcare providers via 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 use of such devices, which previously required more than half a day to piece together the aforementioned information, can be replaced by a method that requires 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 with a second healthcare provider, device 100 receives a first request to display the user's health records via one or more input devices (702). In some embodiments, once the user completes the onboarding process with the healthcare provider, a request to display the health records is automatically sent to device 100. In some embodiments, the user requests device 100 to display the user's health records by selecting a health data affordance 5029A shown in Figure 6A, or an affordance displayed within the onboarding user face. In some embodiments, the request to display the health records is a request to display the health records of multiple users, such as family health records.

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

[0182] A representation of multiple categories includes a first representation of a first category among the multiple categories (706). Figure 6A shows, for example, a category representation 5006D associated with the user's medication. Furthermore, when the device 100 is associated with a first healthcare provider and not with a second healthcare provider, and the first representation of a first category is selected, the device 100 displays multiple health records of the first category from the first healthcare provider on the display 112 (706). In the embodiment shown in Figure 6B, the user is associated only with Alpha Health Care and not with Beta Health Care. Figure 6B shows an embodiment in which, for example, only medication records 5018A-5018B (ABC medications and DEF medications) from Alpha Health Care only are displayed on the device 100.

[0183] Multiple representations include a second representation of a second category among multiple categories (708). Figure 6I shows, for example, a category representation 5006E associated with the user's health status. Furthermore, if the device 100 is associated with a first healthcare provider and not with a second healthcare provider, and a second representation of a second category is selected, the device 100 displays multiple health records of the second category from the first healthcare provider on the display 112 (708). Figure 6J shows, for example, two health status records 5020A and 5020B (cholesterol levels and chronic migraine) in response to the detection of the tap gesture shown in Figure 6I on 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). Figure 6H shows, for example, X-ray records 5016A and 5016B (ordered on October 1, 2017 and September 1, 2017, respectively) displayed in the first color, and medication records 5018A and 5018B (ABC medications and DEF medications) displayed in the second color. Different types of health records are displayed in different colors, making it easier for the user to distinguish health records belonging to different categories (or subcategories). In some embodiments where multiple health records belonging to different categories are displayed simultaneously, the 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, the user may also distinguish different health records from different healthcare providers based solely on color. Furthermore, displaying different types of health records in different colors also reduces user errors when browsing their health records (such as misidentifying or being unable to identify a health record). This enhances device usability and makes the user device interface more efficient by allowing users to distinguish different types of health records based on color. This method also improves user efficiency by enabling users to identify health records by the color assigned to each type. For battery-powered computing devices, this saves power and extends the time between battery charges by allowing users to browse their health records faster and more efficiently.

[0185] In some embodiments, device 100 displays on display 112 a first content summarizing a 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 on display 112 further content associated with the first category that is not included in the first content (720). In some embodiments, the category representation 5006E (health condition category) in Figure 6I includes a summary affordance containing content summarizing the user's specific health condition. Furthermore, in response to detecting a user selection of the summary affordance, device 100 displays further information about the user's health condition, such as the cause of the health condition, methods for identifying the symptoms of the health condition, non-medicinal treatments to alleviate the health condition, and other useful information about the health condition.

[0186] In some embodiments, device 100 also displays on display 112 a second content summarizing a second category and a second category information affordance for the second category, and selecting the second category information affordance causes device 100 to display on display 112 further content associated with the second category that is not included in the second content (720). In some embodiments, category representation 5006B (a clinical document category as shown in Figure 6G) includes a summary affordance containing content summarizing the allergies the user is suffering from. Furthermore, in response to detecting a user selection of the summary affordance, device 100 displays further information about the allergies the patient is suffering from, such as methods for reducing or preventing the onset of a particular allergy, non-medicinal treatments for alleviating allergy symptoms, and other useful information about allergies. Content including a description of the health record category is provided along with the category representation. This method improves user efficiency by enabling the user to make information-based selections of health record categories based on descriptions of different health record categories. This method also enhances device usability and makes the user device interface more efficient by helping users make appropriate inputs and reducing the number of unnecessary inputs caused by users selecting the wrong health record category. For battery-powered computing devices, power is saved and the time between battery charges is extended by allowing users to browse their health records faster and more efficiently.

[0187] In some embodiments, multiple health records of a first category are displayed chronologically (722). Figure 6B-1 shows, for example, medication records 5018A-5018B (ABC medications and DEF medications) arranged based on prescription dates. In some embodiments, multiple health records of a second category are displayed chronologically (722). Figure 6J shows, for example, health condition records 5020A-5020C (associated with cholesterol levels, chronic migraines, and anxiety disorders, respectively) arranged based on prescription dates of medications prescribed for those health conditions. Presenting health records chronologically allows users to browse their health records by date, improving user efficiency. For battery-powered computing devices, enabling users to browse their health records faster and more efficiently saves power and extends the time between battery charges.

[0188] In some embodiments, device 100 detects a selection of a first representation of a first category while device 100 is associated with a first healthcare provider (724). Figure 6I shows, for example, a tap gesture with contact 5518 on a category representation 5006E (health status category). In some embodiments, in response to detecting a selection of a first representation of a first category while device 100 is associated with a first healthcare provider display, device 100 displays a first representation of a first health record from among multiple health records of the first category from the first healthcare provider on display 112 (724). Figure 6J shows, for example, a health status record 5020A, which includes the user's cholesterol level 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, where the numerical value indicates the health status of the first user, and the numerical range indicates a normal numerical range for the health status (724). The health status record 5020A shown in Figure 6J includes a value for the user's cholesterol level, which is 269 mg / dL. In some embodiments, the health status record 5020A also includes a value representing a cholesterol range, such as 0 to 400 mg / dL. This method reduces the cognitive burden on the user by providing the user with numerical values ​​that allow the user to determine the severity of their health status based on those values, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify the severity of their health status from the numerical values. In the case of battery-powered computing devices, power is saved and the intervals between battery charges are extended by allowing the user to identify the severity of their health status, the medical records associated with the health status, and their health status over time more quickly and efficiently.

[0189] In some embodiments, device 100 displays a numerical value in a color selected based on the severity of the first user's health condition (726). In some embodiments, the user's cholesterol level value 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 numerical values ​​based on the severity of the user's health condition allows the user to determine the severity of their health condition without requiring complex knowledge of how to read the numbers, creating a more efficient human-machine interface. This method also improves user efficiency by allowing the user to quickly identify the severity of their health condition based on the color associated with the numerical value. In the case of battery-operated computing devices, power is saved and the intervals between battery charges are extended by allowing the user to identify the severity of their health condition more quickly and efficiently.

[0190] In some embodiments, device 100 displays a second representation of a second health record of multiple health records of a first category from a first healthcare provider, the second representation of the second health record includes a graph showing the status of the first user over a period of time (728). Figure 6K shows, for example, a cholesterol representation 5021B in response to the detection of a tap gesture on a health status record 5020A (user's cholesterol level) shown in Figure 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 and creates a more efficient human-machine interface by providing the user with an image of the user's medical record that provides the user with information about the user's status over time. This method also improves user efficiency by allowing the user to quickly identify their health status over time in one common interface without having to navigate multiple user interfaces. For battery-powered computing devices, enabling users to identify their health status over time more quickly and efficiently saves power and extends the time between battery charges.

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

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

[0193] In some embodiments, the first health record of a first category and the third health record of a second category from the first healthcare provider are records of the first visit to the first healthcare provider (730). Figures 6B and 6E show, for example, 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, a second health record of a first category from a first healthcare provider and a fourth health record of a second category from a first healthcare provider are records of a second visit to the first healthcare provider (730). Figures 6B and 6E show, for example, 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 a health record relating to a first user, the device 100 simultaneously displays a first health record and a third health record in a first group on the display 112, the first group being identified on the display 112 by the first date of the first visit (730). Figure 6H shows, for example, that drug record 5018A (ABC drug) and X-ray record 5016A are grouped into a first group and that drug record 5018A and X-ray record 5016A are displayed simultaneously on the display 112.

[0196] In some embodiments, in response to receiving a first request to display health records relating to a first user, device 100 simultaneously displays second and fourth health records on display 112 within a second group, the second group being identified on display 112 by the second date of the second visit, where the first date is different from the second date (730). Figure 6H shows, for example, grouping medication record 5018B (DEF medication) and X-ray record 5016B into the second group. Further medication record 5018B and X-ray record 5016B are displayed simultaneously on display 112. This method reduces the cognitive burden on the user when viewing health records by grouping them based on appointment dates with healthcare providers and arranging different groups based on appointment dates. Optionally, if health records are from multiple healthcare providers, the health records are grouped by healthcare provider and by appointment date, and the groups are arranged by appointment date. Optionally, this method reduces the cognitive burden on users when viewing health records by displaying health records belonging to different categories in different colors, making it easier for users to distinguish between different health record categories. Optionally, this method also reduces the cognitive burden on users when viewing health records by displaying update badges along with updates to health records. Each of these creates a more efficient human-machine interface. This method also improves user efficiency by allowing users to identify health records based on appointment dates with healthcare providers and different appointment dates with different healthcare providers. This method also improves user efficiency and makes the user device interface more efficient by allowing users to view different health records from different healthcare providers in a common interface. For battery-powered computing devices, power is saved and battery charging intervals are extended by allowing users to browse their health records faster and more efficiently.

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

[0198] In some embodiments, a third health record of a second category from a first healthcare provider and a fourth health record of a second category from the first healthcare provider are displayed in a second color different from the first color (732). Figure 6H shows, for example, medication record 5018B (DEF medication) and X-ray record 5016B ordered on September 1, 2017, in a second color different from the first color. By displaying different health record categories in different colors, users can quickly distinguish between different health records, creating a more efficient human-machine interface. This method also improves user efficiency by allowing users to identify health records based on color. For battery-powered computing devices, power is saved and battery charging intervals are extended by allowing users to browse their health records faster and more efficiently.

[0199] In some embodiments, device 100 receives updates from a first healthcare provider for a first health record of a first category (734). Figure 6L illustrates, for example, the reception of multiple updates from Alpha Health Care (e.g., updates for a clinical document category expression 5006B, an update for a drug category expression 5006D, and an update for a health status category expression 5006E). In some embodiments, device 100 displays a first update badge associated with a first group of first health records on the display 112, and the first update badge and the first health record are displayed simultaneously within a first area of ​​the display 112. For example, Figure 6L shows a category update badge 5106C and a category expression 5006E within an area of ​​the display 112. In some embodiments, the category update badge 5106C is appended to the category expression 5006E. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to identify which health records have been updated. This method also improves user efficiency by allowing users to quickly identify which health records have been updated. For battery-powered computing devices, enabling users to identify updated health records faster and more efficiently saves power and extends the time between battery charges.

[0200] In some embodiments, device 100 displays a third representation of a third health record from a first healthcare provider, where the third representation of the third health record includes an image showing the medical record of a first user (736). In some embodiments, an X-ray image associated with an X-ray record, such as X-ray record 5016A (ordered October 1, 2017) in Figure 6E, is displayed in response to a user selection of this X-ray image. In some embodiments, such as Figure 6E, where X-ray record 5016A includes an image file 5036A of the X-ray image, when the image file 5036A is selected, device 100 enlarges the 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 this medical record. For battery-operated computing devices, allowing the user to access their health status faster and more efficiently saves power and extends the time between battery charges.

[0201] In some embodiments, device 100 receives an update for a health record in a first health record category (738). Figure 6L shows, for example, the reception of multiple updates from Alpha Health Care (e.g., an update for a clinical document category representation 5006B, an update for a medication category representation 5006D, and an update for a health status category representation 5006E). In some embodiments, after receiving an update for a health record in a first category, in response to receiving at least one of a first request to display a health record for a first user and a second request to display a health record for a 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 displayed simultaneously within a first area of ​​display 112 (738). Figure 6M shows, for example, medication records 5020A-5020C (associated with the user's cholesterol level, chronic migraine, and anxiety disorder, respectively) in response to the detection of a gesture on category representation 5006E in Figure 6L. Figure 6M also shows a health record update badge 5140 alongside health record 5020A to indicate that health record 5020A has been updated. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to identify which health records have been updated. This method also improves user efficiency by allowing the user to quickly identify which health records have been updated. In the case of battery-powered computing devices, power is saved and the interval between battery charges is extended by allowing the user to identify updated health records faster and more efficiently.

[0202] In some embodiments, a second update badge is visually associated with a first display of a first category (740). For example, Figure 6L shows a category update badge 5106C and a category representation 5006E (health status category) within a region of the display 112. In some embodiments, the category update badge 5106C is appended to the category representation 5006E. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to identify which categories contain updates to the user's health records. This 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, power is saved and the interval between battery charges is extended by allowing the user to identify updated health records faster and more efficiently.

[0203] In some embodiments, selecting a first representation of a first category while the device 100 is associated with a first healthcare provider causes the device 100 to display this representation of the health record for the first health record category on the display 112, and a second update badge is visually associated with this representation of the health record for the first health record category (742). Figure 6M shows, for example, a health record update badge 5140 and a health status record 5020A (associated with the user's cholesterol level) in the same area. In one or more embodiments, the health record update badge 5140 is attached to the health status record 5020A. This method reduces the cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health records. This method reduces the cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health records, 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-powered computing devices, enabling users to identify updated health records faster and more efficiently saves power and extends the time between battery charges.

[0204] In some embodiments, a second update badge includes the content of the update to the health record (744). In some embodiments, the content of the update, such as an update summary, is displayed on an update badge, such as the category update badge 5106A, 5106B, or 5106C, the health record update badge 5140, or the all-update badge 5104, as shown in Figures 6L and 6M. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to identify the content of the update or an overview of the update content without requiring further action. This method also improves user efficiency by allowing the user to quickly identify changes in health status associated with updated health records. In the case of battery-powered computing devices, power is saved and the intervals between battery charges are extended by allowing the user to identify changes in their health status more quickly and efficiently.

[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 Figure 6L) include update affordances, which are affordances that the user selects to view updates for the corresponding health record. Figure 6L shows, for example, a tap gesture with contact 5522 on category update badge 5106C. In some embodiments, in response to receiving a request to select a second update badge, device 100 displays on display 112 the update for this health record in the first health record category (746). Figure 6M shows, for example, an update for health status record 5020A (a health record of the user's cholesterol level) in response to detecting the tap gesture shown in Figure 6L. As shown in Figure 6M, health status record 5020A has been updated to show the user's cholesterol level as of December 1, 2017. This method reduces the cognitive burden on the user by allowing the user to identify which categories contain updates to their health records. It also reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to access updates to their health records by selecting an update badge. Furthermore, it improves user efficiency by making it easier for users to access updates by selecting an update badge. For battery-powered computing devices, power is saved and battery charging intervals are extended by allowing users to access updated health records faster and more efficiently.

[0206] In some embodiments, device 100 displays updates to a health record and recommended affordances associated with the health record simultaneously (748). Figure 6M shows, for example, the simultaneous display of a health status record 5020A (a health record of the user's cholesterol levels) and a recommended affordance 5240A. In some embodiments, device 100 receives a request to select a recommended affordance via one or more input devices (748). Figure 6M shows, for example, a tap gesture with contact 5524 on the recommended affordance 5240A. In some embodiments, in response to receiving a request to select a recommended affordance, device 100 displays a recommended action on display 112, the recommended action being based on an update to a health record (748). Figure 6N shows, for example, a calendar affordance 5241 in response to the gesture shown in Figure 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 along with the recommendation affordance 5240A. Figure 6M shows a recommendation affordance 5240A that includes text for the recommended action of seeing a doctor, for example. 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 way to respond. In the case of battery-operated computing devices, power is saved and the interval between battery charges is extended by enabling the user to decide more quickly and efficiently whether and how to respond to updates to their health records.

[0207] In some embodiments, the recommendation is to suggest scheduling an appointment with a first healthcare provider (750). In such embodiments, displaying the recommended action includes displaying the recommended action and scheduling affordances simultaneously (750). Figure 6N shows, for example, a calendar affordance 5241 in response to the gesture shown in Figure 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 way to respond. In the case of battery-powered computing devices, power is saved and the intervals between battery charges are extended by enabling the user to decide more quickly and efficiently whether and how to respond to updates to their health records.

[0208] In some embodiments, device 100 receives an update for a health record in a first health record category (752). Figure 6L shows, for example, the reception of multiple updates from Alpha Health Care (e.g., an update for a clinical document category expression 5006B, an update for a medication category expression 5006D, and an update for a health status category expression 5006E). In some embodiments, device 100 responds to the receipt of an update for a health record and displays an update notification on display 112 according to a determination that the importance of the update is greater than a threshold (752). For example, the recommendation affordance 5240A in Figure 6M includes the text "Urgent!" indicating the importance of the user's cholesterol change. In some embodiments, the update notification and the importance of the update overlay a portion of display 112 even if the user interface shown in Figures 6A to 6Q-1 is not displayed on the display. In one or more embodiments, the notification is a text-based notification.

[0209] Device 100 stops displaying update notifications on the display 112 if it determines that the importance of the update is below a threshold (752). In some embodiments, if the user's cholesterol level has not changed or improved significantly, or if the threshold for providing update notifications has not been met, the recommended affordance 5240A in Figure 6M or Figure 6M-1 is not displayed on the display 112. This method reduces the cognitive burden on the user by notifying them of important updates and creates a more efficient human-machine interface. This method also improves user efficiency by allowing the user to determine whether an update is important based on whether or not they receive a notification. In the case of battery-operated computing devices, power is saved and the interval between battery charges is extended by allowing the user to determine whether an update is important more quickly and efficiently.

[0210] After displaying representations of multiple health record categories and being associated with a second healthcare provider, device 100 receives a second request via one or more input devices to display 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 display health records obtained from two or more healthcare providers.

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

[0212] A representation of multiple categories includes a first representation of a first category among the multiple categories (714). Figure 6A shows, for example, a category representation 5006D (medication category) associated with the user's medication. Furthermore, when the device 100 selects a first representation of a first category while associated with a first healthcare provider and a second healthcare provider, the device 100 displays on the display 112 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 (714). Figure 6B-1 shows, for example, an alternative embodiment of Figure 6B. In the embodiment of Figure 6B-1, the user has completed the onboarding process with both Alpha Health Care and Beta Health Care. In this embodiment, while device 100 is associated with Alpha Health Care and Beta Health Care, a gesture involving touch 5502 on the category representation 5006D shown in Figure 6A, or a gesture selecting a similar category representation 5006D, causes device 100 to display drug records obtained from both Alpha Health Care and Beta Health Care. In this regard, Figure 6B-1 shows drug records 5018A and 5018B (ABC drugs and DEF drugs) from Alpha Health Care, and two drug records 5018C and 5018D (GHI drugs and JKL drugs) from Beta Health Care, in response to the detection of a tap gesture on the category representation 5006D shown in Figure 6A.

[0213] The representation of multiple health record categories also includes a second representation of a second category among multiple categories (716). Figure 6I shows, for example, a category representation 5006E (health status category) associated with a user's health status.

[0214] Furthermore, when device 100 selects a second representation of a second category while associated with a first healthcare provider and a second healthcare provider, device 100 displays on the display 112 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 (716). Figure 6J-1 shows, for example, an alternative embodiment of Figure 6J. In the embodiment of Figure 6J-1, the user has completed the 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 status category) shown in Figure 6I, or a gesture selecting a similar category representation 5006E, while device 100 is associated with Alpha Health Care and Beta Health Care, causes device 100 to display health status records obtained from both Alpha Health Care and Beta Health Care (716). In this regard, Figure 6J-1 shows health status records 5020A-5020C (cholesterol levels, chronic migraines, and anxiety disorders) from Alpha Health Care and health status record 5020D (arthritis) from Beta Health Care, in response to the detection of a tap gesture on category representation 5006E shown in Figure 6I.

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

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

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

[0218] In some embodiments, multiple health record subcategories include a second representation of a second subcategory of a first category (754). Figure 6D shows, for example, a subcategory representation 5015A (X-ray image subcategory) in response to the detection of a tap gesture with contact 5506 on category representation 5006B (clinical document category) shown in Figure 6C. Furthermore, the selection of a second representation of the second subcategory 5015B of the first category (CT scan subcategory, Figure 6D) causes the device 100 to display multiple health records of the second subcategory of the first category from the first healthcare provider on the display 112 (754). Figure 6E-1 shows the display of X-ray records 5016A and 5016B acquired from Alpha Health Care and X-ray record 5016C acquired from Beta Health Care in response to the detection of a tap gesture on subcategory representation 5015A shown in Figure 6D. In a similar embodiment, where a tap gesture is detected on the subcategory representation 5015B and the user has completed the onboarding process with both Alpha Health Care and Beta Health Care, the CT scan health records obtained from both Alpha Health Care and Beta Health Care are displayed on the display 112. By organizing the user's health records into multiple subcategories (and further subcategory levels) of categories and providing only the health records belonging to those subcategories (or further subcategory levels) in a common user interface, the user is not required to navigate through all the health records in a category to find a specific one, reducing the time the user spends searching for health records. This reduction in the time the user spends searching for health records allows the user to use the device more quickly and efficiently, reducing the device's power consumption and improving battery life.

[0219] In some embodiments, multiple health records of a first category from a second healthcare provider include a fifth health record of the first category from the second healthcare provider (756). Figure 6H-1 shows, for example, a medication record 5018C (GHI drug) obtained from Beta Health Care. In some embodiments, multiple health records of a second category from a second healthcare provider include a sixth health record of the second category from the second healthcare provider (756). Figure 6H-1 shows, for example, an X-ray record 5016C obtained from Beta Health Care. In some embodiments, the fifth health record of the first category from the second healthcare provider and the sixth health record of the second category from the second healthcare provider are records of a third visit to the second healthcare provider (756). Figure 6H-1 shows, for example, that both medication record 5018C and X-ray record 5016C were obtained during a visit to Beta Health Care on September 15, 2017. In some embodiments, in response to receiving a second request to display health records relating to a first user, device 100 simultaneously displays a fifth and a sixth health record on display 112 within a third group, the third group being identified on display 112 by the third date of the third visit to the second healthcare provider, and the first, second, and third groups are displayed simultaneously on display 112 (756). Figure 6H-1 shows, for example, simultaneous display of medication record 5018C and X-ray record 5016C. Both health records were taken during a visit to Beta Health Care on September 15, 2017. Figure 6H-1 also shows simultaneous display of health records from the first and third groups (health records taken during a visit to Alpha Health Care on October 1, 2017, and health records taken during a visit to Beta Health Care on September 15, 2017). In some embodiments, if the dimensions of the display 112 are large, the device 100 displays the health records of a first group, a second group, and a third group simultaneously.This method reduces the cognitive burden on users when viewing health records from multiple healthcare providers by grouping health records based on appointment dates with healthcare providers and arranging different groups based on appointment dates. This method also improves user efficiency by allowing users to identify health records based on appointment dates with healthcare providers. For battery-powered computing devices, power is saved and battery charging intervals are extended by enabling users to browse their health records faster and more efficiently.

[0220] In some embodiments, in response to receiving a first request to display a health record relating to a first user, device 100 displays first content on display 112 that identifies the identification and location of a first healthcare provider (758). Figure 6B shows, for example, medication records 5018A and 5018B (ABC medications and DEF medications). Each medication record 5018A and 5018B identifies Alpha Health Care as the healthcare provider that prescribed the corresponding medication. In some embodiments, each medication record includes further information about the corresponding medication, such as dosage, medication instructions, the name of the physician who prescribed the medication, the location of Alpha Health Care, the location of the nearest pharmacy to receive or replenish the medication, a medication fact sheet, the date the medication is expected to run out, and other preferred content that provides information about the medication. In some embodiments, in response to receiving a second request to display a health record relating to a first user, device 100 displays second content on display 112 that identifies the identification and location of a second healthcare provider (758). Figure 6J displays, for example, health status records 5020A and 5020B (cholesterol levels and chronic migraine). Each health status record 5020A and 5020B identifies Alpha Healthcare Care as the healthcare provider that prescribed medication for the corresponding health condition. In some embodiments, each health status record includes further information about the corresponding health condition, such as the location of Alpha Healthcare. This method improves user efficiency by allowing users to obtain information about healthcare providers without having to contact them. This method also enhances device usability and makes the user device interface more efficient by allowing users to identify the location and other information about the provider without having to perform further input. This method also reduces the burden on existing networks and reduces the amount of communication between users and healthcare providers. For battery-powered computing devices, power is saved and the intervals between battery charges are extended by allowing users to browse their health records faster and more efficiently.

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

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

[0223] In some embodiments, selecting a first representation of a first category while the device 100 is associated with a first healthcare provider and a 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 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). Figure 6K-1 shows, for example, past health records of the user's cholesterol levels obtained from Alpha Health Care (e.g., cholesterol representations 5030B-5030C of the user's cholesterol levels measured on September 1, 2016 and January 1, 2016) and past health records of the user's cholesterol levels obtained from Beta Health Care (e.g., cholesterol representation 5030D of the user's cholesterol levels measured on September 15, 2015) in response to detecting the gesture shown in Figure 6J.

[0224] In some embodiments, selecting a second representation of a second category while the device 100 is associated with a first healthcare provider and a 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 and the second healthcare provider, where 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, Figure 6J shows, for example, health status records 5020A to 5020C (cholesterol levels, chronic migraine, and anxiety disorder, respectively). In some embodiments, if the user selects health status 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 retrieve past health records and creates a more efficient human-machine interface by allowing the user to access past records associated with a health record by allowing the user to access past records by selecting a health record. This method allows users to easily access their past health records by selecting which health records they want to access, improving user efficiency. For battery-powered computing devices, enabling users to view their past health records faster and more efficiently saves power and extends the time between battery charges.

[0225] It should be understood that the specific order of operations described in Figures 7A to 7F is merely illustrative and not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various methods for rearranging the operations described herein. In addition, it should be noted that the details of the process described above with respect to Method 700 (e.g., Figures 7A to 7F) are applicable in a similar manner to the methods described below. For example, Methods 900 and 1100 optionally include one or more 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 the 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 for specific health states that the user can specify as active or inactive within the health record manager. For brevity, these details will not be repeated below.

[0226] Figures 8A–8N illustrate exemplary dashboard user interfaces with aggregated health records according to several embodiments. Figures 8A–8N enable the display of a single dashboard view of a comprehensive overview of a user's current healthcare data, using health records obtained from each healthcare provider for such a user. For convenience, health records are described herein as the health records of a user of device 100. However, health records may be the health records of family members or other individuals associated with the user of the exemplary user interface. For the purposes of Figures 8A–8N, the user has either completed the 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 using the dashboard user interfaces of Figures 8A–8N, stored on device 100, or accessible by device 100. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 9A–9D.

[0227] Some of the following examples are described with reference to input on a touch screen display (combining a touch sensing surface and a display), but in some embodiments, the device detects input on a touch sensing surface 451 separate from the 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, a voice interface, or other suitable interface. For convenience of explanation, some embodiments are discussed with reference to operations performed on a device having a touch sensing display system 112. In such embodiments, the focus selector optionally is the contact of each finger or stylus, a representative point corresponding to the contact of the finger or stylus (e.g., the centroid of each contact or a point associated with each contact), or the centroid of two or more contacts detected on the touch sensing display system 112. However, similar operations are optionally performed on a device having a display 450 and a separate touch sensing surface 451 in response to detecting a contact on the touch sensing surface 451 while displaying the user interface described below, together with the focus selector.

[0228] Figures 8A–8N show an overview of health records displayed within a dashboard, including information derived from the user's current health records, which is hereafter referred to as health record overview information. As used herein, "current health records" refers to any health record of any health information newer than any other health records stored on or accessible by device 100, managed using the dashboard user interface in Figures 8A–8N. The dashboard user interface in Figures 8A–8N also allows the user to view information about the user's health records at different levels of detail. More specifically, the dashboard first displays a health record overview containing health record overview information, and then allows the user to interact with the dashboard to drill down and access further information not included in the health record overview. Similarly, the user can also interact with the dashboard to review their past health records. When device 100 receives updates to existing health records or updates to new health records, the health record overview displayed on the dashboard is periodically updated so that the user is presented with health record overview information based on the most recent health records, but outdated or other potentially irrelevant past health records are not presented.

[0229] Figure 8A shows category representations 5006A to 5006E (allergy, clinical documentation, test results, medication, and health status categories, respectively) and health record summary representations 7005. A health record summary representation 7005 is an affordance that includes text indicating that such an affordance is associated with a health record summary. A health record summary representation 7005 is selectable by the user to view a health record summary. Figures 8A to 8B show the detection of a tap gesture accompanied by contact 7502 on the health record summary representation 7005 in Figure 8A, and the display of the health record summary in the dashboard of Figure 8B on the display 112 in response to the tap gesture.

[0230] FIG. 8B shows displaying on display 112 a health record summary dashboard including health record summary information including a plurality of 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 of the current health records are displayed by category of the health record, regardless of which healthcare provider the current health record is provided from. In this way, the user's latest health information is displayed within the dashboard. In the illustrated embodiment, the health indicator summary includes health indicator records 7012A to 7012C, drug records 7014A to 7014C, and health status records 7016A to 7016D. FIG. 8B also shows displaying health indicator affordance 7011A, drug affordance 7011B, and health status affordance 7011C. In the illustrated embodiment, the health indicator affordance 7011A, the drug affordance 7011B, and the health status affordance 7011C are each selectable by the user to view the user's past health indicator records, drug records, and health status records, respectively.

[0231] In the embodiment shown in Figure 8B, health indicator records 7012A to 7012C are displayed alphabetically based on the type of health indicator record, within the group having health indicator affordance 7011A. Health indicator record 7012A contains the current measurement of the user's blood pressure measured by Beta Health Care on November 1, 2017. In the illustrated embodiment, the measurement on November 1, 2017, 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 levels measured before November 1, 2017, are available, the user can access such past health records by selecting health indicator affordance 7011A. Health indicator record 7012B contains the current measurement of the user's cholesterol level measured by Alpha Health Care on October 1, 2017. Health indicator record 7012C contains the 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, drug records 7014A to 7014C are displayed alphabetically based on the type of drug within groups having drug affordances 7011B. Drug health records 7014A to 7014C are the user's current prescriptions for ABC drugs, DEF drugs, and GHI drugs, respectively. Drug health records 7014A to 7014C also identify the prescription date of the corresponding drug and the healthcare provider who prescribed the drug.

[0233] In the embodiment shown in Figure 8B, health status records 7016A to 7016D are displayed alphabetically based on the type of health status within groups having health status affordances 7011C. Health status records 7016A to 7016D are health records of the user's current health status, specifically anxiety disorder, asthma, high cholesterol, and migraine, respectively. In some embodiments, health status records 7016A to 7016B and 7016D also include information about medications recently prescribed for the corresponding health status (anxiety disorder, asthma, and migraine), even if these medications are individually identified within a single medication group.

[0234] The embodiment shown in Figure 8B shows 10 health records within a health record summary, but in other embodiments, the health record summary may contain a different number of current health records for the user. Furthermore, in some embodiments, not all of the current health records included in the health record summary are displayed on the display 112 simultaneously. In one or more such embodiments, the user performs a gesture to scroll through the current health records displayed in the health record summary. The health records displayed in the illustrated embodiment are grouped by category and arranged alphabetically, but in other embodiments, health records may be grouped or ordered by date, provider, similarity, severity, related biological function or system (e.g., all cardiac measurements followed by all endocrine gland measurements), or based on any other preferred criterion. In one embodiment, the order in which health records are displayed can be changed by the user or provider (e.g., a primary care physician). Figure 8B also shows that a tap gesture with contact 7503 on the health record affordance 5304 is detected to return to the user interface shown in Figure 8A.

[0235] Figure 8B-1 is an alternative embodiment of the healthcare overview dashboard displayed in response to the detection of a tap gesture accompanied by contact 7502 on the health record overview representation 7005 of Figure 8A. Figure 8B-1 includes healthcare overview information presented as an image representation of the health record. More specifically, Figure 8B-1 shows health indicator record 7012A (blood pressure level) and health indicator record 7012B (cholesterol level). In the illustrated embodiment, health indicator record 7012A includes a chart 7712 showing the user's blood pressure level (140 / 90 mmHg) within a certain blood pressure level range. In the illustrated embodiment, the numerical value of the user's blood pressure level is placed near the position on chart 7712 to which the measured blood pressure within this range belongs. In this manner, chart 7712 may indicate where the user's blood pressure level belongs within a blood pressure level range indicating 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 analyze chart 7712, or information regarding the importance of the user's blood pressure level, making it easier for the user to assess their own blood pressure level.

[0236] Health indicator record 7012B includes a bar graph 7714 showing the user's cholesterol level (269 mg / dL) within a certain cholesterol level range. In the illustrated embodiment, the user's cholesterol level value is placed near the position on chart 7714 to which the measured cholesterol within this range belongs. In the illustrated embodiment, the bars containing the user's cholesterol level values ​​are displayed in colors indicating the normality or severity of the user's cholesterol level. For example, the bars may be green, yellow, or red if the user's cholesterol level is less than 200 mg / dL, between 200 mg / dL and 300 mg / dL, or above 300 mg / dL, respectively.

[0237] In the embodiment shown in Figure 8B-1, the health indicator record 7012A includes a blood pressure level displayed in a larger font than other text displayed in the health indicator record 7012A. In this manner, important information such as test measurements and test results may be highlighted to emphasize such information about the user. Similarly, in the health indicator record 7012B, the user's cholesterol level measurement is also displayed in a larger font to make it easier for the user to identify the user's most recent cholesterol level measurement. In other embodiments, the user can quickly identify their health indicator values ​​by highlighting, displaying in a different color, or using bold, italics, or other preferred formatting. Figure 8B-1 also shows the detection of a tap gesture with contact 7504 on the health indicator affordance 5304 to return to the user interface shown in Figure 8A.

[0238] Device 100 periodically receives updates to the user's health records. Figure 8C shows a dashboard of the health record summary, including an update to health metric record 7012A in Figure 8B, which includes the user's blood pressure measurement. As shown in Figure 8C, health metric record 7052A (blood pressure level measured on December 1, 2017) is displayed in the health record summary instead of health metric record 7012A in Figure 8B (blood pressure level measured on November 1, 2017), which includes the user's previous blood pressure measurement. Furthermore, an update badge 7141A is displayed with health metric record 7052A to indicate that health metric record 7052A is an updated health record and to draw the user's attention to health metric record 7052A. Figure 8C also shows that a tap gesture with contact 7505 on health record affordance 5304 is detected to return to the user interface shown in Figure 8A.

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

[0240] Figure 8D shows one embodiment of a health record archive 7058 containing a user's past health records of cholesterol levels. The health record archive is a user interface for viewing past health records. In the illustrated embodiment, the health record archive 7058 includes a health indicator record 7052B containing the user's current cholesterol level measurement, a health indicator record 7012B displayed in the health record summary shown in Figure 8B before the device 100 received the health indicator record 7052B, and further health indicator records 7056A-7056C. Health indicator records 7056A-7056C include the user's cholesterol level measurements taken 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 levels over time is also displayed within the health record archive 7058. Graph 7021 includes multiple bars, each representing a different measurement of the user's cholesterol level associated with health indicator records 7052B, 7012B, and 7056A-7056C. The bars may be displayed in colors indicating the normality of the user's cholesterol level. For example, a bar representing a cholesterol level measurement below 200 mg / dL may be displayed in a first color, a bar representing a cholesterol level measurement between 200 mg / dL and 300 mg / dL may be displayed in a second color, and a bar representing a cholesterol level measurement above 300 mg / dL may be displayed in a third color. Health indicator records 7052B, 7012B, and 7056A-7056C and Graph 7021 provide the user with information about their cholesterol level over time. Figure 8D also shows that detecting a tap gesture with contact 7507 on health record summary affordance 5308 can display the user's health record summary dashboard in Figure 8E.

[0241] Figure 8E shows one embodiment of the health record summary dashboard shown in Figure 8C-1 after the user has viewed the update of the new health record 7052B (cholesterol level) 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 update of the new health record 7052B. Figure 8E further shows the detection of a tap gesture accompanied by contact 7508 on drug affordance 7011B and the display of the health record archive 7057 in Figure 8F in response to the tap gesture.

[0242] Figure 8F shows one embodiment of a health record archive 7057 that includes a user's past health records of medications. In the illustrated embodiment, the health record archive 7057 includes current medication records 7014A-7014C (ABC medications, DEF medications, and GHI medications, respectively) and past medication records 7015A-7015D. Past medication record 7015A is an expired prescription for the currently prescribed GHI medication. Past medication record 7015A also includes the prescription period of the expired prescription 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 (LMN medications, RST medications, and XYZ medications, respectively). In the illustrated embodiments, past medication records 7015A-7015D are displayed in gray, in a smaller or lighter font, or in a different color from current medication records 7014A-7014C to make it easier for the user to distinguish between medications they are currently taking and expired medications. In some embodiments, past medication records 7015A and current medication records 7014C, both containing information about GHI medications, are not displayed simultaneously in the health record archive. In some embodiments, the user selects the current medication record for a medication (such as ABC medication) to access past medication records for the same medication that the user may have taken in the past or at different doses. Figure 8F further illustrates the detection of a tap gesture with contact 7509 on medication record 7014A, and in response to the tap gesture, further information about ABC medication in Figure 8G is displayed.

[0243] Figure 8G shows the display of a fact sheet corresponding to drug record 7014A, which includes instructions, warnings, and active ingredients for ABC drugs. In other embodiments, further information about ABC drugs may also be displayed, such as information about the pharmacy dispensing the drug, alternative sources for dispensing the drug (e.g., pharmacy benefit administrator), co-payment information, insurance coverage information, available generics, drug replenishment deadline or expiration date, instructions or affordances for drug replenishment, dosage, side effects, or images of the drug. Past drug records 7015E and 7015F, which include expired prescriptions for ABC drugs, are displayed in different colors to indicate that these prescriptions are no longer valid. Figure 8G further shows the detection of a tap gesture with contact 7510 on drug archive affordance 5310 to view the health record archive 7057 shown in Figure 8F.

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

[0245] In the embodiment shown in Figure 8H, the updates to the new medication record 7014D for JKL drugs and the new health status record 7016E for arthritis are displayed in the health record summary along with update badges 7141D and 7141E, respectively. Both the medication record 7014D and the health status record 7016E identify the name of the healthcare provider who prescribed the medication and the name of the medication (JKL drug), but the prescription date is missing from both the medication record 7014D and the health status 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 updates to their health record and to inform the user that information is missing from the health record being updated. Incomplete affordances 7020A and 7020B are affordances that the user selects to obtain more detailed information about the incomplete health record.

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

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

[0248] Similar to Figure 8H, Figure 8J also displays a health record summary after receiving an update to the user's health record. While no information is missing from the health record, device 100 may determine that the authenticity or accuracy of the health record should be verified by the user. Device 100 may make such a determination in response to a determination that the information in the health record is unexpected or falls outside a predetermined range, contains data significantly different from data in previous health records, is from a healthcare provider from whom the user has not received health records for a long period, or for any other preferred reason. In yet another embodiment, device 100 may determine that a health record should be verified if it is considered to be inconsistent or contradictory with other health records.

[0249] In the embodiment shown in Figure 8J, updates to a new medication record 7054B (DEF medication) and a new health status record 7056A (anxiety disorder) are received along 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 status record 7056A, device 100, verification affordances 7022A and 7022B are displayed simultaneously with update badges 7141F and 7141G to notify the user that the health status records 7054B and 7056A should be verified, respectively. Verification affordances 7022A and 7022B are affordances that the user selects to obtain more detailed information about the health record that the user is requested to verify.

[0250] Figure 8J further illustrates the detection of a tap gesture accompanied by a touch 7514 on the verification affordance 7022B, and in response to the tap gesture, the notification 7252 of Figure 8K is displayed regarding information on a health record 7056A (anxiety disorder) that the user has been asked to verify. In one embodiment, the notification 7252 is overlaid on the health record summary dashboard of Figure 8J, as shown in Figure 8K. The notification 7252 includes text asking the user to confirm that DEF medication has been prescribed for anxiety disorder. The notification 7252 includes a confirmation affordance 7155 and an inaccurate mark affordance 7154. The user interacts with the confirmation affordance 7155 to confirm that the corresponding health record is accurate, or the user interacts with the inaccurate mark affordance 7154 to indicate that the information is inaccurate. Figure 8K further illustrates the detection of a tap gesture accompanied by a touch 7516 on the confirmation affordance 7155. In some embodiments, in response to detecting a tap gesture involving contact 7516 on the confirmation affordance 7155, the device 100 designates the information in both the drug record 7054B (DEF drug) and the health status record 7056A shown in Figure 8J as accurate, and removes the confirmation affordances 7022A and 7022B from the health record summary dashboard shown in Figure 8J.

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

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

[0253] Figures 9A to 9D are flowcharts illustrating methods for displaying a dashboard user interface with aggregated health records using an electronic device, according to several embodiments. More specifically, Figures 9A to 9D are flowcharts illustrating methods for displaying a user's current and past health records using, for example, the user interfaces of Figures 8A to 8N. As described with reference to Figures 8A to 8N, Method 900 can be used 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, and 500 shown in Figures 1, 3, and 5A, respectively). In one such embodiment, display 112 is a touchscreen display, and a touch-sensitive surface is on or incorporated into display 112. In some embodiments, display 112 is separated from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented using a device having a physical user interface, a voice interface, or other preferred interface. Some operations in Method 900 are optionally combined. Furthermore, the order of some operations can be optionally changed.

[0254] As described below, Method 900 provides an intuitive method for displaying a dashboard user interface with a user's aggregated health records. Method 900 also provides an intuitive method for displaying a user's current and past health records. This method reduces the cognitive burden on the user when browsing current and past health records, creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to browse their current and past health records faster and more efficiently saves power and extends the time between battery charges.

[0255] Method 900 also provides an intuitive way to display a representation of a user's specific health condition and indicate the severity of such condition. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by enabling the user to determine the severity of a specific health condition from the displayed representation of the health condition. This method improves user efficiency by reducing the time required for the user to understand the severity of their health condition. In the case of battery-powered computing devices, power is saved and the interval between battery charges is extended by enabling the user to understand the severity of their health condition faster and more efficiently.

[0256] Device 100 receives a request via one or more input devices to display health record summary information about a first user, while the device is associated with health data about the first user, which includes multiple health record items of a first type and multiple health record items of a second type different from the first type (902). Figure 8A shows, for example, the detection of a tap gesture with contact 7502 on the health record summary representation 7005.

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

[0258] Multiple health record items include a first health record item of a first type on a first date, and the health record summary information does not include multiple health record items of a first type on a date prior to the first date (906). Figure 8B shows, for example, the display of health indicator record 7012A (blood pressure level) within the health record summary. Health indicator record 7012A includes the user's blood pressure measurement 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). Figure 8B-1 also shows that a health indicator record 7012A (blood pressure level) is displayed 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 certain blood pressure level range. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by providing the user with a representation (such as an image, graph, or chart) that allows the user to determine the severity of their health condition based on the representation. This method also improves user efficiency by allowing the user to quickly identify the severity of their condition from the representation. In the case of battery-powered computing devices, power is saved and the interval between battery charges is extended by allowing the user to identify the severity of their condition more quickly and efficiently.

[0260] In some embodiments, the first health record item includes a representation of the first user's state over a period of time (910). Figure 8D shows, for example, the display of graph 7021, which is a graph of the user's cholesterol levels over two years. In some embodiments, the health indicator record 7012A (blood pressure level) in Figure 8B also includes graph 7021. By providing a graph of the user's state over time, the user can determine whether their state has changed over time without having to navigate multiple user interfaces to access data showing the user's state over different periods, reducing the cognitive burden on the user and creating a more efficient human-machine interface. In the case of battery-powered computing devices, enabling the user to identify their state over time more quickly and efficiently saves power and extends the time between battery charges.

[0261] Multiple health record items also include a second health record item of a second type with a second date different from the first date, and the health record summary information does not include multiple health record items of a second type with a date earlier than the second date (912). Figure 8B shows, for example, the display of medication record 7014A. Medication record 7014A is the health record of the user's prescription for ABC medication prescribed to the user on October 1, 2017. Prescriptions for ABC medication with a date earlier than October 1, 2017 are not included in the health record summary.

[0262] In some embodiments, the health data relating to the first user includes multiple health record items of a third type distinct from the first and second types (914). Figure 8B shows, for example, the display of health status record 7016D. Health status record 7016D is a health record of the user's migraine status. In some embodiments, device 100 simultaneously displays the first health record item, the second health record item, and the third health record item of the third type for a third date within the health record summary information (914). Figure 8B shows, for example, the simultaneous display of health indicator record 7012A (blood pressure level), medication record 7014A (ABC medication), and health status record 7016D (migraine) within the health record summary. Furthermore, in some embodiments, the health record summary information does not include multiple health record items of the third type for dates prior to the third date (914). Health status record 7016D includes information about ABC medication prescribed to the user on October 1, 2017. Previous health records related to the user's migraine condition are not included in the health record summary. Similarly, medication record 7014C in Figure 8B is the health record of the user's prescription for a GHI medication prescribed to the user on September 15, 2017. Prescriptions for GHI medications dated before September 15, 2017 are also not included in the health record summary. By displaying multiple types of health records in a common interface, users can browse multiple types of health records without navigating between multiple user interfaces, creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to browse their records faster and more efficiently saves power and extends the time between battery charges.

[0263] In some embodiments, the health data includes health data associated with multiple healthcare providers of a first user, where a first health record item is associated with a first healthcare provider among the multiple healthcare providers, and a second health record item is associated with a second healthcare provider among the multiple providers (916). Figure 8B shows, for example, that health indicator record 7012A (blood pressure level) is obtained from Beta Health Care and medication record 7014A (ABC medication) is obtained from Alpha Health Care. By displaying multiple health records from multiple healthcare providers in a common interface, users can browse records from different healthcare providers without having to navigate between multiple user interfaces, creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to browse their health records faster and more efficiently saves power and extends the time between battery charges.

[0264] In some embodiments, the multiple health record items include a fourth type of fourth health record item on a fourth date, the first and fourth health record items are associated with a first healthcare provider, and the first and fourth dates are the dates of the first and second visits to the first healthcare provider (918). Figure 8B shows, for example, health indicator record 7012A (blood pressure level) and health status record 7016B (asthma). Both health records were obtained from Beta Health Care. Furthermore, health indicator record 7012A was obtained during a visit to Beta Health Care on November 1, 2017, and health status record 7016B was obtained during a visit to Beta Health Care on September 15, 2017. By displaying multiple health records obtained on different dates in a common interface, users can browse health records obtained on different dates without having to navigate between multiple user interfaces, creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to browse their health records faster and more efficiently saves power and extends the time between battery charges.

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

[0266] Furthermore, in some embodiments, the device 100 displays an updated health record summary for the first user on the display 112 in response to receiving a second request, including displaying the second and third health record items simultaneously without displaying the first health record item (920). Figure 8C shows, for example, an updated health record summary including health indicator record 7052A (blood pressure level). Health indicator record 7052A includes the user's blood pressure measurement taken on December 1, 2017. Health indicator record 7012A includes the user's blood pressure measurement taken on an earlier date. After receiving the user's more recent blood pressure measurement, the device 100 displays health indicator record 7052A in the updated health record summary instead of health indicator record 7012A. By displaying a health record summary that is updated over time and including updates to the user's existing health record, the user can access their updates in a common interface and obtain their most recent health record without having to navigate multiple user interfaces. This method also reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to access their current health record through a health record summary. This method improves user efficiency by allowing the user to access their current health record through a health record summary. For battery-powered computing devices, power is saved and battery charging intervals are extended by allowing users to view their current health record faster and more efficiently.

[0267] In some embodiments, after the device 100 displays a health record including a first health record item and a second health record item, it receives a new health record item for the first user's health data, the new health record item having a date later than the first and second dates (922). In some embodiments, the device 100 receives drug record 7014D (JKL drug) shown in Figure 8H before displaying drug record 7014D in the drug record summary shown in Figure 8H. In some embodiments, after receiving the new health record item, the device 100 receives a third request via one or more input devices to display health record summary information about the first user (922). In some embodiments, the user interface shown in Figure 8A is displayed on the display 112 when the device 100 receives drug record 7014D. In such embodiments, the user views the health record summary shown in Figure 8H by performing gestures similar to the tap gesture shown in Figure 8A.

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

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

[0270] In some embodiments, the device (100) displays a health record archive for a first user on display 112 (926), including simultaneously displaying a first type of health record item with the most recent date and one or more first type of health record items with dates earlier than the first date, in response to receiving a first request to display a first type of health record item not shown in the overview. Figure 8D shows, for example, the simultaneous display of health metric record 7052B, which includes the user's most recent cholesterol measurement taken on December 1, 2017, and health metric records 7056A-7056C, which include previous measurements of the user's cholesterol levels. By displaying the user's current and past health records simultaneously, it becomes unnecessary to navigate multiple user interfaces to retrieve both the user's current and past health records. This method reduces the cognitive burden on the user and creates a more efficient human-machine interface by allowing the user to view their current and past health records within a single user interface. This method improves user efficiency by allowing users to view their current and past health records without having to navigate different user interfaces to access them. For battery-powered computing devices, enabling users to view their current and past health records faster and more efficiently saves power and extends the time between battery charges.

[0271] In some embodiments, in response to receiving a first request to display a first type of health record item not shown in the overview, device 100 displays a fourth type of health record item in the health record archive on display 112 (928). Figure 8D shows, for example, the display of a graph 7021 of the user's cholesterol levels over time in response to the detection of a tap gesture shown in Figure 8C-1. In some embodiments, the fourth health record item includes a representation of health indicators measured on a fourth date prior to a first date (928). The graph 7021 includes current and previous measurements of the user's cholesterol levels. In other embodiments, one or more of the health indicator records 7056A-7056C (cholesterol levels) shown in Figure 8D also include a representation of the user's previous cholesterol levels (such as a bar graph or scale). By displaying representations of past health indicators, the user can determine their health indicators over time without having to contact their healthcare provider, thus freeing up communication systems, reducing network bandwidth, and saving energy. For battery-powered computing devices, enabling users to retrieve historical information about their health indicators faster and more efficiently saves power and extends the time between battery charges.

[0272] In some embodiments, after displaying health record summary information including a first health record and a second health record, device 100 receives a third type of third health record item having a third date later than the first and second dates (930). Health status record 7016E (JKL medication) in Figure 8H was received by device 100 after it received the health indicator record 7012A (blood pressure level) and medication record 7014A (ABC medication) in Figure 8B. Health status record 7016E includes information about the user's arthritis status and information about the JKL medication prescribed to the user on November 15, 2017. The date of health status record 7016E is later than that of health indicator record 7012A (November 1, 2017) and medication record 7014A (October 1, 2017). In some embodiments, device 100 updates the health record summary information to include a third health record item in response to a request to view the health record summary information, so that the first, second, and third health record items are displayed simultaneously within the health record summary information (930). As shown in Figure 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 status record 7016E (e.g., the third health record item) are displayed simultaneously within the health record summary. By displaying a health record summary that includes multiple types of health records, the user can view multiple types of health records within 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. In the case of battery-operated computing devices, power is saved and the interval between battery charging is extended by allowing the user to view their current health records faster and more efficiently.

[0273] In some embodiments, in response to a request to display health record summary information, device 100 displays an incomplete record affordance within the health record summary information based on a determination that a health record item of the health data for a first user is incomplete (932). Figure 8H shows, for example, the display of an incomplete affordance 7020A along with the drug record 7014D (JKL drug) after determining that information is missing from the drug record 7014D. This method reduces the number of errors caused by the user relying on records with missing information. This method reduces the cognitive burden on the user by identifying health records with missing information to the user. This method improves user efficiency by allowing the user to optionally ignore records with missing information when reviewing their health records. In the case of battery-operated computing devices, power is saved and the interval between battery charges is extended by allowing the user to review their health records faster and more efficiently.

[0274] In some embodiments, device 100 receives user verification of the accuracy of one of several health record items displayed in the health record summary information via one or more input devices (934). Figure 8K shows the detection of a tap gesture with contact 7516 on a confirmation affordance 7155 to confirm, for example, that a DEF drug was prescribed for an anxiety disorder. In response to receiving user verification of the accuracy of this health record item, device 100 provides user verification to the healthcare provider associated with this health record item (934). In some embodiments, in response to detecting user input as shown in Figure 8J, device 100 automatically notifies Alpha Health Care that the DEF drug has been 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 health records. This method improves user efficiency by allowing the user to verify the accuracy of specific health records without waiting for verification from a healthcare provider. This method also reduces the bandwidth required to send requests to healthcare providers' electronic systems by reducing the need to request healthcare providers to verify health records. This method also reduces the power consumption of electronic systems by reducing the burden on healthcare providers' electronic systems to process requests. By automatically notifying healthcare providers' electronic systems that health records from healthcare providers have been verified by users, the need for healthcare providers to contact users or their devices (via electronic systems or other telecommunication means) to verify the accuracy or completeness of health records is reduced. As a result, communication systems are freed up, network bandwidth is reduced, and energy is saved.

[0275] In some embodiments, device 100 receives a first user instruction via one or more input devices indicating that one of several health record items included in the health record summary information is inaccurate (936). Figure 8M shows, for example, detecting an inaccurate tap gesture with contact 7520 on mark affordance 7154 to mark the drug record 7014E (XYZ drug) in Figure 8L as inaccurate. In some embodiments, in response to receiving the first user instruction, device 100 removes this health record item from the health record summary information, and after removal from the health record summary information, this health record item is not included in the health record summary information (936). Figure 8N shows, for example, an updated health record summary after the tap gesture shown in Figure 8M is performed. As shown in Figure 8N, the drug record 7014E in Figure 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 inaccurate or incomplete health records. This method improves user efficiency by reducing the time users spend checking inaccurate or incomplete records. For battery-powered computing devices, it saves power and extends the time between battery charges by allowing users to check their health records faster and more efficiently. This method also reduces the number of user errors caused by users relying on inaccurate or inaccurate health records.

[0276] In some embodiments, in response to receiving a first user instruction, device 100 automatically transmits a request for updated information regarding health record items from the healthcare provider's computer system without further user input (938). In some embodiments, when device 100 detects an inaccuracy and a mark affordance 7154 in Figure 8K, it designates the health record as an inaccurate health record and automatically transmits a request for the health record to the healthcare provider. 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. As a result, the communication system is freed up, network bandwidth is reduced, and energy is saved. Furthermore, the 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, updating inaccurate health records faster and more efficiently saves power and extends the time between battery charges.

[0277] In some embodiments, device 100 receives information to update a first health record item via one or more input devices (940). Figure 8I shows, for example, a user making edits to health indicator record 7014D (JKL drug). In some embodiments, device 100 receives edits to health indicator record 7014D after the user performs the tap gesture shown in Figure 8I, which involves touching 7512 on the edit affordance 7152 in Figure 8I. In some embodiments, after receiving information to update the first health record item, device 100 receives a second request to display health record summary information about the first user (940). In some embodiments, after editing health indicator record 7014D, the user selects the health record summary representation 7005 to view the health record summary. In other embodiments, a tap gesture involving touching on the edit affordance 7152 or ignore affordance 7153 in Figure 8I also constitutes a request to display the health record summary. In some embodiments, device 100 displays an updated health record summary for a first user in response to a request to display health record summary information for a first user, including simultaneously displaying updated first and second health record items that reflect changes to the first health record item (940). Figure 8J shows, for example, an updated health record summary that includes information about medication record 7014D, which was previously missing from the health record summary shown in Figure 8H. By displaying updates to health records within a common interface along with other current health records, a more efficient human-machine interface is created, allowing the user to view their current health records within a common interface without having to navigate between different user interfaces to retrieve updates to different health records. For battery-operated computing devices, power is saved and battery charging intervals are extended by enabling users to browse their health records faster and more efficiently.

[0278] It should be understood that the specific order of operations described in Figures 9A to 9D is merely illustrative and not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various methods for rearranging the operations described herein. In addition, the details of the processing described above with respect to Method 900 (e.g., Figures 9A to 9D) 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 characteristics of the various methods described above with reference to Method 900. For example, the methods described above with reference to 900 for displaying a health record summary including the current health record and for displaying past records within other user interfaces are optionally used by Method 700 to display aggregated health records and optionally used by Method 1100 to display health records within the health record manager. For brevity, these details will not be repeated below.

[0279] Figures 10A to 10Q illustrate exemplary health record managers according to some embodiments. More specifically, Figures 10A to 10Q show displays of a health record manager that allow a user to specify and manage the status of an activity associated with a particular health record. The user interface in these figures is used to illustrate the processes described below, including the processes in Figures 11A to 11E.

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

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

[0282] In one or more embodiments of Figures 10A to 10Q, an inactive health record as used herein is any health record other than an active health record. Optionally, health records designated as inactive by the user are hidden within the Health Record Manager dashboard user interface but are displayed within other user interfaces of the Health Record Manager that contain more detailed information about the user's health records, while active health records are displayed within the Health Record Manager dashboard user interface. The status of a health record may be changed by the user from active to inactive, for example, when the user's asthma symptoms disappear. Similarly, the status of a health record may be changed by the user from inactive to active, for example, when the user's asthma symptoms recur. 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 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 users to set reminders to perform various tasks related to specific health records. Reminders may be used, for example, to remind users to take prescribed medications at a set time, to replenish prescribed medications, or to track upcoming appointments with doctors or other healthcare professionals. While embodiments in Figures 10A to 10Q are described in relation to the management of health records, more specifically health status 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 test records, clinical records, or allergy records.

[0284] Similar to Figure 8B, Figure 10A shows a display on display 112 of a health record summary dashboard containing 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 status records 9016A-9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively). Figure 10A also shows the display of health indicator affordances 9011A, medication affordances 9011B, and health status affordances 9011C. In the illustrated embodiment, health indicator affordance 9011A, drug affordance 9011B, and health status affordance 9011C are selectable by the user to view the health indicator archive, drug archive, and health status archive, respectively. In the embodiment shown in Figures 10A to 10Q, the health indicator archive, drug archive, and health status archive are health record archives that include current and past health records belonging to the corresponding categories.

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

[0286] In the embodiment shown in Figure 10A, drug records 9014A to 9014D are displayed alphabetically based on the type of drug. Drug health records 9014A to 9014D are the user's current prescriptions for ABC drugs, DEF drugs, GHI drugs, and LMN drugs, respectively. Drug health records 9014A to 9014D also identify the prescription date of the corresponding drug and the healthcare provider who prescribed the drug.

[0287] In the embodiment shown in Figure 10A, health status records 9016A to 9016D are displayed alphabetically based on the type of health status. Each health status record 9016A to 9016D contains information about the user's current health status, including anxiety disorder, asthma, high cholesterol, and migraines. In some embodiments, health status records 9016A to 9016D also include information about medications recently prescribed for the corresponding health status (anxiety disorder, asthma, high cholesterol, and migraines), even if these medications are individually identified within a single medication group. Figure 10A further illustrates the detection of a tap gesture accompanied by contact 9502 on a health status affordance 9011C, and the display of the health status archive 9058 in Figure 10B in response to the tap gesture.

[0288] Figure 10B shows one embodiment of a health status archive 9058 that includes a health record of the user's health status and a status toggle for specifying whether the health record is active or inactive. In the illustrated embodiment, the health status archive 9058 includes health status records 9016A to 9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively). In the illustrated embodiment, health status record 9016A includes the user's anxiety disorder, medications prescribed to treat the user's anxiety disorder (DEF medications), the date of the initial diagnosis, and information regarding the next scheduled visit to Alpha Health Care for the user's anxiety disorder. Health status record 9016B includes the user's asthma, medications prescribed to treat the user's asthma (GHI medications), the date of the initial diagnosis, and information regarding the next scheduled visit to Beta Health Care for the user's asthma. Health status record 9016C includes information about the user's high cholesterol, the measured cholesterol level and date of the cholesterol test, the medication prescribed to treat the user's high cholesterol (LMN medication), the date of the initial diagnosis, and information about the user's next scheduled visit to Alpha Health Care regarding the user's high cholesterol. Health status record 9016D includes information about the user's migraines, the medication prescribed to treat the user's migraines (ABC medication), the date of the initial diagnosis, and information about the user's next scheduled visit to Alpha Health Care regarding the user's migraines. In other embodiments, health status records 9016A to 9016D each include further information about the corresponding health condition, such as the names of medications previously prescribed for that health condition, the name of the physician or other healthcare professional the user will see for that health condition, a list of symptoms for that health condition, and other useful information related to that health condition.

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

[0290] In some embodiments, status toggles 9022A-9022D (relating to anxiety disorders, asthma, high cholesterol, and migraines, respectively) are not displayed within the health status archive 9058. In one or more such embodiments, the health status archive 9058 includes status designation affordances (not shown), which are affordances with which the user interacts to access the status toggles 9022A-9022D. For example, in response to the detection of a gesture for selecting a status designation affordance, device 100 overlays another user interface containing the status toggles 9022A-9022D on top of a portion of the user interface shown in Figure 10B. In other embodiments, the status toggles are displayed within a health record summary along with the corresponding health record, allowing the user to specify the status of a particular health condition without drilling down into the health status archive 9058. In yet another embodiment, the user selects an individual health status record, such as one of health status records 9016A to 9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively), and displays the respective status toggles 9022A, 9022B, 9022C, or 9022D for such health status records. In one or more such embodiments, after the user interacts with the status toggles displayed in the health record summary, a notification similar to a notification prompting the user to confirm a change in the status of the corresponding health status is displayed. In such embodiments, the device 100 changes the health status after detecting input confirming a change in the health status to avoid accidental input.

[0291] In the illustrated embodiment, status toggles 9022A to 9022C (representing anxiety disorder, asthma, and high cholesterol, respectively) indicate that the corresponding health condition is active. Figure 10B further illustrates the detection of a swipe gesture involving a touch 9602 on status toggle 9022D (representing migraine) and a movement of the touch from position 9602A to position 9602B to designate migraine as an inactive health condition. Figure 10C shows the display of a notification 9252 that prompts the user to confirm the user's decision...

Claims

1. It is a method, In an electronic device having a display and one or more input devices, The electronic device is associated with a first healthcare provider and is not associated with a second healthcare provider, and while it is doing so, it receives a first request via one or more input devices to display a health record relating to a first user. In response to receiving the first request to display health records relating to the first user, the display shows representations of a plurality of health record categories, wherein the representations of the plurality of health record categories are A first representation of a first category among the aforementioned 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 with the second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display; A second representation of a second category among the aforementioned multiple 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 multiple health records of the second category from the first healthcare provider on the display. Including, After displaying the representations of the plurality of health record categories and after the electronic device has been associated with the second healthcare provider, a second request to display the health records relating to the first user is received via one or more input devices. In response to receiving a second request to display health records relating to the first user, the representation of the plurality of health record categories is displayed on the display, wherein the representation of the plurality of health record categories is The first representation of the first category among 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 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 on the display, The second representation of the second category among 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 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 on the display, Including, A method that includes this.

2. Receiving a first selection of the first representation of the first category via one or more input devices, In response to receiving the first selection, the display shows representations of multiple subcategories of the first health record category, wherein the representations of multiple subcategories of the first health record category are A first representation of a first subcategory of the first category, wherein selecting the first representation of the first subcategory of the first category causes the electronic device to display a plurality of health records of the first subcategory of the first category from the first healthcare provider on the display. A second representation of a second subcategory of the first category, wherein selecting the second representation of the second subcategory of the first category causes the electronic device to display a plurality of health records of the second subcategory of the first category from the first healthcare provider on the display. Including, The method according to claim 1, further comprising:

3. The method according to 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 the representations of the aforementioned multiple health record categories on the display is Displaying on the display a 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 that is not included in the first content. Displaying on the display a second content summarizing the second category and a second category information affordance of the second category, wherein selecting the second category information affordance causes the electronic device to display on the display further content associated with the second category that is not included in the second content. The method according to any one of claims 1 to 3, further comprising:

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

6. The plurality of health records of the first category from the first healthcare provider include a first health record of the first category from the first healthcare provider and a second health record of the first category from the first healthcare provider. The plurality of health records of the second category from the first healthcare provider include a third health record of the second category from the first healthcare provider and a fourth health record of the second category from the first healthcare provider. The first health record of the first category and the third health record of the second category from the first healthcare provider are records of the first visit to the first healthcare provider. The second health record of the first category from the first healthcare provider and the fourth health record of the second category from the first healthcare provider are records of the second visit to the first healthcare provider. The method described above is In response to receiving a first request to display a health record relating to the first user, the first health record and the third health record are simultaneously displayed on the display within a first group, wherein the first group is identified on the display by the first date of the first medical examination. In response to receiving a first request to display a health record relating to the first user, the second health record and the fourth health record are simultaneously displayed on the display within a second group, wherein the second group is identified on the display by the second date of the second medical examination, and the first date is different from the second date. The method according to any one of claims 1 to 5, further comprising:

7. The plurality of health records of the first category from the second healthcare provider include a fifth health record of the first category from the second healthcare provider. The plurality of health records of the second category from the second healthcare provider include a sixth health record of the second category from the second healthcare provider, The fifth health record of the first category and the sixth health record of the second category from the second healthcare provider are records of the third visit to the second healthcare provider. The method further includes, in response to receiving a second request to display a health record relating to the first user, simultaneously displaying the fifth health record and the sixth health record in a third group on the display, The third group is identified on the display by the 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 the display. The method according to claim 6.

8. The first health record of the first category from the first healthcare provider and the second health record of the first category from the first healthcare provider are displayed in the first color. The third health record of the second category from the first healthcare provider and the fourth health record of the second category from the first healthcare 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 of the first category from the first healthcare provider, Displaying a first update badge associated with the first health record of the first group on the display, wherein the first update badge and the first health record are displayed simultaneously within a first area of ​​the display. The method according to any one of claims 6 to 8, further comprising:

10. In response to receiving a first request to display health records relating to the first user, the system displays on the display first information that identifies the first healthcare provider and their location, In response to receiving a second request to display health records relating to the first user, the second content identifying the second healthcare provider and its location is displayed on the display, The method according to any one of claims 1 to 9, further comprising:

11. While the electronic device is associated with the first healthcare provider, the selection of the first representation of the first category is detected. In response to the electronic device detecting the selection of the first representation of the first category while it is associated with the first healthcare provider, the first representation of the first health record from the plurality of health records of the first category from the first healthcare provider is displayed on the display, The first representation of the first health record includes a numerical value within a certain range. The aforementioned numerical value indicates the health status of the first user, and the aforementioned numerical range indicates a normal numerical range related to the health. That thing, The method according to any one of claims 1 to 10, including the method described in any one of claims 1 to 10.

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

13. The method according to any one of claims 1 to 12, further comprising displaying a second representation of a second health record of the plurality of health records of the first category from the first healthcare provider, wherein the second representation of the second health record includes a graph showing the status of the first user over a period of time.

14. The method according to any one of claims 1 to 13, further comprising displaying a third representation of a third health record among the plurality of health records of the first category from the first healthcare provider, wherein the third representation of the third health record includes an image showing the medical record of the first user.

15. Receiving an update to a health record in the aforementioned first health record category, After receiving the update to the health record of the first category, in response to receiving at least one of the following: a first request to display the health record relating to the first user and a second request to display the health record relating to the first user, a second update badge associated with the first category is displayed on the display, wherein the second update badge and the first representation of the first category are displayed simultaneously within a first area of ​​the display. The method according to any one of claims 1 to 14, further comprising:

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

17. The method according to 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 the representation of the health record of the first health record category on the display, and the second update badge is visually associated with the representation of the health record of the first health record category.

18. The method according to any one of claims 15 to 17, wherein displaying the second update badge on the display includes displaying the content of the update to the health record on the second update badge.

19. Receiving a request to select the second update badge via one or more input devices, In response to receiving the request to select the second update badge, the update to the health record in the first health record category is displayed on the display, The method according to any one of claims 15 to 18, further comprising:

20. Displaying the update to the health record on the display includes simultaneously displaying the update to the health record and the recommended affordance associated with the health record, and the method is Receiving a request to select the aforementioned recommended affordance via one or more input devices, In response to receiving the request to select the recommended affordance, the recommended action is displayed on the display, wherein the recommended action is based on the update to the health record. The method according to claim 19, further comprising:

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

22. Receiving an update to a health record in the aforementioned first health record category, In response to receiving the update to the aforementioned health record, In accordance with the determination that the importance of the update is greater than a threshold, a notification of the update is displayed on the display. In accordance with the determination that the importance of the update is below the threshold, the notification of the update is not displayed on the display. The method according to 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 with the second healthcare provider causes the electronic device to display past health records associated with the first category from the first healthcare provider on the display, wherein the past health records associated with the first category include the plurality of health records of 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 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, and the past health records associated with the second category include the plurality of health records of 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, wherein 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. 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 the second healthcare provider, wherein the past health records associated with the second category are 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. The method according to any one of claims 1 to 22.

24. It is an electronic device, The display and One or more input devices, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, The electronic device is associated with a first healthcare provider and is not associated with a second healthcare provider, and while it is doing so, it receives a first request via one or more input devices to display a health record relating to a first user. In response to receiving the first request to display health records relating to the first user, the display shows representations of a plurality of health record categories, wherein the representations of the plurality of health record categories are A first representation of a first category among the aforementioned 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 with the second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display; A second representation of a second category among the aforementioned multiple 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 multiple health records of the second category from the first healthcare provider on the display. Including, After displaying the representations of the plurality of health record categories and after the electronic device has been associated with the second healthcare provider, a second request to display the health records relating to the first user is received via one or more input devices. In response to receiving a second request to display health records relating to the first user, the representation of the plurality of health record categories is displayed on the display, wherein the representation of the plurality of health record categories is The first representation of the first category among 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 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 on the display, The second representation of the second category among 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 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 on the display, Including, Electronic devices, including instructions for use.

25. A non-temporary computer-readable storage medium for storing one or more programs, wherein the one or more programs are executed by one or more processors of an electronic device having a display and one or more input devices, and the electronic device is configured to store one or more programs. The electronic device is associated with a first healthcare provider and is not associated with a second healthcare provider, and while it is doing so, it receives a first request via one or more input devices to display a health record relating to a first user. In response to receiving the first request to display health records relating to the first user, the display shows representations of a plurality of health record categories, wherein the representations of the plurality of health record categories are A first representation of a first category among the aforementioned 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 with the second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display; A second representation of a second category among the aforementioned multiple 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 multiple health records of the second category from the first healthcare provider on the display. Including, After displaying the representations of the plurality of health record categories and after the electronic device has been associated with the second healthcare provider, a second request to display the health records relating to the first user is received via one or more input devices. In response to receiving a second request to display health records relating to the first user, the representation of the plurality of health record categories is displayed on the display, wherein the representation of the plurality of health record categories is The first representation of the first category among 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 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 on the display, The second representation of the second category among 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 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 on the display, Including, A non-temporary computer-readable storage medium containing instructions to execute a command.

26. It is an electronic device, The display and One or more input devices, Means for receiving a first request to display a health record relating to a first user via one or more input devices while the electronic device is associated with a first healthcare provider and not with a second healthcare provider, In response to receiving a first request to display a health record relating to the first user, means for displaying representations of a plurality of health record categories on the display, wherein the representations of the plurality of health record categories are A first representation of a first category among the aforementioned 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 with the second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display; A second representation of a second category among the aforementioned multiple 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 multiple health records of the second category from the first healthcare provider on the display. Means including, After displaying representations of the plurality of health record categories and after the electronic device has been associated with the second healthcare provider, means for receiving a second request via one or more input devices to display health records relating to the first user, In response to receiving a second request to display health records relating to the first user, means for displaying representations of the plurality of health record categories on the display, wherein the representations of the plurality of health record categories are The first representation of the first category among 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 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 on the display, The second representation of the second category among 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 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 on the display, Means including, An electronic device equipped with the following features.

27. An information processing device for use in an electronic device having a display and one or more input devices, Means for receiving a first request to display a health record relating to a first user via one or more input devices while the electronic device is associated with a first healthcare provider and not with a second healthcare provider, In response to receiving a first request to display a health record relating to the first user, means for displaying representations of a plurality of health record categories on the display, wherein the representations of the plurality of health record categories are A first representation of a first category among the aforementioned 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 with the second healthcare provider causes the electronic device to display a plurality of health records of the first category from the first healthcare provider on the display; A second representation of a second category among the aforementioned multiple 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 multiple health records of the second category from the first healthcare provider on the display. Means including, After displaying representations of the plurality of health record categories and after the electronic device has been associated with the second healthcare provider, means for receiving a second request via one or more input devices to display health records relating to the first user, In response to receiving a second request to display health records relating to the first user, means for displaying representations of the plurality of health record categories on the display, wherein the representations of the plurality of health record categories are The first representation of the first category among 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 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 on the display, The second representation of the second category among 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 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 on the display, Means including, An information processing device equipped with the following features.

28. It is an electronic device, The display and One or more input devices, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 1 to 23.

29. A non-temporary computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by one or more processors of an electronic device having a display and one or more input devices, include instructions causing the electronic device to perform the method according to any one of claims 1 to 23.

30. It is an electronic device, The display and One or more input devices, Means for carrying out any of the methods described in claims 1 to 23, An electronic device equipped with the following features.

31. An information processing device for use in an electronic device having a display and one or more input devices, The means for carrying out any of the methods described in claims 1 to 23, Information processing device.

32. It is a method, In an electronic device having a display and one or more input devices, While the electronic device is associated with health data relating to a first user, which 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, it receives a request via one or more input devices to display a summary of health record information relating to the first user. In response to receiving the aforementioned request, display a summary of the health record information relating to 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 any multiple health record items of the first type for dates earlier than the first date, A second health record item of the second type for a second date different from the first date, wherein the health record summary information does not include multiple health record items of the second type for dates earlier than the second date, This includes displaying multiple health record items simultaneously, A method that includes this.

33. The method according to claim 32, wherein the health data relating to 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 the third health record item of the third type for a third date, and the health record summary information does not include a plurality of health record items of the third type for dates earlier than the third date.

34. The method according to claim 32 or 33, wherein the health data includes health data associated with a plurality of healthcare providers of the first user, the first health record item is associated with a first healthcare provider among the plurality of healthcare providers, and the second health record item is associated with a second healthcare provider among the plurality of providers.

35. The method according to any one of claims 32 to 34, wherein the plurality of health record items include a fourth type of fourth health record item for 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 the dates of the 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 on a third date later than the first date, After receiving the third health record item, a second request is received via one or more input devices to display a summary of the health record information relating to the first user. In response to receiving the second request, display updated health record summary information relating to the first user on the display, including displaying the second health record item and the third health record item simultaneously without displaying the first health record item; The method according to 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 item of the health data relating to the first user, wherein the date of the new health record item is later than the first date and the second date, After receiving the new health record item, a third request is received via one or more input devices to display a summary of the health record information relating to the first user. In response to receiving the third request, the updated health record summary information relating to the first user is displayed on the display, which includes simultaneously displaying the first health record item, the second health record item, and the new health record item. The method according to any one of claims 32 to 36, further comprising:

38. While the health record summary information for the first user is displayed on the display, Receiving a first request via one or more input devices to display the first type of multiple health record items not shown in the summary, In response to receiving a first request to display the first type of multiple health record items not shown in the summary, the display shows the first type of multiple health record items for a date earlier than the first date, The method according to any one of claims 32 to 37, further comprising:

39. In response to receiving a first request to display the plurality of health record items of the first type not shown in the summary, the health record archive relating to the first user is displayed on the display, further comprising simultaneously displaying the health record item of the first type with the most recent date and one or more of the plurality of health record items of the first type with dates earlier than the first date. The method according to claim 38.

40. In response to receiving a first request to display the plurality of health record items of the first type not shown in the summary, a fourth health record item of the first type is displayed on the display within the health record archive, further comprising the fourth health record item including a representation of a health indicator measured on a fourth date prior to the first date. The method according to claim 39.

41. After displaying the health record summary information, which includes the first health record and the second health record, Receiving a third type of third health record item on a third date that is later than the first date and the second date, In response to a request to view the health record summary information, the health record summary information is updated to include the third health record item, wherein the first health record item, the second health record item, and the third health record item are displayed simultaneously within the health record summary information. The method according to any one of claims 32 to 40, further comprising:

42. The method according to any one of claims 32 to 41, wherein the first health record item includes an expression of the severity of the first user's condition.

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

44. In response to the request to display health record summary information, the system further includes displaying incomplete record affordances within the health record summary information, based on the determination that the health record items of the health data relating to the first user are incomplete. The method according to any one of claims 32 to 43.

45. The system receives user verification of the accuracy of one of the multiple health record items displayed in the health record summary information via one or more input devices, In response to receiving the user verification of the accuracy of the health record item, to provide the user verification to the healthcare provider associated with the health record item, The method according to any one of claims 32 to 44, further comprising:

46. Receiving a first user instruction via one or more input devices indicating that one of the multiple health record items included in the health record summary information is inaccurate, In response to receiving the first user instruction, the health record item is excluded from the health record summary information, and the health record item is not included in the health record summary information after being excluded from it. The method according to any one of claims 32 to 45, further comprising:

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

48. Receiving information to update the first health record item via one or more input devices, After receiving the information to update the first health record item, a second request is received to display a summary of health record information for the first user. In response to receiving the request to display a health record summary information relating to the first user, the updated health record summary relating to the first user is displayed, which includes simultaneously displaying the updated first health record item and the second health record item that reflect the changes to the first health record item, The method according to any one of claims 32 to 47, further comprising:

49. It is an electronic device, The display and One or more input devices, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, While the electronic device is associated with health data relating to a first user, which 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, it receives a request via one or more input devices to display a summary of health record information relating to the first user. In response to receiving the aforementioned request, display a summary of the health record information relating to 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 any multiple health record items of the first type for dates earlier than the first date, A second health record item of the second type for a second date different from the first date, wherein the health record summary information does not include multiple health record items of the second type for dates earlier than the second date, This includes displaying multiple health record items simultaneously, An electronic device containing instructions for performing an action.

50. A non-temporary computer-readable storage medium for storing one or more programs, wherein the one or more programs are executed by one or more processors of an electronic device having a display and one or more input devices, and the electronic device is configured to store one or more programs. While the electronic device is associated with health data relating to a first user, which 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, it receives a request via one or more input devices to display a summary of health record information relating to the first user. In response to receiving the aforementioned request, display a summary of the health record information relating to 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 any multiple health record items of the first type for dates earlier than the first date, A second health record item of the second type for a second date different from the first date, wherein the health record summary information does not include multiple health record items of the second type for dates earlier than the second date, This includes displaying multiple health record items simultaneously, An electronic device that contains instructions to execute.

51. It is an electronic device, The display and One or more input devices, While the electronic device is associated with health data relating to a first user, which 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, means for receiving a request to display a summary of health record information relating to the first user via one or more input devices, In response to the receipt of the aforementioned request, means for displaying a summary of health record information relating to the first user on the display, wherein the display is A first health record item of the first type for a first date, wherein the health record summary information does not include any multiple health record items of the first type for dates earlier than the first date, A second health record item of the second type for a second date different from the first date, wherein the health record summary information does not include multiple health record items of the second type for dates earlier than the second date, A means including the simultaneous display of multiple health record items, An electronic device equipped with the following features.

52. An information processing device for use in an electronic device having a display and one or more input devices, While the electronic device is associated with health data relating to a first user, which 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, means for receiving a request to display a summary of health record information relating to the first user via one or more input devices, In response to the receipt of the aforementioned request, means for displaying a summary of health record information relating to the first user on the display, wherein the display is A first health record item of the first type for a first date, wherein the health record summary information does not include any multiple health record items of the first type for dates earlier than the first date, A second health record item of the second type for a second date different from the first date, wherein the health record summary information does not include multiple health record items of the second type for dates earlier than the second date, A means including the simultaneous display of multiple health record items, An electronic device equipped with the following features.

53. It is an electronic device, The display and One or more input devices, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 32 to 48.

54. A non-temporary computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by one or more processors of an electronic device having a display and one or more input devices, include instructions causing the electronic device to perform the method according to any one of claims 32 to 48.

55. It is an electronic device, The display and One or more input devices, Means for carrying out any of the methods described in claims 32 to 48, An electronic device equipped with the following features.

56. An information processing device for use in an electronic device having a display and one or more input devices, The means for carrying out any of the methods described in claims 32 to 48, Information processing device.

57. It is a method, In an electronic device having a display and one or more input devices, While the electronic device is associated with one or more healthcare providers of the user, it displays a first representation of a first ongoing health state among a plurality of ongoing health states of the user indicated by health record information from the one or more healthcare providers, wherein the plurality of ongoing health states include a second ongoing health state and a third ongoing health state. While displaying the first representation of the first ongoing health state, receiving a request via one or more input devices to mark the first ongoing health state as inactive for the user, After receiving the request to mark the first ongoing health status as inactive, the system receives a request via one or more input devices to display the ongoing health status of the user, In response to receiving the request to display the ongoing health status of the user, the display simultaneously displays a second representation of the user's second ongoing health status from the plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, and a third representation of the user's third ongoing health status from the plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, without displaying the first representation of the user's first ongoing health status as the active health status. A method that includes this.

58. In response to receiving the request to mark the first ongoing health status as inactive, the system further includes displaying a visual indication on the display that the first ongoing health status is inactive. The method according to claim 57.

59. In response to receiving the request to display the user's multiple ongoing health statuses, The first ongoing health condition is indicated by a visual sign that it is inactive, The second ongoing health status of the user, The third ongoing health status of the user, The method according to claim 57 or 58, further comprising simultaneously displaying the above on the display.

60. After receiving the request to mark the first ongoing health state as inactive, the system receives a second request via one or more input devices to mark the first health state as active. In response to receiving the second request to mark the first health state as active, the first representation of the first ongoing health state is updated to indicate that the first ongoing health state is active. After updating the first representation of the first ongoing health status to active, a second request is received to display the multiple ongoing health statuses relating to the user, In response to receiving a second request to display the multiple ongoing health statuses relating to the user, the updated representation of the first ongoing health status, the second representation of the second ongoing health status, and the third representation of the third ongoing health status are simultaneously displayed on the display. The method according to any one of claims 57 to 59, further comprising:

61. In response to receiving the request to mark the first ongoing health condition as inactive, further comprising transmitting information indicating the inactive status of the first ongoing health condition to a computer system associated with the healthcare provider associated with the first ongoing health condition, The method according to any one of claims 57 to 60.

62. After receiving the first ongoing health status update, the system receives a third request via one or more input devices to display the ongoing health status of the user, In response to receiving a third request to display the multiple ongoing health statuses relating to the user, The updated first ongoing health status expression, The second expression of the second ongoing health condition, The third expression of the ongoing health condition, To display the above on the display simultaneously, The method according to any one of claims 57 to 61, further comprising:

63. In response to receiving the update for the first ongoing health condition, further includes marking the first ongoing health condition as an active health condition. The method according to claim 62.

64. In response to receiving the update for the first ongoing health condition, further comprising transmitting the update to a computer system associated with the healthcare provider associated with the first ongoing health condition, The method according to claim 62 or 63.

65. In response to determining a set of dates associated with the second ongoing health condition, the system further includes displaying a notification on the display regarding the second ongoing health condition for each date in the set of dates. The method according to any one of claims 57 to 64.

66. The method according to 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 drug replenishment for the second ongoing health condition is scheduled, and the notification includes a reminder to replenish the prescription drug.

67. The method according to claim 65 or 66, further comprising predicting a date on which the remaining amount of prescription medication for the second ongoing health condition will fall below a threshold, wherein the set of dates associated with the second ongoing health condition includes a second date, the second date being a date on which the prescription medication is expected to fall below a threshold, and the notification includes a reminder to replenish the prescription medication.

68. The method of claim 67, further comprising requesting one of the one or more healthcare providers to replenish the prescription drug on the second date, wherein the healthcare provider is associated with the second ongoing health condition.

69. Receiving updates on the remaining amount of prescription medication for the second ongoing health condition via one or more input devices, In accordance with the determination that the remaining amount of the prescribed drug is below a threshold, a notification to replenish the prescribed drug is displayed on the display. The method according to any one of claims 65 to 68, further comprising:

70. The method according to 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 one of the one or more healthcare providers is scheduled, and the healthcare provider is associated with the second ongoing health condition.

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

72. Following the decision that the reminder associated with the second ongoing health condition is also associated with time, The notification regarding the reminder associated with the second ongoing health condition is displayed on the display at the specified time, The method according to any one of claims 67 to 71, further comprising:

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

74. The notification includes a second reminder affordance associated with the reminder, and the method is The request to select the second reminder affordance is received via one or more input devices, In response to receiving the request to select the second reminder affordance, the remaining amount of the prescription drug is calculated, In accordance with the determination that the remaining amount of the prescribed drug is below a threshold, a second notification regarding the second ongoing health condition is displayed on the display, wherein the second notification is a reminder to replenish the prescribed drug. The method according to claim 73, further comprising:

75. The user is a patient, and the electronic device is a patient device. While the patient device is associated with one or more healthcare providers of the patient, the first representation of the first ongoing health condition is displayed on the display of the patient device. While the representation of the first ongoing health status is displayed on the patient device, a request is received from the patient via one or more input devices to mark the first ongoing health status as inactive for the patient. After receiving the request from the patient to mark the first ongoing health status as inactive, the system receives a request from the patient via one or more input devices to display the ongoing health status of the patient. In response to receiving the request from the patient to display the ongoing health status of the patient, the second representation of the second ongoing health status and the third representation of the third ongoing health status are simultaneously displayed on the display of the patient device without displaying the first representation of the ongoing health status. The method according to any one of claims 57 to 74.

76. It is an electronic device, The display and One or more input devices, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, While the electronic device is associated with one or more healthcare providers of the user, it displays a first representation of a first health state among a plurality of ongoing health states of the user indicated by health record information from the one or more healthcare providers, wherein the plurality of ongoing health states include a second ongoing health state and a third ongoing health state. While displaying the first representation of the first ongoing health state, receiving a request via one or more input devices to mark the first ongoing health state as inactive for the user, After receiving the request to mark the first ongoing health status as inactive, the system receives a request via one or more input devices to display the ongoing health status of the user, In response to receiving the request to display the ongoing health status of the user, the system simultaneously displays on the display a second representation of the user's second ongoing health status from the plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, and a third representation of the user's third ongoing health status from the plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, without displaying the first representation of the user's first ongoing health status as active. Includes instructions for executing, Electronic devices.

77. A non-temporary computer-readable storage medium for storing one or more programs, wherein the one or more programs are executed by one or more processors of an electronic device having a display and one or more input devices, and the electronic device is configured to store one or more programs. While the electronic device is associated with one or more healthcare providers of the user, it displays a first representation of a first health state among a plurality of ongoing health states of the user indicated by health record information from the one or more healthcare providers, wherein the plurality of ongoing health states include a second ongoing health state and a third ongoing health state. While displaying the first representation of the first ongoing health state, receiving a request via one or more input devices to mark the first ongoing health state as inactive for the user, After receiving the request to mark the first ongoing health status as inactive, the system receives a request via one or more input devices to display the ongoing health status of the user, In response to receiving the request to display the ongoing health status of the user, the system simultaneously displays on the display a second representation of the user's second ongoing health status from the plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, and a third representation of the user's third ongoing health status from the plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, without displaying the first representation of the user's first ongoing health status as active. A non-temporary computer-readable storage medium containing instructions to execute a command.

78. It is an electronic device, The display and One or more input devices, Means for displaying a first representation of a first health state among a plurality of ongoing health states of the user, as indicated by health record information from the plurality of healthcare providers, while the electronic device is associated with one or more healthcare providers of the user, wherein the plurality of ongoing health states include a second ongoing health state and a third ongoing health state, Means for receiving, via one or more input devices, a request to mark the first ongoing health state as inactive for the user, while the first representation of the first ongoing health state is being displayed. Means for receiving, via one or more input devices, a request to display an ongoing health status relating to the user, after receiving the request to mark the first ongoing health status as inactive. Means for simultaneously displaying on the display, in response to the receipt of the request to display the ongoing health status of the user, a second representation of the user's second ongoing health status from a plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, and a third representation of the user's third ongoing health status from a plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, without displaying the first representation of the user's first ongoing health status as active, An electronic device equipped with the following features.

79. An information processing device for use in an electronic device having a display and one or more input devices, Means for displaying a first representation of a first health state among a plurality of ongoing health states of the user, as indicated by health record information from the plurality of healthcare providers, while the electronic device is associated with one or more healthcare providers of the user, wherein the plurality of ongoing health states include a second ongoing health state and a third ongoing health state, Means for receiving, via one or more input devices, a request to mark the first ongoing health state as inactive for the user, while the first representation of the first ongoing health state is being displayed. Means for receiving, via one or more input devices, a request to display an ongoing health status relating to the user, after receiving the request to mark the first ongoing health status as inactive. Means for simultaneously displaying on the display, in response to the receipt of the request to display the ongoing health status of the user, a second representation of the user's second ongoing health status from a plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, and a third representation of the user's third ongoing health status from a plurality of ongoing health statuses indicated by health record information from one or more healthcare providers, without displaying the first representation of the user's first ongoing health status as active, An information processing device equipped with the following features.

80. It is an electronic device, The display and One or more input devices, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 57 to 75.

81. A non-temporary computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by one or more processors of an electronic device having a display and one or more input devices, include instructions causing the electronic device to perform the method according to any one of claims 57 to 75.

82. It is an electronic device, The display and One or more input devices, Means for carrying out any of the methods according to claims 57 to 75, An electronic device equipped with the following features.

83. An information processing device for use in an electronic device having a display and one or more input devices, The means for carrying out any of the methods described in claims 57 to 75, Information processing device.

Images