CN117441211A - User interface related to clinical data - Google Patents

Abstract

The present disclosure relates generally to methods and user interfaces for displaying and managing a user interface including information related to physiological measurements. In some embodiments, methods and user interfaces for displaying laboratory types based on whether the laboratory type has been previously specified are described. In some embodiments, methods and user interfaces for displaying a user interface including a health topic are described, where information included in the user interface corresponds to a selected health topic.

Description

User interface related to clinical data

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No. 63/197,422 entitled "USER INTERFACES RELATED TO CLINICAL DATA" filed 6/2021 and U.S. patent application No. 17/540,991 entitled "USER INTERFACES RELATED TO CLINICAL DATA" filed 2/12/2021, the contents of each of which are hereby incorporated by reference in their entirety.

Technical Field

The present disclosure relates generally to computer user interfaces, and more particularly to techniques for displaying and managing user interfaces that include information related to physiological measurements.

Background

The personal electronic device allows the user to view information related to the physiological measurements. Some personal electronic devices include the ability to display a user interface related to physiological measurements.

Disclosure of Invention

However, some techniques for displaying and managing user interfaces including information related to physiological measurements using electronic devices are often cumbersome and inefficient. For example, some prior art uses complex and time-consuming user interfaces that may include multiple key presses or keystrokes, particularly when displaying information related to multiple physiological measurements. The prior art requires more time than is necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

Thus, the present technology provides faster, more efficient methods and interfaces for an electronic device to display and manage a user interface that includes information related to physiological measurements. Such methods and interfaces optionally complement or replace other methods for displaying and managing user interfaces including information related to physiological measurements. Such methods and interfaces reduce the cognitive burden on the user and result in a more efficient human-machine interface. For battery-powered computing devices, such methods and interfaces conserve power and increase the time interval between battery charges.

According to some embodiments, a method performed at a computer system in communication with a display generation component and one or more input devices is described. The method comprises the following steps: displaying, via a display generating component, a first user interface comprising user-interactive graphical user interface objects corresponding to a first laboratory type, wherein: in accordance with a determination that a first laboratory type has been specified via user input received through one or more input devices, a user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and in accordance with a determination that the first laboratory type has not been specified via the user input, displaying, via the display generating component, a user-interactive graphical user interface object corresponding to the first laboratory type without displaying a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type.

According to some embodiments, a non-transitory computer readable storage medium is described. The non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with the display generation component and the one or more input devices, the one or more programs comprising instructions for: displaying, via a display generating component, a first user interface comprising user-interactive graphical user interface objects corresponding to a first laboratory type, wherein: in accordance with a determination that a first laboratory type has been specified via user input received through one or more input devices, a user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and in accordance with a determination that the first laboratory type has not been specified via the user input, displaying, via the display generating component, a user-interactive graphical user interface object corresponding to the first laboratory type without displaying a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type.

According to some embodiments, a transitory computer readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: displaying, via a display generating component, a first user interface comprising user-interactive graphical user interface objects corresponding to a first laboratory type, wherein: in accordance with a determination that a first laboratory type has been specified via user input received through one or more input devices, a user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and in accordance with a determination that the first laboratory type has not been specified via the user input, displaying, via the display generating component, a user-interactive graphical user interface object corresponding to the first laboratory type without displaying a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type.

According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via a display generating component, a first user interface comprising user-interactive graphical user interface objects corresponding to a first laboratory type, wherein: in accordance with a determination that a first laboratory type has been specified via user input received through one or more input devices, a user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and in accordance with a determination that the first laboratory type has not been specified via the user input, displaying, via the display generating component, a user-interactive graphical user interface object corresponding to the first laboratory type without displaying a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type.

According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: means for displaying, via the display generating component, a first user interface comprising a user-interactive graphical user interface object corresponding to a first laboratory type, wherein: in accordance with a determination that a first laboratory type has been specified via user input received through one or more input devices, a user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and in accordance with a determination that the first laboratory type has not been specified via the user input, displaying, via the display generating component, a user-interactive graphical user interface object corresponding to the first laboratory type without displaying a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type.

According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for: displaying, via a display generating component, a first user interface comprising user-interactive graphical user interface objects corresponding to a first laboratory type, wherein: in accordance with a determination that a first laboratory type has been specified via user input received through one or more input devices, a user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and in accordance with a determination that the first laboratory type has not been specified via the user input, displaying, via the display generating component, a user-interactive graphical user interface object corresponding to the first laboratory type without displaying a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type.

According to some embodiments, a method performed at a computer system in communication with a display generation component and one or more input devices is described. The method comprises the following steps: a clinical data set is received at a computer system, the clinical data set comprising: a set of data instances corresponding to a first health topic, and a set of data instances corresponding to a second health topic different from the first health topic; displaying, via a display generating component, a clinical data user interface, the clinical data user interface comprising: a first user interactive graphical user interface object corresponding to a first health topic; a second user interactive graphical user interface object corresponding to a second wellness topic; and a set of data instance graphical user interface objects, wherein: in accordance with a determination that a first user-interactive graphical user interface object is currently selected, a set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a first health topic; and in accordance with a determination that a second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a second health topic.

According to some embodiments, a non-transitory computer readable storage medium is described. The non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with the display generation component and the one or more input devices, the one or more programs comprising instructions for: a clinical data set is received at a computer system, the clinical data set comprising: a set of data instances corresponding to a first health topic, and a set of data instances corresponding to a second health topic different from the first health topic; displaying, via a display generating component, a clinical data user interface, the clinical data user interface comprising: a first user interactive graphical user interface object corresponding to a first health topic; a second user interactive graphical user interface object corresponding to a second wellness topic; and a set of data instance graphical user interface objects, wherein: in accordance with a determination that a first user-interactive graphical user interface object is currently selected, a set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a first health topic; and in accordance with a determination that a second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a second health topic.

According to some embodiments, a transitory computer readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: a clinical data set is received at a computer system, the clinical data set comprising: a set of data instances corresponding to a first health topic, and a set of data instances corresponding to a second health topic different from the first health topic; displaying, via a display generating component, a clinical data user interface, the clinical data user interface comprising: a first user interactive graphical user interface object corresponding to a first health topic; a second user interactive graphical user interface object corresponding to a second wellness topic; and a set of data instance graphical user interface objects, wherein: in accordance with a determination that a first user-interactive graphical user interface object is currently selected, a set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a first health topic; and in accordance with a determination that a second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a second health topic.

According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: a clinical data set is received at a computer system, the clinical data set comprising: a set of data instances corresponding to a first health topic, and a set of data instances corresponding to a second health topic different from the first health topic; displaying, via a display generating component, a clinical data user interface, the clinical data user interface comprising: a first user interactive graphical user interface object corresponding to a first health topic; a second user interactive graphical user interface object corresponding to a second wellness topic; and a set of data instance graphical user interface objects, wherein: in accordance with a determination that a first user-interactive graphical user interface object is currently selected, a set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a first health topic; and in accordance with a determination that a second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a second health topic.

According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: means for receiving a clinical data set at a computer system, the clinical data set comprising: a set of data instances corresponding to a first health topic, and a set of data instances corresponding to a second health topic different from the first health topic; means for displaying, via a display generating component, a clinical data user interface comprising: a first user interactive graphical user interface object corresponding to a first health topic; a second user interactive graphical user interface object corresponding to a second wellness topic; and a set of data instance graphical user interface objects, wherein: in accordance with a determination that a first user-interactive graphical user interface object is currently selected, a set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a first health topic; and in accordance with a determination that a second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a second health topic.

According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for: means for receiving a clinical data set at a computer system, the clinical data set comprising: a set of data instances corresponding to a first health topic, and a set of data instances corresponding to a second health topic different from the first health topic; displaying, via a display generating component, a clinical data user interface, the clinical data user interface comprising: a first user interactive graphical user interface object corresponding to a first health topic; a second user interactive graphical user interface object corresponding to a second wellness topic; and a set of data instance graphical user interface objects, wherein: in accordance with a determination that a first user-interactive graphical user interface object is currently selected, a set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a first health topic; and in accordance with a determination that a second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a second health topic.

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 transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

Thus, a faster, more efficient method and interface for displaying and managing a user interface including information related to physiological measurements is provided for a device, thereby improving the effectiveness, efficiency and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for displaying and managing user interfaces including information related to physiological measurements.

Drawings

For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, in which like reference numerals designate corresponding parts throughout the several views.

Fig. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.

Fig. 2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

Fig. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

Fig. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display in accordance with some embodiments.

Fig. 5A illustrates a personal electronic device according to some embodiments.

Fig. 5B is a block diagram illustrating a personal electronic device, according to some embodiments.

Fig. 6A-6N illustrate exemplary user interfaces for displaying laboratory types based on their designated status.

Fig. 7 is a flow chart illustrating a method for displaying laboratory types based on specified states of the laboratory types using a computer system, according to some embodiments.

Fig. 8A-8I illustrate an exemplary user interface for displaying a health topic.

Fig. 9 is a flowchart illustrating a method for displaying a health topic using a computer system in accordance with some embodiments.

Detailed Description

The following description sets forth exemplary methods, parameters, and the like. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of exemplary embodiments.

There is a need for an electronic device that provides an efficient method and interface for displaying and managing a user interface that includes information related to physiological measurements. For example, the laboratory type needs to be displayed based on a specified state of the laboratory type. As another example, there is a need for an apparatus that enables an intuitive and efficient method for displaying a health topic. Such techniques may reduce the cognitive burden on users who regularly view various laboratory types, thereby improving productivity. Further, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user inputs.

1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of an exemplary device for performing techniques for managing event notifications. Fig. 6A-6N illustrate exemplary user interfaces for displaying laboratory types based on their designated status. Fig. 7 is a flow chart illustrating a method for displaying laboratory types based on specified states of laboratory types, according to some embodiments. The user interfaces in fig. 6A-6N are used to illustrate the processes described below, including the process in fig. 7. Fig. 8A-8I illustrate an exemplary user interface for displaying a health topic. Fig. 9 is a flow chart illustrating a method for displaying a health topic in accordance with some embodiments. The user interfaces in fig. 8A-8I are used to illustrate the processes described below, including the process in fig. 9.

The processes described below enhance operability of the device and make the user-device interface more efficient through various techniques (e.g., by helping a user provide appropriate input and reducing user error in operating/interacting with the device), including by providing improved visual feedback to the user, reducing the number of inputs required to perform the operation, providing additional control options without cluttering the user interface with additional display controls, performing the operation when a set of conditions has been met without further user input and/or additional techniques. These techniques also reduce power usage and extend battery life of the device by enabling a user to use the device faster and more efficiently.

Furthermore, in a method described herein in which one or more steps are dependent on one or more conditions having been met, it should be understood that the method may be repeated in multiple iterations such that during the iteration, all conditions that determine steps in the method have been met in different iterations of the method. For example, if a method requires performing a first step (if a condition is met) and performing a second step (if a condition is not met), one of ordinary skill will know that the stated steps are repeated until both the condition and the condition are not met (not sequentially). Thus, a method described as having one or more steps depending on one or more conditions having been met may be rewritten as a method that repeats until each of the conditions described in the method have been met. However, this does not require the system or computer-readable medium to claim that the system or computer-readable medium contains instructions for performing the contingent operation based on the satisfaction of the corresponding condition or conditions, and thus is able to determine whether the contingent situation has been met without explicitly repeating the steps of the method until all conditions to decide on steps in the method have been met. It will also be appreciated by those of ordinary skill in the art that, similar to a method with optional steps, a system or computer readable storage medium may repeat the steps of the method as many times as necessary to ensure that all optional steps have been performed.

Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another element. For example, a first touch may be named a second touch and similarly a second touch may be named a first touch without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some implementations, both the first touch and the second touch are touches, but they are not the same touch.

The terminology used in the description of the various illustrated embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also 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. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

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

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. 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 the portable multifunction device include, but are not limited to, those from Apple inc (Cupertino, california)Device, iPod->Device, and->An apparatus. Other portable electronic devices, such as a laptop or tablet computer having a touch-sensitive surface (e.g., a touch screen display and/or a touchpad), are optionally used. It should also be appreciated that in some embodiments, the device is not a portable communication device, but rather has a touch-sensitive watch Desktop computers with surfaces (e.g., touch screen displays and/or touch pads). In some embodiments, the electronic device is a computer system in communication (e.g., via wireless communication, via wired communication) with the display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, "displaying" content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually produce the content.

In the following discussion, an electronic device including 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.

The device typically supports various applications such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, fitness 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.

The various applications executing on the device optionally use at least one generic physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed for different applications and/or within the respective applications. In this way, the common physical architecture of the devices (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

Attention is now directed to embodiments of a portable device having a touch sensitive display. Fig. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience and is sometimes referred to or referred to as a "touch-sensitive display system". Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripheral interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external ports 124. The apparatus 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 (e.g., generating tactile output on a touch-sensitive surface, such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300) for generating tactile output on device 100. These components optionally communicate via one or more communication buses or signal lines 103.

As used in this specification and the claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of the contact on the touch-sensitive surface (e.g., finger contact), or to an alternative to the force or pressure of the contact on the touch-sensitive surface (surrogate). The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. 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 and/or its variation detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface and/or its variation in the vicinity of the contact and/or the resistance of the touch-sensitive surface and/or its variation in the vicinity of the contact are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, surrogate measurements of contact force or pressure are directly used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to surrogate measurements). In some implementations, surrogate 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., the intensity threshold is a pressure threshold measured in units of pressure). The intensity of the contact is used as an attribute of the user input, allowing the user to access additional device functions that are not otherwise accessible to the user on a smaller sized device of limited real estate for displaying affordances and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical control, such as a knob or button).

As used in this specification and in the claims, the term "haptic output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to a centroid of the device, to be detected by a user with a user's feel. For example, in the case where the device or component of the device is in contact with a touch-sensitive surface of the user (e.g., a finger, palm, or other portion of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touch pad) is optionally interpreted by a user as a "press click" or "click-down" of a physically actuated button. In some cases, the user will feel a tactile sensation, such as "press click" or "click down", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moved. As another example, movement of the touch-sensitive surface may optionally be interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when the smoothness of the touch-sensitive surface is unchanged. While such interpretation of touches by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touches are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down," "click up," "roughness"), unless stated otherwise, the haptic output generated corresponds to a physical displacement of the device or component thereof that would generate that sensory perception of a typical (or ordinary) user.

It should be understood that the device 100 is merely one example of a portable multifunction device, and that the device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. 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 and/or application specific integrated circuits.

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

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs, such as computer programs (e.g., including instructions), and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

The RF (radio frequency) circuit 108 receives and transmits RF signals, also referred to as electromagnetic signals. RF circuitry 108 converts/converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates via wireless communication with networks such as the internet (also known as the World Wide Web (WWW)), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices. The RF circuitry 108 optionally includes well-known circuitry for detecting a Near Field Communication (NFC) field, such as by a short-range communication radio. Wireless communications optionally use any of a variety of communication standards, protocols, and technologies including, but not limited to, global system for mobile communications (GSM), enhanced Data GSM Environment (EDGE), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), evolution, pure data (EV-DO), HSPA, hspa+, dual cell HSPA (DC-HSPDA), long Term Evolution (LTE), near Field Communications (NFC), wideband code division multiple access (W-CDMA), code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), 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.11 ac), voice over internet protocol (VoIP), wi-MAX, email protocols (e.g., internet Message Access Protocol (IMAP) and/or Post Office Protocol (POP)), messages (e.g., extensible message handling and presence protocol (XMPP), protocols for instant messaging and presence using extended session initiation protocol (sime), messages and presence (IMPS), instant messaging and/or SMS (SMS) protocols, or any other suitable communications protocol not yet developed herein.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data to electrical signals, and transmits the electrical signals to speaker 111. The speaker 111 converts electrical signals into sound waves that are audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to the peripheral interface 118 for processing. The audio data is optionally retrieved from and/or transmitted to the memory 102 and/or the RF circuitry 108 by the peripheral interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in fig. 2). The headset jack provides an interface between the audio circuit 110 and removable audio input/output peripherals such as output-only headphones or a headset having both an output (e.g., a monaural or binaural) and an input (e.g., a microphone).

I/O subsystem 106 couples input/output peripheral devices on device 100, such as touch screen 112 and other input control devices 116, to peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from/transmit electrical signals to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click-type dials, and the like. In some implementations, the input controller 160 is optionally coupled to (or not coupled to) any of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., 208 in fig. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in fig. 2). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with one or more input devices. In some implementations, the one or more input devices include a touch-sensitive surface (e.g., a touch pad as part of a touch-sensitive display). In some implementations, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and/or one or more depth camera sensors 175) such as for tracking gestures (e.g., hand gestures and/or air gestures) of the user as input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. In some embodiments, the air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independent of an input element that is part of the device) and based on a detected movement of a portion of the user's body through the air, including a movement of the user's body relative to an absolute reference (e.g., an angle of the user's arm relative to the ground or a distance of the user's hand relative to the ground), a movement relative to another portion of the user's body (e.g., a movement of the user's hand relative to the user's shoulder, a movement of the user's hand relative to the other hand of the user, and/or a movement of the user's finger relative to the other finger or part of the hand of the user), and/or an absolute movement of a portion of the user's body (e.g., a flick gesture that includes a predetermined amount and/or speed of movement of the hand in a predetermined gesture that includes a predetermined gesture of the hand, or a shake gesture that includes a predetermined speed or amount of rotation of a portion of the user's body).

The quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. patent application 11/322,549 (i.e., U.S. patent 7,657,849) entitled "Unlocking a Device by Performing Gestures on an Unlock Image," filed on even date 12/23, 2005, which is hereby incorporated by reference in its entirety. Long presses of a button (e.g., 206) optionally cause the device 100 to power on or off. The function of the one or more buttons is optionally customizable by the user. Touch screen 112 is used to implement virtual buttons 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 electrical signals from touch screen 112 and/or transmits electrical signals to touch screen 112. Touch screen 112 displays visual output to a user. Visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output optionally corresponds to a user interface object.

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

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, but in other embodiments other display technologies are used. Touch screen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, a projected mutual capacitance sensing technique is used, such as in the case of a sensor from Appl e inc (Cupertino, california)And iPod->Techniques used in the above.

The touch sensitive display in some implementations of touch screen 112 is optionally similar to the multi-touch sensitive touch pad described in the following 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 U.S. patent publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while touch sensitive touchpads do not provide visual output.

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

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some implementations, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to make contact with touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contact and gestures, which may not be as accurate as stylus-based input due to the large contact area of the finger on the touch screen. In some embodiments, the device translates the finger-based coarse input into a precise pointer/cursor position or command for performing the action desired by the user.

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

The apparatus 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

The apparatus 100 optionally further comprises one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 optionally includes a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the 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 image and/or video image acquisition. In some embodiments, the optical sensor is located on the front of the device such that the user's image is optionally acquired for video conferencing while viewing other video conference participants on the touch screen display. In some implementations, the position of the optical sensor 164 may be changed by the user (e.g., by rotating a lens and sensor in the device housing) such that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and/or video image acquisition.

The device 100 optionally further includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to a depth camera controller 169 in the I/O subsystem 106. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of objects (e.g., faces) within the scene from a point of view (e.g., depth camera sensor). In some implementations, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of the image captured by the imaging module 143. In some embodiments, a depth camera sensor is located at the front of the device 100 such that a user image with depth information is optionally acquired for a video conference while the user views other video conference participants on a touch screen display, and a self-photograph with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the back of the device, or at the back and front of the device 100. In some implementations, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating a lens and sensor in the device housing) such that the depth camera sensor 175 is used with a touch screen display for both video conferencing and still image and/or video image acquisition.

The apparatus 100 optionally further comprises one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring force (or pressure) of a contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a surrogate for pressure information) from the environment. In some implementations, at least one contact intensity sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the rear of the device 100, opposite the touch screen display 112 located on the front of the device 100.

The device 100 optionally further includes one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I/O subsystem 106. The proximity sensor 166 optionally performs as described in the following U.S. patent application nos.: 11/241,839, entitled "Proximity Detector In Handheld Device";11/240,788, entitled "Proximity Detector In Handheld Device";11/620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output";11/586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11/638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals," which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor is turned off and the touch screen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a telephone call).

The device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in the I/O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and/or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating means (e.g., means for converting an electrical signal into a tactile output on a device). The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on the device 100 that can be perceived by a user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward/outward of the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the rear of the device 100, opposite the touch screen display 112 located on the front of the device 100.

The device 100 optionally further includes one or more accelerometers 168. Fig. 1A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in the following U.S. patent publication nos.: 20050190059 under the names "acceletation-based Theft Detection System for Portable Electronic Devices" and 20060017692 under the name "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which disclosures are incorporated herein by reference in their entirety. In some implementations, 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. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., longitudinal or lateral) of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A and 3. The device/global internal state 157 includes one or more of the following: an active application state indicating which applications (if any) are currently active; display status, indicating what applications, views, or other information occupy various areas of the touch screen display 112; sensor status, including information obtained from the various sensors of the device and the input control device 116; and location information relating to the device location and/or pose.

Operating system 126 (e.g., darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitates communication between the various hardware components and software components.

The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and/or the external ports 124. External port 124 (e.g., universal Serial Bus (USB), firewire, etc.) is adapted to be coupled directly to other devices or indirectly via a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is in communication withThe 30-pin connector used on the (Apple inc. Trademark) device is the same or similar and/or compatible with a multi-pin (e.g., 30-pin) connector.

The contact/motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the strength of the contact (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or a contact break). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact optionally includes determining a velocity (magnitude), a speed (magnitude and direction), and/or an acceleration (change in magnitude and/or direction) of the point of contact, the movement of the point of contact being represented by a series of contact data. These operations are optionally applied to single point contacts (e.g., single finger contacts) or simultaneous multi-point contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on the touch pad.

In some implementations, the contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether the user has "clicked" on an icon). In some implementations, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by activation thresholds of particular physical actuators and may be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touch screen display hardware, the mouse "click" threshold of the touchpad or touch screen may be set to any of a wide range of predefined thresholds. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once with a system-level click on an "intensity" parameter).

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

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other displays, including means for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attribute) of the displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphic module 132 receives one or more codes for designating graphics to be displayed from an application program or the like, and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to output to the display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by haptic output generator 167 to generate haptic output at one or more locations on device 100 in response to user interaction with device 100.

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

The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as picture/video metadata, and to applications that provide location-based services, such as weather gadgets, local page gadgets, and map/navigation gadgets).

The application 136 optionally includes the following modules (or sets of instructions) or a subset or superset thereof:

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

a telephone module 138;

video conferencing module 139;

email client module 140;

an Instant Messaging (IM) module 141;

a fitness support module 142;

a camera module 143 for still and/or video images;

an image management module 144;

a video player module;

a music player module;

browser module 147;

Calendar module 148;

a gadget module 149, optionally comprising one or more of: weather gadgets 149-1, stock gadgets 149-2, calculator gadget 149-3, alarm gadget 149-4, dictionary gadget 149-5, and other gadgets obtained by the user, and user-created gadgets 149-6;

a gadget creator module 150 for forming a user-created gadget 149-6;

search module 151;

a video and music player module 152 that incorporates the video player module and the music player module;

a note module 153;

map module 154; and/or

An 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, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage an address book or contact list (e.g., in application internal state 192 of contacts module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting the name from the address book; associating a telephone number, email address, physical address, or other information with the name; associating the image with the name; classifying and classifying names; providing a telephone number or email address to initiate and/or facilitate communications through telephone 138, video conferencing module 139, email 140, or IM 141; etc.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contact module 137, modify the entered telephone number, dial the corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephony module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction 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 captured by the camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, instant message module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously inputted characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone-based instant messages or using XMPP, SIMPLE, or IMPS for internet-based instant messages), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant message optionally includes graphics, photographs, audio files, video files, and/or other attachments supported in an MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions for creating a workout (e.g., with time, distance, and/or calorie burn targets); communicate with a fitness sensor (exercise device); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for exercise; and displaying, storing and transmitting the fitness data.

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

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

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

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

In conjunction 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, gadget module 149 is a mini-application (e.g., weather gadget 149-1, stock gadget 149-2, calculator gadget 149-3, alarm gadget 149-4, and dictionary gadget 149-5) or a mini-application created by a user (e.g., user created gadget 149-6) that is optionally downloaded and used by a user. In some embodiments, gadgets include HTML (hypertext markup language) files, CSS (cascading style sheet) files, and JavaScript files. In some embodiments, gadgets include XML (extensible markup language) files and JavaScript files (e.g., yahoo | gadgets).

In conjunction 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, gadget creator module 150 is optionally used by a user to create gadgets (e.g., to transform user-specified portions of a web page into gadgets).

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and playback recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, rendering, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple inc.).

In conjunction with the touch screen 112, the display controller 156, the contact/movement module 130, the graphics module 132, and the text input module 134, the notes module 153 includes executable instructions for creating and managing notes, backlog, and the like according to user instructions.

In conjunction with 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, map module 154 is optionally configured to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to shops and other points of interest at or near a particular location, and other location-based data) according to user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for: allowing a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on a touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online video in one or more file formats such as h.264. In some embodiments, the instant messaging module 141 is used to send links to particular online videos instead of the email client module 140. Additional descriptions of online video applications can be found in U.S. provisional patent application Ser. No. 60/936,562, entitled "Portable Multifunction Device, method, and Graphical User Interface for Playing Online Videos," filed on even 20, 6, 2007, and U.S. patent application Ser. No. 11/968,067, entitled "Portable Multifunction Device, method, and Graphical User Interface for Playing Online Videos," filed on even 31, 12, 2007, the contents of both of which are hereby incorporated by reference in their entirety.

Each of the modules and applications described above corresponds to a set of executable instructions for performing one or more of the functions described above, as well as the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented in a separate software program, such as a computer program (e.g., including instructions), process, or module, and thus the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, the video player module is optionally combined with the 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 modules and data structures described above. Further, memory 102 optionally stores additional modules and data structures not described above.

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

A predefined set of functions performed solely by the touch screen and/or touch pad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, a main desktop menu, or a root menu. In such implementations, a touch pad is used to implement a "menu button". In some other embodiments, the menu buttons are physical push buttons or other physical input control devices, rather than touch pads.

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

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

In some implementations, the application internal state 192 includes additional information, such as one or more of the following: restoration information to be used when the application 136-1 resumes execution, user interface state information indicating that the information is being displayed or ready for display by the application 136-1, a state queue for enabling the user to return to a previous state or view of the application 136-1, and a repeat/undo queue of previous actions taken by the user.

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

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

In some implementations, the event classifier 170 also includes a hit view determination module 172 and/or an active event identifier determination module 173.

When the touch sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where within one or more views a sub-event has occurred. The view is made up 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 view (of the respective application) in which the touch is detected optionally corresponds to a level of programming within the application's programming or view hierarchy. For example, the lowest horizontal view in which a touch is detected is optionally referred to as a hit view, and the set of events that are recognized as correct inputs is optionally determined based at least in part on the hit view of the initial touch that begins a touch-based gesture.

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

The activity event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the active event identifier determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the activity event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively engaged views, and thus determines that all actively engaged views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely localized to an area associated with one particular view, the higher view in the hierarchy will remain the actively engaged view.

The event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In embodiments that include an active event recognizer determination module 173, the event dispatcher module 174 delivers event information to the event recognizers determined by the active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue that is retrieved by the corresponding event receiver 182.

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, the application 136-1 includes an event classifier 170. In yet another embodiment, the event classifier 170 is a stand-alone module or part of another module stored in the memory 102, such as the 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 includes instructions for processing touch events that occur within a respective view of the user interface of the application. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module that is a higher level object from which methods and other properties are inherited, such as the user interface toolkit or application 136-1. In some implementations, the respective event handlers 190 include one or more of the following: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of application views 191 include one or more corresponding event handlers 190. Additionally, in some implementations, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in a respective application view 191.

The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events based on the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 further includes at least a subset of metadata 183 and event transfer instructions 188 (which optionally include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about sub-events such as touches or touch movements. The event information also includes additional information, such as the location of the sub-event, according to the sub-event. When a sub-event relates to movement of a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes rotation of the device from one orientation to another orientation (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about a current orientation of the device (also referred to as a device pose).

The event comparator 184 compares the event information with predefined event or sub-event definitions and determines an event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some implementations, sub-events in an event (e.g., 187-1 and/or 187-2) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double click on the displayed object. For example, a double click includes a first touch on the displayed object for a predetermined length of time (touch start), a first lift-off on the displayed object for a predetermined length of time (touch end), a second touch on the displayed object for a predetermined length of time (touch start), and a second lift-off on the displayed object for a predetermined length of time (touch end). In another example, the definition of event 2 (187-2) is a drag on the displayed object. For example, dragging includes touching (or contacting) on the displayed object for a predetermined period of time, movement of the touch on the touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some implementations, the event definitions 186 include definitions of events for respective user interface objects. In some implementations, the 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 that displays three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, 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 an event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the respective event (187) further includes a delay action that delays delivery of the event information until it has been determined that the sequence of sub-events does or does not correspond to an event type of the event recognizer.

When the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event impossible, event failed, or event end state after which subsequent sub-events of the touch-based gesture are ignored. In this case, the other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, the respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to the actively engaged event recognizer. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how event recognizers interact or are able to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some implementations, the respective event identifier 180 delivers event information associated with the event to the event handler 190. The activate event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a marker associated with the recognized event, and event handler 190 associated with the marker retrieves the marker and performs a predefined process.

In some implementations, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about the sub-event without activating the event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively engaged view. Event handlers associated with the sequence of sub-events or with the actively engaged views receive the event information and perform a predetermined process.

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

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

It should be appreciated that the above discussion regarding event handling of user touches on a touch sensitive display also applies to other forms of user inputs that utilize an input device to operate the multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; contact movement on the touchpad, such as tap, drag, scroll, etc.; inputting by a touch pen; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof is optionally used as input corresponding to sub-events defining the event to be distinguished.

Fig. 2 illustrates a portable multifunction device 100 with a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within a User Interface (UI) 200. In this and other embodiments described below, a user can select one or more of these graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics will occur when a user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up and/or down), and/or scrolling of a finger that has been in contact with the device 100 (right to left, left to right, up and/or down). In some implementations or in some cases, inadvertent contact with the graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over an application icon optionally does not select the corresponding application.

The device 100 optionally also includes one or more physical buttons, such as a "home desktop" or menu button 204. As previously described, menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on device 100. Alternatively, in some embodiments, the menu buttons are implemented as soft keys in a GUI displayed on touch screen 112.

In some embodiments, the device 100 includes a touch screen 112, menu buttons 204, a press button 206 for powering the device on/off and for locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and a docking/charging external port 124. Pressing button 206 is optionally used to turn on/off the device by pressing the button and holding the button in the pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input through the microphone 113 for activating or deactivating certain functions. The device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on the touch screen 112, and/or one or more haptic output generators 167 for generating haptic outputs for a user of the device 100.

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

Each of the above elements in fig. 3 is optionally stored in one or more of the previously mentioned memory devices. Each of the above-described modules corresponds to a set of instructions for performing the above-described functions. The above-described modules or computer programs (e.g., sets of instructions or instructions) need not be implemented in a separate software program (such as a computer program (e.g., instructions), process or module, and thus the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Further, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces optionally implemented on, for example, portable multifunction device 100.

Fig. 4A illustrates an exemplary user interface of an application menu on the portable multifunction device 100 in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

time 404;

bluetooth indicator 405;

battery status indicator 406;

tray 408 with icons for commonly used applications, such as:

an icon 416 labeled "phone" of the o phone module 138, the icon 416 optionally including an indicator 414 of the number of missed calls or voice mails;

an icon 418 labeled "mail" of the o email client module 140, the icon 418 optionally including an indicator 410 of the number of unread emails;

icon 420 labeled "browser" of the omicron browser module 147; and

an icon 422 labeled "iPod" of the omicron video and music player module 152 (also known as iPod (trademark of Apple inc.) module 152); and

icons of other applications, such as:

icon 424 labeled "message" of omicron IM module 141;

icon 426 labeled "calendar" of calendar module 148;

icon 428 labeled "photo" of image management module 144;

an icon 430 labeled "camera" of the omicron camera module 143;

icon 432 labeled "online video" of online video module 155;

Icon 434 labeled "stock market" for the o stock market gadget 149-2;

icon 436 labeled "map" of the omicron map module 154;

icon 438 labeled "weather" for the o weather gadget 149-1;

icon 440 labeled "clock" for the o alarm clock gadget 149-4;

icon 442 labeled "fitness support" of omicron fitness support module 142;

icon 444 labeled "note" of the omicron note module 153; and

an icon 446 labeled "set" for a set application or module that provides access to the settings of device 100 and its various applications 136.

It should be noted that the iconic labels shown in fig. 4A are merely exemplary. For example, the icon 422 of the 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 of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

Fig. 4B illustrates an exemplary user interface on a device (e.g., device 300 of fig. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of fig. 3) separate from a display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of the contact on the touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of the device 300.

While some of the examples below will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments the device detects inputs on a touch sensitive surface separate from the display, as shown in fig. 4B. In some implementations, the touch-sensitive surface (e.g., 451 in fig. 4B) has a primary axis (e.g., 452 in fig. 4B) that corresponds to the primary axis (e.g., 453 in fig. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at a location corresponding to a respective location on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in fig. 4B). In this way, when the touch-sensitive surface (e.g., 451 in FIG. 4B) is separated from the display (e.g., 450 in FIG. 4B) of the multifunction device, user inputs (e.g., contacts 460 and 462 and movement thereof) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be appreciated that similar approaches are optionally used for other user interfaces described herein.

Additionally, while the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger flick gestures, finger swipe gestures), it should be understood that in some embodiments one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced with a mouse click (e.g., rather than a contact), followed by movement of the cursor along the path of the swipe (e.g., rather than movement of the contact). As another example, a flick gesture is optionally replaced by a mouse click (e.g., instead of detection of contact, followed by ceasing to detect contact) when the cursor is over the position of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be appreciated that multiple computer mice are optionally used simultaneously, or that the mice and finger contacts are optionally used simultaneously.

Fig. 5A illustrates an exemplary personal electronic device 500. The 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., fig. 1A-4B). In some implementations, the device 500 has a touch sensitive display 504, hereinafter referred to as a touch screen 504. In addition to or in lieu of touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some implementations, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of the touch screen 504 (or touch sensitive surface) may provide output data representative of the intensity of the touch. The user interface of the 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 the device 500.

Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: international patent application sequence PCT/US2013/040061, filed 5/8 a 2013, entitled "Device, method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", issued as WIPO patent publication No. WO/2013/169849; and international patent application serial number PCT/US2013/069483, filed 11/2013, entitled "Device, method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", published as WIPO patent publication No. WO/2014/105276, each of which is hereby incorporated by reference in its entirety.

In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) may be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow for attachment of the device 500 with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, leash, shoe, purse, backpack, or the like. These attachment mechanisms allow the user to wear the device 500.

Fig. 5B depicts an exemplary personal electronic device 500. In some embodiments, the apparatus 500 may include some or all of the components described with reference to fig. 1A, 1B, and 3. The device 500 has a bus 512 that operatively couples an I/O section 514 with one or more computer processors 516 and memory 518. The I/O portion 514 may be connected to a display 504, which may have a touch sensitive component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I/O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, bluetooth, near Field Communication (NFC), cellular, and/or other wireless communication technologies. The device 500 may include input mechanisms 506 and/or 508. For example, the input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

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

The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by the one or more computer processors 516, may, for example, cause the computer processors to perform the techniques described below, including processes 700 and 900 (fig. 7 and 9). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, and device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer readable storage medium may include, but is not limited to, magnetic storage devices, optical storage devices, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or blu-ray technology, and persistent solid state memories such as flash memory, solid state drives, etc. The personal electronic device 500 is not limited to the components and configuration of fig. 5B, but may include other components or additional components in a variety of configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and/or 500 (fig. 1A, 3, and 5A-5B). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

As used herein, the term "focus selector" refers to an input element for indicating the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor detects an input (e.g., presses an input) on a touch-sensitive surface (e.g., touch pad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) above a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations including a 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, the contact detected on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by a contact) is detected on the touch screen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without a corresponding movement of the cursor or movement of contact on the touch screen display (e.g., by moving the focus from one button to another using a tab key or arrow key); in these implementations, the focus selector moves according to movement of the focus between different areas of the user interface. Regardless of the particular form that the focus selector takes, the focus selector is typically controlled by the user in order to deliver a user interface element (or contact on the touch screen display) that is interactive with the user of the user interface (e.g., by indicating to the device the element with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (rather than other user interface elements shown on the device display).

As used in the specification and claims, the term "characteristic intensity" of a contact refers to the characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired during a predetermined period of time (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detection of contact, before or after detection of lift-off of contact, before or after detection of start of movement of contact, before or after detection of end of contact, and/or before or after detection of decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: maximum value of intensity of contact, average value of intensity of contact, value at first 10% of intensity of contact, half maximum value of intensity of contact, 90% maximum value of intensity of contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, contact of the feature strength that does not exceed the first threshold results in a first operation, contact of the feature strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and contact of the feature strength that exceeds the second threshold results in a third operation. In some implementations, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform or forgo performing the respective operations) rather than for determining whether to perform the first or second operations.

Attention is now directed to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

Fig. 6A-6N illustrate exemplary user interfaces for displaying laboratory types based on their designated status according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in fig. 7.

Fig. 6A shows a computer 600 displaying a summary user interface 608a via a display 602. In some embodiments, computer system 600 optionally includes one or more features of device 100, device 300, or device 500. In some embodiments, computer system 600 is a tablet, phone, laptop, desktop, camera, or the like. In some embodiments, the inputs described below may be optionally replaced with alternative inputs, such as swipe inputs and/or long press inputs.

Summary user interface 608a includes relevant information regarding health related data, where the content of summary user interface 608a depends on the specified status of the various laboratory types. The summary user interface shown in fig. 6A does not include any laboratory affordances or information related to a particular laboratory, and in particular does not include laboratory affordances having graphical indications that compare two values corresponding to a particular laboratory type. In contrast, in FIG. 6M, described below, the summary user interface 608b displayed by computer system 600 includes a graphical indicator corresponding to the difference between two laboratory values of the locked laboratory type. Summary user interface 608a includes a laboratory update user interface object 610a. The laboratory update user interface object 610a has an update user interface object 610a1 that shows an update to the laboratory. The user interface object may include visual and/or textual indicators that are available for laboratory data updates. The laboratory update user interface object 610a also includes an update description 610a2 regarding the contents of laboratory data updates.

The summary user interface 608a also includes a health record update section 612 that provides information that health record updates are available. The summary user interface 608a may also include measurements (e.g., measurement 614a1 and measurement 614a 2) describing different measurements of the health related information. Summary user interface 608a also includes a summary affordance 616 that, when not displayed, causes computer system 600 to display a summary user interface (e.g., 608 a) when selected. At fig. 6A, summary affordances 616 are displayed in a visually different appearance (e.g., bold, outline, highlighting) to indicate that the summary user interface is currently being displayed and/or that the summary affordances 616 are currently selected and/or in an active state. Summary user interface 608a also includes a sharing affordance 617 that, when selected, causes computer system 600 to display a user interface for sharing and/or transmitting information related to health data to other users. The summary user interface 608a also includes a view affordance 618 that, when selected, causes the computer system 600 to display a user interface for viewing health-related information. The summary user interface 608a also includes an avatar 604 that includes graphical indicators corresponding to users and/or user accounts associated with the computer system 600.

At fig. 6A, computer system 600 receives input 650a (e.g., tap input) on laboratory update user interface object 610 a. In response to receiving input 650a, computer system 600 displays laboratory user interface 620a, as shown in fig. 6B.

Fig. 6B shows computer system 600 displaying laboratory user interface 620a. The laboratory user interface 620a includes laboratory affordances corresponding to various laboratory types. The laboratory user interface 620a also includes an edit affordance 628 that, when selected, causes the computer system 600 to display a user interface for editing aspects of laboratory data included in the laboratory user interface 620a (e.g., selecting which laboratory types are locked to the top of the section (e.g., specified via user input)), as shown below in fig. 6D. The laboratory user interface 620a includes a return affordance 624 that, when selected, causes the computer system 600 to display a previously displayed user interface screen (e.g., summary user interface 608 a). The laboratory user interface 620a also includes a search bar 622 that, when selected, causes the computer 600 to display options for searching among the laboratory data in the displayable laboratory user interface 620a (e.g., by inputting letters corresponding to the laboratory data via a touch-pad, via voice input received via a microphone).

The laboratory user interface 620a also includes a latest ordering option 630a that, when selected, causes the computer system 600 to display laboratory data included in the laboratory user interface 620a based at least in part on the chronology information (e.g., the most recently updated laboratory type is at the top). At fig. 6B, the latest sort option 630a is displayed in a visually different appearance (e.g., bold, outline, highlighting) to indicate that the latest sort option 630a is currently selected. Laboratory user interface 620a also includes an alphabetical option 632a, which when selected, causes computer system 600 to display laboratory data included in laboratory user interface 620a based at least in part on the alphabetical information (e.g., the laboratory data is alphabetically ordered). At fig. 6B, alphabetical order option 632a is displayed with an appearance that does not include a visual distinction (e.g., a visual appearance that is not bolded, outlined, or highlighted) indicating that alphabetical order option 632a was selected to indicate that alphabetical order option 632a is not currently selected.

The laboratory user interface 620a also includes a lock laboratory prompt 634 that includes a lock description 634a that may be locked (e.g., specified via user input) with respect to a laboratory type corresponding to the laboratory affordance included in the laboratory user interface 620a, and a dismissal affordance 634b that, when selected, causes the computer system 600 to cease displaying (e.g., forgo displaying) the lock laboratory prompt 634.

The laboratory user interface 620a also includes a time range indicator 636 that includes visual and/or textual indicators that display laboratory data below the time range indicator 636 corresponding to a particular time range (e.g., last 7 days, last 30 days). Laboratory user interface 620a also includes an affordance corresponding to laboratory results, as described below.

The laboratory user interface 620a includes a laboratory affordance 638a that, when selected, causes the computer system 600 to display a corresponding laboratory user interface. The laboratory affordances 638a include laboratory types 638a1 that include visual and/or textual indicators corresponding to laboratory types of the laboratory affordances 638a (e.g., physiological characteristics measured by the corresponding laboratory). The laboratory affordance 638a also includes a value 638a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to the laboratory affordance 638 a. The laboratory affordance 638a also includes a date 638a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

The laboratory user interface 620a also includes a laboratory affordance 640a that, when selected, causes the computer system 600 to display a corresponding laboratory user interface. Laboratory affordances 640a include laboratory types 640a1 that include visual and/or textual indicators corresponding to laboratory types of laboratory affordances 640a (e.g., physiological characteristics measured by the corresponding laboratory). Laboratory affordance 640a also includes a value 640a2 that corresponds to the laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 640 a. Laboratory affordance 640a also includes a date 640a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated. Laboratory affordance 640a also includes a range 640a4 that includes a graphical indicator of a range of possible values for the most recent laboratory result corresponding to laboratory affordance 640a relative to the corresponding laboratory type (e.g., the most recent laboratory result compared to the full range of possible results, the most recent laboratory result compared to the range of healthy values).

The laboratory user interface 620a also includes a laboratory affordance 642a that, when selected, causes the computer system 600 to display a corresponding laboratory user interface. Laboratory affordances 642a include laboratory types 642a1 that include visual and/or textual indicators corresponding to laboratory types of laboratory affordances 642a (e.g., physiological characteristics measured by the corresponding laboratory). Laboratory affordance 642a also includes a value 642a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 642 a. Laboratory affordance 642a also includes a date 642a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

At fig. 6B, computer system 600 detects input 650B (e.g., tap input) on alphabetic option 632 a. In response to receiving input 650b, computer system 600 displays laboratory user interface 620b, as shown in fig. 6C.

Fig. 6C shows computer system 600 displaying laboratory user interface 620b. Laboratory user interface 620b illustrates a laboratory user interface with laboratory results displayed alphabetically (e.g., based on corresponding laboratory types). In some embodiments, the laboratory affordances are displayed according to different ordering orders such that the content is displayed at different locations within the laboratory affordance. For example, fig. 6C shows that dates included in laboratory affordances (e.g., 644a, 640B, 638B, 642B, and 646C) are displayed below corresponding laboratory values, and that these dates are displayed in right-justified fashion within the laboratory affordance in fig. 6B.

Laboratory user interface 620b includes laboratory affordance 644a, which includes laboratory type 644a1 that indicates that laboratory affordance 644a corresponds to "albumin". Laboratory affordance 644a also includes a value 644a2 that corresponds to the laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 644 a. Laboratory affordance 644a also includes a date 644a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

Laboratory user interface 620b also includes laboratory affordance 646a, which includes laboratory type 646a1 indicating that the corresponding laboratory type is "zinc". Laboratory affordance 646a also includes a value 646a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 646 a. Laboratory affordance 646a also includes a date 646a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated. Laboratory affordance 646a also includes a range 646a4 that includes a graphical indicator of a range of possible values for the most recent laboratory result corresponding to laboratory affordance 646a relative to the corresponding laboratory type (e.g., the most recent laboratory result compared to the full range of possible results, the most recent laboratory result compared to the health value range, etc.).

The laboratory user interface 620b further includes: laboratory affordance 640b, which includes content similar to laboratory affordance 640 a; laboratory affordance 638b, which includes content similar to laboratory affordance 638a described above; and a laboratory affordance 642b that includes content similar to laboratory affordance 642a described above.

Laboratory user interface 620b also includes an alphabetical option 632b, which when selected, causes computer system 600 to display laboratory data included in laboratory user interface 620b based at least in part on the alphabetical information. Laboratory user interface 620b also includes a most recent ordering option 630b that, when selected, causes computer system 600 to display laboratory data included in laboratory user interface 620b based at least in part on the chronology information (e.g., the most recently updated laboratory type is at the top). The laboratory user interface also includes a laboratory affordance 648 that, when selected, causes the computer system 600 to display additional laboratory data that is not currently included (e.g., displayed) in the laboratory user interface 620 b.

The laboratory user interface 620b also includes an edit affordance 628 that, when selected, causes the computer system 600 to display a user interface for editing aspects of laboratory data included in the laboratory user interface 620b, as shown in fig. 6D. In laboratory user interface 620b, computer system 600 receives various user inputs (650 c, 660a, 650 d) corresponding to requests to initiate a process for locking a laboratory (e.g., designating a laboratory via user input).

At fig. 6C, computer system 600 receives input 650C (e.g., tap input) on edit affordance 628. In response to receiving input 650c, computer system 600 displays laboratory user interface 620c, as shown in fig. 6D. At fig. 6C, the computer system also receives an input 660a (e.g., swipe input) on laboratory affordance 644a, and in response, displays laboratory user interface 620d, as shown in fig. 6E. At fig. 6C, computer system 600 also receives a long press input 650d on laboratory affordance 642b and, in response, displays an option for locking the "iron" laboratory type, as shown in fig. 6F below.

At fig. 6D, computer system 600 displays a laboratory user interface 620c that includes options for locking the laboratory type. Selecting the lock icon causes the corresponding laboratory result to be locked (e.g., via user input designation). For example, at fig. 6D, computer system 600 receives input 650e (e.g., tap input) on lock icon 640c5 included in laboratory affordance 640a, and in response to receiving input 650e, computer system 600 specifies (e.g., locks) the laboratory type (e.g., "creatinine") corresponding to laboratory affordance 640c, as shown below in fig. 6G.

The laboratory user interface 620c includes a laboratory affordance 644b that includes content similar to the laboratory affordance 644a, and that further includes a lock icon 644b4 for locking a laboratory type corresponding to the laboratory affordance 644 b. The laboratory user interface 620c also includes a laboratory affordance 640c that includes content similar to the laboratory affordance 640a, as described above, and that also includes a lock icon 640c4 for locking the laboratory type corresponding to the laboratory affordance 640 c. The laboratory user interface 620c also includes a laboratory affordance 638c, which includes content similar to laboratory affordance 638a, as described above, and which also includes a lock icon 638c4 for locking the laboratory type corresponding to laboratory affordance 638 c. The laboratory user interface 620c also includes a laboratory affordance 642c that includes content similar to the laboratory affordance 642a, but at fig. 6D it also includes a lock icon 642c4 for locking the laboratory type corresponding to the laboratory affordance 642 c. Laboratory user interface 620c also includes a laboratory affordance 646b that includes content similar to laboratory affordance 646a, but at fig. 6D it also includes a lock icon 646b5 for locking the laboratory type corresponding to laboratory affordance 646 b.

At fig. 6E, computer system 600 displays a laboratory user interface 620d that includes an option to lock the "albumin" laboratory type in response to receiving swipe input 660a on laboratory affordance 644a, as shown above in fig. 6C. The laboratory user interface 620d includes a laboratory affordance 644c that includes content similar to the laboratory affordance 644a, and that further includes a laboratory affordance 644c having a lock option 644c4 that, when selected, specifies (e.g., locks) a laboratory type (e.g., "albumin") corresponding to the laboratory affordance 644 c. In some embodiments, updating the laboratory affordance 644c in response to receiving the input 660a includes displaying an animation, wherein the laboratory affordance 644c slides over the animation to make room for the lock option 644c 4. At FIG. 6E, computer system 600 receives input 650f (e.g., tap input) on lock option 644c 4. In response to receiving input 650f, computer system 600 specifies (e.g., locks) a laboratory type (e.g., "albumin") corresponding to laboratory affordance 644c, as shown in fig. 6G below.

The laboratory user interface 620d also includes a laboratory affordance 640d that includes content similar to the laboratory affordance 640a described above. The laboratory user interface 620d also includes a laboratory affordance 638d that includes content similar to the laboratory affordance 638a described above. The laboratory user interface 620d also includes a laboratory affordance 642d that includes content similar to the laboratory affordance 642a described above. The laboratory user interface 620d also includes a laboratory affordance 646c that includes content similar to the laboratory affordance 646a described above.

At fig. 6F, in response to receiving input 650d, computer system 600 displays laboratory user interface 620e, as shown in fig. 6C above. The laboratory user interface 620e is an updated version of the laboratory user interface 620c, wherein in response to receiving the input 650d, the computer system displays the laboratory user interface 620e, wherein laboratory affordances other than the selected laboratory affordance are grayed out (e.g., 644d, 640e, 638e, 646 d). However, the selected laboratory affordance (e.g., 642 e) is displayed without graying, and a lock laboratory affordance 654 is displayed alongside it to indicate that the corresponding laboratory type (e.g., "iron") can be locked via input on the lock laboratory affordance 654. In fig. 6F, computer system 600 detects input 650g on lock lab affordance 654 and, in response, locks the "iron" lab type.

The laboratory user interface 620e includes a laboratory affordance 644d, the contents of which are similar to the laboratory affordance 644a described above. The laboratory user interface 620e also includes a laboratory affordance 640e that includes content similar to the laboratory affordance 640a described above. The laboratory user interface 620e also includes a laboratory affordance 638e that includes content similar to the laboratory affordance 638a described above. The laboratory user interface 620e also includes a laboratory affordance 642e that includes content similar to the laboratory affordance 642a described above. Laboratory user interface 620e also includes laboratory affordance 646d, which includes content similar to laboratory affordance 646 a.

Fig. 6G shows computer system 600 displaying laboratory user interface 620F, where both the laboratory type corresponding to "albumin" and the laboratory results corresponding to "creatinine" have been locked (e.g., via user input designations as in fig. 6D, 6E, and/or 6F), as shown by laboratory affordances 644E and 640F. The laboratory user interface 620f includes a "lock" identifier 656 that includes visual and/or textual indications in the laboratory user interface 620f that display a portion of the locked laboratory. The laboratory user interface 620f also includes a "your laboratory" indicator 652 that includes visual and/or textual indications in the laboratory user interface 620f that display a portion of the unlocked laboratory.

The laboratory user interface 620f is a user interface for editing a laboratory type of lock state included in the laboratory user interface 620 f. Laboratory affordances corresponding to the locked laboratory type are displayed with affordances of the unlocked laboratory type, while laboratory affordances corresponding to the unlocked laboratory type are displayed with affordances of the locked laboratory type. The laboratory user interface 620f includes a laboratory affordance 644e that includes content similar to laboratory affordance 644a, and that further includes an unlock icon 644e4 that, when selected, causes the laboratory type corresponding to laboratory affordance 644e to be unlocked (e.g., not specified). The laboratory user interface 620f also includes a laboratory affordance 640f that includes content similar to the laboratory affordance 640a, and that further includes an unlock icon 640f5 that, when selected, causes the laboratory type corresponding to the laboratory affordance 640f to be unlocked (e.g., not specified). The laboratory user interface 620f also includes a laboratory affordance 638f that includes content similar to the laboratory affordance 638c described above. The laboratory user interface 620f also includes a laboratory affordance 642f that includes content similar to the laboratory affordance 642c described above. The laboratory user interface 620f also includes a laboratory affordance 646e that includes content similar to the laboratory affordance 646b described above.

The laboratory user interface 620f also includes a completion affordance 629 that, when selected, causes the computer system 600 to exit the user interface for editing aspects of laboratory data. In fig. 6G, computer system 600 receives input 650h (e.g., tap input) on completion affordance 629. In response to receiving input 650H, computer system 600 displays laboratory user interface 620g, as shown in fig. 6H.

Fig. 6H shows computer system 600 displaying laboratory user interface 620g. Laboratory user interface 620g shows a user interface that includes some locked laboratory types and some unlocked laboratory types. For example, a laboratory affordance 640g corresponds to a locked "creatinine" laboratory type, and a laboratory affordance 644f corresponds to a locked "albumin" laboratory type, while a laboratory affordance 638g corresponds to an unlocked "HbA1c" laboratory type, a laboratory affordance 642g corresponds to an unlocked "iron" laboratory type, and a laboratory affordance 646f corresponds to an unlocked "zinc" laboratory type.

Laboratory user interface 620g includes laboratory affordance 644f, which includes content similar to laboratory affordance 644a described above. The laboratory user interface 620g also includes a laboratory affordance 640g that includes content similar to the laboratory affordance 640a described above. The laboratory user interface 620g also includes a laboratory affordance 638g that includes content similar to the laboratory affordance 638a described above. The laboratory user interface 620g also includes a laboratory affordance 642g that includes content similar to the laboratory affordance 642a described above. Laboratory user interface 620g also includes laboratory affordance 646f, which includes content similar to laboratory affordance 646a described above.

At fig. 6H, alphabetical order option 632a is displayed with an appearance that does not include a visual distinction (e.g., a visual appearance that is not bolded, outlined, or highlighted) indicating that alphabetical order option 632a was selected to indicate that alphabetical order option 632a is not currently selected. Notably, the locked and unlocked laboratory types are ordered separately. For example, while date 638g3 indicates that the "HbA1c" laboratory type was updated on day 9 months 1, which date is more recent than date 640g3 indicated for the "creatinine" laboratory type, laboratory user interactive graphical user interface 640g corresponding to laboratory type 638g1 ("creatinine") is displayed at a higher location on top of laboratory user interface 620g than laboratory affordance 638g corresponding to laboratory type 640g1 ("HbA 1 c"). Thus, the ranking criteria are based in part on the chronology information and are based at least in part on the locking status (e.g., designated status) of the laboratory type.

In fig. 6H, computer system 600 receives input 650i on laboratory affordance 644f (e.g., tap input), input 650j on laboratory affordance 640g, which causes computer system 600 to display an "albumin" laboratory user interface as shown in fig. 6K below. At fig. 6H, computer system 600 also receives input 650j on laboratory affordance 640g, which causes computer system 600 to display a "creatinine" laboratory user interface as shown in fig. 6I below. In fig. 6H, computer system 600 also receives an input 660b (e.g., swipe input) on laboratory affordance 640g, which causes computer system 600 to display an unlock option for the "creatinine" laboratory type as shown in fig. 6J below. In fig. 6H, computer system 600 also receives an input 650k (e.g., tap input) on laboratory affordance 642g, which causes computer system 600 to display a "iron" laboratory user interface 658c as shown in fig. 6L below.

At fig. 6I, in response to receiving input 650j, computer system 600 displays laboratory user interface 658a. Laboratory user interface 658a is a user interface for displaying more detailed information about the laboratory type corresponding to the selected laboratory affordance (e.g., "creatinine"). Fig. 6I illustrates a user interface including laboratory data and/or results corresponding to a selected laboratory type (e.g., "creatinine"). Laboratory user interface 658a includes a return affordance 662 that, when selected, causes computer system 600 to display a previous user interface (e.g., laboratory user interface 620 g) that was displayed prior to displaying laboratory user interface 658a. Laboratory user interface 658a also includes a laboratory type 664a that indicates the laboratory type (e.g., "creatinine") to which laboratory user interface 658a corresponds. The laboratory user interface 658a also includes chart data 666a that includes graphs and/or charts corresponding to laboratory results corresponding to laboratory types 664 a. The laboratory user interface 658a also includes education 668a regarding laboratory type 664a (e.g., for obtaining common causes of a laboratory associated with laboratory type 664a, physiological functions associated with laboratory type 664 a).

The laboratory user interface 658a also includes an incremental highlighting 670a that includes information related to differences between newer laboratory results and previous laboratory results. The incremental highlighting 670a includes a laboratory type 670a1 that includes visual and/or textual indications of the laboratory type being compared, and an assessment 670a2 that includes visual and/or textual indications of differences between newer laboratory results of the indicated laboratory type and older laboratory results of the indicated laboratory type. The incremental highlighting 670a also includes a graphical indicator 670a3 that includes a graphical representation of the relative relationship between the newer laboratory result of the indicated laboratory type and the previous laboratory result of the indicated laboratory type (e.g., an up arrow if the newer laboratory result is higher than the older laboratory result, a horizontal line if the newer laboratory result is the same as the older laboratory result, and a down arrow if the newer laboratory result is lower than the older laboratory result). The delta highlighting 670a also includes a range 670a4 that provides a graphical indication of older laboratory results relative to a range of possible laboratory result values for the corresponding laboratory type, and a range 670a5 that includes a graphical indication of newer laboratory results relative to a range of possible laboratory result values for the corresponding laboratory type.

Laboratory user interface 658a also includes an unlocked affordance 672a that, when selected, causes the laboratory type indicated by laboratory type 664a to be unlocked by user input (e.g., unlocked; no longer specified by user input). Laboratory user interface 658a also includes a record indicator 674a that includes visual and/or textual indications of record data corresponding to one or more laboratory results corresponding to laboratory type 664 a. The laboratory user interface 658a also includes laboratory affordances 676a that correspond to laboratory results of laboratory types corresponding to laboratory types 664 a. Laboratory user interface 658a also includes displaying all affordances 678a that, when selected, cause computer system 600 to display additional laboratory results corresponding to laboratory type 664a in laboratory user interface 658 a.

At fig. 6J, computer system 600 displays laboratory user interface 620H in response to receiving swipe input 660b as shown in fig. 6H. The laboratory user interface 620h is an updated version of the laboratory user interface 620g, wherein in response to receiving the input 660b, the computer system displays a laboratory affordance 640h having an unlock option 640h 5. In fig. 6J, computer system 600 receives input 650m on unlock option 640h5 and, in response, unlocks the corresponding laboratory type ("creatinine").

Laboratory affordance 640H includes content similar to laboratory affordance 640H, but in fig. 6H, now also includes an unlock option 640H5 that, when selected, de-designates (e.g., unlock) a laboratory type (e.g., laboratory type 640H1, "creatinine") corresponding to laboratory affordance 640H.

The laboratory user interface 620h includes a laboratory affordance 644g that includes content similar to the laboratory affordance 644a described above. The laboratory user interface 620h also includes a laboratory affordance 638h that includes content similar to the laboratory affordance 638a described above.

The laboratory user interface 620h also includes a laboratory affordance 642h that includes content similar to the laboratory affordance 642a described above. The laboratory user interface 620h also includes a laboratory affordance 646g, which includes content similar to the laboratory affordance 646g described above.

In fig. 6K, computer system 600 displays laboratory user interface 658b in response to receiving input 650i in fig. 6H, as described above. Fig. 6K illustrates a user interface including laboratory data and/or results corresponding to a selected laboratory type (e.g., "albumin"). Notably, in contrast to the laboratory user interface 658a, the laboratory user interface 658b does not include a graphical indication of the difference between the two values corresponding to the laboratory type. In some embodiments, if the computer system has access to only one record and/or value corresponding to a laboratory type, the laboratory user interface foregoes displaying a graphical indication of the difference between the two values corresponding to the laboratory type.

Laboratory user interface 658b includes a laboratory type 664b that indicates the laboratory type (e.g., "albumin") to which laboratory user interface 658b corresponds. The laboratory user interface 658b also includes chart data 666b that includes graphs and/or charts corresponding to laboratory results corresponding to laboratory types 664 b. The laboratory user interface 658b also includes education 668b regarding laboratory type 664b (e.g., for obtaining common reasons for a laboratory associated with laboratory type 664b, physiological functions associated with laboratory type 664 b).

Laboratory user interface 658b also includes an unlocked affordance 672b that, when selected, causes the laboratory type indicated by laboratory type 664b to be deselected (e.g., unlocked) by user input. Laboratory user interface 658b also includes a record indicator 674b that includes visual and/or textual indications of record data corresponding to one or more laboratory results corresponding to laboratory type 664 b. The laboratory user interface 658b also includes laboratory affordances 676b that correspond to laboratory results corresponding to laboratory types 664 b. Laboratory user interface 658b also includes displaying all affordances 678b that, when selected, cause computer system 600 to display additional laboratory results corresponding to laboratory types 664b in laboratory user interface 658 b. In fig. 6K, computer system 600 receives input 650n (e.g., tap input) on return affordance 662. In response to receiving input 650n, computer system 600 returns to display laboratory user interface 620g.

In fig. 6L, computer system 600 displays laboratory user interface 658c in response to receiving input 650k in fig. 6H, as described above. Fig. 6L shows a laboratory user interface for an unlocked laboratory type (e.g., "iron"). Laboratory user interface 658c includes laboratory type 664c, which indicates the laboratory type (e.g., "iron") to which laboratory user interface 658c corresponds. The laboratory user interface 658c also includes chart data 666c including graphs and/or charts corresponding to laboratory results corresponding to laboratory types 664 c. The laboratory user interface 658c also includes education 668c regarding laboratory type 664c (e.g., for obtaining common reasons for a laboratory associated with laboratory type 664c, physiological functions associated with laboratory type 664). The laboratory user interface 658c also includes a visual indication 680 that indicates that information of the laboratory type 664c can be locked.

The laboratory user interface 658c also includes an incremental highlighting 670b that includes information related to differences between newer laboratory results and previous laboratory results. Notably, in contrast to the delta highlighting 670b, the delta highlighting 670a is not included in the summary user interface 608b shown in FIG. 6M below. In some implementations, the incremental highlighting 670b is not included in the summary user interface 608b, at least in part because the laboratory type (e.g., "iron") corresponding to the incremental highlighting 670b is unlocked.

The incremental highlighting 670b includes a laboratory type 670b1 that includes visual and/or textual indications of the laboratory type being compared, and an assessment 670b2 that includes visual and/or textual indications of differences between newer laboratory results of the indicated laboratory type and older laboratory results of the indicated laboratory type. The incremental highlighting 670b also includes a graphical indicator 670b3 that includes a graphical representation of the relative relationship between the newer laboratory result of the indicated laboratory type and the previous laboratory result of the indicated laboratory type. The delta highlighting 670b also includes a range 670b4 that provides a graphical indication of older laboratory results relative to a range of possible laboratory result values for the corresponding laboratory type, and a range 670b5 that includes a graphical indication of newer laboratory results relative to a range of possible laboratory result values for the corresponding laboratory type.

Laboratory user interface 658c also includes a lock affordance 682 that, when selected, causes the laboratory type indicated by laboratory type 664c to be specified by user input (e.g., locked). Laboratory user interface 658c also includes a record indicator 674c that includes visual and/or textual indications of record data corresponding to one or more laboratory results corresponding to laboratory type 664 c. The laboratory user interface 658c also includes laboratory affordances 676c that correspond to laboratory results corresponding to laboratory types 664 c. Laboratory user interface 658c also includes displaying all affordances 678c that, when selected, cause computer system 600 to display additional laboratory results corresponding to laboratory type 664c in laboratory user interface 658 c. At fig. 6L, computer system 600 receives input 650o (e.g., tap input) and returns in response to display laboratory user interface 620g.

In FIG. 6M, computer system 600 displays summary user interface 608b in response to receiving input 650l on return affordance 624 as shown in FIG. 6J, as described above. In summary user interface 608, the laboratory type corresponding to "creatinine" and the laboratory type corresponding to "albumin" are locked (e.g., specified via user input), as shown in fig. 6J. At fig. 6M, in accordance with a determination that the laboratory type corresponding to "creatinine" is locked and computer system 600 has data available to display an incremental highlighting for the "creatinine" laboratory type, computer system 600 includes incremental highlighting 670a in summary user interface 608 b. Notably, summary user interface 608b does not include an incremental highlighting of the laboratory type corresponding to "albumin" because, as shown in fig. 6K, the computer system does not have an incremental highlighting available for the laboratory type corresponding to "albumin" (e.g., does not include an incremental highlighting in a laboratory user interface corresponding to "albumin" laboratory type). Further, summary user interface 608b does not include an incremental highlighting 670b corresponding to the laboratory type corresponding to "iron". The lab user interface 658c includes an incremental highlighting (e.g., incremental highlighting 670b as shown in fig. 6L) for the lab type corresponding to the iron, which indicates that the computer system 600 has data available to display the incremental highlighting associated with the "iron" lab type. However, the incremental highlighting 670b is not included in the summary user interface 670b, at least in part, because the laboratory type corresponding to "iron" is not locked (e.g., specified by user input) when the summary user interface 670b is displayed by the computer system 600.

As shown in fig. 6M, summary user interface 608b includes an incremental highlighting 670a that includes a laboratory type 670a1. The summary user interface 608b also includes a summary affordance 616 that, when selected, causes the computer system 600 to display the summary user interface 608b. At fig. 6M, summary affordances 616 are displayed in a visually different appearance (e.g., bold, outline, highlighting) to indicate that summary information is currently being displayed and/or that summary affordances 616 are currently selected. At FIG. 6M, computer system 600 receives input 650p on shared affordance 617.

In FIG. 6N, computer system 600 displays shared user interface 682 in response to receiving input 650p on shared affordance 617 as shown in FIG. 6M, as described above. Fig. 6N illustrates a user interface for sharing laboratory data and/or transmitting laboratory data. The shared user interface 682 includes a cancel affordance 684 that, when selected, causes the computer system to return to the user interface (e.g., summary user interface 608 b) that was displayed prior to displaying the shared user interface 682. The shared user interface also includes a shared laboratory indicator 694 that provides a visual and/or graphical indication that the shared user interface 682 is a user interface for sharing laboratory data and/or results. The shared user interface 682 further includes an all-laboratory affordance 686 that, when selected, selects all laboratory types that are available to the computer 600 when the all-laboratory affordance 686 is selected for sharing and/or transmission. The sharing user interface 682 further includes a lock lab affordance 688 that, when selected, selects the type of laboratory that is locked (e.g., specified via user input) when the lock lab affordance 688 is selected to be shared and/or transmitted.

The sharing user interface 682 also includes individual switches for selecting the laboratory type to share and/or transfer. For example, the sharing user interface includes a laboratory type 690a1 that indicates a first laboratory type ("albumin") for sharing and is displayed alongside a switch 690a2 that, when selected, switches the selection state of the first laboratory type (e.g., from selected to unselected, or from unselected to selected). The sharing user interface also includes a laboratory type 690b1 that indicates a second laboratory type ("calcium ion") for sharing and is displayed next to a switch 690b2 that switches the selection status of the second laboratory type when selected. The sharing user interface also includes a laboratory type 690c1 that indicates a third laboratory type ("creatinine") for sharing and is displayed next to a toggle switch 690c2 that toggles the selection status of the third laboratory type when selected. The sharing user interface also includes a laboratory type 690d1 that indicates a fourth laboratory type ("iron") for sharing and is displayed next to a toggle switch 690d2 that toggles the selection state of the fourth laboratory type when selected. The shared user interface 682 further includes a next affordance 692 that, when selected, causes the computer system 600 to proceed to a next step (e.g., display a next user interface) of the process for sharing and/or transmitting laboratory data related to the laboratory type selected when the next affordance 692 was selected.

Fig. 7 is a flow chart illustrating a method for displaying laboratory types based on specified states of the laboratory types using a computer system, according to some embodiments. The method 700 is performed at a computer system (e.g., 100, 300, 500) (e.g., a wearable electronic device (e.g., a smart watch), a smart phone, a desktop computer, a laptop computer, a tablet computer) in communication with a display generating component and one or more input devices (e.g., a display controller, a touch-sensitive display system, a rotatable input mechanism, a touch-sensitive surface). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, method 700 provides an intuitive way for displaying laboratory types based on their designated status. The method reduces the cognitive burden on the user caused by displaying the laboratory type based on the specified state of the laboratory type, thereby creating a more efficient human-machine interface. For battery-powered computing devices, a user is enabled to more quickly and efficiently view laboratory type power savings and increase the time interval between battery charges based on a specified state of the laboratory type.

The computer system (e.g., 600) displays (e.g., 702) a first user interface (e.g., a health summary user interface) (e.g., 608 b) via a display generation component, the user interface including user interactive graphical user interface objects (e.g., affordances) corresponding to a first laboratory type (e.g., type of physiological measurement, type of laboratory result, category of health and/or clinical data (e.g., blood glucose, creatinine, iron, LDL cholesterol)).

In accordance with a determination (e.g., 704) that a first laboratory type has been (e.g., previously) specified (e.g., locked, selected) via user input (e.g., via tap input, press input, and/or swipe input) received via one or more input devices (e.g., 650 e), a user-interactive graphical user interface object corresponding to the first laboratory type (e.g., 670 a) includes a first value (e.g., a numerical value corresponding to a physiological measurement and/or a reading corresponding to a first laboratory data instance) corresponding to the first laboratory type and at least a second value (e.g., a physiological measurement and/or a reading corresponding to a second laboratory data instance different from the first laboratory data instance) corresponding to the first laboratory type (e.g., an increase, decrease, no change indication, increment) graphical indication (e.g., an up arrow (e.g., employing a first color), a down arrow (e.g., employing a second color different from the first color), and/or a horizontal line) (e.g., 670a 3).

In accordance with a determination (e.g., 706) that the first laboratory type has not been specified via user input (e.g., via any previous user input; the first laboratory type is not currently a specified/selected/locked laboratory type) (e.g., 650 e), the computer system (e.g., 600) displays, via the display generation component (e.g., 602), a user interactive graphical user interface object (e.g., 670 a) corresponding to the first laboratory type that there is no graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type (e.g., any graphical indication of a difference between the first value and any other previous value of the first laboratory type). In some embodiments, the first value corresponding to the first laboratory type is a most recent (e.g., most recently performed and/or most recently received by a computer system) value (e.g., physiological measurement and/or reading) corresponding to the first laboratory type. In some embodiments, the second value corresponding to the first laboratory type is updated (e.g., performed more recently and/or received more recently by the computer system) than the first value corresponding to the first laboratory type. In some embodiments, the first value corresponding to the first laboratory type is the same as the second value corresponding to the first laboratory type. In some embodiments, the first value corresponding to the first laboratory type and the second value corresponding to the first laboratory type are different. In some embodiments, the graphical indication comprises an up arrow if the first value is greater than the second value. In some embodiments, if the first value is less than the second value, the graphical indication comprises a down arrow. In some embodiments, the graphical indication comprises a horizontal line if the first value and the second value are equal. The inclusion of a graphical indication of a discrepancy corresponding to two values of a laboratory type in accordance with a determination of whether the laboratory type has been specified via user input enables the graphical indication of the discrepancy to be displayed without requiring the user to manually select the laboratory type to view the graphical indication of the discrepancy. Performing operations when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by displaying graphical indications when the criteria are met), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device. Further, the graphical indication of the display difference provides visual feedback as to whether the value corresponding to the laboratory type is rising or falling. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some embodiments, in accordance with a determination that the first value corresponding to the first laboratory type is greater than the second value corresponding to the first laboratory type, the graphical indication (e.g., 670a 3) has a first appearance. In some embodiments, in accordance with a determination that the first value corresponding to the first laboratory type is less than the second value corresponding to the first laboratory type, the graphical indication has a second appearance that is different from the first appearance. In some embodiments, in accordance with a determination that the first value corresponding to the first laboratory type is equal to the second value corresponding to the first laboratory type, the graphical indication has a third appearance different from the first appearance and the second appearance. In some embodiments, the graphical indication indicates whether the laboratory result is increased, decreased, or remains the same as compared to a previous laboratory result at the same time. In some embodiments, the graphical indication includes an up arrow if the newer laboratory result is greater than the previous laboratory result of the same type. In some embodiments, the graphical indication includes a downward arrow if the newer laboratory result is less than the previous laboratory result. In some embodiments, the graphical indication comprises a straight line if the newer laboratory result is the same as the previous laboratory result. Displaying graphical indications in different appearances provides visual feedback regarding the overall movement trend (e.g., trajectory) of the corresponding laboratory type, depending on whether the determined values are increasing, decreasing, or remain the same. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some embodiments, when performing a process configured for sharing health-related data with a second user account (e.g., a user account associated with an external computer system), the computer system (e.g., 600) displays a shared data selection user interface (e.g., 682), wherein displaying the shared data selection user interface includes: in accordance with a determination that a first laboratory type (e.g., a locked laboratory type) has been specified via user input, the computer system displays a second user-interactive graphical user interface object (e.g., 690a2, 690b2, 690c2, 690d 2) that, when selected, causes data of the first laboratory type to be shared with a second user account upon completion of a process of configuring health-related data for sharing with the second user account. In some embodiments, in accordance with a determination that a first laboratory type (e.g., a locked laboratory type) has not been specified via user input, the computer system forgoes displaying a second user-interactive graphical user interface object that, when selected, causes data of the first laboratory type to be shared with a second user account upon completion of a process of configuring health-related data for sharing with the second user account. In some embodiments, the lock status of the laboratory type determines whether the laboratory type was recommended for sharing during the process for sharing health-related data. In some embodiments, while an unspecified laboratory type is not recommended (e.g., presented as part of a preferred subset of data that may be shared) for sharing, the laboratory type may be specified for sharing via a manual selection process that provides the user with the ability to manually select what health-related data to share. Selectively displaying or not displaying a user-interactive graphical user interface object that, when selected, causes laboratory-type data to be shared with the second user account upon completion of a process of configuring health-related data for sharing with the second user account, in accordance with determining whether the laboratory type has been specified, which provides visual feedback regarding laboratory types that the user is more likely to want to share. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently. In accordance with a determination of whether a laboratory type has been specified, a user-interactive graphical user interface object is selectively displayed or not, which, when selected, causes data of the laboratory type to be shared with the second user account upon completion of the process of configuring health-related data for sharing with the second user account, which enables improved advice as to which laboratory types are possible candidates for sharing without requiring the user to manually select which laboratory types from all of their laboratory types to share. Performing the operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by providing advice about a laboratory), which in turn reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, during the process of configuring the health-related data for sharing with the second user account, the computer system (e.g., 600) displays a laboratory type sharing selection user interactive graphical user interface object (e.g., laboratory type sharing selection affordance) (e.g., 617). In some implementations, the computer system receives input (e.g., 650 p) corresponding to a laboratory type sharing selection user interactive graphical user interface object. In some embodiments, in response to receiving input corresponding to a laboratory type sharing selection user interactive graphical user interface object, the computer system displays a third user interactive graphical user interface object (e.g., 690a 2) that, when selected, modifies whether data of a first laboratory type will be shared with a second user account when a process configured for health-related data sharing with the second user account is complete (e.g., switches status from not sharing to sharing and/or vice versa) and a fourth user interactive graphical user interface object (e.g., 690b 2) that, when selected, modifies whether data of a third laboratory type will be shared with the second user account when a process configured for health-related data sharing with the second user account is complete (e.g., switches status from not sharing to sharing and/or vice versa). Displaying a third user-interactive graphical user interface object that, when selected, modifies whether data of the first laboratory type is to be shared and a fourth user-interactive graphical user interface object that, when selected, modifies whether data of the third laboratory type is to be shared enables users to quickly and easily select the laboratory type they wish to share, thereby reducing the amount of input required to select the appropriate laboratory type to share. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping users select laboratories to share quickly and easily), which in turn reduces power usage and extends battery life of the device by enabling users to use the system more quickly and efficiently.

In some embodiments, prior to displaying the first user interface (e.g., 608 b), the computer system (e.g., 600) displays a second user interface (e.g., laboratory user interface) via a display generation component (e.g., 602) (e.g., 620 a). In some embodiments, the second user interface and the first user interface are the same user interface. In some embodiments, the second user interface and the first user interface are both interfaces of one application (e.g., a health data application) that includes a fifth user interactive graphical user interface object (e.g., affordance) corresponding to a first laboratory type (e.g., type of physiological measurement, type of laboratory result, type of health and/or category of clinical data) (e.g., 640 c) and a sixth user interactive graphical user interface object corresponding to a second laboratory type (e.g., 644 a). In some implementations, the computer system receives (e.g., while the second user interface is displayed) a user input (e.g., tap input) specifying a laboratory type (e.g., 650 e). In some implementations, in accordance with a determination that the fifth user-interactive graphical user interface object meets a set of threshold criteria (e.g., the laboratory has been selected and/or updated at least 3 times within a threshold amount of time (e.g., 3 months)), the computer system displays a visual indication (e.g., a text indication) that can specify the first laboratory type via user input (e.g., 680). Displaying a user interface with a fifth user-interactive graphical user interface object and a sixth user-interactive graphical user interface object that can be specified via user input enables a user to quickly and easily select from a single user interface the laboratory type they wish to lock to thereby reduce the amount of input required to specify the laboratory type. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user quickly and easily specify a particular laboratory type), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, the user input specifying the laboratory type (e.g., 650 e) is selected from the group consisting of: in some embodiments, the second user interface is configured to allow a user to specify a laboratory type using any of the input types in the set via a variety of methods (e.g., multiple types of input types) so that the user can quickly and easily select the laboratory type they wish to lock in a variety of ways, thereby reducing the number of input types required to specify the laboratory type (e.g., a tap on an object that draws a menu, then a second input that selects an option that specifies a laboratory type (e.g., 682)).

In some embodiments, in accordance with a determination that a first laboratory type has been specified (e.g., locked, selected) via user input (e.g., via tap input, press input, and/or swipe input) received via one or more input devices (e.g., 650 e) (e.g., previously), the computer system (e.g., 600) includes a fifth user-interactive graphical user interface object (e.g., 640 g) corresponding to a first laboratory type in a first set of one or more user-interactive graphical user interface objects (e.g., each of a set of objects (e.g., 640g, 644 f) specified via user input) displayed in a first portion of a second user interface (e.g., a portion of the second user interface for the specified (e.g., locked) laboratory) via the display generation component. In some embodiments, in accordance with a determination that the first laboratory type has not been specified via user input (e.g., via any previous user input; the first laboratory type is not currently a specified/selected/locked laboratory type), the computer system displays, via the display generation component, a fifth user-interactive graphical user interface object corresponding to the first laboratory type in a second set of one or more user-interactive graphical user interface objects (e.g., 638g, 642g, 646 f) (e.g., a set of objects each not specified via user input) displayed via the display generation component in a second portion of the second user interface (e.g., a portion of the interface for a laboratory that has not been specified (e.g., locked)). In some embodiments, the first portion of the second user interface and the second portion of the second user interface do not overlap. Displaying user-interactive graphical user interface objects corresponding to a first laboratory type in a first portion of the user interface and displaying user-interactive graphical user interface objects corresponding to a second laboratory type in a second portion of the user interface provides visual feedback as to which laboratory types were specified at a given point in time. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some implementations, the first set of one or more user-interactive graphical user interface objects (e.g., 640g, 644 f) are ordered (e.g., arranged, ranked) in a first portion of the second user interface (e.g., 620 f) according to a first ordering criteria (e.g., alphabetically, chronologically). In some implementations, the second set of one or more user-interactive graphical user interface objects (e.g., 638g, 642g, 646 f) are ordered (e.g., arranged, ranked) in a second portion of the second user interface according to a second ordering criteria (e.g., alphabetically, chronologically, same or different ordering criteria as the first ordering criteria, ordering criteria that are independent of the first ordering criteria). Automatically ordering the user-interactive graphical user interface objects within the respective portions of the second user interface enables an organized user interface with ordered user-interactive graphical user interface objects without requiring the user to manually order or rearrange the user-interactive graphical user interface objects. Performing operations when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by displaying information in a sorted order), which in turn reduces power usage and extends battery life of the device by enabling a user to more quickly and efficiently use the device.

In some embodiments, the second user interface (e.g., 620 b) includes an editing user-interactive graphical user interface object (e.g., 628) that, when selected, initiates a process for modifying a specified state of the first laboratory type (e.g., changing the state from specified to unspecified and/or vice versa). Displaying the editing user-interactive graphical user interface object that, when selected, initiates a process for modifying the specified state of the laboratory type in the second user interface enables a user to quickly and easily modify the specified state of the laboratory type from the second user interface, thereby reducing the amount of input required to edit the specified state of the laboratory type. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user quickly and easily specify a particular laboratory type), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

It should be noted that the details of the process described above with respect to method 700 (e.g., fig. 7) also apply in a similar manner to the method described below. For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, the user interface described above may include an affordance corresponding to a health topic, where a user-interactive graphical object corresponding to a laboratory type displayed in the user interface corresponds to a selected health topic. For the sake of brevity, these details are not repeated hereinafter.

Fig. 8A-8I illustrate an exemplary user interface for displaying a health topic. The user interfaces in these figures are used to illustrate the processes described below, including the process in fig. 9.

Fig. 8A illustrates a computer system 600 displaying a laboratory user interface 802a via a display 602. In some embodiments, computer system 600 optionally includes one or more features of device 100, device 300, or device 500. In some embodiments, computer system 600 is a tablet, phone, laptop, desktop, camera, or the like. In some embodiments, the inputs described below may be optionally replaced with alternative inputs, such as swipe inputs and/or long press inputs.

In fig. 8A, computer system 600 displays a laboratory user interface 802a. The laboratory user interface 802a includes affordances including laboratory data (e.g., 820a, 824a, 826 a) and health screens (e.g., 814a, 816a, 818 a) that, when selected, cause the computer system 600 to display laboratory affordances corresponding to the selected health screens. In fig. 8A, computer system 600 displays a laboratory user interface 802a with a selected "all" laboratory condition filter 814a that allows for the display of all available laboratory affordances, whether or not the laboratory type corresponding to the displayed laboratory affordance corresponds to a particular health condition.

The laboratory user interface 802a includes a return affordance 806 that, when selected, causes the computer system 600 to display a previously displayed user interface screen. The laboratory user interface 802a also includes a search bar 810 that, when selected, causes the computer 600 to display options for searching in laboratory data included in the laboratory user interface 802a (e.g., searching by inputting letters corresponding to laboratory data via a touch-pad, searching via voice input received via a microphone). The laboratory user interface 802a also includes a time indicator 804a that includes a visual and/or textual representation of the current time (e.g., 7:00 at FIG. 8A). Laboratory user interface 802a also includes an alphabetical option 812a that, when selected, causes computer system 600 to display laboratory data included in laboratory user interface 802a based at least in part on the alphabetical information (e.g., the laboratory data is alphabetically ordered).

The laboratory user interface 802a also includes a health screener that, when selected, causes the computer system 600 to limit the displayed laboratory affordance to laboratory affordances corresponding to the health conditions associated with the selected health screener. The laboratory user interface 802a includes a health screener 814a corresponding to an "all" health screener (e.g., allowing for display of all laboratory affordances), a health screener 816a corresponding to "diabetes" and screening the displayed laboratory affordances as laboratory affordances associated with diabetes when selected, and a health screener 818a corresponding to "heart health" and screening the displayed laboratory affordances as laboratory affordances associated with heart health when selected.

The laboratory user interface 802a also includes a lock indicator 821 that indicates a portion of the laboratory user interface 802a that corresponds to the laboratory type that has been locked (e.g., specified via user input). The laboratory user interface 802a also includes an incremental highlighting 820a that includes information related to differences between newer laboratory results and previous laboratory results. Incremental highlighting 820a includes a laboratory type 820a1 that includes a visual and/or textual indication of the laboratory type being compared (e.g., "HbA1c" in FIG. 8A), and an evaluation 820a2 that includes a visual and/or textual indication of the difference between the newer laboratory results for the indicated laboratory type and the older laboratory results for the indicated laboratory type. The incremental highlighting 820a also includes a graphical indicator 820a3 that includes a graphical representation of the relative relationship between the newer laboratory result of the indicated laboratory type and the previous laboratory result of the indicated laboratory type (e.g., an up arrow if the newer laboratory result is higher than the older laboratory result, a horizontal line if the newer laboratory result is the same as the older laboratory result, and a down arrow if the newer laboratory result is lower than the older laboratory result). The delta highlighting 820a also includes a range 820a4 that provides a graphical indication of older laboratory results relative to a range of possible laboratory result values for the corresponding laboratory type, and a range 820a5 that includes a graphical indication of newer laboratory results relative to a range of possible laboratory result values for the corresponding laboratory type. The laboratory user interface 802a also includes a time range indicator 822 that includes visual and/or textual indicators that display laboratory data below the time range indicator 822 corresponding to a particular time range (e.g., last 7 days, last 30 days).

The laboratory user interface 802a also includes a laboratory affordance 824a that includes a laboratory type 824a1 that indicates that the corresponding laboratory type is "creatinine. Laboratory affordance 824a also includes a value 824a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 824 a. Laboratory affordance 824a also includes date 824a3, which includes visual and/or textual indicators of the date when the corresponding laboratory type was updated. Laboratory affordance 824a also includes a range 824a4 that includes graphical indicators of the range of possible values for the most recent laboratory result corresponding to laboratory affordance 824a relative to the corresponding laboratory type (e.g., the most recent laboratory result compared to the full range of possible results, the most recent laboratory result compared to the range of healthy values).

The laboratory user interface 802a also includes a laboratory affordance 826a that includes a laboratory type 826a1 that indicates that the corresponding laboratory type is "calcium ion. Laboratory affordance 826a also includes a value 826a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 826 a. Laboratory affordance 826a also includes date 826a3, which includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

In fig. 8A, computer system 600 receives input 850a (e.g., tap input) on alphabetic option 812 a. Further, in fig. 8A, computer system 600 receives input 860a (e.g., swipe input) on laboratory user interface 802 a.

In fig. 8B, in response to receiving input 860a, computer system 600 displays laboratory user interface 802B. Fig. 8B illustrates a computer system 600 displaying a laboratory user interface that selects a "diabetes" health class filter, wherein the selected health class filter has moved from "all" to "diabetes" in response to input 860 a. The laboratory user interface 802b includes at least a portion of a health screener 814b corresponding to an "all" health screener (e.g., allowing for display of all laboratory affordances), a health screener 816b corresponding to "diabetes" and screening the displayed laboratory affordances as laboratory affordances associated with diabetes when selected, and a health screener 818b corresponding to "heart health" and screening the displayed laboratory affordances as laboratory affordances associated with heart health when selected. In the laboratory user interface 802b, the health filter 816b includes a visual indication (e.g., a profile) that indicates that the health filter 816b is currently selected. The laboratory user interface 802b includes laboratory data corresponding to the selected "diabetes" health screener, and in particular, screens the displayed laboratory affordance as a laboratory affordance corresponding to the selected "diabetes" health screener. The laboratory user interface 802b includes education 828a regarding a health status filter 816b (e.g., "diabetes").

The laboratory user interface 802b also includes an incremental highlighting 820b that includes content similar to the incremental highlighting 820a described above. The laboratory user interface 802b also includes a laboratory affordance 834a that includes a laboratory type 834a1 that indicates that the corresponding laboratory type is "fasting glucose". Laboratory affordances 834a also include values 834a2 that correspond to laboratory measurements (e.g., most current laboratory measurements) corresponding to laboratory affordances 834 a. Laboratory affordance 834a also includes a date 834a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

The laboratory user interface 802b also includes an absence indicator 832 that indicates a portion of the laboratory user interface 802b that includes information related to laboratory types that are not yet available at the computer system 600 (e.g., laboratory types for which laboratory results have not been received by the computer system 600). In some embodiments, the portion of the laboratory user interface 802b identified by the absence indicator 832 includes one or more laboratory affordances corresponding to the suggested laboratory type based on determining that the suggested laboratory type is related to a currently selected health screener (e.g., "diabetes") and/or based on available (e.g., existing) laboratory results displayed by the computer system 600. The laboratory user interface 802b also includes a presence indicator 830 that indicates a portion of the laboratory user interface 802b that includes information related to the laboratory types available at the computer system 600 (e.g., the laboratory type for which the computer system 600 received laboratory results).

The laboratory user interface 802b also includes a laboratory affordance 836a that includes a laboratory type 836a1 that indicates that the corresponding laboratory type is "TSH". The laboratory affordance 836a also includes a description 836a2 regarding the corresponding laboratory type. Notably, laboratory affordance 836a is displayed below absence identifier 832 to indicate that the laboratory type (e.g., "TSH") corresponding to laboratory affordance 836a is not in the records available to computer system 600. Thus, computer system 600 has no "TSH" laboratory data available at the time laboratory user interface 802b is displayed. At fig. 8B, computer system 600 receives input 850B (e.g., tap input) on health filter 818B and, in response, displays laboratory user interface 802c.

In fig. 8C, in response to receiving input 850b, computer system 600 displays laboratory user interface 802C. Fig. 8C illustrates a computer system 600 displaying a laboratory user interface for selecting a "heart health" health class filter. In some embodiments, updating the laboratory user interface to show that the health 818c was selected includes displaying a scroll animation that shows the health filter 818c scrolling to the left of the laboratory user interface 802c. The laboratory user interface 802c includes at least a portion of a health screener 816c corresponding to "diabetes," a health screener 818c corresponding to "heart health," and a health screener 838a corresponding to "bone health. In laboratory user interface 802c, health filter 816c includes a visual indication (e.g., a profile) that health filter 818c is currently selected. The laboratory user interface 802c includes laboratory data corresponding to a selected "heart health" health condition filter (e.g., 818 c). The laboratory user interface 802c includes education 828b regarding a health screener 818c (e.g., "heart health").

The laboratory user interface 802c also includes laboratory data related to "heart health" based on the selected health condition filter 818 c. The laboratory user interface 802c also includes a laboratory affordance 840a that includes a laboratory type 840a1 that indicates that the corresponding laboratory type is "cholesterol. Laboratory affordance 840a also includes a value 840a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 840 a. Laboratory affordance 840a also includes a date 840a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

The laboratory user interface 802c also includes a laboratory affordance 842a that includes a laboratory type 842a1 that indicates that the corresponding laboratory type is "heart rate". The laboratory affordance 842a also includes a value 842a2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to the laboratory affordance 842 a. The laboratory affordance 842a also includes a date 842a3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

The laboratory user interface 802c also includes an absence indicator 832 that indicates a portion of the laboratory user interface 802c that includes information related to laboratory types that are not yet available at the computer system 600 (e.g., laboratory types for which laboratory results have not been received by the computer system 600). Laboratory user interface 802c includes laboratory affordance 844a, which includes laboratory type 844a1 indicating that the corresponding laboratory type is "iron". Laboratory affordances 844 are displayed based at least in part on corresponding laboratory types (e.g., "iron") that correspond to the selected laboratory type (e.g., "heart health").

The laboratory affordance 844a also includes a description 844a2 of the corresponding laboratory type. Notably, laboratory affordance 844a is displayed below absence identifier 832 to indicate that the laboratory type (e.g., "iron") corresponding to laboratory affordance 844a is not in the records available to computer system 600. Thus, computer system 600 has no "iron" laboratory data available at the time laboratory user interface 802c is displayed. The laboratory user interface 802C also includes a time indicator 804a that includes a visual and/or textual representation of the current time (e.g., 7:00 at FIG. 8C). The laboratory user interface 802c also includes a return affordance 806 that, when selected, causes the computer system 600 to display a previously displayed user interface screen. In fig. 8C, computer system 600 receives input 850C (e.g., tap input) on return affordance 806.

In fig. 8D, in response to detecting input 850c, computer system 600 displays summary user interface 846a. Summary user interface 846a includes a time indicator 804b that indicates that time has elapsed (e.g., from 7:00 to 10:09) between fig. 8C and 8D. Between 7:00 and 10:09, the computer system receives laboratory data corresponding to the missing laboratory type (e.g., "iron") indicated in fig. 8C, and displays updates related to the new laboratory data as a result. Summary user interface 846a also includes a laboratory update affordance 854a that includes an update indicator 854a1 that includes visual and/or textual indicators that laboratory data updates are available. The laboratory update affordance 854a also includes an update description 854a2 regarding the contents of laboratory data updates.

The summary user interface 846a also includes a health record update section 856a that includes visual and/or textual indicators that health record updates are available (e.g., new "iron" laboratory results). Summary user interface 846a also includes preference indicator 858, which indicates the portion of summary user interface 846a that displays preference information. Summary user interface 846a also includes: a measurement 862a1 comprising a visual representation of the first type of health related information and a measurement 862a2 comprising a visual representation of the second type of health related information. Summary user interface 846a also includes summary affordance 864, which when selected causes computer system 600 to display a summary user interface (e.g., 846 a). At fig. 8D, summary affordance 864 is displayed in a visually different appearance (e.g., bold, outline, highlighting) to indicate that the summary user interface is currently being displayed and/or that summary affordance 864 is currently selected. Summary user interface 846a also includes a sharing affordance 866 that, when selected, causes computer system 600 to display a user interface for sharing and/or transmitting information related to health data to other users. Summary user interface 846a also includes a browse affordance 868 that, when selected, causes computer system 600 to display a user interface for browsing health-related information. The summary user interface 846a also includes an avatar 852 that includes graphical indicators corresponding to the user and/or user account associated with the computer system 600. At fig. 8D, computer system 600 receives input 850D (e.g., touch input) on laboratory update affordance 854 a.

In fig. 8E, in response to receiving input 850d, computer system 600 displays laboratory user interface 802d. Laboratory user interface 802d shows an updated version of laboratory user interface 802a after computer system 600 has received new laboratory results. The laboratory user interface 802d includes a health filter 814c corresponding to "all" health filters, a health filter 816d corresponding to "diabetes", and a health filter 818d corresponding to "heart health".

In fig. 8E, laboratory user interface 802d includes a new laboratory affordance 844b that is not included in laboratory user interface 802a, indicating that a "iron" laboratory result has been received. Laboratory affordance 844b includes laboratory type 844b1, indicating that the corresponding laboratory type is "iron". Laboratory affordance 844b also includes a value 844b2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 844 b. Laboratory affordance 844b also includes date 844b3, which includes visual and/or textual indicators of the date when the corresponding laboratory type was updated. Laboratory affordance 844b corresponds to new laboratory data, as indicated by date 844b3, indicating that the laboratory type is updated to "today". Further, laboratory affordance 844b corresponds to an updated view of laboratory affordance 844a that indicates laboratory data for laboratory type "iron" is not available and laboratory data for laboratory type "iron" is now available.

The laboratory user interface 802a also includes a lock indicator 821 that indicates a portion of the laboratory user interface 802d that corresponds to the laboratory type that has been locked (e.g., specified via user input). The laboratory user interface 802d also includes an incremental highlighting 820c that includes content similar to the incremental highlighting 820a described above.

The laboratory user interface 802d also includes a laboratory affordance 824b that includes content similar to the laboratory affordance 824a described above. In fig. 8E, computer system 600 receives input 850E (e.g., tap input) on health filter 816 d.

In fig. 8F, in response to receiving input 850e, computer system 600 displays laboratory user interface 802e. Fig. 8F illustrates a computer system 600 displaying a laboratory user interface for a "diabetes" health class filter selected. Laboratory user interface 802e is an updated version of laboratory user interface 802b in which computer system 600 has received laboratory data corresponding to a "iron" laboratory type. Laboratory user interface 802e includes a health filter 814d that allows display of all laboratory affordances, a health filter 816e corresponding to "diabetes," and at least a portion of a health filter 818e corresponding to "heart health. In laboratory user interface 802e, health filter 816e includes a visual indication that health filter 816e is currently selected. The laboratory user interface 802e includes laboratory data corresponding to the selected "diabetes" health condition filter. The laboratory user interface 802e includes education 828a regarding a health status filter 816e (e.g., "diabetes").

The laboratory user interface 802e also includes laboratory data related to "diabetes" based on the selected health condition filter 816 e. The laboratory user interface 802e also includes an incremental highlighting 820d that includes content similar to the incremental highlighting 820a described above. The laboratory user interface 802e also includes a laboratory affordance 834b that includes a laboratory type 834b1 that indicates that the corresponding laboratory type is "fasting glucose". Laboratory affordance 834b also includes a value 834b2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 834 b. Laboratory affordance 834b also includes a date 834b3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated. Laboratory user interface 802e also includes laboratory affordance 844c, which includes content similar to laboratory affordance 844b described above. At fig. 8F, computer system 600 receives input 860b (e.g., swipe input) on laboratory user interface 802e and, in response, displays laboratory user interface 802F.

At fig. 8G, in response to receiving input 860b, computer system 600 displays laboratory user interface 802f. Fig. 8G illustrates a computer system 600 displaying a laboratory user interface for selecting a "heart health" health class filter. The laboratory user interface 802f is an updated version of the laboratory user interface 802c in which the computer system 600 has received laboratory data corresponding to the "iron" laboratory type. The laboratory user interface 802f includes at least a portion of a health screener 816f corresponding to "diabetes," a health screener 818f corresponding to "heart health," and a health screener 838b corresponding to "bone health. In the laboratory user interface 802f, the health filter 818f includes a visual indication that the health filter 818f is currently selected. The laboratory user interface 802f includes laboratory data corresponding to the selected "heart health" health screener. The laboratory user interface 802f includes education 828b regarding a health filter 818f (e.g., "heart health").

The laboratory user interface 802f also includes laboratory data related to "heart health" based on the selected health condition filter 818 f. The laboratory user interface 802f also includes a laboratory affordance 840b that includes a laboratory type 840b1 that indicates that the corresponding laboratory type is "cholesterol. Laboratory affordance 840b also includes a value 840b2 that corresponds to a laboratory measurement (e.g., the most current laboratory measurement) corresponding to laboratory affordance 840 b. Laboratory affordance 840b also includes a date 840b3 that includes visual and/or textual indicators of the date when the corresponding laboratory type was updated.

The laboratory user interface 802f also includes a laboratory affordance 842b that includes content similar to the laboratory affordance 842b described above. Laboratory user interface 802f also includes laboratory affordances 844d, the contents of which are similar to laboratory affordances 844b as described above. Notably, the laboratory user interface 802f does not include the absence indicator 832. Whereas laboratory user interface 802c indicates that laboratory results corresponding to the "iron" laboratory type are not available and/or missing, laboratory affordance 844d indicates that laboratory results corresponding to the "iron" laboratory type are now available. In some embodiments, in accordance with a determination that computer system 600 has received and/or has access to laboratory results corresponding to a previously absent and/or non-present laboratory type, computer system 600 foregoes displaying non-presence indicator 832. In fig. 8G, computer system 600 receives input 850f (e.g., tap input) on laboratory affordance 844d and, in response, displays laboratory user interface 870.

In fig. 8H, in response to receiving input 850f, computer system 600 displays laboratory user interface 870. Fig. 8H illustrates a user interface including laboratory data and/or results corresponding to a selected laboratory type (e.g., "iron") that has not been locked (e.g., has not been specified via user input). The laboratory user interface 870 also includes a lock affordance 880 that, when selected, causes the laboratory type indicated by laboratory type 874 to be specified by user input (e.g., locked).

The laboratory user interface 870 includes a return affordance 872 that, when selected, causes the computer system 600 to display a previous user interface (e.g., laboratory user interface 802 f) that was displayed prior to displaying the laboratory user interface 870. The laboratory user interface 870 also includes a laboratory type 874 that indicates the laboratory type (e.g., "iron") to which the laboratory user interface 870 corresponds. Laboratory user interface 870 also includes chart data 876 that includes graphs and/or charts corresponding to laboratory results corresponding to laboratory type 874. The laboratory user interface 870 also includes education 878 regarding the laboratory type 874 (e.g., for obtaining common causes of a laboratory associated with the laboratory type 874, physiological functions associated with the laboratory type 874). Laboratory user interface 870 also includes a record indicator 886 that includes visual and/or textual indications of recorded data corresponding to one or more laboratory results corresponding to laboratory type 874. The laboratory user interface 870 also includes a laboratory affordance 888 that corresponds to laboratory results of a laboratory type that corresponds to laboratory type 874. The laboratory user interface 870 also includes a display of all affordances 890 that, when selected, cause the computer system 600 to display additional laboratory results corresponding to laboratory type 874 in the laboratory user interface 870.

The laboratory user interface 870 also includes a tab affordance associated with the laboratory type 874 that, when selected, causes the computer system 600 to display information related to a particular health condition. The laboratory user interface 870 includes a tab affordance 882 that, when selected, causes the computer system 600 to display a user interface that includes laboratory data related to "bone health. The laboratory user interface 870 also includes a tab affordance 884 that, when selected, causes the computer system 600 to display a user interface (e.g., laboratory user interface 802 e) that includes laboratory data related to "diabetes.

At fig. 8I, in response to receiving input 850a, the computer system displays a laboratory user interface 802g, as discussed above with respect to fig. 8A. Laboratory user interface 802g is an updated version of laboratory user interface 802a, wherein laboratory data is displayed based at least in part on alphabetical information (e.g., laboratory data is ordered alphabetically) in response to selection of alphabetical option 812a (e.g., via input 850 a). In fig. 8I, the laboratory user interface 802g includes an alphabetical order option 812b, which includes an outline that visually indicates that the alphabetical order option 812b was selected.

The laboratory user interface 802g also includes a lock indicator 821 that indicates a portion of the laboratory user interface 802g that corresponds to the laboratory type that has been locked (e.g., specified via user input). The laboratory user interface 802g also includes an incremental highlighting 820e that includes content similar to the incremental highlighting 820a described above. Laboratory user interface 802e also includes an alphabetical indicator 892 comprising visual and/or textual indicators that laboratory data displayed below alphabetical indicator 892 is ordered into an alphabetical order. The laboratory user interface 802g also includes a laboratory affordance 824c, the contents of which are similar to the laboratory affordance 824a described above. The laboratory user interface 802g also includes a laboratory affordance 826b, the contents of which are similar to the laboratory affordance 826a described above.

Notably, laboratory affordance 826b is displayed above laboratory affordance 824c because laboratory results are ordered into an alphabetical order based on their corresponding laboratory types (e.g., "calcium ions" and "creatinine"). However, the locked laboratory type (e.g., "HbA1 c") is displayed in a separate portion of the laboratory user interface 802g from the unlocked laboratory type (e.g., "calcium ions" and "creatinine") and is ordered separately (e.g., alphabetically) within the separate portion of the laboratory user interface 802 g.

The laboratory user interface 802g includes a health screener 814e that allows for the display of all laboratory affordances, a health screener 816g corresponding to "diabetes," and a health screener 818g corresponding to "heart health.

Fig. 9 is a flowchart illustrating a method for displaying a health topic using a computer system in accordance with some embodiments. The method 900 is performed at a computer system (e.g., 100, 300, 500) (e.g., a wearable electronic device (e.g., a smart watch), a smart phone, a desktop computer, a laptop computer, a tablet computer) in communication with a display generating component and one or more input devices (e.g., a display controller, a touch-sensitive display system, a rotatable input mechanism, a touch-sensitive surface). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, the method 900 provides an intuitive way for displaying a health topic. The method reduces the cognitive burden on the user caused by viewing and managing the health topics, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to view health topics faster and more efficiently saves power and increases the time interval between battery charges.

A computer system (e.g., 600) receives (e.g., 902) a clinical data set (e.g., physiological measurements, laboratory results, health data, medical data (e.g., blood glucose, creatinine, iron, LDL cholesterol)) at the computer system, the clinical data set comprising: a set of data instances (e.g., one or more data) corresponding to a first health topic (e.g., medical condition, health problem, diagnosis, symptom, and/or risk factor) (e.g., 904), and a set of data instances (e.g., 906) corresponding to a second health topic different from the first health topic. In some embodiments, the one or more data instances corresponding to the first health topic do not correspond to the second health topic. In some embodiments, the one or more data instances include at least one data instance corresponding to at least a first health topic and a second health topic.

A computer system (e.g., 600) displays (e.g., 908) a clinical data user interface (e.g., 802 a) via a display generation component (e.g., 602), the clinical data user interface comprising: a first user-interactive graphical user interface object (e.g., an affordance) corresponding to a first health topic, a first topic filter (e.g., 816 a) (e.g., 910), a second user-interactive graphical user interface object (e.g., an affordance) corresponding to a second health topic, a second health topic filter (e.g., 818 a) (e.g., 912), and a set of data instance graphical user interface objects (e.g., 914) (e.g., 820a, 824a, 826 a).

In accordance with a determination (e.g., 916) that the first user-interactive graphical user interface object (e.g., 816 b) is currently selected (e.g., currently in focus, highlighted, bolded), the set of data instance graphical user interface objects (e.g., 820b, 834 a) corresponds to (e.g., each user interface object in the set of data instance graphical user interface objects represents a single data instance in the set of data instances) a set of data instances corresponding to the first health topic. In some embodiments, when the first user interactive graphical user interface object is currently selected, data instances that do not correspond to the first health topic are not displayed (e.g., filtered out). In some embodiments, both the first user-interactive graphical user interface object and the second user-interactive graphical user interface object cannot be selected simultaneously (e.g., selecting one (or selecting another filter) will deselect the other).

In accordance with a determination (e.g., 918) that a second user-interactive graphical user interface object (e.g., 818 c) is currently selected, the set of data instance graphical user interface objects (e.g., 840a, 842 a) corresponds to a set of data instances corresponding to a second health topic. In some embodiments, the set of data instances corresponding to the first health topic and/or the set of data instances corresponding to the second health topic includes data instances related to test results, laboratory results, and/or physiological measurements. When a user interactive graphical user interface object corresponding to one of the health topics is selected, the set of data instance graphical user interface objects corresponding to the health topic is displayed to provide visual feedback regarding the set of data instance graphical user interface objects corresponding to the given health topic. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently. Further, when a user interactive graphical user interface object corresponding to one of the health topics is selected, displaying the set of data instance graphical user interface objects corresponding to that health topic enables a user to quickly and easily restrict the set of data instance graphical user interface objects displayed as corresponding to the given health topic without requiring the user to manually sort and/or remove data instance graphical user interface objects that do not correspond to that health topic. Performing operations when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by displaying information corresponding to a particular health topic), which in turn reduces power usage and extends battery life of the device by enabling a user to more quickly and efficiently use the device.

In some embodiments, a computer system (e.g., 600) receives, at the computer system, a second clinical data set comprising a first data instance. In some embodiments, after receiving the second clinical data set, the computer system displays a clinical data user interface (e.g., 802 b), wherein displaying the clinical data user interface comprises: in accordance with a determination that the first user-interactive graphical user interface object is currently selected (e.g., 816 b) and the first data instance corresponds to the first health topic, the computer system displays the first data instance graphical user interface object corresponding to the first data instance (e.g., 820 b). In some embodiments, in accordance with a determination that a second user-interactive graphical user interface object (e.g., 818 c) is currently selected and the first data instance corresponds to the second health topic, the computer system displays the first data instance graphical user interface object corresponding to the first data instance. In accordance with a determination that the first data instance corresponds to a third health topic different from the first health topic and the second health topic, the computer system displays a third user interactive graphical user interface object (e.g., an affordance; a third topic filter) corresponding to the third health topic (e.g., 838 a). In some embodiments, displaying the clinical data user interface includes displaying a first data instance graphical user interface object corresponding to the first data instance in accordance with a determination that the third user interactive graphical user interface object is currently selected and the first data instance corresponds to the third health topic. Displaying the data instance graphical user interface object corresponding to the received data instance in accordance with a determination that the data instance corresponds to the currently selected user-interactive graphical user interface object (e.g., a health topic filter) enables newly added data instances to be quickly ordered and displayed with their corresponding health topics without requiring the user to manually order and/or add the received data instance to the health topic. Performing operations when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by displaying information in a sorted order), which in turn reduces power usage and extends battery life of the device by enabling a user to more quickly and efficiently use the device.

In some implementations, the set of data instance graphical user interface objects includes a second data instance graphical user interface object (e.g., 820 b), wherein the second data instance graphical user interface object includes a graphical indication (e.g., 820b 3) of a difference between a first value (e.g., a current value) corresponding to the second data instance graphical user interface object and a second value (e.g., a previous value) corresponding to the second data instance graphical user interface object. In some embodiments, the graphical indication comprises an up arrow if the first value is greater than the second value. In some embodiments, if the first value is less than the second value, the graphical indication comprises a down arrow. In some embodiments, the graphical indication comprises a horizontal line if the first value and the second value are equal. Displaying a graphical indication of a difference between two values corresponding to a data instance graphical user interface object provides improved visual feedback regarding an overall trend (e.g., trajectory) of values associated with the data instance graphical user interface object. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some implementations, the set of data instance graphical user interface objects includes a third data instance graphical user interface object (e.g., 844 c), where the third data instance graphical user interface object corresponds to a first data instance of a first type (e.g., a first laboratory type, a first laboratory test provider) and a second data instance of a second type (e.g., a second laboratory type, a first laboratory test provider). Displaying the data instance graphical user interface objects corresponding to the plurality of data instances enables a user to quickly and easily view aggregated data related to the first data instance and the second instance by viewing and/or interacting with the data instance graphical user interface objects (e.g., selecting the data instance graphical user interface objects), thereby reducing the amount of input required to view data related to the first data instance and the second data instance. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user to quickly and easily view aggregated laboratory data), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some implementations, the set of data instance graphical user interface objects includes a fourth data instance graphical user interface object (e.g., 844 d). In some implementations, when the clinical data user interface (e.g., 802 f) is displayed, the computer system (e.g., 600) receives a user input (e.g., tap input) corresponding to a selection of a fourth data instance graphical user interface object (e.g., 850 f). In some embodiments, in response to receiving a user input corresponding to a selection of a fourth data instance graphical user interface object, the computer system displays a laboratory user interface (e.g., 870) corresponding to the fourth data instance graphical user interface object, wherein the laboratory user interface includes a fifth user interactive graphical user interface object (e.g., an affordance; a first topic filter) corresponding to a sixth health topic (e.g., 884). In some embodiments, the computer system receives user input corresponding to selection of a fifth user interactive graphical user interface object when displaying the laboratory user interface. In some embodiments, in response to receiving a user input corresponding to selection of a fifth user interactive graphical user interface object, the computer system displays a clinical data user interface (e.g., 802 e), wherein the set of data instance graphical user interface objects corresponds to a set of data instances corresponding to a sixth health topic. Displaying a clinical data user interface including information corresponding to a wellness topic in response to selecting a user interactive graphical user interface object enables a user to quickly and easily view clinical data related to the wellness topic, thereby reducing the amount of input required to view the data related to the wellness topic. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user quickly and easily view clinical data related to a health topic), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some implementations, the first user-interactive graphical user interface object (e.g., 816 a) and the second user-interactive graphical user interface object (e.g., 818 a) are aligned along a first axis (e.g., arranged in a clinical data user interface in a first direction (e.g., left to right), and the set of data instance graphical user interface objects (e.g., 820a, 824a, 826 a) are aligned along a second axis different from the first axis (e.g., arranged in a second direction (e.g., top to bottom) in the clinical data user interface). Aligning the filter user interactive graphical user interface object and the data instance along the first axis the set of graphical user interface objects provides visual feedback regarding different properties of different on-screen elements, and in some embodiments, provides visual feedback that different types of on-screen elements can scroll in two different directions corresponding to their alignment. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some embodiments, the computer system (e.g., 600) receives a first user input (e.g., 850 b) when the first user interactive graphical user interface object (e.g., 816 b) is currently selected and when a set of data instance graphical user interface objects corresponding to a set of data instances (e.g., 820b, 834 a) corresponding to the first health topic is displayed. In some implementations, in response to receiving the first user input, the computer system selects a second user-interactive graphical user interface object (e.g., 818 b). In some implementations, in response to receiving the first user input, the computer system modifies the set of data instance graphical user interface objects (e.g., modifies a display (e.g., appearance) thereof) to correspond to the set of data instances corresponding to the second health topic. Displaying the set of data instance graphical user interface objects corresponding to the selected user-interactive graphical user interface object based on the swipe input enables a user to quickly and easily view data instance graphical user interface objects related to the selected user-interactive graphical user interface object (e.g., the health filter) without requiring the user to manually sort and/or locate the related data instance graphical user interface objects. Performing operations when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by screening information according to health topics), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, displaying the clinical data user interface (e.g., 802 c) includes concurrently displaying a third user-interactive graphical user interface object (e.g., 842 a) that includes a first visual representation (e.g., 842a 2) of data collected via a physiological measurement sensor (e.g., heart rate sensor, VO2max sensor). In some embodiments, in response to receiving a user input corresponding to selection of a third user-interactive graphical user interface object, the computer system displays a sensor user interface including additional data from the physiological measurement sensor. The inclusion of visual representations of data collected via the physiological measurement sensor in the clinical data user interface enables a user to quickly and easily view the physiological measurement sensor data while viewing other clinical data, thereby reducing the number of inputs required to toggle between clinical data retrieved from elsewhere (e.g., a hospital, laboratory) and physiological measurement sensor data. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user view physiological measurement sensor data quickly and easily while viewing other clinical data), which in turn reduces power usage and extends the battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, in accordance with a determination that the first user-interactive graphical user interface object (e.g., 816 b) is currently selected (e.g., currently in focus, highlighted, bolded), the clinical data user interface (e.g., 802 b) includes chart data corresponding to the first health topic (e.g., charts and/or graphs including data related to the first health topic). In some embodiments, in accordance with a determination that a second user-interactive graphical user interface object (e.g., 818 c) is currently selected, the clinical data user interface (e.g., 802 c) includes chart data (e.g., charts and/or graphics including data related to the first health topic) corresponding to the second health topic. In some embodiments, both the first user-interactive graphical user interface object and the second user-interactive graphical user interface object cannot be selected simultaneously (e.g., selecting one (or selecting another filter) will deselect the other). Displaying chart data corresponding to the first health topic or the second health topic in accordance with a determination of which health topic filter was selected enables a user to quickly and easily view chart data related to the health topic, thereby reducing the number of inputs required to view chart data related to the selected health topic filter. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user view chart data related to a health topic quickly and easily), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some embodiments, in accordance with a determination that the first user-interactive graphical user interface object (e.g., 816 b) is currently selected, the clinical data user interface (e.g., 802 b) includes a set of information corresponding to the first health topic (e.g., a textual description of the scope importance of the first health topic) (e.g., 828 a). In some embodiments, in accordance with a determination that the second user-interactive graphical user interface object (e.g., 818 c) is currently selected, the clinical data user interface (e.g., 802 c) includes a set of information corresponding to the second health topic (e.g., a textual description of the scope importance of the second health topic) (e.g., 828 b). In some embodiments, the set of information related to the health topic includes information related to one or more of a set of data instance graphical user interface objects included in the clinical data user interface. Displaying information corresponding to the first or second health topic in accordance with a determination of which health topic filter was selected enables a user to quickly and easily view educational data related to the health topic, thereby reducing the number of inputs required to view chart data related to the selected health topic filter. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user quickly and easily view educational data related to a health topic), which in turn reduces power usage and extends the battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, in accordance with a determination that the first user-interactive graphical user interface object (e.g., 816 b) is currently selected and the computer system (e.g., 600) has not received one or more data instances corresponding to the first laboratory type corresponding to the first health topic (e.g., clinical association (e.g., blood glucose for diabetes)), the computer system displays a first visual indicator (e.g., 836 a) corresponding to the first laboratory type (e.g., the computer system has not received a text and/or graphical indication of data corresponding to the first laboratory type, a suggestion to add data instances corresponding to the first laboratory type). In some embodiments, in accordance with a determination that a second user-interactive graphical user interface object (e.g., 818 c) is currently selected and one or more data instances corresponding to a second laboratory type associated with a second health topic have not been received by the computer system, the computer system displays a second visual indicator (e.g., 844 a) corresponding to the second laboratory type. In some embodiments, the first laboratory type and the second laboratory type are different. In some embodiments, the first visual indicator and the second visual indicator are different. In accordance with a determination that a health topic filter corresponding to a laboratory type has been selected and that a data instance corresponding to the laboratory type has not been received by the computer system to display a visual indicator corresponding to the laboratory type provides visual feedback regarding a potentially lost laboratory type corresponding to a health topic being viewed. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some embodiments, upon displaying the clinical data user interface (e.g., 802 f), the computer system receives a second user input (e.g., tap input) (e.g., 850 f) corresponding to a selection of a data instance graphical user interface object (e.g., 844 d) in the graphical user interface object set (e.g., included therein). In some embodiments, in response to receiving the second user input, the computer system displays a second laboratory user interface (e.g., 870), wherein the second laboratory user interface comprises: a third visual indicator corresponding to one or more data instances (e.g., one or more data) (e.g., 888) corresponding to a data instance graphical user interface object in the graphical user interface object set and a fourth user interactive graphical user interface object (e.g., an affordance; a fourth topic filter) corresponding to a fourth health topic (e.g., 882, 884). Displaying a user-interactive graphical user interface object corresponding to the fourth health topic in the laboratory user interface provides visual feedback regarding the health topic that may be related to the content being viewed. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

In some embodiments, the clinical data set includes a fourth data instance (e.g., 834 b) corresponding to the first health topic and not to the second health topic. Maintaining a clinical dataset comprising data instances corresponding to different health topics enables features of the clinical dataset to be displayed simultaneously, aggregated, and/or ordered by criteria, thereby reducing the amount of input required to navigate between different data sets associated with different health topics. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user navigate between different data sets related to different health topics quickly and easily), which in turn reduces power usage and extends the battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, the clinical data set includes fifth data instances (e.g., 844c, 844 d) corresponding to the first and second health topics. The inclusion of data instances corresponding to a first health topic and a second health topic in a clinical data set enables the data instances to be displayed in a plurality of user interfaces corresponding to two corresponding health topics, thereby reducing the number of inputs required to select corresponding health topics for data instances that may correspond to two or more health topics. Reducing the number of inputs required to perform an operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user quickly and easily select a corresponding health topic for a data instance that may correspond to two or more health topics), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, upon displaying the clinical data user interface (e.g., 802 a), the computer system (e.g., 600) receives a first set of one or more user inputs including inputs for adding a fifth wellness topic. In some embodiments, in response to receiving the first set of one or more user inputs, the computer system updates the clinical data user interface to include a user interactive graphical user interface object corresponding to the fifth wellness topic. Updating the clinical user interface to include a user interactive graphical user interface object corresponding to one of the wellness topics in response to receiving a set of user inputs enables a user to quickly and easily add the wellness topic when displaying the clinical data user interface, thereby reducing the amount of input required to select a corresponding wellness topic for data instances that may correspond to two or more wellness topics. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user add health topics quickly and easily when displaying a clinical data user interface), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, upon displaying the clinical data user interface (e.g., 802 a), the computer system (e.g., 600) receives a second set of one or more user inputs including inputs for removing the first health topic. In some embodiments, in response to receiving the second set of one or more user inputs, the computer system updates the clinical data user interface to not include the first user-interactive graphical user interface object corresponding to the first health topic (e.g., to exclude the first health topic). Updating the clinical user interface to exclude (e.g., to exclude) user-interactive graphical user interface objects corresponding to one health topic in response to receiving a set of user inputs enables a user to quickly and easily remove the health topic when displaying the clinical data user interface, thereby reducing the amount of input required to select a corresponding health topic for data instances that may correspond to two or more health topics. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user quickly and easily remove health topics when displaying a clinical data user interface), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, displaying the clinical data user interface (e.g., 802 a) includes concurrently displaying ordered user interactive graphical user interface objects (e.g., 812 a) that, when selected, cause the set of data instance graphical user interface objects to be displayed within the clinical data user interface based on at least a first ordering criteria (e.g., alphabetically, chronologically). Displaying the sorting user-interactive graphical user interface objects that, when selected, cause the set of data instance graphical user interface objects to be sorted enables a user to quickly and easily sort the data instance graphical user interface objects without manually sorting them, thereby reducing the number of inputs required to sort the data instance graphical user interface objects. Reducing the number of inputs required to perform the operation enhances the operability of the system and makes the computer system more efficient (e.g., by helping a user to quickly and easily order data instance graphical user interface objects), which in turn reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the system.

In some embodiments, in accordance with a determination that a first subset (e.g., 820 c) of the set of data instance graphical user interface objects has been (e.g., previously) specified (e.g., locked, selected) via user input (e.g., via tap input, press input, and/or swipe input) received via the one or more input devices, the computer system (e.g., 600) displays the first subset (e.g., 820 c) of the set of data instance graphical user interface objects in a first portion (e.g., a portion of the clinical data user interface for the specified (e.g., locked) data instance graphical user interface objects) of the clinical data user interface (e.g., 802 a) via the display generation component (e.g., 600). In some embodiments, in accordance with a determination that a second subset (e.g., 826b, 824 c) of the set of data instance graphical user interface objects that is different from the first subset of the set of data instance graphical user interface objects has not been specified (e.g., locked, selected) via user input (e.g., via tap input, press input, and/or swipe input) received via the one or more input devices (e.g., has not been previously described), the computer system displays the second subset of the set of data instance graphical user interface objects in a second portion of the clinical data user interface (e.g., a portion of the clinical data user interface for the data instance graphical user interface that has not been specified (e.g., locked)) via the display generation component (e.g., 602). In some embodiments, in accordance with a determination that a difference (e.g., an increase, a decrease, an unchanged indication, a changed indication, an increment) between a first value (e.g., a numerical value corresponding to a physiological measurement and/or a reading corresponding to a first laboratory data instance) of a graphical user interface object included in a first subset of the set of data instance graphical user interface objects and at least a second value (e.g., a physiological measurement and/or a reading corresponding to a first laboratory data instance) of a graphical user interface object included in a first subset of the set of data instance graphical user interface objects (e.g., a physiological measurement and/or a reading corresponding to a first laboratory data instance) is specified (e.g., locked, selected) via a user input (e.g., via a tap input, a press input, and/or a swipe input) received via one or more input devices is included in the first subset of the set of data instance graphical user interface objects. In some implementations, in accordance with a determination that the data instance graphical user interface objects included in the second subset of the set of data instance graphical user interface objects have not been specified via user input (e.g., via any previous user input; the first laboratory type is not currently a specified/selected/locked laboratory type), the data instance graphical user interface objects included in the second subset of the set of data instance graphical user interface objects are displayed via the display generation component without displaying a graphical indication of a difference between the first value of the data instance graphical user interface objects included in the second subset of the set of data instance graphical user interface objects and at least the second value of the data instance graphical user interface objects included in the second subset of the set of data instance graphical user interface objects. Visual feedback is provided regarding which data instance graphical user interface objects have been previously specified via user input in response to determining whether a subset of the set of data instance graphical user interface objects has been previously specified via user input, the subset being displayed in the first portion or the second portion of the clinical data user interface. Providing improved visual feedback to the user enhances the operability of the system and makes the computer system more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the system), which in turn reduces power usage and extends battery life of the device by enabling the user to use the system more quickly and efficiently.

It is noted that the details of the process described above with respect to method 900 (e.g., fig. 9) also apply in a similar manner to the method described below. For example, method 700 optionally includes one or more of the features of the various methods described above with reference to method 900. For example, the data instances described above may be displayed in a particular portion of a user interface, where the data instances are included based on determining whether the data instances (or corresponding health topics or laboratory types) have been previously specified via user input. For the sake of brevity, these details are not repeated hereinafter.

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 teaching. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Those skilled in the art will be able to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

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

As described above, one aspect of the present technology is to collect and use data available from a variety of sources to allow a user to view and manage relevant clinical, health-related, and/or physiological data. The present disclosure contemplates that in some examples, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, tweet IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be used to benefit users. For example, personal information data may be used to display user-specific clinical, health-related, or physiological measurement data. Thus, the use of such personal information data enables users to view and manage themselves, or users sharing corresponding data. In addition, the present disclosure contemplates other uses for personal information data that are beneficial to the user. For example, health and fitness data may be used to provide insight into the overall health of a user, or may be used as positive feedback to individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will adhere to established privacy policies and/or privacy practices. In particular, such entities should exercise and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be readily accessible to the user and should be updated as the collection and/or use of the data changes. Personal information from users should be collected for legal and reasonable use by entities and not shared or sold outside of these legal uses. In addition, such collection/sharing should be performed after informed consent is received from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and to ensure that others who have access to personal information data adhere to their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to collect and/or access specific types of personal information data and to suit applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state law, such as the health insurance flow and liability act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be processed accordingly. Thus, different privacy practices should be maintained for different personal data types in each country.

In spite of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, with respect to clinical, health-related, or physiological measurement data, the present technology may be configured to allow a user to choose to "opt-in" or "opt-out" to participate in the collection of personal information data during or at any time after service registration. As another example, the user may choose not to provide clinical, health-related, or physiological measurement data for the targeted content delivery service. As another example, the user may choose to limit the length of time that clinical, health-related or physiological measurement data is maintained or to prohibit storage or maintenance of clinical, health-related or physiological measurement data altogether. In addition to providing the "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that his personal information data will be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, risk can be minimized by limiting the data collection and deleting the data. In addition, and when applicable, included in certain health-related applications, the data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level instead of at an address level), controlling how data is stored (e.g., aggregating data among users), and/or other methods, as appropriate.

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may be implemented without accessing such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, clinical, health-related, or physiological measurement data may be displayed by inferring preferences based on non-personal information data or absolute minimum-sized personal information, such as content requested by a device associated with a user, other non-personal information available to a computer system, or publicly available information.

Claims (43)

1. A method, comprising:

at a computer system in communication with a display generation component and one or more input devices:

displaying, via the display generating component, a first user interface comprising a user-interactive graphical user interface object corresponding to a first laboratory type, wherein:

in accordance with a determination that the first laboratory type has been specified via user input received through the one or more input devices, the user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and is also provided with

In accordance with a determination that the first laboratory type has not been specified via user input, the user-interactive graphical user interface object corresponding to the first laboratory type is displayed via the display generation component without displaying a graphical indication of the difference between the first value corresponding to the first laboratory type and at least the second value corresponding to the first laboratory type.

2. The method according to claim 1, wherein:

In accordance with a determination that the first value corresponding to the first laboratory type is greater than the second value corresponding to the first laboratory type, the graphical indication has a first appearance;

in accordance with a determination that the first value corresponding to the first laboratory type is less than the second value corresponding to the first laboratory type, the graphical indication has a second appearance that is different from the first appearance; and is also provided with

In accordance with a determination that the first value corresponding to the first laboratory type is equal to the second value corresponding to the first laboratory type, the graphical indication has a third appearance that is different from the first appearance and the second appearance.

3. The method of any of claims 1-2, wherein the computer system is associated with a first user account, the method further comprising:

when performing a process configured for health related data sharing with a second user account, displaying a shared data selection user interface, wherein displaying the shared data selection user interface comprises:

in accordance with a determination that the first laboratory type has been specified via the user input, displaying a second user-interactive graphical user interface object that, when selected, causes data of the first laboratory type to be shared with the second user account upon completion of the process of configuring health-related data for sharing with the second user account; and

In accordance with a determination that the first laboratory type has not been specified via the user input, the second user-interactive graphical user interface object is relinquished from being displayed, which, when selected, causes data of the first laboratory type to be shared with the second user account upon completion of the process of configuring health-related data for sharing with the second user account.

4. A method according to claim 3, further comprising:

displaying a laboratory type sharing selection user interactive graphical user interface object during the process of configuring health related data for sharing with a second user account;

receiving input corresponding to the laboratory type sharing selection user interactive graphical user interface object;

in response to receiving the input corresponding to the laboratory type sharing selection user interactive graphical user interface object, displaying:

a third user-interactive graphical user interface object that, when selected, modifies whether to share the first laboratory-type data with a second user account upon completion of the process of configuring health-related data for sharing with the second user account; and

A fourth user-interactive graphical user interface object that, when selected, modifies whether third laboratory-type data is to be shared with a second user account upon completion of the process of configuring health-related data for sharing with the second user account.

5. The method of any one of claims 1 to 4, further comprising:

prior to displaying the first user interface:

displaying, via the display generating component, a second user interface comprising a fifth user-interactive graphical user interface object corresponding to the first laboratory type and a sixth user-interactive graphical user interface object corresponding to a second laboratory type; and

the user input specifying the laboratory type is received.

6. The method of claim 5, wherein the user input specifying the laboratory type is selected from the group consisting of:

a sustained input on the fifth user interactive graphical user interface object greater than a predetermined time,

an input corresponding to the fifth user interactive graphical user interface object, the input comprising a movement in a first direction, and

A set of one or more inputs corresponding to a first input of the fifth user-interactive graphical user interface object is included.

7. The method of any of claims 5 to 6, further comprising:

in accordance with a determination that the first laboratory type has been specified via user input received through the one or more input devices, including the fifth user-interactive graphical user interface object corresponding to the first laboratory type in a first set of one or more user-interactive graphical user interface objects displayed in a first portion of the second user interface via the display generation component; and

in accordance with a determination that the first laboratory type has not been specified via user input, the fifth user-interactive graphical user interface object corresponding to the first laboratory type is displayed via the display generation component in a second set of one or more user-interactive graphical user interface objects displayed in a second portion of the second user interface via the display generation component.

8. The method of claim 7, wherein:

ranking the first set of one or more user-interactive graphical user interface objects in the first portion of the second user interface according to a first ranking criterion, and

The second set of one or more user-interactive graphical user interface objects are ordered in the second portion of the second user interface according to a second ordering criterion.

9. The method of any of claims 5 to 8, wherein the second user interface comprises an editing user-interactive graphical user interface object that, when selected, initiates a process for modifying a specified state of the first laboratory type.

10. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method of any of claims 1-9.

11. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising:

one or more processors; and

a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of claims 1-9.

12. A computer system configured to communicate with a display generation component and one or more input devices, comprising:

apparatus for performing the method of any one of claims 1 to 9.

13. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing the method of any of claims 1-9.

14. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for:

displaying, via the display generating component, a first user interface comprising a user-interactive graphical user interface object corresponding to a first laboratory type, wherein:

in accordance with a determination that the first laboratory type has been specified via user input received through the one or more input devices, the user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and is also provided with

In accordance with a determination that the first laboratory type has not been specified via user input, the user-interactive graphical user interface object corresponding to the first laboratory type is displayed via the display generation component without displaying a graphical indication of the difference between the first value corresponding to the first laboratory type and at least the second value corresponding to the first laboratory type.

15. A computer system configured to communicate with a display generation component and one or more input devices, comprising:

one or more processors; and

a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for:

displaying, via the display generating component, a first user interface comprising a user-interactive graphical user interface object corresponding to a first laboratory type, wherein:

in accordance with a determination that the first laboratory type has been specified via user input received through the one or more input devices, the user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and is also provided with

In accordance with a determination that the first laboratory type has not been specified via user input, the user-interactive graphical user interface object corresponding to the first laboratory type is displayed via the display generation component without displaying a graphical indication of the difference between the first value corresponding to the first laboratory type and at least the second value corresponding to the first laboratory type.

16. A computer system configured to communicate with a display generation component and one or more input devices, comprising:

means for displaying, via the display generating component, a first user interface comprising a user interactive graphical user interface object corresponding to a first laboratory type, wherein:

in accordance with a determination that the first laboratory type has been specified via user input received through the one or more input devices, the user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and is also provided with

In accordance with a determination that the first laboratory type has not been specified via user input, the user-interactive graphical user interface object corresponding to the first laboratory type is displayed via the display generation component without displaying a graphical indication of the difference between the first value corresponding to the first laboratory type and at least the second value corresponding to the first laboratory type.

17. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for:

displaying, via the display generating component, a first user interface comprising a user-interactive graphical user interface object corresponding to a first laboratory type, wherein:

in accordance with a determination that the first laboratory type has been specified via user input received through the one or more input devices, the user-interactive graphical user interface object corresponding to the first laboratory type includes a graphical indication of a difference between a first value corresponding to the first laboratory type and at least a second value corresponding to the first laboratory type; and is also provided with

In accordance with a determination that the first laboratory type has not been specified via user input, the user-interactive graphical user interface object corresponding to the first laboratory type is displayed via the display generation component without displaying a graphical indication of the difference between the first value corresponding to the first laboratory type and at least the second value corresponding to the first laboratory type.

18. A method, comprising:

at a computer system in communication with a display generation component and one or more input devices:

receiving, at the computer system, a clinical data set, the clinical data set comprising:

data instance set corresponding to first health topic

A set of data instances corresponding to a second health topic different from the first health topic;

displaying, via the display generating component, a clinical data user interface, the clinical data user interface comprising:

a first user interactive graphical user interface object corresponding to the first wellness topic;

a second user interactive graphical user interface object corresponding to the second wellness topic; and

a set of data instance graphical user interface objects, wherein:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the first health topic; and is also provided with

In accordance with a determination that the second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the second health topic.

19. The method of claim 18, further comprising:

receiving, at the computer system, a second clinical data set comprising the first data instance;

after receiving the second clinical data set, displaying the clinical data user interface, wherein displaying the clinical data user interface comprises:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected and the first data instance corresponds to the first health topic, displaying a first data instance graphical user interface object corresponding to the first data instance; and

in accordance with a determination that the second user-interactive graphical user interface object is currently selected and the first data instance corresponds to the second health topic, displaying the first data instance graphical user interface object corresponding to the first data instance; and

in accordance with a determination that the first data instance corresponds to a third health topic different from the first health topic and the second health topic, a third user interactive graphical user interface object corresponding to the third health topic is displayed.

20. The method of any of claims 18-19, wherein the set of data instance graphical user interface objects comprises a second data instance graphical user interface object, wherein the second data instance graphical user interface object comprises a graphical indication of a difference between a first value corresponding to the second data instance graphical user interface object and a second value corresponding to the second data instance graphical user interface object.

21. The method of any of claims 18 to 20, wherein the set of data instance graphical user interface objects comprises a third data instance graphical user interface object, wherein the third data instance graphical user interface object corresponds to a first data instance of a first type and a second data instance of a second type.

22. The method of any of claims 18 to 21, wherein the set of data instance graphical user interface objects comprises a fourth data instance graphical user interface object, the method further comprising:

receiving user input corresponding to selection of the fourth data instance graphical user interface object while the clinical data user interface is displayed;

responsive to receiving the user input corresponding to selection of the fourth data instance graphical user interface object, displaying a laboratory user interface corresponding to the fourth data instance graphical user interface object, wherein the laboratory user interface comprises a fifth user interactive graphical user interface object corresponding to a sixth wellness topic;

receiving user input corresponding to a selection of the fifth user interactive graphical user interface object while the laboratory user interface is displayed; and

In response to receiving the user input corresponding to selection of the fifth user interactive graphical user interface object, displaying the clinical data user interface, wherein the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the sixth health topic.

23. The method of any of claims 18 to 22, wherein the first user-interactive graphical user interface object and the second user-interactive graphical user interface object are aligned along a first axis and the set of data instance graphical user interface objects are aligned along a second axis different from the first axis.

24. The method of any of claims 18 to 23, further comprising:

receiving a first user input when the first user interactive graphical user interface object is currently selected and when the set of data instance graphical user interface objects corresponding to the set of data instances corresponding to the first health topic is displayed; and

in response to receiving the first user input:

selecting the second user interactive graphical user interface object; and

the set of data instance graphical user interface objects is modified to correspond to the set of data instances corresponding to the second health topic.

25. The method of any of claims 18 to 24, wherein displaying the clinical data user interface comprises simultaneously displaying a third user-interactive graphical user interface object comprising a first visual representation of data collected via a physiological measurement sensor.

26. The method of any of claims 18 to 25, further comprising:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the clinical data user interface includes chart data corresponding to the first health topic; and

in accordance with a determination that the second user interactive graphical user interface object is currently selected, the clinical data user interface includes chart data corresponding to the second health topic.

27. The method of any of claims 18 to 26, further comprising:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the clinical data user interface includes a set of information corresponding to the first health topic; and

in accordance with a determination that the second user interactive graphical user interface object is currently selected, the clinical data user interface includes a set of information corresponding to the second health topic.

28. The method of any of claims 18 to 27, further comprising:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected and the computer system has not received one or more instances of data corresponding to a first laboratory type corresponding to the first health topic, displaying a first visual indicator corresponding to the first laboratory type; and

in accordance with a determination that the second user-interactive graphical user interface object is currently selected and the computer system has not received one or more instances of data corresponding to a second laboratory type corresponding to the second health topic, a second visual indicator corresponding to the second laboratory type is displayed.

29. The method of any of claims 18 to 28, further comprising:

receiving a second user input corresponding to a selection of a data instance graphical user interface object in the set of graphical user interface objects while the clinical data user interface is displayed;

in response to receiving the second user input, displaying a second laboratory user interface, wherein the second laboratory user interface comprises:

A third visual indicator corresponding to one or more data instances corresponding to the data instance graphical user interface object in the set of graphical user interface objects; and

a fourth user interactive graphical user interface object corresponding to a fourth wellness topic.

30. The method of any of claims 18 to 29, wherein the clinical data set includes a fourth data instance corresponding to the first health topic and not corresponding to the second health topic.

31. The method of any of claims 18-30, wherein the clinical data set includes fifth data instances corresponding to the first and second health topics.

32. The method of any of claims 18 to 31, further comprising:

while displaying the clinical data user interface, receiving a first set of one or more user inputs comprising inputs for adding a fifth health topic; and

in response to receiving the first set of one or more user inputs, the clinical data user interface is updated to include user-interactive graphical user interface objects corresponding to the fifth wellness topic.

33. The method of any of claims 18 to 32, further comprising:

While displaying the clinical data user interface, receiving a second set of one or more user inputs including an input for removing the first health topic; and

in response to receiving the second set of one or more user inputs, the clinical data user interface is updated to exclude the first user-interactive graphical user interface object corresponding to the first health topic.

34. The method of any of claims 18-33, wherein displaying the clinical data user interface includes concurrently displaying ranked user-interactive graphical user interface objects that, when selected, cause the set of data instance graphical user interface objects to be displayed within the clinical data user interface based on at least a first ranking criteria.

35. The method of any of claims 18 to 34, further comprising:

in accordance with a determination that a first subset of the set of data instance graphical user interface objects has been specified via user input received through the one or more input devices, displaying the first subset of the set of data instance graphical user interface objects in a first portion of the clinical data user interface via the display generation component; and

In accordance with a determination that a second subset of the set of data instance graphical user interface objects that is different from the first subset of the set of data instance graphical user interface objects has not been specified via user input received through the one or more input devices, the second subset of the set of data instance graphical user interface objects is displayed in a second portion of the clinical data user interface that is different from the first portion of the clinical data user interface via the display generation component.

36. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method of any of claims 18-35.

37. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising:

one or more processors; and

a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of claims 18-35.

38. A computer system configured to communicate with a display generation component and one or more input devices, comprising:

apparatus for performing the method of any one of claims 18 to 35.

39. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing the method of any of claims 18-35.

40. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for:

receiving, at the computer system, a clinical data set, the clinical data set comprising:

data instance set corresponding to first health topic

A set of data instances corresponding to a second health topic different from the first health topic;

Displaying, via the display generating component, a clinical data user interface, the clinical data user interface comprising:

a first user interactive graphical user interface object corresponding to the first wellness topic;

a second user interactive graphical user interface object corresponding to the second wellness topic; and

a set of data instance graphical user interface objects, wherein:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the first health topic; and is also provided with

In accordance with a determination that the second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the second health topic.

41. A computer system configured to communicate with a display generation component and one or more input devices, comprising:

one or more processors; and

a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for:

Receiving, at the computer system, a clinical data set, the clinical data set comprising:

data instance set corresponding to first health topic

A set of data instances corresponding to a second health topic different from the first health topic;

displaying, via the display generating component, a clinical data user interface, the clinical data user interface comprising:

a first user interactive graphical user interface object corresponding to the first wellness topic;

a second user interactive graphical user interface object corresponding to the second wellness topic; and

a set of data instance graphical user interface objects, wherein:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the first health topic; and is also provided with

In accordance with a determination that the second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the second health topic.

42. A computer system configured to communicate with a display generation component and one or more input devices, comprising:

Means for receiving a clinical data set at the computer system, the clinical data set comprising:

data instance set corresponding to first health topic

A set of data instances corresponding to a second health topic different from the first health topic;

means for displaying a clinical data user interface via the display generating component, the clinical data user interface comprising:

a first user interactive graphical user interface object corresponding to the first wellness topic;

a second user interactive graphical user interface object corresponding to the second wellness topic; and

a set of data instance graphical user interface objects, wherein:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the first health topic; and is also provided with

In accordance with a determination that the second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the second health topic.

43. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for:

Receiving, at the computer system, a clinical data set, the clinical data set comprising:

data instance set corresponding to first health topic

A set of data instances corresponding to a second health topic different from the first health topic;

displaying, via the display generating component, a clinical data user interface, the clinical data user interface comprising:

a first user interactive graphical user interface object corresponding to the first wellness topic;

a second user interactive graphical user interface object corresponding to the second wellness topic; and

a set of data instance graphical user interface objects, wherein:

in accordance with a determination that the first user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the first health topic; and is also provided with

In accordance with a determination that the second user-interactive graphical user interface object is currently selected, the set of data instance graphical user interface objects corresponds to the set of data instances corresponding to the second health topic.