1. Field
The description relates to the field of tablet packaging and delivery systems. More particularly, the description relates to ordering and filling a prescription comprising a plurality of different medications.
2. Description of Related Art
One of the major problems in the taking of prescribed daily medications emanates from the fact that, in many instances the patient has to take more than one medication in the form of pills or tablets. A principal concern is determining whether all medications have been taken in compliance with the prescribed daily regimen. Many times this concern is compounded by the requirement that portions of the various medications must be taken at different times during the day.
The fear of taking improper dosages of prescribed medication can be particularly acute in the elderly, many of whom have some degree of mental dementia and can easily be confused as to whether they have taken all of their medications at the correct time. Some patients, with curtailed mental capabilities, have difficulty just in sorting out the medications preparatory to taking them, let alone taking the medication in a timely manner. Providing medications to disabled and/or incapacitated individuals can also be a problem for caregivers, particularly those in hospitals and assisted living facilities where one caregiver may oversee the medication of many patients.
Thus, there is a need for a positive delivery system and tablet package assembly for the delivery of multi-prescription dosages. A tablet packaging and delivery system that could decrease the possibility of human error and provide an easy to use set-up for the correct selection and delivery of multi-tablet/multi-time medications would be welcomed by the pharmaceutical and medical communities.
There is also a need for a tablet delivery system that provides evidence that the prescriptions were actually taken or administered as prescribed. Such a system would be an efficient way for any patient to take such multi-dosages but it would be especially beneficial for a patient of limited mental capacity as well as to caregivers in the hospital setting.
There is also a need for a tablet assembly and delivery system for vitamin supplements. Vitamin supplements are also often used in the same manner as many prescribed drug regiments with many of the same problems and inconveniences. Therefore a delivery system that addresses the needs of multi-prescription administration also contains many benefits for, and can be applied to, the vitamin and herbal supplement market.
One solution to the problem of taking multiple medications is to pre-package the multiple medications so that users can take the pre-packaged medications at a predetermined time. Generally, these methods of pre-packaging medications are targeted to patients that may lack maturity and/or mental capacity to take the correct medications at the correct time. For example, young children in a school or campground, and elderly individuals in elder care centers, or nursing homes are target groups for the pre-packaging of medications. Some of the pre-packaged medications are placed in a small plastic bag, which may be easily misplaced and is not child proof. Other pre-packaged medications are placed in sealed cups that are difficult to open and that can not be made child proof.
Additionally, the pre-packaging of multiple medications is also limited by distributing pre-packaged medications to a limited geographical location. For example, the pre-packaging of multiple medications is only provided in hospitals, medical institutions, campgrounds, or schools. Thus, the geographic limitation makes it difficult to effectively distribute the pre-packaged medications to a broad group of people over a broad geographic area.
Furthermore, pre-packaged multiple medications are difficult to order because the pre-packaging of multiple medications is a specialty service that has not been automated. The manual processing of prescription orders is expensive because the process lacks automation. Therefore, there is a need for an automated ordering system and process that is simple and cost effective for a patient or a pharmacist to use. An automated system and method for receiving orders would make it substantially easier to process a multiple prescription order, which would in turn make the process much more cost effective.
Further still, the current pre-packaging of multiple medications does not provide a simplified labeling technique that permits a caregiver to efficiently monitor the dispensing of different medications at pre-determined intervals. For example, the current techniques for dispensing medications do not provide summaries of the medications being taken by a patient. Additionally, although a pharmacist may provide information about drug interactions, there is no simple and clear record that describes drug interactions in a patient-friendly manner.
Further yet, there is a need for an efficient production facility that efficiently processes and inspects the pre-packaged multiple prescription containers. Automated processing and inspection techniques can dramatically improve efficiencies and minimize improper packaging or labeling. Thus, by automating the tablet processing and inspection process a more cost effective solution for the pre-packaging of multiple prescriptions can be obtained.
The following description provides a convenient and efficient way for patients, pharmacists, and physicians to order multi-drug prescriptions from a pharmaceutical dispensing system which produces multi-dose prescriptions. This description allows for prescriptions to be placed from a computer, telephone, facsimile, mail, or any combination thereof.
An ordering system that fills a prescription order is described. The ordering system comprises a Graphical User Interface, a transactional component, a production facility, a detailed labeling component, and a distribution point. The GUI is configured to receive at least one prescription order that is associated with a particular patient wherein the at least one prescription order comprises at least two different medications. The transactional component charges for processing the prescription order. The production facility receives the prescription order and fills a plurality of multiple prescription containers. Each of the multiple prescription containers is associated with a prescribed time interval determined by the prescription order, and each multiple prescription container comprises the different medications that are to be consumed at the prescribed time interval. The detailed labeling component is associated with the multiple prescription containers, and the detailed labeling component is configured to generate a detailed label that provides a plurality of medical information regarding the medications to the patient. The detailed label is then combined with the multiple prescription container.
Additionally, a means for receiving the multiple prescription order that is associated with the patient is described. By way of example and not of limitation, the means for receiving the multiple prescription order includes from a networked computer, a telephone order, a mail order, a scanned order, or any combination thereof.
A method for processing a multiple prescription order that comprises a plurality of different medications is also described. The method comprises receiving a multiple prescription order that is associated with a particular patient. The multiple prescription order comprises at least two different medications that are to be consumed at the same prescribed interval determined by the multiple prescription order. The method also comprises initiating a transaction that charges for filling the multiple prescription order. The multiple prescription containers are filled so that each multiple prescription is associated with a prescribed time interval determined by the prescription order, and each multiple prescription container comprises the different medications that are to be consumed at the prescribed time interval. A detailed label is generated that comprises medical information regarding the medications to the particular patient. The multiple prescription containers and the detailed label are then combined for the particular patient.
The present invention will be more fully understood by reference to the following drawings which are for illustrative, not limiting, purposes.
Before the present assembly, apparatus and methods are described, it is to be understood that this invention is not limited to particular embodiments described, as such may, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present invention will be limited only by the appended claims. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.
Referring to
A direct order may then be placed at decision diamond 14. A “direct order” is an order that is placed by a medical professional such as a medical doctor or pharmacist. By way of example and not of limitation, the order is placed using a graphical user interface (GUI) resident on a browser running on a computer that is in communication with the Internet by a pharmacist, patient or caregiver.
If the direct order requires a pharmacist, the method proceeds to block 16 where a pharmacist places the order for the appropriate medications. After block 16, the method proceeds to block 17 where the pharmacist may be prompted for at least one packaging option. A variety of different packaging options may be provided to the pharmacist. The packaging options comprise multiple prescription containers as described in further detail below. Alternatively, as described by block 18, the order may also be placed by telephone, fax, mail, scanned order, or any other such means for placing an order that does not employ a graphical user interface.
If the prescription order can be placed without the need for a pharmacist, the method proceeds to block 19 where the user may be prompted to select at least one packaging option. Generally, the user is either a patient or a caregiver. A variety of packaging options may be provided to the caregiver or consumer, and illustrative packaging options are described herein. As described above, the order may also be placed on-line, by telephone, fax, mail, or other such means for communicating the order.
After receiving an order, the method proceeds to decision diamond 22 where a decision about how to process a multiple prescription order is made. A multiple prescription order or “Multi-Script” order is an order that comprises at least two tablets or medications comprising a first tablet or medication that is different from a second tablet or medication. Generally, a multiple prescription order requires taking multiple tablets or medications at approximately the same time as prescribed, which is also referred to as a prescribed time interval. If the order is not a multiple prescription order, the method proceeds to block 24, in which a single vial is prepared with a simple label. However, if the order is a multiple prescription order, the method proceeds to block 26 where a multiple prescription container is selected and the appropriate label is generated. At block 28, either the simple vial or each of the multiple prescription containers is filled.
At block 30, a detailed label comprising a plurality of written information may also be generated. This plurality of information may include information related to each medication, summary information about each medication, appropriate container labeling, some summary information about the patient, a drug interaction report, or any such combination thereof. The drug interaction report may provide information to help individuals properly take the prescribed medication. The drug interaction report includes information about the various drug interactions that may be associated with each prescription. For example, certain foods may interact with a particular prescription. Additionally, there may be a group of particular drugs that may interact with the prescription, and this information may not be readily available to the patient or the patient's caregiver. The drug interaction report may be used to help identify foods, medications, vitamins, supplements, or any combination thereof that may interact with the patient's filled prescription. The written information may also include a summary of the medications being taken as described in further detail below.
The method then proceeds to decision diamond 32 where a decision is made about how to distribute the combined filled prescription order and detailed label. If the filled order is to be distributed to a pharmacist 36, the pharmacist 36 provides the filled prescription to the consumer 34 that may be a patient or caregiver. Alternatively, the filled prescription may be distributed directly to the particular consumer 34 by shipping to the consumer or having the consumer pick-up the filled prescription order.
Referring to
The method then proceeds to decision diamond 54 where a determination is made if the verified order was a multiple prescription order. If the order is not a multiple prescription order, the method proceeds to block 56 where a single prescription order is processed, and then subsequently the filled prescription is sent or provided to a pharmacy or customer as shown in block 64, and described herein.
If the verified prescription order is a multiple prescription order, the method proceeds to block 58 where the facility determines the filling procedure to use. The filling procedure will depend on a host of variables such as the type of user selectable packaging. The method then proceeds to block 60 where the production facility inspects the tablets that have been placed in the multiple prescription containers. The type of inspection depends on the particular design of the production facility. For example, the inspection may be conducted by tablet counters, RFID counters, by using X-ray or near IR technology, visual robotic inspection, weighing the containers or other such technology capable of inspecting the multiple prescription containers that is described herein and that would readily suggest themselves to those of ordinary skill in the art.
After completing the inspection, the production facility generates the detailed label and other labels having the plurality of written information shown in block 62. The written information may also comprise packaging information. The written information may comprise information about each substance, appropriate labeling, summary information, a drug interaction report, or a combination thereof. At block 64, the filled prescription order and the detailed label are combined and this patient-specific combination is then sent or distributed to a designated entity or individual including, but not limited to, the patient, the caregiver, the pharmacist, the user, the customer, or the consumer.
Referring to
Additionally, sufficient information is provided so that the appropriate tablets can be associated with the appropriate multiple prescription containers at the appropriate dosing times as represented by block 68. The method then proceeds to block 70 where each of the multiple prescription containers is filled with the appropriate tablets. A more detailed explanation of the method for filling each of the multiple prescription containers is described in further detail below.
A more detailed view of block 60 where the production facility inspects the containers is also described. The inspection may be conducted either before the multiple prescription containers are sealed as represented by block 72. A label may then be printed on lidstock 74 and the multiple prescription container may then be sealed 76 with the labeled lidstock. Additionally, the medications within the multiple prescription container may be inspected after the multiple prescription containers are sealed as represented by block 78. Thus, the filled multiple prescription container may be inspected either before the multiple prescription containers is sealed, after the multiple prescription container is sealed, or both.
A more detailed view of block 62 is also presented in
Referring to
Furthermore, the user may provide specific ordering options such as instructing about the type of user selectable packaging. For example, a plurality of single packages 128 may be requested for multiple medications. Also, a multiple prescription package 130 or “multi-script” package may be requested. The multiple prescription package may include a variety of user selectable options such as type of package, size of package, and child resistant packaging. The type of package may include a sleeved package or a circular package as described below. Alternatively, the packaging may employ other packaging techniques such as grid packaging or the use of plastic bags also referred to a “pouches.” The size of package may also vary and may come in three different sizes: travel (small), notebook (medium), and companion (large).
Data fields are also provided for identifying the requested medications 132 that include a description of the product 134, the dosage 136, the quantity 138, and the type of drug 140. The type of drug 140 may include information about whether the drug is generic or name brand. If the product is available, the on-line ordering system may then provide a price 142 for the product. A sub-total 144 is then provided, and shipping costs 146 are identified if applicable. Note, the GUI may also support customer pick-up at a local pharmacy. A final order total 148 is then presented to the user.
A transactional component that charges for processing the prescription is also provided. By way of example and not of limitation, the patient may then provide a card 150 such as a credit card, a debit card or any other such information for conducting an on-line transaction; the name, the card number, the type of card and the expiration date of the card are requested in the illustrative embodiment.
Referring to
The illustrative label 160 includes a picture or image 162 of the particular patient, and the patient specific information 164 such as name, address, and telephone number of the patient. Furthermore, there may be additional unique information about the patient printed on the label, such as the doctor's name 166 and telephone number, and health insurance information. The label 160 also includes pictures 168 of the tablets that have been prescribed. Additionally, there may be a particular description 170 about each tablet on the folded label that may include manufacturer's latest labeling information, a summary of expected side effects 172, and a short description of possible drug interactions 174. This information may be presented in a manner similar to the Physician's Desk Reference, which includes a color picture of the pill with summary information about each pill. Additionally, information about how to administer the medication may be provided; this information may be used by a caregiver, to help in dispensing the appropriate medications.
Referring to
In
Referring to
The PC 202 is configured to remotely communicate with an online ordering server 206. By way of example and not of limitation, the online server 206 is behind a firewall and is part of a secure local area network (LAN) 208 located at a production facility. Generally, the production facility is configured to generate a filled multiple prescription order. The secure LAN also comprises a production server 210. In the illustrative example of
The online ordering server 206 is communicatively coupled to the production server 210. The online ordering server 206 is configured to communicate with the user and/or clients that are placing the on-line order. The ordering server 206 also contains the hardware and software necessary for addressing queries about inventory in the production facility. The online server 206 may be configured to query the user about a particular prescription, about health insurance, and other pertinent information. The online server 206 may comprise software and hardware that permits the client 202 to pull up notes, research the prescribed medication(s), research side effects and drug interactions with other medications, vitamins, foods, and other such information that would help the patient properly consume the products ordered by the patient.
The production server 210 controls the processing of the multiple prescription orders at the production facility that generates containers having a plurality of different tablets in each container. The illustrative production server 210 comprises a system database 214 that stores information about the products available at the production facility such as prescription medication, over-the-counter medication, vitamins, supplements, herbs, oils, or other such substances. Additionally, the system database 214 may include historical prescription information that is associated with the patient, so that the user may access the multiple prescription order at a later time for ordering refills. In one illustrative example, the production server contains and maintains all the information to control the production facility. The production server 210 may be configured with management software that manages all the filling, inspection, printing, sealing, order tracking, and tablet assembly traffic control functions.
While placing an order, the online ordering server 206 may request information from a medical provider server 216 or provide information to the medical provider. For example, a medical provider such as a medical doctor or nurse can confirm that a specific medication has been ordered and will be administered in a particular manner. Additionally, the medical provider may also include notes for the patient on how the medicine should be taken, and this information may be printed by the production facility and associated with the patient's on-line order. Additionally, historical prescription order information may also be stored on the medical provider server 216.
The online ordering server 206 may also request information on the accuracy or changes in the end user's medical insurance from the insurance provider server 218. The online ordering server 216 may also request information from the pharmaceutical company server 220 about certain prescribed medications and updated information that pertains to the prescribed medications. These queries to the pharmaceutical company server 220 may occur during the online ordering process initiated by the end user or at various times when updating the system database. Additional queries may be made to government agencies, private medical facilities, on-line search engines, websites, databases, or any combination thereof.
The online ordering server 206 and/or the production facility server 210 may also be communicatively connected to an updated medical information server 222 via the Internet or a secure wide area network connection. The updated medical information server 222 may be a private or government maintained server with compiled updated information on the various drugs stored in the production facility. The updated information may comprise new warnings on drug interactions, updated expiration dates, toxicity information and the like. The updated information is communicated to the second labeling component. This information is valuable in assuring the multi-drug prescriptions are effective and safe.
Additionally, the online ordering server 206 comprises a transactional component 212 that processes the user's financial information. The transactional component enables the online ordering server 206 to obtain pertinent information from the user, healthcare provider and the user's insurance company to verify the prescription. The transactional component is also configured to carry out the payment of the order and informs the user if the prescription has been processed or if the financial transaction has failed.
Referring to
The client 232 then proceeds to communicate with the secure LAN 236 that comprises a production server 238 and an online server 240. The production server 238 is associated with managing the inventory in the production facility and comprises an inventory database module 242 that determines if the production facility can satisfy the client's prescription order.
The online server 240 may be located in a variety of different places such as a separate on-line pharmacy, a physician's website, a healthcare provider's website, a health insurance website, a school, a university, or any other such entity that out-sources the multiple prescription packaging to the production facility described herein. In the illustrative embodiment, the online server 240 comprises a web server inventory lookup module 244 that is operatively coupled to the inventory database module 242 and receives updates regarding the production facility's ability to satisfy the client's request.
In operation, the client 230 may access the production server 238 directly or through the illustrative online server 240 that may be associated with a separate on-line pharmacy, a physician, a health care provider, a health insurance provider, a school, a university or any other such entity. Additionally, physicians involved in the patient's care may utilize the Internet to generate a new prescription for the patient, or modify a previous prescription that may be stored on the production server 238.
Patient confidentiality may be preserved by using encryption technology and by requiring strong authentication. Using encryption technology such as Secure Sockets Layer (SSL) and Public Key Infrastructure (PKI), communications across the Internet are kept secure. Illustrative embodiments may use available encryption tools such as Pretty Good Privacy (PGP), OpenPGP (the IETF's RFC 2440) and other available PKI encryption standards. Information stored on databases and servers may also be encrypted. Strong authentication may be obtained by asking the user for one or more unique identifiers such as date of birth (DOB), unique IP address, last 4 digits of a social security number, username, password, or any other such unique identifier.
Once the client 230 has been authenticated, the client is able to place a multiple prescription order using the illustrative graphic user interface (GUI) 100. In one illustrative example, a local pharmacist's on-line server communicates with the production server 238 and the inventory database 242. The pharmacist's on-line server makes a request to determine whether the production facility can satisfy the pharmacist's order. The inventory database 242 is accessed to determine if the prescription order may be filled. Once the pharmacist's online server has received confirmation that the prescription order can be filled, the online server relays this information back to the clients computer via the Internet.
By way of example and not of limitation, the illustrative production server 238 comprises software to access the drug interaction database to determine if there may be possible interactions between the prescribed tablets stored. The production server 238 also communicates the order to production facility computers which control the various systems and subsystems involved in producing the multiple prescription containers, including printers for labeling the lidstock on each individually sealed container with medication instructions such as date and time to take the tablets in each individual container. The production server 238 may also communicate to production facility computers which are connected to a printer for generating labels with patient specific information, drug information and expiration date(s) for the medication stored within the individual containers. It should be noted that vitamins and herbal supplements may also be stored together with prescription drugs.
Referring now to
At decision diamond 256, the prescription order is validated if user information and prescription information also match information stored on the online server. Additionally, the prescription may be validated after the online server communicates with another server such as the medical provider's server. Alternatively, the prescription order may be simply validated if the user information matches the prescription information. For example, if either the patient information or the prescription order information does not match the information stored on the online server, then the method proceeds to block 258 where the user receives a failed prescription notification. By way of example and not of limitation, an explanation may be provided by the online server such as the patient's personal information is incorrect, or the prescription has expired, or a physician's examination is required before filling the order, or the patient needs to wait a couple more days before the prescription order may be filled. Those skilled in the art shall appreciate that the user information and prescription information may require being input more than once before a failed notification is provided to the user.
If the prescription order is validated by having the patient information match the prescription order information, the method proceeds to decision diamond 260 and determines if the prescription order is covered by the user's health insurance. As with prescription information, the insurance information for a specific user may be stored on a database associated with the online server of the production facility or the health insurance company's server may be queried by the online server via secured network about the accuracy of the user's insurance policy such as determining if the insured's policy is up-to-date. Additionally, information about the medications covered by the specific insurer may be queried, co-payment information, prescription drug policy, secondary insurance information, or any other such pertinent insurance information.
If the prescription order is paid for partially or fully by the user's health insurance, the method proceeds to process the transaction at block 262. A more detailed view of the transaction process 262 is provided below in
The prescription order may not be covered, or may only be partially covered by the user's insurance and so the method proceeds to decision diamond 264 where alternative payment methods can be provided. By way of example and not of limitation, alternative payment methods include VISA transactions, debit card transactions, ATM transactions, PayPal transactions, Electronic Fund Transfers, and other such methods for performing on-line transactions. If the alternative payment method can be processed, the method proceeds to block 262 where the transaction is processed. However, if the alternative payment method can not be effectively processed, the method proceeds to block 266 where the user receives a failed payment notification.
Referring to
If a determination is made that the transaction is not a valid transaction, the method proceeds to block 272 where a log of either the prescription complication, transaction complication, or both is recorded. The prescription complication may arise because the production facility can not satisfy the order. The transactional complication may be caused by the payment method not being authenticated.
If the transaction is valid, the method proceeds to block 274 where the log indicates that prescription has been filled. The processing of the online transaction may also comprise confirming that the drugs requested are in the production facility's inventory and ready for dispensing. Inventory information may be stored on either the online server or the production server or on any other communicatively connected database or computer associated to the transaction component of the online server.
After determining whether the transaction is valid, the method proceeds to block 276 where the user receives a completed or failed transaction notification. In the illustrative example, the failed transaction notification comprises information explaining to the user that the transaction failed because an invalid credit card number was provided. If the transaction is determined to be valid, the prescription is logged as filled and the user receives a prescription completed notification via the network connection between the online server and the user's computer.
A multiple prescription container assembly comprises a plurality of containers that are configured to receive a plurality of medications, even though a single prescription may reside within an individual container. The multiple prescription container assembly is configured to dispense a plurality of different tablets to a particular individual. The illustrative multiple prescription container assembly comprises a plurality of containers made from a single piece of moldable material wherein the containers are ordered to permit sequential dispensing. At least one of the containers is configured to receive a first tablet associated with a first medication, and a second tablet associated with a second medication that is different from the first medication; the first tablet and the second tablet to be taken at approximately the same time by the particular patient, which is also referred to as a prescribed interval. By way of example and not of limitation, there is a flange on the top surface of each of the containers. The multiple prescription container assembly also comprises a plurality of lids, the lidstock configured to interface with the flange of each integrated container. Each lid seals each of the containers and has a surface that receives a printable indicia with specific information regarding the particular individual. Additionally, the multiple prescription assembly comprises a sleeve or “secondary package” that is coupled to the plurality of sealed containers wherein the sleeve is configured to permit sequential dispensing for each of the sealed containers.
Referring to
Each of the illustrative embodiments 302, 304 and 306 is an element of the multiple prescription container that stores tablets. It should be noted that a “tablet” is a small article which is swallowed. A tablet includes pills, capsules, and caplets. A tablet may also be a solid dose of medication or supplement, i.e. pill, tablet, capsule or a liquid dose of medication, e.g. Vitamin E or (cod liver oil) provided in a capsule. In general, a tablet may be a prescription medication, supplements, or any other such article that is intended to be ingested to improve a user's health or wellbeing. A tablet may also be medication in the form of a suppository, or vitamins, herbal supplements and the like.
Referring to
In one embodiment, the multiple prescription container comprises a plurality of individual containers. In the illustrative embodiment, container 321 adjacent to container 328 and are sealed with lid 326. The lid 326 seals all the containers. The sequential connection between containers provides a linear grouping of the individual containers. However, it should be noted that the quantity of containers in a multiple prescription assembly may vary as well as the interconnection configuration of the containers, e.g. a circular, an elliptical, polyhedral, etc. In this illustrative embodiment, the empty and unsealed containers are made from a single piece of moldable material having indentations 330, which may also be perforations or cuts, that separates container 321 from the other container 328.
At least one of the containers is configured to receive a first tablet associated with a first medication, and a second tablet associated with a second medication that is different from the first medication. The set of containers 334 are separated from one another by frangible connections 336 or perforations positioned within the flanged edge 324 that is proximate to the adjacent container. The frangible connection 336, which is between containers, allows the containers to “break-away” from the set of containers 334 in a sequential manner. Once the lids are attached and/or sealed to the top flanged surface 324, this sequential connection supports a linear configuration for sequential dispensing.
Each container may also comprise a collar 338 below the flanged edge 324 that allows the containers to be stored in a stackable configuration. Each container may also comprise a bottom surface 340 with at least one ridge 342. The ridge is useful in minimizing tablet-to-tablet collisions and avoiding medication sloughing off of a tablet due to collisions with other tablets. By limiting excessive movement of the tablets in each of the containers, the ridge or ridges on the bottom of the container(s) help preserve the integrity of the tablets within. The ridge may protrude outward from the bottom surface of the containers as shown in
The illustrative set of containers 334 comprises seven adjacent containers configured for sequential dispensing of the contents of each container. Sequential dispensing refers to individual containers being “dispensed one at a time,” which is different from being “cherry picked” from a grid of individual containers. The number of containers in a set of integrated containers may vary due to the prescription prescribed for the user. While the illustrative embodiment describes seven containers, a set of containers may comprise at least two containers to about 20 containers, and more preferably about 5 to about 14 containers. It is expected that most of the containers will be of similar size for ease of filling the containers, but in certain embodiments varying container sizes may be needed. The set of containers 334 may be opaque but in preferred embodiments, the moldable material comprises enough clarity for the user to visualize the contents of the containers.
The illustrative lid 326 of container 321 comprises a printing surface where unique prescription-specific information is displayed for each container. The information displayed on the printing surface may include, but is not be limited to, the patient's name, the date and the day of the week the contained mixed dosage medications are to be taken, as well as the time of day that the tablets are to be taken. The markings on the containers inform the patient and/or caregiver the time in which the contents of the container are to be taken in the proper sequence. In general, the lid stock comes from a roll and the appropriate amount of lidstock is released from the roll to accommodate the designated number of containers to be sealed. For a thermoformed container, using polypropylene for the material for the lid stock, an unsealed area of lid film is generally used to help in the peeling of the lid. The breakaway tab 332 on the illustrative container 321 gives the user something to hold onto and is a useful feature to a container that is manufactured by injection molding with plastics like polyethylene or styrene.
Referring to
Additionally, there is shown a notch 363 that is configured to be fit into an illustrative cavity that is a square-shaped perimeter 365 and receives a notch similar to notch 363. The notch 363 permits two dispensing sleeves to “snap” together. The square shaped perimeter 365 is located on near the edge of the dispensing sleeve 352 and has a square cut and a lip.
Printed material 366 such as detailed label 160 in
Referring to
Additionally, the particular sleeve 368 further comprises integral, mold-in release tabs 380a and 380b configured to allow the sealed containers to slide out of the dispensing sleeve 368 when pressure is applied to release tabs 380a and 380b. The container 350 is then removed by breaking the perforation mark between the containers. The release tabs are configured to “catch” the next container 350 so that one container is released at a time, thereby providing child resistance.
Referring to
Referring to
Referring to
Referring to
In the illustrative embodiment of
Each individual container within each set of containers is to be taken at the correct, prescheduled time each day as marked 426 on each container. The multiple prescription container assembly 420 may be provided to the patient or caregiver as three separate sets of containers enclosed in three separate dispensing sleeves. The patient or caregiver can interlock the three separate dispensing sleeves 428a, 428b, and 428c.
Referring to
Referring to
Referring to
Referring to
Both of the multiple prescription container assemblies 450 and 454 are configured for sequential dispensing. While the illustrative embodiment describes seven containers, a set of containers may comprise at least two containers to about 20 containers, and more preferably about 5 to about 14 containers. It is expected that most of the containers will be of similar size for ease of filling the containers. Additionally, the illustrative moldable material comprises enough clarity for the user to visualize the contents of the containers.
Referring to
Referring to
Additionally, the illustrative lid 464 is cut to permit a patient to remove the lid by placing a finger underneath a cut 472. A ridge 474 permits the lid 464 to be more easily removed from the container. A more detailed view of a patient or caregiver removing the lid 464 is provided in
Referring to
The method comprises sealing the plurality of containers of the set of integrated containers with the corresponding plurality of lids 510 of the lidstock. The quantity of the containers in the tablet assembly is variable, depending on the prescription of the patient. The number of lids will correspond to the number of containers utilized in the tablet assembly. A printable surface is provided on each of the plurality of lids 512 in which specific printing indicia or information is placed 514 relating to the administration of the tablets held in the container sealed by the corresponding lid.
This method may also comprise providing a sleeve or secondary package for receiving the set of sealed containers 516 and placing the set of sealed containers or primary package into the sleeve 518 or secondary package. The patient completes the process of dispensing the tablets by expelling or manually moving one of the plurality of sealed containers out of the sleeve at the time printed on the corresponding lid 520. Once the container has been slid out from the secondary package, the container is removed from the set of containers as well as the secondary package and/or sleeve by tearing the frangible connection between the expelled container and the adjacent container remaining in the sleeve 522. The patient can then gain access to the tablets in the expelled container by removing the lid from the container 524. In some alternative embodiments, the method comprises providing extended tabs on the lids, break-away tabs and/or providing chamfered edges on the containers to make removing the lid off of the container more convenient.
In yet another embodiment, the method further comprises providing a child safety release tab on a secondary sleeve as seen on the tablet assembly embodiment shown above, to prevent unwanted tampering of the tablets in the containers by children. In the embodiment described above, at the proper time for dispensing the tablets from a container, the patient holds the dispenser and manually actuates the release tabs while simultaneously manually sliding the strip of containers in a direction “out of the dispenser.” When the perforations or frangible connection between the first two containers in the strip reach the outer edge of the dispenser the release tab resets, thus locking the strip from further sliding motion. The patient then tears off, at the perforations, the protruding container that contains the correct medications for the stated time, pulls up on the extended corner of the lid, and opens the container by peeling back the lid, exposing the medications. The dispenser then is left with the correct printed markings showing in the thumb groove display window, ready for the next dosage to be taken. Other embodiments of the methods of dispensing tablets comprise providing a “senior friendly” tablet assembly instead of an assembly with a child safety tab for the convenience of patients with limited dexterity shall be readily identified by those of ordinary skill in the art.
Referring to
The order processing system 602 is in communication with a tablet management system 608. The tablet management system 608 controls the tablets that fill the pill refill modules, which in turn fill up the appropriate multiple prescription containers. The tablet management system 608 also communicates when a refill module is not properly being filled. The order processing system 602 also communicates with a container selection process 604. The container selection process 604 may receive an order for a particular container assembly from the user placing the order, e.g. pharmacist, caregiver, patient, etc. Alternatively, the container selection process 604 may simply receive a multiple prescription order, and may have to select the appropriate container for filling the order, e.g. less than 5 tablets require a small container, 6-10 tablets require a mid-size container, and 10-20 tablets require a large container.
After the container selection process 604, there is a container inspection process 606 during which inspection of the appropriate container is performed, to ensure that the appropriate container or substitute container has been selected. Additionally, the inspection process 606 may include identifying whether the container is broken or has some obstruction that may cause some difficulty to downstream systems and/or processes.
After the container inspection 606, the container filling process 610 is initiated. In an illustrative example, the container filling process 610 occurs by placing the selected container on a pallet or tote and moving the pallet or tote on a conveyer, which moves the pallet to the appropriate filling location so that the appropriate tablets may fill the container.
After filling the appropriate container with a plurality of medications and/or tablets, an inspection of the filled containers is performed at block 612. The inspection may be conducted by using X-ray detection, near infrared detection, robotic detection at visual wavelengths, or any other such technique that looks at color, shape, weight, density, or other such parameter to determine if the appropriate container has been filled with the correct prescription. In certain instances, a visual inspection by a pharmacist may also be performed.
After inspection, the method proceeds to the lid assembly process 614 during which the lid is applied to the multiple prescription container producing the primary package. The sleeve is then applied at the sleeve assembly process in block 616. Alternatively, a cap may be placed on the sealed multiple prescription container, as described above. For purposes of this patent, the term “sleeved container” or secondary package includes a multiple prescription container having a cap, unless otherwise indicated.
At block 618, the inspection of the sleeved sealed containers is conducted. This inspection at block 618 is performed after the multiple prescription container has been sealed. Note, the inspection at block 612 was conducted before sealing. The need for the second inspection described in block 618 is in case a tablet or medication fell out of the container or was mislabeled. Additionally, one of the tablets or medications may also have been broken or otherwise compromised. As stated above, the inspection may be conducted using a variety of different instruments including, but not limited to, robotic inspections at a visual wavelength, near IR, X-ray and any other detection means that can identify the type of tablets or medication in each container.
The method then proceeds to block 620 where the sleeved sealed container(s) are combined with printed materials in the tote. The printed materials may include detailed labels as described in
After combining the printed materials and the sleeved sealed multiple prescription containers at a distribution element, the combination is shipped to a pharmacy, customer, or sent to a pick-up window as represented by block 624. As stated above, the customer may be a patient, a caregiver, a medical health professional, or any other such person
Referring to
The powered conveyor then transports the tote having the empty containers to filler cells that have a particular medication or tablet. As the empty container passes under each filler cell 635, the tablet management system determines whether a tablet is to be dispensed. The container filling process requires a variety of different filling cells that have to be refilled by illustrative operators 636 and 638. The conveyor belts and filler cells are grouped into units for easier operation and maintenance. In the illustrative embodiment, the powered conveyers can travel to the appropriate filler cell in an efficient manner that permits a particular pallet to bypass traveling along the perimeter of the conveyor assembly. For example, a particular pallet may bypass traveling along the length of a conveyor via a bypass 640 or 642.
The filled containers are then inspected to determine if the container has been properly filled. An operator 644 mans the inspection equipment. If order adjustments are needed, another operator 646 is charged with resolving any problems with one or more orders. The operator 644 determines that the prescription has been properly filled after having visually inspected the multiple prescription or using other inspection means are described herein. The appropriate lid is then placed on the containers. A lidstock sealer 648 seals the lid on the multiple prescription container. The sleeve is then selected at the sleeve assembly 650 and then applied. The operator 652 inspects the sleeve. Additionally, the operator 652 may be charged with combining the sleeved and sealed prescription container. A separate tote filling system 654 or detailed labeling component generates the detailed label that is combined with the sleeved and sealed multiple prescription containers. The conveyor 656 then transports the filled prescription order to a predetermined location so that the filled prescription order may be shipped to the pharmacy or customer.
Referring to
Referring to
The order processing system 602 also accommodates receiving the tablet received in block 700, after having placed the order for additional inventory in block 696. After receiving the ordered tablets, the inventory management system is updated as indicated in block 702. The updated inventory is then communicated to the pill management system 608. The order processing system 602 is intended to make it more efficient for a production facility and/or pharmacist to manage the tablet or medication inventory stored at the local facility. By creating a system and method for automated ordering, the order processing system can provide a more efficient means for controlling inventory and thereby more efficiently control the filling of multiple prescription orders in multiple prescription containers.
Referring to
At block 706, the method may determine the type of container to use based on the types of medications, size, and frequency. The determination of the type of container may be performed without receiving a user's request for a particular multiple prescription container assembly as described above. The determination of container availability is then made at decision diamond 708. If a particular container is not available, the method may return to block 706 to select an alternative container. Issues associated with container availability are reported to the inventory management system 702. If the containers are available, the method proceeds to block 710 where the containers are de-nested and then placed on the appropriate pallet, at block 712. The method then proceeds to container inspection at block 606.
Referring to
A tablet refill control system 728 manages the tablet being distributed to the appropriate refill module 730. Additionally, the tablet refill control system receives tablet information 732, and this tablet information is stored on the tablet refill control system 728. The additional tablet inventory and is then communicated to the inventory management system 702.
Referring to
Referring to
The illustrative conveyer system receives a container pallet or tote at block 752. The containers then stop at the appropriate refill module and are filled with tablets as described in block 754. Additionally, each refill module may comprise a sensor 738 that counts the number of tablets that are distributed by the refill module, and this count may be communicated to the tablet refill control system 728. A container tracking system 756 tracks the location of each container so that the appropriate medications or tablets are filled by the appropriate filling modules. By way of example and not of limitation, the container tracking system 756 and the refill module are communicatively coupled to the tablet refill control system 728. After the containers are filled by the plurality of refill modules, the illustrative unsealed containers are inspected at block 612.
Referring to
Referring to
Referring to
In the illustrative production facility 628, a pallet is used to transport the multiple prescription container to the appropriate lid assembly section, as described by block 778. In another embodiment 660, a pallet is not needed and the container simply travels along the conveyer. In yet another embodiment, a conveyer is not needed. However, regardless of the system and method used to transfer the filled multiple prescription container, a label needs to be applied. In this illustrative embodiment, the appropriate label is generated as described above and placed on the filled multiple prescription container as represented by block 780. The method then proceeds to block 782 where the lidstock is heat sealed to the filled multiple prescription container. The sleeve is then applied at the sleeve assembly process 616.
Referring to
The illustrative sleeve is generated by receiving a blank sleeve 794 and placing the sleeve 796 in the appropriate position so that a printed label 798 can be placed on the sleeve. The printed label 798 may be generated locally with printing ink, toner, or a ribbon 802. The complete sleeve assembly 804 is then ready to be coupled to the sealed multiple prescription container. As described above, a cap may also be placed on the sealed multiple prescription container, instead of a sleeve.
Refer to
Note, that other problems that may also be identified during the inspection process 618 include identifying tablets or medication being broken, compromised, or too many tablets being dispensed at one particular time. Additionally, the inspection may not be limited to simply checking the label, and a more exhaustive secondary inspection may be conducted using a variety of different instruments including, but not limited to, robotic inspections at a visual wavelength, near IR, X-ray, precision weighing and any other detection means that can identify the type of tablets or medication in each container.
Referring to
Referring to
Referring to
It is to be understood that the foregoing is a detailed description of illustrative embodiments. The scope of the claims is not limited to these specific embodiments. Various elements, details, execution of any methods, and uses can differ from those just described, or be expanded on or implemented using technologies not yet commercially viable, and yet still be within the inventive scope of the present disclosure. The scope of the invention is determined by the following claims and their legal equivalents.
This application claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Application No. 60/795,370, filed Apr. 26, 2006, which is incorporated herein by reference in its entirety. This application claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Application No. 60/795,446, filed Apr. 26, 2006, which is incorporated herein by reference in its entirety. This application claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Application No. 60/795,413, filed Apr. 26, 2006, which is incorporated herein by reference in its entirety. This application is a continuation-in-part of patent application of patent application Ser. No. 11/241,783, filed Sep. 30, 2005, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
2294220 | Albertson | Aug 1942 | A |
3126129 | Weinberg | Mar 1964 | A |
3254828 | Hershey | Jun 1966 | A |
3308962 | Bryant | Mar 1967 | A |
3409721 | Norman | Nov 1968 | A |
3410450 | Fortenberry | Nov 1968 | A |
3432951 | Phil | Mar 1969 | A |
3450306 | Gill | Jun 1969 | A |
3497982 | Schulz | Mar 1970 | A |
3503493 | Nagy | Mar 1970 | A |
3703955 | Inacker | Nov 1972 | A |
3773250 | Phillips | Nov 1973 | A |
3780856 | Braverman | Dec 1973 | A |
3809220 | Arcudi | May 1974 | A |
3881625 | Landen | May 1975 | A |
3884379 | Landen | May 1975 | A |
3921804 | Tester | Nov 1975 | A |
3933245 | Mullen | Jan 1976 | A |
4036385 | Morris | Jul 1977 | A |
4039080 | Cappuccilli | Aug 1977 | A |
4062445 | Moe | Dec 1977 | A |
4274550 | Feldstein | Jun 1981 | A |
4318477 | Kerpe | Mar 1982 | A |
4416375 | Braverman et al. | Nov 1983 | A |
4512476 | Herrington | Apr 1985 | A |
4535890 | Artusi | Aug 1985 | A |
4546901 | Buttarazzi | Oct 1985 | A |
4553670 | Collens | Nov 1985 | A |
4635890 | Matsuda et al. | Jan 1987 | A |
4655026 | Wigoda | Apr 1987 | A |
4693371 | Malpass | Sep 1987 | A |
4733797 | Haber | Mar 1988 | A |
4736849 | Leonard et al. | Apr 1988 | A |
4749085 | Denney | Jun 1988 | A |
4799590 | Furman | Jan 1989 | A |
4805800 | Nocek et al. | Feb 1989 | A |
4811764 | McLaughlin | Mar 1989 | A |
4823982 | Aten et al. | Apr 1989 | A |
4830183 | Metters | May 1989 | A |
4832229 | Hackmann et al. | May 1989 | A |
4850489 | Weithmann et al. | Jul 1989 | A |
4860899 | McKee | Aug 1989 | A |
4867315 | Baldwin | Sep 1989 | A |
4872559 | Schoon | Oct 1989 | A |
4872593 | Behringer | Oct 1989 | A |
4887790 | Wilkinson et al. | Dec 1989 | A |
4918604 | Baum | Apr 1990 | A |
4953745 | Rowlett | Sep 1990 | A |
4954210 | Desmond | Sep 1990 | A |
4972657 | McKee | Nov 1990 | A |
4993586 | Taulbee et al. | Feb 1991 | A |
5014851 | Wick | May 1991 | A |
5027954 | Hickerson | Jul 1991 | A |
5085510 | Mitchell | Feb 1992 | A |
5186345 | An | Feb 1993 | A |
5195123 | Clement | Mar 1993 | A |
5199636 | Young | Apr 1993 | A |
5310057 | Caldwell et al. | May 1994 | A |
5310437 | Tucker | May 1994 | A |
5366087 | Bane | Nov 1994 | A |
5390796 | Kerfoot | Feb 1995 | A |
5422831 | Misra et al. | Jun 1995 | A |
5443178 | Holmes | Aug 1995 | A |
5457895 | Thompson et al. | Oct 1995 | A |
5505371 | O'Neill | Apr 1996 | A |
5522512 | Archer et al. | Jun 1996 | A |
5544768 | Gargione | Aug 1996 | A |
5558229 | Halbich | Sep 1996 | A |
5577612 | Chesson et al. | Nov 1996 | A |
5597995 | Williams et al. | Jan 1997 | A |
5638657 | Archer et al. | Jun 1997 | A |
5642906 | Foote et al. | Jul 1997 | A |
5671592 | Yuyama et al. | Sep 1997 | A |
5711442 | Kusz | Jan 1998 | A |
5737539 | Edelson et al. | Apr 1998 | A |
5746323 | Dragotta | May 1998 | A |
5788079 | Bouthiette | Aug 1998 | A |
5788974 | Maida | Aug 1998 | A |
5792092 | Turngren | Aug 1998 | A |
D400412 | Gold | Nov 1998 | S |
5873466 | Hulick | Feb 1999 | A |
5878887 | Parker et al. | Mar 1999 | A |
5883370 | Walker et al. | Mar 1999 | A |
5891078 | Turngren et al. | Apr 1999 | A |
5899333 | Williams et al. | May 1999 | A |
5921398 | Carroll | Jul 1999 | A |
5941402 | Krueger | Aug 1999 | A |
5963453 | East | Oct 1999 | A |
5995938 | Whaley | Nov 1999 | A |
6012582 | Haygeman et al. | Jan 2000 | A |
6021392 | Lester et al. | Feb 2000 | A |
6021623 | Bouthiette | Feb 2000 | A |
6023916 | Bouthiette | Feb 2000 | A |
6066374 | Healy et al. | May 2000 | A |
6068156 | Liff et al. | May 2000 | A |
6077530 | Weinstein et al. | Jun 2000 | A |
6115996 | Yuyama et al. | Sep 2000 | A |
6129211 | Prakken et al. | Oct 2000 | A |
6155423 | Katzner et al. | Dec 2000 | A |
6155485 | Coughlin et al. | Dec 2000 | A |
6170230 | Chudy et al. | Jan 2001 | B1 |
6171439 | Groeneweg | Jan 2001 | B1 |
6176392 | William et al. | Jan 2001 | B1 |
6181979 | Murakami | Jan 2001 | B1 |
6202923 | Boyer et al. | Mar 2001 | B1 |
6213343 | Damikolas | Apr 2001 | B1 |
6227371 | Song | May 2001 | B1 |
6273260 | ColDepietro et al. | Aug 2001 | B1 |
6293403 | Holmberg | Sep 2001 | B1 |
6308494 | Yuyama et al. | Oct 2001 | B1 |
6317648 | Sleep et al. | Nov 2001 | B1 |
6318630 | Coughlin et al. | Nov 2001 | B1 |
6324253 | Yuyama et al. | Nov 2001 | B1 |
6330351 | Yasunaga | Dec 2001 | B1 |
6343695 | Petrick et al. | Feb 2002 | B1 |
D455057 | Medhurst | Apr 2002 | S |
6371297 | Cha | Apr 2002 | B1 |
6375956 | Hermelin et al. | Apr 2002 | B1 |
6378572 | Neubauer et al. | Apr 2002 | B1 |
6401919 | Griffis et al. | Jun 2002 | B1 |
6449921 | Kim | Sep 2002 | B1 |
6449927 | Hebron et al. | Sep 2002 | B2 |
6460693 | Harrold | Oct 2002 | B1 |
6505461 | Yasunaga | Jan 2003 | B1 |
6523694 | Lux et al. | Feb 2003 | B2 |
6527138 | Pawlo et al. | Mar 2003 | B2 |
6535637 | Wootton et al. | Mar 2003 | B1 |
6564945 | Weinstein et al. | May 2003 | B1 |
6581798 | Liff et al. | Jun 2003 | B2 |
6594928 | Clawson et al. | Jul 2003 | B1 |
6611733 | Huerga | Aug 2003 | B1 |
6662081 | Jacober et al. | Dec 2003 | B1 |
6681935 | Lewis | Jan 2004 | B1 |
6690998 | Yuyama | Feb 2004 | B1 |
6711460 | Reese | Mar 2004 | B1 |
6735497 | Wallace et al. | May 2004 | B2 |
6738723 | Hamilton | May 2004 | B2 |
6757898 | Ilsen et al. | Jun 2004 | B1 |
6771369 | Rzasa et al. | Aug 2004 | B2 |
6839403 | Kotowski et al. | Jan 2005 | B1 |
6892512 | Rice et al. | May 2005 | B2 |
6925774 | Peterson | Aug 2005 | B2 |
6962266 | Morgan et al. | Nov 2005 | B2 |
6971541 | Williams et al. | Dec 2005 | B2 |
6981592 | Siegel | Jan 2006 | B2 |
7006893 | Hart et al. | Feb 2006 | B2 |
7010899 | McErlean et al. | Mar 2006 | B2 |
7017513 | Giewercer | Mar 2006 | B2 |
7017748 | Weinstein | Mar 2006 | B2 |
7028723 | Alouani et al. | Apr 2006 | B1 |
7055294 | Lewis | Jun 2006 | B1 |
7089131 | Thouin et al. | Aug 2006 | B2 |
7111780 | Broussard et al. | Sep 2006 | B2 |
7185476 | Siegel et al. | Mar 2007 | B1 |
7225597 | Knoth | Jun 2007 | B1 |
7398279 | Muno et al. | Jul 2008 | B2 |
7426814 | Knoth | Sep 2008 | B2 |
7509787 | Ballestrazzi et al. | Mar 2009 | B2 |
7559482 | Coveley | Jul 2009 | B2 |
7568580 | Fenton | Aug 2009 | B2 |
7668730 | Reardan | Feb 2010 | B2 |
7672859 | Louie et al. | Mar 2010 | B1 |
7690173 | Luciano et al. | Apr 2010 | B2 |
7747345 | Ohmura et al. | Jun 2010 | B2 |
7828148 | Gibson | Nov 2010 | B2 |
7894656 | Kim | Feb 2011 | B2 |
7942280 | Priebe et al. | May 2011 | B2 |
7942451 | Adler | May 2011 | B2 |
7946421 | Kowalik et al. | May 2011 | B2 |
8020702 | Strub et al. | Sep 2011 | B2 |
8041102 | Yuyama et al. | Oct 2011 | B2 |
8055512 | Pankow et al. | Nov 2011 | B1 |
8074426 | Luciano et al. | Dec 2011 | B2 |
8122849 | Clarke et al. | Feb 2012 | B2 |
8123036 | Luciano et al. | Feb 2012 | B2 |
8146747 | Luciano et al. | Apr 2012 | B2 |
8196774 | Clarke et al. | Jun 2012 | B1 |
8266878 | Luciano et al. | Sep 2012 | B2 |
8556077 | Hanley | Oct 2013 | B1 |
8712582 | Luciano et al. | Apr 2014 | B1 |
8713897 | Luciano et al. | May 2014 | B2 |
8727208 | Poisner | May 2014 | B2 |
8752704 | Alonso et al. | Jun 2014 | B2 |
8777012 | Luciano et al. | Jul 2014 | B2 |
8789700 | Luciano et al. | Jul 2014 | B2 |
8914298 | Luciano | Dec 2014 | B1 |
8931241 | Luciano et al. | Jan 2015 | B2 |
8972288 | Luciano | Mar 2015 | B2 |
9334096 | Luciano et al. | May 2016 | B2 |
9428314 | Luciano et al. | Aug 2016 | B2 |
20010017023 | Armington et al. | Aug 2001 | A1 |
20010041968 | Hamilton | Nov 2001 | A1 |
20020029223 | Rice et al. | Mar 2002 | A1 |
20020042725 | Mayaud | Apr 2002 | A1 |
20020047019 | Devers | Apr 2002 | A1 |
20020066691 | Varon | Jun 2002 | A1 |
20020099467 | Sleep et al. | Jul 2002 | A1 |
20020104778 | Lux et al. | Aug 2002 | A1 |
20020117405 | Wang et al. | Aug 2002 | A1 |
20030012701 | Sangha et al. | Jan 2003 | A1 |
20030018495 | Sussman | Jan 2003 | A1 |
20030136698 | Klatt | Jul 2003 | A1 |
20030142784 | Suzuki et al. | Jul 2003 | A1 |
20030174326 | Rzasa et al. | Sep 2003 | A1 |
20030176942 | Sleep et al. | Sep 2003 | A1 |
20030193185 | Valley | Oct 2003 | A1 |
20030200726 | Rast | Oct 2003 | A1 |
20030209461 | French et al. | Nov 2003 | A1 |
20030216831 | Hart et al. | Nov 2003 | A1 |
20040011806 | Luciano et al. | Jan 2004 | A1 |
20040011961 | Platt et al. | Jan 2004 | A1 |
20040045863 | Rhoades | Mar 2004 | A1 |
20040065053 | Rice et al. | Apr 2004 | A1 |
20040069674 | Siegel | Apr 2004 | A1 |
20040069675 | Stevens | Apr 2004 | A1 |
20040088187 | Chudy et al. | May 2004 | A1 |
20040094050 | Ackley et al. | May 2004 | A1 |
20040122713 | Hill et al. | Jun 2004 | A1 |
20040123564 | McErlean et al. | Jul 2004 | A1 |
20040140241 | Weinstein | Jul 2004 | A1 |
20040158507 | Meek et al. | Aug 2004 | A1 |
20040162634 | Rice et al. | Aug 2004 | A1 |
20040172295 | Dahlin et al. | Sep 2004 | A1 |
20040188312 | Stepowany | Sep 2004 | A1 |
20040188998 | Henthorn | Sep 2004 | A1 |
20040217038 | Gibson | Nov 2004 | A1 |
20040225528 | Brock | Nov 2004 | A1 |
20040243445 | Keene | Dec 2004 | A1 |
20040249591 | Trebbi | Dec 2004 | A1 |
20040251157 | Behnke et al. | Dec 2004 | A1 |
20040256277 | Gedanke | Dec 2004 | A1 |
20040260424 | Mahar | Dec 2004 | A1 |
20040268413 | Reid et al. | Dec 2004 | A1 |
20050021367 | Saeger et al. | Jan 2005 | A1 |
20050044762 | Atluri | Mar 2005 | A1 |
20050049746 | Rosenblum | Mar 2005 | A1 |
20050049747 | Willoughby et al. | Mar 2005 | A1 |
20050060197 | Mayaud | Mar 2005 | A1 |
20050061825 | Willoughby et al. | Mar 2005 | A1 |
20050144038 | Tamblyn et al. | Jun 2005 | A1 |
20050171813 | Jordan | Aug 2005 | A1 |
20050209879 | Chalmers | Sep 2005 | A1 |
20050218152 | Simon | Oct 2005 | A1 |
20050269817 | Alasia et al. | Dec 2005 | A1 |
20060045323 | Ateya | Mar 2006 | A1 |
20060064670 | Linebarger et al. | Mar 2006 | A1 |
20060065670 | Doublet et al. | Mar 2006 | A1 |
20060076262 | Bassett | Apr 2006 | A1 |
20060122729 | Murphy et al. | Jun 2006 | A1 |
20060124502 | Lee | Jun 2006 | A1 |
20060163269 | Anderson et al. | Jul 2006 | A1 |
20060163869 | Adler et al. | Jul 2006 | A1 |
20060213816 | Jorritsma | Sep 2006 | A1 |
20060219595 | Peters | Oct 2006 | A1 |
20070000805 | Brink | Jan 2007 | A1 |
20070131576 | Ehling et al. | Jun 2007 | A1 |
20070150219 | Cawker et al. | Jun 2007 | A1 |
20070168228 | Lawless | Jul 2007 | A1 |
20070169838 | Yuyama et al. | Jul 2007 | A1 |
20070173971 | Richardson et al. | Jul 2007 | A1 |
20070210164 | Conlon et al. | Sep 2007 | A1 |
20070228047 | Pehr et al. | Oct 2007 | A1 |
20070235369 | Perell | Oct 2007 | A1 |
20080000979 | Poisner | Jan 2008 | A1 |
20080010848 | Miles | Jan 2008 | A1 |
20080059228 | Bossi et al. | Mar 2008 | A1 |
20080110131 | Kim | May 2008 | A1 |
20080142400 | Arnold | Jun 2008 | A1 |
20080149657 | Kim | Jun 2008 | A1 |
20080190076 | Klingel et al. | Aug 2008 | A1 |
20080228160 | Harrison | Sep 2008 | A1 |
20090119129 | Nadas et al. | May 2009 | A1 |
20090133362 | Bentele et al. | May 2009 | A1 |
20090139893 | McGonagle et al. | Jun 2009 | A1 |
20090230013 | Born et al. | Sep 2009 | A1 |
20090301925 | Alloro | Dec 2009 | A1 |
20100069213 | Luciano et al. | Mar 2010 | A1 |
20100089936 | Luciano et al. | Apr 2010 | A1 |
20100100391 | Daya et al. | Apr 2010 | A1 |
20100139222 | Federle et al. | Jun 2010 | A1 |
20100147734 | Luciano et al. | Jun 2010 | A1 |
20100153129 | Luciano et al. | Jun 2010 | A1 |
20100175352 | Soloman | Jul 2010 | A1 |
20100252479 | Corroon | Oct 2010 | A1 |
20100265072 | Goetz et al. | Oct 2010 | A1 |
20100287880 | Yasunaga et al. | Nov 2010 | A1 |
20100324728 | Rosenblum | Dec 2010 | A1 |
20110015576 | Plumptre et al. | Jan 2011 | A1 |
20110036856 | Ooyen et al. | Feb 2011 | A1 |
20110040572 | Chmiel et al. | Feb 2011 | A1 |
20110100863 | Luciano | May 2011 | A1 |
20110101016 | Luciano | May 2011 | A1 |
20110157342 | Kim | Jun 2011 | A1 |
20110161097 | Fox et al. | Jun 2011 | A1 |
20110251850 | Stephens | Oct 2011 | A1 |
20110264465 | Lindsay | Oct 2011 | A1 |
20120022893 | Findlay et al. | Jan 2012 | A1 |
20120089416 | Luciano | Apr 2012 | A1 |
20120097560 | Contractor | Apr 2012 | A1 |
20120116579 | Shows et al. | May 2012 | A1 |
20120123907 | Luciano | May 2012 | A1 |
20120145585 | Doyle et al. | Jun 2012 | A1 |
20120145739 | Doyle et al. | Jun 2012 | A1 |
20120158430 | MacDonald | Jun 2012 | A1 |
20120186693 | Luciano et al. | Jul 2012 | A1 |
20120200596 | Gotou et al. | Aug 2012 | A1 |
20120290129 | Luciano et al. | Nov 2012 | A1 |
20120293623 | Nygaard | Nov 2012 | A1 |
20120296592 | Luciano et al. | Nov 2012 | A1 |
20120312714 | Luciano et al. | Dec 2012 | A1 |
20130161207 | Luciano et al. | Jun 2013 | A1 |
20140002631 | Amano et al. | Jan 2014 | A1 |
Number | Date | Country |
---|---|---|
3502647 | Jul 1986 | DE |
9613790 | May 1996 | WO |
WO 9613790 | May 1996 | WO |
2004082561 | Sep 2004 | WO |
WO 2004082561 | Sep 2004 | WO |
2005102841 | Nov 2005 | WO |
WO 2005102841 | Nov 2005 | WO |
2011080462 | Jul 2011 | WO |
Entry |
---|
http://www.dailymedrx.com/index.html . “DailyMedRex.com : Convenient Pharmacy. Precise Medication.” |
USPTO, Notice of Allowance of Feb. 26, 2014 for U.S. Appl. No. 12/631,586. |
USPTO, Notice of Allowance of Mar. 28, 2014 for U.S. Appl. No. 12/684,060. |
Number | Date | Country | |
---|---|---|---|
20070250346 A1 | Oct 2007 | US |
Number | Date | Country | |
---|---|---|---|
60795370 | Apr 2006 | US | |
60795446 | Apr 2006 | US | |
60795413 | Apr 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11241783 | Sep 2005 | US |
Child | 11796125 | US |