KR102590279B1 - Systems and methods for displaying aggregated health records - Google Patents

Abstract

The present invention generally relates to displaying aggregated health records on an electronic device. The method includes receiving a request to display health records for a user while the device is associated with a health care provider. The method also includes displaying categories of health records in response to receiving the first request, wherein selection of a category while the device is associated with the health care provider causes the device to: Displays health records of categories. The method also includes receiving a second request to display health records for the user while the device is associated with two health care providers, wherein the device is associated with both health care providers. Selection of a category causes the device to display health records within the selected category that are from both health care providers.

Description

Systems and methods for displaying aggregated health records {SYSTEMS AND METHODS FOR DISPLAYING AGGREGATED HEALTH RECORDS}

The present invention relates generally to computer user interfaces, and more particularly, to techniques for displaying aggregated health records.

Health care providers sometimes provide patients with paper copies of their health records. Paper copies of health records are easily lost and damaged. Some digitized health care providers provide patients with electronic copies of their health records. However, current methods for displaying health records on electronic devices are outdated, cumbersome, and inefficient. For example, some existing methods use complex and time-consuming user interfaces, which may include multiple key presses or keystrokes to provide a limited amount of health records to the user. Additionally, these methods take longer than necessary, wasting energy. This latter consideration is especially important in battery-operated devices.

It is well understood that use of personally identifiable information must be subject to generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining the privacy of users. In particular, personally identifiable information data must be managed and processed to minimize the risks of unintended or unauthorized access or use, and the nature of authorized use must be clearly indicated to users.

US Patent Publication US 2016/0210434 A1 US Patent Publication US 2013/0191647 A1 US Patent Publication US 2012/0232929 A1

Accordingly, the present technique provides faster and more efficient methods and interfaces for electronic devices to display aggregated health records. These methods and interfaces optionally complement or replace other methods for displaying health records. Such methods and interfaces reduce the number, size, and/or type of inputs from the user, reduce cognitive burden on the user, and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces save power and increase time between battery charges.

These defects and other problems associated with user interfaces for electronic devices (eg, with touch-sensitive surfaces) are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (eg, a laptop computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (eg, a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, a device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory to perform multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on a touch-sensitive surface. In some embodiments, the functions include, optionally, image editing, drawing, presenting, word processing, spreadsheet creation, playing games, making phone calls, video conferencing, sending email, instant messaging, exercising. Includes support for digital photography, digital video recording, web browsing, digital music playback, note taking, and/or digital video playback. Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

According to some embodiments, the method is performed at an electronic device having a display and one or more input devices. The method includes receiving, via one or more input devices, a first request to display health records for a first user while the electronic device is associated with the first health care provider and is not associated with the second health care provider. Includes. In response to receiving the first request to display health records for the first user, the method also includes displaying, on the display, a plurality of representations of categories of health records. The plurality of representations of categories of health records includes a first representation of a first category of the plurality of categories, wherein the electronic device is associated with a first health care provider and is not associated with a second health care provider. Selecting a first representation of a category causes the electronic device to display, on the display, a plurality of health records in the first category from a first health care provider. The plurality of representations of categories of health records also include a second representation of a second category of the plurality of categories, wherein the electronic device is associated with the first health care provider and is not associated with the second health care provider. Selection of the second representation of the second category while causing the electronic device to display, on the display, a plurality of health records in the second category from the first health care provider. The method also provides a second device to display health records for a first user after displaying, via one or more input devices, a plurality of representations of categories of health records and after the electronic device is associated with a second health care provider. It includes receiving a request. In response to receiving the second request to display health records for the first user, the method also includes displaying, on the display, a plurality of representations of categories of health records. The plurality of representations of categories of health records include a first representation of a first category of the plurality of categories, wherein the first representation of the first category while the electronic device is associated with the first health care provider and the second health care provider. 1 Selection of a representation causes the electronic device to display, on the display, one or more health records in a first category from a first health care provider and one or more health records in a first category from a second health care provider. do. The plurality of representations of the categories of health records also include a second representation of a second category of the plurality of categories, wherein the electronic device is associated with the first health care provider and the second health care provider. Selecting the second representation of the category causes the electronic device to display, on the display, one or more health records in the second category from the first health care provider and one or more health records in the second category from the second health care provider. display them.

According to some embodiments, a non-transitory computer-readable storage medium is provided that stores one or more programs comprising instructions, which when executed by one or more processors of an electronic device having a display and one or more input devices. , causing the electronic device to receive, via one or more input devices, a first request to display health records for a first user while the electronic device is associated with the first health care provider and not associated with the second health care provider. Let's do it. In response to receiving the first request to display health records for the first user, the instructions further cause the electronic device to display, on the display, a plurality of representations of categories of health records. The plurality of representations of categories of health records includes a first representation of a first category of the plurality of categories, wherein the electronic device is associated with a first health care provider and is not associated with a second health care provider. Selecting a first representation of a category causes the electronic device to display, on the display, a plurality of health records in the first category from a first health care provider. The plurality of representations of categories of health records also include a second representation of a second category of the plurality of categories, wherein the electronic device is associated with the first health care provider and is not associated with the second health care provider. Selection of the second representation of the second category while causing the electronic device to display, on the display, a plurality of health records in the second category from the first health care provider. The instructions, when executed, also cause the electronic device to display, via one or more input devices, a plurality of representations of categories of health records and to the first user after the electronic device has been associated with the second health care provider. Receive a second request to display health records for In response to receiving the second request to display health records for the first user, the instructions also cause the device to display a plurality of representations of categories of health records on the display. The plurality of representations of categories of health records include a first representation of a first category of the plurality of categories, wherein the first representation of the first category while the electronic device is associated with the first health care provider and the second health care provider. 1 Selection of a representation causes the electronic device to display, on the display, one or more health records in a first category from a first health care provider and one or more health records in a first category from a second health care provider. do. The plurality of representations of the categories of health records also include a second representation of a second category of the plurality of categories, wherein the electronic device is associated with the first health care provider and the second health care provider. Selecting the second representation of the category causes the electronic device to display, on the display, one or more health records in the second category from the first health care provider and one or more health records in the second category from the second health care provider. display them.

According to some embodiments, the method is performed at an electronic device having a display and one or more input devices. The method includes, through one or more input devices, an electronic device receiving health data for a first user including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type. and receiving a request to display health record summary information for the first user while associated. The method also includes displaying health record summary information for the first user including simultaneously displaying, on the display, a plurality of health record items in response to receiving the request. The plurality of health record items include a first health record item of a first type having a first date, wherein the health record summary information excludes the plurality of health record items of the first type having dates earlier than the first date. . The plurality of health record items also include a second health record item of a second type having a second date that is different from the first date, wherein the health record summary information is of a second type having a date that is earlier than the second date. Excludes multiple health record items.

According to some embodiments, a non-transitory computer-readable storage medium is provided that stores one or more programs comprising instructions, which when executed by one or more processors of an electronic device having a display and one or more input devices. , causing the electronic device, via one or more input devices, to transmit a message to a first user, where the electronic device 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. Receive a request to display health record summary information for the first user while associated with health data. The instructions also cause the device to display, on the display, health record summary information for the first user, including simultaneously displaying a plurality of health record items in response to receiving the request. The plurality of health record items include a first health record item of a first type having a first date, wherein the health record summary information excludes the plurality of health record items of the first type having dates earlier than the first date. . The plurality of health record items also include a second health record item of a second type having a second date that is different from the first date, wherein the health record summary information is of a second type having a date that is earlier than the second date. Excludes multiple health record items.

According to some embodiments, the method is performed at an electronic device having a display and one or more input devices. The method includes: determining a first of a plurality of ongoing health states of a user as indicated by health record information from one or more health care providers while the electronic device is associated with the user's one or more health care providers; and displaying the first representation. The method also includes receiving, via one or more input devices, a request to mark the first ongoing health condition as inactive for the user while displaying the first representation of the first ongoing health condition. The method also includes receiving, via one or more input devices, a request to display ongoing health conditions for the user after receiving the request to mark the first ongoing health condition as inactive. The method further includes, in response to receiving a request to display ongoing health conditions for the user, displaying, on the display, one or more first representations of the user's first ongoing health condition as an active health condition. a second representation of a second ongoing health state of the user from a plurality of ongoing health conditions represented by health record information from health care providers, and a second representation of the user's second ongoing health condition represented by health record information from one or more health care providers. and simultaneously displaying a third representation of the user's third ongoing health state from the plurality of ongoing health states.

According to some embodiments, a non-transitory computer-readable storage medium is provided that stores one or more programs comprising instructions, which when executed by one or more processors of an electronic device having a display and one or more input devices. , causing the electronic device to select a first of a plurality of ongoing health conditions of the user as indicated by health record information from one or more health care providers while the electronic device is associated with the user's one or more health care providers. Causes display of a first representation of health status. The instructions further cause the electronic device to receive, via one or more input devices, a request to mark the first ongoing health state as inactive for the user while displaying a first representation of the first ongoing health state. do. The instructions also cause the electronic device to receive, via one or more input devices, a request to display ongoing health states for the user after receiving the request to mark the first ongoing health state as inactive. . The instructions may also cause the electronic device, in response to receiving a request to display ongoing health conditions for the user, to display a first representation of the user's first ongoing health condition without displaying the first representation of the user's first ongoing health condition as an active health condition. on, a second representation of the user's second ongoing health condition from a plurality of ongoing health conditions indicated by health record information from one or more health care providers, and health from one or more health care providers. and simultaneously display a third representation of a third ongoing health state of the user from the plurality of ongoing health states indicated by the record information.

According to some embodiments, the electronic device includes a display, one or more input devices, one or more processors, and memory that stores 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 for performing or causing performance of the operations of any of the methods described herein. According to some embodiments, a computer-readable storage medium, when executed by an electronic device having a display and one or more input devices, causes the device to perform or perform the operations of any of the methods described herein. The commands that cause it to occur are stored internally. According to some embodiments, a graphical user interface on an electronic device having a display and one or more input devices, a memory, and one or more processors for executing one or more programs stored in the memory includes any of the methods described herein. A method includes one or more of the displayed elements, which are updated in response to inputs, as described in any of the methods described herein. According to some embodiments, the electronic device includes a display, one or more input devices, and means for performing or causing performance of the operations of any of the methods described herein. According to some embodiments, an information processing apparatus for use in an electronic device having a display and one or more input devices includes means for performing or causing performance of the operations of any of the methods described herein. do.

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

Accordingly, devices are 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 may complement or replace other methods for displaying aggregated health records.

For a better understanding of the various described embodiments, reference should be made to the following drawings in which like reference numerals indicate corresponding parts throughout the drawings.
1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display, according to some embodiments.
1B is a block diagram illustrating example components for event processing, according to some embodiments.
2 illustrates a portable multifunction device with a touch screen, according to some embodiments.
3 is a block diagram of an example multifunction device having a display and a touch-sensitive surface, according to some embodiments.
4A illustrates an example user interface for a menu of applications on a portable multifunction device, according to some embodiments.
4B illustrates an example user interface for a multifunction device with a touch-sensitive surface separate from the display, according to some embodiments.
5A illustrates a personal electronic device according to some embodiments.
5B is a block diagram illustrating a personal electronic device according to some embodiments.
6A-6Q' illustrate example user interfaces for displaying aggregated health records, according to some embodiments.
7A-7F are flow diagrams of a process for displaying aggregated health records, according to some embodiments.
8A-8N illustrate example dashboard user interfaces for displaying aggregated health records, according to some embodiments.
9A-9D are flow diagrams of a process for displaying dashboard user interfaces with aggregated health records, according to some embodiments.
10A-10Q illustrate example user interfaces for displaying a health record manager that allows a user to specify the status of certain health records, according to some embodiments.
11A-11E are flow diagrams illustrating a method for displaying a health record manager that allows a user to specify the status of certain health records, according to some embodiments.

The following description sets forth exemplary methods, parameters, etc. However, it should be recognized that this description is not intended as a limitation on the scope of the invention, but instead is provided as a description of illustrative embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for displaying health records aggregated in a common interface. The use of such a common interface avoids the risk that a user may be viewing health records that are not complete in relation to a particular interest or issue within the interface. The use of such a common interface also improves the user's efficiency while viewing the user's health records by reducing the need to navigate multiple user interfaces to view health records displayed on the interface. Such techniques can reduce the cognitive burden on the user accessing the user's health records, thereby improving productivity. Additionally, such techniques can reduce processor and battery power that would otherwise be wasted on excessive user inputs.

Below, FIGS. 1A and 1B, 2, 3, 4A and 4B, and 5A and 5B provide descriptions of example devices for performing techniques for displaying aggregated health records. do. 6A-6Q' illustrate example user interfaces for displaying aggregated health records. 7A-7F are flow diagrams illustrating methods for displaying aggregated health records, according to some embodiments. The user interfaces of FIGS. 6A-6Q' are used to illustrate the processes described below, including the processes of FIGS. 7A-7F. 8A-8N illustrate example dashboard user interfaces for displaying aggregated health records. 9A-9D are flow diagrams illustrating methods for displaying dashboard user interfaces with aggregated health records, according to some embodiments. The user interfaces of FIGS. 8A-8N are used to illustrate the processes described below, including the processes of FIGS. 9A-9D. 10A-10Q illustrate example user interfaces for displaying a health record manager that allows a user to specify the status of certain health records through the health record manager. 11A-11E are flowcharts illustrating methods for displaying a health record manager that allows a user to specify the status of certain health records through the health record manager, according to some embodiments. The user interfaces of FIGS. 10A-10Q are used to illustrate the processes described below, including the processes of FIGS. 11A-11E.

Although the following description uses terms such as “first,” “second,” etc. to describe various elements, these elements should not be limited by those terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the various embodiments described, a first touch may be referred to as a second touch, and similarly, a second touch may be referred to as a first touch. Although the first touch and the second touch are both touches, they are not the same touch.

The terminology used in the description of various embodiments described herein is for the purpose of describing specific embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly dictates otherwise. It is intended. Additionally, it will be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The terms "include", "including", "comprise", and/or "comprising", when used herein, refer to the features referred to, an integer. Specifies the presence of features, steps, operations, elements, and/or components, but the presence of one or more other features, integers, steps, operations, elements, components, and/or groups thereof It will be further understood that addition is not excluded.

The term "if" means, optionally, "when" or "upon" or "in response to determining" or " It is interpreted to mean “in response to detecting.” Similarly, the phrases “when it is determined that” or “when [the stated condition or event] is detected” can optionally be used as “when determining that” or “in response to determining that” or “,” depending on the context. is interpreted to mean “upon detecting [the stated condition or event]” or “in response to detecting the [stated condition or event].”

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include iPhone®, iPod Touch®, and iPad® devices from Apple Inc., Cupertino, CA. Includes without. Other portable electronic devices, such as laptop or tablet computers with touch-sensitive surfaces (eg, touch screen displays and/or touchpads), are optionally used. It should also be understood that in some embodiments, the device is a desktop computer with a touch-sensitive surface (eg, a touch screen display and/or touchpad) rather than a portable communication device.

In the discussion below, an electronic device comprising a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

Devices typically support a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, gaming applications, phone applications, video conferencing applications, and email. applications, instant messaging applications, exercise 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.

Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are optionally adjusted and/or changed from one application to the next and/or within each application. In this way, the device's common physical architecture (such as a touch-sensitive surface) optionally supports a variety of applications using user interfaces that are intuitive and transparent to the user.

We now turn our attention to embodiments of portable devices with touch-sensitive displays. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112, according to some embodiments. Touch-sensitive display 112 is sometimes referred to for convenience as a “touch screen” and is sometimes 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 peripherals interface 118, and a RF device. Circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Includes. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors to detect the intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Includes (165). Device 100 may optionally use a touchpad 355 of device 300 or a touch-sensitive display system 112 of device 100 to generate tactile outputs on device 100. and one or more tactile output generators 167 (for generating tactile outputs on the same touch-sensitive surface). These components optionally communicate via one or more communication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on a touch-sensitive surface, or touch. Refers to a substitute (proxy) for the force or pressure of contact on a sensitive surface. The intensity of contact has a range of values, including at least four distinct values and more typically including hundreds (eg, at least 256) distinct values. The intensity of contact is selectively determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (eg, weighted average) to determine the estimated force of the contact. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the touch-sensitive surface proximate to the contact. The resistance of and/or changes thereto are optionally used as a substitute for the force or pressure of contact on the touch-sensitive surface. In some implementations, alternative measurements of contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (eg, the intensity threshold is stated in units corresponding to the alternative measurements). In some implementations, alternative measurements of contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., an intensity threshold is the pressure threshold measured in units of pressure). Using intensity of contact as an attribute of user input allows for affordances that would otherwise not be displayed (e.g., on a touch-sensitive display) and/or (e.g., on a touch-sensitive display, a touch-sensitive surface, or Allows user access to additional device features that may not be accessible by the user on a reduced size device with limited real estate (via physical/mechanical controls such as knobs or buttons) to receive user input Let it be done.

As used in the specification and claims, the term “tactile output” refers to the physical displacement of a device relative to its previous position, the physical displacement of a component of a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing). ) refers to the physical displacement of the component, or the displacement of the component with respect to the center of mass of the device to be detected by the user using the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., fingers, palm, or other part of the user's hand), the tactile output generated by the physical displacement may be transmitted by the user to the device or It will be interpreted as a tactile sensation that corresponds to a perceived change in the physical properties of the device's components. For example, movement of a touch-sensitive surface (eg, a touch-sensitive display or trackpad) is optionally interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation, such as a “down click” or “up click,” even without movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement. . As another example, movement of the touch-sensitive surface is optionally interpreted or perceived by the user as “roughness” of the touch-sensitive surface, even if there is no change in the flatness of the touch-sensitive surface. Although these interpretations of touch by a user will likely be influenced by the user's individualized sensory perception, there are many sensory perceptions of touch that are universal 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 tactile output produced is typical (or corresponds to a physical displacement of the device or its components that would produce the described sensory perception for an average) user.

Device 100 is only one example of a portable multi-function device, and device 100 may optionally have more or fewer components than shown, optionally combine two or more components, or optionally use a combination of components. It should be understood that they have different configurations or arrangements. The various components shown in FIG. 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 (ASICs).

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

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

Radio frequency (RF) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. RF circuitry 108 converts electrical signals to and from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes, but is not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. , and includes well-known circuitry for performing these functions. RF circuitry 108 optionally connects to networks, such as the Internet, also referred to as the World Wide Web (WWW), intranets, and/or wireless networks, such as cellular telephone networks, wireless local area networks (LANs), and/or MANs. (metropolitan area network), and communicate with other devices by wireless communication. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. Wireless communications may optionally include 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), HSPA, HSPA+, DC-HSPDA (Dual-Cell HSPA), LTE (long term evolution), NFC (near field communication), W-CDMA (wideband code division multiple access), CDMA (code division multiple access) ), 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, protocols for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging (XMPP)) and presence protocol), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and/or Short Message Service (SMS), or communications not yet developed as of the filing date of this document. Utilizes any of a plurality of communication standards, protocols and technologies, including but not limited to protocols, as well as any other suitable communication protocols.

The audio circuit unit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit unit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts electrical signals into sound waves that humans can hear. The audio circuitry 110 also receives electrical signals converted from sound waves by the microphone 113. Audio circuitry 110 converts electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. Audio data, optionally, is retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212 in FIG. 2). The headset jack is located between audio circuitry 110 and detachable audio input/output peripherals, such as output-only headphones, or a headset with both an output (e.g., headphones for one or both ears) and an input (e.g., a microphone). Provides an interface.

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals 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 for other input or control devices. 160). One or more input controllers 160 receive/transmit electrical signals to/from other input control devices 116. Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller(s) 160 is, optionally, coupled to any (or not coupled to any) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. does not). One or more buttons (e.g., 208 in FIG. 2) optionally include up/down buttons for volume control of the speaker 111 and/or microphone 113. One or more buttons optionally include a push button (e.g., 206 in FIG. 2).

A quick press of the push button optionally unlocks the touch screen 112 or initiates processes that optionally use gestures on the touch screen to unlock the device, which As described in U.S. Patent Application Serial No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed dated U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. do. A longer press of the push button (e.g., 206) selectively powers device 100 on or off. The functionality of one or more buttons may optionally be customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. Display controller 156 receives and/or transmits electrical signals to and from touch screen 112. Touch screen 112 displays visual output to the user. Visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptics and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) are capable of controlling any contact (and any movement or interruption of contact) on touch screen 112. ) and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages or images) displayed on the touch screen 112. In an example embodiment, the point of contact between touch screen 112 and the user corresponds to the user's finger.

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

The touch-sensitive display in some embodiments of the touch screen 112 may optionally include, but is not limited to, U.S. Patents 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman et al.) , and/or the multi-touch sensitive touchpads described in US Patent Publication No. 2002/0015024A1, each of which is incorporated herein by reference in its entirety. However, while touch screen 112 displays visual output from device 100, touch-sensitive touchpads do not provide visual output.

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

Touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user, optionally, contacts the touch screen 112 using any suitable object or attachment, such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily using finger-based contacts and gestures, which may be less precise than stylus-based input due to the finger's larger contact area on the touch screen. In some embodiments, the device converts coarse finger-based input into precise pointer/cursor positions or commands to perform desired actions by the user.

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

Device 100 also includes a power system 162 to power various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator ( such as light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within portable devices.

Device 100 also optionally includes one or more optical sensors 164. 1A shows an optical sensor coupled to an optical sensor controller 158 within I/O subsystem 106. The optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Light sensor 164 receives light from the surrounding environment, projected through one or more lenses, and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the back of device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still and/or video image acquisition. let it be In some embodiments, the optical sensor is positioned on the front of the device such that an image of the user is optionally obtained for the video conference while the user views other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the sensor and lens within the device housing) such that a single optical sensor 164 can display an image with a touch screen display. It is intended to be used for both conferencing and still and/or video image acquisition.

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

Device 100 also optionally includes one or more proximity sensors 166. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I/O subsystem 106. Proximity sensor 166 may optionally be described in U.S. Patent Application Serial No. 11/241,839, “Proximity Detector In Handheld Device”; No. 11/240,788, “Proximity Detector In Handheld Device”; No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are incorporated herein by reference in their entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is positioned near the user's ear (e.g., when the user is talking on the phone).

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

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

In some embodiments, software components stored in memory 102 include operating system 126, communications module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module ( or set of instructions) 132, a text input module (or set of instructions) 134, a GPS module (or set of instructions) 135, and applications (or sets of instructions) 136. . Additionally, in some embodiments, memory (102 in FIG. 1A or 370 in FIG. 3) stores device/global internal state 157 as shown in FIGS. 1A and 3. Device/global internal state 157 includes active application state, if present, indicating which applications are currently active; display state indicating which applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information regarding the location and/or posture of the device.

Operating system 126 (e.g., an embedded operating system such as Darwin, RTXC, LINUX, UNIX, OS Includes various software components and/or drivers for controlling and managing and facilitates communication between various hardware and software components.

The communication module 128 enables communication with other devices through one or more external ports 124, and also provides various functions for processing data received by the RF circuitry 108 and/or external ports 124. Contains software components. External port 124 (e.g., USB, FIREWIRE, etc.) is configured to couple to other devices directly or indirectly through a network (e.g., Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same or similar to and/or compatible with the 30-pin connector used in iPod® (a trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen 112 (along with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). . Contact/motion module 130 may be configured to determine whether contact has occurred (e.g., detecting a finger-down event), the strength of the contact (e.g., the force or pressure of the contact, or determining the force of the contact or a proxy for pressure) and tracking movement across the touch-sensitive surface by determining whether there is movement of the contact (e.g., one or more finger-dragging events) ), and determining whether the contact has stopped (e.g., detecting a finger-up event or interruption of contact). Includes various software components to perform. Contact/motion module 130 receives contact data from a touch-sensitive surface. Determining the movement of the point of contact represented by the set of contact data may optionally determine the speed (magnitude), velocity (magnitude and direction), and/or acceleration (change in size and/or direction) of the point of contact. It includes doing. These operations are optionally applied to single contacts (eg, single finger contacts) or to multiple simultaneous contacts (eg, “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on the touchpad.

In some embodiments, contact/motion module 130 may use a set of one or more intensity thresholds to determine whether an action was performed by a user (e.g., to determine whether the user “clicked” on an icon). Use . In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators, and changing the physical hardware of device 100 can be adjusted without). For example, the mouse “click” threshold of a trackpad or touch screen display can be set to any of a wide range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device may select one of a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or adjusting multiple intensity thresholds all at once with a system-level click "intensity" parameter). Software settings are provided to adjust the abnormality.

Contact/motion module 130 optionally detects gesture input by the user. Different gestures on a touch-sensitive surface have different contact patterns (eg, different motions, timings, and/or intensities of detected contacts). Accordingly, the gesture is, optionally, detected by detecting a specific contact pattern. For example, detecting a finger tap gesture involves detecting a finger-down event and then finger-down at the same location (or substantially the same location) as the finger-down event (e.g., at the location of the icon). Includes detecting up (liftoff) events. As another example, detecting a finger swipe gesture on a touch-sensitive surface may involve detecting a finger-down event followed by one or more finger-dragging events, followed by a finger-up (liftoff) event. ) includes detecting events.

Graphics module 132 may render and display graphics on a touch screen 112 or other display, including components for changing the visual effect (e.g., brightness, transparency, saturation, contrast, or other visual properties) of displayed graphics. It includes various known software components for display. As used herein, the term “graphics” includes, without limitation, text, web pages, icons (e.g., user interface objects including soft keys), digital images, videos, animations, etc. , contains arbitrary objects that can be displayed to the user.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives one or more codes specifying graphics to be displayed, along with coordinate data and other graphics attribute data, if necessary, from applications, etc., and then generates screen image data to display controller 156. Print out.

Haptic feedback module 133 is used by tactile output generator(s) 167 to generate tactile outputs at one or more locations on device 100 in response to user interactions with device 100. Contains various software components for generating instructions.

Text input module 134, optionally a component of graphics module 132, is used for various applications (e.g., contacts 137, email 140, IM 141, browser 147, and text input). Provides soft keyboards for entering text into any other application).

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

Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

연락처 모듈(137)(때때로 주소록 또는 연락처 목록으로 지칭됨);

Contacts module 137 (sometimes referred to as address book or contact list);

Telephone module 138;

화상 회의 모듈(139);

video conferencing module 139;

이메일 클라이언트 모듈(140);

email client module 140;

인스턴트 메시징(IM) 모듈(141);

instant messaging (IM) module 141;

운동 지원 모듈(142);

exercise support module 142;

정지 및/또는 비디오 이미지들을 위한 카메라 모듈(143);

Camera module 143 for still and/or video images;

이미지 관리 모듈(144);

image management module 144;

비디오 재생기 모듈;

video player module;

음악 재생기 모듈;

music player module;

브라우저 모듈(147);

browser module 147;

캘린더 모듈(148);

calendar module (148);

날씨 위젯(149-1), 주식 위젯(149-2), 계산기 위젯(149-3), 알람 시계 위젯(149-4), 사전 위젯(149-5), 및 사용자에 의해 얻어지는 다른 위젯들뿐 아니라 사용자-생성 위젯들(149-6) 중 하나 이상을 선택적으로 포함하는 위젯 모듈들(149);

Weather widget (149-1), Stock 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 widget modules 149 optionally including one or more of the user-created widgets 149-6;

사용자-생성 위젯들(149-6)을 만들기 위한 위젯 생성기 모듈(150);

a widget generator module 150 for creating user-created widgets 149-6;

검색 모듈(151);

Search module 151;

비디오 재생기 모듈 및 음악 재생기 모듈을 통합하는 비디오 및 음악 재생기 모듈(152);

a video and music player module 152 incorporating a video player module and a music player module;

메모 모듈(153);

memo module 153;

지도 모듈(154); 및/또는

map module (154); and/or

온라인 비디오 모듈(155).

Online Video Module (155).

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

Contacts module 137, along with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, optionally includes an address book or contact list ( e.g., stored in memory 102 or application internal state 192 of contacts module 137 in memory 370, including: adding name(s) to the address book; thing; deleting name(s) from the address book; Associating a name with a phone number(s), email address(es), physical address(es) or other information; associating an image with a name; sorting and sorting names; Providing phone numbers or email addresses to initiate and/or facilitate communication by phone 138, video conferencing module 139, email 140 or IM 141, etc.

RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text. In conjunction with input module 134, phone module 138 may optionally input a sequence of characters corresponding to a phone number, access one or more phone numbers within contact module 137, and modify the entered phone number. It is used to dial individual phone numbers, initiate conversations, and disconnect or hang up when the conversation is complete. As discussed above, wireless communications optionally utilize any of a plurality of communication standards, protocols and technologies.

RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, touch/motion In conjunction with module 130, graphics module 132, text input module 134, contact module 137, and phone module 138, video conferencing module 139 is capable of interacting with a user and one or more other users according to user instructions. Contains executable commands to initiate, conduct, and terminate video conferences between participants.

Email client module 140, along with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, provides user instructions. Contains executable commands that allow you to create, send, receive, and manage email in response to commands. Together with the image management module 144 , the email client module 140 makes it very easy to create and send emails with still or video images taken with the camera module 143 .

Instant messaging module 141, along with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, provides instant messaging Enter a sequence of characters corresponding to a message, modify previously entered characters (e.g., use the Short Message Service (SMS) or Multimedia Message Service for phone-based instant messaging). , MMS) protocol, or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), and contains executable instructions for sending individual instant messages, receiving instant messages, and viewing received instant messages. . In some embodiments, instant messages sent and/or received optionally include graphics, photos, audio files, video files, and/or other attachments as supported in MMS and/or Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). ) refers to both.

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154. , and the music player module, the workout support module 142 is designed to design workouts (e.g., with time, distance, and/or calorie expenditure goals); communicate with exercise sensors (sports devices); receive motion sensor data; calibrate sensors used to monitor exercise; Select and play music for your workout; Contains executable instructions to display, store, and transmit exercise data.

with touch screen 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 can capture still images or video (including a video stream) and store them in memory 102, modify the characteristics of the still image or video, or retrieve still images or video from memory 102. Contains executable commands to delete a video.

Image management module 144, along with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, can /or Contains executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slideshow or album), and store video images. .

Browser module 147, along with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, displays a web page. Executable instructions for browsing the Internet according to user instructions, including retrieving, linking to, receiving, and displaying attachments and other files linked to web pages or portions thereof. includes them.

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, email client module 140, and browser module ( In conjunction with 147), calendar module 148 is executable to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) according to user instructions. Contains commands.

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, along with widget modules. 149 may be optionally downloaded and used by the user (e.g., weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widgets 149-5), or mini-applications that are created by a user (e.g., user-created widgets 149-6). In some embodiments, widgets include Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, a widget includes an Extensible Markup Language (XML) file and a JavaScript file (eg, Yahoo! widgets).

A widget generator module, along with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147. 150 is optionally used to create widgets by the user (e.g., change a user-specific portion of a web page into a widget).

In conjunction with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 provides one or more search criteria according to user instructions. and executable instructions to search for text, music, sound, images, video, and/or other files in memory 102 that match (e.g., one or more user-specific search terms).

with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speakers 111, RF circuitry 108, and browser module 147. , the video and music player module 152 includes executable instructions that allow a user to download and play recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and videos ( and executable instructions for displaying, playing, or otherwise playing (e.g., on touch screen 112 or on an external connected display through 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.).

Along with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the memo module 153 creates notes, notes, and actions according to user instructions. Contains executable commands for creating and managing task lists, etc.

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147. ), the maps module 154 optionally provides maps and data associated with the maps according to user instructions (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data).

Touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, In conjunction with the email client module 140 and the browser module 147, the online video module 155 allows users to access online videos in one or more file formats, such as H.264, browse them (e.g., stream and /or by download), play (e.g., on a touch screen or on an externally connected display via external port 124), send an email with a link to a particular online video, and otherwise manage Includes commands that In some embodiments, instant messaging module 141 rather than email client module 140 is used to send links to specific online videos. For additional description of online video applications, see 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 December 31, 2007. See U.S. Patent Application Serial No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety. .

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

In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or touchpad. By using a touch screen and/or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, etc.) on device 100 is optionally reduced.

A predefined set of functions performed entirely via the touch screen and/or touchpad, optionally including navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main, home, or root menu from any user interface displayed on device 100. In such embodiments, the “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

1B is a block diagram illustrating example components for event processing, according to some embodiments. In some embodiments, memory (102 in FIG. 1A or 370 in FIG. 3) stores event sorter 170 (e.g., in operating system 126) and each application 136-1 (e.g., the application described above). Includes any of (137 to 151, 155, 380 to 390).

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

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

The event monitor 171 receives event information from the peripheral interface 118. Event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 may be connected to the I/O subsystem 106 or sensors, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (via audio circuitry 110). Send the information you receive. Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving input that exceeds a predetermined noise threshold and/or exceeds a predetermined duration) .

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

Hit view determination module 172 provides software procedures for determining where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. Views consist of controls and other elements that the user can see on the display.

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 views (of each application) for which a touch is detected optionally correspond to program levels within the application's program or view hierarchy. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events that are recognized as appropriate inputs is optionally based at least in part on the hit view of the initial touch that initiates the touch-based gesture. It is decided.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. If the application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy for which the subevent should be handled. In most situations, the hit view is the lowest level view in which the initiating subevent (eg, the first subevent in a sequence of subevents forming an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events associated with the same touch or input source that led it to be identified as the hit view.

The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of a sub-event are actively involved views, such that all actively involved views are It is determined that the sequence should be received. In other embodiments, even if touch sub-events are confined entirely to an area associated with one particular view, higher-level views in the hierarchy will still remain actively participating views.

Event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In embodiments that include the active event recognizer determination module 173, the event dispatcher module 174 forwards event information to the event recognizer determined by the active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information in an event queue, from which event information is retrieved by each event receiver 182.

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

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which can handle touch events that occur within a respective view of the application's user interface. Contains commands for processing. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 may be part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. am. In some embodiments, each event handler 190 may receive one of event data 179 from data updater 176, object updater 177, GUI updater 178, and/or event sorter 170. Includes more. Event handler 190 optionally uses or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included within each application view 191.

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

Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events, for example, touch or touch movement. Depending on the sub-event, the event information also includes additional information such as the location of the sub-event. If the sub-event involves the motion of a touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the events include rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes the device's current orientation (also referred to as device pose). ) includes corresponding information about.

Event comparator 184 compares event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the status of the event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 include definitions of events (e.g., predefined sequences of sub-events), e.g., Event 1 (187-1), Event 2 (187-2), etc. In some embodiments, sub-events within event 187 include, for example, touch start, touch end, touch move, touch cancel, and multiple touches. In one example, the definition for event 1 187-1 is a double tap on a displayed object. A double tap can be, for example, a first touch on a displayed object during a predetermined phase (start of touch), a first liftoff during a predetermined phase (end of touch), and a first touch on the displayed object during a predetermined phase. a second touch on the top (touch start), and a second liftoff (touch end) during a predetermined phase. In another example, the definition for event 2 187-2 is dragging on a displayed object. Dragging includes, for example, a touch (or contact) on a displayed object during a predetermined phase, movement of the touch across the touch-sensitive display 112, and liftoff of the touch (termination of the touch). In some embodiments, an event also includes information about one or more associated event handlers 190.

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

In some embodiments, the definition for each event 187 also includes deferred actions that delay delivery of event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event type of the event recognizer. .

If each event recognizer 180 determines that the set of sub-events does not match any of the events in event definitions 186, then each event recognizer 180 determines that the event is not possible, the event is failed, or The event end state is entered, after which each event recognizer ignores subsequent subevents of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process subevents of the ongoing touch-based gesture.

In some embodiments, each event recognizer 180 includes configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. It includes metadata 183. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact with each other or are enabled for interaction. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether subevents are delivered to the view or various levels in the program hierarchy.

In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 passes event information associated with the event to event handler 190. Activating the event handler 190 is separate from sending (and delaying sending) sub-events to each hit view. In some embodiments, event recognizer 180 sends a flag associated with the recognized event, and event handler 190 associated with that flag catches that flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information regarding a sub-event without activating an event handler. Instead, sub-event delivery instructions deliver event information to event handlers associated with a series of sub-events or to actively participating views. Event handlers associated with a series of sub-events or actively participating views receive event information and perform predetermined processes.

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

In some embodiments, event handler(s) 190 includes or accesses data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included within a single module of each application 136-1 or application view 191. In other embodiments, they are included within two or more software modules.

The foregoing discussion of event handling of user touches on a touch-sensitive display also applies to other forms of user input for operating multifunction devices 100 with input devices, not all of which are initiated on touch screens. You must understand that this is not the case. For example, mouse movements and mouse button presses, optionally combined with single or multiple keyboard presses or holds; Contact movements such as tapping, dragging, scrolling, etc. on the touchpad; pen stylus inputs; movement of the device; verbal commands; detected eye movements; biometric inputs; and/or any combination thereof are optionally used as inputs corresponding to sub-events defining the event to be recognized.

2 shows a portable multifunction device 100 with a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, the user may use, for example, one or more fingers 202 (not shown to scale in the figure) or one or more styluses 203 (not to scale in the figure). It is possible to select one or more of the graphics by making a gesture on the graphics using (not shown as shown). In some embodiments, selection of one or more graphics occurs when the user ceases contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps of a finger in contact with device 100, one or more swipes (left to right, right to left, up and/or down). , and/or rolling (right to left, left to right, upward and/or downward). In some implementations or situations, if a graphic is inadvertently contacted, the graphic is not selected. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

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

In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering on/off and locking the device, and volume control button(s) 208. , a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking/charging external port 124. Push button 206 optionally powers the device on/off by pressing the button and holding the button pressed for a predefined time interval; lock the device by pressing a button and releasing the button before a predefined time interval has elapsed; Used to unlock the device or initiate the unlocking process. In an alternative embodiment, device 100 also accepts verbal input for activating or deactivating some functions via microphone 113. Device 100 may also optionally include one or more contact intensity sensors 165 to detect the intensity of contacts on touch screen 112 and/or to generate tactile outputs for a user of device 100. It includes one or more tactile output generators 167 for.

3 is a block diagram of an example multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 may be a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., for home or industrial use). 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). Communication buses 320 optionally include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communications between them. Device 300 includes an input/output (I/O) interface 330 that includes a display 340, typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output devices for generating tactile outputs on device 300. Generator 357 (e.g., similar to the tactile output generator(s) 167 described above with reference to FIG. 1A ), and sensors 359 (e.g., light sensor, acceleration sensor, proximity sensor, touch-sensitive sensor, and/or a contact intensity sensor similar to the contact intensity sensor(s) 165 described above with reference to FIG. 1A. Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; Optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310. In some embodiments, memory 370 includes programs, modules, and data structures similar to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (Figure 1A). , or a subset of them. Additionally, memory 370 optionally stores additional programs, modules and data structures not present within memory 102 of portable multifunction device 100. For example, memory 370 of device 300 may optionally include a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, and a disk authoring module 388. ), and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store such modules.

Each of the previously identified elements in Figure 3 is, optionally, stored in one or more of the memory devices described above. Each of the previously identified modules corresponds to a set of instructions for performing the above-described functions. The modules or programs (e.g., sets of instructions) identified above need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may optionally be combined in various embodiments. Either it is or it is rearranged. In some embodiments, memory 370 optionally stores a subset of the previously identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

Attention now turns to embodiments of user interfaces that are optionally implemented, for example, on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applications on portable multifunction device 100, according to some embodiments. Similar user interfaces are optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

셀룰러 및 Wi-Fi 신호들과 같은 무선 통신(들)을 위한 신호 세기 표시자(들)(402);

signal strength indicator(s) 402 for wireless communication(s) such as cellular and Wi-Fi signals;

시간(404);

time(404);

블루투스 표시자(405);

Bluetooth indicator (405);

배터리 상태 표시자(406);

battery status indicator 406;

다음과 같은, 빈번하게 사용되는 애플리케이션들에 대한 아이콘들을 갖는 트레이(408):

Tray 408 with icons for frequently used applications, such as:

o an icon 416 for the phone module 138 labeled “Phone”, optionally including an indicator 414 of the number of missed calls or voicemail messages;

o Icon 418 for the email client module 140 labeled “Mail”, optionally including an indicator 410 of the number of unread emails;

o an icon 420 for the browser module 147 labeled “browser”; and

o an icon 422 for a video and music player module 152 labeled “iPod,” also referred to as iPod (a trademark of Apple Inc.) module 152; and

다음과 같은, 다른 애플리케이션들에 대한 아이콘들:

Icons for different applications, such as:

o Icon 424 for IM module 141 labeled “Messages”;

o Icon 426 for the calendar module 148 labeled “Calendar”;

o Icon 428 for the image management module 144 labeled “Photos”;

o Icon 430 for camera module 143 labeled “Camera”;

o Icon 432 for the Online Video module 155 labeled “Online Video”;

o Icon (434) for the stock widget (149-2) labeled “Stocks”;

o icon 436 for map module 154 labeled “maps”;

o Icon (438) for weather widget (149-1) labeled “Weather”;

o Icon 440 for an alarm clock widget 149-4 labeled “Clock”;

o Icon 442 for the Athletic Support module 142 labeled “Athletic Support”;

o an icon 444 for a notes module 153 labeled “Notes”; and

o Icon 446 for a Settings application or module, labeled “Settings,” which provides access to settings for the device 100 and its various applications 136.

It should be noted that the icon labels illustrated in Figure 4A are examples only. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to each application icon. In some embodiments, the label for a particular application icon is separate from the name of the application that corresponds to the particular application icon.

FIG. 4B illustrates a device (e.g., FIG. 3 An example user interface on device 300 is shown. Device 300 may also optionally include one or more contact intensity sensors (e.g., one or more of sensors 359 ) to detect the intensity of contacts on touch-sensitive surface 451 and/or device 300 ) and one or more tactile output generators 357 for generating tactile outputs for the user.

Although some of the examples that follow will be presented with reference to inputs on touch screen display 112 (a combination of a touch-sensitive surface and display), in some embodiments, the device may be configured separately from the display, as shown in FIG. 4B. Detect inputs on a personal touch-sensitive surface. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) corresponding to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device interacts with the touch-sensitive surface 451 at positions corresponding to respective positions on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). Detect contacts (eg, 460 and 462 in FIG. 4B). In this way, user inputs (e.g., contacts 460, 462 and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) can be performed while the touch-sensitive surface is separate from the display. When used by the device to manipulate the user interface on the display of the multifunction device (e.g., 450 in FIG. 4B). It should be understood that similar methods, optionally, may be used for other user interfaces described herein.

Additionally, while the examples below are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), in some embodiments, one or more of the finger inputs may be combined with other inputs. It should be understood that input from the device (eg, mouse-based input or stylus input) is substituted. For example, a swipe gesture is optionally replaced with a mouse click (eg, instead of a contact) followed by movement of the cursor along the path of the swipe (eg, instead of a movement of the contact). As another example, the tap gesture is optionally replaced by a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of stopping to detect contact following detection of the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are being used selectively simultaneously, or mouse and finger contacts are being used selectively simultaneously.

FIG. 5A depicts an example 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., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504 (hereinafter referred to as touch screen 504). Alternatively or in addition to a touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100, 300, in some embodiments, touch screen 504 (or touch-sensitive surface) is optionally configured to detect the intensity of contacts (e.g., touches) being made. Includes more than one intensity sensor. One or more intensity sensors of touch screen 504 (or a touch-sensitive surface) may provide output data representing the intensity of touches. The user interface of device 500 may respond to touches based on the intensity of the touches, meaning that touches of different intensities may invoke different user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity are described, for example, in related applications: Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to International Patent Application PCT/US2013/040061 (published as WIPO Publication No. WO/2013/169849), filed on November 11, 2013 and entitled “Device, Method, and Graphical User Interface” for Transitioning Between Touch Input to Display Output Relationships", International Patent Application No. PCT/US2013/069483, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in its entirety.

In some embodiments, device 500 has one or more input mechanisms 506, 508. Input mechanisms 506, 508 (if included) may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. These attachment mechanisms (if included) allow device 500 to attach, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watch strap, chain, pants, belt, shoe, wallet, etc. , so that it can be attached to a backpack, etc. These attachment mechanisms allow device 500 to be worn by a user.

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

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

Memory 518 of personal electronic device 500, for example, when executed by one or more computer processors 516, causes the computer processors to perform processes 700, 900, and 1100 (FIGS. 7A-7). 7F, FIGS. 9A-9D, and FIGS. 11A-11E). . A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a temporary computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include persistent solid-state memory such as flash, solid-state drives, etc., as well as magnetic disks, optical disks based on CD, DVD, or Blu-ray technologies. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in a number of configurations.

As used herein, the term “affordance” refers to a user interaction that is selectively displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A and 5B). Refers to a user-interactive graphical user interface object. For example, images (eg, icons), buttons, and text (eg, hyperlinks) each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other location marker, a touch-sensitive surface (e.g., FIG. 3 When an input (e.g., a press input) is detected on the touchpad 355 in or the touch-sensitive surface 451 in FIG. It functions as Some implementations include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display. In the field, a particular user interface element is detected when an input (e.g., a tactile press input) is detected on the touch screen display at the location of the particular user interface element (e.g., a button, window, slider, or other user interface element). Contacts detected on the touch screen function as “focus selectors” to adjust according to the input received. In some implementations, focus is moved to one of the user interfaces without movement of a corresponding cursor or touch on the touch screen display (e.g., by using the tab key or arrow keys to move focus from one button to another). moves from one area to another area of the user interface; In these implementations, the focus selector moves in response to movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally used to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user wishes to interact). A user interface element controlled by (or by contact on a touch screen display). For example, while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of the focus selector (e.g., a cursor, touch, or selection box) on each button (on the device's display) (unlike other visible user interface elements) will indicate that the user is attempting to activate the respective button.

As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity may optionally be generated over a predefined number of intensity samples, or (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the onset of movement of the contact, A predetermined period of time for a predefined event (e.g., prior to detecting the end of contact, before or after detecting an increase in the intensity of contact, and/or before or after detecting a decrease in intensity of contact) It is based on a set of intensity samples collected for 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds). The characteristic intensity of contact may optionally be the maximum value of the intensities of contact, the mean value of the intensities of contact, the average value of the intensities of contact, the top 10 percentile of intensities of contact. value), a value of half the maximum value of the contact intensities, a value of 90 percent of the maximum value of the contact intensities, etc. In some embodiments, the duration of contact is used to determine characteristic intensity (eg, when the characteristic intensity is an average of the intensity of contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action was performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, as a result of the contact having a characteristic intensity that does not exceed the first intensity threshold, a first action is performed, and as a result of the contact having a characteristic intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold, a second action is performed. An action is performed and, as a result of the contact having a characteristic intensity above the second threshold, a third action is performed. In some embodiments, the comparison between the characteristic strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., perform each operation), rather than being used to determine whether to perform the first operation or the second operation. It is used to decide whether or not to hold off on performing each action.

In some embodiments, a portion of the gesture is identified to determine characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a starting position to reach an ending position, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the continuous swipe contact (eg, only the portion of the swipe contact at the end position) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensities of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally be one of an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. Contains one or more In some situations, these smoothing algorithms remove narrow spikes or dips in the intensities of a swipe contact to determine the characteristic intensity.

The intensity of the contact on the touch-sensitive surface is optionally characterized against one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to the intensity at which the device will perform operations typically associated with clicking a button on a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to the intensity at which the device will perform operations that are different from operations typically associated with clicking a button on a physical mouse or a trackpad. In some embodiments, when contact is detected 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), the device determines the light press intensity. It will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing any actions associated with the threshold or deep press intensity threshold. Generally, unless otherwise noted, these intensity thresholds are consistent between different sets of user interface diagrams.

An increase in the characteristic intensity of a contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase in the characteristic intensity of a contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more actions may be performed in response to detecting a gesture comprising the respective press input or to detect each press input performed with each contact (or multiple contacts). is performed in response to: wherein each press input is detected based at least in part on detecting an increase in the intensity of the contact (or plurality of contacts) above a press input intensity threshold. In some embodiments, each action is performed in response to detecting an increase in the intensity of the respective contact above a pressing input intensity threshold (e.g., a “down stroke” of the respective pressing input). In some embodiments, the press input includes an increase in the intensity of each contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the press input intensity threshold, each action being performed with each contact below the press input intensity threshold. This is performed in response to detecting a subsequent decrease in the intensity of the contact (e.g., the “up stroke” of the respective pressing input).

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as “jitter,” where the device sets a hysteresis intensity threshold ( For example, define or select the hysteresis intensity threshold to be As such, in some embodiments, the pressing input includes an increase in intensity of each contact above a pressing input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the pressing input intensity threshold, respectively. The operation of is performed in response to detecting a subsequent decrease in the intensity of each contact (e.g., an “up stroke” of the respective pressing input) below the hysteresis intensity threshold. Similarly, in some embodiments, the press input causes the device to increase the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and, optionally, to an intensity below the hysteresis intensity threshold. Detected only when detecting a subsequent decrease in the intensity of the contact, each action is performed in response to detecting a pressing input (eg, an increase in the intensity of the contact or a decrease in the intensity of the contact depending on the surroundings).

For ease of explanation, descriptions of actions performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input include, optionally, an increase in the intensity of the contact above the press input intensity threshold, a hysteresis intensity threshold; increasing the intensity of the contact from an intensity below to an intensity above the pressing input intensity threshold, decreasing the intensity of the contact below the pressing input intensity threshold, and/or increasing the intensity of the contact below the hysteresis intensity threshold corresponding to the pressing input intensity threshold. Triggered in response to detecting either decrease. Additionally, in examples where the operation is described as being performed in response to detecting a decrease in the intensity of the contact below a pressing input intensity threshold, the operation may optionally be performed in response to a pressing input intensity threshold and below a lower hysteresis intensity threshold. It is performed in response to detecting a decrease in the intensity of contact.

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

6A-6Q' illustrate example user interfaces for displaying aggregated health records to a user, according to some embodiments. For convenience, the health records will be described herein as the user's health records. However, the health records may be health records of family members or other individuals associated with the user of the example user interfaces. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 7A-7F.

Although some of the examples that follow will be given with reference to inputs on a touch screen display (a combination of a touch-sensitive surface and display), in some embodiments the device may be configured to display a display 450 separate from the display 450, as shown in FIG. 4B. Detect inputs on the touch-sensitive surface 451. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. For ease of explanation, the embodiments described below will be discussed with reference to operations performed on a device having the touch-sensitive display system 112. In such embodiments, the focus selector may optionally be: an individual finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the center of the individual contact, or a point associated with the individual contact), or a touch. It is the center of two or more contacts detected on the responsive display system 112. However, similar operations may be performed on the display 450 and a separate touch-sensitive surface 451 in response to detecting contacts on the touch-sensitive surface 451 while displaying the user interfaces discussed below, optionally with a focus selector. It is performed on a device with surface 451.

6A-6Q' illustrate example user interfaces for displaying a user's aggregated health information, according to some embodiments. The user interfaces of FIGS. 6A-6Q' allow a user to review the user's health records from one or more health care providers. Such user interfaces present a user's health records in an organized manner that allows the user to view the user's health records quickly and efficiently. More specifically, the health records in FIGS. 6A-6Q' are organized into categories. In the illustrated embodiments, such categories include allergies, clinical documentation, laboratory results, medications, and health conditions. However, in alternative embodiments, additional or different categories or groupings may be utilized to organize health records. The user interfaces also present updates to existing health records and new health records in an organized manner that integrates updates to existing health records and new health records.

In one embodiment, to obtain the user's health information for display in the example user interfaces illustrated in FIGS. 6A-6Q', the user may use one or more user interfaces not illustrated herein ("onboarding (onboarding) user interfaces”) to initiate, continue, or complete the onboarding process with a health care provider. In some embodiments, and while the user interface shown in FIG. 6A or a similar user interface is displayed on display 112, a user accesses onboarding user interfaces by interacting with affordances 5302 of health care providers. do. The user may periodically access the onboarding user interfaces to initiate the onboarding process of a new health care provider, review information about an existing health care provider for whom the user has completed the onboarding process, or contact a health care provider. You can update information about a health care provider, or remove a health care provider. Once the onboarding process with the health care provider is complete, device 100 obtains access to the user's health records from the health care provider and displays the health care provider's health records on display 112. In some embodiments, device 100 displays the user interface illustrated in FIG. 6A on display 112 in response to determining that the onboarding process is complete. In other embodiments, onboarding user interfaces include a toolbar 5029 with affordance 5029A of health data as illustrated in FIG. 6A. In such embodiments, a user accesses Figure 6A by interacting with affordance 5029A of health data.

FIG. 6A illustrates one embodiment of displaying representations of categories of a user's health records from one or more health care providers. Figure 6A includes category representations 5006A, 5006B, 5006C, 5006D, 5006E, and a representation of all records associated with all of the user's health records 5006F. In the illustrated embodiment, category representation 5006A is associated with allergy health records, category representation 5006B is associated with clinical documentation, category representation 5006C is associated with laboratory results, and category representation 5006D ) is associated with drugs, and the category expression 5006E is associated with health conditions. Each of the category expressions 5006A through 5006E is an affordance that includes text identifying that such affordance is associated with health records from a particular category. Each of category representations 5006A-5006E is selectable by the user to view the user's health records from the associated category. In some embodiments, category representations 5006A-5006E also include a description of the corresponding category, a summary of health records included in the corresponding category, or other information about the corresponding category. For example, category representation 5006E may include information summarizing the user's different ongoing health conditions. The representation of all records 5006F is an affordance containing text indicating that such affordance is associated with all health records. All records representation 5006F is selectable by the user to view all of the user's health records. 6A and 6B illustrate detecting an affordance (e.g., a tap gesture at contact 5502, FIG. 6A) on a category representation for drugs 5006D, and in response to the tap gesture, detecting an affordance (e.g. , illustrates displaying health records corresponding to a category of health records associated with medication records 5018A and 5018B ( FIG. 6B ).

FIG. 6B illustrates a display of health records associated with the category representation 5006D illustrated in FIG. 6A for medications. More specifically, drug records 5018A, 5018B (ABC drug and DEF drug) are displayed. In the illustrated embodiment, medication records 5018A, 5018B are health records of medications taken by the user, the name of the medication (ABC and DEF medications, respectively), and the health care provider who prescribed the medication (both records for Alpha Healthcare), and text identifying the date the medication was prescribed (October 1, 2017 and September 1, 2017, respectively). A health care provider may be a designation of one or more of the following: an individual physician, the name of a health care organization such as a home health agency or hospital group, or a specific facility or location where treatment was provided, such as a specific hospital or clinic location. In other embodiments, a pharmacy dispensing the drug, a refill or expiration date of the drug, instructions or affordances to refill the drug, dosages, instructions, warnings, drug side effects, active ingredients, and an image of the drug. Text or images representing additional information about the drug, such as a fact sheet about the drug, or any other suitable information, may be displayed in drug records 5018A, 5018B. In the illustrated embodiment, medication records 5018A, 5018B are arranged in order of most recent prescription date. In other embodiments, medication records 5018A, 5018B are arranged to list daily medications in alphabetical order, ahead of other medications, or in another suitable order for dispensing medications. FIG. 6B also shows a user interaction to view the category representations 5006A-5006E illustrated in FIG. 6A (categories of Allergies, Clinical Documents, Lab Results, Medications, and Health Conditions, respectively). This illustrates the affordance 5304 of health records, which is an affordance to do so. In that regard, Figure 6B further illustrates the detection of a tap gesture at contact 5504 on the affordances 5304 of health records to display category representations 5006A-5006E in Figure 6C.

In Figure 6B, medication records 5018A, 5018B (ABC Medication and DEF Medication) are both health records provided by Alpha Healthcare. 6A-6Q', if the user has completed the onboarding process with more than one health care provider, including information about medications provided by all of the user's health care providers. Medication records are simultaneously displayed on display 112. In that regard, Figure 6B' illustrates an alternative embodiment in which a user completes the onboarding process with Alpha Healthcare and Beta Healthcare. 6B', drug records (for GHI and JKL drugs, respectively) prescribed by Beta Healthcare in response to detecting a tap gesture at contact 5502 on category representation 5006D of FIG. 6A. (5018C, 5018D) are displayed simultaneously with drug records (5018A, 5018B) prescribed by Alpha Healthcare. In that way, the user can review all of the user's prescriptions from the user's health care providers in one interface. In the illustrated embodiment, medication records 5018A-5018D are organized by prescription date. In other embodiments, the medication records included in FIGS. 6A-6Q' may be organized by health care provider, by condition treated, or in any other suitable manner.

FIG. 6B' also shows the affordance of health records to display category representations 5006A-5006E of FIG. 6C (categories of Allergies, Clinical Documentation, Lab Results, Medications, and Health Conditions, respectively). 5304 Above illustrates detecting a tap gesture at the contact portion 5504'. Figure 6C illustrates re-displaying category representations 5006A-5006E in response to detecting a tap gesture at contact 5504 or 5504' over affordance 5304 of health records. FIG. 6C further displays three representations 5015A - 5015C of the subcategories of clinical documents of FIG. 6D (subcategories of x-ray images, CT-scans, and ultrasound images, respectively). For example, detecting a tap gesture at contact 5506 on a category representation 5006B associated with clinical documents is illustrated.

FIG. 6D illustrates a display of a representation of all clinical documents 5017A as well as representations of subcategories of clinical documents 5015A-5015C. 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 illustrated in Figure 6D, each of subcategory representations 5015A-5015C is an affordance that includes text identifying that such affordance is associated with health records from a particular subcategory of clinical documents. The representation of all clinical documents 5017A is an affordance that includes text identifying that such affordance is associated with all health records in the clinical documents. Additionally, each of subcategory representations 5015A-5015C is selectable by the user to view the user's clinical documents from the associated subcategory. In the illustrated embodiment, subcategories of a category of clinical documents are formed based on the type of clinical document. In other embodiments, clinical documents obtained during different time periods (eg, within a year, within a quarter, within a month, or within another time period) are grouped into different subcategories of clinical documents based on those time periods. In further embodiments, subcategories of the user's health records are subcategorized based on other suitable means for organizing the user's health records. FIG. 6D further illustrates detection of a tap gesture at contact 5508 on subcategory representation 5015A associated with x-ray images to display x-ray records 5016A, 5016B of FIG. 6E. . FIG. 6E shows a display of health records associated with subcategory representation 5015A (e.g., subcategory of “X-Ray Images”, FIG. 6D). More specifically, x-ray records 5016A and 5016B are displayed. In the illustrated embodiment, x-ray records 5016A, 5016B are records of x-ray images of users and providers who ordered or performed x-ray examinations (Dr. Doe and Alpha for both records). Includes text identifying health care). In the embodiment illustrated in Figure 6E, both the physician (which may be the physician ordering or reviewing the x-ray image) and the facility are identified as providers. In that way, both the health care professional and the organization or facility associated with the health record can be identified in the health record. In other embodiments, multiple doctors may be listed to identify the doctor ordering the x-ray, or the doctor reviewing the x-ray. In such embodiments, both the health care provider organization and facility are identified to provide additional information to the user. Each of the x-ray records 5016A, 5016B also includes the date the x-ray image was taken (October 1, 2017 and September 1, 2017, respectively) and a photograph of the x-ray image. Contains text identifying the image file (5036A or 5036B). In some embodiments, the user can tap on one of the image files 5036A or 5036B to overlay a full screen photo of the x-ray image or to zoom in on a photo of the x-ray image. Alternatively, additional information regarding the X-ray image may be obtained, such as radiologist's notes or diagnosis.

Similar to Figure 6B, in Figure 6E, x-ray records 5016A, 5016B are both health records provided by Alpha Healthcare. Figure 6E' illustrates an alternative embodiment in which a user completes the onboarding process with Alpha Healthcare and Beta Healthcare. 6E', in response to detecting a tap gesture at contact 5508 on subcategory representation 5015A (subcategory of x-ray images) of FIG. 6D, an ) is displayed simultaneously with x-ray records 5016A, 5016B from Alpha Healthcare. In that way, similar to the user interface of FIG. 6C', the user can review all of the user's x-ray images from the user's health care providers in one interface. In the illustrated embodiment, x-ray record 5016C contains text identifying the providers (Dr. Smith and Beta Healthcare) and the date such x-ray images were taken (September 15, 2017), as well as - Contains an image file (5036C) containing a photo of the line image. Although not illustrated in Figure 6E', in one embodiment, health records from different subcategories of clinical documents from both Alpha Healthcare and Beta Healthcare, for example, all clinical documents illustrated in Figure 6D. Upon user selection of the representation 5017A, it may be displayed in a single user interface.

6E and 6E' each show contacts (on the affordances 5307 of clinical documents) for displaying subcategory representations 5015A - 5015C of FIG. 6F (x-ray images, CT scans, and ultrasound images), respectively. Detecting a tap gesture at 5510 or 5510') is exemplified. 6F illustrates re-displaying subcategories 5015A-5015C in response to detecting a tap gesture at contact 5510 or 5510' over affordance 5308 of clinical documents. In some embodiments, a user may select subcategory representation 5015B or subcategory representation 5015C to view health records belonging to such different subcategories of health records. In the illustrated embodiment, a user may view their health records to view category representations 5006A - 5006E of FIG. 6G (categories of Allergies, Clinical Documentation, Lab Results, Medications, and Health Conditions, respectively). A tap gesture on the contact portion 5512 is performed on the affordance 5304. Figure 6G illustrates re-displaying category representations 5006A-5006E in response to detecting a tap gesture at contact 5512 over affordance 5304 of health records (e.g., as shown in Figure 6F). Illustrate.

FIG. 6G also illustrates detecting a tap gesture at contact 5514 on a representation of all records 5006F to simultaneously display health records from different categories in FIG. 6H. Figure 6H illustrates displaying health records from multiple categories of health records. In the illustrated embodiment, medication records and x-ray records are displayed simultaneously and organized by date. More specifically, Figure 6H shows x-ray records 5016A, 5016B and drug records 5018A, 5018B of x-ray images acquired on October 1, 2017 and September 1, 2017 (ABC Drugs). and DEF drugs). In the illustrated embodiment, health records are grouped based on dates of visits to health care providers. Medication record 5018A and x-ray record 5016A are displayed in the first group of health records from a visit to Alpha Healthcare dated October 1, 2017. Medication record 5018B and x-ray record 5016B are displayed in a second group of health records from a visit to Alpha Healthcare dated September 1, 2017. In the illustrated embodiment, health records are displayed in different colors to distinguish between different categories of health records. Medication records 5018A, 5018B are displayed in a first color representing medications, and x-ray records 5016A, 5016B are displayed in a second color representing clinical documents. In an alternative embodiment, x-ray records 5018A, 5018B are displayed in a color representing the subcategory of x-ray images. In other embodiments, health records may be displayed in groups, or colors may indicate certain characteristics, such as time period, date of visit, provider (where more than one provider is present, as described with respect to FIG. 6H'). been onboarded), category of health record, subcategory of health record, severity of condition, or any other suitable criteria. Characteristics such as health care providers may be further divided or differentiated by organization, physician, facility, or location. In that way, the groups in which health records are displayed, and the colors of those health records, can be used to allow a user to quickly visualize and distinguish between health records with different characteristics. In other embodiments, health records that meet a common criterion are typically displayed in a specific font to allow the user to distinguish health records by more than two criteria, which is available when only display groups and color are utilized. They may be displayed in groups, at specific locations, with specific icons, with specific graphical elements, or otherwise with specific visual characteristics.

6H, x-ray records 5016A, 5016B, and drug records 5018A, 5018B of x-ray images acquired on October 1, 2017 and September 1, 2017 (ABC Drug and DEF) medications) are all health records provided by Alpha Healthcare. Figure 6H' illustrates an alternative embodiment in which a user completes the onboarding process with Alpha Healthcare and Beta Healthcare. In FIG. 6H', drug record 5018C for an ) (GHI drug) and x-ray record 5016C are both obtained from Beta Healthcare and displayed simultaneously with the drug record 5018A and x-ray record 5016A from Alpha Healthcare. 6H', medication record 5018C and x-ray record 5016C are displayed as a group and represent health records from a visit to Beta Healthcare on September 15, 2017. In the illustrated embodiment, medication record 5018C and x-ray record 5016C are health records from a visit dated September 15, 2017, and medication record 5018B and x are health records from a visit dated September 1, 2017. -More recent than the previous record (5016B). Accordingly, drug record 5018C and x-ray record 5016C are displayed on display 112 instead of or prior to drug record 5018B and x-ray record 5016B. In one embodiment, the user performs a swipe gesture (not shown) to view less recent health records, such as medication records 5018B and x-ray records 5016B. In other embodiments, display 112 displays health records from more than two visits simultaneously.

6H and 6H' each further display category representations 5006A-5006E of FIG. 6I (categories of Allergies, Clinical Documentation, Lab Results, Medications, and Health Conditions, respectively). For this purpose, detecting a tap gesture at the contact portion 5516 or 5516', respectively, on the affordance 5304 of the health records is exemplified. Figure 6I illustrates re-displaying category representations 5006A-5006E in response to detecting a tap gesture at contact 5516 or 5516' over affordance 5304 of health records. FIG. 6I also illustrates detecting a tap gesture at contact 5518 on category representation 5006E to view health status records 5020A, 5020B, and 5020C of FIG. 6J.

Figure 6J illustrates displaying the user's health status records 5020A, 5020B, and 5020C. In the illustrated embodiment, health status record 5020A is a health record that includes information regarding the user's cholesterol level, the date the user's cholesterol was measured, and the name of the health care provider who measured the user's cholesterol level. In some embodiments, the value of the user's cholesterol level is displayed in an enlarged font, underlined, highlighted, or otherwise formatted to emphasize the user's cholesterol level. In some embodiments, the value of the user's cholesterol level is also displayed with a color indicating when the user's cholesterol level is within a range of cholesterol levels. For example, the value of the user's cholesterol level is green if the user's cholesterol level is less than 200 mg/dL, yellow if the user's cholesterol level is between 200 mg/dL and 300 md/dL, and yellow if the user's cholesterol level is between 200 mg/dL and 300 md/dL. If the level is above 300 mg/dL, it may be displayed in red. In one embodiment, the numeric value of the current cholesterol value is displayed within a range of numeric values. The numerical value indicates the severity of the user's cholesterol level, and the range of values indicates normal or severe health condition. Similar numerical values and ranges of numerical values may be used for other health conditions of the user to display normality or severity of any condition. Graphical representations of such values and ranges may also be utilized. In the illustrated embodiment, health condition record 5020B is a health record that includes information regarding the user's chronic migraines, medications prescribed to the user, date of prescription, and health care provider that provided the prescription to the user. Similarly, health condition record 5020C is a health record that includes information regarding the user's anxiety disorder, medications prescribed to the user, date of prescription, as well as the name of the health care provider who provided the prescription to the user. .

In Figure 6J, health status records 5020A through 5020C (cholesterol level, chronic migraine, and anxiety disorder, respectively) are all health records provided by Alpha Healthcare. Figure 6J' illustrates an alternative embodiment in which a user completes the onboarding process with Alpha Healthcare and Beta Healthcare. 6J', in response to detecting a tap gesture at contact 5518 on category representation 5006E (category of health conditions) of FIG. 6I, health condition record 5020D from Beta Healthcare is displayed as a health condition record. are displayed simultaneously with fields 5020A to 5020C. Health condition record 5020D, similar to health condition records 5020B and 5020C, contains information regarding the drug prescribed to treat the health condition, the date the drug was prescribed to the user, and the health condition that provided the prescription to the user. A health record that includes the name of the care provider. In some embodiments, each health condition record may also include information about the individual's health condition, such as a description of the health condition, symptoms, related health conditions, treatment options, lifestyle recommendations, and other suitable information regarding the individual's health condition. Includes additional information regarding your health status. In some embodiments, each health condition record is an affordance for a user to select to view additional information about the corresponding health condition. In that regard, FIGS. 6J and 6J' also show a tap gesture at contact 5520 or 5520', respectively, on health status record 5020A to display such additional information of FIG. 6K or 6K', respectively. This is an example of detection.

Figure 6K illustrates displaying additional information regarding health status record 5020A (user's cholesterol level). As illustrated in Figure 6K, cholesterol representation 5021A is displayed, including an indication of the user's current cholesterol level and an indication if the user's current cholesterol levels are within a range of cholesterol levels. More specifically, cholesterol representation 5021A graphically identifies the user's current cholesterol level in the range of 240 mg/dL to 300 mg/dL, thereby indicating high cholesterol (240 mg/dL) to very high cholesterol (300 mg/dL). mg/dL) range. In the illustrated embodiment, cholesterol representation 5021B is also displayed on display 112. As further illustrated in Figure 6K, cholesterol representation 5021B is displayed, including a bar graph of the user's cholesterol level over time, where each bar represents a measurement of the user's cholesterol level. In the depicted embodiment, different bars representing cholesterol levels within different ranges are displayed with different colors. In other embodiments, additional representations of the user's current and historical cholesterol levels are displayed. FIG. 6K also illustrates displaying historical health records of the user's cholesterol level in health status records 5030B and 5030C from September 1, 2016 and January 1, 2016, respectively. As used herein, a historical health record is a health record of any specific health information other than a current health record of such health information. For example, a medication record that contains information about medications that are no longer prescribed for the user is a historical health record. Additional examples of historical records are illustrated in at least FIGS. 8D and 8E and are discussed in subsequent paragraphs. In the illustrated embodiment, historical health records are also color-coded based on the severity of the user's health condition relative to normal. 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 less than 200 mg/dL. is greater than 300 mg/dL and is assigned a secondary color (e.g., red). In other embodiments, different colors are assigned to different ranges of cholesterol levels, identifying different severity levels of the user's health condition.

6K' illustrates displaying additional information regarding health status record 5020A from both Alpha Healthcare and Beta Healthcare. In the illustrated embodiment, with historical health records 5030B and 5030C previously described in Figure 6K (user's cholesterol levels measured as of September 1, 2016 and January 1, 2016, respectively) The historical health record (5030D) obtained from Beta Healthcare as of September 15, 2017 is displayed. In the illustrated embodiment, the user's cholesterol level as measured on September 15, 2017 is between 200 mg/dL and 300 mg/dL and is assigned a third color (eg, orange). Additionally, cholesterol representation 5021B includes bar graphs of the user's historical cholesterol levels obtained from both Alpha Healthcare and Beta Healthcare.

6L-6Q' illustrate user interfaces for displaying notifications of updates made to a user's health records on device 100. Updates to the user's health records may include updates to the user's existing health records or new health records. Similar to FIG. 6A , FIG. 6L shows category representations 5006A through 5006E (allergies, clinical documentation, lab results, respectively) after updates to the user's health records are received by device 100. categories of drugs, medications, and health conditions). In the illustrated embodiment, three updates have been received by device 100 that have not yet been reviewed by the user. To notify the user of the three updates, a global update badge 5104 is displayed, with a representation of all health records 5006F and category update badges 5106A, 5106B, and 5106C respectively representing category representations ( 5006B, 5006D, 5006E). In the illustrated embodiment, total updater badge 5104 is a circle containing the number of total updates to the user's health records. Similarly, category update badges 5106A, 5106B, and 5106C are circles containing the number of updates to health records within the health record category associated with category representations 5006B, 5006D, and 5006E, respectively. In the illustrated embodiment, total updates badge 5104 indicates that three updates have been received for health records that have not been reviewed, and category updates 5106A through 5106C each update to a health record within the corresponding health record category. , indicates that one update was received that was not reviewed. 6K and 6K' each further illustrate detecting a tap gesture at contact 5521 or 5521', respectively, on affordances 5306 of health states, which allows the user to use the user illustrated in FIGS. 6J and 6J' It is an affordance to choose to return to the interface.

Although Figure 6L illustrates one embodiment of a display of updater badges to indicate updates to a user's health records, other text, symbols, graphics, or displayed of any size, shape, color, or design may be used. The effect can be used to indicate an update or as an update badge to indicate the number of updates. For example, an update badge may be a highlighted or flashing category representation, or may display the time or date of the update. In some embodiments, overall update badge 5104 and category update badges, such as category update badges 5106A-5106C (respectively, provide updates to clinical documentation records, medication records, and records of health conditions). shown) are not displayed at the same time. In one or more of such embodiments, only category update badges are displayed on display 112. In one or more of such embodiments, only the full update badge 5104 is displayed on display 112. In some embodiments, a summary or portion of the content of the update is displayed on or along with the update badge. In one embodiment, the update badge is an affordance separate from the affordances of the category, and the user selects the update badge to display the updated health record or a summary or portion of the updated health record. Figure 6L further illustrates detecting a tap gesture at contact 5522 on category update badge 5106C to display an update to health status record 5020A of Figure 6M.

6L-6Q', in addition to or instead of an update badge, the user may receive notification of all updates via on-screen alerts, text messages, or audio or video notifications. . In some embodiments, such notifications may be based on whether certain health records are designated as urgent by the user or health care provider. In one embodiment, device 100 may be preconfigured with one or more thresholds for one or more types of health records, or may be configurable by the user to set them. When an update to a health record is received that has a particular result, measurement, value, reading, or other measurable aspect that exceeds an established threshold or otherwise satisfies a criterion, one or more notifications to the user may be displayed on device 100. is automatically created. In some embodiments, the method of notification may vary based on the severity of a particular result, measurement, value, reading, or other measurable aspect, or based on the type or number of thresholds reached. For example, a text message may be generated for some updates, while an audible alarm is generated for other updates that repeat regularly or at increasingly shorter intervals until the user completes the required action. It can be. In one embodiment, updates that are not urgent or do not exceed established thresholds do not trigger the creation of a notification.

Figure 6L' illustrates an alternative embodiment of Figure 6L after the user has completed the onboarding process with both Alpha Healthcare and Beta Healthcare. As illustrated in FIG. 6L', as a result of the inclusion of two health care providers instead of the single health care provider associated with FIG. 6L, four updates are now displayed, instead of the three updates of FIG. 6L. In the illustrated embodiment, overall update badge 5104 indicates that 4 overall updates have been received that have not been reviewed, and category update badge 5106A indicates that 2 updates to clinical records have been received but have not yet been reviewed. , category update badge 5106B indicates that an update has been received to medication records that have not been reviewed, and category update badge 5106C indicates that an update has been received to health condition records that have not been reviewed. Figure 6L' further illustrates detecting a tap gesture at contact 5522'on category update badge 5106C to display an update to health status record 5020A of Figure 6M'.

6M and 6M' display an update to health status record 5020A (user's cholesterol level) in response to detecting a tap gesture at contact 5522 or 5522', respectively, on category update badge 5106C. exemplifies this. In each of the illustrated embodiments, the user's cholesterol level has been updated to reflect new cholesterol measurements taken by Alpha Healthcare as of December 1, 2017. In each of the illustrated embodiments, a health record update badge 5140 is displayed with health record 5020A to indicate that health record 5020A has been updated. Health status record 5020A is displayed in color indicating the severity of the user's cholesterol level. In each of the illustrated embodiments, a recommendable affordance 5240A is displayed along with a health status record 5020A, including a recommended action to visit a doctor. In some embodiments, the affordance of the recommendation is a recommendation to engage in exercise, change the user's diet, or engage in other suitable actions that reduce the user's cholesterol levels. In some embodiments, advisory affordance 5240A also includes content indicating the importance of an update or the severity of the user's condition. In one or more of such embodiments, a user can self-specify the importance of certain types of health records as well as updates to certain types of health records. For example, a user may designate all updates to the user's cholesterol level as urgent updates. In one or more of such embodiments, a user assigns importance to certain types of health records based on the amount of positive or negative change in the user's health status. For example, a user may specify the importance of updates to the user's cholesterol level based on the amount of change in the user's cholesterol level. In other embodiments, a health care provider may specify the importance of certain updates. Although the discussion of FIGS. 6M and 6M' above relates to recommendations and updates thereto based on the user's cholesterol, the preceding paragraphs also apply to other types of health records. For example, if a user receives a new measurement of serum iron, an advisory affordance may be displayed on display 112 advising the user to change the user's diet to increase sources of iron. You can.

6M and 6M' illustrate a tap gesture at contact 5524 or 5524', respectively, on affordance 5240A of recommendations, including recommendations based on the user's cholesterol level, to display affordance 5241 of the calendar in Figure 6N. Detecting is further exemplified. More specifically, Figure 6N illustrates the display of affordance 5241 of a calendar overlaid on the user interface illustrated in Figure 6M or Figure 6M'. Figure 6N also illustrates the detection of a tap gesture at contact 5526 on the date January 8 on affordance 5241 of a calendar. In that manner, the user can select a date to schedule an appointment with the doctor that matches the recommendation displayed in the recommendation affordance 5240A. Additional affordances may be utilized to select an appointment time or to display or enter additional information about the appointment. In some embodiments, affordance 5241 of the calendar or additional affordances displays dates and times based on the user's availability and the doctor's available appointments.

Figures 6O and 6O' each illustrate displaying an update to the affordance 5240A of a recommendation. In each illustrated embodiment, the affordance of the recommendation 5240A for the health condition record 5020A has been updated to include text indicating the name of the doctor the user is scheduled to see and the date of the appointment. In some embodiments, device 100 will specify a time to display or otherwise announce a notification to remind the user about an upcoming appointment. 6O and 6O' also show contacts at contacts 5527 or 5527', respectively, on the affordances 5304 of the health records to display any remaining updates to the health records in FIGS. 6P and 6P', respectively. Detecting a tap gesture is illustrated.

6P and 6P' illustrate category representations 5006A-5006E (categories of allergies, clinical documentation, lab results, medications, and health conditions, respectively) and remaining updates to the user's health records. Illustrate the display. In the embodiment of Figure 6P, if the user has onboarded only one healthcare provider, total updates badge 5104, which represents the total number of updates received by device 100 but not reviewed by the user, is Updated from 3 updates to 2 updates to indicate the remaining number of updates still to be reviewed. Category update badge 5106C, which was previously displayed with representation category 5006E (category of health conditions) in FIG. 6L, is no longer displayed because the user has reviewed the update to health condition record 5020A. . Similarly, in the embodiment of Figure 6P', if the user has onboarded two healthcare providers and there are more updates as a result, the total updates badge 5104 indicates the remaining number of updates the user still has to review. It has been updated from 4 updates to 3 updates to indicate . Similar to Figure 6P, category update badge 5106C, which was previously displayed with representation category 5006E in Figure 6L', is no longer displayed because the user has reviewed the update to health status record 5020A. am. Figures 6P and 6P' each further illustrate detecting a tap gesture at contact 5528 or 5528', respectively, on a badge 5104 of full updates to display Figure 6Q or Figure 6Q', respectively.

6Q and 6Q' each display updates to multiple types of health records. The illustrated embodiment of FIG. 6Q displays the first update of the new medication record 5018E for a new prescription of an ABC drug prescribed by Alpha Healthcare as of December 1, 2017; A second update of the new x-ray record 5016D of the x-ray taken at Alpha Healthcare is displayed with update badges 5142 and 5144, respectively. In some embodiments, health record update badges that are for updates to existing health records and updates to new health records allow a user to switch between updates to existing health records and updates to new health records. have different symbols, shapes, sizes, text fonts, text colors, or other visual differences to help distinguish them. The illustrated embodiment of FIG. 6Q' also includes a medication record 5018E of an ABC drug, a record 5020A of health conditions of the user's cholesterol level, and an x-ray image dated December 1, 2017. -Illustrates displaying line record 5016D. In addition to the updates from Alpha Healthcare as of December 1, 2017 in the new drug record (5018E) and the new A third update of a new x-ray record (5016E) taken at Beta Healthcare as of November 15, 2016 is displayed along with a health record update badge (5146).

7A-7F are flow diagrams illustrating a method for displaying a user's aggregated health records using an electronic device, according to some embodiments. Figures 7A-7F are flow diagrams illustrating a method for displaying aggregated health records for a user, for example using the user interfaces of Figures 6A-6Q'. As described with reference to FIGS. 6A-6Q', method 700 may be utilized to display the user's aggregated health records from one health care provider or from multiple health care providers. there is. Method 700 is performed at a device (e.g., devices 100, 300, and 500 illustrated in FIGS. 1, 3, and 5A, respectively). In one such embodiment, display 112 is a touch screen display, and a touch-sensitive surface is on or integrated with display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. Some operations within method 700 are optionally combined. Additionally, the order of some operations is optionally changed.

As described below, method 700 provides an intuitive way to display aggregated health records obtained from the user's health care provider. Method 700 also provides an intuitive way to simultaneously display aggregated health records obtained from a user's multiple health care providers. The method reduces cognitive burden on the user when the user is viewing the user's health records obtained from one or more of the user's health care providers, thereby creating a more efficient human-machine interface. The method also increases user efficiency by simultaneously displaying health records obtained from multiple health care providers. For battery-operated computing devices, allowing users to review health records obtained from a health care provider or multiple health care providers faster and more efficiently saves power and increases time between battery charges. .

Similar to FIGS. 6A-6Q', using method 700, a user can visualize health records in a common interface. The use of such a common interface avoids the risk that users may be viewing health information that is not complete and relevant to a particular interest or issue. For example, a user may not be aware that blood tests taken by two different providers tested for a particular condition and provide inaccurate information to a hospital or other subsequent provider. Similarly, the use of device 100 to store health records across multiple providers for the user to view in a common interface allows for information about the user's health over a period of time, even if the user moves or changes providers. It can provide users with an easily available source of comprehensive information. Often, former health care providers may destroy health records after a period of time when the patient does not see that health care provider, and such information may be lost forever. Such health records may include important health history information and baseline data important for diagnosing and treating subsequent conditions. Additionally, use of such a common interface may allow a user to use device 100 to access various locations on device 100, or other websites, portals, and other information, to aggregate information about a particular health condition. It avoids the need to retrieve data from sources, with the risk that information may be overlooked, not readily available, or only available after a too lengthy electronic search using device 100. Additionally, storing such health records within device 100 and providing a single interface that allows the user to view and browse all of such health records allows the user to aggregate health records from multiple sources. Multiple health care providers using device 100 to make back-and-forth voice calls (often with too long holding times), interactive phone systems, voicemails, email, etc. and avoids the need to communicate with other electronic messaging platforms. The required half-a-day or more use of device 100 to compile the above-described information can now be accomplished with a few clicks on device 100 by the user at the interface illustrated in FIG. 6B'. This can result in significant savings in previously wasted bandwidth, battery life, and energy.

Figures 7A-7F are flow diagrams illustrating a method for displaying aggregated health records for a user, for example using the user interfaces of Figures 6A-6Q'. As described with reference to FIGS. 6A-6Q', method 700 may be utilized to display the user's aggregated health records from one health care provider or from multiple health care providers. there is. Method 700 is performed at a device (e.g., device 100, 300, 500). In one such embodiment, display 112 is a touch screen display, and a touch-sensitive surface is on or integrated with display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. Some operations within method 700 are optionally combined. Additionally, the order of some operations is optionally changed.

Similar to FIGS. 6A-6Q', using one or more embodiments of the method 700 described below as illustrated by FIGS. 7A-7F, a user can visualize health records in a common interface. Use of such methods avoids the risk that users may be viewing health information that is not complete and relevant to a particular interest or issue. For example, a user may not be aware that blood tests taken by two different providers tested for a particular condition and provide inaccurate information to a hospital or other subsequent provider. Similarly, use of the method on a device, such as device 100, to store health records across multiple providers for viewing by a user in a common interface allows the user to move or change providers over a period of time. may provide the user with an easily available source of comprehensive information regarding the user's health. Often, former health care providers may destroy health records after a period of time when the patient does not see that health care provider, and such information may be lost forever. Such health records may include important health history information and baseline data important for diagnosing and treating subsequent conditions. Additionally, use of such methods may allow a user to use a device, such as device 100, to access various locations on such device, or other websites, portals, and other information, to aggregate information about a particular health condition. It avoids the need to retrieve data from sources, with the risk that information may be overlooked, not readily available, or only available after a too long electronic search using the device. Additionally, storing and displaying such health records using such a method on a device, such as device 100, and providing a single interface that allows a user to view and browse all of such health records from multiple sources. The user uses the device to compile health records of multiple health care providers, interactive phone systems, voicemails, emails, with back and forth voice calls (often with too long holding times). and avoids the need to communicate with other electronic messaging platforms. The required half-day or more use of such a device to compile the above-mentioned information is now replaced by the use of a method that requires only a few clicks on the device by the user, thereby reducing the bandwidth, battery life, and energy that was previously wasted. and can result in significant savings in energy.

In some embodiments, while device 100 is associated with a first health care provider and not with a second health care provider, device 100 records health records for the user, via one or more input devices. A first request to display is received (702). In some embodiments, once the user completes the onboarding process with the health care provider, a request to display health records is automatically transmitted to device 100. In some embodiments, a user selects affordance 5029A of health data illustrated in FIG. 6A or an affordance displayed in the onboarding user interface to request device 100 to display health records for the user. In some embodiments, the request to display health records is a request to display health records of multiple users, such as family health records.

Device 100, in response to receiving the first request to display health records for the first user, displays (704) a plurality of representations of categories of health records on display 112. FIG. 6A illustrates, for example, five categories of health records (e.g., category representations 5006A-5006E).

The plurality of representations of categories includes a first representation of a first category among the plurality of categories (706). Figure 6A shows, for example, a category representation 5006D associated with the user's medications. Additionally, selection of a first representation of the first category while device 100 is associated with a first health care provider and not a second health care provider causes device 100 to display to display 706 a plurality of health records within a first category from a first health care provider. In the embodiment illustrated in Figure 6B, the user is only associated with Alpha Healthcare and not Beta Healthcare. FIG. 6B shows one embodiment in which, for example, only medication records 5018A, 5018B (ABC Medication and DEF Medication) from Alpha Healthcare alone are displayed on device 100.

The plurality of representations also includes a second representation of a second one of the plurality of categories (708). FIG. 6I illustrates a category representation 5006E associated with, for example, a user's health conditions. Additionally, selection of a second representation of the second category while device 100 is associated with a first health care provider and not a second health care provider causes device 100 to display to display (708) a plurality of health records in the second category from the first health care provider. FIG. 6J shows, for example, two health status records 5020A and 5020B (cholesterol level and chronic migraine) in response to detecting the tap gesture shown in FIG. 6I over category representation 5006E.

In some embodiments, the first type of health records are displayed in a first color and the second type of health records are displayed in a second color that is different from the first color (718). 6H shows, for example, displaying x-ray records 5016A, 5016B (dated October 1, 2017 and September 1, 2017, respectively) in a first color, and drug records. Illustrative of displaying fields 5018A and 5018B (ABC drug and DEF drug) in a second color. Different types of health records are displayed in different colors to help the user distinguish health records belonging to different categories (or subcategories). In some embodiments, when multiple health records belonging to different categories are displayed simultaneously, a user may rely solely on colors to determine which category (or subcategory) a health record belongs to. In other embodiments, when multiple records from different health care providers are displayed simultaneously, the user may also rely on colors to distinguish different health records from different health care providers. Additionally, displaying different types of health records in different colors also reduces the risk of incorrectly identifying a health record (or failing to identify a health record) when the user is browsing the user's health records. Reduces user errors (such as The above allows the user to distinguish between different types of health records based on color, thereby improving the operability of the device and making the user-device interface more efficient. The method also increases user efficiency by allowing the user to identify health records by a color assigned to the type of health record. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 displays, on display 112, first content summarizing the first category and an affordance of first category information associated with the first category, wherein the first category information Selection of the affordance causes the device 100 to display, on the display 112, additional content associated with the first category that is not included in the first content (720). In some embodiments, category representation 5006E of Figure 6I (category of health conditions) includes the affordance of a summary that includes content that summarizes the user's particular health condition. Additionally, device 100, in response to detecting the user's selection of the affordances of the summary, may provide additional information about the user's health conditions, such as the reason for the health condition, a method for identifying symptoms of the health condition, and alleviating the health condition. Displays non-medical treatments to treat as well as other helpful information about your health condition.

In some embodiments, device 100 also displays, on display 112, second content summarizing the second category, and affordances of second category information of the second category, wherein the second category Selection of the affordance of information causes device 100 to display, on display 112, additional content associated with the second category that is not included in the second content (720). In some embodiments, category representation 5006B (a category of clinical documents as shown in Figure 6G) includes the affordance of a summary that includes content summarizing allergies experienced by the user. Additionally, device 100, in response to detecting the user's selection of the affordances of the summary, may provide additional information about allergies suffered by the user, such as methods for reducing or preventing triggers of specific allergies, symptoms of allergies, etc. It displays other helpful information about allergies as well as non-medical treatments for relief. Category representations are provided in the content containing descriptions of categories of health records. The method increases user efficiency by allowing the user to make a known selection of a category of health records based on descriptions of different categories of health records. The method also improves the operability of the device and user-device interface by helping the user provide appropriate inputs and reducing the number of extraneous inputs caused by the user selecting the wrong category of health records. makes it more efficient. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the plurality of health records within the first category are displayed in chronological order (722). 6B' shows drug records 5018A, 5018B (ABC drug and DEF drug) arranged based on prescription date, for example. In some embodiments, the plurality of health records within the second category are displayed in chronological order (722). 6J shows health condition records 5020A - 5020C arranged based on prescription dates of medications prescribed for health conditions, for example, associated with cholesterol level, chronic migraine, and anxiety disorder, respectively. shows. Presenting health records in chronological order allows the user to view the user's health records based on date, which increases user efficiency. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 detects selection of a first representation of a first category while device 100 is associated with a first health care provider (724). FIG. 6I shows, for example, a tap gesture at contact 5518 on a category representation 5006E (a category of health conditions). In some embodiments, device 100 displays, on display 112, a selection of a first representation of a first category while device 100 is associated with a first health care provider. 1 Display 724 a first representation of a first health record among a plurality of health records in a first category from a health care provider. 6J illustrates, for example, health status record 5020A, where health status record 5020A includes the user's cholesterol level as measured by Alpha Healthcare as of October 1, 2017. The first representation of the first health record includes a numeric value within a range of numeric values, where the numeric value represents a health state of the first user, where the range of values represents a normal range of values for the health state (724) . The health conditions record 5020A illustrated in FIG. 6J includes a value of the user's cholesterol level of 269 mg/dL. In some embodiments, health status record 5020A also includes values representing a range of cholesterols, such as 0 to 400 mg/dL. The method reduces cognitive burden on the user by providing the user with numerical values that enable the user to determine the severity of a health condition based on the numerical values, thereby creating a more efficient human-machine interface. The method also increases user efficiency by allowing the user to quickly identify the severity of a health condition from numerical values. For battery-operated computing devices, power savings allow users to more quickly and efficiently identify the severity of a health condition, medical records associated with the condition, as well as health status over time. Saves and increases time between battery charges.

In some embodiments, device 100 displays a numeric value in a color selected based on the severity of the first user's health condition (726). In some embodiments, the user's cholesterol value is displayed in green if the value is less than 200 mg/dL, yellow if the value is between 200 mg/dL and 300 mg/dL, and the value If it exceeds 300 mg/dL, it is displayed in red. Displaying numerical values based on the severity of the user's health condition allows the user to determine the severity of the health condition without complex knowledge of how to read the numerical value, thereby creating a more efficient human-machine interface. do. The method also increases user efficiency by allowing the user to quickly identify the severity of a health condition based on the color associated with the numerical value. For battery-operated computing devices, allowing users to identify the severity of a health condition faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 displays a second representation of a second health record among a plurality of health records in a first category from a first health care provider, wherein the second representation of the second health record is It includes a graph representing the state of the first user over a certain period of time (728). FIG. 6K shows, for example, a cholesterol representation 5021B in response to detecting the tap gesture illustrated in FIG. 6J on health status record 5020A (the user's cholesterol level). Cholesterol representation 5021B is a bar graph of the user's cholesterol level over time. The method also reduces the cognitive burden on the user by providing the user with images of the user's medical history (which provides the user with information about the user's condition over time), thereby making the user more efficient. -Create machine interface. The method also increases user efficiency by allowing the user to quickly identify the user's health status over time in one common interface, without having to navigate multiple user interfaces. For battery-operated computing devices, allowing a user to identify the user's health status over time faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the plurality of health records in a first category from a first health care provider include a first health record in a first category from a first health care provider and a first health record in a first category from a first health care provider. 2 Includes health records (730). FIG. 6B depicts two drug records 5018A, 5018B (ABC Drug and DEF Drug) obtained, for example, from Alpha Healthcare.

In some embodiments, the plurality of health records in the second category from the first health care provider include a third health record in the second category from the first health care provider and a third health record in the second category from the first health care provider. 4 Includes health records (730). FIG. 6E shows two x-ray records 5016A, 5016B (dated October 1, 2017 and September 1, 2017, respectively) obtained, for example, from Alpha Healthcare.

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

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

In some embodiments, and in response to receiving the first request to display health records for the first user, device 100 displays, on display 112, the first health record in the first group and the first health record in the first group. Three health records are displayed simultaneously, where the first group is identified on display 112 by the first date of the first visit (730). 6H shows, for example, grouping drug records 5018A (ABC drugs) and x-ray records 5016A within a first group, with drug records 5018A and The line record 5016A is displayed simultaneously.

In some embodiments, and in response to receiving the first request to display health records for the first user, device 100 may display, on display 112, a second health record in the second group and a second health record in the second group. Displays four health records simultaneously, where a second group is identified on display 112 by a second date of the second visit, where the first date is different from the second date (730). Figure 6H shows, for example, grouping drug record 5018B (DEF drug) and x-ray record 5016B within a second group. Additional drug record 5018B and x-ray record 5016B are displayed simultaneously on display 112. The method reduces cognitive burden on the user when he or she is viewing health records by grouping health records based on appointment dates with a health care provider and arranging different groups based on appointment dates. Optionally, if the health records are from multiple health care providers, the health records are grouped by health care provider and appointment date, and the groups are arranged by appointment date. Optionally, the method reduces cognitive burden on the user when the user is viewing health records by displaying health records belonging to different categories in different colors to help the user distinguish between different categories of health records. I order it. Optionally, the method also reduces cognitive burden on the user when the user is viewing health records by displaying update badges with updates to the health records. Each of the above creates a more efficient human-machine interface. The method also increases the efficiency of the user by allowing the user to identify health records based on the date of the appointment with the health care provider and based on different appointment dates with different health care providers. The method also allows the user to view different health records from different health care providers in a common interface, thereby increasing the efficiency of the user and making the user-device interface more efficient. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the first health record in a first category from the first health care provider and the second health record in the first category from the first health care provider are displayed in a first color (732). FIG. 6H illustrates, for example, medication record 5018A (ABC Drug) and x-ray record 5016A, dated October 1, 2017, in first color.

In some embodiments, the third health record in the second category from the first health care provider and the fourth health record in the second category from the first health care provider are displayed in a second color that is different from the first color. (732). FIG. 6H shows, for example, drug record 5018B (DEF drug) and x-ray record 5016B, dated September 1, 2017, in a second color that is different from the first color. Displaying different categories of health records with different colors allows the user to quickly distinguish between different health records, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to identify health records based on color. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives (734) an update to a first health record within a first category from a first health care provider. 6L illustrates, for example, a number of updates from Alpha Healthcare (e.g., category representation for clinical dossiers 5006B, category representation for medications 5006D, and category representation for health conditions 5006E). ) exemplifies receiving updates for ). In some embodiments, device 100 displays, on display 112, a first update badge associated with a first health record of the first group, where the first update badge and the first health record are displayed ( 112) are simultaneously displayed in the first area. FIG. 6L illustrates, for example, a category update badge 5106C and a category representation 5006E in a region of display 112. In some embodiments, category update badge 5106C is attached to category representation 5006E. The method reduces cognitive burden on the user by allowing the user to identify which health records have been updated, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing users to identify updated health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 displays a third representation of a third health record among the plurality of health records in a first category from a first health care provider, wherein the third representation of the third health record is Contains an image representing the first user's medical record (736). In some embodiments, an image of an x-ray associated with an x-ray record, such as It is displayed. In some embodiments, such as Figure 6E, if x-ray recording 5016A includes an image file 5036A of an x-ray image, selection of image file 5036A causes device 100 to Let file 5036A be enlarged. The method reduces the cognitive burden on the user by providing the user with images of the user's medical records (which allows the user to quickly assess the health condition associated with the medical records), thereby creating a more efficient human-machine system. Create an interface. For battery-operated computing devices, allowing a user to assess the user's health status faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives updates to certain health records in the first category of health records (738). 6L illustrates, for example, a number of updates from Alpha Healthcare (e.g., Category Representation for Clinical Documents 5006B, Category Representation for Medications 5006D, and Category Representation for Health Conditions 5006E). ) exemplifies receiving updates for ). In some embodiments, after receiving an update to the first category of health records, and at least one of the first request to display health records for the first user and the second request to display health records for the first user. In response to receiving one, device 100 displays, on display 112, a second update badge associated with the first category, wherein the first representation of the first category and the second update badge are displayed ( It is simultaneously displayed in the first area of 112 (738). 6M illustrates, for example, in response to detecting the gesture in FIG. 6L over category representation 5006E, medication records 5020A through 5020C (related to cholesterol level, chronic migraine, and anxiety disorder of the user, respectively). ) is shown. FIG. 6M also shows health record update badge 5140 with health record 5020A to indicate that health record 5020A has been updated. The method reduces cognitive burden on the user by allowing the user to identify which health records have been updated, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing users to identify updated health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the second update badge is visually associated with the first representation of the first category (740). FIG. 6L illustrates, for example, a category update badge 5106C and a category representation 5006E (a category of health conditions) in a region of display 112. In some embodiments, category update badge 5106C is attached to category representation 5006E. The method reduces cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health records, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing users to identify updated health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, selection of a first representation of the first category while device 100 is associated with a first health care provider causes device 100 to display, on display 112, a selection of health records. Display a representation of a health record of one category, wherein the second update badge is visually associated with the representation of the health record of the first category of health records (742). FIG. 6M illustrates, for example, health record update badge 5140 and health status record 5020A (related to the user's cholesterol level) within the same area. In one or more embodiments, health record update badge 5140 is attached to health status record 5020A. The method reduces cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health records. The method reduces cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health records, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to quickly identify which health records have been updated. For battery-operated computing devices, allowing users to identify updated health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the second update badge includes content of an update to the health record on the second update badge (744). In some embodiments, the content of the update, such as a summary of the update, may be displayed as an update badge, such as category update badge 5106A, 5106B, or 5106C shown in FIGS. 6L and 6M, health record update badge 5140, or full update. displayed on badge 5104. The method reduces the cognitive burden on the user by allowing the user to identify the content of the update or a summary of the content of the update without having to perform additional actions, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to quickly identify changes in health status associated with updated health records. For battery-operated computing devices, allowing a user to identify changes in the user's health status faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives, via one or more input devices, a request to select a second update badge (746). In some embodiments, overall update badge 5104 and category update badges 5106A - 5106C (each, shown in Figure 6L) include affordances of updates, which allow the user to determine the corresponding health These are the affordances of choosing to view updates to records. Figure 6L shows, for example, a tap gesture at contact 5522 on a category update badge 5106C. In some embodiments, and in response to receiving a request to select a second update badge, device 100 displays an update to a health record of the first category of health records on display 112 (746). FIG. 6M illustrates, for example, an update to health status record 5020A (a health record of the user's cholesterol level) in response to detecting the tap gesture illustrated in FIG. 6L. As illustrated in FIG. 6M, health status record 5020A has been updated to indicate the user's cholesterol level as of December 1, 2017. The method reduces cognitive burden on the user by allowing the user to identify which categories contain updates to the user's health records. The method reduces cognitive burden on the user by allowing the user to access updates to health records by selecting an update badge, which creates a more efficient human-machine interface. The method also increases user efficiency by allowing users to easily access updates by selecting an update badge. For battery-operated computing devices, allowing a user to access updates to the user's health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 simultaneously displays 748 the affordances of updates to the health record and recommendations associated with the health record. FIG. 6M illustrates, for example, simultaneous display of a record of health conditions 5020A (a health record of the user's cholesterol level) and an affordance of a recommendation 5240A. In some embodiments, device 100 receives, via one or more input devices, a request to select an affordance of a recommendation (748). Figure 6M, for example, also shows a tap gesture at contact 5524 over advisory affordance 5240A. In some embodiments, and in response to receiving a request to select an affordance of a recommendation, device 100 displays, on display 112, a recommended action, where the recommended action is for health records. Based on update (748). FIG. 6N illustrates affordance 5241 of a calendar in response to the gesture illustrated in FIG. 6M , for example. In the illustrated embodiment, the recommended action is to schedule an appointment with a doctor. In some embodiments, content describing or illustrating the recommended action is also displayed along with the affordance of the recommendation 5240A. FIG. 6M shows a recommendation affordance 5240A that includes text of a recommended action, for example, to visit a doctor. The method reduces the user's cognitive burden by providing recommendations without user input, thereby creating a more efficient human-machine interface. The method also increases user efficiency by automatically providing response strategies to the user. For battery-operated computing devices, allowing users to more quickly and more efficiently decide not only whether to respond to updates to their health records, but also how to respond to updates, saves power and recharges the battery. Increase the time between sessions.

In some embodiments, the recommendation is a recommendation to schedule an appointment with a first health care provider (750). In such embodiments, displaying the recommended action includes simultaneously displaying the recommended action and the affordance of scheduling (750). FIG. 6N illustrates affordance 5241 of a calendar in response to the gesture illustrated in FIG. 6M , for example. In the illustrated embodiment, the recommended action is to schedule an appointment with a doctor. The method reduces the user's cognitive burden by providing recommendations without user input, thereby creating a more efficient human-machine interface. The method also increases user efficiency by automatically providing response strategies to the user. For battery-operated computing devices, allowing users to more quickly and more efficiently decide not only whether to respond to updates to their health records, but also how to respond to updates, saves power and recharges the battery. Increase the time between sessions.

In some embodiments, device 100 receives updates to certain health records in the first category of health records (752). 6L illustrates, for example, a number of updates from Alpha Healthcare (e.g., Category Representation for Clinical Documents 5006B, Category Representation for Medications 5006D, and Category Representation for Health Conditions 5006E). ) exemplifies receiving updates for ). In some embodiments, device 100 displays a notification of the update on display 112 in response to receiving an update to the health record and in accordance with a determination that the importance of the update exceeds a threshold ( 752). Recommendation affordance 5240A of FIG. 6M includes the text “Urgent!” to indicate, for example, the importance of changes in the user's cholesterol. In some embodiments, the updates and notifications of the importance of the updates overlay a portion of the display 112 even when the user interfaces illustrated in FIGS. 6A-6Q' are not displayed on the display. In one or more embodiments, the notification is a text-based notification.

Device 100 withholds displaying the notification of the update on display 112 (752), depending on the determination that the importance of the update is below the threshold. In some embodiments, if the user's cholesterol level has not significantly changed or improved or has not met a threshold for providing notification regarding an update, then the affordance of recommendation 5240A of FIG. 6M or FIG. 6M' is not displayed on the display 112. The method reduces cognitive burden on the user by notifying the user about important updates, thereby creating a more efficient human-machine interface. The method also increases efficiency for the user by allowing the user to determine whether an update is an important update based on the presence or absence of a notification. For battery-operated computing devices, allowing users to determine faster and more efficiently whether an update is important saves power and increases time between battery charges.

Device 100, after displaying the plurality of representations of categories of health records and after being associated with a second health care provider, sends, via one or more input devices, a second request to display health records for the first user. Receive (710). In some embodiments, when the user has completed the onboarding process with multiple health care providers, the user requests device 100 to display health records obtained from two or more health care providers.

After device 100 processes the user's request to display health records obtained from two or more health care providers, device 100 receives a second request from the user to display the user's health records. . Device 100, in response to receiving the second request to display health records for the first user, displays (712) a plurality of representations of categories of health records on display 112. FIG. 6A shows, for example, five category representations 5006A - 5006E (categories of Allergies, Clinical Documents, Lab Results, Medications, and Health Conditions, respectively).

The plurality of representations of categories includes a first representation of a first category among the plurality of categories (714). FIG. 6A shows, for example, a category representation 5006D (category of drugs) associated with the user's drugs. Additionally, selection of the first representation of the first category while device 100 is associated with the first health care provider and the second health care provider causes device 100 to display, on display 112, a first representation of the first category. Display 714 one or more health records in a first category from a health care provider and one or more health records in a first category from a second health care provider. Figure 6b' illustrates, for example, an alternative embodiment to Figure 6b. In the example of Figure 6B', the user completed the onboarding process with both Alpha Healthcare and Beta Healthcare. In this embodiment, device 100 may make a gesture at contact 5502 on category representation 5006D, illustrated in FIG. 6A, or category representation 5006D while associated with Alpha Healthcare and Beta Healthcare. A similar gesture of selecting causes device 100 to display medication records obtained from both Alpha Healthcare and Beta Healthcare. In that regard, Figure 6B' shows drug records 5018A, 5018B (ABC Drug and DEF Drug) from Alpha Healthcare, in response to detecting the tap gesture shown in Figure 6A on category representation 5006D, and Two drug records (5018C, 5018D) from Beta Healthcare are shown (GHI drug and JKL drug).

The plurality of representations of the categories of health records also include a second representation of a second one of the plurality of categories (716). FIG. 6I shows, for example, a category representation 5006E (category of health conditions) associated with the user's health conditions.

Additionally, selection of the second representation of the second category while device 100 is associated with the first health care provider and the second health care provider causes device 100 to display, on display 112, a first representation of the first health care provider. Display 716 one or more health records in a second category from a health care provider and one or more health records in a second category from a second health care provider. Figure 6J' illustrates, for example, an alternative embodiment to Figure 6J. In the example of Figure 6J', the user completed the onboarding process with both Alpha Healthcare and Beta Healthcare. In this embodiment, a gesture at contact 5518 on category representation 5006E (category of health conditions) illustrated in FIG. 6I while device 100 is associated with Alpha Healthcare and Beta Healthcare, or A similar gesture selecting category representation 5006E causes device 100 to display health status records obtained from both Alpha Healthcare and Beta Healthcare (716). In that regard, Figure 6J' shows health status records 5020A-5020C from Alpha Healthcare (cholesterol level, chronic migraine, and anxiety disorders), and a health condition record (5020D) from Beta Healthcare (arthritis).

In some embodiments, device 100 receives 754 a first selection of a first representation of a first category, via one or more input devices. FIG. 6C illustrates, for example, a tap gesture at contact 5506 on a category representation 5006B (a category of clinical documents).

In some embodiments, and in response to receiving the first selection, device 100 displays (754) a plurality of representations of subcategories of health records in the first category on display 112. FIG. 6D illustrates subcategory representations 5015A through 5015C (respectively, x-ray images), e.g., in response to detecting the tap gesture shown in FIG. 6C over category representation 5006B (a category of clinical documents). subcategories of images, CT-scans, and ultrasound images).

In some embodiments, the plurality of subcategories of health records include a first representation of a first subcategory of a first category (754). FIG. 6D illustrates, for example, a subcategory representation 5015A (a subcategory of x-ray images) in response to detecting the tap gesture shown in FIG. 6C over category representation 5006B. In the illustrated embodiment, representation 5015A of subcategory is associated with x-ray images. Additionally, selection of the first representation of the first subcategory of the first category may cause device 100 to display, on display 112, a plurality of representations within the first subcategory of the first category from the first health care provider. Display health records (754). FIG. 6E shows, for example, x-ray records 5016A and 5016B (October 1, 2017 and 2017, respectively) in response to detecting a tap gesture on subcategory representation 5015A shown in FIG. 6D. (ordered as of September 1).

In some embodiments, the plurality of subcategories of health records include a second representation of a second subcategory of the first category (754). FIG. 6D illustrates, for example, a subcategory representation 5015A (x-ray image) in response to detecting the tap gesture shown in FIG. 6C at contact 5506 on a category representation 5006B (a category of clinical documents). subcategories). Additionally, selection of a second representation of the first category 5015B (CT-scan subcategory, FIG. 6D) causes device 100 to display, on display 112, a first health care provider. Display 754 a plurality of health records within a second subcategory of the first category from. Figure 6E' shows x-ray records 5016A, 5016B obtained from Alpha Healthcare and x-ray records obtained from Beta Healthcare in response to detecting a tap gesture on the subcategory representation 5015A shown in Figure 6D Illustrative of displaying line record 5016C. In a similar embodiment, if a tap gesture is detected on the subcategory representation 5015B while the user has completed the onboarding process with both Alpha Healthcare and Beta Healthcare, the acquisition is obtained from both Alpha Healthcare and Beta Healthcare. Health records from the CT-scan will be displayed on display 112. Organizing a user's health records into subcategories of categories (and additional levels of subcategories), and presenting only health records belonging to a subcategory (or additional levels of subcategories) in a common user interface, allows the user to avoids the need to navigate through all health records in a category to find a specific health record, which reduces the time the user spends searching for health records. Reducing the time a user spends retrieving health records allows the user to use the device more quickly and efficiently, resulting in lower power usage and improving the device's battery life.

In some embodiments, the plurality of health records within the first category from the second health care provider include a fifth health record within the first category from the second health care provider (756). Figure 6H' depicts medication record 5018C (GHI Drug) obtained, for example, from Beta Healthcare. In some embodiments, the plurality of health records within the second category from the second health care provider include a sixth health record within the second category from the second health care provider (756). Figure 6H' shows an x-ray recording 5016C obtained, for example, from Beta Healthcare. In some embodiments, the fifth health record in the first category from the second health care provider and the sixth health record in the second category from the second health care provider are records of the third visit to the second health care provider. Take in (756). Figure 6H', for example, shows that both medication records 5018C and x-ray records 5016C were obtained during a visit to Beta Healthcare on September 15, 2017. In some embodiments, and in response to receiving the second request to display health records for the first user, device 100 displays, on display 112, a fifth health record in the third group and a fifth health record in the third group. Displays six health records simultaneously, wherein a third group is identified on display 112 by a third date of a third visit to a second health care provider, and the first group, second group, and third group are are displayed simultaneously on display 112 (756). Figure 6H' shows, for example, simultaneous display of drug record 5018C and x-ray record 5016C. Both health records were obtained during a visit to Beta Healthcare on September 15, 2017. Figure 6H' also shows the first and third groups of health records (health obtained during the October 1, 2017 visit to Alpha Healthcare and during the September 15, 2017 visit to Beta Healthcare, respectively). records) are displayed simultaneously. In some embodiments, if the dimensions of display 112 are larger, device 100 will display the first, second, and third groups of health records simultaneously. The method provides awareness to the user when the user is viewing health records from multiple health providers by grouping the health records based on the date of the appointment with the health care provider and arranging the different groups based on the date of the appointment. Reduces enemy burden. The method also increases user efficiency by allowing the user to identify health records based on the date of an appointment with a health care provider. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, and in response to receiving the first request to display health records for the first user, device 100 displays, on display 112, the identity and location of the first health care provider. The identifying first content is displayed (758). FIG. 6B displays drug records 5018A, 5018B (ABC Drug and DEF Drug), for example. Each medication record 5018A, 5018B identifies Alpha Healthcare as the health care provider that prescribed the corresponding medication. In some embodiments, each medication record may include the dosage, instructions to take the medication, the name of the doctor who prescribed the medication, the location of Alpha Healthcare, the location of the nearest pharmacies to pick up or refill the medication, and the medication. Include additional information about the corresponding drug, such as the fact sheet, the date the drug is scheduled to run out, as well as other appropriate content that provides information about the drug. In some embodiments, and in response to receiving the second request to display health records for the first user, device 100 displays, on display 112, the identity and location of the second health care provider. The identifying second content is displayed (758). 6J displays, for example, health status records 5020A and 5020B (cholesterol level and chronic migraine). Each health condition record 5020A, 5020B identifies Alpha Healthcare as the health care provider that prescribed the medication for the corresponding health condition. In some embodiments, each health condition record includes additional information about the corresponding health condition, such as the location of Alpha Healthcare. The method increases efficiency for the user by allowing the user to obtain information about a health care provider without having to contact the health care provider. The method also improves the operability of the device and makes the user-device interface more efficient by helping the user determine location as well as other information about the provider, without having to perform additional inputs. The method also reduces strain on existing networks and reduces the amount of telecommunication between users and health care providers. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, selection of a first representation of a first category while device 100 is associated with a first health care provider and not a second health care provider causes device 100 to display At 112, display historical health records associated with a first category from a first health care provider, wherein the historical health records associated with the first category are plurality of historical health records within the first category from the first health care provider. Includes health records (760). Figure 6K shows, for example, in response to detecting the gesture illustrated in Figure 6J, historical health records of the user's cholesterol level obtained from Alpha Healthcare (e.g., September 1, 2016 and September 1, 2016). Cholesterol representations (5030B, 5030C) of the user's cholesterol level measured as of the 1st of the month are shown.

In some embodiments, selection of a second representation of the second category while device 100 is associated with a first health care provider and not a second health care provider causes device 100 to display At 112, display historical health records associated with a second category from a first health care provider, wherein the historical health records associated with the second category are plurality of historical health records within the second category from the first health care provider. Includes health records (760). FIG. 6J shows, for example, health status records 5020A-5020C (cholesterol level, chronic migraine, and anxiety disorder, respectively). In some embodiments, if the user selects health record 5020B, health records in the history of the user's migraine history will be displayed.

In some embodiments, selection of the first representation of the first category while device 100 is associated with the first health care provider and the second health care provider causes device 100 to display display historical health records associated with a first category from a first health care provider and a second health care provider, wherein historical health records associated with the first category are displayed in a first category from a first health care provider. and one or more health records within the first category from a second health care provider (760). 6K' shows, for example, in response to detecting the gesture illustrated in FIG. 6J, historical health records of the user's cholesterol level obtained from Alpha Healthcare (e.g., September 1, 2016 and 2016). Cholesterol representations (5030B, 5030C) of the user's cholesterol level measured as of January 1) and historical health records of the user's cholesterol level obtained from Beta Healthcare (e.g., measured as of September 15, 2015) A cholesterol representation (5030D) of the user's cholesterol level is shown.

In some embodiments, selection of a second representation of the second category while device 100 is associated with the first health care provider and the second health care provider causes device 100 to display , display historical health records associated with a second category from a first health care provider and from a second health care provider, wherein historical health records associated with the second category are associated with a second category from the first health care provider. one or more health records within and one or more health records within a second category from a second health care provider (760). In some embodiments, Figure 6J shows, for example, health condition records 5020A-5020C (cholesterol level, chronic migraine, and anxiety disorder, respectively). In some embodiments, if the user selects health record 5020B, health records in the history of the user's migraine history obtained from both Alpha Healthcare and Beta Healthcare will be displayed. The method includes obtaining historical health records by allowing a user to access historical health records by selecting a health record, thereby allowing the user to access historical health records of the user associated with the health record. Reduces the number of inputs required, thereby creating a more efficient human-machine interface. The method allows the user to easily access health records in the user's history for a particular record by selecting the health record, thereby increasing the user's efficiency. For battery-operated computing devices, allowing a user to view the user's historical health records faster and more efficiently saves power and increases time between battery charges.

The specific order in which the operations in FIGS. 7A-7F are described is illustrative only and is not intended to indicate that the described order is the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7F) are also applicable in a similar manner to the methods described below. For example, methods 900 and 1100 optionally include one or more of the features of the various methods described above with respect to method 700. For example, the methods for displaying aggregated health records described above with reference to 700 are optionally used by method 900 to display current and historical health records in a dashboard user interface. Similarly, methods for displaying aggregated health records described above with reference to 700 may optionally include methods for displaying health records of certain health states that the user may designate as active or inactive in the health record manager ( 1100). For brevity, these details are not repeated below.

8A-8N illustrate example dashboard user interfaces with aggregated health records, according to some embodiments. 8A-8N allow the display of a single dashboard view of a comprehensive summary of the user's current healthcare data using health records obtained from the user's respective healthcare providers. For convenience, the health records will be described herein as the health records of the user of device 100. However, the health records may be health records of family members or other individuals associated with the user of the example user interfaces. For the purposes of Figures 8A-8N, the user has completed the onboarding process by Alpha Healthcare and Beta Healthcare, or is otherwise managed using the dashboard user interfaces of Figures 8A-8N, or is otherwise connected to the device. Has health records from Alpha Healthcare and Beta Healthcare stored on or accessible by 100. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 9A-9D.

Although some of the examples that follow will be given with reference to inputs on a touch screen display (a combination of a touch-sensitive surface and display), in some embodiments the device may be configured to display a display 450 separate from the display 450, as shown in FIG. 4B. Inputs on the touch-sensitive surface 451 are detected. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. For ease of explanation, the embodiments described below will be discussed with reference to operations performed on a device with touch-sensitive display system 112. In such embodiments, the focus selector may optionally be: an individual finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the center of the individual contact, or a point associated with the individual contact), or a touch. It is the center of two or more contacts detected on the responsive display system 112. However, similar operations may be performed on the display 450 and a separate touch-sensitive surface 451 in response to detecting contacts on the touch-sensitive surface 451 while displaying the user interfaces discussed below, optionally with a focus selector. It is performed on a device with surface 451.

8A-8N illustrate a health record summary displayed in a dashboard containing information derived from the user's current health records, hereinafter such information is referred to as health record summary information. As used herein, a current health record is one that is managed using the dashboard user interfaces of FIGS. 8A-8N or is more recent than other health records stored on or accessible by device 100. Refers to a health record of arbitrary health information. The dashboard user interfaces of FIGS. 8A-8N also allow a user to display information regarding the user's health records at different levels of detail. More specifically, the dashboard initially displays a health record summary containing health record summary information, and then allows the user to drill down and access additional information not included in the health record summary. Allows you to interact with the dashboard. Similarly, the user may also interact with the dashboard to review the user's historical health records. As device 100 receives updates to existing health records or new health records, the health record summary displayed on the dashboard presents health record summary information to the user based on the most recent health records. and is updated periodically to avoid presenting old or other historical health records that may no longer be relevant.

8A illustrates category representations 5006A-5006E (categories of allergies, clinical documentation, lab results, medications, and health conditions, respectively) and health history summary representation 7005. Health record summary representation 7005 is an affordance that includes text indicating that such affordance is associated with a health record summary. Health record summary representation 7005 is selectable by the user to view a health record summary. 8A and 8B illustrate detecting a tap gesture at contact 7502 on health history summary representation 7005 in FIG. 8A and, in response to the tap gesture, on display 112 in the dashboard of FIG. 8B. Illustrative of displaying a health record summary.

FIG. 8B illustrates displaying a dashboard of a health record summary containing health record summary information including multiple types of health records on display 112 . The health records of the illustrated embodiment are current health records obtained from both Alpha Healthcare and Beta Healthcare. In the illustrated embodiment, all current health records are displayed for each category of health records, regardless of which health care provider the current health record is provided by. In that way, the most recent health information about the user is displayed on the dashboard. In the illustrated embodiment, the health metric summary includes health metric records 7012A-7012C, medication records 7014A-7014C, and health status records 7016A-7016D. FIG. 8B also illustrates displaying the affordance of health metrics 7011A, the affordance of medications 7011B, and the affordance of health states 7011C. In the illustrated embodiment, affordance of health metrics 7011A, affordance of medications 7011B, and affordance of health states 7011C each view health metric records, medication records, and health state records in the user's history. can be selected by the user.

In the embodiment illustrated by FIG. 8B , health metric records 7012A - 7012C are displayed in a group with affordance 7011A of health metrics in alphabetical order based on the type of health metric record. Health metrics record 7012A includes current measurements of the user's blood pressure as measured by Beta Healthcare as of November 1, 2017. In the illustrated embodiment, the November 1, 2017 measurement is the user's most recent blood pressure measurement from both Alpha Healthcare and Beta Healthcare. In some embodiments, if historical health records of the user's blood pressure level measured before November 1, 2017 are available, the user accesses those historical health records by selecting affordance 7011A of health metrics. can do. Health metrics record 7012B includes a current measurement of the user's cholesterol level as measured by Alpha Healthcare as of October 1, 2017. Health metrics record 7012C contains current measurements of the user's serum iron levels as measured by Alpha Healthcare as of October 1, 2017.

In the embodiment illustrated in FIG. 8B , drug records 7014A - 7014C are displayed in groups with affordances 7011B of drugs in alphabetical order based on the type of drug. Drug health records 7014A through 7014C are the user's current drug prescriptions for ABC drugs, DEF drugs, and GHI drugs, respectively. Each of medication health records 7014A through 7014C also identifies the health care provider that prescribed the medication and the date of prescription for the corresponding medication.

In the embodiment illustrated by FIG. 8B , health condition records 7016A - 7016D are displayed in groups with affordances 7011C of health conditions in alphabetical order based on the type of health condition. Health status records 7016A through 7016D are health records of the user's current health conditions of anxiety disorder, asthma, high cholesterol, and migraine, respectively. In some embodiments, health condition records 7016A, 7016B, 7016D also identify the most recently prescribed medications for the corresponding health conditions (anxiety disorder, asthma, and migraine) individually in the drug group. Even so, it includes information about those drugs.

Although the embodiment illustrated in FIG. 8B shows 10 health records in the health record within the health record summary, in other embodiments, the health record summary may include a different number of the user's current health records. Additionally, in some embodiments, not all of the current health records included in the health record summary are displayed simultaneously on display 112. In one or more of such embodiments, the user performs a gesture to scroll through current health records displayed in the health record summary. Although in the illustrated embodiments the displayed health records are grouped by category and arranged alphabetically, in other embodiments, the health records may be grouped by date, provider, similarity, criticality, relevant biological function or system (e.g., any endocrine Measurements may be grouped or organized by (following all cardiology measurements), or any other suitable criteria, or based on any suitable factor. In one embodiment, the order in which health records are displayed is configurable by the user or provider (eg, by the primary care physician). FIG. 8B also illustrates detecting a tap gesture at contact 7503 on affordance 5304 of health records to return to the user interface illustrated in FIG. 8A.

FIG. 8B' is an alternative embodiment of a dashboard of health care summaries displayed in response to detecting a tap gesture at contact 7502 on health record summary representation 7005 in FIG. 8A. 8B' includes health care summary information shown as graphical representations of health records. More specifically, FIG. 8B' illustrates health metric record 7012A (blood pressure level) and health metric record 7012B (cholesterol level). In the illustrated embodiment, health metric record 7012A includes chart 7712 illustrating the user's blood pressure level (140/90 mmHg) within a range of blood pressure levels. In the illustrated embodiment, the numerical value of the user's blood pressure level is placed at a location on the chart 7712 proximate to where the measured blood pressure would be within that range. In that way, chart 7712 may illustrate where the user's blood pressure level is relative to the range of blood pressure levels that indicate normal or severe blood pressure levels. In some embodiments, health metrics record 7012A may also include information regarding the importance of the user's blood pressure level or a legend or other information about how to analyze the chart 7712 to help the user evaluate the user's blood pressure level. Include an explanation.

Health metric record 7012B includes a bar graph 7714 illustrating the user's cholesterol level (269 md/dL) within a range of cholesterol levels. In the illustrated embodiment, the numerical value of the user's cholesterol level is placed at a location on the chart 7714 proximate to where the measured cholesterol would be within that range. In the illustrated embodiment, a bar containing a numeric value of the user's cholesterol level is displayed with a color indicating the normal or severe nature of the user's cholesterol level. For example, the bar 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 greater than 300 mg/dL, respectively.

8B', health metrics record 7012A includes blood pressure levels displayed in text in a larger font than other text displayed in health metrics record 7012A. In that way, important information, such as testing measurements or laboratory results, can be highlighted to highlight such information to the user. Similarly, in health metrics record 7012B, measurements of the user's cholesterol level are also displayed in a larger font to assist the user in identifying the most recent measurement of the user's cholesterol level. In other embodiments, text containing measurements of the user's health metrics is highlighted, displayed in a different color, bolded, italicized, or other text that allows the user to quickly identify the user's health metrics. Formatted in other suitable ways. FIG. 8B' also illustrates detecting a tap gesture at contact 7504 on affordance 5304 of health records to return to the user interface illustrated in FIG. 8A.

Device 100 periodically receives updates to the user's health records. FIG. 8C illustrates displaying a dashboard of a health record summary including updates to health metric record 7012A of FIG. 8B including the user's blood pressure measurements. As illustrated in Figure 8C, health metric record 7052A (blood pressure level measured as of December 1, 2017) is similar to health metric record 7012A in Figure 8B (blood pressure level measured as of December 1, 2017), which includes the user's previous blood pressure measurements. Blood pressure levels measured as of the 1st of the month) are displayed in the health record summary instead. Additionally, 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. FIG. 8C also illustrates detecting a tap gesture at contact 7505 on affordance 5304 of health records to return to the user interface illustrated in FIG. 8A.

Figure 8C' illustrates an alternative embodiment of the dashboard of Figure 8C. In the illustrated alternative embodiment, health metric record 7052A with new blood pressure measurements illustrated in Figure 8C was not received by device 100. However, health metric record 7052B was received by device 100 with more recent cholesterol measurements than health metric record 7012B illustrated in FIG. 8B. Accordingly, Figure 8C' illustrates that health metric record 7052B is displayed in the health record summary instead of health metric record 7012B illustrated 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 record 7016C (high cholesterol) in FIG. 8B is also updated with health record 7056C to reflect the user's current measurement of cholesterol. Additionally, update badges 7141B, 7141C are displayed along with health metric record 7052B and health status record 7056C to indicate updates and draw the user's attention to the corresponding health records. 8C' further illustrates detecting a tap gesture at contact 7506 on health metrics record 7052B, and in response to the tap gesture, displaying the archive of health records 7058 in FIG. 8D. do.

FIG. 8D illustrates one embodiment of an archive of health records 7058 that includes historical health records of a user's cholesterol level. The Archive of Health Records is a user interface for the display of historical health records. In the illustrated embodiment, the archive of health records 7058 includes a health metric record 7052B containing a current measurement of the user's cholesterol level, illustrated in FIG. 8B before device 100 receives health metric record 7052B. health metric record 7012B displayed in the health record summary, and additional health metric records 7056A through 7056C. Health metrics records 7056A through 7056C contain measurements of the user's cholesterol levels as measured by Alpha Healthcare or Beta Healthcare as of September 15, 2017, September 1, 2016, and January 1, 2016. Includes. A graph 7021 of the user's cholesterol levels over time is also displayed in the archive 7058 of health records. Graph 7021 includes several bars, each representing a different measure of the user's cholesterol level associated with health metric records 7052B, 7012B, 7056A through 7056C. The bar may be displayed in colors that indicate the normal level of the user's cholesterol level. For example, a bar representing measurements of cholesterol levels below 200 mg/dL may be displayed in a first color, and a bar representing measurements of cholesterol levels between 200 mg/dL and 300 mg/dL may be displayed in a second color. and the bar representing measurements of cholesterol levels greater than 300 mg/dL may be displayed in a third color. Health metric records 7052B, 7012B, 7056A through 7056C and graph 7021 provide the user with information regarding the user's cholesterol level over time. FIG. 8D also illustrates detecting a tap gesture at contact 7507 on affordance 5308 of the health record summary to display a dashboard of the user's health record summary of FIG. 8E.

FIG. 8E illustrates one embodiment of a dashboard of health record summaries shown in FIG. 8C' after a user has viewed an update of new health record 7052B (cholesterol level) in FIG. 8C'. Update badges 7141B, 7141C (shown in FIG. 8C') are no longer displayed in FIG. 8E because the user has already reviewed the update of new health record 7052B. Figure 8E further illustrates detecting a tap gesture at contact 7508 on affordance 7011B of drugs, and in response to the tap gesture, displaying the archive of health records 7057 in Figure 8F.

8F illustrates one embodiment of an archive of health records 7057 that includes health records from the user's medication history. In the illustrated embodiment, archive of health records 7057 includes current medication records 7014A through 7014C (ABC medications, DEF medications, and GHI medications, respectively) and historical medication records 7015A through 7015D. do. Historical drug record (7015A) is an expired prescription for a currently prescribed GHI medication. Historical medication record 7015A also provides the name of the health care provider who prescribed the medication and the prescription period for the expired prescription. Historical drug records 7015B to 7015D are health records of drugs the user is no longer taking (LMN, RST, and XYZ drugs, respectively). In the illustrated embodiment, historical medication records 7015A - 7015D are either grayed out or grayed out to allow the user to easily distinguish between current medications the user is taking and expired medications. are displayed in a smaller or brighter font than the drug records 7014A to 7014C, or are displayed in a different color than them. In some embodiments, historical medication record 7015A and current medication record 7014C, both of which contain information regarding GHI medications, are not displayed simultaneously in the archive of health records. In some embodiments, the user selects a current medication record for a drug (e.g., an ABC drug) to access historical drug records for the same drug that the user may have been taking for an earlier period or at different doses. . Figure 8F further illustrates detecting a tap gesture at contact 7509 on medication record 7014A, and in response to the tap gesture, displaying additional information regarding the ABC drug in Figure 8G.

FIG. 8G illustrates displaying a fact sheet corresponding to medication record 7014A containing directions, warnings, and active ingredients for an ABC drug. In other embodiments, a pharmacy dispensing the medication, alternative sources for dispensing the medication (e.g., pharmacy benefit manager (PBM)), co-payment information, coverage information, available generics, refills of the medication, or Additional information about the ABC drug may also be displayed, such as information about the expiration date, instructions or information to refill the drug, dosages, drug side effects, or images of the drug. Historical medication records 7015E, 7015F containing expired prescriptions for ABC medications are displayed in a different color to indicate that the prescriptions are not active. FIG. 8G further illustrates detecting a tap gesture at contact 7510 on the affordance of an archive of drugs 5310 to view an archive of health records 7057 illustrated in FIG. 8F.

Similar to Figure 8C', Figure 8H also displays an embodiment of a dashboard of health record summaries after receiving updates to the user's health records. Sometimes, health records provided by health care providers are incomplete. An incomplete health record is one that is missing information such as the date of a hospital visit, doctor's name, prescription date, or other information that would allow the user to properly understand the health record. Health records may be stored by a health care provider, directly by a user, or automatically by device 100 in response to determining that a field in a received health record expected for the type of health record received is missing. It may be flagged as incomplete. Such determination by device 100 may include parsing the health record, automatically searching for specific text strings, obtaining information from the header file of the specific health record, determining whether required fields are missing, or for that health record. This may be determined by determining that fewer than the expected number of fields were received, or by any other suitable method.

In the embodiment illustrated in FIG. 8H , the update of the new medication record 7014D for JKL medication and the update of the new health condition record 7016E for arthritis are combined with update badges 7141D and 7141E in the health record summary. are displayed respectively. Although both the Medication Record (7014D) and Health Condition Record (7016E) identify the name of the drug (JKL Drug) and the name of the health care provider prescribing the drug, the date of prescription is ) is missing from both. In the illustrated embodiment, affordances of incompleteness 7020A, 7020B are configured to notify the user about updates to the user's health records and to notify the user that the health records that are the subject of the updates are missing information. It is displayed simultaneously with the update badges 7141D and 7141E. Incomplete affordances 7020A and 7020B are affordances that a user selects to obtain more information about an incomplete health record.

FIG. 8H illustrates detecting a tap gesture at contact 7511 on an incomplete affordance 7020A on drug record 7014D (JKL Drug), and in response to the tap gesture, from drug record 7014D in FIG. Further illustrates displaying notification 7250 of FIG. 8I regarding missing information. In the illustrated embodiment, notification 7250 is overlaid on the dashboard of the health record summary shown in Figure 8H. Notification 7250 includes text indicating that the prescription date for the JKL medication is missing from medication record 7014D in Figure 8H. Notification 7250 also includes an affordance of edit 7152 and an affordance of ignore 7153. In some embodiments, the user is aware of the missing information (e.g., missing prescription date from medication record 7014D, and health condition record 7016E for arthritis in FIG. 8H) and can fill in the missing information. The user interacts with the edit affordance 7152 to edit or add information about the JKL medication, such as prescription date. In that regard, Figure 8I also illustrates detecting a tap gesture at contact 7512 on affordance 7152 of editing. Once the user has added information about the JKL drug that was incomplete, the user selects the affordance 7153 to ignore.

In response to the user's selection of affordance 7153 to ignore, and device 100 determining that missing information has been provided by the user, device 100 receives notification from medication record 7014D (JKL Drug) in FIG. 8H. Remove the display of (7020A). Since notification 7020B was an indication that health status record 7016E (arthritis) was incomplete for the same reason (missing prescription date for JKL medication), device 100 also updated the health status record in FIG. 8H Removes display of notification 7020B from 7016E. In other embodiments, if device 100 determines that the user did not enter correct information that is missing, or if the user selected affordance 7153 of ignore without entering any information, the incompleteness of FIG. 8H may occur. Affordances 7020A and 7020B remain displayed along with medication record 7014D and health status record 7016E, respectively.

Similar to Figure 8H, Figure 8J also displays a health record summary after receiving updates to the user's health records. Device 100 sometimes determines that the health record is not missing any information, but that the authenticity or accuracy of the health record should be verified by the user. Device 100 may determine whether information in the health record is unexpected or does not fall within an established range of values, contains data that changes dramatically from data included in a previous health record, or the user has not received a health record for an extended period of time. Such determination may be made in response to a determination that it is from a health care provider, or for any other suitable reason. In still other embodiments, device 100 determines that a health record should be verified if the health record appears to conflict or contradict other health records.

In the embodiment illustrated by FIG. 8J , updates to new medication record 7054B (DEF medication) and new health condition record 7056A (anxiety disorder) are each received with the date of the most recent prescription for the DEF medication; Displayed with update badges (7141F, 7141G). Although neither medication record 7054B nor health status record 7056A was missing any information, device 100, affordances of verification 7022A and 7022B, respectively, allowed the user to access health status records 7054B and 7056A, respectively. are displayed simultaneously with the update badges 7141F and 7141G to notify the user that they must be verified. Verification affordances 7022A, 7022B are affordances that the user selects to obtain more information about the health records that the user is asked to verify.

8J illustrates detecting a tap gesture at contact 7514 on affordance of verification 7022B, and in response to the tap gesture, information in health condition record 7056A (anxiety disorder) that the user is asked to verify. Regarding, further illustrating displaying notification 7252 in Figure 8K. In one embodiment, notification 7252 is overlaid on the dashboard of the health record summary of Figure 8J, as illustrated in Figure 8K. Notice 7252 includes text requesting the user to confirm that DEF medication has been prescribed for an anxiety disorder. Notification 7252 also includes an affordance of confirmation 7155 and an affordance of incorrect mark 7154. The user interacts with the confirmation affordance 7155 to confirm the accuracy of the corresponding health record. Alternatively, the user interacts with the affordance 7154 of the inaccuracy mark to indicate that the information is inaccurate. Figure 8K further illustrates detecting a tap gesture at contact 7516 on affordance 7155 of confirmation. In some embodiments, in response to detecting a tap gesture at contact 7516 on affordance 7155 of confirmation, device 100 displays medication record 7054B (DEF medication) and health status illustrated in FIG. 8J. Designates information in both records 7056A as incorrect and removes verification affordances 7022A and 7022B from the dashboard of the summary of health records illustrated in FIG. 8J.

Similar to Figure 8J, Figure 8L also displays a health record summary after receiving updates to the user's health records. In the embodiment illustrated in Figure 8L, an update of the new medication record 7014E of drug XYZ prescribed by Omega Healthcare is received and displayed with update badge 7161F. Although health record 7014E is not missing any information, device 100 requires the user to verify the accuracy of health record 7014E upon determining that the user was never prescribed medication by Omega Healthcare. Display verification badge 7122C to notify the user.

FIG. 8L illustrates detecting a tap gesture at contact 7518 on verification affordance 7122C, and in response to the tap gesture, health status record 7014E of FIG. 8L (XYZ Drugs) that the user is asked to verify. ) further illustrates displaying notification 7253 in FIG. 8M regarding information in ). In the illustrated embodiment, notification 7253 is overlaid on the dashboard of the health record summary of Figure 8L, as illustrated in Figure 8M. Notice 7253 includes text requesting the user to confirm that drug XYZ was prescribed by Omega Healthcare as of January 15, 2018. Notification 7253 also includes an affordance of confirmation 7155 and an affordance of incorrect mark 7154. 8M further illustrates detecting a tap gesture from the user at contact 7520 on the affordance 7154 of an incorrect mark. In some embodiments, in response to detecting a tap gesture at contact 7520 on affordance 7154 of the incorrect mark, device 100 designates medication record 7014E as incorrect and the health in FIG. 8N. Remove medication record (7014E) from the dashboard of record summary. As illustrated in Figure 8N, medication record 7014E in Figure 8L is no longer displayed in the health record summary. In some embodiments, health records that have been marked as inaccurate by the user remain included in the archive of health records. In that regard, the user may interact with the drugs affordance 7011B of FIG. 8N to review the drug record 7014E.

9A-9D are flow diagrams illustrating a method for displaying dashboard user interfaces with aggregated health records using an electronic device, according to some embodiments. More specifically, Figures 9A-9D are flow charts illustrating a method for displaying a user's current and historical health records, for example, using the user interfaces of Figures 8A-8N. As described with reference to FIGS. 8A-8N, method 900 may be utilized to display dashboard user interfaces for displaying the user's current as well as historical health records. Method 900 is performed at a device (e.g., devices 100, 300, and 500 illustrated in FIGS. 1, 3, and 5A, respectively). In one such embodiment, display 112 is a touch screen display, and a touch-sensitive surface is on or integrated with display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. Some operations within method 900 are optionally combined. Additionally, the order of some operations is optionally changed.

As described below, method 900 provides an intuitive way to display dashboard user interfaces with a user's aggregated health records. Method 900 also provides an intuitive way to display a user's current as well as historical health records. The method reduces cognitive burden on the user when the user is browsing current and historical health records, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to browse the user's current and historical health records faster and more efficiently saves power and increases time between battery charges.

Method 900 also provides an intuitive way to display representations of a user's certain health conditions to indicate the severity of such conditions. The method reduces cognitive burden on the user by allowing the user to determine the severity of certain health conditions from displayed representations of the health conditions, thereby creating a more efficient human-machine interface. The method increases user efficiency by reducing the time required for the user to understand the severity of the user's health conditions. For battery-operated computing devices, allowing a user to understand the severity of the user's health conditions faster and more efficiently saves power and increases time between battery charges.

Device 100, while associated with health data for a first user, 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. A request is received, via input devices, to display health record summary information for the user (902). 8A illustrates, for example, detecting a tap gesture at contact 7502 on health record summary representation 7005.

Device 100, in response to receiving the request, displays 904 health record summary information for the first user, including simultaneously displaying a plurality of health record items on the display. FIG. 8B shows, for example, in response to detecting a tap gesture at contact 7502 on health record summary representation 7505 as illustrated in FIG. 8A , health metric records 7012A - 7012C (blood pressure level , cholesterol level, and serum iron level), medication records (7014A to 7014C) (ABC medication, DEF medication, and GHI medication, respectively), and health status records (7016A to 7016D) (anxiety disorder, asthma, and is shown displaying a health history summary including high cholesterol, and migraines).

The plurality of health record items include a first health record item of a first type having a first date, wherein the health record summary information excludes the plurality of health record items of the first type having dates earlier than the first date. (906). FIG. 8B illustrates displaying health metric record 7012A (blood pressure level) in a health record summary, for example. Health metric record 7012A includes measurements of the user's blood pressure as of November 1, 2017. Previous measurements of the user's blood pressure are not included in the health record summary.

In some embodiments, the first health record item includes an expression of the severity of the first user's condition (908). 8B' also illustrates displaying health metric record 7012A (blood pressure level) in a health record summary. In the illustrated embodiment, health metric record 7012A includes chart 7712 illustrating the user's blood pressure level within a range of blood pressure levels. The method reduces the cognitive burden on the user by providing the user with a representation (e.g., within an image, graph, or chart) that allows the user to determine the severity of a health condition based on the representation, thereby making it more efficient. Create a human-machine interface. The method also increases the user's efficiency by allowing the user to quickly identify the severity of the condition from the representation. For battery-operated computing devices, allowing users to identify the severity of a condition faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the first health record item includes a representation of the first user's condition over a period of time (910). FIG. 8D illustrates displaying graph 7021, which is, for example, a graph of a user's cholesterol levels over two years. In some embodiments, health metric record 7012A (blood pressure level) of FIG. 8B also includes graph 7021. Providing a graph of a user's state over time allows the user to see how the user's state changes over time, without having to navigate multiple user interfaces to access data representing the user's state from different time periods. This reduces the cognitive burden on the user and creates a more efficient human-machine interface. For battery-operated computing devices, allowing a user to identify the user's status over time faster and more efficiently saves power and increases time between battery charges.

The plurality of health record items also include a second health record item of a second type having a second date that is different from the first date, wherein the health record summary information is of a second type having a date that is earlier than the second date. Exclude multiple health record items (912). Figure 8B shows, for example, displaying medication record 7014A. The drug record (7014A) is a health record of the user's prescription for the ABC drug that was prescribed to the user as of October 1, 2017. Previous prescriptions for ABC medications predating October 1, 2017 are not included in the health record summary.

In some embodiments, the health data for the first user includes a plurality of health record items of a third type that is different from the first type and the second type (914). FIG. 8B shows, for example, displaying health status record 7016D. The health status record 7016D is a health record of the user's migraine condition. In some embodiments, device 100 simultaneously displays a first health record item, a second health record item, and a third type of third health record item with a third date in the health record summary information (914). . FIG. 8B illustrates simultaneous display of health metric record 7012A (blood pressure level), medication record 7014A (ABC Medication), and health condition record 7016D (migraine) within a health record summary, for example. . Additionally, in some embodiments, the health record summary information excludes 914 a plurality of health record items of a third type that have dates earlier than the third date. Health status record 7016D contains information regarding ABC medications that have been prescribed to the user as of October 1, 2017. Previous health status records regarding the user's migraine condition are not included in the health history summary. Similarly, medication record 7014C in FIG. 8B is a health record of the user's prescription for a GHI medication that was prescribed to the user as of September 15, 2017. Previous prescriptions for GHI medications prior to September 15, 2017 are also not included in the health record summary. Displaying multiple types of health records in a common interface allows users to browse multiple types of health records without having to navigate between multiple user interfaces, thereby creating a more efficient human-machine experience. Create an interface. For battery-operated computing devices, allowing a user to browse through the user's history faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the health data includes health data associated with a plurality of health care providers of the first user, wherein the first health record item is associated with a first health care provider of the plurality of health care providers; The second health record item is associated with a second health care provider among the plurality of providers (916). FIG. 8B shows, for example, that health metric record 7012A (blood pressure level) was obtained from Beta Healthcare and medication record 7014A (ABC medications) was obtained from Alpha Healthcare. Displaying multiple health records from multiple health care providers in a common interface allows a user to browse records from different health care providers without having to navigate between multiple user interfaces, This creates a more efficient human-machine interface. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the plurality of health record items include a fourth type of fourth health record item having a fourth date, wherein the first health record item and the fourth health record item are associated with the first health care provider. and the first and fourth dates are the dates of the first and second visits to the first health care provider (918). 8B illustrates, for example, health metric record 7012A (blood pressure level) and health status record 7016B (asthma). Both health records were obtained from Beta Healthcare. Additionally, health metric record 7012A was obtained during a visit to Beta Healthcare on November 1, 2017, and health status record 7016B was obtained during a visit to Beta Healthcare on September 15, 2017. Displaying multiple health records acquired on different dates in a common interface allows the user to browse health records acquired on different dates without having to navigate between multiple user interfaces, thereby , creating more efficient human-machine interfaces. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

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

Additionally, in some embodiments, device 100, in response to receiving the second request, displays the second health record item and the third health record item on display 112 without displaying the first health record item. Display 920 an updated health record summary for the first user, including simultaneously displaying record items. FIG. 8C shows an updated health record summary including, for example, health metric record 7052A (blood pressure level). Health metric record 7052A includes measurements of the user's blood pressure as of December 1, 2017. Health metrics record 7012A also includes measurements of the user's blood pressure measured at an earlier date. Device 100, after receiving a more recent measurement of the user's blood pressure, displays health metric record 7052A instead of health metric record 7012A in the updated health record summary. Displaying a health record summary updated over time to include updates to the user's existing health records allows the user to navigate through multiple user interfaces to obtain the user's most recent health records. Provides access to the user's updates from the interface. The method also reduces cognitive burden on the user by allowing the user to access current health records through a health record summary, thereby creating a more efficient human-machine interface. The method increases user efficiency by allowing the user to access the user's current health records through a health record summary. For battery-operated computing devices, allowing a user to view the user's current health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives a new health record item of health data for the first user after displaying the health record including the first health record item and the second health record item, where The new health record item has a date that is more recent than the first and second dates (922). In some embodiments, device 100 receives medication record 7014D (JKL Medication) illustrated in FIG. 8H prior to displaying medication record 7014D in the health record summary illustrated in FIG. 8H. In some embodiments, device 100, after receiving a new health record item, receives (922) a third request, via one or more input devices, to display health record summary information for the first user. In some embodiments, the user interface illustrated in FIG. 8A is displayed on display 112 when device 100 receives medication record 7014D. In such embodiments, the user performs a gesture similar to the tap gesture shown in FIG. 8A to view the health record summary illustrated in FIG. 8H.

In some embodiments, device 100, in response to receiving the third request, includes simultaneously displaying the first health record item, the second health record item, and the new health record item on the display. , display 922 an updated health record summary for the first user. 8H displays an updated health record summary, including, for example, health metric record 7012A (blood pressure level), medication record 7014A (ABC Medication), and medication record 7014D (JKL Medication). shows that Displaying a health record summary updated over time to include the user's new health records allows the user to view the user's updates in a common interface without having to navigate multiple user interfaces to obtain the user's most recent health records. provide access to the fields. The method also reduces cognitive burden on the user by allowing the user to access current health records through a health record summary, thereby creating a more efficient human-machine interface. The method increases user efficiency by allowing the user to access the user's current health records through a health record summary. For battery-operated computing devices, allowing a user to view the user's current health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives (924) a first request, via one or more input devices, to display a plurality of health record items of a first type that are not displayed in the summary. 8C' shows, for example, a tap gesture at contact 7506 on health metric record 7052B (cholesterol level). In some embodiments, device 100, in response to receiving a first request to display a plurality of health record items of a first type that are not displayed in the summary, displays on the display a date that is earlier than the first date. Display 924 a plurality of health record items of a first type having . FIG. 8D illustrates displaying health metric records 7056A-7056C (cholesterol levels) in response to detecting the tap gesture illustrated in FIG. 8C', for example. Health metrics records 7056A through 7056C are the user's health metrics as of September 15, 2017, September 1, 2016, and January 1, 2016, made by an employee of Alpha Healthcare or Beta Healthcare. Includes measurements of cholesterol levels. All of health metric records 7056A through 7056C precede health metric record 7052B. Additionally, none of health metric records 7056A-7056C are displayed in health metric record 7012B (cholesterol level) illustrated in FIG. 8H. The method reduces the number of inputs required to obtain historical health records by allowing the user to access the user's historical health records through a health record summary, thereby creating a more efficient human-machine interface. do. The method increases user efficiency by allowing the user to access the user's historical health records through a health record summary. For battery-operated computing devices, allowing a user to view the user's historical health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100, in response to receiving a first request to display a plurality of health record items of a first type that are not displayed in the summary, displays, on display 112, the most recent date. An archive of health records for a first user, comprising simultaneously displaying one or more of a health record item of a first type having a and a plurality of health record items of a first type having dates earlier than the first date. Display (926). 8D illustrates, for example, health metric record 7052B, which includes the user's most recent cholesterol measurement as of December 1, 2017, and health metric records that include earlier measurements of the user's cholesterol level. Simultaneous display of (7056A to 7056C) is exemplified. Simultaneously displaying the user's current and historical health records avoids the need to navigate multiple user interfaces to obtain both the user's current health records and the user's historical health records. The method reduces cognitive burden on the user by allowing the user to view the user's current and historical health records in one user interface, thereby creating a more efficient human-machine interface. The method increases user efficiency by allowing the user to view the user's current and historical health records without having to navigate different user interfaces to view the current and historical health records. For battery-operated computing devices, allowing a user to view the user's current and historical health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100, in response to receiving a first request to display a plurality of health record items of a first type that are not displayed in the summary, displays, on display 112, an archive of health records. Displays the fourth health record item of the first type in (928). FIG. 8D illustrates displaying a graph 7021 of a user's cholesterol level over time, for example, in response to detecting the tap gesture illustrated in FIG. 8C'. In some embodiments, the fourth health record item includes a representation of a health metric measured as a fourth date earlier than the first date (928). Graph 7021 includes current and previous measurements of the user's cholesterol level. In other embodiments, one or more of the health metric records 7056A-7056C (cholesterol levels) illustrated in FIG. 8D also includes a representation (e.g., a bar graph, or scale) of the user's previous cholesterol level. Displaying a representation of historical health metrics allows the user to determine the user's health metrics over time without the need to contact the user's health care provider, thereby making communication systems free to use. up), reducing bandwidth on networks and saving energy. For battery-operated computing devices, allowing a user to obtain historical information about the user's health metrics faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100, after displaying health record summary information having the first and second health records, displays a third health record having a third date that is more recent than the first and second dates. A third health record item of type is received (930). Health status record 7016E (JKL medication) in FIG. 8H is administered to device 100 after device 100 receives health metric record 7012A (blood pressure level) and medication record 7014A (ABC medication) in FIG. 8B. ) was received by. Health status record 7016E includes information about the user's arthritis condition, and information about JKL medications that were prescribed to the user as of November 15, 2017. The date of the health status record 7016E is more recent than the date of the health metrics record 7012A (November 1, 2017) and the date of the medication record 7014A (October 1, 2017). In some embodiments, device 100, in response to a request to view the health record summary information, updates the health record summary information to include a third health record item, wherein the first health record item, the second health record item, The record item, and the third health record item are displayed simultaneously in the health record summary information (930). As shown in FIG. 8N, health metric record 7012A (e.g., first health record item), medication record 7014A (e.g., second health record item), and health status record 7016E (e.g., first health record item). 3 health record items) are displayed simultaneously in the health record summary. Displaying a health record summary containing multiple types of health records allows a user to view multiple types of health records in a common interface without having to navigate multiple user interfaces, thereby providing the user with It reduces the cognitive burden on users and also creates a more efficient human-machine interface. The method also increases user efficiency by allowing the user to access multiple types of health records from a common interface. For battery-operated computing devices, allowing a user to view the user's current health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100, in response to a request to display health record summary information, determines that a health record item of health data for the first user is incomplete and, in response to a determination that a health record item of health data for the first user is incomplete, displays the incomplete record in the health record summary information. Display the affordance (932). FIG. 8H illustrates, for example, displaying an affordance of incompleteness 7020A with medication record 7014D (JKL Drug) after determining that medication record 7014D is missing information. The method reduces the number of mistakes caused by users relying on records that are missing information. The method reduces cognitive burden on the user by identifying health records that are missing information for the user. The method increases user efficiency while reviewing the user's health records by allowing the user to selectively ignore records that are missing information. For battery-operated computing devices, allowing users to review their health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives, via one or more input devices, user verification of the accuracy of certain health record items among a plurality of health record items displayed in health record summary information (934). Figure 8K shows, for example, detection of a tap gesture at contact 7516 on affordance 7155 of confirmation to confirm that DEF medication has been prescribed for an anxiety disorder. Device 100, in response to receiving the user verification of the accuracy of the health record item, provides the user verification to the health care provider associated with the health record item (934). In some embodiments, device 100 may, in response to detecting the user's input illustrated in Figure 8J, determine that DEF medication has been verified by the user as a medication the user is taking to treat the user's anxiety disorder. Alpha Healthcare is automatically notified. The method reduces cognitive burden on users by allowing them to verify the accuracy of their health records. The method increases user efficiency by allowing the user to verify the accuracy of certain health records without waiting for verification from a health care provider. The method also reduces the need to request a health care provider to verify a health record, which saves the bandwidth required to transmit that request to the health care provider's electronic system. The method also reduces the burden on the health provider's electronic system for processing requests, which in turn also reduces the power cost of the electronic system. Automatically notifying the health care provider's electronic system that a health record from the health care provider has been verified by the user means that the health care provider may (via the electronic system or by other means of telecommunication) verify the accuracy or completeness of the health record. (through) reduces the need for contact with the user or the user's device. The above frees up communication systems, reduces bandwidth on networks, and saves energy.

In some embodiments, device 100 receives, via one or more input devices, a first user indication that certain health record items among a plurality of health record items included in health record summary information are inaccurate (936) . FIG. 8M illustrates, for example, detection of a tap gesture at contact 7520 on affordance 7154 of an incorrect mark to mark drug record 7014E of FIG. 8L (XYZ drug) as incorrect. In some embodiments, device 100, in response to receiving the first user indication, excludes the health record item from health record summary information, wherein the health record item is subsequently excluded from health record summary information. No longer included in health record summary information (936). FIG. 8N shows an updated health record summary, for example, after the tap gesture illustrated in FIG. 8M has been performed. As shown in Figure 8N, medication record 7014E in Figure 8L is not displayed in the updated health record summary. The method reduces cognitive burden on the user by allowing the user to ignore inaccurate or incomplete health records. The method increases user efficiency by reducing the time the user spends reviewing inaccurate or incomplete records. For battery-operated computing devices, allowing users to review their health records faster and more efficiently saves power and increases time between battery charges. The method also reduces the number of user errors caused by the user relying on incomplete or inaccurate health records.

In some embodiments, device 100, in response to receiving the first user indication, automatically, without further user input, transmits a request for updated information for the health record item from the health care provider computer system. Do it (938). In some embodiments, device 100, upon detecting an interaction with the mark as affordance of inaccuracy 7154 in FIG. 8K to designate the health record as an inaccurate health record, directs the health record's health care provider to automatically sends the request. Automatically notifying a health care provider's electronic system of inaccuracies in a health record from a health care provider means that the user (using a device or other means of telecommunication) can request that the health care provider update the inaccurate health record. thus) reducing the need for manual contact with health care providers. The above frees up communication systems, reduces bandwidth on networks, and saves energy. Additionally, updated information may also be received from the health care provider before the user has the option to update missing information. For battery-operated computing devices, updating inaccurate health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 receives information to update the first health record item, via one or more input devices (940). Figure 8I, for example, shows a user making edits to health metric record 7014D (JKL Drugs). In some embodiments, device 100 may access health metric record 7014D after a user performs the tap gesture shown in FIG. 8I at contact 7512 over affordance of editing 7152 of FIG. 8I. Receive edits. In some embodiments, device 100, after receiving information updating the first health record item, receives a second request to display health record summary information for the first user (940). In some embodiments, after editing health metric record 7014D, the user selects health record summary representation 7005 to view a health record summary. In other embodiments, a tap gesture on the contact over affordance 7152 of edit or affordance 7153 of Figure 8I also becomes a request to display a health record summary. In some embodiments, device 100, in response to receiving a request to display health record summary information for the first user, updates the first health record item and the second health record item to reflect changes to the first health record item. Display 940 an updated health record summary for the first user, including simultaneously displaying the updated first health record item. FIG. 8J shows, for example, an updated health record summary that includes information regarding medication record 7014D that was previously missing from the health record summary illustrated in FIG. 8H. Displaying updates to health records with other current health records in a common interface allows the user to view the user's current health in a common interface without having to navigate through different user interfaces to obtain updates to different health records. Makes records visible, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to browse their health records faster and more efficiently saves power and increases time between battery charges.

The specific order in which the operations in FIGS. 9A-9D are described is illustrative only and is not intended to indicate that the described order is the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, details of the processes described above with respect to method 900 (e.g., FIGS. 9A-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 of the features of the various methods described above with respect to method 900. For example, methods for displaying a health record summary including current health records and for displaying historical records in other user interfaces described above with reference to 900 include: Optionally used by method 700 and optionally used by method 1100 to display health records in a health record manager. For brevity, these details are not repeated below.

10A-10Q illustrate an example health record manager according to some embodiments. More specifically, FIGS. 10A-10Q illustrate the display of a health record manager that allows a user to specify the status of certain health records and manage activities associated with them through the health record manager. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 11A-11E.

Although some of the examples that follow will be given with reference to inputs on a touch screen display (a combination of a touch-sensitive surface and display), in some embodiments the device may be configured to display a display 450 separate from the display 450, as shown in FIG. 4B. Inputs on the touch-sensitive surface 451 are detected. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. For ease of explanation, the embodiments described below will be discussed with reference to operations performed on a device having the touch-sensitive display system 112. In such embodiments, the focus selector may optionally be: an individual finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the center of the individual contact, or a point associated with the individual contact), or a touch. It is the center of two or more contacts detected on the responsive display system 112. However, similar operations may be performed on the display 450 and a separate touch-sensitive surface 451 in response to detecting contacts on the touch-sensitive surface 451 while displaying the user interfaces discussed below, optionally with a focus selector. It is performed on a device with surface 451.

As used herein, in one or more embodiments of FIGS. 10A-10Q, active health records are the user's active health records that have been designated as current by the user or the health care provider, or are being treated by the health care provider. These are health records that are associated with a medical condition, or a health condition that the user is currently monitoring. For example, in one embodiment, active health records include each type of most recent health record for the user, such as a blood test from the user's most recent annual physical or other recent visit to a health care provider. It may be the results of, or the user's current prescription records. In another embodiment, active health records may be the most recent record of specific health conditions that the user is monitoring, such as blood pressure and cholesterol levels. In another embodiment, active health records may simply be health records associated with an acute or chronic health condition for which the user is actually being treated by a health care provider. In another embodiment, active health records may be any health records that are no older than a period of time set by the user or automatically determined by device 100. In one embodiment, all health records are designated active when first received by device 100 from a health care provider. However, in the illustrated embodiments, a user can designate any health record as active.

As used herein, in one or more of the embodiments of FIGS. 10A-10Q, an inactive health record is any health record other than an active health record. Optionally, health records designated as inactive by the user are hidden in the health record manager's dashboard user interface but displayed in the health record manager's other user interfaces containing more detailed information about the user's health records. Active health records are displayed in the health record manager's dashboard user interface. The status of health records can be changed by the user from active to inactive, such as when the user's asthma symptoms are no longer present. Similarly, the status of health records can be changed by the user from inactive to active, such as when the user's asthma symptoms return. 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 health care provider. Similarly, in response to a change in the status of the health record from inactive to active, a notification is also automatically generated by the device and transmitted to the user's health care provider.

The health record manager also allows the user to set reminders to perform various tasks related to certain health records. Reminders may, for example, remind the user to take medications prescribed to the user at predetermined times, refill medications prescribed to the user, or track upcoming appointments with doctors or other health care professionals. can be used for Although the embodiments of FIGS. 10A-10Q are described in relation to the management of health records, and more specifically, health status records, in some embodiments, representations of health information other than health records represent a user's health information. It can be used for management. Similarly, other categories of health records may also be used to manage a user's health information, such as laboratory records, clinical records, or allergy records.

Similar to FIG. 8B , FIG. 10A illustrates displaying a dashboard of a health record summary containing health record summary information including multiple types of health records on display 112 . The health records of the illustrated embodiment are current health records obtained from both Alpha Healthcare and Beta Healthcare. In the illustrated embodiment, the health metric summary includes health metric records 9012A through 9012C (blood pressure, cholesterol level, and serum iron level, respectively), medication records 9014A through 9014D (ABC drug, DEF drug, respectively, GHI medications, and LMN medications), and health condition records (9016A through 9016D) (anxiety disorders, asthma, high cholesterol, and migraines, respectively). Figure 10A also illustrates displaying the affordance of health metrics 9011A, the affordance of drugs 9011B, and the affordance of health conditions 9011C. In the illustrated embodiment, affordance of health metrics 9011A, affordance of medications 9011B, and affordance of health states 9011C each enable a user to view the archive of health metrics, archive of medications, and archive of health states, respectively. It can be selected by . 10A-10Q, each of the archive of health metrics, archive of medications, and archive of health conditions is an archive of health records including current health records and historical health records belonging to the corresponding category. am.

In the embodiment illustrated by Figure 10A, health metric records 9012A - 9012C are displayed in alphabetical order based on the type of health metric record. Health metrics record 9012A includes current measurements of the user's blood pressure as measured by Beta Healthcare as of November 1, 2017. Health metrics record 9012B includes a current measurement of the user's cholesterol level as measured by Alpha Healthcare as of October 1, 2017. Health metrics record 9012C includes current measurements of the user's serum iron levels as measured by Alpha Healthcare as of October 15, 2017.

In the embodiment illustrated by Figure 10A, drug records 9014A-9014D are displayed in alphabetical order based on the type of drug. Drug health records 9014A through 9014D are the user's current drug prescriptions for ABC drugs, DEF drugs, GHI drugs, and LMN drugs, respectively. Each of medication health records 9014A through 9014D also identifies the health care provider that prescribed the medication and the date of prescription for the corresponding medication.

In the embodiment illustrated by FIG. 10A , health condition records 9016A - 9016D are displayed in alphabetical order based on the type of health condition. Health status records 9016A through 9016D include information regarding the user's current health conditions, including anxiety disorder, asthma, high cholesterol, and migraine, respectively. In some embodiments, health condition records 9016A-9016D also include corresponding health conditions (anxiety disorder, asthma, high cholesterol, and migraine), even if those drugs are individually identified in a group of drugs. Includes information on the most recently prescribed medications. FIG. 10A further illustrates detecting a tap gesture at contact 9502 over an affordance of health states 9011C, and in response to the tap gesture, displaying an archive of health states 9058 in FIG. 10B .

FIG. 10B illustrates one embodiment of an archive of health states 9058 that includes health records of a user's health states and status toggles to designate health records as active or inactive. In the illustrated embodiment, the archive of health conditions 9058 includes health condition records 9016A through 9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively). In the illustrated embodiment, health status record 9016A may include information regarding the user's anxiety disorder, medications prescribed to treat the user's anxiety disorder (DEF medications), date of initial diagnosis, and Alpha Health regarding the user's anxiety disorder. Includes the next scheduled visit to care. Health status record 9016B includes information about the user's asthma, medications prescribed to treat the user's asthma (GHI medications), date of initial diagnosis, and the user's next scheduled visit to Beta Healthcare regarding the user's asthma. do. The health status record (9016C) contains information about the user's high cholesterol, the level of cholesterol measured and the date the cholesterol test was given, the medication prescribed to treat the user's high cholesterol (LMN medication), the date of initial diagnosis, and the date of the user's high cholesterol. Includes next scheduled visit to Alpha Healthcare regarding high cholesterol. The health status record (9016D) includes information about the user's migraines, medications prescribed to treat the user's migraines (ABC drugs), date of initial diagnosis, and the user's next scheduled visit to Alpha Healthcare regarding the user's migraines. do. In other embodiments, each of health condition records 9016A - 9016D may include additional information about the corresponding health condition, such as the names of medications previously prescribed for the health condition, a physician with whom the user consults regarding the health condition, Include name(s) of the health condition(s) or other health care professionals, a list of symptoms of the health condition, as well as other useful information related to the health condition.

As illustrated in FIG. 10B, health status records 9016A through 9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively) also include status toggles 9022A through 9022D, respectively, which allow the user to select predetermined settings. These are affordances that interact to specify the status of health states. In the illustrated embodiment, status toggles 9022A - 9022D each allow a user to designate a corresponding health state as active or inactive. In other embodiments, each of the health status records 9016A - 9016D may also allow the user to specify other conditions, such as setting up a reminder to take medication for the corresponding health condition or providing information about the health condition. Includes different types of status toggles that allow you to set up a reminder to visit a doctor, or set up options to receive notifications or updates about your health status.

In some embodiments, status toggles 9022A - 9022D (for anxiety disorder, asthma, high cholesterol, and migraine, respectively) are not displayed in the archive of health conditions 9058. In one or more of such embodiments, the archive of health states 9058 includes a status-specific affordance (not shown), which is an affordance with which a user interacts to access status toggles 9022A-9022D. For example, device 100 may, in response to detecting a gesture for selecting an affordance of a status designation, display another user's gesture that includes status toggles 9022A through 9022D on the portion of the user interface displayed in FIG. 10B. Overlay the interface. In other embodiments, status toggles are displayed with corresponding health records within the health record summary to allow the user to specify the status of specific health conditions without having to drill down into the archive of health conditions 9058. . In another embodiment, a user may select health status records 9016A through 9016D (respectively anxiety disorder, asthma, high Select a record of your individual health conditions (such as cholesterol, migraines, etc.). In one or more of such embodiments, after a user interacts with a status toggle displayed in a health record summary, a notification similar to the notification requesting the user to confirm a change in the status of the corresponding health condition is displayed. In such embodiments, device 100 changes the status of the health state after detecting an input that confirms the change in the status of the health state to avoid accidental inputs.

In the illustrated embodiment, status toggles 9022A - 9022C (for anxiety disorder, asthma, and high cholesterol, respectively) indicate that the corresponding health conditions are active. 10B shows a swipe gesture at contact 9602 on status toggle 9022D (for migraine) and movement of the contact from location 9602A to location 9602B to designate migraine as an inactive health state. Detection is further illustrated. Figure 10C illustrates displaying a notification 9252 requesting the user to confirm the user's decision to designate migraine as inactive. Notification 9252 has an affordance of Confirm, which is an affordance with which the user interacts to confirm the designation of a migraine as inactive, and an affordance of Ignore, which is an affordance with which the user interacts to cancel the designation of a migraine as inactive. Includes affordance (9154). Figure 10C further illustrates detecting a tap gesture at contact 9506 on affordance 9153 of confirmation, and in response to the tap gesture, designating migraine as an inactive health state in Figure 10D.

FIG. 10D illustrates an embodiment of an archive of health conditions 9058 after a user designates migraine as an inactive health condition. In the illustrated embodiment, status toggle 9022D (for migraine) was switched from active to inactive in response to the user's gestures illustrated in FIGS. 10B and 10C. In some embodiments, affordance 9252 of the notification illustrated in Figure 10C is not displayed in response to the user's gestures illustrated in Figure 10B. In such embodiments, health condition record 9016D (Migraine) is designated as an inactive health condition in response to the swipe gesture performed in FIG. 10B. Health status record 9016D is grayed out (or displayed in a different color than the color of health conditions records 9016A-9016C) to indicate that migraine is no longer an active health condition. Figure 10D further illustrates detecting a tap gesture at contact 9510 on affordance 5308 of the health record summary, and in response to the tap gesture, displaying the updated health record summary in Figure 10E.

10E illustrates displaying an updated health record summary on display 112. As illustrated in FIG. 10E , the updated health record summary includes information about migraines, or medication record 9014A (ABC Medications) illustrated in FIG. 10A , which includes information about medications prescribed to treat migraines. does not include health condition record 9016D (migraine) illustrated in FIG. 10A. In the illustrated embodiment, health records that have been designated as inactive are not shown in the health record summary. In such embodiments, a user may access an archive of health records of a category of health records (e.g., archive of health conditions 9058 illustrated in FIG. 10B) to view inactive records belonging to the corresponding category. In other embodiments, such as the embodiment illustrated in FIG. 10H, the health record summary includes both active health records and inactive health records. However, inactive health records are grayed out or displayed in a different color than active health records. In further embodiments, the updated health record summary can be configured to include an inactive health record view, an affordance for a user to interact with to view all inactive health records, or a similar affordance for a user to interact with to view inactive health records within a health record summary. Includes affordances (not shown). In one or more of such embodiments, device 100 displays inactive health records in a health record summary after detecting user interaction with the affordance of viewing inactive health records. FIG. 10E further illustrates detecting a tap gesture at contact 9512 over an affordance of health states 9011C, and in response to the tap gesture, displaying an archive of health states 9058 in FIG. 10F .

Similar to FIG. 10D , FIG. 10F also displays health status records 9016A through 9016D with status toggles 9022A through 9022D in the archive of health conditions 9058 (anxiety disorder, asthma, high cholesterol, respectively). and migraine). 10F further illustrates a swipe gesture at contact 9604 on status toggle 9022B and detecting movement of the contact from location 9604A to location 9604B to designate asthma as an inactive health state. do.

10G shows a swipe gesture at contact 9604 on status toggle 9022B (for Asthma) to designate asthma as an inactive health state, and after moving the contact from location 9604A to location 9604B. This is a continued view of Figure 10f. 10G , the order of health condition records 9016A-9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively) is that of the inactive health condition records (health condition records 9016B, 9016D). Shifted to display the group of active health status records (health status records 9016A, 9016C) ahead of the group, thereby presenting the health status records in a different order than the order in FIG. 10F. Additionally, health condition records within each group are organized in alphabetical order based on the name of the health condition. FIG. 10G further illustrates detecting a tap gesture at contact 9516 on health record summary 5308, and in response to the tap gesture, displaying the updated health record summary in FIG. 10H.

Similar to Figure 10E, Figure 10H also illustrates displaying an updated health record summary after a user designates a health record as an inactive health record. In contrast to the embodiment of Figure 10E, medication records 9014A, 9014C (ABC Medication and GHI Medication) and health condition records 9016B, 9016D (Asthma and Migraine) were all designated as inactive health records. It is displayed simultaneously with active health records. In the illustrated embodiment, the displayed order of medication records 9014A through 9014D (ABC Drug, DEF Drug, GHI Drug, and LMN Drug, respectively), and health condition records 9016A through 9016D (anxiety disorder, respectively). , asthma, high cholesterol, and migraines) were rearranged to group active health records together and inactive health records together. Additionally, health records within each group are arranged alphabetically by name of corresponding medications (for drug records) or by name of corresponding health conditions (for health condition records). In other embodiments, all inactive health records are grouped together regardless of category, grouped in a different order, or identified in some other way that allows the user to distinguish active health records from inactive health records. Figure 10H further illustrates detecting a tap gesture at contact 9518 on affordance 9011B of drugs, and in response to the tap gesture, displaying the archive of drugs 9057 in Figure 10I.

Figure 10I illustrates an archive of drugs 9057 containing drug records 9014A to 9014D for ABC drug, DEF drug, GHI drug, and LMN drug, respectively. Each of medication records 9014A through 9014D also includes information regarding the health condition for which the medication was prescribed, the health care provider who provided the prescription for the medication, and the recommended dosage. In some embodiments, medication records 9014A-9014D may also display additional information about the corresponding medications, such as warnings, directions, locations of nearest pharmacies, as well as other information about the medications. Includes. In the illustrated embodiment, medication records 9014A and 9014C are displayed together and grayed out to indicate that the ABC medication and GHI medication are prescribed for inactive health conditions. In the illustrated embodiment, inactive medication records 9014A and 9014C are displayed together, organized alphabetically by name of the corresponding health conditions. In other embodiments, inactive medication records are organized alphabetically by name of medications, or other methods to help the user identify inactive health records.

In some embodiments of the archive of drugs 9057, a user can directly designate drug records 9014A through 9014D (ABC Drug, DEF Drug, GHI Drug, and LMN Drug, respectively) as active or inactive. For example, a DEF drug is prescribed for an active medical condition (anxiety disorder), but the user may be unable to use it (e.g., due to an allergic reaction to the DEF drug, due to accepting a prescription for an alternative drug to treat anxiety, or for any If the user is no longer taking the DEF drug (due to other reasons), the DEF drug can be designated as an inactive drug. In one or more of such embodiments, status toggles similar to the status toggles 9022A through 9022D illustrated in FIG. 10B (for anxiety disorder, asthma, high cholesterol, and migraine, respectively) are used for drug records 9014A through 9014D. ) is displayed together. In such embodiments, a user may toggle one or more status toggles to designate a corresponding medication record as an active health record or an inactive health record. In the illustrated embodiment, the archive of medications 9057 also includes a setting reminders affordance 9020, which is an affordance for a user to choose to designate reminders regarding certain health records. FIG. 10I further illustrates detecting a tap gesture at contact 9520 on set reminders affordance 9020, and in response to the tap gesture, displaying medication records 9014A-9014D in FIG. 10J do.

Figure 10J illustrates the display of medication records 9014A - 9014D (ABC Drug, DEF Drug, GHI Drug, and LMN Drug, respectively) to allow a user to set reminders for medications. Medication records 9014B, 9014D are displayed along with reminder toggles 9024A, 9024B. As used herein, a reminder toggle is an affordance for a user to select to set up one or more types of reminders regarding a corresponding health record. Examples of types of reminders include: reminders to take medication, reminders to refill medication, reminders to schedule a doctor's appointment, reminders to file an insurance claim, reminders about an upcoming appointment with a doctor, Include reminders to have laboratory tests performed, or any other suitable reminder regarding corresponding health records. In the illustrated embodiment, reminder toggles are not displayed with medication records 9014A, 9014C as medication records 9014A, 9014C are designated as inactive health records. In other embodiments, reminder toggles also provide reminders about medications to which the user corresponds (e.g., a reminder to renew an expired prescription, or a reminder to contact a doctor about a health condition associated with an expired prescription). Displayed with inactive drug records to enable setup. Figure 10J illustrates displaying medication records 9014A-9014D and reminder toggles 9024A, 9024B in a user interface 9060 that is separate from the archive of medications shown in Figure 10I. In other embodiments, medication records within archive of medications 9057 include medication records and corresponding reminder toggles. Figure 10J shows a swipe gesture at contact 9606 on reminder toggle 9024B to set a reminder for LMN medication in Figure 10K, and detecting movement of the contact from location 9606A to location 9606B. Additional examples are provided.

Figure 10K illustrates one embodiment of displaying a set reminders notification 9021 to set one or more reminders for LMN medication. In the illustrated embodiment, a set reminder notification 9021 is overlaid on a portion of the user interface 9060 of FIG. 10J, including a reminder toggle 9032A to set a reminder to take LMN medication, and a reminder toggle 9032A to set a reminder to refill LMN medication. Reminder toggle 9032B to set a reminder, and to set up a reminder to visit Alpha Healthcare (or a physician at Alpha Healthcare) regarding the user's cholesterol level, which is a medical condition for which LMN medication is prescribed to treat. Includes toggle (9032C). In other embodiments, each of the reminder toggles 9032A - 9032C, and the text describing the corresponding reminders, may be displayed instead of displaying reminder toggles 9024A, 9024B (for the DEF drug and LMN drug) in Figure 10J. is displayed directly in the user interface 9060 for each drug. In further embodiments, the archive of medications 9057 displays each of the reminder toggles 9032A - 9032C for each medication, such as the reminders setting affordance 9020 in Figure 10I and the user interface 9060 in Figure 10J. , and avoids the need for setting notification 9021 of reminders in FIG. 10K.

10K further illustrates a swipe gesture at contact 9608 on reminder toggle 9032A to set a reminder to take LMN medication, and detecting movement of the contact from location 9608A to location 9608B. do. In some embodiments, the user also specifies a time (or multiple times) during the day to receive reminders. In other embodiments, if the user does not specify a certain time for displaying the reminder, device 100 may select an appropriate time for displaying the reminder, such as a default time such as 10 p.m. or in the morning when the user's daily alarm is set. The decision is made automatically 15 minutes after ringing. In one or more of such embodiments, if the LMN medication is prescribed to be taken multiple times per day, device 100 may, after receiving a designated time to display a reminder to take the LMN medication, take the LMN medication. Automatically calculates other suitable times to display reminders to take. For example, if the medication is assumed to be taken three times a day and the user sets 11 p.m. for the first reminder, device 100 will set 7 a.m. for additional reminders. and 3 p.m. In further embodiments, device 100 accesses the user's calendar schedule and automatically designates a time (or multiple times) to display reminders to the user based on such calendar schedule. In some embodiments, device 100 may, after receiving a designated time to display a reminder to take the LMN medication, until the user changes that time or when the corresponding health record is designated as an inactive health record. Until then, the reminder will continue to be displayed at the specified time.

Figure 10L illustrates displaying a notification 9072 in response to a user setting a reminder to take LMN medication as described in Figure 10K. Notifications, such as notification 9072 (and notifications 9074, 9076, and 9078 illustrated in FIGS. 10N, 10O, and 10Q, respectively), can be placed on the lock screen for the user to review at designated times for such reminders. As a text message or other alert generated by device 100, as a notification badge within the border of the user interface, as a voice prompt from a digital assistant, as a voice prompt from a digital assistant, as a text message or other alert generated by device 100, on an overlay over any application being used, or may be displayed using any other combination of audio or visual notifications. In the illustrated embodiment, notification 9072 includes instructions for taking the LMN medication, including the prescribed dosage. In other embodiments, notification 9072 also includes additional information about the LMN drug, such as warnings, drug facts, ingredients, or other useful information about the LMN drug. Notification 9072 also includes an affordance of task completion 9082, which is an affordance for the user to select to indicate that the user has taken the LMN drug, and an affordance of ignore 9084, which ignores notification 9072. . Figure 10L further illustrates detecting a tap gesture at contact 9522 on affordance 9082 of task completion. In some embodiments, device 100 automatically tracks the amount of LMN drug remaining. In one such embodiment, device 100, in response to detecting a tap gesture at contact 9522 on affordance 9082 of task completion, dispenses the prescribed dose (two tablets) of the remaining LMN drug. The amount is automatically deducted. In some embodiments, the user performs another tap gesture on the contact on the ignore affordance 9084 to ignore the notification 9072. In other embodiments, device 100 may send a notification in response to detecting a tap gesture at a contact on notification 9072 or a tap gesture in an area of display 112 not covered by notification 9072 9072) is ignored. In the illustrated embodiment, notification 9072 is displayed at 10:00am on Saturday, January 8th. In other embodiments, if the user is unable to take the medication at the time of the reminder, the user can use the notification 9072 to delay or specify a different time (not shown) for receiving the notification 9072. there is. In further embodiments, device 100 determines the user's schedule and delays scheduled notifications to a time convenient for the user.

Similar to Figure 10K, Figure 10M illustrates displaying a settings notification 9021 of reminders overlaid on a portion of the user interface 9060. 10M further illustrates a swipe gesture at contact 9610 on reminder toggle 9032B to set up a reminder to refill LMN medication, and detecting movement of the contact from location 9610A to location 9610B. do. In some embodiments, device 100, in response to detecting a gesture to set a reminder to refill the LMN medication, determines the last date the prescription was filled, the number of daily doses given for the medication, and the LMN medication. The estimated remaining amount of LMN drug is calculated based on the number of days since the date on which it was prescribed to the user and based on the assumption that the user has taken the prescribed dose. Alternatively, device 100 may calculate the estimated remaining amount of LMN medication each time the user selects affordance 9082 of task completion in Figure 10L, including the number of prescribed doses provided for the medication and the last time the medication was refilled. Based on the date, it indicates in each case that the user has taken the prescribed dose. In any of the above-described embodiments, device 100 estimates the date the medication will be depleted based on such calculations and includes one or more devices to remind the user to refill the prescription before or on such estimated date. Determine predetermined times. In further embodiments, device 100 periodically queries the user to determine the amount of LMN drug remaining. In one embodiment, the user sets how far in advance such reminders should be given before the date on which such medication is estimated to run out.

Figure 10N illustrates displaying a notification 9074 reminding the user to refill LMN medication in response to the user setting a refill reminder as described in Figure 10M. Notification 9074 includes a number of affordances that the user can interact with to refill the LMN medication or to obtain more information about the LMN medication prior to refilling the LMN medication. In the illustrated embodiment, the user may select the Contact Physician affordance 9081 to contact the physician who prescribed the LMN medication. Additionally, the user may select the affordance 9083 of checking insurance coverage to determine the cost of refilling the LMN drug and the user's insurance coverage. The user may also select the pharmacist contact affordance 9085 to contact the pharmacist to refill the LMN medication or to determine the nearest pharmacy with LMN medication available for pickup. The user may select the affordance of electronic refill 9086 to initiate an alternative process for refilling the LMN medication. The user may also select the ignore affordance 9084 to ignore the notification 9074 without refilling the LMN medication. In some embodiments, notification 9074 includes different types of affordances with which the user can interact to perform other tasks related to refilling LMN medication. In the illustrated embodiment, notification 9074 is displayed on device 100 one week prior to the estimated date that the LMN medication will be depleted. In other embodiments, the user can select different times to receive notifications 9074 (e.g., two weeks before the LMN medication is estimated to run out) as well as how often the user wishes to receive notifications 9074 (e.g., per day). You can specify once, once a week, or any other time period).

Figure 10N further illustrates detecting a tap gesture at contact 9524 on the affordance 9086 of an electronic refill to refill LMN medication. In some embodiments, device 100 automatically initiates the electronic refill process after detecting a tap gesture at a contact on affordance 9086 of electronic refill. In such embodiments, in response to detecting a tap gesture at contact 9524 on affordance 9086 of an electronic refill in FIG. 10N, device 100 displays notification 9076 in FIG. 10O to refill the electronic refill 9086. Indicates that the refill request has been processed. In other embodiments, device 100, in response to detecting a tap gesture, displays a user interface through which a user can initiate an electronic refill process.

Similar to Figure 10M, Figure 10P illustrates displaying a settings notification 9021 of reminders overlaid on a portion of the user interface 9060. 10P shows a swipe gesture at contact 9612 and movement of the contact from location 9612A to location 9612B on reminder toggle 9032C to set a reminder to visit Alpha Healthcare at a scheduled appointment time. Detection is further illustrated. Alternatively, a reminder can be set to remind the user at a later date to schedule an appointment.

FIG. 10Q illustrates displaying a notification 9078 reminding the user about an upcoming appointment with Alpha Healthcare (a physician at) in response to the user setting an appointment reminder as depicted in FIG. 10P. Notification 9078 includes a number of affordances with which the user can interact to get directions to an appointment location, contact a doctor about an upcoming appointment, or re-schedule an upcoming appointment. In the illustrated embodiment, a user may select affordance 9092 of the maps to open the affordance of the map containing directions to Alpha Healthcare. The user may select the Contact a Physician affordance 9085 to contact the physician to discuss arrangements for an upcoming appointment. Additionally, the user may select the affordance of appointment re-scheduling 9094 to re-schedule an upcoming appointment time. The user may also select the ignore affordance 9084 to ignore the notification 9078. In some embodiments, notification 9078 includes different types of affordances with which the user can interact to perform other tasks related to the upcoming appointment. In some embodiments, the user can specify a time to receive notification 9078 (eg, one hour before the scheduled appointment). In other embodiments, if the user does not specify a time to receive notification 9078, device 100 automatically determines a time to display notification 9078. In one or more of such embodiments, device 100 delays notification 9078 or determines a time for notification 9078 based on the user's schedule. In other embodiments, when device 100 is authorized by a user to track the user's location, device 100 calculates an expected travel time from the user's current location to the appointment location. Device 100 then calculates the notification time by adding the threshold time as a fallback, subtracting the expected travel time and threshold time from the appointment time, and displays notification 9078 at or before the notification time.

11A-11E illustrate a health record manager that allows a user, using an electronic device, to specify the status of certain health records and manage activities associated with them through the health record manager, according to some embodiments. These are flowcharts illustrating how to display. More specifically, Figures 11A-11E are flowcharts illustrating a method for displaying a user's health record manager, for example, using the user interfaces of Figures 10A-10Q. As described with reference to FIGS. 10A-10Q, method 1100 may be utilized to display a health record manager that allows a user to specify the status of certain health records. Method 1100 is performed at a device (e.g., devices 100, 300, and 500 illustrated in FIGS. 1, 3, and 5A, respectively). In one such embodiment, display 112 is a touch screen display, and a touch-sensitive surface is on or integrated with display 112. In some embodiments, display 112 is separate from the touch-sensitive surface. In other embodiments, the processes described herein may be implemented in devices with physical user interfaces, voice interfaces, or other suitable interfaces. Some operations within method 1100 are optionally combined. Additionally, the order of some operations is optionally changed.

As described below, method 1100 provides an intuitive way to display a health record manager that allows a user to specify the status of certain health records and manage activities associated with them through the health record manager. to provide. Optionally, health records designated as inactive by the user are hidden from the health record manager's dashboard user interface, but displayed in other user interfaces containing more detailed information about the user's health records. A user can interact with inactive health records to update the status of the inactive health records. The method reduces cognitive burden on the user by allowing the user to distinguish between active and inactive health records, thereby creating a more efficient human-machine interface. The method also increases the user's efficiency by allowing the user to quickly distinguish between active and inactive health records and by providing the user with reminders regarding certain of the user's health records. For battery-operated computing devices, allowing a user to browse the user's active and inactive health records faster and more efficiently saves power and increases time between battery charges.

Device 100, while associated with the user's one or more health care providers, is configured to display a first of the user's plurality of ongoing health states indicated by health record information from the one or more health care providers. Displays a first representation, where the plurality of ongoing health states includes a second ongoing health state and a third ongoing health state (1102). 10A and 10B illustrate, for example, four health condition records 9016A - 9016D (anxiety disorder, asthma, high cholesterol, and migraine).

Device 100, while displaying a first representation of the first ongoing health condition, receives, via one or more input devices, a request to mark the first ongoing health condition as inactive for the user (1104). 10B illustrates, for example, a swipe gesture at a contact at contact 9602 on a status toggle 9022D (for migraine) to designate migraine as an inactive health state, and a location from location 9602A. The movement of the contact to 9602B is shown. The swipe gesture is detected by device 100 and causes device 100 to perform the actions illustrated in FIGS. 10C and 10D.

Device 100, after receiving the request to mark the first ongoing health condition as inactive, receives a request to display ongoing health conditions for the user, via one or more input devices (1106). 10D and 10E illustrate, for example, detecting a tap gesture at contact 9510 on affordance 5308 of a health record summary and, in response to the tap gesture, updated health record on display 112. Shown is displaying a summary. The tap gesture illustrated in Figure 10D is an example of a request to display ongoing health conditions.

In response to receiving a request to display ongoing health conditions for the user, device 100 displays the first representation of the user's first ongoing health condition on display 112 without displaying the first representation of the user's first ongoing health condition as an active health state. a second representation of the user's second ongoing health condition from a plurality of ongoing health conditions represented by health record information from one or more health care providers, and health records from one or more health care providers. Simultaneously display a third representation of the user's third ongoing health state from the plurality of ongoing health states represented by the information (1108). FIG. 10E shows, for example, health condition record 9016A (anxiety disorder), without displaying health condition record 9016D (migraine) illustrated in FIG. 10A that has been designated as an inactive health record by the user. Shown is the simultaneous display of 9016B (asthma), and health status record 9016C (high cholesterol).

In some embodiments, device 100, in response to receiving a request to mark the first ongoing health state as inactive, displays a visual indication on display 112 that the first ongoing health state is inactive. Display (1110). In some embodiments, if the inactive health state is not displayed in the health record summary, device 100 may provide an affordance for the user to interact with the inactive health records to view the inactive health records, or for the user to view the inactive health records in the health record summary. Displays the affordance of an inactive health record (not shown), a similar affordance to interact with. In other embodiments, the health record summary includes a badge or other item indicating that one or more health records have been marked as inactive and are not displayed in the health record summary. In one or more of such embodiments, the badge is attached to the affordance of health metrics 9011A of Figure 10A when the inactive health record is a health metric record and to the affordance of drugs 9011A of Figure 10A when the inactive health record is a medication record. 9011B, and if the inactive health record is a health state record, it is attached to the affordances of health states 9011C of FIG. 10A. In one or more embodiments, the badge includes a numeric value representing the number of inactive health records or the total number of inactive health records belonging to a category. The method reduces cognitive burden on the user by allowing the user to track inactive health records that are not displayed in the user interface. The method also increases the efficiency of the user by allowing the user to quickly determine the status of health records displayed in the user interface and determine whether certain health records of the user have been designated as inactive health records, comprising: This creates a more efficient human-machine interface.

In response to receiving a request to display a plurality of ongoing health states for the user, device 100 may display, on display 112, a visual indication that the first ongoing health state is inactive, and a second ongoing health state for the user. The ongoing health state and the user's third ongoing health state are simultaneously displayed (1112). In some embodiments, the affordances of viewing inactive health records and the badge described in the preceding paragraph can be used to create the health status records illustrated in FIG. 10E with health status records 9016A - 9016C (anxiety disorder, asthma, and high cholesterol, respectively). Displayed in the record summary. The method reduces cognitive burden on the user by tracking the current status of health records, thereby creating a more efficient human-machine interface. The method avoids the need to navigate multiple user interfaces to obtain active health records. The method also increases user efficiency by allowing the user to quickly determine the current status of the user's health records. For battery-operated computing devices, allowing a user to determine the status of the user's health records faster and more efficiently saves power and increases time between battery charges.

After receiving the request to mark the first ongoing health state as inactive, device 100 receives, via one or more input devices, a second request to mark the first health state as active (1114). In some embodiments, while health status record 9016D (migraine), illustrated in FIG. 10D , is marked as inactive, the user may perform a swipe gesture on a contact on status toggle 9022D (for migraine). , and perform movement of the contact in the direction of toggling the status toggle 9022D from an inactive designation to an active designation. In some embodiments, device 100, in response to receiving the second request to mark the first ongoing health state as active, configures the first ongoing health state to indicate that the first ongoing health state is active. Update the first representation (1114). Continuing with the above-described example, device 100 may, in response to detecting inputs that include a swipe gesture to toggle status toggle 9022D from an inactive designation to an active designation, generate health status record 9016D. Updates as an active health state.

In some embodiments, device 100 receives a second request to display a plurality of ongoing health states for the user after actively updating the first representation of the first ongoing health state (1114) . FIG. 10G illustrates a tap gesture at contact 9516, for example, on affordance 5308 of a health record summary. In some embodiments, device 100, in response to receiving the second request to display a plurality of ongoing health states for the user, displays an updated first ongoing health state on display 112. Simultaneously display the representation, the second representation of the second ongoing health state, and the third representation of the third ongoing health state (1114). Continuing with the previous example, if 9016D (migraine) is marked as an active health condition, health record 9016A (anxiety disorder), health record 9016C (high cholesterol), and health record 9016D are shown in FIG. 10H It will be displayed simultaneously in the health record summary illustrated in .

In some embodiments, device 100, in response to receiving a request to mark the first ongoing health condition as inactive, directs the computer system associated with the health care provider associated with the first ongoing health condition to: 1 Transmit along with information indicating the inactivity status of the ongoing health condition (1116). In some embodiments, device 100 may, after detecting inputs including the swipe gesture illustrated in FIG. 10B, indicate that health condition record 9016D (migraine) illustrated in FIG. 10B has been designated as an inactive record. is transmitted to Alpha Healthcare's computer system. The method reduces the need for a user to communicate with a health care provider regarding the status of a health record updated by the user, thereby reducing strain on existing networks, which frees up communication systems and networks. Reduces bandwidth and saves energy. The method also increases user efficiency by automatically providing status of health records to the health care provider's electronic system, thereby creating a more efficient human-machine interface.

In some embodiments, device 100, after receiving the update on the first ongoing health condition, receives a third request to display ongoing health conditions for the user, via one or more input devices ( 1118). In some embodiments, while health condition record 9016D (migraine) is designated as an inactive health record, device 100 receives a request from the user to update the status of health condition record 9016D. In other embodiments, device 100 receives an update from a health care provider that updates the status of a health record (eg, updates a prescription for a previously expired prescription for a medication). In some embodiments, device 100, in response to receiving the third request to display a plurality of ongoing health states for the user, displays an updated first ongoing health state on display 112. Simultaneously display the representation, the second representation of the second ongoing health state, and the third representation of the third ongoing health state (1118). Continuing with the previous example, if 9016D is marked as an active health condition, health record 9016A (anxiety disorder), health record 9016C (high cholesterol), and health record 9016D are as illustrated in FIG. 10H. It will be displayed simultaneously in the health record summary. The method reduces cognitive burden on the user by tracking updates to health records. The method also increases the user's efficiency by allowing the user to quickly determine the current status of the user's health records, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to determine the status of the user's health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100, in response to receiving an update on the first ongoing health state, marks the first ongoing health state as an active health state (1120). Continuing with reference to the above-described examples, device 100 may, in response to receiving an update from a user or a health care provider (Alpha Healthcare) associated with an ongoing health condition, record health condition record 9016D (migraine). Mark as active health record. The method reduces cognitive burden on the user by displaying updated status of ongoing health conditions in response to user input. For battery-operated computing devices, allowing a user to review the user's latest health records faster and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100, in response to receiving an update for the first ongoing health condition, transmits the update to a computer system associated with the health care provider associated with the first ongoing health condition ( 1122). In some embodiments, device 100, after receiving the update provided by the user, transmits an indication to Alpha Healthcare's computer system that health condition record 9016D (migraine) has been updated. In other embodiments, device 100 also transmits data indicating updates to a computer system. The method reduces the need for a user to communicate with a health care provider regarding the status of a health record updated by the user, thereby reducing strain on existing networks, which frees up communication systems and networks. Reduces bandwidth and saves energy. The method also increases user efficiency by automatically providing status of health records to the health care provider's electronic system, thereby creating a more efficient human-machine interface.

In some embodiments, device 100, in response to determining the set of dates associated with the second ongoing health condition, displays on display 112 a second ongoing health condition on each day of the set of dates. Display a notification regarding (1124). FIG. 10L illustrates displaying a notification 9072 reminding the user to take LMN medication, for example, after detecting the swiper gesture illustrated in FIG. 10K. In the embodiment of FIG. 10L , if the recommended dosage is two tablets every six hours, device 100 displays notification 9072 on display 112 at least once a day, each day. The method reduces cognitive burden on the user by tracking a set of days associated with a health condition and automatically displaying notifications on days associated with the health condition. The method also increases the user's efficiency by helping the user track days associated with a health condition and automatically providing notifications on days associated with a health condition, thereby creating a more efficient human-machine interface. do.

In some embodiments, the set of dates associated with the second ongoing health condition includes a first date, where the first date is the date on which the prescription for the second ongoing health condition is scheduled to be refilled, and the notification is Includes a reminder to refill (1126). FIG. 10N illustrates displaying a notification 9074 reminding the user to refill LMN medication, for example, after detecting the swipe gesture illustrated in FIG. 10M. In the illustrated embodiment, notification 9074 is provided to the user one week prior to the scheduled date on which the LMN medication will be depleted. In other embodiments, when a refill request has been processed, a similar notification reminding the user to pick up the LMN medication is displayed on the scheduled pickup date. The method reduces the cognitive burden on the user by predicting when the drug will fall below a threshold. The method also increases the user's efficiency by helping the user decide when to refill a prescription, thereby creating a more efficient human-machine interface. The method also reduces strain on a health care provider's electronic system tasked with reminding the user to refill the user's prescription, thereby freeing up communication systems and reducing bandwidth on networks, Save energy.

In some embodiments, device 100 anticipates a date when the remaining amount of a prescription for a second ongoing health condition will be below a threshold, where the set of dates associated with the second ongoing health condition includes the second date. wherein the second date is the date on which the prescription is expected to be below the threshold, and the notification includes a reminder to refill the prescription (1128). In some embodiments, device 100 tracks remaining doses of LMN drug. In the embodiment of Figure 10L, device 100, in response to detecting a tap gesture on affordance 9082 of task completion, subtracts the recommended dose from the remaining dose. In other embodiments, device 100 assumes that the user takes the recommended dose and estimates the remaining amount based on the recommended dose. FIG. 10N illustrates displaying a notification 9074 reminding the user to refill LMN medication, e.g., after detecting the swipe gesture illustrated in FIG. 10M. In the illustrated embodiment, notification 9074 is provided to the user one week prior to the scheduled date on which the LMN medication will be depleted. In the illustrated example, the threshold is the amount of LMN drug that will be sufficient for the user for more than one week. The method reduces cognitive burden on the user by predicting when medication will fall below a threshold and automatically transmits a request to refill the prescription to the health care provider. The method also increases the user's efficiency by automatically submitting requests to refill prescriptions without requiring the user to track the remaining amount of the prescription, thereby creating a more efficient human-machine interface. Reducing the time users need to spend on their devices reduces the device's power usage and improves battery life.

In some embodiments, device 100 requests, on a second date, a health care provider from one or more health care providers to refill a prescription, where the health care provider is associated with a second ongoing health condition. (1130). FIG. 10N illustrates displaying a notification 9074 reminding the user to refill LMN medication, e.g., after detecting the swipe gesture illustrated in FIG. 10M. In the illustrated embodiment, notification 9074 is provided to the user one week prior to the scheduled date on which the LMN medication will be depleted. In the illustrated embodiment, device 100 requests the health care provider to refill the LMN prescription in response to detecting the gesture illustrated in FIG. 10N over affordance 9086 of electronic refill. In other embodiments, device 100 automatically initiates a request to refill LMN medication. The method reduces cognitive burden on the user by automatically requesting a health care provider to refill the prescription. The method also increases the user's efficiency by reducing the user's need to communicate with a health care provider, thereby creating a more efficient human-machine interface. For battery-operated computing devices, automatically requesting a prescription refill from a health care provider reduces the need for the user to use the device to perform such tasks through the device, thereby saving power and Increases the time between battery charges.

In some embodiments, device 100 receives, via one or more input devices, an update on the remaining amount of the prescription for the second ongoing health condition (1132). In some embodiments, device 100 periodically queries the user to provide an estimate of the amount of prescription medication remaining. In some embodiments, device 100 displays (1132) a notification to refill the prescription on display 112 upon determining that the remaining amount of the prescription is below the threshold. In some embodiments, notification 9074, illustrated in FIG. 10N, is displayed in response to a determination that the user input amount of medication remaining is below a threshold (e.g., one week or less). The method reduces cognitive burden on the user by helping the user keep track of the remaining amount of the user's prescription, thereby creating a more efficient human-machine interface. The method also increases the user's efficiency by helping the user decide when to refill a prescription, thereby creating a more efficient human-machine interface. The method also reduces strain on a health care provider's electronic system tasked with reminding the user to refill the user's prescription, thereby freeing up communication systems and reducing bandwidth on networks, Save energy. For battery-operated computing devices, allowing the user to determine the remaining amount of a prescription faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the set of dates associated with the second ongoing health condition includes a third date, where the third date is a scheduled date for visiting a health care provider of one or more health care providers, and The care provider is associated with the second ongoing health condition (1134). FIG. 10Q illustrates displaying a notification 9078 reminding the user about a scheduled appointment with Alpha Healthcare, for example, on the appointment date. The method reduces cognitive burden on the user by tracking upcoming appointments with health care providers. The method also reduces the device's power usage and improves battery life by reducing the likelihood that the device will need to perform additional tasks to reschedule an appointment with a health care provider. The method further reduces the need for a health care provider to remind the user about an upcoming appointment or contact the user about a missed appointment, thereby freeing up communication systems and reducing bandwidth on networks. , saves energy.

In some embodiments, device 100 displays, on display 112, an affordance of a first reminder associated with a second ongoing health condition (1136). Figure 10K shows, for example, displaying a reminder toggle 9032A to set up a reminder to take LMN medication. In some embodiments, device 100, while displaying the affordances of the first reminder, receives, via one or more input devices, a request to select an affordance of the first reminder (1136). 10K illustrates, for example, a swipe gesture at contact 9608 on reminder toggle 9032A to set up a reminder to take LMN medication, and detecting movement of the contact from location 9608A to location 9608B. Additional examples are provided. The method reduces cognitive burden on the user by helping the user set up reminders regarding the user's health status and by helping the user track the health status. The method also increases the user's efficiency by helping the user track health conditions, thereby creating a more efficient human-machine interface. The method also reduces the likelihood that the user will forget about the health condition and reduces the likelihood that the user will experience complications resulting from ignoring the health condition. For battery-operated computing devices, helping users track their health status more easily and more efficiently saves power and increases time between battery charges.

In some embodiments, device 100 displays a second ongoing health condition and a reminder on display 112 at that time, upon determining that the reminder associated with the second ongoing health condition is also associated with a time. Display notifications regarding associated reminders (1137). In some embodiments, the user specifies a time (eg, 10:00am) to receive reminders to take the LMN medication. Then, the device 100 displays notifications to take the LMN drug at the designated time. FIG. 10L illustrates displaying a notification 9072 to take LMN medication, for example, at 10:00am. The method reduces the cognitive burden on the user by reminding the user when to take the drug. The method also increases the user's efficiency by helping the user track when to take medications, thereby creating a more efficient human-machine interface. The method also reduces the likelihood that the user will forget to take the medication or take the medication at the wrong time, and reduce the likelihood that the user will experience complications resulting from not taking the medication. For battery-operated computing devices, allowing users to decide faster and more efficiently when to take medication saves power and increases time between battery charges.

In some embodiments, the reminder associated with the second ongoing health condition is a recurring reminder associated with an interval of time where the user is instructed to take a prescription for the second ongoing health condition, and the notification is a prescribed dose of the prescription. This is a reminder to take (1138). In the illustrated example of Figure 10L, the LMN drug is scheduled to be taken daily. As such, the notification 9072 to take LMN medication is a repeated notification. In some embodiments, notification 9072 is displayed on display 112 daily at 10:00am and 4:00pm. The method reduces the cognitive burden on the user by reminding the user when to take the drug. The method also increases the user's efficiency by helping the user track when to take medications, thereby creating a more efficient human-machine interface. The method also reduces the likelihood that the user will forget to take the medication or take the medication at the wrong time, and reduce the likelihood that the user will experience complications resulting from not taking the medication. For battery-operated computing devices, allowing users to decide faster and more efficiently when to take medication saves power and increases time between battery charges.

In some embodiments, the notification includes an affordance of a second reminder associated with the reminder (1140). In some embodiments, the affordance of the reminder is an affordance that the user selects to indicate that the user has taken the prescribed dose. Notification 9072 includes an affordance 9072 of task completion. The device 100 receives a request to select an affordance of the second reminder through one or more input devices (1140). FIG. 10L illustrates detecting a tap gesture at contact 9522, for example, on the affordance 9082 of task completion. Device 100, in response to receiving a request to select an affordance of the second reminder, calculates the remaining amount of the prescription (1140). In some embodiments, device 100 automatically tracks the amount of LMN drug remaining. In one such embodiment, device 100, in response to detecting the gesture illustrated in Figure 10L, automatically deducts the remaining amount of LMN drug as the prescribed dose (two tablets). In some embodiments, device 100 displays a second notification regarding a second ongoing health condition on display 112 in response to a determination that the remaining amount of the prescription is below a threshold, wherein the second notification is: This is a reminder to refill your prescription (1140). In some embodiments, device 100 may send notification 9074, illustrated in FIG. 10N , to remind the user to refill the LMN medication after determining that the remaining amount of the LMN prescription is below a threshold (more than one week of supply). ) is displayed. The method reduces cognitive burden on the user by helping the user keep track of the remaining amount of the user's prescription, thereby creating a more efficient human-machine interface. The method also increases the user's efficiency by helping the user decide when to refill a prescription, thereby creating a more efficient human-machine interface. The method also reduces strain on a health care provider's electronic system tasked with reminding the user to refill the user's prescription, thereby freeing up communication systems and reducing bandwidth on networks, Save energy. For battery-operated computing devices, allowing the user to determine the remaining amount of a prescription faster and more efficiently saves power and increases time between battery charges.

In some embodiments, the user is a patient and device 100 is the patient's device. Device 100 is a user device. In some embodiments, device 100 is a patient's device. In some embodiments, while the patient device is associated with the patient's one or more health care providers, device 100 displays a first representation of the first ongoing health condition on display 112 of the patient device. Do (1142). 10A and 10B illustrate, for example, four health condition records 9016A - 9016D (anxiety disorder, asthma, high cholesterol, and migraine, respectively). In some embodiments, device 100, while displaying a representation of the first ongoing health condition on the patient device, may, via one or more input devices, request to mark the first ongoing health condition as inactive for the patient. A request from the patient is received from the patient (1142). 10B illustrates, for example, a swipe gesture at contact 9602 on a status toggle 9022D (for migraine) to designate migraine as an inactive health state, and from location 9602A to location 9602B. Shows the movement of contact to The swipe gesture is detected by device 100 and causes device 100 to perform the actions illustrated in FIGS. 10C and 10D.

In some embodiments, device 100, after receiving a request from the patient to mark the first ongoing health condition as inactive, is configured to display ongoing health conditions for the user, via one or more input devices. A request from the patient is received (1142). 10D and 10E illustrate, for example, detecting a tap gesture at contact 9510 on affordance 5308 of a health record summary, and in response to the tap gesture, updated health record on display 112. Shown is displaying a summary. The tap gesture illustrated in Figure 10D is an example of a request to display ongoing health conditions. In some embodiments, device 100 may, in response to receiving a request from a patient to display ongoing health conditions for the patient, display the patient device without displaying a representation of the first ongoing health condition. On 112, the second representation of the second ongoing health state and the third representation of the third ongoing health state are displayed simultaneously (1142). 10E shows, for example, health condition records 9016A, 9016B, 9016C (anxiety disorder, asthma, and high cholesterol) is shown simultaneously. The method reduces cognitive burden on the patient by allowing the patient to distinguish between active and inactive health records, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing a patient to browse the user's active and inactive health records faster and more efficiently saves power and increases time between battery charges.

The specific order in which the operations in FIGS. 11A-11E are described is illustrative only and is not intended to indicate that the described order is the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, details of the processes described above with respect to method 1100 (e.g., FIGS. 11A-11E) are also applicable in a similar manner to the methods described above. For example, methods 700 and 900 optionally include one or more of the features of the various methods described above with respect to method 1100. For example, methods for displaying health records specified by a user as active or inactive, described above with reference to 1100, are optionally used by method 700 to display aggregated health records, such as in a dashboard. Optionally used by method 900 to display health records in user interfaces. For brevity, these details are not repeated below.

The foregoing description, for purposes of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments were selected and described to best illustrate the principles of the techniques and their practical applications. Accordingly, those skilled in the art will be able to best utilize the techniques and various embodiments using various modifications as appropriate for the particular use contemplated.

Although the present disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will be apparent to those skilled in the art. It is to be understood that such changes and modifications are included within the scope of the disclosure and examples as defined by the claims.

As described above, one aspect of the present technology is the collection and use of data available from various sources to enhance the delivery to users of invited content or any other content that may be of interest to users. . The present invention contemplates that, in some cases, such collected data may include personal information data that uniquely identifies a particular individual or can be used to contact or locate that individual. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, home addresses, or any other identifying information.

The present invention recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data may be used to deliver targeted content of greater interest to users. Accordingly, the use of such personal information data enables calculated control of the delivered content. Additionally, other uses for personal information data that benefit the user are also contemplated by the present invention.

This disclosure further contemplates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities must implement and continue to use privacy policies and practices that are generally recognized as meeting or exceeding industry or administrative requirements for keeping personal information data private and secure. For example, personal information from users must be collected for lawful and appropriate uses of the entity, and must not be shared or sold beyond those lawful uses. Additionally, such collection should only occur after receiving the informed consent of users. Additionally, such entities will take whatever steps are necessary to protect and secure access to such Personal Information Data and to ensure that other persons having access to Personal Information Data adhere to their privacy policies and procedures. In addition, such entities may themselves be evaluated by third parties to demonstrate their adherence to widely accepted privacy policies and practices.

Notwithstanding the foregoing, the present invention also contemplates embodiments in which a user selectively blocks use of, or access to, personal information data. That is, the present invention contemplates that hardware and/or software elements may be provided to prevent or block access to such personal information data. For example, in the case of advertising delivery services, this technology allows users to “opt in” or “opt out” of their participation in the collection of personal information data during registration for the service. It can be configured to allow. In another example, users may choose not to provide location information for targeted content delivery services. In another example, users may choose not to provide precise location information but allow delivery of location zone information.

Accordingly, although the present invention broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the invention also contemplates that various embodiments may also be implemented without the need for access to such personal information data. do. That is, various embodiments of the present technology are not rendered inoperable by the absence of all or part of such personal information data. For example, content may contain a minimal amount of personal information or non-personal information, such as content requested by a device associated with a user, other non-personal information available to content delivery services, or publicly available information. Based on preferences, they can be selected and communicated to users by inferring preferences.

Claims (19)

As a method,
In an electronic device having a display and one or more input devices,
While the electronic device is associated with health data for a first user, including a plurality of health record items of a first type and a plurality of health record items of a second type different from the first type, the one or more receiving, via input devices, a request to display health record summary information for the first user;
In response to receiving the request, displaying health record summary information for the first user, including simultaneously displaying, on the display, a plurality of health record items, the plurality of health record items comprising:
a first health record item of the first type having a first date, wherein health record summary information excludes a plurality of health record items of the first type having dates earlier than the first date; and
A second health record item of the second type having a second date different from the first date—health record summary information excludes a plurality of health record items of the second type having a date earlier than the second date. - Contains -;
While displaying health record summary information for the first user on the display, a first request to display, via the one or more input devices, a plurality of health record items of the first type that are not displayed in the summary. receiving; and
In response to receiving the first request to display a plurality of health record items of the first type that are not displayed in the summary, display, on the display, a plurality of health record items of the first type having dates earlier than the first date. Displaying a plurality of health record items
Method, including. The method of claim 1, wherein the health data for the first user includes a plurality of health record items of a third type different from the first type and the second type, and displaying health record summary information comprises: further comprising simultaneously displaying the first health record item, the second health record item, and the third type of third health record item having a third date, wherein the health record summary information is equal to the third date. and excluding the third type of plurality of health record items with earlier dates. The method of claim 1, wherein the health data includes health data associated with a plurality of health care providers of the first user, and the first health record item is associated with a first health care provider of the plurality of health care providers. and wherein the second health record item is associated with a second health care provider of the plurality of providers. 2. The method of claim 1, wherein the plurality of health record items comprises a fourth type of fourth health record item having a fourth date, wherein the first health record item and the fourth health record item are from a first health care provider. and wherein the first date and the fourth date are the dates of the first and second visits to the first health care provider. The method of claim 1, wherein 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 having a third date that is after the first date;
After receiving the third health record item, receiving, via the one or more input devices, a second request to display health record summary information for the first user; and
In response to receiving the second request, simultaneously displaying the second health record item and the third health record item on the display without displaying the first health record item. 1. The method further comprising displaying updated health record summary information for the user. The method of claim 1, wherein 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 for the first user, the new health record item having a date that is more recent than the first date and the second date;
After receiving the new health record item, receiving, via the one or more input devices, a third request to display health record summary information for the first user; and
In response to receiving the third request, simultaneously displaying the first health record item, the second health record item, and the new health record item on the display. The method further comprising displaying the health record summary information. delete According to paragraph 1,
In response to receiving the first request to display a plurality of health record items of the first type that are not displayed in the summary, on the display, a health record item of the first type having a most recent date, and simultaneously displaying one or more health record items of the plurality of health record items of the first type having dates earlier than the first date. A method further comprising: According to clause 8,
In response to receiving the first request to display a plurality of health record items of the first type that are not displayed in the summary, on the display, a fourth health record of the first type in the archive of health records. The method further comprising displaying an item, wherein the fourth health record item includes a representation of a health metric measured on a fourth date earlier than the first date. The method of claim 1, wherein after displaying health record summary information having the first health record and the second health record,
receiving a third type of third health record item having a third date that is more recent than the first date and the second date; and
In response to a request to view health record summary information, the method further includes updating the health record summary information to include the third health record item, the first health record item, the second health record item, and The method of claim 1, wherein the third health record item is simultaneously displayed in health record summary information. The method of claim 1, wherein the first health record item includes an expression of the severity of the first user's condition. The method of claim 1, wherein the first health record item includes a representation of the first user's condition over a period of time. According to paragraph 1,
In response to the request to display health record summary information, further comprising, in response to a determination that a health record item of the health data for the first user is incomplete, displaying an affordance of an incomplete record in health record summary information. How to. According to paragraph 1,
receiving, via the one or more input devices, user verification of the accuracy of certain health record items among the plurality of health record items displayed in health record summary information; and
In response to receiving the user verification of accuracy of the health record item, the method further comprising providing the user verification to a health care provider associated with the health record item. According to paragraph 1,
receiving, via the one or more input devices, a first user indication that certain health record items among the plurality of health record items included in health record summary information are inaccurate; and
In response to receiving the first user indication, excluding the health record item from health record summary information, wherein the health record item is not included in the health record summary information after being excluded from health record summary information. No longer included, method. 16. The method of claim 15, comprising in response to receiving the first user indication, automatically, without further user input, transmitting a request for updated information for the health record item from a health care provider computer system. How to. According to paragraph 1,
receiving, via the one or more input devices, information updating the first health record item; and
After receiving the information updating the first health record item, receiving a second request to display health record summary information for the first user; and
In response to receiving the request to display health record summary information for the first user, simultaneously displaying an updated first health record item reflecting changes to the first health record item and the second health record item. The method further comprising displaying an updated health record summary for the first user, including displaying. As an electronic device,
display;
one or more input devices;
one or more processors;
Memory; and
and one or more programs stored in the memory and configured to be executed by the one or more processors, wherein the one or more programs perform the method of any one of claims 1 to 6 and 8 to 17. An electronic device comprising instructions for. A computer-readable storage medium 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, cause the electronic device to: A computer-readable storage medium comprising instructions for performing the method of any one of claims 8 to 17.

Images