The present invention relates to a method for a user unit, a user unit and a system comprising said user unit. The user unit is preferably a patient unit for logging the patient-related information between two visits to the doctor, for example.
Today there is a need in e.g. medical care that during a short period of time gather information about a person such as how the person feel, or what a person does at different periods under a time period, and to evaluate the collected information on completion of the period of time. For example, this can concern that under a long time get information on how often and how long a person, for example, has back pain, and how bad the back pain of the patient is.
It may also be desirable to remind a person or a patient to take their medications as that it is done regularly and to monitor how the patient is doing after the medicine is taken.
There is thus a need for an interactive system that allows simple and effective collection of personal event information during a longer time period, and analysis of the collected information.
The present invention relates to a method for a user unit, a user unit and a system comprising said user unit. The user unit is preferably a patient unit for logging the patient-related information between e.g. two visits to the doctor.
The present invention is defined in the independent claims. Preferred embodiments are defined by the dependent claims.
In the description of the present invention, the following definitions will be used.
The present invention will now be described in more detail with reference to the accompanying drawings, in which:
The present invention will be described in more detail with reference to figures
The user unit is preferably a stand-alone unit adapted to communicate with a user. Each user unit can have a unique external identity and can be identified by for example by an ID number or a bar code. The user unit preferably has an inner identity, called a GUID, by which the user unit is identifiable by others in components of the system. The user unit contains a microprocessor with associated program memory for drivers, task manager and an interpreter. The user unit further includes a real time clock, components for displaying and entering information, to communicate with administrative systems and peripherals, and memory for storing program and output of the interpreter.
The first external computer 20 is further disposed in communication with a database 40. The external computer 20 may be arranged to communicate with the database 40 directly or via a wireless or wired communication networks, for example via the communication network 30. Further, said first computer 20 may be adapted to administer one or more user units 10 and for creating one or more reports 60.
The administrative system 20 may include a compiler (not shown) adapted to prepare case definitions and question lists for the user unit interpreter. That is, the compiler may be arranged to define and create the event definitions and question lists to be transferred to a given user unit. The compiler may be implemented by software.
As shown in
The user unit 10 further includes a user interface 13 provided in communication Task 11 and adapted for communication with a user. User interface 13 may include input means, such as a keyboard, microphone, touch sensitive display, and output means, such as screen and speakers. The user interface can be realized as a method and/or a unit for communication between devices in the system.
The user interface can also be used to present or gather information.
User unit 10 further includes a real time interpreter 14 having an instruction memory 15, also referred to as a program memory 15, and a data memory 16. The interpreter is adapted to interpret case definitions and question lists saved in user unit even program memory 15 and, based on the interpreted event definitions and question lists communicate with the task manager which can control the communication with the user based on the interpreted result.
In the data memory 16 are stored the results of performed activities/events, e.g. information related to the user's answers to questions. Preferably, the interpreter is realized by software in the user unit. In embodiments of the invention, the interpreter makes a central component of the user unit's software.
The instruction memory 15 and data memory 16 can be integrated in said real time interpreter 14, but they can also be separate parts arranged in communication with said real time interpreter 14 and the task manager 11.
A real time clock 17 is also contained in the user unit 10 and disposed in communication with the task manager 11. The real time clock is further arranged to continuously update a numerical representation of the time.
It is understood that the arrows in
Task manager 11 is arranged to control the communication between the components of user unit 10.
The interfaces 12, 13 can be handled via the drivers for the hardware. The interfaces 12, 13 may be adapted to initiate activities, which activities should be addressed by the task manager 11 depending on the current system status.
The interpreters 14 program memory 15 and data memory 16 is handled via task manager 11 such that the interpreter 14 is independent of any hardware.
The transfer of information between the administrative system 20 and the user unit 10 may be via a physical link, either by wire, such as the USS (Universal Serial Bus), or wireless, for example, via Bluetooth, infrared communication, SMS (Eng. Short Message Service) or similar. The transfer is performed via a protocol which partly allows a bidirectional transfer of event tables, question lists and other system data. The administrative system can also give the user unit 10 commands of the type initiate interpreter 14, set the time 17, etc.
The user unit can be arranged to be activated when connected to the administrative system. At the initiation of the communication between the user unit and the administrative system the administrative system controls the user units identity, GUID, to ensure that the user unit has access to the administrative system. In embodiments of the invention all other types of activity are stopped when the user unit connects to the administrative system, but it should be understood that certain activities can continue even on connection.
Transfer of data between the user unit 10 and a so-called external unit, i.e. a device located outside the user unit 10, can be done by the external unit enabling the user unit from a standby mode to an active mode.
In embodiments of the invention, the communication with the user is performed by means of the user interface by displaying a text and/or an image on a monitor, whereby the acknowledgment or reply should be given by the user via the input components. The user interface 13 is also used to enable the user unit from its standby mode.
In embodiments of the invention, the real-time clock 17 is performed by software periodically activated in the processor, but can also be realized of an independent circuit which can activate the user unit 10 at a preset or predetermined time.
In embodiments of the invention the interpreter 14 is realized by software which is capable of planning and performing instructions specified in the interpreter's program memory 15. The instructions are defined by the event table, question lists and/or the planning table.
Preferably, the interpreter 14 is configured to manage one or more of the following activities:
How these activities should be handled is defined by the event table and/or the planning table.
The activity “Initialization” is controlled from the administrative system via the task manager. At the initialization the planning table with the timing of the next event, the schema's basic time etc. is created. Planning tables are stored in the user units program memory.
The activity “scheduled event” is initiated/activated by the real time clock in the user unit. If there are higher prioritized events an alarm is set in the real time clock to the next higher prioritized event. When the event is taken care of calls of any consequential events and question lists are performed. Then a check of when the next event will occur is performed. If a higher priority event is scheduled during the period, and the current event is interruptible the higher prioritized event is performed. Thereafter, further processing of the lower priority event is performed if allowed by the treatment rules.
The activity ‘Event generated by external devices” has in embodiments of the invention, the highest priority and interrupts all possible ongoing events. Normally this requires no user interaction. For example, an external device, e.g. a temperature sensor or a pedometer, register a value that exceeds a certain maximum or falls below a specified minimum value.
The activity “Self-reported event” is generated through the user interface. A “Self-reported event” is an event that the user enters in the user unit without preceded by a call or reminder from the user unit. For example, a user input all the times he/she has a headache, have fallen or have felt unwell for any reason.
The activity “Consequence Event” is not scheduable, i.e. it does not follow any schedule. In embodiments of the invention “Consequence Event” is activated by any of activities “Initiation”, “Scheduled event”, “Event generated by external device” and/or “Self-reported event” as described above. A “consequence event” may affect the timing of the next event in a scheduled event. Examples of “consequence events” can be a follow-up question such as “Did you take your aspirin?” when a user has indicated that he/she has a headache.
The activity “Question list” is initiated by any of the above-described event types. It can be non-interruptible or uninterruptible followed by further processing.
A list of questions can be “simple”, i.e. consist of a number of questions that are answered in turn.
An example of a simple list of questions are:
A list of questions can also be branched, i.e. consist of supplementary questions and which is dependent on the answer to the previous question. An example of a branched list of questions are:
The activity “Questions asked by the user” is activated by the user. The user can ask questions like, “When did an event occur the last time”, “When will the event take place next” or “How many times has a certain event occurred”.
Embodiments of the present invention also relates to a method comprising one or more steps 1010-1060 below, cf.
In step 1010, the programming is done by the user unit 10 and one or more of the components a)-g) in event definition is created, i.e. the unique identity; message; event; rules for initialization; response rules; rules for reminders and/or logging rules, created.
One rule for initiation, can for example define if an event should be active on startup and in that case also define when the next instance of the event will happen.
The reply rules may for example include the following:
Rules for reminders may include for example the number of times a user to be reminded of a missed event, and how long the interval should be between reminders.
Logging rules could comprise rules on how and if information about an event should be logged/saved, and if an event is logged even if a user misses it.
In embodiments of the invention may also result events (h) and question lists (i) coupled to the event definition. Further, step 1010 can also include programming and compiling question lists.
In step 1020 the administrator selects events, consequence events and/or question lists that are relevant to the user unit. Further, the administrator can create any schedule of events. The selected event definitions can be saved as an investigation. A saved examination can be used as a template at a later election administrator. Further can complete event definitions be created and compiled into an event table. This step is performed in embodiments of the invention in the administrative system 20.
Step 1030 includes that the user unit connects to the administrative system, illustrated in
In step 1040, the user unit separate from the administrative system and the unit communicates, via the user interface, the user according to the scheduled events.
The user is also able to report events or to ask questions. If the event definition specify that the information about the event should be saved, it will prompt the interpreter to save this data in its data memory.
1050 Transfer from the User Unit.
In step 1050, connects the user unit to the administrative system by e.g. the user submits the user unit to the administrator to connect the unit to the administrative system. Step 1050 further includes information stored in the data memory of the interpreter transferred to the administrative system. Initiation of the interpreter via the communication protocol, see step 1030. If the survey and logging of data will continue with the same event definition called an UE re-initialized) and returned to the user for further use. If the investigation is complete and no more data to be logged user unit retained by the administrator so that it can be reused for a new investigation.
Step 1060 includes analyzing information transmitted from the user unit to the administrative system. Analysis results can be presented to an administrator in the form of reports.
In embodiments of the present invention, the user unit is a patient unit for logging of patient-related information between two doctor visits, for example, but it should be understood that the finding other applications of the invention.
The information presented to the patient can be activities in the form of questions and reminders that are scheduled by the patient's physician. These scheduled tasks are preferably predefined by the doctor. The questions can be questions to determine the patient health conditions at different times of the patient's response and the timing of the response is saved inpatient unit. Depending on the patient's response various actions can be taken. The choice of the resulting action may also depend on the patient's medical history. Following action can be a follow-up question, such as “Does the medicine work?” if the patient has answered yes to the question “Have you taken your medicine?”, but can also be a proposal on an activity, such as taking a certain type of medicine or performing a physical activity.
Information that the patient inputs may be the answer to questions from the patient unit but that may also be information relating to events in the patient's life. For example, if a patient has fallen, have headaches or dizziness and this information can be input along with the timing in the patient unit. Once the patient comes back to her doctor, all Information in the patient unit is downloaded to an external computer for collection and analysis, the doctor can use the compilation and analysis as a decision basis for further patient treatment.
The invention is of course not limited to the above exemplary embodiments but may undergo modifications within the scope of the inventive concept in subsequent claims. Particularly noted that each illustrated hardware or software, unit and/or component can be combined with other illustrated unit and/or component to obtain the desired technical function.
Number | Date | Country | Kind |
---|---|---|---|
SE0801267-6 | May 2008 | SE | national |
Number | Date | Country | |
---|---|---|---|
61159908 | Mar 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12994440 | Feb 2011 | US |
Child | 14447474 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14447474 | Jul 2014 | US |
Child | 15063389 | US |