Communication and user interface control in user activity monitoring systems

Abstract

In some aspects, a non-transitory computer-readable medium is disclosed, the non-transitory computer-readable medium having an application stored thereon, the application, when executed by a processor of an electronic device, causing the processor to perform a process. The process may include receiving motion data from a motion sensor, the motion data indicating motion of a user while wearing the motion sensor. The process may also include: transmitting the motion data to a server; receiving from the server the motion data indicating a time when the user's foot experienced a load force, the load force having a risk of adversely affecting an existing foot ulcer or causing a new foot ulcer; determining a geographic location of the motion sensor at the time when the foot experienced the load force; displaying the time and the geographic location; and requesting the user to identify an activity in which the user participated at the time and the geographic location.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to UK provisional application numbers 1906090.4, 1906092.0, 1906095.3 and 1906097.9 filed on May 1, 2019, the disclosures of which are hereby incorporated by reference in their entirety. Technical Field

[0003] Embodiments of the present disclosure relate to apparatus, systems, and methods for managing communications between a user activity monitoring device and other devices. Background Art

[0004] Pressure ulcers, which may also be called pressure sores, bedsores or decubitus ulcers, are damage to the skin and underlying tissues caused by pressure on the skin, soft tissue, muscle or bone that is chronically above the capillary filling pressure (approximately 32 mmHg).

[0005] One type of pressure ulcer that forms on the foot is called a diabetic foot ulcer (DFU), which tends to occur with greater frequency and intensity in the diabetic population. The management and treatment of diabetic foot ulcers requires offloading of the diabetic foot ulcer through the use of cushioned footwear (e.g., supportive boots, casts, shoes, etc.). While offloading can be effective, it has been found that noncompliance or failure to use offloading devices can play a significant role in delayed healing of diabetic foot ulcers.

[0006] Prior art methods and systems provide little or no information about an individual's lifestyle and compliance with unloading devices. Insights into an individual's lifestyle may be important in preventing and healing pressure ulcers. However, due to these limitations, prevention and healing of pressure ulcers using prior art methods and systems may be delayed or worse, worsen, leading to prolonged discomfort, hospitalization, or even surgery. Summary of the invention

[0007] In some aspects, a non-transitory computer-readable medium is disclosed, the non-transitory computer-readable medium having an application stored thereon, the application, when executed by a processor of an electronic device, causing the processor to perform a process. The process may include: receiving, by a communication interface, motion data from a motion sensor, the motion data indicating motion of a user while wearing the motion sensor; determining a time to request contextual information of the motion data from the user; disabling a function of the application before the time; enabling a function of the application after the time; and requesting the contextual information from the user at the time.

[0008] The non-transitory computer-readable medium of the previous paragraph may include one or more of the following features: the context information may be received from the user before the time and after the time. The context information may include an identification of the type of activity the user engages in while wearing the motion sensor. The disabling may include disabling the function by preventing the user from accessing the function before the time. The function may include the ability of the user to provide input in response to multiple prompts. The context information may be requested from the user via a touch screen. The process may include transmitting motion data to a server via a computer network, and receiving the motion data from the motion sensor when the communication interface is no more than 100 meters away from the motion sensor. The computer network may be a cellular network. The motion sensor may include an accelerometer and a magnetometer, and the motion data may include sensor data from the accelerometer and the magnetometer.

[0009] In some aspects, a method for collecting motion data from a motion sensor and controlling user interaction with an application that processes the motion data is disclosed. The method may include: under the control of a processor executing an application: receiving motion data from the motion sensor by a communication interface, the motion data indicating the motion of the user while wearing the motion sensor; determining a time to request context information of the motion data from the user; disabling a function of the application before the time; enabling the function of the application after the time; and requesting the context information from the user at the time.

[0010] The method of the previous paragraph may include one or more of the following features: The method may include receiving the contextual information from the user before the time and after the time. The contextual information may include identification of the type of activity the user engages in while wearing the motion sensor. The disabling may include preventing the user from accessing the function before the time. The function may include the ability of the user to provide input in response to multiple prompts. The contextual information may be requested and received from the user using a touch screen. The method may include transmitting the motion data to a server via a computer network, and receiving the motion data from the motion sensor when the communication interface is no more than 100 meters away from the motion sensor. The computer network may be a cellular network. The motion sensor may include an accelerometer and a magnetometer, and the motion data may include sensor data from the accelerometer and the magnetometer.

[0011] In some aspects, a device for collecting motion data from a motion sensor and controlling user interaction with an application that processes the motion data is disclosed. The device may include: a communication interface configured to communicate with the motion sensor; and a processor configured to execute an application to: receive motion data from the motion sensor, the motion data indicating a user's motion while wearing the motion sensor, determine a time to request context information of the motion data from the user, disable a function of the application before the time, enable a function of the application after the time, and request the context information from the user at the time.

[0012] The device of the previous paragraph may include one or more of the following features: The device may include: a housing supporting a communication interface and the processor; a display configured to request the context information from the user; or a user input configured to receive the context information from the user. A system may include the device and the motion sensor or server, the processor configured to transmit the motion data to the server via the communication interface.

[0013] In some aspects, a non-transitory computer-readable medium is disclosed, the non-transitory computer-readable medium having an application stored thereon, the application, when executed by a processor of an electronic device, causing the processor to perform a process. The process may include: receiving motion data from a motion sensor by a communication interface, the motion data indicating motion of a user while wearing the motion sensor; requesting and receiving contextual information for the motion data from the user; determining an interaction metric for the user from the contextual information, the interaction metric indicating an amount of interaction of the user with the application; and adjusting a graphical user interface of the application for presentation to the user in response to the interaction metric.

[0014] The non-transitory computer-readable medium of the preceding paragraph may include one or more of the following features: The context information may include an identification of an activity in which the user engages while wearing the motion sensor or an indication of how the user feels. The determining may include determining the interaction metric from a count of the number of days that the user provides the context information. The adjusting may include adjusting the graphical user interface differently if the count meets a threshold than if the count does not meet the threshold. The determining may include determining the interaction metric from the number of consecutive days that the user provides the context information. The adjusting may include adjusting the graphical user interface by presenting user feedback selected from a set of first feedback options instead of a set of second feedback options, the set of first feedback options being different from the set of second feedback options. The adjusting may include adjusting the graphical user interface by changing the format of information included in the graphical user interface. The adjusting may include adjusting the graphical user interface by incorporating a first image into the graphical user interface instead of a second image, the first image being different from the second image. The context information may be requested and received from the user via a touch screen. The process may include: assigning a badge from a plurality of badges to a user based on at least a number of goals set by the user or a number of goals completed by the user; and incorporating the badge into the graphical user interface. The process may include transmitting the motion data to a server via a computer network, and receiving the motion data from the motion sensor when the communication interface is no more than 100 meters from the motion sensor. The computer network may be a cellular network. The motion sensor may include an accelerometer and a magnetometer, and the motion data may include sensor data from the accelerometer and the magnetometer.

[0015] In some aspects, a method for collecting motion data from a motion sensor and processing context information associated with the motion data is disclosed. The method may include: under the control of a processor executing an application: receiving motion data from the motion sensor by a communication interface, the motion data indicating the motion of a user while wearing the motion sensor; requesting and receiving context information for the motion data from the user; determining an interaction metric for the user from the context information, the interaction metric indicating an amount of interaction of the user with the application; and adjusting a graphical user interface of the application in response to the interaction metric, the graphical user interface generated by the processor for presentation to the user.

[0016] The method of the preceding paragraph may include one or more of the following features: The context information may include identification of an activity in which the user engages while wearing the motion sensor or an indication of how the user feels. The determining may include determining the interaction metric from a count of the number of days that the user provides the context information. The adjusting may include adjusting the graphical user interface by presenting user feedback selected from a set of first feedback options instead of a set of second feedback options, the set of first feedback options being different from the set of second feedback options. The adjusting may include adjusting the graphical user interface by changing the format of information included in the graphical user interface or by incorporating a first image instead of a second image into the graphical user interface, the first image being different from the second image. The context information may be requested and received from the user using a touch screen. The method may include transmitting the motion data to a server via a computer network, receiving the motion data from the motion sensor when the communication interface is no more than 100 meters from the motion sensor. The motion sensor may include an accelerometer and a magnetometer, and the motion data may include sensor data from the accelerometer and the magnetometer.

[0017] In some aspects, a device for collecting motion data from a motion sensor and processing contextual information associated with the motion data is disclosed. The device may include: a communication interface configured to communicate with the motion sensor; and a processor configured to execute an application to: receive motion data from the motion sensor, the motion data indicating the motion of a user while wearing the motion sensor, request and receive contextual information for the motion data from the user, determine an interaction metric for the user from the contextual information, the interaction metric indicating the amount of interaction of the user with the application, and in response to the interaction metric, adjust a graphical user interface of the application, the graphical user interface generated by the processor for presentation to the user.

[0018] The device of the previous paragraph may include one or more of the following features: the device may include a housing supporting the communication interface and the processor, a display configured to request the context information from the user and present the graphical user interface, or a user input configured to receive the context information from the user. A system may include the device and the motion sensor or server, the processor configured to transmit the motion data to the server via the communication interface.

[0019] In some aspects, a non-transitory computer-readable medium is disclosed, the non-transitory computer-readable medium having an application stored thereon, the application, when executed by a processor of an electronic device, causing the processor to perform a process. The process may include: receiving, by a communication interface, motion data from a motion sensor, the motion data indicating motion of a user while wearing the motion sensor; transmitting, by the communication interface, the motion data to a server; receiving, by the communication interface, from the server the motion data indicating a time when the user's foot experienced a load force that had a risk of adversely affecting an existing ulcer on the foot or of causing a new ulcer on the foot; determining a geographic location of the motion sensor at the time when the foot experienced the load force; displaying the time and the geographic location to the user on a display; requesting, on the display, the user to identify an activity in which the user participated at the time and the geographic location; and transmitting the activity to the server for storage to a memory device in association with the time and the geographic location.

[0020] The non-transitory computer-readable medium of the preceding paragraph may include one or more of the following features: when the communication interface is no more than 100 meters from the motion sensor, the motion data may be received from the motion sensor, and the motion data may be transmitted to the server via a computer network. The computer network may be a cellular network. The motion sensor may include an accelerometer and a magnetometer, and the motion data may include sensor data from the accelerometer and the magnetometer. The determining may include determining the geographic location from the physical location of the processor at the time. The determining may include determining the physical location using a global positioning system (GPS) receiver or communications received via a computer network. The display may include displaying the time and the geographic location together on the display. The time may indicate when the foot is experiencing a load force that is at risk of adversely affecting an existing ulcer, and when the user is determined to not be wearing a load-reducing device, based at least on the motion data. The activity may include a transportation type, an exercise type, a leisure type, a home activity type, or a work type. The process may include requesting the user to identify the activity from a plurality of different activity types that the user previously indicated as activity types that the user typically engages in.

[0021] In some aspects, a method for collecting motion data from a motion sensor and processing event information associated with the motion data is disclosed. The method may include: receiving motion data from a motion sensor by a communication interface, the motion data indicating the motion of a user while wearing the motion sensor; transmitting the motion data to a server by the communication interface; receiving the motion data from the server by the communication interface indicating a time when the user's foot experienced a load force that had a risk of adversely affecting an existing ulcer on the foot or a risk of causing a new ulcer on the foot; determining, by a processor, the geographic location of the motion sensor at the time when the foot experienced the load force; displaying the time and the geographic location to the user on a display; requesting the user on the display to identify an activity in which the user participated at the time and the geographic location; and transmitting the activity to the server for storage in a memory device in association with the time and the geographic location.

[0022] The method of the preceding paragraph may include one or more of the following features: when the communication interface is no more than 100 meters from the motion sensor, the motion data may be received from the motion sensor, and the motion data may be transmitted to the server via a computer network. The computer network may be a cellular network. The motion sensor may include an accelerometer and a magnetometer, and the motion data may include sensor data from the accelerometer and the magnetometer. The determining may include determining the geographic location from a physical location of the processor at the time. The determining may include determining the physical location using a global positioning system (GPS) receiver or communications received via a computer network. The time may indicate when the foot experienced a load force that was at risk of adversely affecting an existing ulcer based at least on the motion data. The method may include receiving the activity from the user via user input. The activity may include a transportation type, an exercise type, a leisure type, a hobby type, or a work type. The request may include requesting the user to identify the activity from a plurality of different activity types that the user previously indicated as activity types that the user typically engages in.

[0023] In some aspects, an apparatus for collecting motion data from a motion sensor and processing event information associated with the motion data is disclosed. The apparatus may include: a communication interface configured to communicate with a motion sensor and a server; and a processor configured to: receive motion data from the motion sensor, the motion data indicating the motion of a user while wearing the motion sensor, transmit the motion data to the server, receive the motion data from the server indicating a time when the user's foot experienced a load force that had a risk of adversely affecting an existing ulcer on the foot or of causing a new ulcer on the foot, determine a geographic location of the motion sensor at the time when the foot experienced the load force, output the time and the geographic location for presentation to the user, request the user to identify an activity in which the user participated at the time and the geographic location, and transmit the activity to the server for storage in association with the time and the geographic location to a memory device.

[0024] The device of the previous paragraph may include one or more of the following features: the device may include a housing supporting the communication interface and the processor, a display configured to present the time and the geographic location, or configured to receive user input of the activity from the user. A system may include the device and the motion sensor or the server.

[0025] In some aspects, a non-transitory computer-readable medium is disclosed, the non-transitory computer-readable medium having an application stored thereon, the application, when executed by a processor of an electronic device, causing the processor to perform a process. The process may include: requesting behavioral data from the server via a communication interface, the behavioral data indicating (i) a duration of a user's foot activity and (ii) a duration of the user's use of a load-reducing device, the behavioral data being determined from motion data collected by a first motion sensor worn by the user and load-reducing device use data collected from a second motion sensor supported by the load-reducing device; generating a first user interface, the first user interface including a first value responsive to the duration of the foot activity and a second value responsive to the duration of the user's use of the load-reducing device; and displaying the first user interface on a display.

[0026] The non-transitory computer-readable medium of the preceding paragraph may include one or more of the following features: the process may include generating a second user interface that allows selection of individual users of a plurality of users for which the motion data and the unloading device usage data have been collected, the plurality of users including the user; and the process may include transitioning from displaying the second user interface on a display to displaying the first user interface in response to a user input. The process may include displaying the first user interface on a display instead of the second user interface in response to the user input. The first user interface may include a third value that indicates a difference between a duration of the foot activity and a duration of the user using the unloading device. The first user interface may identify the third value as corresponding to a period of time during which the foot is at risk of injury. The first user interface may include a target time period during which the foot should be active, and the process may include setting the target time period in response to the user input. The process may include receiving a plurality of activity types from the server, the plurality of activity types being identified as types of activities in which the user is engaged in which the foot is at risk of injury, and the first user interface may identify the plurality of activity types. The first user interface may identify a plurality of durations corresponding to the plurality of activity types, the plurality of durations indicating a length of time during which the foot is at risk of injury during engagement in the type of activity. The first user interface may identify a plurality of unloading device utilization rates corresponding to the plurality of activity types, the plurality of unloading device utilization rates indicating a portion of time during participation in the type of activity when the user did not use the unloading device, the foot was at risk of injury. When the user selects one of the activity types, the first user interface may present at least one of: (i) a number of events during the selected one of the activity types in which the user participated in the unloading device at risk of injury, (ii) an average time during the selected one of the activity types during which the user's foot was at risk of injury, (iii) a number of foot collisions during the selected one of the activity types, or (iv) a portion of time during participation in the activity type when the user did not use the unloading device. The process may include generating a second user interface, the second user interface identifying a duration of the foot activity during individual ones of the plurality of time periods and a duration of use of the unloading device by the user during individual ones of the plurality of time periods; and the process may include displaying the second user interface on the display. The computer network may be a cellular network. The motion data may include sensor data from an accelerometer and a magnetometer of the first motion sensor.

[0027] In some aspects, a method for processing motion data collected by a motion sensor is disclosed. The method may include: under the control of a processor executing an application: requesting behavior data from a server via a communication interface, the behavior data indicating (i) the duration of a user's foot activity and (ii) the duration of the user's use of a load-reducing device, the behavior data being determined from motion data collected by a first motion sensor worn by the user and load-reducing device use data collected from a second motion sensor positioned on the load-reducing device; generating, by the processor, a first user interface, the first user interface including a first value responsive to the duration of the foot activity and a second value responsive to the duration of the user's use of the load-reducing device; and displaying the first user interface on a display.

[0028] The method of the preceding paragraph may include one or more of the following features: the method may include generating, by the processor, a second user interface, the second user interface allowing selection of individual users of a plurality of users for which the motion data and the unloading device usage data have been collected, the plurality of users including the user; and the method may include transitioning from displaying the second user interface on the display to displaying the first user interface in response to user input. The first user interface may include a third value responsive to a comparison of the duration of the foot activity and the duration of the user using the unloading device, or the first user interface may identify the third value as corresponding to a time period during which the foot is at risk of injury. The method may include receiving, via the communication interface, from the server a plurality of activity types, the plurality of activity types being identified as types of activities in which the foot is at risk of injury by the user, and the first user interface may identify the plurality of activity types. The first user interface may identify a plurality of durations corresponding to the plurality of activity types, the plurality of durations indicating a length of time during which the foot is at risk of injury during participation in the types of activities. The first user interface may identify a plurality of unloading device utilization rates corresponding to the plurality of activity types, the plurality of unloading device utilization rates indicating a portion of time during participation in the types of activities when the user is not using the unloading device when the foot is at risk of injury. When the user selects one of the activity types, the first user interface may present at least one of: (i) the number of events in which the user engaged in the selected one of the activity types in which the foot was at risk of injury, (ii) the average time the user's foot was at risk of injury during the selected one of the activity types, (iii) the number of foot collisions during the user's participation in the selected one of the activity types, or (iv) the portion of time the foot was at risk of injury during the participation in the activity type when the user was not using the unloading device. The method may include generating a second user interface that identifies the duration of the foot activity during individual time periods in a plurality of time periods and the duration of the user's use of the unloading device during individual time periods in a plurality of time periods; and the method may include displaying the second user interface on the display.

[0029] In some aspects, a device for processing motion data collected by a motion sensor is disclosed. The device may include: a communication interface configured to communicate with a server via a computer network; and a processor configured to execute an application to: request behavior data from the server, the behavior data indicating (i) the duration of a user's foot activity and (ii) the duration of the user's use of a load-reducing device, the behavior data being determined from motion data collected by a first motion sensor worn by the user and load-reducing device use data collected from a second motion sensor supported by the load-reducing device; generate a first user interface for presentation, the first user interface including a first value responsive to the duration of the foot activity and a second value responsive to the duration of the user's use of the load-reducing device; and output the first user interface.

[0030] The device of the previous paragraph may include one or more of the following features: the device may include a housing supporting the communication interface and the processor, a display configured to present the first user interface, or a user input configured to receive user input from the user. A system may include the device and the first motion sensor, the second motion sensor, or the server. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Embodiments of the present disclosure will now be described hereinafter, by way of example only, with reference to the accompanying drawings, in which:

[0032] Figure 1 An example user activity monitoring system including an activity monitoring device and an offload monitoring device is shown;

[0033] Figure 2 Shows Figure 1 Example components of an activity monitoring device;

[0034] Figure 3 Shown include Figure 1 Example computing environments for activity monitoring devices and load reduction monitoring devices;

[0035] Figure 4 It shows that Figure 3 An example functional locking process implemented in a computing environment of;

[0036] Figure 5 It shows that Figure 3 An example activity recognition process implemented in a computing environment;

[0037] Figure 6 It shows that Figure 3 An example interface control process implemented in a computing environment of;

[0038] Fig. 7A It shows that Figure 3 An example welcome interface presented in a computing environment of FIG.

[0039] Figure 7B It shows that Figure 3 An example configuration interface presented in a computing environment of FIG.

[0040] Figure 7C It shows that Figure 3 An introductory interface presented in a computing environment;

[0041] Fig.7D It shows that Figure 3 An example travel type interface presented in a computing environment of FIG.

[0042] Fig. 7E It shows that Figure 3 An example exercise type interface presented in a computing environment of;

[0043] Figure 7F It shows that Figure 3 An example user target interface presented in a computing environment of;

[0044] Figure 7G It shows that Figure 3 An example sign-in settings interface presented in a computing environment of ;

[0045] Figure 7H It shows that Figure 3 An example role selection interface presented in a computing environment of FIG.

[0046] Fig. 8A It shows that Figure 3 An example check-in status interface presented in a computing environment of FIG.

[0047] Figure 8B It shows that Figure 3 An example event status interface presented in a computing environment of;

[0048] Figure 8C It shows that Figure 3 An example tag log launch interface presented in a computing environment;

[0049] Fig.8D It shows that Figure 3 An example health and wellness feedback interface presented in a computing environment;

[0050] Fig. 8E It shows that Figure 3 An example foot health feedback interface presented in a computing environment;

[0051] Fig.8F It shows that Figure 3 An example observation user interface presented in a computing environment of;

[0052] Figure 8G It shows that Figure 3 An example goal completion interface presented in a computing environment of FIG.

[0053] Figure 8H It shows that Figure 3 An example unlabeled event summary interface presented in a computing environment of ;

[0054] Fig.8I It shows that Figure 3 An example geolocation interface presented in a computing environment of;

[0055] Figure 8J It shows that Figure 3 An example activity input interface presented in a computing environment of FIG.

[0056] Figure 8K It shows that Figure 3 An event summary interface presented in a computing environment;

[0057] Figure 8L It shows that Figure 3 An event confirmation interface presented in a computing environment;

[0058] Fig.9A It shows that Figure 3 An example user summary interface presented in a computing environment of;

[0059] Fig. 9B It shows that Figure 3 An example home interface presented in a computing environment of FIG.

[0060] Fig. 9C It shows that Figure 3 An example reservation interface presented in a computing environment of;

[0061] Fig.9D It shows that Figure 3 An example foot activity target interface presented in a computing environment;

[0062] Fig. 10A , Fig. 10B , Fig. 10C , Fig. 10D and Fig.10E It shows that Figure 3 An example achievement summary interface presented in a computing environment of;

[0063] Fig.11A It shows that Figure 3 An example clinician login interface presented in a computing environment of FIG.

[0064] Fig. 11B It shows that Figure 3 An example authentication interface presented in a computing environment of;

[0065] Fig. 12A It shows that Figure 3 An example panel interface presented in a computing environment;

[0066] Fig. 12B It shows that Figure 3 An example personal user interface presented in a computing environment of;

[0067] Fig. 12C It shows that Figure 3 An example personal user interface presented in a computing environment of;

[0068] Fig.12D It shows that Figure 3 An example cooking report interface presented in a computing environment of;

[0069] Fig.12E It shows that Figure 3 An example personal user interface presented in a computing environment of;

[0070] Fig.12F It shows that Figure 3 An example daily bar chart summary presented in a computing environment;

[0071] Figure 12G It shows that Figure 3 Another example personal user interface presented in a computing environment of; and

[0072] Fig.13 Shows the available Figure 3 An example computer system for implementing one or more devices or systems within a computing environment. DETAILED DESCRIPTION

[0073] Introduction to User Activity Monitoring

[0074] For various reasons, including wound prevention and monitoring, the user's activity may be desirably monitored by an activity monitoring device. In one example, the user's activity may be monitored when the user may be susceptible to injury or already has an injury (e.g., a pressure ulcer). Information about the user's activity collected by the activity monitoring device may help aid in the prevention or treatment of pressure ulcers. Additionally, information about activity collected by the activity monitoring device may be used to check compliance with a treatment regimen.

[0075] Some aspects disclosed herein relate to wound monitoring or treatment for human or animal bodies. Therefore, any reference to wounds herein may refer to wounds on human or animal bodies, and any reference to body herein may refer to human or animal bodies. The disclosed technology may relate to preventing or minimizing damage to physiological or living tissues, or to the treatment of damaged tissues (e.g., wounds described herein).

[0076] As used herein, the expression "wound" may include damage to living tissue that may be caused by cutting, hitting or other impact, typically damage to the skin that is cut or broken. Wounds may be chronic or acute injuries. Acute wounds are caused by surgery or trauma. They go through several healing stages within a predicted time frame. Chronic wounds usually begin as acute wounds. When acute wounds do not follow the healing stages, acute wounds can become chronic wounds, resulting in prolonged recovery. It is believed that the transition from acute wounds to chronic wounds may be due to the patient's compromised immunity.

[0077] Chronic wounds may include, for example: venous ulcers (such as those arising in the legs), which account for the majority of chronic wounds and primarily affect the elderly; diabetic ulcers (e.g., foot or ankle ulcers); peripheral arterial disease; pressure ulcers or epidermolysis bullosa (EB).

[0078] Examples of other wounds include, but are not limited to, abdominal wounds or other large or open wounds resulting from surgery, trauma, sternotomy, fasciotomy, or other conditions, dehisced wounds, acute wounds, chronic wounds, subacute and dehisced wounds, traumatic wounds, flaps and skin grafts, lacerations, abrasions, contusions, burns, diabetic ulcers, pressure ulcers, stomas, surgical wounds, traumatic ulcers, and venous ulcers.

[0079] The wound may include deep tissue injury. Deep tissue injury is a term proposed by the National Pressure Ulcer Advisory Panel (NUPAP) to describe a unique form of pressure ulcer. These ulcers have been described by clinicians for many years using terms such as purple pressure sores, ulcers that may worsen, and bruises on bony prominences.

[0080] Wounds may also include tissue that is at risk of becoming a wound as discussed herein. For example, tissue at risk may include tissue on a bony prominence (at risk of deep tissue injury / damage) or pre-operative tissue (e.g., knee tissue) that may be cut (e.g., for joint replacement / surgical alteration / reconstruction).

[0081] Some aspects relate to methods of monitoring or treating wounds using the techniques disclosed herein in combination with one or more of the following: advanced footwear, turning the patient, cleaning (e.g., cleaning diabetic foot ulcers), treating infection, system integration, antimicrobial, antibiotics, surgery, removing tissue, affecting blood flow, physiotherapy, exercise, bathing, nutrition, hydration, nerve stimulation, ultrasound, electrical stimulation, oxygen therapy, microwave therapy, active ozone, antibiotics, antimicrobial agents, etc.

[0082] Alternatively or additionally, the wound may be treated using topical negative pressure or conventional advanced wound care that is not assisted by the use of applied negative pressure (also referred to as non-negative pressure therapy).

[0083] Although the present disclosure may refer to pressure sores, foot ulcers, etc., the systems and methods disclosed herein may be used to prevent, monitor, or treat any type of skin injury or wound, such as a venous leg ulcer.

[0084] User activity monitoring system

[0085] Figure 1 A user activity monitoring system 100 is shown including an activity monitoring device 120 attached to a body part 110. The activity monitoring device 120 may be attached to the body part 110 using a strap, adhesive, or other coupling mechanism, and may be worn on or supported by the body.

[0086] Body part 110 may be a user's leg, including a knee 112 and a foot 114. As shown, activity monitoring device 120 may be supported by body part 110 at a position between knee 112 and foot 114, such as near knee 112. In other aspects, activity monitoring device 120 may be supported by another portion of body part 110, such as above knee 112 or elsewhere. Activity monitoring device 120 may monitor and record the activity of body part 110 (e.g., walking, jumping, sitting, lying down, running, squatting, or standing), for example, from the position, movement, or orientation of one or more other sensors of activity monitoring device 120 or activity monitoring device 120. Activity monitoring device 120 may be used, for example, to load monitor the load of foot 114. In some embodiments, multiple body parts may be monitored by activity monitoring device 120, and different sensors may be used to monitor different body parts.

[0087] A body part 110 is shown wearing and partially covered by a load relief device 130. The load relief device 130 can support the body part 110 and reduce pressure on the foot 114 when the user may be standing or engaging in other activities. A load relief monitoring device 132 can be attached to the load relief device 130. The load relief monitoring device 132 can be the same as or similar to the activity monitoring device 120 and monitors and records the activity of the load relief device 130. The load relief monitoring device 132 can be supported by the load relief device 130 using straps, adhesives, or other attachment mechanisms. The load relief monitoring device 132 can be attached to an inner surface or an outer surface of the load relief device 130. Although Figure 1 , but the unloading monitoring device 132 can be attached to an unloading device (e.g., a cane or a walker) that is not worn by the user. In addition, the activity monitoring device 120 can be worn regardless of whether the unloading device 130 can be worn.

[0088] The user activity monitoring system 100 may additionally or alternatively include one or more of the activity monitoring device 120 or the unloading monitoring device 132 at other locations (e.g., at a location supported by the unloading device 130, another part of the body part 110, another device not worn, such as a cane or a walker, or other locations). One or more additional or alternatives of the activity monitoring device 120 or the unloading monitoring device 132 may be the same as or similar to the activity monitoring device 120 and may monitor and record the activity of the unloading device 130, another part of the body part 110, or the body.

[0089] Figure 2 Example components of an activity monitoring device 120 are shown. The activity monitoring device 120 may include a housing 200, a controller 202 configured to be in, for example, electrical communication with one another, a memory device 204, a user interface 206, a power source 208, one or more sensors 210, and a communication interface 212. The power source 208 may provide power to one or more components of the activity monitoring device 120.

[0090] One or more components of the activity monitoring device 120 may be contained in or supported by the housing 200. The housing 200 may be comprised of a top portion and a bottom portion that are sealed together, and the top portion or the bottom portion may be hard or soft. The housing 200 may be flexible and have mechanical structures and design features that provide shoulder pin keyway alignment of the components within the housing 200. The housing 200 may support a circuit board within it, and one or more components of the activity monitoring device 120 may be positioned on the circuit board.

[0091] The housing 200 can be prepared by stereolithography (SLA) or polymer jetting of photopolymer 3D printing materials or by 3D printing of engineering resins with a Shore hardness of 80A. The housing 200 may include an elastomer, a thermoplastic elastomer, or be constructed by injection molding. The molded portion of the housing 200 may be made of white liquid silicone rubber. Adhesives (e.g., adhesives for attaching plastic and elastomeric materials) can be used to glue the top and bottom portions of the housing 200 together, and a wide range of other adhesives (e.g., cyanoacrylate, silicone, epoxy, hydrogel, hydrocolloid, sealant system) or other techniques (e.g., using double-sided adhesive tape, ultrasonic welding, riveting) can be used.

[0092] Controller 202 may control the operation of one or more other components of activity monitoring device 120 (e.g., memory device 204, user interface 206, power source 208, one or more sensors 210, or communication interface 212) based at least on instructions stored in memory device 204. Controller 202 may, for example, control monitoring of loading of body weight on body part 110 or positioning of body part 110 and record data indicative of loading of body part 110 or positioning of body part 110 to memory device 204.

[0093] The user interface 206 may include one or more output elements, such as a visual feedback device (e.g., a light emitting diode), a tactile feedback device, or an audio device (e.g., a speaker) that provides user output to the user. The one or more output elements may convey status information to the user, such as whether the activity monitoring device 120 is operating successfully or has been successfully configured to communicate with another device. The user interface 206 may include one or more input elements, such as buttons, switches, dials, touch pads, microphones, or touch screens, for receiving user input for configuring the activity monitoring device 120. In some aspects, the user interface 206 may have no more than one user input element (e.g., a button) for receiving user input to activate and deactivate the activity monitoring device 120 or to perform one or more other functions.

[0094] One or more sensors 210 may be used to detect and monitor movement of activity monitoring device 120 or other characteristics of or around activity monitoring device 120. One or more sensors 210 may be used to detect and monitor activity of a user of activity monitoring device 120, including, for example, load or positioning of body part 110. One or more sensors 210 may include one or more accelerometers, gyroscopes, magnetometers, impedance sensors, thermistors, pressure sensors, or optical sensors, among other types of sensors. One or more sensors 210 may be positioned proximate to body part 110, or may be remote from body part 110 but may be used to monitor characteristics of body part 110.

[0095] The communication interface 212 may be used, for example, via radio waves and in accordance with Bluetooth TM Protocols (such as Bluetooth TM The communication interface 212 may wirelessly communicate with other devices using a wireless (e.g., low energy) or another protocol. The communication interface 212 may, for example, communicate and pair with other devices and transmit device usage or sensor data (e.g., alarms, monitored loads or positioning, or changes in monitoring or treatment plans performed by the activity monitoring device 120) to the other devices. The communication interface 212 may be used to receive data including commands from other devices. Once the communication channel has been configured to communicate with another device (e.g., by device pairing), the communication interface 212 may allow communication with the other device (e.g., transmitting data to the other device or processing commands from the other device). In some aspects, the communication interface 212 may be unable to communicate at a distance of more than 10 meters, 30 meters, or 100 meters from the communication interface 212.

[0096] Figure 3 Computing environment 300 is shown including activity monitoring device 120 and offload monitoring device 132. Computing environment 300 shows activity monitoring device 120 and offload monitoring device 132 communicating with user operated device 310 and clinician operated device 320, and user operated device 310 and clinician operated device 320 communicating with device management system 340 via network 330.

[0097] The user-operated device 310 may be operated by a user (e.g., a wearer) of the activity monitoring device 120 and the off-load monitoring device 132. The user-operated device 310 may allow the user to use the user-operated device 310 to collect, process, review, or transmit data collected by the activity monitoring device 120 and the off-load monitoring device 132. On the other hand, the clinician-operated device 320 may be operated by a clinician for a user (e.g., an individual who supervises, assists, or cares for a user who uses the activity monitoring device 120 and the off-load monitoring device 132). The clinician-operated device 320 may allow the clinician to use the clinician-operated device 320 to collect, process, review, or transmit data collected by the activity monitoring device 120 and the off-load monitoring device 132.

[0098] The user-operated device 310 and the clinician-operated device 320 may each be a computing device, such as a smartphone, a tablet, or a desktop computer. In some aspects, the user-operated device 310 and the clinician-operated device 320 may receive, send, present, and access data collected by or determined from the activity monitoring device 120 and the offload monitoring device 132, but may not process the data collected by the activity monitoring device 120 and the offload monitoring device 132 to analyze characteristics of the data (e.g., to identify from the data when the user is using an offload device, or to calculate the duration of an activity in which the user is engaged).

[0099] The user operating device 310 may include a user application 312, a communication interface 314 (which may, for example, include any one or more features of the communication interface 212), and a user interface 316 (which may, for example, include any one or more features of the user interface 206). The user application 312 may be a program executed by a processor of the user operating device 310. The user application 312 may enable the user operating device 310 to communicate with the activity monitoring device 120, the load reduction monitoring device 132, and the device management system 340 via the communication interface 314. The user application 312 may receive, collect, process, review, or transmit (i) data collected or determined by the activity monitoring device 120 and the unloading monitoring device 132, such as motion data, alerts, monitored loads or positioning, or changes in monitoring or treatment plans, (ii) data collected or determined by the user application 312, such as user observations, goal information, or identification of activities in which the user is engaged, or (iii) data collected or determined by the device management system 340, such as the duration of time the user is active, the portion of time the user uses an unloading device, or the amount of time the user is at risk of injury due to the user's activity or non-use of an unloading device. The user application 312 may also present one or more graphical user interfaces, such as one or more of the graphical user interfaces described herein, to the user, such as on a display or touch screen of the user interface 316, in conjunction with the user interface 316.

[0100] The user application 312 may be used to collect information from the user to assist in understanding the type of activity the user engaged in when the user's foot may have experienced forces that are at risk of adversely affecting an existing ulcer on the foot or at risk of causing a new ulcer on the foot. The user application 312 may receive from the device management system 340 motion data from the activity monitoring device 120 indicating the time when the user's foot experienced forces that are at risk of adversely affecting an existing ulcer on the foot or at risk of causing a new ulcer on the foot, and the user application 312 may determine (e.g., from a global positioning system (GPS) receiver of the user operating device 310 or communications received by the user operating device 310 via the network 330) the geographic location of the user operating device 310, which may indicate the geographic location of the activity monitoring device 120 at that time. The user application 312 may output the time and geographic location of the user operating device 310, and a request from the user to identify the type of activity the user engaged in at that time and geographic location. For example, the activity type may include a transportation type, an exercise type, a leisure type, a hobby type, or a work type. The request may list a set of activity types that the user typically engages in to assist in selecting the type of activity the user engages in.

[0101] The user application 312 may include a function lock that disables certain functions of the user application 312 before the user's check-in time (e.g., by preventing access to the function). The check-in time may be a time provided by the user when the user anticipates that the user will settle down and may not engage in additional activities that may adversely affect an existing foot ulcer or a new foot ulcer. The function lock may help control the timing of the user's interaction with the user application 312 (e.g., until after the user may have settled down for the day) to help ensure that the requested information is collected from the user that day. The function may, for example, include the ability for the user to respond to prompts (e.g., about the user's thoughts or observations of the day or the user's feelings). Although the function lock may lock some functions, other functions of the user application 312 may be available before the check-in time for the user to access or complete before the check-in time.

[0102] User application 312 may include aspects and interfaces that seek to increase the amount or frequency of user interaction with user application 312. User application 312 may request contextual information (e.g., identification of activities in which the user engages while wearing activity monitoring device 120, or an indication by the user of how the user feels) to assist in tracking or understanding why the user's foot may be experiencing forces that are at risk of adversely affecting an existing ulcer on the foot or at risk of causing a new ulcer on the foot. From the contextual information (e.g., the timing or frequency of receiving the contextual information), user application 312 may determine an interaction metric for the user, which may indicate the amount of user interaction with user application 312. User application 312 may then use the interaction metric to adjust a graphical interface generated by user application 312 and presented to the user by user interface 316.

[0103] The clinician operating device 320 may include a clinician application 322, a communication interface 324 (which may, for example, include any one or more features of the communication interface 212), and a user interface 326 (which may, for example, include any one or more features of the user interface 206). The clinician application 322 may be a program executed by a processor of the clinician operating device 320. The clinician application 322 may enable the clinician operating device 320 to communicate with the activity monitoring device 120, the offload monitoring device 132, and the device management system 340 via the communication interface 324. The clinician application 322 may receive, collect, process, review, or transmit (i) data collected or determined by the activity monitoring device 120 and the off-load monitoring device 132, such as motion data, alarms, monitored loads or positioning, or changes in monitoring or treatment plans, (ii) data collected or determined by the user application 312, such as user observations, goal information, or identification of activities in which the user is engaged, or (iii) data collected or determined by the device management system 340, such as the duration of time the user is active, the portion of time the user uses an off-load device, or the amount of time the user is at risk of injury due to the user's activity or non-use of an off-load device. The clinician application 322 may present one or more graphical user interfaces, such as one or more of the graphical user interfaces described herein, to the clinician, such as on a display or touch screen of the user interface 326.

[0104] In some aspects, the clinician-operated device 320 may not communicate directly with the activity monitoring device 120 or the offload monitoring device 132. Instead, the clinician-operated device 320 may receive any data collected by or associated with the activity monitoring device 120 and the offload monitoring device 132 from the device management system 340 via the user-operated device 310. This design may desirably limit the number of devices (other than the user-operated device 310) that may receive data directly from the activity monitoring device 120 and the offload monitoring device 132, thereby enhancing the security of the data and limiting access to the data.

[0105] Device management system 340 may be a computing device (eg, a server) and include a communication management system 342, a data processing system 344, and a data storage device 346 that may communicate with each other. For example, device management system 340 may use, for example, a server provided by Amazon Web Services TM (AWS), Microsoft TM Azure TM 、Google Cloud Platform TM (GCP) or Oracle TM The cloud infrastructure provided by Cloud Infrastructure (OCI) is partially or completely composed of server infrastructure or cloud architecture. The server infrastructure and cloud infrastructure can comply with HIPAA (Health Insurance Portability and Accountability Act of 1996) requirements and provide data privacy and security protection in view of the potential sensitivity of the data collected, processed or determined by the device management system 340.

[0106] The communication management system 342 may allow the device management system 340 to communicate with the user-operated device 310 and the clinician-operated device 320 over the network 330. The communication management system 342 may include an application programming interface (API), such as a cloud API, to facilitate its communications.

[0107] The data processing system 344 may collect, process, present, store (e.g., in a data storage device 346), or transmit data collected or determined by the activity monitoring device 120 and the off-load monitoring device 132 (e.g., motion data, alarms, monitored loads or positioning, or changes in monitoring or treatment plans) and data collected or determined by the user application 312 (e.g., user observations, goal information, or identification of activities in which the user is engaged). For example, the data processing system 344 may process the data collected by the activity monitoring device 120 and the off-load monitoring device 132 to determine activities that the user may have engaged in during various time periods during which the data was collected (e.g., sitting / standing, driving a car, walking, or lying down with feet elevated), and whether the user may have worn an off-load device during various time periods during which the data was collected (e.g., comparison of motion data from the activity monitoring device 120 and the off-load monitoring device 132). The determined possible activities or use of an off-load device may be shared by the device management system 340 with the user-operated device 310 or the clinician-operated device 320. As another example, the data processing system 344 may process data collected by the activity monitoring device 120 and the offload monitoring device 132 to identify events of interest (e.g., events that may indicate excessive pressure applied to the body part 110), and may share the events of interest with the user-operated device 310 or the clinician-operated device 320.

[0108] The network 330 may be a computer network, such as a cellular communication network. Although the network 330 is shown as one connected network, the network 330 may be subdivided into one or more separate networks that may not communicate directly with each other. For example, the device management system 340 may communicate with the user operating device 310 via a network separate and different from the network used by the device management system 340 to communicate with the clinician operating device 320.

[0109] Although certain data processing in computing environment 300 may be described as being performed by activity monitoring device 120, offload monitoring device 132, user-operated device 310, clinician-operated device 320, or data processing system 344, certain data processing may be transferred to different devices or systems in computing environment 300. For example, user-operated device 310 may be described as not processing motion data provided by activity monitoring device 120 and offload monitoring device 132, but may rely on data processing system 344 to analyze the motion data; however, user-operated device 310 may additionally or alternatively use a method or algorithm similar to or different from data processing system 344 to analyze the motion data.

[0110] Figure 4A function locking process 400 is shown that disables and enables functionality of an application, such as a user application 312 of a user operating device 310. For convenience, the function locking process 400 is described in the context of a computing environment 300, but the function locking process can be implemented in other components or systems described herein, or by other computing systems not shown. In some embodiments, the function locking process 400 can advantageously limit the functionality of the user application 312 until a set time in an attempt to facilitate a particular user engagement and collect all desired or requested data from the user.

[0111] At box 410, the function lock process 400 can disable specified functions of the application. The specified functions can be a first subset of the functions of the application, and a second subset of the application may not be disabled by the function lock process 400. The functions to be disabled can be specified by programming in the application, or in response to a change in a flag in a memory device (where the flag can be controlled by the application). For example, the specified functions may include the ability of a user of the user operating device 310 to perform the following operations: (i) a prompt is presented by the user application 312 requesting a user response, or (ii) providing input to the user application 312 by responding to the prompt. For example, the prompt may request the user to indicate the user's feeling or the condition of the user's ulcer. Other examples of specified functions that can be disabled may include the ability to access certain information within or through the user application, or functions associated with how the user responds to the input of the user application 312 (e.g., by dismissing certain requests or providing one or more alternative prompts instead of the prompt).

[0112] At box 420, the function lock process 400 can determine the time to request information from the user using the application. For example, the user application 312 can request the user to provide a check-in time for requesting the user to provide information via the user interface 316. The check-in time can be a certain time of the day (or some other repetitive time base, such as every hour, every N hours, every N days or every week, where N can be an integer), and in some embodiments can be in the afternoon or evening. The check-in time can be a time provided or selected by the user when the user expects the user to settle down and may not participate in additional activities that may adversely affect existing ulcers or new ulcers. The check-in time can indicate to the user or be understood by the user as a time to request certain information, such as contextual information for the motion data collected by the activity monitoring device 120, such as by identifying the type of activity associated with the event, which has a risk of adversely affecting an existing ulcer on the user's foot or a risk of causing a new ulcer on the foot. When it is determined that the user is not wearing a load-reducing device, the event can be the application of force to the foot. Additionally or alternatively, the user application 312 can request the user to interact with the user application 312 in a desired manner at the check-in time.

[0113] At block 430, the function lock process 400 may remain suspended until the time to request information from the user has been reached (or a time after such time). The user application 312 may continue to provide enabled functionality during the suspension period, such as even providing information to be requested at the check-in time. An example of such an enabled functionality may be the ability to provide contextual information for the motion data collected by the activity monitoring device 120. Once the time is reached, the function lock process 400 may transition to block 440.

[0114] At block 440, the function lock process 400 may enable a specified function of the application that may have been disabled at block 410. The specified function may be enabled by programming in the application due to the expiration of a timer or in response to a flag in a memory device, where the flag may be controlled by the application based on a system time provided by the user operating device 310. For example, the user application 312 may unlock the ability of a user of the user operating device 310 to: (i) present a prompt requesting a user response by the user application 312, or (ii) provide input to the user application 312 by responding to the prompt. In addition, the user application 312 may present a prompt in response to enabling the specified function. In another example, the user application 312 may unlock the user's access to certain information within or through the user application, or adjust how the user application 312 responds to the input of the user application 312.

[0115] At block 450, the function lock process 400 may utilize an application to request information from the user. For example, the user application 312 may request the user to provide the requested information via the user interface 316. Additionally or alternatively, the user application 312 may request the user to interact with the user application 312 in a desired manner.

[0116] After completing the function locking process 400, the specified function of the application may be disabled again. In some embodiments, the function locking process 400 can then return to block 430 and remain suspended until it is time to request information from the user again.

[0117] Although the time to request information determined at block 420 may indicate to the user or be understood by the user as a time to request certain information, such as context information, the functionality lock process 400 may also be used to lock specified functionality of the user application 312 to the user until after the check-in time. At block 420, this functionality lock may not be communicated to the user as a reason for requesting the check-in time. However, in the event that the user attempts to access or deploy the specified functionality of the user application 312 prior to the check-in time, the functionality lock may be communicated to the user later. Thus, the functionality lock may ideally allow the user to access the user application 312 throughout the day, but prompt the user to interact with the user application 312 at least during the check-in time.

[0118] Figure 5 An activity recognition process 500 is shown that determines the type of activity a user is engaged in at a time and geographic location of an event that has a risk of adversely affecting an existing ulcer on a user's foot or causing a new ulcer on a foot. For convenience, the activity recognition process 500 is described in the context of the computing environment 300, but the activity recognition process can be implemented in other components or systems described herein or by other computing systems not shown. In some embodiments, the activity recognition process 500 can advantageously help a user to recall and provide information related to the treatment or prevention of an ulcer in a timely manner so that the information can be stored for later access, such as during a consultation between a user and a clinician.

[0119] At block 510 , activity recognition process 500 may receive motion data from a motion sensor. For example, user application 312 may receive motion data, such as accelerometer or magnetometer data, from activity monitoring device 120 via communication interface 314 .

[0120] At block 520, activity recognition process 500 may transmit the motion data to a server. For example, user application 312 may transmit the motion data to communication management system 342 of device management system 340 via communication interface 314. User application 312 may forward the motion data from activity monitoring device 120 without processing, or may process (e.g., analyze or compress) the motion data before forwarding it.

[0121] At block 530, the activity recognition process 500 may receive, from the server, an identification of a time when a force was applied to a limb of the user, e.g., when it is determined that the user is not wearing an unloading device. The application of a force to a limb without the use of an unloading device may be referred to as an event. For example, the user application 312 may receive, from the device management system 340 via the communication interface 314, motion data indicating a time (e.g., a specific moment or time range) when the user's foot experienced a force that was at risk of adversely affecting an existing ulcer on the foot or at risk of causing a new ulcer on the foot. For example, the data processing system 344 of the device management system 340 may have determined the time by analyzing the motion data.

[0122] At block 540, the activity recognition process 500 may determine a geographic location at or approximately the time when the force was applied to the user's limb. For example, the geographic location may be the location of the user operating device 310, which may be assumed to match the location of the activity monitoring device 120 at or approximately the time. The user application 312 may determine the geographic location from a global positioning satellite (GPS) receiver of the user operating device 310 or communications received by the user operating device 310 via the network 330.

[0123] At block 550 , the activity recognition process 500 can output the time and geographic location for presentation. For example, the user application 312 can output the time and geographic location on a graphical user interface for presentation on a display of the user interface 316 .

[0124] At block 560, the activity identification process 500 may request from the user the type of activity that the user is engaged in at the time and geographic location. For example, the user application 312 may output the request on a graphical user interface along with the time and geographic location at block 550. The activity type may include one or more of the activity types described herein, such as a transportation type (e.g., in a car, on a bus, on a bicycle, on a train, on an airplane, or walking), an exercise type (e.g., walking the dog, running, swimming, using a machine, lifting weights, golfing, bowling, or stretching), an entertainment type (e.g., shopping, entertainment, sightseeing, socializing, walking, or dining out), a household activity type (e.g., sitting, lying down, going up and down stairs, gardening, cleaning, or cooking), or a work type (e.g., sitting, walking, manual labor, driving, or standing).

[0125] In response to the request, the user may select one or more activity types, for example, by selecting one or more activity types via the user interface 316. In some aspects, the user may select only one activity type. To help the user identify one or more activity types from among many different activity types, the user application 312 may initially present a list of activity types identified by the user as activity types that the user typically engages in. The user application 312 may then receive the selected one or more activity types.

[0126] At block 570, the activity identification process 500 may transmit the activity type to a server for storage with the time and geographic location. For example, the user application 312 may transmit the activity type identified by the user to the communication management system 342 for processing by the data processing system 344 and storage in the data storage device 346 in association with the time and geographic location.

[0127] Figure 6 An interface control process 600 is shown for controlling one or more aspects of a graphical user interface of an application (e.g., user application 312) based on the amount of user interaction with user application 312. For convenience, interface control process 600 is described in the context of computing environment 300, but the interface control process can be implemented in other components or systems described herein or by other computing systems not shown. In some embodiments, interface control process 600 can advantageously promote and reward user interaction with user application 312 by changing graphical elements of the application in response to the interaction.

[0128] At block 610 , the interface control process 600 may receive motion data from a motion sensor. For example, the user application 312 may receive motion data, such as accelerometer or magnetometer data, from the activity monitoring device 120 via the communication interface 314 .

[0129] At block 620, the interface control process 600 may request contextual information for the motion data from the user. For example, the user application 312 may request, via the user interface 316, that the user provide contextual information for the motion data collected by the activity monitoring device 120. The contextual information may include identification of an activity type associated with an event that has a risk of adversely affecting an existing ulcer on the user's foot or a risk of causing a new ulcer on the foot. When it is determined that the user is not wearing an unloading device, the event may be an application of force to the foot.

[0130] At block 630, the interface control process 600 may receive contextual information from the user. For example, the user may select one or more activity types, such as by selecting one or more activity types via the user interface 316. In some aspects, the user may select only one activity type. To help the user identify one or more activity types from among many different activity types, the user application 312 may initially present a list of activity types identified by the user as activity types that the user typically engages in. The user application 312 may then receive the selected one or more activity types. The contextual information may include additional or alternative information (e.g., how the user is feeling about the day or the condition of the user's foot or ulcer), or may include interactions between the user and the user application 312 that may be considered desirable interactions.

[0131] At box 640, the interface control process 600 can determine an interaction metric for the user based on the context information. The interaction metric can indicate the amount of interaction the user has with the application. The interaction metric can be determined from a count of the number of days (or other time period) that the user provides context information or a count of consecutive days (or other time period) that the user provides context information. For example, the user application 312 can determine the interaction metric from a count of the number of days that the user provides context information, or determine that the interaction metric is a count of the number of days. In the case where the user may have provided some but not all of the requested speculative information for a particular day, the user application 312 may not include that particular day in the count.

[0132] At block 650, interface control process 600 may adjust a user interface, such as a graphical user interface, in response to the interaction metric. For example, user application 312 may adjust a graphical user interface generated by user application 312 and output the graphical user interface for presentation on a display of user interface 316. For example, the graphical user interface may be adjusted by (i) presenting feedback selected from one set of feedback options to the user instead of another set of feedback options, (ii) changing the format of information included in the graphical user interface, or (iii) incorporating one image into the graphical user interface instead of another image. If the interaction metric satisfies a threshold, the graphical user interface may be adjusted differently than if the interaction metric does not satisfy the threshold.

[0133] In some aspects, the adjustments in the user interface at box 650 can desirably facilitate continued user interaction with the user application 312 by, for example, providing positive feedback to the user (e.g., by allowing the user to advance through multiple levels, awarding the user a virtual reward to celebrate the user's achievements, or increasing the aesthetic appeal of the user application 312), giving the user enhanced access to information (e.g., allowing the user to have additional information about a treatment), or reducing some of the expectations of interacting with the user application 312 (e.g., no longer requiring the user to provide certain information or requesting information in a more concise manner, thereby allowing the user to view less of the graphical user interface or provide less input).

[0134] Figures 7A-7H An example user interface is shown that may be presented by user application 312 on user interface 316 of user operating device 310 and that facilitates introducing a user into operation of user application 312 , enabling user interaction with user application 312 , and initiating the collection of information by user application 312 .

[0135] Fig. 7A An example welcome interface 1000 is shown, which can present a custom message 1002 (e.g., the user's name or other user or wound specific message) and a learn more element 1004. When selected by the user, the learn more element 1004 can transform the user interface 316 to present a Figure 7B Configuration interface 1010 shown in .

[0136] Configuration interface 1010 may provide an introductory message 1012 and include selectable elements 1014, 1016, and 1018. Selectable elements 1014, 1016, and 1018 may each transition user application 312 to a different configuration screen that may be part of a user onboarding or setup process for user application 312.

[0137] Figure 7C An introduction interface 1020 is shown, which may be presented via the configuration interface 1010 after the application configuration is completed. The introduction interface 1020 may include a character 1022 (sometimes referred to as an avatar) that may be used to improve interaction with the user application 312. As further described herein, the character 1022 may be customized by the user to adjust the manner in which the user receives information from the user application 312. The introduction interface 1020 may have an instructional message 1024 and a next element 1026. User selection of the next element 1026 may trigger the user interface 316 to transition to Fig.7D Travel type interface 1030 shown in .

[0138] As shown, the travel type interface 1030 can present a travel type request 1032, which can indicate the requesting user to identify one or more types of vehicles that the user typically uses for travel. The travel type interface 1030 can also include an optional travel type element 1034, which allows the user to indicate one or more specific vehicle types to the user application 312. This information can, for example, enable the user application 312 to determine the type of vehicle utilized by the user to provide a more effective data display or enable the user to enter event data more efficiently. The travel type interface 1030 may include an optional custom element 1036 and an optional skip element 1038, which can allow the user to provide a custom activity type input, and the optional skip element can allow the user to choose not to select one or more of the optional travel type element 1034 or the optional custom element 1036.

[0139] After presenting the row type interface 1030, the user application 312 may transition to Fig. 7E . The exercise type interface 1040 may present an exercise type request 1042, which may indicate the requesting user to identify one or more exercise types that the user typically participates in. The exercise type interface 1040 may also include an optional exercise type element 1044, which allows the user to indicate one or more specific exercise types to the user application 312. This information may, for example, enable the user application 312 to determine the exercise type participated in by the user to provide a more effective data display or enable the user to enter event data more efficiently. The exercise type interface 1040 may include an optional custom element 1046 and an optional skip element 1048, which may allow the user to provide a custom exercise type input, and the optional skip element may allow the user to choose not to select one or more of the optional exercise type element 1044 or the optional custom element 1046.

[0140] Although not shown, the user application 312 can be transformed to other activity type interfaces, including a leisure type interface, a home activity interface, a work type interface, or an auxiliary movement interface. These interfaces can be configured similarly to the travel type interface 1030 or the exercise type interface 1040. The leisure type interface can present a leisure type request, which can indicate that the user is requested to identify one or more leisure types that the user usually participates in. Similar to the exercise type interface, the leisure type interface can include optional leisure type elements that facilitate the user to enter such activities. The work type interface can be configured similarly to the exercise type interface and the leisure type interface, and can be additionally after the work qualifier interface, which requests the user to indicate whether the user works during the wearing of the activity monitoring device 120. If the user indicates that the user will wear the activity monitoring device 120, the work type interface and the corresponding optional elements can be presented to the user, and the work type interface can request the user to identify one or more work activity types that the user usually participates in. If the user indicates that the user will not wear the activity monitoring device 120, the user application 312 may not present the work type interface and proceed to another user interface. The auxiliary movement interface can present an auxiliary movement request, which can indicate that the user is requested to identify one or more auxiliary movement modes or modes that the user will use. As with the other activity interfaces, the assisted movement interface may include a selectable assisted movement type element that facilitates the user to enter the type of assisted movement device that the user may use while wearing the activity monitoring device 120 .

[0141] Figure 7F A user goal interface 1050 is shown that can be used to collect additional goal data from the user for use in the user application 312. As shown, the user goal interface 1050 can have a goal addition element 1056 that enables the user to enter a new goal and an optional goal element 1054, each of which is related to a different goal provided by the user or clinician for the user. This information can assist the user application 312 in tracking information about the user's performance of activities or behaviors to assist the user in staying accountable for actions (e.g., goals related to treatment for the user).

[0142] Figure 7GA check-in setup interface 1060 is shown that can be used to determine a time at which a user can be prompted to provide treatment-related information. As shown, the check-in setup interface 1060 can present a time request 1062 and include selectable time elements 1064, which can prompt the time of day when the user typically settles down and reduces their activity, each selectable time element corresponding to a different time that the user can select to check in. The time provided by the user via the selectable time element 1064 can assist the user application 312 in customizing the time of treatment-related information requested from the user, as well as allowing the user application 312 to disable certain of its functions to facilitate interaction with the user application 312 after the user settles down and reduces their activity for the day. The check-in setup interface 1060 may include a next selectable element 1068, which can allow the user to submit the time selected by the selectable time element 1064 to the user application 312 and advance to the next user interface, such as Figure 7H 1070 as shown in FIG.

[0143] The role selection interface 1070 may allow a user to set a preferred role to be used in various user interfaces of the user application 312. The role selection interface 1070 may present a role request 1072 asking the user to identify which role the user prefers and a changeable role element 1074. The role selection interface 1070 may include a selection element 1078 that allows the user to confirm the selection of the identified role element and proceed to another user interface. In some aspects, the role selected by the user may be core to the user experience of the user application 312 and affect the way the user application 312 interacts with the user, such as the type of encouragement or language used when conveying information or progress to the user.

[0144] Figures 8A-8L An example user interface is shown that may be presented by the user application 312 on the user interface 316 of the user operating device 310 and that may prompt the user to provide information to the user application 312 and allow the user to input information.

[0145] Fig. 8A Shown is a check-in status interface 1080 that prompts or reminds the user when the time for entering contextual information is scheduled to occur. Before the time allowed for such access or input has been reached (e.g., as described in relation to Figure 4 As described in block 430 of , when the time has arrived to request information from the user, the time at which such access or input may be allowed may begin), when the user attempts to access a particular user interface or enter particular data (e.g., as described with respect to Figures 8D-8FWhen the user application 312 is prompted to enter the data or feedback about the user's physical and mental health status as described above, the user application 312 can present a check-in status interface 1080. The check-in status interface 1080 can present an informational message 1084, which can remind the user when the check-in time is scheduled. The time presented in the informational message 1084 can correspond to the time entered by the user through the check-in setup interface 1060 during the loading or setup phase. The check-in status interface 1080 can present a status indicator 1082, which can provide visual feedback to the user when the time is about to occur or has occurred, or when the user has not yet activated or engaged in a particular interaction with the user application 312. When the status indicator 1082 is displayed as a partial outline of a circle and without Figure 8B When the token (shown as a center star) shown in FIG is filled, the status indicator 1082 can indicate that the time has not yet been reached. The optional confirmation element 1086, when selected by the user, causes a transition from the check-in status interface 1080 to a subsequent user interface.

[0146] Figure 8B An event status interface 1090 is shown, which can present an informational message 1094 to the user to inform the user that the number of unmarked events (e.g., a count of events for which the user has not yet provided contextual information) can be maintained. As described herein, an event can be, for example, the application of force to a user's limb when it is determined that the user has not yet worn a load-reducing device. A status indicator 1092 can present visual feedback to the user and can be the same or similar to the status indicator 1082. A mark event element 1096, when selected, can transition the user application 312 from the event status interface 1090 to another interface that can request the user to input information about unmarked events. The user application 312 can display the event status interface 1090 before reaching that time.

[0147] Figure 8C The tag log launch interface 1100 is shown, which prompts the user to sign in to provide contextual information. When the status indicator 1102 is filled with tokens (shown as a center star) and there is no Fig. 8A 1082 may indicate that the time has arrived and the user may now earn tokens by completing the check-in process (where earning tokens may be a positive reward for the user and may serve as feedback to the user or clinician on the user's tracking of the use of the application 312). The user application 312 may display the mark log launch interface 1100 in response to the time being reached. The guidance message 1104 may prompt the user to check in and mark any unmarked events. The mark event selectable element 1106, when selected by the user, may trigger the user application 312 to transition from the mark log launch interface 1100 to a subsequent user interface (e.g., Fig.8DThe user application 312 may present the tag log launch interface 1100 to indicate, for example, the enabling of a disabled function of the user application 312 (e.g., regarding Figure 4 440 ), because the tag log launch interface 1100 can provide access to at least some previously unavailable functionality of the user application 312.

[0148] The physical and mental health feedback interface 1110 can request the user to input information about the user's physical and mental health status. The physical and mental health feedback interface 1110 can request the user to provide the user's happiness level on a five-unit scale from "not happy at all" to "very happy". The physical and mental health status bar 1112 can present a visual status indication of the user's progress through the check-in process, such as a portion of the feedback questions of the check-in process that have been answered or are remaining for the user to answer. The physical and mental health feedback interface 1110 can present feedback questions or prompts 1114 (regarding a first condition, such as "I feel..."), listing the required data input and optional physical and mental health elements 1116, each optional physical and mental health element representing a different response to the feedback question or prompt 1114. In addition, the next optional element 1118, when selected by the user, can transition the user application 312 from the physical and mental health feedback interface 1110 to a subsequent user interface, which can be Fig. 8E Foot health feedback interface 1120 shown in .

[0149] The foot health feedback interface 1120 can present a feedback question or prompt 1124 (regarding the second condition, such as "My feet feel..."). The physical and mental health status bar 1122 can display the physical and mental health status bar 1112 after the feedback question or prompt 1114 is completed. The foot health feedback interface 1120 can present: selectable feedback elements 1126, each selectable feedback element representing a different response to the feedback question or prompt 1124; and a next selectable element 1128, through which the user can confirm the input of the response to the feedback question or prompt 1124 and cause the user application 312 to transition from the foot health feedback interface 1120 to a subsequent user interface (e.g., Fig.8F Observation feedback interface 1130 shown in ).

[0150] The observation feedback interface 1130 can present a feedback question or prompt 1134 regarding a third condition (e.g., “I noticed…”) to request information about one or more conditions of the user's foot or wound area, including observation of swelling, bruising, drainage, or redness. The observation feedback interface 1130 can include selectable elements 1136, each selectable element representing a different response to the feedback question or prompt 1134. The physical and mental health status bar 1132 can display the physical and mental health status bar 1112 after completing the feedback question or prompt 1114 and the feedback question or prompt 1124. The observation feedback interface 1130 can present a next selectable element 1138, through which the user can confirm the input of the response to the feedback question or prompt 1134 and cause the user application 312 to transition from the observation feedback interface 1130 to a subsequent user interface (e.g., Figure 8G ) as shown in the goal completion interface 1140 .

[0151] The goal completion interface 1140 may present feedback questions or prompts 1144 (e.g., questions from the user regarding the user's goal that was previously set by the user via Figure 7F 1050 input). The physical and mental health status bar 1142 can display the physical and mental health status bar 1112 after completing the feedback question or prompt 1114, the feedback question or prompt 1124, and the feedback question or prompt 1134. The goal completion interface 1140 may include selectable goal elements 1146, each selectable goal element representing a different response to the feedback question or prompt 1144. The goal completion interface 1140 may extend beyond a single screen space on the user interface 316, so that the user can, for example, swipe up or scroll down to view the entire goal completion interface 1140, including additional goals. The goal completion interface 1140 may present a next selectable element 1148, through which the user can confirm the input of the response to the feedback question or prompt 1144, and cause the user application 312 to transition from the goal completion interface 1140 to a subsequent user interface, which may optionally be Figure 8H Untagged event summary interface 1150 shown in .

[0152] Untagged event summary interface 1150 can indicate the number of events (e.g., three events as shown) for which the user is requested to provide contextual information (e.g., information about the type of activity the user was engaged in when the event occurred, which can be referred to as a tag). Also included is an optional next element for advancing to another user interface, such as Fig.8I The geographic location interface 1160 shown in .

[0153] The geolocation interface 1160 may be used to request the user to consider contextual information about the event. The geolocation interface 1160 may present event information 1162, including the time (which may also be a time range as shown) and location of the event, to remind the user of the time and location of the event. For example, the event information 1162 may provide the time and location of the event, such as information about Figure 5 550 of . The guidance image 1163 may indicate a determination that the user has worn the unloading device during the event. The user application 312 may have received the time, location, and determination of wearing the unloading device from the device management system 340, for example, in response to a request from the user operating device 310 or a push notification from the device management system 340. The map image 1164 may be used to depict the location of the user or the user operating device 310 at the time of the event. The location input element 1166, when selected by the user, may transition the user application 312 from the geographic location interface 1160 to a different user interface (e.g., Figure 8J ) as shown in the activity input interface 1170 .

[0154] Activity input interface 1170 may display event information 1172, which may be the same as event information 1162. Activity input interface 1170 may prompt the user to provide activity category information 1174 by requesting the user to select the category of activity the user is participating in at the time and location of the event. Activity category information 1174 may be information about Figure 5 The frame 560 and Figure 6 The example of a request from a user as described in block 620 of FIG. 1174 may include activity description categories 1176, which may be selected by the user to enter a category of activity that the user participated in during the event. The activity description categories 1176 may, for example, include home (indicating that the user was at home), leisure (indicating that the user participated in leisure), travel (indicating that the user was traveling), work (indicating that the user was working), exercise (indicating that the user participated in exercise), or I don't remember categories (indicating that the user does not remember what type of activity was participated in).

[0155] The activity description category 1176, when selected by the user, may transition to another user interface that prompts the user to enter the type of activity that the user is participating in at the time and location of the event within the selected category. In some aspects, the activity category may be the same as the activity type (rather than a set of activity types as described in this example). A close element 1178 may be selected to confirm that the user has completed inputting the category or type information requested in the activity input interface 1170 and transition from the activity input interface 1170 to a subsequent interface (e.g., Figure 8K ) as shown in the marked event summary interface 1180 .

[0156] The tagged event summary interface 1180 may display a summary image 1182 representing the type of activity that the user has identified for the event, as well as a time and a map showing the location of the event. The information presented on the tagged event summary interface 1180 may be confirmed by the user by selecting a save element 1188. Selection of the save element 1188 may prompt the user application 312 to save the information for the event, and transmit at least the type of activity identified by the user, for storage by the device management system 340 in association with the event, time, or location. Figure 8K The example shows a user selecting exercise using a machine as the type of activity the user engages in during the event.

[0157] although Figure 8J It is shown that a user can navigate by selecting one or more categories or before selecting one or more activity types, but in some aspects, multiple activity description categories or types may be presented to the user on the activity input interface 1170 that may correspond to different activity types that the user previously indicated (e.g., via travel type interface 1030 or exercise type interface 1040) as types of activity in which the user commonly engages.

[0158] Figure 8L An event confirmation interface 1190 is shown that can provide feedback to the user regarding the input requested to complete the sign-in process. The event confirmation interface 1190 can display a token 1192 (which can be any symbol, such as a star) that transitions to a total token count 1193. The total token count 1193 can represent the total number of times the user successfully entered all requested information for the sign-in process and can be maintained by the user application 312. An information status 1194 can confirm the successful completion of the sign-in process through text. The event confirmation interface 1190 can also display an appointment reminder 1196 for an upcoming doctor's appointment.

[0159] Figures 9A-9D An example user interface is shown that may be presented by a user application 312 on a user interface 316 of a user operated device 310 to provide a summary of monitoring, activities, events, or determinations for a user. The summary may be helpful in monitoring and treating foot ulcers on a user. The summary may be presented to cover data collected over or determined for a selectable length of time, such as over a few hours or less, a day, several days, a week or weeks, or longer.

[0160] Fig.9AA user interface 1300 is shown in which a series of summary information can be presented to a user. The user summary interface 1300 may include an overview message 1302 indicating the subject of the content to be presented and the time period to which the summary information relates (e.g., the illustrated aspect presents a summary of information collected by the user application 312 or determined for the user since "last Friday"). The summary information may include user observations 1306, such as a user feeling summary 1308 (which may present an average of feeling data from the user on a five-point scale of how the user felt during the time period and include graphical symbols, such as a happy face or a sad face, to graphically convey the feeling), a foot feeling summary 1310 (which may present an average of feeling data on a five-point scale of how the user's feet felt during the time period and include graphical symbols, such as a bare foot, to graphically convey the feeling).

[0161] The user summary interface 1300 may present the number of occurrences of swelling 1314, redness 1316, bruising 1318, and drainage 1320 that the user indicated occurred at the user's foot or foot wound during the time period. The user summary interface 1300 may present a summary of any other desired or meaningful observations entered or selected by the user during the user loading or setup process of the user application 312. The user summary interface 1300 may present summary data 1324, such as actual and target average daily foot activity 1328 (e.g., where the actual is shown as 2 hours and 54 minutes, while the target is shown as 6 hours and 23 minutes), unloading device usage 1330 (e.g., where the usage is shown as 72% and is up 24% from the previous time period), and average daily risk time 1332 (e.g., where the risk time is shown as 48 minutes, which may be 1 hour and 34 minutes lower than the previous time period). Risk time may refer to the amount of time that a user's limb may be in an active state when the unloading device is not used.

[0162] The user summary interface 1300 can present a key event summary 1340 to the user, which can include a presentation of the amount of time the user spent participating in a particular activity during the event. Such events can be grouped by activity category or type, and can include family time 1342, leisure time 1344, work time 1346, and unmarked time 1348.

[0163] Home time 1342, leisure time 1344, work time 1346, and unmarked time 1348 may be user-selectable elements that, when selected by a user, expand user summary interface 1300 to another user interface (e.g., Fig. 9B) to present to the user additional information about a selected key event summary 1340 (e.g., the total duration of events occurring at the time / location, an increase or decrease relative to the total duration of the previous time period, load shedding device usage, the amount of time the user engaged in a particular activity type at the time / location, the number of occurrences of events for a particular activity type, the average time per event for a particular activity type, the number of collisions for a particular activity type, the percentage of load shedding device usage for a particular activity type, or the percentage of assisted mobility usage for a particular activity type).

[0164] The user summary interface 1300 can present a target occurrence summary 1350 to the user, which can include the presentation of the number of times the user achieves each target. The target can include the target entered by the user during the user loading or setting process of the user application 312. The example of the target that can be presented includes "check if there are sharp objects under my shoes" (as shown in the first target 1352), "go for a run" as a second target 1354, and "drink more water" as a third target 1356. The targets can be sorted according to the number of times the target is reached (e.g., from the highest number of occurrences to the lowest number of occurrences, and vice versa). The user summary interface 1300 can have a completion element 1360, and the user can trigger the user application 312 to transition to a different or subsequent user interface by selecting the completion element.

[0165] Fig. 9B A home interface 1370 is shown, which may include an interface identifier (e.g., "home") and presents data or information to the user regarding activities that were determined or identified as having occurred at the user's home. The home interface 1370 may present to the user cumulative home event time 1372 and load shedding device percentage usage 1374 for events that occurred while the user was spending time at home. The home interface 1370 may present to the user the amount of time the user engaged in a particular activity while at home and the amount of time during which the event occurred. Such activities may correspond to activities during the activity identification process 500, for example, including ascending / descending stairs 1376, gardening 1378, cooking 1380, or sitting down 1386, which are entered or selected by the user.

[0166] The home interface 1370 may present an activity type summary 1384 that presents information to the user about home events of a particular activity type (e.g., cooking). The activity type summary 1384 may indicate the number of events the user participated in during home time, the average time the user spent per event, the number of collision or trauma events that occurred during home time, the percentage of time the user used a load relief device during home time, and the percentage of time the user received assistance during mobility.

[0167] Fig. 9C An appointment interface 1400 is shown that can present a user with a plan of appointments for a day (e.g., today) and details and tasks related thereto. An instruction message 1402 that can state "Today's appointment" and other descriptive text or symbols can be included in the upper portion of the appointment interface 1400. The appointment interface 1400 can include a pre-appointment checklist 1404 that can present the user with tasks to be completed before the appointment, and an appointment activity checklist 1410 that includes the name of the doctor for the upcoming appointment and other preparation options. A first task element 1406 can present the user with the option of selecting and reviewing a first task. In the example shown, the first task can be "Review my report." Therefore, selecting the first task element 1406 can transition the user application 312 from the appointment interface 1400 to another user interface that presents the user with relevant reports related to the doctor's visit. The second task element 1408, when selected by the user, can transition the user application 312 from the appointment interface 1400 to another user interface in which the user can enter questions, topics, reminders, or other information related to the appointment that the user wishes to prepare. The scheduled activity checklist 1410 may present the user with the ability to set a goal, change sensors (eg, an activity monitoring device 120 or an unloading monitoring device 132 associated with the user application 312), or schedule the next appointment with a clinician.

[0168] Fig.9D A foot activity goal interface 1430 is shown that can present an informational message 1432 to the user, which can include a title for the foot activity goal interface 1430 (which can be "My Daily Foot Activity Goal") and a description of the requested information to be entered or adjusted on the foot activity goal interface 1430. As shown, the requested information can be "How active should my feet be before my next appointment?" The foot activity goal interface 1400 can enable the user to enter an average goal foot activity 1434 (e.g., daily activity) over a certain length of time (e.g., since the last doctor's visit), and a slider element 1436 that can be held in a corresponding position, which can be moved upward (e.g., toward more 1438) for a higher goal, or downward (e.g., toward less 1439) for a lower goal. The foot activity goal interface 1430 can have a save element 1440, which the user's selection can trigger the user application 312 to transition to a different or subsequent user interface.

[0169] Figures 10A-10EAn example user interface is shown that may be presented by a user application 312 on a user interface 316 of a user operating device 310 to facilitate user interaction with the user application 312 and input of requested information into the user application 312. As described herein, the user application 312 may be adjusted in response to the user's interaction with the user application 312. Figures 10A-10E The user interface or aspects thereof, such as Figure 6 As described in block 650 .

[0170] Fig. 10A An achievement summary interface 1500 is shown that can present a summary of achievements to the user. The achievement summary interface 1500 may include an achievement summary table 1502 that is configured to present summary information about various aspects of the user's achievements to the user application 312. The achievement summary table 1502 can present a level element 1504, a goal element 1506, a streak element 1508, and a bonus element 1510. When the user selects the level element 1504, the achievement summary interface 1500 can transition to presenting to the user a specified level 1514 that has been achieved based on the user's compliance or interaction with the user application 312. An underline 1512 can indicate to the user which selectable table element has been selected and is being presented, and unselected table elements can be displayed in a lighter color (e.g., gray), while selected table elements can be displayed in a lighter color (e.g., blue).

[0171] The level can range from, for example, 1 to 5, and can include a level 1 rookie ( Fig. 10A Level 2 Novice (not shown), Level 3 Professional (not shown), Level 4 Expert ( Fig. 10B 1070) and Level 5 Master (not shown). Each of these different levels may present a character 1515, which may be the same character selected by the user via the character selection interface 1070, with different accessories or facial expressions to illustrate or represent the level that the character 1515 has reached. The level of happiness expressed by the facial expression of the character 1515 may increase with each level increase from novice to master.

[0172] The level assigned to a user may depend on a number of tokens (sometimes described herein as stars) that the user has accumulated through compliance or interaction with the user application 312. Each time a user completes a check-in or completes another task, a token may be awarded. The increase in the specified level or number of tokens may cause a visual change (e.g., presentation of different formats, color schemes, text information) in the graphical user interface presented to the user on the user interface 316. A token level indicator 1518 may present the number of tokens that the user has accumulated to the user, and may therefore allow the user to understand the number of stars to be accumulated to reach the next level. The achievement summary interface 1500 may include an instruction message 1516 that instructs the user how to achieve more stars and advance to the next level, and may provide a count of tokens that advance to the next level.

[0173] When the user selects the target element 1506, Fig. 10C As shown by underline 1512 in FIG. 1 , the achievement summary interface 1500 can be transformed to present the user with his or her goal-based achievements based on the user's successful completion of the goal, such as Fig. 10C . Examples of goal-based achievements may include new leaves 1530, goal setters 1532, custom heroes 1534, fearless focus 1536, turntables 1538, and multitaskers 1540. Each different goal-based achievement may be achieved when the user has completed a specific criterion associated with the goal. For example, when the user has completed three of their goals, new leaves 1530 may be achieved. When the user has completed ten of their goals, goal setters 1532 may be achieved. The achievement summary interface 1500 may present a flag or a check mark symbol to indicate the goals that the user has achieved. When selecting a goal-based achievement, the achievement summary interface 1500 may present information about the achievement of the associated goal to the user. The achievement summary interface 1500 may indicate a goal that has not yet been achieved by displaying a padlock symbol positioned near an unachieved goal. The achievement summary interface 1500 may present a progress ring 1541 that fills to indicate the user's progress in achieving the corresponding goal. As progress ring 1541 fills, the progress ring represents greater progress toward achieving the corresponding goal.

[0174] If Fig. 10D , when the user selects the streak element 1508, the achievement summary interface 1500 can be converted to present the user with an achievement reward based on the streak based on the number of consecutive days that the user has completed one or more activities or check-in processes. If the user has completed one or more activities for seven consecutive days, the achievement summary interface 1500 can present the user with a 14-day activity achievement reward 1544 for this achievement. A 14-day activity achievement reward 1548, a 21-day activity achievement reward 1552, or a more than 21-day activity achievement reward (not shown) can be presented to another activity achievement.

[0175] If the user has completed check-ins for seven consecutive days, the achievement summary interface 1500 can present the user with a 7-day check-in achievement reward 1546 for this achievement. For a larger number of consecutive check-in days, a 14-day check-in achievement reward 1550 and a 21-day check-in achievement reward 1554 can also be presented. The achievement summary interface 1500 can present pictures and checkmark symbols indicating the streak achievements that the user has achieved. The achievement summary interface 1500 can indicate the streak achievements that have not yet been achieved by displaying a padlock symbol for each unachieved achievement. The achievement summary interface 1500 can present a progress ring 1555 to indicate the progress of the user in achieving the streak achievement.

[0176] When the user selects the bonus element 1510, Fig.10E As shown by the underline 1512 in , the achievement summary interface 1500 can be transformed to present the user with the bonus achievements that have been earned. The bonus achievement can be presented to the user when the user has reached a threshold number of the following actions (e.g., cumulatively): achieving multiple goals in a day; editing multiple events previously marked as "I don't remember"; marking events 2 days or more ago; viewing multiple log entries; adding multiple talking points for a clinician appointment; or checking in for a set number of days and staying within the activity goal level. Bonus achievements that can be presented include spring cleaning 1560, elephant memory 1562, or others. A locked bonus achievement 1564 can be presented to indicate a bonus achievement that has not yet been achieved or visible.

[0177] Fig.11A and Fig. 11B An example user interface is shown that can be presented by a clinician application 322 to allow a clinician to initiate access to information of a user that the clinician may be assisting. The information may have been collected or determined by the device management system 340 through the user operating device 310 and the activity monitoring device 120 or the load-reducing monitoring device 132. The clinician login interface 1600 can present a login prompt 1602 requesting an email address or account name, and a password. When the login element 1604 is selected, the clinician application 322 can transition from the clinician login interface 1600 to an authentication interface 1610. The authentication interface 1610 can present an authentication request 1612 for an authentication PIN, which can be provided to the clinician via out-of-band communication (e.g., via a text message such as a short message service message (SMS) via a cellular network).

[0178] Figures 12A-12G An example user interface is shown that may be presented by the clinician application 322 to allow a clinician to review information about a user that the clinician may be assisting. Fig.11A and 11BAs described above, the information may have been collected or determined by the device management system 340 via the user operated device 310 and the activity monitoring device 120 or the load reduction monitoring device 132 .

[0179] Fig. 12A A panel interface 1620 is shown which may present a panel title 1622, a My Appointments element 1624, and an All Appointments element 1626. An underline 1628 may indicate to the clinician which appointment element has been selected and is being presented. The panel interface 1620 may provide the user with an appointment list 1630 of appointments in chronological order over a period of time. The appointment list 1630 may identify the time at which the appointment with the user will begin, the user's name, the clinician's name, and a summary of other metrics that may be associated with the user, as well as a brief summary of the user's activity or progress over the period of time, including offload device utilization (ODU) and average daily risk time for each user. The appointment list 1630 may present information for each user's appointment on an optional element that, when selected by the clinician, may transition the clinician application 322 from the panel interface 1620 to the Fig. 12B A personal user interface 1640 is shown in FIG. 1 with additional information and details about the selected patient.

[0180] refer to Fig. 12B , the personal user interface 1640 can present a user identifier 1642, which can include the user's name, picture, age, gender or other medical conditions of the user. The personal user interface 1640 can present a report menu 1644, which can include summary information about the user's available reports and appointment history records. When the clinician selects any optional element in the report table, the clinician application 322 can be transformed from the personal user interface 1640 to another user-related interface, which can, for example, present a detailed report of the user or the user's history (including appointment history records). The personal user interface 1640 can present a user management menu 1645 (which can be referred to as a management user menu), which can transform the clinician application 322 from the personal user interface 1640 to a management appointment interface, a management hardware interface or a deactivation application interface when selected by the clinician.

[0181] Upon selecting the new report available element of the report menu 1644, the clinician application 322 may transition from the personal user interface 1640 to the personal user interface 1650 (e.g., the user interface 1650 may present a report identifier 1652, an observation table 1654, a summary table 1656, a key event table 1658, an unmarked table 1660, an exercise activity summary 1662, a work activity summary 1664, a travel activity summary 1666, and a leisure activity summary 1668. Fig. 12C). Observation table 1654 may present to the clinician a summary of how the user feels, how the user's feet feel, or symptoms observed by the user regarding their feet over a period of time. Summary table 1656 may present to the clinician average daily risk time, rate of unloading device use, or average daily time the feet are active (e.g., regarding Fig.9A As described above). For example, summary table 1656 may include: (i) the time the foot was loaded (or in an active state), which may reflect the amount of time the user has engaged in an activity where the foot was loaded (e.g., any activity other than lying down or sitting / standing with the foot lifted); and (ii) the amount of time the user wore the unloading device since the time the foot was loaded (which may be expressed as a percentage or ratio). Any of these times may be expressed as daily time or average daily time (or another time period). Summary table 1656 may include the time the foot has been at risk, which may be determined as the difference between the time the foot was loaded and the amount of time the user wore the unloading device. Summary table 1656 may include information (e.g., in the form of a line graph or another user interface element) that visually illustrates the time the foot was loaded (shown as a line segment on the left), the time the foot has been at risk (shown as the entire line segment), and the target amount of time to wear the unloading device (shown as a point). These three metrics (alone or in combination with the visual illustration) can allow the clinician to quickly and reliably analyze the user's lifestyle, determine the user's compliance with wearing the offloading device, healing trajectory, or risk of exacerbation of existing ulcers or formation of new ulcers, or make appropriate adjustments to treatment.

[0182] The critical events table 1658 can present information to the clinician regarding the activities in which the user participated and the duration of such activities. Activity categories or types can be presented in the critical events table in a selectable format, wherein upon selecting a particular critical event category, the clinician application 322 can transition from the personal user interface 1650 to a detailed critical event report interface that displays more details about the selected critical event, such as information about the Fig.12D Described. Unlabeled table 1660 can present information about unlabeled events, which can be assigned by data processing system 344, and which have possible activities that users participate in when unlabeled activities. Unlabeled activities can include, for example, time spent in a car (e.g., driving), time spent walking, time spent sitting or standing, or time spent raising legs. Transition element 1670 can transition clinician application 322 from personal user interface 1650 to a subsequent interface.

[0183] Fig.12DA cooking report interface 1680 is shown, which is an example of a detailed critical event report for cooking. Cooking report interface 1680 may include information about cooking events, including a summary 1681 that presents the name of the corresponding critical event category (e.g., "cooking"), the number of times the cooking event occurred, and the percentage of unloading device usage during the cooking event. Cooking report interface 1680 can present a detailed event report 1682, which can display the day of the week for each event, the start time and duration of each event, whether a collision occurred during the corresponding cooking event (which can be a rapid impact to the user's limbs), and the type of auxiliary motion used during the event (if any). Similar reporting interfaces can be used for other activities.

[0184] Fig.12E A user history interface 1690 is shown that may present an informational message 1692 that includes a date range for the history report presented on the user history interface 1690, an overall adherence table 1694, and an appointment history table 1698. The overall adherence table 1694 may present a bar graph summary 1696 that presents ODU time and risk time, for example, per week during the reporting duration. The appointment history table 1698 may display the dates of previous appointments, the ODUs during the time period prior to the appointment, and the average daily risk time during the time period prior to the appointment. The appointment history table 1698 may have an optional appointment element 1699 associated with each previous appointment that, when selected by the clinician, may transition the clinician application 322 from the user history interface 1690 to the Fig.12F , which can present the clinician with the daily ODU time and risk time for each day during the reporting duration. As described herein, this information can allow the clinician to quickly and reliably analyze the user's lifestyle, determine the user's compliance with wearing the unloading device, healing trajectory, or risk of exacerbating an existing ulcer or forming a new ulcer, or make appropriate adjustments to treatment.

[0185] Figure 12GAnother person user interface 1740 similar to personal user interface 1650 is shown, but it presents error information for the user. The user identifier 1742 on the personal user interface 1740 can include the user's name, picture, age, gender or other medical conditions. The personal user interface 1740 can present a report menu 1744, which can present summary information about available reports and user's reservation history records. The report menu 1744 can present a report status indicator 1746, which can remind the clinician that one or more reports may be inaccurate or incomplete. When the clinician selects any optional element in the report menu 1744, the clinician application can be transformed from the personal user interface 1740 to another user-related interface. The personal user interface 1740 can present a user management menu 1748, which can make the presentation of management appointment interface, management hardware interface or deactivation application interface when selected by the clinician. Personal user interface 1740 may include a first warning indicator 1743 and a second warning indicator 1745 , which may alert the clinician that a problem has been detected in a hardware component of the activity monitoring device 120 or the offload monitoring device 132 .

[0186] Any feature, component, image, design, or other detail of any user interface or aspect of a user interface shown or described herein may be additionally or alternatively included in any other user interface or aspect of a user interface shown or described herein to form an additional user interface.

[0187] The user interface shown and described herein may include one or more interface controls, which may be selected, for example, using the user interface 316 of the user operating device 310 or the user interface 326 of the clinician operating device 320. The user interface may be output to present the user application 312 of the user operating device 310 or the clinician application 322 of the clinician operating device 320. The user controls shown are merely illustrative examples, and may vary in other aspects. For example, buttons, drop-down boxes, selection boxes, text boxes, check boxes, slider controls or other user interface controls may be replaced with other types of user interface controls that provide the same or similar functions. In addition, the interface controls may be combined into or divided into other groups of interface controls so that very different appearance user interfaces may be provided for similar functions or the same functions. In addition, each interface control may be selected by the user using one or more input options (for example, mouse, touch screen input or keyboard input, and other interface input options).

[0188] Computer system components

[0189] Fig.13 shows the available Figure 3A computer system 700 including one or more devices (eg, a user-operated device 310 or a clinician-operated device 320), systems (eg, a device management system 340), servers, etc. within a computing environment 300.

[0190] like Fig.13 As shown in , the computer system 700 may include (i) a processor (CPU) 710, (ii) an input / output device 720 configured to allow a user to input and output information and interact with the computer system 700, as well as to transmit and receive data or capture data using one or more sensors such as an image sensor, (iii) a read-only memory device (ROM) 730 or equivalent to provide non-volatile storage of data or programs, (iv) a display 750, such as a computer monitor or other display device, (v) a network connection 740 and a network interface 742, which are configured to allow the computer system 700 to connect to other systems, servers or portable devices, as well as a memory space 760 and a database 790. The database 790 may be further divided or distributed into sub-databases 790A-790N, wherein the sub-databases store feature or function specific information associated with a particular feature or function. Fig.13 The various components shown in can be incorporated into the computer 770. It should be noted that Fig.13 The various components shown in (including database 790) are typically included as part of computer 770, however, in some embodiments, they may be external to computer 770. For example, database 790 may be external to computer 770 and may be a separate database computer system or part of a networked database system. In some cases, computer system 700 may be a computing device such as a desktop computer, a mobile phone, or a server.

[0191] The memory space 760 may include DRAM, SRAM, FLASH, a hard drive, or other memory storage device (e.g., media drive 780) configured to store an operating system 762, application programs 764, and data 768, and the memory space 760 may share, allocate, or overlap with the memory storage capacity of the database 790. In some embodiments, the memory space 760 may include the database 790, or in some embodiments, the database 790 may include the data 768 as shown in the memory space 760. The data stored in the memory space 760 or the database 790 may include information such as athletic data, pairing program information, data processing routines, or other types of data described herein.

[0192] Other variations and terms

[0193] Many other variations other than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain actions, events, or functions of any algorithm described herein may be performed in a different order, may be added, merged, or omitted entirely (e.g., not all described actions or events are necessary to practice the algorithm). In addition, in some embodiments, actions or events may be performed simultaneously, such as by multithreading, interrupt handling, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes may be performed by different machines or computing systems that may work together.

[0194] One or more user inputs described in the present disclosure may be received using one or more different mechanisms. For example, a user may select a user interface control using one or more input options (e.g., a mouse, touch screen input, or keyboard input), as well as other user interface input options. The user interface control selected by the user may include one or more of a button, a drop-down box, a selection box, a text box, a check box, a slider control, or other user interface controls.

[0195] Although certain features are described in the context of controlling pairing, features of the present disclosure may be applied to controlling communication permissions in types of system communications other than pairing.

[0196] The various illustrative logic blocks, modules, and algorithmic steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been generally described above with respect to their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The described functions may be implemented in different ways for each specific application, but such implementation decisions should not be interpreted as departing from the scope of the present disclosure.

[0197] The various illustrative logic blocks and modules described in conjunction with the embodiments disclosed herein may be implemented or executed by a machine, microprocessor, state machine, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A hardware processor may include a circuit or digital logic circuit configured to process computer executable instructions. In another embodiment, the processor includes an FPGA or other programmable device that performs logical operations without processing computer executable instructions. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor), multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. The computing environment may include any type of computer system, including but not limited to a microprocessor-based computer system, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computing engine within an appliance, and the like.

[0198] The steps of the methods, processes, or algorithms described in conjunction with the embodiments disclosed herein may be directly included in hardware, in a software module stored in one or more storage devices and executed by one or more processors, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of non-transitory computer-readable storage medium, medium, or physical computer storage device known in the art. An example storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be an integral part of the processor. The storage medium may be volatile or non-volatile. The processor and the storage medium may reside in an ASIC.

[0199] Unless otherwise expressly stated, or otherwise understood in the context of use, conditional language used herein, such as "may," "might," "could," "for example," and the like, is generally intended to express that certain aspects include, while other aspects do not include, certain features, elements, or statements. Thus, such conditional language is generally not intended to imply that one or more aspects require features, elements, or statements in any way, or that one or more aspects must include logic for determining whether these features, elements, or statements are included in any particular embodiment or to be performed in any particular embodiment with or without author input or prompting. The terms "include," "comprise," "have," and the like are synonymous and are used inclusively in an open-ended manner and do not exclude additional elements, features, actions, operations, and the like. In addition, the term "or" is used in its inclusive sense (rather than in its exclusive sense) so that when used, for example, to connect a list of elements, the term "or" represents one, some, or all of the elements in the list. In addition, in addition to having its ordinary meaning, the term "each" used herein may represent any subset of a set of elements to which the term "each" is applied.

[0200] Unless expressly stated otherwise, conjunctive language such as the phrase "at least one of X, Y, and Z" is understood in context as generally used to indicate that an item, term, etc. can be X, Y, or Z. Thus, such conjunctive language is generally not meant to imply that certain embodiments require the presence of at least one of X, at least one of Y, and at least one of Z.

[0201] Language of degree as used herein, such as the terms "approximately," "about," "substantially," and "roughly" as used herein, refers to a value, amount, or characteristic that is close to a stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms "approximately," "about," "substantially," and "roughly" may refer to an amount that is within less than 10%, less than 5%, less than 1%, less than 0.1%, and less than 0.01% of the stated amount. As another example, in certain embodiments, the terms "substantially parallel" and "roughly parallel" refer to a value, amount, or characteristic that deviates from exact parallelism by less than or equal to 15 degrees, 10 degrees, 5 degrees, 3 degrees, 1 degree, or 0.1 degrees.

[0202] Although the above detailed description has shown, described and pointed out novel features applicable to various embodiments, it should be understood that various omissions, substitutions and changes in the form and details of the described devices or algorithms may be made without departing from the spirit of the present disclosure. As will be appreciated, certain embodiments described herein may be embodied in a form that does not provide all of the features and benefits set forth herein, as some features may be used or practiced separately from other features.

Claims

1. A non-transitory computer-readable medium having an application stored thereon, the application, when executed by a processor of an electronic device, causing the processor to perform a process, the process comprising: receiving, by the communication interface, motion data from the motion sensor, the motion data indicating motion of a user while wearing the motion sensor; Transmitting the motion data to a server via the communication interface; receiving, by the communication interface from the server, the motion data indicating a time when the user's foot experienced a load force that risked adversely affecting an existing ulcer on the foot or risked causing a new ulcer on the foot; determining a geographic location of the motion sensor at a time when the foot experiences the load force; displaying the time and the geographic location to the user on a display; requesting the user to identify, on the display, an activity in which the user participated at the time and at the geographic location; as well as The activity is transmitted to the server for storage to a memory device in association with the time and the geographic location.

2. The non-transitory computer-readable medium of claim 1, wherein the motion data is received from the motion sensor when the communication interface is no more than 100 meters from the motion sensor, and the motion data is transmitted to the server via a computer network.

3. The non-transitory computer-readable medium of claim 2, wherein the computer network comprises a cellular network.

4. The non-transitory computer-readable medium of any one of claims 1-3, wherein the motion sensor comprises an accelerometer and a magnetometer, and the motion data comprises sensor data from the accelerometer and the magnetometer.

5. The non-transitory computer-readable medium of any one of claims 1-3, wherein the determining comprises determining the geographic location from a physical location of the processor at the time.

6. The non-transitory computer-readable medium of claim 5, wherein the determining comprises determining the physical location using a global positioning system (GPS) receiver or communications received via a computer network.

7. The non-transitory computer-readable medium of any one of claims 1-3, wherein the displaying comprises displaying the time and the geographic location together on the display.

8. The non-transitory computer-readable medium of any one of claims 1-3, wherein the time indicates, based at least on the motion data, when the foot is experiencing a load force that is at risk of adversely affecting the existing ulcer and when the user is determined not to be wearing an offloading device.

9. The non-transitory computer-readable medium of any one of claims 1-3, wherein the type of activity comprises a travel type, an exercise type, a leisure type, a home activity type, or a work type.

10. The non-transitory computer-readable medium of claim 9, wherein the travel type comprises in a car, on a bus, on a bicycle, on a train, on an airplane, or on foot.

11. The non-transitory computer-readable medium of claim 9, wherein the types of exercise include walking the dog, running, swimming, using a machine, lifting weights, golfing, bowling, or stretching.

12. The non-transitory computer-readable medium of claim 9, wherein the type of leisure includes shopping, entertainment, sightseeing, socializing, walking, or dining out.

13. The non-transitory computer-readable medium of claim 9, wherein the household activity type comprises sitting, lying down, going up and down stairs, gardening, cleaning, or cooking.

14. The non-transitory computer-readable medium of claim 9, wherein the work type comprises physical labor or driving.

15. The non-transitory computer-readable medium of any one of claims 1-3, wherein the process includes requesting the user to identify the activity from a plurality of different activity types that the user previously indicated as types of activities in which the user typically engages.

16. A method for collecting motion data from a motion sensor and processing event information associated with the motion data, the method comprising: receiving, by the communication interface, motion data from the motion sensor, the motion data indicating motion of a user while wearing the motion sensor; Transmitting the motion data to a server via the communication interface; receiving, by the communication interface from the server, the motion data indicating a time when the user's foot experienced a load force that risked adversely affecting an existing ulcer on the foot or risked causing a new ulcer on the foot; determining, by a processor, a geographic location of the motion sensor at a time when the foot experiences the load force; displaying the time and the geographic location to the user on a display; requesting the user to identify, on the display, an activity in which the user participated at the time and at the geographic location; as well as The activity is transmitted to the server for storage to a memory device in association with the time and the geographic location.

17. The method of claim 16, wherein the motion data is received from the motion sensor when the communication interface is no more than 100 meters from the motion sensor, and the motion data is transmitted to the server via a computer network.

18. The method of claim 17, wherein the computer network comprises a cellular network.

19. The method of any one of claims 16-18, wherein the motion sensor comprises an accelerometer and a magnetometer, and the motion data comprises sensor data from the accelerometer and the magnetometer.

20. The method of any of claims 16-18, wherein the determining comprises determining the geographic location from a physical location of the processor at the time.

21. The method of claim 20, wherein the determining comprises determining the physical location using a Global Positioning System (GPS) receiver or communications received via a computer network.

22. The method of any one of claims 16-18, wherein the time, based at least on the motion data, indicates when the foot is experiencing a loading force that risks adversely affecting the existing ulcer.

23. The method of any of claims 16-18, further comprising receiving the activity from the user via user input.

24. The method according to any one of claims 16-18, wherein the type of activity comprises a travel type, an exercise type, a leisure type, a hobby type or a work type.

25. The method of claim 24, wherein the travel type comprises in a car, on a bus, on a bicycle, on a train, on an airplane, or walking.

26. The method of claim 24, wherein the types of exercise include walking the dog, running, swimming, using a machine, lifting weights, golfing, bowling, or stretching.

27. The method of claim 24, wherein the leisure type includes shopping, entertainment, sightseeing, socializing, walking, or dining out.

28. The method of claim 24, wherein the hobby types include sitting, lying down, climbing stairs, gardening, cleaning, or cooking.

29. The method of claim 24, wherein the type of work comprises manual labor or driving.

30. The method of any of claims 16-18, wherein the request comprises requesting the user to identify the activity from a plurality of different activity types that the user previously indicated as activity types that the user typically engages in.

31. A device for collecting motion data from a motion sensor and processing event information associated with the motion data, the device comprising: a communication interface configured to communicate with the motion sensor and the server; as well as A processor configured to: receiving motion data from the motion sensor, the motion data indicating motion of a user while wearing the motion sensor, transmitting the motion data to the server, receiving from the server the motion data indicating a time when the user's foot was subjected to a load force that risked adversely affecting an existing ulcer on the foot or risked causing a new ulcer on the foot, determining a geographic location of the motion sensor at a time when the foot experiences the load force, outputting the time and the geographic location for presentation to the user, requesting the user to identify an activity in which the user participated at the time and the geographic location, and The activity is transmitted to the server for storage to a memory device in association with the time and the geographic location.

32. The apparatus of claim 31 , further comprising: a housing supporting the communication interface and the processor; a display configured to present the time and the geographic location; or A user input is configured to receive the activity from the user.

33. A system for collecting motion data from a motion sensor and processing event information associated with the motion data, comprising: An apparatus according to claim 31 or 32; as well as The motion sensor or the server.

Images