WO2014142667A1

WO2014142667A1 - Method for creating and/or keeping a personal medication file with the aid of a computer system

Info

Publication number: WO2014142667A1
Application number: PCT/NL2014/050156
Authority: WO
Inventors: Cornelis Wilhelmus Henricus Schaap
Original assignee: Consumer Health Entrepreneurs B.V.
Priority date: 2013-03-14
Filing date: 2014-03-14
Publication date: 2014-09-18
Also published as: NL2010501C2; DE202014010548U1

Abstract

A method for creating and/or keeping a personal medication file with the aid of a computer system, comprising: a. utilizing a first database of the computer system in which by a patient information on the use of his personal medication, coupled to information on the identity of the patient, is stored, characterized in that the method furthermore comprises the steps of: xl: recording at least one medicine which is being purchased by a customer at a cash register system, the cash register system provided with information on medicines to be possibly purchased; x2: the cash register system in an automatic manner passing on information on the at least one medicine recorded at the cash register system to the computer system; x3: generating a code which is associated with the information on the recorded at least one medicine; x4: the cash register system providing the generated code to the customer; x5: an entity such as the customer or the patient entering the code received from the cash register system in step x4 in the computer system; x6: the computer system, on the basis of the code entered at the computer system in step x5, providing to an input entity information on the at least one medicine recorded at the cash register system; x7: an input entity, in particular the input entity of step x6, selecting at the computer system an identity of a patient and the at least one medicine if it will be used by the patient, after which the computer system stores the selected information on the medicine, coupled to the identity of the patient, in the first database.

Description

Title: Method for creating and/or keeping a personal medication file with the aid of a computer system

The invention relates to a method for keeping a personal medication file with the aid of a computer system, comprising:

a. utilizing a first database of the computer system, wherein by an input entity such as a patient, physician or care institution information on the use of personal medication of the patient, coupled to information on the identity of the patient, is stored in the first database.

Such a method is known from inter alia Netherlands patent application 2007735.

The invention contemplates facilitating the input of the information on the medication in the first database in some cases.

According to the invention, the method is characterized in that the method furthermore comprises the steps of:

xl: recording at least one medicine which is being purchased by a customer at a cash register system, the cash register system provided with

information on medicines to be possibly purchased;

x2: the cash register system in an automatic manner passing on information on the at least one medicine recorded at the cash register system to the computer system;

x3: generating a code which is associated with the information on the recorded at least one medicine;

x4: the cash register system providing the generated code to the customer; x5: an input entity such as the customer or the patient entering the code received from the cash register system in step x4 in the computer system; x6: the computer system, on the basis of the code entered at the computer system in step x5, providing to an input entity information on the at least one medicine recorded at the cash register system; x7: an input entity, in particular the input entity of step x6, selecting at the computer system at least one identity of a patient and the at least one medicine if it will be used by the at least one patient, whereupon the computer system stores the selected information on the medicine, coupled to the selected at least one identity of the patient, in the first database.

According to the method, the entry of purchased medicines at the first database is thus facilitated, since it is not necessary anymore, when inputting at least one medicine into the database, to enter the name of the medicine itself. Instead, the code received from the cash register system can be entered at the computer system.

This last can be carried out, for instance, as follows. Suppose that the at least one patient has already created an account at the computer system. This means that an identity of the at least one patient has already been included in the first database. If the at least one patient already uses medicines, generally, information on the personal medication, coupled to information on the identity of the at least one patient, will be stored in the first database. The first database can be accessed, preferably via Internet, for instance with a home computer, by an input entity such as the patient or another person, for instance after entering, in addition to the identity of the patient, a password especially coupled thereto.

The method can for instance be carried out as follows. A customer purchases at least one medicine at, e.g., a drugstore (also: chemist's), supermarket, gas station, or other store. The customer can be, for instance, the patient or someone who purchases the at least one medicine for the patient. The customer then takes the at least one medicine to the cash register system where the at least one medicine is recorded. The cash register system is provided with information on medicines to be possibly purchased. The customer pays for the at least one medicine in the usual manner at the cash register system. The cash register system will then in an automatic manner pass on information on the at least one medicine recorded at the cash register system to the computer system. Also, a code is generated which is associated with the information on the recorded at least one medicine. Generating the code may be carried out, for instance, by the computer system in response to receipt of the information on the at least one medicine recorded at the cash register system. The computer system can then send this code to the cash register system. The cash register system can then issue the code concerned to the customer. Issuing the code to the customer may be done, for instance, by printing it on a slip, in particular the receipt. The computer system, therefore, can generate in a step x3.1 a code which is associated with the information on the recorded at least one medicine received in step x2 from the cash register system. A consequence is therefore that after carrying out step x2 and step x3.1 the computer system comprises the code and the associated information on the at least one medicine recorded at the cash register system. In a step x3.2 the generated code is then supplied to the cash register system by the computer system. In the step x4 the code received from the computer system is then provided to the customer by the cash register system. It is also possible, however, that the cash register system generates a code which is associated with the information on the recorded at least one medicine. The cash register system can then supply this code to the computer system. In that case, the computer system has received from the cash register system information on the at least one medicine as well as the associated code. In that case, the cash register system will provide the code generated by the cash register system to the customer, for instance by printing it on a slip, such as the receipt. The result is that the customer comes into possession of the code while the computer system is also provided with the code as well the associated information on the at least one medicine recorded at the cash register. This holds, therefore, for both cases mentioned above.

The customer then proceeds, for instance, to go home. The customer can then give the code to the at least one patient. It is also possible that the customer himself is the patient. Also, the customer can give the code to another input entity provided with the earlier-mentioned password to get to the data of the patient. The input entity, such as, for instance, the customer or the patient, can then, for instance, in the usual manner, for instance via the Internet, make contact with the computer system., for instance with the aid of his home computer. Thereupon, for instance, a web page may be accessed which is arranged for entering the code. The computer system can then, for instance, in response to the entry of the code, display information of the at least one medicine associated with the code on the screen of the home computer. More particularly, multiple medicines are shown which are each associated with the code. If, for instance, the input entity knows that a particular first patient is going to use one of the medicines shown which have been purchased, he can select this medicine in a usual manner, for instance with a mouse click. Also, the input entity can enter the identity of the first patient who belongs to the selected medicine. With this, the identity of the first patient is then selected as well. After this, the selected medicine concerned, coupled to the selected identity of the first patient, will be stored in the first database. If the input entity knows that the same medicine will also be used by another, second patient, he can also enter the identity of this second patient, as discussed for the first patient. After this, the selected medicine concerned, coupled to the selected identity of the second patient, will be stored in the first database. The first and the second patient can be, for instance, a mother and daughter of the same family. If, for instance, the input entity furthermore knows that a particular other, third patient is going to use one or more of the other medicines shown which have been purchased, he can select this medicine or these medicines in a usual manner, for instance with a mouse click. Also, the input entity can enter the identity of this other third patient who belongs to the selected medicine or the selected medicines. With this, also the identity of the other third patient is selected. After this, the respective selected other medicine or the respective selected other medicines, coupled to the selected other identity of the third patient, will be stored in the first database. Also, preferably, the input entity can indicate that a medicine of the list will not be used by any more patients than has already been indicated, so that the medicine concerned disappears from the list.

According to the invention, all this may also be carried out otherwise.

Thus, the input entity may again access the computer system with his home computer via Internet and now select a web page by which access can be obtained to information on the use of medications by patients whose use of medications is already stored in the first database. For this purpose, for instance, the identity of a first patient together with a password is entered. After this, access is then gained to the information on the use of medications by the first patient that is already stored in the first database. After this, for instance, the code may be entered, after which the at least one medicine associated with the code is shown on the screen of the home computer. After this, it can be indicated that the medicine concerned is used, after which the medicine concerned, coupled to the identity of the first patient, is stored in the first database. If multiple medicines are associated with the code entered, these will each be displayed on the screen. After this, it can be indicated which of these medicines will be used. Each of the selected medicines will then, coupled to the identity of the first patient, be stored in the first database.

Thereupon, for instance, the input entity can again access the computer system via the Internet with his home computer and select the web page through which access can be gained to information on the use of medications by patients whose use of medications is already stored in the first database. After this, for instance, the identity of a second patient together with a password is entered. After this, access is then gained to the information already stored in the first database on the use of medications by the second patient. After this, for instance, the same code may be entered that was entered for the first patient, after which the at least one medicine associated with the code is shown on the screen of the home computer. After this, it can be indicated that the medicine concerned is used, after which the medicine concerned, coupled to the identity of the second patient, is stored in the first database. If multiple medicines are associated with the code entered, these will each be displayed on the screen. After this, it can be indicated which of these medicines will be used. Each of the selected medicines will then, coupled to the identity of the second patient, be stored in the first database. In each of the cases, and in general, it holds, therefore, that a medicine can be stored in the first database while coupled to at least one identity of a patient or coupled to multiple (also more than two) identities of patients.

According to the method, therefore, at the computer system an identity of the at least one patient is selected, for instance in that the identity of a patient is entered together with a password, whereupon access is obtained to information of the patient that is stored in the first database. Also, by the input entity, the at least one medicine, if it will be used by the patient, is selected. Stated differently, the input entity of step x7 selecting at the computer system an identity of at least one patient and the at least one medicine if it will be used by the at least one patient, is carried out by the input entity, after which the computer system stores the selected information on the medicine, coupled to the identity of the at least one patient, in the first database. Selecting the identity of a patient, in that example, is coupled to the provision of access to the computer system on the basis of the identity of the patient and the password. Of course, it is also conceivable that the identity of the patient is selected in a different manner, as already indicated above, together with the at least one medicine. Also, it is possible that on a website of the computer system the code is entered as well as the identity of the at least one patient together with the password whereupon the computer system stores the information on the medicine, coupled to the identity of the patient, in the first database. It is also possible that after the provision of access to the computer system with the aid of the identity of the at least one patient and the password, as discussed above, by thereupon entering the code, the computer system stores the selected information on the medicine, coupled to the identity of the at least one patient, in the first database. The assumption then is that as soon as the code is entered, the at least one medicine will actually be used by the at least one patient. Selecting the at least one patient in step x7 has then been carried out by the above-mentioned provision of access to the computer system with the aid of the identity of the at least one patient and the password. Such variants are within the framework of the invention. From the foregoing it also appears that in general it holds that in the step x6, the computer system, on the basis of the code entered at the computer system in step x5 and the information received in step x2 on the at least one medicine recorded at the cash register system, provides to the input entity, in particular the input entity of step x5, information on the at least one medicine recorded at the cash register system.

A great advantage of the invention is that the code may also be coupled to multiple medicines. It is hence possible that the customer purchases multiple medicines at the same time. What holds in step xl then, is that multiple medicines are recorded in the cash register system. What holds for step x2 then, is that the cash register system in an automatic manner passes on information to the computer system on the multiple medicines recorded at the cash register system. The computer system receives this information and can then, for instance, generate a code which is associated with the information on the recorded multiple medicines. This code is then transmitted by the computer system to the cash register system again. The cash register system again provides the code to the customer. The advantage then is that the single code is associated with multiple medicines. When thereupon the input entity, for instance on his home computer, gains access to the computer system as, for instance, according to any one of the ways as discussed above, the input entity can select from the multiple medicines those medicines that he and/or the patient(s) concerned are actually going to use, whereupon the computer system will store these medicines, coupled to the identity of the patient, in the first database.

According to a practical variant, it may be so that the computer system first of all generates and/or shows a list again, stating the multiple medicines which are associated with the code entered. The input entity can then select from this list those medicines that he and/or the patient(s) concerned are going to use. This may involve, for instance, one or more medicines. After selection, that medicine that is selected to be used is stored in the first database, coupled to the identity of the at least one patient. The medicine that is used then, is removed from the list mentioned, for instance when it is indicated that there are no more patients, or no patients, who are going to use the medicine. It is also possible here that when the patient later decides that he is also going to use other medicines that were purchased and are in the list, these medicines from the list are also selected, so as to be stored in the first database, coupled to the identity of the at least one patient or coupled to the identities of multiple patients. Then, too, it holds that as soon as a medicine is selected, the respective medicine is removed from the respective list. After all, the hst is comprised of medicines which have been purchased but are not used yet.

If multiple medicines are purchased, it is also possible that step x3 comprises the following steps. In a step x3.1 a code is generated by the cash register system, which is associated with information on the recorded multiple medicines. In a step x3.2, the generated code is supplied by the cash register system to the computer system, such that the computer system can associate this code with the information on the purchased medicines supplied in step x2. In the step x4 the code generated by the cash register system is then provided to the customer. Once the customer has the code, an input entity who obtains the code from the customer, or who is the customer himself, can then, as discussed above, enter the code into the computer system. The computer system can then provide to the input entity, on the ground of the code entered, information on the multiple medicines recorded at the cash register system. The input entity can then, at the computer system, select from the multiple medicines those medicines, or the single medicine, of which it is known that they are, or it is, going to be used by the at least one patient. The identity of the at least one patient is, for instance, already selected in that the input entity has gained contact with the computer system on the basis of the identity of the patient and the earlier- mentioned password. The computer system can thereupon store the selected information on the medicines, or the single medicine, that will be used, in the first database, coupled to the identity of the patient. As mentioned, selecting the identity of the at least one patient can take place on the basis of the provision of access to the computer system on the basis of the identity of the patient and the matching password (login). Also, it is possible that, for instance on a web page of the computer system, all at once the identity of the at least one patient, possibly the password and the associated code are entered, after which it may have to be indicated which medicines will be used, so that these medicines, coupled to the identity of the patient, are stored in the first database. It is also possible, however, that by entering the code it is directly assumed that the medicines concerned are used, whereupon the medicines concerned are stored in the first database, all coupled to a selected identity of the at least one patient. Such variants are within the framework of the invention.

A particular variant according to the invention is characterized in that the method further comprises:

b. utihzing a second database of the computer system in which standard information of known medications is stored, wherein in step a. the patient utilizes information from the second database for filling the first database.

As the patient, when entering information on the use of his personal medication, also utilizes information that is stored in the second database, it can be accomplished that the information that the user stores in the first database is correct and unambiguous. For the sake of completeness, it is noted that information on use of personal medications also covers

information on the use of personal medications from the past and which medications are presently not used anymore (history).

In particular, it holds here that in step a. information on the use of a medication is stored in the first database by the patient according to standard information from the second database on the medication to be entered. More particularly, it holds here that at input of the information on the use of the medication by the patient, the computer system, on the basis of a keyword entered by the patient at the computer system, generates a list of possible medications and shows it to the patient, whereupon the patient selects from the list a medication that corresponds to the medication that he uses, whereupon the selected information on the medication, coupled to the identity of the patient, is stored in the first database in the form of standard information. In this manner, it is accomplished that correct and

unambiguous information on the use of medications is entered by the patient.

In particular, it holds here that the patient, of a medication used, also enters information on the frequency of taking a medicine according to the medication, the form of administration of the medicine, the strength of the medicine, the use of the medicine (for example, the period of taking the medicine), the origin of the medicine (supplier), the brand of the medicine, information on a storage life of the medicine, and/or an identity of a person such as a physician or pharmacist, care institution, pharmacy and/or hospital that has prescribed the medication. 'Medication' is here understood to mean a prescribed medicine together with a desired manner of

administration of the medicine such as a frequency of taking it, a manner of taking it, a period of taking it, etc.

According to a highly advanced embodiment of the method, it holds that the computer system generates an alert for the patient when after the entering of new information on a medication used in step a. it appears from the first database that the new information does not go together with information from the first database on the use of a medication that the patient already uses.

In the foregoing the assumption has been that the patient already has access to his information in the first database. The initiative towards storing information of the patient in the first database and providing the patient access to the first database may lie, for example, with a first entity. Preferably, it holds then that the first database in a step c. is initially filled with information of the patient by a first entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution, after which the first entity provides the patient access to his information in the first database. Also, it is possible that the patient first shows the initiative to store information about the patient in the first database. In that case, the first database in an initial step c. is first filled by the patient. The initial filling of the database by the first entity and/or the patient with information of the patient may also comprise only the filling of the database with information on the identity of the patient. Information on the use of medicines and/or other information on the patient can then be entered subsequently, coupled to the identity of the patient, at the first database by the first entity and/or the patient. Access provision by the first entity to the patient can be done when the patient has indicated that he is interested in this. If the patient is not interested, the first entity can use the first database himself and no access to the first database is provided to the patient. In particular, the first database in a step d. is filled by the first entity with information on the identity of the patient. Next, in a step e., by the first entity and/or by the patient, information on the use of the personal medication, coupled to information on the identity of the patient, can be stored in the first database. Also, in the step e., other information on the patient may be stored which is coupled to the identity of the patient. This other information can comprise, for example, results of tests that have been performed on the patient, for example by the first entity, such as X-rays, MRI scans, CT scans and lab results. If the first entity has provided the patient access to the first database, from that moment the patient can inspect his information in the first database. When the patient himself has no access to the first database, the patient can inspect the first database when he is present at the first entity. Then the first entity can inspect the database together with the patient, and in consultation with the patient supplement and/or modify the information of the patient in the first database. When, for example, the patient indicates he is using or no longer using certain medicines, the first database can be modified accordingly.

In particular, in step e. the first entity utilizes the standard information from the second database for filling the first database.

Preferably, here, in step e. information on the use of a medication is stored in the first database by the patient according to standard information from the second database on the medication to be entered.

The patient may, if desired, decide to provide access to his

information in the first database to a second entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution. Here, preferably, the second identity is granted access not to the complete first database but only to that part of the first database that contains information on the patient concerned. In particular, after providing the second entity access to the first database, information on the patient from the first database may be sent by e-mail or similar message to the second entity and/or the second entity is granted an opportunity to obtain or consult information of the patient from the first database, for example, by downloading, printing, or reading from a display. Preferably, the second entity is provided access to information of the patient that is stored in the first database only when the patient has provided access to the second entity, while, in particular, the patient also indicates which information the patient provides the second entity access to. The patient can provide the second entity access, for example, for an indefinite period of time, provide access for a definite period of time, or provide once-only access to

information of the patient stored in the first database. In exceptional circumstances, the second entity may obtain access to information of the patient in the first database anyway, even if the second entity has not obtained permission from the patient for this. Such a special circumstance may occur, for example, when the patient is in danger of hfe and is incapable of providing access to the second entity. In that case, however, it is preferred that the fact that the second entity has consulted information on the patient in the first database be stored in, for example, the first database, so that it can be verified later that the second entity has not taken advantage of the access obtained. Also, the patient may withdraw the access he has provided to the second entity. Thus the patient is and remains the lord and master of the information stored about him in the first database.

Preferably, it holds that the second database is filled with information on medicines according to the G-standard. The patient in step a. then uses this standardized information for filling the first database with information on his use of medicines (medications).

An object of the system and the method according to the invention is therefore to accomplish that every care provider (one of the entities mentioned) from the patient's network has the same information available 24/7/365; only with permission of the patient, of course. That permission can mean authorization at different levels and can be changed by the patient continuously. All is logged with inspection for the patient. For the patient the advantages are that as few misunderstandings as possible will arise about the treatment, as well as the possibilities of reviewing his own use, of targeted search for information, and of targeted communication about this (e.g., with a preferred care provider).

In a particular embodiment of the system and the method according to the invention, this can proceed as follows:

In the personal medication file of patient A an appointment is planned with care institution B (one of the entities mentioned). That appointment comes about in that the medication file of patient A, that is, the particular embodiment of the system according to the invention that comprises the first database, upon instruction from patient A, has asked the planning system of care institution B or someone from care institution B (from the list of care institutions patient A is dealing with) for an

appointment. To this end, accordingly, the system according to the invention is communicatively connected with the planning system of the care institution B. The planning system of the care institution or someone from the care institution himself sends a date/time back to the personal medication file of patient A. Upon receipt by patient A, via the system according to the invention, of the date/time proposal of care institution B, patient A accepts the appointment, via the system according to the invention, at the planning system of the care institution B or at someone of care institution B, and the appointment is in the personal medication file of patient A. If patient A accepts this at his personal medication file, his personal medication file sends the planned appointment, in confirmation, back to care institution B and in particular on to Google Calendar or

Outlook of patient A. However, the appointment may also come about at the request of care institution B in that care institution B has asked the personal medication file of patient A if patient A will come and visit the care institution. Patient A then starts the cycle as above. In particular, for the appointment (set/default) the personal medication file of patient A automatically sends a request for information to the system of care institution B. Along with that request, a once-only permission may be sent for care institution B to retrieve at other care institutions (other entities) information on patient A via the "National

Switch Point". Depending on the permission, the system of care institution B can send the available, or collected, information to the personal

medication file of patient A. The personal medication file receives the information and, preferably, automatically matches that received

information with the information from the "current" overview of patient A in the first database. Any discrepancies result in a question to patient A which is generated by the system comprising the first database and is stored in the personal medication file of patient A. Patient A solves that question or not. If "not", the question ends up in the overview of points-to-discuss of patient A in his personal medication file. During the visit to care institution B, patient A can go through these points with the care provider B. For example, furthermore, the then-existing overview is approved by patient A and, as a definitive overview for once-only use by care institution B, is sent to the system of care institution B as well as added to the personal medication file of patient A. The visit / the treatment can begin.

In particular, care institution B, after the treatment or at the end of the visit, creates an electronic prescription with treatment plan for patient A and sends that prescription and treatment plan via the system according to the invention to the personal medication file of patient A. In particular, after that, patient A can select a pharmacy C to which the prescription is sent (patient A cannot modify the prescription). With the prescription, preferably, a current medication overview comes along, and possibly a once- only permission to retrieve information at other care providers (entities). The prescription, after being sent to pharmacy C, is added in the personal medication file of patient A to the list of "proposed medicines of patient A" and the prescription itself is deleted from the personal medication file of patient A after transmission to pharmacy C. Pharmacy C dehvers/sends the medicines to patient A and preferably a message of delivery to the personal medication file of patient A. Patient A, after receipt of the medicines, starts the use thereof physically and fills in the actual use in his personal medication file, with the status of the medicine changing to "current" with an actual use.

On the retrieval of other information at other care institutions as discussed above, the following may be noted. In principle, pharmacy C cannot find any differences if care institution B has already done a search also. However, supposing that patient A in the meantime has started using drugstore medicines or Internet medicines, a discrepancy can occur between what patient A and care institution B have approved and pharmacy C finds. That is why, preferably, pharmacy C sends an overview of the medicines used to the personal medication file of patient A. The system according to the invention then preferably compares this received information with the current information such as it is stored in the personal medication file of patient A and, in case of variance, generates a question at patient A, and/or the care institution B and/or the pharmacy C.

The invention further relates to a registration system comprising a computer system for creating and/or keeping a personal medication file provided with a first database, the computer system being so arranged that the following step can be carried out:

a by an input entity such as a patient, another person and/or

institution, information on the use of personal medication of the patient, coupled to information on the identity of the patient, is stored in the first database, characterized in that the registration system is furthermore provided with a cash register system, wherein the registration system is arranged to connect the cash register system communicatively with the computer system, wherein the registration system is arranged to enable, in use, carrying out with the aid of the registration system the method steps of: xl: recording at least one medicine which is being purchased by a customer at the cash register system, the cash register system provided with information on medicines to be possibly purchased;

x3: the registration system generating a code which is associated by the registration system with the information on the recorded at least one medicine;

x4: the cash register system providing the generated code to the customer; x5: an input entity such as the customer or the patient entering the code received from the cash register system in step x4 in the computer system; x6: the computer system, on the basis of the code entered at the computer system in step x5, providing to an input entity, in particular the input entity of step x5, information on the at least one medicine recorded at the cash register system;

x7: an input entity, in particular the input entity of step x6, selecting at the computer system at least one identity of a patient and the at least one medicine if it will be used by the at least one patient, whereupon the computer system stores the selected information on the medicine, coupled to the selected identity of the at least one patient, in the first database.

Further, the following applies: Wherever it says "patient A" herein, anyone authorized and having the proper level of authorization may undertake the actions of patient A.

Around the above, all kinds of services can be developed in the field of communication between patient A and/or care institution B and/or pharmacy C and/or other entities such as reminder services, skype contacts, and the like. The invention will presently be elucidated in more detail with reference to the drawings.

In the drawings:

Figure 1 shows a computer system according to the invention for carrying out a method according to the invention;

Figure 2 shows a first fill -in screen for carrying out a step a. of a possible method according to the invention;

Figure 3 shows a second fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 4 shows a third fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 5 shows a fourth fill-in screen for carrying out a step a. of a possible method according to the invention;

Figure 6 shows a fifth fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 7 shows a sixth fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 8 shows a screen with information on the use of a particular medication entered by a patient;

Figure 9 shows a seventh fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 10 shows an eighth fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 11 shows a ninth fill-in screen for carrying out a step a. of a possible method according to the invention;

Figure 12 shows a tenth fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 13 shows an eleventh fill-in screen for carrying out step a. of a possible embodiment of the method; Figure 14 shows a twelfth fill-in screen for carrying out step a. of a possible method according to the invention;

Figure 15 shows a thirteenth fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 16 shows a fourteenth fill-in screen for carrying out step a. of a possible embodiment of the method;

Figure 17 shows an upgraded screen overview, also fill-in screen for new medication;

Figure 18 shows a fill-in screen for printing information;

Figure 19 shows a fill-in screen for printing information;

Figure 20 shows a possible printout by a patient on the use of his medications;

Figure 21 shows a fill-in screen for printing information;

Figure 22 shows a possible letter to a general practitioner (GP) generated with the computer system, based on information from the first database;

Figure 23 shows a fill-in screen for printing information;

Figure 24 shows a possible letter to a pharmacist based on

information from the first database;

Figures 25, 26A, 26B, 27A, 27B, 27C, 28-37, 38A, 38B, 39-43 show fill-in and information- vie wing screens of a particular embodiment of the invention;

Figure 44 shows a receipt with a code thereon;

Figure 45 shows a fill-in screen;

Figure 46 shows a fill-in screen;

Figure 47 shows a fill-in screen; and

Figure 48 shows a fill-in screen.

In Figure 1, with reference numeral 1 a computer system according to the invention for carrying out a method according to the invention is designated. The computer system in this example is provided with a computer 2 of a patient, which is set up, for example, at home. Further, the computer system is provided with a first server 4 and a second server 6. The computer 2 and the first server 4 in this example are connected with each other via Internet 8. Likewise, in this example, the first server 4 and the second server 6 are connected with each other via Internet 8.

On the first server 4 in this example a first database is stored in which a patient has stored information on the use of his personal medication coupled to information on the identity of the patient. This first database is designated with reference numeral 10. Further, in the second server 6 a second database 12 is stored in which standard information of known medications is stored. In this example, the second database is filled with information on medications according to the G-standard.

Via his computer 2 a patient can store information on the use of his personal medication coupled to information on his identity. The first database thus comprises a personal medication file for the patient concerned. All this will be explained on the basis of an example in which the patient 14 wishes to store information on medication that he is using in his personal medication file. This proceeds as follows. First of all, the patient 14 accesses the database 10 with the aid of his computer 2. He can do this, for example, by entering his first name and last name. The server 4 will then ask the user 14, for example, for a password. The user 14 then sees the question: "enter your password" displayed on his computer 2. Then the patient 14 enters the password via the computer 2, which password is supplied via the Internet connection 8 to the first server 4. The first server 4 checks on the basis of information in the database 10 whether the password is correct. When the password is correct, the patient gains access to his personal medication file which is stored in the first database 10. The patient then gets to see, for example, a screen with personal information such as name and address. If a patient wishes to enter a new medication, he can click the tab "medication" on his screen, whereupon a screen according to Figure 2 is shown to him. The screen shows information on medications previously entered by the patient. The patient then energizes a button "add medication" with, for example, his mouse. Thereupon, he gets to see the screen as shown in Figure 3. In the screen, at "reference of the medication" the patient can enter a keyword of the medication concerned. In this example, he enters Ibuprofen as keyword. Then he clicks on the button "search for medication". After this, the picture according to Figure 4 appears on his screen, which in this example is generated by the first server on the basis of information from the second database 12. So this involves

standardized information. To this end, the first server has submitted

Ibuprofen as search query, via the Internet, to the second server. The second server 6 looks for hits relating to Ibuprofen in the second database 12. The information on these hits is sent by the second server to the first server. On the basis of this information the first server creates the screen according to Figure 4 which is displayed on the computer 2 of the patient. Here, the patient sees that there may be two types of Ibuprofen, viz., Dexibuprofen and Ibuprofen. It is also indicated here that Ibuprofen is also known by the name of Antigrippine Ibuprofen. In this example, the user selects with his mouse the button "choose" associated with Ibuprofen. Based on the information from the second database the first server then generates a new fill-in screen according to Figure 5 on the computer 2 of the patient. From this screen it appears that the patient must choose the form in which the medication is administered (such as melting tablet, Capsule, soft, etc.). In this example, the patient chooses Capsule, soft. After this, the fill-in screen according to Figure 6 is generated. Here, the strength of the medication Ibuprofen must be chosen. He can choose between 200 mg and 400 mg. In this example, the patient chooses 200 mg by energizing the respective button associated with 200 mg. Based on the information from the second database, the first server then generates the screen as shown in Figure 7 on the computer 2 of the patient. Now the patient must choose the supplier if he knows it. If he doesn't, he can choose: "I cannot choose". In this example, he chooses the supplier "RECKITT BENCKISER HEALTHCARE B.V." After this, the first server generates the screen according to Figure 8 with information about the chosen medication. The patient can now stop entering if he so wishes. In the first database, information on the use of the medication Ibuprofen, coupled to the identity of the patient 14, is stored. However, the patient can also add information about the use of the medicament in question. To this end, he energizes the text "to indicate" in the screen of Figure 8. Then the screen according to Figure 9 appears, where the patient can enter the starting date and can indicate if this is an estimate or not. He can thereupon confirm the entered information by energizing the button "confirm". Then the screen according to Figure 10 appears where, if this is known, the final date of the period of use can be entered. In this example, as a date, 2010-02-18 is entered. Also, it can again be indicated whether this is an estimate yes or no. After entering this information the button "final date entered" can be energized. If the final date were as yet unknown, the button "no final date yet" could be energized instead. If there is a single medicine use involved, the button "single use on 18-01-2010" can be energized. After energization of one of the three buttons, the server 4 generates the fill-in screen according to Figure 11. Here, the patient can indicate whether the use involved is a medication use exclusively at predetermined times, or a medication use when he needs it but not at predetermined times, or a medication use when he needs it and at predetermined times. In this example, the choice is medication use according to predetermined times. Thereupon the fill-in screen according to Figure 12 appears. Here, the patient must indicate how the medication use repeats itself. He can choose between: "where this medication is concerned, every day is the same", "where this medication is concerned, every week is the same", "my use varies per day and week, but every month looks the same regarding use of the medication" or "the use does not fall into the above categories". In this example, the patient energizes the button associated with "where this medication is concerned, every day is the same". Then the fill-in screen according to Figure 13 appears. Here, it is to be indicated how the medication is used per day. In this example, the patient fills in that he uses two items in the afternoon. After filling in the number 2 he confirms this by energizing the button "confirm". Then the fill-in screen according to Figure 14 appears. Here, the patient can enter the prescriber if applicable. The last option indicates the possibility that the medication has been prescribed by the general practitioner (GP) who is on record in the first database as being associated with the patient concerned. In this example, the patient chooses the last option, i.e., that the medication has been prescribed by Dr Maatbeker of the practice Maakbeter in Rotterdam. In this example, the patient concerned has previously stored in the first database who his general practitioner (family doctor) and pharmacist are. The patient can also choose the option "no, this medication has not been prescribed to me by anyone", "no, this medication has been prescribed to me, but not by anyone from the list below", or "my prescriber is not on the list yet, I wish to add the prescriber to the list". After the patient has chosen the last option, the fill-in screen according to Figure 15 appears. Here, if applicable, the patient can enter the pharmacy where he has obtained the medicament concerned. He can choose between the alternatives: "no, I have not obtained this medication via a pharmacy", "no, I have obtained the medication via a pharmacy, but not via a pharmacy from the list below", "my pharmacy is not on the list yet, I wish to add the pharmacy to the list", or "yes, I have obtained the medication via Pieter de Pil from Rotterdam".

In this example, the patient chooses the last alternative. Then the fill-in screen according to Figure 16 appears, asking for still more

information on the medication use. The patient can choose between "I have indeed a repeat prescription for this medication" or "I have no repeat prescription for this medication". In this case the patient chooses the latter option. After this, the overview according to Figure 17 appears which corresponds to the overview according to Figure 2 except that the use of Ibuprofen has been added.

All information discussed hereinabove and entered along the lines of Figures 3-17 has now been added in the personal medication file of the patient 14. It is noted that the patient, if desired, can also enter yet other information. The screen of Figure 2 could additionally comprise, for example, a button "other information". When this button is energized, for example, a fill-in screen with a free field to be filled in is shown where this other information can be introduced. This can be carried out by the patient by typing in the field. Also, in a known manner, files (word documents, scans, photographs and the like) comprising this other information may be dragged into the free field by the patient so that these files are stored in the first database. This other information is again stored, coupled to the identity of the patient. The other information on the patient can comprise, for example, results of tests which have been performed on the patient, for example by the first entity, such as X-rays, MBI scans, CT scans and lab results.

From Figure 17, it appears furthermore that the patient concerned already uses or has used Dexibuprofen, Dyclophenac and Paracetamol.

Further information (such as use present or past, prescribed by whom, and the like) may be obtained per medication and be shown on the screen of the computer 2 (PC, laptop, iPad, etc.) by clicking on the medication in question. Next, a patient, if he so wishes, can energize the button "add more

medication" when he wishes to add a new use of a medication. An advantage is that in the medication file shown in Figure 6 the information on the use of the medications is correctly and uniformly displayed and stored in the first database by the patient because the information concerned has been generated with the aid of the G-standard. According to the invention, therefore, in a step a. a first database of the computer system is utihzed in which by a patient information about the use of his personal medication, coupled to information on the identity of the patient, is stored. The system utihzes a second database of the computer system in which standard information of known medication is stored, while in step a. the patient utihzes information from the second database for filhng the first database with standard information of a medication.

Also, it has appeared that in the entering of the information on the use of the medication by the patient, the computer system, on the basis of a keyword entered in the computer system by the patient, generates a list of possible medications and shows it to the patient, whereupon the patient chooses from the list a medication that corresponds to the medication that he uses, whereupon the selected information on the medication, coupled to the identity of the patient, is stored in the first database. When entering a medication used by him, the patient can also enter information on the frequency of taking a medicine of the medication, the form of the medicine, the strength of the medicine, the use of the medicine (for example, the period of taking the medicine), the origin of the medicine, the brand of the medicine, information on the storage life of the medicine (for example, not to be used after 1 January 2015), and/or an identity of a person such as a physician or pharmacist, care institution, pharmacy and/or hospital that has prescribed and/or delivered the medication.

The computer system in this example is so arranged as to generate an alert to the patient when after entry of new information on a use of a medication in step a. it appears from the first database that the new information does not go together with the information from the first database on the use of a medication the patient already uses. In effect, this action is carried out by the first server. The first server knows what medications are already used by the patient and consults, for example, the second server to see if the new medication to be entered might present a problem (a problem such as contraindication) with the medications already used by the patient. The information on the incompatibility of the use of different medications can therefore be obtained by the first server, for example, from the second database of the second server.

In the foregoing the assumption has been that the patient already has access to the first database. The initiative for storing information of the patient in the first database and providing the patient access to the first database may lie, for example, with a first entity. What applies then, preferably, is that the first database in a step c. is initially filled with information of the patient by a first entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution, after which the first entity provides the patient access to his information in the first database. The first entity approaches the patient, for example via a letter, mail or personal interview, and asks whether the patient is interested in gaining access to his information in the first database. If the patient indicates he is interested in this, the first entity provides the patient access to his information in the first database (for example, by providing an access code to access the first database via Internet). From that moment onwards, the patient can access the first database to consult it and/or to enter information on his use of medicines, as discussed above.

Providing access can be done when the patient has indicated that he is interested in this, for example, by means of a letter, mail or in a personal interview at the first entity. If the patient is not interested the first entity can himself/itself use the first database and no access is provided to the patient. In particular, after being created, the first database in a step d. is filled by the first entity with information on the identity of the patient. Next, in a step e., information on the use of the personal medication can, coupled to information on the identity of the patient, be stored in the first database by the first entity. It is noted that the first entity, if desired, can also enter yet other information. For this purpose, for example, use can be made of a fill-in screen with a free fill-in field where this other information can be introduced. This can be carried out by the first entity by typing in the field. Also, in a known manner, files (word documents, scans, photographs and the like) comprising this other information may be dragged into the free field by the first entity so that these data files are stored in the first database. This other information is again, coupled to the identity of the patient, stored. The other information on the patient can comprise, for example, results of tests which, for example, have been performed on the patient by the first entity, such as X-rays, MRI scans, CT scans and lab results. If the first entity has provided the patient access to the first database, the patient from that moment onwards can inspect the database. When the patient has no access to the first database, the patient can inspect the first database when he is present at the first entity and the first entity can employ the database exclusively for own use. Also, the first entity can inspect the database possibly in the presence of the patient and in

consultation with the patient supplement and modify it or merely inspect it. When the patient indicates he is using or no longer using certain medicines, the first database may, for example, be modified accordingly.

Preferably, here, in step e., information on the use of a medication is stored in the first database by the patient according to standard information from the second database on the medication to be entered. Preferably, in step e., in the entering of the information on the use of the medication by the first entity, the computer system, on the basis of a keyword entered by the first entity at the computer system, generates a list of possible medications and shows it to the first entity, whereupon the first entity selects from the list a medication that corresponds to the medication the patient uses, whereupon the selected information on the medication, coupled to the identity of the patient, is stored in the form of standard information in the first database. In particular, it holds furthermore that the first entity in step e., of a medication the patient uses or has used, also enters information on the frequency of taking a medicine of the medication, the form of administration of the medicine, the strength of the medicine, the use of the medicine (for example, the period of taking the medicine), the origin of the medicine (supplier), the brand of the medicine, information on a storage life of a medicine, and/or an identity of a person such as a doctor or pharmacist, care institution, pharmacy and/or hospital that has prescribed the medication.

The patient may, if desired, decide to provide access to the first database to a second entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution, while, in particular, the patient also indicates which information the patient is providing the second entity access to. In particular, after providing the second entity access to the first database, information from the first database may be sent by e-mail or similar message to the second entity and/or the second entity is given an opportunity to obtain or consult information from the first database, for example, by downloading, printing or reading from a display.

The patient hence can, if he so wishes, communicate to the first server via his computer 2 that he is providing access to the part of the first database that relates to his person to, for example, a second entity such as a physician and/or a pharmacy and/or a pharmacist and/or hospital and/or care institution. This may be realized in a known manner in that the user protects his information with a password he gives to, for example, the general practitioner beforehand. Via his computer 16 the general

practitioner can then access the first server 4 (for example, via Internet), enter the identity of the patient, as well as the password in question, whereupon the medication file of the patient concerned becomes accessible for the computer 16. The password in question may, for example, afford a physician once-only access to information of the patient, afford access to information of the patient for a definite period of time, or afford access to information of the patient for an indefinite period of time. The patient can also indicate per entity to which information he is providing access. Thus, he can decide to provide a particular second entity mere access to information on medications from a particular period, for example, medications used in the period of 1990-2000. After this, for example, the general practitioner concerned may be granted an opportunity to download the information concerned from the database. It is also possible, however, that the patient arranges for information from the first database relating to his personal medication file to be sent to the computer 16 of, for example, the general practitioner, via an e-mail or an XML message, etc. Also, the second entity may be granted access by the patient to enter information on the patient, and coupled to the patient's identity, in the first database. This information can comprise the same information as can be entered in the first database by the patient and/or the first entity.

Also, it is possible that the patient requests an entity (the first entity, the second entity and/or a third entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution) to check information on medications from the first database that is coupled to the patient's identity. This can be carried out in different manners. For example, the patient can enter the request concerned at the first server. If at the first server in the first database information of, for example, the general practitioner is known, the first server can proceed to forward the request via, for example, the Internet to the computer 16 of the general practitioner. The general practitioner can then, for example, download the information of the patient to check it and, if desired, contact the patient for consultation. Also, the patient can send this request directly to the computer 16 of the general practitioner, together with, for example, a password, so that the general practitioner himself, when it is convenient to him, can access the first server to retrieve the information from the personal medication file of the patient using the password concerned. After this, the general practitioner can assess this information and there can be, for example, consultation by telephone between the general practitioner and the patient.

Other ways of providing access are also conceivable. Suppose a general practitioner wishes to have access via his computer 16 to

information of the patient stored in the first database. If the patient has not provided access to the general practitioner before, the general practitioner will be denied access. The patient can then provide the physician on the spot with a code giving the physician once-only permission to consult data of the patient in the first database. Also, the physician, when the patient is with him, can ask the first database with his computer 16 to send an SMS message with an access code to a mobile telephone of the patient. It holds here that the mobile telephone number of the patient is known at the first database. Upon receipt of the SMS message the patient can let the general practitioner know the access code, after which the general practitioner can feed this access code with his computer 16 to the first database. The first database then provides the computer 16 access when the received code corresponds to the code of the SMS message. Also, via a computer, for example, via the computer 16 of the physician whereat he is present, the patient himself, by entering a password, can gain access to the data stored about him, including account data. Upon access to his patient account, he can enter, for example, that the physician in question gets access to particular data or all data that are stored in the first database about him. Such access may again be once-only, for a definite period of time or an indefinite period of time.

Whatever the manner in which a patient has provided access to a general practitioner, or more generally to a second entity, the patient remains lord and master of the information stored about him in the first database. This appears, in this example, from the following: The second entity is provided access to information of the patient stored in the first database only when the patient has provided access to the second entity. The patient may, for example, provide the second entity permanent access, provide access for a definite period of time, or provide once-only access to information of the patient stored in the first database. In exceptional circumstances the second entity may nonetheless obtain access to

information of the patient in the first database, also when the second entity has not obtained permission from the patient for this. Such a special circumstance may occur, for example, when the patient is in danger of life and is incapable of providing access to the second entity. In that case, however, it is preferred that the fact that the second entity has consulted information on the patient in the first database be stored in, for example, the first database, so that it can be verified later that the second entity has not taken advantage of the access obtained. Also, the patient may retract the access he has provided to the second entity. Thus the patient is and remains lord and master of the information stored about him in the first database.

In this example, the information on the identity of the patient is also stored in the first database. The information on the identity of the patient can comprise, in addition to his name and address, for example, age, sex, blood group or rhesus factor, the name of a general practitioner and/or the name of a pharmacist. All this information is then stored in the first database so as to be associated with the information on the use of

medications of the patient concerned.

The patient can also, as desired, for a general practitioner or for a pharmacist, print out a standard letter based on information from the first database about the use of medication and about the use of medication in the past. For this purpose, he energizes the tab "print", whereupon the screen according to Figure 18 is generated on the computer 2 by the first server. This screen shows that the patient can choose between printing information for himself, for a general practitioner, or for a pharmacist. When the patient energizes the button relating to "for myself, a fill-in screen according to Figure 19 is shown. Here, the patient can choose what he wishes to print: "list of current medication", "list of medication you don't use anymore", "list of pharmacies you go to", and "list of general practitioners you go to". Also, a tick may be provided to indicate that all is to be printed. In this example, the choice is for all to be printed out. Then the button "make the printout" is energized. Thereupon a printout is made according to Figure 20. What holds more generally, therefore, is that the patient obtains, can obtain or consults information from the first database, for example, by downloading, printing or reading from a display. This information then relates to information of the patient, not to information of other patients in the first database.

When in the fill-in screen according to Figure 18 it is chosen that information be printed for a general practitioner, the fill-in screen according to Figure 21 appears. Here, too, a choice is offered between options of what is going to be printed, such as: "your name information", "list of current medication", "list of medication you are no longer using", "list of pharmacies that you go to", "list of general practitioners that you go to". Also, it is possible to tick off a command to print all. Also, in addition, the salutation of the letter may be chosen, as in this case "Dear doctor". After this, the choices made can be confirmed by pressing the button "make the printout". Then a letter according to Figure 22 is printed on a printer which is connected to the computer 2. In this letter, it is clear that the only

medicament that is still used is Ibuprofen; the other medications are medications from the past. Also, it is indicated who the general practitioner is and which is the pharmacy. When, by contrast, it is chosen in Figure 18 that a letter for a pharmacy be printed, the screen according to Figure 23 appears. Here are the same printing options as discussed in relation to the general practitioner. In this example, it is again chosen to print all. When thereupon the button "make the printout" is energized, a letter according to Figure 24 addressed to the pharmacist is printed. Such variants are each understood to fall within the invention. In the foregoing it has already been indicated how the first entity may first store data of the patient in the first database, how access to the first database may be provided by the first entity to the patient for accessing data of the patient that are stored in the first database, how the patient can then enter in the computer system to what extent (definite period, indefinite period or once-only) the first entity retains access to data of the patient that are stored in the first database and, possibly, how the patient, if desired, can provide the second entity access to the data of the patient that are stored in the first database, in which case, possibly, the patient can proceed to enter in the computer system to what extent (definite period, indefinite period or once-only) the second entity has access to data of the patient that are stored in the first database.

Of course, also the patient himself can in a step c. initially fill the first database with information of the patient. In that case the patient can go, for example via the Internet, to a web page of the first database. The patient can indicate there that he wishes to store his information in the first database. This can mean, for example, that the patient in a step d. fills the first database with information on the identity of the patient. Also, the patient may then, in a step e., store information on the use of his personal medication, coupled to the information on his identity, in the first database. The patient can then also enter a password, with which the data are protected. When filling the first database, the patient again utilizes the standard information from the second database as discussed hereinabove. After the patient has logged out, he can return via the Internet to the website in question again. When he wishes to access his data, he will then first need to enter the password he himself has specified.

In particular, it also holds that in step e. information about the use of the medication is stored in the first database by the patient according to standard information from the second database on the medication to be entered.

How all of this works will be shown hereinafter.

In Figure 25 the start screen is shown that a patient sees when on his computer 2 he goes to the website named "meddossier.nl", which website can provide access to the first database. The patient here has the option of energizing the button "Log In" if the patient has earlier obtained access to his data stored in the first database. After the button "Log In" has been energized, a screen appears (see Figure 26A) in which the patient must fill in, for example, his name and address details and/or a user name as well as a password (in the password field). After logging in, the screen according to Figure 27A appears. From this screen, the patient can gain access to his data stored in the first database, as has been discussed with reference to Figures 2-24. If, for example, in the screen of Figure 27A the button

'medication' is energized, the screen of Figure 2 appears.

In the screen of Figure 25, the patient can also energize the button "fill in this code" if the patient wishes to gain access to his data first entered by a first entity such as a physician. 'Button' is here understood to cover a hyperlink in a text passage which, for example, is of a color different from the rest of the text (see, for example, "fill in this code" in Figure 25). In that case, the first entity has created an account for the patient in the first database. After this, the patient has obtained an access code from the first entity in order for himself to obtain access to his data in the first database. This will be discussed hereinafter with reference to Figures 41-43.

Since in this case, however, the patient 14 himself wishes to register for the first time at the first database (wishes to create an account himself), the patient energizes the button "Register" in the screen of Figure 25 and thus ends up in the screen in which he can fill in his name and address details and/or a user name (see Figure 26B). Also, in this screen the patient is asked to type a password (in the password field). In this example, the password has to be typed twice. After the password has been typed, the patient energizes the password by pressing the button "Register". After this, the patient can navigate via the screen of Figure 25 to the screen of Figure 26A to log in on his just-created account. After login, the screen according to Figure 27A appears, as discussed above. Then, the patient can add medications in the system or review them by energizing the button

"medication" in the screen of Figure 27A, whereupon a screen is shown to him such as shown in Figure 2. Adding medication then proceeds entirely analogously to the procedure discussed above with reference to Figures 2-17. Also, the patient can then perform the operations described hereinabove with reference to Figures 18-24.

Also, the patient can manage authorizations by energizing the button "authorizations" in the screen of Figure 27A, whereupon the screen according to Figure 28 appears, as will be further discussed hereinafter.

When the patient visits the website a next time, he can energize the button "Log in" in the screen according to Figure 25, whereupon, in the screen of Figure 26A, he can enter his name and address details and/or user name and password to gain access, via the screen of Figure 27A, to his data in the first database. After the patient has entered his name and address details and password (in the field password of the screen of Figure 26A) in the system, the patient can add medications in the system by energizing the button "medication" in the screen of Figure 27A, whereupon he is shown a screen as shown in Figure 2. Adding medication then proceeds entirely analogously to the procedure as discussed with reference to Figures 2-17. Also, the patient can then perform the operations described hereinabove with reference to Figures 18-24.

Once a patient has stored his data in the first database, he can also issue authorizations to third parties for them to consult his data. For this purpose, the patient energizes the button "authorizations" in the screen of Figure 27A. The patient is then presented a screen as shown in Figure 28. In the screen of Figure 28 a list of authorizations is given. In this case, the screen is empty, which means that no authorizations have been issued yet. The patient can now add authorizations by energizing "add authorizations", for example, with the mouse. After energization of "add authorizations", the screen of Figure 29 appears. This screen shows that the patient can choose between "authorize someone else" or entering an authorization (you) "have obtained from someone else". In this case the patient energizes "authorize someone else", whereupon the screen of Figure 30 appears. In the screen of Figure 30 it is indicated by default setting that the authorization starts and ends on the current date, viz. 22 April 2011. The patient, however, changes the default values such that the authorization expires on 30 April 2011. It was also indicated by default setting that the authorized entity is

authorized to read-only and not to make any changes. The patient changes this to "reading and making changes are allowed". All this is shown in Figure 31. After the patient has made the changes concerned, he energizes the button "create authorization code". Then the screen according to Figure 32 appears. The computer system is arranged so as to generate an

authorization code, which is designated in Figure 32 as

"1674.2533.1807.7562.5376". The intention is for the patient to give this authorization code to, for example, a second entity such as a pharmacy he wishes to authorize to gain access to his data. When the patient thereupon energizes the button "overview of authorizations", the computer system generates the screen according to Figure 33 (corresponds to the screen of Figure 28, though with an updated content). Here it is indicated what authorization code has been issued, when it was issued, and until when it is valid. Also, it is indicated that the code entitles to reading and editing. Also, it appears that the authorization code concerned has not been used yet by the second entity. Further, it is possible that the patient, by pressing the button "remove", withdraws the authorization code again. Also, if he so desires, the patient, by pressing the button "add more authorizations", can furnish an authorization to other entities, whereupon once again Figures 30-33 are traversed as described hereinabove.

When the second entity has received the authorization code from the patient, the second entity, just like the patient, can access the first database via Internet by going to the web page ofmeddossier.nl". The second entity can access the first database via an own computer, which is not indicated in Figure 1 for simplicity, but whose situation is similar to that of the computer 2 and the computer 16. The second entity can only obtain access to the first database when the second entity himself has already stored at least his name and address details in the first database. For this purpose, the second entity, just like the patient did at some point, has created his own account and created and then entered a password. The second entity accordingly opens his data by energizing in the screen as shown in Figure 25 the button "Log in", whereupon, in the screen of Figure 26A, he can enter his name and address details and/or user name and his password. After this has been done, the screen according to Figure 27C appears. In this screen the second entity can press the button "authorizations", whereupon he is presented with the screen according to Figure 34 (corresponds to the screen according to Figures 28 and 33, but now for the second entity)- After this, the second entity can press "add authorizations", whereupon the screen of Figure 35 is shown to the second entity. In the screen according to Figure 35 the second entity can energize the button "have obtained from someone else". Then the screen according to Figure 36 appears on his computer. In this screen the second entity can fill in the authorization code

" 1674.2533.1807.7562.5376". The second entity "the pharmacist Cees

Schaap" can then energize the button "activate authorization code". Then the screen according to Figure 37 appears on the computer of the second entity. This shows that the second entity "Cees Schaap" has obtained access to the file of the patient "Sven Berkvens-Matthijsse". When the second entity has obtained access to the file of the patient, he can proceed to consult and/or change the content of this file, as has been discussed with reference to Figures 2-17. Also, the operations that have been discussed with reference to Figures 18-24 may be performed.

When thereupon the second entity presses the button "overview of authorizations", the screen according to Figure 38A appears. This screen shows from whom the second entity (Cees Schaap) has obtained

authorizations, (from "Sven Berkvens - Matthijsse"), what the status of the authorization is, i.e., "reading and editing", and that the authorization is valid from 22-30 April. When the second entity actually wishes to inspect and change the medication file of Sven Berkvens - Matthijsse (the patient), he must presently press the button "log in" in the screen of Figure 38. This prompts automatic login on the medication file of the patient, whereupon, via the screen of Figure 38B, data of the patient can be edited and read as already set out with reference to Figures 2-24. This can be done, for example, by energizing the button 'medication'. If, for example, the second entity had not obtained permission to edit the data but tries to do so anyway, he will be shown a page according to Figure 39. This page shows clearly that the editing operation is not allowed.

In the foregoing example it has been assumed that the patient himself has set up his medication file in a first step c, d. and e. It is also possible, however, that this is done by, for example, a first entity such as a physician whom the patient is visiting. Via his computer, the physician has already obtained access to the first database via the website "meddossier.nl" from the starting screen as shown in Figure 25. When logging in, the first entity then used the screen according to Figure 26A, as described

hereinabove for the patient and the second entity. Thereupon the screen according to Figure 27B appears because the system knows that the first entity is a care provider. In this screen according to Figure 27B the first entity energizes the button "create new patient account", whereupon the system shows a fill-in screen as shown in Figure 40 on the computer of the physician. In this fill-in screen, the first entity fills in name and address details of the patient. In this screen the system generates an access code, which is once-only in this example. This access code, which is generated by the system, is read from the screen by the first entity and given to the patient. Evidently, this access code may also be communicated to the patient in a different manner, for example, via an SMS message or e-mail. Also, the first entity can now, as has been discussed with reference to Figures 2-24, enter data of the patient at the database. It holds that the first entity is automatically authorized to access the data now stored in the first database of the patient.

Then, for example, the patient goes home and on his computer goes to the website of "meddossier.nl". From the starting screen of Figure 25, he energizes the button "fill in this code". The system then generates the screen according to Figure 41. Here, the patient can enter the access code which he has obtained from the first entity. The patient thereupon fills in the access code "1111.2222.3333.4444.5555" (Figure 42) and energizes the button "Activate". Then the screen according to Figure 43 appears. Here the patient can enter a user name (hereinbefore also designated as name and address details) and the same password twice. Then the patient energizes the button 'activate'. From that moment onwards, the patient can log in via the screen according to Figure 25, Figure 26A and Figure 27A on the basis of his user name and password. By pressing the button "authorizations", a screen as shown in Figure 28 appears, listing to whom authorizations have been given. In this case, it would then appear that the first entity who in steps c, d. and e. has initially stored data of the patient in the first database, was automatically authorized. In this regard, for that matter, there are two possibilities. At the moment when the first entity performs the steps c, d., and e., he can also indicate, in consultation with the patient, what the nature is of his automatic authorization, such as, read-only, reading and writing, or full access or access to a part of the information of the patient. Also, it may be indicated whether the authorization is for a definite or for an indefinite period of time. When nothing is indicated, it is assumed that the authorization is a full authorization and for an indefinite period of time. When the patient is logged in on the computer system to consult his data which are stored in the first database, he can see, when he presses the button "authorizations", that the first entity has access for reading and editing and, for example, has access for an indefinite period of time. If he so wishes, he can remove or alter the authorization, for example, by changing the access for reading and editing to read-only and/or, for example, by changing the access for an indefinite period of time to an access for a definite period of time. He can do so by energizing the respective fields with a mouse click.

According to a particular embodiment, the computer system of Figure 1 is extended with at least one cash register system 18. The cash register system 18 and the computer system 1 together form a registration system 20. The cash register system 18 may be set up in a place where medicines are sold, such as a store, drugstore, gas station, and the like. The cash register system 18 is connected, for instance via an Internet connection 22, with the first server 4 of the computer system 1.

In the foregoing it has been explained that the first database can be filled by the patient himself, by the first entity and/or the second entity. Hereinafter, a patient, a first entity, a second entity and/or another person and/or institution that can fill the first database with information on the use of personal medication of a patient, coupled to information on the identity of the patient, will be referred to as an input entity. An input entity can be the patient himself, a physician, another person, or an institution such as a care institution or hospital. The working of the apparatus, in this example, is as follows.

A customer purchases, for instance, multiple medicines in a store where the cash register system 18 is set up. At the cash register system the medicines being purchased are recorded in the usual manner. This can be done, for instance, by reading out barcodes of the packages of the medicines. The customer can then pay for the medicines so that the customer

purchases the medicines. In this example, it holds that the cash register system is provided with information about medicines to be possibly purchased. By, for instance, scanning the barcodes, this information in the cash register system can be retrieved to determine what the medicines cost. All this is done in a step xl. The cash register system, however, is so arranged that it also passes on information on the medicines recorded at the cash register system to the computer system in an automatic manner via the connection 22. In this example, multiple medicines are involved, but also a single medicine may be involved. Passing on information on medicines recorded at the cash register system in an automatic manner is thus carried out in a step x2. The computer system 1, more particularly the server 4, is so arranged, in this example, that it carries out a step x3.1. In the step x3.1, the first server 4, in response to the information received in step x2, generates a code which is associated with the information received from the cash register system on the multiple medicines recorded. It holds, therefore, that a single code is associated with the multiple medicines recorded at the cash register system. The code and the associated information on the purchased medicines are thus present in the computer system for later use. The computer system, in this example the first server, thereupon supplies the generated code to the cash register system 18 in a step x3.2. In a step x4 the cash register system, in response to the received code, will provide the generated code to the customer. In this example, this is done in that the cash register system provides the code in a step x4 via printing on a receipt (see Figure 44) which is printed at purchase of the multiple medicines. The buyer takes along the medicines together with the receipt. The buyer can, for instance, hand over the medicines together with the code to a first patient who is already registered in the first database. Also, it is possible that the buyer himself is the user of the medicines but is not registered in the database yet. Then the buyer can register himself in the database, as already set out above. However that may be, we now assume that the first patient who is going to use the medicines was registered in the database at some point.

When the first patient is registered in the database, access to the data of the first patient can then be obtained in a usual manner, for instance on the basis of a password, by the patient or by an authorized person, such as a user who is in possession of the identity of a patient together with a password. This can be done, for instance, with the aid of the home computer 2 as has been discussed above with reference to the start screen of Figure 25.

The screen according to Figure 2 may then be shown after login. As can be seen, the screen according to Figure 2 also comprises a button 50 with the indication "purchased". When this button is energized, a fill-in screen according to Figure 45 is shown. In this fill-in screen, it is requested to fill in the code. A receipt that was printed at the cash register system after the multiple medicines were purchased is shown in Figure 44. On this receipt the code y5x2 can be read. This code can then be entered in the fill-in screen of Figure 45. Thus a step x5 is carried out. In response to the entry of the code, Figure 46 is then shown on the screen of the computer 2. In Figure 46, in this example, all medicines are shown that are associated with the respective code. In this case, two medicines are involved, viz., dexibuprofen and ibuprofen. Thus a step x6 is carried out, according to which the computer system, on the basis of the code entered at the computer system in step x5, provides to the input entity of step x5 information on the multiple medicines recorded at the cash register system. As in the computer system there is information on the purchased medicines available which is associated with the code, the computer system, on the basis of the code, can provide information on the purchased medicines to the input entity. This may be exactly the information that is associated with the respective code or, for instance, information on the purchased medicines in another format, for instance, supplemented with other information on respective medicines that is available in the computer system, such as information in the second database. The input entity can then, in a step x7, by energizing a button "choose" corresponding to the respective medicine, select a medicine that he is going to use. The computer system will then store the selected

information on the medicine, coupled to the identity of the first patient, in the first database. If, for instance, the medicine dexibuprofen is selected, it will be removed from the list because this medicine will presently be really used and no longer belongs in a hst actually relating to purchased

medicines. As obtaining access to the computer system also required the input entity to enter the identity of the first patient together with a password, it holds on balance that a step x7 is carried out according to which the input entity, in this example the input entity of step x6, selects at the computer system an identity of the first patient (a consequence of obtaining access to the computer system by entering the identity of a patient together with the corresponding password) and the at least one medicine if it will be used by the first patient, whereupon the computer system stores the selected information on the medicine, coupled to the identity of the first patient, in the first database. It follows, therefore, that the actions taken in step 7 need not be carried out simultaneously. This selecting of the identity of the first patient can be carried out by obtaining access to the computer system through entry of the identity of the patient and the matching password (login), whereas selecting the medicine that will be used in the hst mentioned is carried out at a later moment, once access to the computer system has been obtained (hereinafter an embodiment will be set out in which the substeps of step x7, by contrast, are performed, at least

substantially, simultaneously). Before the selected medication is stored as a medication that is used by the first patient, it is possible, as described above, to check the information input on the basis of the information from the second database 12. Thus, for instance, after selection of dexibuprofen in Figure 46, it is possible still to go through Figures 5 and 6. Such variants are within the framework of the invention.

It may happen that the medicines associated with the code will be used not only by the first patient but also by the second patient. It may also be that a first subset of the medicines associated with the code are used by the first patient and that a second subset of the medicines associated with the code are used by the second patient. In these cases, entirely analogously to what has been described for the first patient, a same procedure can be followed for the second patient. When the second patient is registered in the database, therefore, in a usual manner, for instance on the basis of a password of the second patient, access to the data of the second patient can be obtained by the second patient or by an authorized person, such as a user who is in possession of the identity of the second patient together with a password. This can be done, for instance, with the aid of the home computer 2 as has been discussed above with reference to the start screen of

Figure 25.

The screen according to Figure 2 can then be shown after login. As can be seen, the screen according to Figure 2 also comprises a button 50 with the indication "purchased". When this button is energized, a fill-in screen according to Figure 45 is shown. In this fill-in screen, it is requested to fill in the code. This is again the code of the receipt which is shown in Figure 44. On this receipt the code y5x2 can be read. This code can then be entered in the fill-in screen of Figure 45. Thus a step x5 is carried out. In response to entry of the code, Figure 46 is then shown on the screen of the computer 2. In Figure 46, in this example, all medicines are shown that are associated with the respective code. In this case, two medicines are involved, viz., dexibuprofen and ibuprofen. Thus a step x6 is carried out, according to which the computer system, on the basis of the code entered at the computer system in step x5, provides to the input entity of step x5 information on the multiple medicines recorded at the cash register system. The input entity can then in a step x7, by energizing a button "choose" which corresponds to the respective medicine, select a medicine that he is going to use. The computer system will then store the selected information on the medicine, coupled to the identity of the second patient, in the first database. If, for instance, the medicine dexibuprofen is selected, it will be removed from the list because this medicine will presently be really used and no longer belongs in a list actually relating to purchased medicines. As obtaining access to the computer system also required the input entity to enter the identity of the second patient together with a password, it holds on balance that a step x7 is carried out, according to which the input entity, in this example the input entity of step x6, selects at the computer system an identity of the second patient (a consequence of obtaining access to the computer system by entering the identity of a patient together with the respective password) and the at least one medicine if it will be used by the second patient, whereupon the computer system stores the selected information on the medicine, coupled to the identity of the second patient, in the first database.

Further, it is noted that in this example the code for the multiple medicines has been generated by the computer system, in particular the first server 4. It is also possible, however, that the cash register system generates the respective code. In that case, in step x3.1 the cash register system generates a code which is associated with the information on the recorded multiple medicines. Next, in a step x3.2 the generated code is supplied by the cash register system to the computer system. In step x2, as mentioned, in an automatic manner information on the multiple recorded medicines is passed on by the cash register system to the computer system. In the computer system the information on the multiple recorded medicines is processed, more particularly stored, in association with the received code. Also, the code is issued by the cash register system to the customer, for instance by printing it on the receipt. After this, a situation has come about in which the system can further work as already discussed above with reference to the steps x5, x6 and x7. It will be clear that the apparatus and method as discussed above can also be executed entirely analogously when the multiple medicines comprise only one medicine. In that case, the list shown will include only one medicine, which can then be selected by the input entity when the respective medicine is going to be used, whereupon the respective medicine, associated with the identity of the patient, is stored in the first database.

As mentioned, step 7 in the above -outlined embodiment comprises two substeps which are in fact carried out at mutually different moments in the process. Below, a variant will be described in which this is precisely not the case. In this variant, the steps xl to x4 are entirely analogous to those according to any of the variants as described above. After this, the registration system can be used as follows. The customer establishes contact with the computer system 1 with the aid of his home computer 2. With his computer 2, the customer can then select a web page of the computer system 1 such as for instance shown in Figure 47. At an entry field 20 the customer can enter the code that is on the receipt. This means, therefore, that in effect step x5 is carried out. On the basis of the code, the computer system displays a new web page on the computer 2 as shown in Figure 48. On this page the medicines are identified which are associated with the code entered. In this example, two medicines are involved, viz., dexibuprofen and ibuprofen. Thus, on the basis of Figure 48, step x6 is carried out, according to which the computer system, on the basis of the code entered at the computer system in step x5, provides information to the input entity of step x5 on the multiple medicines recorded at the cash register system. Figure 48 further shows two activation fields 22 and 24, respectively. By energization of the field 22 with, for instance, a mouse chck, the medicine dexibuprofen is selected. By energization of button 24 in this example the medicine ibuprofen is selected. Further, two more entry fields 26 and 28 are shown. Each medicine has its own entry field. The input entity can enter at entry field 26 the identity of a first patient for whom dexibuprofen has been purchased. At the entry field 28 the identity of a possibly other patient or the same patient can be entered for whom ibuprofen has been purchased. When, for instance, in field 26 the identity of a first patient is entered, after which field 22 is energized, this has as a consequence that at the computer system the identity of the first patient and at least one medicine, in this example one medicine, is selected which will, be used by the respective first patient. The computer system will then store the selected information on the medicine, coupled to the identity of the first patient, in the first database. After this, in field 26, if desired, the identity of another patient can be entered. If thereupon the field 22 is energized again with, for instance, a mouse click, this has as a consequence that at the computer system the identity of the second patient and at least one medicine, in this example again the medicine dexibuprofen, is selected which will be used by the respective second patient. The computer system will thereupon store the selected information on the medicine, coupled to the identity of the second patient, in the first database. When for a particular medicine of the list no more patients, or no patients, need to be selected that are going to use the medicine (for instance because a wrong medicine has been purchased), the medicine can be removed from the list, for instance by double chcking on the respective field 22, 24 of the medicine to be removed.

When the first patient and/or the second patient is registered in the database, then, in a usual manner, for instance on the basis of a password, access to the data of the first patient or second patient can be obtained by the first patient and/or second patient or by an authorized person, such as a user who is in possession of the identity of a patient together with a password. This can be done, for instance, for the first patient with the aid of the home computer 2 as has been discussed above with reference to the start screen of Figure 25.

If, for instance, the first patient then goes to the website of the computer system 1, named "meddossier.nl" in the example above, he will see, as discussed, the start screen according to Figure 25. As discussed, he can then navigate to the screen of Figure 2. In this screen, the first patient will then also see the medication appear that has been entered by the customer on the basis of the code. Next, the first patient can indicate in a usual manner when he is going to use this medicine, all this as discussed before. He can also indicate that he is not going to use the medicine, for instance when a wrong medicine has been purchased.

Entirely analogously, also the second patient can go to the website of the computer system 1, in the example above named "meddossier.nl", and, as discussed, see the start screen according to Figure 25. As discussed, he can then navigate to the screen of Figure 2. In this screen the second patient will then also see the medication appear that has been entered by the customer on the basis of the code. Then the second patient can indicate in a usual manner when he is going to use this medicine, all this as discussed before. He can also indicate that he is not going to use the medicine, for instance when a wrong medicine has been purchased.

It is noted that the substeps of step x7 are now carried out, at least substantially, simultaneously, since selecting the medicine, in this case dexibuprofen, as well as the identity of the first patient who is going to use the medicine concerned, is carried out more or less simultaneously on the basis of the screen according to Figure 48. Also, it is noted that it is possible in this manner to select for ibuprofen another identity of another patient or to select the identity of the first patient and/or the second patient. Thus it is possible for multiple medicines to be associated with a single code, after which it holds for each medicine of these multiple medicines that it can be selected to be used for a particular individual patient, while different medicines can be selected for mutually different and/or the same patients. It is advantageous here when the screens of Figures 47 and 48 can be accessed via the same website as the start screen 25 as discussed above. Thus, it is possible, for instance, that also in start screen 25 a separate button is provided which upon energization procures the screen 47. If, by contrast, the code is not entered on the basis of Figure 47, but login is done at the screen of Figure 25 by an input entity who, for instance, is the patient himself, then, as discussed above, after login it is possible to navigate to a screen according to Figure 2, whereupon, by the respective input entity, the button "purchased" can be selected after which the screen of Figure 45 is obtained. In the screen according to Figure 45 the code mentioned can then be entered. Presently, however, the situation is that, next, as set out, the screen according to Figure 46 is shown, where, however, it now holds for each of the medicines of the multiple medicines associated with the code that these can only be stored in the database as being a medicine coupled to the identity of the patient used for login in the screen according to Figure 25. In this example, therefore, it then holds that when the code is entered by a user who has logged in as, or on behalf of, a particular patient, the respective medicines coupled to the identity of this patient can be stored in the first database when they are selected for use. If, however, the code is entered at the web page according to Figures 47 and 48, then the buyer, who, for that matter, can also be the patient, or a representative of the patient, or another person or institution, can select an identity of a patient per medicine. For each variant as described above it holds that the respective code may be generated both by the cash register system and by the computer system. Obviously, the registration system may also be provided with multiple cash register systems which work as described for the cash register system 18. In this example, such a second cash register system 24 is shown in Figure 1. The invention is not limited in any way to the embodiments outlined above. The information on the medicine that is provided by the cash register system to the computer system in step x2 is not limited to any specific form. The only requirement is that on the ground of this information in step x6 information on the at least one purchased medicine (or the multiple purchased medicines) can be provided by the computer system to the input entity, on the basis of which the input entity in step x7 can select the at least one medicine (or medicines of the multiple medicines) if the medicine (or medicines) will be used by the patient. The information which in step x2 is sent by the cash register system to the computer system can therefore comprise the name of the purchased at least one medicine (or the names of medicines of multiple medicines if multiple medicines have been purchased). However, the information can also comprise an article code which relates to the purchased medicine, on the ground of which the computer system in step x6 can provide information about the purchased at least one medicine to the input entity, on the basis of which the input entity in step x7 can select the medicine if it is used. In that case the computer system will be provided with information on possible article codes and associated

information on medicines. In step x6 not the article code itself is then provided to the input entity, but, instead, information on the respective medicine associated therewith. The information on a purchased medicine that is supplied to the computer system in step x2 therefore need not have exactly the same form as the information on the respective purchased medicines that is provided to the input entity in step x6. It will be clear, though, that the information concerns one and the same purchased medicine. The information supplied by the cash register system to the computer system in step x2, however, can also comprise multiple article codes each relating to a purchased medicine if multiple medicines have been purchased, and on the ground of which the computer system in step x6 can provide information on the multiple purchased medicines to the input entity, on the basis of which the input entity in step x7 can select at least one medicine if it is used, or can select several medicines if several medicines are used. An article code can be, for instance, a number or a combination of characters and numerals. The code associated with the at least one medicine purchased or the multiple medicines purchased can also be a number or a combination of characters and numerals. This code is preferred to have the property of being easy to enter for an input entity in step x5. The code may therefore consist of, for instance, a maximum of 10 digits and characters. As mentioned, the code is associated with information on the at least one purchased medicine or the multiple purchased medicines, so that through entry of this single code in the computer system, on the basis of this code the information about the at least one purchased medicine or the multiple purchased medicines can be retrieved from the computer system by the computer system, after which information on the at least one purchased medicine or the multiple purchased medicines can be provided to the input entity in step x6. The code is hence unique within the method and the registration system and is in fact an identification code which is associated with the at least one purchased medicine. The code generated in step x3 may for instance, after it has been entered in step x5, remain valid for a year, i.e., the code and the associated at least one purchased medicine remain available (remain stored) in the computer system. An advantage is that the code can be entered once more in step x5 to be able to carry out step x6 and to be able in step x7 to couple the respective at least one purchased medicine to another patient who is also going to use the same purchased medicine (such as another member of the same family). Upon expiry of the respective year, the respective code and its associated information on the at least one purchased medicine may, for instance, be deleted from the computer system. The respective deleted code can then be generated anew in step x3 to be coupled to another at least one purchased medicine. In the variant according to which the code is generated by a cash register system, the computer system can for instance communicate to all cash register systems that are part of the registration system that the respective code has been deleted and hence can be used anew to be associated with purchased medicines. According to the variant in which the code is generated by the computer system, the computer system itself knows which codes are already in use (since the codes generated in step x2 and the associated at least one purchased medicine are available in the computer system to enable step x6 to be carried out) so that the computer system knowing which codes are already in use can generate a code that is still free to be associated with at least one purchased medicine. Further variants are also possible. Thus, when a patient enters a new use of a medication while this is in conflict with earlier-entered medication, for instance because two medications do not go together and may lead to hazardous reactions in a patient, the computer system may be so arranged as to automatically send an alert to the pharmacist or the general practitioner of the patient if it is stored in the first database who the general practitioner is and/or who the pharmacist of the patient is. If more than one general practitioner and/or more than one pharmacist are coupled to the identity of the patient concerned, then, for instance, each of the pharmacists and/or each of the general practitioners may be automatically sent an e-mail regarding the fact that the patient apparently uses, or is going to use, a medication that is in conflict with medications he is currently using. Furthermore, the first server and the second server may be replaced with one single server on which the first database and the second database are stored. Also, it is possible that the patient sends information about his use of a medication, for example on paper or in a memory stick, to a manager of the first database, whereupon the manager enters the medication at the first database, the patient first having utilized the second database for obtaining standard information on the medication to be entered and/or the manager utilizing the second database for entering the medication at the first database with standard information on the medication. The manager of the network may be, for instance, the first entity. A first entity and/or the second entity can access the first server and/or the second server, for instance, via the professional network E-care. In that case, via his computer 2 the patient then accesses the first server via the public Internet. Such variants are each understood to fall within the scope of the invention.

Claims

1. A method for keeping a personal medication file with the aid of a computer system, comprising:

a. utilizing a first database of the computer system, wherein by an input entity such as a patient, another person or institution, information on the use of personal medication of the patient, coupled to information on the identity of the patient, is stored in the first database, characterized in that the method furthermore comprises the steps of:

information on medicines to be possibly purchased;

x7: an input entity, in particular the input entity of step x6, selecting at the computer system an identity of at least one patient and the at least one medicine if it will be used by the at least one patient, after which the computer system stores the selected information on the medicine, coupled to the selected identity of the at least one patient, in the first database.

2. A method according to claim 1, characterized in that step x3 comprises the steps of:

x3.1: the computer system generating a code which is associated with the information received in step x2 from the cash register system on the recorded at least one medicine;

x3.2: the computer system supplying the generated code to the cash register system;

and that step x4 comprises the cash register system providing the code received from the computer system to the customer.

3. A method according to claim 1, characterized in that step x3 comprises the steps of:

x3.1: the cash register system generating a code which is associated with the information on the recorded at least one medicine;

x3.2: the cash register system supplying the generated code to the computer system so that after the carrying out of steps x3.2 and step x2 the computer system comprises the code and the associated information on the at least one medicine recorded at the cash register system;

and that step x4 comprises the cash register system providing the code generated by the cash register system to the customer.

4. A method according to claim 1, 2 or 3, characterized in that in step x6 the computer system shows the information on the at least one medicine and in particular multiple medicines which are associated with the code to an input entity in a separate list.

5. A method according to claim 4, characterized in that in step x7 an input entity such as the patient, the customer, a physician or a care institution, in particular the input entity of step x6, indicates at the computer system that the medicine stored in the separate list is used by the at least one patient whose identity is also selected in step 7, after which information on the use by the selected at least one patient of the personal medication belonging to the at least one medicine is stored in the first database and wherein in particular at least one medicine of which it is indicated that it is used is removed from the list.

6. A method according to at least one of the preceding claims, characterized in that step xl comprises recording multiple medicines in the cash register system, step x2 comprises the cash register system in an automatic manner passing on information on the multiple medicines recorded at the cash register system to the computer system, step x3 comprises generating the code which is associated with the information on the recorded multiple medicines, step x6 comprises the computer system, on the basis of the code entered at the computer system in step x5, providing information on the multiple medicines recorded at the cash register system to an input entity, and step x7 comprises the input entity, in particular the input entity of step x6, selecting at the computer system an identity of at least one patient and at least one medicine of the multiple medicines if this selected at least one medicine will be used by the at least one patient, after which the computer system stores the selected information on the at least one medicine, coupled to the selected identity of the at least one patient, in the first database.

7. A method according to at least one of the preceding claims, characterized in that in step x5 the code is printed by the cash register system, preferably on the receipt for the purchased at least one medicine.

8. A method according to at least one of the preceding claims, wherein the method furthermore comprises:

b. utihzing a second database of the computer system in which standard information of known medications is stored, wherein in step a. the patient utilizes the standard information from the second database for filling the first database.

9. A method according to claim 8, characterized in that in step a.

information on the use of a medication by the patient is stored in the first database according to standard information from the second database on the medication to be entered.

10. A method according to at least one of the preceding claims,

characterized in that in the entering of the information on the use of the medication by the patient, the computer system, on the basis of a keyword entered by the patient at the computer system, generates a list of

information on possible medications and shows it to the patient, whereupon the patient selects from the list a medication that corresponds to the medication that he uses, whereupon the selected information on the medication, coupled to the identity of the patient, is stored in the first database in the form of standard information.

11. A method according to at least one of the preceding claims,

characterized in that the patient, of a medication that he uses or has used, also enters information on the frequency of taking the medication, the form of administration of the medication, the strength of the medication, the use of the medication (for example, the period of taking the medication), the origin of the medication (supplier), the brand of the medication, information on a storage life of the medication, and/or an identity of a person such as a doctor or pharmacist, care institution, pharmacy and/or hospital that has prescribed the medication.

12. A method according to at least one of the preceding claims,

characterized in that the first database in a step c. is initially filled with information of the patient by a first entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution, after which the first entity, for example when the patient indicates he so wishes, provides the patient access to his information in the first database or that the first database in a step c. is initially filled with information of the patient by the patient.

13. A method according to claim 12, characterized in that the first database in a step d. is filled by the first entity or by the patient with information on the identity of the patient.

14. A method according to claim 12 or 13, characterized in that in a step e., by the first entity or by the patient, information on the use of the personal medication and/or other information on the patient such as information on tests performed on the patient, for example by the first entity, coupled to information on the identity of the patient, is stored in the first database.

15. A method according to at least claims 8 and 14, characterized in that in step e. the first entity or the patient utilizes the standard information from the second database for filling the first database.

16. A method according to any one of the preceding claims, characterized in that the patient provides access to his information in the first database to a second entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution, while in particular the patient also indicates which information the patient provides the second entity access to.

17. A method according to at least claim 8, characterized in that the second database comprises the G-standard, while the patient in step a.

and/or the first entity in step e. of claim 14 utilizes the G-standard for filling the first database.

18. A method according to at least claim 12, characterized in that the first entity provides access to the patient for him to access the first database via Internet, by providing an access code to the patient.

19. A method according to at least claim 16, characterized in that the patient provides the second entity access to his information in the first database by protecting his information with a password which he gives to the second entity.

20. A method according to at least claim 12, characterized in that the computer system, in the carrying out of step c. by the first entity, generates an access code and provides it to the first entity, wherein the intention is that the first entity gives this access code to the patient and wherein the patient can access his data in the first database, preferably via Internet, by entering the access code at the computer system, and wherein after the carrying out of step c. by the first entity the first entity is automatically authorized for access of the data of the patient stored and/or yet to be stored in the first database, wherein in consultation with the patient in the carrying out of step c. by the first entity it can be directly entered in the computer system whether the authorization is for a definite period of time or indefinite period of time and what the nature is of the authorization, such as, read-only, reading and writing, full access or access to a part of the information of the patient and/or characterized in that the initial filling of the database with data of the patient in step c. is carried out by the patient.

21. A registration system comprising a computer system provided with the first database according to at least one of the preceding claims and the cash register system according to any one of the preceding claims wherein the registration system is arranged for carrying out a method according to any one of the preceding claims.

22. A registration system comprising a computer system for creating and/or keeping a personal medication file provided with a first database, the computer system being so arranged that the following step can be carried out:

a by an input entity such as a patient, another person and/or

institution, information on the use of personal medication of the patient, coupled to information on the identity of the patient, is stored in the first database, characterized in that the registration system is furthermore provided with a cash register system, wherein the registration system is arranged to connect the cash register system communicatively with the computer system, wherein the registration system is arranged to enable, in use, the carrying out with the aid of the registration system of the method steps of:

xl: recording at least one medicine which is being purchased by a customer at the cash register system, the cash register system provided with information about medicines to be possibly purchased;

x3: the registration system generating a code which is associated with the information on the recorded at least one medicine; x4: the cash register system providing the generated code to the customer; x5: an input entity such as the customer or the patient entering the code received from the cash register system in step x4 in the computer system; x6: the computer system, on the basis of the code entered at the computer system in step x5, providing to an input entity, in particular the input entity of step x5, information on the at least one medicine recorded at the cash register system;

x7: an input entity, in particular the input entity of step x6, selecting at the computer system at least one identity of a patient and the at least one medicine if it will be used by the at least one patient, after which the computer system stores the selected information on the medicine, coupled to the selected identity of the at least one patient, in the first database.

23. A registration system according to claim 22, characterized in that the registration system is so arranged that step x3 comprises a step x3.1 and x3.2, wherein step x3.1 comprises the computer system, in response to the information received in step x2, generating a code which is associated with the information received from the cash register system on the recorded at least one medicine; and

step x3.2 comprises the computer system supplying the generated code to the cash register system; wherein

step x4 comprises the cash register system providing the code received from the computer system to the customer.

24. A registration system according to claim 22, characterized in that the registration system is so arranged that step x3 comprises a step x3.1 and x3.2, wherein step x3.1 comprises the cash register system generating a code which is associated with the information on the recorded at least one medicine; and step x3.2 comprises the cash register system supplying the generated code to the computer system so that after carrying out of step x3.2 and step x2 the computer system comprises the code and the associated information on the at least one medicine recorded at the cash register system;

25. A registration system according to any one of claims 22-24, characterized in that the registration system is so arranged that in step x6 the computer system shows the information on the at least one medicine and in particular multiple medicines which are associated with the code to an input entity in a separate list.

26. A registration system according to claim 25, characterized in that the registration system is so arranged that in step x7 an input entity such as the patient, the customer, a physician or a care institution, in particular the input entity of step x6, can indicate at the computer system that the medicine stored in the separate list is used by the at least one patient of whom in step 7 the identity is also selected, after which information on the use by the selected at least one patient of the personal medication belonging to the at least one medicine is stored in the first database and wherein in particular at least one medicine of which it is indicated that it is used is removed from the list.

27. A registration system according to any one of the preceding claims 22-26, characterized in that the registration system is so arranged that, in use, according to step xl recording multiple medicines at the cash register system can be carried out, according to step x2 the cash register system in an automatic manner passes on information on the multiple medicines recorded at the cash register system to the computer system, according to step x3 the registration system can generate the code which is associated with the information on the recorded multiple medicines, according to step x6 in an automatic manner, on the basis of the code entered at the computer system in step x5, information on the multiple medicines recorded at the cash register system can be provided by the computer system to the input entity of step x5, and according to step x7 an input entity, in particular the input entity of step x6, can select at the computer system an identity of at least one patient and at least one medicine of the multiple medicines that will be used by the at least one patient, whereupon, in use, the computer system stores the selected information on the at least one medicine, coupled to the selected identity of the patient, in the first database.

28. A registration system according to at least one of the preceding claims 22-27, characterized in that the registration system is so arranged that, in use, according to the step x4 the code is printed by the cash register system, preferably on the receipt for the purchased at least one medicine.

29. A registration system according to at least one of the preceding claims 22-28, characterized in that the computer system is further provided with a second database, wherein in the second database standard information of known medications is stored, the computer system being arranged to have the patient in step a. utilize the standard information from the second database for filling the first database.

30. A registration system according to claim 29, characterized in that the computer system is arranged for in step a. storing information on the use of a medication by the patient in the first database according to standard information from the second database on the medication to be entered.

31. A registration system according to at least one of claims 22-30, characterized in that the computer system is arranged for, in the entering of the information on the use of the medication by the patient, on the basis of a keyword entered by the patient at the computer system, generating a hst of information on possible medications and showing it to the patient, whereupon the patient can choose from the list a medication that

corresponds to the medication that he uses, the computer system being arranged to store the selected information on the medication, coupled to the identity of the patient, in the form of standard information in the first database.

32. A registration system according to any one of claims 22-31,

characterized in that the computer system is so arranged that the patient, of a medication he uses or has used, can also enter information on the frequency of taking the medication, the form of administration of the medication, the strength of the medication, the use of the medication (for example, the period of taking the medication), the origin of the medication (supplier), the brand of the medication, information on a storage life of the medication, and/or an identity of a person such as a doctor or pharmacist, care institution, pharmacy and/or hospital that has prescribed the

medication.

33. A registration system according to any one of the preceding claims 22-32, characterized in that the computer system is so arranged that the first database in a step c. can be initially filled with information of the patient by a first entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution and wherein the computer system is so arranged that the first entity, for example when the patient indicates he so wishes, can provide the patient access to his information in the first database and/or that the computer system is so arranged that the first database in a step c. can be initially filled with information of the patient by the patient.

34. A registration system according to claim 33, characterized in that the computer system is so arranged that the first database in a step d. can be filled by the first entity and/or by the patient with information on the identity of the patient.

35. A registration system according to claim 33 or 34, characterized in that the computer system is so arranged that in a step e. by the first entity and/or the patient information on the use of the personal medication and/or other information on the patient such as information on tests performed on the patient, for example by the first entity, coupled to information on the identity of the patient, can be stored in the first database.

36. A registration system according to claim 35, characterized in that the computer system is so arranged that in step e. the first entity and/or the patient can utilize the standard information from the second database for filling the first database.

37. A registration system according to at least one of the preceding claims 22-36, characterized in that the computer system is so arranged that the patient can provide access to his information in the first database to a second entity such as a physician and/or pharmacy and/or pharmacist and/or hospital and/or care institution, while in particular the patient can also indicate which information the patient provides the second entity access to.

38. A registration system according to claim 29 and possibly at least one of the preceding claims 22-28, 30-37, characterized in that the second database comprises the G-standard, while the computer system is so arranged that the patient in step a. and/or the first entity in step e. of claim 35 can utilize the G-standard for filling the first database.

39. A registration system according to at least claim 33 and possibly at least one of the preceding claims 22-32, 34-38, characterized in that the computer system is so arranged that the first entity can provide access to the patient for him to access the first database via Internet, by providing an access code to the patient.

40. A registration system according to at least claim 37 and possibly at least one of the preceding claims 22-36, 38-39, characterized in that the computer system is so arranged that the patient can provide the second entity access to his information in the first database by protecting his information with a password which he gives to the second entity.

41. A registration system according to at least claim 33 and possibly at least one of the preceding claims 22-32, 34-40, characterized in that the computer system is so arranged that the computer system, in the carrying out of step c. by the first entity, generates an access code and provides it to the first entity, wherein the intention is that the first entity gives this access code to the patient and wherein the computer system is so arranged that the patient can access his data in the first database, preferably via Internet, by entering the access code at the computer system, and wherein after the carrying out of step c. by the first entity the first entity is automatically authorized for access of the data of the patient stored and/or yet to be stored in the first database, wherein the computer system is further so arranged that in consultation with the patient in the carrying out of step c. by the first entity it can be directly entered in the computer system whether the automatic authorization is for a definite period of time or indefinite period of time and what the nature is of the automatic authorization, such as, read-only, reading and writing, full access or access to a part of the information of the patient and/or characterized in that the computer system is so arranged that the initial filling of the database with data of the patient in step c. can be carried out by the patient.