20+ Million Readerbase
Indexed In
  • Open J Gate
  • Genamics JournalSeek
  • Academic Keys
  • JournalTOCs
  • The Global Impact Factor (GIF)
  • China National Knowledge Infrastructure (CNKI)
  • Ulrich's Periodicals Directory
  • RefSeek
  • Hamdard University
  • EBSCO A-Z
  • OCLC- WorldCat
  • Publons
  • Geneva Foundation for Medical Education and Research
  • Euro Pub
  • Google Scholar
Share This Page
Recommended Webinars & Conferences
Journal Flyer
Flyer image

Conference Proceeding - (2012) Volume 0, Issue 0

A Smart RFID Device for Drugs Administration

Ernesto Iadanza*
Department of Electronics and Telecommunications, Firenze, Italy
*Corresponding Author: Ernesto Iadanza, Department of Electronics and Telecommunications, Firenze, Italy Email:

Abstract

Abstract

In this work a device is described that can be used in hospitals to lower the risk of Adverse Drug Events (ADE) due to the incorrect link between patients and drugs. The device is a container that can be handled by the patient himself of by the caregivers. It is provided with an internal lock that prevents any openings when there is a mismatch between the patient and the drugs inside the container. It is based on passive RFID (Radio Frequency Identification) technology and is designed to give a visual alert if a wrong drug (tagged with RFID) is accidentally inserted, also preventing its administration by locking the top aperture.

The internal RFID reader is designed to read both the patient’s wristband and the drugs inserted into the device (provided that they are tagged with RFID): the device will not open if some un-prescribed drug is found inside the container, alerting the patient/operator using the on-board display.

Every single event is logged in an internal memory and can be transferred to a remote information system for analyses, statistics and risk management.

The device is also provided with two status LEDs, a green one and a red one, and with a text display that can show information about the patient’s identity, and therapy.

We are now working on the mechanical design and on the development of management software in order to link the device with CPOE (Computerized Physician Order Entry) systems and with automated drug storage systems.

Keywords: RFID, Drugs administration, Patient safety, Patient?s identification

Introduction

In this paper we will show the design of a device that is intended as a solution for reducing the number of Adverse Drug Events (ADEs) related to drugs administration to patients. The device is a container that incorporates an RFID (Radio Frequency Identification) reader in order to perform a check on patient's identity and to allow the administration of medications only to the right patient.

Many studies can be found in literature on this subject, assessing the problem of human factors in medication administration errors. Part of them are based on data coming from incident-reporting, others apply proactive analysis tools such as FMEA (Failure Modes and Effects Analysis) or HTA (Hierarchical Task Analysis). The National Coordinating Council for Medication Error Reporting and Prevention defines a medication error as "any preventable event that may cause or lead to inappropriate medication use or patient harm while the medication is in the control of the health care professional, patient, or consumer. Such events may be related to professional practice, health care products, procedures, and systems, including prescribing; order communication; product labelling, packaging, and nomenclature; compounding; dispensing; distribution; administration; education; monitoring; and use [1]." Adverse Drug Events (ADEs) are defined as injuries resulting from the use of a drug. Under this definition, ADEs include damages caused by the drug (adverse drug reactions and overdoses) and damages from the use of the drug (including dose reductions and discontinuations of medication therapy) [2].

According to [3,4], the 28% of all the ADEs come from the medication administration step.

Technological solutions, such as radio frequency tagging has been widely suggested as a solution to the problem of the wrong identification of patients and of the incorrect association between patient and medications.

In this work we are focusing on the error in the administration step, defined as the change between what the physician's prescription and the actual medication administered to the patient. Medication errors that originate from mistakes during prescribing can be significantly reduced by using CPOE (Computerized Physician Order Entry) software, thereby solving problems related to incomplete orders, bad calligraphy, misunderstandings in abbreviations, incompatible drugs etc. Nevertheless, CPOE use itself cannot prevent that the medication that is actually given to the patient is different from what the doctor prescribed. We can notice a lack in patient's safety in the last step of the whole therapeutic process: the administration step.

Some authors claim that use of Barcode Point-of-Care Technology (BPOC) to reduce medication errors is a patient-safety approach that hospitals can implement within a short time frame and obtain immediate benefits [5]. Some claim that the integration of bar codes and radio frequency identification tags are viewed as critical in achieving effective and safe patient care although systems using these capabilities must be carefully planned to achieve optimal outcomes [6-8].

Materials and Methods

Results



We started the design process by spotting 28 requirements to which our device must respond (see Table 1) and generating 20 corresponding technical specifications (see Table 2). The identified requirements relate to aspects of process safety as well as to procedural aspects and usability. Also affordability is an issue, to guarantee the widest dissemination of our device in hospitals.

Code Requirement Technical specifications
R.1 Integration with Hospital Information System S.1
R.2 Small reading distance between tags and device S.2
R.3 Each patient must be provided with an identification device S.3
R.4 The container of drugs should prevent unauthorized openings S.4
R.5 Tags collision management S.5
R.6 Wearable identification device S.3
R.7 ID device hygienic S.3
R.8 Drugs container sanitisable S.6
R.9 Drugs container must protect drugs from direct lightening S.7
R.10 Drugs temperature must never exceed 30°C S.8
R.11 Water-proof drugs container S.9
R.12 Access to medications must be controllable S.2,S.3,S.4,S.10
R.13 Tracking of every attempt (successful or not) to access drugs S.5,S.11
R.14 ID device not expensive S.3
R.15 Drugs container ergonomic S.12
R.16 Drugs container big enough to contain a whole medication therapy S.19
R.17 Procedure for drugs distribution S.1
R.18 Procedure for drugs administration S.2,S.3,S.10
R.19 Information to patients about the use of the device S.13
R.20 Low power consumption S.20
R.21 Staff must be able to force the device opening in case of emergency S.14
R.22 Emergency openings must be logged S.11
R.23 Easy identification of the association patient-container S.15
R.24 Reprogrammable S.2,S.16
R.25 Faults management S.5
R.26 Verification of the right association between patient and medication S.4,S.5,S.17
R.27 Alarm in case of wrong association between patient and medication S.4,S.5,S.17
R.28 Controlled administration S.18

Table 1: Requirements and corresponding technical specifications.

Code Technical specification Type
S.1 Electronic Patient Records  + CPOE + smart cabinets for a global automated management of drugs distribution system Software, electronic
S.2 RFID reader and RFID tag following ISO15693 standard Electronic, technological
S.3 Disposable wristband RFID tag Technological
S.4 Electro-mechanic cover control Electro-mechanic
S.5 Warning system using LED lighting Electronic
S.6 Sanitized container with the possibility of putting disposable bags inside Mechanic
S.7 Semi-transparent container Mechanic
S.8 Screen insulation between the electronics section of the container and drug section Mechanic
S.9 Degree of protection IP47 Mechanic
S.10 Unambiguous association between the container and patient medication Electronic, Firmware
S.11 Internal memory for access logging Electronic
S.12 Cylindrical shape of small dimensions in the central part of the body Mechanic
S.13 Short training course on the use of the device to the medical staff Methodological
S.14 Master key tags Technological
S.15 LCD character display Methodological
S.16 RFID reader with a microprocessor system equipped with a PC interface for manual or automatic programming Software, Technological
S.17 Opening the cover by pressing the release button Electro-mechanic
S.18 Record of device opening and closing on internal memory Software
S.19 Dimensions of the container equal to 8 cm in diameter and 11 cm in height Methodological
S.20 Adequate battery life Electronic

Table 2: Technical specifications.

The device, based on above requirements and technical specifications, is a container with an electronically operated lock that opens only when the opening attempt is performed by the patient to whom the drugs are destined (or by healthcare staff), thus dramatically reducing the chance of wrong administrations. The device integrates a custom miniaturized RFID reader operating at 13.56 MHz for the recognition of the patient and/or operator that must wear a simple and cheap passive ISO 15693 compatible wrist band. The compliancy to this standard guarantees maximum compatibility to bracelets commercially available.

As shown in figure 2, the device incorporates an internal tag that will contain information about the patient's identity and his drug therapy. This solution has been preferred to flash memories because in this way we can read/write on this "internal memory" using the onboard electronic card or a standard external RFID reader without any wired connections. Each attempt to open the device (successful or not) and each consequent alarm is logged using this internal tag as an on-board memory. The device is also provided with an USB port, but this is used just for battery recharge and for firmware maintenance.

pharmaceutica-analytica-acta-device-components

Figure 2: Block diagram of the device components.

As stated in specification S.5 (see Table 2), the container is provided with two LEDs, a red one and a green one, to give feedback to the user about the correct patient-drugs matching.

The technical specification S.15 is satisfied by providing a small 16 × 2 display. This is used to show the name of the patient for which the device has been prepared for, and to display the list of drugs prescribed to the patient.

The firmware is also able to read the drugs inserted into the device (provided that they are tagged with RFID) and to prevent its opening if some un-prescribed drug is found inside the container, alerting the patient/operator using the on-board display (Figure 3).

pharmaceutica-analytica-acta-drug-container

Figure 3: The RFID drug container.

Discussion

The patient himself can easily operate the presented device, since its input interface consists of a single button, to be pressed after placing the device in proximity of the RFID wristband. It is also possible, for caregivers, to force the opening by using their own RFID badge. All these operations are logged in the internal tag and can be wirelessly sent to a central HIS (Hospital Information System).

By logging the number of granted/denied openings, the device could feed a Hospital Risk Management System, providing the risk manager with some valuable data to assess the quality of the medication service. If inserted in a CEP (Complex Event Processing) system the proposed device could significantly increase the patient's safety as well as the knowledge of the process by the hospital executives.

The ideal usage scenario provides an interface between the device and the hospital information system and CPOE and with an automated pharmacy that provides single dose RFID-tagged medications. In this setting, the device can easily signal mistakes in the preparation before the wrong drugs can reach the patient. It will also prevent openings in this case.

Future works include improving the performance of the antenna, realizing a mechanical prototype and analysing the domestic scenario for possible use of the device at home.

Acknowledgements

Author thanks Lorenzo Baroncelli, Aldo Manetti and Giovanni Burchietti for the big effort profused in this project. Heartfelt thanks goes to prof. Biffi for the expert help.

References

  1. Nebeker JR, Barach P, Samore M H (2004) Clarifying adverse drug events: A clinician's guide to terminology, documentation, and reporting. Ann Intern Med 140: 795-801.
  2. Hartwig SC, Denger S D, Schneider PJ (1991) Severity-indexed, incident report-based medication error-reporting program. Am J Hosp Pharm 48: 2611-2616.
  3. Bates DW, Cullen DJ, Laird N, Petersen LA, Small SD, et al. (1995) Incidence of adverse drug events and potential adverse drug events. Implications for prevention. ADE Prevention Study Group. JAMA 274: 29-34.
  4. Johnson VR, Hummel J, Kinninger T, Lewis RR (2004) Immediate steps toward patient safety. Healthc Financ Manage 58: 56-61.
  5. Perrin RA, Simpson N (2004) RFID and bar codes--critical importance in enhancing safe patient care. J Healthc Inf Manag 18: 33-39.
  6. Iadanza E, Dori F, Miniati R, Bonaiuti R (2008) Patients tracking and identifying inside hospital: A multilayer method to plan an RFId solution. 30th Annual International Conference of the IEEE Engineering in Medicine and Biology Society, EMBS'08, Italy.
  7. BiffiGentili G, Dori F, Iadanza E (2010) Dual-frequency active RFID solution for tracking patients in a children's hospital. Design method, test procedure, risk analysis, and technical solution. Proceedings of the IEEE 98: 1656-1662.
  8. Iadanza Ernesto (2009) Recent Advances in Biomedical Engineering, InTech, Croatia.
Citation: Iadanza E (2012) A Smart RFID Device for Drugs Administration. Pharm Anal Acta S15:004

Copyright: © 2012 Iadanza E. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
bellicon