Patent Application
20210005300
This application relates to a customizable communication platform and more particularly to providing customized communication to a user device.
Conventionally, the approach to providing users with ongoing communications regarding a plan or other repetitive course of action may leave the majority of the work to the user. The smartphone and other personal computing devices are not being properly utilized when offering users with options for maintaining a course of treatment or a set of goals. The lack of action taken by the professional service provider and/or the user can lead to personal health problems and lost revenue for providers, insurers, etc., as well as the users.
An example embodiment of the present application provides a method that includes at least one of displaying a treatment plan table via a cloud based server, for a patient having a set of treatment information including at least one selectable parameter block, wherein the at least one selectable parameter block has a recordation input type, a recordation input frequency, a communication schedule, at least one guardrail value, at least one flag value, and a message text query, receiving a treatment plan identifier from a healthcare provider server, populating the treatment plan table with the at least one selectable parameter block and the treatment plan identifier, creating a treatment plan based on the populated treatment plan table and sending the treatment plan to a patient device.
Another example embodiment of the present application provides a non-transitory computer readable medium comprising instructions that, when read by a processor, cause the processor to perform at least one of displaying a treatment plan table via a cloud based server, for a patient having a set of treatment information including at least one selectable parameter block, wherein the at least one selectable parameter block has a recordation input type, a recordation input frequency, a communication schedule, at least one guardrail value, at least one flag value, and a message text query, receiving a treatment plan identifier from a healthcare provider server, populating the treatment plan table with the at least one selectable parameter block and the treatment plan identifier, creating a treatment plan based on the populated treatment plan table and sending the treatment plan to a patient device.
A further example embodiment of the present application provides a system, comprising at least one cloud-based processor, and at least one memory electrically coupled to the at least one cloud-based processor and storing an application, wherein the at least one cloud-based processor performs at least one operation to display a treatment plan table via a cloud based server, for a patient having a set of treatment information including at least one selectable parameter block, wherein the at least one selectable parameter block has a recordation input type, a recordation input frequency, a communication schedule, at least one guardrail value, at least one flag value, and a message text query, receive a treatment plan identifier from a healthcare provider server, populate the treatment plan table with the at least one selectable parameter block and the treatment plan identifier, create a treatment plan based on the populated treatment plan table and send the treatment plan to a patient device.
It will be readily understood that the components of the present application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of a method, apparatus, and system, as represented in the attached figures, is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments of the application.
The features, structures, or characteristics of the application described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments”, “some embodiments”, or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments”, or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Examples of treatment plans and other objectives may include a care management service for assessment of patient medical needs. The system and application may ensure timely receipt of all recommended treatment actions, drugs, third party services over a designated period of time. Also, referrals to other providers and additional services may provide emergency visits, discharge instructions, nursing facility operations, and home health care functions. In operation, the procedure may begin with the medical treatment provider creating a treatment plan or ‘journey’ for each patient. Each journey is generally for a single chronic condition or objective. One patient may have multiple journeys integrated into a single application. Also, the journeys may originate from various different providers and service entities.
In addition, while the term “message” has been used in the description of embodiments of the present application, the application may be applied to many types of network data, such as, packet, frame, datagram, etc. For purposes of this application, the term “message” also includes packet, frame, datagram, and any equivalents thereof. Furthermore, while certain types of messages and signaling are depicted in exemplary embodiments of the application, the application is not limited to a certain type of message, and the application is not limited to a certain type of signaling.
According to example embodiments, a user device, such as a smartphone, cellular phone, tablet device, laptop or other computing device with a memory and processor, may communicate with another computing device and/or a server to provide an integrated communication platform. A patient device as stated herein is a user device.
Example embodiments provide a computer system programmed to use automated messaging from medical offices to specific patients. The application is not limited to medical procedures and functions and may be used with other configurations for various purposes and services benefitting the end user. Example embodiments include three main computer systems, which work together in an integrated manner including a management platform that controls set-up, functionality, activity reporting, and messaging credentials for the users. An administrative platform which the doctor and doctor's office can access via the internet, and a mobile application that a patient can download into a mobile computer device such as a smartphone or tablet.
The integrated platform provides a way of checking-in with a patient at prescribed intervals during times between office visits and when undergoing certain treatment that the doctor is providing or overseeing for the patient. The patient dialog may gather relevant information about the status of the patient's conditions or recovery and can be modified or tailored to specifically meet the dialog requirements of the treating physician. Once initiated by the doctor's office, the application operates in an autonomous manner by delivering messages to the patient to prompt responses if needed. The application functions are monitored to assure that the patient replies to the information requests from the doctor, otherwise a no-response alert is sent to the doctor's office. The interactions are recorded and time-stamped, providing an auditable record of the dialog, suitable for insurance billing purposes. The application can also support parametric information from devices that measure certain body functions, such as diabetes glucometers, or blood pressure cuffs, or any sensory readable health care metric. The application may also create a longitudinal record of information for the patient to illustrate week-to-week trends.
The operations of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a computer program executed by a processor, or in a combination of the two. A computer program may be embodied on a computer readable medium, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.
An exemplary storage medium may be coupled to the processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (“ASIC”). In the alternative, the processor and the storage medium may reside as discrete components. For example,
As illustrated in
A first example method shown in
Communication Platform Builder
One example screen layout of the communication platform builder is depicted in
The selectable parameter blocks are broken into block subsets such as weight, blood pressure, temperature, electro-cardiogram, diabetes monitoring, psychological monitoring, medication adherence and habitat monitoring. Within each of the block subsets there are associated selectable parameter blocks. The blocks are provided by the cloud based server and may be chosen by the healthcare provider to modify a journey or create a journey.
The weight block subset may have a manual weight input parameter block, connection weight input parameter block and the like. The blood pressure block subset may have manual arm pressure cuff input parameter block, an ear bud parameter block and the like. The temperature block subset may have a manual oral temperature parameter block, a fever scout auto-report parameter block and the like. The electrocardiogram block subset may have a specific manufacturer email in parameter block, a wearable patch that provides ECG data, auto-pull parameter block and the like. The diabetes monitoring block subset may have different manual glucometer parameter blocks and wearable glucose monitoring parameter block inputs and the like. The psychological monitoring block subset may have a standardized patient health questionnaire, a frequency, intensity, burden of side effects (FiBSER) parameter block and the like. The medical adherence monitoring block may have a standard medication parameter block and a taper course parameter block. The habitat monitor block may have a senior living with family, a patient living alone parameter block and the like.
As an example, within the blood pressure subset 814, manual arm pressure cuff input parameter block, there may be a recording interval within which the data is to be recorded, the recording may be manual, or if an automatic arm pressure cuff with communication capabilities is utilized, the data may be uploaded directly from the device, a communication interval within which the data is communicated to the health care provider through the system by messages sent from the cloud based server to the healthcare provider and a set of guardrails and flags indicating low and high blood pressure values. The manual arm pressure cuff input parameter block may also include text messages 816 requesting specific information from the patient.
The various input parameter blocks may be suggested by the cloud based system and from these, specific blocks dragged and dropped into a specific treatment plan. A title identifier 818 may be input to the specific treatment plan to be added to a library of treatment plans. Once the various input parameter blocks are placed into the treatment plan a review and quality control may be performed on the treatment plan to insure that each relevant indices for the patient is addressed. The quality control may be performed by the cloud based system reviewing the plan for errors or substantial differences from similar treatment plans. The treatment plan table may be viewed 820 and saved 822.
In an example depicted in
The cloud based server as discussed herein is a central repository of data to be utilized by a healthcare provider server. The cloud based server may assess the original treatment in light of a pool of similar patients to the current patient, based on condition, age, sex, demographics and the like and may propose an alternative treatment based on a positive outcome for the similar pool of patients. The treatments for the pool of patients and their outcomes may be stored on the cloud server in a format which does not identify the particular patients of the pool, but does describe their characteristics and outcomes. The data from the cloud server may be scrubbed and may be disease, patient characteristic, regimen and outcome centric. This collection and correlation of data may allow for continuous improvement in treatment proposals to the healthcare provider.
The method may include loading a trigger table having a set of trigger dates based on the treatment plan, a message dispatch responsive to the set of trigger dates. The selectable parameter block may be drag and drop, where parameters are individually selectable within the selectable parameter block. The method may include displaying a review display to review a set of selected parameter blocks and review parameters within the set of selected parameter blocks and displaying a quality assurance display that detects whether additional components should be added based on similar treatment plans. The treatment plan may be added to a treatment plan library. The recordation input type is of manual and wirelessly received receiving parametric device information of patient body functions. The method may include storing a T-code identifier, a timestamp and a patient response to an auditable patient record and the treatment plan may be modified.
In another example, a non-transitory computer readable medium comprising instructions that, when read by a processor, cause the processor to perform, displaying a treatment plan table via a cloud based server, for a patient having a set of treatment information including at least one selectable parameter block, wherein the at least one selectable parameter block has a recordation input type, a recordation input frequency, a communication schedule, at least one guardrail value, at least one flag value, and a message text query. The instructions further comprise receiving a treatment plan identifier from a healthcare provider server, populating the treatment plan table with the at least one selectable parameter block and the treatment plan identifier, creating a treatment plan based on the populated treatment plan table and sending the treatment plan to a patient device.
In yet a further example, a cloud-based processor, and memory electrically coupled to the cloud-based processor and storing an application where the cloud-based processor performs operations to, display a treatment plan table via a cloud based server, for a patient having a set of treatment information including at least one selectable parameter block, wherein the at least one selectable parameter block has a recordation input type, a recordation input frequency, a communication schedule, at least one guardrail value, at least one flag value, and a message text query. The instructions further cause the processor to receive a treatment plan identifier from a healthcare provider server, populate the treatment plan table with the at least one selectable parameter block and the treatment plan identifier, create a treatment plan based on the populated treatment plan table and send the treatment plan to a patient device.
With respect to the timing of patient responses, the first example method may also include, awaiting the patient response to the message for a late response duration and categorizing the patient response if the patient response is received within the late response duration. If the patient response is not received within the late response duration the method further comprises sending a duplicate message and flagging the patient response as non-responsive if the patient response to the duplicate message is not received within a second late response duration.
The timing of the message dispatches associated with the treatment plan is partly governed by a trigger table. The method may include loading the trigger table having a set of trigger dates based on the treatment plan where the message dispatch is sent according to the set of trigger dates. The method may further include receiving a message start date and receiving an initialization message from a patient mobile device to initiate the treatment plan and to initialize the set of trigger dates in the trigger table.
Although an exemplary embodiment of the system, method, and computer readable medium of the present application has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the application is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the spirit or scope of the application as set forth and defined by the following claims. For example, the capabilities of the system of the various figures can be performed by one or more of the modules or components described herein or in a distributed architecture and may include a transmitter, receiver or pair of both. For example, all or part of the functionality performed by the individual modules, may be performed by one or more of these modules. Further, the functionality described herein may be performed at various times and in relation to various events, internal or external to the modules or components. Also, the information sent between various modules can be sent between the modules via at least one of: a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device and/or via plurality of protocols. Also, the messages sent or received by any of the modules may be sent or received directly and/or via one or more of the other modules.
One skilled in the art will appreciate that a “system” could be embodied as a personal computer, a server, a console, a personal digital assistant (PDA), a cell phone, a tablet computing device, a smartphone or any other suitable computing device, or combination of devices. Presenting the above-described functions as being performed by a “system” is not intended to limit the scope of the present application in any way, but is intended to provide one example of many embodiments of the present application. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with computing technology.
It should be noted that some of the system features described in this specification have been presented as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, or the like.
A module may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. Further, modules may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM), tape, or any other such medium used to store data.
Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
It will be readily understood that the components of the application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the detailed description of the embodiments is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments of the application.
One having ordinary skill in the art will readily understand that the application as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations that are different than those which are disclosed. Therefore, although the application has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the application. In order to determine the metes and bounds of the application, therefore, reference should be made to the appended claims.
While preferred embodiments of the present application have been described, it is to be understood that the embodiments described are illustrative only and the scope of the application is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto.
| Number | Date | Country | |
|---|---|---|---|
| 62869483 | Jul 2019 | US | |
| 62869497 | Jul 2019 | US |
