Patent ID: 12239454

DETAILED DESCRIPTION

Introduction to User Activity Monitoring

Activities of a user may be desirably monitored by an activity monitoring device for a variety of reasons, including wound prevention and monitoring. In one example, the activities of a user can be monitored when the user may be prone to or already have a wound, such as a pressure ulcer. Information gathered by the activity monitoring device about the activities of the user can be helpful for assisting with prevention or treatment of the pressure ulcer. In addition, information gathered by the activity monitoring device about the activities can be useful for checking compliance with a treatment regimen.

Some aspects disclosed herein relate to wound monitoring or therapy for a human or animal body. Therefore, any reference to a wound herein can refer to a wound on a human or animal body, and any reference to a body herein can refer to a human or animal body. The disclosed technology may relate to preventing or minimizing damage to physiological tissue or living tissue, or to the treatment of damaged tissue (for example, a wound as described herein).

As used herein the expression “wound” may include an injury to living tissue that may be caused by a cut, blow, or other impact, typically one in which the skin is cut or broken. A wound may be a chronic or acute injury. Acute wounds occur as a result of surgery or trauma. They move through the stages of healing within a predicted timeframe. Chronic wounds typically begin as acute wounds. The acute wound can become a chronic wound when it does not follow the healing stages resulting in a lengthened recovery. It is believed that the transition from acute to chronic wound can be due to a patient being immuno-compromised.

Chronic wounds may include for example: venous ulcers (such as those that occur in the legs), which account for the majority of chronic wounds and mostly affect the elderly, diabetic ulcers (for example, foot or ankle ulcers), peripheral arterial disease, pressure ulcers, or epidermolysis bullosa (EB).

Examples of other wounds include, but are not limited to, abdominal wounds or other large or incisional wounds, either as a result of surgery, trauma, sterniotomies, fasciotomies, 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, stoma, surgical wounds, trauma and venous ulcers or the like.

Wounds may include a deep tissue injury. Deep tissue injury is a term proposed by the National Pressure Ulcer Advisory Panel (NPUAP) to describe a unique form of pressure ulcers. These ulcers have been described by clinicians for many years with terms such as purple pressure ulcers, ulcers that are likely to deteriorate and bruises on bony prominences.

Wound may also include tissue at risk of becoming a wound as discussed herein. For example, tissue at risk may include tissue over a bony protuberance (at risk of deep tissue injury/insult) or pre-surgical tissue (for example, knee tissue) that may have the potential to be cut (for example, for joint replacement/surgical alteration/reconstruction).

Some aspects relate to methods of monitoring or treating a wound with the technology disclosed herein in conjunction with one or more of the following: advanced footwear, turning a patient, offloading (such as, offloading diabetic foot ulcers), treatment of infection, systemix, antimicrobial, antibiotics, surgery, removal of tissue, affecting blood flow, physiotherapy, exercise, bathing, nutrition, hydration, nerve stimulation, ultrasound, electrostimulation, oxygen therapy, microwave therapy, active agents ozone, antibiotics, antimicrobials, or the like.

Alternatively or additionally, a wound may be treated using topical negative pressure or traditional advanced wound care, which is not aided by the using of applied negative pressure (may also be referred to as non-negative pressure therapy).

Although the present disclosure may refer to pressure ulcers, foot ulcers, or the like, the systems and methods disclosed herein can be used for preventing, monitoring, or treating any type of skin injury or wound, such as venous leg ulcer.

User Activity Monitoring System

FIG.1illustrates a user activity monitoring system100including an activity monitoring device120attached to a body part110. The activity monitoring device120can be attached to the body part110using a strap, adhesive, or other coupling mechanism and may be worn on or supported by the body.

The body part110can be a leg of a user that includes a knee112and a foot114. As illustrated, the activity monitoring device120can be supported by the body part110at a position between the knee112and the foot114, such as proximate to the knee112. In other aspects, the activity monitoring device120can be supported by another part of the body part110, such as above the knee112or elsewhere. The activity monitoring device120can monitor and record activities (for instance, walking, jumping, sitting, laying down, running, squatting, or standing) of the body part110, such as from a position, movement, or orientation of the activity monitoring device120or one or more other sensors of the activity monitoring device120. The activity monitoring device120can, for example, be used for loading monitoring of loading of the foot114. In certain implementations, multiple body parts can be monitored by the activity monitoring device120, and different sensors can be used for monitoring different body parts.

The body part110is shown wearing and being partly covered by an offloading device130. The offloading device130can support the body part110and reduce a pressure on the foot114when the user may be standing or engaging in other activities. An offloading monitoring device132can be attached to the offloading device130. The offloading monitoring device132can be the same as or similar to the activity monitoring device120and monitor and record activities of the offloading device130. The offloading monitoring device132can be supported by the offloading device130using a strap, adhesive, or other coupling mechanism. The offloading monitoring device132can be attached to an inner surface or outer surface of the offloading device130. Although not shown inFIG.1, the offloading monitoring device132may be attached to an offloading device that is not worn by the user (for example, a cane or a walker). Moreover, the activity monitoring device120can be worn regardless of whether the offloading device130may be worn.

The user activity monitoring system100can additionally or alternatively include one or more of the activity monitoring device120or the offloading monitoring device132at other positions, such as at a position supported by the offloading device130, another part of the body part110, another device not worn such as a cane or a walker, or elsewhere. The one or more additional or alternative of the activity monitoring device120or the offloading monitoring device132can be the same as or similar to the activity monitoring device120may monitor and record activities of the offloading device130, the another part of the body part110, or the body.

FIG.2illustrates example components of the activity monitoring device120. The activity monitoring device120can include a housing200, a controller202, a memory device204, a user interface206, a power source208, one or more sensors210, and a communication interface212that are configured to communicate, such as electrically, with one another. The power source208can provide power to one or more components of the activity monitoring device120.

One or more of the components of the activity monitoring device120can be contained in or supported by the housing200. The housing200can be composed of a top portion and a bottom portion that are sealed together, and the top portion or the bottom portion can be hard or soft. The housing200can be flexible and have a mechanical structure and design features that provide for a shouldered keyway alignment of components within the housing200. The housing200can support a circuit board on its inside and on which one or more components of the activity monitoring device120may be positioned.

The housing200can be made by stereolithography (SLA) or polyjet from photopolymer 3D printing material or by 3D printing from an engineering resin with a shorehardness of80A. The housing200can include an elastomer, a thermoplastic elastomer, or be constructed by injection molding. The molded parts of the housing200can be made from liquid silicone rubber in white. An adhesive (for example, one for attaching plastics and elastomeric materials) can be used to glue the top and bottom portions of the housing200together, and a wide range of other adhesives (for example, cyanoacrylates, silicones, epoxies, hydrogels, hydrocolloids, sealant systems) or other techniques (for example use of double-sided adhesive tapes, ultrasonic welding, staking) can be used.

The controller202can control operations of one or more other components (for instance, the memory device204, the user interface206, the power source208, the one or more sensors210, or the communication interface212) of the activity monitoring device120according at least to instructions stored in the memory device204. The controller202can, for instance, control monitoring of loading of the body part110with a weight of the body or positioning of the body part110and record data indicative of loading of the body part110or positioning of the body part110to the memory device204.

The user interface206can include one or more output elements, such as visual feedback devices (for example, light emitting diodes), haptic feedback devices, or audio devices (for example, speakers), that provide user outputs to a user. The one or more output elements can convey status information to the user like whether the activity monitoring device120is successfully functioning or has successfully configured communication with another device. The user interface206can include one or more input elements, such as buttons, switches, dials, touch pads, microphones, or touch screens, for receiving user inputs for configuring the activity monitoring device120. In some aspects, the user interface206may have no more than one user input element, such as a button, for receiving user inputs to activate and deactivate the activity monitoring device120or performing one or more other functions.

The one or more sensors210can be used to detect and monitor a motion of the activity monitoring device120or other characteristics of or around the activity monitoring device120. The one or more sensors210can be used to detect and monitor activities of the user of the activity monitoring device120that include, for instance, a loading or positioning of the body part110. The one or more sensors210can include one or more accelerometers, gyroscopes, magnetometers, impedance sensors, thermistors, pressure sensors, or optical sensors, among other types of sensors. The one or more sensors210can be positioned proximate to the body part110or may be remote from the body part110yet usable to monitor characteristics of the body part110.

The communication interface212can be used to communicate with other devices, such as wirelessly via radio waves and according to a Bluetooth™ protocol like Bluetooth™ Low Energy or another protocol. The communication interface212can, for example, communicate and pair with other devices and transmit device usage or sensor data like alarms, monitored loading or positioning, or changes to a monitoring or therapy program performed by the activity monitoring device120to the other devices. The communication interface212can be used to receive data, including commands, from the other devices. The communication interface212can permit communication with (for example, transfer of data to or processing commands from) another device once a communication channel has been configured for communication with the another device (for example, by device pairing). The communication interface212may, in some aspects, be unable to communicate farther than 10 meters, 30 meters, or 100 meters away from the communication interface212.

FIG.3illustrates a computing environment300that includes the activity monitoring device120and the offloading monitoring device132. The computing environment300shows the activity monitoring device120and the offloading monitoring device132in communication with a user operation device310and a clinician operation device320, as well as the user operation device310and the clinician operation device320in communication with a device management system340via a network330.

The user operation device310can be operated by a user, such as a wearer, of the activity monitoring device120and the offloading monitoring device132. The user operation device310can permit the user to use the user operation device310to collect, process, review, or transmit the data gathered by the activity monitoring device120and the offloading monitoring device132. On the other hand, the clinician operation device320can be operated by a clinician for the user, such as an individual who supervises, assists, or cares for the user that uses the activity monitoring device120and the offloading monitoring device132. The clinician operation device320can permit the clinician to use the clinician operation device320to collect, process, review, or transmit the data gathered by the activity monitoring device120and the offloading monitoring device132.

The user operation device310and the clinician operating device320may each be a computing device such as a smart phone, a tablet computer, or a desktop computer. In some aspects, the user operation device310and the clinician operating device320can receive, send, present, and access data gathered by the activity monitoring device120and the offloading monitoring device132or data determined therefrom, but may not process the data gathered by the activity monitoring device120and the offloading monitoring device132to analyze the characteristics of the data (such as to identify from the data when the user used an offloading device or calculate a duration of activity engaged in by the user.

The user operation device310can include a user application312, a communication interface314(which can, for instance, include any one or more of the features of the communication interface212), and a user interface316(which can, for instance, include any one or more of the features of the user interface206). The user application312can be program that is executed by processor of the user operation device310. The user application312can enable the user operation device310to communicate via the communication interface314with the activity monitoring device120, the offloading monitoring device132, and the device management system340. The user application312may receive, collect, process, review, or transmit (i) data gathered or determined by the activity monitoring device120and the offloading monitoring device132, such as motion data, alarms, monitored loading or positioning, or changes to a monitoring or therapy program, (ii) data collected or determined by the user application312, such as user observations, goal information, or identifications of activities engaged in by a user, or (iii) data collected or determined by the device management system340, such as a duration of time that the user was active, a portion of time that the user used an offloading device, or an amount of time at which an injury of the user may be at risk due to activity by the user or nonuse of the offloading device. The user application312can moreover present to the user one or more graphical user interfaces, such as one or more of the graphical user interfaces described herein, with the user interface316, such as on a display or a touchscreen of the user interface316.

The user application312can be used to gather information from the user to assist with understanding what type of activity was engaged in by the user when the foot of the user may have experienced a force which risked adversely impacting an existing ulcer on the foot or risked causing a new ulcer on the foot. The user application312can receive from the device management system340a time that the motion data from the activity monitoring device120indicates a foot of the user experienced a force which risked adversely impacting an existing ulcer on the foot or risked causing a new ulcer on the foot, and the user application312can determine a geographic location of the user operation device310(such as from a global positioning system (GPS) receiver of the user operation device310or a communication received by the user operation device310via the network330) that may be indicative of a geographic location of the activity monitoring device120at the time. The user application312may output the time and the geographic location of the user operation device310along with a request that the user identify the type of activity engaged in by the user at the time and the geographic location. The type of activity can, for example, include a type of transportation, a type of exercise, a type of leisure, a type of hobby, or a type of work. The request may list a set of types of activities commonly engaged in by the user to assist in selecting the type of activity engaged in by the user.

The user application312can include a functionality lock out that causes certain functionality of the user application312to be disabled (such as by preventing access to the functionality) prior to a check-in time for the user. The check-in time can be a time provided by the user when the user anticipates that the user will settle down and likely not engage in additional activity which may adversely impact an existing or new foot ulcer. The functionality lock out can assist with controlling a timing of engagement by the user with the user application312, such as until after the user may have settled down for a day, to help ensure a complete collection of requested information from the user for the day. The functionality can, for instance, include an ability of the user to respond to prompts, such as regarding the user's thoughts or observations on the day or the user's feelings. Although the functionality lock out may lock out some functionality, other functionality of the user application312can be available prior to the check-in time for access or completion by the user prior to the check-in time.

The user application312can include aspects and interfaces that seek to increase the amount or frequency of user engagement with the user application312. The user application312may request contextual information (such as an identification of an activity engaged in by the user while wearing the activity monitoring device120or an indication by the user of how the user is feeling) to assist with tracking or understanding why the foot of the user may have experienced a force which risked adversely impacting an existing ulcer on the foot or risked causing a new ulcer on the foot. From the contextual information, such as a timing or frequency of receipt of the contextual information, the user application312can determine an engagement metric for the user that may be indicative of an amount of engagement by the user with the user application312. The engagement metric can, in turn, be used by the user application312to adjust a graphical interface generated by the user application312and presented to the user by the user interface316.

The clinician operation device320can include a clinician application322, a communication interface324(which can, for instance, include any one or more of the features of the communication interface212), and a user interface326(which can, for instance, include any one or more of the features of the user interface206). The clinician application322can be program that is executed by processor of the clinician operation device320. The clinician application322can enable the clinician operation device320to communicate via the communication interface324with the activity monitoring device120, the offloading monitoring device132, and the device management system340. The clinician application322may receive, collect, process, review, or transmit (i) data gathered or determined by the activity monitoring device120and the offloading monitoring device132, such as motion data, alarms, monitored loading or positioning, or changes to a monitoring or therapy program, (ii) data collected or determined by the user application312, such as user observations, goal information, or identifications of activities engaged in by a user, or (iii) data collected or determined by the device management system340, such as a duration of time that the user was active, a portion of time that the user used an offloading device, or an amount of time at which an injury of the user may be at risk due to activity by the user or nonuse of the offloading device. The clinician application322can present to the clinician one or more graphical user interfaces, such as one or more of the graphical user interfaces described herein, with the user interface326, such as on a display or a touchscreen of the user interface326.

In some aspects, the clinician operation device320may not directly communicate with the activity monitoring device120or the offloading monitoring device132. Instead, the clinician operation device320may receive any data collected by or associated with the activity monitoring device120and offloading monitoring device132from the device management system340through the user operation device310. Such a design may desirably limit the number of devices (other than the user operation device310) that may receive data directly from the activity monitoring device120and the offloading monitoring device132and thereby enhance the security of and limit access to the data.

The device management system340can be a computing device, such as a server, and include a communication management system342, a data processing system344, and a data storage346that may be in communication with one another. The device management system340may, for instance, be constructed partly or entirely of a server infrastructure or a cloud architecture, such as using a cloud infrastructure provided by Amazon Web Services™ (AWS), Microsoft™ Azure™, Google Cloud Platform™ (GCP), or Oracle™ Cloud Infrastructure (OCI). The server infrastructure and the cloud infrastructure can be compliant with the requirements of HIPAA (Health Insurance Portability and Accountability Act of 1996) and provide data privacy and security protections in view of the potentially sensitive nature of the data collected, processed, or determined by the device management system340.

The communication management system342may permit the device management system340to communicate over the network330with the user operation device310and the clinician operation device320. The communication management system342can include an application programming interface (API), such as a cloud API, to facilitate its communications.

The data processing system344can collect, process, present, store (such as in the data storage346), or transmit the data gathered or determined by the activity monitoring device120and the offloading monitoring device132(such as motion data, alarms, monitored loading or positioning, or changes to a monitoring or therapy program) and the data collected or determined by the user application312(such as user observations, goal information, or identifications of activities engaged in by a user). For example, the data processing system344can process the data gathered by the activity monitoring device120and the offloading monitoring device132to determine an activity likely engaged in by the user (such as sitting/standing, driving a car, walking, or laying down with foot elevated) during various periods of time over which the data was gathered, as well as whether the user likely wore an offloading device (such as from a comparison of the motion data from the activity monitoring device120and the offloading monitoring device132) during various periods of time over which the data was gathered. The determined likely activity or use of the offloading device may be shared by the device management system340with the user operation device310or the clinician operation device320. As another example, the data processing system344can process the data gathered by the activity monitoring device120and the offloading monitoring device132to identify events of interest, such as events that may indicate excessive pressure being placed on the body part110, and may share the events of interest with the user operation device310or the clinician operation device320.

The network330can be a computer network, such as a cellular communications network. Although the network330is shown as one connected network, the network330can be subdivided into one or more separate networks which may not directly communicate with one another. For example, the device management system340can communicate with the user operation device310via a separate and different network from the network that the device management system340uses to communication with the clinician operation device320.

Although certain data processing in the computing environment300may be described as being performed by the activity monitoring device120, the offloading monitoring device132, the user operation device310, the clinician operation device320, or the data processing system344, the certain data processing can be shifted to a different device or system in the computing environment300. For example, the user operation device310may be described as not processing the motion data provided by the activity monitoring device120and the offloading monitoring device132and can instead rely on the data processing system344to analyze the motion data; however, the user operation device310can additionally or alternatively analyze the motion data using similar or different approaches or algorithms to the data processing system344.

FIG.4illustrates a functionality lockout process400for disabling and enabling a functionality of an application, such as the user application312of the user operation device310. For convenience, the functionality lockout process400is described in the context of the computing environment300, but may instead be implemented in other components or systems described herein, or by other computing systems not shown. The functionality lockout process400can advantageously, in certain implementations, restrict the functionality of the user application312until a set to time try to encourage specific user engagement and collection of all desired or requested data from the user.

At block410, the functionality lockout process400can disable a designated functionality of the application. The designated functionality may be a first subset of the functionality of the application, and a second subset of the application may not be disabled by the functionality lockout process400. The functionality to be disabled can be designated by a programming in the application or responsive to changes in a flag in the memory device where the flag may be controlled by the application. For example, the designated functionality can include an ability of the user of the user operation device310to (i) be presented, by the user application312, with prompts to which the user is requested to reply or (ii) provide inputs to the user application312by responding to the prompts. The prompts, for instance, may request that the user indicate how the user is feeling or the condition of the user's ulcer. Other examples of the designated functionality that may be disabled can include a functionality for accessing certain information within or through the user application312or a functionality associated with how the user responds to inputs to the user application312(such as by dismissing certain requests or providing one or more alternative prompts in place of the prompts).

At block420, the functionality lockout process400can determine a time at which to request information from the user with the application. For example, the user application312may request via the user interface316that the user provide a check-in time at which the user is requested to provide information. The check-in time can be a time each day (or some other repeated time basis, such as hourly, every N hours, every N days, or weekly where N may be an integer) and may be in the afternoon or evening in some implementations. The check-in time can be a time provided or selected by the user when the user anticipates that the user will settle down and likely not engage in additional activity which may adversely impact an existing or new ulcer. The check-in time may be indicated to the user or understood by the user to be the time for requesting of certain information like contextual information for motion data gathered by the activity monitoring device120, such as by identifying a type of activity associated with an event risked adversely impacting an existing ulcer on a foot the user or risked causing a new ulcer on the foot. The event can be an application of force to the foot when the user was determined to have not been wearing an offloading device. Additionally or alternatively, the user application312can request that the user interact with the user application312in a desired manner at the check-in time.

At block430, the functionality lockout process400can remain on hold until the time at which to request information from the user has been reached (or at a time after such time). The user application312can continue to provide enabled functionalities during the on hold time, such as even to provide the information that is to be requested at the check-in time. One example of such an enabled functionality can be the ability to provide the contextual information for motion data gathered by the activity monitoring device120. Once the time has been reached, the functionality lockout process400can transition to block440.

At block440, the functionality lockout process400can enable the designated functionality of the application that may have been disabled at block410. The designated functionality can be enabled by a programming in the application due to expiration of a timer or responsive to the flag in the memory device where the flag may be controlled by the application according to a system time provided by the user operation device310. For example, the user application312can unlock the ability of the user of the user operation device310to (i) be presented, by the user application312, with prompts to which the user is requested to reply or (ii) provide inputs to the user application312by responding to the prompts. The user application312moreover may present the prompts responsive to enabling the designated functionality. In another example, the user application312can unlock the user's access to certain information within or through the user application312or adjust how the user application312responds to inputs to the user application312.

At block450, the functionality lockout process400can request the information from the user with the application. The user application312, for example, can request via the user interface316that the user provide the requested information. Additionally or alternatively, the user application312can request that the user interact with the user application312in the desired manner.

Upon completion of the functionality lockout process400, the designated functionality of the application may again be disabled. The functionality lockout process400may then, in some implementations, return to block430and remain on hold until the time at which to request information from the user has been again reached.

Although the time at which to request the information determined at block420may be indicated to the user or understood by the user to be the time for requesting of certain information like the contextual information, the functionality lockout process400can further serve to lock out the designated functionality of the user application312from the user until after the check-in time. This functionality lockout may be not communicated to the user at block420as a reason for requesting the check-in time. The functionality lockout may, however, be later communicated to the user in the event that the user attempts to access or deploy the designated functionality of the user application312prior to the check-in time. The functionality lockout can accordingly desirably allow the user to access the user application312throughout the day but push the user to at least interact with user application312at the check-in time.

FIG.5illustrates an activity identification process500for determining a type of activity engaged in by a user at a time and a geographic location of an event which risked adversely impacting an existing ulcer on a foot the user or risked causing a new ulcer on the foot. For convenience, the activity identification process500is described in the context of the computing environment300, but may instead be implemented in other components or systems described herein, or by other computing systems not shown. The activity identification process500can advantageously, in certain implementations, assist a user in timely recalling and providing information relevant to the treatment or prevention of an ulcer so that the information can be stored for later access, such as during a consultation between the user and a clinician.

At block510, the activity identification process500can receive motion data from a motion sensor. For example, the user application312can receive motion data, such as accelerometer or magnetometer data, from the activity monitoring device120via the communication interface314.

At block520, the activity identification process500can transmit the motion data to a server. For example, the user application312can transmit the motion data via the communication interface314to the community management system342of the device management system340. The user application312may forward the motion data from the activity monitoring device120without processing or may process, such as analyze or compress, the motion data prior to forwarding.

At block530, the activity identification process500can receive from the server and identification of a time that a force was applied to a limb of the user, such as when the user was determined to have not been wearing an offloading device. The application of force to the limb without use an offloading device may be referred to as an event. For example, the user application312can receive via the communication interface314a time (such as a particular instant or time range) from the device management system340that the motion data indicates a foot of the user experienced a force which risked adversely impacting existing ulcer on the foot or risked causing a new ulcer on the foot. The data processing system344of the device management system340may, for instance, have determined the time from analyzing the motion data.

At block540, the activity identification process500can determine a geographic location at or around a time that the force was applied to the name of the user. For example, the geographic location can be a location of the user operation device310, which may be assumed to match a location of the activity monitoring device120at or around the time. The geographic location can be determined by the user application312from a global positioning satellite (GPS) receiver of the user operation device310or a communication received by the user operation device310via the network330.

At block550, the activity identification process500can output the time and geographic location for presentation. For example, the user application312can output the time and geographic location on a graphical user interface for presentation on a display of the user interface316.

At block560, the activity identification process500can request from the user a type of activity engaged in by the user at the time and geographic location. For example, the user application312can output the request on the graphical user interface along with the time and geographic location at block550. The types of activities can include one or more types of activities described herein, such as a type of transportation (for instance, in a car, on a bus, riding a bike, on a train, on a plane, or walking), a type of exercise (for instance, dog walking, running, swimming, using machines, lifting weights, golfing, bowling, or stretching), a type of leisure (for instance, shopping, entertainment, sightseeing, socializing, going for a stroll, or eating out), a type of home activity (for instance, sitting down, lying down, walking up or down stairs, gardening, cleaning, or cooking), or a type of work (for instance, sitting, walking, manual labor, driving, or standing).

In reply to the request, the user may select one or more of the types of activities, such as by a selection of the one or more types of activities via the user interface316. In some aspects, the user may select only one of the types of activities. To assist the user with identifying one or more types of activities from numerous different types of activity, the user application312may initially present a list of types of activities identified by the user as being types of activities commonly engaged in by the user. The user application312can, in turn, receive the selected one or more types of activities.

At block570, the activity identification process500can transmit the type of activity to the server for storage with the time and geographic location. For example, the user application312can transmit the type of activity identified by the user to the communication management system342for processing by the data processing system344and storage in association with the time and geographic location in the data storage346.

FIG.6illustrates an interface control process600for controlling one or more aspects of a graphical user interface of an application, such as the user application312, according to an amount of engagement by the user with the user application312. For convenience, the interface control process600is described in the context of the computing environment300, but may instead be implemented in other components or systems described herein, or by other computing systems not shown. The interface control process600can advantageously, in certain implementations, encourage and reward engagement with the user application312by the user by changing graphical elements of the application responsive to the engagement.

At block610, the interface control process600can receive motion data from a motion sensor. For example, the user application312can receive motion data, such as accelerometer or magnetometer data, from the activity monitoring device120via the communication interface314.

At block620, the interface control process600can request from the user contextual information for the motion data. The user application312, for example, can request via the user interface316that the user provide contextual information for the motion data gathered by the activity monitoring device120. The contextual information can include an identification of a type of activity associated with an event which risked adversely impacting an existing ulcer on a foot the user or risked causing a new ulcer on the foot. The event can be an application of force to the foot when the user was determined to have not been wearing an offloading device.

At block630, the interface control process600can receive the contextual information from the user. For example, the user may select one or more of the types of activities, such as by a selection of the one or more types of activities via the user interface316. In some aspects, the user may select only one of the types of activities. To assist the user with identifying one or more types of activities from numerous different types of activity, the user application312may initially present a list of types of activities identified by the user as being types of activities commonly engaged in by the user. The user application312can, in turn, receive the selected one or more types of activities. The contextual information may include additional or alternative information, such as how the user felt that day or the condition of the user's foot or ulcer, or may include interactions between the user and the user application312that may be considered desirable engagement.

At block640, the interface control process600can determine an engagement metric for the user from the contextual information. The engagement metric can be indicative of an amount of engagement by the user with the application. The engagement metric can be determined from a count of a number of days (or other time periods) for which the user provided the contextual information or a number of consecutive days (or other time periods) for which the user provided the contextual information. For example, the user application312can determine the engagement metric from or to be a count of the number of days for which the user provided the contextual information. In instances where the user may have provided partial but not all requested conjectural information for a particular day, the user application312may not include that particular day in the count.

At block650, the interface control process600can adjust a user interface, such as a graphical user interface, responsive to the engagement metric. For example, the user application312can adjust a graphical user interface generated by the user application312and output the graphical user interface for presentation on a display of the user interface316. The graphical user interface may be adjusted, for instance, by (i) presenting to the user feedback that was selected from one set of feedback options rather than another set of feedback options, (ii) changing the formatting of information included in the graphical user interface, or (iii) incorporating one image rather than another image in the graphical user interface. The graphical user interface can be adjusted differently if the engagement metric satisfies a threshold than if the engagement metric does not satisfy the threshold.

The adjustment in the user interface at block650can desirably, in certain aspects, encourage the user to continue to engage with the user application312by, for example, providing positive feedback to the user (such as through permitting the user to advance through multiple levels, awarding the user virtual awards to celebrate accomplishments by the user, or increase an aesthetic appeal of the user application312), giving the user enhanced access to information (such as permitting the user to have additional information about treatment), or relaxing some expectations for engaging with the user application312(such as no longer requiring the user to provide certain information or requesting information in a more concise manner which permits the user to view fewer graphical user interfaces or provide fewer inputs).

FIGS.7A-7Gillustrate example user interfaces that can be presented by the user application312on the user interface316of the user operation device310and assist with introducing a user to operation of the user application312, engaging the user with the user application312, and initiating collection of information by the user application312.

FIG.7Aillustrates an example welcome interface1000that can present a customized message1002, such as a user's name or other user or wound-specific message, and an learn more element1004. The learn more element1004can, upon selection by a user, transition the user interface316to present a configuration interface1010, which is shown inFIG.7B.

The configuration interface1010can provide an introductory message1012and include selectable elements1014,1016, and1018. The selectable elements1014,1016, and1018can each transition the user application312to different configuration screens that may be part of a user onboarding or setup process for the user application312.

FIG.7Cillustrates an introduction interface1020that may be presented upon completion of application configuration through the configuration interface1010. The introduction interface1020can include a character1022(sometimes referred to as an avatar) that may be used to improve engagement with the user application312. As described further herein, the character1022may be customized by the user to adjust how the user receives information from the user application312. The introduction interface1020can have an instructional message1024and a next element1026. Selection of the next element1026by a user can trigger a transition by the user interface316to a travel type interface1030shown inFIG.7D.

As shown, the travel type interface1030can present a travel type request1032, which can indicate that the user is requested to identify one or more types of transportations which the user commonly utilizes to travel. The travel type interface1030can also include selectable travel type elements1034that permit the user to indicate one or more specific types of transportation to the user application312. This information can, for example, enable the user application312to determine the types of transportation utilized by the user to provide more efficient display of data or enable the user to more efficiently input event data. The travel type interface1030can include a selectable custom element1036, which may permit the user to provide a custom activity type input, and a selectable skip element1038, which may allow the user to elect not to select one or more of the selectable travel type elements1034or the selectable custom element1036.

The user application312may transition to an exercise type interface1040shown inFIG.7Eafter presenting the travel type interface1030. The exercise type interface1040can present an exercise type request1042, which can indicate that the user is requested to identify one or more types of exercise which the user commonly engages in. The exercise type interface1040can also include selectable exercise type elements1044that permit the user to indicate one or more specific types of exercise to the user application312. This information can, for example, enable the user application312to determine the types of exercise engaged in by the user to provide more efficient display of data or enable the user to more efficiently input event data. The exercise type interface1040can include a selectable custom element1046, which may permit the user to provide a custom exercise type input, and a selectable skip element1048, which may allow the user to elect not to select one or more of the selectable exercise type elements1044or the selectable custom element1046.

Although not illustrated, the user application312may transition to other activity type interfaces, including a leisure type interface, a home activity interface, a work type interface, or an assisted movement interface. These interfaces can be configured similarly to the travel type interface1030or the exercise type interface1040. The leisure type interface can present a leisure type request, which can indicate that the user is requested to identify one or more types of leisure that the user commonly engages in which, similar to the exercise type interface, can include selectable leisure type elements that facilitate the user's input of such activities. The work type interface can be similarly configured to the exercise and leisure type interface and may additionally be preceded by a work qualifier interface that requests a user to indicate whether the user will be working during the wearing of the activity monitoring device120. If the user indicates that the user will be wearing the activity monitoring device120, then the user may be presented with the work type interface which can request the user to identify one or more types of work activities that the user will be commonly be engaged in, along with respective selectable elements. If the user indicates that the user will not be wearing the activity monitoring device120, then the user application312may not present the work type interface and proceed to another user interface. The assisted movement interface can present an assisted movement request, which can indicate that the user is requested to identify one or more manners or modes of assisted movement that the user will use. As with the other activity interfaces, the assisted movement interface can include selectable assisted movement type elements that facilitate the user's input of what type of assisted movement device the user may use while wearing the activity monitoring device120.

FIG.7Fillustrates a user goal interface1050that can be used to collect additional goal data form the user for the user application312. As shown, the user goal interface1050can have a goal add element1056, which enables to user to enter a new goal, and selectable goal elements1054, each relating to a different goal provided by the user or a clinician for the user. This information can assist the user application312in tracking information about the performance of activities or behaviors by the user to assist the user in remaining accountable for actions, such as goals related to a therapy for the user.

FIG.7Gillustrates a check-in setting interface1060that can be used to determine a time at which the user may be prompted to provide information related to treatment. As shown, the check-in setting interface1060can present a time request1062, which may prompt for a time of day at which the user typically settles down and reduces his or her activity, and include selectable time elements1064, each corresponding to a different time at which the user may elect to check-in. The time provided by the user via the selectable time elements1064can assist the user application312in customizing the time that information related to therapy is requested from the user, as well as permit the user application312to disable certain of its functionality to encourage engagement with the user application312subsequent to the user setting down and reducing activity for the day. The check-in setting interface1060can include a next selectable element1068that may to allow the user to submit the time selected by the selectable time elements1064to the user application312and progress to a next user interface, such as a character select interface1070shown inFIG.7H.

The character select interface1070can permit the user to set a preferred character that will be used in various user interfaces of the user application312. The character select interface1070can present a character request1072, which asks a user to identify which character the user prefers, and changeable character elements1074. The character select interface1070can include a select element1078that allows the user to confirm the selection of the identified character element and advance to another user interface. The character selected by the user can, in some aspects, be the centerpiece of a user experience for the user application312and influence how the user application312engages with the user, such as the type of encouragement or language used in communicating information or progress to the user.

FIGS.8A-8Lillustrate example user interfaces that can be presented by the user application312on the user interface316of the user operation device310and may remind the user about providing information to the user application312and permit the user to input the information.

FIG.8Aillustrates a check-in status interface1080that prompts or reminds the user when a time for input of context information is scheduled to occur. The user application312can present the check-in status interface1080when a user attempts to access a certain user interface or input certain data, such as data or feedback regarding a state of wellness of the user as described with respect toFIGS.8D-8F, before the time permitted for such access or input has been reached (for example, the time at which such access or input may be permitted can start when the time to request information from the user has been reached as described with respect to block430ofFIG.4). The check-in status interface1080can present an informational message1084that can alert the user when the check-in time is scheduled. The time presented in the informational message1084can correspond with the time that the user input via the check-in setting interface1060during the onboarding or setup phase. The check-in status interface1080can present a status indicator1082that may provide visual feedback to the user when the time will occur or that the time has occurred, or that the ability for the user to activate or engage in a particular interaction with the user application312has not yet occurred. When the status indicator1082appears as a partial outline of a circle and without a token (illustrated as a center star) being filled as illustrated inFIG.8B, the status indicator1082may signify that the time has not yet been reached. A selectable confirmatory element1086, when selected by the user, cause a transition from the check-in status interface1080to a subsequent user interface.

FIG.8Billustrates an event status interface1090that can present the user with an informational message1094to inform the user of a number of events that may remain untagged (for instance, a count of events for which the user has not yet provided contextual information). As described herein, an event can, for example, be an application of force to a limb of a user when the user was determined to have not been wearing an offloading device. A status indicator1092can present visual feedback to the user and may be the same as or similar to the status indicator1082. A tag event element1096, when selected, can transition the user application312from the event status interface1090to another interface that may request that the user input the information regarding untagged events. The user application312may display the event status interface1090prior to the time being reached.

FIG.8Cillustrates a tag log initiation interface1100that prompts the user to check in to provide the contextual information. When the status indicator1102appears with a token (illustrated as a center star) being filled in and without an outline of a circle as illustrated inFIG.8A, the status indicator1082may signify that the time has been reached and that the user may now earn the token though completion of a check-in process (where the earning of the token may be a positive reward for the user and serve as a feedback for the user or clinician for tracking the user's utilization of the user application312). The user application312may display the tag log initiation interface1100responsive to the time being reached. An instructional message1104can prompt the user to check in and tag any untagged events. A tag events selectable element1106, when selected by the user, can trigger the user application312to transition from the tag log initiation interface1100to a subsequent user interface, such as a wellness feedback interface1110shown inFIG.8D, for inputting the contextual information. The presentation of the tag log initiation interface1100by the user application312can, for example, indicate an enabling of disabled functionality of the user application312, such as described respect to block440ofFIG.4, because the tag log initiation interface1100may provide access to at least some previously unavailable functionality of the user application312.

The wellness feedback interface1110may request that the user input information regarding a state of wellness of the user. The wellness feedback interface1110can request that user provide a level of happiness of the user on a five-unit scale from “not happy at all” to “very happy”. A wellness status bar1112can present a visual status indication of the user's progress through a check-in process, such as a portion of feedback questions of the check-in process that have been answered or are remaining for the user to answer. The wellness feedback interface1110can present a feedback question or prompt1114(regarding a first condition like “I feel . . . ”), list data input that is desired, and selectable wellness elements1116, each characterizing a different response to the feedback question or prompt1114. Additionally, a next selectable element1118can, upon selection by the user, transition the user application312from the wellness feedback interface1110to a subsequent user interface, which can be a foot health feedback interface1120shown inFIG.8E.

The foot health feedback interface1120may present a feedback question or prompt1124(regarding a second condition like “My feet feel . . . ”). A wellness status bar1122may show the wellness status bar1112after completion of the feedback question or prompt1114. The foot health feedback interface1120can present selectable feedback elements1126, each characterizing a different response to the feedback question or prompt1124, and a next selectable element1128by which the user can confirm the entry of the response to the feedback question or prompt1124and cause the user application312to transition from the foot health feedback interface1120to a subsequent user interface, such as an observation feedback interface1130shown inFIG.8F.

The observation feedback interface1130can present a feedback question or prompt1134regarding a third condition, such as “I noticed . . . ” to request information regarding one or more conditions of the user's foot or wound area, including observations of swelling, bruising, drainage, or redness. The observation feedback interface1130can include selectable elements1136, each characterizing a different response to the feedback question or prompt1134. A wellness status bar1132may show the wellness status bar1112after completion of the feedback question or prompt1114and the feedback question or prompt1124. The observation feedback interface1130can present a next selectable element1138by which the user can confirm the entry of the response to the feedback question or prompt1134and cause the user application312to transition from the observation feedback interface1130to a subsequent user interface, such as a goal completion interface1140shown inFIG.8G.

The goal completion interface1140can present a feedback question or prompt1144(for example, a question for the user about the user's goals that were previously input by the user via the user goal interface1050illustrated inFIG.7F). A wellness status bar1142may show the wellness status bar1112after completion of the feedback question or prompt1114, the feedback question or prompt1124, and the feedback question or prompt1134. The goal completion interface1140can include selectable goal elements1146, each characterizing a different response to the feedback question or prompt1144. The goal completion interface1140can extend beyond a single screen space on the user interface316such that the user may, for instance, swipe or scroll up or down to view an entirety of the goal completion interface1140, including additional goals. The goal completion interface1140can present a next selectable element1148by which the user can confirm the entry of the response to the feedback question or prompt1144and cause the user application312to transition from the goal completion interface1140to a subsequent user interface, which can optionally be an untagged event summary interface1150shown inFIG.8H.

The untagged event summary interface1150can indicate a number of events (for example, three events as illustrated) for which the user is requested to provide contextual information (for example, information about a type of activity engaged in by the user when an event occur, which may be referred to as tagging). A selectable next element is also included for advancing to another user interface, such as a geographic location interface1160illustrated inFIG.8I.

The geographic location interface1160can be used to request that the user consider contextual information regarding an event. The geographic location interface1160may present event information1162, including a time (which may also be a time range as shown) and a location of the event, to remind the user of the time and the location that the event occurred. The event information1162can, for example, provide the time and the location of the event as described with respect to block550ofFIG.5. A boot image1163can denote that the user was determined to have been wearing an offloading device during the event. The user application312may have received the time, the location, and the determination of wearing the offloading device from the device management system340, such as in response to a request from the user operation device310or a push notification from the device management system340. A map image1164can be used to depict the location of the user or the user operation device310at the time of the event. A location input element1166can, upon selection by the user, transition the user application312from the geographic location interface1160to a different user interface, such as an activity input interface1170shown inFIG.8J.

The activity input interface1170can display event information1172, which can be the same as the event information1162. The activity input interface1170can prompt the user to provide activity category information1174by requesting that the user select the category of activity engaged in by the user at the time and the location of the event. The activity category information1174may be an example of the request from the user described with respect to block560ofFIG.5and block620ofFIG.6. The activity category information1174can include activity description categories1176, which can be selected by the user to input the category of activity that the user was engaged in during the event. The activity description categories1176can, for example, include home (to indicate that the user was at home), leisure (to indicate that the user was engaged in leisure), travel (to indicate that the user was traveling), work (to indicate that the user was working), exercise (to indicate that the user was engaged in exercise), or an I don't remember category (to indicate that the user does not recall what type of activity was being engaged in).

The activity description categories1176can, upon selection by the user, transition another user interface that prompts the user to input a type of activity within the selected category that the user was engaged in at the time and the location of the event. In some aspects, a category of activity may be the same as a type of activity rather than a group of types of activities as described in this example. A close element1178can be selected to confirm that the user has completed the input of the category or type information requested in the activity input interface1170and to transition from the activity input interface1170to a subsequent interface, such as a tagged event summary interface1180illustrated inFIG.8K.

The tagged event summary interface1180can show a summary image1182representative of the type of activity that has been identified by the user for the event, as well as the time and a map showing the location of the event. The information presented on the tagged event summary interface1180can be confirmed by the user by selection of a save element1188. The selection of the save element1188may prompt the user application312save the information for the event and transmit at least the type of activity identified by the user for storage by the device management system340in associate with the event, time, or location. The example ofFIG.8Kshows that the user selected the exercise using machines as the type of activity that the user was engaged in during the event.

AlthoughFIG.8Jillustrates that the user may navigate through selection of one or more categories or prior to selection of one or more types of activities, in some aspects, the user can instead be presented on the activity input interface1170with multiple activity description categories or types that may correspond to different activity types previously indicated by the user (such as via the travel type interface1030or the exercise type interface1040) to be types of activities commonly engaged in by the user.

FIG.8Lillustrates an event confirmation interface1190that may provide feedback to the user regarding the completion of the requested inputs for the check-in process. The event confirmation interface1190can show a token1192(which can be any symbol, such as a star) transitioning to a total token count1193. The total token count1193can represent a total number of times the user successfully input all of the requested information for a check-in process and may be maintained by the user application312. An information status1194can confirm by text the successful completion of the check-in process. The event confirmation interface1190can also display an appointment reminder1196for an upcoming doctor appointment.

FIGS.9A-9Gillustrate example user interfaces that can be presented by the user application312on the user interface316of the user operation device310to provide summaries of monitoring, activities, events, or determinations for a user. The summaries may assist in the monitoring and treatment of a foot ulcer on the user. The summaries can be presented to cover data collected over or determined with respect to a selectable length of time, such as over few hours or less, one day, multiple days, one or more weeks, or longer.

FIG.9Aillustrates a user summary interface1300that can present a range of summary information to the user. The user summary interface1300can include an overview message1302indicating a subject of the content to be presented and a time period that the summary information pertains to (for example, the illustrated aspect presents a summary of the information collected by the user application312or determined for the user since “last Friday”) The summary information can include user observations1306, such as a user feeling summary1308(which can present an average of the feeling data from the user on a five point scale regarding how the user felt during the time period and include a graphical symbol, such as a happy face or a sad face, to graphically communicate the feeling) a foot feeling summary1310(which can present an average of the feeling data from the user on a five point scale of regarding how the user's feet felt during the time period and include a graphical symbol, such as a bare foot, to graphically communicate the feeling).

The user summary interface1300can present a number of occurrences during the time period that the user indicated swelling1314, redness1316, bruising1318, and drainage1320at the user's feet or foot wound. The user summary interface1300can present a summary of any other desired or meaningful observations that were input or selected by the user during user onboarding or a setup process for the user application312. The user summary interface1300can present summary data1324, such as actual and target average daily foot activity1328(for example, where actual is illustrated to be 2 hours and 54 minutes and target is illustrated to be 6 hours 23 minutes), offloading device usage1330(for example, where usage is illustrated to be 72% and up 24% from a previous period), and average daily time at risk1332(for example, where time at risk is illustrated to be 48 minutes which may be down 1 hour and 34 minutes from a previous period). The time at risk can refer to an amount of time during which a limb of the user may be active while an offloading device is not in use.

The user summary interface1300can present the user with a key events summary1340, which can include a presentation of an amount of time the user spent engaging in particular activities during events. Such events can be grouped by category or type of activity and may include home time1342, leisure time1344, work time1346, and untagged time1348.

The home time1342, leisure time1344, work time1346, and untagged time1348, can be user selectable elements that, when selected by the user, expand the user summary interface1300to another user interface (such as a home interface1370illustrated inFIG.9B) to present the user with additional information (for example, a total duration of events that occurred at the time/location, an increase or decrease in the total duration relative to a previous period, an offloading device usage, an amount of time at the time/location at which the user engaged in particular types of activities, a number of occurrences of events for particular types of activities, an average time per event for particular types of activities, a number of impacts for particular types of activities, an offloading device usage percentage for particular types of activities, or an assisted movement usage percentage for particular types of activities) regarding the selected one of the key events summary1340.

The user summary interface1300can present a user with a goal occurrences summary1350, which can include a presentation of a number of times that the user achieved individual goals. The goals can include the goals that the user input during the user onboarding or setup process for the user application312. Examples of goals that can be presented include “Check my shoes for sharp objects lodged underneath”, as shown a first goal1352, “Go for a run” as a second goal1354, and “Drink more water” as a third goal1356. The goals can be ordered according to a number of times that the goal was achieved (such as, from highest to lowest number of occurrences or vice versa). The user summary interface1300can have a done element1360, the selection of which by the user can trigger a transition by the user application312to a different or subsequent user interface.

FIG.9Billustrates a home interface1370that can include an interface identifier (for example, “Home”) and present the user with data or information regarding the activities that occurred when the user was determined or identified to have been at his or her home. The home interface1370can present the user with a cumulative home event time1372and an offloading percentage usage1374for events that occurred while the user spent at home. The home interface1370can present the user with an amount of time that the user was engaged in particular activities while at home and during which events occurred. Such activities can correspond with activities, including walking up/down stairs1376, gardening1378, cooking1380, or sitting down1386that were input or selected by the user, such as during the activity identification process500.

The home interface1370can present an activity type summary1384that presents the user with information regarding the home events for a particular type of activity, such as cooking. The activity type summary1384can indicate the number of events that the user was engaged in during the home time, the average time the user spent per event, the number of impacts or trauma events that occurred during the home time, the percentage of time the user used the offloading device during the home time, and the percentage of time that the user was assisted during movement.

FIG.9Cillustrates an appointment interface1400that can present the user with a schedule of one day's (such as today's) appointments, as well as details and tasks related thereto. An instructional message1402that can state “Today's appointments” and other descriptive text or symbols can be included on an upper portion of the appointment interface1400. The appointment interface1400can include a pre-appointment checklist1404, which can present the user with tasks to be completed before the appointment, and an appointment activities checklist1410, which include a name of the doctor for an upcoming appointment and other preparation options. A first task element1406can present the user with an option to select and review the first task. In the illustrated example, the first task can be to “review my report.” Accordingly, selecting the first task element1406can transition the user application312from the appointment interface1400to another user interface that presents the user with a relevant report related to a doctor visit. A second task element1408can, upon selection by the user, transition the user application312from the appointment interface1400to another user interface in which the user can input questions, issues, reminders, or other information related to the appointment for which the user wishes to prepare. The appointment activities checklist1410can present the user with an ability to set goals, replace sensors (such as the activity monitoring device120or the offloading monitoring device132associated with the user application312), or schedule a next appointment with a clinician.

FIG.9Dillustrates a foot activity target interface1430that can present the user with an informational message1432, which can include the title of the foot activity target interface1430(which can be “My daily foot activity target”) and a description of the requested information to be input or adjusted on the foot activity target interface1430. As illustrated, the requested information can be “How active should my foot be before my next appointment?” The foot activity target interface1400can enable the user to input an average target foot activity1434, such as daily activity, over a length of time (for example, since the last doctor visit) and a slider element1436that may be maintained in a corresponding position, which can be moved up for a higher target (for example, toward more1438), or moved down for a lower target (for example, toward less1439). The foot activity target interface1430can have a save element1440, the selection of which by the user can trigger a transition by the user application312to a different or subsequent user interface.

FIGS.10A-10Eillustrate example user interfaces that can be presented by the user application312on the user interface316of the user operation device310to encourage interactions by the user with the user application312and the input of requested information to the user application312. The user interfaces ofFIGS.10A-10Eor aspects thereof can be adjusted, as described herein, responsive to an engagement by the user with the user application312, such as described with respect to block650ofFIG.6.

FIG.10Aillustrates an achievement summary interface1500that can present the user with a summary of achievements to date. The achievement summary interface1500can include an achievements summary table1502configured to present summary information regarding aspects of the user's achievements with the user application312. The achievements summary table1502can present a levels element1504, a goals element1506, the streaks element1508, and a bonus element1510. Upon selection by the user of the levels element1504, the achievement summary interface1500can transition to presenting the user with an assigned level1514that has been achieved based on the user's compliance or engagement with the user application312. An underscore1512can indicate to the user which selectable table element has been selected and is being presented, and the unselected table elements can be shown in a lighter color, such as gray, while the selected table element can be shown in a brighter color, such as blue.

The levels can range, for example, from 1 to 5 and may include level 1 Newbie (shown inFIG.10A), level 2 Novice (not shown), level 3 Pro (not shown), level 4 Expert (shown inFIG.10B), and level 5 Master (not shown). Each of these different levels can have a present a character1515, which may be the same character selected via the character select interface1070by the user, with different accessories or facial expressions to illustrate or represent the level that the character1515has achieved. The level of happiness expressed in the facial expressions of the character1515can increase with each increasing level from Newbie to Master.

The level assigned to the user may depend on a number of tokens (sometimes described herein as stars) that the user has accumulated through compliance or engagement with the user application312. A token may be awarded each time a user completes a check-in or completes another task. Increases in the assigned level or number of tokens may result in visual changes in the graphical user interfaces presented on the user interface316to the user (for example, different formatting, color schemes, presentation of textual information). A token level indicator1518can present to the user the number of tokens that the user has accumulated and may accordingly allow the user to understand the number of stars to accumulate to achieve a next level. The achievement summary interface1500can include an instructional message1516instructing the user on how to achieve more stars and advance to the next level and may provide a count of tokens to advance to the next level.

Upon selection by the user of the goals element1506, as indicated by the underscore1512inFIG.10C, the achievement summary interface1500can transition to present the user with his or her goal-based achievements based on the user's successful completion of goals, as shown inFIG.10C. Examples of goal-based achievements can include New Leaf1530, Goalsetter1532, Habit Hero1534, Fearless Focus1536, Plate Spinner1538, and Multitasker1540. Each of the different goal-based achievements can be achieved when the user has completed certain criteria associate with the goals. For example, New Leaf1530can be achieved when the user has completed three of his or her goals. Goalsetter1532can be achieved when a user has completed ten of his or her goals. The achievement summary interface1500can present a flag or checkmark symbol to indicate the goals that have been achieved by the user. Upon selecting a goal-based achievement, the achievement summary interface1500can present the user with information about achievement of the associated goal. The achievement summary interface1500can indicate the goals that have not yet been achieved by showing a padlock symbol positioned proximate to the unachieved goals. The achievements summary interface1500can present a progress ring1541which fills to indicate the user's progress in achieving a respective goal. As the progress ring1541fills, the progress ring denotes greater progress toward achieving the respective goal.

Upon selection by the user of the streaks element1508, as indicated by the underscore1512inFIG.10D, the achievement summary interface1500can transition to present the user with streak based achievement awards based on a consecutive number of days that a user has completed one or more activities or the checked-in process. If the user has completed one or more activities for seven consecutive days, the achievement summary interface1500can present the user with a 14 days activity achievement award1544for this achievement. Another achievement for activities can be presented for a 14 days activity achievement award1548, a 21 days activity achievement award1552, or a more than 21 days activity achievement award (not shown).

If a user has completed check-ins for seven consecutive days, the achievement summary interface1500can present the user with a 7 days check-in achievement award1546for this achievement. A 14 days check-in achievement award1550and a 21 days check-in achievement award1554can similarly be presented for a greater number of consecutive days of check-ins. The achievement summary interface1500can present a picture and checkmark symbol to indicate the streak achievement that has been achieved by the user. The achievement summary interface1500can indicate the streak achievement that have not yet been achieved by showing a padlock symbol for each of the unachieved achievements. The achievements summary interface1500can present a progress ring1555to indicate the user's progress in achieving the streak achievements.

Upon selection by the user of the bonus element1510, as indicated by the underscore1512inFIG.10E, the achievement summary interface1500can transition to present the user with earned bonus achievements. Bonus achievements can be presented to the user when the user has achieved a threshold number of the following actions (for instance, cumulatively): achieving multiple goals in one day, editing multiple events previously identified as “I don't remember”, tagging events from 2 or more days prior, viewing multiple journal entries, adding multiple talking points for clinician appointments, or having checked-in and stayed within activity target level for a set number of days. Bonus achievements that can be presented include Spring Cleaning1560, Elephant Memory1562, or others. Locked bonus achievements1564can be presented to indicate bonus achievements that are not yet achieved or viewable.

FIGS.11A and11Billustrate example user interfaces that can be presented by the clinician application322to permit a clinician to initiate access to information for the users which the clinician may be assisting. The information may have been gathered or determined by the device management system340through the user operation device310, as well as the activity monitoring device120or the offloading monitoring device132. A clinician login interface1600can present a login prompt1602requesting an email address or account name, as well as a password. Upon selection of the login element1604, the clinician application322can transition from the clinician login interface1600to an authentication interface1610. The authentication interface1610can present an authentication request1612for an authentication PIN, which may be provided to the clinician via out-of-band communication, such as through a text message like a short message service message (SMS) over a cellular network.

FIGS.12A-12Gillustrate example user interfaces that can be presented by the clinician application322to allow a clinician to review information for the users which the clinician may be assisting. As described with respect toFIGS.11A and11B, the information may have been gathered or determined by the device management system340through the user operation device310, as well as the activity monitoring device120or the offloading monitoring device132

FIG.12Aillustrates a dashboard interface1620, which may present a dashboard heading1622, a my appointments element1624, and an all appointments element1626. An underscore1628can indicate to the clinician which appointments element has been selected and is being presented. The dashboard interface1620can provide an appointment list1630of the appointments with users in chronological order for a period of time. The appointment list1630can identify a time when an appointment with a user will start, a name of the user, a name of the clinician, and a summary of other metrics that may be relevant to the user, and a brief summary of the user's activities or progress during a period of time, including an offloading device usage (ODU) and an average daily time at risk for each user. The appointment list1630can present the information for each user appointment on a selectable element that, upon selection by the clinician, can transition the clinician application322from the dashboard interface1620to an individual user interface1640shown inFIG.12Bthat has additional information and details regarding the patient that was selected.

With reference toFIG.12B, the individual user interface1640can present a user identifier1642that can include the user's name, picture, age, gender, or other medical conditions for the user. The individual user interface1640can present a report menu1644that can include summary information regarding available reports and a history of appointments for the user. Upon selection by the clinician of any of the selectable elements within the report table, the clinician application322can transition from the individual user interface1640to another user-related interface that can, for example, present a detailed report of the user or a history of the user, including an appointment history. The individual user interface1640can present a user management menu1645(which may be referred to as a manage user menu) that, upon selection by the clinician, can transition the clinician application322from the individual user interface1640to a manage appointments interface, a manage hardware interface, or a decommission application interface.

Upon selection of the new report available element of the report menu1644, the clinician application322can transition from the individual user interface1640to an individual user interface1650(as shown inFIG.12C) that can present a report identifier1652, an observations table1654, a summary table1656, a key events table1658, an untagged table1660, an exercise activity summary1662, a work activity summary1664, a travel activity summary1666, and a leisure activity summary1668. The observations table1654can present to the clinician a summary of how the user felt, how the user's foot felt, or symptoms observed by the user regarding his or her feet during a period of time. The summary table1656can present to the clinician an average daily time at risk, an offloading device usage, or an average daily time that the foot was active, such as is described with respect toFIG.9A. For example, the summary table1656can include (i) a time the foot was loaded (or active), which can reflect the amount of time the user has engaged in activity that loaded the foot (such as, any activity other than laying down or sitting/standing up with the foot lifted) and (ii) an amount of time from the time the foot was loaded that the user wore the offloading device (which can be expressed as a percentage or ratio). Any of these times can be expressed as a daily time or average daily time (or another time period). The summary table1656can include a time the foot has been at risk, which can be determined as the difference between the time the foot was loaded and the amount of time the user wore the offloading device. The summary table1656can include information (for example, in form of a line graph or another user interface element) that visually illustrates a time the foot was loaded (illustrated as a line segment on the left side), a time the foot has been at risk (illustrated as the entire line segment), and a target amount of time for wearing the offloading device (illustrated as a dot). 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 a user's compliance with wearing the offloading device, a healing trajectory, or a risk of exacerbating an existing ulcer or developing a new ulcer, or make appropriate adjustments to therapy.

The key events table1658can present the clinician with information regarding the activities engaged in by the user and the duration of such activities. The category or type of activity may be presented in the key events table in a selectable format wherein, upon selection of a particular key event category, the clinician application322can transition from the individual user interface1650to a detailed key event report interface showing more details regarding the selected key event, such as described with respect toFIG.12D. The untagged table1660can present information regarding untagged events, which may be been assigned by the data processing system344with likely activities engaged in by the user at the time of the untagged activities. The untagged activities can include, for example, time spent in a car (such as driving), time spent walking, time spent sitting or standing, or time spent with the leg elevated. A transition element1670can transition the clinician application322from the individual user interface1650to a subsequent interface.

FIG.12Dillustrates a cooking report interface1680, which is an example of a detailed key event report for cooking. The cooking report interface1680can include information about cooking events, including a summary1681presenting the name of the respective key event category (such as, “Cooking”), number of cooking event occurrences, and the percentage of offloading device usage during the cooking events. The cooking report interface1680can present a detailed event report1682that can show the day of the week of each event, the start time and duration of each event, whether an impact (which can be a quick strike to the limb of a user) occurred during the respective cooking event, and the type of assisted movement used, if any, during the event. Similar report interfaces can be available for other activities.

FIG.12Eillustrates a user history interface1690that can present an informational message1692including the date range of the history report presented on the user history interface1690, an overall compliance table1694, and an appointment history table1698. The overall compliance table1694can present a bar graph summary1696that presents the ODU time and time at risk, such as on a weekly basis during the report duration. The appointment history table1698can show the dates of previous appointments, the ODU during the time period before the appointment, and the average daily time at risk during the time period before the appointment. The appointment history table1698can have selectable appointment elements1699associated with each previous appointment that, upon selection by the clinician, can transition the clinician application322from the user history interface1690to a daily bar graph summary1710illustrated inFIG.12Fthat can present the clinician with the ODU time and time at risk on a daily basis during the report duration. As described herein, this information can allow the clinician to quickly and reliably analyze the user's lifestyle, determine a user's compliance with wearing the offloading device, a healing trajectory, or a risk of exacerbating an existing ulcer or developing a new ulcer, or make appropriate adjustments to therapy.

FIG.12Gillustrates another individual user interface1740similar to the individual user interface1650, but which presents error information for the user. A user identifier1742on the individual user interface1740that can include the user's name, picture, age, gender, or other medical conditions. The individual user interface1740can present a report menu1744that can present summary information regarding reports that are available and history of appointments for the user. The report menu1744can present a report status indicator1746that can alert the clinician that one or more reports may be inaccurate or incomplete. Upon selection by the clinician of any of the selectable elements within the report menu1744, the clinician application can transition from the individual user interface1740to another user-related interface. The individual user interface1740can present a user management menu1748that, upon selection by the clinician, can cause presentation of a manage appointments interface, a manage hardware interface, or a decommission application interface. The individual user interface1740can include a first warning indicator1743and a second warning indicator1745that can alert the clinician that issues were detected in the hardware components of the activity monitoring device120or the offloading monitoring device132.

Any of the features, components, images, designs, or other details of any of the user interfaces or aspects of user interfaces shown or described herein can additionally or alternatively be included in any of the other user interfaces or aspects of user interfaces shown or described herein to form additional user interfaces.

The user interfaces shown and described herein can include one or more interface controls that may be selected, for example, using the user interface316of the user operation device310or the user interface326of the clinician operation device320. The user interfaces may be output for presentation by the user application312of the user operation device310or the clinician application322of the clinician operation device320. The user controls shown are merely illustrative examples and can be varied in other aspects. For instance, buttons, dropdown boxes, select boxes, text boxes, check boxes, slider controls, or other user interface controls may be substituted with other types of user interface controls that provide the same or similar functionality. Further, interface controls may be combined or divided into other sets of interface controls such that similar functionality or the same functionality may be provided with very different looking user interfaces. Moreover, each of the interface controls may be selected by a user using one or more input options, such as a mouse, touch screen input, or keyboard input, among other interface input options.

Computer System Components

FIG.13illustrates a computer system700usable to construct one or more of the devices (for instance, the user operation device310or the clinician operation device320), systems (for instance, the device management system340), servers, or the like within the computing environment300ofFIG.3.

As shown inFIG.13, the computer system700can include (i) a processor(s) (CPUs)710, (ii) an input/output device(s)720configured to allow users to input and output information and interact with the computer system700as well as transfer and receive data or capture data with one or more sensors like an image sensor, (iii) a read only memory device(s) (ROMs)730or equivalents to provide nonvolatile storage of data or programs, (iv) a display(s)750such as a computer monitor or other display device, (v) a network connection(s)740and a network interface(s)742configured to allow the computer system700to connect to other systems, servers, or portable devices, as well as a memory space(s)760and a database(s)790. The database(s)790may be further divided or distributed as sub-database(s)790A-790N, with the sub-database(s) storing feature or function specific information associated with a particular feature or function. The various components shown inFIG.13may be incorporated in a computer(s)770. It is noted that the various components shown inFIG.13, including the database(s)790, are typically included as part of the computer(s)770, however, they may be external to the computer(s)770in some embodiments. For example, the database(s)790may be external to the computer(s)770and may be part of a separate database computer system or networked database system. In some instances, the computer system700may be a computing device like a desktop computer, mobile phone, or a server.

The memory space(s)760may include DRAM, SRAM, FLASH, hard disk drives, or other memory storage devices, such as a media drive(s)780, configured to store an operating system(s)762, an application program(s)764, and data768, and the memory space(s)760may be shared with, distributed with or overlap with the memory storage capacity of the database(s)790. In some embodiments, the memory space(s)760may include the database(s)790or in some embodiments the database(s)790may include the data768as shown in the memory space(s)760. The data stored in the memory space(s)760or the database(s)790may include information, such as motion data, pairing program information, data processing routines, or other types of data described herein.

Other Variations and Terminology

Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines or computing systems that can function together.

One or more user inputs described in this disclosure may be received using one or more different mechanisms. For example, user interface controls may be selected by a user using one or more input options, such as a mouse, touch screen input, or keyboard input, among other user interface input options. The user interface controls selected by the user can include one or more of buttons, dropdown boxes, select boxes, text boxes, check boxes, slider controls, or other user interface controls.

Although certain features are described in context of controlling of pairing, features of the disclosure can apply to control of communication permissions in types of system communications other than pairing.

The various illustrative logical blocks, modules, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, a microprocessor, a state machine, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a 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 can include electrical circuitry or digital logic circuitry configured to process computer-executable instructions. In another embodiment, a processor includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.

The steps of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC.

Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain aspects include, while other aspects do not include, certain features, elements or states. Thus, such conditional language is not generally intended to imply that features, elements or states are in any way required for one or more aspects or that one or more aspects necessarily include logic for deciding, with or without author input or prompting, whether these features, elements or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.

Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z. Thus, such conjunctive language is not generally intended 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.

Language of degree used herein, such as the terms “approximately,” “about,” “generally,” and “substantially” as used herein represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “approximately”, “about”, “generally,” and “substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount. As another example, in certain embodiments, the terms “generally parallel” and “substantially parallel” refer to a value, amount, or characteristic that departs from exactly parallel by less than or equal to 15 degrees, 10 degrees, 5 degrees, 3 degrees, 1 degree, or 0.1 degree.

While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others.