AU2012101981A4 - Medication management - Google Patents

Abstract

Abstract A method of packing medication for a subject, the medication being packed into packaging including a number of receptacles for receiving medication, the method including, in a packing station, determining packing Determine subject 100 data indicative of medication to be packed for the subject, providing an indicative of medication to be packed and, providing an indication of a receptacle into which the medication should be packed, thereby allowing a user to pack the medication into the receptacle in the packaging.

Description

MEDICATION MANAGEMENT

Background of the Invention [0001] The present invention relates to a method and apparatus for managing medication for a subject including a method and apparatus for packing medication for a subject.

Description of the Prior Art [0002] The reference in this specification to any prior publication (or information derived from it), or to any matter which is known, is not, and should not be taken as an acknowledgment or admission or any form of suggestion that the prior publication (or information derived from it) or known matter forms part of the common general knowledge in the field of endeavour to which this specification relates.

[0003] The management of medication for individuals can be difficult, particularly in circumstances when individuals are not able to reliably monitor their own medication. This problem is exacerbated in healthcare scenarios, such as in hospitals, nursing homes or the like, where a large number of individuals may need a range of different medications. In these situations, the healthcare practitioners administering the medication typically have a supply of different medications and a paper based list of the names of individuals and the medication each individual should receive. However, the healthcare practitioner may not always know the individuals, or be familiar with the nature of the medications, meaning there is a significant risk of individuals receiving the wrong medication, which in turn can have serious consequences on the individual’s health.

Summary of the Present Invention [0004] In a first broad form the present invention seeks to provide a method of packing medication for a subject, the medication being packed into packaging including a number of receptacles for receiving medication, the method including, in a packing station:

a) determining packing data indicative of medication to be packed for the subject;

b) providing an indication of a medication to be packed; and,

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

c) providing an indication of a receptacle into which the medication should be packed, thereby allowing a user to pack the medication into the receptacle in the packaging.

[0005] Typically the method includes, in the packing station, providing the indication of a receptacle by selectively illuminating thereceptacle.

[0006] Typically the method includes:

a) positioning the packaging on an array of radiation sources; and,

b) selectively activating a radiation source to thereby illuminate a receptacle.

[0007] Typically the packing station includes a processor, and wherein the method includes, in the processor, selectively activating the radiation sources in accordance with the packing data.

[0008] Typically the indication of a medication includes an image of the medication.

[0009] Typically the method includes:

a) determining a packaging identifier indicative of an identity of the packaging; and,

b) determining the packing data at least in part using the packaging identifier.

[0010] Typically the method includes:

a) determining a subject identifier indicative of an identity of the subject;

b) determining medication data associated with the subject at least in part using the subject identifier; and,

c) determining the packing data at least in part using the medication data.

[0011] Typically the method includes:

a) determining a medication identifier associated with a medication, the medication identifier being indicative of an identify of the medication; and,

b) confirming the medication should be packed at least in part using the medication identifier.

[0012] Typically the method includes, in the packing station, determining when a medication has been packed in accordance with input commands from a user.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-3[0013] Typically the method includes, in the packing station:

a) illuminating the receptacles; and,

b) determining approval of the packing.

[0014] Typically the packaging includes a visual indicator of when medication in each receptacle should be administered.

[0015] Typically the method includes sealing the packaging.

[0016] Typically the packaging includes a base defining the number of receptacles and a cover layer, the method including sealing the packaging by applying the cover layer.

[0017] Typically the cover layer includes a visual indicator of when medication in each receptacle should be administered.

[0018] Typically the packing station communicates with a base station via a communications network to thereby determine the packing data.

[0019] Typically the method includes:

a) using an imaging device to image the packaging; and,

b) storing the image of the packaging.

[0020] Typically the method includes, using a display to display at least one of:

a) an indication of a medication; and,

b) an indication of a receptacle.

[0021] Typically the method includes, in the packing station:

a) determining a packaging identifier;

b) determine packing data at least in part using the packaging identifier;

c) displaying an indication of a next medication to be packed;

d) determining a medication identifier associated with a medication;

e) confirming the medication is the next medication using the medication identifier;

f) illuminating a receptacle into which the next^- medication should be packed; and,

g) determining when the medication has been packed.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-4[0022] In a second broad form the present invention seeks to provide apparatus for packing medication for a subject, the medication being packed into packaging including a number of receptacles for receiving medication, the apparatus including a packing station that:

a) determines packing data indicative of medication to be packed for the subject;

b) provides an indication of a medication to be packed; and,

c) provides an indication of a receptacle into which the medication should be packed, thereby allowing a user to pack the medication into the receptacle in the packaging.

[0023] Typically the packing station provides the indication of a receptacle by selectively illuminating the receptacle.

[0024] Typically the packing station includes an array of radiation sources, each radiation source corresponding to a respective receptacle.

[0025] Typically the packing station includes a processor, and wherein the processor selectively activates the radiation sources in accordance with the packing data.

[0026] Typically the packing station includes a housing having a recess for receiving the packaging, the recess acting as a guide to thereby align the receptacles with the radiation sources.

[0027] Typically the apparatus includes a display for displaying the indication of a medication to be packed.

[0028] Typically the indication includes an image of the medication to be packed.

[0029] Typically the packing station includes a sensing device for sensing identifier data.

[0030] Typically the packing station:

a) determines a medication identifier associated with a medication, the medication identifier being indicative of an identify of the medication; and,

b) confirms the medication should be packed at least in part using the medication identifier.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-5[0031] Typically the packing station includes an imaging device for imaging the packaging.

[0032] Typically the packing station includes a processing system coupled to at least one array, each array including a plurality of radiation sources for selectively illuminating receptacles in packaging, and each array being used for packing medication in respective packaging.

[0033] In a third broad form the present invention seeks to provide a method of managing medication for a subject, the method including, in a processing system:

a) determining a subject identifier indicative of an identity of the subject;

b) determining medication data associated with the subject at least in part using the subject identifier;

c) determining assigned medication associated with the subject using the medication data; and,

d) providing an indication of the assigned medication to a user.

[0034] Typically the method includes:

a) determining subject details associated with the subject at least in part using the subject identifier; and,

b) providing an indication of the subject details to a user.

[0035] Typically the method includes displaying an image of the subject to allow a user to visually confirm the identity of the subject.

[0036] Typically the method includes allowing an action to be performed, the action including at least one of:

a) administering medication;

b) assigning medication;

c) assigning a medication dose;

d) approving medication; and,

e) packing medications.

[0037] Typically the method includes determining an action to be performed using at least one of:

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

a) action data stored in a store, the action data being indicative of actions to be performed; and,

b) input commands from a user.

[0038] Typically the method includes determining whether an action can be performed using at least one of:

a) medication details indicative of any assigned medication; and,

b) subject details associated with the subject.

[0039] Typically the method includes displaying a representation including at least some of the subject details and medication details to allow visual inspection of the displayed subject and medication details.

[0040] Typically the method includes displaying at least one of an image of the subject and an image of the medication to allow visual inspection of at least one of the subject and the medication.

[0041] Typically the method includes:

a) determining completion of an action; and,

b) recording an indication of completion of the action.

[0042] Typically the method includes recording at least one of:

a) the action performed;

b) a date the action was performed;

c) a time the action was performed;

d) a subject identifier indicative of an identity of the subject;

e) a user identifier indicative of an identity of a user;

f) an image indicative of the completed action; and,

g) a medication identifier indicative an identity of any medication.

[0043] Typically the method includes determining a medication identifier associated with a medication, the medication identifier being indicative of an identify of the medication.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-7[0044] Typically the method includes determining whether an action should be performed at least in part using the medication identifier.

[0045] Typically the method includes confirming a medication is an assigned medication in accordance with the identity of the medication.

[0046] Typically the method includes:

a) determining an assigned medication using the medication data;

b) determining a medication identifier associated with a selected medication;

c) comparing the identity of the selected medication to the assigned medication to determine the selected medication is the assigned medication.

[0047] Typically the method includes displaying an image of the assigned medication to allow a visual comparison to be performed by the user.

[0048] Typically the method includes:

a) providing an approval request to at least one approver, the approval request requesting approval of the assigning of medication to the subject;

b) determining approval of the medication request from the at least one approver; and,

c) updating the medication data in accordance with the approval.

[0049] Typically the approval request is indicative of at least one of:

a) an identity of an assigned medication;

b) a dosage of an assigned medication;

c) medication details; and,

d) subject details.

[0050] Typically the method includes:

a) determining a medication request, the medication request being indicative of at least an identity of the subject and a requested medication;

b) providing the approval request to the approver using the medication request.

[0051] Typically the method includes:

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-δα) determining assigned medication at least in part using the medication data associated with a subject;

b) generating packing data in accordance with the determined assigned medication; and,

c) transferring the packing data to a packing station, to allow the medication to be packed.

[0052] Typically the medication is packed in packaging including a number of receptacles, and wherein the packing instructions are indicative of receptacles into which respective medication should be packed.

[0053] Typically method includes, in the packing station, displaying an indication of a receptacle into which medication should be packed to a user thereby allowing the user to pack the medication in the receptacle.

[0054] Typically the packaging includes a visual indicator of when medication in each receptacle should be administered.

[0055] Typically the method includes, in a packing station, applying the visual indicator to the packaging.

[0056] Typically the method includes determining an identifier by:

a) determining identifier data, the identifier data being associated with a respective identifier; and,

b) using the identifier data to determine the identifier.

[0057] Typically the method includes sensing identifier data using a sensing device.

[0058] Typically the method includes retrieving an identifier from a store using the identifier data.

[0059] Typically the method includes sensing subject identifier data based on at least one of:

a) an identification tag; and,

b) a physical attribute of the subject.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-9[0060] Typically the processing system includes a store, and wherein the method includes at least one of storing in and retrieving from the store, at least one of:

a) subject data; and,

b) medication data; and,

c) action data.

[0061] Typically the store is at least one of a memory and a database.

[0062] Typically the subject data is indicative of at least one of:

a) an identity of the subject;

b) subject details;

c) a subject photo;

d) a medical history; and,

e) subject allergies.

[0063] Typically the medication data is indicative of at least one of:

a) an identity of any assigned medications;

b) a timing associated with medication administration;

c) an image of the medication; and,

d) a medication dosage.

[0064] Typically the processing system includes an input device, and wherein the method includes receiving input commands from a user using the input device.

[0065] Typically the processing system includes a processor, and wherein the processor executes instructions stored in a store to cause at least one action to be performed.

[0066] Typically the processing system includes a display for displaying indications.

[0067] Typically the method is performed at least in part using an end station, coupled to a base station, via a communications network.

[0068] Typically the base station includes a processing system and a store.

[0069] Typically the end station includes a processing system having a display.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-10[0070] Typically the end station includes a sensing device for sensing identifier data.

[0071] Typically the method includes, in the end station:

a) determining subject identifier data indicative of a subject identifier;

b) transferring the subject identifier data to the base station via the communications network;

c) receiving an indication of an assigned medication from the base station via the communications network; and,

d) displaying the indication of the assigned medication to a user on a display .

[0072] Typically the method includes, in the end station:

a) receiving subject details from the base station; and,

b) displaying an indication of the subject details to a user on a display.

[0073] Typically the method includes, in the end station:

a) determining medication identifier data indicative of an identity of a medication; and,

b) comparing the medication identifier data to the indication of the assigned medication to determine if the medication is the assigned medication.

[0074] Typically the method includes, in the end station:

a) determining a medication request; and,

b) transferring the medication request to the base station via the communications network, the base station being responsive to the medication request to seek approval for the medication request from at least one user.

[0075] Typically the method includes, in the base station:

a) transferring an approval request to an approver end station via the communications network; and,

b) receiving an approval indication from the approver end station in response to approval by the approver.

[0076] Typically the method includes, in the approver end station:

a) receiving the approval request;

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

b) displaying at least one of subject details, medication details and an indication of a requested assigned medication to the approver; and,

c) generating the approval indication in accordance with a response provided by the user.

[0077] Typically the method is performed using a base station coupled to a packing station via a communications network.

[0078] Typically the method includes, in the base station:

a) determining packing instructions in accordance with medication data and,

b) transferring the packing instructions to the packing station via the communications network.

[0079] Typically the medication management method includes defining at least dose by:

a) determining at least one assigned medication for a subject;

b) determining an indication of when the medication should be administered; and,

c) updating the medication data in accordance with the indication of when the medication should be administered.

[0080] Typically the determination of when medication should be administered is determined in accordance with user input commands.

[0081] Typically the method includes defining a dose administration plan.

[0082] In a fourth broad form the present invention seeks to provide apparatus for managing medication for a subject, the apparatus including a processing system that:

a) determines a subject identifier indicative of an identity of the subject;

b) determines medication data associated with the subject at least in part using the subject identifier;

c) determines assigned medication associated with the subject using the medication data; and,

d) provides an indication of the assigned medication to a user.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

- 12[0083] Typically the apparatus includes an end station, coupled to a base station, via a communications network.

[0084] Typically the base station includes a processing system and a store.

[0085] Typically the end station includes a processing system having a display.

[0086] Typically the end station includes a sensing device for sensing identifier data.

[0087] Typically the apparatus includes a packing station coupled to the base station via a communications network.

Brief Description of the Drawings [0088] An example of the present invention will now be described with reference to the accompanying drawings, in which: [0089] Figure 1 is a flow chart of an example of a process for managing the medication of a subject;

[0090] Figure 2 is a schematic diagram of an example of a distributed computer architecture;

[0091] Figure 3 is a schematic diagram of an example of a processing system;

|0092] Figure 4 is a schematic diagram of an example of an end station;

[0093] Figures 5A to 5C are a flow chart of an example of a process for administering assigned medication to a subject;

[0094] Figures 6A to 6C are a flow chart of an example of a process for assigning medication;

[0095] Figure 7A is a diagram of a first example of a user interface for entering prescription details;

[0096] Figure 7B is a diagram of a second example of a user interface for entering prescription details;

[0097] Figure 7C is a diagram of an example of a user interface for use in defining a dose administration plan;

[0098] Figure 8 is a flow chart of an example of a packing process;

[0099] Figure 9 is a flow chart of an example of a method of packing medication;

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

- 13 (0100] Figures 10A and 10B are schematic plan and side views of an example of a packing station;

[0101] Figures 10C and 10D are images of a specific example of a packing station; [0102] Figure 11 is a flow chart of an example of a process for defining packing data;

[0103] Figure 12A is diagram of a first example of a user interface for use in defining a package layout;

[0104] Figure 12B is diagram of a second example of a user interface for use in defining a package layout;

[0105] Figures 13A to 13C are a flow chart of a second example of a process for packing medication;

[0106] Figure 14 is a flow chart of an example of a process for allowing a subject to review their medication.

Detailed Description of the Preferred Embodiments [0107] An example process for managing medication of a subject will now be described with reference to Figure 1.

[0108] In this example, at step 100 a subject identifier is determined. The subject identifier is indicative of the identity of the subject and can be of any suitable form depending on the implementation. Typically the subject identifier is a unique alpha-numeric code, or similar, which is associated with the subject, such as a healthcare number, a unique identifier assigned to the subject on admission to hospital, or the like. However, this is not essential, and any identifier that allows the subject’s identity to be uniquely determined, such as the subject’s name or the like, could be used.

(0109] The manner in which the subject identifier is determined will vary depending on the preferred implementation. Typically the process is implemented at least in part using a suitably programmed processing system. In this example, the subject identifier can be provided to the processing system by having a user enter the subject identifier via an appropriate user interface, or the like. Alternatively, however, the subject identifier can be determined based on subject identifier data sensed by a sensing device, such as an imaging device, barcode reader, or the like. In this example, the processing system uses the subject

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

- 14identifier data to determine the subject identifier, for example by decoding the subject identifier data using a decoding algorithm, or by retrieving the subject identifier from a store, such as a database, using the subject identifier data.

[0110] The subject identifier and subject identifier data may be the same. However, more typically, the subject identifier data is an encoded version of the subject identifier that is presented in a format capable of being sensed by the sensing device. Thus, for example, the subject identifier data can be in the form of barcodes, which may be sensed using a barcode scanner, radio frequency identification tags (RFID), which may be sensed using RFID scanning technology, or the like.

[0111] Alternatively, the subject identifier data may be biometric data representative of the identity of the subject. Such biometric data may include finger prints, facial attributes, optical characteristics or any other physical attributes that may be used to identify a person. These attributes may be sensed using an image sensor or suitable biometric scanning device.

[0112] It will be appreciated that any other suitable technologies can also be used for sensing identifier data. Although a number of the detailed examples provided below assume that a barcode scanner is used as the sensing device, this is for the purposes of illustrating a possible implementation of the sensing device, but it will be understood that any other sensing device may be used in a similar manner.

[0113] At step 110, the subject identifier is used to access medication data, with this being used to determine assigned medication for the subject at step 120. The medication data, which is typically stored in a store, such as a database, includes details of assigned medication for each of a number of subjects. In particular, this can include information such as active, stopped, and pending medications, or the like, as well as details of the times and days that each medication dose needs to be given to the patient. This process therefore typically involves having the processing system access the medication data and then determine the medication data associated with the subject using the subject identifier and/or identity of the subject.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

- 15 [0114] At step 130 an indication of any medication assigned to the subject is provided to a user, for example by having the indication displayed on a display of the processing system. This allows the user’s, such as nurses, doctors, pharmacists, or any other individual authorised to use the system, to perform one or more actions associated with the management of the subject’s medication, such as administering the assigned medication, changing a subject’s assigned medication, packaging medication for subsequent administration, or the like.

[0115] The medication details can include an image, such as a photo of the relevant medication, thereby allowing this to be easily recognised by the user, so that when performing an action they can ensure this is performed using the correct medication, for example by performing a visual comparison with the displayed image. The medication details can additionally or alternatively be printed as a medication chart, which is a recognised way of representing the active medications for a patient and corresponding scheduled administration times. Typically medication charts only show the medication details along with empty boxes for the nurse to fill out whenever the medication was given. However, by having the dose timing information stored as part of the medication details, for use in dose administration and packing, the system can print a medication chart that specifically shows what times the medications should be given. Similarly, with the dose administration results it can print medication charts that show when the medication was or was not given. This information could also be used as an electronic medication chart displayed on a tablet/pad or bedside device.

By allowing medication data to be accessed based on a subject identifier, this allows the assigned medication for a subject to be easily and reliably determined, thereby ensuring that the medication for the subject is correctly managed.

|0116] In particular, the above described process can help avoid problems related to incorrectly providing medication to the wrong subject, which can in turn have a negative impact on the health of the subject. This process is therefore of particular benefit in scenarios where medication is provided to a number of different subjects on a regular basis, such as in hospital wards, nursing homes, or the like. In such situations, it is easy for the individuals administering the medication to misidentify the medication that should be given to each

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

- 16individual. However, by allowing a user of the system to retrieve and view an indication of the assigned medication, based on a subject identifier, this can help ensure that the medication is administered correctly, particularly when the subject identifier is determined based on identifier data received from a sensing device.

[0117] The above described process also allows other actions associated with the management of medication, such as assigning or altering prescription of medication, entering details of prescribed medications, assigning or altering assigned medications, packing of medication, or the like, to be performed easily using, or by updating, the stored medication data. It will be appreciated that in some examples, the actions can be performed by third parties. Thus, for example, prescribing of medication may need to be performed separately by a suitably qualified medical practitioner, such as a Doctor, pharmacist, or the like, with details of the prescribed medication being added to the system to allow this to be administered to a subject. A number of further benefits and applications will become apparent from the examples discussed in more detail below.

[0118] As mentioned above, the process is performed at least in part using a processing system, such as a suitably programmed computer system. Whilst this can be performed on a stand alone machine, in one example, this is more typically performed by one or more processing systems operating as part of a distributed architecture. An example of a distributed architecture will now be described with reference to Figure 2.

[0119] In this example, a base station 201 is coupled via a communications network, such as the Internet 202, and/or a number of local area networks (LANs) 204, to a number of end stations 203, and optionally to packing stations 205, which will be described in more detail below. It will be appreciated that the configuration of the networks 202, 204 are for the purpose of example only, and in practice the base station 201, end stations 203 and packing stations 205 can communicate via any appropriate mechanism, such as via wired or wireless connections, including, but not limited to mobile networks, private networks, such as an 802.11 networks, the Internet, LANs, WANs, or the like, as well as via direct or point-topoint connections, such as Bluetooth, or the like.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

- 17[0120] In use, the base station 201 includes one or more processing systems 210 that can be used in the process of managing medication, as well as to allow for storing, accessing and updating of relevant data, which is typically stored in a database 211. Whilst the base station 201 is a shown as a single entity, it will be appreciated that the base station 201 can be distributed over a number of geographically separate locations, for example by using processing systems 210 and/or databases 211 that are provided as part of a cloud based environment.

[0121] The end stations 203 and packing stations 205 are typically used to allow remote interaction with the base station 201, for example, to allow users to interact with data stored at the base station 201. Through the use of portable end stations 203 this allows the management process to be performed remotely to the base station 201, allowing the medication management process to be performed in situ.

[0122] In one example, the management process is implemented at least in part using suitable medication management applications software. Whilst this can be executed by each end station 203, more typically this is hosted by one or more processing systems 210, with the end stations 203 being used to allow user interaction with the medication management software, via the communications networks 202, 204. Each end station 203 therefore typically executes applications software allowing communication with the medication management software, such as a browser application, or the like. However, this is not essential and any suitable arrangement may be used.

[0123[ An example of a suitable processing system 210 is shown in Figure 3. In this example, the processing system 210 includes at least one processor 300, a memory 301, an input/output device 302, such as a keyboard and/or display, and an external interface 303, interconnected via a bus 304 as shown. In this example the external interface 303 can be utilised for connecting the processing system 210 to peripheral devices, such as the communications networks 202, 204, the databases 211, other storage devices, or the like. Although a single external interface 303 is shown, this is for the purpose of example only, and in practice, multiple interfaces using various methods (e.g. Ethernet, serial, USB, wireless, mobile networks, such as 3G, 4G, GSM networks, or the like) may be provided.

WO 2012/145789

PCI7AU2012/000432

2012101981 26 Apr 2012

- 18[0124] In use, the processor 300 executes instructions in the form of applications software stored in the memory 301 to allow the medication management process to be performed, or to provide access to any data required by the end stations 203. Accordingly, it will be appreciated that the processing system 300 may be formed from any suitable processing system, such as a suitably programmed computer system, PC, web server, network server, or the like. In one particular example, the base station 201 is implemented as part of a cloud architecture, and it will be appreciated from this that the processing system 210 can be a single processing system or multiple processing systems 210 interconnected by a computer network.

[0125] As shown in Figure 4, in one example, the end stations 203, and optionally the packing stations 205, include at least one processor 400, a memory 401, an input/output device 402, such as a keyboard and/or display, and an external interface 403, interconnected via a bus 404 as shown. In this example the external interface 403 can be utilised for connecting the end station 203 to peripheral devices, such as a sensing device, the communications networks 202, 204, databases 211, other storage devices, or the like. Although a single external interface 403 is shown, this is for the purpose of example only, and in practice multiple interfaces using various methods (e.g. Ethernet, serial, USB, wireless, mobile networks or the like) may be provided. It will also be appreciated that additional hardware components, such as a sensing device, may be incorporated into the end stations 203, depending on the particular implementation.

[0126] In use, the processor 400 executes instructions in the form of applications software stored in the memory 401 to allow communication with the base station 201, to thereby perform aspects of the medication management process. For example, this can be used to allow an operator to interact with medication management applications software hosted by the base station 201 and/or to view or modify data, as will be described in more detail below. Accordingly, it will be appreciated that the end stations 203 may be formed from any suitably programmed processing system, such as a suitably programmed PC, Internet terminal, laptop, hand-held PC, tablet, slate PC, iPad™, mobile phone, smart phone, PDA (Personal Data Assistant), or other communications device.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

- 19[0127] It will be appreciated that one processing system configuration particularly well suited to an environment such as a hospital, nursing home, or the like, will involve the use of end stations 203 in the form of portable hand-held devices, such as tablets and/or smartphones, in wireless communication with a base station 201. Such wireless communications can include cellular networks, such as a mobile network, private networks, such as an 802.11 network, or the like. This configuration allows users to conveniently access management functionalities remotely at the end stations 203 whilst performing their duties, but with storage and heavy processing tasks such as database queries being performed centrally at the base station 201.

[0128] In one particular example, the hand-held devices can include a combination of tablets and/or smartphones. For example, tablets can be provided associated with trolleys that are used for transporting drugs for administration around a ward, whilst smartphones are used by each user of the system, for example when interacting with the patient. However, it will be appreciated that this is for the purpose of illustration only and is not intended to be limiting.

[0129] In one example, the base station 201 is a cloud based server including the processing system 210 and database 211, and end stations 203 are hand-held wireless devices that can display information to, and receive input from, a user via a touch screen based GUI. In particular, the end stations 203 execute local application software to perform user interface functionalities such as presenting options to a user for selection by the user, receiving data input by the user and providing indications to the user. Furthermore, the end stations 203 communicate wirelessly with the base station 201 to provide or receive instructions, requests, or data to the base station 201.

[0130] In one. particular example, end stations 203 each include a sensing device, such as a barcode scanner or image sensor, which allows identifier data to be conveniently determined. In this example, the identifier data can be in the form of a barcode, or any other unique means of identification. It will be appreciated that the particular combination of a hand-held wireless end station 203 with a sensing device allows for the user to conveniently access the management functionalities with a high degree of portability.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-20[0131] In one example usage scenario, a user selects an option displayed on the GUI of a hand-held end station 203, such as an option to administer medication. The user is then prompted to enter or use the sensing device to sense respective identifiers or identifier data as required. If the end station 203 is equipped with a sensing device, the user can simply sense corresponding unique identifier data, such as barcodes, to allow the identifiers to be easily determined. The end station 203 then communicates with the base station 201 as required to retrieve data from the base station 201 or to request that the base station 201 performs processing, or the like. For example, the end station 203 may transmit the subject identifier to the base station 201 and request that the base station 201 provides an indication of the assigned medication.

[0132] In one example, end stations 203 may be provided as computer terminals to allow the use of other user interfaces, such as a keyboard and mouse, and the display of increased volumes of information to the user on a screen having a larger size than the hand-held devices, via a web interface, or the like. A computer terminal of this type may be used to retrieve detailed reports on the history of actions performed, for example to view audit reports, perform stock audits, or the like. In one example, such a computer terminal allows direct queries of the database 211 by the user. A combination of hand-held devices and computer terminals may be used to allow the respective benefits or each type of end station 203 to be realised.

[0133] It will be appreciated that any appropriately configured end stations 203 may be used to deliver similar functionality, and these may be provided as off shelf devices such as mobile phones, PDAs, laptops, tablet computers or the like, or as custom-designed devices.

[0134] It will also be appreciated that the partitioning of functionality between the end stations 203 and base station 201 may vary, depending on the particular implementation. In this regard, the end stations 203 may be simplified to provide a user interface only, and in this case the base station 201 may handle the majority of processing tasks. On the other hand, the end stations 203 may be equipped with substantial processing power, such that the base station 201 merely acts as a database server for providing required information to the end stations 203 for remote processing. It will also be appreciated that a single processing system

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-21 incorporating functionality of the end station 203 or packing station 205, and the base station 201, may be used.

[0135] In any event, the medication management process is not particularly limited by the hardware implementation, and the skilled person will understand that variations in the processing system configuration will be possible.

[0136] In the following specific example processes, it will be assumed that the user uses a hand-held end station 203 and interacts with application software executed by the end station 203 via a touch screen based GUI, or the like. Actions performed by the end station 203 are performed by the processor 400 in accordance with instructions stored as applications software in the memory 401 and/or input commands received from a user via the I/O device 402. It will also be assumed that the hand-held end stations 203 include a sensing device for sensing identifier data. In particular, a barcode scanner will be used throughout the detailed examples, although it will be appreciated that any sensing device, such as a camera built into the hand-held device, along with appropriate image processing software, near-field RFID, or the like, can be used. Similarly, it will be appreciated that the use of hand-held devices is for the purpose of example only.

[0137] The base station 201 is a server which communicates with the hand-held end stations 203 via a wireless LAN, mobile networks, or the like, and the computer terminal end station 203 via a wired or wireless LAN, mobile networks, or the like, depending on the particular network infrastructure available. In the following examples, it is assumed that the processing system 210 of the base station 201 hosts a medication management application that performs a majority of the processing tasks, with the end stations 203 being used primarily to provide the user interface. Actions performed by the processing system 210 are performed by the processor 300 in accordance with instructions stored as applications software in the memory 301 and/or input commands received from a user via the I/O device 302, or commands received from the end stations 203.

[0138] However, it will be appreciated that the above described configuration assumed for the purpose of the following examples is not essential, and numerous other configurations may be used.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

- 22 [0139] For the purpose of the following examples, it will be assumed that the management process is carried out by a user, such as a medical assistant, who is managing medication for a subject, such as a patient.

[0140] An example process for administering medication will now be described with reference to Figures 5A to 5C.

[0141] In this example, the user accesses the management application using the end station 203. As part of this process the user may be required to undergo an authentication process, for example by having the user supply a username and/or password, thereby allowing the medication management application to verify the user is authorised. This can be used to prevent unauthorised access to information, such as subject and/or medication details, as will be appreciated by persons skilled in the art. This can also be used to identify the user for other purposes, for example for auditing purposes, as will be described in more detail below, or for customising operation of the system, for example by customising the interface that is presented to the user. This can allow the options presented to the user to be configured for that user, and the actions they may perform. For example, this allows the system to predict what ward to select for dose administration based on where the user works.

[0142] It will be appreciated from the above that any suitable technique for identifying the user could be used. For example, on an end station 203 such as a phone, it can be difficult to enter a username and password using small touch screen based keyboards. Accordingly, as an alternative, gesture recognition can be used in which a user can draw a symbol and the system can recognise that the sequence and accuracy of symbol strokes entered matches a previously registered symbol for the user. This is particularly attractive for Asian cultures where a Chinese character can be used at the login. Alternatively the user can just enter a PIN using an onscreen numeric keypad. In both instances the user and end station 203 would have initially been paired (i.e. by entering a username and PIN, or a username and symbol on that end station 203). This stops someone from picking up any end station 203 and entering any PIN and being able to login, they would have to enter a PIN that has previously been entered on that end station 203. The user can alternatively scan a barcode or RFID tag on their ID badge to login.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-23[0143] The management application causes the end station 203 to display a list of available management actions at step 500, for example determined from action data stored in a store such as the database 210. The action data is indicative of different actions that can be performed, such as administering medication, assigning medication, assigning a medication dose, approving medication and packing medications, and typically specifies a sequence of steps to be performed in order to allow each action to be completed. At step 505, the user selects an administer assigned medication option, with an indication of the selected action being provided to the management application implemented by the processing system 210.

[0144] It will be appreciated that the above described step may not however be required. For example, when the user logs in, there may only be one action the user can perform, in which case this action will automatically commence. Alternatively, by identifying the user, the processing system 210 may determine an action that the user needs to perform, such as dose administration, and cause this action to be automatically selected. Similarly, if dose administration is being performed on a ward, the processing system 210 can automatically determine the ward and round based on the user who logged in and the time of day.

[0145] At step 510, the management application prompts the user to use the end station 203 to sense subject identifier data, which in one example is provided on a tag worn by the subject, such as a wristband. The tag includes a visual or other detectable representation of the subject identifier, such as a barcode, RFID tag or the like, allowing the end station 203 to sense the subject identifier, with corresponding subject identifier data being transferred to the processing system 210 at step 515.

[0146] Alternatively, however, this could be performed by having the processing system 210 use the indication of the ward and round, determined as described above, and use this information to present the user with a short list of subjects to whom medication needs to be administered on this ward, at this time. This list contains the subject photo, name, ward, room, and bed and can be sorted by subject name, or by their room and bed numbers, or by the order in which they were previously dosed in the past, or by a preconfigured route through the ward. The user can then select a subject directly from this list without having to use a search or barcode scanner. Alternatively, the user can manually search for a subject based on their name. Accordingly, whilst the barcode scanner is particularly advantageous as

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-24it ensures the subject is correctly identified, alternative mechanisms to determine the subject identifier can be used.

[0147] The processing system 210 uses the subject identifier data to determine the subject identifier, and then uses this to access subject data and medication data for the subject at step 520. The subject and medication data are typically stored in a store, such as the database 210, and is generally created during an initial set-up process. The subject data can include, but is not limited to subject details, such as the subject’s name, age, photo, medical history, details of any allergies, notes relating to administration of medication, details of the subject’s location (eg: hospital and ward) or the like. The medication data typically includes, but is not limited to, details of any assigned medications for the subject, together with associated dosing information. It will be appreciated that the subject data and medication data are typically stored together with the subject identifier of the associated subject, allowing the data to be accessed using the subject identifier. Whilst separate subject and medication data are described, this is not essential, and it will be appreciated that the medication data may form part of the subject data.

[0148] At step 525, subject and medication details are transferred to the end station 203 allowing these to be displayed to the user at step 530, as part of a user interface. In one specific example, first the subject data is displayed, including the subject’s photo, allergies and administration notes. Following this, the user can continue or choose not to administer anything. For example, the photo of the subject is displayed to the user to allow the user to perform a visual comparison of the subject with the photo, thereby ensuring that the subject and medication details selected correctly correspond to the actual subject. By providing this information to the user at the point at which the medication is administered, this allows the user to perform a visual comparison just before administration, vastly reducing the chance of medication being incorrectly administered to the wrong subject. Assuming the user continues however, the medications that are to be administered can then be displayed.

[0149] In any event, the above allows the user to view the subject details, such as the subject’s medical records and details of any allergies, or the like, allowing the user to make an assessment if there is any reason why the medication should not be administered. This can include, for example, reviewing historical information, such as the amount of medication

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-25administered over the past 24 hours, the last time the medication was administered, or the like.

[0150] In addition, this allows the user to view details of the medication, allowing them to ensure that the correct medication is administered. Additionally, administration notes may also be displayed which give the user information on how to administer the medications. For example, an indication that “subject has difficulty swallowing” implies that the user may need to crush the tablets and mix in a glass of water, or possibly use a feeding tube.

[0151] To allow additional checking to be performed, at step 535 the user can use the end station 203 to optionally sense medication identifier data provided on the medication, in a manner similar to that described above with respect to the subject identifier data. Accordingly, the medication identifier data can be encoded on the medication in the form of a printed barcode, RFID tag or similar. In one example, the medication identifier is a packaging identifier associated with a particular package of medication, such as a blister pack or pill box, including a number of different medications for administering to the user, as will be described in more detail below.

(0152] As an alternative to sensing a medication identifier, this can be determined using other techniques, such as manual input of the identifier by the user, or by having the end station 203 display a list of medications to be administered, allowing the user to select the relevant medication from the list. Thus, whilst sensing the identifier is generally preferred to ensure accuracy, it will be appreciated that other techniques for determining the identifier can be used.

(0153] The end station 203 transfers the medication identifier data to the processing system 210 at step 540, allowing the processing system to determine a medication identifier indicative of the identity of the medication at step 545. In one example, the identity of the medication can be a medication type, however alternatively the identity can be uniquely indicative of a respective medication batch, or the like. For example, the user may scan a packaging identifier, which is then indicative of the multiple medications provided in the package.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-26[0154] At step 550, the identity of the medication is compared to the medication assigned to the subject, as determined from medication data. This comparison can be performed either in the processing system 210 or the end station 203.

[0155] The comparison is used to ensure the medication is the assigned medication, and in the event that medication is incorrect, an indication of this is typically provided to the user in the form of an alert displayed on the end station 203, at step 560. In the event that this occurs, this allows the process to return to step 535, with the user selecting an alternative medication and repeating steps 540 to 555 until the correct medication is selected.

[0156] If a number of medications are assigned to the subject, the above described process can be performed a number of times to allow all the relevant medications to be determined, so that these can be administered to the subject collectively. As an alternative to scanning each medication separately, the medication can be provided in a pack, such as a blister pack, so that the user need only scan the packaging a single time to determine a packaging identifier, which in turn allows all the relevant medications in the pack to be identified.

[0157] Whilst the above described process involves sensing a medication identifier and then allowing the base station 201 to determine the medication is correct, this is not essential. In an alternative process, the medication details uploaded to the end station 203 can include the medication identifiers of the medications to be administered. Accordingly, this allows the end station 203 to perform the comparison itself, thereby avoiding the need for further communication with the base station 201.

[0158] Once the user has correctly selected all the medications to be administered, the user administers the medications at step 565. During this process, the user may make use of administration notes displayed to the user on the end station 203, as well as an image of the medication being administered. Again, this allows the user to visually compare the selected medication to the medication shown in the photo, allowing the user to assess whether the correct medication is being administered. It will be appreciated from this, that displaying a photo of the subject and the medication they are to receive can significantly increase the safety of the administration process, in particular reducing administration errors and the required skill level of the administration staff.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-27[0159] So, for example, if a blister pack containing a number of medications to be administered is used, the administration notes can include a graphical representation of the blister pack, showing the respective receptacles within the pack within which the medication to be administered is provided. In this instance, the user can typically select each receptacle on the graphical representation, allowing the contents of each receptacle to be shown. This allows the user to identify the medication provided therein, which can be used for example to provide an indication of whether medication is taken, as described below.

[0160] At step 570 the user can optionally provide an indication that the medication has been administered, for example by selecting an administration complete indication presented on the user interface by the end station 203. In one example, the user may be required to initial or sign an administration record using an electronic signature capture system on the end station 203, thereby proving the medication has been administered.

[0161] Additionally, the user may be presented with other options. This can include, for example, indicating if the wrong medication has been chosen, or allowing other actions to be requested, for example to allow an independent healthcare professional, such as a Doctor, to be consulted or to allow alternative medication to be assigned. It will be appreciated from this, that the workflow can therefore link with the workflows described in other flow charts as required.

[0162] As a further alternative, this can be used to allow the user to indicate if a medication was not taken for any reason, or to indicate an actual dosage value that has been administered, for example if this differs to an intended dose (i.e. the patient was supposed to take two but only wanted to take one).

[0163] In one specific example, the end station 203 displays to a user all medications that are supposed to be administered to the subject. In this example, the user can use the touch screen to selectively highlight any one of the medications. The user therefore highlights all the medications they are giving the subject and selects “done” to complete the process, and update the base station 201 accordingly. If any medications were not highlighted they will be prompted for a reason why that medication was not administered (e.g. refused, vomiting, etc.).

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-28[0164] At step 575 the end station 203 provides confirmation to the processing system 210, allowing the processing system to record that the medication has been administered at step 580.

[0165] The process of recording completion of the action can be performed by updating data stored in the database, such as the medication data, subject data or the like. The process of recording completion typically involves recording details such as the action performed, a date or time at which the action was performed, the subject identifier of the subject, a user identifier indicative of an identity of the user performing the action and a medication identifier indicative the medication administered. It will be appreciated that any other relevant information may also be recorded.

[0166] At this point, for any medications that were not administered an alert can optionally be sent to predefined recipient, such as a pharmacist, or predefined group of recipients, such as a pharmacy department, to notify them that a medication was not taken. This could be achieved in any manner, such as via email or directly to their smartphone using SMS or an alert application. This would typically be configured based on a specific patient, and/or a specific medication, and/or a class of medication. Additionally, the system can send an alert even if the user had not recorded that the medication was not administered, i.e. if the patient was missed or that round was missed and a specific period of time had elapsed, the system would automatically generate a missed dose alert.

[0167] Recording that medication has been administered (or has not been administered for any reason) is useful for auditing purposes, for example to determine the cause of an adverse reaction to medication, or the like. In particular, this can be used to generate reports, for example to view the dosing history or missed doses for individual patients, wards, or institutions. Usage reports can also show the total amount of medications administered to patients in comparison to medication supplied. Furthermore, records of administered medication can also be used for billing purposes, for example to bill users for medication.

[0168] The above described process applies to regular medications, however a very similar process can be used for missed medications, PRN medications, and imprest medications. Medications that were missed in previous rounds may or may not need to be

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-29given in this round to catch up, the process can show medications that were previously missed and the user can choose whether to give them or not (depending on user permissions this option may not be available). PRN medications are taken as required, for example, the patient can have medication (such as a pain killer) that is given only when symptom arises. The system will present the user with available PRN medications and the user can choose (or scan) which ones to give and how much to give now. In such scenarios, it is useful to know how much has been given in the last 24 hours as there is usually a maximum limit that should not be exceeded. Imprest medications typically exist in an imprest cupboard on the ward and are available to treat specific common conditions (e.g. vomiting), often a nurse is allowed to give an imprest medication without any prior entry into the system for that patient. The system will present them with a list of on hand imprest items which the user can choose (or scan) which one to give and specify how much to give. Some imprest items may be restricted to different user permission levels.

[0169] Accordingly, the above described process can be used to ensure that medication is administered to a subject as intended, for example by a medical professional thereby avoiding the problems associated with incorrect administration of medication to a subject. Additionally, details of the completed administering process can be subsequently reviewed as required, allowing the cause of any problems associated with the administering of medication to be identified, and subsequently addressed, for example by modifying the medication assigned.

[0170] An example of a process for assigning medications will now be described with reference to Figures 6A to 6C.

[0171] As in the previous example, the user initially accesses the management application using the end station 203, causing the end station 203 to display a list of available management actions at step 600. This would usually include the step of identifying the user, for example by having the user undergo authentication by the system, for example by providing a username and password, predetermined input gesture, PIN, or the like, as described above.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-30[0172] At step 605, the user selects an assign medication option, before sensing the subject identifier data, to determine the subject identifier at step 610.

(0173] At step 615, if the medication to be assigned is available, the user can use the end station 203 to optionally sense medication identifier data provided on the medication, in a manner similar to that described above. Alternatively, the user may identify the medication in some other manner, such as by inputting an indication of the identity of the medication via a suitable user interface, selecting medication from a list of available medication, or the like, as will be appreciated by persons skilled in the art.

[0174] At this stage, the user will also typically provide additional information such as who initiated the new medication, route of administration (if not implied, e.g. intramuscular, subcutaneous), and dosing instructions. The dosing instructions are an indication of when a particular dose of medication should be taken. The dosing instructions are entered via a user interface that prompts the user to indicate the timing and dose.

[0175] Other additional attributes that can also be optionally set include starting date, stop date, additional instructions (e.g. take with food), whether this is a PRN medication, whether it should be included in a blister pack, and the initial quantity on hand so that quantities can be tracked for reordering. Additionally, the user can specify whether the medication needs approval or already has approval, such as via an existing paper prescription.

[0176] An example of a user interface for entering medication details will now be described with reference to Figure 7A.

[0177] It will be appreciated that the particular interface shown is for the purpose of example only, and is not intended to be limiting. Although the interface is indicated to be for prescription entry, it will be appreciated that this is also for the purpose of example only and is not intended to be limited to prescribed medications. In particular, the user interface can be used to enter details of an already prescribed medication, or to generate a request for a medication to be prescribed, or otherwise assigned to a subject. Furthermore, although the interface is intended for use with a subject that is a patient, this is again not intended to be limiting, and the term patient will therefore be understood to include any subject.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-31 [0178] In this example the user interface 700 includes an actions menu 710 including action icons corresponding to different actions that can be performed. This allows the user to select between different actions, such as assigning a medication, administering medications, packing medication, or the like. .

[0179] The user interface 700 also includes a patient details window 720 which displays patient details for a currently selected patient. In this example, a name, photo, age, height, weight and date of birth are shown, although this is not essential, and any suitable patient details may be displayed. The user can then select a drug to be administered to the patient, either by entering details in a new drug window 730, or performing a search, for example from a list of available drugs. Alternatively the user may scan a medication identifier, as described above.

[0180] Information regarding assignment of the drug to the patient will then be displayed in the prescription window 740. This can include any one or more of the current date, an indication of the start date on which medication is to be administered and optionally, a stop date and quantity to be supplied. The name of the prescriber or initiator is also shown. The prescriber could be the doctor that has previously generated the prescription being entered, or could be the initiator making the current request. If there is a previous prescription, this will include a unique “Rx” or prescription number, which can be entered by the user. Otherwise, an Rx number can be automatically generated by the processing system 210. PRN dosing can be performed by selecting a PRN indication 741. It will be appreciated from this that the term prescription window applies equally to medication that is assigned but not necessarily prescribed, such as over the counter, herbal, traditional, alternative, and complementary medications.

[0181] Dosing information can then be entered via a dosing window 750. In the example of Figure 7A the user can enter the dose, or number of capsules, in a dose field 751 and any repeat information in a repeat field 752. A delivery route will typically be indicated in a route field 753 with any additional directions being specified in a field 754. In addition to this, the dosing window 750 includes a dosing table 755 setting out when doses should be taken. In entering a dosage into the dosage table, the user can simply select an appropriate

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-32entry using the touch screen and then use appropriate inputs to increase or decrease the medication to be taken at the specified time.

[0182J By selecting an input button 756 the user can switch to an alternative view shown in Figure 7B. In this example, the table 755 is omitted, whilst information is entered as a number of capsules or milligrams to be taken with timing and additional directions then being set.

[0183] In any event, directions for taking the medication, based on the entered information can then be generated automatically as shown at 758.

[0184] The user can then indicate using an approval window 760 whether approval is requested at 761, whether a paper prescription has previously been generated at 762, in which case approval is not required, or whether this is a non prescription drug request at 763, for example if the medication is over-the-counter, herbal, complementary, traditional, or the like. It will be appreciated from this that the dosing information may be based on a previously issued prescription. Alternatively, the dosing information can be proposed by the user, in which case this will typically have to be checked by a suitably qualified individual to make sure the proposed dosing is appropriate.

(0185] In any event, the dosing information can be interpreted by the processing system 210, and used to automatically set up the dose timings to be used during a packing process, described in more detail below, and by the above described administration process.

[0186] At step 620, the end station 203 transfers a medication request to the processing system 210. The medication request typically includes an indication of the subject identifier, and either the medication identifier, or an indication of the medication to be assigned, as well as additional information, such as dosing information, supplied as described above.

[0187] At step 625, the processing system 210 access the subject data and medication data associated with the subject, using the subject identifier, allowing subject and medication details to be determined.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-33[0188] At step 630, it is determined if approval for the medication and/or dosing has previously been provided. If so, then the process proceeds to step 670 to update the medication data associated with the subject. Otherwise, at least one approver is determined by the processing system 210 at step 635. The approver is an individual that is authorised to approve the assigning of medication and may therefore be a medically qualified individual, such as a doctor, pharmacist, or the like. Details of available approvers, such as contact details including phone numbers, emails, addresses, or the like, are typically stored in the database 210 and may be stored together with criteria specifying the type of approvals they are authorised to provide. Thus, for example, the approver selected may depend on the subject to whom the medication is to be assigned, the type of medication or the like, thereby ensuring the approver is able to approve the assigning of the particular medication to the respective subject.

[0189] At step 640, an approval request is transferred to the approver, for example by forwarding the approval request to an end station 203 used by the approver. This may occur for example by having an email or other notification transferred to the approver’s end station 203, allowing the approver to access the management application and view the approval request. The approver will typically need to undergo authentication, for example by providing a username and password, predetermined input gesture, PIN, or the like, in a manner similar to that described above.

[0190] The approval request typically includes any information required to prescribe, or otherwise assign, the medication to the subject, such as subject details, details of any existing assigned medications, subject symptoms, and details of the medication for which the current request is made. However, alternatively, this information may be made available by having the approver access this via the management application. In any event, this information allows the approver to ensure that the medication being requested is both suitable for the individual, for example taking into account the subject’s medical history including allergies, symptoms, or the like, as well as to ensure it will not adversely react with existing assigned medications.

[0191] At step 645, the approver reviews the approval request and assesses whether the medication is to be assigned. As part of this, at step 650, the approver may determine that

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-34additional consultation is required, in which case the approver will consult with one or more other individuals at step 655. This may be required, for example to allow the approver to consult with a pharmacist, specialist, or the like, to thereby ensure that assigning the medication is appropriate.

[0192] At step 660, assuming approval is granted, the approver provides an approval indication via their end station 203, together with any required dosing information, such as the dose, frequency and timing with which the medication should be administered, if this has not already been provided, or if this requires alteration.

[0193] It will be appreciated that in the event that approval is not provided, the user requesting the approval will typically be informed, allowing intervention to be provided, such as by having the subject attend a consultation with a medical practitioner, thereby allowing a prescription to be provided in the normal manner.

[0194] Assuming approval is provided, the approval indication is transferred to the processing system 210 at step 665, allowing the processing system 210 to update the medication data associated with the subject at step 670. This ensures that when medication is administered to the subject in future using the process of Figures 5A to 5C, this is performed in accordance with the updated medication data, thereby ensuring the newly assigned medication is administered.

[0195] As in the previous example, details of the completion of the approval process can also be recorded, for example by recording details of the user making the medication request, details of the approver, and any other relevant information. This again allows an audit trail of the assigning of medication to be established, allowing this to be reviewed in the event that any adverse outcomes are experienced.

(0196] At step 675, a medication notification may be optionally sent to a pharmacist, for example by having the processing system 210 generate a prescription request, which can be electronically transferred to the pharmacist via an end station 203. This can be used to ensure that the medication is available the next time medication is to be administered to the subject. Similarly this notification may let the pharmacist know that they should access the

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-35management application and configure the dose timings, for example through the creation of a dose administration plan at step 680. As part of this process, the pharmacist will be authenticated by the system, for example by having the pharmacist provide a username and password, predetermined input gesture, PIN, or the like.

[0197] An example of a dose administration plan is shown in Figure 7C. In this example, the dose administration plan is presented by a user interface 700 including an actions menu 710 as in the previous example.

[0198| The dose administration plan interface includes a patient details window 720, showing details of a subject, such as a currently selected patient. A medication window 770 is provided including a list of medications current assigned to the user at 771, allowing the user to select a particular medication from the list 771, with information regarding the selected medication being shown at 772. The user then determines when the medication is to be administered to the subject, and provides an indication by selecting a cell 781 in a dosing table 785 shown in a dosing window 780.

[0199J This allows users to review details of each of the medications currently assigned to the patient, and then provide an indication of the time and date on which dosage should be provided using the dosing window. This can be achieved by simply clicking on cells in the dosing window to increase the number of doses assigned to each cell. Alternatively, the user can use input buttons, shown generally at 782, allowing dosages within any given cell to be increased or decreased as required.

[0200] It will be appreciated that in one example, the dosing table 785 can be automatically populated, based on population of the dosing table 755 described above with respect to Figure 7A. In this instance, population of additional drugs can be performed, as well as altering the administration timing and/or dose of drugs, if required.

[0201] The dose administration plan is defined by the pharmacist in this example. This allows the pharmacist to take into account interaction between different assigned medications, as will be appreciated by persons skilled in the art. However, this is not

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-36essential, and alternatively, the dose administration plan can be defined by any suitably qualified user.

(0202] At this stage, the pharmacist may go on to generate packing instructions, in the form of packing data, thereby allowing blister packs containing multiple medications for a subject to be created. This process will be described in more detail below with reference to Figure 11.

(0203] Once the dose administration plan is defined at step 685, details of the dose administration plan can be returned to the processing system 210, allowing the processing system to update the medication data associated with the user at step 690.

(0204] At this stage, notifications may also be sent to other users at step 695, for example if they also choose to receive alerts when a specific patient’s medications are changed, regardless of whether they need to perform any actions.

(0205] Accordingly, it will be appreciated that the above described process can be used to assign new medication, or alter existing medication, with the changes being automatically approved and updated in the medication data, thereby ensuring the newly assigned medication is administered appropriately.

(0206] An example of a process for packing medications will now be described with reference to Figure 8.

[0207] For the purpose of this example, it is assumed that the medication is to be provided in a packaging that includes information indicating when medication is to be taken. This can be for example in the form of a blister pack, pill box, or other similar arrangement, which includes separate receptacles for different medications, and which includes indications indicating when the medications in each receptacle are to be taken. This allows medications to be provided to the subject in accordance with a particular timing sequence, thereby allowing a subject to more easily adhere to a medication regime.

[0208] In this example, at step 800 packing data is prepared. The packing data typically specifies how the medication should be packaged in the packaging, and in particular specifies

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-37a receptacle within the packaging into which each type of medication is to be packed. The packing data may be defined in any suitable manner, but typically involves using one of the processing systems 210, end stations 203 or a packing station 205, and optionally a dose administration plan, to define where in the packaging particular medications should be packed, thereby ensuring the are administered at an appropriate time.

[0209] Depending on the quality of the dosing information provided during the process of Figures 6A to 6C, it is possible in some situations to automatically derive the packing information from the dosing information. Accordingly, in most cases this can be performed automatically, for example using the processing system 210, and requires no human intervention. However, this is not always the case, and in some examples manual input is required, particularly to perform activities such as splitting up packs if there are too many medications to physically fit in one pack. It will also be appreciated that packing data may only need to be generated when a medication is added, changed, or stopped for a patient. Once the packing information is set up, that same information can be used every week/month to pack packaging as required.

[0210] At step 805, the packing data is used to pack the medication into packaging, using one of the packing stations 205. The manner in which this is performed will depend on the preferred implementation. For example, this could be performed automatically using a suitable packing machine. More typically however this is performed as a manual process, with a user being guided to perform the packing, as will be described in more detail below.

[0211] At step 810, the packaging may optiorially be checked to ensure packing has been performed correctly. In one example, the packing is checked by an individual other than the packer to thereby help ensure that packing is correct. This is particularly important in the event that the user performing the packing at step 805 is a relatively unskilled worker, in which case oversight by medically qualified personnel may be mandatory, or at very least desirable, to ensure packing is error free, and to allow errors to be corrected as required.

[0212] At step 815, following confirmation that packing is correct, the packaging is sealed, before being provided to a user or subject, thereby allowing the medication to be administered as part of the above described process at step 820. It will be appreciated that

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-38packaging may be sealed before or after checking, depending on the preferred implementation.

[0213] It will also be appreciated that the packs may be prepared off site (e.g. at a pharmacy), in which case, the packs may then need to delivered. This is particularly feasible given the distributed nature of the architecture used, which allows data, such as dosing information or packing data to be transferred to a packing location, as required. Shipping of packaged medication can involve putting the packs in boxes, confirming shipment of the boxes, confirming receipt of the boxes at the facility, confirming receipt of the packs, or the like.

[0214] An example of the packing step 805, as performed manually using a packing station 205 will now be described in more detail with reference to Figure 9. For the purpose of this example, it is assumed that the user has been authenticated by the system, for example by providing a username and password, predetermined input gesture, PIN, or the like, via the packing station 205, and is authorised to perform packing of medication.

[0215] In this example, at step 900, the packing station 205 determines packing data. Whilst this may be performed in any suitable manner, this typically involves retrieving previously generated packing data from a store, such as the database 211. The packing data can be retrieved in any suitable manner, but can include, for example, sensing a packaging or subject identifier provided on the packaging, select from a list of packs to be packed, search for the subject by name and select from a list of packs, or the like.

[0216] At step 905, the packing station 205 provides an indication of a medication to be packed. The indication is typically provided to a user via a display, or the like, allowing the user to visually identify the medication, although any suitable technique may be used. In one example, the indication of the medication can include an image of the medication, allowing visual confirmation by a user that the medication selected for packing is correct.

[0217] At step 910, an indication of the receptacle into which the medication is packed can then be provided to the user, allowing the user to provide the medication in the correct receptacle. This can be performed in any suitable manner, such as by having the packing station 205 present the indication on a display. In this instance, the indication is typically in

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-39the form of a representation of the packaging with a particular receptacle highlighted to thereby indicate the receptacle into which the medication should be packaged.

[0218] It will be appreciated that the above described process can therefore display an image of the particular medication to be packed, together with an indication of where the medication should be provided in the packaging. This allows the user to perform a visual comparison of the medication with the medication image, and the packing location with the packing indication. This significantly reduces errors associated with the packing process, and reduces the required skill of the packer. By reducing the skill required for mundane tasks, skilled staff are freed for tasks requiring decision making, or the like, thereby making the overall process more efficient.

[0219J In this example, the packing station 205 generally includes functionality similar to that of one of the end stations 203, and this will not therefore be described in further detail.

[0220] However, simply presenting a representation of the packaging can still lead to packing errors. Accordingly, more typically the packing station 205 includes an array onto which packaging can be positioned. In this example, the array can be selectively illuminated to allow individual receptacles within the packaging to be identified, thereby allowing a user to ensure different medications are correctly provided into the correct receptacles. An example of such a packing station 205 will now be described with reference to Figures 10A to 10D.

[0221] In this example, the packing station 205 includes a housing 1000 incorporating a display 1010, as well as a processor 1011, memory 1012 and an interface 1013, interconnected via a bus (not shown). The packing station 205 also includes an array 1020, provided in an array housing, including a number of radiation sources, such as LEDs (Light Emitting Diodes) 1021, although other sources of visible radiation can alternatively be used. The array 1020 defines a recess 1022, which in use can receive packaging 1030, such as the base of a blister pack or similar. The packaging 1030 includes receptacles 1031, which when the packaging is positioned is in the recess 1001 align with the LEDs 1021, so each LED 1021 can illuminate a respective receptacle 1031.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-40[0222] The array 1020 may also include an arm 1023 having an imaging device, such as a camera 1024, mounted thereon. The camera is designed to allow the array 1020, and in particular the packaging 1030, to be imaged during the packing process, thereby allowing the packing process to be tracked. In one example, the camera 1024 can capture a low resolution video throughout the whole packing process, with the camera taking a high resolution image when the user indicates that an individual medication has been packed, or when all packing is complete. Thus, the process can store an image associated with a completed action, in this case packing of the medication, allowing this to be subsequent reviewed, for example to ensure the correct medication was indeed packed. The video and the photos can also be used for auditing, training or the like.

[0223] In addition, in another example, the LEDs 1021 can be modulated to allow changes in an individual receptacle to be detected using the camera 1024. This can be used in conjunction with video processing technology to allow a degree of automated checking to be performed, for example to detect if filled receptacles should be empty, or vice versa. The modulation of the LEDs 1021 can also be used to detect whether the user is somehow blocking the view of the pack so that the high resolution photo is only taken when all of the packaging receptacles are visible.

[0224] In one example, arrays 1020 can be wirelessly connected to the packing station 205, for example using Bluetooth or the like. Accordingly, it will be appreciated that the arrays 1020 may also include a processor, memory, and interface (not shown for clarity), to allow communication with the processor 1011, as well as to allow commands provided by the processor 1011 to be interpreted, and actions to be performed, such as illuminating respective LEDs 1021. It will be appreciated that in this example, as the LED array is connected via Bluetooth, the packing station can be implemented in the form of a standard hardware device, such as a suitably programmed smartphone, tablet/pad, or laptop which can connect to a LED array, thereby significantly reducing implementation costs.

[0225] In a further example, a single packing station 205 can be used to control multiple arrays 1020, allowing the user to pack multiple packs at the same time. This can be used to allow multiple packs to be packed for a single subject, at the same time, which can be useful when using unit dose packs (i.e. one pack for breakfast, one pack for lunch, one pack for

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-41 dinner, etc.), and which can also significantly increase the efficiency of the packer, for example by allowing multiple identical packs to be packaged simultaneously.

[0226] In the above example, the external interface 1013 can be utilised for connecting the packing station 205 to peripheral devices, such as a sensing device for sensing identifiers, the communications networks 202, 204, databases 211, other storage devices, or the like. Although a single external interface 1013 is shown, this is for the purpose of example only, and in practice multiple interfaces using various methods (e.g. Ethernet, serial, USB, wireless, mobile networks or the like) may be provided. It will also be appreciated that additional hardware components, such as a sensing device, or camera 1024 may be incorporated into the packing station 205, depending on the particular implementation.

[0227] In use, the processor 1011 executes instructions in the form of applications software stored in the memory 1012 to allow communication with the base station 201, to thereby allowing the packing process to be performed. For example, this can be used to allow an operator to access packing data, view indications of medication to be packed on the display 1010, interact with medication management applications software hosted by the base station 201, or the like. In addition to this, the processor 1011 is adapted to control the LEDs 1021, allowing the LEDs 1021 to be selectively activated in accordance with the packing data, thereby allowing the receptacles 1031 to be illuminated when medication is to be provided therein.

[0228] The functionality of the packing station 205 is broadly similar to that of the end stations 203, albeit with the addition of the array 1020. Accordingly, it will be appreciated that a packing station 205 can be formed from an end station 203 including, or otherwise in communication with, an array 1020, provided as a peripheral device. Thus, for example, the packing station 205 could include a tablet computer coupled to the array 1020, with the tablet providing processing and display functionality. Accordingly, the term packing station 205 will be understood to include an end station 203 with a peripheral array as required. Furthermore, where actions are described as being performed by an end station 203, it will be appreciated that these could also be performed by a packing station 205.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-42[0229] The packing process will now be described in further detail with reference to Figures 11 and 12A and 12B. In particular, an example of the process for manually defining packing data will now be described with reference to Figure 11.

[0230] In this example, at step 1100 a user uses an end station 203, or packing station 205, to select a define packing data option, with an indication of the selected option being provided to the management application implemented by the processing system 210. As in previous examples, the user is typically required to undergo an authentication procedure to make sure the user is authorised to prepare the packing information, for example by providing a username and password, predetermined input gesture, PIN, or the like, in a manner similar to that described above..

[0231] At step 1105, the management application prompts the user to use the end station 203 to select a respective subject. Whilst this could be performed by sensing a subject identifier, as the subject may not present at this stage in the process, the user may alternatively simply select a user for example by accessing a list of available subjects, or by manually entering an indication of the subject identifier.

[0232] At step 1110 the processing system 210 access the subject’s medication data to determine medication details, including any dosage plans, which are transferred to the end station 203 at step 1115, allowing the end station 203 to display the medication details at step 1120. At this stage any additional available information, such as existing packing data for the subject, as well as the pack template data that defines the types and layouts of the packs, would also be supplied.

[0233] At step 1125, the user selects a package layout and assigns medication to the receptacles. The package layout shows the visual indications that will be provided on the packaging to be used, and this will typically include information regarding the time and date or day on which medication should be administered.

[0234] In one example, the package layout is divided into specific days (Monday, Tuesday, Wednesday etc) and times (breakfast, lunch, dinner and bedtime), however, other arrangement can be used. In this regard, it will be appreciated that several different

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-43arrangements may be available, the system can cope with each of them simultaneously. The layout selected will depend on the particular circumstances. For example, the layout may be dictated by the preference of the administrating body, such as a nursing home or the like, and is generally related to the level of training available and the associated cost. Highly trained homes prefer unit dose where each column is reserved for one medication and a pack represents the time of day resulting in more packs per patient, whereas less trained homes use multidose where each column represents the time of day and a whole pack can satisfy a week of medications. It is also possible to have a monthly pack where a pack represents a time of day like the unitdose pack, but the columns represent week one, week two, week three, week four. It will be appreciated that the user may define their own layout, or use pre-stored layouts retrieved from a store, such as the database 211, as required.

[0235] An example of a user interface for generating packing data will now be described with reference to Figure 12A.

[0236] In this example the user interface 1200 includes an actions menu 1210 allowing different actions of the software system to be selected, as previously described. In addition, a patient details window 1220, a pack window 1230, a medication window 1240 and a packaging representation 1250.

[0237] As in previous examples, once the subject has been selected, patient details will be automatically populated in the patient details window 1220. A next particular pack of medication to be provided to the patient will be selected using the pack window 1230. The medication window 1240 will then include a list 1241 of the different medications that are to be included in the respective pack with details 1242 of each medication also being shown.

[0238] In this example, the user can select a particular medication with an image of this being displayed. The user can then select a cell 1251 in the packaging representation 1250, which corresponds to one of the packaging receptacles 1031. The user can assign medication to particular receptacles 1031 in any suitable, manner, such as by dragging and dropping medication into a particular receptacle, or by providing a numerical value associated with a particular medication.

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-44[0239] Thus, for example, medications for the user can be assigned respective numerical values (“1”, “2” etc) representing the quantity to be packed and administered, with the user simply entering these in the appropriate receptacle. As this is designed for touch screen, in another example, the user touches the cells to increase or decrease the value. Alternatively, the user can increase or decrease the specified quantity of drugs to be included in the respective receptacle using the input buttons 1252. As a further option, using the lock toggle button and clicking on one cell 1251 can modify in an entire column of cells 1251 at once rather than an individual cell 1251, as this is typically how most medications are dosed. The user can also choose to do special dosing like once per week, once every two days, once every three days, etc.

[0240] It will be appreciated that the above described process thereby provides a visual representation of the packaging, allowing the user to visualise the appearance of the final packaging, and in particular, the layout of medications within the packaging. This is in contrast to typical systems in which data is often prepared using input fields and the true layout is not known until the pack is printed. This visualisation process can assist the user in ensuring that medication is laid out in an appropriate and accurate manner, thereby assisting in ensuring resulting packages can be easily used.

[0241] An alternative form of representation is shown in Figure 12B, which is designed to accommodate unit-dose packs. The above described process can be used not only to define new package layouts, but also to schedule changes to packs. In this regard, many systems work off a current pack layout and it is up to the user to change the layout ready for the current week. However, if a medication starts in the middle of the week then continues for two weeks, the first week’s pack will be half full, the second week’s pack will be full, and the third week’s pack will be half full. In other systems the user would have to remember to change the pack layout each week, however by scheduling the changes each of the layouts can be defined at the time the medication was initiated.

[0242] At step 1130, the end station 203 generates the packing data representing the packing layout, and including an indication of the visual indications that are to be printed on the packing, together· with a unique package identifier that is assigned to the package. The package identifier can be a particular instance of a medication identifier and/or can be

WO 2012/145789

PCT/AU2012/000432

2012101981 26 Apr 2012

-45associated with multiple medication identifers, allowing the above described administering process of Figures 5A to 5C to be performed on the basis of the packaging identifier, to thereby ensure that the correct medication package is delivered to the correct subject.

[0243] The packing data is then transferred to the processing system 210 at step 1135, allowing this to be stored for subsequent retrieval during the packing process, with the package identifier also being typically stored as part of the subject and/or medication data, to thereby uniquely associate the package with the subject.

(0244] Whilst the above described process is described as being performed manually, this is not essential, and alternatively, it may be performed automatically by having the end station 203 or processing system 210 automatically associate medication with particular receptacles based on the medication data. However, as correct packing is important in ensuring the correct administering of medication, typically if automatic association of medication with packaging receptacles is performed, there would at least be a review process performed by a pharmacist or other medically qualified personnel.

(0245] Despite this, as the pharmacist need not actually pack the medication, then this can reduce workloads on pharmacists, allowing a reduced number of qualified personnel to be used in the packing process, which is important in circumstances where availability of personnel may be limited.

[0246] Once the packing data has been generated, this can be used to allow foil covers to be printed for use in the packing process. Whilst this may be performed on a pack by pack basis as part of the packing process, more typically this is performed as part of a batch process, with multiple foil covers being prepared and then provided for use in the packing process.

[0247] An example of the packing process will now be described in more detail with reference to Figures 13A to 13C.

[0248] In this example, at step 1300, the user accesses the management application using the packing station 205 and selects a medication packing option. As in previous examples, the user is typically required to undergo an authentication procedure to make sure the user is authorised to prepare the packing information, for example by providing a username and

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-46password, predetermined input gesture, PIN, or the like, in a manner similar to that described above..

[0249] At step 1305, the user uses the packing station 205 to sense the packing identifier provided on the foil cover of the package to be packed. In the event that the foil cover is not available, for example if this has not been provided, the user can alternatively enter this information manually, or select from a list provided by the processing system 210. The packing identifier is used to identify the package to be packed, and as an alternative the user can select a subject whose medication is to be packed. In one example, this can be achieved by sensing subject identifier data, for example from a box containing the subject’s medications. Alternatively, the user can simply enter details of the subject, such as the subject’s name or identifier, or select the subject from a list of subjects, using a suitable user interface. Alternatively, the processing system 210 may be used to schedule packing of medication, in which case, the processing system can simply select the next package to be packed automatically.

[0250] At step 1310, the packing identifier is transferred to the processing system 210, which uses this information to determine the associated packing data at step 1310. The packing data is transferred to the packing station 205 at step 1320.

[0251] It will be appreciated by persons skilled in the art that in the event that an automated packing system is used, the automated packing system can then begin packing the medication in the packaging in accordance with the packing data, thereby ensuring that the medication is packed correctly. In the current example however, the packing is performed manually. This is particularly relevant in a number of scenarios, for example in nursing homes, or the like, where the use of automated packing systems is unfeasible.

[0252] Having received the packing data, the packing station 205 determines the medications to be packed at step 1325, before displaying an indication of the medications to the user at step 1330. The indication may be displayed in any appropriate manner, but will typically involve displaying details of the medication, such as a medication name and optionally other identifying information, such as an image of the medication, on a user interface presented on a display. This can be achieved for example by displaying information in a manner similar to

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-47that described with respect to the medication window 1240 of Figure 12A. It will be appreciated that at this stage, additional information, such as subject details or the like may also be displayed.

[0253) At step 1335 the user selects a next medication. As part of this process, the user will typically sense the medication identifier associated with the next medication, using the sensing device at step 1340. This may be performed to allow the medication to be selected. Alternatively, the next medication can be selected using appropriate input commands, for example based on manual selection from a list, or by selecting a “Next Medication” option which can be triggered by a capacitive button on the LED array, or similar, which will automatically select the next non-packed medication in the list. In this case, the user may then sense the medication identifier data provided on the medication.

[0254) It will be appreciated that sensing the medication identifier from the packaging allows to the packing station 205 to compare the medication identifier of the selected medication to the assigned medication indicated in the medication data, thereby allowing a check to be performed to ensure the correct medication has been selected by the user, at step 1350.

[0255) If it is determined that the selected medication is incorrect, an indication of this is displayed to the user at step 1355, allowing the process to return to step 1335, so that the user can selected the correct medication. It will be noted images of the medications are typically displayed to the user as extra confirmation for the user that the correct medication has been selected.

[0256| Once the correct medication is selected, the packing station 205 displays an indication of the one or more receptacles in which the medication should be packed at step 1360. This can be displayed on a screen, such as the display 1010, or alternatively, as described above, can involve selectively activating the LEDs 1021 in the array 1020 to thereby illuminate the corresponding receptacles 1031 in the packaging. The user need then simply insert the medication into the indicated receptacles at step 1365, thereby ensuring the medication is correctly packed.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-48[0257] A single medication can have multiple doses (e.g. 1 in the morning and 2 at night). So once a medication is selected it will show the first dose to pack, once this is packed it will then show the next dose and so on until all doses are packed for that medication. The dose quantity is shown on the screen prominently in both numeric and textual form (e.g. 1.5 = ONE AND A HALF) to avoid misreading, as well as using colours for different doses to emphasise when there is a change.

[0258] At step 1370, the user confirms the respective medication has been packed in the respective receptacles. Once a medication dose is packed the processing system 210 can subtract the packed quantity from the quantity on hand for that patient so that system can know when to reorder medications. There is also the ability for the user to record wastage (i.e. if they dropped a tablet on the floor, or crushed it instead of splitting it) so as to maintain an accurate record of the remaining quantity on hand for each medication.

[0259] The packing station 205 determines if all medication has been packed step 1375. If not, the process returns to step 1335 allowing a next medication to be packed. Otherwise, once all packing is completed, the packing station 205 can image the filled packaging using the camera 1024, allowing the image to be stored for subsequent review. This can be used to subsequently identify if incorrect packaging has occurred, which is useful for audit purposes or the like. The image can be stored together with other information regarding the packing process, such as the time and date of packing, or the like. In addition to this, the camera 1024 can be used to record low resolution video footage of the packing process and/or images each time a medication is packed, which can also be stored for subsequent review if required.

[0260] Once packing is completed, the packaging can be provided for verification at step 1380. The verification process typically involves visual inspection by another user, such as suitably qualified pharmacist, or the like. The verification process can be performed by illuminating all of the receptacles with white light so as not to obscure the colour of the medications themselves, allowing the pharmacist to more easily visually identify the packed medication, and confirm whether it is correct.

[0261] In one particular example, the verification involves two distinct phases which are combined as a linear process. The user loads the pack and is presented with an initial screen

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-49that shows the pack and patient details. The first phase of verification is then equivalent to the packing process where each dose is displayed individually, the difference is that the user does not select the medication rather the system goes through each medication sequentially. The second phase is then a process of verifying combinations meaning that each can have a different combination of medication doses. The system will determine all the unique combinations and will display them sequentially along with a count of the number of individual dose units (i.e. lx tablet A + lx tablet B = 2 dose units, and 0.5x tablet A + lx table B also = 2 dose units but a different combination). The user simply has to count that the correct number of total dose units exists in the illuminated receptacles. One of the checks can also include counting the number of empty receptacles. In both of these phases the user has the option to pass, fail, or fix the medications in that step. If one or more steps are failed, then the whole pack is considered to have failed checking. For unit dose packs there is no need to do combination verification (except for empty cells) as each column is dedicated to only one drug and so the first phase will cover this.

[0262] Verification is performed by someone other than the packer to thereby provide independent verification, with the verifier being an authorised user that is appropriately skilled to sign off on the packs.

[0263] If any errors are found during verification, they can be fixed at that time, or the pack can be marked as failed and the packer must perform a fixing step to correct it, depending on the preferred implementation. The fixing will show which medication and corresponding dose time was marked as failed.

[0264] Whilst manual verification takes time, it will be appreciated that this is still substantially less than the time required to pack the medication, thereby reducing overall workloads on the pharmacist, whilst still providing sufficient certainty that the medication is packed correctly.

[0265] At step 1385, assuming verification confirms packing is correct, the packaging can be again imaged by the camera 1024, with an image again being stored for example for subsequent review. Following this, the packaging is then sealed, although alternatively the

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-50pack can either be sealed before verification is performed, depending on the preferred implementation.

[0266] Sealing is typically achieved by applying the printed foil cover including the relevant visual indications. The system can assist with the assembly phase by ensuring that the right foil and header card are used through barcodes scanning, and showing the user what colour folder to use, if any, and where to place any special stickers that may be required (e.g. start here, keep refrigerated, etc.). The assembly phase is also tracked by having the user provide confirmation of completion of an action using the end station 203 or packing station 205. This allows the processing system 210 to track assembly of the packs, and in particular, where a batch and or pack is up to in its lifecycle. When performed as part of a batch process, as described in more detail below, the system can tell the user how many of each type of component is needed for the whole batch (e.g. 20 blue folders, 5 pink folders, and 2 purple folders). It will be appreciated that in the event that the foil cover has not been previously prepared, this can be printed by an appropriate printing device, at this time.

[0267] The next stage is the delivery of the packed medications to locations, such as healthcare facilities, for subsequent administration to subjects. The delivery process broadly includes four different tasks, which are typically performed at different physical locations, with the process being tracked by having users enter details via an end station 203. For example, the first task involves putting the packs in boxes ready for shipping, with this being tracked by sensing a barcode on the box and each pack, allowing the processing system 210 to record which packs went into which box. The second task is then shipping the boxes, with each box being scanned as it leaves the packing facility, to thereby record it is in transit. The third step involves scanning the boxes as they arrive at the healthcare facility to record they have been received. The fourth step involves scanning each pack as it is removed from the boxes.

[0268] During this process, alerts and reporting can be generated by the processing system 210, allowing users to identify if any boxes or packs have gone missing. It will be appreciated however that the delivery process is for the purpose of example only, and alternative delivery techniques may be used.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-51[0269] Once delivered, the medication is then administered as described above with respect to Figures 5A to 5C. Following this, empty packs may then be returned to the packing facility. Some of the components such as the coloured folders are reused, so tracking the returns helps to monitor stock levels. Additionally, some packs may be returned unused or partially used in which case the medications can also be returned to stock for the patient, helping to keep track of accurate quantities for individual patients. In situations where the dose administration system is not used, the return of unused medications can be a crude indication of a patient's compliance and can trigger missed doses alerts.

[0270] Each of the processes outlined above, including packing, verifying, fixing, assembly, delivery, and returns, are considered individual activities. Each activity would typically be performed as part of a batch process, and usually by different users. It will therefore be appreciated that for each activity, the user will be required to go through an authentication process before selecting the activity to be performed. Following this, the processing system 210 displays details of the respective medication pack, via the end station 203 or packing station 205, allowing the user to complete the activity for that pack. The processing system then records completion of the activity and loads details of the next pack, allowing the process to be repeated for the next pack in the batch.

[0271] Especially when it comes to packing, many different activities have to be done by specific times to ensure that everything is completed in time. There are many additional activities such as reordering prescriptions from the doctor and reordering medications from the pharmacy which need to be done with enough time to allow delivery before the packing commences. The system can report on which medications need to be reordered based on cunent records of on hand quantities and requirements of future scheduled packs. With proper planning each activity will have a deadline (e.g. packing must be done by 12pm Monday so that verifying can be done by 5pm, etc.). One or more selected users will have an overview of the batches that are currently in progress and will be able to see what has been completed and what is running behind schedule. Similarly each user may have their own limited view of a batch which shows the activities that have been assigned to them or can be performed by them. Multiple batches will be running concurrently as each batch will

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-52typically represent one healthcare facility for one week but typically takes longer than one week to complete (i.e. from ordering of new prescriptions through to return of used packs).

[0272] Accordingly, the above described process allows unskilled users to perform packing based on clear instructions and visual guides provided by the packing station, thereby reducing the likelihood of packing errors. The accuracy of packing achieved using this process is further enhanced by requiring that each medication can be scanned before being packed, thereby reducing the likelihood of incorrect medication identification by unskilled workers.

[0273] Thus, the above described process guides users to accurately pack one or more blister packs at a time by displaying the details and image of the drug on screen in conjunction with illuminating the target receptacles in the blister pack. The process reduces the chances of human error associated with such repetitive tasks by using barcode recognition, visual clues, and a well defined procedure. Additionally, by allowing independent verification to be performed using a systematic process, this can confirm that the correct drugs were packed into the pack, thereby simplifying the packing activity whilst reducing the chance of errors.

[0274] In another example, the above described process can also be performed using an end station 203, without a peripheral array. In this example, the process is substantially as described above, however instead of illuminating specific receptacles using the array 1020, the end station 203 will merely display a representation of the package with the relevant receptacle highlighted. It will be appreciated that this allows the process to be used even in the event that an array is not available, thereby ensuring the packing process can be continued even in the event of hardware failure. It will be appreciated that in contrast, if hardware failure occurs with a robotic packing system, then typically it would not be possible to pack the medication.

[0275] The above described management system can also be used to provide subjects with access to their subject and medication data, for example to satisfy legislative requirements, as will now be described with reference to Figure 14.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-53[0276] In this example, at step 1400 the subject accesses the management application using an end station 203. As part of this process, the subject will typically be required to provide authentication information, such as a username and password, predetermined input gesture, PIN, or the like, in a manner similar to that described above, including an indication of their subject identifier, or the like at step 1405. This information is transferred to the processing system 210, allowing the processing system 210 to authenticate the subject at step 1410. It will be appreciated that this is performed to prevent unauthorised access to the subject data, and that as a consequence authentication failure will prevent the subject accessing the system.

[0277] At step 1415, assuming the subject is successfully authenticated in a manner similar to that described with respect to other activities, the user selects a view details option, with this triggering the processing system 210 to access the subject and medication data for the subject at step 1420. At step 1425, the subject and medication details can be transferred to the end station 203, allowing an indication of these to be presented to the subject at step 1430. The user can also anange these to be forwarded to an alternative location, such as an email address or the like, allowing the medical records to be more easily reviewed. When travelling outside the native country, the system can provide translations of medication details so that they can be understood in other regions (e.g. the generic Paracetamol is known as Acetaminophen in the USA). Translations to other languages (e.g. English to Chinese) could be done on any patient or medication data.

[0278] Additionally, the subject can optionally arrange for alerts to be generated by their end station 203 at step 1435. The alerts can be generated in accordance with the medication data to indicate to the subject that medication is due to be administered. This is particularly useful in situations in which subjects are in charge of taking their own medication from a prepared package and can act to remind the subject that medication is due to be taken.

[0279] It will be appreciated that this allows the subject to review their own details including details of any assigned medications, which can be useful for example if the subject , is responsible for managing their own medication. Additionally, this can be used to allow the subject to update some details, such as personal information, thereby allowing the subject to ensure these are up to date, as well as allowing reminders to be generated, for example using a smartphone or the like, thereby ensuring adherence to medication regimes.

WO 2012/145789

PCT/AU2012/000432

2012101981 26Apr2012

-54[0280] Accordingly, the above described system allows medication of a subject to be managed and accurately summarised for the subject. This process is particularly important in situations where access to medically trained personnel is restricted. In particular, the above described process provides sufficient oversight to allow medication to be administered by users that may have only limited or no medical qualifications. Furthermore, the process provides an approval mechanism allowing a limited number of medically qualified practitioners, such as doctors, or pharmacists, to assign, manage and review medication for a greater number of subjects than would otherwise be possible if a face-to-face consultation were required. The process can also be used to allow unskilled workers to package medication for subsequent self administration by subjects, thereby further reducing workloads on skilled professionals. As a result, the system can provide significant benefits in terms of workforce optimisation to cope with workforce shortages and other associated issues.

[0281] It will be appreciated that the above described process can be used in a wide range of situations in which medication is assigned to individuals. The term subject will therefore be understood to apply to any individual to whom medication is assigned, and can include patients, as well as other individuals. It will also be appreciated that the subject can be a user of the system, and in other examples can include non-human subjects such as an animal, including but not limited to, primates, livestock, performance animals, such as race horses, or the like.

[0282] The term assigned medication indicates any form of medication to be taken by a subject. This can include OTC (over the counter) or complementary and herbal medications, as well as prescribed medications.

[0283] Persons skilled in the art will appreciate that numerous variations and modifications will become apparent. All such variations and modifications which become apparent to persons skilled in the art, should be considered to fall within the spirit and scope that the invention broadly appearing before described.

Claims (84)

1. THE CLAIMS DEFINING THE INVENTION ARE AS FOLLOWS:

   1) A method of packing medication for a subject, the medication being packed into packaging including a number of receptacles for receiving medication, the method including, in a packing station:

   a) determining packing data indicative of medication to be packed for the subject;

   b) providing an indication of a medication to be packed; and,

   c) providing an indication of a receptacle into which the medication should be packed, thereby allowing a user to pack the medication into the receptacle in the packaging.
2. 2) A method according to claim 1, wherein the method includes, in the packing station, providing the indication of a receptacle by selectively illuminating the receptacle.
3. 3) A method according to claim 2, wherein the method includes:

   a) positioning the packaging on an array of radiation sources; and,

   b) selectively activating a radiation source to thereby illuminate a receptacle.
4. 4) A method according to any one of the claims 1 to 3, wherein the packing station includes a processor, and wherein the method includes, in the processor, selectively activating the radiation sources in accordance with the packing data.
5. 5) A method according to any one of the claims 1 to 4, wherein the indication of a medication includes an image of the medication.
6. 6) A method according to any one of the claims 1 to 5, wherein the method includes:

   a) determining a packaging identifier indicative of an identity of the packaging; and,

   b) determining the packing data at least in part using the packaging identifier.
7. 7) A method according to any one of the claims 1 to 6, wherein the method includes:

   a) determining a subject identifier indicative of an identity of the subject;

   b) determining medication data associated with the subject at least in part using the subject identifier; and,

   c) determining.the packing data at least in part using the medication data.
8. 8) A method according to any one of the claims 1 to 7, wherein the method includes:

   a) determining a medication identifier associated with a medication, the medication identifier being indicative of an identify of the medication; and,

   b) confirming the medication should be packed at least in part using the medication identifier.

   WO 2012/145789

   PCT/AU2012/000432

   2012101981 26Apr2012
9. 9) A method according to any one of the claims 1 to 8, wherein the method includes, in the packing station, determining when a medication has been packed in accordance with input commands from a user.
10. 10) A method according to any one of the claims 1 to 9, wherein the method includes, in the packing station:

    a) illuminating the receptacles; and,

    b) determining approval of the packing.
11. 11) A method according to any one of the claims 1 to 10, wherein the packaging includes a visual indicator of when medication in each receptacle should be administered.
12. 12) A method according to any one of the claims 1 to 11, wherein the method includes sealing the packaging.
13. 13) A method according to claim 12, wherein the packaging includes a base defining the number of receptacles and a cover layer, the method including sealing the packaging by applying the cover layer.
14. 14) A method according to claim 13, wherein the cover layer includes a visual indicator of when medication in each receptacle should be administered.
15. 15) A method according to any one of the claims 1 to 14, wherein the packing station communicates with a base station via a communications network to thereby determine the packing data.
16. 16) A method according to any one of the claims 1 to 14, wherein the method includes:

    a) using an imaging device to image the packaging; and,

    b) storing the image of the packaging.
17. 17) A method according to any one of the claims 1 to 16, wherein the method includes, using a display to display at least one of:

    a) an indication of a medication; and,

    b) an indication of a receptacle.
18. 18) A method according to any one of the claims 1 to 17, wherein the method includes, in the packing station:

    a) determining a packaging identifier;

    b) determine packing data at least in part using the packaging identifier;

    c) displaying an indication of a next medication to be packed;

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26Apr2012

    d) determining a medication identifier associated with a medication;

    e) confirming the medication is the next medication using the medication identifier;

    f) illuminating a receptacle into which the next medication should be packed; and,

    g) determining when the medication has been packed.
19. 19) Apparatus for packing medication for a subject, the medication being packed into packaging including a number of receptacles for receiving medication, the apparatus including a packing station that:

    a) determines packing data indicative of medication to be packed for the subject;

    b) provides an indication of a medication to be packed; and,

    c) provides an indication of a receptacle into which the medication should be packed, thereby allowing a user to pack the medication into the receptacle in the packaging.
20. 20) Apparatus according to claim 19, wherein the packing station provides the indication of a receptacle by selectively illuminating the receptacle.
21. 21) Apparatus according to claim 19 or claim 20, wherein the packing station includes an array of radiation sources, each radiation source corresponding to a respective receptacle.
22. 22) Apparatus according to claim 21, wherein the packing station includes a processor, and wherein the processor selectively activates the radiation sources in accordance with the packing data.
23. 23) Apparatus according to claim 22, wherein the packing station includes a housing having a recess for receiving the packaging, the recess acting as a guide to thereby align the receptacles with the radiation sources.
24. 24) Apparatus according to any one of the claims 21 to 23, wherein the apparatus includes a display for displaying the indication of a medication to be packed.
25. 25) Apparatus according to claim 24, wherein the indication includes an image of the medication to be packed.
26. 26) Apparatus according to any one of the claims 19 to 25, wherein the packing station includes a sensing device for sensing identifier data.
27. 27) Apparatus according to any one of the claims 19 to 26. wherein the packing station:

    a) determines a medication identifier associated with a medication, the medication identifier being indicative of an identify of the medication; and,

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26Apr2012

    b) confirms the medication should be packed at least in part using the medication identifier.
28. 28) Apparatus according to any one of the claims 19 to 27, wherein the packing station includes an imaging device for imaging the packaging.
29. 29) Apparatus according to any one of the claims 19 to 28, wherein the packing station includes a processing system coupled to at least one array, each array including a plurality of radiation sources for selectively illuminating receptacles in packaging, and each array being used for packing medication in respective packaging.
30. 30) A method of managing medication for a subject, the method including, in a processing system:

    a) determining a subject identifier indicative of an identity of the subject;

    b) determining medication data associated with the subject at least in part using the subject identifier;

    c) determining assigned medication associated with the subject using the medication data; and,

    d) providing an indication of the assigned medication to a user.
31. 31) A method according to claim 30, wherein the method includes:

    a) determining subject details associated with the subject at least in part using the subject identifier; and,

    b) providing an indication of the subject details to a user.
32. 32) A method according to claim 30 or claim 31, wherein the method includes displaying an image of the subject to allow a user to visually confirm the identity of the subject.
33. 33) A method according to any one of the claims 30 to 32, wherein the method includes allowing an action to be performed, the action including at least one of:

    a) administering medication;

    b) assigning medication;

    c) assigning a medication dose;

    d) approving medication; and,

    e) packing medications.
34. 34) A method according to any one of the claims 30 to 33, wherein the method includes determining an action to be performed using at least one of:

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26Apr2012

    a) action data stored in a store, the action data being indicative of actions to be performed; and,

    b) input commands from a user.
35. 35) A method according to any one of the claims 30 to 34, wherein the method includes determining whether an action can be performed using at least one of:

    a) medication details indicative of any assigned medication; and,

    b) subject details associated with the subject.
36. 36) A method according to claim 35, wherein the method includes displaying a representation including at least some of the subject details and medication details to allow visual inspection of the displayed subject and medication details.
37. 37) A method according to claim 35 or claim 36, wherein the method includes displaying at least one of an image of the subject and an image of the medication to allow visual inspection of at least one of the subject and the medication.
38. 38) A method according to any one of the claims 30 to 37, wherein the method includes:

    a) determining completion of an action; and,

    b) recording an indication of completion of the action.
39. 39) A method according to claim 38, wherein the method includes recording at least one of:

    a) the action performed;

    b) a date the action was performed;

    c) a time the action was performed;

    d) a subject identifier indicative of an identity of the subject;

    e) a user identifier indicative of an identity of a user;

    f) an image indicative of the completed action; and,

    g) a medication identifier indicative an identity of any medication.
40. 40) A method according to any one of the claims 30 to 39, wherein the method includes determining a medication identifier associated with a medication, the medication identifier being indicative of an identify of the medication.
41. 41) A method according to claim 40, wherein the method includes determining whether an action should be performed at least in part using the medication identifier.
42. 42) A method according to claim 40 or claim 41, wherein the method includes confirming a medication is an assigned medication in accordance with the identity of the medication.

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26 Apr 2012
43. 43) A method according to any one of the claims 30 to 42, wherein the method includes:

    a) determining an assigned medication using the medication data;

    b) determining a medication identifier associated with a selected medication;

    c) comparing the identity of the selected medication to the assigned medication to determine the selected medication is the assigned medication.
44. 44) A method according to claim 43, wherein the method includes displaying an image of the assigned medication to allow a visual comparison to be performed by the user.
45. 45) A method according to any one of the claims 30 to 44, wherein the method includes:

    a) providing an approval request to at least one approver, the approval request requesting approval of the assigning of medication to the subject;

    b) determining approval of the medication request from the at least one approver; and,

    c) updating the medication data in accordance with the approval.
46. 46) A method according to claim 45, wherein the approval request is indicative of at least one of:

    a) an identity of an assigned medication;

    b) a dosage of an assigned medication;

    c) medication details; and,

    d) subject details.
47. 47) A method according to claim 45 or claim 46, wherein the method includes:

    a) determining a medication request, the medication request being indicative of at least an identity of the subject and a requested medication;

    b) providing the approval request to the approver using the medication request.
48. 48) A method according to any one of the claims 30 to 47, wherein the method includes:

    a) determining assigned medication at least in part using the medication data associated with a subject;

    b) generating packing data in accordance with the determined assigned medication; and,

    c) transferring the packing data to a packing station, to allow the medication to be packed.
49. 49) A method according to claim 48, wherein the medication is packed in packaging including a number of receptacles, and wherein the packing instructions are indicative of receptacles into which respective medication should be packed.

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26 Apr 2012
50. 50) A method according to claim 49, wherein method includes, in the packing station, displaying an indication of a receptacle into which medication should be packed to a user thereby allowing the user to pack the medication in the receptacle.
51. 51) A method according to claim 49 or claim 50, wherein the packaging includes a visual indicator of when medication in each receptacle should be administered.
52. 52) A method according to claim 51, wherein the method includes, in a packing station, applying the visual indicator to the packaging.
53. 53) A method according to any one of the claims 30 to 52, wherein the method includes determining an identifier by:

    a) determining identifier data, the identifier data being associated with a respective identifier; and, '

    b) using the identifier data to determine the identifier.
54. 54) A method according to any one of the claims 30 to 53, wherein the method includes sensing identifier data using a sensing device.
55. 55) A method according to claim 54, wherein the method includes retrieving an identifier from a store using the identifier data.
56. 56) A method according to claim 54 or claim 55, wherein the method includes sensing subject identifier data based on at least one of:

    a) an identification tag; and,

    b) a physical attribute of the subject.
57. 57) A method according to any one of claims 30 to 56, wherein the processing system includes a store, and wherein the method includes at least one of storing in and retrieving from the store, at least one of:

    a) subject data; and,

    b) medication data; and,

    c) action data.
58. 58) A method according to claim 57, wherein the store is at least one of a memory and a database.
59. 59) A method according to any one of claims 30 to 58, wherein the subject data is indicative of at least one of:

    a) an identity of the subject;

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26Apr2012

    -62b) subject details;

    c) a subject photo;

    d) a medical history; and,

    e) subject allergies.
60. 60) A method according to any one of claims 30 to 59, wherein the medication data is indicative of at least one of:

    a) an identity of any assigned medications;

    b) a timing associated with medication administration;

    c) an image of the medication; and,

    d) a medication dosage.
61. 61) A method according to any one of claims 30 to 60, wherein the processing system includes an input device, and wherein the method includes receiving input commands from a user using the input device.
62. 62) A method according to any one of claims 30 to 61, wherein the processing system includes a processor, and wherein the processor executes instructions stored in a store to cause at least one action to be performed.
63. 63) A method according to any one of claims 30 to 62, wherein the processing system includes a display for displaying indications.
64. 64) A method according to any one of the claims 30 to 63, wherein the method is performed at least in part using an end station, coupled to a base station, via a communications network.
65. 65) A method according to claim 64, wherein the base station includes a processing system and a store.
66. 66) A method according to claim 64 or claim 65, wherein the end station includes a processing system having a display.
67. 67) A method according to claim 66, wherein the end station includes a sensing device for sensing identifier data.
68. 68) A method according to any one of the claims 64 to claim 67, wherein the method includes, in the end station:

    a) determining subject identifier data indicative of a subject identifier;

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26Apr2012

    -63b) transferring the subject identifier data to the base station via the communications network;

    c) receiving an indication of an assigned medication from the base station via the communications network; and,

    d) displaying the indication of the assigned medication to a user on a display.
69. 69) A method according to claim 68, wherein the method includes, in the end station:

    a) receiving subject details from the base station; and,

    b) displaying an indication of the subject details to a user on a display.
70. 70) A method according to claim 68 or claim 69, wherein the method includes, in the end station:

    a) determining medication identifier data indicative of an identity of a medication; and,

    b) comparing the medication identifier data to the indication of the assigned medication to determine if the medication is the assigned medication.
71. 71) A method according to any one of the claims 62 to 68, wherein the method includes, in the end station:

    a) determining a medication request; and,

    b) transferring the medication request to the base station via the communications network, the base station being responsive to the medication request to seek approval for the medication request from at least one user.
72. 72) A method according to claim 71, wherein the method includes, in the base station:

    a) transferring an approval request to an approver end station via the communications network; and,

    b) receiving an approval indication from the approver end station in response to approval by the approver.
73. 73) A method according to claim 72, wherein the method includes, in the approver end station:

    a) receiving the approval request;

    b) displaying at least one of subject details, medication details and an indication of a requested assigned medication to the approver; and,

    c) generating the approval indication in accordance with a response provided by the user.

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26 Apr 2012
74. 74) A method according to any one of the claims 30 to 73, wherein the method is performed using a base station coupled to a packing station via a communications network.
75. 75) A method according to claim 74, wherein the method includes, in the base station:

    a) determining packing instructions in accordance with medication data and,

    b) transferring the packing instructions to the packing station via the communications network.
76. 76) A method according to any one of the claims 30 to 75, wherein the medication management method includes defining at least dose by:

    a) determining at least one assigned medication for a subject;

    b) determining an indication of when the medication should be administered; and,

    c) updating the medication data in accordance with the indication of when the medication should be administered.
77. 77) A method according to claim 76, wherein the determination of when medication should be administered is determined in accordance with user input commands.
78. 78) A method according to claim 76 or claim 77, wherein the method includes defining a dose administration plan.
79. 79) Apparatus for managing medication for a subject, the apparatus including a processing system that:

    a) determines a subject identifier indicative of an identity of the subject;

    b) determines medication data associated with the subject at least in part using the subject identifier;

    c) determines assigned medication associated with the subject using the medication data; and,

    d) provides an indication of the assigned medication to a user.
80. 80) Apparatus according to claim 79, wherein the apparatus includes an end station, coupled to a base station, via a communications network.
81. 81) Apparatus according to claim 80, wherein the base station includes a processing system and a store.
82. 82) A method according to claim 80 or claim 81, wherein the end station includes a processing system having a display.

    WO 2012/145789

    PCT/AU2012/000432

    2012101981 26 Apr 2012
83. 83) A method according to claim 82, wherein the end station includes a sensing device for sensing identifier data.
84. 84) Apparatus according to any one of the claims 79 to 83, wherein the apparatus includes a packing station coupled to the base station via a communications network.