CN116724359A

CN116724359A - User interface for monitoring health

Info

Publication number: CN116724359A
Application number: CN202280010264.8A
Authority: CN
Inventors: M·W·克罗莱伊
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2021-01-14
Filing date: 2022-01-14
Publication date: 2023-09-08

Abstract

The present disclosure relates generally to user interfaces for monitoring health. In some embodiments, the notification is generated and/or displayed by the electronic device based on sensor data that does not include a direct measurement of pressure. In some embodiments, the electronic device displays a user interface for tracking and/or monitoring blood pressure measurement data received over a selected time range. The user interface for tracking and/or monitoring received blood pressure measurement data includes a measurement entry user-interactive graphical user interface object that initiates a process for the electronic device to receive blood pressure measurement data corresponding to respective measurement indicators of the user interface corresponding to the current day and selected time range.

Description

User interface for monitoring health

Cross Reference to Related Applications

The present application claims the benefit of U.S. provisional application Ser. No. 63/137,704, titled "USER INTERFACES FOR MONITORING HEALTH", filed 1/14/2021, U.S. provisional application Ser. No. 63/142,757, titled "USER INTERFACES FOR MONITORING HEALTH", filed 1/28/2021, and U.S. patent application Ser. No. 17/574,268, titled "USER INTERFACES FOR MONITORING HEALTH", filed 1/12/2022, each of which is hereby incorporated by reference in its entirety.

Technical Field

The present disclosure relates generally to computer user interfaces, and more particularly to techniques for managing and/or presenting health data.

Background

The electronic device includes a user interface that displays various health information to a user. The health information may include data collected by sensors of the electronic device and/or data entered by a user.

Disclosure of Invention

However, some techniques for managing and/or presenting health 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 key presses or keystrokes. The prior art requires more time than is necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

Thus, the present technology provides faster, more efficient methods and interfaces for electronic devices to manage and/or present health data. Such methods and interfaces optionally supplement or replace other methods for managing and/or presenting health data. Such methods and interfaces reduce the cognitive burden on the user and result in a more efficient human-machine interface. For battery-powered computing devices, such methods and interfaces conserve power and increase the time interval between battery charges. Such methods and interfaces also provide notifications to the user related to health events, thereby providing the user with information related to his or her health without requiring input. Such methods and interfaces also enable a user to conveniently track health information, thereby facilitating the user's ability to monitor his or her health.

According to some embodiments, a method performed at a computer system in communication with one or more output devices and one or more sensors is described. The method comprises the following steps: receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and in response to receiving the first data from the one or more sensors: in accordance with a determination that the first data from the one or more sensors meets a set of hypertension notification criteria, generating, via the one or more output devices, a notification indicative of a hypertension event associated with the user of the computer system; and in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, forgoing generating the notification of the hypertension event.

According to some embodiments, a non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with one or more output devices and one or more sensors is described. The one or more programs include instructions for: receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and in response to receiving the first data from the one or more sensors: in accordance with a determination that the first data from the one or more sensors meets a set of hypertension notification criteria, generating, via the one or more output devices, a notification indicative of a hypertension event associated with the user of the computer system; and in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, forgoing generating the notification of the hypertension event.

According to some embodiments, a transitory computer-readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with one or more output devices and one or more sensors is described. The one or more programs include instructions for: receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and in response to receiving the first data from the one or more sensors: in accordance with a determination that the first data from the one or more sensors meets a set of hypertension notification criteria, generating, via the one or more output devices, a notification indicative of a hypertension event associated with the user of the computer system; and in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, forgoing generating the notification of the hypertension event.

According to some embodiments, a computer system is described that includes one or more output devices, one or more sensors, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and in response to receiving the first data from the one or more sensors: in accordance with a determination that the first data from the one or more sensors meets a set of hypertension notification criteria, generating, via the one or more output devices, a notification indicative of a hypertension event associated with the user of the computer system; and in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, forgoing generating the notification of the hypertension event.

According to some embodiments, a computer system is described. The computer system includes: one or more output devices; one or more sensors; and means for receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and means for, in response to receiving the first data from the one or more sensors: in accordance with a determination that the first data from the one or more sensors meets a set of hypertension notification criteria, generating, via the one or more output devices, a notification indicative of a hypertension event associated with the user of the computer system; and in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, forgoing generating the notification of the hypertension event.

According to some embodiments, a method performed at a computer system in communication with a display generation component and one or more input devices is described. The method comprises the following steps: receiving, via the one or more input devices, a first set of one or more inputs including a first input selecting a time range; displaying, via the display generating component, a first user interface in response to receiving the first set of one or more inputs, wherein the first user interface comprises: in accordance with a determination that the first user input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range; in accordance with a determination that the first user input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and a first measurement entry user-interactive graphical user interface object that, when selected via the one or more input devices, initiates a measurement entry process for: entering blood pressure measurements corresponding to the first time range and the day according to the first user interface including the first plurality of measurement indicators within the first time range; and entering blood pressure measurements corresponding to the second time range and the current day according to the first user interface including the second plurality of measurement indicators within the second time range.

According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with a display generation component and one or more input devices is described. The one or more programs include instructions for: receiving, via the one or more input devices, a first set of one or more inputs including a first input selecting a time range; displaying, via the display generating component, a first user interface in response to receiving the first set of one or more inputs, wherein the first user interface comprises: in accordance with a determination that the first user input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range; in accordance with a determination that the first user input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and a first measurement entry user-interactive graphical user interface object that, when selected via the one or more input devices, initiates a measurement entry process for: entering blood pressure measurements corresponding to the first time range and the day according to the first user interface including the first plurality of measurement indicators within the first time range; and entering blood pressure measurements corresponding to the second time range and the current day according to the first user interface including the second plurality of measurement indicators within the second time range.

According to some embodiments, a transitory computer-readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with a display generation component and one or more input devices is described. The one or more programs include instructions for: receiving, via the one or more input devices, a first set of one or more inputs including a first input selecting a time range; displaying, via the display generating component, a first user interface in response to receiving the first set of one or more inputs, wherein the first user interface comprises: in accordance with a determination that the first user input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range; in accordance with a determination that the first user input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and a first measurement entry user-interactive graphical user interface object that, when selected via the one or more input devices, initiates a measurement entry process for: entering blood pressure measurements corresponding to the first time range and the day according to the first user interface including the first plurality of measurement indicators within the first time range; and entering blood pressure measurements corresponding to the second time range and the current day according to the first user interface including the second plurality of measurement indicators within the second time range.

According to some embodiments, a computer system is described that includes a display generating component, one or more input devices, 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 include instructions for: receiving, via the one or more input devices, a set of one or more inputs comprising a first input selecting a time range; displaying, via the display generating component, a first user interface in response to receiving the first set of one or more inputs, wherein the first user interface comprises: in accordance with a determination that the first user input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range; in accordance with a determination that the first user input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and a first measurement entry user-interactive graphical user interface object that, when selected via the one or more input devices, initiates a measurement entry process for: entering blood pressure measurements corresponding to the first time range and the day according to the first user interface including the first plurality of measurement indicators within the first time range; and entering blood pressure measurements corresponding to the second time range and the current day according to the first user interface including the second plurality of measurement indicators within the second time range.

According to some embodiments, a computer system is described. The computer system includes: a display generation section; one or more input devices; and means for receiving, via the one or more input devices, a first set of one or more inputs including a first input selecting a time range; means for displaying, via the display generating component, a first user interface in response to receiving the first set of one or more inputs, wherein the first user interface comprises: in accordance with a determination that the first user input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range; in accordance with a determination that the first user input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and a first measurement entry user-interactive graphical user interface object that, when selected via the one or more input devices, initiates a measurement entry process for: entering blood pressure measurements corresponding to the first time range and the day according to the first user interface including the first plurality of measurement indicators within the first time range; and entering blood pressure measurements corresponding to the second time range and the current day according to the first user interface including the second plurality of measurement indicators within the second time range.

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

Thus, faster, more efficient methods and interfaces for managing and/or presenting health data are provided for devices, thereby improving the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may supplement or replace other methods for managing and/or presenting health data.

Drawings

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

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

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

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

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

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

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

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

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

Fig. 6A-6P illustrate an exemplary user interface for generating notifications associated with health events, according to some embodiments.

Fig. 7 is a flow chart illustrating a method for generating notifications associated with health events, in accordance with some embodiments.

Fig. 8A-8U illustrate an exemplary user interface for managing health information over a predefined time frame, according to some embodiments.

Fig. 9 is a flowchart illustrating a method for managing health information within a predefined time frame, according to some embodiments.

Detailed Description

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

There is a need for an electronic device that provides efficient methods and interfaces for managing and/or presenting health data. For example, there is a need for an electronic device that monitors health data over time and notifies a user of potential health events without periodic and/or intermittent user input. As another example, there is a need for an electronic device that facilitates a user's ability to record and/or track health information over time so that the user can easily monitor his or her health. Such techniques may alleviate the cognitive burden on users accessing health data on electronic devices, thereby improving productivity. Further, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user inputs.

1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of an exemplary device for performing techniques for managing event notifications. Fig. 6A-6P illustrate an exemplary user interface for generating notifications associated with health events. Fig. 7 is a flow chart illustrating a method of generating notifications associated with health events, according to some embodiments. The user interfaces in fig. 6A-6P are used to illustrate the processes described below, including the process in fig. 7. Fig. 8A-8U illustrate an exemplary user interface for managing health information over a predefined time frame. Fig. 9 is a flow chart illustrating a method of managing health information over a predefined time frame, according to some embodiments. The user interfaces in fig. 8A-8U are used to illustrate the processes described below, including the process in fig. 9.

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

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

The terminology used in the description of the various illustrated embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

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

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

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

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

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

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

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

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

It should be understood that the device 100 is merely one example of a portable multifunction device, and that the device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in fig. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.

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

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

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

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

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

The quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. patent application Ser. No. 11/322,549 (i.e., U.S. patent No.7,657,849) entitled "Unlocking a Device by Performing Gestures on an Unlock Image," filed on even 23, 12, 2005, which is hereby incorporated by reference in its entirety. Long presses of a button (e.g., 206) optionally cause the device 100 to power on or off. The function of the one or more buttons is optionally customizable by the user. Touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

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

The touch sensitive display in some implementations of touch screen 112 is optionally similar to the multi-touch sensitive touch pad described in the following U.S. patents: 6,323,846 (Westerman et al), 6,570,557 (Westerman et al) and/or 6,677,932 (Westerman et al) and/or U.S. patent publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while touch sensitive touchpads do not provide visual output.

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

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

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

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

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

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

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

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

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

The device 100 optionally further includes one or more accelerometers 168. Fig. 1A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in the following U.S. patent publications: U.S. patent publication No.20050190059, entitled "acception-based Theft Detection System for Portable Electronic Devices" and U.S. patent publication No.20060017692, entitled "Methods And Apparatuses For Operating APortable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some implementations, information is displayed in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., longitudinal or lateral) of the device 100.

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

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

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

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

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

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

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

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

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

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

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

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

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

a telephone module 138;

video conferencing module 139;

email client module 140;

an Instant Messaging (IM) module 141;

a fitness support module 142;

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

an image management module 144;

a video player module;

a music player module;

browser module 147;

Calendar module 148;

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

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

search module 151;

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

a note module 153;

map module 154; and/or

An online video module 155.

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

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

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

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

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

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

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

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

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

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

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

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, gadget module 149 is a mini-application (e.g., weather gadget 149-1, stock gadget 149-2, calculator gadget 149-3, alarm gadget 149-4, and dictionary gadget 149-5) or a mini-application created by a user (e.g., user created gadget 149-6) that is optionally downloaded and used by a user. In some embodiments, gadgets include HTML (hypertext markup language) files, CSS (cascading style sheet) files, and JavaScript files. In some embodiments, gadgets include XML (extensible markup language) files and JavaScript files (e.g., yahoo | gadgets).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, gadget creator module 150 is optionally used by a user to create gadgets (e.g., to transform user-specified portions of a web page into gadgets).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When the touch sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where within one or more views a sub-event has occurred. The view is made up of controls and other elements that the user can see on the display.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

time 404;

bluetooth indicator 405;

battery status indicator 406;

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

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

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

icon 420 labeled "browser" for browser module 147; and

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

icons of other applications, such as:

icon 424 marked "message" for IM module 141;

icon 426 of calendar module 148 marked "calendar";

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

icon 430 marked "camera" for camera module 143;

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

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

icon 436 marked "map" of map module 154;

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

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

icon 442 labeled "fitness support" for fitness support module 142;

icon 444 marked "note" of the note module 153; and

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

It should be noted that the iconic labels shown in fig. 4A are merely exemplary. For example, the icon 422 of the video and music player module 152 is labeled "music" or "music player". Other labels are optionally used for various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

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

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

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

Fig. 5A illustrates an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., fig. 1A-4B). In some implementations, the device 500 has a touch sensitive display 504, hereinafter referred to as a touch screen 504. In addition to or in lieu of touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some implementations, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of the touch screen 504 (or touch sensitive surface) may provide output data representative of the intensity of the touch. The user interface of the device 500 may respond to touches based on the intensity of the touches, meaning that touches of different intensities may invoke different user interface operations on the device 500.

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

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

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

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

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

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

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

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

In some implementations, a portion of the gesture is identified for determining a feature strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and to an ending position where the contact intensity increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or depressions in the intensity of the swipe contact for the purpose of determining the characteristic intensity.

The intensity of the contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the tap strength threshold corresponds to a strength of: at this intensity the device will perform the operations normally associated with clicking a button of a physical mouse or touch pad. In some embodiments, the deep compression intensity threshold corresponds to an intensity of: at this intensity the device will perform an operation that is different from the operation normally associated with clicking a physical mouse or a button of a touch pad. In some implementations, when a contact is detected with a characteristic intensity below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, a contact below the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector according to movement of the contact over the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface drawings.

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

In some implementations described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein a respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some implementations, the respective operation is performed in response to detecting that the intensity of the respective contact increases above a press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "upstroke" of the respective press input).

In some implementations, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," in which the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the compression input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the compression input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the compression input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of the respective contact above a press input intensity threshold and a subsequent decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting that the intensity of the respective contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting a press input (e.g., an increase in contact intensity or a decrease in contact intensity depending on the circumstances).

For ease of explanation, optionally, a description of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture comprising a press input is triggered in response to detecting any of the following: the contact strength increases above the compression input strength threshold, the contact strength increases from an intensity below the hysteresis strength threshold to an intensity above the compression input strength threshold, the contact strength decreases below the compression input strength threshold, and/or the contact strength decreases below the hysteresis strength threshold corresponding to the compression input strength threshold. In addition, in examples where the operation is described as being performed in response to the intensity of the detected contact decreasing below a press input intensity threshold, the operation is optionally performed in response to the intensity of the detected contact decreasing below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

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

Fig. 6A-6P illustrate an exemplary user interface for generating notifications associated with health events, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in fig. 7.

Fig. 6A shows a computer system 600 having a display generation component 602 and a health user interface 604 for displaying a health application of the computer system 600 on a first date (e.g., a 4 month 5 day sunday) via the display generation component 602. At fig. 6A, the health user interface 604 includes health data user interface objects 604a and 604b and a health event notification user interface object 606. Health data user interface objects 604a and 604b include information related to health parameters of a user associated with computer system 600 (e.g., quantitative and/or qualitative measurements and/or characteristics detected by sensors of computer system 600 and/or received by computer system 600 via user input and/or from external devices). In some embodiments, the health user interface 604 is a home screen or default screen of the health application that the computer system 600 displays via the display generation component 602 when the health application is launched.

In fig. 6A, a computer system 600 displays a health event notification user interface object 606 that prompts a user to enable and/or activate notifications related to particular health events. The health event notification user interface object 606 is associated with a hypertension notification generated by the computer system 600 in response to determining that a user associated with the computer system 600 is at risk for hypertension. As used herein, "hypertension" refers to a user suffering from and/or at risk of chronically high blood pressure, rather than a single instance and/or single measurement of high blood pressure. Thus, computer system 600 generates a hypertension notification upon determining that a user associated with computer system 600 is regularly experiencing high blood pressure (e.g., rather than the user simply having one instance and/or one measurement indicating high blood pressure).

The computer system 600 displays a health event notification user interface object 606 on the health user interface 604 based on determining that the user has not previously enabled and/or activated a hypertension notification. In some embodiments, the health event notification user interface object 606 may be displayed on another user interface of the health application, such as a checklist user interface prompting the user to enable and/or activate tracking of health parameters (e.g., heart rate and/or rhythm monitoring, electrocardiogram monitoring, blood oxygen monitoring, noise exposure monitoring, and/or cardiac fitness level monitoring) that have not been enabled and/or activated by the user. In some embodiments, computer system 600 enables and/or activates the hypertension notification by default and/or without user input (e.g., computer system 600 enables the hypertension notification as a default setting upon initial startup of computer system 600).

At fig. 6A, computer system 600 detects a user input 650a (e.g., a tap gesture) corresponding to selection of a user interface object 606A (e.g., a user interface object labeled "enabled") of health event notification user interface object 606. In response to detecting the user input 650a, the computer system 600 displays a first settings user interface 608 for the first date, as shown in FIG. 6B. The first settings user interface 608 includes additional information related to enabling and/or activating hypertension notification. For example, the first settings user interface 608 includes a more understood region 608a that provides information related to hypertension and/or hypertension notification. Thus, a user associated with computer system 600 may obtain further guidance from knowing more area 608a before deciding to enable and/or activate a hypertension notification. At fig. 6B, computer system 600 detects user input 650B (e.g., a flick gesture) on user interface object 608B (e.g., a user interface object labeled "set"). In response to detecting the user input 650b, the computer system 600 displays a second settings user interface 610 for the first date, as shown in FIG. 6C.

The second settings user interface 610 includes further information (e.g., text information) regarding the hypertension notification generated by the computer system 600. At fig. 6C, computer system 600 detects user input 650C (e.g., a tap gesture) on user interface object 610a (e.g., a user interface object labeled "enabled") of second setup user interface 610. In response to detecting the user input 650c, the computer system 600 displays a third settings user interface 612 for the first date, as shown in FIG. 6D.

The third settings user interface 612 includes a date of birth user interface object 612a, a first diagnostic user interface object 612b, a second diagnostic user interface object 612c, and a next user interface object 612d. In some embodiments, computer system 600 is configured to: the hypertension notification is enabled and/or activated for users that meet the feature pass criteria and is not enabled and/or activated (e.g., prevented from being enabled and/or activated) for users that do not meet the feature pass criteria. For example, the feature qualification criteria include a criterion that the user is above a threshold age (e.g., 22 years). Thus, computer system 600 receives information related to the date of birth of a user associated with computer system 600. In some embodiments, computer system 600 displays (e.g., pre-populates) a birth date in birth date user interface object 612a that corresponds to a birth date previously received by computer system 600 (e.g., entered by a user and/or received by computer system 600 during initial setup and/or activation of computer system 600). In some embodiments, computer system 600 receives a date of birth and displays the received date of birth in date of birth user interface object 612a in response to one or more inputs corresponding to selection of date of birth user interface object 612 a.

In addition, the feature qualification criteria include criteria that the user has not been diagnosed as having hypertension (e.g., received a diagnosis from a physician). At fig. 6D, the third setup user interface 612 includes a first diagnostic user interface object 612b corresponding to a user having been previously diagnosed as having hypertension (e.g., the user obtaining a diagnosis of hypertension from a physician). The second diagnostic user interface object 612c corresponds to a user not previously diagnosed as having hypertension (e.g., the user has not obtained a diagnosis of hypertension from a physician). In some embodiments, computer system 600 is configured to: enabling and/or activating a hypertension notification for a user who has not received a hypertension diagnosis, and configured to: the hypertension notification is not enabled and/or activated (e.g., prevented from being enabled and/or activated) for the user that has received the hypertension diagnosis. In some embodiments, computer system 600 is configured to: sensor data is not enabled and is not collected and stored for the purpose of determining whether to provide a hypertension notification for users that do not meet the feature qualification criteria. In some embodiments, computer system 600 does not make a determination based on the hypertension notification criteria for users that do not meet the feature eligibility criteria.

In some implementations, the next user interface object 612d is unavailable (e.g., via user input) for selection (e.g., the next user interface object 612d is grayed out or not displayed) in response to the birth date being associated with an age below a threshold age and/or in response to user input selecting the first diagnostic user interface object 612 b. In other words, if the user is below a threshold age and/or the user has been previously diagnosed as having hypertension, the computer system 600 does not enable the user to complete the setting (e.g., enabling and/or activating) of the hypertension notification. In some embodiments, the computer system 600 foregoes displaying the health event notification user interface object 606 on the health user interface 604 in response to detecting that the user's age is below a threshold age and/or in response to receiving data indicative of a hypertension diagnosis of a user associated with the computer system 600.

At fig. 6D, computer system 600 receives and/or detects a birth date of a user associated with an age above a threshold age and receives user input corresponding to selection of second diagnostic user interface object 612 c. Thus, the next user interface object 612d is available for selection. At FIG. 6D, computer system 600 detects user input 650D on the next user interface object 612D. In response to detecting the user input 650d, the computer system 600 displays a fourth settings user interface 614 for the first date, as shown in FIG. 6E.

At fig. 6E, the fourth setup user interface 614 includes a first information disk 614a, a second information disk 614b, and a third information disk 614c. Message disks 614a, 614b, and 614c provide additional details regarding the notification of hypertension. Additional details may include text information that provides guidance and/or suggested actions to the user when receiving and/or in the absence of a hypertension notification. At fig. 6E, computer system 600 detects user input 650E on user interface object 614d of fourth settings user interface 614. In response to detecting the user input 650e, the computer system 600 displays a confirmation user interface 616 for the first date, as shown in FIG. 6F.

At fig. 6F, confirmation user interface 616 includes a hypertension notification user interface object 616a (e.g., a toggle). The hypertension notification user interface object 616a is in an active and/or "on" position, indicating that the computer system 600 successfully enables and/or activates hypertension notification. Confirmation user interface 616 confirms to the user that the setup process for enabling the notification of hypertension has been successfully completed. In some embodiments, computer system 600 detects completion of user input (e.g., a flick gesture; not shown) on user interface object 616 b. In response to detecting completion of user input on user interface object 616b, computer system 600 displays health user interface 604 (e.g., health user interface 604 without health event notification user interface object 606) and/or hypertension user interface 644 as described below with reference to fig. 6L (e.g., hypertension user interface 644 without notification user interface objects 646a and 646 b).

After the computer system 600 enables and/or activates the hypertension notification, the computer system 600 initiates a process that causes one or more sensors 618, 620, and/or 622 of the computer system 624 to collect data corresponding to one or more parameters and/or characteristics of a user of the computer system 624. As set forth below, computer system 624 communicates with computer system 600 and provides (e.g., transmits) collected data and/or an indication that a set of notification criteria (e.g., hypertension notification criteria) has been met to computer system 600 (e.g., via wireless signals such as bluetooth, wi-Fi, and/or Zigbee).

At fig. 6G, computer system 624 collects data from sensors 618, 620, and/or 622 for a predetermined period of time, such as within 30 days, before computer system 624 and/or computer system 600 determines whether the data meets the set of notification criteria (e.g., hypertension notification criteria). For example, fig. 6G includes a table 626 that illustrates days and/or times at which data was collected from sensors 618, 620, and/or 622 after the computer system 600 enabled and/or activated the hypertension notification. The table 626 includes a first day 626a, a second day 626b, and a third day 626c, each of which falls within a predetermined time period (e.g., 30 days from the first of the 4 month 5 day sunday). As shown in fig. 6G, data is collected on each of the first, second, and third days 626a, 626b, and 626c, as indicated by the check marks in the "data collected" column of table 626. While fig. 6G shows data collected on first, second, and third days 626a, 626b, and 626c within a predetermined period of time, data is also collected at other times within the predetermined period of time (e.g., other days and/or times within first, second, and/or third days 626a, 626b, and/or 626 c). In some embodiments, the data is collected on days when the computer system 624 is worn by the user (e.g., on the user's wrist) for an amount of time sufficient for the sensors 618, 620, and/or 622 to collect at least one measurement. In some embodiments, computer system 600 and/or computer system 624 determine whether the data meets the set of notification criteria (e.g., hypertension notification criteria) in response to the data including a threshold number of data points. For example, before making a determination of whether the data meets the notification criteria, the computer system 600 and/or the computer system 624 determines whether the data includes data points collected for at least 15 days of a 30 day period and/or whether the data includes data points for at least 5 hours, 8 hours, 10 hours, and/or 12 hours of each of the 15 days of the 30 day period. In some embodiments, if the data does not include a threshold number of data points, computer system 600 and/or computer system 624 does not determine whether the data meets the set of notification criteria (e.g., hypertension notification criteria). Thus, computer system 600 and/or computer system 624 does not generate a hypertension notification unless the data includes a threshold number of data points.

The predetermined period of time is long enough for the computer system 624 to collect data sufficient to determine whether the user is at risk of hypertension. Thus, the predetermined period of time is greater than 1 hour, 1 day, and/or 1 week. Further, the data collected over the predetermined period of time includes individual data points that are spaced apart from one another by an amount of time that is greater than an amount of time for collecting the corresponding data points. For example, the data collected during the time period may include a first data point collected on a first day of the predetermined time period and a second data point collected on a second day of the predetermined time period, wherein the first day and the second day are spaced apart by a plurality of days. Additionally, the sensors 618, 620, and/or 622 may collect individual data points in less than 1 second, and/or 1 minute. Thus, the time it takes for the computer system 624 to collect each data point is significantly less than the predetermined period of time within which data is ultimately collected in order to determine whether the data meets the set notification criteria.

As set forth above, computer system 600 and/or computer system 624 determine after a predetermined period of time has elapsed if the data collected over the predetermined period of time meets the set of notification criteria. In some embodiments, the set of notification criteria includes a threshold risk score (e.g., a quantitative value). Computer system 600 and/or computer system 624 determine a risk score by inputting data collected over a predetermined period of time into an algorithm (e.g., a machine learning algorithm). The algorithm is configured to evaluate data collected over a predetermined period of time for trends and/or patterns associated with hypertension. For example, the algorithm is generated based on clinical data from users other than the current user associated with computer system 600 and computer system 624. Clinical data includes data from users diagnosed with hypertension, and optionally data from users having normal blood pressure and not yet diagnosed with hypertension. Thus, the algorithm analyzes the data to generate a risk score (e.g., a quantitative value) associated with whether the user associated with computer system 600 and computer system 624 has hypertension. In response to the algorithm generating a risk score that meets or exceeds the threshold risk score, computer system 600 and/or computer system 624 determine that data collected over a predetermined period of time meets the set of notification criteria. Conversely, in response to the algorithm generating a risk score below the threshold risk score, computer system 600 and/or computer system 624 determine that the data collected over the predetermined period of time does not meet the set of notification criteria.

At fig. 6G, sensor 618 is a photoplethysmograph sensor (e.g., a photoplethysmograph) that collects data indicative of changes in skin light absorption. For example, the sensor 618 of the computer system 624 emits light 618a that reflects off the skin of a user associated with the computer system 624 (e.g., the user wearing the computer system 624 and the same user associated with the computer system 600). Light 618a is reflected from the skin of the user and received by sensor 618 of computer system 624, which may enable computer system 624 (and/or computer system 600) to determine a change in the blood volume of the user associated with computer system 624. In addition, sensor 620 is a gyroscope sensor and/or accelerometer that collects data indicative of movement (e.g., angular velocity) 620a of a user associated with computer system 624. Still further, the sensor 622 is an Electrocardiogram (ECG) sensor and/or heart rate sensor that collects data indicative of a heart rate of a user associated with the computer system 624.

Thus, the sensors 618, 620, and 622 of the computer system 624 do not directly measure the pressure and/or blood pressure of the user associated with the computer system 624. In particular, sensors 618, 620, and 622 do not provide raw data including pressure and/or blood pressure to computer system 624 and/or computer system 600. Further, computer system 624 and/or sensors 618, 620, and 622 of computer system 624 do not apply pressure and/or restrict blood flow to a user associated with computer system 624. Still further, the sensors 618, 620, and 622 do not measure vibrations. Thus, the sensors 618, 620, and 622, individually or collectively, are not conventional blood pressure measurement devices, such as blood pressure meters that measure pressure, vibration, and/or sound associated with blood flowing through an artery and/or blood vessel. Instead, the sensors 618, 620, and 622 provide data associated with the light absorption of the user's skin, the user's movement, and/or the user's heart rate to the computer system 624 and/or the computer system 600. This data received from sensors 618, 620 and 622 is then input into an algorithm to determine a risk score for the data collected over a predetermined period of time, which is then compared to a threshold risk score.

In addition, the data collected by sensors 618, 620, and 622 is measured passively. In other words, computer system 624 causes sensors 618, 620, and 622 to collect data while the user is wearing computer system 624 without the user providing input each time a data point is measured. Thus, a user associated with computer system 624 (e.g., the same user associated with computer system 600) may enable hypertension notification via the setup process described above with respect to fig. 6A-6F, and no further input is provided to computer system 600 and/or computer system 624 in order for computer system 600 and/or computer system 624 to collect data over a predetermined period of time.

As set forth above, the data measured and/or collected from the sensors 618, 620, and 622 is received by the computer system 624 and/or the computer system 600 (e.g., via the computer system 624). Computer system 624 and/or computer system 600 utilizes data collected over a predetermined period of time to determine whether the set of notification criteria is met (e.g., whether a risk score generated by an algorithm using the data exceeds a threshold risk score). In response to determining that the data collected over the predetermined period of time meets the set of notification criteria, computer system 600 and/or computer system 624 generates a notification indicating that a user associated with computer system 600 and computer system 624 is at risk of hypertension.

At fig. 6H, computer system 600 displays notification 628 on user interface 630 (e.g., a lock screen user interface and/or a home screen user interface). The computer system 600 displays a notification 628 of a second date (e.g., 5 months, 5 days, tuesdays) that occurs after a predetermined period of time has elapsed since the first date (e.g., 4 months, 5 days, sunday). Accordingly, computer system 600 (and/or computer system 624) determines that data collected during a predetermined period of time (e.g., as shown in fig. 6G) meets the set of notification criteria, thereby causing notification 628 to be displayed. At fig. 6H, notification 628 includes an application indicator 628a and an information indicator 628b. The application indicators 628a include graphical user interface elements and/or text that indicate an application (e.g., a health application) of the computer system 600 associated with the notification 628. In addition, the information indicator 628b provides details (e.g., textual details) indicating that the notification 628 relates to the user being at risk of hypertension. As shown in fig. 6H, notification 628 does not include an indication of the user's blood pressure measurement (e.g., a numerical indicator and/or a quantitative value of systolic and/or diastolic blood pressure), but rather notifies the user that the collected data indicates that the user is at risk for hypertension.

In some embodiments, computer system 600 and/or computer system 624 reset a predetermined period of time after generating notification 628. Thus, computer system 600 and/or computer system 624 does not generate another notification indicating that the user is at risk of hypertension until another set of data is collected within a second predetermined period of time (e.g., 30 days; a predetermined period of time that does not overlap with the predetermined period of time for generating notification 628). For example, computer system 600 generates and displays notification 628 on a 5 month 5 day Tuesday. Computer system 600 and/or computer system 624 resets the predetermined period of time such that the second notification is not generated and/or displayed until after the predetermined period of time has elapsed again starting on the 5 month 5 day tuesday. In other words, the predetermined period of time for collecting data for generating the first hypertension notification does not overlap with the predetermined period of time for collecting data for generating the second hypertension notification.

Specifically, at FIG. 6I, computer system 600 displays notification 632 on user interface 630 (e.g., a lock screen user interface). The computer system 600 displays a notification 632 on a third date (e.g., 6 months 5 days friday) that occurs after a predetermined period of time (e.g., 30 days) has elapsed since the second date (e.g., 5 months 5 days friday). Accordingly, computer system 600 and/or computer system 624 reset the predetermined period of time in response to generating and displaying notification 628 such that a subsequent notification (e.g., notification 632) is not generated and/or displayed until the predetermined period of time has elapsed since the time notification 628 was generated. At fig. 6I, notification 632 includes an application indicator 632a and an information indicator 632b. The application indicator 632a includes graphical user interface elements and/or text that indicate an application (e.g., a health application) of the computer system 600 associated with the notification 632. In addition, the information indicator 632b provides details (e.g., textual details) indicating that the notification 632 is related to the user being at risk of hypertension. As shown in fig. 6I, notification 632 does not include an indication of the user's blood pressure measurement (e.g., a numerical indicator and/or a quantitative value of systolic and/or diastolic blood pressure), but rather notifies the user that the collected data indicates that the user is at risk for hypertension.

At fig. 6I, computer system 600 detects user input 650f (e.g., a tap gesture and/or user input meeting a set of unlocking criteria) on notification 632. In response to detecting the user input 650f, the computer system 600 displays a health event user interface 634, as shown in fig. 6J. The health event user interface 634 corresponds to the notification 632 and provides further information and/or details associated with the notification 632. Similar to the notification 632, the health event user interface 634 does not include blood pressure measurements of the user, such as numerical and/or quantitative values of systolic and/or diastolic blood pressure measurements. In contrast, the health event user interface 634 includes an information area 634a, a notification details area 636, and a device details area 638. Information area 634a provides a textual indication of the reason that computer system 600 displayed notification 632 and additional information for consideration by the user as a result of notification 632. The notification details area 636 includes: a date user interface object 636a indicating a date and time of generation of notification 632 by computer system 600 (and/or computer system 624); a source user interface object 636b that indicates an application of the computer system 600 (e.g., a health application) associated with the notification 632; and a log user interface object 636c that indicates the date and time the application log indicated by the source user interface object 636b recorded, stored, and/or otherwise recorded the notification. Device details area 638 provides one or more user interface objects that indicate the particular device (e.g., computer system 600 and/or computer system 624) that generated notification 632.

In some embodiments, in addition to or in lieu of user input 650f, a user of computer system 600 may access health event user interface 634 via health user interface 604. For example, at FIG. 6K, computer system 600 displays health user interface 604 including notification 640. Notification 640 corresponds to notification 632 and, thus, computer system 600 displays notification 640 in response to determining (e.g., by computer system 600 and/or computer system 624) that the data collected over the predetermined period of time meets the set of notification criteria for generating a hypertension notification. At fig. 6K, notification 640 includes an indication (e.g., a text indication) that provides the user with information related to the reason for notification 640. In addition, notification 640 includes knowledge of more user interface objects 640a. In response to detecting a user input corresponding to a selection of the more user interface object 640a, the computer system 600 displays an educational user interface that provides the user with further information related to hypertension and suggested actions that the user may take as a result of receiving the notification 640.

In contrast to the healthy user interface 604 of fig. 6A, the healthy user interface 604 of fig. 6K translates in an upward direction. Accordingly, the computer system 600 displays notifications, such as notification 640, in the notification area 642 of the health user interface 604, where the notifications in the notification area 642 are associated with and/or generated by the health application. In some embodiments, when the computer system 600 launches the health application and displays the health user interface 604 (e.g., prior to receiving user input requesting translation of the health user interface 604), the notification area 642 of the health user interface 604 is positioned over and/or in front of the health data user interface objects 604a and/or 604 b. Thus, when the computer system 600 launches the health application, a user associated with the computer system 600 can easily view the most recent notifications corresponding to the health event and/or health information associated with the user.

At fig. 6K, computer system 600 detects user input 650g (e.g., a flick gesture) corresponding to selection of notification 640. In response to detecting user input 650g, computer system 600 displays a hypertension user interface 644, as shown in FIG. 6L. Hypertension user interface 644 is another user interface associated with a health application of computer system 600, but includes user interface objects that are specifically related to hypertension notifications and information associated with hypertension and/or hypertension notifications. For example, the hypertension user interface 644 includes a status user interface object 644a, a notification area 646, and a knowledge further area 648. Status user interface object 644a provides an indication of the status of the hypertension notification feature (e.g., whether computer system 600 has enabled and/or activated the hypertension notification). In some implementations, the status user interface object 644a includes an indication (e.g., a text indication) of the date and/or time at which the data from the sensors 618, 620, and 622 was last collected within a predetermined period of time.

The notification area 646 of the hypertension user interface 644 includes a first notification user interface object 646a and a second notification user interface object 646b. The first notification user interface object 646a corresponds to a notification 632 generated on a third date (e.g., 6 months, 5 days) and the second notification user interface object 646b corresponds to a notification 628 generated on a second date (e.g., 5 months, 5 days). Accordingly, computer system 600 displays a history of hypertension notifications generated by computer system 600 and/or computer system 624 within notification area 646 of hypertension user interface 644. Thus, a user associated with computer system 600 and computer system 624 may access and view a history of hypertension notifications that have been generated by computer system 600 and/or computer system 624. In some embodiments, notification area 646 includes more notification user interface objects than two notification user interface objects 646a and 646b (e.g., when computer system 600 and/or computer system 624 have generated additional hypertension notifications). In some embodiments, computer system 600 displays notification user interface objects (e.g., nearest at the top, longest at the bottom) within notification area 646 in reverse order of time. In some embodiments, computer system 600 displays a predetermined number of notification user interface objects in notification area 646 and displays a user interface object (e.g., "view all") that, when selected, causes computer system 600 to display a list of notification user interface objects for all hypertension notifications generated by computer system 600 and/or computer system 624. In some embodiments, computer system 600 resizes notification area 646 on hypertension user interface 644 such that notification user interface objects corresponding to each respective hypertension notification are displayed on hypertension user interface 644.

In some embodiments, computer system 600 and/or computer system 624 determine that data collected over a predetermined period of time does not meet the set of notification criteria. In response to determining that the data collected over the predetermined period of time does not meet the set of notification criteria, computer system 600 forego displaying notifications 628 and 632 and forego displaying notification user interface objects 646a and 646b on hypertension user interface 644.

At fig. 6L, computer system 600 detects user input 650h (e.g., a flick gesture) corresponding to selection of first notification user interface object 646 a. In response to detecting the user input 650h, the computer system 600 displays a health event user interface 634 corresponding to the notification 632 generated by the computer system 600 and/or the computer system 624 on a third date (e.g., 6 months, 5 days), as shown in fig. 6J. In some embodiments, in response to user input corresponding to selection of the second notification user interface object 646b, the computer system 600 displays a health user interface 634 corresponding to a notification 628 generated by the computer system 600 and/or computer system 624 on a second date (e.g., 5 months, 5 days).

Additionally, at fig. 6L, the know more region 648 of the hypertension user interface 644 includes a first user interface object 648a (e.g., labeled "must know matters"), a second user interface object 648b (e.g., labeled "how hypertension notification works"), and a third user interface object 648c (e.g., labeled "know more" and/or "about hypertension"). In response to user input corresponding to selection of user interface objects 648a, 648b, and/or 648c, computer system 600 displays an educational user interface that provides additional details and/or information to the user regarding hypertension, hypertension notification, and/or suggested actions of the user as a result of receiving the hypertension notification.

At FIG. 6L, computer system 600 detects user input 650i (e.g., swipe gesture; swipe up gesture) on hypertension user interface 644. In response to detecting user input 650i, computer system 600 translates hypertension user interface 644 and displays additional options area 652 of hypertension user interface 644 (e.g., concurrently with learning more area 648, displaying additional options area 652 and ceasing to display notification area 646), as shown in fig. 6M. At FIG. 6M, the additional options region 652 includes a favorites user interface object 652a, all data user interface objects 652b, and a source user interface object 652c.

In response to user input corresponding to selection of the favorites user interface object 652a, the computer system 600 is configured to add the user interface object to the health user interface 604 displayed in a favorites area (e.g., an area of the health user interface 604 that includes health data user interface objects 604a and/or 604 b). Thus, after enabling and/or activating the hypertension notification, information related to the hypertension notification may be included on the health user interface 604, regardless of whether the hypertension notification was recently generated (e.g., by the computer system 600 and/or the computer system 624).

In response to user input corresponding to all data user interface objects 652b, computer system 600 displays a list of dates and/or times that data was collected and/or measured by sensors 618, 620, and 622 of computer system 624. In some embodiments, in response to user input corresponding to selection of an item in the list of dates and/or times at which data was collected, computer system 600 displays additional information (e.g., a measurement value, a device used to collect the data, a date and/or time at which data was added to the health application, and/or a test type).

In response to user input corresponding to source user interface object 652c, computer system 600 displays an additional user interface having information related to the computer system and/or device used to collect and/or measure data used to determine whether to generate a hypertension notification. In some embodiments, the additional user interface also includes information related to other applications (e.g., applications other than health applications), devices, and/or software for which the user has provided access to data used by computer system 600 and/or computer system 624 to determine whether to generate notifications of hypertension.

In some embodiments, computer system 624 is further configured to generate and display a notification in response to determining that the data collected over the predetermined period of time meets the set of notification criteria. For example, at fig. 6N, computer system 624 includes a display generation component 654, and computer system 624 displays notification 656 via display generation component 654. The notification 656 may be generated by the computer system 624 and/or the computer system 600 and may be displayed simultaneously with one of the notifications 628, 632. Thus, the user may be notified about potential hypertension events on both computer system 600 and computer system 624.

At fig. 6N, computer system 624 detects user input 650j (e.g., a tap gesture) on notification 656. In response to detecting the user input 650j, the computer system 624 displays a notification user interface 658 via the display generation component 654, as shown in fig. 6O. The notification user interface 658 includes an indication 658a (e.g., text indication) associated with the notification and knowledge of the more user interface objects 658b. As set forth above, notification 656 and notification user interface 658 do not include the user's blood pressure measurements (e.g., numerical and/or quantitative values representing systolic and/or diastolic blood pressure). In contrast, notification 656 and notification user interface 658 notify the user that data collected over a predetermined period of time indicate that the user may have hypertension (e.g., based on data collected over a predetermined period of time, the user is at risk for hypertension). In some implementations, the notification user interface 658 includes an indication 658a that can correspond to the information region 634a of the health event user interface 634. However, notification user interface 658 does not include the information provided in notification details area 636 and device details area 638 of health event user interface 634. Accordingly, the indication 658a may prompt the user to display the health user interface 604 and/or the health event user interface 634 using the computer system 600 to ultimately obtain the information provided in the notification details area 636 and the device details area 638 of the health event user interface 634.

At FIG. 6O, computer system 624 detects user input 650k (e.g., a flick gesture) on more user interface object 658 b. In response to detecting the user input 650k, the computer system 624 displays an educational user interface 660, as shown in fig. 6P. The educational user interface 660 provides instructions (e.g., textual instructions) related to information about hypertension, suggested actions taken by the user as a result of receiving the notification 656, and/or information about how to generate the notification 656.

Fig. 7 is a flow chart illustrating a method for generating notifications associated with health events using an electronic device, in accordance with some embodiments. The method 700 is performed at a device (e.g., 100, 300, 500) having one or more output devices and one or more sensors. Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, the method 700 provides an intuitive way for generating notifications associated with health events. The method reduces the cognitive burden on the user to access information about the health event, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to access information about health events faster and more efficiently saves power and increases the time between battery charges.

Computer systems (e.g., 100, 300, 500, 600, and/or 624) (e.g., electronic devices, smart devices such as smartwatches or smartphones, mobile devices, wearable devices) communicate with: one or more output devices (e.g., 602 and/or 654) (e.g., a display generating component (display, such as a touch screen display), an audio generating component (e.g., audio circuitry; integrated speaker; connected speaker), a haptic output component (e.g., haptic feedback controller; haptic motor), and one or more sensors (e.g., 618, 620, and/or 622) (e.g., photoplethysmograph sensor, gyroscopic sensor, and/or electrocardiograph sensor).

The computer system receives (702) first data associated with a user of the computer system from one or more sensors (e.g., 618, 620, and/or 622) (e.g., periodically and/or intermittently receiving measurement data from the one or more sensors, wherein the data from the one or more sensors includes data indicative of light absorption by skin of the user associated with the computer system (e.g., one or more measurements received from a photoplethysmograph sensor), data indicative of orientation and/or angular velocity of the computer system (e.g., one or more measurements received from a gyroscope sensor), and/or data indicative of voltage over time (e.g., one or more measurements of electrical activity of the heart received from an electrocardiogram sensor)). The first data from the one or more sensors (e.g., 618, 620, and/or 622) does not include direct measurements of pressure (e.g., values from sensors configured to specifically measure pressure such as pressure gauges, pressure transducers, strain gauges, and/or piezometers). In some embodiments, the data from the one or more sensors is data from (e.g., generated by; associated with; relating to) a user of the computer system. In some embodiments, the data from the one or more sensors includes indirect measurements of pressure. For example, raw data from one or more sensors (e.g., as a seed to an algorithm) may be utilized to calculate and/or estimate pressure, such as systolic blood pressure and/or diastolic blood pressure. In some embodiments, the computer system does not use the data to indirectly determine and/or calculate a numerical measurement of the pressure.

In response to receiving the first data (704) from the one or more sensors (e.g., 618, 620, and/or 622) and in accordance with a determination that the first data from the one or more sensors (e.g., 618, 620, and/or 622) meets a set of hypertension notification criteria (e.g., the computer system uses the data from the one or more sensors to make an assessment as to whether a user associated with the computer system is at risk of chronic hypertension (e.g., the user associated with the computer system is suffering from a sustained high blood pressure rather than being considered a primary instance of high blood pressure, an estimate, and/or a blood pressure measurement result), the computer system uses the data from the one or more sensors to generate a risk score indicating chronic hypertension and the risk score exceeds a threshold), the computer system generates (706) (e.g., outputs; displays; indicates a notification (e.g., 628,632,656) (e.g., the data from the one or more sensors is associated with the computer system is at risk) and/or a smart watch (e.g., the computer system is in communication with a primary instance of high blood pressure) and generates a signal (e.g., the computer system is not being displayed) (e.g., a primary instance of a watch, a display, a smart watch is not being displayed) and the risk score is generated) is displayed (e.g., a smart watch is displayed), the signal is received by the external device, the signal causing the external device to display a notification on a display generating part of the external device). In some embodiments, the set of hypertension notification criteria does not include (e.g., does not include any) criteria based on (e.g., in view of) blood pressure values (e.g., diastolic and/or systolic values of a user of the computer system). In some embodiments, the set of hypertension notification criteria does not include criteria based on pressure measurements (e.g., any criteria).

In response to receiving the first data (704) from the one or more sensors (e.g., 618, 620, and/or 622), and in accordance with a determination that the first data from the one or more sensors (e.g., 618, 620, and/or 622) does not meet the set of hypertension notification criteria (e.g., the computer system uses the data from the one or more sensors to make an assessment as to whether a user associated with the computer system is at risk of chronic hypertension (e.g., the user associated with the computer system does not have sustained high blood pressure), the computer system uses the data from the one or more sensors to generate a risk score indicative of chronic hypertension, and the risk score does not exceed a threshold), the computer system discards (708) generating a notification of a hypertension event (e.g., 628, 632, 656) (e.g., the computer system and an external device do not display the notification because the data from the one or more sensors indicates that the user associated with the computer system is not at risk of chronic hypertension).

Conditionally generating a notification indicating a hypertension event provides feedback to the user regarding the received first data and the relationship of the data to the set of hypertension notification criteria. Providing improved user feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the first data associated with the user of the computer system includes data received from one or more sensors (e.g., 618, 620, and/or 622) over a first period of time selected from the group consisting of: a period of time greater than 1 hour; a period of greater than 1 day; and a period of greater than 1 week. In some embodiments, the first data is intermittent sensor data from the time period. In some embodiments, intermittent data is collected at regular intervals. In some embodiments, intermittent data is collected at irregular levels. In some embodiments, the first data is continuous sensor data from the time period.

In some embodiments, the first data associated with a user of the computer system includes a plurality of data subsets (e.g., the first data is intermittently collected data), the plurality of data subsets including: a first subset of data received within a second time period (e.g., a measurement time window (e.g., 1 second)); and beginning the received second subset of data after a third period of time has elapsed (e.g., a time interval between the collection of the first subset of data and the collection of the second subset of data (e.g., a 10 second period after the collection of the first subset of data)) after the first subset of data is received (e.g., after the end of the first period of time). The third time period is greater than the second time period.

Conditionally generating notifications based on data collected over multiple time periods reduces the risk of transient errors in data collection and reduces the risk of false notifications. Reducing the occurrence of error notifications enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the set of hypertension notification criteria includes criteria that are met when a risk score (e.g., a quantitative value derived or calculated based on data) exceeds a threshold (e.g., an empirically derived value calculated based on a plurality of clinical patients including patients diagnosed with hypertension and patients not diagnosed with hypertension). The risk score is generated based on first data associated with a user of the computer system.

In some embodiments, the one or more sensors (e.g., 618, 620, and/or 622) are selected from the group consisting of photoplethysmograph sensors, gyroscopic sensors, electrocardiographic sensors, accelerometers, and combinations thereof.

In some embodiments, the first data associated with a user of the computer system does not include data from a vibration sensor. In some embodiments, the one or more sensors do not include (e.g., do not include any) sensors that measure vibration and/or pressure values.

In some embodiments, the computer system is not in communication with (e.g., does not include) a component (e.g., any component) that actively applies mechanical pressure (e.g., a blood pressure cuff) to a user of the computer system. In some embodiments, the one or more sensors (e.g., 618, 620, and/or 622) do not include (e.g., do not include any) sensors (e.g., pressure sensors) that measure data for a fourth period of time (e.g., 1 second, 30 seconds, 1 minute, 1 hour) after the active mechanical pressure is applied to the user of the computer system.

In some embodiments, a user of a computer system meets a set of feature qualification criteria. In some embodiments, the feature eligibility criteria include criteria that are met when the user has been determined to exceed a first age (e.g., to exceed 22 years). In some embodiments, the method further comprises: in some embodiments, if the user of the computer system does not meet the set of feature eligibility criteria, no data is collected from the sensor for determining whether to provide a notification indicative of a hypertension event, and no determination is made based on the set of hypertension notification criteria.

In some embodiments, the set of hypertension notification criteria includes criteria that are met when a user of the computer system meets a set of feature eligibility criteria. In some embodiments, the feature eligibility criteria include criteria that are met when the user has been determined to exceed a first age (e.g., to exceed 22 years).

Conditionally generating notifications based on data of users that meet a set of feature eligibility criteria reduces the risk of generating false notifications (e.g., due to errors caused by user diseligibility). Reducing the occurrence of error notifications enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the computer system receiving first data associated with a user of the computer system from one or more sensors (e.g., 618, 620, and/or 622) includes the computer system receiving the first data within a first predetermined period of time (e.g., 1 day period; 7 day period; 15 day period; 30 day period). In some embodiments, the set of hypertension notification criteria includes criteria that are met when data has been collected for at least a predetermined period of time.

In some embodiments, after the computer system receives first data associated with a user of the computer system from one or more sensors (e.g., 618, 620, and/or 622) within a first predetermined period of time, the computer system receives second data associated with the user of the computer system from one or more sensors (e.g., 618, 620, and/or 622), wherein the second data is received within a second predetermined period of time that does not overlap the first predetermined period of time (e.g., a period of time that is equal to the first predetermined period of time). In response to the computer system receiving second data from the one or more sensors and in accordance with a determination that the second data from the one or more sensors meets the set of hypertension notification criteria, the computer system generates a second notification (e.g., 632) indicative of a hypertension event associated with a user of the computer system via the one or more output devices (e.g., 602 and/or 654).

In some embodiments, the first data and the second data are non-overlapping data sets. In some embodiments, a first notification indicating a hypertension event may be issued based on the first data (e.g., if the first data meets the set of hypertension notification criteria issues), and a second notification indicating a hypertension event may be issued based on the second data (e.g., if the second data meets the set of hypertension notification criteria issues). In some embodiments, the first data is stored in the first data buffer until a first predetermined period of time has elapsed, and the computer system resets the first data buffer before receiving the second data and storing the second data in the first data buffer.

Conditionally generating the first notification and the second notification based on the collected separate data sets makes the first notification and the second notification independent and reduces the risk that transient, abnormal data will affect multiple notifications. Generating independent notifications and reducing the occurrence of error notifications enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to use the computer system more quickly and efficiently.

In some implementations, one or more output devices (e.g., 602 and/or 654) include display generating components (e.g., 602 and/or 654), and the computer system communicates with one or more input devices (e.g., 602 and/or 654) (e.g., touch-sensitive surface, mouse, microphone). The computer system receives a first set of one or more inputs (e.g., 650 f) corresponding to a notification (e.g., 628) via one or more input devices (e.g., 602) (e.g., a touch gesture or mouse click on a displayed notification as a user-selectable graphical object; a verbal command received after outputting an audio notification). In response to the first set of one or more inputs (e.g., 650 f), the computer system displays, via the display generation component (e.g., 602), a first user interface (e.g., 634) that includes first information (e.g., 634a, 636b, 636c, and/or 638) corresponding to the first data (e.g., information about when the data was received, information about the sensors, values of the first data and/or a subset of the first data).

Displaying the interface with additional information corresponding to the first data provides feedback to the user regarding the received first data. Providing improved user feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some implementations, one or more output devices (e.g., 602 and/or 654) include a display generation component (e.g., 602 and/or 654). After the computer system generates notifications (e.g., 628, 632, and/or 656) indicating the hypertension event, the computer system displays a second user interface (e.g., 644) that includes information (e.g., 646a and/or 646 b) (e.g., time the notification was generated; total number of notifications generated; data for generating notifications) corresponding to one or more notifications (e.g., 628, 632, and/or 656) indicating the hypertension event, including notifications (e.g., 628, 632, and/or 656) indicating the hypertension event. In some embodiments, the second user interface includes a set of one or more user-selectable graphical objects that affect one or more settings associated with the notification indicating the hypertension event (e.g., frequency of notification, duration of notification, one or more criteria of the set of hypertension notification criteria).

A second interface, displaying information with information corresponding to a notification indicating a hypertension event, provides additional feedback to the user regarding the notification and data received by the system. Providing improved user feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the notification (e.g., 628, 632, and/or 656) indicating the hypertension event does not include a numerical (e.g., quantitative) indication of the blood pressure value of the user of the computer system. In some embodiments, the notification does not include any numerical or quantitative values. In some embodiments, the notification includes only non-numeric information.

In some embodiments, the first data associated with the user of the computer system includes a second plurality of data subsets (e.g., the first data is intermittently collected data) including a third data subset received at a first time and a fourth data subset received a second predetermined period of time after the third data subset is received (e.g., the second time being a predetermined time). The third subset of data is not received in response to user input (e.g., any user input; the first time is a predetermined time; the third subset of data is received independently of user input (e.g., is received automatically)). In some embodiments, the fourth subset of data is not received in response to user input (e.g., any user input; the second time is a predetermined time; the fourth subset of data is received independently of user input (e.g., is received automatically)).

Conditionally generating notifications based on separate data sets that are automatically collected over time reduces the risk of false notifications and missing data collections. Reducing the occurrence of error notifications and reducing the risk of missing data collections enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to use the computer system more quickly and efficiently.

It should be noted that the details of the process described above with respect to method 700 (e.g., fig. 7) also apply in a similar manner to the method described below. For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, a notification generated via method 700 may be used to prompt a user to initiate a data collection log for a predefined period of time, as set forth in method 900. For the sake of brevity, these details are not repeated hereinafter.

Fig. 8A-8U illustrate an exemplary user interface for managing health information over a predefined period of time, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in fig. 9.

Fig. 8A shows a computer system 600 having a display generation component 602 and displaying a health user interface 604 of a health application of the computer system 600 on a first date (e.g., monday of 11 days 5 month) via the display generation component 602. At fig. 8A, the health user interface 604 includes a first health data user interface object 604a and a third health data user interface object 604c. The first health data user interface object 604a includes information related to a first health parameter (e.g., "weight") of a user associated with the computer system 600, and the third health data user interface object 604c includes information related to a second health parameter (e.g., "blood pressure") of a user associated with the computer system 600. In some embodiments, the health user interface 604 is a home screen or default screen of the health application that the computer system 600 displays via the display generation component 602 when the health application is launched. In some embodiments, the health user interface 604 includes more than two health data user interface objects or one health data user interface object.

At fig. 8A, computer system 600 detects user input 850a (e.g., a flick gesture) corresponding to selection of third health data user interface object 604c. In response to detecting the user input 850a, the computer system 600 displays a blood pressure user interface 800 for the first date, as shown in FIG. 8B. The blood pressure user interface 800 includes a blood pressure graphical element 802 (e.g., a chart) that includes visual indications of one or more blood pressure measurements (e.g., a set of data points corresponding to systolic and diastolic blood pressure), if available, received by the computer system 600. Computer system 600 is not configured to measure blood pressure of a user associated with computer system 600 (e.g., apply pressure to the user and/or measure pressure and/or vibration values). Instead, computer system 600 receives blood pressure data (e.g., blood pressure measurements) via user input and/or via an external device (e.g., a blood pressure measurement device in communication with computer system 600).

Blood pressure data received by computer system 600 is included on blood pressure graphical element 802. At fig. 8B, blood pressure user interface 800 also includes an information user interface object 803. In response to detecting user input corresponding to selection of the information user interface object 803, the computer system 600 displays an indication of a particular standard and/or rating system associated with blood pressure data received by the computer system 600 and/or displayed on the blood pressure graphical element 802. For example, different countries, regions and/or regions around the world utilize different rating systems to measure blood pressure and/or determine whether a person has high, low and/or normal blood pressure. Thus, the information user interface object 803 enables the computer system 600 to display indicators that provide information regarding particular criteria and/or rating systems applicable to the blood pressure data corresponding to the blood pressure user interface 800.

In some embodiments, computer system 600 filters blood pressure data displayed on blood pressure graphical element 802. For example, the blood pressure user interface 800 includes a date filter 804 that enables the computer system 600 to adjust the time scale of the blood pressure graphical element 802 and filter blood pressure data displayed on the blood pressure graphical element 802 based on the date. At fig. 8B, date filters 804 include a day filter 804a, a week filter 804B, a month filter 804c, and a year filter 804. In some embodiments, the data filter 804 may include other suitable time periods for filtering blood pressure data. At fig. 8B, the day filter 804a of the date filter 804 is activated (e.g., selected), and thus, the computer system 600 displays all blood pressure data received by the computer system 600 on a particular day (e.g., the day) on the blood pressure graphical element 802. In response to detecting user input on week filter 804b, computer system 600 displays all blood pressure data received by computer system 600 at a particular week (e.g., including the week of the day) on blood pressure graphical element 802. In response to detecting user input on month filter 804c, computer system 600 displays all blood pressure data received by computer system 600 at a particular month (e.g., including the month of the day) on blood pressure graphical element 802. Similarly, in response to detecting user input on the year filter 804d, the computer system 600 displays all blood pressure data received by the computer system for a particular year (e.g., including the year of the day) on the blood pressure graphical element 802.

In addition to filtering the blood pressure data at the time the computer system 600 receives the blood pressure data and/or the timestamp associated with the blood pressure data, the computer system 600 is configured to provide an indication of a particular blood pressure range (e.g., a normal blood pressure range, a low blood pressure range, and/or a high blood pressure range) on the blood pressure graphical element 802. Thus, the user can visually compare his or her blood pressure data with various blood pressure ranges to better understand his or her health. At fig. 8B, the computer system detects a user input 850B (e.g., a flick gesture) corresponding to a selection of a filter user interface object 806 of the blood pressure user interface 800. In response to detecting the user input 850b, the computer system 600 displays an indicator of the normal blood pressure range on the blood pressure graphical element 802 on the first date, as shown in fig. 8C.

At fig. 8C, the blood pressure graphical element 802 includes a first indicator 808 and a second indicator 810 that represent an upper limit (e.g., the first indicator 808) and a lower limit (e.g., the second indicator), respectively, of a normal range for a first portion (e.g., systolic blood pressure) of the blood pressure measurement. In addition, the blood pressure graphical element 802 includes a third indicator 812 and a fourth indicator 814 that represent an upper limit (e.g., third indicator 812) and a lower limit (e.g., fourth indicator 814), respectively, of a normal range of a second portion (e.g., diastolic blood pressure) of the blood pressure measurement. Accordingly, computer system 600 is configured to display indications of various blood pressure ranges in response to user input on filter user interface object 806 such that a user associated with computer system 600 can easily compare his or her blood pressure measurements to normal blood pressure ranges, low blood pressure ranges, and/or high blood pressure ranges.

At fig. 8C, blood pressure user interface 800 also includes a blood pressure log user interface object 816. As set forth in detail below, in response to user input corresponding to selection of the blood pressure log user interface object 816, the computer system 600 is configured to activate and/or initiate a schedule for recording blood pressure measurements over a selected time horizon. In response to activation and/or initiation of the schedule, the computer system 600 generates a notification that alerts the user to input and/or otherwise provide blood pressure measurements to the computer system 600 over a selected time frame. Thus, the schedule for recording blood pressure measurements facilitates the user's ability to track his or her blood pressure over a selected time frame, thereby improving the user's knowledge of his or her health.

At fig. 8C, computer system 600 detects user input 850C (e.g., a flick gesture) corresponding to a selection of blood pressure log user interface object 816. In response to detecting the user input 850c, the computer system 600 initiates a setup process for activating a schedule for recording blood pressure measurements and displays a first setup user interface 818 for a first date, as shown in fig. 8D. At fig. 8D, the first settings user interface 818 includes a text indication that provides the user with information related to a schedule for recording blood pressure measurements. At fig. 8D, computer system 600 detects a user input 850D (e.g., a tap gesture) corresponding to a selection of a setup user interface object 818a of first setup user interface 818. In response to detecting the user input 850d, the computer system 600 displays a second settings user interface 820 for the first date, as shown in FIG. 8E. The second setup user interface 820 includes a text indication related to a blood pressure measurement device (e.g., a manual blood pressure measurement device and/or a bluetooth blood pressure measurement device) that the user may use to measure his or her blood pressure. At fig. 8E, computer system 600 detects user input 850E (e.g., a flick gesture) corresponding to selection of a next user interface object 820a of second setup user interface 820. In response to detecting the user input 850e, the computer system 600 displays a third settings user interface 822 for the first date, as shown in FIG. 8F.

At fig. 8F, the third setup user interface 822 includes a first time range user interface object 822a, a second time range user interface object 822b, and a next user interface object 822c. The computer system 600 may initiate a schedule for recording blood pressure measurements over different time ranges based on a user selection of the first time range user interface object 822a or the second time range user interface object 822 b. At fig. 8F, the first time range user interface object 822a corresponds to a first time range of seven days and the second time range user interface object 822b corresponds to a second time range of 30 days. As set forth below, the schedule for recording blood pressure measurements over a first time range may include a first number of blood pressure measurements, such as two blood pressure measurements per day over a seven day range. The schedule for recording blood pressure measurements over a second time frame may include a second number of blood pressure measurements different from the first number of blood pressure measurements, such as one blood pressure measurement per day over a 30 day frame. Thus, the computer system 600 determines different time periods (e.g., half a day or one whole day) within the selected time range for recording the corresponding blood pressure measurements based on which time range is selected.

At fig. 8F, computer system 600 detects user input 850F (e.g., a flick gesture) corresponding to selection of user interface object 822a for a first time horizon. In some implementations, in response to detecting the user input 850f, the computer system 600 displays an indicator 824 on the first time range user interface object 822a indicating that the first time range associated with the first time range user interface object 822a is selected. After detecting the user input 850f, the computer system 600 detects a user input 850g (e.g., a flick gesture) corresponding to the selection of the next user interface object 822c. After detecting user input 850G (and optionally after detecting user inputs 850I, 850J, and/or 850k described below with reference to fig. 8G-8I), computer system 600 displays blood pressure user interface 800, as shown in fig. 8J.

Alternatively, at fig. 8F, computer system 600 detects user input 850h (e.g., a flick gesture) corresponding to selection of a second time range user interface object 822 b. In some implementations, in response to detecting the user input 850h, the computer system 600 displays an indicator 824 on the second time-scope user interface object 822b (e.g., instead of on the first time-scope user interface object 822 a) indicating that a second time-scope associated with the second time-scope user interface object 822b is selected. After detecting user input 850h, the computer system detects user input 850g corresponding to selection of the next user interface object 822c. After detecting user input 850G (and optionally after detecting user inputs 850I, 850j, and/or 850K described below with reference to fig. 8G-8I), computer system 600 displays blood pressure user interface 800, as shown in fig. 8K. In some embodiments, before computer system 600 detects user input 850f or user input 850h, computer system 600 deactivates and/or discards displaying the next user interface object 822c. Thus, the computer system 600 does not process and/or detect the user input 850g until after receiving the user input corresponding to the selection of one of the first time-range user interface object 822a or the second time-range user interface object 822 b.

While fig. 8F shows the selection of a timeframe as a schedule for recording blood pressure measurements for user interface objects 822a and 822b, in some embodiments, the third setup user interface 822 includes user interface objects that enable a user to enter a custom timeframe via a keyboard or other input device in addition to and/or in lieu of user interface objects 822a and 822 b.

At fig. 8F, in response to detecting the user input 850G, the computer system 600 displays a fourth settings user interface 826 for the first date, as shown in fig. 8G. The fourth settings user interface 826 includes text instructions that inform the user that the computer system 600 generates a notification that prompts the user to enter blood pressure measurements according to a schedule and/or selected time frame. In some embodiments, the fourth settings user interface 826 includes one or more user interface objects that, when selected, cause the computer system 600 to deactivate notification reminders associated with a schedule for recording blood pressure measurements. At fig. 8G, the computer system 600 detects a user input 850i (e.g., a tap gesture) corresponding to a selection of a next user interface object 826a of the fourth setup user interface 826. In response to detecting the user input 850i, the computer system 600 displays a fifth settings user interface 828 for the first date, as shown in FIG. 8H. The fifth settings user interface 828 includes text instructions that provide information to the user as to how to measure blood pressure to obtain a blood pressure measurement that is ultimately provided to the computer system 600 (e.g., via user input and/or transmission from an external device). At fig. 8H, computer system 600 detects user input 850j (e.g., a tap gesture) corresponding to selection of a next user interface object 828a of fifth settings user interface 828. In response to detecting the user input 850j, the computer system 600 displays a sixth settings user interface 830 for the first date, as shown in FIG. 8I.

The sixth settings user interface 830 includes a log blood pressure measurement user interface object 830a and a skip blood pressure measurement user interface object 830b. Thus, the sixth settings user interface 830 enables the user to provide (e.g., via selection of the log blood pressure measurement user interface object 830 a) a first blood pressure measurement for the schedule and/or complete settings, and to provide (e.g., via selection of the skip blood pressure measurement user interface object 830 b) a first blood pressure measurement for the schedule at a time subsequent to the current time. At fig. 8I, computer system 600 detects user input 850k (e.g., a flick gesture) corresponding to a selection of skip blood pressure measurement user interface object 830b. In response to detecting the user input 850K, the computer system 600 displays a blood pressure user interface 800 for the first date, as shown in fig. 8J and 8K. As set forth below, based on the computer system 600 detecting a user input 850F or 850h at FIG. 8F, the computer system 600 displays a blood pressure user interface 800 that includes a first schedule user interface object 832 (FIG. 8J) corresponding to a first time range or a second schedule user interface object 834 (FIG. 8K) corresponding to a second time range.

Alternatively, at fig. 8I, computer system 600 detects user input 850l (e.g., a flick gesture) corresponding to selection of log blood pressure measurement user interface object 830 a. In response to detecting the user input 850l, the computer system 800 displays a measurement input user interface 854, as shown in FIG. 8O.

Turning now to fig. 8J, the computer system 600 detects a user input 850f corresponding to selection of the first time range user interface object 822a and displays the blood pressure user interface 800 with the first schedule user interface object 832 for the first date. The first schedule user interface object 832 corresponds to the schedule being within a first timeframe of seven days. Thus, the first schedule user interface object 832 includes day indicators 832a-832g corresponding to respective days of the week. Alternatively, the first schedule user interface object 832 includes a first interval indicator 832h and a second interval indicator 832i. Because the first time range associated with the first schedule user interface object 832 is for a relatively short period of time (i.e., seven days versus 30 days), the first schedule user interface object 832 provides a plurality of blood pressure measurements per day. At fig. 8J, the first schedule user interface object 832 includes measurement indicators 836 that represent time periods (e.g., intervals) for respective blood pressure measurements over a first time range. In other words, the measurement indicator 836 indicates that the computer system 600 within the first time range is configured to prompt the user to provide (e.g., input and/or otherwise transmit) a respective time sub-range (e.g., half a day or 12 hours) of the blood pressure measurement to the computer system 600.

In addition, computer system 600 displays add measurement user interface object 838 on blood pressure user interface 800. In response to detecting a user input corresponding to a selection of add measurement user interface object 838, computer system 600 displays measurement input user interface 854 as illustrated in FIG. 8O. As explained in detail below with reference to fig. 8O, blood pressure measurements received by computer system 600 via measurement input user interface 854 correspond to respective measurement indicators 836 associated with the current time of day and/or day. In other words, in response to detecting a user input corresponding to selection of add measurement user interface object 838, computer system 600 is configured to receive and record blood pressure measurements corresponding to respective measurement indicators 836 associated with the current time of day and/or day, and not to receive and record blood pressure measurements corresponding to measurement indicators 836 not associated with the current time of day and/or day.

As set forth above, in response to detecting the user input 850h corresponding to the selection of the second time range user interface object 822b, the computer system 600 displays the blood pressure user interface 800 with the second schedule user interface object 834, as shown in fig. 8K. The second schedule user interface object 834 corresponds to the schedule being within a second time frame of 30 days. Thus, the second schedule user interface object 834 includes day indicators 834a-834g corresponding to respective days of the week in five weeks (e.g., rows within the second schedule user interface object 834) that occur within the course of 30 days. In contrast to the first schedule user interface object 832, the second schedule user interface object 834 does not include an interval indicator. Because the second time range associated with the second schedule user interface object 834 is for a relatively long period of time (i.e., 30 days versus 7 days), the second schedule user interface object 834 provides a single blood pressure measurement per day. In other words, because the second time range includes several weeks, the schedule for recording blood pressure measurements receives an amount of data sufficient to identify trends and/or patterns in the user's blood pressure, even when the data is entered and/or received once per day.

At fig. 8K, the second schedule user interface object 834 includes measurement indicators 840 that represent each day for a respective blood pressure measurement over a second time horizon. In other words, the measurement indicator 840 indicates that the computer system 600 within the second time range is configured to prompt the user to provide (e.g., input and/or otherwise transmit) various time sub-ranges (e.g., one day or 24 hours) of blood pressure measurements to the computer system 600.

At fig. 8K, computer system 600 detects user input 850m (e.g., a flick gesture) corresponding to a selection of add measurement user interface object 838. In response to detecting user input 850m, computer system 600 displays a measurement input user interface 854, as shown in FIG. 8O. As explained in detail below with reference to fig. 8O, blood pressure measurements received by computer system 600 via measurement input user interface 854 correspond to respective measurement indicators 840 associated with the current time of day and/or day. In other words, in response to detecting a user input corresponding to selection of add measurement user interface object 838, computer system 600 is configured to receive and record blood pressure measurements corresponding to respective measurement indicators 840 associated with the current time of day and/or day, and not to record blood pressure measurements corresponding to measurement indicators 840 not associated with the current time of day and/or day.

Turning now to fig. 8L, computer system 600 displays notification 842 on user interface 844 (e.g., a lock screen user interface and/or a home screen user interface) on a second date (e.g., 5 months 15 days friday) after the first date. Notification 842 corresponds to confirmation: the blood pressure measurement is received within a time period of the first time range and/or the second time range corresponding to the current time of day and/or the day. For example, notification 842 provides the user with the following confirmation: blood pressure measurements are received in the morning of 5 months 15 days friday when the time range is a first time range (e.g., seven days) and/or in the day of 5 months 15 days friday when the time range is a second time range (e.g., 30 days). In some embodiments, computer system 600 displays notification 842 after receiving a blood pressure measurement (e.g., via user input when computer system 600 displays measurement input user interface 854). In some embodiments, computer system 600 displays notification 842 in response to receiving a blood pressure measurement from an external device (e.g., a blood pressure measurement device configured to transmit wireless signals indicative of the blood pressure measurement to computer system 600 via bluetooth, wi-Fi, and/or Zigbee). In some embodiments, before computer system 600 displays a reminder notification (e.g., notification 846 at fig. 8M), computer system 600 displays notification 842 in response to receiving any blood pressure measurements, the reminder notification prompting the user to provide blood pressure measurements during a time period within the first time range and/or the second time range corresponding to the current time of day and/or time of day.

The computer system 600 is configured to prompt the user to provide the blood pressure measurement for a period of time corresponding to the current time of day and/or day within the first time range and/or the second time range in response to detecting that the blood pressure measurement has not been received. At fig. 8M, in response to detecting that no blood pressure measurement has been received within a threshold time (e.g., 1 hour, 6 hours, 8 hours, 10 hours, 12 hours) from the beginning of a time period (e.g., 12 pm in a day and/or 12 pm in a day) of the first time range and/or the second time range corresponding to the current time of day and/or day, computer system 600 displays notification 846 on user interface 844 on the second date. Thus, the computer system 600 prompts and/or alerts the user to provide blood pressure measurements such that the computer system 600 may receive blood pressure measurements for each time period within the first range and/or the second time range.

In some embodiments, in response to receiving the blood pressure measurement (e.g., via an external device, such as a bluetooth-enabled blood pressure device and/or sensor), computer system 600 is configured to remove notification 846 from and/or stop displaying notifications on user interface 844 and/or another user interface associated with the health application. Thus, when the reminder to provide the blood pressure measurement is no longer appropriate, the computer system 600 clears the reminder notification.

At fig. 8M, computer system 600 detects user input 850n (e.g., a long press gesture) corresponding to notification 846. In response to detecting the user input 850N, the computer system 600 displays a skip blood pressure measurement user interface object 848 and a log blood pressure measurement user interface object 852 on the user interface 844 on the second date, as shown in fig. 8N. In response to receiving a user input corresponding to a selection of skip blood pressure measurement user interface object 848, computer system 600 clears and/or removes notification 846 from user interface 844. In some embodiments, computer system 600 provides an additional notification prompting the user to provide a blood pressure measurement after detecting a predetermined period of time from the detection of a user input corresponding to the selection of skip blood pressure measurement user interface object 848.

At fig. 8N, computer system 600 detects user input 850o (e.g., a flick gesture) corresponding to selection of a log blood pressure measurement user interface object 852. In response to detecting user input 850O, computer system 600 displays a measurement input user interface 854 for the second date, as shown in FIG. 8O. As set forth above, computer system 600 may also display measurement result input user interface 854 in response to user inputs 850l and/or 850 m.

The measurement input user interface 854 includes a first measurement user interface object 854a and a second measurement user interface object 854b. At fig. 8O, computer system 600 detects user input 850p (e.g., a flick gesture) corresponding to a selection of first measurement user interface object 854 a. In addition, the computer system 600 detects one or more user inputs (e.g., via a keyboard and/or other input device) that correspond to a value of the first blood pressure measurement, such as systolic blood pressure from the blood pressure measurement. At fig. 8O, computer system 600 also detects user input 850q (e.g., a flick gesture) corresponding to a selection of a second measurement user interface object 854b. In addition, the computer system 600 detects one or more user inputs (e.g., via a keyboard and/or other input device) that correspond to a value of the second measured blood pressure, such as a diastolic blood pressure from the blood pressure measurement. In some embodiments, the measurement input user interface 854 includes a single measurement user interface object that enables a user to input two portions of a blood pressure measurement (e.g., systolic and diastolic pressures).

At FIG. 8O, the measurement input user interface 854 is displayed at 9:41 night for 5 months 15 days (e.g., the day). Thus, inputs corresponding to the first measurement user interface object 854a and the second measurement user interface object 854b (e.g., collectively blood pressure measurements) correspond to respective measurement indicators 836 and/or 840 for the evening and/or full day of the 5 month 15 friday. At fig. 8O, the measurement input user interface 854 does not include a user interface object that enables the computer system 600 to receive a measurement corresponding to another measurement indicator that is not associated with the current time of day and/or day.

In some embodiments, computer system 624, which is in communication with computer system 600 (e.g., and associated with the same user as computer system 600), is also configured to provide notifications related to a schedule for collecting blood pressure measurements. For example, at FIG. 8P, the computer system 624 displays a notification user interface 856. The computer system 624 displays the notification user interface 856 in response to determining that the computer system 600 did not receive blood pressure measurements within a period of time within the first time range and/or the second time range. In some embodiments, computer system 600 displays notification user interface 856 when computer system 624 displays notification 846.

At fig. 8P, the notification user interface 856 includes a first measurement user interface object 856a and a second measurement user interface object 856b. At fig. 8P, the computer system 624 detects a user input 850r (e.g., a flick gesture) corresponding to a selection of a first measurement user interface object 856 a. In addition, computer system 624 detects one or more user inputs (e.g., via a keyboard and/or another input device) that correspond to a value of the first blood pressure measurement, such as systolic blood pressure from the blood pressure measurement. At fig. 8P, the computer system 624 also detects a user input 850s (e.g., a flick gesture) corresponding to the selection of the second measurement user interface object 856b. In addition, computer system 624 detects one or more user inputs (e.g., via a keyboard and/or another input device) that correspond to a value of a second measurement of blood pressure, such as diastolic blood pressure from the blood pressure measurement. In some embodiments, notification user interface 856 includes a single measurement user interface object that enables the user to input two portions of a blood pressure measurement (e.g., systolic and diastolic pressures).

At FIG. 8P, the notification user interface 856 is displayed at 9:41 night for 5 months 15 days (e.g., the day). Thus, inputs corresponding to the first measurement user interface object 856a and the second measurement user interface object 856b (e.g., collectively blood pressure measurements) correspond to respective measurement indicators 836 and/or 840 for the evening and/or full day of the 5 month 15 friday. At fig. 8P, the measurement input user interface 856 does not include a user interface object enabling the computer system 624 to receive a measurement corresponding to another measurement indicator not associated with the current time of day and/or day.

In response to receiving the blood pressure measurement via the measurement input user interface 854 and/or the notification user interface 856, the computer system 600 updates the respective measurement indicators 836 and/or 840 to reflect the receipt of the blood pressure measurement, as shown in fig. 8Q. At fig. 8Q, computer system 600 displays a blood pressure user interface 800 that includes a second schedule user interface object 834 corresponding to a second time horizon. In response to receiving the blood pressure measurement on the second date (e.g., 5 month 15 day friday), computer system 600 updates the appearance of measurement indicator 840a (e.g., populates measurement indicator 840a with a check mark) corresponding to the second date (e.g., 5 month 15 day friday) to indicate that computer system 600 received a blood pressure measurement corresponding to the time period associated with measurement indicator 840 a. In addition, the computer system 600 updates the blood pressure graphical element 802 to include an indication (e.g., a pair of data points) of the blood pressure measurement corresponding to the received second date. In some embodiments, computer system 600 stops displaying add measurement user interface object 838 and/or adjusts the appearance of add measurement user interface object 838 to further indicate that a current time period blood pressure measurement associated with the current time of day and/or day has been received.

At fig. 8Q, computer system 600 also updates the appearance of measurement indicators 840b, 840d, and 840e, which indicate that computer system 600 also received blood pressure measurements for the dates associated with measurement indicators 840b, 840d, and 840 e. In addition, the computer system 600 has not updated the appearance of the measurement indicator 840c corresponding to tuesday of 12 days 5 months, which indicates that the computer system 600 did not receive blood pressure measurements on the day within the second range.

In some embodiments, computer system 600 is configured to receive blood pressure measurements for days and/or other time periods (e.g., half a day) that occur outside of a current time period (e.g., the current time of day and/or day). At fig. 8Q, computer system 800 receives user input 850t corresponding to add data user interface object 858 of blood pressure user interface 800. In response to detecting the user input 850t, the computer system 600 displays a previous measurement input user interface 860, as shown in FIG. 8R. The previous measurement input user interface 860 is similar to the measurement input user interface 854, but also includes a date user interface object 860a and a time user interface object 860b. In response to detecting one or more user inputs corresponding to the date user interface object 860a, the computer system 600 is configured to update the date indicator 860c displayed in the date user interface object 860 a. The date indicator 860c corresponds to a date at which an input blood pressure measurement (e.g., a blood pressure measurement input via the first measurement user interface object 854a and the second measurement user interface object 854 b) was taken. Similarly, in response to detecting one or more user inputs corresponding to the time user interface object 860b, the computer system 600 is configured to update the time indicator 860d displayed in the time user interface object 860b. The time indicator 860d corresponds to a time at which an input blood pressure measurement (e.g., a blood pressure measurement input via the first measurement user interface object 854a and the second measurement user interface object 854 b) was taken on a date associated with the date indicator 860c. Thus, in some embodiments, computer system 600 is configured to receive blood pressure measurements associated with a day and/or time preceding or preceding the day (e.g., a time period within the first time range and/or the second time range that is not associated with the current time of day and/or day).

Turning now to fig. 8S, computer system 600 displays a blood pressure user interface 800 having a second schedule user interface object 834 on a third date (e.g., tuesday 9 th month) corresponding to a second time horizon. At fig. 8S, computer system 600 has updated each measurement indicator 840 of second schedule user interface object 834 to indicate that blood pressure measurements for each time period (e.g., daily) of the second time range (e.g., 30 days) have been received. In other words, at fig. 8S, the computer system 600 displays the blood pressure user interface 800 with the second schedule user interface 834 after the second time frame is completed (e.g., 30 days have elapsed since the schedule for collecting blood pressure measurements was initiated). In response to detecting completion of the second time range, the computer system 600 also displays a shared user interface object 862 and a new schedule user interface object 864. Thus, in some embodiments, computer system 600 foregoes displaying shared user interface object 862 and/or new schedule user interface object 864 until the second time range (and/or another selected time range) has elapsed.

The sharing user interface object 862 enables sharing of blood pressure measurements received during the second time range with an external device. For example, in response to user input corresponding to selection of the shared user interface object 862, the computer system 600 generates an exportable file including blood pressure measurements received during the second time range. Thus, computer system 600 may transmit the exportable file to an external device via email, via a short message service, via bluetooth, via Wi-Fi, via short range communication, and/or via another suitable communication technology.

The new schedule user interface object 864 enables the computer system 600 to begin a new schedule for collecting blood pressure measurements. For example, in response to detecting a user input corresponding to selection of the new schedule user interface object 864, the computer system 600 displays the first settings user interface 818 and/or the third settings user interface 822. Thus, computer system 600 is configured to receive one or more inputs that cause the computer system to activate and/or initiate another schedule for collecting blood pressure measurements.

As set forth above, computer system 600 is configured to generate a hypertension notification in response to determining that a set of notification criteria (e.g., hypertension notification criteria) have been met. At fig. 8T, computer system 600 displays notification 628 on user interface 630 (e.g., a lock screen user interface and/or a home screen user interface). At fig. 8T, computer system 600 detects user input 850u (e.g., a long press gesture) on notification 628. In response to detecting user input 850U, computer system 600 displays new schedule user interface object 866 and/or skips schedule user interface object 868 on user interface 630, as shown in fig. 8U. Thus, computer system 600 may activate and/or initiate a new schedule for collecting blood pressure measurements in response to user input 850u on notification 628 and additional user input corresponding to selection of new schedule user interface object 866. Thus, after the computer system 600 generates the hypertension notification, the user may cause the computer system 600 to activate and/or initiate a schedule for collecting blood pressure measurements. In contrast, in response to detecting a user input corresponding to skip list user interface object 868, computer system 600 clears and/or removes notification 628 from user interface 630.

Fig. 9 is a flowchart illustrating a method for managing health information within a predefined time frame using an electronic device, according to some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500, 600, and/or 624) having a display generating component and one or more input devices. Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, the method 900 provides an intuitive way for managing health information within a predefined time frame. The method reduces the cognitive burden on the user to track and/or monitor health information, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to more quickly and efficiently track and/or monitor health information saves power and increases the time between battery charges.

Computer systems (e.g., 100, 300, 500, 600, and/or 624) (e.g., electronic devices, smart devices such as smartwatches or smartphones, mobile devices, wearable devices) communicate with: display generation component (e.g., 602 and/or 654) (e.g., a display, such as a touch screen display); and one or more input devices (e.g., 602 and/or 654) (e.g., keyboard, mouse, touch-sensitive surface).

The computer system receives (902), via one or more input devices (e.g., 602 and/or 654), a first set of one or more inputs (e.g., 850a, 850c, 850d, 850e, 850f, 850g, 850h, 850i, 850j, and/or 850 k) (e.g., one or more taps, gestures, mouse clicks) including a first input (e.g., 850f and/or 850 h) selecting a time range (e.g., selecting a user-interactive graphical user interface object corresponding to the first time range from a plurality of user-interactive graphical user interface objects corresponding to different time ranges; entering a value corresponding to the time range).

In response to receiving the first set of one or more inputs, the computer system displays (904) a first user interface (e.g., 800) (e.g., a user interface including data and/or information associated with recorded measurements of recorded user characteristics (e.g., blood pressure)) via a display generation component (e.g., 602 and/or 654).

In accordance with a determination that the first user input (e.g., 850 f) corresponds to a selection of a first time range (e.g., one week; two weeks; one month), the first user interface (e.g., 800) includes (906) a first plurality of measurement indicators (e.g., 836) (e.g., 14 measurement indicators) within the first time range.

In accordance with a determination that the first user input (e.g., 850 h) corresponds to a selection of a second time range (e.g., one week; two weeks; one month) that is different from the first time range, the first user interface (e.g., 800) includes (908) a second plurality of measurement indicators (e.g., 840) (e.g., 30 measurement indicators) within the second time range. In some embodiments, the first time range is a subset of the second time range (e.g., the first time range is the first week of the month, and the second time range is the entire month).

The first user interface (e.g., 800) further includes (910) a first measurement entry user-interactive graphical user interface object (e.g., 838) (e.g., corresponding to an added measurement affordance based on a respective measurement indicator of the first user input) that, upon selection via one or more input devices (e.g., 602) (e.g., via a tap gesture on a touch-sensitive surface), initiates a measurement entry process (e.g., displays a second user interface that includes one or more user-interactive graphical user interface objects that enable a user to enter blood pressure measurements).

According to the first user interface (e.g., 800) including a first plurality of measurement indicators (e.g., 836) within a first time range, the measurement entry process includes (912) the computer system entering blood pressure measurements (e.g., systolic and/or diastolic measurements) corresponding to the first time range and the current day (e.g., the current time of day and/or day when the first measurement entry user interactive graphical user interface object was selected). In some embodiments, the blood pressure measurement corresponds to a first time range and to a particular measurement indicator of the first plurality of measurement indicators (e.g., a particular measurement indicator of the first plurality of measurement indicators that corresponds to the current time of day and/or day).

According to the first user interface (e.g., 800) including a second plurality of measurement indicators (e.g., 840) within a second time range, the measurement entry process includes (914) the computer system entering blood pressure measurements corresponding to the second time range and the current day (e.g., the current time of day and/or day when the first measurement entry user interactive graphical user interface object was selected). In some embodiments, the blood pressure measurement corresponds to a second time range and to a particular measurement indicator of the second plurality of measurement indicators (e.g., a particular measurement indicator of the second plurality of measurement indicators that corresponds to the current time of day and/or day).

Displaying a user interface comprising a first plurality of measurement indicators or a second plurality of measurement indicators according to the selected time range, providing a user with control over the content of the user interface for subsequent input related to blood pressure measurements, thereby improving user-system interaction. Improving user-system interactions enhances the operability of a computer system and makes the user-system interface more efficient (e.g., by helping a user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the first plurality of measurement indicators (e.g., 836) (e.g., 14) includes a first number of measurement indicators, and the second plurality of measurement indicators (e.g., 840) includes a second number of measurement indicators (e.g., 30) different from the first number. In some embodiments, the first plurality of measurement indicators comprises a plurality of indicators for a single first day, and the second plurality of measurement indicators comprises a single indicator for the single first day.

Different numbers of measurement indicators are displayed according to the selected time range, providing the user with control over the content of the user interface for subsequent input related to the blood pressure measurement, thereby improving user-system interaction. Improving user-system interactions enhances the operability of a computer system and makes the user-system interface more efficient (e.g., by helping a user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the computer system communicates with one or more blood pressure sensors (e.g., integrated sensors; sensors of an external blood pressure measurement device in wireless communication with the computer system). The computer system receives first data corresponding to the first blood pressure measurement via one or more blood pressure sensors (e.g., wirelessly), wherein the first data is not received in response to user input (e.g., any user input) at the computer system (e.g., the first data is received automatically).

In some embodiments, the first data is received when a first notification (e.g., 846) is active (e.g., marked for display in a notification center; marked as unread; actively displayed on a display of a computer system). In response to receiving the first data, the computer system deactivates the first notification (e.g., 846) (e.g., stops displaying the displayed notification; marks the notification as read; dismisses the notification flag).

Automatically deactivating the notification assists the user in managing the notification when the first data is received. Automatically performing operations enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the computer system by enabling the user to use the system more quickly and efficiently.

In some implementations, in response to receiving the first data, the computer system displays an indication (e.g., 842) (e.g., a notification) of receipt of the first data via the display generation component (e.g., 602). In some embodiments, the notification includes an indication of a time period (e.g., whole day, morning, evening) that the first data of the day has been associated with it.

In response to receiving the first data, a display indication provides feedback to the user regarding the received data. Providing improved user feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the first plurality of measurement indicators (e.g., 836) includes a first measurement indicator that represents (e.g., corresponds to) a first time period (e.g., 12 hours), and the second plurality of measurement indicators (e.g., 840) includes a second measurement indicator (e.g., 840a, 840b, 840c, 840d, and/or 840 e) that represents (e.g., corresponds to) a second time period (e.g., 1 day) that is different from the first time period.

In some implementations, the first set of one or more inputs (e.g., 850a, 850c, 850d, 850e, 850f, 850g, 850h, 850i, 850j, and/or 850 k) includes a first input (e.g., 850f and/or 850 h) (e.g., a tap gesture; a mouse click) corresponding to a first user-selectable graphical user interface object (e.g., 822 a) corresponding to a first time range or corresponding to a second user-selectable graphical user interface object (e.g., 822 b) corresponding to a second time range. In some implementations, the first user-selectable graphical user interface object and the second user-selectable graphical user interface object are displayed on the same user interface.

Providing a selectable graphical user interface object for selecting a time range provides feedback to a user regarding whether a first plurality of measurement indicators or a second plurality of measurement indicators will be displayed in response to an input. Providing improved user feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, after the computer system receives the first set of one or more inputs (e.g., 850a, 850c, 850d, 850e, 850f, 850g, 850h, 850i, 850j, and/or 850 k) (e.g., after displaying the first user interface) and in accordance with a determination that a reminder notification (e.g., 846 and/or 856) has been elapsed (e.g., has elapsed) from the first event (e.g., since the last blood pressure measurement was received; from 8 a.m., since 5 a.m.), from the receipt of the first set of one or more inputs (e.g., has elapsed) and not received (e.g., automatically received; manually received) via the display generating component (e.g., 602 and/or 654) (e.g., a notification indicating that a blood pressure measurement has not been received).

Automatically displaying a reminder notification when certain conditions are met performs the function without further user input and provides feedback to the user regarding the conditions being met. Automatically performing operations and providing improved feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping a user provide appropriate input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the computer system by enabling the user to use the system more quickly and efficiently.

In some embodiments, the first user interface (e.g., 800) includes a first plurality of measurement indicators (e.g., 836) over a first time range, and after (e.g., in response to) the computer system enters a blood pressure measurement corresponding to the first time range, the computer system modifies an appearance (e.g., marks as complete; changes color; changes shape) of a first measurement indicator (e.g., an indicator corresponding to a first half of a day) of the first plurality of measurement indicators (e.g., 836). According to the first user interface (e.g., 800) including a second plurality of measurement indicators (e.g., 840) within a second time range, and after (e.g., in response to) the computer system entering blood pressure measurements corresponding to the second time range, the computer system modifies an appearance of a second measurement indicator (e.g., 840 a) (e.g., an indicator corresponding to an entire day of the day) of the second plurality of measurement indicators (e.g., 840).

Modifying the appearance of the respective measurement indicators in response to receiving the blood pressure measurement provides feedback to the user as to which indicator the measurement has been associated with. Providing improved feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the first user interface (e.g., 800) includes a graphical depiction (e.g., 802) (e.g., a graph (e.g., a line graph; a scatter graph); a table) of one or more received blood pressure measurements.

Displaying a graphical depiction of the received measurement data provides feedback to the user as a result of the received blood pressure measurement. Providing improved feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some implementations, the first user interface (e.g., 800) includes a third user-selectable graphical object (e.g., 803) that, when selected, causes (e.g., in the first user interface) information (e.g., scale; criteria shown in the depiction) corresponding to the graphical depiction (e.g., 802) (e.g., corresponding to parameters or aspects of the depiction) to be displayed.

Displaying information about the graphical depiction provides feedback to the user regarding the graphical depiction and aspects of the blood measurements depicted in the depiction. Providing improved feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide proper input and reducing user error in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the first user interface (e.g., 800) includes a fourth user-selectable graphical object (e.g., 858) that, when selected, causes the computer system to initiate a process for receiving (e.g., via manual entry) blood pressure measurements (e.g., systolic and/or diastolic measurements) for a time period of one day (e.g., the past day) prior to the current day (e.g., a second user interface that includes one or more user-interactive graphical user interface objects that enable a user to enter blood pressure measurements).

Providing an object for entering measurements of previous time periods provides the user with additional control options, thereby facilitating improved and sustained user-system interaction. Improving and continuing user-system interactions enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping a user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the first user interface (e.g., 800) includes a fifth user-selectable graphical object (e.g., 862) that, when selected, causes the computer system to initiate a process for transmitting data corresponding to the one or more received blood pressure measurements to an external electronic device (e.g., a computer associated with a medical provider).

In some embodiments, the first user interface (e.g., 800) includes a sixth user selectable graphical object (e.g., 864) (e.g., a new diary period affordance) that, when selected, causes the computer system to initiate a process for selecting a second time range (e.g., selecting a user interactive graphical user interface object corresponding to the first time range from a plurality of user interactive graphical user interface objects corresponding to different time ranges; entering a value corresponding to the time range) and for displaying a second user interface (e.g., 800) (e.g., including one or more features of the first user interface) that includes a third plurality of measurement indicators (e.g., 836 and/or 840) including a plurality of measurement indicators selected based on the second time range. In some embodiments, a sixth affordance is included (only; first included) in the first user interface in accordance with a determination that a sufficient number (e.g., 14; 30) of blood pressure measurements have been received and/or a determination that a predetermined period of time (e.g., 7 days; 30 days) has elapsed.

Providing an object for initiating a process of selecting a new time range provides the user with additional control options, thereby facilitating improved and sustained user-system interaction. Improving and continuing user-system interactions enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping a user provide proper input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

In some embodiments, the computer system communicates with one or more sensors (e.g., 618, 620, and/or 622) (e.g., a photoplethysmograph sensor, a gyroscopic sensor, and/or an electrocardiograph sensor). In some embodiments, the one or more sensors do not include a sensor for directly and/or specifically measuring a pressure value of a user of the computer system. The computer system receives (702) first sensor data associated with a user of the computer system from one or more sensors (e.g., 618, 620, and/or 622) (e.g., periodically and/or intermittently receiving measurement data from the one or more sensors, wherein the data from the one or more sensors includes data indicative of light absorption by skin of the user associated with the computer system (e.g., one or more measurements received from a photoplethysmograph sensor), data indicative of orientation and/or angular velocity of the computer system (e.g., one or more measurements received from a gyroscope sensor), and/or data indicative of voltage over time (e.g., one or more measurements of electrical activity of the heart received from an electrocardiogram sensor)). In some embodiments, the first sensor data from the one or more sensors does not include direct measurements of pressure (e.g., values from sensors configured to specifically measure pressure such as pressure gauges, pressure transducers, strain gauges, and/or piezometers). In some embodiments, the data from the one or more sensors is data from (e.g., generated by; associated with; relating to) a user of the computer system. In some embodiments, the data from the one or more sensors includes indirect measurements of pressure. For example, raw data from one or more sensors (e.g., as a seed to an algorithm) may be utilized to calculate and/or estimate pressure, such as systolic blood pressure and/or diastolic blood pressure. In some embodiments, the computer system does not use the data to indirectly determine and/or calculate a numerical measurement of the pressure.

In response to receiving first sensor data (704) from one or more sensors (e.g., 618, 620, and/or 622) and in response to determining that the first sensor data from the one or more sensors (e.g., 618, 620, and/or 622) meets a set of hypertension notification criteria (e.g., the computer system uses data from the one or more sensors to make an assessment as to whether a user associated with the computer system is at risk of chronic hypertension (e.g., the user associated with the computer system is suffering from chronic hypertension, rather than being considered to be a primary instance of high blood pressure, an estimate, and/or a blood pressure measurement result), the computer system uses data from the one or more sensors to generate a risk score indicative of chronic hypertension, and the risk score exceeds a threshold), the computer system displays a notification (e.g., the computer system indicates that the user associated with the computer system is at chronic hypertension using data from the one or more sensors) (e.g., the computer system indicates that the user associated with the computer system is not at risk of chronic hypertension, is not at hypertension, and is in communication with an external device (e.g., the computer system and an external device, such as a watch) and/or an external device) generates a signal (e.g., a smart watch) via a display generating means (e.g., a display generating means, a smart watch), the signal causes the external device to display a notification on a display generating part of the external device). In some embodiments, the set of hypertension notification criteria does not include (e.g., does not include any) criteria based on (e.g., in view of) blood pressure values (e.g., diastolic and/or systolic values of a user of the computer system). In some embodiments, the set of hypertension notification criteria does not include criteria based on pressure measurements (e.g., any criteria).

In response to receiving the first sensor data (704) from the one or more sensors (e.g., 618, 620, and/or 622) and in accordance with a determination that the first sensor data from the one or more sensors (e.g., 618, 620, and/or 622) does not meet the set of hypertension notification criteria (e.g., the computer system uses the data from the one or more sensors to make an assessment as to whether a user associated with the computer system is at risk of chronic hypertension (e.g., the user associated with the computer system does not have sustained hypertension), the computer system uses the data from the one or more sensors to generate a risk score indicative of chronic hypertension and the risk score does not exceed a threshold), the computer system displays a notification of a hypertension event (e.g., 628) (e.g., the computer system and an external device do not display the notification because the data from the one or more sensors indicates that the user associated with the computer system is not at risk of chronic hypertension).

After (e.g., in response to) the computer system displaying a notification of the hypertension event (e.g., 628; within a predetermined time herein), the computer system displays a notification (e.g., 866) via the display generating component prompting the user to initiate a process for receiving a second set of one or more inputs for selecting a third time range and for displaying a third user interface (e.g., 800) (e.g., which includes one or more features of the first user interface) including a fourth plurality of measurement indicators (e.g., 836 and/or 840) including a plurality of measurement indicators selected based on the third time range.

Automatically generating a reminder notification after displaying the notification of the hypertension event reveals the relevant functionality to the user, no further user input is required, and thus user-system interaction is improved and maintained. Automatically performing operations and continuing user-system interactions enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping a user provide appropriate input and reducing user errors in operating/interacting with the computer system), which in turn reduces power usage and extends battery life of the system by enabling the user to more quickly and efficiently use the computer system.

It is noted that the details of the process described above with respect to method 900 (e.g., fig. 9) also apply in a similar manner to the method described above.

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

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

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

The present disclosure recognizes that the use of such personal information data in the present technology may be used to benefit users. For example, personal information data may be used to facilitate third parties in assessing the health of a user. In addition, the present disclosure contemplates other uses for personal information data that are beneficial to the user. For example, health and fitness data may be used to provide insight into the overall health of a user, or may be used as positive feedback to individuals using technology to pursue health goals.

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

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

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

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may be implemented without accessing such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, the captured sensor data and/or the received blood pressure data may be maintained entirely on the user's electronic device, and access to data corresponding to the captured sensor data and/or the received blood pressure data by another device (e.g., a server) may be prohibited without explicit user consent.

Claim (modification according to treaty 19)

1. A method, comprising:

at a computer system in communication with one or more output devices, one or more input devices, and one or more sensors, wherein the one or more output devices include a display generation component:

receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure;

In response to receiving the first data from the one or more sensors:

in accordance with a determination that the first data from the one or more sensors meets a set of hypertension notification criteria, generating, via the one or more output devices, a notification indicative of a hypertension event associated with the user of the computer system; and

in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, discarding the generation of the notification of the hypertension event;

after generating the notification indicating the hypertension event associated with the user of the computer system, receiving a first set of one or more inputs corresponding to the notification via the one or more input devices; and

in response to the first set of one or more inputs, a first user interface including first information corresponding to the first data is displayed via the display generation component.

2. The method of claim 1, wherein the first data associated with a user of the computer system comprises data received from the one or more sensors over a first period of time selected from the group consisting of: a period of time greater than 1 hour; a period of greater than 1 day; and a period of greater than 1 week.

3. The method of any one of claims 1 to 2, wherein:

the first data associated with a user of the computer system includes a plurality of data subsets including:

a first subset of data received during a second time period; and

and beginning receiving a second subset of data after a third period of time has elapsed after receiving the first subset of data, wherein the third period of time is greater than the second period of time.

4. The method of any of claims 1-3, wherein the set of hypertension notification criteria includes criteria that are met when a risk score exceeds a threshold, wherein the risk score is generated based on the first data associated with the user of the computer system.

5. The method of any one of claims 1 to 4, wherein the one or more sensors are selected from the group consisting of a photoplethysmograph sensor, a gyroscopic sensor, an electrocardiographic sensor, an accelerometer, and combinations thereof.

6. The method of any of claims 1-5, wherein the first data associated with the user of the computer system does not include data from a vibration sensor.

7. The method of any of claims 1-6, wherein the computer system is not in communication with a component that actively applies mechanical pressure to the user of the computer system, and wherein the one or more sensors do not include a sensor that measures data for a fourth period of time after the active mechanical pressure is applied to the user of the computer system.

8. The method of any of claims 1-7, wherein the user of the computer system meets a set of feature qualification criteria.

9. The method of any of claims 1-8, wherein receiving the first data associated with the user of the computer system from the one or more sensors comprises: the first data is received within a first predetermined period of time.

10. The method of claim 9, further comprising:

receiving second data associated with the user of the computer system from the one or more sensors after receiving the first data associated with the user of the computer system from the one or more sensors for the first predetermined period of time, wherein the second data is received for a second predetermined period of time that does not overlap the first predetermined period of time; and

In response to receiving the second data from the one or more sensors:

in accordance with a determination that the second data from the one or more sensors meets the set of hypertension notification criteria, a second notification is generated via the one or more output devices indicating a hypertension event associated with the user of the computer system.

11. (cancel)

12. The method of any of claims 1-10, wherein the one or more output devices include a display generation component, the method further comprising:

after generating the notification indicating the hypertension event, displaying a second user interface comprising information corresponding to one or more notifications indicating the hypertension event, the one or more notifications comprising the notification indicating the hypertension event.

13. The method of any of claims 1-10 and 12, wherein the notification indicating a hypertension event does not include a numerical indication of a blood pressure value of a user of the computer system.

14. The method of any one of claims 1 to 10 and 12 to 13, wherein:

the first data associated with a user of the computer system includes a second plurality of data subsets, the second plurality of data subsets including:

A third subset of data received at the first time, wherein the third subset of data is not received in response to user input; and

a fourth subset of data received a second predetermined period of time after receiving the third subset of data.

15. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with one or more output devices and one or more sensors, the one or more programs comprising instructions for performing the method of any of claims 1-10 and 12-14.

16. A computer system, comprising:

one or more output devices;

one or more sensors;

one or more processors; and

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

17. A computer system, comprising:

one or more output devices;

one or more sensors; and

Apparatus for performing the method of any one of claims 1 to 10 and 12 to 14.

18. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with one or more output devices, one or more input devices, and one or more sensors, wherein the one or more output devices include display generating components, the one or more programs including instructions for:

in response to receiving the first data from the one or more sensors:

19. A computer system, comprising:

one or more output devices, wherein the one or more output devices comprise a display generation component;

one or more input devices;

one or more sensors;

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:

In response to receiving the first data from the one or more sensors:

20. A computer system, comprising:

one or more input devices;

One or more sensors; and

means for receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure;

means for, in response to receiving the first data from the one or more sensors:

means for receiving, via the one or more input devices, a first set of one or more inputs corresponding to the notification after generating the notification indicating the hypertension event associated with the user of the computer system; and

means for displaying, via the display generating component, a first user interface including first information corresponding to the first data in response to the first set of one or more inputs.

21. A method, comprising:

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

receiving, via the one or more input devices, a first set of one or more inputs including a first input selecting a time range;

displaying, via the display generating component, a first user interface in response to receiving the first set of one or more inputs, wherein the first user interface comprises:

in accordance with a determination that the first input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range;

in accordance with a determination that the first input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and

a first measurement entry user-interactive graphical user interface object that, when selected via the one or more input devices, initiates a measurement entry process for:

entering blood pressure measurements corresponding to the first time range and the day according to the first user interface including the first plurality of measurement indicators within the first time range; and

According to the first user interface comprising the second plurality of measurement indicators within the second time range, blood pressure measurements corresponding to the second time range and the current day are entered.

22. The method of claim 21, wherein the first plurality of measurement indicators comprises a first number of measurement indicators and the second plurality of measurement indicators comprises a second number of measurement indicators different from the first number.

23. The method of any one of claims 21 to 22, wherein the computer system is in communication with one or more blood pressure sensors, the method further comprising:

first data corresponding to a first blood pressure measurement is received via the one or more blood pressure sensors, wherein the first data is not received in response to user input at the computer system.

24. The method of claim 23, wherein the first data is received at a first notification activity, the method further comprising:

the first notification is deactivated in response to receiving the first data.

25. The method of claim 24, further comprising:

Displaying, via the display generating component, an indication of receipt of the first data in response to receipt of the first data.

26. The method of any one of claims 21 to 25, wherein:

the first plurality of measurement indicators includes a first measurement indicator representing a first time period; and is also provided with

The second plurality of measurement indicators includes a second measurement indicator representing a second time period different from the first time period.

27. The method of any of claims 21-26, wherein the first set of one or more inputs includes a first input corresponding to a first user-selectable graphical user interface object corresponding to the first time range or a second user-selectable graphical user interface object corresponding to the second time range.

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

after receiving the first set of one or more inputs:

in accordance with a determination that a predetermined period of time has elapsed since the first event without receiving a blood pressure measurement, a reminder notification is displayed via the display generating component.

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

According to the first user interface comprising the first plurality of measurement indicators within the first time range, and after entering blood pressure measurements corresponding to the first time range, modifying an appearance of a first measurement indicator of the first plurality of measurement indicators; and

according to the first user interface comprising the second plurality of measurement indicators within the first time range, and after entering blood pressure measurements corresponding to the second time range, modifying an appearance of a second measurement indicator of the second plurality of measurement indicators.

30. The method of any one of claims 21 to 29, wherein the first user interface comprises a graphical depiction of one or more received blood pressure measurements.

31. The method of claim 30, wherein the first user interface comprises a third user-selectable graphical object that, when selected, causes information corresponding to the graphical depiction to be displayed.

32. The method of any of claims 21 to 31, wherein the first user interface comprises a fourth user selectable graphical object that, when selected, initiates a process for receiving blood pressure measurements for a time period of a day preceding the day.

33. The method of any of claims 21 to 32, wherein the first user interface comprises a fifth user-selectable graphical object that, when selected, initiates a process for transmitting data corresponding to one or more received blood pressure measurements to an external electronic device.

34. The method of any of claims 21 to 33, wherein the first user interface comprises a sixth user-selectable graphical object that, when selected, initiates a process for selecting a second time range and for displaying a second user interface comprising a third plurality of measurement indicators, the third plurality of measurement indicators comprising a plurality of measurement indicators selected based on the second time range.

35. The method of any of claims 21 to 34, wherein the computer system is in communication with one or more sensors, the method further comprising:

receive first sensor data associated with a user of the computer system from the one or more sensors;

in response to receiving the first sensor data from the one or more sensors:

In accordance with a determination that the first sensor data from the one or more sensors meets a set of hypertension notification criteria, displaying, via the display generating component, a notification indicative of a hypertension event associated with the user of the computer system; and

in accordance with a determination that the first sensor data from the one or more sensors does not meet the set of hypertension notification criteria, discarding the notification displaying the hypertension event; and

after displaying the notification of the hypertension event, displaying a notification via a display generating component, the notification prompting the user to initiate a process for receiving a second set of one or more inputs for selecting a third time range and for displaying a third user interface comprising a fourth plurality of measurement indicators, the fourth plurality of measurement indicators comprising a plurality of measurement indicators selected based on the third time range.

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

37. A computer system, comprising:

a display generation section;

one or more input devices;

one or more processors; and

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

38. A computer system, comprising:

a display generation section;

one or more input devices; and

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

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

40. A computer system, comprising:

a display generation section;

one or more input devices;

One or more processors; and

41. A computer system, comprising:

a display generation section;

one or more input devices; and

means for receiving, via the one or more input devices, a first set of one or more inputs including a first input selecting a time range;

means for displaying a first user interface via the display generating component in response to receiving the first set of one or more inputs, wherein the first user interface comprises:

Claims

1. A method, comprising:

at a computer system in communication with one or more output devices and one or more sensors:

receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and

in response to receiving the first data from the one or more sensors:

in accordance with a determination that the first data from the one or more sensors does not meet the set of hypertension notification criteria, the generating the notification of the hypertension event is aborted.

3. The method of any one of claims 1 to 2, wherein:

a first subset of data received during a second time period; and

7. The method of any of claims 1-6, wherein the computer system is not in communication with a component that actively applies mechanical pressure to the user of the computer system, wherein the one or more sensors do not include a sensor that measures data for a fourth period of time after the active mechanical pressure is applied to the user of the computer system.

10. The method of claim 9, further comprising:

receiving second data associated with the user of the computer system from the one or more sensors after receiving the first data associated with the user of the computer system from the one or more sensors for the first predetermined period of time, wherein the second data is received for a second predetermined period of time that does not overlap the first predetermined period of time;

in response to receiving the second data from the one or more sensors:

11. The method of any of claims 1-10, wherein the one or more output devices include a display generation component and the computer system is in communication with one or more input devices, the method further comprising:

Receiving, via the one or more input devices, a first set of one or more inputs corresponding to the notification;

12. The method of any of claims 1-11, wherein the one or more output devices include a display generation component, the method further comprising:

13. The method of any of claims 1-12, wherein the notification indicating a hypertension event does not include a numerical indication of a blood pressure value of a user of the computer system.

14. The method of any one of claims 1 to 13, wherein:

15. A non-transitory computer readable storage medium storing one or more programs configured for execution by one or more processors of a computer system in communication with one or more output devices and one or more sensors, the one or more programs comprising instructions for performing the method of any of claims 1-14.

16. A computer system, comprising:

one or more output devices;

one or more sensors;

one or more processors; and

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

17. A computer system, comprising:

one or more output devices;

one or more sensors; and

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

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

in response to receiving the first data from the one or more sensors:

19. A computer system, comprising:

one or more output devices;

one or more sensors;

one or more processors; and

In response to receiving the first data from the one or more sensors:

20. A computer system, comprising:

one or more output devices;

one or more sensors; and

means for receiving first data associated with a user of the computer system from the one or more sensors, wherein the first data from the one or more sensors does not include a direct measurement of pressure; and

21. A method, comprising:

in accordance with a determination that the first user input corresponds to a selection of a first time range, a first plurality of measurement indicators within the first time range;

in accordance with a determination that the first user input corresponds to a selection of a second time range different from the first time range, a second plurality of measurement indicators within the second time range; and

The first notification is deactivated in response to receiving the first data.

25. The method of claim 24, further comprising:

26. The method of any one of claims 21 to 25, wherein:

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

after receiving the first set of one or more inputs:

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

in response to receiving the first sensor data from the one or more sensors:

37. A computer system, comprising:

a display generation section;

one or more input devices;

one or more processors; and

38. A computer system, comprising:

a display generation section;

one or more input devices; and

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

40. A computer system, comprising:

a display generation section;

one or more input devices;

One or more processors; and

41. A computer system, comprising:

a display generation section;

one or more input devices; and