Smart Container Authentication via Server Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing pharmaceutical fulfillment systems lack effective monitoring and tracking of medication access, leading to issues such as lost, stolen, or tampered containers, medication errors, and non-adherence to prescribed regimens.
Innovation Solution
The implementation of smart containers that register users through a central server, allowing only authorized individuals to access and handle the containers, and providing real-time monitoring and notifications for adherence and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional pharmaceutical fulfillment systems are used, then the system is simple and easy to operate, but there is no effective monitoring and tracking of medication access, leading to lost, stolen, or tampered containers
Solution Approach 1:
The system performs preliminary actions by registering users and assigning roles before medication distribution. The smart container is pre-configured with authorized user information, enabling automatic authentication and tracking when users access the container. This preliminary setup ensures security and monitoring are in place before any medication handling occurs.
Solution Approach 2:
The patent introduces a server as an intermediary between users and smart containers. The server manages user registrations, stores role information, and coordinates authentication processes. This intermediary component enables centralized control and monitoring of medication access without requiring complex embedded systems within each container.
2Reliability
If smart containers with user registration and role-based access are implemented, then access control and monitoring are improved, but the device complexity increases
Solution Approach 1:
The system segments functionality between the smart container, user devices, and the server. The container itself remains relatively simple, while authentication and authorization logic are distributed to user devices and centralized on the server. This segmentation reduces the complexity burden on individual components while maintaining comprehensive access control.
Solution Approach 2:
The smart container is designed with multi-functionality, serving as both a medication storage device and a communication node that can detect user devices, exchange authentication data, and report access events. By combining these functions in a single device, the system avoids needing separate specialized components for each function.
3Reliability
If real-time monitoring and historical ledger tracking are implemented, then accountability and error reduction are improved, but data management complexity increases
Solution Approach 1:
The system implements feedback mechanisms where the smart container continuously monitors access events, detects user devices, and communicates with the server to update the historical ledger. This automated feedback loop ensures real-time tracking of medication access without requiring manual intervention or complex data management procedures.
Solution Approach 2:
The smart container performs self-service by automatically detecting user devices, retrieving authentication information, and logging access events. The system autonomously manages its own monitoring and reporting functions, reducing the need for external management infrastructure and simplifying data management complexity.
Data Source
AI summary
A system for monitoring access to a contained medication is disclosed. The system includes a server configured to store user information for each of a plurality of registered users. The system also includes a smart container configured to hold a medication. The smart container includes a processor configured to (a) detect a user device of a user in possession of the smart container, (b) determine if the user device is associated with one of the registered users, and (c) if the determination is affirmative, manage a user session with the user device and transmit one or more session messages to the server. The server is configured to store a transaction corresponding to each of the session messages to thereby create a transaction history for the smart container.