A COMPUTER-IMPLEMENTED SYSTEM AND METHOD FOR ALERTING AN EXPECTANT MOTHER TO A MEDICAL RISK DURING PREGNANCY

Abstract

A computer-implemented system and method are for alerting an expectant mother to a medical risk during pregnancy. A profile of the expectant mother is used, and reports are received from the expectant mother identifying experienced symptoms. In response to a report at a particular time, any reports received over a subsequent time window are monitored, and based on the combination of reports received during the time window and the profile of the expectant mother, the need for a risk alert is determined. The user is more willing to report symptoms, because a risk alert (which functions as reporting symptoms to a medical expert) only takes place when a real risk is identified.

Claims

1. A computer-implemented system for alerting an expectant mother to a medical risk during pregnancy, comprising: a database of pre-stored possible symptoms including at least headache, blurred vision, vomiting, swelling, rashes, joint pain, and fever; an input interface adapted to receive: a profile of the expectant mother, including at least timing information in respect of her pregnancy; and reports provided by the expectant mother identifying experienced symptoms from said pre-stored possible symptoms, when those symptoms arise; a processor; and an output interface for outputting a risk alert, wherein the processor is adapted, in response to a report at a particular time, to monitor any reports received over a non-zero time window following that report, and determine, based on the combination of reports received during the time window and the profile of the expectant mother, whether or not to generate and output a risk alert.

2. The system as claimed in claim 1, wherein the processor is adapted to select the time window duration depending on the symptom reported at the particular time.

3. The system as claimed in claim 1, wherein the profile of the expectant mother further includes one or more of her age, body mass index, and ethnicity.

4. The system as claimed in claim 1, wherein the profile of the expectant mother includes a general risk level associated with general health of the expectant mother and/or with specific medical conditions or history of the expectant mother.

5. The system as claimed in claim 1, wherein the time window has a duration of between 24 hours and 1 week, optionally an integer number of days from 1 to 7.

6. The system as claimed in claim 1, wherein the reports provide an indication of a nature of a symptom and a severity of the symptom, and the risk alert is generated in dependence on the nature, the severity, frequency, and trends of the reported symptoms within the time window.

7. The system as claimed in claim 1, wherein the processor is further adapted, in response to a reported symptom: to generate advisory information for output using the output interface presenting advice in respect of alleviating measures or precautionary actions relating to the symptom; and/or to request further input from the expectant mother in respect of related symptoms that she may be experiencing.

8. The system as claimed in claim 1, further comprising a memory for storing the reports and the risk alert, to create an overall pregnancy profile of the expectant mother.

9. The system as claimed in claim 1, further comprising a communications unit for sending the risk alert automatically to an antenatal care provider of the expectant mother.

10. The system as claimed in claim 1, wherein the input interface is further adapted to receive physiological parameters of the expectant mother monitored by physiological sensors.

11. The system as claimed in claim 1, wherein the input interface and the output interface are implemented on a mobile phone or tablet.

12. A processor for generating a risk alert for alerting an expectant mother to a medical risk during pregnancy, comprising: an input adapted to receive profile data of the expectant mother, including at least timing information in respect of a pregnancy and reports provided by the expectant mother identifying experienced symptoms, wherein said experienced symptoms are selected from a database of pre-stored possible symptoms including at least headache, blurred vision, vomiting, swelling, rashes, joint pain, and fever, wherein the processor is adapted, in response to a report at a particular time, to monitor any reports received over a non-zero time window following that report, and determine, based on the combination of reports received during the time window and the profile of the expectant mother, whether or not to generate a risk alert.

13. A computer-implemented method for alerting an expectant mother to a medical risk, comprising: providing a profile of the expectant mother to a computer-implemented system, including at least timing information in respect of a pregnancy; providing reports to the computer-implemented system identifying symptoms experienced by the expectant mother, wherein said experienced symptoms are selected from a database of pre-stored possible symptoms including at least headache, blurred vision, vomiting, swelling, rashes, joint pain, and fever; using a processor of the computer-implemented system, in response to a report at a particular time, to monitor any reports received over a non-zero time window following that report, and determine, based on the combination of reports received during the time window and the profile of the expectant mother, whether or not to generate and output a risk alert; and outputting a generated alert to the expectant mother as a result of the risk alert being generated.

14. A non-transitory computer readable medium having computer-executable instructions for performing a method of running a software program on a computing device, the computing device operating under an operating system, the method including issuing instructions from the software program comprising the method of claim 13.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0061] For a better understanding of the invention, and to show more clearly how it may be carried into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0062] FIG. 1 shows a computer-implemented system for alerting an expectant mother to a medical risk during pregnancy; and

[0063] FIG. 2 shows a computer-implemented method for alerting an expectant mother to a medical risk during pregnancy.

DETAILED DESCRIPTION OF THE EMBODIMENTS

[0064] The invention will be described with reference to the Figures.

[0065] It should be understood that the detailed description and specific examples, while indicating exemplary embodiments of the apparatus, systems and methods, are intended for purposes of illustration only and are not intended to limit the scope of the invention. These and other features, aspects, and advantages of the apparatus, systems and methods of the present invention will become better understood from the following description, appended claims, and accompanying drawings. It should be understood that the Figures are merely schematic and are not drawn to scale. It should also be understood that the same reference numerals are used throughout the Figures to indicate the same or similar parts.

[0066] The invention provides a computer-implemented system and method for alerting an expectant mother to a medical risk during pregnancy. A profile of the expectant mother is used, and reports are received from the expectant mother identifying experienced symptoms. In response to a report at a particular time, any reports received over a subsequent time window are monitored, and based on the combination of reports received during the time window and the profile of the expectant mother, the need for a risk alert is determined. The user is more willing to report symptoms, because a risk alert (which functions as reporting symptoms to a medical expert) only takes place when a real risk is identified.

[0067] FIG. 1 shows a computer-implemented system 10 for alerting an expectant mother to a medical risk during pregnancy. The system comprises a user terminal 12, which is for example in the form of a smartphone or tablet on which a suitable computer program is loaded.

[0068] The user terminal comprises an input interface 14 which is adapted to receive inputs from the user. These inputs may be input manually or they may be received automatically from sensors or other sources of information.

[0069] The inputs comprise a profile, P, of the expectant mother, including at least timing information in respect of her pregnancy, i.e. the gestational stage of her pregnancy.

[0070] This profile typically also includes her age, BMI and ethnicity. The profile may also include a general risk level associated with her general health or with any specific medical conditions or history.

[0071] The inputs also include reports, R, provided by the expectant mother identifying experienced symptoms. These reports may be provided manually by the expectant mother, but to simplify use of the system, they may be selected from a menu of possible symptoms supported by the system. For this purpose, there is database 20 of pre-stored possible symptoms, from which the expectant mother can select. This database is in practice simply an area of memory of the mobile phone or tablet in which data is stored. The pre-stored possible symptoms for example include at least headache, blurred vision, vomiting, swelling, rashes, joint pain, fever and bleeding.

[0072] The reports may not only identify the nature of a symptom but also indicate the severity of the symptom, so that a progression of symptom severity can be tracked.

[0073] The input interface 14 further optionally receives physiological sensing parameters, PS, of the expectant mother monitored by physiological sensors. These may for example comprise blood pressure and heart rate.

[0074] The input interface is typically the touch screen or a separate keyboard of the device, although any suitable input interface may be used such as using voice recognition.

[0075] The user terminal has a processor 16 and an output interface 18, most importantly for outputting a risk alert, RA.

[0076] The output information may additionally comprise advisory information, AI, presenting advice in respect of alleviating measures or precautionary actions relating to the symptom. The output information may further comprise a request for further input, RFI, from the expectant mother in respect of related symptoms that she may be experiencing. In this way, the system can check if there are multiple related symptoms.

[0077] The user terminal also comprises a memory 22 for storing all reports (and all risk alerts, discussed below) to create an overall pregnancy profile as a timeline of events. This may be used by a medical practitioner to provide a full history of the pregnancy.

[0078] The processor is the processor of the mobile phone or tablet and the output interface is the screen and microphone, or else the output interface may comprise a wireless communications system for communicating with another remote device.

[0079] In order to determine if a risk warning is needed, the processor 16 starts a time window when a first report of a symptom is received, e.g. following a period of no reports or after the end of any previous time window. The time window may have fixed duration, or it may have a duration which depends on the nature of the first symptom recorded. During this time window, any reports received following that first report are monitored. Based on the combination of reports (and the optional physiological parameter sensing) received during the time window, and the profile of the expectant mother, it is determined whether or not to generate and output a risk alert. A risk alert is generated in dependence on the nature, severity, frequency and trends of the reported symptoms and physiological parameters within the time window.

[0080] If a symptom reported is severe by itself, a risk alert can be generated immediately. However, if the symptom is not sufficiently severe, because it may be a normal side effect to be expected (based on the other profile information), then the monitoring continues for the remainder of the time window. If the progression of symptoms or physiological parameters indicates that in fact there is a risk of a medical complication, the risk alert is generated.

[0081] The time window for example has a duration of between 1 day and 1 week, such as between 2 days and 4 days, such as 3 days.

[0082] FIG. 1 also shows a computer system 24 of an antenatal care provider. Any risk alerts RA are also automatically sent to the antenatal care provider of the expectant mother, i.e. to the computer system 24.

[0083] FIG. 2 shows a method for alerting an expectant mother to a medical risk.

[0084] In step 30, the expectant mother registers with the system. This involves inputting part of the data that forms the user profile. A health care professional for example introduces the system to the expectant mother and instructs her to register, by filling in her personal information via the app running on the user terminal.

[0085] In step 32, the caregiver receives the registration notice via a professional carer app interface on the system 24. The registration notice confirms that a client has registered in the system.

[0086] The health care professional then enters the gestational age (after a scan) and any remaining information for the user profile, such as other related medical information.

This activates the reporting cycle.

[0087] Thus, a profile of the expectant mother has then been input to the system, including at least timing information in respect of the pregnancy, for example age, expected due date, BMI, ethnicity/race, language preference etc. It may include existing medical conditions and history.

[0088] In step 32, a risk profile may also be selected for that user, e.g. high risk, low risk or medium risk. This may depend on the medical history of the user and any finding from blood tests or ultrasound imaging of the fetus. The risk level for example sets the thresholds at which a risk alert is triggered in a user-dependent manner. The risk level is for example selected by the caregiver.

[0089] The description that follows applies to all risk profiles, but the determination of whether a risk alert is considered appropriate will take account of that risk profile.

[0090] In step 34 the user (expectant mother) is able to provide a report to the system identifying symptoms experienced. This may be based on a drop down menu system, for example. The method waits for a symptom to be reported in step 36, although automatic physiological monitoring may indicate that a symptom is present. In step 36, it is determined if the symptom that has been reported relates to a potential risk.

[0091] If the symptom is related to a potential risk, it is determined in step 38 whether the reported symptom is sufficiently serious for a risk alert to generated straight away, in step 40.

[0092] If the symptom is not indicative of an emergency and hence immediate reporting is not needed, a time window is opened, in step 42. In step 44, the user is again able to provide further reports to the system identifying symptoms experienced. For any reported symptom, it is determined in step 46 if, in combination with the previously reported symptoms within the time window, a risk alert should be made. Alternatively, if the newly reported symptom is sufficiently serious alone, a risk alert is needed. (e.g. a bleed), In either case, the method can jump to step 40 when a risk alert is needed.

[0093] If not, there is continued physiological monitoring during the time window, if physiological monitoring is used. During the time period of the time window, the user may optionally be requested to consider if other specific symptoms are present, in step 48, to assist the system in gathering all relevant information. This may for example be particularly relevant if some symptoms are repeatedly being reported or with increasing severity. Even if symptoms are all mild, they may in combination be indicative of a more serious condition.

[0094] This continues, until the time window has ended as determined in step 50.

[0095] Once a time window expires, a new one will be opened by a new reporting of a subsequent symptom by the user. Thus, once the time window has expired without a risk alert, a new time window can start when there is a next reported symptom. In the example described herein, the algorithm will not consider reports that occurred in a previous time window in order to make the risk assessment. However, all reporting will be logged, and if a risk flag is eventually raised (in a new cycle), health care professionals can review the onset of previous reported symptoms to assess the potential risk level.

[0096] The purpose of the system is basically to flag an imminent emerging risk before it becomes an acute condition, and typically before a next scheduled medical meeting.

[0097] Note that a time window of around 3 days is considered suitable for most risk conditions (except a small number of risks that may require a window of different length).

[0098] Risks that develop more slowly (i.e. over a longer period of time than the time window) will be identified during regularly scheduled (e.g. weekly or fortnightly) antenatal care visits. For example, the World Health Organization's antenatal care model recommends that all pregnant women should have eight contacts with a health provider throughout pregnancy.

[0099] The time window may instead be thought of as a moving window, so that for any reported symptom, the immediately preceding history for the already-existing duration of the time window is take into account in determining whether there is a need for a risk alert. Thus, the analysis looks back at previous history.

[0100] Once a symptom related to a potential risk has been used to open the time window, the prompting of the user interface will try to pro-actively establish if a user may be experiencing any other symptoms related to the same underlying risk.

[0101] For the example represented in FIG. 2, at the end of the time window, a (further) risk assessment is made in step 52. This is of course optional, if all required risk assessment has been completed in step 46. This may take account of the risk profile of the user.

[0102] Each risk assessment (e.g. in step 46 or in the final assessment in step 52) takes account of the nature of the reported (or detected) symptoms and the severity of the symptoms, as well as the frequency and trends of the symptoms within the time window. The risk assessment involves identifying deviations from the expected physiological development timeline of the patient group corresponding to the user, such as the patient group for that particular gestational age etc. Thus, there is mapping of reported symptoms to the expected physiological development of the user, and the expected development of symptoms of the user associated with the progression of a pregnancy. The invention provides real time analysis for enabling early intervention.

[0103] In step 54, it is then determined if there is an issue to report. This may for example be based on an increased overall risk level. If a risk alert is needed, it is reported in step 40. This report may be to the user and to a caregiver of the user. The user history is then updated in step 56.

[0104] If in step 54 it is determined that there is no need to issue a risk alert, other actions may still be taken. In step 58, output information may be provided to the user, for example giving tips or advice about avoiding or alleviating the symptoms. For example, tips may be given about dealing with nausea. Advice may be given about medication that should or should not be taken e.g. as a headache remedy. Note that this step 58 may also take place during the time window (e.g. with step 48), not only at the end as shown.

[0105] The user history is then updated in step 56. Thus, regardless of whether a risk alert is needed, all information is stored as part of the user history.

[0106] Thus, the operation of the system overall is that in response to a report, any reports received over a time window following that report are monitored, and based on the combination of reports received during the time window and the profile of the expectant mother, it is determined whether or not to generate and output a risk alert. The algorithm in particular recognizes symptoms or patterns of different symptoms, such as identified in national health guidelines, in order to trigger an alert.

[0107] When the user (pregnant woman) reports symptoms the algorithm checks whether the reported symptom may be linked to a potential risk. If it finds a positive correlation, the system prompts the user (in step 48) and asks questions to determined whether she has other related symptoms that in combination would increase the chance of that risk condition. The questions are provided with the pre-defined time window after a symptom is actively reported by the woman. This takes account of the fact that not all symptoms of a risk condition often appear at once.

[0108] By way of example, a pregnant woman in her 20th week of pregnancy may vomit in the morning but only have severe headache and blurred vision starting later in the day. If the user experiences vomiting in the morning but does not have other symptoms, she will naturally only report vomiting as the only symptom of her condition. When she experiences headache and blurred vision later on during the day, she may not naturally feel the need to report as she may associate that as further side effects linked to the first symptoms.

[0109] The time window allows the system to prompt the user to check whether her last reported symptom still persists and whether she has additional signs of symptoms that could be linked to a risk condition. The prompting method enables pregnant women to feel at ease in reporting symptoms without being stigmatized as being paranoid. It also helps the user to be aware of their symptoms.

[0110] As antenatal care visits are typically scheduled over weekly intervals, another advantage of the invention is to be able to alert both user and caregiver for diagnostics, that are earlier than scheduled visits. This system also helps to keep track of all symptoms reported by the woman throughout her pregnancy, so that professional caregivers can use this additional information to create a holistic view of the patient case.

[0111] It is noted that the processing carried out by the system may be performed within the user terminal or it may be performed remotely. For example, the processor may be on a remote server and the phone or tablet is essentially only used as interface to the server. The processing may take place at one location or it may be distributed. The system is of particular interest when health care professionals (midwife/obstetrician) monitor any risk alerts generated by the user terminal. Thus, the health care professional uses their own a care provider interface to access the system, and the care provider is also registered to the system. Thus, the expectant mother women is registered with a health care professional who will monitor her symptoms as reported via the system.

[0112] The input interface and output interface have been discussed above. In each case, the “interface” may support different types of input and output. For example, data may be input manually by interaction with the device or by data communication from a remote device. There may be multiple modes of inputting data, such as by sound, touch or by connection to a keyboard. Similarly, data may be output directly from the device (by a screen and/or speaker) or by sending data to another output device.

[0113] Variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure and the appended claims. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. The computer program may be stored/distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. If the term “adapted to” is used in the claims or description, it is noted the term “adapted to” is intended to be equivalent to the term “configured to”. Any reference signs in the claims should not be construed as limiting the scope.