Automated Mobile Pharmacy

Abstract

An automated, mobile pharmacy system is disclosed. The invention is comprised of a small structure or conventional shipping container converted into a secure pharmacy with robotic systems and artificial intelligence software operations that can be delivered to communities around the world. Embodiments of the invention can be rented and managed by pharmacists. The system within the pharmacy conducts automated prescription filling and includes drive-through pickups at an attached kiosk, scheduled walk-in pickups at internal lockers, mail deliveries, and home delivery services. During drive through and internal locker pickups, users present their identification and security code to the window to pick up medications. During scheduled walk in pickups, users are notified when a prescription is ready and enter the pharmacy using a security code and retrieve their medications from secure lockers inside. An object of the invention is to enhance secure access to prescription medications.

Claims

1. A mobile pharmacy comprised of the following parts: a) a portable building for storing and dispensing medications; b) automated robotic arms for preparing medications for pickups and deliveries; c) computer systems for remotely managing the mobile pharmacy; d) a kiosk for customer pickups; e) lockers for customer pickups and postal and courier delivery pickups. f) a software application; and g) a cloud network.

2. The mobile pharmacy of claim 1 wherein the mobile pharmacy can be rented by pharmacists and pharmacy companies.

3. The mobile pharmacy of claim 1 wherein the mobile pharmacy can transported to multiple locations to serve communities.

4. The mobile pharmacy of claim 1 wherein the portable building has exterior and interior security cameras and systems.

5. The mobile pharmacy of claim 1 wherein the computer systems and automated robotic arms can be monitored and shut down by the pharmacist remotely.

6. The mobile pharmacy of claim 1 wherein the kiosk and lockers have customer identification verification systems.

7. The mobile pharmacy of claim 1 wherein the software application manages patient profiles and pharmacist demographics, alerts stakeholders of prescription problems, and archives transactions and medication histories.

8. The mobile pharmacy of claim 1 wherein the software application allows doctors to add prescription refills to a patient's profile and automatically notifies the patient of the prescription status.

9. The mobile pharmacy of claim 1 wherein the software application allows patients to request prescription refills, schedule home deliveries, and postal deliveries of medications remotely online.

10. The mobile pharmacy of claim 1 wherein the software application allows pharmacists to monitor the mobile pharmacy security operations, prescription filling, drug expiration dates and restock supplies for the mobile pharmacy in real time online.

11. The mobile pharmacy of claim 1 wherein the software application provides consultations to patients by means of AI predictive algorithms.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0015] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate some, but not the only or exclusive, examples of embodiments and/or features.

[0016] FIG. 1 shows a perspective view of the invention in use.

[0017] FIG. 2 shows a perspective view of the prescription filling automation.

[0018] FIG. 3 shows a close-up view of the robotic automation.

[0019] FIG. 4 shows a side view of the pickup kiosk.

[0020] FIG. 5 shows a side view of the pickup kiosk.

[0021] FIG. 6 shows a close-up view of the pickup kiosk.

[0022] FIG. 7 shows a representative view of the invention's process.

[0023] Other aspects of the present invention shall be more readily understood when considered in conjunction with the accompanying drawings, and the following detailed description, neither of which should be considered limiting.

DETAILED DESCRIPTION OF FIGURES

[0024] In this description, the directional prepositions of up, upwardly, down, downwardly, front, back, top, upper, bottom, lower, left, right and other such terms refer to the device as it is oriented and appears in the drawings and are used for convenience only; they are not intended to be limiting or to imply that the device has to be used or positioned in any particular orientation. Conventional components of the invention are elements that are well-known in the prior art and will not be discussed in detail for this disclosure.

[0025] FIG. 1 shows a perspective view of the preferred embodiment of the invention 1 comprised of a plurality of portable buildings including but not limited to conventional shipping containers etc. having a multitude of secure windows, doors and prescription storage lockers etc. The structure having a multitude of internal and external security cameras. The figure showing patient 2 logging into the mobile pharmacy software 4 and receiving a message on smart phone 3. The figure also showing the mobile pharmacy being managed by pharmacist 5 remotely. FIGS. 2 and 3 showing automated robotic arms 7 retrieving medications from secure storage drawers 6 and preparing them for deliveries and pickups. Said automated robotic arms being controlled by workstations with software connected remotely to a cloud network that is governed by a pharmacist. FIGS. 5-6 showing another embodiment of the invention having a pickup kiosk 9 that allows users to verify their identity (by scanning barcodes, QR codes, facial recognition, entering passcodes on the touchscreen, etc.), make payments (using a credit card, cash, PayPal and Venmo etc.), and then receiving their medications through the kiosk.

[0026] Those of skill in the art will recognize that mobile applications are written in several languages include, by way of non-limiting examples, C, C++, C#, Objective-C, Java, Javascript, Pascal, Object Pascal, Python, Ruby, VB.NET, WML, and XHL/HL with or without CSS, or combinations thereof. The app in invention 1 is also compatible with a plurality of operating systems such as, but not limited to: Windows, Apple, and Android, and compatible with a multitude of hardware platforms such as, but not limited to: personal desktops, laptops, tablets, smartphones and the like. Suitable mobile application development environments are available from several sources. Commercially available development environments include, by way of non-limiting examples, AirplaySDK, alcheMo, Appcelerator, Celsius, Bedrock, Flash Lite, .NET Compact Framework, Rhomobile, and WorkLight Mobile Platform. Other development environments are available without cost including, by way of non-limiting examples, Lazarus, MobiFlex, MoSync, and Phonegap. Also, mobile device manufacturers distribute software developer kits including, by way of non-limiting examples, iPhone and iPad (iOS) SDK, Android SDK, BlackBerry SDK, BREW SDK, Palm OS SDK, Symbian SDK, webOS SDK, and Windows Mobile SDK. Those of skill in the art will recognize that several commercial forums are available for distribution of mobile applications including, by way of non-limiting examples, Apple App Store, Google Play, Chrome Web Store, BlackBerry App World, App Store for Palm devices, App Catalog for webOS, Windows Marketplace for Mobile, Ovi Store for Nokia devices, Samsung Apps, and Nintendo DSi Shop.

[0027] In some embodiments, a computer program includes a standalone application, which is a program that is run as an independent computer process, not an add-on to an existing process, e.g., not a plug-in. Those of skill in the art will recognize that standalone applications are often compiled. A compiler is a computer program(s) that transforms source code written in a programming language into binary object code such as assembly language or machine code. Suitable compiled programming languages include, by way of non-limiting examples, C, C++, Objective-C, COBOL, Delphi, Eiffel, Java™, Lisp, Python™, Visual Basic, and VB .NET, or combinations thereof. Compilation is often performed, at least in part, to create an executable program. In some embodiments, a computer program includes one or more executable complied applications. In some embodiments, the computer program includes a web browser plug-in (e.g., extension, etc.). In computing, a plug-in is one or more software components that add specific functionality to a larger software application. Makers of software applications support plug-ins to enable third-party developers to create abilities which extend an application, to support easily adding new features, and to reduce the size of an application. When supported, plug-ins enable customizing the functionality of a software application. For example, plug-ins are commonly used in web browsers to play video, generate interactivity, scan for viruses, and display particular file types. Those of skill in the art will be familiar with several web browser plug-ins including, Adobe Flash Player, Microsoft Silverlight, and Apple QuickTime.

[0028] In view of the disclosure provided herein, those of skill in the art will recognize that several plug-in frameworks are available that enable development of plug-ins in various programming languages, including, by way of non-limiting examples, C++, Delphi, Java™, PHP, Python, and VB .NET, or combinations thereof. Web browsers (also called Internet browsers) are software applications, designed for use with network-connected digital processing devices, for retrieving, presenting, and traversing information resources on the World Wide Web. Suitable web browsers include, by way of non-limiting examples, Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Apple Safari, Opera Software Opera, and KDE Konqueror. In some embodiments, the web browser is a mobile web browser. Mobile web browsers (also called micro-browsers, mini-browsers, and wireless browsers) are designed for use on mobile digital processing devices including, by way of non-limiting examples, handheld computers, tablet computers, netbook computers, subnotebook computers, smartphones, music players, personal digital assistants (PDAs), and handheld video game systems. Suitable mobile web browsers include, by way of non-limiting examples, Google Android browser, RIM BlackBerry Browser, Apple Safari, Palm Blazer, Palm WebOS Browser, Mozilla Firefox for mobile, Microsoft Internet Explorer Mobile, Amazon Kindle Basic Web, Nokia Browser, Opera Software Opera Mobile, and Sony PSP™ browser. Software Modules.

[0029] In some embodiments, the platforms, systems, media, and methods disclosed herein include software, server, and/or database modules, or use of the same. In view of the disclosure provided herein, software modules are created by techniques known to those of skill in the art using machines, software, and languages known to the art. The software modules disclosed herein are implemented in a multitude of ways. In various embodiments, a software module comprises a file, a section of code, a programming object, a programming structure, or combinations thereof. In further various embodiments, a software module comprises a plurality of files, a plurality of sections of code, a plurality of programming objects, a plurality of programming structures, or combinations thereof. In various embodiments, the one or more software modules comprise, by way of non-limiting examples, a web application, a mobile application, and a standalone application. In some embodiments, software modules are in one computer program or application. In other embodiments, software modules are in more than one computer program or application. In some embodiments, software modules are hosted on one machine. In other embodiments, software modules are hosted on more than one machine. In further embodiments, software modules are hosted on cloud computing platforms. In some embodiments, software modules are hosted on one or more machines in one location. In other embodiments, software modules are hosted on one or more machines in more than one location.

[0030] FIG. 7 showing a representative view of the preferred embodiment of the invention's process. Pharmacy managers having access to functions that include but are not limited to: administrative operations 10 (entering their demographics and credentials, logging into the invention website, purchasing a rental subscription to the mobile pharmacy, monitoring medicinal stores for expirations etc.); monitoring the mobile pharmacy 11 (scanning security cameras, reviewing monetary transactions and sales, etc.); overriding automated robotic systems 12 (emergency shutdowns, de-energizing robotic arms, controlling the kiosk etc.); providing real-time video consultation with patients remotely 30; receiving emergency alerts 32 (break-ins, tapering, fire emergencies etc.); and reviewing and restocking medical supplies 33 (physical access to the mobile pharmacy—including all doors and kiosk entries etc.). The figure also showing operations available to a patient, including but not limited to: administrative functions 23 (entering demographics, pharmaceutical needs, and purchase history etc.); medical archives 24 (insurance providers, prescription status, current medications, pickup and delivery history etc.); prescription requests 25 (status, delivery type, prescription filled dates, etc.); notifications 27 (prescription changes, prescription status, drug news via SMS, email, text etc.); remote consultations scheduled with pharmacist 28 (including AI algorithms that are constantly learning about drug profiles, new medications, and drug interactions to make accurate predictions from meta data gathered); and identity scan operations 29 (profile barcode, QR code, retinal scan, finger scan, facial recognition, kiosk scans etc.).

[0031] The pharmacist and the patient being connected to the mobile pharmacy by means of cloud network 16. Cloud network 16 having routines and operations such as but not limited to: administrative management 17 (managing stakeholder accounts, subscriptions, payments, rental operations etc.); automated prescription filling algorithms 18 (preprogrammed and dynamic robotic arm operations); prescription filling and verification systems 19 (retrieval routines and security recordings etc.); prescription pickup scheduling 34 (notifications, Google calendars, etc. or patient pickups, postal deliveries and courier visits etc.); artificial intelligence operations 20 (predicting proper medical filled processes and automated recommendations to patients, etc.); archive database 21 (patient and prescription history, digital security logs, medical supply orders, pharmacy transactions and history etc.); security surveillance and network encryptions 22; and notifications to stakeholders 35 (SMS, texts, emails etc.).

[0032] It is additionally noted and anticipated that although the device is shown in its most simple form, various components and aspects of the device may be differently shaped or slightly modified when forming the invention herein. As such those skilled in the art will appreciate the descriptions and depictions set forth in this disclosure or merely meant to portray examples of preferred modes within the overall scope and intent of the invention, and are not to be considered limiting in any manner. While all of the fundamental characteristics and features of the invention have been shown and described herein, with reference to particular embodiments thereof, a latitude of modification, various changes and substitutions are intended in the foregoing disclosure and it will be apparent that in some instances, some features of the invention may be employed without a corresponding use of other features without departing from the scope of the invention as set forth. It should also be understood that various substitutions, modifications, and variations may be made by those skilled in the art without departing from the scope of the invention.