ePharmtool connects patients, pharmacies, hospitals, general Practitioners (GP) and Medical Practitioners under one platform. This innovative architecture integrates and centralizes all the prescription details including Prescription reference number, Medicare/ Passport / Driving License/ other ID number, prescribed drugs/medication (based on Australian Medical Terminology -AMT by National e-Health Transition Authority), provider number of the medical practitioner (assigned by Human Services Directory - HSD), order sentences and pharmacists license number (assigned by the Pharmacy Board). At present, connecting the pharmacy with the GP, Hospital and Medical Practitioners is a major challenge. These stakeholders (i.e. pharmacy, GP, hospital, Medical Practitioners) use disparate and often isolated software, running on different platforms. Before going into the details of the architectural details, few of the core components of our design must be identified. ePharmtool Integration Engine (117): This is the standard interface for our centralized repository (116). All the e-prescriptions, containing drugs information, provider code, pharmacy code and prescription reference number are pushed towards ePharmtool Integration Engine from the medical providers like GP / Hospital / Specialists etc. ePharmtool Integration Engine surrounds the centralized repository that contains detail information of the e-Pharmacy. ePharmtool Client Desktop Push (119): This the stand alone software running in medical provider's (i.e. GP / Hospital / Medical Practitioner) personal computer. This software submits e-Prescriptions (containing prescription reference number, prescribed, medication information, order sentences, provider ID) ePharmtool adapter desktop Push: If the medical providers (i.e. GP / Hospital I Medical Practitioner) are already using existing software then ePharmtool adapter desktop Push becomes the communicator between the third party software and the ePharmtool Integration Engine. This adapter makes sure that the third party software talks in a common language expected with ePharmtool Integration Engine. ePharmtool Client Mobile Push (113 or 118): The roaming medical providers (i.e. GP, Doctors) can use this mobile version of ePharmtool to generate ePrescriptions for the patients. The generated ePrescriptions can be submitted to the ePharmtool Integration Engine or it can be pushed to the ePharmtool Mobile Read only (i.e. mobile phone carried by the patients). 1 ePharmtool Client Desktop Pull (107 / 108): This is standalone software used by the pharmacy. This software pulls the ePrescriptions from the patient's mobile phone (105) /SmartCard (109) (i.e. ePharmtool Mobile Read only/ SmartCard). ePharmtool Adapter Desktop Pull (110): This adapter works, if the pharmacy uses a software by a third party vendor. This module works as a standard interface between the third party pharmacy software and the ePharmtool Integration Engine. ePharmtool Mobile Read only: This is mobile software installed in Patient's mobile phone. Patient's mobile phone's read only application can carry the encrypted prescription detail s pushed by the GP / Hospital / Medical Provider via epharmtool Desktop Client. On the other hand, when the patient visits the pharmacy, medications can be dispensed by the pharmacy after the pharmacy pulls the ePrescription from the patient's mobile phone. ePharmtool SmartCard (105): Is a pocket-sized card with embedded ePharmtool SmartCard Programmed module. ePharmtool SmartCard can be used to store encrypted prescription details by the GP / Hospital / Medical Provider via ePharmtool Desktop Client of course SmartCard reader is required for this action. On the other hand, when the patient visits the pharmacy, medications can be dispensed by the pharmacy after the pharmacy pulls the ePrescription from the patients SmartCard. How it works: Patients can choose either carrying a "key" for e-prescription printed on paper or pushed to mobile phone or store in ePharmtool SmartCard. Option one (Patient's ID used for prescription reference ID) - When patient (300) visits the Hospital / GP / Medical practitioners (302), an e prescription will be issued form ePharmtool client / adapter in HL7 / CSV / XML / Raw data format. The Messages (Prescription reference number, Medicare/ Passport / Driving License/ other ID number, prescribed drugs/medication) will be then uploaded (311) or submitted to ePharmtool Integration engine via Internet/WAN (307). Once the message is received by the EPharmtool integration engine, 2 Acknowledge messages will be generated and sent to GP/Hospital/ Medical practitioners via email and message to update to client application (305). - Prescription script with doctor/medical practitioner signature will be printed and handed to patient where patient can use this script to purchases the prescribed drugs or medications (304). - At Pharmacy, Patient will need to provide their medicare number/other ID together with the prescription script. Pharmacy or assistant will key these 2 reference numbers (eg.- Medicare Number, and Prescription number) or scan the 2 barcode to get the drugs/medication populate/download from Central DB (309) via internet (307) to their dispensing application or ePharmtool dispensing application. - Once all drugs have been dispensed, the pharmacy name (eg.- Terry White), Pharmacist professional reference number who had dispensed the drugs/Medications will be automatically populated into the dispensing form with special instructions for patient and printed on A5/A4 paper. This information will then update to the database and mark the Prescription dispensed with date and time (310). - Acknowledge message will then be trigged by ePharmtool integration engine and email will be sent to the Pharmacist mailbox and message to update to pharmacist software system or ePharmtool dispensing system (306). Option two (Patient's Mobile phone used for prescription reference ID) - The patient can choose to have the ePrescription sent directly to his mobile phone from the ePharmtool client / desktop to his mobile phone (running ePharmtool mobile view-only version) via Bluetooth protocol (204). In this case, Hospital / GP / Medical practitioner doesn't require to access internet and update the ePharmtool Integration engine - Patient carrying the ePrescription on their mobile phone (210) can visit their desired pharmacy to obtain the prescribed medications / drugs. The ePharmtool desktop client / adapter retrieves the encrypted messages from the patient's mobile phone and decrypts it (213). The ePharmtool desktop client / adapter will then populates the possible options (trading names for the prescribed generic drugs), dispenses and dispatches the medications to the patient (215). At the end of the transaction, the ePharmtool desktop updates the ePharmtool Integration engine (214) (dispatched drugs names, order sentences etc.) via internet. Option three (Patient's ePharmtool SmartCard prescription reference ID) - The patient can choose to have the ePrescription sent into Patient's ePharmtool SmartCard (204). In this case, Hospital / GP / Medical practitioner doesn't require to access internet and update the ePharmtool Integration engine - Patient carrying the ePrescription on their ePharmtool SmartCard can visit their desired pharmacy to obtain the prescribed medications / drugs (205). The ePharmtool desktop client / adapter retrieves the encrypted messages from the ePharmtool SmartCard (211) and decrypts it (213). The ePharmtool desktop client / adapter will then populates the possible options (trading names for the prescribed generic drugs), dispenses and dispatches the medications to the patient (215). At the end of the transaction, the ePharmtool desktop updates the ePharmtool Integration engine (214) (dispatched drugs names, order sentences etc.) via internet (209). 3 Figure 4 shows the basic workflow of the patient when he visits the doctor / GP / specialist (i.e. Prescriber). At the beginning of Fig. 4, the prescriber examines the patient (400). Then, based on the examination results the prescriber writes the prescription (401). Depending on the availability of the internet connection (402), a prescription is printed with reference number (404) only when internet connection is available and Mobile phone / smart card is not available (403). In 404, the prescription reference number, medicare / passport / driving license / other ID number are printed, which is fetched by using 406. However, if internet connection is not available or the patient / prescriber willing to use mobile phone/ smart card for storing the prescription, then mobile phone (409) or smart card (408) is used .A central database is updated if internet connection is available (407) for mobile phone / smart card. At the end, the patient leaves the clinic with the reference number (in case of 404) or encrypted prescription stored within patient's mobile phone (409) or smart card (408). Figure 5 shows the workflow of the patient when he visits the pharmacy of his / her choice for obtaining the prescribed drugs of Figure 4. The patient can use paper script (500), where pharmacy attendant (509) uses barcode (512) or uses the reference number of the printed prescription (511). Irrespective of the path taken at 510 (i.e. using barcode or reference number), the drugs details or prescribed medications (401) are downloaded via internet (514). Once the prescribed drugs details are downloaded, they can be dispatched. Alternatively, the patient can use mobile phone (503) or smart card (502) for storing the information (as shown in 410). For these cases, the encrypted drugs / medication details are decrypted and eventually the right drugs are dispatched (505, 506, 507). At the end, the central database is updated with the dispatched drugs information (508). 4 Integrating all these entities under one umbrella (i.e. under one system) can harness the following benefit: o Electronic medical records can be efficiently managed by the naYve user / patient. There will be less error in updating prescription entries since there is no need for manual entry for the prescription drugs. After the patient's visit to the GP / Hospital / Medical Practitioners, the patient gets e Prescription pushed into his/ her mobile via Bluethooth / ePharmtool SmartCard from software running in the computer of GP / Hospital I Medical Practitioners. o There will be less error within the pharmacy since they can electronically retrieve the e-prescription directly from the patient's mobile, ePharmtool SmartCard or from a central server. o The pharmacy will save time, because electronic retrieval of e-prescription (i.e. either from the patient's mobile phone, SmartCard or the central database) is substantially faster than manual entry by the pharmacy attendant o Having a centralized control of the e-prescription record for individual patients, enables various reporting options relevant to drugs, pharmacy, pharmaceutical companies and the hospitals. For example, pharmaceutical companies can know which pharmacy promoted their drugs well and might decide to rewards that pharmacy for promoting their product. GP or the hospital might know the drug history for a particular patient to assess whether that patient has developed an affinity or side effect etc. 5