User interface for shared health-related data

Abstract

The present disclosure generally relates to a user interface for managing sharing of health-related data. In some embodiments, a user interface for establishing sharing of health-related data is described. In some embodiments, a user interface for viewing and managing shared health-related data is described.

Description

[0001] This application is a divisional application of the invention patent application with application date of May 23, 2022, application number 202280040622.X, and invention name “User Interface for Shared Health-Related Data”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Patent Application No. 63 / 197,494, filed on June 6, 2021, entitled “USER INTERFACES FOR SHARED HEALTH-RELATED DATA”; U.S. Provisional Patent Application No. 63 / 197,957, filed on June 7, 2021, entitled “USER INTERFACES FOR SHARED HEALTH-RELATED DATA”; and U.S. Patent Application No. 17 / 483,380, filed on September 23, 2021, entitled “USER INTERFACES FOR SHARED HEALTH-RELATED DATA”. The contents of these patent applications are hereby incorporated by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for managing shared health-related data. Background Art

[0005] Electronic devices collect, store and access health-related information of users. Such devices provide users with the ability to manage health information and corresponding functions using electronic devices. Users can select certain health-related information to be shared with family, friends and / or health institutions via electronic devices. Summary of the invention

[0006] However, some techniques for managing shared health-related data using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0007] Therefore, the present technology provides electronic devices with faster and more efficient methods and interfaces for managing shared health-related data. Such methods and interfaces optionally supplement or replace other methods for managing shared health-related data. Such methods and interfaces reduce the cognitive burden on users and produce more effective human-computer interfaces. For battery-driven computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0008] According to some embodiments, a method is described that is performed at a computer system that communicates with a display generation component and one or more input devices. The method includes: receiving a first set of one or more inputs corresponding to a request to initiate a process for sharing a set of health-related data via one or more input devices; and in response to receiving the first set of one or more inputs: displaying a first data selection user interface via the display generation component, the first data selection user interface including: based on determining that the first data type meets the first set of criteria, a first selectable user interface object, the first selectable user interface object corresponds to the first data type and when selected, modifies the sharing state of the first data type in the process for sharing a set of health-related data; and based on determining that the second data type meets the first set of criteria, a second selectable user interface object, the second selectable user interface object corresponds to the second data type and when selected, modifies the sharing state of the second data type in the process for sharing a set of health-related data.

[0009] 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 communicating with a display generation component and one or more input devices, the one or more programs including instructions for performing the following operations: receiving a first set of one or more inputs corresponding to a request to initiate a process for sharing a set of health-related data via one or more input devices; and in response to receiving the first set of one or more inputs: displaying a first data selection user interface via the display generation component, the first data selection user interface including: based on determining that the first data type meets the first set of criteria, a first selectable user interface object, the first selectable user interface object corresponds to the first data type and when selected, modifies the sharing state of the first data type in the process for sharing a set of health-related data; and based on determining that the second data type meets the first set of criteria, a second selectable user interface object, the second selectable user interface object corresponds to the second data type and when selected, modifies the sharing state of the second data type in the process for sharing a set of health-related data.

[0010] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, the one or more programs including instructions for performing the following operations: receiving a first set of one or more inputs corresponding to a request to initiate a process for sharing a set of health-related data via one or more input devices; and in response to receiving the first set of one or more inputs: displaying a first data selection user interface via the display generation component, the first data selection user interface including: based on determining that the first data type satisfies the first set of criteria, a first selectable user interface object, the first selectable user interface object corresponds to the first data type and when selected, modifies the sharing state of the first data type in the process for sharing a set of health-related data; and based on determining that the second data type satisfies the first set of criteria, a second selectable user interface object, the second selectable user interface object corresponds to the second data type and when selected, modifies the sharing state of the second data type in the process for sharing a set of health-related data.

[0011] 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 performing the following operations: receiving a first set of one or more inputs corresponding to a request to initiate a process for sharing a set of health-related data via one or more input devices; and in response to receiving the first set of one or more inputs: displaying a first data selection user interface via the display generation component, the first data selection user interface including: based on determining that the first data type meets the first set of criteria, a first selectable user interface object, the first selectable user interface object corresponds to the first data type and when selected, modifies the sharing state of the first data type in the process for sharing a set of health-related data; and based on determining that the second data type meets the first set of criteria, a second selectable user interface object, the second selectable user interface object corresponds to the second data type and when selected, modifies the sharing state of the second data type in the process for sharing a set of health-related data.

[0012] 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: a device for receiving a first set of one or more inputs corresponding to a request to initiate a process for sharing a set of health-related data via one or more input devices; and a device for performing the following operations in response to receiving the first set of one or more inputs: displaying a first data selection user interface via the display generation component, the first data selection user interface including: based on determining that the first data type meets the first set of criteria, a first selectable user interface object, the first selectable user interface object corresponds to the first data type and when selected, modifies the sharing state of the first data type in the process for sharing a set of health-related data; and based on determining that the second data type meets the first set of criteria, a second selectable user interface object corresponds to the second data type and when selected, modifies the sharing state of the second data type in the process for sharing a set of health-related data.

[0013] 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 communicating with a display generation component and one or more input devices. One or more programs include instructions for performing the following operations: receiving a first set of one or more inputs corresponding to a request to initiate a process for sharing a set of health-related data via one or more input devices; and in response to receiving the first set of one or more inputs: displaying a first data selection user interface via a display generation component, the first data selection user interface including: based on determining that a first data type satisfies a first set of criteria, a first selectable user interface object, the first selectable user interface object corresponds to the first data type and when selected, modifies the sharing state of the first data type in the process for sharing a set of health-related data; and based on determining that a second data type satisfies a first set of criteria, a second selectable user interface object, the second selectable user interface object corresponds to the second data type and when selected, modifies the sharing state of the second data type in the process for sharing a set of health-related data.

[0014] According to some embodiments, a method performed at a computer system in communication with a display generation component is described, wherein the computer system is associated with a first user account of a first user. The method includes: displaying a health data sharing user interface via the display generation component, the health data sharing user interface including a plurality of selectable graphical user interface objects, the plurality of selectable graphical user interface objects including: a first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and a second selectable user interface object corresponding to a third user account of a third user who is receiving a second set of health-related data from the first user account.

[0015] 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 a display generation component, wherein the computer system is associated with a first user account of a first user, and the one or more programs include instructions for performing the following operations: displaying a health data sharing user interface via the display generation component, the health data sharing user interface including one or more selectable graphical user interface objects, the one or more selectable graphical user interface objects including: a first selectable user interface object, the first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and a second selectable user interface object, the second selectable user interface object corresponding to a third user account of a third user who is receiving a second set of health-related data from the first user account.

[0016] According to some embodiments, a transient computer-readable storage medium is described. The transient 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, wherein the computer system is associated with a first user account of a first user, and the one or more programs include instructions for performing the following operations: displaying a health data sharing user interface via the display generation component, the health data sharing user interface including one or more selectable graphical user interface objects, the one or more selectable graphical user interface objects including: a first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and a second selectable user interface object corresponding to a third user account of a third user who is receiving a second set of health-related data from the first user account.

[0017] According to some embodiments, a computer system configured to communicate with a display generation component is described, wherein the computer system is associated with a first user account of a first user. 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 performing the following operations: displaying a health data sharing user interface via the display generation component, the health data sharing user interface including one or more selectable graphical user interface objects, the one or more selectable graphical user interface objects including: a first selectable user interface object, the first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and a second selectable user interface object, the second selectable user interface object corresponding to a third user account of a third user who is receiving a second set of health-related data from the first user account.

[0018] According to some embodiments, a computer system configured to communicate with a display generation component is described, wherein the computer system is associated with a first user account of a first user. The computer system includes: a device for displaying a health data sharing user interface via the display generation component, the health data sharing user interface including one or more selectable graphical user interface objects, the one or more selectable graphical user interface objects including: a first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and a second selectable user interface object corresponding to a third user account of a third user who is receiving a second set of health-related data from the first user account.

[0019] 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 communicating with a display generation component, wherein the computer system is associated with a first user account of a first user. One or more programs include instructions for performing the following operations: displaying a health data sharing user interface via a display generation component, the health data sharing user interface including one or more selectable graphical user interface objects, the one or more selectable graphical user interface objects including: a first selectable user interface object, the first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and a second selectable user interface object, the second selectable user interface object corresponding to a third user account of a third user who is receiving a second set of health-related data from the first user account.

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

[0021] Thus, a faster, more efficient method and interface for managing shared health-related data is provided for devices, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for managing shared health-related data. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] 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, wherein like reference numerals designate corresponding parts throughout the several views.

[0023] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

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

[0025] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0026] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0027] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device is shown according to some embodiments.

[0028] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface that is separate from the display according to some embodiments.

[0029] Figure 5A A personal electronic device according to some embodiments is shown.

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

[0031] Figures 6A to 6T An exemplary user interface related to sharing health-related data using a computer system is shown according to some embodiments.

[0032] Figure 7 is a flow chart illustrating a method for initiating sharing of health-related data using a computer system according to some embodiments.

[0033] Figures 8A to 8P An exemplary user interface related to using a computer system to manage and view shared health-related data is shown according to some embodiments.

[0034] Fig. 9 is a flow chart illustrating a method for displaying shared health-related data using a computer system according to some embodiments. DETAILED DESCRIPTION

[0035] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0036] A computer system that provides an efficient method and interface for managing shared health-related data is needed. For example, it is advantageous to establish a sharing relationship of health-related data between users. In addition, it is advantageous to notify a user of changes in another user's health-related data. Such techniques can reduce the cognitive burden of users who share health-related data, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0037] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an exemplary device for performing techniques for management event notifications is provided. 6A to 6T An exemplary user interface for managing shared health-related data is shown. Figure 7 is a flow chart illustrating a method for managing shared health-related data according to some embodiments. 6A to 6T The user interface in is used to show the following description including Figure 7 The process of the process. FIG. 8A to FIG. 8P An exemplary user interface for displaying shared health-related data is shown. Fig. 9 is a flow chart illustrating a method for displaying shared health-related data according to some embodiments. FIG. 8A to FIG. 8P The user interface in is used to illustrate the processes described below, which include Fig. 9 process.

[0038] In addition, in the method described herein where one or more steps depend on one or more conditions being met, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions for determining the steps in the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then the ordinary technician will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on one or more conditions being met can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether the possible situation has been met without explicitly repeating the steps of the method until all conditions for determining the steps in the method have been met. It will also be understood by ordinary technicians in the art that, similar to the method with the contingent step, the system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all the contingent steps have been performed.

[0039] 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 can be named a second touch and similarly a second touch can 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 embodiments, both the first touch and the second touch are touches, but they are not the same touch.

[0040] The terms used in the description of various described embodiments in this article are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "including" and / or "comprising" are used in this specification to specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0042] 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 a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally use other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). 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 generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes 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 generate content to display content (e.g., video data rendered or decoded by display controller 156).

[0043] 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.

[0044] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0045] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

[0046] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A is a block diagram showing a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of 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 for generating tactile output on device 100 (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). These components optionally communicate via one or more communication buses or signal lines 103.

[0047] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a 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 a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at 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 a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0048] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0049] It should be understood that device 100 is merely one example of a portable multifunction device, and that 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. Figure 1A The various components shown in the EMBODIMENTS 2000 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0050] Memory 102 optionally includes high-speed random access memory, and optionally also 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 other components of device 100 to access memory 102.

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

[0052] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses 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, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

[0053] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0054] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device 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 tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (or none 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., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures and / or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an 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 is based on detected movement of a part of the user's body through the air, including movement of the user's body relative to an absolute reference (for example, the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (for example, movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (for example, a tap gesture involving moving the hand in a predetermined posture by a predetermined amount and / or speed, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).

[0055] A 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, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0056] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

[0058] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use 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 the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

[0059] The touch-sensitive display in some embodiments of touch screen 112 is optionally similar to the multi-touch-sensitive touchpad 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 a touch-sensitive touchpad does not provide visual output.

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

[0061] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0063] The device 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., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0064] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. 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 the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image is optionally obtained for video conferencing while the user views other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0065] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, 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 an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0066] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force 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 force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0067] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals 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 is optionally implemented as described in the following U.S. patent application numbers: 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, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

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

[0069] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 is optionally implemented as described in the following U.S. Patent Publication Nos.: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the 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., portrait or landscape) of the device 100.

[0070] 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 (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information related to the device's position and / or posture.

[0071] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitating communication between various hardware components and software components.

[0072] 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 circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0073] 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 contact has occurred (e.g., detecting a finger press event), determining the contact strength (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 the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.

[0074] In some embodiments, 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 a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0075] 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 motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. 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 press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

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

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

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

[0079] 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).

[0080] 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 a weather widget, a local yellow pages widget, and a map / navigation widget).

[0081] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0082] ● Contacts module 137 (sometimes called address book or contact list);

[0083] ● Telephone module 138;

[0084] ● Video conferencing module 139;

[0085] ● Email client module 140;

[0086] ●Instant messaging (IM) module 141;

[0087] ●Fitness support module 142;

[0088] ● Camera module 143 for still images and / or video images;

[0089] ●Image management module 144;

[0090] ●Video player module;

[0091] ●Music player module;

[0092] ●Browser module 147;

[0093] ●Calendar module 148;

[0094] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;

[0095] A widget creator module 150 for forming a user-created widget 149-6;

[0096] ●Search module 151;

[0097] ● Video and music player module 152, which merges the video player module and the music player module;

[0098] ●Note module 153;

[0099] ● Map module 154; and / or

[0100] ●Online video module 155.

[0101] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

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

[0103] 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, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0104] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0105] In conjunction with RF circuit 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 image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0106] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0107] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0108] In conjunction with the 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, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

[0109] In conjunction with touch screen 112, display controller 156, touch / 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, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0110] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with 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.

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

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

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

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

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

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

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

[0118] 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 performing the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0119] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs (such as computer programs (e.g., including instructions)), processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

[0120] In some embodiments, the device 100 is a device where the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a 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.

[0121] A predefined set of functions that are performed exclusively through a touch screen and / or a touch pad optionally includes navigation between user interfaces. In some embodiments, the touch pad, 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 embodiments, a touch pad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touch pad.

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

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

[0124] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by the application 136-1, a state queue for enabling a 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.

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

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

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

[0128] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

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

[0130] Hit view determination module 172 receives information related to sub-events of touch-based gestures. 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 where the sub-events should be processed. 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 a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0131] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0132] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

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

[0134] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

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

[0136] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0137] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sub-event sequence), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events (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 a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0138] In some embodiments, event definition 186 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying 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 corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.

[0139] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0140] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, 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.

[0141] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can 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.

[0142] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and executes a predefined process.

[0143] In some embodiments, the event delivery instructions 188 include a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.

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

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

[0146] It should be understood that the above discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events that define the event to be distinguished.

[0147] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

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

[0149] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0150] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference Figure 1A The memory 370 may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and may optionally include a non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 may optionally include one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores data related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, 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 a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0151] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be implemented with separate software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore 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 above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0152] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0153] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

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

[0155] ●Time 404;

[0156] ●Bluetooth indicator 405;

[0157] ●Battery status indicator 406;

[0158] A tray 408 with icons for commonly used applications, such as:

[0159] o an icon 416 of the phone module 138 labeled “Phone”, the icon 416 optionally including an indicator 414 of the number of missed calls or voicemails;

[0160] o an icon 418 of the email client module 140 labeled “Mail”, the icon 418 optionally including an indicator 410 of the number of unread emails;

[0161] o an icon 420 labeled “Browser” of the browser module 147; and

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

[0163] ● Icons for other applications, such as:

[0164] o Icon 424 labeled “Messages” of IM module 141;

[0165] o Icon 426 labeled “Calendar” of calendar module 148;

[0166] o Icon 428 labeled “Photos” of the image management module 144;

[0167] o Icon 430 labeled “Camera” of camera module 143;

[0168] o Icon 432 labeled “Online Video” of the online video module 155;

[0169] o Icon 434 labeled “Stock Market” of the stock market widget 149 - 2 ;

[0170] o an icon 436 labeled “MAP” of the map module 154;

[0171] o Icon 438 labeled “Weather” of the weather widget 149 - 1 ;

[0172] o Icon 440 labeled “Clock” of the alarm clock widget 149 - 4 ;

[0173] o an icon 442 labeled “Fitness Support” of the fitness support module 142;

[0174] o an icon 444 labeled "Notes" of the notes module 153; and

[0175] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136 .

[0176] It should be noted that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 of 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 a corresponding application icon includes the name of the application corresponding to the corresponding 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.

[0177] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0178] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0179] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap 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 by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.

[0180] Figure 5AAn exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. As an alternative or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more strength sensors for detecting the intensity of contact (e.g., touch) applied. One or more strength sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

[0181] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International patent application serial number PCT / US2013 / 040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013, published as WIPO patent publication number WO / 2013 / 169849; and International patent application serial number PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on November 11, 2013, published as WIPO patent publication number WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0182] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.

[0183] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, the device 500 may include a reference Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, 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. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.

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

[0185] 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 one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700 and 900 ( Figure 7 and Fig. 9). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are 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, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0186] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0187] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of the contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0188] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (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 contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, 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 the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0189] Attention is now turned 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.

[0190] 6A to 6T An exemplary user interface for managing shared health-related data according to some embodiments is shown. The user interface in these figures is used to illustrate the following description including Figure 7 The process of the process.

[0191] Fig. 6ADevice 600 is shown, the device includes a touch screen display 602, the touch screen display displays a health summary user interface 604 within a health application (e.g., health application) running on the device 600. Device 600 is a smart phone with one or more features of device 100, 300 and / or 500, and can be used to track health data associated with a primary user account, and other user accounts configured to receive shared health-related user data. In some embodiments, device 600 includes a sensor (e.g., accelerometer, gyroscope, GPS) for tracking health-related user data. In some embodiments, device 600 is communicating with one or more smart devices (e.g., smart watches, smart weight scales, blood glucose monitors) via a wireless communication protocol (e.g., Bluetooth and / or WiFi), and these smart devices are associated with the primary user account. In some embodiments, one or more smart devices communicating with device 600 transmit health-related user data to device 600. In some embodiments, device 600 receives one or more user inputs corresponding to manually inputting health-related user data. In some embodiments, health-related user data associated with a primary user account from a third-party application running on the device 600 may be imported for display on the health summary user interface 604 .

[0192] exist Fig. 6A, health summary user interface 604 includes various selectable affordances 604a to 604e for a primary user account associated with user Tiffany Smith and a primary user affordance 606. Primary user affordance 606 indicates that the health data displayed on health summary user interface 604 is associated with the user account of the primary user of device 600 (e.g., Tiffany Smith). Selectable health data affordances 604a to 604d are displayed in a "Favorites" portion of health summary user interface 604. Activity affordance 604a summarizes movement-related health data, such as calories burned, minutes of exercise, and hours of standing for at least one minute performed by the primary user. Heart rate affordance 604b includes heart rate measurements of the primary user. Weight affordance 604c includes the most recent weight measurement of the primary user. Step affordance 604d includes a count of how many steps the primary user has walked in a day (e.g., today). The highlighted affordance 604e is displayed in the “Highlights” portion of the health summary user interface 604 and includes a trend based on the number of steps taken by the primary user in a day over a predetermined time period (e.g., one day (e.g., today vs. yesterday), one week (e.g., 7-day trend), two weeks (e.g., this week vs. last week), one month), indicating that the primary user has increased their step count over the past week. In some embodiments, the highlighted affordance 604e is based on other types of health data, such as activity, heart rate, blood oxygen level, weight, fitness, sleep, etc. As previously described, in some embodiments, the health data displayed in affordances 604a to 604e can be collected and transmitted to device 600 by an external device (e.g., a smart watch) associated with the primary user account and in communication with device 600. In some embodiments, the health data displayed in affordances 604a to 604e can be manually entered using device 600. In some embodiments, the health data displayed in affordances 604a to 604e is imported from a third-party application.

[0193] exist Fig. 6A , device 600 also displays summary enable representation 608, sharing enable representation 610, and browsing enable representation 612 on display 602. Summary enable representation 608 is displayed in an emphasized state (e.g., bold) to indicate that health summary user interface 604 is being simultaneously displayed on device 600. In some embodiments, when sharing enable representation 610 is displayed in an emphasized state, a health sharing user interface is displayed. In some embodiments, when browsing enable representation 612 is displayed in an emphasized state, a health theme user interface is displayed and health data related to various different health data types associated with the primary user account can be viewed. Fig. 6A, the device 600 detects a tap input 650a corresponding to a selection of the sharing enable representation 610 via the touch screen display 602.

[0194] exist Figure 6B , in response to receiving a tap input 650a at a sharing affordance 610, the device 600 displays a health sharing user interface 614, and the sharing affordance 610 is displayed in an emphasized state. The health sharing user interface 614 includes a "shared with you" portion 616 having a first sharing affordance 616a and a second sharing affordance 616b. The "shared with you" portion 616 details other user accounts that are sharing their health-related data with the user account of the device 600. The first sharing affordance 616a is shown as an invitation from Matt Appleseed to receive their shared health-related data. Similar to the first sharing affordance 616a, the invitation to create and receive shared health-related data is described in more detail below. The second sharing affordance 616b corresponds to the shared health-related data of Grandma Appleseed. In some embodiments, similar to the first sharing affordance 616a, the second sharing affordance 616b is displayed on the health sharing user interface 614 as an invitation to receive the shared health-related data of Grandma Appleseed. In some embodiments, after accepting the invitation to receive Grandma Appleseed's shared health-related data, a second sharing affordance 616b is shown with a summary of Grandma Appleseed's shared health-related data, for which reference will be made to FIG. 8A to FIG. 8P Discuss in more detail.

[0195] Figure 6BThe health sharing user interface 614 also includes a “You’re Sharing With” portion 618 that details the other user accounts and / or medical organizations (e.g., healthcare providers) that are receiving shared health-related data from the primary user account associated with the device 600. In this example, the “You’re Sharing With” portion 618 includes a third sharing enablement representation 618a that indicates that Matt Appleseed is receiving one topic of shared health-related data associated with the primary user account of the device 600, and a fourth sharing enablement representation 618b that indicates that Team Medical is receiving ten topics of shared health-related data associated with the primary user account of the device 600. In some embodiments, after sending an invitation to share health-related data associated with the primary user account with another user account (e.g., Matt Appleseed’s account) and before the other user (e.g., Matt Appleseed) accepts the invitation, the third sharing enablement representation 618a is displayed in an invitation pending state, similar to Figure 6R The fifth shared capability representation is 618c.

[0196] Figure 6B The health sharing user interface 614 also includes a sharing portion 620 having an application affordance 620a and a survey affordance 620b. In some embodiments, the device 600 detects input corresponding to a selection of the application affordance 620a, and in response, displays a user interface including an application (e.g., an application installed on the device 600) that is receiving health-related data associated with a primary user account of the device 600. In some embodiments, the device 600 detects input corresponding to a selection of the survey affordance 620b, and in response, displays a user interface including a survey that is receiving health-related data associated with the primary user account of the device 600. In some embodiments, the primary user associated with the device 600 previously signed up for a survey and selected health-related data for sharing with the survey.

[0197] exist Figure 6B , device 600 receives tap input 650b corresponding to selection of sharing affordance 614a displayed on health sharing user interface 614. Figure 6C, in response to detecting tap input 650b at share affordance 614a, device 600 displays a menu including a "with people" affordance 614aa and a "with doctor" affordance 614ab. Device 600 receives tap input 650c corresponding to selection of "with people" affordance 614aa to initiate creation of an invitation to receive shared health-related data associated with a primary user account of device 600. In some embodiments, selection of "with doctor" affordance 614ab initiates a process for selecting health-related data associated with a primary user account to share with medical professionals and / or healthcare providers.

[0198] exist Fig.6D In response to receiving tap input 650c, device 600 initiates a process for sharing health-related data associated with the primary user account and displays information user interface 622. Information user interface 622 includes an overview for sharing health-related data with other user accounts. Information user interface 622 includes next enable indication 622a and cancel enable indication 622b. In some embodiments, selection of cancel enable indication 622b cancels the process for sharing health-related data. Device 600 receives tap input 650d corresponding to selection of next enable indication 622a, and in response, displays contact selection user interface 624, as shown in FIG. Fig. 6E shown.

[0199] exist Fig. 6E , the device 600 displays a contact selection user interface 624 on the touch screen display 602. The contact selection user interface 624 includes suggested contacts 624a to 624c. In some embodiments, the suggested contacts are user accounts of family members associated with the primary user account via family account sharing, user accounts of people who frequently interact with the primary user account, or a combination thereof. In some embodiments, user accounts designated as colleagues are excluded from the suggested contacts. The contact selection user interface 624 also includes a search bar 624d, where the device 600 can receive input at the keyboard 624e to search for and display specific contacts. Fig. 6E , device 600 detects a tap input 650e corresponding to a selection of suggested contact 624c (Nick Rivera), and in response, specifies Nick Rivera's user account to receive shared health-related data. In some embodiments, device 600 can receive additional input to specify more than one contact (e.g., user account) to receive shared health-related data. In some embodiments, additional instances of the process for creating an invitation to receive shared health-related data associated with the primary user account of device 600 must be completed to share health-related data with more than one contact.

[0200] exist Fig. 6F , after selecting Nick Rivera's suggested contact 624c, the device 600 displays a sharing introduction user interface 626. The sharing introduction user interface 626 includes a prompt for selecting the type of data to be included in the set of health-related data to be shared with the specified contact Nick Rivera, a selectable affordance "Back" for returning to the previous user interface, and a selectable "Cancel" affordance for canceling the process for sharing the health-related data. The sharing introduction user interface 626 also includes suggested topic affordances 626a and see all affordances 626b. The device 600 receives a tap input 650fa corresponding to a selection of the suggested topic affordances 626a, and in response, displays a data type selection user interface 628, as shown. Figure 6G Device 600 receives tap input 650fb corresponding to a selection to view all affordances 626b, and in response, displays all topics user interface 648, to which reference will be made. Figure 6T Further discussion.

[0201] exist Figure 6G , in response to detecting that a tap input 650fa selects a suggested topic affordance 626a, the device 600 displays a data type selection user interface 628. The data type selection user interface 628 includes an information portion 628a and a suggestion area containing data type affordances 628b to 628f. The information portion 628a provides details about categories, activities, and mobility with suggested data types (e.g., data types recommended by the device 600 for sharing). The data type affordances 628b to 628f each represent health-related measurements about activities and mobility. In some embodiments, the device 600 suggests data types for sharing based on the presence of user data (e.g., data types that do not have any user data are not displayed as suggestions). In some embodiments, the device 600 suggests data types for sharing based on the recency of the user data (e.g., data types containing user data that are earlier than a predetermined threshold time period (e.g., earlier than six months, earlier than one year) are not displayed as suggestions). In some embodiments, the device 600 suggests data types for sharing based on how often the user interacts with the data type (e.g., by viewing the data type or by user data entry) (e.g., data types that are used more frequently than other data types are displayed as suggestions). In some embodiments, the device 600 suggests data types for sharing based on user designation that the data type is a "favorite" data type (e.g., data that has been specifically designated via user input (e.g., "pinned" data) and is therefore displayed in some embodiments as a "favorite" data type). Fig. 6AIn some embodiments, the data type selection user interface 628 includes a "view more" enable representation, which, when selected, causes the device 600 to display a list of health-related data types related to "activity" and "mobility" that are selected to be included in a set of shared health-related data. In some embodiments, in response to selection of the "view more" enable representation, the device 600 displays a list of all health-related data types (including data types related to "activity" and "mobility") that are selected to be included in a set of shared health-related data. In some embodiments, if user data related to "activity" and "mobility" is not available (e.g., the user data does not meet at least one of the recommended criteria previously described), the device 600 abandons displaying the data type selection user interface 628.

[0202] exist Figure 6G , data type enable representations 628b through 628f each include a toggle switch in the “off” position, indicating that each data type is not currently included in the set of health-related data (e.g., health topics) for sharing with specified contacts. Device 600 detects tap input 650ga corresponding to selection of a toggle switch within data type enable representation 628b for “activity” and tap input 650gb corresponding to selection of a toggle switch within data type enable representation 628d for “steps.” In response to receiving tap input 650ga and tap input 650gb, device 600 modifies the toggle switches in data type enable representation 628b for “activity ring” and data type enable representation 628d for “steps” to be in the “on” position, as shown. Figure 6H In some embodiments, device 600 detects a tap input at an "all on" affordance 628g and, in response, modifies the toggle switch to be in the "on" position for all data type affordances 628b through 628f.

[0203] exist Figure 6H , the device 600 displays a data type selection user interface 628 on the touch screen display 602. The data type selection user interface 628 includes a data type enable representation 628b for "activity" and a data type enable representation 628d for "steps", wherein the toggle switch is in the "on" position, indicating that each of these data types is included in the set of health-related data for sharing. The device 600 detects a tap input 650h corresponding to the selection of the next enable representation 628h. In response to receiving the tap input 650h, the device 600 displays the data type selection user interface 630, as shown in FIG. Fig.6I shown.

[0204] exist Fig.6I , device 600 displays on touch screen display 602 a data type selection user interface 630 for suggesting data types associated with the basic health measurement category. Data type selection user interface 630 is similar to data type selection user interface 628 in that it includes a set of data type affordances associated with the overall categories that may be selected to be included in a set of health-related data for sharing (e.g., “Basic Health Measurements” of data type selection user interface 630 and “Activity and Mobility” of data type selection user interface 628). Figure 6G The data type affordances included in data type selection user interface 630 are suggested using criteria similar to those described for data type selection user interface 628 in Figure 6. The toggle switch included in the data type affordance of data type selection user interface 630 is shown in an "off" position, indicating that the data type is not to be included in the set of health-related data for sharing. In some embodiments, if user data related to basic health measurements is not available (e.g., the user data does not meet the requirements of the previously referenced Figure 6G If at least one recommended standard described in the specification is not met, the device 600 abandons the display of the data type selection user interface 630.

[0205] exist Fig.6I , device 600 receives a tap input 650i corresponding to selection of the next affordance 630a. Figure 6J , in response to detecting tap input 650i, device 600 displays, on touch screen display 602, data type selection user interface 632 for suggestions of data types related to the heart health category. Data type selection user interface 632 is similar to data type selection user interface 628 in that it includes a set of data type affordances related to overall categories that may be selected for inclusion in a set of health-related data for sharing (e.g., “heart health” for data type selection user interface 632 and “activity and mobility” for data type selection user interface 628). Figure 6G The data type affordances included in data type selection user interface 632 are suggested using criteria similar to those described in data type selection user interface 628 in FIG. 10 . In some embodiments, if user data related to cardiac health is not available (e.g., the user data does not meet the criteria previously described in FIG. 10 ), the user data affordances included in data type selection user interface 632 may be suggested using criteria similar to those described in data type selection user interface 628 in FIG. Figure 6G If at least one recommended standard described in the specification is not met, the device 600 abandons the display of the data type selection user interface 632.

[0206] exist Figure 6JIn the example of FIG. 6 , device 600 detects a tap input 650ja corresponding to a selection of a toggle switch included in data type enable representation 632a for heart rate to include the heart rate measurement result in a set of health-related data for sharing. In response to receiving tap input 650ja, device 600 updates the toggle switch in data type enable representation 632a for heart rate from an “off” position to an “on” position, similar to Figure 6H After detecting tap input 650ja corresponding to the selection of next enable indication 632b, device 600 also detects tap input 650jb, and in response, device 600 displays data type selection user interface 634, as shown in FIG. Figure 6K shown.

[0207] exist Figure 6K , device 600 displays data type selection user interface 634 on touch screen display 602 for suggesting data types associated with the category of “cycle tracking” (e.g., menstrual cycle). Data type selection user interface 634 is similar to data type selection user interface 628 in that it includes a set of data type affordances associated with overall categories that may be selected for inclusion in a set of health-related data for sharing (e.g., “cycle tracking” of data type selection user interface 632 and “activity and mobility” of data type selection user interface 628). Figure 6G The data type affordances included in data type selection user interface 634 are suggested using criteria similar to those described in data type selection user interface 628 in FIG. 6 . In some embodiments, if user data associated with the loop trace is not available (e.g., the user data does not satisfy the criteria previously described in FIG. 6 ), the user data affordances included in data type selection user interface 634 may be suggested using criteria similar to those described in data type selection user interface 628 in FIG. Figure 6G If at least one recommended standard described is not present, the device 600 abandons display of the data type selection user interface 634.

[0208] exist Figure 6K , device 600 receives tap input 650k corresponding to selection of next affordance 634a. Figure 6L, in response to detecting the tap input 650k, the device 600 displays a lab result user interface 636 on the touch screen display 602. The lab result user interface 636 includes a lab result portion, which includes lab result affordances 636a to 636d. The lab result affordances 636a to 636d correspond to a specific instance in which a lab test (e.g., a blood test, an allergy test) is performed and the result is received by the device 600 (e.g., via data transmission from an external device, via data transmission from an application, or via manual user input). In some embodiments, if the corresponding lab result meets the recent criteria (e.g., the lab test was performed within the past six months), the device 600 displays the lab result affordance. In some embodiments, the device 600 displays the lab result affordance for each historical lab result associated with the primary user account. In some embodiments, the device 600 receives an input corresponding to the selection of a toggle switch within the lab result affordance 636a, and in response, updates the toggle switch from the "off" position to the "on" position. In such embodiments, when the toggle switch is in the "on" position, the device 600 shares only the specific lab results corresponding to the lab result indication 636a. In some embodiments, the lab result indications 636a to 363d correspond to various types of lab test results. In such embodiments, in response to detecting an input corresponding to the selection of the toggle switch to enable sharing of a type of lab test result, the device 600 shares one or more lab results corresponding to the selected type of lab test result, including historical results of the selected type of lab test result, optionally traced back to a predetermined time period (e.g., COVID-19 test results over the past 6 months; lab results for current and previous cholesterol level tests).

[0209] exist Figure 6L , when displaying lab results user interface 636, device 600 detects tap input 6501 corresponding to selection of all affordances 636e. In some embodiments, device 600 detects input corresponding to selection of one or more lab results affordances 636a to 636d to enable sharing of one or more selected existing lab results prior to detecting tap input 6501. In response to receiving tap input 6501, device 600 displays all lab results user interface 638, as shown in FIG. Figure 6M In some embodiments, tap input 6501 causes lab result affordances 636a through 636d to be toggled, but does not cause display of all of lab result user interface 638 until another input is received selecting the “next” affordance of lab result user interface 636.

[0210] exist Figure 6M , device 600 displays an all lab results user interface 638 for enabling sharing of any future lab test results for the primary user account received by device 600. Device 600 receives a tap input 650ma corresponding to a selection of a toggle switch within the auto-share enable indication 638a. In response to receiving the tap input 650ma, device 600 updates the toggle switch from an “off” position to an “on” position and enables sharing of future lab test results received for the primary user account. In some embodiments, device 600 does not receive the tap input 650ma and does not enable sharing of future lab test results received for the primary user account. Device 600 also receives a tap input 650mb after receiving a tap input 650ma corresponding to a selection of a next enable indication 638b, and in response, displays a health alert user interface 640, as shown. Figure 6N shown.

[0211] exist Figure 6N , the device 600 displays a health alert user interface 640 on the touch screen display 602. The health alert user interface 640 includes an information section detailing the content type for sharing, including a warning about delayed delivery of the alarm, an alarm enable representation 640a for an irregular heart rhythm alarm, and an alarm enable representation 640b for a low blood pressure alarm. In some embodiments, the device 600 displays an alarm enable representation corresponding to the alarm type enabled for the main user account. In this example, the device 600 outputs an alarm after detecting an irregular heart rhythm and / or low blood pressure. Each toggle switch within the alarm enable representation 640a to 640b is shown as being in the "on" position to be included in a set of health-related data for sharing. In some embodiments, the device 600 displays a health alert user interface 640, wherein each toggle switch within the alarm enable representation 640a to 640b is in the "off" position, and the device 600 receives one or more inputs corresponding to the selection of one or more toggle switches, and in response, the selected toggle switch is updated to the "on" position. In some embodiments, device 600 detects input corresponding to a selection to skip affordance 640d and forgoes including the health alert in a set of health-related data for sharing. Device 600 detects tap input 650n corresponding to a selection of next affordance 640c and, in response, displays summary user interface 642, such as Fig.6O shown.

[0212] exist Fig.6O In FIG. 6 , device 600 displays a summary user interface 642 detailing a set of health topics selected for sharing. Summary user interface 642 includes: a data type affordance 628b for “activity”, such as FIG. 6G to FIG. 6H The data type for "number of steps" can be represented by 628d, such as FIG. 6G to FIG. 6H The data type for "heart rate" can be represented by 632a, such as Figure 6J The selected laboratory result can be indicated as 638c, corresponding to Figure 6M 638a of the automatic sharing indication; and the alarm indication 640e, corresponding to Figure 6N In some embodiments, if the alarm indicator is enabled for sharing in Figure 6L If one or more laboratory test results are selected for sharing in the summary user interface 642, the summary user interface 642 includes a corresponding Figure 6L In some embodiments, summary user interface 642 includes two alarm enable indications similar to alarm enable indication 640e, corresponding to each alarm enable indication 640a for an irregular heart rhythm alarm and alarm enable indication 640b for a low blood pressure alarm, such as Figure 6N In some embodiments, device 600 receives input corresponding to a selection of edit enable indication 642b and, in response, displays a user interface for editing topics included in a set of health-related data for sharing (e.g., excluding one or more previously selected topics from the set for sharing; including one or more topics not previously selected in the set for sharing).

[0213] exist Fig.6O , device 600 receives tap input 650oa corresponding to selection of preview affordance 642a shown on summary user interface 642. Device 600 also receives tap input 650ob at a point in time after receiving input 650oa; responses to input 650ob are discussed in more detail below. In response to detecting tap input 650oa, device 600 displays preview user interface 644, as shown in FIG. Figure 6P shown.

[0214] exist Figure 6P, device 600 displays a preview user interface 644 on touch screen display 602 that previews the format and layout of the health topic shared with specified contact Nick Rivera. In some embodiments, preview user interface 644 is an approximation of the interface that will be displayed on a device associated with user account Nick Rivera when viewing shared health data for Tiffany Smith's account (once shared). Preview user interface 644 includes a contact area 644a having a primary user affordance 606 of Tiffany Smith, similar to Fig. 6A The preview user interface 644 also includes an activity affordance 604a containing metrics for the primary user TiffanySmith, a step affordance 604d, and a heart rate affordance 604b, which are similar to those shown on the health summary user interface 604 and referenced. Fig. 6A In some embodiments, device 600 receives a swipe input and, in response, scrolls preview user interface 644 to show additional health topic affordances corresponding to the highlighted display (e.g., Fig. 6A Device 600 receives a tap input 650p corresponding to a selection of completed affordance 644b and, in response, stops displaying preview user interface 644 and redisplays Fig.6O A summary user interface 642 is provided.

[0215] Back to Fig.6O , after device 600 stops displaying preview user interface 644 and while device 600 is displaying summary user interface 642, device 600 receives tap input 650ob corresponding to selection of share affordance 642c. In response to detecting tap input 650ob, device 600 completes the process for sharing a collection of health-related data by sending an invitation to designated contact Nick Rivera to receive the shared health-related data, such as Figure 6Q In some embodiments, Fig.6O In the embodiment, the device 600 receives an input corresponding to a selection of the cancel enable indication 642d to cancel the process for sharing health-related data, and the health-related data is not shared.

[0216] exist Figure 6Q, in response to receiving a selection of sharing affordance 642c, device 600 completes the process for sharing a set of health topics and displays completion user interface 646. Completion user interface 646 includes confirmation text detailing that an invitation to receive the set of health topics has been sent to a specified contact, Nick Rivera, and a contact affordance 646a that, when selected, initiates the process of contacting Nick Rivera. Device 600 receives a tap input 650q corresponding to a selection of completed affordance 646b, and in response, returns to displaying health sharing user interface 614, as shown in FIG. Figure 6R shown.

[0217] exist Figure 6R , device 600 displays health sharing user interface 614, now with fifth sharing affordance 618c, as well as third sharing affordance 618a and fourth sharing affordance 618b, as shown in reference Figure 6B As discussed in the “You are sharing with” section 618. The fifth sharing affordance 618c indicates that there are pending invitations for five subjects to Nick Rivera to receive shared health-related data associated with the primary user account (e.g., Tiffany Smith) of the device 600. The “You are sharing with” section 618 shows the user accounts receiving the shared health data in alphabetical order, followed by the medical institutions receiving the shared health data. In some embodiments, the “You are sharing with” section 618 is organized with the most recent sharing relationships first, followed by the sharing relationships established earlier.

[0218] exist Figure 6S , device 600 continues to display health sharing user interface 614, and now Nick Rivera has accepted the invitation to receive shared health topics associated with primary user account Tiffany Smith. The fifth sharing affordance 618c no longer includes the "Invite Pending" text, and now indicates that Nick Rivera is receiving five topics of shared health-related data associated with the primary user account of device 600.

[0219] Now go to Figure 6T , the device 600 responds to receiving a request corresponding to viewing Fig. 6FThe all topics user interface 648 is displayed by a tap input 650fb corresponding to a selection of all enable representations 626b in the display. The all topics user interface 648 includes all enable representations 648a shown in an emphasized state (e.g., a selected state; a state with a border around the enable representation 648a) and existing data enable representation 648b shown in an inactive state (e.g., no border). In some embodiments, the device 600 receives an input corresponding to a selection of the existing data enable representation 648b, and in response, updates the existing data enable representation 648b to an emphasized state, updates all enable representations 648a to an inactive state (e.g., all enable representations 648a and existing data enable representation 648b are mutually exclusive toggle switches), and displays a list of health topics that include data entries corresponding to the user account of the primary user, without displaying health topics that do not include data entries corresponding to the user account of the primary user. When all enable representations 648a are shown in an emphasized state, as in Figure 6T , the all topics user interface 648 includes a list of all health topics for sharing, including health topics that have no data entries corresponding to a user account of the primary user. In some embodiments, additional filter options are displayed, such as a recent data filter or a manually entered data filter, for providing health topics based on different criteria. In some embodiments, the device 600 receives a swipe input, and in response, scrolls the all topics user interface 648 to reveal additional health topics for sharing. In some embodiments, the device 600 receives one or more inputs corresponding to selections of one or more triggers within a data type row to enable sharing of one or more health topics. In some embodiments, the device 600 also receives input corresponding to selection of a next affordance, and in response, displays a summary user interface detailing a set of health topics selected for sharing via the all topics user interface 648, similar to Fig.6O A summary user interface 642 is provided.

[0220] Figure 7It is a flowchart showing a method for managing shared health-related data using a computer system according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600) (e.g., a smart phone, a smart watch), which communicates with a display generation component (e.g., 112, 340, 504, 602) (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated or connected)) and one or more input devices (e.g., 112, 116, 350, 355, 359, 534, 536, 538, 602) (e.g., a gyroscope, an accelerometer, a microphone, and / or 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.

[0221] As described below, method 700 provides an intuitive way to manage shared health-related data. The method reduces the cognitive burden of users managing shared health-related data, thereby creating a more effective human-computer interface. For battery-powered computing devices, users are able to manage shared health-related data more quickly and more efficiently, saving power and increasing the time between battery charges.

[0222] The computer system receives (702) via one or more input devices (e.g., 602) corresponding to initiating a process for sharing a set of health-related data (e.g., as described by Figure 6B The sharing enable representation 614a is initiated by selection of a first set of one or more inputs (e.g., 650b, 650b) (e.g., tap inputs) requesting a process for sharing health-related data associated with a first user account of a first user (e.g., belonging to the first user (e.g., associated with data of the first user); a user of a computer system)).

[0223] In response to receiving the first set of one or more inputs (704), the computer system displays (706) via the display generation component (e.g., 602) a first data selection user interface (e.g., 628, 630, 632), the first data selection user interface including: determining the first data type (e.g., in Figure 6G The first selectable user interface object (e.g., a user interface that lists the suggestions on the user interface 628 of the computer system) satisfies a first set of criteria (708) (e.g., existence (e.g., data type used via manual input or via an external device that communicates with the computer system (e.g., a smart watch, a blood glucose monitor, a smart scale)); recency (e.g., data entered within the last 6 months); enabled features (e.g., health alerts)). Figure 6GThe first selectable user interface object corresponds to a first data type (e.g., activity rings, weight, low heart rate) and when selected modifies the sharing state of the first data type in the process of sharing a set of health-related data (e.g., whether data of the first data type is shared). In some embodiments, based on determining that the first data type does not meet the first set of criteria, the computer system abandons displaying the first selectable user interface object in the data selection user interface).

[0224] In response to receiving the first set of one or more inputs (704), the computer system displays (706) via the display generation component (e.g., 602) a first data selection user interface (e.g., 628, 630, 632), the first data selection user interface including: determining the second data type (e.g., in Figure 6G ) (e.g., a data type different from the first data type) satisfies the first set of criteria (710), the second selectable user interface object (e.g., Figure 6G ), the second selectable user interface object corresponds to a second data type (e.g., steps, blood oxygen, high heart rate) and when selected modifies the sharing status of the second data type in the process of sharing a set of health-related data (e.g., whether data of the second data type is shared) (modification does not affect the sharing status of the first data type). In some embodiments, based on determining that the second data type does not meet the first set of criteria, the computer system abandons displaying the second selectable user interface object in the data selection user interface. In some embodiments, the first user and the second user described with respect to method 900 perform method 700 before displaying the first selectable user interface object and the second selectable user interface object of method 900). In some embodiments, including (or not including) selectable user interface objects in the data selection user interface based on the first set of criteria met provides the user with the most relevant selectable user interface object candidates for selection without the user having to search for those candidates. Performing optimization operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0225] In some embodiments, the first set of criteria includes criteria that are satisfied when the first data type includes user data that was created or modified within a predetermined time period (e.g., Fig. 6A604a, 604b, 604c, 604d) (e.g., user data within a recent period of time (e.g., 6 months; 1 year)). In some embodiments, displaying selectable user interface objects corresponding to data types that meet creation or modification criteria allows the user to quickly identify potentially important data types and reduces the number of inputs required to identify and display potentially important data types. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0226] In some embodiments, when displaying the first selectable user interface object and / or displaying the second selectable user interface object (e.g., Figure 6G The computer system receives a second set of one or more inputs (e.g., 650ga and 650gb, 650ob). In response to the second set of one or more inputs, the computer system: completes a process for sharing a set of health-related data (e.g., Figure 6Q and sharing a set of health-related data (e.g., as shown in user interface 646 of the computer system); and sharing a set of health-related data (e.g., as shown in user interface 646 of the computer system) with at least one external computer system (e.g., a smart phone, a smart watch associated with a user different from the user of the computer system). Figure 6R ) (e.g., sharing selected health-related data associated with a first user account of a first user (e.g., belonging to the first user (e.g., associated with data belonging to the first user)) with a second account of a second user (e.g., a second user selected by the first user), wherein: based on determining that the second group of one or more inputs includes a first input corresponding to a selection of a first selectable user interface object corresponding to the first data type (e.g., 650ga), the shared set of health-related data includes shared data of the first data type (e.g., Fig.6O 628b in the “Health Topics” section of the present invention) (e.g., the first data type is shared with the selected contact); and based on determining that the second set of one or more inputs includes a second input corresponding to a selection of a second selectable user interface object corresponding to the second data type (e.g., 650gb), the shared set of health-related data includes shared data of the second data type (e.g., Fig.6O628d in the "Health Topics" section of the present invention) (e.g., the second data type is shared with the selected contact). In some embodiments, based on determining that the second set of inputs does not include the selection of the first selectable user interface object, the shared data does not include any data of the first type. In some embodiments, based on determining that the second set of inputs does not include the selection of the second selectable user interface object, the shared data does not include any data of the second type. In some embodiments, when both the first data type and the second data type are selected, the shared data includes data of both the first data type and the second data type. In some embodiments, activating health-related data sharing via a set of one or more inputs ensures that the information required to correctly share the selected data type is received, thereby ensuring correct sharing and reducing errors. Ensuring correct activation of functions and reducing errors enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0227] In some embodiments, the first type of data is selected from the group consisting of: user-entered data (e.g., Figure 6K The computer system may include, for example, a computer system that provides a plurality of data types (e.g., data types suggested on the user interface 634 of the computer system) (e.g., data manually entered via a software or hardware keyboard), data collected by one or more sensors (e.g., 168) that communicate with the computer system (e.g., sensors integrated into the computer system, sensors wirelessly connected to the computer system), data transmitted by one or more external devices (e.g., 500) (e.g., smart watches; dedicated diagnostic devices (e.g., continuous glucose monitors, sleep trackers)), and combinations thereof. In some embodiments, various data collection methods are utilized to provide the computer system with sufficient data to create data entries belonging to the data types, which enhances the operability of the computer system. Improving the operability of the device makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0228] In some embodiments, the first data type and the second data type satisfy a first set of grouping criteria (e.g., Figure 6G) (e.g., both the first data type and the second data type are classified within the first data genus (e.g., both data types are physical activity data types (e.g., total calories burned, total active minutes) or both data types are heart-related data types (e.g., EKG data or heart rate data)). In some embodiments, the first data type and the second data type do not meet the second set of grouping criteria. After displaying the first data selection user interface (e.g., 628), the computer system displays a second user selection user interface (e.g., 630), which includes: a third selectable user interface object, which corresponds to a third data type (e.g., Fig.6I and when selected, modifies a sharing state of a third data type in a process for sharing a set of health-related data, wherein the third data type satisfies the second set of grouping criteria but does not satisfy the first set of grouping criteria (e.g., Fig.6I is related to the “basic health measures” of Figure 6G ” activity and mobility ” related to) (e.g., the third data type belongs to the second data genus, but does not belong to the same data genus as the first data type and the second data type); and a fourth selectable user interface object corresponding to the fourth data type (e.g., Fig.6I ) and when selected, modifies a sharing state of a fourth data type in a process for sharing a set of health-related data, wherein the fourth data type satisfies the second set of grouping criteria but does not satisfy the first set of grouping criteria (e.g., Fig.6I is related to the “basic health measures” of Figure 6G 's "activity and mobility" (e.g., the fourth data type belongs to the same data genus as the third data type, but does not belong to the same data genus as the first data type and the second data type). In some embodiments, displaying data types based on grouping criteria enables a user to identify related data types without cluttering the user interface with unrelated data types. Providing improved visual feedback to the user without cluttering the user interface enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0229] In some embodiments, prior to displaying the first data selection user interface (e.g., 628), the computer system displays a fifth selectable user interface object (e.g., 626b) (e.g., a "View All Data Types" option). In some embodiments, the computer system receives a third set of one or more user inputs including inputs corresponding to the fifth selectable user interface object (e.g., 650fb). In response to receiving the third set of one or more user inputs, the computer system displays a third data selection user interface (e.g., 648) (e.g., an interface presenting data types belonging to multiple different data type categories (e.g., data types belonging to different general health categories)), the third data selection user interface including: a sixth selectable user interface object corresponding to the first data type (e.g., Figure 6T a toggle switch within a row of “active” data types (e.g., a data type that satisfies the first set of grouping criteria) and that when selected modifies a sharing state of the first data type in a process for sharing a set of health-related data; and a seventh selectable user interface object that corresponds to a third data type (e.g., Figure 6T A toggle switch within a row of a "weight" data type (e.g., a data type that meets the second set of grouping criteria but does not meet the first set of grouping criteria) and when selected modifies the sharing status of a third data type in the process of sharing a set of health-related data. In some embodiments, displaying a user interface that includes data types that meet different grouping criteria enables a user to quickly select one or more data types for sharing without having to view multiple group-specific user interfaces. Providing additional control options without the need to display multiple user interfaces enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0230] In some embodiments, the first data selection user interface (e.g., 628) includes an eighth selectable user interface object (e.g., a "view all" affordance similar to 626b). The computer system receives user input corresponding to the eighth selectable user interface object (e.g., in Figure 6G In response to receiving user input corresponding to the eighth selectable user interface object, the computer system displays a ninth user-selectable user interface object (e.g., a tap at 628g in FIG. 10 ) (e.g., a “view all” option that enables display of all data types in the common data type category (even data types that do not meet the initial display criteria)). Figure 6T The toggle switch within the "loop distance" of Figure 6GThe ninth user-selectable user interface object corresponds to a fifth data type and when selected modifies a sharing state of the fifth data type in a process for sharing a set of health-related data, wherein: the fifth data type satisfies the first set of grouping criteria (e.g., Figure 6G 's "activity and mobility" (e.g., the fifth data type belongs to the same data type genus as the first data type and the second data type) (in some embodiments, and the second set of sharing criteria is not met), and the fifth data type does not meet the first set of criteria (e.g., the fifth data type does not include any recent data). In some embodiments, an option to view all data types is displayed, regardless of whether the first set of criteria are met, providing the user with additional controls for sharing various data types. Providing additional control options enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0231] In some embodiments, the first selectable user interface object and the second selectable user interface object are independently selectable (e.g., by input 650ga and input 650gb, respectively) to modify the sharing state of the corresponding type of data (e.g., as Figure 6H ). In some embodiments, the user can select the first data type, the second data type (without selecting the first data type), neither, or both data types for sharing as part of a set of health-related data. In some embodiments, the user can select an "all on" user interface object that enables sharing of all suggested data types displayed on the data selection user interface.

[0232] In some embodiments, after displaying the first selection user interface (in some embodiments, after displaying the user interface for all other categories of health data except laboratory data) and before completing the process for sharing a set of health-related data, a third data selection user interface (e.g., 636) (e.g., different from the first data selection user interface; different from the second data selection user interface) is displayed, the third data selection user interface including: a first laboratory result selectable user interface object (e.g., a toggle switch within 636a), the first laboratory result selectable user interface object corresponding to a first laboratory result data type (e.g., data from laboratory results that have been transmitted to the computer system from one or more testing laboratories) and when selected, modifying the sharing state of the first laboratory result data type in the process of sharing a set of health-related data; and a second laboratory result selectable user interface object (e.g., a toggle switch within 636b), the second laboratory result selectable user interface object corresponding to a second laboratory result data type (e.g., data from laboratory results that have been transmitted to the computer system from one or more testing laboratories) and when selected, modifying the sharing state of the second laboratory result data type in the process of sharing a set of health-related data. In some embodiments, laboratory results are presented separately from other health-related data categories. In some embodiments, displaying more than one selectable user interface object for a lab result provides the system with the ability to enable sharing of multiple lab results from one user interface, thereby increasing the control options available to the user via the user interface. Providing additional control options enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0233] In some embodiments, the first lab result selectable user interface object and the second lab result selectable user interface object are (e.g., by Figure 6L 636a and a tap input on a toggle switch in 636b) can be independently selected to modify the sharing status of the corresponding type of laboratory result data. In some embodiments, the user can select the first data type, the second data type (not selecting the first data type), neither, or both data types for sharing as part of a set of health-related data.

[0234] In some embodiments, the third data selection user interface (e.g., 636) includes a tenth selectable user interface object (e.g., 636e) (e.g., a "share all" affordance). The computer system receives a user input (e.g., 650l) corresponding to the selection of the tenth selectable user interface object (e.g., 636e); in response to the user input corresponding to the selection of the tenth selectable user interface object, the computer system displays a confirmation user interface (e.g., 638) including a confirmation selectable user interface object (e.g., a toggle switch within 638a), which modifies the sharing state of all laboratory result types when selected (e.g., sharing all current and future entries about laboratory data (e.g., laboratory results)). In some embodiments, the selection of the confirmation selectable user interface object modifies the state of multiple but not all laboratory result data types (future laboratory results without past laboratory results). In some embodiments, allowing the user to select a user interface object to modify the sharing state of all laboratory results reduces the number of inputs required to share all laboratory results. Providing additional control options without requiring additional user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0235] In some embodiments, after displaying the first data selection user interface (e.g., 628) and before completing the process for sharing a set of health-related data, the computer system displays a fourth data selection user interface (e.g., 640) (e.g., different from the first data selection user interface and the second data selection user interface; different from the third data selection user interface), the fourth data selection user interface includes a tenth selectable user interface object (e.g., 640a, 640b) (e.g., "enable notification" sharing affordance), which modifies the sharing state of the first type of health-related notification (e.g., fall detection, heart-related (e.g., abnormal heart rate or ECG data), aerobic fitness, noise and / or environmental hazard exposure notification) provided at the computer system when the tenth selectable user interface object is selected (e.g., when the notification is provided at the computer system, whether such notification is shared with the selected contact). In some embodiments, the fourth data selection user interface (e.g., 640) includes multiple objects, each of which corresponds to a different type of notification (e.g., 640a, 640b). In some embodiments, allowing a user to select a user interface object to modify the sharing state of a health-related notification reduces the number of inputs and user interfaces required to share health-related notifications. Providing additional control options without requiring additional user input and user interface enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0236] In some embodiments, before displaying a first data selection user interface (e.g., 628), the computer system displays a contact selection user interface (e.g., 624), which includes: a first contactable user-selectable user interface object that satisfies a set of contact grouping criteria (e.g., 624c) (e.g., a set of criteria including a criteria that is satisfied when the first contact has a user account that shares a home account with the first user of the computer system; a set of criteria that is satisfied when the first contact has a user account that is frequently in contact with the first user of the computer system) (e.g., family, relative, important person not related to work) and when selected (e.g., by input 650e) specifies the first contactable user (e.g., NICK RIVERA of 624c) as a recipient of a set of health-related data; and a second contactable user-selectable user interface object (e.g., 624a, 624b) that satisfies the set of contact grouping criteria and when selected specifies the second contactable user as a recipient of a set of health-related data. In some embodiments, third contactable users accessible to the computer system that do not meet a set of contact grouping criteria are not included in the contact selection user interface. In some embodiments, displaying contactable user selectable user interface objects that meet a set of contact grouping criteria allows a user to quickly identify potentially important contactable users and reduces the number of inputs required to identify and display potentially important contactable users. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0237] In some embodiments, the process for sharing a set of health-related data includes specifying a single contactable user (e.g., NICK RIVERA of 624c) to receive a set of health-related data (e.g., each single iteration of the process). In some embodiments, the process can be re-initiated for a second iteration to specify that a different contactable user also receives a set of health-related data. In some embodiments, both the first contactable user (e.g., 624c) and the second contactable user (e.g., 624a, 624b) cannot be simultaneously designated as the recipient of a set of health-related data via a contact selection user interface (e.g., 624). In some embodiments, if a second contactable user selectable user interface object is currently selected, the selection of the first contactable user selectable user interface object cancels the selection of the second contactable user selectable user interface object, and vice versa.

[0238] In some embodiments, prior to completing the process for sharing a set of health-related data, the computer system displays a summary user interface (e.g., 642), wherein the summary user interface includes the data types (e.g., Fig.6O 628b, 628d, 632a, 638c, 640e) of the device, which data types have been selected to be included in the set of health-related data for sharing when the process for sharing a set of health-related data is completed. In some embodiments, a list / summary of the types of data and / or notifications that will be shared when the sharing process is completed is displayed before sharing begins. In some embodiments, a summary user interface including an indication of the selected data type for sharing is displayed to provide enhanced feedback to the user to ensure correct sharing, thereby reducing errors. Providing improved feedback and reducing errors enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0239] In some embodiments, the summary user interface includes an eleventh selectable user interface object (e.g., 642a) (e.g., a "preview" affordance). In some embodiments, the computer system receives input (e.g., 650oa) corresponding to the eleventh selectable user interface object (e.g., 642a), and in response to receiving the input corresponding to the eleventh selectable user interface object, the computer system displays a preview user interface (e.g., 644), wherein the preview user interface includes a graphical preview of a set of health-related data that will be presented to a designated recipient of the set of health-related data after completing the process for sharing the set of health-related data (e.g., Figure 6P 604a, 604d, 604b). In some embodiments, the graphical preview includes one or more visual characteristics (e.g., color, color pattern) based on the data type that has been selected for sharing via the process. In some embodiments, displaying a preview user interface that includes a graphical preview of the selected data type that will be presented to the specified recipient provides enhanced feedback to the user to ensure that the health data is shared correctly before completing the sharing process, thereby reducing errors. Providing improved feedback and reducing errors enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0240] In some embodiments, the summary user interface (e.g., 642) includes a twelfth selectable user interface object (e.g., 642b) (e.g., an "edit" affordance) that, when selected, enables modification of the data type that has been selected to be included in the set of health-related data for sharing when the process for sharing the set of health-related data is completed (e.g., removal or addition of the data type). In some embodiments, providing a selectable user interface object for modifying the selected data type for sharing enables a user to edit a set of health-related data before sharing, thereby reducing errors. Providing additional control options enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0241] In some embodiments, during a process for sharing a set of health-related data or after the process for sharing a set of health-related data is completed, the computer system displays a thirteenth user-selectable user interface object (e.g., an enable representation on user interface 642), which, when selected, initiates a process of requesting health-related data (e.g., requesting sharing of health-related data) from a second designated recipient of a set of health-related data (e.g., from a contact selected to receive a set of health data corresponding to a first user account of a first user of the computer system).

[0242] In some embodiments, the computer system completes a process for sharing a set of health-related data. In some embodiments, completion of the process for sharing a set of health-related data results in the first set of health-related data being shared with a third designated recipient (e.g., Fig. 6E selected by Figure 6R NICK RIVERA) shown in 618c within 618 of ; and completing a second process for sharing a second set of health-related data (e.g., re-initiating and completing the process after completing the process for the first time), wherein: the second process for sharing the second set of health-related data causes the second set of health-related data to be shared with a fourth designated recipient (e.g., Figure 6R The first set of health-related data is shared by MATT APPLESEED) shown in 618a within 618, and the first set of health-related data includes data types that are different from (e.g., more data types, fewer data types) from the data types included in the second set of health-related data.

[0243] It should be noted that the process described above with respect to method 700 (eg Figure 7) also apply in a similar manner to the methods 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, method 700 is performed before displaying the first selectable user interface object and the second selectable user interface object described with reference to method 900. For the sake of brevity, these details are not repeated below.

[0244] FIG. 8A to FIG. 8P An exemplary user interface for managing shared health-related data according to some embodiments is shown. The user interface in these figures is used to illustrate the following description including Fig. 9 The process of the process.

[0245] exist Fig. 8A , the device 600 displays a lock screen user interface 802 in an unlocked state (e.g., after successfully completing authentication (e.g., facial authentication)) on the touch screen display 602, thereby revealing the content of the health notification 802a. In some embodiments, the device 600 is in a locked state and displays a lock screen user interface 802 with a limited content health notification. In the unlocked state, the health notification 802a includes information about new changes in Grandma Appleseed's shared health data (e.g., weight changes) and a user-enabled representation 804 of Grandma Appleseed's contact photo (e.g., caller ID photo). In some embodiments, when a shared contact (e.g., Grandma Appleseed) creates a new data entry after a predetermined time period (e.g., the first weight entry in six weeks), the device 600 outputs a notification. In some embodiments, when the data entry pattern of the shared contact (e.g., Grandma Appleseed) changes (e.g., Grandma Appleseed has daily data entries for "steps", but has not generated data entries for "steps" in two days), the device 600 outputs a notification. In some embodiments, device 600 outputs a notification when data of a shared contact (e.g., Grandma Appleseed) follows a trend (e.g., increases, decreases, remains stable) over a predetermined time period (e.g., weight decreases over six months; heart rate increases over four weeks).

[0246] exist Fig. 8A , the device 600 detects a tap input 850a corresponding to a selection of the health notification 802a, and in response, displays a health data user interface 806, such as Figure 8B As shown. Figure 8B, device 600 displays health data user interface 806 including user affordance 804 and health data area 808. Health data user interface 806 includes user affordance 804 with a contact photo of GrandmaAppleseed to indicate that the health information shown in health data area 808 belongs to Grandma Appleseed's user account.

[0247] exist Figure 8B , on the health data user interface 806, the health data area 808 shows a time frame indicator 808a set to six months (e.g., "6M"), a graph 808b with data points 808c, and a trend indication 808d. In some embodiments, the time frame indicator 808a is set to days (e.g., "D"), weeks (e.g., "W"), or months (e.g., "M"), and the x-axis of time in the graph 808b is updated accordingly. Data point 808c corresponds to the most recent weight measurement of Grandma Appleseed received by the device 600. Trend indication 808d explains that Grandma Appleseed's weight measurement has decreased over the past six months.

[0248] exist Figure 8B , health data user interface 806 includes option affordance 806a. In some embodiments, device 600 receives input corresponding to option affordance 806a, and in response, displays an option user interface for modifying settings (e.g., notification settings) related to receiving shared health data from GrandmaAppleseed.

[0249] exist Figure 8B , health data user interface 806 also includes a contact affordance 804a that, when selected, initiates a message to Grandma Appleseed. Device 600 detects tap input 850b2 corresponding to selection of contact affordance 804a, and in response, device 600 displays a new message user interface 807 on touch screen display 602, as shown in FIG. Figure 8B1As shown. New message user interface 807 indicates that the message will be sent to Grandma Appleseed and includes a message draft area 807a pre-populated with a weight chart 808b. Message draft area 807a also includes a trend indicator 808d. In some embodiments, device 600 detects user input corresponding to keyboard 807b to compose a message (e.g., related to weight chart 808b and / or trend indicator 808d) to be included with weight chart 808b and trend indicator 808d when the message is sent. In some embodiments, device 600 detects user input corresponding to selection of send enable indication 807c to send the message including weight chart 808b and trend indicator 808d to Grandma Appleseed. In some embodiments, device 600 receives a selection corresponding to Fig. 8A similar to health notification 802a, about other user accounts and / or other trends based on the shared data type, and by reference to Figure 8B and Figure 8B1 The described process initiates a messaging conversation with an associated user account regarding health notifications.

[0250] Back to Figure 8B , device 600 detects tap input 850b corresponding to selection of health sharing affordance 806b, and in response, device 600 displays health sharing user interface 614, as shown in FIG. Figure 8C As shown. Figure 8C , device 600 displays a health sharing user interface 614 on touch screen display 602, the health sharing user interface including: a first sharing enable representation 616a as an invitation for receiving the shared health-related data of Matt Appleseed; a second sharing enable representation 616b for receiving the shared health-related data of Grandma Appleseed; a third sharing enable representation 618a for sharing the health-related data with Matt Appleseed; a fifth sharing enable representation 618c for sharing the health-related data with Nick Rivera (e.g., via initiating a sharing reference 6A to 6T a set of health-related data discussed); and a fourth sharing enable representation 618b for sharing health-related data with a medical team.

[0251] exist Figure 8C, sharing affordances 616b, 618a, and 618c each include a set of one or more colors (as indicated by the shading) that represent the overall category of the health topic being shared. Note that the first sharing affordance 616a does not include colors because the health-related data has not yet been received from Matt Appleseed. In some embodiments, the first sharing affordance 616a includes colors that serve as a preview of the category of health topics selected for sharing. In the second sharing affordance 616b corresponding to GrandmaAppleseed, four colors are shown (as indicated by the shading). The first color 810a represents activity and mobility related health topics (e.g., reference Figure 6G Detailed description of activities, fitness, steps, topics); the second color 810b represents health topics related to the heart (e.g., heart rate, heart health level, about Figure 6J Detailed topic); a third color 810c represents laboratory results (e.g., COVID-19 test results, platelet count results, reference Figure 6L Detailed topics); the fourth color 810d represents a health alarm (e.g., irregular heartbeat alarm, low blood pressure alarm, fall detection alarm, low blood oxygen alarm, reference Figure 6N In some embodiments, other colors represent other health categories, such as basic health measurements (e.g., weight, height, reference Fig.6I Detailed topics), hearing-related (e.g., ambient sound level, headphone audio level), and / or cycle tracking-related (e.g., menstruation, reference Figure 6K Detailed topics). In this example, the sharing affordances display represents up to four colors (as indicated by the shading) corresponding to various overall categories of health topics shared with or from the primary user account of device 600. In some embodiments, the colors are selected based on the overall category with the highest number of health topics selected for sharing (e.g., the colors shown represent the category with the most shared topics). In some embodiments, the colors are selected based on the overall category with the most active health topics selected for sharing. The third sharing affordance 618a indicates that one topic is being shared with Matt Appleseed and includes the first color 810a, indicating that the one shared topic is a data type related to activity and mobility. In some embodiments, the third sharing affordance 618a indicates that two (or more) health topics (e.g., aerobic fitness and steps) are being shared with Matt Appleseed, yet still only includes the first color 810a for activity and mobility related data types, indicating that the two (or more) topics are activity and mobility related data types.

[0252] exist Figure 8C, a fifth shared affordance 618c for sharing health-related data with Nick Rivera includes a first color 810a, a second color 810b, a third color 810c, and a fourth color 810d, which are the same colors as in a second shared affordance 616b for receiving health-related data from GrandmaAppleseed. For visual distinction, the formation of colors 810a through 810d in the fifth shared affordance 616c is different from the formation of colors 810a through 810d in the second shared affordance 618b. In some embodiments, the colors within a shared affordance are animated within the shared affordance so that each shared affordance is visually distinct and unique even though the same colors are included (e.g., because health topics of the same overall health category are being shared).

[0253] exist Figure 8C In addition to the colors discussed above, the second sharing affordance 616b for receiving health-related data from Grandma Appleseed includes a first notification 812a, a second notification 812b, and a third notification 812c. The first notification 812a and the second notification 812b indicate health alerts corresponding to Grandma Appleseed (e.g., low heart rate, elevated blood pressure). In some embodiments, when initiating sharing with the primary user account of device 600, Grandma Appleseed enables sharing of health alerts, similar to reference Figure 6N health alert discussed. A third notification 812c indicates that there are five additional updates related to Grandma Appleseed's health data. In some embodiments, if Grandma Appleseed has three or fewer updates, notifications corresponding to each update are detailed within the second shared affordance representation 616b. In some embodiments, notifications included within the shared affordance representation are sorted by importance (e.g., a health alert displayed before a new data entry is updated). In some embodiments, additional updates that are sorted as less important are grouped into a single notification, such as the third notification 812c.

[0254] exist Figure 8C , device 600 detects a tap input 850c corresponding to a selection of second sharing affordance 616b, and in response, displays a shared data user interface 814, such as Fig.8D As shown. Figure 8C , device 600 detects tap input 850d corresponding to selection of view invitation affordance 616aa within first sharing affordance 616a, and in response, displays invitation user interface 816, such as Figure 8FIn some embodiments, device 600 receives input corresponding to a selection of dismissal affordance 616ab within first sharing affordance 616a, and in response, declines to receive Matt Appleseed's invitation to share health data. In some embodiments, prior to displaying first sharing affordance 616a, Matt Appleseed initiates a process for sharing a set of health-related user data, similar to that described in reference to FIG. 6A to 6T The process is repeated and Tiffany Smith (eg, the primary user account of device 600) is selected as the designated recipient.

[0255] exist Fig.8D In response to receiving tap input 850c, device 600 displays a shared data user interface 814 for viewing health data shared by Grandma Appleseed and the primary user account of device 600. The shared data user interface 814 includes a user affordance representation 804 with a contact photo (e.g., a caller ID photo) of Grandma Appleseed to indicate that the displayed health data is associated with Grandma Appleseed. In some embodiments, device 600 receives input corresponding to option affordance representation 806a, and in response, displays an option user interface for modifying settings related to receiving shared health data from Grandma Appleseed (e.g., notification settings). The shared data user interface 814 also includes a message affordance representation 816a and a call affordance representation 816b, which, when selected, initiate a message or a phone call to Grandma Appleseed, respectively. In some embodiments, if Grandma Appleseed shares a location with a primary user account of device 600 and device 600 receives input corresponding to a selection of location affordance 816c, device 600 displays a location user interface showing the location of Grandma Appleseed. In some embodiments, device 600 receives input corresponding to a selection of contact affordance 816d and, in response, displays a contact user interface for Grandma Appleseed.

[0256] exist Fig.8D , the shared data user interface 814 includes a first color 810a, a second color 810b, a third color 810c, and a fourth color 810d (all represented by hatching) to indicate the overall category of health topics shared by Grandma Appleseed. The health topics shared by Grandma Appleseed are displayed on the shared data user interface 814, which spans Fig.8D and Fig. 8EGrandma Appleseed's shared health topics include: health alerts, such as low heart rate alert indicator 814a (corresponding to Figure 8C The first notification 812a) and the alarm indication 814b of the increased blood pressure (corresponding to Figure 8C In some embodiments, device 600 detects input corresponding to selection of a health topic indicator and, in response, displays a health data user interface detailing historical data entries for the health topic, similar to Figure 8B The device 600 detects the swipe input 650e and, in response, scrolls the shared data user interface 814 to show additional health-themed affordances, such as Fig. 8E shown.

[0257] exist Fig. 8E , shared data user interface 814 also includes an alarm history affordance 814h that indicates that Grandma Appleseed has received five low heart rate alarms (e.g., notifications) in the past. In some embodiments, device 600 detects input corresponding to selection of alarm history affordance 814h and, in response, displays an alarm history user interface that records past health alarms associated with Grandma Appleseed's low heart rate.

[0258] Now go to Figure 8F , the device 600 responds to receiving Figure 8C d and displays an invitation user interface 818 on the touch screen display 602. The invitation user interface 818 includes informational text and a health data topic selected for sharing from Matt Appleseed. The data types selected for sharing with the primary user account of the device 600 are activity 818a, step count 818b, and heart rate 818c. In some embodiments, the device 600 receives an input corresponding to the cancel enable indication 822, and in response, the device 600 stops displaying the invitation user interface 818 and returns to displaying the health sharing user interface 614, such as Figure 8C In some embodiments, device 600 receives input corresponding to a selection to reject affordance 820, and in response, device 600 does not allow receipt of shared health data from Matt Appleseed, stops displaying invitation user interface 818, and returns to displaying health sharing user interface 614, as shown. Figure 8CAs shown, there is no first shared enable indication 616a.

[0259] exist Figure 8F , device 600 receives tap input 850f corresponding to a selection to accept affordance 818d and, in response, enables receipt of shared health data from Matt Appleseed. Figure 8G In addition to being able to receive the shared health data of Matt Appleseed, the device 600 also displays a notification setting user interface 624 for enabling notifications related to the health data of Matt Appleseed, similar to Fig. 8A Health notification 802a. In some embodiments, notifications for healthcare purposes must be enabled before notifications specific to health sharing are enabled (e.g., received). Notification settings user interface 624 includes information text detailing that the notification may not be delivered immediately due to lack of connection (e.g., the sender or recipient has no cellular service, Wi-Fi, Bluetooth). Device 600 detects tap input 650g corresponding to a selection to enable notifications enable indication 826, and in response, device 600 enables display of notifications related to shared health data from Matt Appleseed. In some embodiments, device 600 detects input corresponding to a selection that is not now enable indication 828, and in response, device 600 abandons enabling notifications related to shared health data from Matt Appleseed while continuing to receive shared health data from Matt Appleseed.

[0260] exist Figure 8H , device 600 displays health sharing user interface 614 after accepting an invitation to receive shared health data from Matt Appleseed (in some embodiments, in response to input 850g). Matt Appleseed's first sharing affordance 616a and Grandma Appleseed's second sharing affordance 616b are displayed in alphabetical order in a "Shared with You" section 616. In some embodiments, the sharing affordances are arranged based on the recency of establishing the sharing relationship (e.g., the first sharing affordance 616a is listed before the second sharing affordance 616b). In some embodiments, the sharing affordances can be rearranged to accommodate the preferences of the primary user of device 600.

[0261] exist Figure 8H , the first shared affordance 616a for Matt Appleseed includes information corresponding to activity and mobility-related health topics (e.g., Figure 8Factivity 816a and step count 816b) and a first color 810a (shown as hatched) corresponding to a heart-related health topic (e.g., Figure 8F In some embodiments, the size of the color representing a category is set based on the number of health topics shared from that category (e.g., the first color 810a is displayed in two-thirds of the area around the contact photo, representing two of the three shared topics, while the second color 810b is displayed in one-third of the area around the contact photo).

[0262] exist Figure 8H , Matt Appleseed's first shared affordance 616a includes a fourth notification 812d indicating that Matt Appleseed's step count has increased, and a fifth notification 812e indicating that Matt Appleseed's heart rate has decreased. In some embodiments, trend updates similar to fourth notification 812d and fifth notification 812e are grouped as "other updates" when there are more updates than space to display, similar to third notification 812c. In some embodiments, health alerts such as first notification 812a and second notification 812b are displayed in preference to trend updates. In some embodiments, when viewing Fig.8D and Fig. 8E After viewing the shared health data of Grandma Appleseed, the first notification 812a, the second notification 812b, and the third notification 812c are no longer displayed in the second sharing enable representation 616b for Grandma Appleseed (e.g., the notifications are cleared after viewing the shared user's health data).

[0263] exist Figure 8H , device 600 detects tap input 850h corresponding to selection of fifth sharing affordance 618c of Nick Rivera, and in response, displays sharing management user interface 830, as shown in FIG. Fig.8I As shown. Figure 8H , the device 600 receives the swipe input 850i and, in response, scrolls the health sharing user interface 614 to display an additional portion of the health sharing user interface 614, such as Figure 8N As shown. Figure 8H , the device detects a tap input 850j corresponding to a selection of the summary affordance 608 and, in response, displays the summary user interface 604, as shown in FIG. Figure 8P shown.

[0264] exist Fig.8I, in response to receiving tap input 850h, device 600 displays sharing management user interface 830 for viewing and modifying health data associated with a primary user account shared from device 600 to Nick Rivera, as indicated by user enable indication 831, with Nick Rivera's contact photo and text indicating that the health data has been shared for 90 days. Sharing management user interface 830 includes preview enable indication 830a and stop enable indication 830b, which when selected causes device 600 to stop sharing a collection of health-related data shared from device 600 to Nick Rivera. Device 600 detects tap input 850k corresponding to selection of preview enable indication 830a, and in response, displays preview user interface 644, to which is displayed information about the health data. Figure 8J Further discussion.

[0265] exist Fig.8I , sharing management user interface 830 includes a first color 810a, a second color 810b, a third color 810c, and a fourth color 810d (all represented by hatching) to indicate the overall category of health topics shared with Nick Rivera. Sharing management user interface 830 also includes a health topics portion having an affordance corresponding to the type of data initially selected for sharing with Nick Rivera, such as Fig.6O . Activity enable indication 830c indicates that activity data is collected via a watch (e.g., an external device that communicates with device 600) and includes a removal enable indication for removing activities from the health topic shared with Nick Rivera. Unlike activity enable indication 830c, step enable indication 830d does not explicitly describe the device collecting the data. In some embodiments, the absence of an indication of an external device for data collection for a particular health topic means that data for that health topic is collected by device 600. Sharing management user interface 830 also includes a heart rate enable indication 830e with a "watch only" indication that data for the heart rate health topic is collected by and can only be obtained with an external smart watch. Activity indicator 830c includes a similar “watch only” indication, while lab results indicator 830f and health alert indicator 830g do not include a “watch only” indication because data related to lab results and health alerts may be collected via an external smartwatch and / or other methods (e.g., manual input from a user; collected via sensors of device 600; imported from other health and healthcare applications; collected by a device configured to communicate with device 600).

[0266] exist Fig.8I, device 600 detects tap input 8501 corresponding to a selection of a remove affordance within step affordance 830d, and in response, device 600 stops sharing health data related to Nick Rivera's steps, as shown in FIG. Figure 8M Device 600 also detects a tap input 850m corresponding to a selection of add theme affordance 832 and, in response, displays all theme user interface 648, as shown. Figure 8K shown.

[0267] Now go to Figure 8J , in response to receiving a Fig.8I The preview affordance in FIG. 830a indicates the selected tap input 850k, and the device 600 displays a preview user interface 644. The preview user interface 644 is similar to the reference Figure 6P The preview user interface 644 is shown in FIG. 6 and includes a primary user affordance 606 to indicate that the preview user interface 644 is showing Tiffany Smith's health data. The preview user interface 644 includes a first color 810a, a second color 810b, a third color 810c, and a fourth color 810d (all represented by hatching) to indicate the general category of health topics that Tiffany Smith (e.g., the primary user account of device 600) and Nick Rivera share. The colors on the preview user interface 644 have been animated to be in a state corresponding to the health data of Tiffany Smith. Fig.8I The arrangements shown on the sharing management user interface 830 are different arrangements.

[0268] exist Figure 8J , preview user interface 644 includes highlighted affordance 604e prior to other health data affordances, such as active affordance 604a. In some embodiments, highlighted affordance 604e is shown after the other health data affordances. In some embodiments, device 600 receives input to scrolling preview user interface 644 and, in response, displays additional health data affordances corresponding to additional health topics shared with Nick Rivera. Highlighted affordance 604e and active affordance 604a are the same health data affordances shown on health summary user interface 604, for which reference will be made to FIG. Figure 8P Further discussion. In some embodiments, device 600 receives input corresponding to a "done" affordance and, in response, stops display of preview user interface 644 and returns to displaying Fig.8I A shared management user interface 830 is provided.

[0269] Now go to Figure 8K , the device 600 responds to the corresponding Fig.8IThe tap input 850m of the Add Theme affordance 832 selection displays the All Themes user interface 648. The All Themes user interface 648 is similar to the reference Figure 6T Those described. All topics user interface 648 includes all affordances 648a shown in an emphasized state (e.g., a selected state), and existing data affordances 648b shown in an inactive state. In some embodiments, device 600 receives input corresponding to a selection of existing data affordances 648b, and in response, updates existing data affordances 648b to an emphasized state and displays a list of health topics containing data entries corresponding to the primary user's user account.

[0270] exist Figure 8K , all topics user interface 648 includes an activity affordance 648c in which a toggle switch is shown in the “on” position, indicating that the activity is a data topic shared by device 600. In some embodiments, device 600 detects a swipe input and, in response, scrolls all topics user interface 648 to display additional data topic affordances, such as an affordance for heart rate with the toggle switch in the “on” position. Device 600 detects a tap input 850n corresponding to a selection of a toggle switch within body temperature affordance 648d. In response to receiving the tap input 850n, device 600 updates the toggle switch from the “off” position to the “on” position, as shown. Figure 8L shown.

[0271] exist Figure 8L , device 600 displays all themed user interfaces 648 with body temperature affordance 648d, showing the toggle switch in the “on” position, indicating that body temperature data entry is enabled for sharing with Nick Rivera from the primary user account of device 600. In some embodiments, device 600 receives input corresponding to selection of a toggle switch within activity affordance 648c, and in response, deactivates sharing of health data associated with the activity and updates the toggle switch to the “off” position. Device 600 detects tap input 650 corresponding to selection of completion affordance 648e, and in response, cancels (e.g., stops displaying) all themed user interfaces 648.

[0272] exist Figure 8M In the example, after eliminating all the theme user interfaces 648, the device 600 displays a shared management user interface 830 with an updated health theme portion, the updated health theme portion including a temperature indicator 830h and not including a step indicator 830d, the updated health theme portion in Fig.8I810e is removed from the shared health topic. The body temperature indicator 830h includes a note that the data entry of the body temperature was manually entered into the device 600. The sharing management user interface 830 now includes a fifth color 810e, as well as a second color 810b, a third color 810c, and a fourth color 810d (all represented by hatching) to indicate the overall category of updates to the health topic that Tiffany Smith (e.g., the primary user account of the device 600) is now sharing with Nick Rivera. The colors 810b to 810e are also animated into the new form on the sharing management user interface 830.

[0273] Now go to Figure 8N , the device 600 responds to receiving Figure 8H 850i of the health sharing user interface 614 is scrolled upward to display the health sharing user interface 614. The fifth sharing affordance 618c for sharing health-related data with Nick Rivera is updated to include a fifth color 810e (indicated by hatching). The health sharing user interface 614 includes a fifth color 810e similar to the reference numeral 810e. Figure 6B The device 600 detects a tap input 850p corresponding to the selection of the application enablement representation 620a and, in response, displays a display having a function of receiving a selection. Fig.8O In some embodiments, device 600 detects input corresponding to selection of survey enable representation 620b, and in response, displays a user interface including a survey that is receiving health-related data associated with the primary user account of device 600, similar to Fig.8O Application user interface 836 of information affordance 834 is displayed. In some embodiments, a primary user associated with device 600 has previously signed up for a research study and selected health-related data for sharing with the research study. In some embodiments, device 600 detects input corresponding to selection of information affordance 834 and, in response, displays an information user interface regarding sharing health-related data.

[0274] exist Fig.8O , device 600 displays an application user interface 836 having a selectable application affordance corresponding to an application that receives health data associated with a primary user account of device 600. In some embodiments, device 600 receives input corresponding to a selection of the application affordance and, in response, displays an application settings user interface for modifying the health data shared with the application.

[0275] Now go to Figure 8P, the device 600 responds to detecting the corresponding Figure 8H 608 of summary affordance 608 is selected and tap input 850j is displayed to display health summary user interface 604. Health summary user interface 604 includes primary user affordance 606, which indicates that the health data displayed on health summary user interface 604 is associated with the user account of the primary user of device 600 (e.g., Tiffany Smith). The active affordance 604a and highlighted affordance 604e shown on health summary user interface 604 are associated with the user account of the primary user (e.g., Tiffany Smith) of device 600. Figure 8J The health summary user interface 604 includes the same health topics as those shared by Tiffany Smith's Nick Rivera in . Figure 8J Additional health topic indicators (e.g., heart rate indicator 604b, weight indicator 604c, and step indicator 604d) are shown in the preview user interface 644 because these health topics were not included in the set of health-related data types selected for sharing with Nick Rivera.

[0276] Fig. 9 It is a flowchart showing a method of displaying a user interface of shared health-related data using a computer system according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 600) (e.g., a smart phone, a smart watch), and the computer system is associated with a display generation component (e.g., 112, 340, 504, 602) (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated or connected)), wherein the computer system is associated with a first user account of a first user (e.g., belonging to the first user (e.g., associated with data about the first user)). In some embodiments, the computer system is associated with only a single user account (e.g., a login account) for health data at any given time. Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0277] As described below, method 900 provides an intuitive way to display a user interface for shared health-related data. The method reduces the cognitive burden of users viewing shared health-related data, thereby creating a more effective human-computer interface. For battery-powered computing devices, users are able to view shared health-related data more quickly and more efficiently, saving power and increasing the time between battery charges.

[0278] The computer system (e.g., 600) displays (902) via a display generating component (e.g., 602) a health data sharing user interface (e.g., 614), the health data sharing user interface including a plurality of selectable graphical user interface objects, the plurality of selectable graphical user interface objects including: a first selectable user interface object (904) (e.g., 616b) corresponding to a second user account (e.g., GRANDMA APPLESEED of 616b) (e.g., a user other than the computer system; a user of the second computer system) that is sharing a first set of health-related data (e.g., data types 814a to 814h shown on the user interface 814) (e.g., medical and / or laboratory data related to the user's health; one or more types of data related to health; health data specific to the second user; health data that does not include the first user's data) with a first user account (e.g., a user of the computer system); and a second selectable user interface object (906) (e.g., 618c) corresponding to a second user account (e.g., GRANDMA APPLESEED of 616b) that is receiving a second set of health-related data (e.g., health topics listed on the user interface 642) from the first user account; Fig.8I 830c to 830g) (e.g., medical and / or laboratory data related to the user's health; one or more types of data related to health; health data specific to the first user; health data that does not include data of the second user and / or the third user) of a third user (e.g., NICKRIVERA of 618c) (e.g., a user different from the computer system; a user of the second computer system; a user of the third computer system). In some embodiments, the second set of health-related data is different from the first set of health-related data. In some embodiments, the second user account and the third user account are the same. In some embodiments, the second user account and the third user account are different. In some embodiments, method 700 is used to establish (e.g., at a computer system) a health-related data sharing relationship from the second user account to the first user account and from the first user account to the third user account. In some embodiments, a selectable user interface object corresponding to an account of a user who is sharing health-related data with the computer system and / or receiving health-related data from the computer system is displayed to provide visual feedback to the user for the sharing status. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0279] In some embodiments, the health data sharing user interface (e.g., 614) includes: a fourth selectable user interface object (e.g., Figure 8H 616a), the fourth selectable user interface object corresponds to sharing a third set of health-related data (e.g., such as Figure 8F 818a, 818b, 818c of ) (e.g., medical and / or laboratory data related to the user's health; one or more types of data related to health; health data specific to a second user; health data that does not include data of the first user) of a fourth user (e.g., MATTAPPLESEED of 616a) (e.g., different from the user of the computer system and the second user). In some embodiments, displaying a selectable user interface object corresponding to the account of the user who is sharing health-related data with the computer system provides the user with visual feedback of the account shared with the user. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0280] In some embodiments, the health data sharing user interface (e.g., 614) includes: a fourth selectable user interface object (e.g., 618a) corresponding to receiving a fourth set of health-related data (e.g., such as Figure 8C In some embodiments, a health-related data sharing relationship is established for the fifth user account (e.g., "1 topic" shown in 618a of ) (e.g., medical and / or laboratory data related to the user's health; one or more types of data related to health; health data specific to the first user; health data that does not include data of the second user and / or third user). In some embodiments, method 700 is used (e.g., at the computer system) to establish a health-related data sharing relationship for the fifth user account. In some embodiments, displaying a selectable user interface object corresponding to the account of the user who is receiving health-related data from the computer system provides the user with visual feedback of the account that the user is sharing. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0281] In some embodiments, the health data sharing user interface (e.g., 614) includes: based on determining that the first set of health-related data includes health-related notification data that meets a set of notification display criteria (e.g., the notification is recent, the notification is unread), a health-related notification indication (e.g., 812a, 812b) associated with the second user (e.g., a notification of a change in the health status of the second user (e.g., a health alert (e.g., a low heart rate)); based on determining that the first set of health-related data includes health-related data that meets a set of recency criteria (e.g., the data is generated within a predetermined time period (e.g., 1 day, 1 week, 1 month), and the data is received after the health data sharing user interface was last displayed), a recent health data indication (e.g., 812c) associated with the second user (e.g., a graphical object presenting new data); and based on determining that the first set of health-related data includes health-related data that meets a set of change criteria (e.g., the data corresponds to an existing health-related value (e.g., a physiological parameter A device may include a display of changed health-related data (e.g., laboratory result data; physiological data) related to the second user (e.g., weight, blood sugar level, blood pressure; additional exercise (e.g., calories burned, steps walked)), a changed health data indication (e.g., 812d, 812e) related to the second user (e.g., a graphical object presenting the changed data (in some embodiments, including a comparison with a previous value of the data (e.g., a trend comparison comparing the data value of the first time period to the data value of the second time period))). In some embodiments, displaying a health-related notification indication provides feedback to the user as to whether the health-related data being shared by another user meets a set of criteria. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0282] In some embodiments, a computer system receives a set of one or more inputs (e.g., including Figure 8B and / or Fig.8D An input at 806a for displaying an options user interface; Figure 8G850g) (in some embodiments, a set of one or more inputs includes at least one input received when displaying a configuration user interface); in response to receiving a set of one or more inputs, the computer system modifies (e.g., enables or disables) a display configuration of an indication type selected from the group consisting of the following (e.g., a configuration that controls whether an indication of the indication type is displayed): an indication type corresponding to a health-related notification indication (e.g., 812a, 812b), an indication type corresponding to a recent health data indication (e.g., 802a), and an indication type corresponding to a changed health data indication (e.g., 812c, 812d, 812e). In some embodiments, modifying the display configuration of the indication type via a set of one or more inputs provides the user with additional controls for enhancing visual feedback. Providing additional control over displayed content enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, indications are organized by indication type and / or the recency of data associated with the indication.

[0283] In some embodiments, the instructions included in the health data sharing user interface are organized by type of instruction (e.g., in Figure 8H 812a and 812b shown at the top of 616b in (e.g., any health-related notification indications first, then any recent health data indications, followed by any changed health data indications). In some embodiments, the indications can occupy no more than a predetermined maximum amount (e.g., lines, area) of the user interface.

[0284] In some embodiments, a first indication (e.g., 812d, 812c) (e.g., a single first indication) is used to indicate multiple data instances that meet a set of notification display criteria, a set of recency criteria, and / or a set of changed health data indications. In some embodiments, after a maximum number of discrete (e.g., one-to-one indications) indications are displayed, additional data that meets the criteria is grouped into a single indication (e.g., a single indication of "10 other updates"). In some embodiments, providing indications indicating multiple instances of data that meet a set of criteria reduces the amount of indications provided to the user, thereby tidying up the user interface. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0285] In some embodiments, a set of change criteria includes criteria that are met when a first set of health-related data (e.g., step data corresponding to 812d; heart rate data corresponding to 812e; step data corresponding to 604e) includes data indicating that a first health-related parameter (e.g., a health-related measurement or value (e.g., heart rate, calories burned, blood sugar level, weight) undergoes a threshold amount of change (e.g., the difference in bar height between Sunday and Saturday in 604e) (e.g., decreases or increases (e.g., average, total, periodic (e.g., daily over a period of time)) a minimum amount) over at least a threshold amount of time (e.g., "7 days" as in 604e) (e.g., 5 days, a week, a month, six months, a year). In some embodiments, the health data sharing user interface includes a trend indication that shows significant changes in health-related parameters of users who share data with users of the computer system. In some embodiments, providing an indication of data that meets the threshold criteria provides the user with feedback on potentially important portions of the health data without cluttering the user interface with data that does not meet the threshold criteria. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0286] In some embodiments, when the first set of health-related data includes data indicating that the health-related parameter has undergone a change by a threshold amount, an indication is also provided to the second user at an external computer system associated with the second user.

[0287] In some embodiments, a set of change criteria includes a criterion that is satisfied when an average value (in some embodiments, median, mode value, noise-corrected average value) of a second health-related parameter in a first set of health-related data within a first time period (e.g., the "past 7 days" in 604e) differs from an average value of the second health-related parameter within a second time period (e.g., the 7 days before the "past 7 days" in 604e) (e.g., a time period of the same length as the first time period, a time period of a different length than the first time period, a time period continuous with the first time period (e.g., immediately before or after), the second time period being a predetermined length / time window (e.g., a 4-week time window (or a 26-week time window) that together with the first time period is equal to or greater than a first predetermined difference (e.g., a clinically and / or empirically determined significantly large value (e.g., a clinically significantly large value)), wherein the first time period and the second time period are sub-portions of the time window that together constitute the entire window ) time period. In some embodiments, if the user experiences a significant change between a first sub-period (e.g., an early period) and a second sub-period (e.g., a late period) of a predetermined time window (e.g., a 4-week window, a 26-week window), an indication of the changed health data may be issued / provided. In some embodiments, the early and late periods are determined based on the most obvious single change in the predetermined time window (e.g., the most obvious one-day change). In some embodiments, providing an indication of data that meets the average standard provides the user with feedback about potentially important portions of the health data without cluttering the user interface with data that does not meet the average standard. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0288] In some embodiments, if (e.g., when determined based on) the difference between the average values ​​of a first time period and a second time period for a third health-related parameter (e.g., a different parameter that is clinically related to the second health-related parameter (e.g., calories burned in a day and steps walked in a day) is greater than the difference of a first determined amount, then the difference between the average values ​​of the first time period and the second time period is less than the difference of the first determined amount but greater than the difference of the second amount, a criterion in a set of change criteria is satisfied. Thus, in some embodiments, a more "relaxed" difference / change notification threshold may result in a change notification for a given health-related parameter if the associated health-related parameter satisfies the "unrelaxed" threshold. In some embodiments, a notification based on satisfying a relaxed threshold for a health-related parameter also indicates the associated health-related parameter satisfying the "unrelaxed" threshold.

[0289] In some embodiments, a first selectable user interface object (e.g., 616b) has a first visual characteristic (e.g., a color represented by hatching 810a to 810e) (e.g., the color and / or color pattern of the object, the shape of the object, the size of the object), the first visual characteristic: based on determining that a first set of visual characteristic display criteria are satisfied, wherein the first set of visual characteristic display criteria include criteria that are satisfied when the first set of health-related data includes a first data type (e.g., 814d) (e.g., physical activity data, heart-related data, blood glucose data), the first visual characteristic includes a first value of the first visual characteristic (e.g., a specific color (e.g., red, blue, green) or a color pattern (red and blue, green and orange)). In some embodiments, based on determining that the first set of health-related data does not include the first data type, the first visual characteristic does not include the first value of the first visual characteristic. In some embodiments, a first selectable user interface object (e.g., 616b) has a first visual characteristic (e.g., a color represented by hatching 810a to 810e) (e.g., the color and / or color pattern of the object, the shape of the object, the size of the object), the first visual characteristic: based on determining that a second set of visual characteristic display criteria are satisfied, wherein the second set of visual characteristic display criteria include criteria that are satisfied when the first set of health-related data includes a second data type (e.g., 814a, 814f) (e.g., different from the first data type), the first visual characteristic includes a second value of the first visual characteristic (e.g., 810b) (e.g., a specific color (e.g., red, blue, green) or color pattern (red and blue, green and orange)). In some embodiments, displaying a selectable user interface object with a visual characteristic based on a set of health-related data provides feedback to the user about the type of data included in the set of health-related data. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and additionally, by enabling the user to use the device more quickly and efficiently, this may also reduce power usage and extend the battery life of the device.

[0290] In some embodiments, the first set (and in some embodiments, the second set) of visual characteristic display criteria include criteria that are met when the first visual characteristic does not include (e.g., includes) more than a predetermined number (e.g., 3, 4, 5, 6) of other values ​​(e.g., other colors) of the first visual characteristic (e.g., 4 colors indicated by 810a to 810d of 616b; Figure 8M In some embodiments, the second user interface object may include a predetermined maximum number of values ​​for the property (e.g., no more than 4 colors, each color corresponding to a type of data being shared).

[0291] In some embodiments, the first visual characteristic includes a predetermined number of values ​​of the first visual characteristic (e.g., 4 colors indicated by 810a through 810d of 616b; Figure 8M ), and the values ​​of the included first visual characteristics correspond to the data types that are most frequently used (e.g., most frequently selected for sharing, most frequently collected / available) in the second set of health-related data. In some embodiments, limiting the value of the first visual characteristic provides feedback to the user about the potentially important types of data included in a set of health-related data without cluttering the display with additional visual characteristic values. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0292] In some embodiments, the first visual characteristic of the first selectable user interface object includes a first value and a second value of the first visual characteristic (e.g., the four colors indicated by 810a through 810d of 616b; the four colors indicated by 810a through 810d of 616b; Figure 8M In some embodiments, the computer system displays the image in the form of at least a first visual state and a second visual state (e.g., FIG. 8I to FIG. 8JIn some embodiments, the display of the first visual characteristic of the first selectable user interface object is animated over time (e.g., position changes of 810a to 810d in ). In some embodiments, the first selectable user interface object and the fifth selectable user interface object corresponding to the sixth user account of the sixth user sharing the health-related data have a second visual characteristic, which includes the same value (e.g., the first value and the second value) as the visual characteristic included in the first visual characteristic of the first selectable user interface object (e.g., the first value and the second value) (e.g., the first selectable user interface object and the fifth selectable user interface object both include the same color pattern), wherein the objects are animated so that the visual states are not aligned at at least one point in time (e.g., when the objects have the same color pattern, the patterns are asynchronously animated through the states so that the objects are visually distinguishable). In some embodiments, the display of the visual characteristics of the animated selectable user interface objects provides feedback to the user about the type of data included in one set of health-related data while being visually distinguishable from another set of health-related data. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and additionally, by enabling the user to use the device more quickly and efficiently, this may also reduce power usage and extend the battery life of the device.

[0293] In some embodiments, the computer system receives data indicating that the sixth user is requesting to share the fifth set of health-related data with the first user (e.g., 818a to 818c) from an external computer system (e.g., a computer system associated with MATTAPPLESEED in 616a), and in response to receiving the data indicating that the sixth user is requesting to share the fifth set of health-related data with the first user, the computer system displays a notification indicating that the sixth user is requesting to share the fifth set of health-related data with the first user (e.g., Figure 8C 616a). In some embodiments, the notification includes a selectable user interface object that, when selected, initiates a process for accepting a sharing request from a sixth user. In some embodiments, displaying a notification indicating that another user is requesting to share a set of health-related data provides the user with visual feedback about the sharing status of the other user. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0294] In some embodiments, the computer system accepts a request to share a fifth set of health-related data with a first user (in some embodiments, based on a set of inputs including inputs received when displaying notifications) (e.g., via input 850d at 616aa and input 850f at 818d), wherein accepting the request includes enabling (e.g., approving) one or more subsequent notifications corresponding to the fifth set of health-related data (e.g., via input 850g at 826) (e.g., future health-related notifications associated with a sixth user). In some embodiments, enabling one or more notifications corresponding to a set of health-related data provides the user with visual feedback about potentially important health-related data from another user. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0295] In some embodiments, after accepting the request, the computer system displays an option to enable sharing of the first user's health-related data with a sixth user, similar to that described in method 700 .

[0296] In some embodiments, the computer system receives a first set of one or more user inputs (e.g., 850c), the first set of one or more user inputs including input corresponding to a first selectable user interface object (e.g., 616b), and in response to receiving the first set of one or more user inputs, the computer system displays a shared health data user interface (e.g., 814) via a display generation component (e.g., 602), the shared health data user interface corresponding to the first set of health-related data and including: a first set of one or more user interface objects (e.g., 814a to 814g), the first set of one or more user interface objects representing the first set of health-related data (e.g., a view of the health data of the second user); and a second set of one or more user interface objects representing previously received notifications based on the first set of health-related data (e.g., 814h) (e.g., a history of health-related alerts related to the second user). In some embodiments, displaying a shared health data user interface including user interface objects representing a set of shared health-related data provides the user with visual feedback about the type of data being shared by another user. Displaying a shared health data user interface including user interface objects that represent previously received notifications related to a set of shared health-related data provides a user with visual feedback about potentially important historical health-related data shared by another user. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0297] In some embodiments, the second user (e.g., Fig.8D The shared health data user interface (e.g., 814) of the GRANDMAAPPLESEED shown on 814 of the GRANDMAAPPLESEED includes a contact selectable user interface object (e.g., 816a to 816d) that, when selected, initiates a process for contacting (e.g., by phone, by text, by email) a second user. In some embodiments, providing a selectable user interface object that initiates a process for contacting on the shared health data user interface minimizes the number of inputs required to contact other users. Reducing the number of inputs required to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0298] In some embodiments, the computer system receives a second set of one or more user inputs including inputs (e.g., 850h) corresponding to a second selectable user interface object (e.g., 618c), and in response to receiving the second set of one or more user inputs, the computer system displays a shared health data user interface (e.g., 830) corresponding to a second set of health-related data (e.g., 830c through 830g) from the first user account via a display generating component (e.g., 602).

[0299] In some embodiments, the shared health data user interface (e.g., 830) includes a shared preview selectable user interface object (e.g., 830a) that provides a preview of the second set of health-related data being shared with a third user when the shared preview selectable user interface object (e.g., by input 850k) is selected (e.g., 644). In some embodiments, the preview is visually formatted in a manner similar to how the second set of health-related data will be presented to the third user on the third user's computer system. In some embodiments, a preview of a collection of health-related data being shared with another user provides the user with visual feedback about the display of their health-related data from the perspective of another user. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0300] In some embodiments, the preview of the second set of health-related data includes at least a plurality of graphical objects (eg, Figure 8J 604e, 604a).

[0301] In some embodiments, the shared health data user interface (e.g., 830) includes a modification selectable user interface object (e.g., 832) that, when selected, initiates a process for modifying (e.g., adding, removing) data included in the second set of health-related data (e.g., Figure 8K to Figure 8LThe process of modifying the type of data included in the second set of health-related data (e.g., as shown by the change in the position of the toggle switches 648c and 648d in ). In some embodiments, providing a selectable user interface object for modifying the data included in a shared set of health-related data provides the user with more control over the computer system and the data being shared. Providing additional control options enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0302] In some embodiments, the health data sharing user interface (e.g., 614) includes an indication (e.g., 620a, 618b) of an application (e.g., an application installed on a computer system; an application corresponding to a medical provider grouping) that is receiving a sixth set of health-related data from a first user account. In some embodiments, the health data sharing user interface includes an indication of one or more surveys of health-related data being received from a first user account. In some embodiments, an indication of an application that is receiving health-related data from a computer system is displayed to provide users with a visual indication of the sharing status of their health-related data. Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0303] Note that the above description is relative to method 900 (eg, Fig. 9 ) also apply in a similar manner to the methods described above. 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, a selectable user interface object of method 900 is displayed after initiating sharing of health-related data via method 700. For the sake of brevity, these details are not repeated below.

[0304] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

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

[0306] As described above, one aspect of the technology of the present invention is to collect and use data from various sources to improve the management of health-related data. The disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter 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 identification or personal information.

[0307] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to monitor conditions related to health and overall health. Therefore, the use of such personal information enables users to view and understand their own health-related data over time, as well as the health-related data of other users that are permitted to be shared according to the above methods. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0308] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement 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 easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to safeguard and protect access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0309] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of 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, in the case of managing health-related data, the technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" at any time during or after service registration to decide to participate in the collection of personal information data. In another example, a user may choose not to provide health-related data to other selected users and / or medical institutions. In another example, a user may choose to limit the length of time that health-related data is kept, or completely prohibit the development of basic health conditions. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.

[0310] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can 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 the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0311] 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 various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, health-related features may be presented to a user by inferring preferences based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to a computer system, or publicly available information.

Claims

1. A method comprising: At a computer system in communication with a display generating component, wherein the computer system is associated with a first user account of a first user: displaying, via the display generating component, a health data sharing user interface comprising a plurality of selectable graphical user interface objects, the plurality of selectable graphical user interface objects comprising: a first selectable user interface object corresponding to a second user account of a second user who is sharing a first set of health-related data with the first user account; and A second selectable user interface object corresponding to a third user account of a third user that is receiving a second set of health-related data from the first user account.

2. The method according to claim 1, wherein the health data sharing user interface comprises: A fourth selectable user interface object corresponding to a fourth user account of a fourth user sharing a third set of health-related data with the first user account.

3. The method according to any one of claims 1 to 2, wherein the health data sharing user interface comprises: A fourth selectable user interface object corresponding to a fifth user account of a fifth user receiving a fourth set of health-related data from the first user account.

4. The method according to any one of claims 1 to 3, wherein: based on determining that the first set of health-related data includes health-related notification data that satisfies a set of notification display criteria, the health data sharing user interface includes an indication of a health-related notification associated with the second user; Based on determining that the first set of health-related data includes health-related data that meets a set of recency criteria, the health data sharing user interface includes an indication of recent health data associated with the second user; and Based on determining that the first set of health-related data includes health-related data that satisfies a set of change criteria, the health data sharing user interface includes an indication of changed health data associated with the second user.

5. The method according to claim 4, further comprising: Receives a set of one or more inputs; In response to receiving the set of one or more inputs, modify the display configuration of an indication type selected from the group consisting of: an indication type corresponding to the health-related notification indication, an indication type corresponding to the recent health data indication, and an indication type corresponding to the changed health data indication. The method of claim 4 , wherein the indications included in the health data sharing user interface are organized by type of indication.

7. The method of claim 4, wherein the first indication is an indication of a plurality of data instances that satisfy the set of notification display criteria, the set of recency criteria, and / or the set of changed health data indications.

8. The method of claim 4, wherein the set of change criteria comprises criteria that are satisfied when the first set of health-related data comprises data indicating that a first health-related parameter undergoes a threshold amount of change for at least a threshold amount of time.

9. A method according to claim 4, wherein the set of change criteria includes a criterion that is met when the difference between the average value of a second health-related parameter in the first set of health-related data for a first time period and the average value of the second health-related parameter for a second time period is greater than a first predetermined amount of difference.

10. The method of any one of claims 1 to 9, wherein the first selectable user interface object has a first visual characteristic: Based on determining that a first set of visual characteristic display criteria is satisfied, the first visual characteristic includes a first value for the first visual characteristic, wherein the first set of visual characteristic display criteria includes criteria that are satisfied when the first set of health-related data includes a first data type; and The first visual characteristic includes a second value of the first visual characteristic based on determining that a second set of visual characteristic display criteria is satisfied, wherein the second set of visual characteristic display criteria includes criteria that are satisfied when the first set of health-related data includes a second data type.

11. The method of claim 10, wherein the first set of visual characteristic display criteria includes criteria that are satisfied when the first visual characteristic does not include more than a predetermined number of other values ​​of the first visual characteristic.

12. The method of claim 11, wherein the first visual characteristic comprises the predetermined number of values ​​of the first visual characteristic, and the included values ​​of the first visual characteristic correspond to the most commonly used data type in the second set of health-related data.

13. The method of claim 10, wherein the first visual property of the first selectable user interface object comprises the first value and the second value of the first visual property, the method further comprising: Display of the first visual characteristic of the first selectable user interface object is animated over time through at least a first visual state and a second visual state.

14. The method according to claim 10, further comprising: receiving data from an external computer system indicating that a sixth user is requesting to share a fifth set of health-related data with the first user; In response to receiving the data indicating that the sixth user is requesting to share the fifth set of health-related data with the first user, displaying a notification indicating that the sixth user is requesting to share the fifth set of health-related data with the first user.

15. The method according to claim 14, further comprising: Accepting the request to share the fifth set of health-related data with the first user, wherein accepting the request includes enabling one or more subsequent notifications corresponding to the fifth set of health-related data.

16. The method according to any one of claims 1 to 15, further comprising: receiving a first set of one or more user inputs including input corresponding to the first selectable user interface object; as well as In response to receiving the first set of one or more user inputs, displaying, via the display generation component, a shared health data user interface, the shared health data user interface corresponding to the first set of health-related data and comprising: a first set of one or more user interface objects, the first set of one or more user interface objects representing the first set of health-related data; as well as A second set of one or more user interface objects represents previously received notifications based on the first set of health-related data.

17. The method of claim 16, wherein the shared health data user interface corresponding to the second user includes a contact selectable user interface object that, when selected, initiates a process for contacting the second user.

18. The method according to any one of claims 1 to 17, further comprising: receiving a second set of one or more user inputs including input corresponding to the second selectable user interface object; as well as In response to receiving the second set of one or more user inputs, displaying, via the display generation component, a shared health data user interface corresponding to the second set of health-related data from the first user account.

19. A method according to claim 18, wherein the shared health data user interface includes a shared preview selectable user interface object, which, when selected, provides a preview of the second set of health-related data being shared with the third user.

20. The method of claim 18, wherein the shared health data user interface includes a modification selectable user interface object that, when selected, initiates a process for modifying the data included in the second set of health-related data.

21. The method of any one of claims 1 to 20, wherein the health data sharing user interface includes an indication of an application that is receiving a sixth set of health-related data from the first user account.

22. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component, wherein the computer system is associated with a first user account of a first user, the one or more programs comprising instructions for executing a method according to any one of claims 1 to 21.

23. A computer system configured to communicate with a display generation component, wherein the computer system is associated with a first user account of a first user, 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 executing the method according to any one of claims 1 to 21.

24. A computer system configured to communicate with a display generation component, wherein the computer system is associated with a first user account of a first user, the computer system comprising: Module for performing the method according to any one of claims 1 to 21.

25. 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, wherein the computer system is associated with a first user account of a first user, the one or more programs comprising instructions for executing a method according to any one of claims 1 to 21.

Images