GB2544338A - Electonic method and system for data provision - Google Patents

Abstract

Dose quantity and dose frequency of a prescribed drug is extracted from a received text string. A dosage matrix (figure 3) of instances per day against number of days is configured and mapped onto a calendar for recording when the drug should be taken. An indication of consumption or the amount of medication remaining may be presented on a display 116. An audible or visual alarm may be activated when the medication is scheduled to be taken or when the remaining supply is low. An image of a drug box label may be captured (703, figure 7) by a mobile communication device 115, for example a smart phone or tablet, and text may be extracted using optical character recognition, OCR (704, figure 7). Processing circuitry 102 may determine dose quantity and frequency via sentence syntax analysis on an extracted text string. The name, strength and form of medication may be verified using a drug database or library 110. The system allows a patient to provide accurate information to their GP surgery 104 or pharmacy 106 when requesting a repeat prescription using their mobile phone 115.

Description

ELECTRONIC METHOD AND SYSTEM FOR DATA PROVISION Field of the invention

The field of this invention relates to an electronic method and system for data provision.

Background of the Invention

Current prescription services permit a medical prescription (including a repeat prescription) to be sent electronically (over the Internet for example) directly from a patient’s GP (general practitioner) surgery to a pharmacy. An issued medical prescription typically includes the identity of the patient, the name, strength, form and quantity of the drug required and the dosage (for example a phrase such as “take one tablet twice a day” or “take two tablets three times a day every four days”). When a medical prescription has been received at the pharmacy, the pharmacy can contact the patient (by email, text message, mobile phone or landline for example) to let the patient know that the drug is ready for collection.

Some patients may have difficulty in working out exactly when they should take their medication, especially in cases such as the example given above where the medication is not taken every day but “three times a day every four days.” Also, not all patients are diligent in remembering to take their medication at the correct times nor may they have the time to work out when the medication is going to run out and when they should be ordering a repeat prescription from their GPs surgery. Hence, it would be beneficial to provide a means for alerting the patient when it is time to take their medication and to monitor the usage of the medication so that the patient can be prompted to make a request for a repeat prescription at an appropriate time.

When making a request for a repeat prescription, the patient may send a request (by email for example) to the GP surgery. This relies on the patient correctly identifying the name of the drug, strength (in milligrams, for example) and form (tablet or capsule, for example). If the patient makes a spelling mistake with the name of the drug or forgets to include the strength or mis-types it for example, then it may not be possible to process the request. Therefore, it would be beneficial to provide a means for enabling the patient to provide accurate and complete information to the GP surgery when submitting a request for a repeat prescription.

Summary of the invention

Aspects of the invention provide apparatus and methods as described in the appended claims.

According to a first aspect of invention, there is provided a computer-implemented method comprising: receiving a description of a drug to be prescribed wherein said description includes a text string relating to dosage; extracting from said text string a dose quantity and a dose frequency; from said extracted dose quantity and dose frequency, configuring a dosage matrix of instances per day against number of days comprising a dosage cycle; and mapping the dosage matrix onto a calendar for recording when the drug should be taken.

In one example, dose quantity and dose frequency may be determined by performing a sentence syntax analysis on the text string.

In one example, the text string has the form “take x capsule(s)/tablet(s) y times a day” where x and y are integers. Other, additional and/or alternative examples may refer to a quantity of liquid(s), cream(s), ointment(s), powder(s), gel(s) or any other known formulation, for example for cutaneous and/or inhalation applications, rather than or in addition to tablets or capsules. Another example of a text string may take the form “take x tablet(s) y times a day every z days” and/or “take x tablet(s) y times every z day(s) and take w tablet(s) on the remaining days” (where w and z are also integers). It will be appreciated that the aforementioned text strings are exemplary only and any other text string formulation and/or combination of the aforementioned text strings may be provided.

In one example, the prescription includes information relating to the total quantity of medication provided and the method further includes monitoring consumption of the medication. A start date for taking the medication may be estimated. An indication of consumption of the medication may be presented to a patient taking the medication as an amount (for example a percentage) of medication remaining. An audible or visual alarm may be activated for alerting the patient when the remaining supply of medication is running low. The amount of medication remaining may be adjusted if one or more doses are missed.

An audible or visual alarm may be activated in order to alert the patient when it is time for the medication to be taken. In one example, the name of the medication to be taken is also presented to the patient.

In additional or alternative example, the dosage matrix is provided to a mobile communication device which includes a calendar function and a display screen.

In one optional embodiment, the method comprises, in a mobile communication device having an image capture facility, capturing an image of printed matter which includes a name, strength and form of a medication, wherein the method further comprises extracting text comprising the name, strength and form of the medication from the captured image and displaying the extracted text on a display screen of the mobile communication device.

In one additional or alternative example, extracting text comprises searching for a word by finding spaces to the left and right of identified characters that comprise the word. Optionally, the extracted name, strength and form of the medication may be checked (and/or verified and/or identified) by searching a drug database.

According to a second aspect of the invention, there is provided a patient medication management system, the system comprising first signal processing circuitry for receiving a description of a drug to be prescribed wherein said description includes a text string relating to dosage; extracting from said text string a dose quantity and a dose frequency; from said extracted dose quantity and dose frequency, configuring a dosage matrix of instances per day against number of days comprising a dosage cycle; the system comprising second signal processing circuitry for receiving the dosage matrix and for mapping the dosage matrix onto a calendar function for recording when the drug should be taken.

The first signal processing circuitry may be located in a pharmacy where the prescription may be received from a GP surgery.

The second signal processing circuitry and calendar function may be included a mobile communication device said device also being provided with a display screen for indicating to a patient when the drug should be taken.

In one optional embodiment, the mobile communication device includes an image capture facility for capturing an image of printed matter which includes a name, strength and form of a medication, wherein the system further includes processing circuitry for extracting text comprising the name, strength and form of the medication from the captured image for displaying the extracted text on the display screen of the mobile communication device.

In one example, the processing circuitry may be arranged to search for a word in the captured image by finding spaces to the left and right of identified characters that comprise the word. Optionally, the extracted name, strength and form of the medication may be checked (and/or verified and/or identified) by searching a drug database.

According to a third aspect of the invention, there is provided a tangible computer program product having executable program code stored thereon for executing a process to perform patient medication management methods as described herein.

The tangible computer program product may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable

Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.

In a further embodiment, there is disclosed a computer-implemented method comprising: receiving a text string comprising two or more data fields; extracting from said text string data from the two or more data fields; wherein the extracted data is indicative of a quantity and frequency; constructing a matrix of instances based on the extracted data; and triggering an alert based on the extracted data as set out in the constructed matrix of instances. The text string may comprise dosage quantity and frequency data in respect of a prescribed medication, and preferably, wherein the matrix of instances calculates a dosage cycle based on the dosage quantity and frequency. In some preferable embodiments, the trigger may be in the form of a calendar providing an indication that a drug and/or medication should be taken.

These and other aspects, features and advantages of the invention will be apparent from, and elucidated with reference to, the embodiments described hereinafter.

Brief Description of the Drawings

Further details, aspects and embodiments of the invention will be described, by way of example only, with reference to the drawings. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. Like reference numerals have been included in the respective drawings to ease understanding.

Figure 1 is a schematic block diagram of patient medication management system in accordance with an embodiment of the invention;

Figure 2 is a simplified flowchart illustrating a process for operating a patient medication management system in accordance with a first embodiment of the invention;

Figure 3 illustrates a matrix for determining when medication should be taken;

Figure 4 is a table illustrating examples of medication dosages;

Figure 5 illustrates a first dosage matrix;

Figure 6 illustrates a second dosage matrix;

Figure 7 is a simplified flowchart illustrating a process for operating a patient medication management system in accordance with a second embodiment of the invention;

Figure 8 illustrates a touchscreen configuration for image capture;

Figure 9 illustrates a captured image on a touchscreen; and

Figure 10 is a simplified flowchart illustrating a process for extracting textual descriptors for use in the second embodiment.

Detailed Description of the preferred embodiments

Those skilled in the art will recognise and appreciate that the specifics of the specific examples described are merely illustrative of some embodiments and that the teachings set forth herein are applicable in a variety of alternative settings.

Referring now to figure 1, a patient medication management system 100 comprises a server 101 which includes a signal processor 102, whose purpose and function will be described below, and a store 103. The server 101 may communicate with a GP surgery 104 over a communications link 105. The server 101 and GP surgery 104 may communicate with a pharmacy 106 over communication links 107 and 108 respectively. The pharmacy includes a processor circuit 109, whose purpose and function will be described below, and a library 110. The pharmacy 106, server 101, and GP surgery 104 may all communicate over wireless links 111, 112, 113 respectively with a mobile communications device 115. The mobile communications device 115 includes a display screen 116, a processor 117, whose purpose and function will be described below, and a loudspeaker 118 for providing an audible alarm to a user of the mobile communications device 115. In this particular example, the display screen 116 is a touchscreen and the mobile communications device is a mobile phone or “smart phone”. It will be appreciated that any other mobile communications device may be used including but not limited to an iPad, tablet, laptop, or any other portable device. A method for patient medication management will now be described with reference to figure 1 and the flowchart of figure 2. At 201, a prescription for medication is prepared (in respect of a patient who is the user of the mobile communications device 115) at the GP surgery 104. At 202, the prescription is received at the pharmacy 106 and may also be received at the server 101 by way of one of the communication links 108 and 105. The communication links 108, 105 and also 107 may be hosted by an Internet service provider (not shown) for example. The prescription typically comprises the following information: the identity of the intended recipient of the medication (in this example the user of the mobile communications device 115), and a text string giving a name, strength, form and quantity of the medication. For example, “venlafaxine 15mg capsules 28 capsules.” The prescription also typically comprises a text string giving a dosage instruction such as “take one tablet twice a day.” At 203, the medication is prepared from the prescription at the pharmacy 106 and the pharmacy may notify the server 101 and the mobile communications device 115 via the communication links 107 and 111 of a date when the medication will be available for collection. Alternatively, the server 101 may notify the mobile communications device 115 of this date over the wireless communication link 112.

The method then proceeds to step 204 and subsequently to step 205. Both of these steps may be carried out by the signal processor 102 in the server 101 and/or by the processor circuit 109 in the pharmacy 106. The signal processor 102 and processor circuit 109 are configured to perform a sentence syntax analysis function on the received dosage text string. This type of analysis function can operate typically to tokenise a sentence into space delimited strings of characters. Each word in the sentence is tagged and identified in terms of type of lexical item (or part of speech). In the above example “take one tablet twice a day” the words “tablet” and “day” are classified as nouns and the word “twice” as an adverb. A sentence syntax tree can then be generated, at 204, using known linguistic rules. Using known sentence structures for describing quantity and frequency, words denoting these values (of quantity and frequency) are then identified. Following identification of the values, the signal processor 102 and/or processor circuit 109 are configured to operate further on these values by parsing them into numeric values and using the numeric values to populate a dosage matrix at step 205.

Reference will now be made to figures 3, 4, 5 and 6. Figure 3 shows a matrix of instances per day against cycle (days). A number of times (instances) per day which medication needs to be taken ranges from 1 to an integral value “m.” A value for cycle ranges from one day to an integer “n” days. The value “m will be the maximum number of instances occurring on any day within the cycle. Figure 4 is a table comprising two columns labelled “regime” and “cycle” where “regime” means the frequency of a dose. For example, when the medication needs to be taken daily, then the cycle is one day. In a case where medication needs to be taken on alternate days, then the cycle is two days. If the medication needs to be taken three times a week, then the cycle is seven days. These and other examples are illustrated in the table of figure 4. Based on the matrix of figure 3 and the table of figure 4, a dosage matrix can be populated and two examples of these are given in figures 5 and 6. In figure 5 the dosage instruction is “take one tablet three times a day. Flence, the dosage matrix comprises one column and three rows, each row in the single column being populated with the number “1.” In figure 6, the dosage instruction is “take 2 tablets three times a day every four days.” The dosage matrix in this case thus comprises four columns and three rows. All three rows of the first column (which relates to the first day in the cycle) are populated with the number 2 and all rows of the subsequent three columns are populated with the number 0.

Returning again to figure 2, at 206, data relating to the received prescription and the computed dosage matrix are stored in the library 110 of the pharmacy 106 and/or the store 103 of the server 101. Advantageously, when the same dosage instruction is received again, a look-up operation can be performed in order to extract the relevant dosage matrix rather than repeating steps 204 and 205.

At 207, the mobile communications device 115 receives the dosage matrix from either the server over the wireless communication link 112 or from the pharmacy over the wireless communication link 111. The mobile communications device 115 also receives (from the pharmacy 106 or the server 101) the identity of the medication to which the dosage matrix relates and the total quantity prescribed. At 208, the processor 117 in the mobile communications device 115 maps the information contained in the dosage matrix onto a calendar function provided in the mobile communications device 115. In one example, the processor 117 in the mobile communications device 115 also uses the information contained in the dosage matrix to set an alarm function so that either the loudspeaker 118 is activated or the display 116 illuminates (for example) when it is time for medication to be taken. From additional information provided by the pharmacy 106 concerning the date of availability of the medication, and knowing the total quantity supplied, the processor 117 in the mobile communications device 115 can also estimate a start date (for commencement of taking the medication in accordance with the prescribed dosage) and thereby monitor usage of the medication. In one example, when the quantity of the medication is running low, the processor 117 can activate either an audible or visual alarm on the mobile communications device 115 and thereby facilitate a reordering process.

At 209, useful and relevant information is displayed on the screen 116. An example of such a display of information is shown in figure 1. A calendar is displayed with the current day highlighted and some displayed text informs the user which medication to take and at which time of day. For example “8 am take 1x Venlafaxine capsule”. In another example, the strength may also be displayed; for example “8 am take 1x Venlafaxine 75mg capsule”. An indication of the amount of medication remaining (as a percentage for example) can also be displayed. Default settings may be used for the times of day when the medication is to be taken. For example, if the dose specifies three times a day, the default setting could be set at 8am, 1 pm and 6pm.

If a dose is missed then at 210 a “patient input” step is provided so that this information can be entered into the mobile communications device 115 and captured by the processor 117 which in response, at 211, updates the value of the amount remaining and displays the corrected value on the display 116.

Advantageously, by virtue of the dosage matrix, the patient can be prompted to take medication at the correct time even in cases where the dosage instruction is complicated such as in the example given above where tablets are taken every four days rather than daily.

When the supply of medication has been exhausted, the patient may wish to request a repeat prescription. A further embodiment of the invention provides a means for a patient to send a request from a mobile communication device to a GP surgery. Some names of drugs are complicated and difficult to spell and some patients may have difficulty in typing the name of the drug into their mobile communication device prior to sending off a request. To avoid such problems, the mobile communication device 115 of figure 1 is provided with an image capture or scanning facility and the processor 117 is provided with optical character recognition functionality.

Referring now to figure 7 when the patient wishes to request a repeat prescription using the mobile communication device 115, the patient commences the process of entering a request, at step 701, by activating a button (not shown) on the touchscreen 116. In response, at 702, the processor 117 configures the touchscreen in the particular manner illustrated in figure 8. Referring briefly to figure 8, the touchscreen highlights a scan area 801 which includes a selection window 802, in the centre of which is a cross hair 803. The patient places the box which contains the drug (or a prescription receipt or a drug label for example) in contact with the touchscreen 116 such that the cross hair is centred on the drug name as is printed on the box (or receipt or label). Referring back to figure 7, at step 703 an image is captured and an OCR operation is performed on the captured image. Figure 9 illustrates an example of a captured image where the name of the drug “Lansoprazole” is centred underneath the cross hair. On the same row as this word and to the right is the strength of the drug “15 mg.” The second and third rows which are below the row containing the drug name describe the form of the drug “gastro-resistant capsules.” Other text or data (such as a bar code and/or the name of the drug manufacturer, e.g. “Mylan” as illustrated in figure 9) may also be captured by the image capture process but this extraneous material can be ignored by the OCR operation.

Although in the aforementioned embodiment a cross hair is exemplified, it will be appreciated that a cross hair need not be provided. It will also be appreciated that although a cross hair has been detailed, alternative targeting means may be provided.

In one exemplary method, no cross hair is displayed but its virtual position is interpreted to be that underneath where the user taps the touchscreen. In this example, an image of the drug label is captured and displayed to the user on the touchscreen. The user then taps the central region of the word “Lanzoprasole” and the process continues from step 703. It will be appreciated that in some embodiments both a cross hair (and/or other suitable targeting means) and a tap feature can be provided. In this exemplary embodiment, the tap feature may be used as an additional verification step.

At 704 the relevant text which describes the drug name, strength and form is extracted in a manner to be described below with reference to figure 10. This text extraction may be performed by the signal processor 117 in the mobile communication device 115 or alternatively, by the signal processor 102 in the server 101 or by the processor circuit 109 in the pharmacy 106. If the text extraction is to be performed in the server or pharmacy, then the mobile communication device transmits the result of the OCR operation to either the server or pharmacy for subsequent processing and the server (or pharmacy as the case may be) transmits the checked result back to the mobile communication device.

At 705, the extracted text is checked (and/or verified and/or identified) by searching a drug database. The drug database may be accessed from a remote source, over the Internet for example, or may be kept in the library 110 of the pharmacy 106 or the store 103 of the server 101. Alternatively a drug database may be stored in the mobile communication device 115. At 706, the verified extracted text which describes the drug, its strength and form (in this example “Lansoprazole 15mg gastro-resistant capsules” is presented to the patient on the touchscreen 116. The patient can then incorporate this text in a message and send it wirelessly from the mobile communication device 115 to the GP surgery at 707. This message may be sent directly or via the pharmacy and server to the GP surgery or via the server to the GP surgery. A method for extracting relevant text from the result of the OCR operation will now be described with reference to figure 10. The word between blank spaces beneath the cross hair (see figure 9) and/or the region where the user taps the screen is assumed to be the name of the drug. The remaining captured text is processed in order to find a drug strength (an amount in mg for example) and a drug form (tablets or capsules for example). At 1001, the OCR result is received. In the example illustrated in figure 9 the OCR result comprises three rows of text. The first row comprises the drug name, to the left of which is a space and then the number 15. To the right of the drug name is a space then the number 15 then another space and then the letters mg. On the second row from left to right, are the letters mg followed by a space followed by the words “gastro-resistant.” On the third row is the word “capsules.”

At 1002, the centred word (that is; the word whose approximate centre lies beneath the cross hair 803 and/or where the user tapped the screen and which, in fact, is the name of the drug) is found. This is done by first examining the character directly underneath the cross hair and then moving one character width at a time to the left and to then to the right until a space is reached on both sides.

At 1003, a strength descriptor is searched for. This process may be assisted by use of a library of known strength descriptors. Starting to the right of the centred drug name, this search involves finding characters that have a space to the left and to the right of them. The search commences with the first row and if that yields no result then the same operation is carried out on the second row and then if necessary, on the third row as well. In this example, the descriptor “mg” is found to the right of the first row.

At 1004, the number which qualifies the strength descriptor is searched for. Starting at the strength descriptor, and moving to the left, numbers are searched for until a space is found. In this example, the numbers 1 and 5 are found to the left of the descriptor. At 1005, the descriptor and numbers are concatenated to give the drug strength 15 mg.

At 1006 a form descriptor is searched for. This process may be assisted by use of a library of known form descriptors. This is similar to the process used for finding the drug name in step 1002. The search starts on the first row to the right the centred drug name. It a search on the first row yields no result then the second row is searched. Similarly, if the search on the second row yields no result, then the third row is searched. The search entails finding a string of characters that has a space to the right and to the left.

At 1007, the search results can be concatenated to yield a set of specific search terms of the medication with single space separation; “Lansoprazole 15mg gastro-resistant capsules.” As mentioned above with reference to figure 7, the search results can be checked/verified/identified using a drug database. Firstly, the full concatenated description is searched in the database. If a matching result is found then nothing further needs to be done. On the other hand, if no match is found, then the form of the drug is removed from the search term and the description “Lansoprazole 15mg” is searched in the database for a match. If all forms of “Lansoprazole 15mg” are found to be listed in the database then the search is considered to have been successful. However, if no match was found then the strength descriptor is removed from the search term and the description containing the drug name and form “Lansoprazole gastro-resistant capsules” is searched in the database. If all strengths of Lansoprazole gastro-resistant capsules are listed then the search is considered to have been successful. If a match is not found however, then form and strength are removed from the search term and just the drug name Lansoprazole is searched in the database. If all strengths and forms of Lansoprazole are listed in the database then the search is considered to have been successful. If, however, no match is found, then an error message can be generated and presented to the patient on the touchscreen 116 of the mobile communication device 115.

The signal processing functionality of the embodiments of the invention, particularly the processor, processor circuit 109 and signal processor 102, may be achieved using computing systems or architectures known to those who are skilled in the relevant art. Computing systems such as, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, tablet etc.), mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment can be used. The computing system can include one or more processors which can be implemented using a general or special-purpose processing engine such as, for example, a microprocessor, microcontroller or other control module. At least some of the signal processing functionalities of the processor 117 may be downloaded as an application (or “app”) into a mobile communication device. At least some of the signal processing functionalities of the processor circuit 109 and the signal processor 102 may be similarly downloaded into a terminal accessible by a pharmacy and into a server, respectively.

The computing system can also include a main memory, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by a processor. Such a main memory also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor. The computing system may likewise include a read only memory (ROM) or other static storage device for storing static information and instructions for a processor.

The computing system may also include an information storage system which may include, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW), or other removable or fixed media drive. Storage media may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive. The storage media may include a computer-readable storage medium having particular computer software or data stored therein.

In alternative embodiments, an information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. Such components may include, for example, a removable storage unit and an interface, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to computing system.

The computing system can also include a communications interface. Such a communications interface can be used to allow software and data to be transferred between a computing system and external devices. Examples of communications interfaces can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a universal serial bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via a communications interface are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by a communications interface medium.

In this document, the terms ‘computer program product’, ‘computer-readable medium’ and the like may be used generally to refer to tangible media such as, for example, a memory, storage device, or storage unit. These and other forms of computer-readable media may store one or more instructions for use by the processor comprising the computer system to cause the processor to perform specified operations. Such instructions, generally referred to as ‘computer program code’ (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system to perform functions of embodiments of the present invention. Note that the code may directly cause a processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.

In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system using, for example, removable storage drive. A control module (in this example, software instructions or executable computer program code), when executed by the processor in the computer system, causes a processor to perform the functions of the invention as described herein.

Furthermore, the inventive concept can be applied to any circuit for performing signal processing functionality within a communications terminal or device. It is further envisaged that, for example, a semiconductor manufacturer may employ the inventive concept in a design of a stand-alone device, such as a microcontroller of a digital signal processor (DSP), or application-specific integrated circuit (ASIC) and/or any other sub-system element.

It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to a single processing logic. However, the inventive concept may equally be implemented by way of a plurality of different functional units and processors to provide the signal processing functionality. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organisation.

Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors or configurable module components such as FPGA devices. Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term ‘comprising’ does not exclude the presence of other elements or steps.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.

Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to ‘a’, ‘an’, ‘first’, ‘second’, etc. do not preclude a plurality.

Claims (25)

Claims

1. A computer-implemented method comprising: receiving a description of a drug to be prescribed wherein said description includes a text string relating to dosage; extracting from said text string a dose quantity and a dose frequency; from said extracted dose quantity and dose frequency, configuring a dosage matrix of instances per day against number of days comprising a dosage cycle; and mapping the dosage matrix onto a calendar for recording when the drug should be taken.

2. The method of claim 1 wherein dose quantity and dose frequency are determined by performing a sentence syntax analysis on the text string.

3. The method of claim 1 or claim 2 wherein the text string has the form “take x capsule(s)/tablet(s) y times every z day” where x, y and z are integers.

4. The method of any preceding claim wherein the prescription includes information relating to the total quantity of medication provided and the method comprises monitoring consumption of the medication.

5. The method of claim 4 comprising estimating a start date for taking the medication.

6. The method of claim 5 comprising presenting an indication of consumption of the medication to a patient taking the medication as an indication of the amount of medication remaining.

7. The method of claim 6 comprising activating an audible or visual alarm when the remaining supply of medication is running low.

8. The method of claim 6 comprising adjusting the indication of the amount of medication remaining if one or more doses are missed.

9. The method of any preceding claim comprising activating an audible or visual alarm in order to alert the patient when it is time for the medication to be taken.

10. The method of any preceding claim comprising displaying the name of the medication to be taken.

11. The method of any preceding claim comprising providing the dosage matrix to a mobile communication device which includes a calendar function and a display.

12. The method of any preceding claim comprising; in a mobile communication device having an image capture facility, capturing an image of printed matter which includes a name, strength and form of a medication, wherein the method further comprises extracting text comprising the name, strength and form of the medication from the captured image and displaying the extracted text on a display screen of the mobile communication device.

13. The method of claim 12 wherein extracting text comprises searching for a word by finding spaces to the left and right of identified characters that comprise the word.

14. The method of claim 13 comprising verifying the extracted name, strength and form of the medication using a drug database.

15. A patient medication management system comprising first signal processing circuitry for receiving a description of a drug to be prescribed wherein said description includes a text string relating to dosage; extracting from said text string a dose quantity and a dose frequency; from said extracted dose quantity and dose frequency, configuring a dosage matrix of instances per day against number of days comprising a dosage cycle; the system comprising second signal processing circuitry for receiving the dosage matrix and for mapping the dosage matrix onto a calendar function for recording when the drug should be taken.

16. The system of claim 15 wherein the first signal processing circuitry is configured to determine dose quantity and dose frequency by performing a sentence syntax analysis on the text string.

17. The system of claim 15 or claim 16 wherein the first signal processing circuitry is located in a pharmacy where the prescription is received from a GP surgery.

18. The system of claim 15, 16 or 17 wherein the second signal processing circuitry and calendar function are included a mobile communication device, said device also being provided with a display screen for indicating to a patient when the drug should be taken.

19. The system of claim 18 wherein the mobile communication device includes an capture facility for capturing an image of printed matter which includes a name, strength and form of a medication, and wherein the system further includes processing circuitry for extracting text comprising the name, strength and form of the medication from the captured image for displaying on the display screen of the mobile communication device.

20. The system of claim 19 wherein the processing circuitry is arranged to search for a word in the captured image by finding spaces to the left and right of identified characters that comprise the word.

21. The system of claim 20 wherein the processing circuitry is arranged to verify the extracted name, strength and form of the medication using a drug database.

22. A tangible computer program product having executable program code stored thereon for executing a process to perform a patient medication management method in accordance with any of claims 1 to 14.

23. The tangible computer program product of claim 21 wherein the tangible computer program product comprises at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.

24. A patient medication management method for operating an electronic prescription service substantially as hereinbefore described with reference to the drawings.

25. A patient medication management system for operating an electronic prescription service substantially as hereinbefore described with reference to the drawings