User interface for tracking medicaments

Abstract

The invention relates to a user interface for tracking drugs. The present disclosure relates generally to methods and user interfaces for tracking a medicament, managing (e.g., for a tracked medicament) logged actions, and / or displaying a summary of a tracked medicament.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of June 2, 2023, the national application number 202380045052.8, and the invention name “User Interface for Tracking Drugs”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Patent Application No. 18 / 204,897, entitled “USER INTERFACES TO TRACK MEDICATIONS,” filed on June 1, 2023, and U.S. Provisional Patent Application No. 63 / 462,631, entitled “USER INTERFACES TO TRACK MEDICATIONS,” filed on April 28, 2023, and U.S. Provisional Patent Application No. 63 / 349,114, entitled “USER INTERFACES TO TRACK MEDICATIONS,” filed on June 5, 2022. The contents of each of these patent applications are incorporated herein by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for tracking medications. Background Art

[0005] Electronic devices and software applications operating on such devices are used to track medications that a user needs to take and when the user needs to take those medications. Summary of the invention

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

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

[0008] 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 includes: displaying, via a display generation component, a first user interface for selecting a first medication to be added to a medication tracking application; while displaying the first user interface, detecting, via one or more input devices, a first set of one or more inputs including a first input corresponding to a selection of the first medication; in response to detecting the first set of one or more inputs, displaying, via the display generation component, a second user interface, the second user interface including: a first option for a first medication form based on the first medication; and a second option for a second medication form based on the first medication, the second medication form being different from the first medication form; while displaying the second user interface, detecting, via the one or more input devices, a second set of one or more inputs including a second input corresponding to a selection of a corresponding medication form; and in response to detecting the second set of one or more inputs, displaying, via the display generation component, a third user interface, the third user interface including: a first set of at least two medication strength options based on the first medication form based on a determination that a first set of strength criteria are satisfied, wherein the first set of strength criteria include a first strength criteria that is satisfied when the corresponding medication form corresponds to the first medication form; and a second set of at least two medication strength options based on the second medication form based on a determination that a second set of strength criteria are satisfied, wherein the second set of strength criteria include a second strength criteria that is satisfied when the corresponding medication form corresponds to the second medication form, wherein the second set of at least two medication strength options are different from the first set of at least two medication strength options.

[0009] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying a first user interface for selecting a first drug to be added to a drug tracking application via the display generation component; while displaying the first user interface, detecting a first group of one or more inputs including a first input corresponding to the selection of the first drug via one or more input devices; in response to detecting the first group of one or more inputs, displaying a second user interface via the display generation component, the second user interface including: a first option for a first drug form based on the first drug; and a second option for a second drug form based on the first drug, the second drug form being different from the first drug form; in displaying When displaying a second user interface, a second group of one or more inputs including a second input corresponding to a selection of a corresponding drug form is detected via the one or more input devices; and in response to detecting the second group of one or more inputs, a third user interface is displayed via the display generating component, the third user interface including: a first group of at least two drug strength options based on the first drug form based on determining that the first group of strength standards are satisfied, wherein the first group of strength standards includes a first strength standard that is satisfied when the corresponding drug form corresponds to the first drug form; and a second group of at least two drug strength options based on the second drug form based on determining that the second group of strength standards are satisfied, wherein the second group of strength standards includes a second strength standard that is satisfied when the corresponding drug form corresponds to the second drug form, wherein the second group of at least two drug strength options are different from the first group of at least two drug strength options.

[0010] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying a first user interface for selecting a first drug to be added to a drug tracking application via the display generation component; while displaying the first user interface, detecting a first group of one or more inputs including a first input corresponding to the selection of the first drug via one or more input devices; in response to detecting the first group of one or more inputs, displaying a second user interface via the display generation component, the second user interface including: a first option for a first drug form based on the first drug; and a second option for a second drug form based on the first drug, the second drug form being different from the first drug form; while displaying the first user interface, detecting a first group of one or more inputs including a first input corresponding to the selection of the first drug via the one or more input devices; in response to detecting the first group of one or more inputs, displaying a second user interface via the display generation component, the second user interface including: a first option for a first drug form based on the first drug; and a second option for a second drug form based on the first drug, the second drug form being different from the first drug form; When a second user interface is displayed, a second group of one or more inputs including a second input corresponding to a selection of a corresponding drug form is detected via the one or more input devices; and in response to detecting the second group of one or more inputs, a third user interface is displayed via the display generating component, the third user interface including: a first group of at least two drug strength options based on the first drug form based on determining that the first group of strength standards are satisfied, wherein the first group of strength standards includes a first strength standard that is satisfied when the corresponding drug form corresponds to the first drug form; and a second group of at least two drug strength options based on the second drug form based on determining that the second group of strength standards are satisfied, wherein the second group of strength standards includes a second strength standard that is satisfied when the corresponding drug form corresponds to the second drug form, wherein the second group of at least two drug strength options are different from the first group of at least two drug strength options.

[0011] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: displaying a first user interface for selecting a first drug to be added to a drug tracking application via the display generation component; while displaying the first user interface, detecting a first group of one or more inputs including a first input corresponding to the selection of the first drug via one or more input devices; in response to detecting the first group of one or more inputs, displaying a second user interface via the display generation component, the second user interface including: a first option for a first drug form based on the first drug; and a second option for a second drug form based on the first drug, the second drug form being different from the first drug form; while displaying the second user interface a second group of one or more inputs including a second input corresponding to a selection of a corresponding drug form is detected via the one or more input devices; and in response to detecting the second group of one or more inputs, a third user interface is displayed via the display generation component, the third user interface including: a first group of at least two drug strength options based on the first drug form based on determining that the first group of strength standards are satisfied, wherein the first group of strength standards includes a first strength standard that is satisfied when the corresponding drug form corresponds to the first drug form; and a second group of at least two drug strength options based on the second drug form based on determining that the second group of strength standards are satisfied, wherein the second group of strength standards includes a second strength standard that is satisfied when the corresponding drug form corresponds to the second drug form, wherein the second group of at least two drug strength options are different from the first group of at least two drug strength options.

[0012] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for displaying a first user interface for selecting a first drug to be added to a drug tracking application via the display generation component; a component for detecting a first group of one or more inputs including a first input corresponding to the selection of the first drug via one or more input devices when displaying the first user interface; a component for displaying a second user interface via the display generation component in response to detecting the first group of one or more inputs, the second user interface including: a first option for a first drug form based on the first drug; and a second option for a second drug form based on the first drug, the second drug form being different from the first drug form; and a component for detecting a first group of one or more inputs including a first input corresponding to the selection of the corresponding drug form via the one or more input devices when displaying the second user interface. A component for selecting a second group of one or more inputs corresponding to a second input; and a component for displaying a third user interface via a display generating component in response to detecting the second group of one or more inputs, the third user interface comprising: a first group of at least two drug strength options based on a first drug form based on a determination that a first group of strength standards are satisfied, wherein the first group of strength standards includes a first strength standard that is satisfied when the corresponding drug form corresponds to the first drug form; and a second group of at least two drug strength options based on a second drug form based on a determination that a second group of strength standards are satisfied, wherein the second group of strength standards includes a second strength standard that is satisfied when the corresponding drug form corresponds to the second drug form, wherein the second group of at least two drug strength options are different from the first group of at least two drug strength options.

[0013] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying a first user interface for selecting a first drug to be added to a medication tracking application via the display generation component; while displaying the first user interface, detecting a first set of one or more inputs including a first input corresponding to the selection of the first drug via one or more input devices; in response to detecting the first set of one or more inputs, displaying a second user interface via the display generation component, the second user interface including: a first option for a first medication form based on the first medication; and a second option for a second medication form based on the first medication, the second medication form being different from the first medication form; while displaying the second user interface, a second user interface, detecting via the one or more input devices a second group of one or more inputs including a second input corresponding to a selection of a corresponding drug form; and in response to detecting the second group of one or more inputs, displaying via the display generating component a third user interface, the third user interface comprising: a first group of at least two drug strength options based on the first drug form based on determining that the first group of strength standards are satisfied, wherein the first group of strength standards includes a first strength standard that is satisfied when the corresponding drug form corresponds to the first drug form; and a second group of at least two drug strength options based on the second drug form based on determining that the second group of strength standards are satisfied, wherein the second group of strength standards includes a second strength standard that is satisfied when the corresponding drug form corresponds to the second drug form, wherein the second group of at least two drug strength options are different from the first group of at least two drug strength options.

[0014] According to some embodiments, a method is described that is performed at a computer system that communicates with a display generation component and one or more input devices. The method includes: detecting a first set of one or more inputs corresponding to a request to add a medication to be tracked in a medication tracking application for a first user via the one or more input devices; and in response to detecting the first set of one or more inputs corresponding to the request to add the medication to be tracked, displaying a first user interface of the medication tracking application via the display generation component, wherein displaying the first user interface includes: displaying a graphical user interface object for searching for medications; based on determining that the first user has a clinical health record that identifies the corresponding medication, displaying an option for adding the corresponding medication to be tracked in the medication tracking application based on the clinical health record; and based on determining that the first user does not have a clinical health record that identifies the corresponding medication, forgoing displaying an option for adding the medication as a medication to be tracked in the medication tracking application based on the clinical health record.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting a first set of one or more inputs corresponding to a request to add a drug to be tracked in a drug tracking application for a first user via the one or more input devices; and in response to detecting the first set of one or more inputs corresponding to the request to add a drug to be tracked, displaying a first user interface of the drug tracking application via the display generation component, wherein displaying the first user interface includes: displaying a graphical user interface object for searching for drugs; based on determining that the first user has a clinical health record identifying the corresponding drug, displaying an option for adding the corresponding drug to be tracked in the drug tracking application based on the clinical health record; and based on determining that the first user does not have a clinical health record identifying the corresponding drug, abandoning the option of displaying the drug to be added as a drug to be tracked in the drug tracking application based on the clinical health record.

[0016] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting a first set of one or more inputs corresponding to a request to add a medication to be tracked in a medication tracking application for a first user via the one or more input devices; and in response to detecting the first set of one or more inputs corresponding to the request to add the medication to be tracked, displaying a first user interface of the medication tracking application via the display generation component, wherein displaying the first user interface includes: displaying a graphical user interface object for searching for medications; based on determining that the first user has a clinical health record that identifies the corresponding medication, displaying an option for adding the corresponding medication to be tracked in the medication tracking application based on the clinical health record; and based on determining that the first user does not have a clinical health record that identifies the corresponding medication, abandoning the option of displaying the option for adding the medication as a medication to be tracked in the medication tracking application based on the clinical health record.

[0017] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: detecting a first set of one or more inputs corresponding to a request to add a medication to be tracked in a medication tracking application for a first user via the one or more input devices; and in response to detecting the first set of one or more inputs corresponding to the request to add the medication to be tracked, displaying a first user interface of the medication tracking application via the display generation component, wherein displaying the first user interface includes: displaying a graphical user interface object for searching for medications; based on determining that the first user has a clinical health record identifying the corresponding medication, displaying an option for adding the corresponding medication to be tracked in the medication tracking application based on the clinical health record; and based on determining that the first user does not have a clinical health record identifying the corresponding medication, forgoing displaying an option for adding the medication as a medication to be tracked in the medication tracking application based on the clinical health record.

[0018] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for detecting a first set of one or more inputs corresponding to a request to add a medication to be tracked in a medication tracking application for a first user via the one or more input devices; and a component for displaying a first user interface of the medication tracking application via the display generation component in response to detecting the first set of one or more inputs corresponding to the request to add the medication to be tracked, wherein displaying the first user interface includes: displaying a graphical user interface object for searching for medications; based on determining that the first user has a clinical health record that identifies the corresponding medication, displaying an option for adding the corresponding medication to be tracked in the medication tracking application based on the clinical health record; and based on determining that the first user does not have a clinical health record that identifies the corresponding medication, forgoing displaying an option for adding the medication as a medication to be tracked in the medication tracking application based on the clinical health record.

[0019] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting, via the one or more input devices, a first set of one or more inputs corresponding to a request to add a medication to be tracked in a medication tracking application for a first user; and in response to detecting the first set of one or more inputs corresponding to the request to add the medication to be tracked, displaying, via the display generation component, a first user interface of the medication tracking application, wherein displaying the first user interface includes: displaying a graphical user interface object for searching for medications; based on determining that the first user has a clinical health record identifying the corresponding medication, displaying an option for adding the corresponding medication to be tracked in the medication tracking application based on the clinical health record; and based on determining that the first user does not have a clinical health record identifying the corresponding medication, forgoing displaying an option for adding the medication as a medication to be tracked in the medication tracking application based on the clinical health record.

[0020] 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 includes: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to add a corresponding drug as a drug to be tracked in a drug tracking application; in response to detecting the set of one or more inputs corresponding to the request to add the corresponding drug as a drug to be tracked, displaying, via the display generation component, a user interface of the drug tracking application, wherein displaying the user interface includes: based on determining that the corresponding drug has a first drug interaction that satisfies a first set of criteria, displaying an indication of the first drug interaction in a first portion of the user interface; and based on determining that the corresponding drug has a second drug interaction that satisfies a second set of criteria that is different from the first set of criteria, displaying an indication of the second drug interaction in a second portion of the user interface that is different from the first portion of the user interface.

[0021] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to add a corresponding drug as a drug to be tracked in a drug tracking application; in response to detecting a set of one or more inputs corresponding to the request to add the corresponding drug as a drug to be tracked, displaying a user interface of the drug tracking application via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first drug interaction that satisfies a first set of criteria, displaying an indication of the first drug interaction in a first portion of the user interface; and based on determining that the corresponding drug has a second drug interaction that satisfies a second set of criteria that is different from the first set of criteria, displaying an indication of the second drug interaction in a second portion of the user interface that is different from the first portion of the user interface.

[0022] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to add a corresponding drug as a drug to be tracked in a drug tracking application; in response to detecting a set of one or more inputs corresponding to the request to add the corresponding drug as a drug to be tracked, displaying, via the display generation component, a user interface of the drug tracking application, wherein displaying the user interface includes: based on determining that the corresponding drug has a first drug interaction that satisfies a first set of criteria, displaying an indication of the first drug interaction in a first portion of the user interface; and based on determining that the corresponding drug has a second drug interaction that satisfies a second set of criteria that is different from the first set of criteria, displaying an indication of the second drug interaction in a second portion of the user interface that is different from the first portion of the user interface.

[0023] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: detecting a set of one or more inputs corresponding to a request to add a corresponding drug as a drug to be tracked in a drug tracking application via the one or more input devices; in response to detecting a set of one or more inputs corresponding to the request to add the corresponding drug as a drug to be tracked, displaying a user interface of the drug tracking application via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first drug interaction that satisfies a first set of criteria, displaying an indication of the first drug interaction in a first portion of the user interface; and based on determining that the corresponding drug has a second drug interaction that satisfies a second set of criteria different from the first set of criteria, displaying an indication of the second drug interaction in a second portion of the user interface that is different from the first portion of the user interface.

[0024] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to add a corresponding drug as a drug to be tracked in a drug tracking application; a component for displaying, via the display generation component, a user interface of the drug tracking application in response to detecting the set of one or more inputs corresponding to the request to add the corresponding drug as a drug to be tracked, wherein displaying the user interface includes: based on determining that the corresponding drug has a first drug interaction that satisfies a first set of criteria, displaying an indication of the first drug interaction in a first portion of the user interface; and based on determining that the corresponding drug has a second drug interaction that satisfies a second set of criteria that is different from the first set of criteria, displaying an indication of the second drug interaction in a second portion of the user interface that is different from the first portion of the user interface.

[0025] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to add a corresponding drug as a drug to be tracked in a drug tracking application; in response to detecting the set of one or more inputs corresponding to the request to add the corresponding drug as a drug to be tracked, displaying, via the display generation component, a user interface of the drug tracking application, wherein displaying the user interface includes: based on determining that the corresponding drug has a first drug interaction that satisfies a first set of criteria, displaying an indication of the first drug interaction in a first portion of the user interface; and based on determining that the corresponding drug has a second drug interaction that satisfies a second set of criteria that is different from the first set of criteria, displaying an indication of the second drug interaction in a second portion of the user interface that is different from the first portion of the user interface.

[0026] 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 includes: displaying a first user interface via the display generation component, wherein displaying the first user interface includes displaying a representation of a corresponding medication scheduled to be taken at a scheduled time in a first portion of the first user interface; detecting a first set of one or more inputs corresponding to a request to record an action associated with the corresponding medication when displaying the first user interface, the first set of one or more inputs including at least one detected input; and in response to detecting the first set of one or more inputs corresponding to a request to record an action associated with the corresponding medication, moving the representation of the corresponding medication from the first portion of the first user interface to a second portion of the first user interface different from the first portion.

[0027] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: displaying a first user interface via a display generation component, wherein displaying the first user interface includes displaying a representation of a corresponding drug scheduled to be taken (taken) at a scheduled time in a first portion of the first user interface; detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug when displaying the first user interface, the first group of one or more inputs including at least one detected input; and in response to detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug, moving the representation of the corresponding drug from the first portion of the first user interface to a second portion of the first user interface different from the first portion.

[0028] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: displaying a first user interface via a display generation component, wherein displaying the first user interface includes displaying a representation of a corresponding drug scheduled to be taken (taken) at a scheduled time in a first portion of the first user interface; detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug when displaying the first user interface, the first group of one or more inputs including at least one detected input; and in response to detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug, moving the representation of the corresponding drug from the first portion of the first user interface to a second portion of the first user interface that is different from the first portion.

[0029] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: displaying a first user interface via a display generation component, wherein displaying the first user interface includes displaying a representation of a corresponding drug scheduled to be taken (taken) at a scheduled time in a first portion of the first user interface; detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug when displaying the first user interface, the first group of one or more inputs including at least one detected input; and in response to detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug, moving the representation of the corresponding drug from the first portion of the first user interface to a second portion of the first user interface different from the first portion.

[0030] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for displaying a first user interface via the display generation component, wherein displaying the first user interface includes displaying a representation of a corresponding drug scheduled to be taken at a scheduled time in a first portion of the first user interface; a component for detecting a first set of one or more inputs corresponding to a request to record an action associated with the corresponding drug when displaying the first user interface, the first set of one or more inputs including at least one detected input; and a component for moving the representation of the corresponding drug from the first portion of the first user interface to a second portion of the first user interface different from the first portion in response to detecting the first set of one or more inputs corresponding to a request to record an action associated with the corresponding drug.

[0031] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: displaying a first user interface via the display generation component, wherein displaying the first user interface includes displaying a representation of a corresponding drug scheduled to be taken (taken) at a scheduled time in a first portion of the first user interface; detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug when displaying the first user interface, the first group of one or more inputs including at least one detected input; and in response to detecting a first group of one or more inputs corresponding to a request to record an action associated with the corresponding drug, moving the representation of the corresponding drug from the first portion of the first user interface to a second portion of the first user interface that is different from the first portion.

[0032] According to some embodiments, a method is described that is performed at a computer system that communicates with a display generation component and one or more input devices. The method includes: detecting an input corresponding to a request to display a summary of multiple recorded actions associated with a corresponding drug via the one or more input devices; and in response to detecting an input corresponding to a request to display a summary of action records associated with the corresponding drug, displaying a user interface including a time scale via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first type of recorded action for a first recorded action in the multiple recorded actions, displaying a first indicator of the first recorded action as having a first appearance on the time scale; and based on determining that the corresponding drug has a second type of recorded action different from the first type of recorded action for a first recorded action in the multiple recorded actions, displaying a second indicator of the first recorded action as having a second appearance on the time scale, the second appearance being different from the first appearance.

[0033] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting an input corresponding to a request to display a summary of multiple recorded actions associated with a corresponding drug via the one or more input devices; and in response to detecting an input corresponding to a request to display a summary of action records associated with the corresponding drug, displaying a user interface including a time scale via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first type of recorded action for a first recorded action in the multiple recorded actions, displaying a first indicator of the first recorded action as having a first appearance on the time scale; and based on determining that the corresponding drug has a second type of recorded action different from the first type of recorded action for a first recorded action in the multiple recorded actions, displaying a second indicator of the first recorded action as having a second appearance on the time scale, the second appearance being different from the first appearance.

[0034] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: detecting an input corresponding to a request to display a summary of multiple recorded actions associated with a corresponding drug via the one or more input devices; and in response to detecting an input corresponding to a request to display a summary of action records associated with the corresponding drug, displaying a user interface including a time scale via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first type of recorded action for a first recorded action in the multiple recorded actions, displaying a first indicator of the first recorded action as having a first appearance on the time scale; and based on determining that the corresponding drug has a second type of recorded action different from the first type of recorded action for a first recorded action in the multiple recorded actions, displaying a second indicator of the first recorded action as having a second appearance on the time scale, the second appearance being different from the first appearance.

[0035] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: detecting an input corresponding to a request to display a summary of multiple recorded actions associated with a corresponding drug via the one or more input devices; and in response to detecting an input corresponding to a request to display a summary of action records associated with the corresponding drug, displaying a user interface including a time scale via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first type of recorded action for a first recorded action in the multiple recorded actions, displaying a first indicator of the first recorded action as having a first appearance on the time scale; and based on determining that the corresponding drug has a second type of recorded action different from the first type of recorded action for a first recorded action in the multiple recorded actions, displaying a second indicator of the first recorded action as having a second appearance on the time scale, the second appearance being different from the first appearance.

[0036] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for detecting an input corresponding to a request to display a summary of multiple recorded actions associated with a corresponding drug via the one or more input devices; and a component for displaying a user interface including a time scale via the display generation component in response to detecting an input corresponding to a request to display a summary of action records associated with the corresponding drug, wherein displaying the user interface includes: based on determining that the corresponding drug has a first type of recorded action for a first recorded action in the multiple recorded actions, displaying a first indicator of the first recorded action as having a first appearance on the time scale; and based on determining that the corresponding drug has a second type of recorded action different from the first type of recorded action for a first recorded action in the multiple recorded actions, displaying a second indicator of the first recorded action as having a second appearance on the time scale, the second appearance being different from the first appearance.

[0037] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: detecting an input corresponding to a request to display a summary of multiple recorded actions associated with a corresponding drug via the one or more input devices; and in response to detecting an input corresponding to a request to display a summary of action records associated with the corresponding drug, displaying a user interface including a time scale via the display generation component, wherein displaying the user interface includes: based on determining that the corresponding drug has a first type of recorded action for a first recorded action in the multiple recorded actions, displaying a first indicator of the first recorded action as having a first appearance on the time scale; and based on determining that the corresponding drug has a second type of recorded action different from the first type of recorded action for a first recorded action in the multiple recorded actions, displaying a second indicator of the first recorded action as having a second appearance on the time scale, the second appearance being different from the first appearance.

[0038] According to some embodiments, a method is described that is performed at a computer system that communicates with a display generation component and one or more input devices. The method includes: displaying a watch face user interface that includes an indication of the current time and a complication of a medication tracking application; while displaying the watch face user interface, detecting an input corresponding to a selection of the complication; and in response to detecting the input corresponding to the selection of the complication, displaying a user interface that includes: displaying a plurality of recording options for the first medication based on a determination that the first medication meets a scheduling criterion; and displaying the plurality of recording options for the first medication and the plurality of recording options for the second medication based on a determination that the second medication and the first medication meet the scheduling criterion.

[0039] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: displaying a dial user interface including an indication of the current time and a complex functional component of a medication tracking application; while displaying the dial user interface, detecting an input corresponding to a selection of the complex functional component; and in response to detecting an input corresponding to a selection of the complex functional component, displaying a user interface, the user interface including: displaying multiple recording options for the first drug based on determining that the first drug meets the scheduling criteria; and displaying the multiple recording options for the first drug and the multiple recording options for the second drug based on determining that the second drug and the first drug meet the scheduling criteria.

[0040] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying a dial user interface including an indication of the current time and a complex functional component of a medication tracking application; while displaying the dial user interface, detecting an input corresponding to a selection of the complex functional component; and in response to detecting the input corresponding to the selection of the complex functional component, displaying a user interface, the user interface including: displaying multiple recording options for the first medication based on determining that the first medication meets the scheduling criteria; and displaying the multiple recording options for the first medication and the multiple recording options for the second medication based on determining that the second medication and the first medication meet the scheduling criteria.

[0041] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: displaying a dial user interface including an indication of the current time and a complex functional component of a medication tracking application; while displaying the dial user interface, detecting an input corresponding to a selection of the complex functional component; and in response to detecting the input corresponding to the selection of the complex functional component, displaying a user interface, the user interface including: displaying multiple recording options for the first medication based on determining that the first medication meets the scheduling criteria; and displaying the multiple recording options for the first medication and the multiple recording options for the second medication based on determining that the second medication and the first medication meet the scheduling criteria.

[0042] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for displaying a dial user interface including an indication of the current time and a complex functional component of a medication tracking application; a component for detecting an input corresponding to a selection of the complex functional component when displaying the dial user interface; and a component for displaying a user interface in response to detecting an input corresponding to a selection of the complex functional component, the user interface including: displaying multiple recording options for the first medication based on determining that the first medication meets the scheduling criteria; and displaying the multiple recording options for the first medication and the multiple recording options for the second medication based on determining that the second medication and the first medication meet the scheduling criteria.

[0043] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying a dial user interface including an indication of the current time and a complex functional component of a medication tracking application; while displaying the dial user interface, detecting an input corresponding to a selection of the complex functional component; and in response to detecting the input corresponding to the selection of the complex functional component, displaying a user interface, the user interface including: displaying multiple recording options for the first medication based on determining that the first medication meets the scheduling criteria; and displaying the multiple recording options for the first medication and the multiple recording options for the second medication based on determining that the second medication and the first medication meet the scheduling criteria.

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

[0045] Thus, devices are provided with faster, more efficient methods and interfaces for tracking medications, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices.Such methods and interfaces may supplement or replace other methods for tracking medications. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0051] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is illustrated.

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

[0053] Figure 5A Personal electronic devices according to some embodiments are illustrated.

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

[0055] FIG. 6A to FIG. 6AD An exemplary user interface for tracking medications according to some embodiments is illustrated.

[0056] FIG. 7A to FIG. 7B is a flow chart illustrating a method for tracking medications according to some embodiments.

[0057] Figure 8 is a flow chart illustrating a method for tracking medications according to some embodiments.

[0058] Fig. 9 is a flow chart illustrating a method for tracking medications according to some embodiments.

[0059] FIG. 10A to FIG. 10N An exemplary user interface for managing recording actions according to some embodiments is illustrated.

[0060] Fig.11 is a flowchart illustrating a method for managing recording actions according to some embodiments.

[0061] FIG. 12A to FIG. 12E An exemplary user interface for displaying a summary of tracked medications is illustrated in accordance with some embodiments.

[0062] Fig.13is a flow chart illustrating a method of displaying a summary of tracked medications according to some embodiments.

[0063] FIG. 14A to FIG. 14K An exemplary user interface for tracking medications according to some embodiments is illustrated.

[0064] Fig.15 is a flow chart illustrating a method for tracking medications according to some embodiments. DETAILED DESCRIPTION

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

[0066] There is a need for electronic devices that provide efficient methods and interfaces for tracking medications. Tracking medications, for example, provides users with the ability to schedule and record medications. Such techniques can reduce the cognitive burden on users who track medications, thereby increasing productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0067] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an exemplary device for performing techniques for management event notifications is provided. FIG. 6A to FIG. 6AD An exemplary user interface for tracking medications is illustrated. FIG. 7A to FIG. 7B , Figure 8 and Fig. 9 is a flow chart illustrating a method for tracking medications according to some embodiments. FIG. 6A to FIG. 6AD The user interface in is used to illustrate the process described below, including FIG. 7A to FIG. 7B , Figure 8 and Fig. 9 process. FIG. 10A to FIG. 10N An exemplary user interface for managing recording actions is illustrated. Fig.11 is a flow chart illustrating a method of managing recorded actions according to some embodiments. FIG. 10A to FIG. 10N The user interface in is used to illustrate the process described below, including Fig.11 process. FIG. 12A to FIG. 12E An exemplary user interface for displaying a summary of tracked medications is illustrated. Fig.13 is a flow chart illustrating a method for displaying a summary of tracked medications according to some embodiments. FIG. 12A to FIG. 12E The user interface in is used to illustrate the process described below, including Fig.13 process. FIG. 14A to FIG. 14K An exemplary user interface for tracking medications is illustrated. Fig.15 is a flow chart illustrating a method for tracking medications according to some embodiments. FIG. 14A to FIG. 14K The user interface in is used to illustrate the process described below, including Fig.15 process.

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

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

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

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

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

[0073] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). Devices, iPod Equipment and Device. Optionally use other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).

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

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

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

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

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

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

[0080] It should be understood that device 100 is merely one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown 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.

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

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

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

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

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

[0086] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

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

[0090] The touch-sensitive display in some embodiments of touch screen 112 is optionally similar to the multi-touch-sensitive touchpad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while a touch-sensitive touchpad does not provide visual output.

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

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

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

[0094] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0095] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that when the user views other video conference participants on the touch screen display, the image of the user is optionally obtained for video conferencing. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

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

[0097] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

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

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

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

[0101] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: active application state, which indicates which application (if any) is currently active; display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information related to the device's position and / or posture.

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

[0103] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

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

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

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

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

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

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

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

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

[0112] Application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

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

[0114] ● Telephone module 138;

[0115] ● Video conferencing module 139;

[0116] ● Email client module 140;

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

[0118] ●Fitness support module 142;

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

[0120] ●Image management module 144;

[0121] ●Video player module;

[0122] ●Music player module;

[0123] ●Browser module 147;

[0124] ● Calendar module 148;

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

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

[0127] ●Search module 151;

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

[0129] ●Note module 153;

[0130] ● Map module 154; and / or

[0131] ●Online video module 155.

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

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

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

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

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

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

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

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

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

[0141] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

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

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

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

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

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

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

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

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

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

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

[0152] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

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

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

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

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

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

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

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

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

[0161] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the 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 a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it is identified as the hit view.

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

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

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

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

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

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

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

[0169] In some embodiments, event definition 186 includes a definition of an event for a corresponding user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.

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

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

[0172] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

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

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

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

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

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

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

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

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

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

[0182] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the function described above. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be realized with independent software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

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

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

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

[0186] ●Time 404;

[0187] ●Bluetooth indicator 405;

[0188] ●Battery status indicator 406;

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

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

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

[0192] o an icon 420 labeled "Browser" of the browser module 147; and

[0193] o Video and music player module 152 (also known as iPod (Apple Inc.

[0194] (trademark of Apple Inc.)) module 152) labeled "iPod" icon 422; and

[0195] ● Icons for other apps, such as:

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

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

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

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

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

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

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

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

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

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

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

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

[0208] It should be noted that Figure 4A The illustrated icon labels 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 corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

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

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

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

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

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

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

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

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

[0217] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700 to 900, 1100, 1300, and / or 1500 ( FIG. 7A to FIG. 7B , Figure 8 , Fig. 9 , Fig.11 , Fig.13 and Fig.15). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

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

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

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

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

[0222] FIG. 6A to FIG. 6AD Example user interfaces for tracking medications according to some embodiments are illustrated. The user interfaces in these figures are used to illustrate the processes described below, including FIG. 7A to FIG. 9 process.

[0223] exist Fig. 6AAt 600, device 600 displays a home screen with a health application icon 602 on display 601. In some embodiments, device 600 includes one or more features of device 100, 300, and / or 500. While displaying health application icon 602, device 600 detects input 650a (e.g., a tap and / or a mouse click) directed to health application icon 602. In response to detecting input 650a, device 600 displays a functional interface 604b of a health application associated with health application icon 602, such as Figure 6B Depicted.

[0224] exist Figure 6B , functional interface 604b includes affordances of different functions of the health application, including a medication tracker affordance 608 of the medication tracker function of the health application. The user associated with profile icon 606 is logged into the user account. Thus, the medication tracker (or optionally, the health application) is user-specific, thereby tracking medications specific to the user. In some embodiments, the medication tracker includes functionality related to scheduling medications and / or recording a medication log.

[0225] While displaying functional interface 604b, device 600 detects input 650b (e.g., a tap and / or a mouse click) directed to medication tracker affordance 608. In response to detecting input 650b, device 600 displays the following: Figure 6C In some embodiments (e.g., during the initial setup process of the medication tracker), the search interface 604c is the initial interface for the process of adding a new medication that the user wishes to be tracked by the health application and device 600. FIG. 6D to FIG. 6V An additional user interface is depicted for the process of adding a new medication. In some embodiments (e.g., after an initial setup process of the medication tracker), in response to detecting input 650b, device 600 displays a Figure 6W and / or Figure 6X Tracking interface 656 is depicted.

[0226] exist Figure 6C, the search interface 604c includes different options for searching for medications to be added to the medication tracker. The search interface 604c includes a text search bar 610a and an image search enable representation 610b for searching for medications. The search interface 604c also includes a clinical health record enable representation 612. ("CHR enable representation"). In some embodiments, the CHR enable representation 612 is based on the user's clinical health record. In some embodiments, the device 600 has access to the user's CHR based on wireless communication with a computer that maintains the care provider's record of the user (e.g., via an online portal provided by the care provider and / or via a server that maintains the care provider's record of the user). In some embodiments, the device 600 has access to the user's CHR based on the care provider's record of the user stored locally on the device 600. In some embodiments, the care provider's record includes prescriptions and / or care provider's notes.

[0227] exist Figure 6C At , the device 600 pre-fills the search interface 604c with the CHR enable representation 612 without the need for search input (such as a text-based search via a text search bar 610a and / or an image-based search via an image search enable representation 610b). In some embodiments, the CHR enable representation 612 is associated with at least one of a drug name, a drug form, and / or a drug strength (when identified by the device 600). In this way, the CHR enable representation 612 allows the user to bypass providing input to search for a specific drug. In addition, in an embodiment in which the device 600 displays a corresponding CHR enable representation based on identifying a drug form and / or drug strength, such an embodiment allows the user to bypass the user interface and reduce the number of inputs to configure the drug form and / or drug strength. In some embodiments, pre-filling the search interface 604c with CHR enable representations 612a to 612b reduces user input and maintains the battery life of the device 600.

[0228] exist Figure 6C In some embodiments, based on information in the user's clinical health record, CHR affordances 612a and CHR affordances 612b are associated with medications prescribed within the previous year. In some embodiments, search interface 604c does not include CHR affordances for medications prescribed before the previous year.

[0229] exist Figure 6CIn some embodiments, CHR enable representation 612a and CHR enable representation 612b both include the name of the drug, the form of the drug, and the strength of the drug. In some embodiments, CHR enable representation 612a and / or CHR enable representation 612b do not include the form of the drug and / or the strength of the drug (e.g., because they are missing from CHR 614 and / or cannot be identified by device 600).

[0230] exist Figure 6C At 650c3, while displaying search interface 604c, device 600 detects input 650c3 (e.g., a tap and / or a mouse click) directed to CHR affordance 612a. In response to detecting input 650c3, device 600 displays the following Figure 6N 604n is depicted. Thus, the user not only bypasses searching for medications, but also bypasses the user interfaces for configuring medication forms and / or medication strengths (these user interfaces are described in greater detail herein). In some embodiments, device 600 does not identify medication forms and / or medication strengths from the user's CHR. In such embodiments, in response to detecting input on the CHR affordance, device 600 will display form selection interface 604e and / or strength selection interface 604g (e.g., so that the user can provide medication forms and / or medication strengths, respectively).

[0231] exist Figure 6C In the example of FIG. 6 , a user may use the search bar 610 to search for drugs. While displaying the search interface 604c, the device 600 detects an input 650c1 (e.g., a tap, a mouse click, and / or a keystroke) directed to the text search bar 610a. In response to detecting the input 650c1, the device 600 displays a menu similar to Fig.6D 604d, but without text 618 (if the user has not provided text input) and / or without search results 620a to 620c. In some embodiments, in response to detecting input 650c1, device 600 stops displaying CHR enable representation 612.

[0232] exist Figure 6C At 610b, while displaying search interface 604c, device 600 detects input 650c2 (e.g., a tap and / or a mouse click) directed to image search affordance 610b. In response to detecting input 650c2, device 600 displays the following Figure 6K Depicted command interface 604k.

[0233] exist Fig.6DAt , in response to detecting user input adding text (e.g., text 618) to the search bar 610a, the device 600 displays a search interface 604d. The device 600 displays search results 620 for drugs in the search interface 604d based on the detected text 618. In some embodiments, the search results include brand names and / or chemical names based on the text 618. In some embodiments, corresponding drugs with multiple forms and / or strengths are displayed in a single search result (e.g., as opposed to displaying multiple results with different forms and / or strengths for a single drug). In some embodiments, the device 600 displays a keyboard and / or search results in position 616a (e.g., the area previously occupied by the CHR enable representation 612). In some embodiments, the device 600 moves the text search bar 610a (e.g., relative to the search bar 612). Figure 6C 610a in the text search bar).

[0234] exist Fig.6D In the embodiment of the present invention, search result 620 includes nitroglycerin affordance representation 620a for nitroglycerin, which is available in a variety of forms (e.g., capsules, tablets, patches, and / or oral solutions) and in a variety of strengths. While displaying search interface 604d, device 600 detects input 650d1 (e.g., a tap and / or a mouse click) directed to nitroglycerin affordance representation 620a. In response to detecting input 650d1, device 600 displays a search result such as Fig. 6E A form selection interface 604e is depicted.

[0235] exist Fig.6D In the example, search result 619 includes a nitrofurantoin affordance 620b for nitrofurantoin, which is available in a single form (e.g., only) (e.g., oral suspension) and multiple strengths (e.g., 10 mg / 5 mL and / or 25 mg / 5 ml). While displaying search interface 604d, device 600 detects input 650d2 (e.g., a tap and / or a mouse click) directed to nitrofurantoin affordance 620b. In response to detecting input 650d2, device 600 displays a search interface similar to FIG. Figure 6G Strength user interface of strength selection interface 604g is depicted. The strength user interface includes an affordance for one or more strengths (e.g., multiple strengths) of the drug available (e.g., 10 mg / 5 mL and / or 25 mg / 5 ml). In some embodiments, in response to detecting input 650d2, device 600 abandons displaying form selection interface 604e.

[0236] exist Fig.6DIn some embodiments, the search results 620 include a nitisinone affordance 620c for nitisinone, which is available in a single form (e.g., only) (e.g., oral suspension) and a single strength (e.g., only) (e.g., 5 mg / mL). While displaying the search interface 604d, the device 600 detects an input 650d3 (e.g., a tap and / or a mouse click) directed to the nitisinone affordance 620c. In response to detecting the input 650d3, the device 600 displays a screen similar to the following: Figure 6N Arrangement user interface of interface 604n depicted. In some embodiments, in response to detecting input 650d3, device 600 abandons displaying form selection interface 604e and intensity selection interface 604g.

[0237] exist Fig. 6E At, form selection interface 604e allows the user to select the suggested drug form for a specific drug. As shown, form selection interface 604e includes affordances 622a to 622d of the drug form of nitroglycerin, including capsules, tablets, patches and oral solutions. The drug form includes different types of nitroglycerin forms available for its nitroglycerin. In some embodiments, form selection interface 604e does not include affordances for drug forms that are unavailable for its nitroglycerin. This simplifies the process of adding drugs to the drug tracker application because it reduces the number of options displayed in the user interface and allows users to efficiently add drugs without the need to manually type in further input of drug forms. In some embodiments, form selection interface 604e is displayed in response to text-based search (e.g., text-based search without identifying drug form and / or search results with user selection of multiple forms) or image-based search (e.g., image-based search without identifying drug form, such as images of medicine bottle scans or drug packaging)) and / or CHR suggestions (e.g., CHR suggestions without including drug form).

[0238] exist Fig. 6E At , the form selection interface 604e includes a "next" enable indication 624a. In some embodiments, the "next" enable indication 624a is disabled until the user selects an enable indication for the form of the medication (e.g., the tablet enable indication 622b). In some embodiments, the "next" enable indication 624a has a first appearance (e.g., color and / or shading) when disabled. While displaying the form selection interface 604e, the device 600 detects an input 650e (e.g., a tap and / or a mouse click) directed to the tablet enable indication 622b. In response to detecting the input 650e, the device 600 displays the following. Fig. 6F A form selection interface 604e is depicted.

[0239] exist Fig. 6FAt , form selection interface 604e includes an indication that tablet 622a has been selected. In some embodiments, "next" enable indication 624 is enabled in response to detecting a selection of a medication form (e.g., tablet). In some embodiments, in response to "next" enable indication 624a being enabled, "next" enable indication 624a is displayed in a second appearance different from the first appearance. While displaying form selection interface 604e, device 600 detects input 650f (e.g., a tap and / or a mouse click) directed to "next" enable indication 624. In response to detecting input 650f, device 600 displays as shown. Figure 6G Intensity selection interface 604g is depicted.

[0240] exist Figure 6G At , the strength selection interface 604g allows the user to select the suggested drug strength based on a specific drug form. As shown, the strength selection interface 604g includes indications 626a to 626c of drug strengths (such as 0.2mg, 0.4mg, and 0.6mg) based on the device 600 previously detecting the selection of the tablet indication 622a. In some embodiments, the drug strength includes a strength value (e.g., 0.2, 0.4, and / or 0.6) and a strength unit (e.g., mg and / or mL). In some embodiments, the only drug strength displayed in the strength selection interface 604g is the available strength of nitroglycerin in tablet form. In some embodiments, the strength selection interface 604g does not include the strength of nitroglycerin that is not available in tablet form. This simplifies the process of adding drugs to the drug tracker application because it reduces the number of options displayed in the user interface and allows the user to efficiently add drugs without further input of manually typing in the strength value. In some embodiments, the strength selection interface 604g is displayed in response to a text-based search (e.g., a text-based search that does not identify drug strengths and / or a search result with a user selection of a single form with multiple strengths available) or an image-based search (e.g., an image-based search that does not identify drug strengths) and / or CHR recommendations (e.g., CHR recommendations that do not include drug strengths).

[0241] exist Figure 6G , the user has selected drug strength 626a (0.2 mg). As shown, "next" affordance 624 is enabled. In some embodiments, while strength selection interface 604g is displayed, device 600 detects input (e.g., a tap and / or a mouse click) directed to "next" affordance 624. In response to detecting input directed to "next" affordance 624, device 600 displays a screen similar to Figure 6NIn some embodiments, in response to detecting input pointing to "next" affordance 624, device 600 displays a user interface other than interface 604n, such as icon editing interface 604s, icon editing interface 604t, add details interface 604u, or interaction factor interface 604v.

[0242] Figure 6H Describes the use of Fig.6D The text string shown in the reference is different from the text string after filling Fig.6D The search interface in question. Figure 6H At 4:00, device 600 detects an update to text 618 in search bar 610 to search for vitamin X, which does not return any search results. As shown, interface 604h indicates that there is no match (e.g., vitamin X is an unknown drug). Interface 604h includes user interface object 628 to add vitamin X as a tracked drug. While displaying interface 604h, device 600 detects input 650h (e.g., a tap and / or a mouse click) directed to user interface object 628. In response to detecting input 650h, device 600 displays the following: Fig.6I Intensity selection interface 604i is depicted.

[0243] exist Fig.6I At , strength selection interface 604i includes drug forms 630a-630b. Because vitamin X is an unknown drug, drug forms 630a-630b are a general set of drug forms, which is contrary to the drug forms associated with affordances 622a-622d that are specific to known drugs. In some embodiments, drug forms 630a-630b are divided into two subsets. As shown, subset 630a includes common drug forms (e.g., typical drug forms) and subset 630b includes uncommon drug forms (e.g., atypical drug forms).

[0244] exist Fig.6I At , intensity selection interface 604i includes an indication that form 630c (e.g., a capsule) has been selected. While intensity selection interface 604i is displayed, device 600 detects input 650i (e.g., a tap and / or a mouse click) directed to “next” affordance 624. In response to detecting input 650i, device 600 displays the following: Figure 6J Intensity selection interface 604j is depicted.

[0245] exist Figure 6JAt , strength selection interface 604j includes an affordance 632 for adding a drug strength (e.g., a strength value and / or a strength unit). In some embodiments, while displaying strength selection interface 604j, device 600 detects input (e.g., a tap and / or a mouse click) directed to affordance 632. In response to detecting the input directed to affordance 632, device 600 displays an interface for configuring the strength value and / or the strength unit. In some embodiments, affordance 632 includes a suggested strength unit based on the selected drug form (e.g., a capsule). In some embodiments, affordance 632 does not include a suggested strength unit based on the selected drug form.

[0246] exist Figure 6J , strength selection interface 604j includes a no-strength affordance 634 that the user can select when the user does not know the strength of the medication. In some embodiments, while strength selection interface 604j is displayed, device 600 detects input (e.g., a tap and / or a mouse click) on “next” affordance 624. In response to detecting the input on “next” affordance 624, device 600 displays a screen similar to Figure 6N In some embodiments, in response to detecting input on "next" affordance 624, device 600 displays a user interface other than interface 604n, such as icon editing interface 604s, icon editing interface 604t, add details interface 604u, or interaction factor interface 604v.

[0247] exist Figure 6K At, the device 600 responds to the pointing Figure 6C The device 600 may display an instruction interface 604k by receiving input 650c2 of the image search enable representation 610b. The instruction interface 604k includes instructions on how to search for medications using image data captured by one or more cameras of the device 600. While the instruction interface 604k is displayed, the device 600 detects input 650k (e.g., a tap and / or a mouse click) directed to the "Continue" enable representation 636. In response to detecting input 650k, the device 600 displays the following instructions: Figure 6L Camera interface 6041 is depicted.

[0248] exist Figure 6LAt 604 l, the camera interface 604 l includes a representation 638 of a container labeled Nitrostat based on image information (e.g., a live camera feed from one or more cameras of the device 600). As shown, the camera interface 604 l includes an indicator 639 that the device 600 detected the object and / or the drug. In some embodiments, the device 600 detects (e.g., from the image information) one or more characteristics of the drug, such as the drug brand name (e.g., Nitrostat), the drug form (e.g., capsules), and / or the drug strength (0.2 mg). In response to detecting the characteristics of Nitrostat, the device 600 displays a Figure 6M Confirmation interface 604m is depicted. In some embodiments, device 600 detects (eg, from image data) a machine-readable code, such as a barcode, National Drug Code (NDC), and / or QR code, that identifies the medication and / or one or more details of the medication (eg, strength and / or form).

[0249] exist Figure 6M At 604 m, confirmation interface 604 m includes an indication of the characteristics identified from the image data, including the type of drug, the form of the drug, and / or the strength of the drug. Thus, the user can confirm that device 600 correctly identified the drug. Confirmation interface 604 m includes a “continue” enable indication 636 and a “scan again” enable indication 641. In some embodiments, in response to detecting input on the “scan again” enable indication 641, device 600 displays Figure 6L Camera interface 6041 is depicted. In some embodiments, device 600 does not identify one or more characteristics of the drug (e.g., drug type, drug form, and / or drug strength). In such embodiments, device 600 displays a set of one or more user interfaces (e.g., interfaces 604e, 604g, 604i, and / or 604j) to allow the user to input (e.g., select) the corresponding characteristics (e.g., before and / or in response to detecting an input on “continue” enable indication 636).

[0250] exist Figure 6M In some embodiments, while displaying confirmation interface 604m, device 600 detects input (e.g., a tap and / or a mouse click) on “continue” enable representation 636. In response to detecting input on “continue” enable representation 636, device 600 displays a screen similar to the following. Figure 6N Arrangement interface of interface 604n depicted. In some embodiments, in response to detecting input on "next" affordance 624, device 600 displays a user interface other than interface 604n, such as icon editing interface 604s, icon editing interface 604t, add details interface 604u, or interaction factor interface 604v.

[0251] Figures 6N to 6R Depicted is a scheduling interface for configuring a schedule for medications. In some embodiments, before displaying the interface for configuring a schedule for medications, device 600 detects that the medication being added is the same as the medication already being tracked by the health application, with the same form and strength. In such embodiments, as a result of detecting that a duplicate medication is being added, device 600 displays a user interface that provides one or more affordances for modifying the medication type, medication form, and / or medication strength of the medication being added. In some embodiments, the health application does not allow two identical medications to be added.

[0252] exist Figure 6N At , scheduling interface 604n includes daily affordances 640a, on-demand affordances 640b, and custom affordances 640c. Interface 604n includes a "next" affordance 624 that is disabled.

[0253] exist Figure 6N At , while displaying the scheduling interface 604n, the device 600 detects an input 650n1 (eg, a tap and / or a mouse click) directed to the daily affordance representation 640a. In response to detecting the input 650n1, the device 600 displays the following Fig.6O While displaying the scheduling interface 604n, the device 600 detects an input 650n2 (e.g., a tap and / or a mouse click) directed to the on-demand affordance 640b. In response to detecting the input 650n2, the device 600 displays a screen similar to Figure 6S While displaying the arrangement interface 604n, the device 600 detects an input 650n3 (e.g., a tap and / or a mouse click) directed to the custom affordance 640c. In response to detecting the input 650n3, the device 600 displays the following: Figure 6P Arrangement interface 604p is depicted.

[0254] exist Fig.6O At , scheduling interface 640o includes time affordance 640d for configuring a medication taking time. In response to detecting an input directed to time affordance 640d, device 600 displays a user interface for modifying a scheduled time for medication taking.

[0255] exist Fig.6O At 640 o, the arrangement interface 640 o includes a dosage indicator 640 e for configuring the dosage of the drug to be taken. For example, in response to detecting an input pointing to the dosage indicator 640 e, the device 600 displays a user interface for modifying the dosage from one capsule to two capsules.

[0256] exist Fig.6OAt the same time, the scheduling interface 604o includes an "add another time" indication 640f for scheduling another medication time. In response to detecting an input pointing to the "add another time" indication 640f, the device 600 displays another time indication and a dosage indication. Interface 604p includes a start date indication 640g for configuring the start date of taking the medication. In response to detecting an input pointing to the start date indication, the device 600 displays a user interface for modifying the start date.

[0257] exist Fig.6O At , while displaying scheduling interface 604o, device 600 detects input 650o (e.g., a tap and / or a mouse click) directed to “next” affordance 624. In response to detecting input 650o, device 600 displays Figure 6S Icon editing interface 604s is depicted.

[0258] exist Figure 6P At, the device responds to Figure 6N The device 600 displays a scheduling interface 604p based on the input 650n3 in the input 650n3. The scheduling interface 604p includes a regular interval enable representation 640j for scheduling medication at regular intervals (every day and / or every other day) and a specific day enable representation 640i for scheduling medication for a specific day of the week. As shown in the figure, in response to detecting the selection of the regular interval enable representation 640j, the device 600 displays different interval enable representations for taking medication, including every day, every other day, every three days, and / or every four days.

[0259] exist Figure 6P At 604p, while the scheduling interface 604p is displayed, the device 600 detects an input 650p (e.g., a tap and / or a mouse click) directed to a specific day indicator 640i. In response to detecting the input 650p, the device 600 displays the following Figure 6Q Arrangement interface 604q is depicted.

[0260] exist Figure 6Q At 604q, scheduling interface 604q includes a weekday indicator 640k. As shown, Sunday is selected (e.g., the medication will be scheduled to be taken every Sunday). While scheduling interface 604q is displayed, device 600 detects input 650q (e.g., a tap and / or a mouse click) directed to completion indicator 642. In response to detecting input 650q, device 600 displays the following Figure 6R Arrangement interface 604r is depicted.

[0261] exist Figure 6R, scheduling interface 604r is similar to scheduling interface 604o. Scheduling interface 604r includes an indication that custom affordance 640c has been selected (e.g., using a symbol (e.g., a check mark) and / or including information about the custom configuration (e.g., "Every Sunday")). In some embodiments, device 600 detects input directed to "next" affordance 624. In response to detecting input directed to the "next" affordance, device 600 displays a screen similar to the following. Figure 6S An icon interface of the icon editing interface 604s is depicted.

[0262] exist FIG. 6S to FIG. 6T At , the device 600 displays an interface configured with icons (e.g., glyphs and / or images) for the medication. Figure 6S At 604s, the icon editing interface includes a set of affordances to select a shape (e.g., a symbol) representing melatonin. FIG. 6C to FIG. 6M In some embodiments, melatonin is selected based on the techniques described in Figure 6P to Figure 6R One of the techniques described in is a melatonin selection arrangement. The enable representations for selecting shapes include a first subset 644a of shape enable representations associated with common shapes of medications (e.g., medicine bottles, tablets, and / or liquids). The enable representations for selecting shapes also include a second subset 644b of shape enable representations associated with shapes in which the medication does not appear and / or are less common for the medication (e.g., triangles, hearts, and / or polygons). In response to detecting input 650s1 directed to the capsule enable representation 644c (e.g., a tap and / or a mouse click), the device 600 displays (e.g., updates and / or replaces a previous icon) the melatonin icon 648a. In some embodiments, in response to detecting a selection to skip the enable representation 625, the device 600 skips the configuration process for the icon (e.g., and optionally, displays Figure 6V Interaction factor interface 604v).

[0263] exist Figure 6S At 604s, while displaying icon editing interface 604c in which affordance 644c is selected, device 600 detects input 650s2 (e.g., a tap and / or a mouse click) directed to “next” affordance 624. In response to detecting input 650s2, device 600 displays Figure 6T Icon editing interface 604t is depicted.

[0264] exist Figure 6TAt , icon editing interface 604t includes a set of affordances for selecting one or more visual aspects (e.g., colors, symbols, shapes, patterns, and / or symbols) of a background of icon 648a. In response to detecting input 650t1 (e.g., a tap and / or a mouse click) directed to a visual aspect (e.g., a grid) associated with affordance 644f, device 600 displays the visual aspect of the background of icon 648a (e.g., updating and / or replacing a previous visual aspect of the background).

[0265] exist Figure 6T At , the set of affordances includes affordances 644e for selecting a visual aspect (e.g., a color, symbol, shape, pattern, and / or symbol) of the capsule. In some embodiments, in response to detecting input 650t2 (e.g., a tap and / or a mouse click) directed to a visual aspect associated with affordance 644g, device 600 displays the capsule with the selected visual aspect (e.g., updating and / or replacing the previous visual aspect of icon 648a). In some embodiments, multiple colors for different parts of the shape may be selected. For example, in some embodiments, one color is selected for one end of the capsule, and a different color is selected for the other end of the capsule.

[0266] exist Figure 6T At 604t, while displaying the icon editing interface 604t, the device 600 detects an input 650t3 (e.g., a tap and / or a mouse click) directed to the “next” affordance 624. In response to detecting the input 650t3, the device 600 displays the following Figure 6U Add details interface 604u is depicted.

[0267] exist Figure 6U At the add details interface 604u, the add details interface 604u includes a text field for adding details of the medication. In some embodiments, the details interface 604u includes a nickname text field 646a to allow the user to configure a nickname for melatonin. The add details interface 604u includes a note text field 646b to allow the user to add a note for melatonin. While displaying the add details interface 604u, the device 600 detects an input 650u (e.g., a tap and / or a mouse click) directed to the "next" affordance 624. In response to detecting the input 650u, the device 600 displays the following: Figure 6V Interaction factors interface 604v is depicted.

[0268] exist Figure 6VAt , the interaction factor interface 604v includes an enable representation for enabling or disabling interaction factors associated with the user. In some embodiments, the interaction factors 652 include non-drug factors that potentially increase risk (e.g., risk of side effects and / or injury) when combined with taking medications. In some embodiments, when the user is adding an initial medication to the health application, the device 600 displays the interaction factor interface 604v. In some embodiments, when the user adds a subsequent medication (e.g., a medication added after the initial medication), the interaction factor interface 604v is not displayed. In some embodiments, the displayed interaction factors are selected / managed based on a specific medication, where different medications potentially have different interaction factors to choose from.

[0269] exist Figure 6V , alcohol affordance 652a for alcohol is enabled (e.g., indicating that the user consumes alcohol). affordance 652b for marijuana is disabled (e.g., indicating that the user does not consume marijuana). affordance 652c for tobacco is disabled (e.g., indicating that the user does not consume tobacco). While displaying interaction factor interface 604v, device 600 detects input 650v (e.g., a tap and / or a mouse click) for completion affordance 654. In response to detecting input 650v, device 600 displays as shown. Figure 6W Tracking interface 656 is depicted.

[0270] exist Figure 6W At, the tracking interface 656 includes melatonin as a tracked drug (e.g., an active drug and / or an enabled drug). In some embodiments, melatonin is included in the scheduled drug section 660a (e.g., as opposed to being added as an on-demand drug without a schedule). In some embodiments, the scheduled drug section 660a includes an indication that the scheduled drug is due. In some embodiments, the indication that the scheduled drug is due includes a scheduled drug tile 668a. In some embodiments, the scheduled drug tile 668a includes one or more drugs that are due. As shown, the scheduled drug section 660a includes a scheduled time 643 for melatonin (e.g., 9:00 p.m.), an icon 648a of melatonin, and a nickname for melatonin. In some embodiments, as shown, when a drug has a nickname (e.g., "sleep aid"), the drug name (e.g., "melatonin") is not displayed in the scheduled drug section 660a.

[0271] exist Figure 6WIn the example, the tracking interface 656 includes an active medication portion 660b. In some embodiments, the active medication portion 660b includes a group of one or more medications being actively tracked by the health application. As shown, melatonin is included in the active medication portion 660b such as an active medication tile 670a. In some embodiments, as shown, the active medication tile 670a includes an icon 648a of melatonin, a nickname of melatonin, a medication form of melatonin (e.g., "capsule") (e.g., a configurable option similar to the selected form 630c), a medication strength (e.g., "10mg") (e.g., a configurable option similar to the selected strength option 626a), and an indication of frequency (e.g., a configurable option similar to the daily indicator 640a).

[0272] In some embodiments, tracking interface 656 includes an add medication affordance 662 that allows a user to add medication to the health application. While tracking interface 656 is displayed, device 600 detects input 650w (e.g., a tap and / or a mouse click) directed to add medication affordance 662. In response to detecting input 650w, device 600 displays the following: Figure 6C Search interface 604c is depicted.

[0273] exist Figure 6X , time has passed since melatonin was added, and the user has added multiple drugs, including nitroglycerin, aspirin, losartan and cetirizine, as indicated by active drug tiles 670b to 670e. Active drug tiles 670b to 670e are similar to active drug tiles 670a, but have different states based on the user's selection when adding the corresponding drug. Nitroglycerin is the drug most recently added to the health application. Therefore, active drug tiles 670b are located above active drug tiles 670a, 670c to 670e. In some embodiments, the user can edit the order of active drug tiles later. In addition, because nitroglycerin, losartan and cetirizine are arranged drugs, the arrangement information associated with these drugs is displayed in arranged drug tiles 668b to 668c, which are similar to arranged drug tiles 668a, but have different states based on the user's selection when adding the corresponding drug. As shown, the scheduled medication tiles 668b through 668c are displayed in the order of when the scheduled medications are due.

[0274] exist Figure 6X At 60 , the tracking interface 656 includes a first risk tile 674. As shown, the first risk tile 674 is for nitroglycerin (which is the most recently added drug to the health app). The first risk tile 674 shows a serious risk of a potential drug interaction with alcohol, which is consumed by the user (e.g., via Figure 6VIn some embodiments, the first risk tile 674 is non-persistent. For example, the first risk tile 674 can be removed from the tracking interface 656 based on detecting a selection to remove the affordance 675 to remove the notification from the indicator. In some embodiments, the device 600 stops displaying the first risk tile 674 after a period of time has passed. In some embodiments, the first risk tile 674 persists until the user interacts with the tile.

[0275] exist Figure 6X At , the tracking interface 656 includes a second risk tile 676. The second risk tile 676 includes an indication of two moderate risks and an indication of a serious risk. As shown, the indication of the serious risk of the interaction between nitroglycerin and alcohol appears differently in the second risk tile 676 than in the first risk tile 674 (e.g., different amounts of information and / or different visual characteristics). In some embodiments, the second risk tile 676 is persistent (e.g., cannot be removed). As shown, the second risk tile 676 is located below the first risk tile 674. In some embodiments, while displaying the first risk tile 674, the device 600 detects input 650x1 (e.g., swipe and / or drag). In response to detecting input 650x1, the device 600 scrolls the tracking interface 656 to display the second risk tile 676 (e.g., and stops displaying the first risk tile 674).

[0276] At 6X, the first risk tile 674 and the second risk tile 676 are user selectable. While displaying the first risk tile 674, the device 600 detects an input 650x2 (e.g., a tap and / or a mouse click) directed to the first risk tile 674. In response to detecting the input 650x2, the device 600 displays the following. Figure 6Y The risk interface 672a is depicted. While the second risk tile 676 is displayed, the device 600 detects an input 650x2 (eg, a tap and / or a mouse click) directed to the second risk tile 676. In response to detecting the input 650x2, the device 600 displays the following. Figure 6Z Risk interface 672b is depicted.

[0277] exist Figure 6Y At 672a, the risk interface 672a includes expanded details associated with the first risk tile 674. As shown, these details include potential side effects of the interaction between melatonin and drinking alcohol.

[0278] exist Figure 6ZAt, risk interface 672b includes selectable risk indicators. As shown, risk interface 672b includes different categories of risks, including severe interaction risk, moderate interaction risk and low interaction risk. Under severe interaction risk category, risk indicator 678a indicates the interaction between alcohol and nitroglycerin (similar to first risk block 674). Select risk indicator 678a to display an interface similar to risk interface 672a. Under moderate interaction risk category, risk indicator 678b indicates the interaction between alcohol and sleeping aids, while risk indicator 678c indicates the interaction between alcohol and painkillers. Select risk indicator 678b and / or risk indicator 678c to make device 600 display a user interface including details about interaction, similar to interface 672a (which includes additional information about interaction). Risk interface 672b also includes a risk indicator 678d indicating the absence of low risk interaction.

[0279] exist Figure 6Z At , risk interface 672b includes an interaction factor indicator 680 indicating that alcohol will potentially interact with active medications. The user can modify interaction factor 652 by selecting an “edit” affordance. While interaction factor indicator 680 is displayed, device 600 detects input 650z (e.g., a tap and / or a mouse click) corresponding to a request to modify interaction factor 652. In response to detecting input 650z, device 600 displays a request to modify interaction factor 652. Figure 6V The interaction factor interface 604v is similar to the interaction factor interface.

[0280] exist Figure 6AA At, after the user modifies the interaction factor 652 to disable the alcohol affordance 652a, the device 600 displays the tracking interface 656. As shown, based on the alcohol affordance 652a being disabled, the first risk tile 674 is no longer displayed. As a result of the device 600 removing the first risk tile 674, the device 600 moves the arranged drug tiles 668b to 668c upward. In addition, the device 600 updates the second risk tile 676 based on the alcohol affordance 652a being disabled. As shown, the second risk tile 676 indicates that no drug interaction is found. Although the first risk tile 674 and the second risk tile 676 are described as indicating the potential risk of interaction between the drug and the interaction factor 652, in some embodiments, the first risk tile 674 and the second risk tile 676 indicate the potential risk of interaction between two active drugs. In some embodiments, the first risk tile 674 and the second risk tile 676 do not indicate the potential risk of interaction between an inactive drug and an active drug.

[0281] exist Figure 6AAAt , while displaying tracker interface 656, device 600 detects input 650aa (e.g., a tap and / or a mouse click) corresponding to an affordance for editing an active medication. In response to detecting input 650aa, device 600 displays Figure 6AB Interface 682 is depicted.

[0282] exist Figure 6AB At the interface 682, the active drug 683a (similar to Figure 6X 670a to 670e of FIG. 670a ) and inactive drugs 683b. In some embodiments, the device 600 stores drug information (e.g., drug form, drug strength, dosage, and / or scheduling information) for the inactive drugs 683b. As shown, amoxicillin, which is an inactive drug, can be activated in response to an input pointing to the activation enable indication 684b. In some embodiments, activating amoxicillin causes the device 600 to enable the drug, including displaying when amoxicillin is scheduled to be taken in the tracking interface 656, displaying amoxicillin as an active drug in the tracking interface 656, and / or displaying an indicator of the potential risk of taking amoxicillin in the first risk tile 674 and / or the second risk tile 676.

[0283] exist Figure 6AB At nitroglycerin as an active medication, nitroglycerin is displayed with deactivation indicator 684a. In some embodiments, deactivating nitroglycerin causes device 600 to deactivate the medication, including not displaying when nitroglycerin is scheduled to be taken in tracking interface 656, not displaying nitroglycerin in active medications in tracking interface 656, and / or not displaying an indication of the potential risk of taking nitroglycerin in first risk tile 674 and / or second risk tile 676. Interface 682 also includes add medication indicator 662.

[0284] exist Figure 6AB At , while displaying interface 682, device 600 detects input 650ab (e.g., a tap and / or a mouse click) directed to deactivate affordance 684a. In response to detecting input 650ab, device 600 displays sharing notification 684 indicating that the medication is shared with another user (e.g., a care provider and / or family member), such as Figure 6AC Depicted.

[0285] exist Figure 6AC At 684, sharing notification 684 includes a continue sharing affordance 686a and a stop sharing affordance 686b. While displaying sharing notification 684, device 600 detects input 650ac (e.g., a tap and / or a mouse click) directed to stop sharing affordance 686b. In response to detecting input 650ac, device 600 stops sharing the medication. Additionally, in response to detecting input 650ac, device 600 displays the following: Figure 6AD Tracking interface 656 is depicted.

[0286] exist Figure 6AD At , based on the deactivation of nitroglycerin, the tracking interface 656 has been updated. As shown in the figure, nitroglycerin has been removed from Figure 6AA The arrangement block 668c is removed so that the device 600 is Figure 6AD At 668a, the scheduled medication tile 668a including only sleep aids is displayed. In addition, the active medication tile 670b for nitroglycerin is no longer displayed, and active medication tiles 670a, 670c to 670e are displayed. Figure 6AA If the risk indicator (e.g., first risk tile 674 and second risk tile 676) of the tracking interface 656 of the device 600 indicates a potential risk of nitroglycerin causing an interaction, the device 600 will update the device 600 based on the discontinuation of nitroglycerin. Figure 6AD Tracking interface 656.

[0287] FIG. 7A to FIG. 7B 1 is a flowchart illustrating a method for tracking medication using a computer system according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600, and / or 1400) (e.g., a smart watch, a smart phone, a tablet computer, and / or a laptop computer) communicating with a display generation component (e.g., 601 and / or 1401) (e.g., a display controller, a touch-sensitive display system, and / or a monitor) and one or more input devices (e.g., 601 and / or 1401) (e.g., a touch-sensitive surface, a keyboard, a controller, a rotatable input device, a microphone, and / or a mouse). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0288] As described below, method 700 provides an intuitive way to configure the properties of a medication. The method reduces the cognitive burden on a user when tracking medications, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to track medications faster and more efficiently saves power and increases the time interval between battery charges.

[0289] The computer system displays (702) via a display generation component for selecting a first drug (e.g., Fig.6D nitroglycerin) (e.g., scheduled medications and / or on-demand medications) (e.g., prescription or over-the-counter medications; digital therapeutics; pharmaceutical compounds) to be added to a first user interface (e.g., 604c to 604d) of a medication tracking application (e.g., an application that includes a schedule for taking one or more medications and / or an application that notifies a user when a medication is scheduled to be taken).

[0290] While displaying a first user interface, the computer system detects (704) a first group of one or more inputs via one or more input devices, the first group of one or more inputs including a first input corresponding to a selection of a first drug (e.g., 650d1 and / or an input on a CHR enable representation (e.g., 612a to 612b) associated with a drug that does not have a drug form) (e.g., a tap, a swipe, a mouse click, a voice input, and / or a key press; a selection of an enable representation corresponding to a drug; a confirmation input confirming the selection; a text input specifying a drug).

[0291] In response to detecting the first set of one or more inputs, the computer system displays (706) via the display generation component a second user interface (e.g., 604e) (e.g., the same as the first user interface and / or different from the first user interface), the second user interface including: first options (708) (e.g., 622a to 622d) (e.g., user-selectable graphical objects) for a first medication form (e.g., a capsule, a tablet, a patch, and / or an oral solution) (e.g., the form in which the medication is taken (e.g., consumed and / or administered)) (e.g., the dosage form (e.g., shape, formulation (e.g., capsule, suspension, liquid, and / or tablet)) in which the medication is taken (e.g., consumed and / or administered) (in some embodiments, including a filling a first drug form (e.g., an agent, a binder, and / or an adjuvant)), the first drug form being based on the first drug (e.g., the first drug form is a form available for the first drug (e.g., as indicated by a reference database)); a second option (710) (e.g., 622a to 622d) (e.g., a user-selectable graphical object), the second option being for a second drug form (e.g., a capsule, a tablet, a patch, and / or an oral solution), the second drug form being based on the first drug (e.g., the second drug form is a different form available for the first drug), the second drug form being different from the first drug form; in some embodiments, in response to an input set corresponding to a request to add the first drug, a third option for a third drug form that is not available for the first drug is not displayed.

[0292] While displaying the second user interface, the computer system detects (712) a second set of one or more inputs via one or more input devices, the second set of one or more inputs including a second input (e.g., 650e and / or 650f) corresponding to a selection of a corresponding drug form (e.g., a tap, a swipe, a mouse click, a voice input, and / or a key press).

[0293] In response to detecting the second set of one or more inputs, the computer system displays (714) a third user interface (e.g., 604g) (e.g., the same as the first user interface and / or the second user interface, or, optionally, different from the first user interface and / or the second user interface) via the display generation component, and a first set of at least two drug strength options (e.g., 622a to 622d) (e.g., indicators indicating; an amount and / or concentration of one or more active ingredients in a drug form and / or unit of a drug form (e.g., 50 mg (e.g., for a capsule drug form) and / or 250 mg / 5 mL (e.g., for a suspension drug form)) based on a determination (716) that the first set of strength criteria are satisfied (where the first set of strength criteria includes a first strength criteria that is satisfied when the corresponding drug form corresponds to the first drug form), the first set of at least two drug strength options are based on the first drug form (e.g., the first set of at least two drug strength options are strengths in which the first drug form of the first drug is available).

[0294] In response to detecting the second set of one or more inputs, the computer system displays (714) a third user interface (e.g., 604g) (e.g., the same as the first user interface and / or the second user interface, or, optionally, different from the first user interface and / or the second user interface) via the display generation component, and a second set of at least two drug strength options based on (718) determining that the second set of strength criteria are met (wherein the second set of strength criteria include second strength criteria that are met when the corresponding drug form corresponds to the second drug form), the second set of at least two drug strength options are based on the second drug form (e.g., the second set of at least two drug strength options are strengths available for the second drug form of the first drug) (in some embodiments, the second set of drug strength options include a third drug strength and a fourth drug strength that is different from the third drug strength. In some embodiments, the third drug strength and / or the fourth drug strength is not available in the first drug form). In some embodiments, the second set of at least two medication strength options is different from the first set of at least two medication strength options (e.g., options similar to affordances 626a-626d but at least two of which correspond to medication strength options other than 0.2 mg, 0.4 mg, and / or 0.6 mg) (e.g., the second set includes medication strength options that are not in the first set, or vice versa. In some embodiments, the second set includes at least one medication strength option in the first set). In some embodiments, the first set of medication strength options includes a first medication strength and a second medication strength that is different from the first medication strength. Displaying a second user interface including options for different medication forms based on the selected medication provides a curated experience without cluttering the user interface when the user specifies aspects when adding medications to the medication tracking application, thereby providing improved visual feedback to the user, and performing operations without further user input when a set of conditions are met. Displaying a third user interface including a set of different medication strength options based on the selected medication form provides a curated experience without cluttering the user interface when the user specifies aspects when adding medications to the medication tracking application, thereby providing improved visual feedback to the user, and performing operations without further user input when a set of conditions are met.

[0295] In some embodiments, in response to detecting the second set of one or more inputs, the computer system ceases to display the second user interface and / or options for the drug form (e.g., a first option for the first drug form and / or a second option for the second drug form). In some embodiments, drug strength is not displayed in the second user interface. In some embodiments, the option for drug strength is not selectable (and / or not displayed) until the drug form is selected. In some embodiments, the option for drug strength is not displayed until the drug form is selected.

[0296] In some embodiments, the first user interface includes the second drug (in some embodiments, the first user interface is displayed in response to a search for the drug; in some embodiments, the first user interface includes a first set of search results having the first drug and the second drug). In some embodiments, while displaying the first user interface, the computer system detects, via one or more input devices, a third set of one or more inputs that includes a search result related to the search for the second drug (e.g., Fig.6D In some embodiments, in response to detecting the third set of one or more inputs, the computer system displays, via the display generation component, a fourth user interface including a third option for a third drug form (e.g., an oral suspension, a foam, a device, an inhaler, a topical medication, drops, and / or an oral solution) that is different from the first drug form, wherein the fourth user interface does not include an option selected from the group consisting of the first option and the second option. Displaying the first user interface for selecting between different drugs to display different drug forms depending on the selected drug provides a curated experience without cluttering the user interface when the user specifies aspects when adding drugs from a plurality of drugs to the drug tracking application, thereby providing improved visual feedback to the user, and performing operations without further user input when a set of conditions are met.

[0297] In some embodiments, the first set of strength criteria includes a third strength criterion that is satisfied when the first drug is a drug of a first type (e.g., a particular drug / drug combination (e.g., nitroglycerin, aspirin, losartan, and / or cetirizine)). ... fourth strength criterion that is satisfied when the corresponding drug form corresponds to the first drug form and a fourth strength criterion that is satisfied when the first drug is a drug of a second type different from the first type (e.g., if the first drug is nitroglycerin, the second type of drug is Fig.6DIn some embodiments, the strength options provided are based on both the selected form and the selected drug. In some embodiments, the first group of at least two drug strength options and the second group of at least two drug strength options do not include drug strength options that are not associated with the first drug (e.g., drug strength options that are identified as not relevant to the first drug and / or drug strength options that are not available for its first drug) (in some embodiments, only strengths available for its drug are displayed in the third user interface). Providing drug strength options based on drug type and selected drug form performs an operation (e.g., provides related drug strength options) without requiring further user input when a set of conditions (selection of a specific drug type and a specific form) are met.

[0298] In some embodiments, the method of determining that a fourth set of strength criteria is met (wherein the fourth set of strength criteria includes when the corresponding drug form (e.g., the first drug form and / or the second drug form) is combined with less than two drug strengths (e.g., Fig.6D In some embodiments, the third user interface includes one or more options for medical characteristics other than drug strength (e.g., a shape option or a nickname option). Omitting the drug strength option from the third user interface when there is only one possible drug strength option reduces the number of inputs required to perform the operation, and performing the operation without further user input when a set of conditions are met.

[0299] In some embodiments, in response to detecting the second set of one or more inputs, displaying a third user interface includes and based on determining that a fourth set of strength criteria is satisfied (where the fourth set of strength criteria includes a sixth strength criterion that is satisfied when the corresponding drug form (e.g., the first drug form and / or the second drug form) is associated with at least two active ingredients in drug form (e.g., a single drug form and / or a single unit of the drug form has at least two chemical ingredients in specific amounts and / or specific concentrations)), the computer system displays an option to define the drug strength value of the drug strength as unknown (e.g., no strength exists and / or no known strength exists). In some embodiments, based on determining that a third set of criteria includes a fifth criterion that is satisfied when the corresponding drug form is associated with less than two drug strengths, the computer system displays options to define drug characteristics other than drug strength (e.g., an option to specify an arrangement and / or an option to select visual characteristics of a representation of the first drug).

[0300] In some embodiments, the computer system detects, via one or more input devices, a fourth set of one or more inputs, the fourth set of one or more inputs including a fourth input corresponding to a selection of a first medication strength option (e.g., 626a-626c) for a first medication strength, wherein the first medication strength option is included in the first set of at least two medication strength options. In some embodiments, in response to detecting the fourth set of one or more inputs and based on determining that a first set of medication tracking criteria is satisfied (wherein the first set of medication tracking criteria includes a first medication tracking criteria that is satisfied when the medication tracking application does not include an existing medication (e.g., an active medication and / or an archived medication) that matches (e.g., corresponds to) at least the first medication form and the first medication strength), the computer system adds the first medication to the medication tracking application (e.g., in Figure 6G In the example, when the medication tracking application does not include the same medication in the same form and strength (e.g., 0.2 mg of nitroglycerin in tablet form, 0.2 mg of nitroglycerin in tablet form is added to the medication tracking application).

[0301] In some embodiments, in response to detecting the fourth set of one or more inputs and based on determining that the first set of medication tracking criteria is not satisfied, the computer system forgoes adding the first medication to the medication tracking application (e.g., Figure 6GIn some embodiments, when the medication tracking application includes the same medication (e.g., 0.2 mg nitroglycerin in tablet form) in the same form and strength, 0.2 mg nitroglycerin in tablet form is not added to the medication tracking application (e.g., the medication tracking application prohibits the user from adding duplicate medications in the same form and medication strength). In some embodiments, based on determining that a first set of existing medication criteria including a first existing medication criterion is not met, the computer system displays an option to modify a previously selected medication characteristic (e.g., a first medication, a first medication form, and / or a first medication strength). Conditionally continuing to add medications to the medication tracking application based on whether there is another medication in the same medication form and medication strength allows the computer system to prevent duplicate input in the medication tracking application, thereby providing improved feedback to the user regarding the system status (e.g., whether the system includes or does not include medication inputs in the same medication form and medication strength), and performing operations without further user input when a set of conditions are met.

[0302] In some embodiments, in response to detecting the fourth set of one or more inputs, the computer system displays, via the display generating component and based on determining that the second set of medication tracking criteria are satisfied (wherein the second set of medication tracking criteria includes the second medication tracking criteria being satisfied when an inactive medication (e.g., an archived medication and / or a medication that is not actively tracked, including a medication that is not a scheduled medication and / or is not included as an on-demand medication) of the medication tracking application matches (e.g., corresponds to) at least the first medication form and the first medication strength), an option to activate the inactive medication (e.g., in the display generating component). Figure 6G In the example of FIG. 6 , an option to activate 0.2 mg of nitroglycerin in tablet form is displayed when the medication tracking application includes the same medication in the same form and strength (e.g., 0.2 mg of nitroglycerin in tablet form) but the medication is inactive (683b) (e.g., modifying a medication that is not actively tracked to be an actively tracked medication, including a scheduled medication and / or an on-demand medication). Displaying the option to activate the inactive medication notifies the user that there is a medication previously added to the medication tracking application that has the same medication form and medication strength as the medication the user is currently attempting to add, thereby providing the user with improved visual feedback (e.g., regarding the state of the system, such as whether the system includes or does not include a medication input having the same medication form and medication strength), and performing the operation without further user input when a set of conditions are met.

[0303] In some embodiments, the computer system detects a fifth set of one or more inputs (e.g., Figure 6GIn some embodiments, the computer system displays one or more options for configuring a schedule according to which the first medication should be taken (e.g., options for specifying a schedule for recording an action and / or options for defining a frequency of reminders for recording an action for the first medication) in response to detecting the fifth set of one or more inputs (e.g., input pointing to 624 in the middle) (e.g., the same and / or different from the fourth set of inputs), the fifth set of one or more inputs including a fifth input (e.g., the same and / or different from the fourth input) corresponding to a selection of a second medication strength option (e.g., 626a to 626c) (e.g., the same and / or different from the first medication strength option) for a second medication strength (e.g., the same and / or different from the first medication strength), wherein the second medication strength option is included in the first set of at least two medication strength options. In some embodiments, in response to detecting the fifth set of one or more inputs (in some embodiments, based on determining that the first medication is to be added to the medication tracking application (e.g., the user has already selected a medication form and a medication strength and / or the first medication does not correspond to an existing medication tracked by the medication tracking application)), the computer system displays one or more options for configuring a schedule according to which the first medication should be taken (e.g., options for specifying a schedule for recording an action and / or options for defining a frequency of reminders for recording an action for the first medication) (e.g., 640a to 640k). In some embodiments, the one or more options for configuring the schedule include an option to designate the first medication as a non-scheduled medication (e.g., an on-demand medication). In some embodiments, one or more options for configuring a schedule include a daily option for scheduling the first medication for each day of the week. In some embodiments, selection of the daily option results in simultaneous display of an option for setting a first scheduled time (e.g., taking the first medication and / or recording a recording action), an option for configuring a scheduled dose (e.g., quantity or amount) of the first medication (e.g., 1 tablet and / or 2 tablets), an option for configuring adding a second scheduled time different from the first scheduled time, and an option for configuring a start date for taking the first medication. Displaying one or more options for configuring a schedule according to which the first medication should be taken provides a curated experience without cluttering the user interface when the user specifies aspects when adding medications to the medication tracking application, thereby providing improved visual feedback to the user, and performing operations without further user input when a set of conditions are met.

[0304] In some embodiments, the computer system forgoes adding (e.g., does not add) the first medication until a schedule for the first medication has been configured (e.g., including designating the first medication as a non-scheduled medication, such as an on-demand medication) (e.g., the first medication cannot be added without a schedule for the first medication being configured).

[0305] In some embodiments, in response to detecting a request to configure the first drug as a non-scheduled drug, the computer system displays an option (e.g., 604s and / or 604t) for configuring the visual characteristics (e.g., color, shape, symbol and / or icon) of the representation of the first drug. In some embodiments, one or more options for configuring the arrangement include a first arrangement option, which, when selected, causes the display to arrange the first drug at regular intervals (e.g., once every other day and / or once every three days). In some embodiments, one or more options for configuring the arrangement include a second arrangement option, which, when selected, causes the display to arrange the first drug on a specific day of the week (e.g., every Sunday and / or every Wednesday). In some embodiments, selecting the second arrangement option results in displaying the corresponding options for each day of the week, which, when selected, arrange the drug for the selected day. In some embodiments, selecting the second arrangement option defaults to the corresponding option for Sunday being selected.

[0306] In some embodiments, (in some embodiments, after the computer system detects a selection of a corresponding drug form (e.g., the first drug form and / or the second drug form) and a corresponding drug strength (e.g., a drug strength option in the first set of at least two drug strength options and / or the first set of at least two drug strength options) of the first drug) the computer system displays one or more options (e.g., 644a to 644e) to configure a visual appearance (e.g., color, shading, texture, and / or symbol) of a representation (e.g., 648a (e.g., an icon, a capsule icon, a tablet icon, and / or a medicine bottle icon) of the first drug, wherein an option in the one or more options corresponds to a background (e.g., 644d and / or 644f) of the representation. In some embodiments, the background of the icon includes an area surrounding the icon (e.g., rather than the color and / or interior of the icon). Displaying one or more options to configure the visual appearance of the background of the representation of the first drug allows a user to customize how the computer system will present information, thereby providing improved visual feedback to the user, providing additional control options without cluttering the user interface with additional displayed controls, and performing operations when a set of conditions are met without requiring further user input.

[0307] In some embodiments, when the first medication is added, the computer system displays different color options for configuring the visual appearance of the icon depending on what icon (e.g., 604s and / or 604t) is selected (e.g., detecting selection of a capsule icon will produce options for customizing the color of both ends of the capsule, while selecting a pill will present options for customizing the color of the entire pill).

[0308] In some embodiments, in response to detecting input confirming that a schedule according to which the first medication should be taken, the computer system displays one or more options for configuring the visual appearance (e.g., color, shading, texture, and / or symbol) of the representation of the first medication. In some embodiments, the computer system forgoes displaying one or more options for configuring the visual appearance (e.g., color, shading, texture, and / or symbol) of the representation of the first medication until input confirming that a schedule according to which the first medication should be taken is detected.

[0309] In some embodiments, when adding a first medication, the computer system displays an option for configuring the name (e.g., a nickname and / or label) of the first medication. In some embodiments, the name is editable after the first medication has been added to the medication tracking application as a tracked medication. In some embodiments, when adding a first medication, the computer system displays an option for configuring a note about the first medication. In some embodiments, the note is editable after the first medication has been added to the medication tracking application as a tracked medication. In some embodiments, one or more medication characteristics (e.g., clinical name, medication form, and / or medication strength) cannot be edited after the first medication has been added to the medication tracking application as a tracked medication. In some embodiments, at least two tracked medications have the same name and / or note.

[0310] In some embodiments, after the first medication is added to the medication tracking application, the computer system displays a fifth user interface (e.g., 656), the fifth user interface including: in a first portion (e.g., 668a) of the fifth user interface corresponding to one or more scheduled medications, a first representation (e.g., 648a) of the first medication (e.g., text, such as a medication name, and / or an image, such as an icon of the medication), the first representation of the first medication including an indication of a first time (e.g., 643), in which a recording action for the first medication is scheduled (e.g., due); and in a second portion (e.g., 660b) of the fifth user interface corresponding to one or more medications being tracked (e.g., actively tracked) by the medication tracking application, a second representation (e.g., 648a) of the first medication (e.g., text, such as a medication name, and / or an image, such as an icon of the medication) (in some embodiments, the second representation is different from the first representation). In some embodiments, the first representation in the fifth user interface is similar to that described in reference to FIG. Fig.11 and Figures 10A to 10NThe method 1100 of claim 1100 includes a first user interface including representations of respective medications scheduled to be taken at the scheduled time. Displaying a fifth user interface separately including a first portion including a first representation of the first medication and a second portion including a second representation of the first medication notifies the user that the first medication has been added as an active medication and when the first medication should be taken, thereby providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, and performing an operation without requiring further user input when a set of conditions are met.

[0311] In some embodiments, the first portion of the fifth user interface includes a first plurality of representations (e.g., 668b and / or 668c) of a first plurality of medications (e.g., including the first medication). In some embodiments, the first plurality of representations are based on corresponding times for scheduling a recording action for the first plurality of medications (e.g., such as Figure 6X In some embodiments, the second portion of the fifth user interface includes a second plurality of representations of the second plurality of medications (e.g., 670a through 670e). In some embodiments, the representation of the medication in the second plurality of medications that was most recently added to the medication tracking application is displayed at a predetermined position (e.g., at the top (e.g., at the top of the sorted list)) in the second portion of the fifth user interface (e.g., reference 670a through 670e). Figure 6X , nitroglycerin is optionally the most recently added medication to the medication tracking application). Displaying a fifth user interface including a first portion having medications ordered based on respective times at which the recording action is scheduled and a second portion in which the most recently added medication is displayed in a predetermined position in the second portion allows the computer system to present medications in different orders in a single user interface to help the user identify information more quickly, thereby providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, and performing an operation without further user input when a set of conditions are met.

[0312] In some embodiments, the fifth user interface includes a first drug interaction corresponding to the first drug (e.g., Figure 6X interactions that alter (e.g., increase or decrease) the effectiveness of the corresponding medication (e.g., with different medications and / or user-defined factors (e.g., alcohol, marijuana, and / or tobacco)) and / or provide a risk of causing (e.g., introducing, increasing and / or decreasing) side effects from taking the corresponding medication (e.g., as described in reference Fig. 9Displaying an indication of a first drug interaction (e.g., 674) (e.g., a notification about a drug interaction and / or information about a drug interaction) allows the computer system to provide visual feedback about the status of the medication tracking application and whether it has identified a potential risk of taking the first medication, thereby providing improved visual feedback to the user and reducing the number of inputs required to perform operations.

[0313] In some embodiments, the computer system displays a sixth user interface (e.g., 604v) via a display generation component, the sixth user interface including a first user-selected interaction factor (e.g., 652a to 652c) having a corresponding state (e.g., enabled and / or disabled). In some embodiments, the sixth user interface includes an option to modify (e.g., deactivate and / or disable) a corresponding state (e.g., from an active state to an inactive state) of a first user-selected interaction factor (e.g., a lifestyle factor, a user-defined activity, and / or a non-drug factor). In some embodiments, the sixth user interface is displayed during the process of adding the first medication to the medication tracking application (e.g., before or after displaying the third user interface, but before displaying a main tracking user interface (e.g., the fifth user interface) including an indication that the first medication is an active medication). In some embodiments, the sixth user interface is displayed after the first medication is added to the medication tracking application. In some embodiments, the sixth user interface is displayed after the first medication is added to the medication tracking application. Fig. 9 Displaying the sixth user interface with the user-selected interaction factor in an active state and one or more options for modifying the state of the user-selected interaction factor allows the computer system to perform operations based on user-selected preferences, thereby providing improved visual feedback to the user, providing additional control options without cluttering the user interface with additional displayed controls, and performing operations without requiring further user input when a set of conditions are met.

[0314] In some embodiments, the computer system displays one or more options to modify the state of the interaction factor selected by the first user after displaying the option to select the drug form and drug strength of the first drug. In some embodiments, the computer system displays one or more options to modify the state of the interaction factor selected by the first user before adding the first drug as a tracked drug to the drug tracking application (e.g., during the process of adding the first drug to the drug tracking application). In some embodiments, the computer system displays one or more options to modify the state of the interaction factor selected by the first user during the process of adding the initial drug (e.g., the first drug that will be tracked by the drug tracking application) to the drug tracking application. In some embodiments, the computer system abandons displaying one or more options to modify the state of the interaction factor selected by the first user during the process of adding the drug after the initial drug. In some embodiments, after adding the initial drug to the drug tracking application and in response to detecting a request to modify the state of the interaction factor selected by the first user, the computer system displays one or more options to modify the state of the interaction factor selected by the first user.

[0315] Note that the above reference method 700 (eg, FIG. 7A to FIG. 7B ) also apply in a similar manner to the methods described below. For example, methods 800, 900, 1100, 1300, and / or 1500 optionally include one or more features of the various methods described above with reference to method 700. For example, the process of configuring various drug features and / or adding drugs in method 700 optionally occurs before and / or after methods 800, 900, 1100, 1300, and / or 1500. In addition, methods 800, 900, 1100, 1300, and / or 1500 optionally utilize various features and drugs configured in method 700. For the sake of brevity, these details are not repeated below.

[0316] Figure 8 800 is a flowchart illustrating a method for tracking medication according to some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600, and / or 1400) (e.g., smart watch, smart phone, tablet computer, and / or laptop computer) communicating with a display generation component (e.g., 601 and / or 1401) (e.g., display controller, touch-sensitive display system, and / or monitor) and one or more input devices (e.g., 601 and / or 1401) (e.g., touch-sensitive surface, keyboard, controller, rotatable input device, microphone, and / or mouse). Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0317] As described below, method 800 provides an intuitive way to track an application by visualizing related medications to be added to the medication tracking application. The method reduces the cognitive burden on a user when searching for related medications to be added to the medication tracking application, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to search for medications faster and more efficiently saves power and increases the time interval between battery charges.

[0318] In a medication tracking application (e.g., an application that includes scheduling for taking one or more medications and / or an application that notifies a user when a medication is scheduled to be taken) for a first user (e.g., a user associated with device 600), a computer system detects (802) via one or more input devices a first set of one or more inputs (e.g., taps, swipes, mouse clicks, and / or voice inputs) (e.g., 650b, 650w) corresponding to a request to add a medication to be tracked (e.g., a scheduled medication and / or an on-demand medication) (e.g., a prescription or over-the-counter medication; a digital therapeutic; a pharmaceutical compound) (e.g., a set of inputs including at least one input on a medication addition affordance). In some embodiments, the first set of one or more inputs includes utterances corresponding to a request to add a medication to be tracked in the medication tracking application for the first user.

[0319] In response to detecting a first set of one or more inputs corresponding to a request to add a medication to be tracked, the computer system displays (804) via a display generating component a first user interface (e.g., 604c) of the medication tracking application, wherein displaying the first user interface includes displaying (806) a graphical user interface object (e.g., 610a to 610b) for searching for medications (e.g., a text field (e.g., a search bar) for searching for medications using text and / or an affordance for initiating a process of searching for medications using an image (e.g., an image captured by one or more cameras of the computer system and / or an image stored on the computer system, a scan of a pill bottle)), and based on determining that the first user has a clinical health record (e.g., a prescription, a clinical note, a correspondence with a caregiver, and / or an electronic health record accessible to (e.g., stored on) the computer system and / or the medication tracking application that identifies a corresponding medication (e.g., a specific medication (in some embodiments, the specific medication includes a specific dosage form and / or strength based on information in the CHR)) (e.g., stored and / or accessible). Figure 6C In the clinical health record and / or CHR enable indication 1234 for amoxicillin and / or albuterol, the computer system displays (808) options (e.g., 612a to 612b) (e.g., enable indications and / or buttons) for adding corresponding medications (e.g., scheduled medications and / or on-demand medications) based on the clinical health record to be tracked in the medication tracking application.

[0320] In response to detecting a first set of one or more inputs corresponding to a request to add a medication to be tracked, the computer system displays (804) a first user interface (e.g., 604c) of a medication tracking application via a display generating component, wherein displaying the first user interface includes displaying (806) a graphical user interface object (e.g., 610a to 610b) for searching for medications (e.g., a text field (e.g., a search bar) for searching for medications using text and / or an affordance for initiating a process of searching for medications using an image (e.g., an image captured by one or more cameras of the computer system and / or an image stored on the computer system, a scan of a pill bottle)), and based on determining that the first user does not have a clinical health record that identifies a corresponding medication, the computer system forgoes (810) displaying an option for adding medications (e.g., corresponding medications and / or non-corresponding medications) based on the clinical health record as medications to be tracked in the medication tracking application (e.g., scheduled medications and / or on-demand medications) (e.g., device 600 does not display a CHR affordance such as CHR affordances 612a to 612b). In some embodiments, the option to add the corresponding drug includes an indication of the drug type (e.g., name), an indication of the drug form, and / or an indication of the strength of the corresponding drug. In some embodiments, the option to add the corresponding drug does not include an indication of the drug type (e.g., name), an indication of the drug form, and / or an indication of the strength of the corresponding drug. In some embodiments, the computer system identifies multiple drugs in one or more CHRs and displays at least two options for adding different drugs (and / or different drugs from different institutions (and / or caregivers)) as scheduled drugs. In some embodiments, the computer system identifies clinical health records by accessing locally stored health records (e.g., associated with a drug tracking application) and / or by accessing externally stored health records (e.g., a caregiver's system). Displaying a user interface object for searching for drugs simultaneously with displaying drugs identified from clinical health records improves the computer system because this reduces the number of inputs required to add drugs to a drug tracking application, which reduces the number of inputs required to perform an operation.

[0321] In some embodiments, the first group of one or more inputs includes detecting input on an option to add a medication to the medication tracking application. In some embodiments, the first user interface is displayed in response to detecting input on the option to add a medication. In some embodiments, the option to add a medication is on a user interface that includes active medications (e.g., actively tracked and / or enabled medications) and / or archived medications. In some embodiments, the option to add a medication is on a user interface that includes scheduled medications. Displaying a user interface in response to detecting input on an option provides visual feedback to the user that the input is detected, and allows the user to add medication to the medication tracking application, which provides improved visual feedback and improves the human-computer interface.

[0322] In some embodiments, the option to add the corresponding medication is displayed before (e.g., independent of; in the absence of) detecting input on a graphical user interface object that searches for medications (e.g., displaying CHR affordances 612a-612b without device 600 detecting a search for medications). Displaying medications identified from clinical health records improves the computer system because it reduces the number of inputs required to add medications to the medication tracking application, which reduces the number of inputs required to perform operations.

[0323] In some embodiments, while displaying the option to add the corresponding drug, the computer system detects a second set of one or more inputs, the second set of one or more inputs including inputs corresponding to the option to search for drugs (e.g., 650c1 and / or 650c2) (e.g., selecting and / or entering text in the option) (e.g., selecting a text field, detecting text entered in the text field, selecting an affordance for initiating a process of searching for drugs using an image). In some embodiments, in response to detecting the second set of one or more inputs, the computer system stops displaying the option to add the corresponding drug (e.g., Fig.6D and / or Figure 6K In some embodiments, the option to add the corresponding drug is displayed in at least a portion of the corresponding area. In some embodiments, after the option to add the corresponding drug is stopped being displayed, the option (and / or keyboard) of the search results is displayed in the at least a portion of the corresponding area. In some embodiments, the option to add the corresponding drug is displayed simultaneously with the search results. Stopping the display of the drug identified from the clinical health record provides the user with visual feedback that the input of the search drug has been detected, and an additional display area for the search results is provided in the user interface, which provides improved visual feedback and does not clutter the user interface.

[0324] In some embodiments, while displaying the first user interface, the computer system detects a first input (e.g., 650c3, 650d1, 650d2, and / or 650d3). In some embodiments, in response to detecting the first input and in accordance with determining that the first input corresponds to a selection of an option to add a corresponding medication, the computer system displays a second user interface (e.g., 604n to 604r) including a scheduling option (e.g., an option for setting a medication time, a start medication date, and / or a number of doses to be taken at the scheduled time). In some embodiments, in response to detecting the first input and in accordance with determining that the first input corresponds to an option for adding a medication from the search results (e.g., 620a to 620c) (e.g., an option displayed in response to an input corresponding to a graphical user interface object for searching for medications), the computer system displays a third user interface (e.g., 604e, 604g, 604i, 604j) that does not include a scheduling option (e.g., the second user interface includes one or more options for defining the characteristics of the corresponding medication (e.g., medication form and / or medication strength)). In some embodiments, based on determining that the third set of one or more inputs corresponds to a selection of an option to add the corresponding medication, the computer system forgoes displaying one or more options for selecting a medication form and / or a medication strength. Displaying a user interface including scheduling options when a medication identified from a clinical health record is selected improves the computer system because it reduces the number of inputs required on an intermediate user interface (such as inputs for defining a medication form and / or a medication strength), which reduces the number of inputs required to perform an operation.

[0325] In some embodiments, the computer system displays search results (e.g., 620a to 620c) for the corresponding drug (e.g., in response to a text-based search and / or in response to an image-based search). In some embodiments, when displaying the search results for the corresponding drug, the computer system detects a third group of one or more inputs (e.g., 650d1, 650d2, and / or 650d3) including inputs corresponding to selections of the search results for the corresponding drug. In some embodiments, in response to detecting the third group of one or more inputs, the computer system displays options corresponding to the characteristics of the corresponding drug, wherein based on determining that the corresponding drug is a first drug, the characteristics of the corresponding drug are first characteristics (e.g., first drug strength, first drug form). In some embodiments, in response to detecting the third group of one or more inputs, the computer system displays options corresponding to the characteristics of the corresponding drug, wherein based on determining that the corresponding drug is a second drug, the characteristics of the corresponding drug are second characteristics different from the first characteristics (e.g., different drug strengths; different drug forms). In some embodiments, in response to detecting an input corresponding to a selection of a search result for a corresponding drug, the computer system forgoes an option to display features that are not available for the corresponding drug (e.g., the drug is not in the form in which it appears and / or the drug is not in the drug strength in which it appears). In some embodiments, in response to detecting an input corresponding to a selection of a search result for a corresponding drug, the computer system forgoes an option to display a drug strength for the corresponding drug (e.g., a drug strength for the corresponding drug). Figures 7A to 7B The option to display suggested properties based on the selected medication improves the computer system because it displays properties that are relevant to the selected medication (e.g., it removes properties that are not relevant to the selected medication), which reduces the number of inputs required to perform operations and does not clutter the user interface.

[0326] In some embodiments, the computer system detects a fourth set of one or more inputs (e.g., 650c2 and / or 650k) that includes inputs corresponding to a request to search using an image (e.g., an image taken before detecting the fourth set of one or more inputs and / or an image captured when detecting the fourth set of one or more inputs) (e.g., the fourth set of one or more inputs includes inputs pointing to a capture image option of a camera user interface and / or the computer system automatically captures an image in response to identifying one or more drug characteristics such as a drug type, a drug form, and / or a drug strength). In some embodiments, in response to detecting the fourth set of one or more inputs corresponding to a request to search using an image and based on determining that the image includes an identified drug form and an identified drug strength (e.g., such as Figure 6MIn some embodiments, in response to detecting a fourth set of one or more inputs corresponding to a request to search using an image and in response to determining that the image includes an identified drug form (e.g., Figure 6M is identified) rather than the strength of the drug being identified (e.g., Figure 6M In some embodiments, the image includes image data representing a label of a medication container (e.g., a bottle, a tube, and / or a spray can). In some embodiments, the image includes image data representing an image of a prescription and / or a medical record (e.g., a prescription written by a care provider). In some embodiments, in response to detecting a fourth set of one or more inputs corresponding to a request to search using an image and based on determining that the image includes an identified medication strength (e.g., Figure 6M is marked) rather than the marked drug strength (e.g., Figure 6M In some embodiments, the set of criteria includes criteria that the drug form is identified. Based on determining that the drug form is not identified, the computer system displays a suggested drug form for the corresponding drug (e.g., the drug identified in the image and / or the brand name identified in the image). In some embodiments, the set of criteria includes criteria that the drug strength is identified. In some embodiments, based on determining that the drug strength is not identified (and optionally, based on determining that the drug form is identified), the computer system displays a suggested drug strength for the corresponding drug. In some embodiments, these processes (e.g., the process of defining drug strength and / or the process of defining drug form) are similar to those described in reference to Figures 7A to 7B The process of method 700 is described in more detail. Displaying the option to confirm the medication identified in the image prevents the addition of erroneous medications to the application that the user will later need to delete and / or remove, which reduces the number of inputs required to perform the operation.

[0327] In some embodiments, while displaying the option to add the corresponding medication, the computer system detects a fifth set of one or more inputs that includes inputs corresponding to the option to add the corresponding medication (e.g., 650c3). In some embodiments, in response to detecting the fifth set of one or more inputs and based on determining that a medication form of the corresponding medication for the first user is not identified in the clinical health record (e.g., Figure 6C In some embodiments, in response to detecting the fifth set of one or more inputs and based on determining that the drug strength of the corresponding drug of the first user is not identified in the clinical health record (e.g., Figure 6C In the event that the "50MP" in 612a of the clinical health record is not identified), the computer system displays the suggested drug strengths (e.g., 626a to 626c) for the corresponding drug in the clinical health record. Displaying suggested characteristics for drugs identified from the clinical health record in the event that the data is missing or cannot be determined from the health record improves the computer system because it only displays the suggested characteristics when they are necessary, which reduces the number of inputs required to perform an operation and does not clutter the user interface.

[0328] In some embodiments, the computer system displays a second search result (e.g., 620a to 620c) for the corresponding drug via a display generation component (e.g., in a first user interface) (in some embodiments, the second search result is displayed in response to a search performed using a graphical user interface object for searching drugs). In some embodiments, the computer system detects a sixth group of one or more user inputs including an input corresponding to the second search result for the corresponding drug. In some embodiments, in response to detecting the sixth group of one or more user inputs and based on determining that the second search result corresponds to a plurality of potential choices (e.g., values, possibilities, choices, and / or options) for the first drug characteristic (e.g., strength and / or form) of the corresponding drug, (e.g., 622a to 622d and / or 626a to 626c), the computer system displays a user interface (e.g., 640e and / or 604g) including one or more options for identifying the selection of the first drug characteristic for the corresponding drug. In some embodiments, based on determining that the second search result corresponds to a single selection for drug characteristics, a user interface other than the user interface including one or more options for identifying the selection of the first drug characteristic for the corresponding drug is displayed. Displaying search results for the same drug that result in different user interfaces being displayed based on search criteria being met (e.g., search results for the drug that when selected lead to a scheduling user interface and search results for the drug that when selected lead to a non-scheduling user interface (e.g., a user interface for drug form and / or drug strength)) improves the computer system because it limits the amount of user input required to navigate through unnecessary user interfaces and only displays relevant user interfaces, which reduces the amount of input required to perform an operation.

[0329] In some embodiments, the first drug characteristic of the corresponding drug is selected from the group consisting of drug strength (e.g., 622a to 622d) and drug form (e.g., 626a to 626c). In some embodiments, the fourth user interface does not include an option for drug form and / or an option for drug strength. Displaying a user interface including drug form and / or drug strength options based on the selected drug search results provides visual feedback to the user about the state of the computer system (e.g., the computer cannot detect a form or strength from the search provided by the user, and / or the computer determines that the drug is associated with multiple forms and / or strengths), which provides improved visual feedback.

[0330] In some embodiments, the computer system displays a third search result (e.g., 620a to 620c) for the corresponding drug via a display generation component (e.g., in the first user interface) (in some embodiments, the second search result is displayed in response to a search performed using a graphical user interface object for searching for drugs). In some embodiments, the computer system detects a seventh set of one or more inputs including inputs corresponding to the third search result for the corresponding drug. In some embodiments, in response to detecting the seventh set of one or more user inputs and in accordance with determining that the third search result for the corresponding drug has multiple potential choices for the second drug characteristic (e.g., nitroglycerin has multiple forms, such as Fig.6D ), the computer system displays a user interface (e.g., 604e) including one or more options (e.g., 622a to 622d) for identifying a selection of a second drug characteristic for the corresponding drug (e.g., associated with the third search result). In some embodiments, in response to detecting the seventh set of one or more inputs and based on determining that the third search result for the corresponding drug has a single potential selection for the second drug characteristic (e.g., nitisinone has a drug form such as Fig.6D ), the computer system displays a user interface (e.g., 604g) including one or more options (e.g., 626a0626c) for identifying a selection for a third drug characteristic different from the second drug characteristic (e.g., similar to reference Figures 7A to 7B Displaying search results for a medication that result in different options being displayed based on whether the medication is associated with a single form or multiple forms reduces the number of inputs required to select a form when the medication is only available in a single form, which reduces the number of inputs and / or simplifies the user process for adding a medication to a medication tracking application.

[0331] In some embodiments, the computer system displays a fourth search result (e.g., 620b and / or 620c) for the corresponding drug via a display generation component (e.g., in the first user interface) (in some embodiments, the fourth search result is displayed in response to a search performed using a graphical user interface object for searching drugs). In some embodiments, the computer system detects an eighth set of one or more inputs including inputs corresponding to the fourth search result for the corresponding drug. In some embodiments, in response to detecting the eighth set of one or more user inputs and in accordance with determining that the fourth search result for the corresponding drug has multiple potential selections for drug strengths (e.g., nitrofurantoin has multiple drug strengths, such as Fig.6DIn some embodiments, in response to detecting the eighth set of one or more user inputs and in accordance with determining that the fourth search result for the corresponding drug has a single potential selection for a drug strength (e.g., nitisinone has a single drug strength, such as Fig.6D ), the computer system displays a user interface (e.g., 604e) including one or more options (e.g., 622a to 622d) for identifying a selection for a fourth drug characteristic other than drug strength (e.g., similar to reference FIG. 7A to FIG. 7B Conditionally displaying options for medication strengths based on whether the medication is associated with a single or multiple medication strengths reduces the number of inputs required to select a form when the medication is only available in a single medication strength and reduces the number of options displayed, which reduces the number of inputs and / or simplifies the user flow for adding a medication to a medication tracking application.

[0332] In some embodiments, the clinical health record for the corresponding medication is a clinical health record (e.g., a clinical health record associated with CHR enable representations 612a to 612b) that meets a predetermined record age standard (e.g., not older than a predetermined record age threshold (e.g., 3 months, 6 months, 1 year, 2 years, 5 years)) (in some embodiments, the record age is the prescription issuance / writing date). Displaying medications from clinical health records only if they are within a threshold time period reduces the number of inputs required to select the relevant medication and does not clutter the user interface, which reduces the number of inputs and / or simplifies the user process of adding medications to a medication tracking application.

[0333] In some embodiments, the computer system detects a ninth set of one or more inputs (e.g., text 618 in text search bar 610a) that includes input corresponding to a search for a corresponding drug. In some embodiments, in response to detecting the ninth set of one or more inputs and in accordance with determining that the search corresponding to the ninth set of one or more inputs does not correspond to (e.g., match) a known drug (e.g., Figure 6HIn some embodiments, the computer system displays an option to add a user-specified medication (e.g., a custom medication) (e.g., depicted) (e.g., a medication in a database accessible to the computer system), the computer system displays an option to add a user-specified medication (e.g., a custom medication) (e.g., 628). In some embodiments, the computer system receives a tenth set of one or more inputs (e.g., 650h) including inputs corresponding to the option to add a user-specified medication. In some embodiments, in response to receiving the tenth set of one or more inputs, the computer system displays a medication form selection user interface (e.g., 604i), which includes a first set of predetermined medication form options (e.g., 630a) (e.g., common forms) in a first portion of the medication form selection user interface. In some embodiments, in response to receiving the tenth set of one or more inputs, the computer system displays a medication form selection user interface, which includes a second set of predetermined medication form options (e.g., less common forms) (e.g., 630b) in a second portion of the medication form selection user interface that is different from the first set of predetermined medication form options. In some embodiments, the second group includes more options than the first group. Displaying two different medication form categories separate from one another allows a user to quickly identify related medication forms, which reduces the amount of input and / or simplifies the user process for adding medications to a medication tracking application.

[0334] Note that the process described above with respect to method 800 (eg, Figure 8 ) also applies in a similar manner to the methods described below / above. For example, method 800 optionally includes one or more features of the various methods described above with reference to methods 700, 900, 1100, 1300, and / or 1500. For example, the process of visualizing the characteristics of the related drugs and configuring the related drugs in method 800 optionally occurs before and / or after methods 700, 800, 900, 1100, 1300, and / or 1500. In addition, methods 700, 900, 1100, 1300, and / or 1500 optionally rely on and / or utilize the drugs selected in method 800. For the sake of brevity, these details are not repeated below.

[0335] Fig. 91 is a flowchart illustrating a method for tracking medication according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 600, and / or 1400) (e.g., smart watch, smart phone, tablet computer, and / or laptop computer) communicating with a display generation component (e.g., 601 and / or 1401) (e.g., display controller, touch-sensitive display system, and / or monitor) and one or more input devices (e.g., 601 and / or 1401) (e.g., touch-sensitive surface, keyboard, controller, rotatable input device, microphone, and / or mouse). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0336] As described below, method 900 provides an intuitive way to visualize drug interactions for tracked drugs. The method reduces the cognitive burden on users when identifying drug interactions, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to identify drug interactions faster and more efficiently saves power and increases the time interval between battery charges.

[0337] The computer system detects (907) via one or more input devices a set of one or more inputs (e.g., 650b and / or 650w) corresponding to adding corresponding medications as medications to be tracked in a medication tracking application (e.g., a medication tracking application associated with medication tracker enable indication 608) (e.g., an application that includes scheduling for taking one or more medications and / or an application that notifies a user when a medication is scheduled to be taken) (e.g., scheduled medications and / or on-demand medications).

[0338] In response to detecting a set of one or more inputs corresponding to a request to add the corresponding drug as a drug to be tracked, the computer system displays (904) via a display generation component a user interface (e.g., 656) of the medication tracking application. In some embodiments, displaying the user interface includes displaying a first drug interaction (see, e.g., 656) based on a determination that the corresponding drug has a first drug interaction that meets a first set of criteria (e.g., is a "serious" risk drug interaction and / or a high risk drug interaction). Figure 6X ) (e.g., interactions that alter (e.g., increase or decrease) the effectiveness of the corresponding medication (e.g., interactions with different medications and / or user-defined factors (e.g., alcohol, marijuana, and / or tobacco)) and / or induce (e.g., introduce, increase, and / or decrease) the risk of side effects by taking the corresponding medication), displaying (906) an indication of a first drug interaction (e.g., as shown in the first portion (e.g., 674) of the user interface (e.g., in a first panel and / or first tile). Figure 6XIn some embodiments, displaying the user interface includes displaying a second drug interaction (see, e.g., a notification about a drug interaction and / or information about a drug interaction) based on determining that the corresponding drug has a second drug interaction that meets a second set of criteria that is different from the first set of criteria (e.g., a drug interaction with a "non-serious" risk (e.g., a moderate and / or low risk drug interaction) and / or a risk of no drug interaction). Figure 6X ) (e.g., an indication of a risk of a drug interaction and / or an indication of an absence of a risk of a drug interaction), displaying (908) an indication of a second drug interaction (e.g., as Figure 6X ). In some embodiments, an indication of the second drug interaction is not displayed in the first portion of the user interface (e.g., a "non-serious" risk is not displayed as "serious" in a "serious" risk disk and / or tile). Displaying drug interactions at different locations depending on whether the drug meets different criteria (e.g., the drug interaction is displayed at the top if it is serious and / or at the bottom if it is not serious) provides improved visual feedback to the user because it indicates how the drug interacts with other drugs and / or lifestyle factors (e.g., consuming alcohol and / or tobacco) and will draw the user's attention to specific types of interactions (e.g., serious and / or high risk), which improves visual feedback and / or improves whether the drug should be added or consumed with other drugs of the medication tracking application.

[0339] In some embodiments, the first portion (and / or the indication for the first drug interaction) is separated (e.g., spaced apart) from the second portion (and / or the second drug interaction) by one or more graphical elements (e.g., a palette, tile, and / or affordance) of a user interface (e.g., one or more other scheduled drugs, one or more recorded drugs, an option for recording an on-demand drug, one or more active drugs, an option to initiate adding a drug, and / or an option to initiate archiving a drug). In some embodiments, the first portion (and / or the indication for the first drug interaction) is closer to the scheduled drug portion of the user interface (and / or the user interface area including the one or more scheduled drugs) than the second portion (and / or the indication for the second drug interaction). In some embodiments, the second portion (and / or the indication for the second drug interaction) is located below the graphical element of the one or more active drugs, while the first portion (and / or the indication for the first drug interaction) is located above the graphical element of the one or more active drugs. In some embodiments, the indication for the first drug interaction is positioned above the second drug interaction (and / or the first drug interaction is near the top of the user interface, while the second drug interaction is near the bottom of the user interface). In some embodiments, an indication of a first drug interaction displayed in a first portion of the user interface is not displayed simultaneously with a second drug interaction displayed in a second portion of the user interface (eg, the user must scroll to view the second portion).

[0340] In some embodiments, in response to detecting a set of one or more inputs and based on determining that the corresponding drug has a first drug interaction that satisfies the first set of criteria (e.g., an interaction that alters (e.g., increases or decreases) the effectiveness of the corresponding drug (e.g., an interaction with a different drug and / or a user-defined factor (e.g., alcohol, marijuana, and / or tobacco)) and / or causes (e.g., introduces, increases, and / or decreases) the risk of side effects by taking the corresponding drug), the computer system displays a second indication of the first drug interaction in a second portion (e.g., in addition to the first portion) (e.g., as Figure 6X ) (e.g., a notification about a drug interaction and / or information about a drug interaction). Displaying drug interactions at two locations (e.g., displaying severe drug interactions at both the top and bottom) provides improved visual feedback to the user because it prevents the user from missing specific drug interactions (e.g., severe and / or high risk), which improves visual feedback and / or improves whether the drug should be added or consumed with other drugs of the medication tracking application. Additionally, this provides improved visual feedback that the drug has been added to the medication tracking application, and the action is performed without further user input when a set of conditions are met.

[0341] In some embodiments, the indication for the first drug interaction displayed in the first portion has a first appearance (e.g., Figure 6X In some embodiments, the second indication of the first drug interaction displayed in the second portion has a second appearance that is different from the first appearance (e.g., as depicted in FIG. 1 ). Figure 6X ). Displaying drug interactions in a particular location differently than drug interactions in a different location (e.g., displaying a severe drug interaction at the top versus at the bottom) provides improved visual feedback to the user so that the user does not miss a particular drug interaction (e.g., severe and / or high risk), which improves visual feedback and / or improves whether the drug should be added or consumed with other drugs of the medication tracking application. Additionally, this provides improved visual feedback that the drug has been added to the medication tracking application.

[0342] In some embodiments, the first portion of the user interface includes (e.g., includes only) a list of the most recently added medications (e.g., Figure 6X In some embodiments, the second portion of the user interface includes indications of drug interactions for drugs added before the most recently added drug (e.g., drugs added before the newly added drug or drugs added before the most recently added drug) (e.g., drugs added before the newly added drug or drugs added before the most recently added drug). Figure 6X The second risk tile 676 includes indications of drug interactions for pain relievers, blood pressure medications, cetirizine, and / or sleep aids). Displaying specific drug interactions (e.g., severe and / or high risk) for the most recently added drug in one location and drug interactions for previously added drugs in another location provides improved visual feedback to the user because it draws the user's attention to the drug interactions of the most recently added drug while allowing the user to still view drug interactions for previously added drugs, which improves visual feedback and / or improves whether the drug should be added or consumed with other medications of the medication tracking application. Additionally, this provides improved visual feedback that the drug has been added to the medication tracking application.

[0343] In some embodiments, the second portion of the user interface includes a second indication of drug interactions for the most recently added drug (e.g., Figure 6XDisplaying the specific drug interactions (e.g., severe and / or high risk) of the most recently added drug in two locations provides improved visual feedback to the user because it blocks drug interactions of the most recently added drug while allowing the user to still view drug interactions of previously added drugs, which improves visual feedback and / or improves whether the drug should be added or consumed with other drugs of the medication tracking application.

[0344] In some embodiments, the first portion of the user interface does not include indications of drug interactions for drugs added before the most recently added drug (e.g., Figure 6X Not displaying the drug interactions of previously added drugs in a particular location (e.g., at the top of the user interface) provides improved visual feedback to the user because it does not clutter the user interface, which improves visual feedback and / or human-machine interface.

[0345] In some embodiments, the computer system displays a user interface (e.g., Figure 6X In some embodiments, the computer system displays an indication of a drug interaction (e.g., a first drug interaction and / or a second drug interaction) for the first drug in a user interface (e.g., 674 of the user interface) (e.g., in a first portion of the user interface and / or in a second portion of the user interface). In some embodiments, the first drug is classified as an active drug (e.g., 670b). In some embodiments, in response to detecting a set of one or more inputs (e.g., 650aa, 650ab, and / or 650ac) corresponding to a request to classify the first drug as an inactive drug (e.g., 683b) (e.g., to archive the drug and / or deactivate active tracking of the drug), the computer system classifies the first drug as an inactive drug. In some embodiments, in response to detecting a set of one or more inputs corresponding to a request to classify the first drug as an inactive drug (e.g., to archive the drug and / or deactivate active tracking of the drug), the computer system stops displaying the indication of the drug interaction in the user interface (e.g., the device 600 stops displaying Figure 6X674 in the first risk tile). Not displaying drug interactions for specific drugs that have been deactivated (e.g., archived) provides the user with improved visual feedback of the user input that the drug has been archived and does not clutter the user interface, which improves visual feedback and / or improves the human-computer interface. In some embodiments, when an indication of a first drug interaction is displayed in the first portion, the computer system detects a set of one or more inputs (e.g., 650x1) that scroll the user interface. In some embodiments, in response to detecting a set of one or more inputs that scroll the user interface in a first downward direction (and / or move the first drug interaction and / or other elements upward), the computer system displays an indication of a second drug interaction in the second portion. In some embodiments, the indication of the first drug interaction is not displayed in the second portion simultaneously with the second indication of the second drug interaction. In some embodiments, the indication of the first drug interaction is displayed in the second portion simultaneously with the second indication of the second drug interaction. Displaying a first type of drug interaction (e.g., severe and / or high risk) and then displaying a second type of drug interaction (e.g., non-severe and / or moderate / low risk) provides the user with improved visual feedback of the detected input and prioritizes the order of the first type of drug interactions in the user interface over the second type of drug interactions (e.g., severe drug interactions will be displayed above non-severe drug interactions in the user interface), which improves visual feedback.

[0346] In some embodiments, while an indication of a first drug interaction is displayed in a first portion of the user interface, the computer system detects an input to remove the indication of the first drug interaction in the first portion (e.g., an input pointing to a “remove” affordance 675). In some embodiments, in response to detecting the input to remove the indication of the first drug interaction in the first portion, the computer system stops displaying the indication of the first drug interaction in the first portion. In some embodiments, in response to detecting the input to remove the first indication of the first drug in the first portion, the computer system moves the scheduled drugs (e.g., Fig.11 Removing a first type of drug interaction (e.g., severe and / or high risk) from the user interface in response to user input provides improved visual feedback to the user that the input was detected and does not clutter the user interface, which improves visual feedback and improves the human-machine interface.

[0347] In some embodiments, in response to detecting input to remove the indication of the first drug interaction in the first portion, the computer system maintains display of the indication of the first drug interaction in the second portion (e.g., 676 continues to be displayed in the display after 674 is removed). Figure 6XIn some embodiments, the second portion is always included in the user interface and / or cannot be removed from the user interface. In some embodiments, the first user interface does not include any selectable option to remove the indication of the second drug interaction. Maintaining the display of the second drug interaction in the user interface even if the first drug interaction is removed provides the user with improved visual feedback about the status of the drugs being tracked by the medication tracking application, and maintains the display of risks identified by the computer system that the user should consider when taking a particular medication, which improves visual feedback and improves how the medication tracking application functions.

[0348] In some embodiments, the indication of the second drug interaction corresponds to the second drug. In some embodiments, when the indication of the second drug interaction is displayed in the second portion, the computer system detects a first input corresponding to the indication of the second drug interaction (e.g., 650x3). In some embodiments, in response to detecting the first input corresponding to the indication of the second drug interaction, the computer system displays one or more indications of one or more (e.g., all and / or multiple) drug interactions of a drug different from the second drug (e.g., such as Figure 6Z ) (and optionally, including an indication of the first drug interaction). Displaying additional drug interactions (e.g., all interactions for actively tracked drugs) in response to detecting an input on a particular drug interaction (e.g., non-serious and / or moderate / low risk) provides improved visual feedback to the user that the input was detected, and provides improved visual feedback of how the tracked drugs interact with each other, which improves the visual feedback and improves how the medication tracker application tracks the medications.

[0349] In some embodiments, when an indication of a first drug interaction is displayed in the first portion, the computer system detects an input corresponding to the indication of the first drug interaction (e.g., 650x2). In some embodiments, in response to detecting the input corresponding to the indication of the first drug interaction, the computer system displays information about the drug corresponding to the indication of the first drug interaction (e.g., Figure 6Y ) (and optionally, the computer system forgoes displaying information corresponding to other drug interactions (e.g., a second drug interaction). Displaying information for a single drug interaction in response to detecting an input on a particular drug interaction (e.g., severe and / or high risk) provides improved visual feedback to the user that the input was detected, and provides improved visual feedback and does not clutter the user interface by limiting the amount of information displayed for other types of drug interactions, which improves visual feedback and does not clutter the user interface.

[0350] In some embodiments, displaying a user interface for a medication tracking application includes, based on determining that the corresponding medication has a third drug interaction that satisfies a third set of criteria that is different from the first set of criteria and the second set of criteria (e.g., no risk of drug interaction), displaying an indication that no risk of drug interaction is identified in a third portion of the user interface (e.g., the same as and / or different from the second portion) that is different from the first portion of the user interface (e.g., Figure 6AA 676 in ). Displaying an indication that no risk exists (eg, no risk found) provides the user with improved visual feedback of the status of the medication tracker application (eg, the application is actively checking for drug interactions), which improves the visual feedback.

[0351] In some embodiments, the second set of criteria includes criteria that are met when the first user-selected interaction factor (e.g., lifestyle factor, user-defined activity, and / or non-drug factor) is active (e.g., currently selected; currently applicable to the user). In some embodiments, when the indication of the second drug interaction is displayed in the second portion, the computer system detects a second input corresponding to the indication of the second drug interaction. In some embodiments, in response to detecting the second input corresponding to the indication of the second drug interaction, the computer system displays one or more options (e.g., Figure 6Z An option to display one or more options in a drug interaction user interface that, when selected, results in modification of a user-defined factor reduces the number of inputs to modify lifestyle factors that may trigger an indication of a drug interaction, which reduces the number of inputs required to perform an operation and improves how a medication tracker application tracks drug interactions.

[0352] In some embodiments, the first set of criteria and / or the second set of criteria include criteria that are met when a second user-selected interaction factor (e.g., 652a-652c) (e.g., a lifestyle factor, a user-defined activity, and / or a non-drug factor; a factor that is the same or different from the first user-selected interaction factor) is active. In some embodiments, before displaying a user interface for the medication tracking application, the computer system receives user input (e.g., input at 652a-652c) corresponding to a request to set (e.g., modify) the state of the second user-selected interaction factor. Displaying the indication of a drug interaction based on user-defined factors received prior to displaying the indication improves how the medication tracker application detects potential risks of taking medications based on the user's lifestyle, improving how the medication tracker application tracks drug interactions.

[0353] In some embodiments, the first set of criteria and / or the second set of criteria include criteria that are satisfied when a third user-selected interaction factor (e.g., 652a-652c) (e.g., a lifestyle factor, a user-defined activity, and / or a non-drug factor; a factor that is the same as or different from the first and / or second user-selected interaction factor) is active. In some embodiments, prior to displaying the user interface for the medication tracking application, the computer system receives input corresponding to a request to initiate a process for adding a new medication to the medication tracking application (e.g., 650b at 608, when in communication with Figure 6B In some embodiments, in response to receiving an input corresponding to a request to initiate a process for adding a new medication to the medication tracking application, the computer system initiates a process for adding a new medication to the medication tracking application (e.g., displaying FIG. 6C to FIG. 6V In some embodiments, during a process for adding a new medication to a medication tracking application (e.g., at a predefined point in the process; in response to input received during the process) and based on a determination that the new medication is an initial medication being added to the medication tracking application (e.g., in response to input received during the process), Figure 6B In some embodiments, during a process for adding a new medication to the medication tracking application (e.g., at a predefined point in the process; in response to input received during the process) and based on a determination that the new medication is not an initial medication being added to the medication tracking application (e.g., a first medication and / or the very first medication to be tracked by the medication tracking application), the computer system displays a user interface (e.g., 604v) that includes one or more selectable options (e.g., 652a to 652c) (e.g., an affordance; a text input field) for modifying the state of the interaction factor selected by the third user. In some embodiments, during a process for adding a new medication to the medication tracking application (e.g., at a predefined point in the process; in response to input received during the process) and based on a determination that the new medication is not an initial medication being added to the medication tracking application (e.g., Figure 6B 608 in which the associated medication tracking application is tracking medications and / or the medication tracking application does not include active medications and discontinued medications) (e.g., a second medication or a subsequent medication to be added), the computer system abandons displaying (e.g., continues the process without displaying) a user interface (e.g., in response to 650g, does not display 604v) including one or more selectable options (e.g., affordances; text input fields) for modifying the state of the third user-selected interaction factor (e.g., in reference to FIG. 7A to FIG. 7B Method 700 and Figure 8Appearing a notification to add user-defined factors when a medication is first added to a medication app (where the user-defined factors are used as criteria for determining the risk of subsequent medications) improves how the medication tracker app detects potential risks of taking medications based on the user's lifestyle, which improves how the medication tracker app tracks medication interactions.

[0354] Note that the above description is relative to method 900 (eg, Fig. 9 ) also apply in a similar manner to the methods described below / above. For example, methods 700, 800, 1100, 1300, and / or 1500 optionally include one or more features of the various methods described above with reference to method 900. For example, the process of revealing the risk of drug interaction in method 900 optionally occurs before and / or after methods 700, 800, 900, 1100, 1300, and / or 1500. For another example, the selection made within the user interface described in methods 700, 800, 1100, 1300, and / or 1500 causes the various features of the drug interaction described in method 900 to be displayed. For the sake of simplicity, these details are not repeated below.

[0355] FIG. 10A to FIG. 10N An exemplary user interface for recording medications according to some embodiments is illustrated. Figures 10A to 10N Drugs and Use Recorded in Figures 6A to 6AD The user interface in these figures is used to illustrate the process described below, including Fig.11 process.

[0356] exist Fig. 10A At the tracking interface 656 and Figure 6AD The tracking interface 656 is the same as Fig. 10A , tracking interface 656 includes a record-enabled representation 1010 for a medication arranged in medication tile 668b and a record-enabled representation 1010 for a medication arranged in medication tile 668a. While tracking interface 656 is displayed, device 600 detects input 1050a (e.g., a tap and / or a mouse click) directed to record-enabled representation 1010 of arranged medication tile 668b. In response to detecting input 1050a, device 600 displays the following information: Fig. 10B While displaying tracking interface 656, device 600 (e.g., a digital assistant of device 1400) detects voice input 1051a (e.g., recording the words of medication at 8:00 AM) (e.g., via a microphone). In response to detecting voice input 1051a, device 600 displays the following: Fig. 10BRecording interface 1002a depicted. In some embodiments, device 600 detects voice input 1051a (e.g., recording the utterance of 8:00 a.m. medication) while displaying a user interface other than tracking interface 565. In some embodiments, device 600 detects voice input 1051a (e.g., recording the utterance of 8:00 a.m. medication) while displaying a user interface of a home screen and / or a user interface of an application other than the medication tracker application. In some embodiments, while displaying tracking interface 656 (and / or while displaying a user interface other than tracking interface 656, such as the home screen of device 600 or a user interface of a different application), device 600 detects the utterance recording the 8:00 a.m. medication as taken (and / or skipped). In such embodiments, device 600 records cetirizine and antihypertensive medication (losartan) as taken (and / or skipped) at the current time of the utterance (e.g., 11:00 a.m.). In some embodiments, while displaying tracking interface 656 (and / or while displaying a user interface other than tracking interface 656, such as a home screen or a user interface of a different application), device 600 detects an utterance recording cetirizine as taken and antihypertensive medication (losartan) as skipped (and / or skipped). In such embodiments, device 600 records cetirizine as taken and antihypertensive medication (losartan) as skipped at the current time of the utterance (e.g., 11:00 AM), similar to the reference to FIG. Fig.10F A method was described in which cetirizine was recorded as taken and the antihypertensive medication (losartan) was recorded as skipped.

[0357] exist Fig. 10B At , the recording interface 1002 includes a recording interface for the drug arranged in the drug tile 668b. The recording interface 1002 includes an indication of the recording time of 11:00 based on the current time being 11:00. The recording interface 1002 is based on the user adding the corresponding drug (for example, using Fig.6O The dosage indicator 640e) is configured as a tablet and includes indications of the dosage of both cetirizine and the antihypertensive drug in one tablet.

[0358] exist Fig. 10B At , the recording interface 1002 includes a "mark all medications as taken" enable indication 1004. In some embodiments, in response to detecting the selection of the "mark all medications as taken" enable indication 1004, the device 600 selects a taken enable indication 1006 for cetirizine and a taken enable indication 1006 for antihypertensive drugs. The taken enable indication 1006 can be selected when the user wants to record that the user has taken the medication. The recording interface 1002 also includes skipped enable indications 1008a to 1008b, which can be selected when the user wants to record that the user has not taken the corresponding medication.

[0359] exist Fig. 10B At 1050b1, while displaying recording interface 1002, device 600 detects input 1050b1 (e.g., a tap and / or a mouse click) directed to taken affordance 1006a for cetirizine. In response to detecting input 1050b1, device 600 displays an indication that taken affordance 1006a for cetirizine has been selected, such as Fig. 10C While displaying the recording interface 1002, the device 600 detects an input 1050b2 (e.g., a tap and / or a mouse click) pointing to the skipped enable indication 1008b for the antihypertensive drug. In response to detecting the input 1050b2, the device 600 displays an indication that the skipped enable indication 1008b for the antihypertensive drug has been selected, such as Fig. 10C Depicted.

[0360] exist Fig. 10C At 1050c, while displaying recording interface 1002, device 600 detects input 1050c (e.g., a tap and / or a mouse click) directed to time affordance 1014a. In response to detecting input 1050c, device 600 displays the following Fig. 10D Recording interface 1016 is depicted.

[0361] exist Fig. 10D At , the device 600 has updated the dose from one tablet to two tablets in response to one or more user inputs, as shown in the edit dose enable indication 1018. In addition, the device 600 has updated the indication of the recording time to 9:00 AM in response to one or more user inputs pointing to the time user interface object 1020. The recording interface 1016 includes an "Apply Recording Time" enable indication 1022. Selecting the "Apply Recording Time" enable indication 1022 applies the recording time of 9:00 AM to both cetirizine and antihypertensive drugs. In some embodiments, selecting the "Apply Recording Time" enable indication 1022 only modifies the recording time of the selected drug. In some embodiments, after configuring the recording time of 9:00 AM, the device 600 detects a request to apply the time only to cetirizine (e.g., an input on the "Back" enable indication and / or an enable indication that applies the time only to the corresponding drug). While recording interface 1016 is displayed, device 600 detects input 1050d (e.g., a tap and / or a mouse click) directed to “Apply Recording Time” affordance 1022. In response to detecting input 1050d, device 600 displays the following: Fig.10E Recording interface 1002 is depicted.

[0362] exist Fig.10E At , device 600 updates recording interface 1002 to reflect the recording time of 9:00 a.m. In addition, recording interface 1002 includes completion indicator 1012. Fig.10EThe completion indicator indicates that 1012 is enabled, and Fig. 10B The completion indication 1012 is disabled. The completion indication 1012 is enabled in response to detecting input 1050b1 and / or input 1050b2, such as Fig. 10C as depicted. In some embodiments, only one medication is selected to enable completion enable indication 1012. In some embodiments, all scheduled medications are selected to enable completion enable indication 1012. In some embodiments, completion enable indication 1012 is displayed (e.g., completion enable indication "floats" on the user interface) regardless of (and / or independently of) the device 600 scrolling in a particular direction (e.g., downward) to display off-screen medications that are due (and / or scheduled to be recorded). In some embodiments, completion enable indication 1012 is not initially displayed until the device 600 scrolls in a particular direction to display off-screen medications that are due. While displaying recording interface 1002, device 600 detects input 1050e (e.g., a tap and / or a mouse click) directed to completion enable indication 1012. In response to detecting input 1050e, device 600 displays as shown. Fig.10F Tracking interface 656 is depicted.

[0363] exist Fig.10F At 11:00, the device 600 updates the tracking interface 656 based on recording the cetirizine and antihypertensive medication of the scheduled medication tile 668a. As shown, the tracking interface 656 includes the recorded medication tile 1023a. The recorded medication tile 1023a includes an indication that the recorded time is 9:00 a.m., indicating when the user took the cetirizine and skipped the antihypertensive medication. When the user records the medication at 11:00, the recorded time is 9:00 based on when the user took and / or skipped the corresponding medication. In some embodiments, the recorded medication tile 1023a includes a recorded time corresponding to the time when the medication was originally scheduled to be taken, similar to Fig.14E In such an embodiment, the recorded medication tile 1023a includes an indication that the recording time is 8:00 am.

[0364] exist Fig.10F At, device 600 displays the representation of the drug differently in the recorded drug tile based on how the drug is recorded (e.g., skipped and / or taken). As shown, device 600 displays the text of the drug (cetirizine and antihypertensive drug) differently (e.g., with different visual appearances) based on whether the drug is recorded as taken or skipped. As shown, compared with cetirizine recorded as taken, the antihypertensive drug recorded as skipped is shown in bold and in different fonts. In some embodiments, device 600 displays icons associated with the drug differently based on whether the drug is recorded as taken or skipped.

[0365] exist Fig.10F At 1050f2, recorded medication tile 1023a includes a modification affordance 1026 that, once selected (e.g., in response to input 1050f2), causes device 600 to display recording interface 1002. Thus, modification affordance 1026 allows the user to change the recording time, the recorded dosage, and even modify whether the medication has been taken or skipped.

[0366] exist Fig.10F At , the tracking interface 656 no longer includes the arranged medication tile 668a. Therefore, the arranged medication tile 668b moves upward. Fig.10F The arranged medication tile 668b in Fig. 10A In addition, as shown, device 600 displays recorded medication tile 1023a below scheduled medication tile 668b and below record on-demand medication affordance indication 1024. In this way, tracking interface 656 prioritizes the scheduled medication tile over the recorded tile,...

Claims

1. A method comprising: At a computer system in communication with a display generating component and one or more input devices: Displaying a first user interface via the display generation component, wherein displaying the first user interface comprises: displaying in a first portion of the first user interface a representation of a corresponding medication scheduled to be taken at a scheduled time; detecting, while displaying the first user interface, a first set of one or more inputs corresponding to a request to record an action associated with the respective medication, the first set of one or more inputs comprising at least one detected input; and In response to detecting the first set of one or more inputs corresponding to the request to record an action associated with the corresponding medication, moving the representation of the corresponding medication from the first portion of the first user interface to a second portion of the first user interface that is different from the first portion.

2. The method according to claim 1, further comprising: In response to detecting the first set of one or more inputs corresponding to the request to record the action associated with the respective medication: based on determining that there are no more scheduled medications, replacing the representation of the corresponding medication in the first portion of the first user interface with an indication that there are no more scheduled medications; as well as Based on determining that there is another scheduled medication, the indication that there are no more scheduled medications is abandoned.

3. The method of any one of claims 1 to 2, wherein detecting the first set of one or more inputs comprises detecting a first input corresponding to a selection of an option for initiating a recording action for both a fourth scheduled medication and the corresponding medication, the method further comprising: In response to detecting the input corresponding to the selection of the option for initiating the recording action for both the fourth scheduled medication and the corresponding medication: Displaying a second user interface, wherein the second user interface includes: one or more first recording options for recording a recording action for the fourth scheduled medication; one or more second recording options for recording a recording action for the corresponding medication; and A third recording option for recording a recording action for both the fourth scheduled drug and the corresponding drug.

4. The method according to claim 3, further comprising: while displaying the second user interface, detecting an input corresponding to a request to change a time associated with a recorded action for the corresponding medication; as well as In response to detecting the input corresponding to the request to change the time associated with the recorded action for the corresponding medication, an option is displayed to apply the change of the time associated with the recorded action to the fourth scheduled medication.

5. The method according to claim 3, wherein: The one or more first recording options include an option for modifying a dosage of the fourth scheduled medication and an option for modifying a time associated with a recorded action for the fourth scheduled medication; and The one or more second recording options include an option for modifying a dosage of the corresponding medication and an option for modifying a time associated with a recorded action for the corresponding medication.

6. The method of any one of claims 1 to 2, wherein detecting the first set of one or more inputs comprises detecting a second input, the method further comprising: In response to detecting the second input: An option for modifying a time associated with a recorded action for the respective medication is displayed, wherein the option for modifying the time associated with the recorded action for the respective medication defaults to a current time.

7. The method according to claim 6, further comprising: In response to detecting the second input: An option for modifying a dosage of the corresponding medication is displayed, wherein the option for modifying the dosage of the corresponding medication defaults to a scheduled dosage.

8. The method according to any one of claims 1 to 2, further comprising: displaying the representation of the corresponding medication in the second portion along with an indication of the first time in accordance with determining that the corresponding medication corresponds to a first time associated with a recorded action; as well as Based on determining that a medication different from the corresponding medication corresponds to a second time associated with the recorded action, a representation of the medication is displayed in the second portion along with an indication of the second time, wherein the first time is different from the second time.

9. The method according to claim 8, further comprising: The representation of the corresponding medication is displayed in the second portion together with an option for modifying a recorded action.

10. The method according to any one of claims 1 to 2, further comprising: displaying, in the first user interface, an option for displaying a group of medications; In response to detecting an input corresponding to a selection of the option for displaying a group of medications: Displays an option to record unscheduled medications; and Displays options for recording scheduled medications.

11. The method according to any one of claims 1 to 2, further comprising: Based on determining that all scheduled medications within the first time range have been recorded, displaying a first indication that all of the scheduled medications have been recorded; as well as Based on determining that all scheduled medications within the second time range have been recorded, a second indication different from the first indication is displayed.

12. The method according to any one of claims 1 to 2, wherein the first user interface comprises: a first time period option corresponding to a first time period and which, when selected, causes display of a user interface for recording one or more medication recording actions scheduled to be recorded during the first time period, wherein: the first time period option having a first appearance based on determining that a first set of one or more medication logging criteria has been satisfied, wherein the first set of one or more medication logging criteria includes criteria that are satisfied when at least one medication logging action scheduled to be logged during the first time period has been logged; and Based on determining that the first set of one or more medication record criteria are not met, the first time period option has a second appearance that is different from the first appearance.

13. The method of claim 12, wherein the first set of one or more medication logging criteria includes criteria that are satisfied when no more than one medication has a corresponding logged action within the first time period, and wherein: Based on determining that a third set of one or more medication recording standards have been met, the first time period option has a third appearance that is different from the first appearance and the second appearance, wherein the third set of one or more medication recording standards includes standards that are met when multiple different medications have corresponding recording actions within the first time period.

14. The method of claim 12, wherein the first set of one or more medication logging criteria includes criteria that are satisfied when less than all medication logging actions scheduled to be logged during the first time period have been logged, and wherein: Based on determining that a fourth set of one or more medication recording criteria have been met, the first time period option has a fourth appearance that is different from the first appearance and the second appearance, wherein the fourth set of one or more medication recording criteria includes criteria that are met when all medication recording actions scheduled to be recorded during the first time period have been recorded.

15. The method of claim 12, wherein the first set of one or more medication logging criteria comprises criteria that are satisfied when a medication logging action has been logged for a first medication scheduled to be logged during the first time period, wherein: Based on determining that a fifth set of one or more medication recording criteria have been met, the first time period option has a fifth appearance that is different from the first appearance and the second appearance, wherein the fifth set of one or more medication recording criteria includes criteria that are met when a medication recording action for a second medication scheduled to be recorded during the first time period has been recorded, wherein the second medication is different from the first medication.

16. The method according to any one of claims 1 to 2, wherein the representation of the corresponding drug is displayed in the second portion with a corresponding appearance, wherein: Based on determining that the corresponding medication is associated with a first type of recorded action, the corresponding appearance is a sixth appearance; and Based on determining that the corresponding medication is associated with a second type of recorded action, the corresponding appearance includes a seventh appearance different from the sixth appearance.

17. The method according to any one of claims 1 to 2, further comprising: When the representation of the corresponding medication is displayed in the first portion of the first user interface, an indication is displayed in a third portion of the first user interface that the corresponding medication is an actively tracked medication.

18. The method according to any one of claims 1 to 2, further comprising: while displaying the first user interface, detecting an input corresponding to a request to initiate deactivation of one or more active medications; as well as In response to detecting the input corresponding to the request to initiate deactivation of one or more active medications, displaying a fourth user interface, the fourth user interface comprising: an active medication having an option for deactivating the active medication; and A deactivated medication having an option for activating the deactivated medication.

19. The method according to any one of claims 1 to 2, further comprising: displaying in the first user interface an indication that no medication is recorded; as well as In response to detecting the first set of one or more inputs corresponding to the request to record an action associated with the respective medication: Stop displaying the indication that no medication is recorded.

20. The method according to any one of claims 1 to 2, further comprising: After moving the representation of the corresponding medication and based on determining that a predetermined period of time has elapsed, ceasing to display the corresponding medication in the second portion of the first user interface.

21. The method of any one of claims 1 to 2, wherein the first set of one or more inputs corresponding to the request to record the action associated with the respective medication comprises at least one voice input.

22. The method according to any one of claims 1 to 2, further comprising: displaying a second user interface via the display generation component; detecting, via the one or more input devices, a second set of one or more inputs corresponding to a request to record an action associated with a second corresponding medication while displaying the second user interface, the second set of one or more inputs including at least one detected voice input; as well as In response to detecting the second set of one or more inputs, the action associated with the second corresponding medication is recorded.

23. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system configured to communicate with a display generation component and one or more input devices, the computer-readable storage medium comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 22.

24. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 22.

25. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Memory; and A component for carrying out the method according to any one of claims 1 to 22.

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

Images