WO2009152833A1

WO2009152833A1 - Methods and devices for prescribing and dispensing medicaments based on near field communication modules

Info

Publication number: WO2009152833A1
Application number: PCT/EP2008/004940
Authority: WO
Inventors: Ari Johannes Korpela; Pesonen Mika
Original assignee: Nokia Corporation
Priority date: 2008-06-19
Filing date: 2008-06-19
Publication date: 2009-12-23

Abstract

There is provided an apparatus for a near field communication module for transferring prescription related data, the apparatus comprising a data store configured for storing the prescription related data, the apparatus configured to transfer the prescription related data to/from a near field communicator for communication with a further device. The invention also relates to methods of providing and dispensing prescriptions. Prescriptions can be stored in a database provided by a server.

Description

METHODS AND DEVICES FOR PRESCRIBING AND DISPENSING MEDICAMENTS BASED ON NEAR FIELD COMMUNICATION MODULES

Technical Field

The present invention relates to the field of apparatus for near field communication modules (NFCs) (e.g. RFID modules) for transferring of prescription related data, associated methods, computer programs, modules and devices. Certain embodiments of the invention relate to near field communication modules for portable near field communication tags, and associated devices. The invention also relates to methods of providing prescriptions and associated apparatus.

Background

The provision of particular (controlled) medicaments is generally authorised by a medical practitioner, such as a physician, dentist, etc, and dispensed by another person. The physician (or the like) will not themselves be equipped to dispense such medicaments, and a patient, or the like, will have to retrieve the medicaments from a store, such as a pharmacy, drugstore, etc.

In many instances, authorisation is provided by the medical practitioner on a paper document, the recipient of which (e.g. patient) must in turn take the paper document with them and present to a pharmacist in order retrieve/dispense that particular medicine.

As many medicines are controlled, there is a requirement to interrogate the veracity of the paper documents used to provide prescriptions. Problems can occur when the legibility of such documents is poor, or when a mischievous party attempts to counterfeit such documents with a view to obtaining unauthorised medicines (e.g. printing forgeries, etc.).

In addition, providing prescriptions to patients who have mobility problems, and who cannot attend a surgery can also be problematic, as can providing repeat prescriptions to patients for a particular period of time (e.g. repeat prescriptions for six months). Trade name of particular medicines, can and do, differ from region to region (e.g. sold under one name in a particular country, and sold under another name in another country), it can be helpful for patients who travel between such regions (e.g. between different countries, different states, etc.) to have the correct medicines provided, even when the local trade names differ. This is particularly true of patients who take particular drugs to sustain their life.

The listing or discussion of a prior-published document or any background in this specification should not necessarily be taken as an acknowledgement that the document or background is part of the state of the art or is common general knowledge. One or more aspects/embodiments of the present invention may or may not address one or more of the background issues.

Summary

In a first aspect there is provided an apparatus for a near field communication module for transferring prescription related data, the apparatus comprising a data store configured for storing the prescription related data, the apparatus configured to transfer the prescription related data to/from a near field communicator for communication with a further device.

The prescription related data may be secured prescription related data. The secured prescription related data may be access controlled (e.g. encrypted data, such as by using public key interface, tamperproof data, etc.).

The module may be for providing prescription related data. In which case, the apparatus may be configured to transfer the prescription related data to a near field communicator for communication with a further device (e.g. for use in an RFID tag).

The module may be for receiving prescription related data. In which case, the apparatus may be configured to transfer the data from a near field communicator for communication with a further device (e.g. for use in a receiver of data from a tag).

The apparatus may comprise a near field communicator. The near field communicator may be configured to provide for transfer (e.g. transmission/receipt) of prescription related data. The near field communicator may be configured to provide for transmission of prescription related data to a further device. The near field communicator may be configured to provide for receipt of prescription related data from a further device. The near field communicator may be configured to provide for both transmission and receipt. The further device may comprise a complementary apparatus for a near field communication module for transferring prescription related data

The apparatus may be passive (e.g. configured to act as a transponder). The apparatus may be active (e.g. configured to be provided with a power supply).

The prescription related data may comprise at least one of: an authorisation code/pointer (e.g. a particular code/pointer that relates to an entry in a particular database, such as (secured) prescription provision database); prescription information (e.g. drug name, quantity, dosage, patient, etc.); identification data (e.g. biometric data, which may include a picture of the patient/user); medical details (e.g. medical history, potential pharma- codynamics/cokinetics); unique identifiers (e.g. a unique identifier of the apparatus which can be used to identify the apparatus, and/or a unique identifier which corresponds to a patient's/user's medical data, i.e. identifies the patient); near field communicator type; length of data; encryption signature (e.g. public keys, private keys, etc.)

The apparatus may be configured such that the prescription related data may be transferable only once. In such cases, the apparatus may be disposable. Alternatively, the apparatus may be re-usable, but be required to be provided with new/other/further prescription related data.

The apparatus may be configured such that the prescription related data is transferable from time to time, such as periodically/aperiodically. The apparatus may be configured such that the prescription related data is transferable in order to provide for repeat prescriptions (e.g. transferable monthly, roughly weekly, etc.).

The apparatus may be configured such that the prescription related data is encrypted for transfer (e.g. encrypted when communicated using near field communication). The apparatus may be configured such that the prescription related data is transferable using public key infrastructure. According to a second aspect of the present invention there is provided a near field communication module comprising an apparatus according to any of the first aspect.

According to a third aspect there is provided a portable prescription provision tag comprising a module according to the second aspect. The portable prescription provision tag may be configured to be worn by a patient/user.

According to a fourth aspect there is provided a dispenser apparatus (dispenser) comprising a module according to the second aspect. The dispenser may be configured to use received prescription related data to provide prescription details (e.g. use the received prescription related data to provide prescription details to a pharmacist, or the like). The prescription details comprising the information required in order to allow a pharmacist to provide the particular prescription for that patient/user.

The dispenser may be configured to retrieve prescription details from a server (e.g. a server wired/wirelessly connected to device), by using the received prescription related data. The dispenser may be configured to retrieve supplemental data from a server (e.g. a server wired/wirelessly connected to device), by using the received prescription related data, and provide corresponding prescription details (e.g. using the prescription related data and the supplementary data).

The dispenser may be configured to receive data from a prescription provision database by using the received prescription related data. The prescription provision database may be provided at a server. Such as, using an access code provided by the prescription related data to retrieve an entry in a prescription provision database on the server corresponding to that access code, e.g., the entry relating to prescriptions detail, a particular drug/drug quantity, etc.

According to a fifth aspect there is provided an authorising apparatus (authoriser) comprising a module according to the second aspect, wherein the authoriser is configured to provide prescription related data to a portable prescription provision tag according to the third aspect, using the said near field communication.

The authoriser may be further configured to provide prescription details to a server. The authoriser may be configured to provide supplemental data to a server. The supplemental data may comprise at least one of: drug type; quantity of drug; dosage; name of authorising medical practitioner; other directional information; number of repeats; contact details of authorising surgery; patient details; near field communicator type; length of data; encryption signature; unique tag identifier; biometric data.

The authoriser may be configured to provide prescription related data corresponding to the data provided to a server to a portable prescription provision tag (e.g. providing an access code/pointer, providing partial prescription details to the tag and partial prescription details to the server).

According to a sixth aspect there is provided a prescription provision database comprising data for use with the dispenser/authoriser according to any of the features of the fourth and fifth aspects.

According to a seventh aspect there is provided a data carrier product, comprising prescription related data and/or supplemental data and/or a prescription provision database configured for use with any of the above aspects.

According to an eighth aspect there is provided an apparatus for a portable near field communication tag for transferring prescription related data, the apparatus comprising a data store configured for storing the prescription related data, the apparatus configured to transmit the prescription related data to a near field communicator for communication with a further device.

The prescription related data may be secured prescription related data. The secured prescription related data may be encrypted/tamperproof data. The apparatus may be configured to receive prescription related data from a further device (e.g. an authoriser according to the fifth aspect).

According to a ninth aspect there is provided an apparatus for a near field communication module for a dispensing apparatus (dispenser), the apparatus for receiving prescription related data, the apparatus comprising a data store configured for storing the prescription related data, the apparatus configured to receive the prescription related data from a near field communicator for communication with a further device. The further device may be a tag according to the eighth aspect. The prescription related data may be secured prescription related data. The secured prescription related data may be encrypted/tarn perproof data.

According to a tenth aspect there is provided an apparatus for a near field communication module for an authorising apparatus (authoriser), the apparatus for providing prescription related data, the apparatus comprising a data store configured for storing the prescription related data, the apparatus configured to provide the prescription related data to a near field communicator for communication with a further device.

The apparatus may be configured to provide the prescription related data to a near field communicator for communication with an apparatus for a portable near field communication tag according to the eighth aspect. The prescription related data may be secured prescription related data. The secured prescription related data may be encrypted/tamperproof data.

The apparatus may be further configured to provide corresponding supplementary data/prescription details to a server/prescription provision database. The apparatus may be further configured to provide corresponding supplementary data/prescription details to a server. The server may comprise the prescription provision database.

According to a twelfth aspect there is provided an apparatus for a server, the apparatus configured for communication with a dispensing apparatus, the apparatus configured to store supplementary data/prescription details and provide supplementary data/prescription details in response to a request from a dispensing device (e.g. after the dispensing device has provided the server with information from received prescription related data, such as an access code, etc).

The apparatus for a server may be further configured for communication with an authorising apparatus, the apparatus for a server configured to receive prescription details from the authorising device. The apparatus may be configured to store/provide a prescription provision database.

According to a thirteenth aspect there is provide a server comprising an apparatus according to any of the features of the twelfth aspect. According to a fourteenth aspect there is provided a means for an apparatus for a means for a near field communication module for transferring prescription related data, the means for an apparatus comprising a means for a data store configured for storing the prescription related data, the means for an apparatus configured to transfer the prescription related data to/from a means for near field communication for communication with a means for a further device.

According to a fifteenth aspect there is provided an apparatus for a near field communication module for transferring medical related data, the apparatus comprising a data store configured for storing the medical related data, the apparatus configured to transfer the prescription related data to/from a near field communicator for communication with a further device.

The medical related data may be secured medical related data. The secured medical related data may be access controlled (e.g. encrypted/tamperproof data, etc.).

According to a sixteenth aspect there is provided a method of providing prescriptions, comprising: providing a data store configured for storing prescription related data on an apparatus with prescription related data; providing for transfer of the prescription related data to/from the apparatus using a near field communicator.

The method may comprise providing for secured transfer of the prescription related data to/from a further device using a near field communicator. The secured transfer may be provided by providing access control to the prescription related data (e.g. encrypting the stored data/transferred data).

The method may comprise providing a communicator for near field communication with a further device.

The method may further comprise providing prescription related data to the communicator for communication with a dispenser for dispensing a prescription using the transferred prescription related data. The method may comprise receiving at the dispenser prescription related data. The method may then comprise using the prescription related data at the dispenser to provide a prescription. The method may comprise providing a prescription (e.g. to a person provided the prescription related data).

The method may comprise receiving at the dispenser corresponding supplementary data/prescription details from a server so as to provide a prescription. The method may comprise using the supplemental data and the received prescription related data to provide a prescription details. The method may comprise providing the prescription.

The method may comprise providing prescription related data from an authoriser to the apparatus for storing on the data store, the prescription related data for subsequent use by a dispenser for providing a prescription. The providing of the prescription related data may be by using near field communication, and/or by using another communication link (e.g. USB, IrDA, Ethernet, etc.).

The method may comprise providing supplementary data/prescription details to a server for subsequent use by the dispenser for providing a prescription. The supplemental data/prescription details may be provided by the authoriser. The supplemental data/prescription details may be provided at around the same time (e.g. simultaneously) as providing the prescription related data to the apparatus.

The prescription related data and/or supplemental data and/or prescription details may comprises at least one of: drug type; quantity of drug; dosage; name of authorising medical practitioner; other directional information; number of repeats; contact details of authorising surgery; patient details; near field communicator type; length of data; encryption signature (e.g. public key, private key, etc.); unique tag identifier; biometric data.

According to a seventeenth aspect there is provided a method of providing prescriptions, comprising: receiving prescription related data from a prescription provision tag via near field communication; and providing for dispensing of prescriptions based on the prescription related data. The prescription related data may be received using near field communication. The prescription related data may be received using another form of communication, which may be wired, wireless, or both (e.g. USB, IrDA, Ethernet, etc.). The prescription related data may be secured prescription related data (e.g. access controlled, encrypted, etc.).

The method may comprise receiving from a server supplementary data corresponding to the prescription related data so as to provide for the prescription details. The receiving of may be via a wired/wireless (or both) connection (e.g. Internet). The method may comprise receiving from a server prescription details corresponding to the prescription related data so as to provide for the prescription details (e.g. retrieving prescription details by using an access code received from the prescription related data).

The method may comprise providing a prescription using the prescription related data/supplementary data/prescription details (e.g. providing the prescription to the patient/user of the tag).

According to an eighteenth aspect there is provided a method of providing prescriptions, comprising: providing prescription related data to a prescription provision tag for storing on a data store configured for storing prescription related data for subsequent communication to a dispenser via near field communication.

The prescription related data may be provided using near field communication. The prescription related data may be provided using another form of communication, which may be wired, wireless, or both (e.g. USB, IrDA, Ethernet, etc.). The prescription related data may be secured prescription related data (e.g. access controlled, encrypted, etc.).

The method may further comprise providing to a server supplementary data/prescription details corresponding to the prescription related data (e.g. so as to provide subsequently for prescription details to be used by a dispenser). The providing may be via a wired/wireless (or both) connection (e.g. Internet).

According to a nineteenth aspect there is provided a prescription provision system comprising a tag according to any of the features of the third aspect and a dispenser according to any of the features of the fourth aspect. The tag may be configured to communicate (e.g. using near field communication, USB, Ethernet, etc.) prescription related data to the dispenser to allow for provision of a prescription.

The system may further comprise a server. The dispenser may be configured to receive from the server (e.g. via wired, wireless or both communication) supplementary data corresponding to prescription related data provided by the tag so to allow for provision of a prescription. The dispenser may be configured to receive from the server (e.g. via wired, wireless or both communication) prescription details corresponding to prescription related data provided by the tag so to allow for provision of a prescription.

The prescription provision system may further comprise an authoriser. The authoriser may be configured to communicate (e.g. using near field communication, USB, Ethernet, etc.) prescription related data to the tag for subsequent retrieval by the dispenser for use in dispensing prescription medicines/drugs.

The authoriser may be further configured to provide supplementary data to the server, corresponding to prescription related data provided to the tag, for subsequent use by the dispenser. The supplementary data may be provided for a prescription provision database, and/or for prescription details.

According to a twentieth aspect there is provide a means for an apparatus for a means for a near field communication module for transferring means for prescription related data, the means for an apparatus comprising a means for storing data configured for storing the means for prescription related data, the means for an apparatus configured to transfer the means for prescription related data to/from a means for near field communication for communication with a means for a further device.

According to a twenty-first aspect there is provided a means for a near field communication module comprising a means for an apparatus according to the twentieth aspect.

According to a twenty-second aspect there is provided a means for a portable prescription provision tag comprising means for a near field communication module according to the twenty-first aspect. According to a twenty-third aspect there is provided a means for dispensing comprising a means for a near field communication module according to the twenty-first aspect, wherein the means for dispensing is configured to use received means for prescription related data to allow for providing a prescription.

According to a twenty-fourth aspect there is provided a means for authorising comprising a mean for a near field communication module according to the twenty-first aspect, wherein the means for authorising is configured to provide means for prescription related data to a means for a portable prescription provision tag according to the twenty-second aspect, using the said near field communication.

According to a twenty-fifth aspect there is provided means for a prescription provision database comprising means for supplementary data for use with the means for dispensing/means for authorising according to any of the twenty-third/twenty-fourth aspect.

According to a twenty-sixth aspect there is provided a means for an apparatus for a means for a near field communication module for transferring means for confidential medical related data, the means for an apparatus comprising a means for storing data configured for storing the means for confidential medical related data, the means for an apparatus configured to transfer the means for confidential medical data to/from a means for near field communication for communication with a means for a further device.

According to a twenty-seventh aspect there is provided a method of providing prescriptions, comprising: providing a means for storing data configured for storing means for prescription related data on a means for an apparatus; providing for transfer of means for prescription related data to/from the means for an apparatus using a means for near field communication.

According to a twenty-eighth aspect there is provided a method of providing prescriptions, comprising: receiving means for prescription related data from a means for prescription provision tag using near field communication; and providing for dispensing of a prescription based on the means for prescription related data. According to a twenty-ninth aspect there is provided a method of providing prescriptions, comprising: providing means for prescription related data to a means for a prescription provision tag for storing on a means for storing data configured for storing means for prescription related data for subsequent communication to a means for dispensing via means for near field communication.

According to a thirtieth aspect there is provided a means for a prescription provision system comprising a means for a portable prescription provision tag according to the twenty-second aspect and a means for dispensing according to the twenty-third aspect, wherein the means for a portable prescription provision tag is configured to communicate means for prescription related data to the means for dispensing to allow for provision of a prescription.

The present invention includes one or more corresponding aspects, embodiments or features in isolation or in various combinations whether or not specifically stated (including claimed) in that combination or in isolation. Corresponding means for performing one or more of the discussed functions are also within the present disclosure. It will be appreciated that one or more embodiments/aspects may be useful in increasing security/reducing fraud in relation to the dispensing of prescribed medicaments.

The above summary is intended to be merely exemplary and non-limiting.

Brief Description of the Figures

A description is now given, by way of example only, with reference to the accompanying drawings, in which:-

Figure 1a shows an apparatus for near field communication, and Figure 1b shows an embodiment of a module comprising the apparatus;

Figure 2 shows the module of Figure 1 b comprised with a prescription provision tag;

Figure 3 shows an embodiment of a dispenser for use with a tag shown in Figure 2; Figure 4 shows a further embodiment of a prescription provision tag;

Figure 5 shows an embodiment of an authoriser for use with the tag of Figure 4;

Figure 6 shows a further embodiment of a prescription provision tag;

Figures 7a and 7b show block diagrams of a prescription provisions systems;

Figure 8 shows a further embodiment of a prescription provision system;

Figure 9 shows a flowchart of a method of providing a prescription;

Figure 10 shows a flowchart of a method of providing prescription related data to a tag;

Figure 1 1 shows a flow chart of using the system as shown in Figure 8a; and

Figure 12 shows exemplary tables of prescription related data and supplementary data.

Description of Specific Embodiments

Figure 1a shows an apparatus 100 for a near field communication module for transferring prescription related data. The apparatus 100 comprises a data store 110, configured to store the prescription related data. The apparatus 100 is further configured to transfer the prescription related data to a near field communicator for communication with a further device. In the present embodiment, the apparatus 100 comprises a processor 120 configured to provide for the said transfer.

The apparatus 100 is configured such that the data store 110 securely stores the prescription related data. In the present embodiment the data store 110 is access controlled (e.g. authentication required, encrypted, etc.). In alternative embodiments the prescription related data need not be access controlled, and may be readily accessible.

In some embodiments, the data store 110 is provided by a discrete bank of digital memory (e.g. flash, etc.) and the processor 120 is provided by a discrete processor. In alternative embodiments the apparatus 100 may be provided by a single apparatus, such as a field programmable gate array, application specific integrated circuit, or the like.

Figure 1b shows an embodiment of a module 200 comprising the apparatus 100. The module 200 further comprises a communicator 230, configured for near field communication with a further device. In the present embodiment the communicator 230 is provided by a near field antenna (e.g. an RFID antenna), or the like. Here, the module 200/apparatus 100 are configured such that prescription related data (stored/storable by the data store 1 10) can be transmitted/received from/by the module 200.

Figure 2 shows the module 200 /apparatus 100 comprised with a prescription provision tag 300, which in the present embodiment is a portable tag 300 (e.g. a tag 300 that can be worn or carried by a user). Here, the tag 300 is configured to transmit, by using the communicator 230, prescription related data to a further device (i.e. transmit to a further device, with near field communication capability, prescription related data that is stored on the data store 110). In this embodiment, the tag 300 is configured to communicate using Near Field Communication (NFC) Forum specification (http://www.nfc- forum.org/specs/). It will readily be appreciated that the tag may be active (e.g. powered) or passive (e.g. acting as a transponder).

In the present embodiment, the prescription related data is stored such that it cannot be altered. In this embodiment, prescription related data may be considered as being read only; prescription related data is stored on the data store 1 10 such that even when the tag 300 is not receiving power (e.g. when acting as a transponder) the data is maintained.

The tag 300 is additionally configured such that the prescription related data is only accessed/read by an authorised/certified further device (e.g. by using encryption techniques, such as public key infrastructure).

Figure 3 shows an embodiment of the module 200 /apparatus 100 comprised with a dispensing device 600 (dispenser 600) for received prescription related data. Here, the dispenser 600 is configured to receive, by using the communicator 230, the prescription related data from a tag 300 (i.e. receive by using near field communication, such as receiving data in accordance with NFC Forum specification, the secured prescription related data), so as to allow for a prescription to be provided (e.g. by a user of the dispenser 600, such as a pharmacist).

Here, the dispenser 600 further comprises an output 610 (e.g. a display, printer, or the like), which is configured to provide to a user of the dispenser 600 the received prescription related data (or associated prescription details). It will readily be appreciated that the dispenser 600 may be provided with a personal computer, laptop, or the like (i.e. provided on circuitry of the computer). Alternatively the dispenser 600 may be configured to connect/disconnect to a personal computer, etc. (e.g. via a USB connection) so as to use functionality of the PC to provide for shared resources (e.g. using the computer's existing display/printer).

Figure 9 shows a method of providing 900 a prescription according to the present embodiment, wherein in use a patient (or person wishing to obtain prescription medicines, or the like) can be provided 1010 with a portable tag 300 (e.g. provided by a medial practitioner, bought from a counter at a drugstore (i.e. pre-determined tags), or the like), wherein the prescription related data is stored securely on the tag 300 and is specific to the needs of that patient/person (e.g. specific to the medical needs of that person/patient).

The prescription related data stored on the data store 110 of the tag 300 may include one or more of data such as: drug type (e.g. trade name, generic name, etc); quantity of drug (e.g. 100x200mg tablets); dosage (e.g. 2 tablets, four times a day); name of authorising medical practitioner; other directional information (e.g. best taken after food); number of repeats (e.g. able to use the tag three times); contact details of authorising surgery (e.g. address, telephone, e-mail, fax, etc); patient details (e.g. name, age, country of residence, address, health service ID number), etc.

The prescription related data may additionally comprise data for allowing communication using near field communication (e.g. NFC Forum specification data) such as: near field communicator type (e.g. NDEF); length of data; encryption signature (e.g. public keys, private keys, etc); unique tag identifier, etc.

A patient/person may then take 1020 the tag 300 to a pharmacy/drugstore (or the like) where there exists a dispenser 600 for near field communication with the tag 300. Rather than relying on paper documentation, or similar, a pharmacist or user can bring the tag

300 into proximity 1030 with the dispenser 600 (the proximity of the tag 300 and the dispenser 600 being roughly 10 cm or less) such that it reads 1040 the prescription related data from the tag 300, and outputs details allowing the pharmacist to prepare the prescription (prescription details) on the output 610. Thus, the desired/required prescription is able to be provided 1050 by the pharmacist, or the like (in some embodiments the dispensing may be automated, e.g. no output required, and the drugs are automatically dispensed based on the prescription related data).

It will readily be appreciated that the tag 300 may be provided with further prescription related data, such as data relating to the identity of the intended recipient of the medicament(s). In such an arrangement the tag 300 may be provided (e.g. securely provided) with prescription related data which relates to, for example, the biometric data for the intended recipient (e.g. passport-style image, such as a portrait image, finger-print details, etc.). In the embodiment of using a passport-style image, the dispenser 600 is configured to read that particular prescription related data in addition to the other data stored on the tag 300 and provide that image on the output 610 (i.e. print the image, display the image, etc.). In such a case, the pharmacist (for example), can visually confirm that the prescription is for the intended person.

It will also be readily appreciated that the prescription related data may comprise data relating to the time at which the prescription may be retrieved. For example, in one embodiment the prescription related data comprises a time, after which the prescription should not be dispended (e.g. expiry of prescription), or at what intervals the tag 300 may be used to receive a prescription (e.g. dates during every month that the prescription should be dispensed, every several months, etc.).

In alternative embodiments, the processor 110 of the apparatus 100 of the tag 300 is configured such that the prescription related data is not retrievable/readable after a particular time/date (e.g. the prescription related data is erased after it has expired), and/or configured such that the prescription related data is only accessible after a particular length of time after the last read event (e.g. readable after a month from the last time the tag 300 was read by a dispenser 600, readable after three months from the last read event, etc.). Such an arrangement, allows a user to be provided with a single tag 300 which can accommodate repeat prescription instructions, without the need to obtain further documentation for each further prescription, or to revisit a medical practitioner, or the like (e.g. repeat prescriptions of drugs which often do not require further consultation, such as antihistamines). A skilled reader would readily be able to implement such an arrangement.

It will also be appreciated that while in the above embodiment the tag 300 was configured such that the prescription related data could not be amended/overwritten/added to (e.g. exhaustion of the prescription related data is monitored remotely to the tag), in alternative embodiments this need not be the case. In some cases, the tag 300/dispenser 600 may be configured such that the dispenser 600 is able to amend/provide prescription related data at roughly the same time (e.g. during) near field communication with the tag 300. In such embodiment, the tag 300 may be additionally configured to receive, by using the communicator 230, prescription related data from a further device (e.g. dispenser 600).

In such an arrangement, the dispenser 600 may be configured to provide data to the tag for storage on the data store 110 relating to the time/date of the read event (the read event occurring when the tag 300 is in communication with the dispenser 600 so as to provide prescription related data). The dispenser 600 may be configured to amend data stored on the data store 110, such as the number of repeat prescriptions available (e.g. amending the number of repeats from "3", down to "2", during/after a read event).

In further embodiments still, the tag 300 may be configured to amend/add prescription related data. The tag 300 may be configured to amend data stored on the data store 110, such as the number of repeat prescriptions available after a read event, etc. In such an arrangement, no data is provided by the dispenser 600: the tag 300 provides the amendment/update (e.g. using the processor 120).

Figure 4 shows the module 200 /apparatus 100 comprised with a further embodiment of a prescription provision tag 400. Again, the tag 400 is portable and is configured to transmit, by using the communicator 230, prescription related data to a further device

(i.e. transmit to a further near field communication device). In this embodiment, the tag

400 is configured to receive, by using the communicator 230, prescription related data from a further device (e.g. such as receiving data in accordance with NFC Forum specification). The apparatus 100 is configured to store received prescription related data in a secured manner (e.g. such that it can only altered/accessed by an authorised/certified further device). In certain embodiments however the data may be altered by the tag 400 (e.g. when the data is a function of time/read event as discussed above).

Figure 5 shows the module 200 /apparatus 100 comprised with an authorising device 700 (authoriser 700) for providing prescription related data. Here, the authoriser 700 is configured to communicate, by using the communicator 230, the prescription related data to a tag 400, (i.e. transmitting, by using near field communication, such as transmitting data in accordance with NFC Forum specification,, the prescription related data). Here, the authoriser 700 further comprises an input 710 (e.g. a display/keyboard/touch-screen or the like), which is configured to allow a user (e.g. a medical practitioner, such as a physician) to input/select particular prescription related data for transmission to a tag 400.

In certain embodiments, the authoriser 700 is comprised with a personal computer, laptop or the like, or alternatively may be connectable/disconnectable with a computer etc. (e.g. via USB), to use the input 710 (e.g. keyboard, display). In some embodiments the authoriser 700 computer may share resources, as will be readily appreciated.

Figure 10 shows a method of providing 1100 prescription related data to a tag 400 wherein, in use, a person, such as medical practitioner, is able to bring 1110 into proximity the tag 400 with the authoriser 700. Using the input 710, the medical practitioner is able to communicate 1120 to the tag 400 prescription related data. The type of data may be consistent to the data detailed above (e.g. drug, dosage, biometric data, public key, etc.). The prescription related data is stored on the tag 400. In such an arrangement the data may be considered to be read/writable, such that a user can be provided with a personal prescription tag (e.g. a tag 400 which^' can be used more than once). Alternatively, the tags 400 may be configured such that they can only be written to once. A prescription may then be retrieved in a similar manner to that described above.

It will readily be appreciated that in alternative embodiments, the tag 400/authoriser 700 may not be configured to receive/transmit data by using near field communication. In alternative embodiments the tag 400 / authoriser 700 may use alternative communication. In some embodiments the tag 400/ authoriser 700 may be provided with an alternative/additional communication link.

Figure 6 shows the module 200 /apparatus 100 comprised with a further embodiment of a prescription provision tag 500, in which there is provided an additional communication link 550. Again, the tag 500 is portable and is configured to transmit, by using the communicator 230, prescription related data to a further device (i.e. transmit to a further near field communication device, such as a dispenser 600). Here, the tag 500 is additionally configured to receive, by using the communication link 550, prescription related data from a further device. In this embodiment, the link 550 is configured as a USB port. It will readily be appreciated however that this may be provided by any number of links which allow for transfer of data, such as a RJ45 (e.g. for 100/10 LAN), WiFi receiver, IrDA, GSM receiver, etc.

In certain embodiments the tag 500 is configured to retrieve prescription related data from a further network. For example, the tag 500 may be configured to retrieve, and store (e.g. securely store), prescription related data from an authoriser 700 via the Internet (e.g. using Ethernet connectivity). That is to say that the authoriser 700 may be configured to communicate particular prescription related data over a network, rather than using near field communication. In such arrangements the prescription related data may be stored/retrieved on an intermediary device (e.g. a home computer connected to the Internet) for communication to the tag 500 via the USB connection. Such an arrangement may allow for when a user of the tag 500 (e.g. the patient) is unable to travel to the medical practitioner in order to retrieve their prescription.

It will be readily appreciated by the skilled reader that the tag 500 (and tags 300, 400 of other embodiments) may additionally/alternatively be configured to provide (e.g. transmit) the prescription related data to a corresponding dispenser 600 using the communication link. That is that in some embodiments, communication to the dispenser is by using USB, IrDA, Ethernet, etc. (e.g. without the use of near field communication)

Figures 7a and 7b show block diagrams of configurations of prescription provision systems. In Figure 7a, a tag 400 is configured to receive (by using near field communication) and store (e.g. securely store), prescription related data from an authoriser 700. The tag 400 is configured such that it can transmit the particular prescription related data to a dispenser 600 to allow for providing a particular prescription. Figure 7b shows a similar embodiment, in which the prescription related data is transferred from the authoriser to the tag 500 via a network 800 (e.g. Internet). A skilled party will appreciate however that in alternative arrangements the authoriser 700 may not communicate with the tag 500 via a network 800, but may communicate via a link such as a USB connection, or the like.

Figure 8a shows a further block diagram of a prescription provision systems using a tag 400, 500, authoriser 700, and dispenser 600. Here, there is also provided a server 900, comprising a processor 910 and a database store 920. The server 900 is in communication with the authoriser 700 via a first network connection 930a, and in communication with the dispenser 600 via a second network connection 930b. It will be readily appreciated that either of the first and second network connections 930a, 930b may be provided by wire or wireless connection (or combination thereof) and may also be provided with further intermediary network equipment (including the same equipment).

In this arrangement the prescription related data is provided (by the authoriser 700) to the tag 300, 400 such that it can subsequently be communicated to the dispenser 600. In addition, supplementary data are communicated to the server 900 for storage by the server processor 910 on the database store 920. The supplementary data may comprise any of: drug type (e.g. trade name, generic name, etc); quantity of drug (e.g. 100x200mg tablets); dosage (e.g. 2 tablets, four times a day); name of authorising medical practitioner; other directional information (e.g. best taken after food); number of repeats (e.g. able to use the tag three times); contact details of authorising surgery (e.g. address, telephone, e-mail, fax, etc); patient details (e.g. name, age, country of residence, address, health service ID number), prescription issue number (e.g. a unique number relating to a particular prescription details), etc. The supplementary data may be considered as data which can subsequently be used to provide prescription details. In some embodiments the authoriser 700 is configured to communicate prescription details to the server 900.

When the tag 300, 400 transmits the particular prescription related data to the dispenser

600, the dispenser 600 is configured to retrieve supplementary data/prescription details from the server 900 via the second network connection 930a. The supplementary data may be biometric data (e.g. a picture, etc.) so as to allow for confirmation of the user of the tag 300, 400 so as to provide prescription details. Alternatively/additionally the supplementary data may comprise other prescription details (e.g. drug dosage, etc as described above.).

In some arrangements the prescription related data stored on the data store 110 of the tag 400, 500 may be data relating to the access/location of the supplementary data (e.g. a particular secure code, a pointer (e.g. database entry location), unique identifier of the tag corresponding to particular data stored on the server 900, prescription issue number etc.). The server may comprise a multitude of data entries for a multitude of tags/patients. In such arrangements the server 900 may be considered to comprise a prescription provision database.

Figure 8b shows a further embodiment in which the authoriser 700 is not configured to communicate with the server 900. In such an arrangement, the authoriser 700 may be configured to provide a prescription related data that comprises data to access particular information existing on the server 900 (e.g. a pre-compiled list of drugs/dosages, etc.).

It will readily be appreciated that in further alternative embodiments, the prescription providing system may not comprise an authoriser 700. That is the system may use a tag 300 as shown in Figure 2 (e.g. a tag 300 that is provided with read only data). Again, the prescription related data may correspond to data stored in a prescription provision database on the server (e.g. a pointer, code, unique tag identifier, etc.).

Figure 11 shows a flow chart 1200 of using the system as shown in Figure 8a. A user is provided 1210 with a tag for communication with an authoriser 700 and a dispenser 600. The tag 300, 400 is brought into proximity 1220 with (or connected to) the authoriser 700 such that the authoriser is able to communicate 1230 prescription related data to the tag 300, 400. The authoriser is also configured (e.g. at the same time, sometime before/afterward) to communicate 1240 supplementary data to the server 900 using the first network connection 930a. The server is configured to store 1250 the supplementary data with a prescription provision database. A user takes 1260 the tag 300, 400 to the dispenser 600, and brings 1270 the tag 300, 400 into proximity with the dispenser 600 such that the dispenser 600 is able to read 1280 the prescription related data stored securely on the tag 300, 400. The dispenser 600 is further configured to retrieve 1290 corresponding supplementary data from the server 900, via the second network connection 930b, so as to provide 1300 for prescription details. !n the embodiment shown in Figure 8b, it will readily be appreciated that the prescription provision database need not be updated/added to by the authoriser, and may be updated/added to by a further device, or may be provided with a predefined database (e.g. a list of drugs and dosages, each of which correspond to a particular access code provided by prescription related data).

It will readily be appreciated that in some embodiments multiple authorisers 700/ dispenser 600 may be in communication with the server 900. In such arrangements the server may store a prescription provision database for multiple authorisers 700 and/or dispenser 600, or may a single database for each authoriser and/or dispenser.

In some embodiments, the user may be provided with a tag 300, 400, 500 comprising prescription related data that relates to travel medicines, or required for life medicines

(e.g. blood pressure medicines). The user can use the tag 300, 400, 500 with a foreign dispenser 600 (or a dispenser 600 in a different state), and wherein the dispenser 600 is configured to communicate with a local server 900 (e.g. a server in the user's local country, state, etc.) so as to provide the prescription details (e.g. converting for local trade names, etc.). Such an arrangement may additionally allow for a foreign health provider to invoice a local health provider for dispensing of medicaments (e.g. without the need for a user to pay costs for the medicaments).

Figure 12a shows a table 1300 of exemplary prescription related data that might be stored on the data store of a tag 300, 400, 500 (e.g. stored in no particular order). Figure

12b shows a further table 1400 of exemplary supplementary data stored which might be stored as an entry in a prescription provision database on the data store 910 of a server

900, while Figure 12c shows a table 1500 of corresponding prescription related data that might be stored on a tag 300, 400, 500. It will readily be appreciated that in alternative embodiments, other data may be provided (including any of the examples detailed above, e.g. contact details, etc.). A data store configured for storing the prescription related data may be considered to be a data store with specifically defined fields, according to a particular predefined format, available for/comprising prescription related data. For example, this format may be according to a format defined above in Figures 12a-c, or by the NFC Forum specifications (Figure 12d below). Figure 12d shows pseudo data structure of an exemplary record packet 1600, like that provided by the NFC Forum specifications (i.e. an exemplary record which might be used for providing prescription related data). Here, the data is the first record, but not the last to be communicated (as indicted message begin/end fields). The Type is a Record Type Definition, which allows for defining record formats for applications such a prescription provision applications. This allows for creating of propriety/bespoke applications based on NFC Forum specifications for prescription related data. Thus the tag/dispenser/authoriser is configured to store and communicate data which is configured specifically for prescription related data (in this case specifically configured Record Type Definition). It will be appreciated that other data records (not shown) with additional information (e.g. drug name) would be associated with the record shown in Figure 12d to provide the data required to allow dispensing of a prescription.

It will readily be appreciated that in alternative embodiments the Type may be a further Type, not provided by the present NFC Forum specification. A skilled reader would readily be able to implement such arrangements.

The data (as shown in Figure 12b) is additionally provided with an ID. In some embodiments the payload may be used to transfer the data. In other embodiments, the ID may be used to transfer the data (e.g. providing the ID so as to provide a pointer to other data, such as that stored on a server).

In some embodiments, a unique identifier of the tag itself may be used to provide a pointer to other data (e.g. using the unique identifier of the tag to provide a prescription issue number, or the like). It will be appreciated that in some embodiment, during the first interrogation of the tag (i.e. communication prior to being able to access a data store), the tag may be configured to provide a unique identifier, such as a unique identifier to be used for subsequent communication to/from the tag. This identifier may be used for using/retrieving further data (e.g. supplementary data).

Similarly, while the above embodiments the describe the transfer of prescription related data (mainly for the purposes of allowing for (securely) providing prescriptions to patients and the like), in alternative embodiment the data may be associated with other medical data, such as biochemistry data (e.g. laboratory results of blood tests, etc.). A person skilled the art would readily be able to implement such further configurations.

Also, the above discussion is not limited to using a tag 300, 400, 500 as a discrete portable element, and the tag 300, 400, 500 may be provided with a further device, such as a portable electronic device capable of further functions/operations.

It will be appreciated to the skilled reader that the module/tag/device/server and/or other features of particular apparatus may be provided by apparatus arranged such that they become configured to carry out the desired operations only when enabled, e.g. switched on, or the like. In such cases, they may not necessarily have the appropriate software loaded into the active memory in the non-enabled (e.g. switched off state) and only load the appropriate software in the enabled (e.g. on state). The apparatus may comprise hardware circuitry and/or firmware. The apparatus may comprise software loaded onto memory.

It will be appreciated that any of the aforementioned apparatus 100, module 200, tag 300, 400, 500, dispenser 600, authoriser 700 and server 900 may have other functions in addition to the mentioned functions, and that these functions may be performed by the same circuit/apparatus/elements.

The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the present specification as a whole in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims. The applicant indicates that aspects of the present invention may consist of any such individual feature or combination of features. In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the invention.

While there have been shown and described and pointed out fundamental novel features of the invention as applied to preferred embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of the devices and methods described may be made by those skilled in the art without departing from the spirit of the invention. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the invention. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto. Furthermore, in the claims means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures. Thus although a nail and a screw may not be structural equivalents in that a nail employs a cylindrical surface to secure wooden parts together, whereas a screw employs a helical surface, in the environment of fastening wooden parts, a nail and a screw may be equivalent structures.

Claims

1. An apparatus for a near field communication module for transferring prescription related data, the apparatus comprising a data store configured for storing the prescription related data, the apparatus configured to transfer the prescription related data to/from a near field communicator for communication with a further device.

2. An apparatus according to claim 1 , wherein the apparatus is configured to store secured prescription provision data.

3. An apparatus according to claim 1 or 2, wherein the module is for providing prescription related data, the apparatus being configured to transfer the data to a near field communicator for communication with a further device.

4. An apparatus according to claim 1 or 2, wherein the module is for receiving prescription related data, the apparatus being configured to transfer the data from a near field communicator for communication with a further device.

5. An apparatus according to any preceding claim, further comprising a near field communicator, the near field communicator configured to provide for transfer of prescription related data.

6. An apparatus according to any preceding claim, wherein the prescription related data comprises at least one of: drug type; quantity of drug; dosage; name of authorising medical practitioner; other directional information; number of repeats; contact details of authorising surgery; patient details; near field communicator type; length of data; encryption signature; unique tag identifier; prescription issue number; biometric data.

7. An apparatus according to any preceding claim, configured such that the prescription related data is transferable once.

8. An apparatus according to any preceding claim, configured such that the prescription related data is transferable from time to time.

9. An apparatus according to any preceding claim, configured such that the prescription related data is transferable using public key interface.

10. A near field communication module comprising an apparatus according to any of the preceding claims.

1 1. A portable prescription provision tag comprising a module according to claim 10.

12. A dispenser apparatus comprising a module according to claim 10, wherein the dispenser is configured to use received prescription related data to provide a prescription.

13. A dispenser according to claim 12, configured to retrieve supplementary data from a server, by using the received prescription related data.

14. A dispenser according to claim 13, configured to receive supplementary data from a prescription provision database, the prescription provision database being provided at a server, by using the received prescription related data.

15. An authoriser apparatus comprising a module according to claim 10, wherein the authoriser is configured to provide prescription related data to a portable prescription provision tag according to claim 11 , using the said near field communication.

16. An authoriser according to claim 15, further configured to provide supplementary data to a server for providing in a prescription provision database.

17. A prescription provision database comprising supplementary data for use with the dispenser/authoriser according to any of the claims 12 to 16.

18. An apparatus for a near field communication module for transferring confidential medical related data, the apparatus comprising a data store configured for storing the confidential medical related data, the apparatus configured to transfer the data to/from a near field communicator for communication with a further device.

19. A method of providing prescriptions, comprising: providing a data store configured for storing prescription related data on an apparatus; providing for transfer of prescription related data to/from the apparatus using a near field communicator.

20. A method according to claim 19, the method comprising providing for secured transfer of the prescription related data to/from the apparatus using a near field communicator.

21. A method according to claim 19 or 20, comprising providing a communicator for near field communication with a further device.

22. A method according to claim 21 , further comprising providing prescription related data to the communicator for communication with a dispenser for dispensing a prescription using the transferred prescription related data.

23. A method according to claim 22, further comprising receiving at the dispenser prescription related data and corresponding supplementary data from a server so as to provide a prescription.

24. A method according to claim 22 or 23, further comprising providing prescription related data from an authoriser to the apparatus for storing on the data store, the prescription related data for subsequent used by the dispenser for providing a prescription.

25. A method according to claim 24 further comprising providing supplementary data to a server for subsequent use by the dispenser for providing a prescription.

26. A method according to any of the claims 19 to 24, wherein the prescription related data comprises at least one of: drug type; quantity of drug; dosage; name of authorising medical practitioner; other directional information; number of repeats; contact details of authorising surgery; patient details; near field communicator type; length of data; encryption signature; unique tag identifier; prescription issue number; biometric data.

27. A method of providing prescriptions, comprising: receiving prescription related data from a prescription provision tag using near field communication; and providing for dispensing of a prescription based on the prescription related data.

28. A method according to claim 27, wherein the prescription related data is secured prescription related data.

29. A method according to claim 27 or 28, further comprising receiving from a server supplementary data corresponding to the prescription related data so as to provide for dispensing of the prescription.

30. A method of providing prescriptions, comprising: providing prescription related data to a prescription provision tag for storing on a data store for configured for storing prescription related data for subsequent communication to a dispenser via near field communication.

31. A method according to claim 30, wherein the prescription related data is secured prescription related data.

32. A method according to claim 30 or 31, further comprising providing to a server supplementary data corresponding to the prescription related data so as to provide subsequently for prescription details to be accessed by a dispenser.

33. A prescription provision system comprising a tag according to claim 11 and a dispenser according to any of the claims 12 to 14, wherein the tag is configured to communicate prescription related data to the dispenser to allow for provision of a prescription.

34. A prescription provision system according to claim 33, further comprising a server, and wherein the dispenser is configured to receive from the server supplementary data corresponding to prescription related data provided by the tag so to allow for provision of a prescription.

35. A prescription provision system according to claim 33 or 34, further comprising an authoriser, the authoriser configured to communicate prescription related data to the tag for subsequent retrieval by the dispenser for use in dispensing prescription medicine.

36. A prescription provision system according to claim 35 wherein the authoriser is further configured to provide supplementary data to the server, corresponding to prescription related data provided to the tag, for subsequent use by the dispenser.

37. An apparatus for a means for a near field communication module for transferring prescription related data, the apparatus comprising a means for a data store configured for storing the prescription related data, the apparatus configured to transfer the prescription related data to/from a means for near field communication for communication with a means for a further device.