Contextual system for remote patient monitoring

Abstract

The invention relates to a patient remote monitoring system capable of collecting enriched physiological data and adapting the notification level on a remote monitoring interface based on the enriched physiological data. See Figure 6 for summary.

Description

Title of the invention: Contextual patient remote monitoring system technical field

[0001] The invention relates to a remote patient monitoring system, known as an RPM system (for "remote patient monitoring"). These systems generally comprise a measuring device, such as a blood pressure monitor, incorporating a sensor capable of measuring the physiological data of a user (also called a patient) and wirelessly connected to a network, and a monitoring device, incorporating a user interface and / or a data management workflow, so that a healthcare team can monitor the patient remotely.

[0002] The objective of the RPM system is to continuously monitor a patient's vital signs, such as weight, blood pressure, oxygen saturation, etc. Prior art

[0003] In the RPM system, healthcare professionals monitor patients remotely using measuring devices. In the area of ​​blood pressure, elevated blood pressure readings generally trigger a routine that requires healthcare professionals (physician or nurse) to contact the patient. However, some blood pressure readings are imperfect and do not require immediate attention because they are due to external factors that reduce the criticality of the blood pressure data, and some blood pressure readings are correctly elevated but not critical, as criticality may depend on other factors.

[0004] Documents EP1726257, WO2017 / 089171, US20240172990A1, US2013267795, WO2019 / 200158, US 8438038 present various solutions, some of which relate to RPM systems and others incorporate surveys or questions to users to enrich the measurement.

[0005] Withings™ provides body scales, blood pressure monitors (including the BPM Pro 2™) and other devices suitable for RPM systems.

[0006] It is necessary to provide improved RPM systems that will streamline the RPM process for professionals by reducing the number of false positives, i.e., cases where intervention by the health professional is not necessary, and / or by better understanding what lies behind blood pressure data. Description of the invention

[0007] This disclosure relates to a patient remote monitoring system (called "RPM system"), involving a user (or patient) and a professional (e.g., a doctor, a nurse and any other professional) taking care of the user remotely through connected physiological devices.

[0008] One object of the disclosure is a patient remote monitoring system, RPM, comprising a physiological measurement device including a physiological sensor, a user interface including a display and input hardware, including a wireless communication module, the RPM system further comprising a remote monitoring interface, configured to operate on a remote monitoring device, wherein the remote monitoring device and the physiological measurement device are two separate devices. The physiological measurement device is configured to send data to the remote monitoring interface using the wireless communication module. The physiological measurement device is configured to: - to obtain physiological data using the physiological sensor, - to display on the display of the physiological measurement device a question accompanied by a plurality of predetermined answers, the question and the plurality of predetermined answers forming a plurality of contextual data, - receive a predetermined response selected by the user using the blood pressure monitor's input hardware, the question and the selected predetermined response forming selected contextual data, - assign a notification level to physiological data using the selected physiological and contextual data, with the notification level chosen from a plurality of available notification levels, - display on the remote monitoring interface a display mode based on the assigned notification level.

[0009] Another aspect of the disclosure is a patient remote monitoring system, RPM, comprising: - a blood pressure monitor comprising: a casing, a user interface mounted on the casing, with a display and input hardware, a blood pressure sensor, BP, configured to generate blood pressure data on use, a wireless communication module, - a remote monitoring interface, configured to operate on a remote monitoring device, in which the remote monitoring device and the blood pressure monitor are two separate devices.

[0010] The blood pressure monitor is configured to send data to the remote monitoring interface using the wireless communication module.

[0011] The RPM system is configured to: - Obtain blood pressure data using the blood pressure sensor of the sphygmomanometer, - display on the blood pressure monitor a question with a plurality of predetermined answers, the question and the plurality of predetermined answers forming a plurality of contextual data, - receive a predetermined response selected by the user using the blood pressure monitor's input hardware, the question and the selected predetermined response forming selected contextual data, - assign a notification level to blood pressure data using the selected blood pressure and contextual data, the notification level being chosen from a plurality of available notification levels, - display on the remote monitoring interface a display mode based on the assigned notification level.

[0012] Thanks to these RPM systems, contextual data is used to modify the notification level of the physiological measurement, thus helping the healthcare professional caring for the patient to better take into account the current critical physiological data. In the case of the blood pressure monitor, having a fully integrated device that takes the measurement, displays questions, and receives user feedback during the same measurement session allows for the collection of user feedback regarding the blood pressure measurement. The blood pressure monitor is easy to use, even for people who are not used to it or for the elderly.

[0013] The following paragraphs present other characteristics of the RPM systems described above.

[0014] In one embodiment, the plurality of available notification levels includes between 3 and 5 notification levels.

[0015] In one embodiment, the remote monitoring interface comprises several display modes, each display mode having a dedicated presentation corresponding to a notification level, such that the display modes show physiological data (e.g., blood pressure data), for which contextual data are available, differently depending on the notification level. In particular, identical physiological data (e.g., blood pressure data) with different selected contextual data that have led to different notification levels for the physiological data (e.g., blood pressure data) have different display modes, and different display modes show the physiological data differently.

[0016] In one embodiment, the display mode includes a notification inbox, updated according to the assigned notification level.

[0017] In one embodiment, the physiological data (for example, the data relating to blood pressure) is an average of several physiological data values ​​(for example, the value of the data relating to blood pressure).

[0018] In one embodiment, the question is displayed in response to the determination that physiological data (e.g., blood pressure data) confirm a health condition. For example, the physiological data are below or above a threshold. The health condition can be modified (e.g., added, changed, updated, etc.) via the remote monitoring interface, so that the professional can customize the health condition to better suit their practice (specialty, disease, patients, etc.), particularly on a user-by-user basis.

[0019] In one embodiment, the display mode includes the display of physiological data (for example, data relating to blood pressure) with the selected contextual data.

[0020] In one embodiment, the RPM further includes a server and the wireless communication module of the physiological device (e.g., the sphygmomanometer) sends the physiological data (blood pressure data) and selected contextual data to the server, and the remote monitoring interface receives from the server the physiological data (e.g., blood pressure data), selected contextual data and the assigned notification level.

[0021] In one embodiment, the assignment of the notification level involves querying a matching database using physiological data (e.g., blood pressure data) and selected contextual data, wherein the matching database links a plurality of notification levels or variations of notification levels to ranges of values ​​for the blood pressure data and the contextual data. The variations of the notification level are to be applied to a pre-existing notification level based solely on the physiological data (e.g., blood pressure data).

[0022] In one embodiment, the matching database is stored on the server and the assignment is performed by the server.

[0023] In one embodiment, the matching database is stored on the tensiometer and the assignment is performed by the tensiometer.

[0024] In one embodiment, the RPM system further includes a remote monitoring device configured to execute the remote monitoring interface, the matching database being stored in the remote monitoring device.

[0025] In one embodiment, the correspondence database is modifiable via the remote monitoring interface, so that the professional can personalize the correspondence database to better adapt it to their practice (specialty, disease, patients, etc.), in particular user by user.

[0026] In one embodiment, the wireless communication module is a cellular module.

[0027] Another object of the disclosure is a method of remote patient monitoring, using one of the RPM systems presented above, the method comprising: - obtaining physiological data (e.g., blood pressure data) using the physiological sensor (blood pressure sensor) of the physiological measuring device (e.g., a sphygmomanometer), - display a question accompanied by a plurality of predetermined answers, the question and the predetermined answer forming predetermined contextual data, - receive a predetermined response selected by the user using the input material, the question and the selected predetermined response forming selected contextual data, - assign a notification level to physiological data (e.g., blood pressure data) using the selected physiological data (e.g., blood pressure data) and contextual data, the notification level being chosen from a plurality of available notification levels, - display on the remote monitoring interface a display mode based on the assigned notification level.

[0028] Another object of disclosure is a server or a method from the server's point of view, for any RPM system as described above: - the server sends to the physiological measurement device (e.g., the blood pressure monitor) a database of questions, the database of questions comprising at least one question and a plurality of predetermined answers for each question, the question and the predetermined answer forming contextual data, - the server sends a health condition to the physiological measurement device (e.g., the blood pressure monitor), the health condition to be verified using physiological data (e.g., blood pressure data), - the server receives physiological data (e.g., blood pressure data) from the physiological measuring device (e.g., blood pressure monitor) with a predetermined answer to a question, the question and the selected predetermined answer constituting selected contextual data. - the server assigns a notification level to physiological data (e.g., blood pressure data), for example using a matching database stored on the server, as previously stated, - finally, the server sends the physiological data (e.g., blood pressure data), the selected contextual data, and the assigned notification level to the remote monitoring interface.

[0029] The additional features disclosed previously also apply to the server, if applicable. Brief description of the drawings

[0030] Other features will be visible in the following non-limiting drawings: - [Fig. 1]: [Fig. 1] shows a patient remote monitoring system, RPM, according to a disclosure embodiment, - [Fig.2]: [Fig.2] shows a tensiometer according to one embodiment of the disclosure, - [Fig.3]: [Fig.2] shows a remote monitoring interface running on a monitoring device according to one form of disclosure implementation, - [Fig. 4]: [Fig. 4] shows a server according to one embodiment of the disclosure, - [Fig. 5]: [Fig. 5] shows the blood pressure data obtained and displayed by the sphygmomanometer according to one embodiment of the disclosure. - [Fig. 6]: [Fig. 6] shows examples of questions displayed by the blood pressure monitor according to one disclosure embodiment. - [Fig. 7]: [Fig. 7] shows an example of a display mode with notification levels on the remote monitoring interface according to an embodiment of the invention, - [Fig. 8]: [Fig. 8] shows an example of a display mode with enriched blood pressure data on the remote monitoring interface according to one embodiment of the invention. - [Fig.9]: [Fig.9] shows a matching database according to one embodiment of the invention, - [Fig. 10]: [Fig. 10] shows an RPM method executed by an RPM system, in accordance with an implementation of the disclosure, - [Fig.11]: [Fig. 11] shows an RPM method executed by the server, according to one disclosure implementation mode. Detailed description

[0031] Figure 1 illustrates a patient remote monitoring system 100, referred to as the RPM system 100. The RPM system comprises at least one physiological measurement device 110 (here a sphygmomanometer 110a, referred to as a sphygmomanometer, and / or a body scale 110b, and / or a multiscope 110c (as disclosed in EP24217550) or devices called BeamO™), but could include other devices, such as those disclosed in EP4386383 to Withings™, or U-Scan™ devices developed by Withings™), a remote monitoring interface 120, a server 130, and a communication network 140. The RPM system 100 may also include a mobile device 150, such as a smartphone or smartwatch. The remote monitoring interface 120 is configured to operate on a remote monitoring device (not shown in [Fig. 1]), which is located at a distance from the blood pressure monitor 110a. The mobile device 150 can be configured to run a close-range monitoring interface, tailored to the user.

[0032] The RPM 100 system is used by several people, defined as follows: the user of the blood pressure monitor 110a is called the patient, and the user of the monitoring device 140 is called the professional, since they are a healthcare professional, such as a nurse or a doctor. In an RPM system, the professional and the patient are generally not in the same room, but rather at their respective workplaces or homes, except for a specific appointment, such as a follow-up examination.

[0033] In a typical situation, the blood pressure monitor 110a measures the patient's blood pressure data and sends the blood pressure data to the server 130 via the communication network 140. The server 130 then sends the blood pressure data, or data derived from the blood pressure data, to the remote monitoring device 120, also via the communication network 140. As will be described in more detail, the RPM system 100 of this disclosure also allows for the addition of contextual information related to the blood pressure data. The close-up monitoring interface of the mobile device 150 allows the user to view the blood pressure data or any other related data.

[0034] The RPM 100 system is intended to collect blood pressure data from the patient, via the sphygmomanometer 110a, and to provide them to the professional, via the remote monitoring device 120.

[0035] The blood pressure monitor 110a, the remote monitoring device 120 and the server 130 all exchange data using the communication network 140, which can be a hybrid network (Ethernet, Wi-Fi, 3G, 4G, 5G, etc.).

[0036] The 110a sphygmomanometer

[0037] Figure 2 illustrates a 200 tensiometer corresponding to the 110a tensiometer of [Fig. 1]. The sphygmomanometer 200 comprises a housing 202, a user interface 204 mounted on the housing 202, and a blood pressure sensor 206. The user interface 204 includes a display 208 and input hardware 210. The display 208 can be a screen, as shown in [Fig. 2], or a speaker. From this point From the perspective of the 200 blood pressure monitor, the display 208 is intended to provide information to the user, while the input device 210 is intended to receive information from the user. The input device 210 may include buttons, as illustrated. Since the 200 blood pressure monitor is intended for elderly users, the simpler the input device 210, the better. Alternatively, or in addition, the input device 210 may include a touchscreen.

[0038] The blood pressure sensor 206 is represented as a cuff in [Fig.2], but the blood pressure sensor 206 generally includes the cuff, a pump (connected to the cuff by a flexible tube) and a pressure sensor configured to generate pressure data in the cuff.

[0039] As schematically shown in [Fig. 2], the blood pressure monitor 200 comprises a control unit 212, consisting of a processor 214, a memory 216, and an I / O (input / output) interface 218. The memory 216, which includes storage, is configured to store instructions that, when executed by the processor, enable the blood pressure monitor 200 to, among other things, take blood pressure measurements, display information on the display, and receive data from the user. The I / O interface 218 manages the interactions of the control unit 212 with the other components. A communication module 220 enables the blood pressure monitor 200 to exchange data, generally wirelessly, with the communication network 140. A battery 222 stores energy to allow the blood pressure monitor 200 to operate without being plugged into an electrical outlet.

[0040] In one embodiment, the communication module 220 is a cellular module capable of exchanging data on a cellular network of the communication network, so that no mobile device 150 is required to transmit the data generated by the tensiometer 110a.

[0041] The 110a blood pressure monitor can be shared by several users. To this end, each user has a user account. The data generated for the same user is associated with the same user account.

[0042] The 120 remote monitoring interface

[0043] Figure 3 illustrates a remote monitoring interface 300 corresponding to the remote monitoring interface 120 of Figure 1. The remote monitoring interface 300 can be operated by a monitoring device 302 using a control unit 304 capable of processing data, in particular receiving data from the server 130 and displaying data. The remote monitoring interface 300 is configured to allow interaction with the operator. To this end, the remote monitoring interface 300 may include a display 306, such as a monitor, and a hardware input 308, such as a keyboard and / or mouse, or a touchpad. The remote monitoring device 302 is generally a personal computer (e.g., a laptop).

[0044] The 300 remote monitoring interface is typically a software interface, which can be deployed as an application, for example accessible on an Appstore™, or as a web application or web page accessible from a browser. The 300 remote monitoring interface is generally provided as SaaS (Software as a Service).

[0045] As schematically shown in [Fig. 3], the control unit 304 comprises a processor 310, a memory 312, and an I / O (input / output) interface 314. The memory 312, which includes storage, is configured to store instructions that, when executed by the process, allow the monitoring device 302 to display information on the display 306 and receive user input via the hardware input 308. The I / O interface 314 manages the interactions of the control unit 302 with other components. A communication module 316 enables the monitoring device 302 to exchange data with the communication network 140. A battery 318 can store energy to allow the monitoring device to operate without being electrically connected.

[0046] To be considered as an RPM 100 system, the remote monitoring interface 120 is generally not activated on the blood pressure monitor 110a or the user's mobile phone, but only on the professional's monitoring device 302.

[0047] The remote monitoring interface 120, 300 allows the professional to access the data of different user accounts, including (and only) the user accounts of the user which are under an RPM program by the professional.

[0048] Server 130

[0049] [Fig.4] illustrates a server 400 corresponding to server 130 of [Fig.1]. Server 130 is a remote hardware unit configured to receive, store, and process data received from the 110a blood pressure monitor and to send blood pressure data or other related data to the 120 remote monitoring interface. Conversely, Server 130 is also configured to receive, store, and process data received from the 120 remote monitoring interface and to send data or other related data. Server 130 is typically located remotely from both the 110a blood pressure monitor and the 120 remote monitoring interface. Server 130 may be located in a data center, such as one provided by a data center vendor, the blood pressure monitor supplier, or the healthcare professional's hospital data center.

[0050] Server 400 can store user accounts (with all associated data) centrally and serves as a backup in the cloud.

[0051] As schematically shown in [Fig. 4], the server 400 comprises a control unit 402, consisting of a processor 404, a memory 406, and an I / O (input / output) interface 408. The memory 406, which includes storage, is configured to store instructions that, when executed by the process, allow the server 400 to query a lookup database, which will be described in more detail later. The I / O interface 408 manages the interactions of the control unit 402 with the other components. A communication module 410 allows the tensiometer 200 to exchange data, generally via a hardwired connection to the communication network 140.

[0052] The server 130, 400 may comprise several servers, for example, a first server provided by the blood pressure monitor supplier and a second server provided by the professional's facilities, the first and second servers exchanging data via the API (application programming interface), or a server storing the user's EHR (electronic health record). In the RPM system of the present invention, any combination of these servers is considered to be the server.

[0053] The RPM system

[0054] The description will now explain in more detail the operation of the RPM 100 system. In particular, the RPM 100 system aims to provide contextual information to blood pressure data so that the RPM system can adapt the display of blood pressure data on the remote monitoring interface 120. This allows the professional to triage users who need immediate support due to their blood pressure data from users whose blood pressure data has been negatively influenced by their behavior (lack of medication, physical exertion before measurement, etc.).

[0055] All data of the same user are associated with a user account.

[0056] Blood pressure data

[0057] The 110a blood pressure monitor is configured to obtain blood pressure data from the user. This function is well known and will not be disclosed in further detail. The blood pressure data can be displayed on the display 208, as shown in [Fig. 5]. However, since blood pressure data can be influenced by external factors, as previously mentioned, the RPM system requests contextual information.

[0058] In one embodiment, the data relating to blood pressure is an average value of several measurements, taken successively during the same session (for example three successive blood pressure measurements with a minute of rest between the two), or taken on different days.

[0059] Questions

[0060] To gather contextual information, the 110a blood pressure monitor is configured to display one or more questions to the user on the display 208. Generally, the question is displayed after the blood pressure data has been shown.

[0061] In one embodiment, the question is displayed regardless of the blood pressure data value; that is, the blood pressure data is not checked. This means that contextual information will be generated for each blood pressure reading, and therefore for each blood pressure measurement taken by the user. This allows the professional to gather much more information about the user's health, but it makes the blood pressure measurement process more cumbersome for the user, who may become impatient and stop taking their blood pressure.

[0062] In another embodiment, the question is displayed if the blood pressure data confirms a health condition. This avoids generating contextual information for blood pressure data considered, for example, to be healthy. The health condition can be a range of blood pressure data, for example, a systolic pressure value or range. The health condition can be that below 119 mmHg for systolic pressure, no question is displayed by the sphygmomanometer 110a.

[0063] The health condition can be adapted to each user, in particular by the professional, using the remote monitoring interface 120.

[0064] The health condition allows for avoiding interaction with the user when unnecessary and avoiding the generation of contextual data for the professional when also unnecessary. The objective of the RPM system in this disclosure is to streamline the process in order to improve the quality of remote monitoring by the professional. Therefore, any "noise" must be avoided.

[0065] Each question corresponds to a limited number of answers that the user can select on the screen using the input equipment, called predetermined answers.

[0066] In one embodiment, the question is a yes / no question, and one button is assigned to YES and another to NO. The 110a blood pressure monitor is thus particularly easy to use, especially for the elderly. Examples A) and B) in [Fig. 6] show a yes / no question on the 110a blood pressure monitor, with buttons 602 and 604 assigned to YES and NO, respectively.

[0067] In one embodiment, the question is a series of successive sub-questions and the possible answers for each question are a number, so that the predetermined answers for the question (here the series of successive sub-questions) are also a number, for example, all possible values ​​of the sum of all the numbers that answered the series of successive questions or the entire possible value of the average of these numbers.

[0068] The questions and predetermined answers for each question are stored in a question database. Each question and the plurality of predetermined answers constitute contextual data that can be selected by the user using input 210. The selected question and predetermined question constitute selected contextual data.

[0069] The following list provides non-exhaustive examples of questions and associated answers: Did you take your medication today? Yes / No; Did you rest for 5 minutes before taking your blood pressure? Yes / No; Did you sleep well? Yes / No; Did you eat a particularly salty meal? Yes / No. Other sample questions are provided in the documents cited in the introduction.

[0070] The question database is stored on the sphygmomanometer 110a, while a master question database is stored on the server 130, and a portion of this (the question database) is downloaded periodically by the sphygmomanometer 110a. The master question database can be updated, notably via the remote monitoring interface 120, by the professional, for example, to write specific questions for certain users. The master question database and the question database can be identical. However, if there are several health problems to address with different contextual data requirements, the master question database will be populated with a large number of questions.

[0071] The measured blood pressure data and the selected contextual data are associated and sent to server 130.

[0072] Notification level and display modes

[0073] One of the challenges of notification levels is managing the professional's attention span and the time available to assist users who require their help. However, some blood pressure readings may be abnormally high but less critical than others, particularly because recent user behavior has tended to increase the blood pressure readings. For example, several notification levels are available for managing blood pressure data at the remote monitoring interface 120.

[0074] For example, there may be three notification levels: green, yellow, and red. The green level means that the professional does not need to be alerted, while the yellow level means that the professional should consult the blood pressure data, and finally, the red level means that the professional must consult the blood pressure data as soon as possible. A fourth notification level can be implemented for cases that are not urgent but need to be examined: for example, blood pressure data of a patient with hypertension that are within the range of normal blood pressure values.

[0075] Depending on the notification level, the remote monitoring interface 120 can display different display modes. These different display modes must be evaluated for blood pressure data with contextual data. This means that identical blood pressure data with different selected contextual data, resulting in different notification levels for the blood pressure data, will have different display modes. In other words, different display modes show the blood pressure data differently.

[0076] In one embodiment, the arrangement of the different display modes varies according to the notification level. There is a predetermined number of display modes, corresponding, for example, to the number of notification levels.

[0077] For example, blood pressure data with a red notification level appears with a flag, while blood pressure data with a green notification level is not distinguished. [Fig. 7] illustrates an example of display modes 800, in which measurement 702 and measurement 706, both high blood pressure data with contextual data, do not appear in the same way because measurement 702 includes contextual data (see icon 704) on blood pressure data that triggered a lower notification level than measurement 706, which includes contextual data (see icon 708) on blood pressure data that triggered a higher notification level. A higher notification level implies a greater sense of urgency than a lower notification level. Measurement 706, for example, has a colored background, while measurement 702 does not.Just by looking at the display modes, the professional is informed that measure 706 presents a higher level of urgency than measure 702.

[0078] In one embodiment, the arrangement between the different display modes is standard for all notification levels, but there is a notification inbox, which is updated according to the assigned notification level. Figure 8 illustrates an example of a notification inbox, in which the green level is called "no alert", the yellow level is called "yellow alert", and the red level is called "red alert".

[0079] In one embodiment, the remote monitoring interface 120 displays enriched blood pressure data, i.e., the selected contextual data is displayed along with the blood pressure data. The RPM 100 system can slightly reformulate the selected contextual data to make them clearer. For example, the contextual data "Did you take your medication today? No" can be changed to "medication not taken today".

[0080] The notification level can also take into account the repetition of the same contextual data over time. For example, the notification level for blood pressure data of a user who has not taken their medication for two consecutive days can be increased by one level for each additional day.

[0081] The correspondence database

[0082] In particular, in the present disclosure, the RPM 100 system assigns a notification level to blood pressure data using this blood pressure data and selected contextual data. The selected contextual data is intended to increase or decrease the notification level of the blood pressure data relative to a non-contextual notification level, which is based solely on the blood pressure data. Selected contextual data combined with an increase in the blood pressure data value (e.g., no rest before measurement or no use of antihypertensive medication) tends to decrease the notification level (since external factors temporally increase the blood pressure data value, a high blood pressure data value is less critical).Selected contextual data associated with an accurate assessment or a decrease in blood pressure value tends to increase the notification level (the blood pressure value being at or below its actual value, a high pressure value is more critical), for the same blood pressure value.

[0083] To determine the notification level, a 900, 902 matching database illustrated in [Fig.9] can be used.

[0084] In one embodiment, the 900 matching database provides a notification level for blood pressure data with selected contextual data. To this end, the 900 matching database takes as input the blood pressure data (their value, for example, diastolic and systolic pressure values) and the question with the selected contextual data, and returns as output a notification level for the entered blood pressure data.

[0085] In this embodiment, the matching database 900 therefore includes, for at least the question displayed on the sphygmomanometer 110a (in one embodiment, for the entire question database stored in the sphygmomanometer 110a; in another embodiment, for all questions in the main question database), a table giving a notification level for all combinations of blood pressure values ​​(e.g., ranges of blood pressure data values) and predetermined answers for all questions in the database.

[0086] In one embodiment, the matching database 902 provides a variation in the notification level based on the selected blood pressure data and contextual data. To this end, the matching database 900 takes as input the blood pressure data (their value, for example, diastolic and systolic pressure values) and the question with the selected contextual data, and returns as output a variation in the notification level for the entered blood pressure data. The variation is then applied to a pre-existing notification level for the blood pressure data only (without contextual data).

[0087] The 900 matching database may include, as entries: - Ranges for blood pressure values. For example, systolic blood pressure ranges could be: less than 119 mmHg, between 120 and 139 mmHg, between 139 and 179 mmHg, and more than 180 mmHg (this is only an illustrative example and has no medical value). - Predetermined answers to each question, such as "Did you take your medication today?" or "Have you rested for 5 days?" or "Did you rest for 5 minutes before taking the measurement?". At each intersection of the entries, a notification level or a variation of the notification level is associated. The choice of notification level or variation of the notification level can be defined by the professional, for example, via the remote monitoring interface 120.This determination can be made by the professional on a user-by-user and / or disease-by-disease basis, to allow for better personalization of the notification level. Similarly, the number of notification levels can be determined by the professional, based on their own practices or the user's needs.

[0088] For example, assuming that there are only two ranges and two questions with two predetermined answers (such as YES or NO questions), the matching database comprises 2 ranges x 2 questions x 2 predetermined answers = 8 cells.

[0089] For example, as in the 900 matching database of [Fig.9], assuming that there are only four ranges and two questions with two predetermined answers (such as YES or NO questions), the 900 matching database comprises 4 ranges x 2 questions x 2 predetermined answers = 16 cells.

[0090] In practice, the 900 matching database can then be queried to obtain a notification level. The query includes entering the blood pressure data value (such as systolic and / or diastolic value) and contextual data (i.e., the question and predetermined selected answers) and returning the notification level associated with these entries.

[0091] The size of the matching database depends directly on the data relating to blood pressure (diastolic pressure, systolic pressure and / or heart rate), the number of questions and the number of predetermined answers for each question.

[0092] The matching database 900 can be stored on the blood pressure monitor 110a, the server 130, or the remote monitoring interface 120. The assignment of the notification level to the blood pressure data using this blood pressure data and the selected contextual data can be performed by the blood pressure monitor 110a, the server 130, or the remote monitoring interface 120. In one embodiment, since the server 130 is on the path of the blood pressure data and the selected contextual data from the blood pressure monitor 110a to the remote monitoring interface 120, the assignment of the notification level is performed by the server 130.

[0093] Resumption function

[0094] In certain cases, depending on the selected contextual data, the 110a blood pressure monitor may ask the user to provide further blood pressure data. For example, when the selected contextual data is "Have you rested for 5 minutes? No," the 110a blood pressure monitor may ask this before starting another blood pressure measurement.

[0095] Health condition

[0096] As previously stated, the 110a blood pressure monitor can check a health condition for blood pressure data before displaying a question. In another embodiment, the health condition is applied to other user health data collected by another measuring device of the RPM 100 system, such as weight data measured by a scale. For example, the RPM 100 system includes a scale, and the health condition is that there is a significant weight change over two consecutive days.

[0097] RPM Method

[0098] Figure 10 illustrates an RPM method using the RPM 100 system presented previously. The steps are executed either by the tensiometer 110a, or by the remote monitoring interface 120, or by the server 130.

[0099] In step 1002, the sphygmomanometer 110a obtains blood pressure data using the blood pressure sensor 206. The blood pressure data is stored in the sphygmomanometer 110a.

[0100] In step 1004, in one embodiment, the blood pressure monitor 110a checks whether the blood pressure data confirms a health condition. The health condition can be a range of values ​​for the blood pressure data, as previously stated. For example, the health condition is a high systolic value for the blood pressure data (e.g., greater than 140 mm Hg).

[0101] In step 1006, after determining that the blood pressure data verifies the health condition or, in the absence of such verification, after (or in fact before, to create a rest period for the user before taking the measurement) obtaining the blood pressure data 1002, the blood pressure monitor 110a displays a question on the display, along with a plurality of predetermined answers. The predetermined answers can be selected by the user using input 210. The plurality of predetermined answers associated with the question constitutes a plurality of contextual data.

[0102] In the absence of check 1004, the display of question 1006 can be carried out before obtaining the blood pressure data 1002. This slows down the blood pressure measurement process for the user and increases the quality of the measurement.

[0103] At step 1008, the sphygmomanometer 110a receives a predetermined response selected by the user by means of input input 210. The predetermined selected response (example: "YES") associated with the question (example: "did you take your medication today?") constitutes a selected contextual data point.

[0104] In step 1010, the blood pressure monitor 110a sends the blood pressure data and selected contextual data to the server 130 using the wireless communication module. The blood pressure data and the selected contextual data form a set, as they are associated with each other. The blood pressure data coupled with the selected contextual data can be called "enriched blood pressure data." In one variant, the enriched blood pressure data can be sent directly from the blood pressure monitor 110a to the remote monitoring interface 120.

[0105] At step 1012, server 130 assigns a notification level to the blood pressure data using the enriched blood pressure data, that is, using the blood pressure data and selected contextual data. The assignment of notification level 1012 is performed from among a plurality of available notification levels. More specifically, the assignment 1012 can be performed using a query on a matching database 900 stored on server 130, as previously described. In an alternative, the The 900 matching database can be stored on the 110a blood pressure monitor or the 120 remote monitoring interface, and the 1012 assignment is carried out respectively by the 110a blood pressure monitor or the 120 remote monitoring interface.

[0106] At step 1014, the remote monitoring interface 120 receives the blood pressure data enriched with the assigned notification level

[0107] At step 1016, the remote monitoring interface 120 displays a display mode based on the assigned notification level.

[0108] In one embodiment, the display mode includes the display of blood pressure data or enhanced blood pressure data with a specific presentation associated with the label. For example, a red notification level implies red font, while a yellow notification level implies yellow font.

[0109] In another embodiment, the display mode includes the display of a notification inbox, classified according to the notification level.

[0110] In one embodiment, a display mode may consist of not displaying blood pressure data, particularly when the notification level is minimum.

[0111] Fig. 11 illustrates an RPM method using the RPM 100 system presented earlier from the point of view of server 130.

[0112] In step 1102, the server 130 sends a database of questions to the sphygmomanometer 110a, the database of questions comprising at least one question and a plurality of predetermined answers for each question. The question and the predetermined answer constitute contextual data.

[0113] In step 1104, in one embodiment, the server 130 sends to the tensiometer 110a is a health condition. The health condition must be verified using blood pressure data.

[0114] In step 1106, the server 130 receives blood pressure data from the sphygmomanometer along with a predetermined answer to a question. The question and the selected predetermined answer constitute selected contextual data.

[0115] In step 1108, identical to step 1012, server 130 assigns a notification level to the blood pressure data. To this end, server 130 stores a matching database as described above.

[0116] At step 1110, server 130 sends the enriched blood pressure data and the assigned notification level to the remote monitoring interface.

[0117] Other achievements

[0118] In another embodiment, the RPM 100 system includes the close monitoring interface of the smartphone 150 and the question is displayed on the latter, rather than on the blood pressure monitor 110a.

[0119] In another case, the measuring device is replaced by a 110b bathroom scale, and the input material may include the weight sensor for selecting a response. Instead of monitoring blood pressure data, the RPM system here monitors weight. Contextual data may relate to lifestyle, meals, or responses related to heart failure symptoms.

[0120] More generally, the physiological monitoring device includes a user interface with a display and input hardware for receiving user data.

[0121] In another embodiment, the physiological measuring device 110 is a device capable of measuring temperature, blood oxygen saturation, lung or heart sounds, and / or capable of taking an electrocardiogram. An example of such a device is given in document EP24217550. In particular, this device includes a display and input material very similar to that of the blood pressure monitor 110a.

Claims

Demands

1. Patient remote monitoring system, RPM, (100), comprising: • a sphygmomanometer (110a, 200), comprising: • a case (202), • a user interface (204) mounted on the housing, comprising a display (208) and input hardware (210), • a blood pressure sensor (206) configured to generate blood pressure data from a user, • a wireless communication module, • a remote monitoring interface (120), configured to operate on a remote monitoring device (302), in which the remote monitoring device (302) and the blood pressure monitor (110, 200) are two separate devices, in which the blood pressure monitor is configured to send data to the remote monitoring interface using the wireless communication module, in which the RPM (100) system is configured for: - obtain (1002) blood pressure data using the blood pressure sensor of the blood pressure monitor, - display (1006) on the display of the blood pressure monitor (110a) a question accompanied by a plurality of predetermined answers, the question and the plurality of predetermined answers forming a plurality of contextual data, - receive (1008) a predetermined answer selected by the user using the input material of the blood pressure monitor, the question and the selected predetermined answer forming selected contextual data, - assign (1012) a notification level to the blood pressure data using the blood pressure data and the selected contextual data, the notification level being chosen from a plurality of available notification levels, - display (1016) on the remote monitoring interface a display mode based on the assigned notification level.

2. The RPM system according to claim 1, wherein the plurality of available notification levels comprises between 3 and 5 notification levels.

3. The RPM system according to claim 1 or 2, wherein the remote monitoring interface comprises several display modes, each display mode comprising a dedicated presentation corresponding to a notification level, such that the display modes show blood pressure data, for which contextual data are available, differently depending on the notification level.

4. The RPM system according to any one of claims 1 to 3, wherein the display mode includes a notification inbox, updated according to the assigned notification level.

5. The RPM system according to any one of claims 1 to 4, wherein the blood pressure data are an average of several blood pressure values.

6. The RPM system according to any one of claims 1 to 5, wherein the display of the question is performed in response to the determination that blood pressure data verifies a health condition.

7. The RPM system according to claim 6, wherein the health condition is modifiable via the remote monitoring interface.

8. The RPM system according to any one of claims 1 to 7, wherein the display mode includes the display of blood pressure data with the selected contextual data.

9. The RPM system according to any one of claims 1 to 8, further comprising a server (130), in which: - the wireless communication module of the blood pressure monitor sends the blood pressure data and the selected contextual data to the server, - the remote monitoring interface receives from the server the blood pressure data, the selected contextual data and the assigned notification level.

10. The RPM system according to any one of claims 1 to 9, wherein the assignment of the notification level comprises: - querying a matching database using selected blood pressure data and contextual data, wherein the matching database links a plurality of notification levels or variations of notification level to ranges of values ​​for the blood pressure data and contextual data, wherein the variations of notification level are applicable to a pre-existing notification level based solely on the blood pressure data.

11. The RPM system according to claims 9 and 10, wherein the matching database is stored on the server and the assignment is performed by the server.

12. The RPM system according to claim 10, wherein the matching database is stored on the tensiometer and the assignment is performed by the tensiometer.

13. The RPM system according to any one of claims 10 to 12, further comprising a remote monitoring device (302) configured to execute the remote monitoring interface (120), in which the base

14.

15.

16. Correspondence data is stored in the remote monitoring device (302). The RPM system according to any one of claims 10 to 13, wherein the matching database is modifiable via the remote monitoring interface. The RPM system according to any one of claims 1 to 14, wherein the wireless communication module is a cellular module. A method for remote patient monitoring, using an RPM system according to any one of claims 1 to 15, the method comprising: - Obtain blood pressure data using the blood pressure sensor of the sphygmomanometer, - display a question accompanied by several predetermined answers, the question and the predetermined answer forming predetermined contextual data, - receive a predetermined response selected by the user using the input material, the question and the selected predetermined response forming selected contextual data, - Assign a notification level to blood pressure data using the selected blood pressure and contextual data, with the notification level chosen from a plurality of available notification levels. - display on the remote monitoring interface a display mode based on the assigned notification level.

Images