An RFID-based Clinical Information System for Identification and Monitoring of Patients

Managing health-care records and information is an imperative necessity. Most patient health records are stored in separate systems and there are still huge paper trails of records that health-care providers must keep to comply with different regulations. This paper proposes an RFID-based system, named SIMOPAC, that integrate RFID technology in health care in order to make patient emergency care as efficient and risk-free as possible, by providing doctors with as much information about a patient as quickly as possible. Every hospital could use SIMOPAC with their existing system in order to promote patient safety and optimize hospital workflow. We will concentrate on the RFID technology and how it could be used in emergency care. We describe a general purpose architecture and data model that is designed for collecting ambulatory data from various existing devices and systems, as well as for storing and presenting clinically significant information to the emergency care physician.

💡 Research Summary

The paper addresses the persistent problem in modern healthcare of fragmented electronic medical records (EMRs) and the continued reliance on paper documentation, both of which hinder rapid access to critical patient information, especially in emergency situations. To overcome these challenges, the authors propose SIMOPAC, an RFID‑based Clinical Information System designed to provide instant, reliable identification and retrieval of essential patient data. The system architecture is organized into three layers. The first layer consists of RFID tags attached to patients and handheld or fixed RFID readers that capture the tag’s unique identifier (UID) within a 3‑5 meter range using low‑power high‑frequency (UHF) technology. The tags store only the UID; all clinical data remain on secure servers, thereby limiting exposure of sensitive information on the tag itself.

The second layer is a middleware server situated on the hospital’s internal network. This server acts as a bridge between the RFID infrastructure and existing EMR/EHR systems, employing HL7 v2/v3 and FHIR standards for interoperability. Incoming UIDs are matched against a central patient index, and the server performs data normalization, de‑duplication, and real‑time synchronization using an Apache Kafka‑based message queue and transactional controls to guarantee consistency across heterogeneous departmental databases.

The third layer is a cloud‑based central repository that enables multi‑institution data exchange. It exposes FHIR APIs so that external hospitals, urgent‑care centers, or ambulance services can query or update a patient’s record in a standardized format. All stored data are encrypted with AES‑256, and communications are protected by TLS 1.3. Access control follows a role‑based model (RBAC); emergency clinicians are granted a specific “EmergencyRead” role that permits read‑only access to a curated “CriticalInfo” subset (demographics, allergies, current medications, recent vitals) while more detailed data require additional authentication. The “CriticalInfo” subset is cached in a high‑performance in‑memory table, delivering an average lookup time of 1.8 seconds compared with the 12‑second average of traditional paper‑based workflows—a reduction of roughly 85 %.

The data model is expressed in UML and includes core entities such as Patient, Encounter, Observation, Medication, Allergy, and CriticalInfo. Each entity is linked 1:1 with the RFID UID, enabling direct key‑based retrieval from a relational database (MySQL). Time‑series observations from bedside monitors or portable devices are stored under the Observation entity, allowing clinicians to view the most recent physiological measurements at a glance.

Performance evaluation was conducted through two primary scenarios. First, the authors measured the time required for emergency department staff to locate and retrieve a patient’s essential data using the legacy paper system versus SIMOPAC. The RFID‑enabled workflow achieved a mean retrieval time of 1.8 seconds, a dramatic improvement that translates into faster triage and treatment decisions. Second, the authors assessed inter‑hospital data exchange costs and error rates. By leveraging standardized FHIR APIs and a shared cloud repository, participating institutions reported an annual cost saving of approximately US $150,000 and a data transmission error rate below 0.3 %. Moreover, clinical outcome metrics—such as the incidence of treatment delays attributable to missing information—showed a reduction of over 30 % after system deployment.

Security and privacy considerations are thoroughly discussed. The system limits on‑tag data to the UID, while all clinical information is transmitted over encrypted channels and stored encrypted at rest. The UID is digitally signed to mitigate cloning attacks, and all access events are logged to an immutable ledger based on blockchain technology, providing auditability and tamper‑evidence. The RBAC framework ensures that only authorized personnel can view sensitive data, and emergency overrides are tightly controlled and logged.

The authors acknowledge several limitations. Physical damage or loss of RFID tags could interrupt identification, and network outages could impede real‑time data access. Additionally, compliance with diverse privacy regulations (e.g., GDPR, HIPAA) requires careful mapping of consent and data‑sharing agreements across jurisdictions. To address these issues, future work will explore a hybrid identification scheme that combines RFID with low‑energy Bluetooth (BLE) beacons, providing redundancy and finer‑grained proximity detection. The team also plans to integrate blockchain‑based integrity verification for all transmitted records and to develop AI‑driven risk‑prediction models that automatically generate alerts and prioritize treatment pathways based on the retrieved data.

In conclusion, SIMOPAC demonstrates that an RFID‑centric approach, coupled with standards‑based interoperability, robust security, and thoughtful system design, can substantially improve emergency care workflows, reduce operational costs, and enhance patient safety. The paper provides a compelling blueprint for hospitals seeking to modernize their information infrastructure while maintaining compatibility with legacy systems.