REFERENCE TO RELATED APPLICATIONSThis application is a divisional of U.S. patent application Ser. No. 11/013,285 filed Dec. 15, 2004, which application claims the benefit of U.S. Provisional Patent Application No. 60/565,221 filed Apr. 24, 2004, the entirety of which prior applications are incorporated herein by this reference.
FIELD OF THE INVENTIONThe invention relates generally to systems for facilitating patient medication compliance, and more particularly to apparatus and methods for remotely delivering individual doses of therapeutic products to a patient in a non-sequential fashion. The invention allows dosage amounts to be remotely tailored in real-time to accommodate fluid medical conditions.
BACKGROUND OF THE INVENTIONPatient non-adherence to prescribed medication regimens is a significant problem which undermines efforts to manage chronic illnesses. Factors such as an overall increase in outpatient medical procedures have contributed to an increased level of responsibility being placed upon patients and caregivers in the administration of prescription drugs. While estimates of medication non-adherence in remote, residential settings typically range from 30-60%, depending on the disease state, elderly patients average a rate of more than 45% due in part to visual, auditory, and cognitive impairments. Drugs not taken, or taken incorrectly, incur the same health care costs as fully adherent regimens, but without the expected medical outcome. The consequences of non-adherence can be significant, resulting in emergency room visits, extended hospitalizations, long-term care facility admissions, and death.
The ability to comply with a medication regimen is complicated in situations where dosing amounts change over time. For instance, prescribed dosing amounts are frequently a function of ongoing laboratory tests that determine the patient's status. Likewise, appropriate dosage amounts are determined in accordance with a patient's health condition and must reflect unexpected changes in such condition. In these situations, healthcare practitioners such as physicians, pharmacists, and nurses need to be able to adjust a patient's dosage as quickly as possible. Medication compliance is particularly important when narrow therapeutic index drugs are prescribed, as over-medicating or under-medicating a patient can cause serious side effects, illness and even death.
A fairly large number of devices have been developed for prompting a patient to take a prescribed dose of medication at the correct times. Existing devices function primarily to remind patients when to take a particular medication and to sequentially deliver that medication in accordance with a predetermined schedule. Many of these devices are designed to expel medication automatically, in accordance with a predetermined schedule. In this regard, the devices do not provide adequate protection against both under-dosage and over-dosage. If the patient fails to take the medication according to schedule, the devices continue to expel medication at set intervals based on the premise that the patient took all previous medications appropriately. Such a situation greatly enhances the risk of non-compliance, wherein a patient takes less medication than is prescribed. Conversely, if the patient does not take the medication according to schedule, but too close to the time for taking subsequent medication, the patient faces the risk of over-dosage.
Certain devices incorporate means for retrieving pills which are discharged but not removed from the device. Some of these devices provide notification to caregivers of a patient's failure to take medication according to schedule. Other devices have been integrated into comprehensive medication management and delivery systems in which a healthcare practitioner remotely monitors information regarding patient compliance and non-compliance with a medication regimen. While these systems enhance patient compliance with a prescribed treatment regimen, they are deficient in one notable respect, that is, they do not provide a mechanism by which a patient's failure to take a scheduled dose of medication can be rectified in minutes. As such, the systems do not overcome the problem of patient under-dosage and over-dosage. This drawback is particularly significant with respect to high risk patient populations, where patients frequently suffer from cognitive, visual and/or auditory impairments which contribute to non-adherence.
An additional shortcoming of the existing systems is that they fail to provide a mechanism by which a prescribed dosage can be remotely adjusted in minutes, in response to an unexpected change in a patient's health condition. Although the systems allow a healthcare practitioner to communicate a change in dosing amount to the patient, they do not enable the practitioner to immediately and remotely change, adjust or discontinue a prescribed dosage. There is often a delay of several hours, and in some cases, several days, before a patient is able to procure the new dosage. During this period, the patient may be confused as to the correct regimen and continue to take the discontinued dosage. In addition, because a new prescription is required every time a dose is adjusted, the patient is must travel to a physician's office and/or a pharmacy. Although this may pose an inconvenience to some patients, this is particularly disadvantageous to mobility-impaired patients and is a major contributor to drug non-compliance. Frequently the patient's condition deteriorates, as the patient is unable to continue the correct course of treatment.
A further drawback of the conventional systems is that prescriptions are filled in either standard thirty day or sixty day allotments. With such means, there is no accurate way to inventory pharmaceuticals and/or to audit patient compliance or consumption of the product. This is due in part to the fact that the pharmaceuticals are dispensed in a lot, and not every pill or dose is separately bar coded and traceable.
The above-described medication management and delivery systems suffer from a still further limitation, namely, they fail to establish a secure data communication process to deploy communications to and from a remote medication delivery device based in a patient's home while protecting patient privacy. Maintaining patient privacy in the data communication process has to date been a formidable challenge. Moreover, an increasing number of regulations regarding the maintenance and storage of patient data have been enacted in response to the Health Insurance Portability Accountability Act. Accordingly, there is a need and a desire for a cost-effective system that quickly addresses a patient's non-compliance with a prescribed drug regimen in real time and minimizes disruptions to a patient's course of treatment while protecting patient information.
SUMMARY OF THE INVENTIONThe present invention comprises a medication management and compliance system for enabling a healthcare practitioner to remotely manage and deliver sealed unit dose packages of prescription and non-prescription therapeutic products to a patient, on a dose by dose basis, and in a manner that provides immediate confirmation that a dose has been delivered. Clinical software is used for storing patient prescription and dosing regimen information, enabling authorized healthcare personnel to remotely deliver a unit dose therapy to a patient and monitor patient compliance with a dosing regimen, without violating patient privacy. The system includes delivery apparatus located in proximity to the patient, wherein the delivery apparatus is remotely coupled to the clinical software and to a control center by means of a data communications network.
The delivery apparatus features a controller for executing command signals received from the control center and clinical software, as well as a storage area for storing unit dose packages. The apparatus delivers a sealed, unit dose package to the patient at a scheduled dosing time, in response to a command signal. The present system enables the healthcare practitioner to remotely deliver any unit dose package stored within the delivery apparatus to a patient, in non-consecutive fashion, without being limited by a predetermined sequence. In this way, medication dosage amounts can be instantaneously tailored to adapt to fluid medical conditions. The present invention provides a fully integrated, real-time, non-sequential, comprehensive medication management and compliance system that is the first to ensure accurate delivery of both custom packaged and commercially available sealed unit dose and unit-of-issue therapeutic products to patients.
BRIEF DESCRIPTION OF THE DRAWINGSFIG. 1 is a perspective view of a non-sequential medication delivery module in accordance with one embodiment of the invention.
FIG. 2 is a block diagram showing a non-sequential medication delivery module with remote monitoring and access control in accordance with an embodiment of the invention.
FIG. 3 is an assembly view of one example of a non-sequential medication delivery module in accordance with an embodiment of the invention.
FIGS. 4 and 5 are cutaway views showing the friction drive assembly and storage elevator in accordance with one embodiment of the invention.
FIG. 6 is a perspective view depicting the storage apparatus in accordance with the present invention.
FIG. 7ais a cross-sectional view illustrating the mechanism of operation of the latch apparatus.FIG. 7bis an exploded view of the latch apparatus in an unlocked position.
FIG. 8 is a cross-sectional view illustrating the mechanism of operation of the friction drive assembly with respect to an incoming medication carrier in accordance with an embodiment of the invention.
FIG. 9ais a cross-sectional view of a medication carrier fully inserted into the delivery module.FIG. 9bis an exploded view of the latch apparatus in a locked position.
FIG. 10 is a cross-sectional view illustrating the mechanism of operation of the carriage drive assembly in accordance with one embodiment of the invention.
FIG. 11 is a cross-sectional view illustrating the operation of the storage elevator and associated linear motion assembly in accordance with an embodiment of the invention.
FIG. 12ais a cross-sectional view showing the ejector assembly in a rest position and operative position for ejecting a unit dose package from a medication carrier in accordance with one embodiment of the invention.
FIG. 12bis an assembly view of the ejector assembly shown inFIG. 12ain accordance with an embodiment of the invention.
FIG. 13 is a cross-sectional view showing the ejected unit dose package ofFIG. 12aalong with previously ejected unit dose packages.
FIGS. 14 and 15 depict medication carriers containing unit dose packages of varying strengths in accordance with the present invention.
FIGS. 16-20 are electrical schematics illustrating various operations of the non-sequential medication delivery module in accordance with the present invention.
FIGS. 21a, bandcare perspective views of medication carriers containing 32, 20 and 16 stalls, respectively, for accommodating different sized unit dose packages.
FIGS. 22-23 and25-26 are flow charts illustrating the operations of the non-sequential medication delivery module and compliance system of the present invention.
FIG. 24 is a flow chart illustrating the process that may take place to suitably deliver a prescribed dosage to a patient in accordance with an embodiment of the invention.
FIGS. 27-31 are examples of worksheets that appear on the computer monitor of healthcare personnel.
DETAILED DESCRIPTION OF THE INVENTIONThe present invention provides a fully integrated, real-time, non-sequential medication management and compliance system for prompting a patient remote from a clinical environment to take medication in accordance with a prescribed schedule. A principal advantage of the delivery module of the present invention is that it implements a prescribed medication regimen by delivering a selected unit dose package of medication to a patient upon receipt of an encrypted command signal and patient confirmation. These multiple safeguards ensure that the patient receives the prescribed medication at the correct dosing times. In this manner, the invention enhances patient compliance and allows for chronotherapeutic applications that maximize medication benefits and minimize medication side effects. Also significant is the fact that command signals are securely transmitted to and from the delivery module without compromising patient privacy in any way.
A further advantage of the present invention is that it enables a healthcare practitioner to remotely monitor patient compliance with a prescribed medication regimen and receive rapid notification of non-compliance. Most notably, the healthcare practitioner can promptly adjust the patient's treatment plan to accommodate a missed dosage or to reflect other fluid medical conditions, such as an unexpected change in the health status of the patient. Where necessary, dosage adjustments can be made immediately, without the need for a new prescription. As such, the invention minimizes any loss of time which may complicate non-compliance and reduces medication waste by eliminating the need for a patient to discard remaining doses in the event of a dose adjustment.
A still further advantage of the invention is that it protects the patient from adverse drug reactions and related consequences of over- and under-medicating by ensuring that the patient remains within recommended therapeutic levels. The patient receives a required dosage at the proper time, thereby reducing the incidence of emergency room visits and hospital admissions occasioned by non-adherence to a prescribed drug regimen or other delays in the administration of prescribed medication. In addition, unanticipated visits to health care providers are reduced, thereby reducing overall health care costs. This cost-effective system can be used by healthcare practitioners operating in a variety of settings.
Referring now to the Figures, there is shown inFIG. 2 an overview of the system of the present invention. Acontrol center101, such as a facility operated by INRange Systems, Inc., stocks custom packaged and prepackaged, unit dose prescription and non-prescription medical products, pharmaceuticals and nutraceuticals from various drug manufacturers and suppliers. Such therapeutic products include, but are not limited to, solid orally consumed doses, liquid orally consumed dosages, and injection devices that contain doses that are delivered or administered at the point of care. It will be understood that the term “medication” as used herein is intended to include individual, unit-of-issue doses of prescription and non-prescription medications, medical supplies, pharmaceuticals and nutraceuticals, in a variety of dosage forms and strengths, including single and multiple compound medications. Specific examples include pills, tablets, capsules, suppositories, inhalers, lotions, prefilled syringes, powders, suspensions, and diagnostic materials such as blood testing strips. At thecontrol center101, the typically foil-wrapped or blister-packed unit dose packages27 are inserted intoindividual stalls28 of one of severaldifferent medication carriers26, each carrier being designed and sized to accommodate almost any commercially availableunit dose package27.
Exterior dimensions of themedication carrier26 can be slightly varied, but must be configured to allow thecarrier26 to easily fit within thedelivery module33. Anelectronic code29, such as a bar code or radio frequency identification tag, is affixed to eachmedication carrier26. Theelectronic code29 identifies the carrier type and configuration and provides medication related information, based on a unique identifier such as a serial number. The encoded data is programmed into thecontrol center101computer database35, enabling thecontrol center101 to accurately track and account for eachunit dose package27 at all times, in conjunction with thedelivery module33, as described below.
Referring toFIG. 15, themedication carrier26 comprises a receptacle for holding individual, unit dose packages27 in a non-sequential fashion. Standard unit dose packages28 normally include a plastic bubble for holding the unit dose therapy and a seal fabricated from paper or foil laminate for retaining the unit dose within the plastic bubble. “Identifying indicia”31 such as, for example, an electronic code and human readable information, is imprinted on the seal of theunit dose package27 to denote the medication contained in such package. Themedication carrier26 is designed to permit the identifyingindicia31 to be electronically read by abar code scanner98, optical recognition scanner, radio frequency scanner or other such device, without removing the unit dose packages27 from themedication carrier26. Themedication carrier26 allows an individual,unit dose package27 to be remotely and non-consecutively accessed and discharged from thecarrier26 without disrupting the other unit dose packages27 contained therein.
As shown inFIG. 21b, themedication carrier26 may include 32 stalls arranged in four rows of eightstalls28. In this arrangement, thecarrier26 stores medication for up to 30 calendar days and provides additional surfaces for affixing a label containing a uniqueelectronic identifier29.FIGS. 21aand21cillustratemedication carriers26 having 20 and 16 stalls, respectively, sized and shaped to accommodate larger unit dose packages27. Eachstall28 of themedication carrier26 includes retaining means30 for holding the sealed,unit dose package27 within thestall28 until a scheduled dosing time. At such time, theunit dose package27 is expelled through an aperture in saidstall28.
A printable surface containing identifying indicia is provided on the upper surface of themedication carrier26, along its peripheral edges. The printable surface features location markers such as, for example, infrared absorbent ink dots which indicate certain points of interest on thecarrier26.
Normally, thedelivery module33 is remotely located from a clinical facility where healthcare personnel are based such as, for example, a physician's office, pharmacy, pharmacy benefit manager (PBM), hospital, outpatient clinic, nursing station, assisted living facility or long-term care facility. Each clinical facility is equipped with a computer that includes, for example, a standard microprocessor, input-output circuits, a memory for storing patient records including prescription and dosing schedules, a ROM for storing the operating program and other system information, and a monitor for receiving visual feedback.Software32 such as the Fulfillment, Adjustment and Compliance Tracking System (FACT™), commercially available from INRange Systems, Inc., operates on computer servers at the clinical facility. Patient information is accessed by way of the software's32user interface100, which features a complement of menu-driven worksheets that appear on the monitor of a designated healthcare practitioner (FIGS. 27-31).
Theuser interface100 enables the healthcare practitioner to remotely and actively treat a patient by entering appropriate instructions into his/her computer terminal using a keyboard, mouse or other input device. The healthcare practitioner may, for example, input or retrieve prescription information, configure formularies or therapeutic regimens, remotely schedule a new regimen, monitor patient compliance with a dosing regimen, or modify the dosage amounts of an existing regimen. The entered instructions are transmitted to thecontrol center101, where the instructions are interpreted and routed to theappropriate delivery module33 based on a unique identifier assigned thereto. Theuser interface100 also displays real-time notification of dosage delivery results communicated to theclinical software32, enabling the healthcare practitioner to take immediate action, if necessary.
Theclinical software32 is securely installed within the confines of each clinical facility and utilizes the facility'snetwork security34 policies and procedures to authenticate users and network access to patient data. As described below, thecontrol center101 has no access to patient identifiable information and cannot in any way determine the identity or location of any patient utilizing thedelivery module33. This secure technical and physical information infrastructure is in accord with the Health Insurance Portability and Accountability Act (HIPAA).
Control software35 programmed to constantly monitor for signals from both theclinical software32 anddelivery module33 is installed on computer servers based at thecontrol center101. Thecontrol software35 administers the various treatment instructions entered by the healthcare practitioner, but does not implicate patient information stored within thesoftware database32 of the clinical facility. In general, thecontrol software32 records and stores information related to the operation and contents of thedelivery module33, such as the types and locations ofmedication carriers26 stored within themodule33, a complete inventory of the unit dose packages27 contained within eachmedication carrier26, and a history of all dose administration operations over a set time period. This record keeping and inventorying function is achieved, in part, through the use of electronic coding and other identifiers which are assigned to thedelivery module33,medication carriers26 and unit dose packages27, respectively. The identifiers enable thecontrol center101 to correlate aparticular medication carrier26 to the inventory of unit dose packages27 contained therein, with the assistance ofelectronic code scanners92,98 located within thedelivery module33 for imaging and transmitting encoded information to the controller.
A unique identifier such as a serial number (Unit Identification Number) is typically programmed into thedelivery module33 at the time of manufacture. Similarly, identifying indicia31 (FIG. 14), including an electronic code and human readable information, is imprinted on the seal of eachunit dose package27 by the drug manufacturers or repackagers. Theelectronic code31 identifies thepackage27 contents, including, for example, the medication name, dosage strength, lot number, expiration date, national drug code number (NDC) and/or unique package serial number. A plurality of unit dose packages27 representing a prescribed course of medication are placed into thestalls28 of amedication carrier26, in any order. The unit dose packages27 need not be organized chronologically, as is required in the existing dosage delivery systems, since eachpackage27 is randomly accessed and retrieved. The identifyingindicia31 on the seal of each unit dose package is scanned into the control center computer so that an audit trail of eachpackage27 is maintained.
Thecontrol software35 assigns aunique identifier29, such as a serial number, to themedication carrier26. Theidentifier29 correlates themedication carrier26 to the inventory of unit dose packages27 contained therein and denotes the contents and location of eachunit dose package27. Thecarrier identifier29 is reflected within one or more electronic codes which are printed onto a label and affixed to separate locations on themedication carrier26. This redundancy ensures that at least oneelectronic identifier29 is accessible to acode reader92,98. This information is stored within thecontrol software database35.
As discussed above, the unit dose packages27 are placed into one of severaldifferent medication carriers26, according to the size and configuration of thepackage27. For instance, packages containing syringes are typically placed in amedication carrier26 having longer and wider cells, while packages of oral solid doses are normally placed in acarrier26 containing smaller cells. Position coordinates, based on the internal geometry of themedication carrier26, are stored in thecontrol software database35 to pinpoint the location of eachunit dose package27 within thecarrier26. These coordinates are also reflected in theelectronic identifier label29 that is affixed to themedication carrier26. Thecarrier26 can be inserted into thedelivery module33 in more than one way. Therefore thecontrol software35 also generates a set of location markers such as, for example, infrared absorbent ink dots or lines which indicate certain points of interest on thecarrier26, which are included on a printable surface (e.g. cardboard) preferably disposed on the upper surface of themedication carrier26. This redundancy ensures that at least one location marker can be imaged by an optical recognition reader or otherelectronic scanner98.
Communication between thedelivery module33 and a healthcare practitioner is accomplished through thecontrol software layer35. Contained within this layer are the communication protocols for eachdelivery module33, which correspond to the type of communication link that is selected for a particular module.Suitable communications media36 include radio frequency, internet, modem, telephone line, land line, wireless network, pager network or other transmission means that enables control and data signals to be exchanged with thedelivery module33. Preferred communications media include dedicated Local Area Network and/or existing Local Area Networks (e.g. copper, fiber or wireless). Thecontrol software35 communication protocols enable alert signals to be conveyed from thedelivery module33 to theclinical facility32 to notify appropriate medical personnel of patient non-compliance actions or other urgent conditions. Thecontrol software35 protocols also enable thecontrol center101 to accurately monitor eachunit dose package27 contained within aparticular delivery module33 and update the database inventory records as eachunit dose package27 is delivered to a patient.
In order to ensure the security of patient information transmitted through thecontrol software layer35, a preferred embodiment of the present invention utilizes a secure,encrypted connection25 which maintains the confidentiality and integrity of patient information. The data communication process ensures that the only record correlating adelivery module33 to a particular patient is contained within theclinical software database32. This process is described in detail below.
As previously discussed, theclinical software32 enables a healthcare practitioner to remotely manage and monitor a patient's drug therapy and compliance. All patient information is stored in theclinical software database32 and utilizes the clinical facility'snetwork security34 policies and procedures to authenticate users and network access to patient data (FIG. 2). Contained within theclinical software32 are three key data elements that correlate thedelivery module33 to a particular patient. These include: 1) the delivery module serial number; 2) a randomly generated registration number (used in the initial setup of the module), and 3) a randomly generated Unit Identification Number (UIN).
To communicate with adelivery module33, theclinical software32 sends an encrypted signal using a Secure Socket Layer (“SSL”) to the URL of thecontrol center101 computer servers. This signal is the same protocol used in processing credit card payments via the internet and operates on Port 443 of the clinical facility'sfirewall34. The signal is an XML instruction set that contains the UIN, identifiers required for authentication by thecontrol center101 servers, and a command instruction set. Neither the patient's name nor any information identifying the patient are transmitted beyond the clinical facility'sfirewall34.
This encrypted signal is sent to thecontrol software layer35, which is designed to authenticate signals from only theclinical software32 anddelivery module33. Once a command set is authenticated by thecontrol center101 servers, utilizing the UIN, the command set references thecontrol software database35 to determine thedata communications method36 to the particular delivery module33 (e.g. pager network, wireless network, IP address) and obtains its address information. The signal is reformatted into a proprietary protocol, assigned a randomly generated communication's token and transmitted to thedelivery module33 to be activated.
Once the signal is received by thedelivery module33, the signal is decoded and verified. If authentic, thedelivery module33 transmits a signal back to thecontrol center101 servers confirming receipt of the command instruction. This confirmation contains the communications token for verification by thecontrol center101 servers. Certain commands, such as the dosage delivery command, require a reconfirmation from thecontrol center101 servers to engage the command. This verification process prevents thedelivery module33 from processing any unauthorized commands.
Thedata communication process36, as described above, ensures that only theclinical software32 can correlate data contained on thecontrol center101 servers to a particular patient, or correlate the delivery module's serial number to a particular patient. In this manner, patient identifiable health information is retained securely within the confines of theclinical facility34. A principal advantage of the present invention, therefore, is that it enables bidirectional communication between thedelivery module33 and a healthcare practitioner to be conducted using a secure,encrypted connection25 that maintains the integrity of HIPAA protected patient information.
It will be understood that the present invention may be employed in connection with “non-HIPAA compliant” applications. Stated otherwise, the secure, encrypteddata transmission protocol25 provided herein is not necessary for remote actuation of thedelivery module33. For example, the invention may be used independently of the securedata transmission feature25 to document various drug consumption events that occur during the course of a clinical research trial or drug detoxification program. In this way, the invention provides a means of capturing longitudinal healthcare outcomes associated with drug and nutritional interventions. Similarly, thedelivery module33 may be employed in connection with a home telemetry unit for remote monitoring of a patient's position, blood pressure, pulse, oxygen level, temperature, respiration, serum glucose etc., or for remote monitoring of environmental conditions such as, for example, temperature, humidity, pressure, smoke and carbon dioxide.
Thenon-sequential delivery module33 features a microprocessor-based controller having standard digital data storage features both for data and for the microprocessor programs. The controller receives command signals related to the patient's prescribed medication regimen. These signals, initiated at theclinical software layer32, are authenticated and transmitted through thecontrol layer35 by way of a suitable data communications link36. The controller then executes the entered dosage delivery command by alerting the patient through visual, audible or other means, at each of the programmed dosing times. The controller concurrently establishes a window of time, relative to the alerting signal, during which the patient can input a delivery signal via, for example, a verbal command or an appropriate confirmation key43. The duration of the time window is set by the entered program or by a default value.
If the patient input signal is received before expiration of the time window, a fully sealed unit dose or unit-of-issue package27 is ejected from themedication carrier26 and discharged from thedelivery module33 as described in further detail below. If the patient has not responded, e.g., pressed the “drop”key43 of thedelivery module33 at the end of the time window, the module automatically transmits an alert, via a suitable data communications link36, to designated medical personnel. In this manner, the instant invention ensures that medication is not administered until confirmation is received from the patient. This overcomes a significant deficiency of existing medication delivery systems, in which medication is expelled automatically in accordance with a predetermined schedule, increasing the risk of patient under-dosage and over-dosage.
The present invention includes a unique delivery scheme through which a healthcare practitioner, by entering appropriate commands into the user interface, can instantaneously select, modify, queue, change or discontinue any of 300 unit dose packages27 of prescription or non-prescription medications, pharmaceuticals or nutraceuticals stored within thedelivery module33 of a particular patient. The commands also specify the specific dosage form and strength of theunit dose package27 to be delivered. The commands are received and interpreted by the control center computer servers, which correlate the instruction to aparticular delivery module33 andmedication carrier26. In this manner, the invention provides the flexible and convenient dosage administration that is required for situations where a patient's regimen is the subject of frequent dosage adjustments or where the patient is prescribed more than one therapy to be administered at varying times over the course of a day, a week or several months.
The present invention enables the healthcare practitioner to remotely and non-consecutively access and deliver any of the unit dose packages27 contained within thedelivery module33 to a patient, in any order, without being limited by a predetermined sequence or serial delivery restriction. Unlike existing systems, the system of the present invention is capable of delivering diverse types of unit dose and unit-of-issue therapeutic products out of sequence, and in minutes, enabling the patient's medication regimen to be appropriately tailored to adapt to fluid medical conditions. An example circumstance requiring modification of the patient's regimen is where there is an unexpected change in the patient's health condition. Notably, the invention ensures that any change in patient medication ordered by a doctor is effective immediately. This is a tremendous advantage over existing systems, which take at least several hours, and in some cases, several days for new medication orders to be filled.
The subject invention is particularly useful in situations where it is necessary to immediately discontinue or recall a therapy prescribed as part of a clinical research trial, a frequent occurrence (FIG. 26). In such instances, the clinical software initiates a lock-out procedure to prevent delivery of any of the unit dose packages that have been recalled. To the inventors' knowledge, the present system is the only technology platform that enables real-time quarantine of remotely located products/lots. In this way, the invention provides a unique safeguard that protects patients in the event of a drug recall. This feature is particularly important with respect to narrow therapeutic index drugs that are mislabeled, subpotent or superpotent.
Thedelivery module33 is designed so that each unit dose and unit-of-issue package27 ejected from themedication carrier26 remains fully sealed until the point of delivery to a patient. Therefore, the present invention avoids the medication contamination and degradation problems common to medication delivery systems known in the art.
A further embodiment of the invention combines an early dosing capability with the programmed regimen delivery described above. In this embodiment, thedelivery module33 has an added programmability feature by which a designated healthcare practitioner, by entering appropriate commands into theuser interface100, can obtain an early delivery of one or more unit dose packages27 of the patient's medication. An example circumstance requiring this would be where the patient intends to temporarily leave his/her residence, during which time medication would still be needed, regardless of the patient being remote from thedelivery module33. In emergency situations, themedication carrier26 may be removed from thedelivery module33 for out-of-system use. In such situations, access to thedelivery module33 may be granted to the patient or other authorized personnel by means of a security code, video/smart card or other appropriate safe guard.
As described above, thecontrol center101 server is connected to thenon-sequential delivery module33 via, for example, aradio frequency connection36, wherein thecontrol center101 is provided with a record keeping and inventorying function. In addition to one or more clinical facilities receiving alerts from thedelivery module33, information regarding the module's33 operation, status and unit dose/unit-of-issue package27 inventory is automatically transmitted to thecontrol center101 server. This information includes, for example, a history of all delivery operations over a set time period. Reporting to thecontrol center101 is achieved, in part, through the use ofelectronic codes29,31 imprinted on eachmedication carrier26 and on eachunit dose package27 contained therein. Theelectronic code29 contains identifying information, such as, for example, the serial number, lot number, and expiration date of an individualunit dose package27. In this way, the invention permits a continuously updated, complete inventory of eachmedication carrier26 andunit dose package27 stored within themodule33 to be maintained, and simultaneously provides a complete audit trail of eachunit dose package27 from its manufacture to delivery to a patient.
Although thecontrol center101 maintains a record of the encodedinformation29,31 in its computer server, patient identifiable information is inaccessible to thecontrol center101 and is securely maintained within data servers physically located within the confines of eachclinical facility34. Theelectronic identifiers29,31 imprinted on themedication carrier26 and unit dose/unit-of-issue packages27 do not include patient identification information. Instead, themedication carrier26 is identified according to its uniquely assignedserial number29, while eachunit dose package27 is identified according to serial number and/or national drug code number (NDC)31. As such, the present system is compliant with the Health Insurance Portability and Accountability Act (HIPAA).
In a further embodiment, which may be combined with the above-described reporting function, thecontrol center101 sends queries to thedelivery module33, e.g. viaradio frequency transmission36, requesting inventory status information. The specific apparatus and details of operation of thedelivery module33 are described further below.
There is shown inFIG. 1, adelivery module33 comprising a preferably plastic, box-like housing adapted to rest upon a surface and having a base37 which supports top,side38,39,front41 and rear40 panels. Thefront panel41 features anelectronic display42 on which alphanumeric information and instructions related to a particular unit dose are communicated to the patient. Theelectronic display42 may comprise, for example, a liquid crystal display, digital display or other suitable communication means. Portions of thefront panel41 are also configured with an audible alarm to alert the patient of the need to take a prescribedunit dose package27. To allow for patient input, thefront panel41 of the housing includescontrol keys43 that function as confirmation keys in accordance with the audible alarm andelectronic display42 to enable the patient to take delivery of a prescribed dosage. An audio speaker and remote communication interface may optionally be incorporated within the housing for providing additional instructions to or receiving feedback information from the patient. An alternative embodiment of the invention includes temperature control means (e.g. refrigeration means) for regulating the temperature of themodule33 as may be required for certain medications. A power outlet allows thedelivery module33 to be connected to an external AC power source.
In a further embodiment, the invention includes a wireless communication device worn by the patient which is communicatively linked with thedelivery module33 to provide an additional alert to some patients. The wireless communication device may be, for example, a wrist watch, pager or pendant. Alternatively, a patient may be alerted via telephone or email.
Access to themedication carriers26 and internal hardware of thedelivery module33 is provided when theside panels38,39 are unlocked and open. In order to prevent unwanted access to themedication carriers26, theside panels38,39 may remain locked at all times unless actuated by the controller in response to a command originating from the control center or clinical facility. Alternatively, access to the interior of themodule33 can be granted to a patient, designated caregiver or other authorized personnel by way of a smart card or security access password. The smart card or restrictive password must typically be entered prior to interacting with the delivery module in instances where one or more unit dose packages have been quarantined or recalled. In a further embodiment, thedelivery module33 includes speech recognition means for receiving and interpreting prescribed verbal commands made by the patient or other authorized personnel.
In a manner well known in the art, each constituent of thedelivery module33 is operatively coupled to and controlled by the controller, through control signals, in response to a command instruction set received from a computer server based at thecontrol center101. The controller transmits verification to thecontrol center101 that information has been received and instructions have been carried out. The controller is programmed to activate the dosage “drop” function at appropriate times based on information remotely communicated from thecontrol center101. In particular, the controller activates the alarm,key pad43, wireless communication circuitry,electronic display42, sensors,scanners92,98,actuators60,72,91,motors54,73,80,87 and other electronic devices.
The controller can be one of several standard microprocessor-based controllers having standard type actuator or servo drive interfaces and detector inputs, or other suitable circuitry capable of employing software control, hardware control or a combination thereof. Internal memory is used to store, for example, dosage delivery instructions and logic programs. The controller runs the programs stored in internal memory. Control signals travel by way of a distribution panel to and from the various components configured within thedelivery module33.FIGS. 16-20 further illustrates the controller's mode of communicating with electronic architecture of thedelivery module33.
In the exemplary embodiment shown inFIG. 6, astorage elevator47 is designed to accommodate up to tenmedication carriers26, each containing a thirty day supply of different therapeutic agents in a variety of dosage forms and strengths. Thedelivery module33 is therefore capable of storing approximately three hundred unit dose and unit-of-issue packages27 of medication. As shown inFIG. 14, eachcarrier26 may include different dosage strengths for a single medication. This allows different dosage strengths to be combined to obtain a desired dosage amount. While the instant design is appropriate for use in a home, assisted living facility, long-term care facility or other residential setting, adelivery module33 having astorage elevator47 that can accommodate, for example, up to three hundredmedication carriers26 is preferable for use in an institutional environment (e.g. a correctional institution).
The location of eachunit dose package27 andmedication carrier26 within thedelivery module33 is determined, in part, through the use ofelectronic identifier codes29,31 or other inventory code systems. Theelectronic codes29,31 imprinted on themedication carriers26 and individual unit dose packages27 are scanned by anelectronic code reader98 as eachmedication carrier26 is loaded into thedelivery module33. The encoded information is transmitted to thecontrol center101 computer server, where it is associated with a stored database record by thecontrol software35. This information allows a healthcare practitioner to actively treat a patient remotely located from a clinical facility.
The healthcare practitioner, by way of the menu-drivenuser interface100, simply retrieves and reviews the inventory of unit dose and unit-of-issue packages27 stored within the patient'sdelivery module33 and selects an appropriate dosage within the parameters prescribed for the patient. Upon receipt of a command signal from thecontrol center101 computer server, the patient'sdelivery module33 expels the selected dosage based on theelectronic identifiers29,31 and position coordinates of such dosage within thedelivery module33.
As shown inFIG. 6, thestorage elevator47 includes a cavity which is partitioned intomultiple storage bays48 disposed on separate levels of theelevator47. Eachstorage bay48 has a horizontal opening of a sufficient size to provide the range of motion necessary to allow atransport carriage49 stored within thebay48 to be moved in both forward and rearward directions. Thetransport carriage49 comprises an open-ended frame that defines afluting50 disposed along the length of said frame, such that peripheral edges of themedication carrier26 can be readily fitted within saidfluting50. Thecarriage49 is supported by ahorizontal railing51 which extends along the interior surfaces of thestorage bay48. Ends of therailing51 terminate about aconcentric shaft52 that is generally flush with the opening of thebay48.
Rotatable spur gears or sprocket drives53 are mounted at both ends of theshaft52 so as to come into contact with and suitably engage corresponding stationary gears that protrude from peripheral edges of thecarriage49 for effecting forward and rearward movement of thetransport carriage49. The spur gears53 are rotated by a drive motor (e.g. a servo motor)54 in a controlled fashion, in response to signals from the controller. While a gear assembly is described herein for moving thetransport carriage49 in both forward and rearward directions, it should be understood that any suitable drive assembly may be employed. Location markers are provided along an outer edge of the transport carriage, which indicate the exact horizontal position (“y-axis”) of thecarriage49 andintegral medication carrier26. This information is monitored by the controller through a feedback loop arrangement. Once the controller determines that an appropriate number of markers have been scanned by anelectronic code reader98 mounted within the storage elevator, thedrive motor54 is disengaged. Thetransport carriage49 normally resides within the storage bay48 (the “home position”99) until a prescribed dosage is to be taken or amedication carrier26 is to be replenished.
As discussed above, thetransport carriage49 is adapted for horizontal (x-axis) movement between rear and forward positions (FIGS. 9 and 10). Upon receiving a “dose delivery” signal from the controller, thedrive motor54 rotates spur gears53 of the desiredstorage bay48, such that thecarriage49 andintegral medication carrier26 are moved in a forward direction, sufficiently to clear the opening of thestorage bay48, and achieve a “delivery ready” position in proximity to a vertically disposedplunger93. Likewise, during acarrier26 unloading operation, thedrive motor54 advances thetransport carriage49 to a forward position in which a portion of the carriage extends beyond the opening of thestorage bay48. At such point, additional forward movement of thecarriage49 is accomplished through the action of afriction drive assembly56. Sensors are located to monitor the movement and alignment of thetransport carriage49 as it is moved in both forward and rearward directions.
Referring now toFIG. 1, a handle equippedloading door44 and insertion/retrieval slot45 are provided in thefront panel41 of the housing. When thedoor44 is open, theslot45 is accessible for inserting amedication carrier26 filled with unit dose packages27 of prescription or non-prescription medications and supplies. Adjoining the interior surface of thefront panel41 is a loading area with components for receiving themedication carrier26 into thedelivery module33. Each of these components will be described in detail below in reference toFIGS. 7-10 and17.
A sensor is located in the loading area to detect the presence of anincoming medication carrier26. The sensor is, for example, a micro-switch, optical eye or other electrical contact suitable for monitoring the orientation of themedication carrier26 relative to a limit switch embedded within the loading area. When the sensor detects that themedication carrier26 has been fully inserted, through activation of the limit switch, afriction drive assembly56 is immediately actuated.
A pair ofparallel guide rails57,58 are horizontally mounted to theside panels38,39 to enable thetransport carriage49 and anincoming medication carrier26 to be properly aligned and dispatched through the loading area of the housing to thestorage elevator47. One end of each of the guide rails57,58 abuts the interior surface of thefront panel41 such that the guide rails57,58 at that point intersect the insertion/retrieval slot45 configured in the front panel. The guide rails57,58 extend through the midsection of the housing and terminate in front of thestorage elevator47.
Latch apparatus59 is configured to allow theincoming medication carrier26 to be secured onto thetransport carriage49 and dispatched through the loading area. The latch apparatus is59 operatively coupled to asolenoid60, or other electromechanical actuator, which is mounted to aside panel38 of the housing by a bracket and screws, or similar hardware. Aretractable spring61 andplunger62 are provided at the upper end of thesolenoid60, theplunger62 including agroove64 in a top portion thereof which supports one end of thelatch apparatus59. An opposite end of thelatch apparatus59 features anangle63 that abuts peripheral edges of theguide rail57 and vertically protrudes above theguide rail57 so as to obstruct the loading pathway.
Upon actuation by the controller, thesolenoid60 biases thespring61 andplunger62 downward. This, in turn, lowers thelatch apparatus59 to a position below theguide rail57 so that thetransport carriage49 can be positioned on the exposed, upper surface of the guide rails57,58 for movement beyond thestorage bay48 to a “prime” position, planate with thefront panel41 of the housing. Thesolenoid60 retains thelatch apparatus59 in this suppressed orientation while themedication carrier26 is loaded into thedelivery module33, through the insertion/retrieval slot45. As theincoming medication carrier26 enters the loading area, the carrier's26 peripheral edges automatically slot into the carriage fluting50 so as to form an integral unit therewith for transport to astorage bay48. At such time, thelatch apparatus59 is returned to its initial, indexed position against the peripheral edges of theguide rail57 under the force of thesolenoid60.
A short distance above the guide rails57,58 is aswivel bracket65 which is mounted to and pivots about ahorizontal rod66 attached to theside panels38,39 of the housing. Thebracket65 is configured for mounting afriction drive assembly56 that controls movement of thetransport carriage49 andmedication carrier26 through the loading area. Thebracket65 forms an arch about its anterior, peripheral edges which features opposingvertical flanges67,68. The flanges permit adrive shaft69 and a pair ofdrive wheels70,71, spaced substantially equally apart, to be conveniently attached to thebracket65. It should be noted that thedrive wheels70,71 are preferably made of rubber, soft, compressible polyurethane foam or other material that is capable of gripping amedication carrier26 containing individual unit dose packages27 without breaking or damaging the medication contained therein. Vertically suspended from an opening in a top surface of thebracket65, directly above aguide rail57, is anelectromechanical actuator72 which distends to mate with and exert pressure on an upper surface of themedication carrier26, in response to a control signal. This action causes thebracket65 to pivot downwardly, so as to assume an angled position and lower thedrive wheels70,71 onto the upper surface of thetransport carriage49.
Adrive motor73 such as, for example, a servo motor, is secured to theswivel bracket65 and operatively coupled to apulley system74. Thepulley74 is mounted in perpendicular relation to thedrive shaft69 and is moveable relative thereto by means of themotor73. Upon actuation, themotor73 rotates thepulley74, which in turn, rotates thedrive wheels70,71. The rotary motion of thedrive wheels70,71 directs themedication carrier26 andtransport carriage49 inwardly, toward thestorage elevator47. Once thetransport carriage49 andcarrier26 reach the opening of thevacant storage bay48, the carriage's49 protruding gear elements engage rotatable spur gears or sprocket drives53 mounted about the opening of thestorage bay48, moving thecarriage49 andmedication carrier26 toward the rear of thestorage bay48. When the sensor detects that themedication carrier26 andtransport carriage49 have arrived at theirhome position99, the controller disengages themotor73 and drivewheels70,71.
Referring now toFIGS. 3 and 11, thestorage elevator47 is operably connected to anelevator bracket77 which moves theelevator47 from a rest position, in the lower section of the housing, to an operative position, adjacent the delivery area, along a vertical (“z”) axis. Vertical movement is achieved by means of alinear motion assembly78 such as a gear belt andlead screw81, pulley, or other standard drive component capable of converting rotary motion from a drive motor to linear motion. In the exemplary embodiment, a timing belt andlead screw81 are rotated by astepper motor80 mounted to thebase37 of the housing. Themotor80 is actuated in accordance with electrical signals received from the controller (FIG. 18). The base37 also accommodates the controller and a battery pack (not shown).
Theelevator bracket77 generally spans the length of thedelivery module33 so as to allow thestorage elevator47 to be raised and lowered to a desired level for accessing amedication carrier26 stored within aparticular storage bay48. Theelevator bracket77 includes achannel housing82 having a hollow portion in the center thereof and corresponding openings in upper and lower surfaces through which thelead screw81 and one ormore guide rods83,84 vertically extend. In general, thechannel housing82 serves as a frame for supporting the various components of theelevator bracket77 and imparting stability to theguide rods83,84, or other suitable vertical shaft, such as, for example, an adjustable slide and block assembly. Thechannel housing82 is vertically mounted to thebase37 of thedelivery module33, adjacent therear panel40, and is secured in place by bolts, casters or other suitable hardware.
Also featured in the hollow portion of thechannel housing82 are upper andlower cross members102,26, mounted in horizontal relation to theguide rods83,84 andlead screw81, and interpolated by through holes in which theguide rods83,84 andlead screw81, respectively, are slidably disposed. Thecross members102,26 move along theperpendicular guide rods83,84 by operation of themotor80 andlead screw assembly81. This configuration permits acarrier plate85 attached to the anterior surface of thecross members102,26 to be raised and lowered, in accordance with the direction of motion of thelead screw81. Thecarrier plate85 generally extends across the width of the housing and serves as a platform for attachment and support of thestorage elevator47. Thestorage elevator47 includes a metal protrusion that projects outwardly from the rear wall of the elevator. The protrusion is suitably shaped to conform to a corresponding depression in thecarrier plate85 so that the carrier plate andstorage elevator47 can be conveniently and securely attached thereby.
The position of thestorage elevator47 within the housing is determined by means of an encoder located in thedrive motor80 which relays positional information to the controller in the form of electrical pulses as themotor80 rotates (FIG. 11). Once the appropriate number of pulses is emitted by the encoder, signaling that thestorage elevator47 has attained the correct position for accessing a desiredmedication carrier26, the controller disengages themotor80. In this manner, thestorage elevator47 can be raised or lowered to an appropriate level within the housing.
Referring now toFIG. 12, anejector assembly55 is provided for releasing a prescribed unit dose/unit-of-issue therapy27 to a patient at a predetermined time, in accordance with a drop command originating from theclinical software32. Theejector assembly55 is mounted on and moves along a horizontal slide (“x-axis”)86 which extends across the width of thedelivery module33, between thestorage elevator47 and loading area. During dose delivery, theejector assembly55 is moved from arest position88 into anoperative position89 suitable for achieving contact with a desiredunit dose package27. Identification of the correctunit dose package27 is determined by thecontrol software35, which correlates each instruction from a healthcare practitioner with a specificunit dose package27. Theejector assembly55 includes a sensor,electronic code scanner92,electromechanical actuator91, and aplunger93, wherein each component is vertically positioned within and supported by areceptacle90 that is slidably attached to thehorizontal slide86. Theejector assembly55 is moved in the x-direction by means of amotor87 operatively coupled to and under the control of the controller. The electromechanical drives on the ejector/reader (y-axis), elevator (z-axis), and carriage (x-axis) are specifically designed for non-slip reliability.
A sensor (not shown), such as an optical sensor, is located to sense the movement and alignment of theejector assembly55 as it is moved into anoperative position89 in proximity to the desiredunit dose package27. The sensor ensures that suchoperative position89 corresponds to the designated position coordinates of the selected therapy. This is accomplished by means of a feedback loop arrangement with the controller.
Anelectronic code scanner92, such as a bar code reader, optical recognition reader, radio frequency identification tag reader or other similar device, is operatively coupled to and suspended from a lower end of theactuator91 so that the head of the scanner is positioned in proximity to upwardly facingelectronic identifier codes29,31 imprinted on themedication carrier26 and seal of the desiredunit dose package27. Thescanner92 detects removal of aunit dose package27 from astall28 of themedication carrier26, through interruption of a light beam emitted therefrom, and thereafter, transmits a signal to the controller confirming such removal. An electronic imaging device (e.g. a camera) may also be incorporated to provide visual feedback that the desired medication is suitably discharged from themedication carrier26.
Aplunger93, having anelongated shaft94, is mounted for vertical movement between raised and lowered positions by means of alinear actuator91 attached to theshaft94 thereof. The lowermost end of theshaft94 terminates in a flat, compactingedge95 which is suspended directly above thestall28 of themedication carrier26 containing the desiredunit dose package27. Upon receipt of a control signal, theactuator91 forces theplunger93 downward such that theplunger93 achieves contact with the encoded surface of theunit dose package27, pushing thepackage27 through the opening of thestall28.
Aramp96 or chute is mounted to theside panels38,39 of the housing beneath theejector assembly55. Theramp96 is generally a flat surface which extends across the width of thedelivery module33 and slopes downwardly so as to channel the ejectedunit dose package27 to arotatable guard97 located at the end of theramp96. Theguard97 is used for temporarily retaining an ejectedunit dose package27 until each of the medications within the patient's regimen is expelled. Once each of the prescribed medications is expelled, theguard97 is rotated away from its initial position by a servo motor, releasing the ejected unit dose packages27 into a receivingarea47 for collection by the patient.
The receivingarea47 is an open section configured in thefront panel41 of the housing where the medication is retrieved by a patient for consumption. Medication related information, such as the type, quantity and dosage of the discharged unit dose packages27, appears on theelectronic display42. Alternatively, or in addition, a healthcare practitioner may communicate directly with the patient by providing instructions, additional information, or receiving feedback from the patient through the remote communication interface anddisplay42,keypad43 or speaker.
FIGS. 23 and 24 are flowcharts of the functional steps employed in the non-sequential delivery sequence of the present invention to deliver a desired therapeutic dosage to a patient as part of the same prescription period.
As mentioned above, a significant aspect of the instant invention is that it enables a physician, pharmacist, nurse or other healthcare practitioner remotely located from a patient to deliver any of the unit dose and unit-of-issue packages27 stored within thedelivery module33 to the patient, in non-consecutive order, without being limited by a predetermined sequence. This unique delivery scheme allows the healthcare practitioner to instantaneously modify, queue, change, or discontinue a prescribed dosage in response to fluid medical conditions. Therefore, the precise location and contents of eachunit dose package27 contained within thedelivery module33 must be known at all times, both prior to and during the dose delivery process. The present system uses a feedback loop arrangement to manage this flow of data.
In operation, a healthcare practitioner enters patient prescription information and dosage schedules using the Fulfillment, Adjustment and Compliance Tracking System (FACT™), or other clinical software application32 (FIG. 22). Patient information is accessed by way of the software'suser interface100, which features a complement of menu-driven worksheets that appear on the practitioner's computer monitor.FIG. 29 is a worksheet showing a monthly therapy schedule for a patient, which is stored in memory. Other examples of worksheets which the health care provider uses to interact with theclinical software32 are provided inFIGS. 27-28 and30-31. All patient information, which includes, for example, prescription information, medication dosing schedules, dosage delivery criteria such as drug-drug interactions and food-drug interactions, and a history of dosage delivery results, is stored within theclinical software database32. Theclinical software database32 utilizes the clinical facility'snetwork security34 policies and procedures to authenticate users and network access to patient information, in conformity with the Health Insurance Portability Accountability Act.
Just before a scheduled dosing time, theclinical software32 transmits an encrypted signal to thecontrol software32 operating on a server located at thecontrol center101 to initiate delivery of a particular medication for a particular patient. The signal contains a command instruction set representing a prescribed medication regimen and dosing schedule for the patient, as well as a randomly generated Unit Identification Number (UIN) assigned to that patient'sdelivery module33. Neither the patient's name nor any information identifying the patient are transmitted beyond the medical facility'sfirewall34. Accordingly, only theclinical software32 can correlate the prescribed regimen and dosing schedule, ordelivery module33, to the patient.
Following transmission, the signal is interpreted and authenticated by acontrol center101 computer server. Utilizing the UN, the server'scontrol software35 links each command instruction embedded within the signal to aspecific delivery module33. Next, thecontrol software35 utilizes a look up routine to correlate the instruction to aspecific medication carrier26 containing the desiredunit dose package27. This information, based on the encodedidentifiers29,31 assigned to themedication carrier26 and unit dose packages27, is stored in thecontrol software35 database. Thecontrol software35 ascertains the specific location within thedelivery module33 of theunit dose package27 that is to be delivered to the patient in accordance with the programmed dosing schedule.
Thecontrol software35 database specifies the vertical location (z-coordinate) of themedication carrier26 as well as the row and column positions of thestall28 containing such dose (y- and x-coordinates, respectively). In addition, thecontrol software35 database provides specific dose ejection parameters based on the internal configuration of themedication carrier26 and the type of medication contained therein. This is accomplished using the stored electronic data which is communicated to thecontrol center101 computer server as themedication carriers26 are loaded into thedelivery module33.
In the next step, thecontrol software35 reformats the signal into a proprietary protocol which includes a randomly generated communication's token and instructions for thedelivery module33 to drop the desired medication based on the x-, y- and z-coordinates of such medication. The instructions ensure that the correct medication, in an appropriate dosage form and amount, is delivered to the patient. The server transmits the reformatted signal to the controller located within the patient'sdelivery module33 via radio frequency, or other suitable link. The controller interprets the command sent from thecontrol center101 server and sends confirmation thereto. This confirmation contains the communications token required for verification by thecontrol server101. In response, thecontrol server101 transmits a reconfirmation signal to thedelivery module33, authorizing the controller to drop the prescribed medication.
The module's33 dose delivery sequence is activated upon receipt of the reconfirmation signal. The controller alerts the patient of the need to take the prescribedunit dose therapy27 by way of the alarm,display42 or other suitable visual, audible or other means. The controller concurrently establishes a window of time, relative to the alerting signal, during which the patient can input a delivery signal by, for example, depressing the drop key on thecontrol panel43. If the aural and visual signaling is ignored by the patient, the signaling will repeat every minute or more up to a programmed interval. The duration of the time window is set by the entered program or by a default value.
If the patient depresses the drop key43 during the programmed time window, the controller, in cooperation with thedrive motor80, raises thestorage elevator47 to the correct vertical position (FIGS. 11 and 18) for accessing thestorage bay48 containing theunit dose package27 to be delivered, in accordance with z-coordinate specified in the command instruction set. The position of thestorage elevator47 within the housing is determined by means of the motor-based encoder which relays positional information to the controller, in the form of electrical pulses, as themotor80 rotates. Once the appropriate number of pulses is emitted, signaling that thestorage elevator47 has attained the correct position, the controller disengages thedrive motor80.
When thestorage elevator47 reaches the correct level for accessing the designatedstorage bay48, the controller actuates the servo motor andpulley assembly54 which controls horizontal movement in the y-direction (FIG. 19) so as to move atransport carriage49 andintegral medication carrier26 housed within thestorage bay48 forward, away from thehome position99. Anelectronic code scanner98 located within thestorage elevator47 reads location markers disposed along the outer edge of thecarriage49, which indicate the position of thecarriage49 andmedication carrier26 as they are advanced. This positional information is monitored by the controller through a feedback loop arrangement. Once the controller determines that an appropriate number of markers have been scanned, in accordance with the y-coordinate instruction received from the control server, the motor andpulley assembly54 are disengaged. As thetransport carriage49 andcarrier26 are moved into proper position, thescanner98 also reads an encodedidentifier label29 affixed to the upwardly oriented surface of themedication carrier26, which contains the x-coordinate operational parameters.
At this point, thetransport carriage49 andmedication carrier26 have sufficiently cleared the opening of thestorage elevator47 such that the desiredunit dose package27 is positioned beneath thehorizontal slide86 of theejector assembly55. A control signal (FIGS. 16 and 20) is sent to themotor87 responsible for movement about the x-axis so as to advance the slide-mountedreceptacle90 from arest position88 into anoperative position89 above the medication that is to be delivered. In this delivery ready position, the compactingedge95 of theplunger93 is suspended directly above the upwardly oriented, encoded31 surface of theunit dose package27.
In this orientation, thecode scanner92 suspended from the lower end of theactuator91 is also positioned in proximity to theelectronic identifier code31 on the seal of theunit dose package27. In instances where supplementary confirmation of delivery is desired, thescanner92 reads theidentifier code31 and transmits verification to the controller that the selected dosage is the correct one, as a redundant check. Thecontrol software35 layer links each command to aspecific medication carrier26 andunit dose package27, the identification of which is scanned and verified at the time of loading thedelivery module33.
In the next step, a control signal is sent to theactuator91 connected to theshaft94 of theplunger93. As this occurs, theshaft94 is biased downward, whereby the compactingedge95 contacts the encoded31 surface of theunit dose package27. This action causes the retaining means30 of the affectedstall28 to release theunit dose package27 contained therein. The ejectedpackage27 drops onto theramp96 situated beneath theejector assembly55, and thereafter slides into therotatable guard97 located at the bottom of theramp96. Theguard96 temporarily retains the ejected medication until each of the medications within the patient's regimen is expelled.
When theelectronic code scanner92 detects removal of theunit dose package27, out of themedication carrier26, a signal is sent to the controller, verifying that the prescribed dose is suitably removed from thecarrier26. In instances where visual identification is desirable, an electronic imaging device may be used to independently verify that the desired medication is suitably discharged from thecarrier26.
If additional unit dose packages27 are scheduled to be expelled from thesame medication carrier26, e.g. in instances where multiple dosage strengths of the same medication are combined to obtain a correct dosage amount, thecarrier26 is again advanced in the y-direction, while theejector assembly55 is moved into the appropriate x-position. Once all of the prescribed medications have been ejected from themedication carrier26, thetransport carriage49 andcarrier26 return to theirhome position99 within thestorage bay48.
If a prescribedunit dose package27 is contained in adifferent medication carrier26, thestorage elevator47 is raised or lowered to the appropriate level, in accordance with the z-coordinate specified in the command instruction set. Thereafter, thetransport carriage49 andmedication carrier26 are moved forwardly, into the correct y-position, while thereceptacle90 of theejector assembly55 is moved in the x-direction. When themedication carrier26 is in proper position, theplunger93 pushes thedose27 out of thecarrier26, causing the ejecteddose27 to fall onto theramp96. This sequence is repeated for each of the medications within the patient's regimen, in accordance with the instructions received from thecontrol center101 computer server. It should be understood that all of the medications for a particular dosage period are ejected in rapid succession, typically less than ten seconds per medication.
Once all the medications for the scheduled dosage time are expelled from theirrespective medication carriers26, the controller activates the audible alarm,electronic display42 or other suitable alert mechanism to notify the patient that medication is ready to be taken. Simultaneously, a control signal actuates the servo motor that is operatively coupled to therotatable guard97 at the base of theramp96. As theguard97 rotates, the ejected, fully sealed unit dose packages27 fall into the receivingarea47 for collection by the patient. At the same time, theelectronic display42 presents a description of the medical products placed into the receivingarea47, which may include, for example, the type, quantity and dosage of the delivered medical products.
In order to monitor compliance as well as maintain a complete audit trail of the patient's interaction with thedelivery module33, the module automatically transmits a signal to thecontrol center101 computer server, via radio frequency, orother communication link36, once the dosage is discharged. The signal confirms that the prescribed dosage has been delivered to the patient within the scheduled dosing period. The transmission is date and time stamped in order to provide an accurate record of the transaction. Thecontrol software35, which operates on thecontrol center101 server, receives and decodes the signal. Once the signal is authenticated, thecontrol software35 systematically updates the status of eachunit dose package27 delivered during the scheduled dosing period. The updated usage information is stored in thecontrol software35 database so as to provide precise inventory control and flawless delivery of the diverse medical products contained within thedelivery module33. The dosage administration transaction record is also stored in thecontrol software35 database, then formatted into an XML message stream and sent to theclinical software layer32 in the succeeding polling cycle, using an encryptedSecure Socket Layer25.
Every few minutes, theclinical software32 checks for status updates sent to the clinical facility's data server. When theclinical software32 receives the transaction record, thesoftware32 stores the information in the database which houses the patient's therapeutic regimen and dose delivery instructions entered by the healthcare practitioner. The transaction record provides, for example, an updated, complete inventory of the unit dose packages27 contained within the patient'sdelivery module33 as well as the date and time that the prescribed dosage was received by the patient. This information is directly provided to one ormore computer stations100 within the clinical facility, enabling an authorized healthcare practitioner to review the patient's dosage delivery results in real time. Once the dosage confirmation message is received from the control center server, signifying that the prescribed dosage has been delivered to a patient, theclinical software32 initializes a routine to remove that particular dosage delivery event from the pending list.
If the patient fails to respond to the alarm generated by thedelivery module33 at a scheduled dosing time, e.g., by pressing thedrop key43 of thedelivery module33 at the end of the programmed time window, a routine is initialized which may include a call to the patient or a call to the patient's care provider, doctor, pharmacist or other designated individual. Thedelivery module33 automatically transmits an alert to thecontrol center101 server, via radio frequency or other suitable communications link36. Immediately thereafter, notification of the missed dosage is transmitted to the clinical facility's data server using thesecure encryption method25 as described above.
A further embodiment uses, for example, two time windows during which the patient may input the delivery signal, e.g., depress thedrop key43. In the first time window, thedelivery module33 generates an audible, visual or other alarm at a first intensity. If that first time window ends and the patient has not yet entered the delivery signal themodule33 increases the alarm level. The increased alarm level is continuous or, alternatively, steadily increases until the end of the second time window. Notification of the non-compliance action is transmitted to thecontrol center101 servers if the patient, at the end of the second time window, has still not responded to the alarm.
Delivery of the scheduled dosage does not occur unless the patient actuates thedrop key43 within the designated time interval. In this way, the present invention ensures that the patient receives the exact dose prescribed at the correct dosing time. This feature improves adherence and protects the patient from adverse drug interactions which may result from taking multiple doses of medication at unscheduled dosing times.
Patient dosage administration results are routed to and received by the clinical facility in real time. Theclinical software32 automatically alerts the healthcare practitioner of the non-compliance action by generating an alert message which is displayed on the practitioner's computer monitor (user interface100). The practitioner can then take timely action by directly contacting the patient and/or directing an appropriate command back to thedelivery module33, or as otherwise described below.
After reviewing the notification of non-compliance, the patient's physician, pharmacist or other licensed healthcare practitioner retrieves and evaluates the patient's treatment regimen, which is stored within theclinical software32 database and is accessed by way of theuser interface100. This information includes, but is not limited to, prescription information such as the name, type (brand or generic), potency strength and dosage form of a prescribed medical product, dosing schedules, dosage administration criteria such as drug-drug interactions and drug-food interactions, and the next pending dosage delivery event. The healthcare practitioner then determines whether the patient's medication regimen, dosing schedule, or both, should be modified to accommodate the missed dosage by, for example, entering an instruction that cancels, queues or modifies a prescribed dosage amount, using theappropriate worksheet100.
This is accomplished, in part, through the use ofelectronic identifier codes29,31 which allow the precise location and contents of the prescription and non-prescription medications, pharmaceuticals, and nutraceuticals contained within aparticular delivery module33 to be known at all times, both prior to and during the dosage delivery process. This information is stored and monitored by thecontrol center101. A record of each dosing transaction, which includes an updated inventory of unused unit dose packages27, is transmitted to the clinical facility immediately after each transaction occurs. The healthcare practitioner reviews the updated inventory listing which appears on his/her computer monitor (user interface100). If an unscheduled dosage and/or schedule adjustment is deemed appropriate by the prescribing physician, the healthcare practitioner selects an alternate dosage or different medication from the list of prescribed therapies available to the patient and enters appropriate delivery criteria. The new dosage information is saved within theclinical software32 database. The patient does not have to travel to a physician's office or to a pharmacy in order to obtain and fill a new prescription. There are no delays or interruptions in the continuity of treatment and compliance with the prescribed treatment regimen is addressed almost immediately.
In a similar fashion, the system of the present invention enables the healthcare practitioner to actively respond to an unexpected change in the health condition of a patient almost immediately. The invention is suited for situations where appropriate dosage amounts are evaluated on an ongoing basis, for example, through laboratory tests that change over time in accordance with the patient's needs. In these situations, the healthcare practitioner is able to remotely adjust the patient's dosage amount or deliver a different medication almost immediately, without the need for a new prescription. This is particularly important where narrow therapeutic index drugs are prescribed and over-medicating or under-medicating the patient can cause serious side effects and illness. The present system prevents the patient's condition from deteriorating since the patient is able to continue his/her course of treatment without potentially harmful interruptions.
Every few minutes, theclinical software32 initializes a routine that monitors modifications to the database that houses the schedule and instructions entered by the healthcare practitioner. When thesoftware32 detects a dosage and/or schedule change, the information is conveyed to the URL of thecontrol center101 computer server using an encryptedSecure Socket Layer36. As described previously, the information is formatted into an XML command instruction set that contains the Unit Internal Number (UIN) and other identifiers required for authentication by thecontrol center101 server. Thecontrol software35 installed on the server authenticates and decodes instructions received from theclinical software32. A reply signal is then sent to theclinical software32, acknowledging receipt of such instructions. Utilizing the UIN, thecontrol software35 correlates the adjusted dosage delivery criteria to aparticular delivery module33. Thecontrol software35 then references its database to determine the specific location, within thedelivery module33, of theunit dose package27 that is to be delivered to the patient based on the then current inventory of unit dose packages27 stored within themodule33. Thedelivery module33 is able to expel thepackages27 non-sequentially, without being limited by a serial delivery restriction.
Thecontrol software35 utilizes a look-up routine to retrieve the vertical location (z-coordinate) of theparticular medication carrier26 that contains the desiredunit dose package27, as well as the row and column positions of thestall28 containing such dose (y- and x-coordinates, respectively). In addition, the look-up routine identifies specific dose ejection parameters based on the internal configuration of themedication carrier26 and the type of medication contained therein. This is accomplished using the stored electronically codedidentifiers29,31. Thecontrol software35 simultaneously monitors the current time versus the scheduled drop time for the modified dosage. When the current time equals the scheduled drop time, thesoftware35 transmits a command signal to thedelivery module33 by means of radio frequency, or other suitable communications link36. Included in the signal are instructions for thedelivery module33 to drop the modified dosage, based on the specified location coordinates.
When the command signal is received by thedelivery module33 to be activated, the module's controller decodes, verifies and loads the command signal into the controller execution queue by means of the logic program stored within the controller's memory. Immediately thereafter, the controller alerts the patient through visual, audible or other means, of the need to take the adjusted dosage. Once the patient responds to the alert generated by thedelivery module33, e.g., by articulating a prescribed verbal command or pressing thedrop key43 within the programmed time period, the dosage delivery sequence is initialized. Once the desired dosage has been delivered to the patient, confirmation and status information is sent to thecontrol center101 server. These results are immediately processed and conveyed to the clinical facility, enabling designated medical personnel to review the patient's dose delivery results in real time by way of theuser interface100. Hence, the feedback arrangement described herein permits the patient's medication regimen to be instantly adjusted and tailored to adapt to fluid medical conditions.
The healthcare practitioner can communicate with the patient at the time of dose delivery via telephone, email or by entering an appropriate command into his/her computer terminal. The command signal is processed by thecontrol software35 and thereafter transmitted to the patient'sdelivery module33. Through this remote interface, which includes, for example, a keypad and/or speaker, the patient can be prompted to provide information or respond to questions.
While conventional pharmaceutical delivery systems provide a healthcare practitioner with data regarding a patient's health status, the present system allows a healthcare practitioner to actively respond to a change in a patient's health condition from a remote location. Each of the unit dose packages27 contained within thedelivery module33 is separately encoded31 and inventoried so as to be independently accessible and traceable. This allows the healthcare practitioner to deliver medication in non-consecutive order, on a dose by dose basis, and in a controlled and auditable fashion. In this manner, patient compliance with a prescribed regimen is precisely monitored. Moreover, dosage adjustments and other treatment decisions are made within parameters specified by a doctor in real time, simultaneous with the receipt of a communication regarding a change in a patient's health condition. This feature is particularly important given the overall increase in telehealth and telepharmacy based services.
As discussed above, thedelivery module33 of the exemplary embodiment can accommodate a plurality ofmedication carriers26, each containing diverse therapeutic agents. For purposes of illustration, therefore, atypical carrier26 loading operation is described below (FIGS. 7-10,17 and25a).
Loading of an empty or partiallyempty delivery module33 is typically initiated by a patient, caregiver, or other authorized operator when a new supply ofmedication carriers26 is received. The user simply depresses a load key43 located on thefront panel41 of the housing, prompting the controller to transmit a load verification request to thecontrol center101 via radio frequency or othersuitable transmission method36. Once received by thecontrol center101, the load request signal is authenticated by thecontrol software35 and in most cases is accepted. The load verification request is denied in instances where a security password or other authorization is required to initiate the load operation, but is not entered by the operator.
In an alternative embodiment, the load operation is initialized by thecontrol software35. Thecontrol center101 server transmits an encrypted load instruction, containing a randomly generated communications token, to thedelivery module33. Upon receipt thereof, the signal is decoded and verified for authenticity by the module's controller. If authentic, the controller sends a reply signal to the server, confirming receipt of the load instruction. Thereafter, thedelivery module33 generates an audible, visual or other alert in order to prompt the patient, or other operator, to depress theload key43.
Once the operator activates theload key43, thestorage elevator47 is immediately raised from its rest position in the lower section of the housing to a position operative for loading of anew medication carrier26 into astorage bay48. Movement of thestorage elevator47 to the appropriate level within the housing occurs by operation of themotor80 andlead screw81 assembly, through controller actuation. Thestorage elevator47 is raised to a height at which thestorage bay48 to be loaded generally abuts thehorizontal guide rails57,58 that extend along theside panels38,39 of the housing. In this position, the lower surface of thetransport carriage49 is situated slightly above the guide rails57,58 so that upon exiting thestorage bay48, thecarriage49 automatically rests against the guide rails. As discussed above, thestorage elevator47 is automatically moved to a correct position through operation of the encoder.
When thestorage elevator47 is properly positioned, theactuator60 lowers thelatch apparatus59 to its unobtrusive position below theguide rail57 so that the loading pathway is clear. Thetransport carriage49 is advanced forwardly from itshome position99 within thestorage bay48 to a point at which thecarriage49 extends into the loading area of the housing. As thecarriage49 enters the loading area, its movement is detected by a sensor which relays positional information to the controller. A control signal is sent to the swivel bracket mountedactuator72, wherein theactuator72 distends downward so as to achieve contact with the upper surface of thecarriage49. Simultaneous therewith, theswivel bracket65 pivots downwardly, causing thedrive wheels70,71 to be lowered onto the upper surface of thecarriage49. Thedrive wheels70,71, through operation of themotor73 andpulley assembly74, rotate outwardly so as to move thecarriage49 along the guide rails57,58 in a further frontward direction.
When the front edges of thetransport carriage49 come into contact with thefront panel41 of the housing so as to be flush therewith, i.e. the prime position, the controller temporarily disengages themotor73 so that frontward movement of thecarriage49 ceases. Thedistended actuator72 moves upward to its original, raised position, simultaneously causing theswivel bracket65 and drivewheels70,71 to pivot upwardly so as to release contact with thecarriage49. In this position, thecarriage26 abuts the insertion/retrieval slot45 configured in thefront panel41 of the housing. Thetransport carriage49 is now in position to receive anincoming medication carrier26. Because thedelivery module33 is capable of accessing and delivering the patient's dosages in random sequence, themedication carriers26 need not be loaded into thedelivery module33 in any particular order. This overcomes a significant drawback associated with prior art devices in that medication must be loaded in the order in which it is to be delivered.
At this point, the operator is prompted through audible, visual or other means, to open the handle equippedloading door44 in order to insert anew medication carrier26 into the insertion/retrieval slot45, preferably with the medications facing downward. The controller determines whether amedication carrier26 has been placed in theslot45 by monitoring the sensor. When the sensor detects that amedication carrier26 has been fully inserted, i.e. that peripheral edges of themedication carrier26 extend sufficiently into the loading area (e.g. three inches or other predetermined distance) so as to activate a limit switch, the controller signals thedrive wheels70,71 to distend and rotate in a reverse, or inward, direction and correspondingly advance themedication carrier26 through the insertion/retrieval slot45, into the awaitingcarriage49.
When the sensor detects that themedication carrier26 is fully entrenched in thecarriage49, theactuator60 causes thelatch apparatus59 to resume its original, indexed position above theguide rail57 so as to secure thecarriage49 in place on the guide rails57,58 for transport by thedrive wheels70,71. As themedication carrier26 andcarriage49 move rearward, toward theempty storage bay48, anelectronic scanner98 located in proximity to themedication carrier26 is actuated in response to a control signal. Thescanner98 reads the encodedidentifier29 label attached to the upwardly oriented surface of themedication carrier26, which identifies the carrier's serial number. Thescanner98 also records thespecific storage bay48 in which themedication carrier26 is to be stored. Immediately thereafter, thescanner98 retrieved information is communicated to the computers servers housed at thecontrol center101.
Once themedication carrier26 andtransport carriage49 approach the opening to thestorage bay48, the motor andpulley assembly54 causes the spur gears53 mounted about the opening of thestorage bay48 to rotate, effecting rearward movement of thecarriage49 into thehome position99. Themotor73 attached to theswivel bracket65 is then disengaged so that thedrive wheels70,71 stop rotating. When this occurs, thedistended actuator72, moves upward to its original, raised position, simultaneously causing theswivel bracket65 to pivot upwardly so as to be locked into its initial position.
Almost immediately thereafter, thestorage elevator47 is raised or lowered to a different position, i.e. level, operative for loading asecond medication carrier26. At this point, the operator is prompted to insert anothermedication carrier26 into the insertion/retrieval slot45. Eachnew carrier26 is loaded in similar fashion, with thecarriage49 being advanced to receive and transport anincoming carrier26 to thestorage elevator47, until all themedication carriers26 are present in thedelivery module33. The operator is then alerted through audible, visual or other means, that the loading operation is complete. The entire process occurs very rapidly, generally within three minutes.
As described above, anelectronic scanner98 such as a bar code reader, optical recognition reader or radio frequency identification tag reader scans theelectronic identifier codes29 imprinted on the exposed surface of eachmedication carrier26 as the carrier advances toward thestorage elevator47, and images the specific location of thecarrier26 therein. This information is provided to thecontrol center101 computer servers for later retrieval. Once the loading operation is complete, each of the scannedmedication carriers26 is temporarily removed from itsstorage bay48, in turn. Thescanner98 locates and reads theelectronic identifier codes31 imprinted on the seal of eachunit dose package27 within thecarrier26 and images thespecific storage bay47 in which theunit dose package27 is stored. The controller then transmits the scanner retrieved information to thecontrol center101, where it is correlated with the encoded data previously entered into thecontrol software35 database. In this manner, the precise location and contents of each unit dose and unit-of-issue package27 contained within aparticular delivery module33 are stored within thecontrol software layer35 such that eachdose27 can be accurately tracked from the time of manufacture to the time of delivery to a patient. This stored data enables a healthcare practitioner to remotely select and deliver an appropriate therapy to a patient, as described above.
FIG. 25billustrates a typical unloading operation.Medication carriers26 are typically unloaded by a patient, caregiver, or other authorized operator when the patient's supply of medication is depleted. The operator simply presses the “unload” key43 located on thefront panel41 of the housing, prompting the controller to transmit a verification request signal to thecontrol center101 server. Once received by the server, the signal is authenticated25 by thecontrol software35 and thereafter authorized, once thecontrol center101 database verifies that a preselected number ofstalls28 of one ormore medication carriers26 is empty. Information necessary for verification of the request is stored in the server database, which maintains a continuously updated record of the location and status of eachunit dose package27 within thedelivery module33 through the use of electronically codedidentifiers29,31. In this manner, thecontrol center101 is able to account for eachunit dose package27 at all times.
In an alternative embodiment, the unload operation originates from thecontrol software layer35. Thecontrol center101 server transmits an encrypted25 unload instruction to thedelivery module33 when the patient's medication supply falls below a predetermined level, as reflected by the server database. The signal is decoded and verified for authenticity by thedelivery module33 controller. If authentic, the controller sends a reply signal to the server, confirming receipt of the unload instruction. Thereafter, thedelivery module33 generates an audible, visual or other alert in order to prompt the patient, or other operator, to depress the unload key43.
Once the operator activates the unload key43, thestorage elevator47 is immediately raised from its rest position to a position operative for removal of a depletedmedication carrier26 from astorage bay48. Thereafter, thetransport carriage49 andmedication carrier26 are ushered into the loading area of the housing in the manner described above. When the front edges of thecarriage49 come into contact with thefront panel41 of the housing so as to be flush therewith, i.e. the prime position, frontward movement of thecarriage49 ceases. Thedrive rollers70,71, however, continue to rotate outwardly, moving the depletedmedication carrier26 out of thecarriage49 and into the insertion/retrieval slot45. A sensor is located to monitor movement of theoutgoing medication carrier26 through the insertion/retrieval slot45.
Once the front edges of themedication carrier26 have cleared thefront panel41 of the housing so as to protrude approximately three inches (or other distance suitable for manual retrieval of thecarrier26 by an operator), the controller briefly disengages themotor73, preventing further rotation of thedrive wheels70,71. The depletedmedication carrier26 is now in position to be removed by the operator. At this point, the operator is prompted, through audio, visual or other means, to open the handle equippedloading door44 in order to retrieve themedication carrier26 from the insertion/retrieval slot45.
When the sensor detects that the depletedmedication carrier26 has been removed, the controller signals themotor73 to rotate thedrive wheels70,71 in a reverse direction, that is, inwardly, so as to move thetransport carriage49 in a rearward direction toward theempty storage bay48. Once thecarriage49 reaches itshome position99, themotor73 is disengaged so that thedrive wheels70,71 stop rotating. When this occurs, thebracket actuator72 moves upward to its original, raised position, simultaneously causing theswivel bracket65 to pivot upwardly into its initial position. At such time, thelatch apparatus59 resumes its indexed orientation adjacent theguide rail57.
Thestorage elevator47 is then raised or lowered to unload the nextempty medication carrier26. Eachstorage bay48 is vacated in similar fashion until all thedepleted carriers26 have been removed from thedelivery module33. It should be understood that unloading of themedication carriers26 occurs in rapid succession, with thestorage elevator47 being correctly positioned for removal of adepleted carrier26 from a correspondingstorage bay48 virtually simultaneously with the ejection of acarrier26 through the insertion/retrieval slot45. With the operator in position to receive each ejectedcarrier26, the entire process can take as little as three minutes.
Once all theempty medication carriers26 have been removed from thedelivery module33, thecontrol center101 servers transmit a load signal to the controller of theempty module33. The operator is then notified, through audio, visual or other means, that themodule33 is ready for refilling. At such time, the operator simply depresses the load key43 located on thefront panel41 of the housing, and thereafter, opens theloading door44 in order to insert anew medication carrier26 into the insertion/retrieval slot45.
The present invention is a fully integrated, real-time, non-sequential, medication management and compliance system that ensures accurate delivery of both custom packaged and commercially available sealed unit dose and unit-of-issue therapeutic products to patients. Importantly, the invention fosters patient compliance with a prescribed treatment regimen by, for example, protecting the patient from adverse drug reactions and ensuring that the patient remains within recommended therapeutic levels.
Furthermore, because the delivery of medication occurs on a unit dosage basis, the patient avoids purchasing an unnecessary number of doses and only purchases the number of units required for the prescribed regimen. This is a tremendous advantage over existing systems, in which prescriptions are normally filled in standard thirty day or sixty day allotments. The present invention reduces the incidence of medication waste by supplying only necessary doses to the patient rather than an aggregate number of doses, which are ultimately discarded. A further advantage to the patient is that each unit dose package remains completely sealed until the point of administration to avoid the medication contamination and degradation problems which plague remote medication delivery systems known in the art.
In the event of a change in the health condition of the patient or other situation requiring a dosage adjustment, other medications and doses having higher or lower strengths are immediately available to the patient, eliminating the need to travel to a physician's office and/or to a pharmacy to obtain the requisite medication. This feature is particularly important with respect to mobility impaired patients. In addition, patient expenses are reduced since the new dosage is already on hand and need not be purchased.
Healthcare practitioners such as physicians and pharmacists also benefit from the present invention. The system enables a provider to treat a greater number of patients with better control of high risk patients, including patients with cognitive, visual, and/or auditory impairments who require more frequent monitoring. The invention allows the healthcare practitioner to rectify a patient's failure to take a scheduled dosage in minutes. In addition, the invention reduces the number of unreimbursable medical services, which include, for example, telephone calls to and from the patient. Also, the invention eliminates the need to write a new prescription every time a dosage needs to be adjusted. The healthcare practitioner makes proper dose adjustments in a prompt and timely fashion, all duly recorded, without any disruption to the patient's course of treatment. This is a significant advantage over existing systems, which allow a remotely based healthcare practitioner to communicate a change in medication or dosage amount to a patient but do not enable the practitioner to remotely change a prescribed dosage in real time.
As previously mentioned, with existing dispensing systems, there is no accurate way to inventory pharmaceuticals and/or to audit patient compliance or consumption of the products. This is due, in part, to the fact that the pharmaceuticals are dispensed in a lot, whereby not every pill or dose is separately identifiable and traceable. In the present invention, medication delivery is accomplished on a unit dosage basis wherein each dose is inventoried with its own electronically coded identifier, allowing a healthcare practitioner to accurately monitor patient compliance with a prescribed treatment regimen. The system enables the healthcare practitioner to remotely manage and deliver individual unit dose packages of prescription and non-prescription medications, medical supplies, diagnostic materials, pharmaceuticals and nutraceuticals to a patient, non-consecutively, without being limited by a sequential delivery restriction. Such unit doses may include, for example, solid orally consumed doses, liquid orally consumed doses, and injection devices containing doses that are administered directly into the body, wherein the doses may comprise a single compound or several compounds.
Managed care providers and other third party payors realize significant advantages from the integrated, non-sequential, remote medication management and compliance system described herein. The invention provides a platform for the control and electronic billing of healthcare products distributed to one or more remote locations on consignment. In this regard, consignment medications may be immediately billed upon dispensing, significantly reducing inventory costs associated with medications that are billed and reimbursed at the time of consumption and providing pharmaceutical companies with a competitive advantage.
Notably, the invention reduces the incidence of medication waste by eliminating the need for a patient to discard remaining doses or obtain a new prescription in the event of a dosage adjustment. This increases the likelihood that a patient will receive a required treatment, reducing the incidence of emergency room visits and hospital admissions occasioned by non-adherence to a prescribed drug regimen. In addition, visits to healthcare providers such as physicians and pharmacists are reduced, significantly decreasing provider related costs.
While the invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various alterations in form and detail may be made therein without departing from the spirit and scope of the invention. In particular, while the invention illustrated by the Figures shows a specific size and shape of the delivery module, these parameters can vary considerably and are not limited by the preferred embodiments described herein and depicted in the Figures.
Additionally, while this application generally addresses use of the secure data communication process to deploy communications to and from a delivery module based in a patient's home while protecting patient privacy, the use of such process is by no means limited to this application. The data communication process described herein can be adapted for use in a variety of applications where secure data transmission is desirable (e.g. in conjunction with a patient monitoring system).