NL2010501C2 - METHOD FOR CREATING AND / OR MAINTAINING A PERSONAL MEDICATION FILE USING A COMPUTER SYSTEM. - Google Patents

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

CMJ P101015NL10

Title: Method for creating and / or maintaining a personal medication file using a computer system.

The invention relates to a method for maintaining a personal medication file with the aid of a computer system, comprising: a. Using a first database of the computer system in which information about the use of data is provided by an input entity such as a patient, doctor or healthcare institution personal medication of the patient linked to information about the identity of the patient is stored in the first database.

Such a method is known, inter alia, from Dutch patent application 2007 736. The invention contemplates in some cases simplifying the introduction of the information about the medication into the first database.

According to the invention, the method is characterized in that the method further comprises the following steps: x1: charging at least one medicine that is purchased by a customer at a cash register system wherein the cash register system is provided with information about possible medicines to be purchased; x2: the automatic transmission of information by the cash register system about the at least one medication struck at the cash register system to the computer system; x3: generating a code associated with the information about the excited at least one drug; x4 providing the generated code to the customer by the cash register system ;.

X5: entering the code received from the cash register system in step x4 into the computer system by an input entity such as the customer or patient; x6: providing information from the computer system based on the code entered at the computer system in step x5 to an input entity about the at least one drug struck at the cash register system; x7: selecting at least one identity of a patient and the at least one medication at the computer system by an input entity, in particular the input entity of step x6, if it will be used by the at least one patient, after which the computer system transfers the selected information stores the medication linked to the selected at least one patient's identity in the first database.

According to the method, it is thus facilitated to enter purchased drugs into the first database. After all, it is no longer necessary for the name of the medicine itself to be entered when entering at least one medicine into the database. Instead, the code received from the cash register system can be entered into the computer system.

The latter can, for example, be carried out as follows. Suppose the at least one patient has already created an account with the computer system. This means that an identity of the at least one patient is already included in the first database. If the at least one patient is already taking medication, information about the personal medication, coupled with information about the identity of the at least one patient, will generally be stored in the first database. The first database can preferably be accessed via the internet, for example with a home computer, by an input entity such as the patient or another person, for example after a special password coupled thereto is entered in addition to the patient's identity.

3

The method can be carried out as follows, for example. A customer buys at least one medicine from, for example, a drugstore, supermarket, gas station, or another store. For example, the client may be the patient or someone who buys the at least one drug for the patient. The customer 5 then goes with the at least one medication to the cash register system where the at least one medication is struck. The cash register system is provided with information about possible medicines to be purchased. The customer pays in the usual way for the at least one medicine at the cash register system. The cash register system will then automatically transfer information about the at least one medication that has been struck at the cash register system to the computer system. A code is also generated that is associated with the information about the excited at least one drug. The generation of the code can, for example, be carried out by the computer system in response to the receipt of the information about the at least one drug struck 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 relevant code to the customer. The delivery of the code to the customer can be done, for example, by printing it on a receipt, in particular the receipt. Thus, in a step x3.1, the computer system may generate a code associated with the information received in step x2 from the cash register system about the excited at least one drug. A consequence is therefore that after performing step x2 and step x3.1, the computer system comprises the code and the information associated with it about the at least one medicine struck by 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 step x4 the code received from the computer system is then provided to the customer by the cash register system. However, it is also possible that the cash register system generates a code that is associated with the information about the excited at least one drug. The 4 cash register system can then add this code to the computer system. In that case the computer system has received information from the cash register system about the at least one medicine and the associated code. In that case, the cash register system 5 will provide the customer with the code generated by the cash register system, for example by printing it on a receipt 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 as the information associated with it about the at least one medicine struck at the cash register. This therefore applies to both of the aforementioned cases.

For example, the customer then goes home. The customer can then give the code to the at least one patient. It is also possible that the customer himself concerns the patient. The customer can also give the code to another input entity which is provided with the said password to access the data of the patient. The input entity, such as, for example, the customer or the patient, can then, for example, contact the computer system in the usual manner, for example via the Internet, using, for example, its home computer. Hereafter, for example, a web page can be accessed that is arranged for entering the code. For example, the computer system may then display information on the at least one drug associated with the code in response to entering the code on the home computer screen. More specifically, a plurality of drugs are shown, each of which is associated with the code. For example, if the input entity knows that a particular first patient is going to use one of the displayed medications that have been purchased, he can selectively select this drug with a mouse click, for example. The input unit can also enter the identity of the first patient associated with the selected drug. With this the identity of the first patient is selected. After this, the relevant selected medication, linked to the selected identity of the first patient, will be stored in the first database. If the input entity knows that the same drug will also be used by another second patient, it can also enter the identity of this second patient as discussed for the first patient. After this, the relevant selected medication, linked to the selected identity of the second patient, will be stored in the first database. The first and second patients can, for example, be a mother and daughter of the same family. If, for example, the input entity also knows that a certain other third patient is going to use one or more of the other medications that have been purchased, he can select this medicine or these medicines, for example with a mouse click, in the usual way. The input unit can also enter the identity of this other third patient associated with the selected drug or drugs. With this, the identity of the other third patient is therefore selected. After this, the relevant selected other drug or the selected selected other drugs, linked to the selected other identity of the third patient, will be stored in the first database. The input entity can also preferably indicate that a medicine from the list will not be used by even more patients than has already been indicated, so that the medicine in question disappears from the list.

According to the invention, all this can also be carried out differently.

Thus, the input entity can again access the computer system with its home computer via the internet and now select a web page with which access can be gained to information about the use of medication by patients whose use of medication is already stored in the first database. For this purpose, for example, the identity of a first patient is entered together with a password. After this, access is then obtained to the information already stored in the first database about the use of medications by the first patient. After this, for example, 6 the code can be entered, after which the at least one medicine that is associated with the code is displayed on the screen of the home computer. After this it can be indicated that the medicine in question is used, after which the medicine in question, linked to the identity of the first patient, is stored in the first database. If a plurality of drugs are associated with the entered code, they will each be displayed on the screen. You can then indicate which of these medicines will be used. Each of the selected drugs will then be stored in the first database linked to the identity of the first patient.

Subsequently, for example, the input entity can again access the computer system with its home computer via the internet and select the web page with which access can be gained to information about the use of medication by patients whose use of medication is already stored in the first database. After this, for example, the identity of a second patient is entered together with a password. After this, access is then obtained to the information already stored in the first database about the use of medication by the second patient. After this, for example, the same code that was entered for the first patient can be entered, after which the at least one medication associated with the code is displayed on the home computer screen. It can then be indicated that the relevant medicine is used, after which the relevant medicine, linked to the identity of the second patient, is stored in the first database. If a plurality of drugs are associated with the entered code, they will each be displayed on the screen. You can then indicate which of these medicines will be used. Each of the selected drugs will then be stored in the first database, linked to the identity of the second patient. In each of the cases, and in general, it therefore holds that a medication linked to at least one identity of a patient or linked to a multiple (also more than two) of identities of patients can be stored in the first database.

According to the method, an identity of the at least one patient is therefore selected in the computer system, for instance in that the identity of a patient is entered together with a password, after which access is gained to information of the patient stored in the first database. Also, the at least one drug, if used by the patient, is selected by the input entity. In other words, it is through the input entity of step x7. selecting at the computer system an identity of at least one patient and the at least one medication, if it will be used by the at least one patient, is performed by the input entity, after which the computer system selects the selected information about the medication coupled to the identity of the stores at least one patient in the first database. Selecting the identity of a patient is in that example linked to providing 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 patient's identity is selected in another manner, as has already been indicated above, together with the at least one medication. It is also 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 after which the computer system stores the information about the medicine, linked to the identity of the patient, in the first database . It is also possible that after providing access to the computer system by means of the identity of the at least one patient and the password, as discussed above, by subsequently entering the code the computer system has the selected information about the medicine, coupled to the identity of the at least one patient in the first database. The assumption is then that once the code is entered, the at least one drug will also be used by the at least one patient. The selection of the at least one patient in step x7 is then performed by providing said access to the computer system using the identity of the at least one patient and the password. Such variants fall within the scope of the invention. From the foregoing it also appears that in general it holds that in step x6 the computer system on the basis of the code entered at step x5 at the computer system and the information received at step x2 about the at least one medicine struck at the cash register system 10 at a input entity, in particular the input entity of step x5, information is provided about the at least one drug struck at the cash register system.

A major advantage of the invention is that the code can also be or can be linked to a plurality of medicines. It is therefore possible that the customer purchases a plurality of medicines at the same time. It then holds in step xl that a plurality of medications is struck in the cash register system. It then holds for step x2 that the cash register system automatically transmits information to the computer system about the plurality of medications that have been struck at the cash register system. The computer system receives this information and can then, for example, generate a code associated with the information about the excited multiple of drugs. This code is then sent again by the computer system to the cash register system. The cash register system again provides the customer with the code. The advantage is then that the single code is associated with a plurality of drugs. Subsequently, when the input entity, for example on its home computer, provides itself access to the computer system as, for example, according to one of the ways as discussed above, the input entity can select from the plurality of drugs that drugs it and / or the patient (s) concerned actually go after which the computer system will store these 9 medicines, linked to the identity of the patient, in the first database. According to a practical variant, it may be that the computer system first of all generates and / or shows a list of the multiple medicines that are associated with the entered code.

5 The import entity can then select from this list those medicines that he and / or the patient (s) concerned will use. This can be, for example, one or more medicines. After selection, that drug that is selected for use, linked to the identity of the at least one patient, is stored in the first database. The medicine that is then used is removed from the list mentioned, for example when it is indicated that there are no more patients or no patients who are going to use the medicine. It is also possible that if the patient later decides to also use other medicines that have been purchased and that are on the list, these medicines will also be selected from the list in order to be subsequently linked to the identity of the at least one patient or linked to the identities of a plurality of patients, to be stored in the first database. Even then, once a medicine has been selected, the relevant medicine will be removed from the relevant list. After all, the list includes medicines that have been purchased but are not yet being used.

If a plurality of drugs are purchased, it is also possible that step x3 includes the following steps. In a step x3.1, a code is generated by the cash register system that is associated with information about the excited multiple of drugs. 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 supplied in step x2 about the medicines purchased. In 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 that obtains the code from the customer, or when the input entity is the customer itself, can then enter the code into the computer system as discussed above. The computer system can then, on the basis of the code entered, provide the input entity with information about the plurality of medications initiated at the cash register system. The input entity can then in the computer system select from the plurality of drugs that select drugs or the single drug that is known to be used by the at least one patient. The identity of the at least one patient has for instance already been selected because the input entity has contacted the computer system on the basis of the identity of the patient and the aforementioned password. The computer system can then store the selected information about the drugs or the single drug that will be used, linked to the patient's identity, in the first database. As stated, the identity of the at least one patient can be selected on the basis of providing access to the computer system on the basis of the identity of the patient and the associated password (logging in). It is also possible that on for instance a web page of the computer system the identity of the at least one patient, possibly the password and the associated code are entered in one go, after which it may be necessary to indicate which medicines will be used so that these medicines, coupled the identity of the patient, in the first database. However, it is also possible that by entering the code it is immediately assumed that the medicines in question are used, whereafter the medicines in question are all stored in the first database linked to a selected identity of the at least one patient. Such variants fall within the scope of the invention.

A special variant according to the invention is accordingly characterized in that the method further comprises: 11 b. making use of a second database of the computer system in which standard information of known medications is stored, wherein in step a the patient uses information from the second database for filling the first database.

Because the patient also uses information stored in the second database when entering information about the use of his personal medication, it can be ensured 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 about the use of personal medication also includes information about the use of personal medication from the past and which medication is no longer being used (history).

In particular, it holds here that in step a. Information about the use of a medication by the patient is stored according to standard information from the second database about the medication to be entered in the first database. More in particular, it applies here that when the information on the use of the medication by the patient is entered, the computer system generates and displays a list of possible medications to the patient on the basis of a keyword entered by the patient at the computer system , after which the patient chooses from the list a medication corresponding to the medication he uses, after which the selected information about the medication is linked to the identity of the patient in the form of standard information in the first database. In this way it is ensured that correct and unambiguous information about the use of medication by the patient is entered.

In particular, it holds here that the patient of a used medication also enters information about the frequency of intake of a medication according to the medication, the dosage form of the medication, the strength of the medication, the use of the medication (e.g. the period of the medication), the origin of the medication (supplier), the brand of the medication, information about a shelf life of the medication, and / or an identity of a person such as a doctor or pharmacist, care institution, pharmacy and / or or hospital that has prescribed the medication. Here, medication is understood to mean a prescribed medication together with a desired method of administration of the medication such as a frequency of intake, a method of intake, a period of intake, etc.

According to a very advanced embodiment of the method, the computer system generates a warning for the patient when after entering new information about a used medication in step a. The first database shows that the new information does not coincide with information from the first database on the use of a medication that the patient is already using.

In the foregoing it has been assumed that the patient already has access to his information in the first database. The initiative for storing information from the patient in the first database and providing access to the first database to the patient may, for example, lie with a first entity. Preferably, it then holds that the first database in a step c. is initially filled with information from the patient by a first entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution after which the first entity provides access to the patient's information in the first database. It is also possible that the patient is the first to show the initiative to store information about the patient in the first database. In that case, the first database is entered in an initial step c. first filled by the patient. Initially filling the database with information from the patient by the first entity and / or the patient may also only include filling the database with information about the identity of the patient. Information about the use of medication and / or other information about the patient can then be entered later, linked to the identity of the patient, at the first database by the first entity and / or the patient. Providing access to the patient by the first entity can occur 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 itself and no access to the first database is provided to the patient. In particular, the first database in a step d. filled by information about the identity of the patient by the first entity.

Subsequently, in a step e. the first entity and / or the patient stores information about the use of the personal medication, linked to information about the patient's identity, in the first database. Also in step e. other information about the patient is stored that is linked to the identity of the patient. This other information may include, for example, results of examinations performed by the first entity on the patient, such as X-rays, MRI scans, CT scans, and lab results. If the first entity has given the patient access to the first database, the patient can from that moment view his information in the first database. When the patient himself has no access to the first database, the patient can view the first database when it is at the first entity. The first entity can then view 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. For example, when the patient indicates to use certain drugs or not to use them anymore, the first database can be adjusted accordingly.

In particular, in step e. the first entity uses the standard information from the second database to fill the first database. Preferably, step e.

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

If desired, the patient may decide to grant access to his information in the first database to a second entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution. Here, the second identity is preferably not given access to the complete first database, but only access to that part of the first database that contains information about the patient in question. In particular, after providing the second entity with access to the first database, information about the patient from the first database can be sent by e-mail or similar message to the second entity and / or the second entity is offered the opportunity to obtain or consult information from the patient from the first database, for example by downloading, printing or reading from a display. Preferably, the second entity 15 is only given access to information from the patient stored in the first database when the patient has given access to the second identity, in particular the patient also indicating to which information the patient is giving access to the relevant second entity. The patient may, for example, provide the second entity with access for an indefinite period of time, provide access for a definite period of time, or provide one-time access to information of the patient stored in the first database. In exceptional circumstances, the second entity can still gain access to information from the patient in the first database, even when the second entity has not received permission from the patient for this. Such a special circumstance may occur, for example, when the patient is in danger to life and unable to provide access to the second entity. In that case, however, the fact that the second entity has consulted information about the patient in the first database is preferably stored in, for example, the first database 30 so that it can later be verified that the second entity has not misused the access obtained. The patient can also revoke the access he has provided to the second entity. The patient is and remains the master of the information stored about him in the first database.

Preferably, the second database is filled with information about medicines according to the G standard. In step a. The patient then uses this standardized information for filling the first database with information about his use of medication (medication).

An aim of the system and method according to the invention is therefore to ensure that every care provider (one of the said entities) from the patient's network has the same information available 24/7/365; of course only with the consent of the patient. This permission can mean authorization at different levels and can be changed continuously by the patient. Everything is logged with access to the patient.

The advantage for the patient is that there is as little misunderstanding as possible about the treatment and the possibility to test his own use, to look up information specifically, and to communicate about this in a targeted manner (e.g. with a preferred healthcare provider).

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

In patient A's personal medication file, an appointment is planned with healthcare institution B (one of the aforementioned entities). That agreement comes about because the medication file of patient A, that is to say the special embodiment of the system according to the invention comprising the first database, on the instruction of patient A to the planning system of care institution B or to someone from care institution B ( from the list of care institutions with which patient A does business) asked for an appointment. The system according to the invention is therefore communicatively connected to the planning system of the care institution 16 B. The planning system of the care institution or someone from the care institution itself sends a date / time back to the personal medication file of patient A. After 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 from care institution B, and the appointment is in the personal patient's medication file A. If patient A accepts this with his personal medication file, his personal medication file sends the scheduled appointment for confirmation to healthcare institution B and in particular forwards to patient's Google calendar or Outlook A. The appointment can also be made on request from healthcare institution B is established because healthcare institution B is on the personal medication file of patient A has asked whether patient A wants to come to visit the care institution. Patient A then starts the cycle as above.

In particular, prior to the appointment (set / default), the personal medication file of patient A automatically sends a request for information to the system of healthcare institution B. With that request, a one-time permission can be sent for healthcare institution B to 20 other healthcare institutions (other entities) ) request information about patient A once 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 differences result in a demand for patient A that is generated by the system comprising the first database and stored in the personal medication file of patient A. Patient A solves that question 30 or not. If "not" then the question appears in the overview with 17 discussion points of patient A in his personal medication file. When visiting care institution B, patient A can go through those points with care provider B. For example, the overview that is already existing is approved by patient A and sent as a definitive overview for single use by care institution B to the system of care provider B and this is added to the personal medication file of Patient A. The consultation / treatment can start.

In particular, after treatment or at the end of the consultation, care institution B 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, then patient A select a pharmacy C to which the prescription is sent (patient A cannot change the prescription). The prescription is preferably accompanied by an up-to-date medication overview and possibly a one-off permission to collect information from other care providers (entities). After being sent to pharmacy C, the prescription is added in patient A's personal medication file to the list of “proposed medication from patient A” and the prescription itself is deleted from patient A's personal medication file after sending to pharmacy 20 C. Pharmacy C delivers / sends the medication to patient A and preferably a message of delivery to patient A's personal medication record. Patient A physically starts using it after receiving the medication and enters the actual use in his personal medication record, whereby the status of the drug changes to "topical" with a real use.

The following can be said about retrieving other information from other healthcare institutions as discussed above. In principle, pharmacy C cannot find any differences if healthcare institution B has already done a search. But suppose that patient A has started using 30 drug drugs or internet drugs in the meantime, then 18 a difference can occur between what patient A and healthcare institution B have approved and pharmacy C thinks. Pharmacy C therefore preferably sends an overview of the used medication to the personal medication file of patient A. The system according to the invention then preferably compares this received information with the current information as it is stored in the personal medication file of patient Ais and generates at deviations a question from the patient A, and / or the care institution B and / or the pharmacy C. The invention furthermore relates to a registration system comprising a computer system for creating and / or maintaining a personal medication file provided with a first database, wherein the computer system is arranged such that the following step can be carried out: a. by an input entity such as a patient, another person and / or institution, information about the use of personal medication of the patient is linked to information about the identity of the patient , stored in the first database, with the attribute, that the registration system is further provided with a cash register system wherein the registration system is adapted to communicate the cash register system with the computer system, wherein the registration system is adapted to be able to use the following method steps in use with the aid of the registration system: x1: charging at least one medication that is purchased by a customer at the cash register system whereby the cash register system is provided with information about possible medication to be purchased; X2: the automatic transfer of information by the cash register system on the computer system to the at least one medication struck by the cash register system; x3: generating by the registration system a code associated by the registration system with the information about the excited at least one drug; 19 x4: providing the generated code to the customer by the cash register system; x5: entering the code received from the cash register system in step x4 into the computer system by an input entity such as the customer or the patient; x6: providing information about the at least one drug struck at the cash register system based on the code entered at the computer system in step x5 to an input entity, in particular the input entity of step x5; X7: Selecting at least one identity of a patient and the at least one medication at the computer system by an input entity, in particular the input entity of step x6, if it will be used by the at least one patient, after which the computer system will select the selected information about the medication linked to the selected identity of the at least one patient in the first database.

The following also applies:

Wherever “patient A” is located, an authorized person with the correct level of authorization can take the actions of patient A.

All kinds of services can be developed around this 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 now be further elucidated with reference to the drawing.

Herein: Figure 1 shows a computer system according to the invention for performing a method according to the invention;

Figure 2 shows a first input screen for performing a step a. Of a possible method according to the invention;

Figure 3 shows a second input screen for performing step a.

30 of a possible embodiment of the method; 20

Figure 4 shows a third input screen for performing step a. Of a possible embodiment of the method;

Figure 5 shows a fourth input screen for performing a step a. Of a possible method according to the invention; Figure 6 shows a fifth entry screen for performing step a. Of a possible embodiment of the method;

Figure 7 shows a sixth input screen for performing step a. Of a possible embodiment of the method

Figure 8 shows a screen with information entered by a patient about the use of a specific medication;

Figure 9 shows a seventh input screen for performing step a. Of a possible embodiment of the method;

Figure 10 shows an eighth input screen for performing step a. Of a possible embodiment of the method; Figure 11 shows a ninth entry screen for performing a step a. Of a possible method according to the invention;

Figure 12 shows a tenth entry screen for performing step a. Of a possible embodiment of the method;

Figure 13 shows an eleventh fill-in screen for performing step a. Of a possible embodiment of the method;

Figure 14 shows a twelfth fill-in screen for performing a step a. Of a possible method according to the invention;

Figure 15 shows a thirteenth input screen for performing step a. Of a possible embodiment of the method; Figure 16 shows a fourteenth fill-in screen for performing step a. Of a possible embodiment of the method;

Figure 17 shows an upgraded screen overview ;, also input screen for new medication;

Fig. 18 a fill-in screen for printing information; Figure 19 shows a fill-in screen for printing information; 21

Figure 20 shows a possible print-out by a patient about the use of his medications;

Figure 21 shows an input screen for printing information

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

Fig. 23 is an input 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 fill-in 10 and information display screens of a particular embodiment of the invention;

Figure 44 shows a receipt with a code on it;

Figure 45 shows a fill-in screen;

Figure 46 a fill-in screen Figure 47 a fill-in screen; and

Figure 48 shows an input screen.

In Figure 1 reference numeral 1 designates a computer system according to the invention for performing a method according to the invention. In this example, the computer system is provided with a computer 2 of a patient who is, for example, set up at home. The computer system is furthermore provided with a first server 4 and a second server 6. In this example, the computer 2 and the first server 4 are connected via internet 8. Also in this example the first server 4 and the second server 6 are connected via internet 8.

In this example, a first database is stored on the first server 4, in which information about the use of his personal medication linked to information about the identity of the patient is stored by a patient. This first database is designated with reference number 10. Furthermore, a second database 12 is stored in the second server 6, in which standard information of known medications 22 is stored. In this example, the second database is filled with information about medication according to the G standard.

A patient can store information about the use of his personal medication linked to information about his identity via his computer 2. The first database thus comprises a personal medication file for the patient concerned. This is explained on the basis of an example in which the patient 14 wants to store information about medication that he uses in his personal medication file. This goes as follows. First of all, the patient 14 approaches the database 10 using his computer 2. For example, he can do this by entering his first and last name. The server 1 will then, for example, request a password from the user 14. The user 14 will then see the question displayed on his computer 2: "enter your password". The patient 14 then enters the password via the computer 2, which password is supplied to the first server 4 via the internet connection 8. The first server 4 checks on the basis of information in the database 10 whether the password is correct. If the password is correct, the patient gets access to his personal medication file that is stored in the first database 10. For example, the patient will see a screen with personal information such as name and address. If a patient wants to enter a new medication, he can click on the “medication” tab on his screen, after which he will be shown a screen according to figure 2. The screen shows information about previously entered medication by the patient. The patient then confirms a "add medication" button with, for example, his mouse.

After this he will see the screen as shown in figure 3. In the screen, the patient can enter a keyword for the medication in question under “characteristic of the medication”. In this example he enters Ibuprofen as the keyword. He then clicks the "search for medication" button. The image according to figure 4 then appears on his screen, which in this example is generated by the first server on the basis of information from the second database 12. This therefore concerns standardized information. To this end, the first server has fed Ibuprofen to the second server via the Internet. The second server 6 searches in the second database 12 hits that relate to Ibuprofen. The information about these hits 5 is sent by the second server to the first server. On the basis of this information, the first server generates the screen according to Fig. 4 which is displayed on the computer 2 of the patient. Here the patient sees that there can be two types of Ibuprofen, namely Dexibuprofen and Ibuprofen. It is also indicated here that Ibuprofen 10 is also known as Antigrippine Ibuprofen. In this example, the user selects with his mouse the “choose” button that belongs to Ibuprofen. On the basis of the information from the second database, the first server then generates a new input screen according to Figure 5 on the computer 2 of the patient. This shows that the patient must choose from the form in which the medication is administered (such as melting tablet, capsule, soft, etc.). In this example, the patient opts for Capsule, soft. After this, the input screen according to Figure 6 is generated. The strength of the Ibuprofen medication must be chosen here. He can choose between 200 mg. and 400 mg. In this example, the patient opts for 200 mg. by activating the relevant button that is supposed to be at 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 this. If he does not know this, he can choose: "I cannot choose." In this example he chooses the 25 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 wants to. In the first database, information about the use of the Ibuprofen medication, linked to the identity of the patient 14, is stored. However, the patient can also add information about the use of the medication in question. To this end, he confirms 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 indicate whether or not this is an estimate. He can then confirm the entered information by confirming the "confirm" button. Then the screen according to Figure 10 appears where, if known, the end date of the usage period can be entered. In this example, the date 2010-02- 18. It is also possible to indicate again whether this is an yes or no estimate. After entering this information, the "end date 10 entered" button can be confirmed. If the end date is not yet known, the " no end date "can be validated. If it is a single-use medication, the single-use button can be confirmed on 18-01-2010." After activating one of the three buttons, the server 1 generates the input screen according to figure 11. The patient can indicate whether it is a use of medication only at predetermined times or a use of medication when he needs it, but not on the basis of predetermined times or medication use when he needs it and at predetermined times. In this example, a medication use is chosen according to set times. After this, the input screen appears according to figure 12. Here the patient must indicate how the medication use is repeated. He can choose between: "this medication is the same every day", "this medication is the same every week", "my use differs per day and week, but every month 25 looks the same with regard to the use of the medication" or "the use does not fall into the above categories". In this example, the patient confirms the button associated with "this medication is the same every day." After this, the input screen appears according to figure 13. Here it must be indicated how the medication is used per day. In this example, the patient fills out that he uses two pieces in the afternoon. After entering the number 2 25, he confirms this by confirming the "confirm" button. After this the input screen according to figure 14 appears. Here the patient can enter the prescriber if applicable. In the last option the possibility is already indicated that the medication is prescribed by the general practitioner who is mentioned in the first database as being associated with the patient concerned. In this example, the patient opts for the last option, namely that the medication is prescribed by Dr. Maatbeker of the Maakbeter practice in Rotterdam. In this example, the patient in question has previously stored in the first database who his doctor and pharmacist are. The patient can also choose the option "no, this medication has not been prescribed for me by anyone", "no, this medication has been prescribed for me but not by someone from the list below", or "my prescriber is not listed yet, I wants to add the prescriber to the list ”. After the patient has opted for the last option, the entry screen according to figure 15 appears. Here the patient can, if applicable, enter the pharmacy where he has obtained the medication in question. He can choose between the options: "no, I have not obtained this medication through a pharmacy", "no, I have obtained the medication through a pharmacy, but not through a pharmacy from the list below", "my pharmacy is listed not yet, I want to add the pharmacy to the list ", or" yes, I got the medication through Pieter de Pil from Rotterdam ".

In this example, the patient chooses the latter option. After this, the input screen according to figure 16 appears, in which more information about medication use is requested. The patient can choose between "I indeed have a repeat prescription for this medication" or "I don't have a repeat prescription for this medication". In this case, the patient opts for the latter option. Hereafter the overview according to figure 17 appears which corresponds to the overview according to figure 2 with the difference that the use of Ibuprofen has been added.

26

All information discussed above and entered with reference to Figures 3-17 have now been added to the personal medication file of the patient 14. It is noted that the patient can also enter other information if desired. The screen of Figure 5 2 could, for example, also include a "other information" button.

When this button is actuated, for example, subsequently a fill-in screen with a free fill-in field is shown where this other information can be entered. This can be done by the patient typing in the field. Also, files (word documents, scans, photos, etc.) containing this other information can be dragged by the patient into the free field in a known manner so that these files are stored in the first database. This other information is again stored, linked to the identity of the patient. The other patient information may include, for example, results of examinations performed by the first entity on the patient, such as X-rays, MRI scans, CT scans, and lab results.

Figure 17 also shows that the patient in question has already used or has used Dexibuprofen, Dyclophenac and Paracetamol. Further information (such as past or present use, prescribed by whom, etc.) can be obtained per medication and displayed on the screen of computer 2 (PC, laptop, iPad, etc.) by clicking on the relevant medication. A patient can then, if he wishes, confirm the “add more medication” button when he wants to add a new use of medication. An advantage is that in the medication file shown in figure 6 the information about the use of the medication by the patient is correctly and unambiguously shown and stored in the first database because the relevant information has been created using the G standard.

According to the invention it therefore holds that in a step a. Use is made of a first database of the computer system in which information about the use of his personal medication linked to information about the identity of the patient is stored by a patient. The system uses a second database of the computer system in which standard information of known medication is stored, wherein in step a. The patient uses information from the second database for filling the first database with standard information of a medication.

It has also been found that when the information on the use of the medication by the patient is entered, the computer system generates and displays a list of possible medications on the basis of a keyword entered by the patient into the computer system, after which the patient selects from the list a medication corresponding to the medication he uses, after which the selected information about the medication is linked to the identity of the patient in the first database. When entering a medication used by the patient, the patient may also enter information about the frequency of medication intake, the form of the medication, the strength of the medication, the use of the medication (e.g., the period of taking the medicine), the origin of the medicine, the brand of the medicine, information about the shelf life of the medicine (for example not to use after January 1, 2015), and / or an identity of a person such as a doctor or pharmacist, healthcare institution, pharmacy and / or hospital that has prescribed and / or delivered the medication.

The computer system in this example is arranged such that it generates a warning for the patient when after entering new information about the use of a medication in step a. The first database shows that the new information does not coincide with the information from the first database on the use of a medication that the patient is already using. In fact, this action is performed by the first 30 server. The first server knows which medications are already being used by the patient 28 and, for example, consults the second server to see if the new medication to be introduced may cause a problem (a problem such as contraindication) with the medications already being used by the patient. The information about the non-convergence of the use of different medications can thus be obtained by the first server, for example, from the second database of the second server.

In the foregoing it has been assumed that the patient already has access to the first database. For example, the initiative for storing patient information in the first database and providing access to the first database to the patient may lie with a first entity. Preferably, it then holds that the first database in a step c. is initially filled with information from the patient by a first entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution after which the first entity provides access to the patient's information in the first database. The first entity approaches the patient, for example via a letter, e-mail or personal conversation and asks if the patient is interested in gaining access to his information in the first database. If the patient indicates interest in this, the first entity provides the patient with access to his information in the first database (for example by providing an access code to access the first database via the internet. From that moment on, the patient can access the access the first database to consult it and / or to enter information about its use of medicines as discussed above.

Providing access can occur when the patient has indicated that he is interested in this, for example by means of a letter, e-mail or in a personal conversation with the first entity. If the patient is not interested, the first entity can use the first database itself and no access is provided to the patient. In particular, the first database after it has been created in a step d.

29 filled by information about the identity of the patient by the first entity. Then in a step e. the first entity stores information about the use of the personal medication, linked to information about the identity of the patient, in the first database.

It is noted that the first entity can also enter other information if desired. Use can for instance be made here of a fill-in screen with a free fill-in field where this other information can be entered. This can be done by typing the first entity in the field. Also, files (word documents, scans, photos, etc.) containing this other information can be dragged into the free field by the first entity so that these files are stored in the first database. This other information is again stored, linked to the identity of the patient. The other information about the patient may include, for example, the results of examinations performed by the first entity on the patient, such as X-rays, MRI scans, CT scans, and lab results. If the first entity has given the patient access to the first database, the patient can then view the database from that moment. When the patient does not have access to the first database, when the patient is at the first entity, the patient can view the first database and the first entity can use the database for own use only. The first entity can also view the database in the presence of the patient, if necessary, and supplement and modify it in consultation with the patient or only view it. When the patient indicates to use certain medicines or to stop using them, the first database can for instance be adapted accordingly,

In particular, in step e. the first entity uses the standard information from the second database to fill the first database. Preferably, step e.

30 information about the use of a medication by the patient according to standard information from the second database about the medication to be entered, is stored in the first database. Preferably, this applies in step e. upon entering the information about the use of the medication by the first entity, the computer system generates and displays a list of information about possible medications to the first entity on the basis of a keyword entered by the first entity into the computer system, after which the first entity selects a medication from the list corresponding to the medication he uses after which the selected information about the medication linked to the patient's identity is stored in the first database in the form of standard information. In particular, it further holds that the first entity in step e. of a medication that the patient uses or has used also enters information about the frequency of taking a medication from the medication, the dosage form of the medication, the strength of the medication, the use of the medication (e.g. the period of intake of the medicine), the origin of the medicine (supplier), the brand of the medicine, information about a shelf 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 medication.

The patient may, if desired, decide to grant access to the first database to a second entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution, in which in particular the patient also indicates to which information the patient has access provided to the relevant second entity. In particular, after providing the second entity with 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 may be given the opportunity to request information from the first database. obtain or consult a database, for example by downloading, printing or reading from a display.

31

The patient can therefore, if he so wishes, inform the first server via his computer 2 that he provides access to the part of the first database that relates to his person to, for example, a second entity such as a doctor and / or a pharmacy and / or a pharmacist and / or hospital and / or health care institution. This can be realized in a known manner in that the user protects his information with a password which he for example gives to the doctor in advance. The general practitioner can then access the first server 4 via his computer 16 (for example via the internet), enter the identity of the patient, as well as the relevant password, whereafter the medication file of the relevant patient becomes accessible for the computer 16. The password in question can, for example, provide a doctor with one-time access to information from the patient, provide access to information from the patient for a specific time or provide access to information from the patient for an indefinite period of time.

The patient can also indicate per entity which information he provides access to. He may, for example, decide to give a certain second entity access only to information about medication from a certain period, for example used medication from the period 1990-2000. After this, for example, the GP in question can be offered the opportunity to download the relevant information from the database. However, it is also possible for the patient to ensure that information from the first database relating to his personal medication file is sent to the computer 16 of, for example, the general practitioner via an e-mail or an XML message, etc. The second identity can also be provided by the patient to enter information about the patient and linked to the identity of the patient at the first database. This information may include the same information that can be entered into the first database by the patient and / or the first entity.

32

It is also possible that the patient requests an identity (the first entity, the second entity and / or a third entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution) for information about medication from the first database linked to the identity of the patient. This can be done in various ways. The patient can, for example, enter the relevant request at the first server. If information from, for example, the general practitioner is known at the first server in the first database, the first server can then forward the relevant request via, for example, the internet to the computer 14 of the general practitioner. The doctor can then, for example, download the information from the patient to check it and, if desired, contact the patient for consultation. The patient can also send this request directly to the computer 14 of the general practitioner, together with, for example, a password, so that the general practitioner himself, when it suits him, can approach the first server for the information of the personal medication file of the patient concerned. retrieve using the relevant password. After this, the general practitioner can assess this information and, for example, telephone consultation can take place between the general practitioner and the patient.

Other ways of providing access are also conceivable. Suppose a general practitioner wishes to use his computer 16 to gain access to information of the relevant patient that is stored in the first database. If the patient has not previously given access to the doctor, access to the doctor will be refused. The patient can then also provide the doctor on site with a code with which the doctor is given one-off permission to consult data in the first database of the first patient. Also, when the patient is with him with his computer 16, the doctor may request the first database to send an SMS with an access code to a patient's mobile phone. It applies here that the mobile telephone number of the patient is known to the first database. After receiving the SMS, the patient can inform the doctor of the access code, after which the doctor can supply this access code with his computer 16 to the first database. The first database then provides access to the computer 16 when the received code corresponds to the code of the SMS. The patient himself can also gain access via a computer, for example via the computer 16 of the physician with whom he is present, to his data stored about him, including account data, by entering a password. Upon access to his patient account, he can, for example, enter that the doctor in question has access to certain or all of his data stored in the first database. This access can again be one-off, for a definite period of time or indefinitely.

In which way a patient has provided access to a general practitioner, or more generally to a second entity, the patient remains in control of the information stored about him in the first database. In this example, this is apparent from the following: The second entity is only given access to information from the patient stored in the first database when the patient has given access to the second identity. For example, the patient may provide the second entity with permanent access, allow access for a limited time, or provide access to information from the patient stored in the first database. In exceptional circumstances, the second entity can still gain access to information from the patient in the first database, even when the second entity has not received permission from the patient for this. Such a special circumstance may occur, for example, when the patient is in danger to life and unable to provide access to the second entity. In that case, however, the fact that the second entity has consulted information about the patient in the first database is preferably stored in, for example, the first database 30 so that it can later be verified that the second entity has not misused the access obtained. The patient can also revoke the access he has provided to the second entity. The patient is and remains the master of the information stored about him in the first database.

In this example, the information about the identity of the patient is also stored in the first database. The information about the patient's identity may include, in addition to his name, place of residence, also age, gender, blood type 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 in such a way that this information is associated with the information about the use of medication of the patient concerned.

The patient can also print out a standard letter for a general practitioner or for a pharmacist on the basis of information from the first database about the use of medication and about the use of medication in the past. To this end, he confirms the "print" tab, after which the screen according to Figure 18 is generated on the computer 2 by the first server. This shows that the patient can choose to print information for himself, for a general practitioner, or for a pharmacist. When the patient confirms the button for "for myself", an input screen is shown according to Figure 19. Here the patient can choose from what he wants to print: "list of current medication", "list of medication that you no longer need used "," list of pharmacies you go to ", and" list of doctors you go to. "

25 It can also be checked that everything must be printed. In this example it is chosen that everything must be printed. Then the button "make the printout" is activated. A print-out is then made according to figure 20. More generally, it therefore holds that the patient obtains, can obtain or access information from the first database, for example by downloading, printing or reading from a display. This information then relates to information from the patient, not to information from other patients in the first database.

When the input screen according to figure 18 is chosen for printing information from a general practitioner, the input screen 5 according to figure 21 appears. Here too, there is again a choice from what can be printed, such as: "your name information", "list of current medication "," List of medications that you no longer use "," list of pharmacies where you go "," list of doctors where you go ". It can also be checked that everything is printed. In addition, the preamble of the letter 10 can also be drawn up such as in this example "dear general practitioner". After this, a few things can be confirmed by pressing the “make the printout” button. After this, on a printer connected to the computer 2, a letter is printed according to figure 22. In this letter it is clear that the only medicine that is still used concerns Ibuprofen; the other medications 15 are medications from the past. It is also indicated who the doctor and the pharmacy is. On the other hand, when a letter for a pharmacy is chosen in figure 18, the screen according to figure 23 appears. Here too, the same choices for printing as in relation to the doctor are discussed. In this example, it is again chosen to turn everything out. Subsequently, when the "print out" button is activated, a letter according to Figure 24 is printed addressed to the pharmacist.

Such variants are each understood to fall within the invention. It has already been indicated in the foregoing how the first entity 25 can store the first data of the patient in the first database, how the first entity can provide access to the first database for accessing data from the patient that are stored in the first database, how the patient can then enter to the computer system to what extent (particular period, indefinite period or one-off) the first entity retains access to data of the 36 patient stored in the first database and possibly how the patient can, if desired, provide the second entity with access to the patient's data stored in the first database, the patient possibly subsequently entering the computer system to what extent (second, definite or indefinite period) the second entity has access to patient data stored in the first database.

The patient can of course also go to step c. initially fill the first database with information from the patient. In that case, the patient 10 can, for example via the Internet, go to a web page of the first database. Here the patient can indicate that he wishes to store his data in the first database. This may, for example, involve the patient in a step d. fills the first database with information about the identity of the patient. The patient can then also go to step e. store information about the use of his personal medication linked to the information about his identity in the first database. The patient can then also enter a password that protects his data. When filling the first database, the patient again uses the standard information from the second database as discussed above. After the patient has been logged out, he can return to the relevant website via the Internet. If he wishes to access his data, he will first have to enter the password previously given by himself.

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

How this all works will be shown below.

Figure 25 shows the initial screen that a patient sees when he and his computer 2 go to the website called "meddossier.nl" which website can provide access to the first 37 database. The patient has the option here to confirm the "Log in" button if the patient has previously gained access to his data stored in the first database.

After the "Login" button has been confirmed, a screen appears (see figure 5 26A) in which the patient must, for example, enter his name and address and / or a username and a password (in the password field). From this screen the patient can gain access to his data stored in the first database as discussed with reference to Figs. 2-24 10. If, for example, the 'medication' button is activated in the screen of Fig. 27A the screen of figure 2 appears.

In the screen of Figure 25, the patient can also confirm the "enter this code" button if the patient wants to gain access to his data that was first entered by a first entity such as a doctor. in a text passage that, for example, is colored differently from the rest of the text (see for example “enter this code” in Figure 25.) In that case, the first entity has created an account for the patient in the first database. received an access code from the first entity to gain access to its data in the first database, which will be discussed below with reference to Figures 41-43.

However, because in this case the patient 14 wants to log in for the first time to the first database (create an account himself), the patient confirms the “Log in” button in the screen of figure 25 and thus arrives in the screen in which he is Name and address details and / or a username can be entered (see figure 26 B). The patient is also asked on this screen to enter a password (in the password field). In this example, the password must be entered twice. After the password has been entered, the patient confirms the password by pressing the 30 “Log in” button. After this, the patient can navigate via the screen of figure 38 to the screen of figure 26A to log in to his newly created account. After logging in, the screen according to figure 27A appears as discussed above. After this the patient can add or read medication in the system by confirming the button “medication” in the screen of figure 27A, after which he is shown a screen as shown in figure 2. The addition of medication is then completely analogous as discussed above to the hand of figures 2-17. The patient can then also perform the operations described above with reference to Figures 18-24.

The patient can also manage permissions by confirming the "permissions" button in the screen of Fig. 27A, after which the screen according to Fig. 28 appears as will be discussed below.

When the patient comes to the website the next time, he can confirm the 'Log in' button in the screen according to figure 25, after which he can enter his name and address and / or username and password in the screen of figure 26A in order to Figure 27A to gain access to its data in the first database. After the patient has entered his name and address data (in the field password of the screen of Figure 26A) into the system, the patient can add medications to the system by confirming the “medication” button in the screen of Figure 27A and then a screen is shown as shown in figure 2. The addition of medication is then completely analogous as discussed above with reference to figures 2-17. The patient can then also perform the operations described above with reference to Figures 18-24.

Once a patient has stored his data in the first database, he can also grant authorizations to third parties for consulting his data. To this end, the patient confirms the "permissions" button in the screen of Figure 27A. The patient is then shown a screen as shown in Figure 28. In the screen of Figure 28, a list of permissions is given. In this case the screen is blank, which means that no permissions have yet been given. The patient can now add permissions by “adding permissions”, for example by using his mouse. After confirming "add permissions" 5, the screen of figure 29 appears. This shows that the patient can choose between "authorize someone else" or "have obtained it from someone else". In this case, the patient confirms "authorize someone else" and the screen of Figure 30 appears. In the screen of figure 30, the default indicates that the authorization starts and ends on the current date, namely April 22, 2011. However, the patient changes the default values so that the authorization expires on April 30, 2011.

It was also stated by default that the authorized person was only allowed to read along and not make any changes. The patient changes this to "change and read are allowed". All this is shown in figure 31. After the patient has made the relevant changes, he confirms the button "create authorization code". Then the screen appears according to figure 32. The computer system is arranged such that it generates an authorization code which is indicated in figure 32 as "1674.2533.1807.7562.5376". The patient is intended to give this authorization code to, for example, a second entity such as a pharmacy that he wants to authorize to gain access to his data. When the patient then confirms the "permissions overview" button, the computer system generates the screen of Figure 33 (similar to the screen of Figure 28, but with updated content). Here is indicated which authorization code was issued, when it was issued, and until when it is valid. It is also indicated that the code gives the right to read and edit. It also appears that the relevant authorization code has not yet been used by the second identity. Furthermore, it is possible that the patient withdraws the relevant authorization code 30 by pressing the "delete" button. The patient can also, if he so wishes, grant an authorization to other entities by pressing the "add more 40 permissions" button, after which again figures 30-33 are traversed as described above.

When the second entity has received the authorization code from the patient 5, the second entity, like the patient, can access the first database via the Internet by going to the webpage of “meddossier.nl”. The second entity can access the first database via its own computer which for simplicity's sake is not shown in figure 1, but where the situation is comparable to that of the computer 2 and the computer 16. The second entity can only access the first database when the second entity itself has already stored at least its name, address, and place of residence data in the first database. To this end, the second entity, just like the patient at the time, created his own account and created a password and thus entered it. The second entity therefore opens its data by confirming the "Log in" button in the screen as shown in Figure 25, after which it can enter its name and address and / or username and password in the screen of Figure 26A. the screen according to figure 27 C. In this screen the second entity can press the button "authorizations" after which it is shown the screen according to figure 34 (corresponds to the screen according to figures 28 and 33, but now for the second entity). the second entity can press “add permissions”, after which the screen of figure 35 is shown to the second entity In the screen according to figure 35 the second entity can confirm the button “obtained from someone else.” The screen then appears on his computer according to figure 36. In this screen the second entity can enter the authorization code “1674.2533.1807.7562.5376.” The second entity “the pharmacist Cees Schaap” can then confirm the "activate authorization code" button.

Then the screen according to figure 37 appears on the computer of the second 41 entity. This shows that the second entity "Cees Schaap" has gained access to the file of the patient "Sven Berkvens-Matthijsse". When the second entity has gained access to the patient's file, he can then consult and / or change the contents of this file, as thus discussed with reference to Figures 2-17. It is also possible to perform the operations discussed with reference to Figures 18-24.

Then, when the second entity presses the "permissions overview" button, the screen shown in Figure 38A appears. This shows 10 from whom the second entity (Cees Schaap) has obtained authorizations (from “Sven Berkvens - Matthijsse), what the status of the authorization is, namely“ reading and editing ”, and that the authorization is valid from 22-30 April. When the second entity actually wants to view and change the medication file of Sven Berkvens - Matthijsse (the patient), he must now press the “log in” button in the screen of figure 38. The patient's medication file is then automatically logged in, after which data from the patient can be edited and read via the screen of figure 38B as has already been explained with reference to figures 2-24. This can be done, for example, by confirming the "medication" button. For example, if the second entity would not have given permission to edit data and still try to do so, it will be shown a page according to Figure 39. This page clearly shows that the operation is not allowed.

In the above example, it is assumed that the patient himself takes his medication file in a first step c., D. and e. has set up. However, it is also possible that this is done by, for example, a first entity such as a doctor with the patient visiting. The doctor has already gained access via his computer to the first database via the website “meddossier.nl” from the home screen as shown in figure 25. When logging in, the first entity then had the screen according to figure 26A

42 used as described above for the patient and the second entity. After this, the screen according to Figure 27B appears because the system knows that the first entity is a healthcare provider. In this screen of Figure 27B, the first entity confirms the "Create New Patient Account 5" button, after which the system displays a pop-up screen as shown in Figure 40 on the physician's computer. At this input screen, the first entity enters a name, address and place of residence of the patient. The system generates a one-time access code in this example. This access code, which is generated by the system, is read by the first entity of the screen and given to the patient. Of course, this access code can also be made known to the patient in another way, for example via a text message or e-mail. Also, as discussed with reference to Figures 2-24, the first entity can now enter patient data into the database. It holds that the first entity is automatically authorized to the data that is now stored in the first database of the patient.

For example, the patient then goes home and goes via his computer to the website of "meddossier.nl". From the initial screen of Figure 25, he confirms the "enter this code" button. The system 20 then generates the screen according to Figure 41. Here the patient can enter the access code that he has received from the first entity. The patient then enters the access code "1111.2222.3333.4444.5555" (Figure 42) and confirms the activate button. Then the screen appears according to figure 43. Here the patient can enter a username (also referred to as name and address data) and twice the same password. After this the patient confirms the activate button. From that moment on, the patient can log in via the screen according to figure 25, figure 26A and figure 27A on the basis of his username and password. By pressing the “permissions” button, a screen like the one shown in figure 28 will appear showing which permissions have been given. In this case 43, it would then appear that the first entity operating in steps c., D. and e. has initially saved the patient's data in the first database, is automatically authorized. There are two options here. The moment the first entity steps c., D. and e. He can also indicate, in consultation with the patient, the nature of his automatic authorization such as read, read and write only, or full access or access to part of the information of the patient. It can also be indicated whether the authorization is for a definite or indefinite period. If nothing is stated, the authorization 10 is assumed to be complete and indefinitely. When the patient is logged into the computer system to consult his data stored in the first database, when he presses the "permissions" button, he can see that the first entity has access to read and edit and, for example, access indefinitely. If he wishes, he can remove or adjust the authorization, for example by changing the read and edit access to read only and / or for example by changing the indefinite access to a fixed-time access. He can do this by confirming the relevant fields with a mouse click.

According to a special embodiment, the computer system of Fig. 1 is expanded 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 can be set up at a place where medicines are sold, such as a shop, drugstore Gas station and the like. The cash register system 18 is connected, for example via an internet connection 22, to the first server 4 of the computer system 1.

It has been explained above that the first database can be filled by the patient himself, by the first entity and / or the second entity. After this, a patient, a first entity, a second entity and / or 44 another person and / or institution that can fill the first database with information about the use of a patient's personal medication, linked to information about the patient's identity are referred to as an input entity. An import entity may be the patient himself, a doctor, another person, or an institution such as a healthcare institution or hospital. The operation of the device in this example is as follows.

For example, a customer buys a plurality of medicines in a store where the cash register system 18 is located. With the cash register system, the medicines to be purchased are assessed in the usual way. This can be done, for example, by reading barcodes from the packages of the medicines. The customer can then pay for the medication so that the customer buys the medication. In this example, the cash register system is provided with information about possible medicines to be purchased. By scanning the bar codes, for example, this information can be retrieved in the cash register system to determine what the medication costs. All this is done in a step xl. However, the cash register system is arranged in such a way that it also automatically transmits information via the connection 22 to the computer system about the medication used in the cash register system. This example involves a multiple of 20 drugs, but it can also be a single drug. The automatic transmission of information about medications struck at the cash register system is thus carried out in a step x2. The computer system 1, more particularly the server 4, is arranged in this example such that it performs a step x3.1. In step x3.1, in response to the information received in step x2, the first server 4 generates a code associated with the information received from the cash register system about the excited plurality of drugs. It therefore holds that a single code is associated with the multiple of drugs that have been struck at the checkout. The code and associated information 30 about the purchased drugs are thus present in the computer system for later use. The computer system, in this example the first server, then in a step x3.2 supplies the generated code to the cash register system 18. In a step x4, the cash register system will provide the generated code to the customer in response to the received code. In this example, this occurs because the cash register system prints the code in a step x4 on a sales receipt (see Figure 44) that is printed when purchasing the plurality of medicines. The buyer takes the medicines along with the receipt. For example, the buyer can hand over the medication along with the code to a first patient who is already registered in the first database. It is also possible that the buyer himself is the user of the medication but is not yet registered in the database. Then the buyer can register himself in the database as already explained above. Whatever the case, we now assume that the first patient to use the medication is registered in the database at some point.

When the first patient is registered in the database, access can then be gained in a usual manner, for example by means of a password by the patient or his authorized person, such as a user who has the identity of a patient together with a password. the data of the first patient. This can be done, for example, with the aid of the home computer 2 as discussed above with reference to the initial screen of Figure 25.

The screen according to figure 2 can then be displayed after logging in. As can be seen, the screen according to Figure 2 also comprises a button 50 with the indication "purchased". When this button is actuated, a fill-in screen according to Figure 45 is shown. At this input screen you will be asked to enter the code. A receipt that was printed with the cash register system after the plurality of medicines was purchased is shown in Figure 44. On this receipt the code y5x2 can be read. This code can then be entered in the input screen of figure 45. Thus, a step x5 is performed. In response to entering the code, 46 is then shown on the screen of computer 2. Figure 46 shows in this example all medications associated with the relevant code. This concerns two drugs, namely dexubuprofen 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 the input entity of step x5 with information about the plurality of drugs struck at the cash register system. Thus, since information is available in the computer system about the purchased drugs associated with the code, information about the purchased drugs can be supplied by the computer system to the input entity based on the code. This can be exactly the information associated with the relevant code or, for example, information about the medicines purchased in a different format, for example supplemented with other information about medicines concerned that is available in the computer system, such as information in the second database. The input entity can then, in a step x7, by confirming a "choose" button associated with the particular drug, select a drug that it will use. The computer system will then store the selected information about the drug, linked to the identity of the first patient, in the first database. For example, if the drug dexubuprofen is selected, it will be removed from the list because this drug will now actually be used and no longer belongs in a list that actually relates to purchased drugs. Because in order to gain access to the computer system, the input entity also had to enter the identity of the first patient together with a password, it holds that on balance a step x7 is performed according to which the input entity, in this example the input entity of step x6, selects an identity of the first patient at the computer system (a consequence of gaining access to the computer system by entering the identity of a patient 47 together with the relevant password) and the at least one medication if it will be taken by the first patient be used after which the computer system stores the selected information about the drug, linked to the identity of the first patient, in the first database.

It therefore follows that the actions taken in step 7 need not be performed simultaneously. This selecting the identity of the first patient can be performed by accessing the computer system by entering the identity of the patient and the associated password (logging in) while selecting the drug that will be used on said list on a a later moment is performed once access to the computer system has been obtained (a further embodiment will be explained later in which the sub-steps of step x7 are performed, at least substantially, simultaneously). Before the selected medication is stored as a medication used by the first patient, as described above, the input of the information can still be tested on the basis of the information from the second database 12. For example, after selection of the dexubuprofen of Figure 46, Figures 5 and 6 are still run through. Such variants fall within the scope of the invention.

It may happen that the drugs associated with the code will not only be used by the first patient but also by the second patient. It may also be that a first subset of the medications associated with the code are used by the first patient and that a second subset of the medications associated with the code are used by the second patient. In these cases, the same process can be followed for the second patient, completely as described for the first patient. Thus, when the second patient is registered in the database in a conventional manner, for example on the basis of a password of the second patient by the second patient or by his authorized person, such as a user who shares the identity of the second patient together with a password access to the data of the second patient. This can be done, for example, with the help of the home computer 2 as discussed above with reference to the home screen of Figure 25.

The screen according to figure 2 can then be displayed after logging in. As can be seen, the screen according to Figure 2 also comprises a button 50 with the indication "purchased". When this button is actuated, an input screen according to Figure 45 is shown. At this input screen you will be asked to enter the code. This is then again the code of the receipt 10 which is shown in figure 44. On this receipt the code y5x2 can be read. This code can then be entered in the entry screen of Figure 45. Thus, a step x5 is performed. In response to entering the code, figure 46 is then shown on the screen of computer 2. Figure 46 shows in this example all medications that are associated with the relevant code. This concerns two drugs, namely dexubuprofen and ibuprofen. Thus, a step x6 is performed according to which the computer system, on the basis of the code entered at the computer system in step x5, provides the input entity of step x5 with information about the multiple of drugs struck at the cash register system. The input entity can then, in a step x7, by confirming a "choose" button associated with the particular drug, select a drug that it will use. The computer system will then store the selected information about the drug linked to the identity of the second patient in the first database. For example, if the drug dexubuprofen is selected, it will be removed from the list because this drug will now actually be used and no longer belongs in a list that actually relates to purchased drugs. Because in order to gain access to the computer system, the input entity also had to enter the identity of the second patient together with a password, it holds that on balance 49 a step x7 is performed according to which the input entity, in this example the input entity of step x6, selects an identity of the second patient at the computer system (a consequence of gaining access to the computer system by entering the identity of a patient together with the relevant password) and the at least one medication if it will be taken by the second patient after which the computer system stores the selected information about the drug linked to the identity of the second patient in the first database.

It is further noted that in this example the code for the plurality of medicines is generated by the computer system, in particular the first server 4. However, it is also possible that the cash register system generates the relevant code. In that case, in step x3.1, a code is generated by the cash register system that is associated with the information about the excited multiple of drugs. Subsequently, in a step x3.2, the cash register system supplies the generated code to the computer system. In step x2, as stated, the cash register system automatically passes on information about the plurality of excited medications to the computer system. The information about the plurality of excited drugs is processed in the computer system associated with the received code, more particularly stored. The cash register system also issues the code to the customer, for example by printing it on the receipt. After this a situation has arisen in which the system can continue to work as has already been discussed above with reference to steps x5, x6 and x7. It will be clear that the device and method as discussed above can also be carried out entirely analogously when the plurality of medicines comprises only one medicine. In that case, the list shown will only comprise one drug which can then be selected by the input entity when the drug in question will be used, whereafter the drug in question associated with the patient's identity is stored in the first database.

As stated, in the embodiment outlined above, step 7 comprises two sub-steps which were in fact performed at different moments in the process. A variant will be described below in which this is precisely not the case. In this variant, the steps x1 to x4 are entirely analogous to one of the varaints as described above. After this, the registration system can be used as follows. With the aid of his home computer 2, the customer makes contact with the computer system 1. With this, the customer can use his computer 2 to select a web page of the computer system 1 as shown, for example, in figure 47. At an input field 20, the customer can enter the code which the receipt is. In this case, step x5 is then in fact performed. On the basis of the code, a new web page 15 is displayed by the computer system on the computer 2 as shown in Figure 48. This page lists the drugs that are associated with the entered code. This example involves two drugs, namely dexubuprofen and ibuprofen. Thus, on the basis of Fig. 48, step x6 is carried out according to which the computer system, on the basis of the code entered at step x5 at the computer system, provides the input entity of step x5 with information on the plurality of medications struck at the cash register system. Figure 48 further shows two activation fields 22 and 24, respectively. By activating the field 22 with, for example, a mouse click, the drug dexubuprofen is selected. By activating 25 of button 24, the drug ibuprofen is selected in this example. Two further input fields 26 and 28 are also shown. Every medicine has its own input field. The input entity can enter the identity of a first patient at input field 26 for whom dexubuprofen has been purchased. At the input field 28 the identity of a possibly different patient or the same patient can be entered for whom ibuprofen has been purchased. When 51, for example, the identity of a first patient is entered in field 26, after which field 22 is subsequently confirmed, this has as a consequence that in the computer system the identity of the first patient and at least one medicine, in this example one medicine, is selected which by the first patient in question will be used. The computer system will then store the selected information about the drug linked to the identity of the first patient in the first database. After this, the identity of another patient can be entered in the field 26 if desired. If the field 22 is then again energized with, for example, a mouse click, this has as a consequence that in the computer system the identity of the second patient and at least one medicine, in this example again the medicine dexubuprofen, is selected which will be selected by the relevant second patient. used. The computer system will then store the selected information about the drug, linked to the identity of the second patient, in the first database. When for a certain medicine from the list no more or no patients have to be selected who will use the medicine (for example because a wrong medicine has been purchased) the medicine can be removed from the list, for example by double clicking on the relevant field 22 24 of the drug to be removed.

When the first patient and / or the second patient is registered in the database, it can then be done in the usual manner, for example on the basis of a password by the first patients / or second patient or by his authorized person, such as a user who identifies a patient. Possesses, together with a password, access to the data of the first patient or second patient. This can be done, for example, for the first patient using the home computer 2 as discussed above with reference to the initial screen of Figure 25.

If, for example, the first patient subsequently goes to the website 30 of the cumputer system 1, in the example referred to above as 52 "meddossier.nl", he sees, as discussed, the initial screen according to figure 25. As discussed, he can then go to the screen of figure 2 navigate. In this screen the first patient will also see the medication entered by the customer on the basis of the code. Subsequently, the first patient can indicate in the usual manner when he will use this medicine as discussed above. He can also indicate that he will not use the medicine, for example when a wrong medicine has been purchased.

Completely analogously, the second can also go to the website of computer system 1, in the example referred to above as "meddossier.nl" and, as discussed, see the initial screen according to figure 25. As discussed, he can then navigate to the screen of Figure 2. In this screen the second patient will also see the medication entered by the customer on the basis of the code. Subsequently, the second patient can indicate in the usual manner when he will use this medicine, as discussed above. He can also indicate that he will not use the medicine, for example when a wrong medicine has been purchased.

It is noted that the sub-steps of step x7 are now, at least substantially, carried out simultaneously; after all, the selection of the medicine, in this case dexubuprofen, as well as the identity of the first patient who will use the medicine in question, is performed more or less simultaneously on the basis of the screen according to Figure 48.

It is also noted that it is possible in this way to select a different identity for another patient for ibuprofen or to select the identity of the first patient and / or the second patient. Thus, it is possible that a plurality of drugs are associated with a single code, after which it is then possible for each drug of this plurality of drugs to be selected for use for a particular individual patient with different drugs for 53 different from each other and / or the same patients can be selected. Hereby it is advantageous if the screens of figures 47 and 48 can be accessed via the same website as the initial screen 25 as discussed above. For example, it is also possible that a separate button is also provided in the initial screen 25 which, after energization, yields the screen 47. If, on the other hand, the code is not entered on the basis of Fig. 47, but is logged in to the screen of Fig. 25 by an input entity which, for example, concerns the patient himself, then as discussed above, after logging in to a screen according to Fig. wherein the "purchased" button can then be selected by the relevant input entity, after which the screen of figure 45 is obtained. With the screen according to Fig. 45, the said code can then also be entered. However, it is now the case that, as explained, the screen according to Figure 46 is then shown, but it is now the case that for each of the drugs of the plurality of drugs associated with the code, it can only be entered in the database be stored as being a drug that is linked to the identity of the patient who is logged into the screen of Figure 25. In this example, then, it applies that when the code is entered by a user who is logged in as or on behalf of a particular patient, the relevant drugs linked to the identity of this patient can be stored in the first database when they are selected for use. However, if the code is entered at the webpage according to figures 47 and 48, the buyer, who may also be the patient, or a representative of the patient, or another person or institution, can select a patient's identity per medicine . For each variant as described above, it applies that the relevant code can be generated by both the cash register system and the computer system. Of course, the registration system can also be provided with a plurality of cash register systems that work as described for the 54 cash register system 18. In this example, such a second cash register system 24 is shown in Figure 1.

The invention is in no way limited to the embodiments outlined above. The information about the medicine provided by the cash register system to the computer system in step x2 is not limited to a specific form. The only requirement is that on the basis of this information the computer system in step x6 can provide information about the at least one purchased medicine (or the plurality of purchased medicines) to the input entity on the basis of which the input entity the at least one medicine (or medicines) of the plurality of medications) in step x7 if this (or this) will (or will) be used by the patient. The information sent to the computer system by the cash register system in step x2 may thus include the name of the purchased at least one drug (or the names of drugs from a plurality of drugs if a plurality of drugs are purchased). However, the information may also include an article code that relates to the purchased medicine, on the basis of which the computer system in step x6 can provide information about the purchased at least one medicine to the input unit on the basis of which the input unit in step x7 can select the medicine if it is used. In that case, the computer system will be provided with information about possible article codes and associated information about medicines. In step x6, then, the article code itself is not provided to the input entity, but instead information about the drug in question associated with it. The information about a purchased medicine that is supplied to the computer system in step x2 does not therefore have to be exactly the same shape as the information about the relevant purchased medicine that is provided to the input entity in step x6. It is of course about the one and the same medicine purchased. However, the information supplied by the cash register system to the 55 computer system in step x2 may also include a plurality of article codes that each relate to a purchased medicine if a plurality of medicines are purchased and on the basis of which the computer system provides information about the can provide a plurality of purchased drugs to the input unit on the basis of which the input unit in step x7 can select at least one drug if used, or select multiple drugs if multiple drugs are used. For example, an item code can be a number or a combination of characters and numbers. The code associated with the at least one drug that has been purchased or the plurality of drugs that have been purchased may also be a number or a combination of characters and numbers. This code preferably has the property that it can easily be entered in step x5 by an input entity. The code can therefore consist of, for example, a maximum of 10 digits and characters. As stated, the code is associated with information about the at least one purchased medicine or the plurality of purchased medicines, whereby by introducing this single code into the computer system by the computer system on the basis of this code the information about the at least one purchased medicine or the a plurality of purchased drugs can be retrieved from the computer system after which information about the at least one purchased drug or the plurality of purchased drugs can be supplied to the input unit in step x6. The code is therefore unique within the method and the registration system and is in fact an identification code associated with the at least one purchased drug. For example, the code generated in step x3 may remain valid for another year after it has been entered in step x5, that is, the code and the associated at least one purchased drug remain available (remain stored) in the computer system. An advantage is that the code can be entered again in step x5 in order to be able to perform step x6 and to be able to link in step x7 the 56 concerning at least one purchased medicine with yet another patient who is also going to have the same purchased medicine (such as another member of the same family). After the end of the year in question, the code in question and the information associated with it about the at least one medicine purchased can, for example, be deleted from the computer system. The relevant deleted code can then be regenerated in step x3 to be linked 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 inform all cash register systems that form part of the registration system that the relevant code has been deleted and can therefore be reused 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 (after all, the codes generated in step 15 x2 and the associated at least one drug purchased for being able to perform step x6 are available in the computer system ) so that the computer system itself knows which codes are already in use and can generate a code that is still free to be associated with at least one purchased drug.

Further variants are also possible. For example, when a patient enters a new use of a medication while it is inconsistent with medication already entered, for example, because two medications do not coincide with each other and can lead to dangerous reactions in a patient, the computer system can be set up to automatically sends a warning to the pharmacist or general practitioner of the patient if the first database stores who the general practitioner and / or who the pharmacy is of the patient concerned. If more than one general practitioner and / or more than one pharmacist is linked to the identity of the patient concerned, an e-mail can be automatically sent to each of the pharmacists and / or each of the 30 general practitioners about the fact 57 that the patient apparently uses, or is about to use, medication that is inconsistent with medication that he is currently using. Furthermore, the first server and the second server can be replaced by a single server where the first database and the second database are stored. It is also 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, after which the manager enters the medication into the first database in which the patient has first used the second database for obtaining standard information about the medication to be introduced and / or wherein the manager uses the second database for entering the first medication at the first database with standard information about the medication. The network administrator may, for example, be the first entity. A first entity, and / or the second entity may, for example, access the first server and / or the second server via the professional network E-care. The patient approaches the first server via his computer 2 then via the public internet. Such variants are each understood to fall within the scope of the invention.

Claims (39)

Method for maintaining a personal medication file with the aid of a computer system, comprising: a. Using a first database of the computer system in which information about the use of personal medication is provided by an input entity such as a patient, another person or institution of the patient coupled to information about the identity of the patient is stored in the first database, characterized in that the method further comprises the following steps: x1: charging at least one medicine that is purchased by a customer at a cash register system wherein the cash register system is provided with information about possible medicines to be purchased; x2: the automatic transfer of information by the cash register system on the computer system to the at least one medication struck by the cash register system; X3: generating a code associated with the information about the excited at least one drug; x4 providing the generated code to the customer by the cash register system ;. x5: entering the code received from the cash register system in step x4 into the computer system by an input entity such as the customer or patient; x6: providing information by the computer system on the input of the computer system on the basis of the code entered into the computer system in step x5, in particular the input entity of step x5, about the at least one medicine struck at the cash register system; x7: selecting, by an input entity, in particular the input entity of step x6, at the computer system, an identity of at least one patient and the at least one drug if it will be used by the at least one patient, after which the computer system displays the selected information about the stores medication linked to the selected identity of the at least one patient in the first database; wherein step x1 comprises charging a plurality of drugs in the cash register system, step 5 x2 automatically transmits information from the cash register system about the plurality of drugs stored in the cash register system to the computer system, step x3 generating the includes code associated with the information about the excited multiple of drugs, step x6 includes providing information about the multiple of drugs excited at the cash register system on the basis of the code entered into the computer system in step x5 and step x7 selecting an identity of at least one patient and at least one drug from the plurality of drugs if the selected at least one drug is selected by the at least one patient by the input entity, in particular the input entity of step x6 at the computer system will be used after which the computer system will start stores selected information about the at least one drug linked to the selected identity of the at least one patient in the first database 2. Method as claimed in claim 1, characterized in that step x3 comprises the following steps: x3.1: generating by the computer system a code which is associated with the information received in step x2 from the cash register system about the struck at least one drug; x3.2: the computer system supplying the generated code to the cash register system; and that step x4 comprises providing the customer with the code received from the computer system from the cash register system. 30 3. Method as claimed in claim 1, characterized in that step x3 comprises the following steps: x3.1: generating by the cash register system a code which is associated with the information about the excited at least one medicine; x3.2: supplying the generated code to the computer system by the cash register system so that after performing step x3.2 and step x2, the computer system comprises the code and the associated information about the at least one medication struck at the cash register system; 10 and that step x4 comprises providing the customer with the code generated by the cash register system. 4. Method as claimed in claim 1, 2 or 3, characterized in that in step x6 the computer system shows the information about the at least one medicine and in particular a plurality of medicines that are associated with the code to an input entity in a separation list patient. 5. Method as claimed in claim 4, characterized in that in step x7 an input entity such as the patient, the client, a doctor or a healthcare institution, in particular the input entity of step x6, at the computer system indicates that it is in the separate list stored medication is used by the at least one patient whose identity is also selected in step 7, whereafter information on the use by the selected patient at least one patient of the personal medication associated with the at least one medication is stored in the first database and wherein in particular at least one drug that is indicated to be used is removed from the list. 30 Method according to at least one of the preceding claims, characterized in that in step x5 the code is printed by the cash register stone, preferably on the sales receipt for the purchased at least one medication. A method according to at least one of the preceding claims, wherein the method further comprises: b. making use of a second database of the computer system in which standard information of known medication is stored, wherein in step a. the patient uses the standard information from the second database for filling the first database. 8. Method according to claim 7, characterized in that in step a. Information about the use of a medication by the patient is stored in the first database according to standard information from the second database about the medication to be entered. 9. Method as claimed in at least one of the foregoing claims, characterized in that when entering the information about 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 a list of generates and displays information about possible medications to the patient, after which the patient chooses from the list a medication corresponding to the medication he uses, after which the selected information about the medication is linked to the identity of the patient in the form of standard information in the first database is saved. 10. 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 input information about the frequency of intake of the medication, the dosage form 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 about a shelf life of the medication, and / or an identity of a person such as a doctor or pharmacist, care institution, pharmacy and / or hospital who has prescribed the medication. 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 from the patient by a first entity such as a physician and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution after which the first entity, for example when the patient indicates it wants to, provides access to the patient to his information in the first database or that the first database in a step c. is initially filled by the patient 15 with information from the patient. Method according to claim 11, characterized in that the first database in a step d. is filled by the first entity or by the patient with information about the identity of the patient. 20 A method according to claim 11 or 12, characterized in that in a step e. by the first entity or by the patient information about the use of the personal medication and / or other information about the patient such as information about examinations carried out on the patient by, for example, the first entity coupled to information about the identity of the patient in the first database is saved. Method according to at least claims 7 and 13, characterized in that in step e. the first entity or the patient uses the standard information from the second database for filling the first database. 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 doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution wherein in particular the patient also indicates to which information the patient provides access to the relevant second entity. Method according to at least claim 7, characterized in that the second database comprises the G standard, wherein the patient in step a. And / or the first entity in step e. of claim 14 uses the G standard for filling the first database. 17. Method as claimed in at least claim 11, characterized in that the first entity provides the patient with access to access the first database via internet by providing an access code to the patient. 18. Method according to at least claim 15, characterized in that the patient gives 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. Method according to at least claim 11, characterized in that the computer system performs step c. by the first entity, generating and providing an access code to the first entity where the first entity is intended to give this access code to the patient and wherein the patient can access his data in the first database preferably via the internet through the access code to be entered into the computer system and wherein after performing step c. by the first entity 30 the first entity is automatically authorized to access the data of the patient that are in the first database and / or are still being stored, whereby in consultation with the patient when performing step c the first entity can be directly entered into the computer system whether the authorization is for a definite or indefinite period of time and what the nature of the authorization is such as read, read and write only, full access or access to part of the patient's information and / or with the characteristic that initial filling of the database with data of the patient in step c. carried out by the patient. 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 one of the preceding claims, wherein the registration system is adapted to carry out a method according to one of the preceding claims. 15 A registration system comprising a computer system for creating and / or maintaining a personal medication file provided with a first database, wherein the computer system is arranged such that the following step can be performed: 20. by an input entity such as a patient, another person and / or institution, information about the use of personal medication of the patient is linked to information about the identity of the patient is stored in the first database, characterized in that the registration system is further provided with a cash register system, the registration system being arranged around the cash register system to communicate communicatively with the computer system, wherein the registration system is arranged, in use, to be able to perform the following method steps with the aid of the registration system: x1: hitting at least one medication that is purchased by a customer at the cash register system wherein the cash register system is provided with in information about possible medicines to buy; x2: the information provided by the cash register system in an automatic manner about the at least one medication struck at the cash register system to the computer system; x3: generating by the registration system a code associated with the information about the excited at least one drug; 10 x4: providing the generated code to the customer by the cash register system; x5: entering the code received from the cash register system in step x4 into the computer system by an input entity such as the customer or patient; X6: providing information by the computer system on the input system, in particular the input entity of step x5, to the at least one medicine struck by the cash register system on the basis of the code entered at the computer system in step x5 at the computer system; x7: selecting at least one identity of a patient and the at least one medication by an input entity, in particular the input entity of step 20 x6, if it will be used by the at least one patient, after which the computer system will select the selected information store the medication linked to the selected identity of the at least one patient in the first database; Wherein, the registration system is arranged such that, in use, according to step x1, the inducement of a plurality of drugs can be performed at the cash register system, according to step x2, the cash register system automatically informs about the plurality of drugs that have been charged at the cash register system transmits to the computer system, according to step x3 the registration system can generate the code associated with the information about the excited multiple of drugs, according to step x6 automatically on the basis of the code entered into the computer system in step x5 by the computer system can be provided to the input entity of step x5 with information about the plurality of medications struck at the cash register system and according to step x7 it can be identified by at least one patient by an input entity, in particular the input entity of step x6 be selected and at least one medicine from the plurality of drugs can be selected that will be used by the at least one patient 10 after which, in use, the computer system stores the selected information about the at least one drug linked to the patient's selected identity in the first database. 22. Registration system according to claim 21, characterized in that the registration system is arranged such that step x3 comprises steps x3.1 and x3.2, wherein step x3.1 generates the information received by the computer system in response to the information received in step x2 of a code associated with the information received from the cash register system about the excited at least one drug; and step x3.2 comprises supplying the generated code to the cash register system by the computer system; wherein step x5 comprises providing the code received from the computer system to the customer by the cash register system. A registration system according to claim 21, characterized in that the registration system is arranged such that step x3 comprises steps x3.1 and x3.2, wherein step x3.1 generates a code associated with the information on the cash register system the excited at least one drug comprises; and step x3.2 comprises supplying the generated code to the computer system by the cash register system so that after performing step x3.2 and step x2, the computer system comprises the code and the associated information about at least one medication struck at the cash register system ; and that step x4 comprises providing the customer with the code generated by the cash register system. 24. A registration system according to any one of claims 21-23, characterized in that the registration system is arranged such that in step x6 the computer system shows the information about the at least one medicine and in particular a plurality of medicines associated with the code to an input entity in a separation list. A registration system according to claim 24, characterized in that the registration system is arranged such that in step x7 an input entity such as the patient, the client, a doctor or a healthcare institution, in particular the input entity of step x6, can indicate to the computer system that the medication stored in the separate list is used by the at least one patient whose identity is also selected in step 7, whereafter information about the use by the selected at least one patient of the personal medication belonging to the at least one medication is stored in the first database and in particular at least one drug that is indicated to be used is removed from the list. A registration system according to at least one of the preceding claims 21-25, characterized in that the registration system is arranged such that, in use, according to step x4, the code is printed by the cash register system, preferably on the receipt for the purchased at least one medicine. 27. A registration system according to at least one of the preceding claims 21-26, 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 be used in step a. allowing the patient to use the standard information from the second database for filling the first database. 28. A registration system according to claim 27, characterized in that the computer system is arranged in step a. To store information on the use of a medication by the patient in accordance with standard information from the second database on the medication to be entered, in the first database. to hit. 29. Registration system according to at least one of claims 21-28, characterized in that the computer system is arranged, when entering the information about the use of the medication by the patient, on the basis of a by the patient at the computer system keyword entered to generate and display a list of information about possible medications to the patient, after which the patient can choose a medication from the list corresponding to the medication he uses, the computer system being arranged to link the selected information about the medication to store the identity of the patient in the form of standard information in the first database. 30. Registration system according to at least one of claims 21-29, characterized in that the computer system is arranged such that the patient of a medication that he uses or has used can also input information about the frequency of intake of the medication, the dosage form 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 about a shelf life of the medication, and / or an identity of a person such as a doctor or pharmacist, healthcare institution, pharmacy and / or hospital who has prescribed the medication. 31. Registration system according to at least one of the preceding claims 21-30, characterized in that the computer system is arranged such that the first database in a step c. can be initially filled with information from the patient by a first entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution and wherein the computer system is arranged such that the first entity, for example when the patient indicates wanting this, can give the patient access to his information in the first database and / or that the computer system is arranged such that the first database in a step c. can initially be filled with patient information by the patient. 20 A recording system according to claim 31, characterized in that the computer system is arranged such that the first database in a step d. can be filled by the first entity and / or by the patient with information about the identity of the patient. 25 A registration system according to claim 31 or 32, characterized in that the computer system is arranged such that in a step e. by the first entity and / or the patient information about the use of the personal medication and / or other information about the patient, such as information about examinations carried out on the patient, for example by the first entity, linked to information about the identity of the patient can be stored in the first database. 34. A registration system according to claim 33, characterized in that the computer system is arranged such that in step e. the first entity and / or the patient can use the standard information from the second database for filling the first database. Registration system according to at least one of the preceding claims 21-34, characterized in that the computer system is arranged such that the patient can provide access to his information in the first database to a second entity such as a doctor and / or pharmacy and / or pharmacist and / or hospital and / or healthcare institution where in particular the patient can also indicate to which information the patient provides access to the relevant second entity. 36. A computer system according to claim 27 and optionally at least one of the preceding claims 21-26, 28-35, characterized in that the second database comprises the G standard, wherein the computer system is arranged such that the patient in step a. And / or the first entity in step e. of claim 34 can use the G standard for filling the first database. 37. A registration system according to at least claim 31 and optionally at least one of the preceding claims 21-30, 32-36, characterized in that the computer system is arranged such that the first entity can provide access to the patient to access the first database via the Internet. access by providing an access code to the patient. A registration system according to at least claim 35 and optionally at least one of the preceding claims 21-34, 36-37, characterized in that the computer system is arranged such that the patient can provide the second entity with access to his information in the first database 5 by protecting his information with a password that he gives to the second entity. 39. Registration system according to at least claim 31 and optionally at least one of the preceding claims 21-30, 32-38, characterized in that the computer system is arranged such that the computer system performs step c. by the first entity, generates and provides an access code to the first entity where the first entity is intended to provide this access code to the patient and wherein the computer system is arranged such that the patient records his data in the first database preferably via the Internet can access by entering the access code to the computer system and where after performing step c. by the first entity the first entity is automatically authorized to access the data of the patient in the first database and / or still be stored, the computer system being further arranged such that in consultation with the patient when performing step c. can be directly entered into the computer system by the first entity whether the automatic authorization is for a definite or indefinite period of time and what the nature of the automatic authorization is such as read, read and write only, full access or access to part of the information of the patient and / or characterized in that the computer system is arranged such that initial filling of the database with data of the patient in step c. can be performed by the patient.