Patent Grant
10792226
The present disclosure relates generally to refill and dosage management devices and associated systems and methods, and more particularly, to such devices, systems, and methods for use with computerized oral prescription administration (COPA) devices.
The history of pharmacology has produced a continual evolution of routes of administration, pharmaceutical formulations, dosage forms, and dosing devices in a continuing quest towards maximizing the effective benefit and relative costs of prescription medications. Administration of prescribed substances may begin in controlled healthcare settings, for example, at a healthcare facility or by a physician at a patient's home. Early-stage formulations may include liquid forms for parenteral (e.g., into a blood stream) and enteral (e.g., into a gastro-intestine) administration including elixirs, tonics, solutions, suspensions, syrups and eventually injections, intravenous (IVs), and epidurals. The early-stage formulations may be developed to produce advanced forms, for example, via mechanization and formulation research. The early-stage formulations, the advanced forms, and further research and clinical studies such as patient acceptances of the early-stage formulations and/or the advanced forms may contribute to the routes of administration, pharmaceutical formulations, dosage forms, and dosing devices.
As the healthcare treatment transitioned from limited emergency involvement into longer term chronic illness care, higher percentages of the prescribed medication administration shifts from the controlled healthcare settings to patient managed settings. In a patient managed setting, outside the control of a trained healthcare staff, the administration of liquid formulations may be difficult due to non-specific dosing instructions. Dosing based on teaspoon and/or tablespoon measurements may be vague and variable. Dosing cups may have different measurement formats, and thus may cause confusion in a patient managed setting. In addition, dosing cups are often separated from initial prescription bottles, and thus may lead to erroneous administration.
The advancements of mechanical manufacturing systems and pharmacology research enabled patient managed administrations of prescribed substances to shift from liquid formulations to pills (e.g., tablets or capsule-formulations), which may have increased shelf life and allow for patient ease of use, dosing exactness, and production cost reductions. Thus, a majority of oral medications in patient managed settings are now pills. Additionally, there is an increased interest in microparticulate formulations including pellets, granules, micro particles, mini tablets, and the like. However, patients, such as infants, elderly, or impaired patients, that cannot or prefer not to swallow tablets or capsule-formulations may be given enteral oral liquid prescriptions through dosing syringes in patient managed settings. In addition, parenteral liquid formulations are still commonly administered in controlled healthcare settings since the parenteral liquid formulations often have the fastest rate of absorption and the most expedient success in the desired result and can improve localized administration, inventory control, fraud prevention, and administration path audit capability.
Depending on the entity managing the administration of a drug, various forms of the drug may be developed to meet expectations, needs, and challenges of different entities. While there are some exceptions based on effectiveness and toxicity, most pharmaceutical manufacturers may produce multiple formulations of drugs to support different routes of administration and dosing.
There is a growing demand for drug administration in patient controlled or managed settings as consumers increasingly engage in preventative or resultative treatment plans, which involve drug administration in patient controlled settings. For example, outpatient surgeries and/or one-day inpatient surgery stays are increasingly common for significant medical procedures, which may involve subsequent drug administrations at a patient's home. In addition, as the population ages, the demand for prescription management increases. Consumers may take multiple over-the-counter and/or prescribed medicines daily, where the medicines are commonly in the form of pills. Unfortunately, the ease-of-use of pills and the increasing number of consumers engaged in chronic patient managed treatment plans has led to misuse and mismanagement of many drug classes.
For example, pill forms are lightweight, portable, recipient non-specific, difficult for inventory management, don't carry individual identification number, have extensive shelf life, and are inexpensive to produce. Thus, the intakes or usages of pills are difficult to control once outside of healthcare managed environments. In addition, to achieve the economy of scale in the manufacturing process, pill production is scheduled based on maximizing the output of the machines, materials, and/or ingredients available instead of based on future demands. With a few exceptions, a minimal amount of the pills produced are wasted since pills remain active for a long time. Pills proliferate our society and have become conduits to addiction and abuse.
One such patient managed treatment that is highly susceptible to prescription misuse and mismanagement is opioid pain treatment. For example, according to the Food and Drug Administration (FDA), approximately 100 million people in the United States (US) suffer from pain in a given year. About 9 to 12 million of the pain sufferers have chronic or persistent pain, while the remaining pain sufferers have short-term pain from injuries, illnesses, or medical procedures. In 2014, the Centers for Disease Control and Prevention reported that the number of annual opioid prescriptions in the US is about equal to the number of adults in the US population. While pain sufferers should benefit from skillful and appropriate pain management, the misuse or addiction of opioids needs to be controlled. FDA leaders and physicians attempt to address the opioid epidemic by balancing two complementary principles: deal aggressively with opioid misuse and addiction while protecting the well-being of people experiencing acute or chronic pains. However, the pain sufferers in areas where reforms, policies, and restrictions aimed at opioid misuse have been implemented may not experience the balance. Some states have implemented additional known addict or misuser databases that must be checked by providers prior to prescribing. However, physicians may not check the databases prior to prescribing due to the burden of using the systems and/or they may not want to restrict access by true chronic pain sufferers. Other states have implemented reporting and audit trails to track physicians that have prescribed from the opioid family. However, to avoid the additional steps and potentials for audit scrutiny, some physicians may refuse to offer pain management or short-term pain prescriptions, and may refer all cases to pain clinics.
Attempts at improved patient education, enhanced labeling, restrictive prescribing, have led to higher costs for providers, patients, pharmacies, and insurance companies and less overall effectiveness for the patients. In the end, true pain suffers struggle to have access to opioids while opioid misusers continue to manipulate the available avenues for access regardless of the apparent oversights put in place. Policies and plans at various levels have not been successful and are not sufficient to control or reduce the misuse of prescription drugs. Accordingly, improved devices, systems, and methods for drug administration are needed.
The following summarizes some aspects of the present disclosure to provide a basic understanding of the discussed technology. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in summary form as a prelude to the more detailed description that is presented later.
The present disclosure provides refill and dosage management devices and associated systems and methods for use with computerized oral prescription administration (COPA) devices. In this regard, COPA devices may be similar to those described in U.S. patent application Ser. No. 15/406,043, filed Jan. 13, 2017, which is hereby incorporated by reference in its entirety. In order for COPA devices to fit inside an intended user's mouth and function properly, there is a limited volume of space available for storing the substance(s) to be dispensed by the COPA device. Accordingly, in some instances the COPA device may only be able to hold a portion of the intended user's total prescribed dosage amount. For example, the COPA device may be able to hold one dose of a multi-dose daily supply of the substance, hold one or more days' worth of doses of a week's supply of the substance, or hold one or more weeks' worth of a month's supply of the substance, etc. Therefore, in some instances there can be a need to refill the substance(s) in the COPA device for the intended user to complete a prescribed treatment plan.
To this end, the refill and dosage management devices and associated systems and methods of the present disclosure facilitate refilling of the COPA device in accordance with the prescribed treatment plan. In some instances, a docking station for the COPA device may act as the refill and dosage management device. In this regard, the docking station may serve other purposes in addition to the refill and dosage functions such as providing a secure and sanitary storage location for the COPA device, facilitating network communications between the COPA device and a control unit or network, charging the COPA device, etc. The docking station may include a dispensing unit that controls the dispensing of substances from the docking station to the COPA device. For example, the dispensing unit may control the timing and/or volume of the substance(s) dispensed to the COPA device based on the prescribed treatment plan for the intended user and/or the amount of substance(s) currently in the COPA device. In this regard, parameters associated with the dispensing of the substance(s) (e.g., medication type, dosage amount, timing, intended user information, etc.) can be tracked, stored in a COPA management system, and/or communicated throughout the healthcare continuum, including medical personnel, pharmaceutical personnel, patient, authorized caregivers, and/or insurers, such that patient's compliance with a treatment plan can be evaluated and/or the effectiveness of the treatment plan can be evaluated. In this regard, in some instances a comparison of the amount of substance(s) dispensed to the COPA device by the docking station and the amount of the substance(s) dispensed from the COPA device to the intended user can be used to monitor patient compliance. Any notable discrepancies in these amounts can provide an indication of a malfunction in the docking station and/or the COPA device has occurred or an indication that the intended user is not using the system properly to comply with the treatment plan, whether intentionally or accidentally. The docking station and/or COPA management system can send out alerts to participants of the healthcare continuum to serve as notices, reminders, and/or issues based on the dispensed amounts and/or comparisons thereof.
In some embodiments, an apparatus is provided. The apparatus includes a housing having a structure sized and shaped to receive at least a portion of a mouthpiece of an intended user; and a dispensing unit coupled to the housing, the dispensing unit configured to dispense a substance into a reservoir of the mouthpiece. The dispensing unit can be further configured to dispense the substance into the reservoir of the mouthpiece based on dosage instructions for the substance for the intended user. The dosage instructions can include a dosage amount and/or a dosage timing. The dosage instructions for the substance for the intended user can be stored in memory. The dispensing unit can be further configured to store dispensing data associated with the substance being dispensed into the reservoir of the mouthpiece. The dispensing data can include a dispensed amount and/or a dispensed time. The dispensing unit can be further configured to dispense the substance into the reservoir of the mouthpiece based on an amount of the substance in the reservoir of the mouthpiece. The dispensing unit can be configured to receive a communication indicating the amount of the substance in the reservoir of the mouthpiece. The communication indicating the amount of the substance in the reservoir of the mouthpiece can be received from the mouthpiece and/or a central unit in communication with the dispensing unit.
The dispensing unit can include a holding reservoir containing the substance and an actuator in communication with the holding reservoir. The actuator can be configured to move the substance from the holding reservoir of the dispensing unit to the reservoir of the mouthpiece. In some instances, the dispensing unit further includes a second holding reservoir containing a second substance and the actuator is in communication with the second holding reservoir and further configured to move the second substance from the second holding reservoir of the dispensing unit to a second reservoir of the mouthpiece. In other instances, the dispensing unit further includes a second holding reservoir containing a second substance and a second actuator in communication with the second holding reservoir, where the second actuator is configured to move the second substance from the second holding reservoir of the dispensing unit to a second reservoir of the mouthpiece. The second substance can be different than the substance in the other holding reservoir.
The dispensing unit can include an outlet in communication with the actuator that is configured to engage with an inlet of the mouthpiece. The dispensing unit can further include an inlet in communication with the holding reservoir that is configured to receive the substance via the inlet of the dispensing unit. The holding reservoir of the dispensing unit can have a volume equal to or greater than the reservoir of the mouthpiece, including two, three, four, or more times greater than the reservoir of the mouthpiece. In this regard, the holding reservoir of the dispensing unit may be sized to contain multiple doses (e.g., day(s), week(s), month(s), etc.) of the substance based on the intended user's dosage information, while the reservoir of the mouthpiece may be sized to contain one or more doses based on the intended user's dosage information.
The apparatus can further include an identification unit configured to determine an identity of the intended user when the mouthpiece of the intended user is coupled to the structure of the housing. The identification unit can be configured to determine the identity of the intended user based on a communication from the mouthpiece. The identification unit can be configured to determine the identity of the intended user based on a correlation between one or more structural features of the mouthpiece and one or more structural features of the intended user's dentition.
In some embodiments, a method is provided. The method can include receiving, by a docking station, at least a portion of a mouthpiece of an intended user; and dispensing, by a dispensing unit coupled to the docking station, a substance into a reservoir of the mouthpiece. The dispensing can include dispensing the substance into the reservoir of the mouthpiece based on dosage instructions for the substance for the intended user. The dosage instructions can include a dosage amount and/or a dosage timing. The method can also include storing, in memory of the docking station, dispensing data associated with the substance being dispensed into the reservoir of the mouthpiece. The dispensing data can include a dispensed amount and/or a dispensed time. The dispensing can include dispensing the substance into the reservoir of the mouthpiece based on an amount of the substance in the reservoir of the mouthpiece. The method can further include dispensing, by the dispensing unit, a second substance into a second reservoir of the mouthpiece. The second substance can be different than the other dispensed substance. In some embodiments, the method includes engaging an outlet of the dispensing unit with an inlet of the mouthpiece. In some instances, the method further includes determining an identity of the intended user when the mouthpiece of the intended user is coupled to the docking station. The identity of the intended user can be determined based on a communication from the mouthpiece and/or based on a correlation between one or more structural features of the mouthpiece and one or more structural features of the intended user's dentition.
Additional aspects, features, and advantages of the present disclosure will become apparent from the following detailed description.
Illustrative embodiments of the present disclosure will be described with reference to the accompanying drawings, of which:
For the purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings, and specific language will be used to describe the same. It is nevertheless understood that no limitation to the scope of the disclosure is intended. Any alterations and further modifications to the described devices, systems, and methods, and any further application of the principles of the present disclosure are fully contemplated and included within the present disclosure as would normally occur to one skilled in the art to which the disclosure relates.
Embodiments of the present disclosure provide refill and dosage management devices and associated systems and methods for use with computerized oral prescription administration (COPA) devices. In this regard, COPA devices may be similar to those described herein as well as those described in U.S. patent application Ser. No. 15/406,043, filed Jan. 13, 2017, which is hereby incorporated by reference in its entirety.
The disclosed embodiments may provide several benefits. For example, the employment of a docking station with refill and dosage management capabilities can be utilized with the COPA device to ensure that prescribed medications are delivered to the intended recipient. Thus, the disclosed embodiments may avoid misuse and mismanagement of prescription medications. In addition, the disclosed embodiments may allow healthcare providers and insurance companies to better track the administering of the prescribed medications and evaluate the benefits, effects, and/or results of the prescribed medications more accurately. The disclosed embodiments may deliver a precise amount of prescribed medications to a COPA device in accordance with a treatment plan, which may especially benefit patients that are elderly, impaired, or have behavioral issues that may limit their abilities to self-administer prescribed medications. Further, the ability for an intended user to refill a COPA device without the need to revisit a pharmacist, doctor, or other medical professional can improve the user experience and reduce overall costs of administration using the COPA device. In this regard, the volume of medication that can be prescribed and given to an intended user at one time can be greatly increased by using larger holding reservoirs in the docking station, instead of the reservoir(s) of the COPA device that are subject to more stringent size constraints.
Further, the docking station can be utilized to adjust dosages over time (e.g., due to a change in treatment plan or as part of a treatment plan) by controlling the amount and/or timing of the dispensing to the COPA device, monitoring the amount of substance(s) in the COPA device, and/or communicating updated dosing instructions to the COPA device. In this regard, parameters associated with the dispensing of the substance(s) (e.g., medication type, dosage amount, timing, intended user information, etc.) can be tracked, stored in a COPA management system, and/or communicated throughout the healthcare continuum, including medical personnel, pharmaceutical personnel, patient, authorized caregivers, and/or insurers, such that patient's compliance with a treatment plan can be evaluated and/or the effectiveness of the treatment plan can be evaluated. In some embodiments, the docking station can send out alerts to the patient and/or other participants of the healthcare continuum to serve as notices, reminders, and/or issues based on the dispensed amounts and/or patient compliance.
The recess 110 includes a plurality of sensors 112 positioned at various locations within the recess 110. In some embodiments, the sensors 112 may be pressure sensors or optical position sensors. For example, the sensors 112 may be embedded at locations in contact with crevices, nooks, and gum lines of the user. When the user closes his or her mouth around the COPA device 100 using normal or force bite, the sensors 112 can determine whether the user's dentition is positioned within the recess 110. In some embodiments, the sensors 112 may be housed on one or more agile or flexible filament strands embedded within the recess 110. For example, each filament strand may be coupled between two and twenty sensors 112 or any suitable number of sensors 112. In some embodiments, the sensors 112 may be formed and distributed on a meshed structure embedded within the recess 110. The meshed structure may include any suitable number of sensors 112. The sensors 112 on the meshed structure or the filament strand may allow a pressure profile to be created when the user closes his or her mouth on the COPA device 100. In an embodiment, the sensors 112 may monitor and take position and/or pressure measurements when the user closes his or her mouth. The position and/or pressure measurements may be compared to pre-determined data of the user's dentition as a form of verification to identify an intended recipient of a prescribed substance, as described in greater detail herein.
The COPA device 100 further includes a sealed prescription dispensing unit 120. The sealed prescription dispensing unit 120 may be positioned at the top center of the COPA device 100. The sealed prescription dispensing unit 120 may include a sealed sleeve 124 and a plurality of access ports 122 extending from a top side of the sealed sleeve 124 into the prescription dispensing unit 120. The access ports 122 may be configured to receive prescribed substances. For example, a clinician or pharmacy technician may fill prescribed substances into the prescription dispensing unit 120 via the access ports. The prescribed substances may include formulations in various forms, such as liquid and/or multiparticulate. The prescription dispensing unit 120 may include other components, such as a processor, chambers, flow channels, actuators (e.g., micro-pumps), and exit valves, as described in greater detail herein.
The COPA device 100 may provide patient identification functionalities via the patient's teeth imprint in the recess 110. For example, each individual has a unique dental imprint. While there are certain patterns for the ages at which certain teeth may erupt, mature, and be replaced with permanent teeth and for alignment of teeth types, the setting, size, angle, distance between certain points within a patient's mouth, and the resulting bite are different for different patients. In addition, damaged teeth, missing teeth, filled teeth, capped teeth, and prosthetics such as crowns, bridges, partial, and full dentures further the identifying nature or uniqueness of the mouths of different individuals. Thus, the use of the COPA device 100 with the dentition imprint can be effective in identifying a particular individual. The COPA device 100 may provide further patient identification functionalities via various patient verification mechanisms implemented by a processor coupled to the mouthpiece (e.g., embedded within the sealed prescription dispensing unit 120), as described in greater detail herein.
The COPA device 100 further provides controlled prescription administration functionalities via the sealed prescription dispensing unit 120. For example, the processor may be in communication with the sensors 112 and configured to determine whether the COPA device 100 is correctly positioned within the intended user's mouth. Upon detecting a correct position, the processor may control the components within the sealed prescription dispensing unit 120 to release or deliver an exact dosage of the prescribed substances into the intended user's mouth, as described in greater detail herein.
Referring now to
Referring now to
The processor 310 can be in communication with the sensor 112 and the actuator 330. The actuator 330 can be in communication with the reservoir 320 and the exit valves 340 via flow channels 350. The reservoir 320 can be in communication with the access ports 122 (shown in
The reservoir 320 may include one or more chambers 322, for example, one, two, three, four, five, six, or any suitable number of chambers 322. The chambers 322 may be configured to hold a prescribed substance 720. In this regard, the number and size of the chambers 322 can be selected based on the number of prescribed substances, type(s) of prescribed substances, and/or dosage amounts to be used. The chambers 322 can be any size that will still allow the device to be positioned within the mouth of a patient. In some instances, the chambers 322 are in communication with corresponding chambers or channels formed in the COPA device 100 to allow an increased volume of storage for the prescribed substance(s). The chambers 322 may be in communication with the access ports 122. In some embodiments, each chamber 322 is in communication with one of the access ports 122 through access cannulas 730.
A clinician or a pharmacy technician may fill or refill the prescribed substance 720 via the access ports 122. In addition, the docking station 400 may be used to fill or refill the prescribed substance 720 via the access ports 122 as described below. The prescribed substance 720 may include liquid formulations, powder formulations, multiparticulate formulations, or any other suitable formulations. In some embodiments, all chambers 322 are filled with liquid formulations. In some other embodiments, one chamber 322 may be filled with a liquid formulation and another chamber 322 may be filled with a powder or multiparticulate formulation. The prescribed substance 720 in the different chambers 322 may be released at the same time to form a particular formulation or at different times to prevent certain active ingredients in the prescribed substances 720 from reacting with each other. In this regard, each chamber 322 may contain a different prescribed substance 720 for the intended user.
The actuator 330 may be a micro-pump suitable for delivery of pharmaceutical formulations. The actuator 330 may be activated or triggered by the processor 310 to cause the prescribed substances 720 to flow through the flow channels 350 and exit cannulas 740 and release via the exit valves 340. The actuator 330 may be activated one or more times to release an exact dosage of the prescribed substances 720. The flow channels 350 may be constructed from suitable tubing materials. The exit valves 340 may be any suitable flow control valves, for example, with elastomeric membranes, configured to prevent leakage of the prescribed substances 720 into the user's mouth or backflow of the prescribed substance from the user's mouth into the COPA device 100.
The processor 310 may be any suitable microcontroller or microprocessor configured to perform the functions described herein, including functions such as performing patient identification and verification, performing position sensing and/or pressure detection (e.g., in conjunction with the sensors 112), instructing the actuator 330 to release a dose of the prescribed substance 720, controlling the opening of the exit valves 340, controlling operation of components of the micro-pump unit 300 in accordance with dosage instructions for an intended user, storing dispensing data, etc. The dosage instructions may include at least a dosage amount and timing for dispensing the substance to the intended user. The dosage instructions may be stored in the memory 370.
In operation, the COPA device 100 may be inserted into the mouth of a user. The user may close his or her mouth around the COPA device 100 and bite into the COPA device 100, which may trigger the sensors 112 to perform position and/or pressure measurements. The processor 310 may determine whether the COPA device 100 is correctly positioned within the user's mouth based on the measurements from the sensors 112. In some embodiments, position and/or pressure data of the user's mouth may be recorded and stored in the memory 370 when the COPA device 100 is created. The processor 310 may compare the current position and/or pressure measurements to the original position and/or pressure data to determine whether there is a match between the current user of the COPA device 100 and the intended user of the COPA device 100. The processor 310 may also compare the current position and/or pressure measurements to the original position and/or pressure data to determine whether the COPA device 100 is correctly positioned within the intended user's mouth.
When the user is verified as the intended user and the COPA device 100 is correctly positioned within the intended user's mouth, the processor 310 may send an activation instruction to the actuator 330 and open the exit valves 340 to administer one or more of the prescribed substances 720 stored in the micro-pump unit 300 in accordance with dosage instructions for the intended user. The activation of the actuator 330 and the opening of the exit valves 340 may be based on dosage instructions or prescriptions stored in the memory 370 when the prescribed substance 720 is filled. In this manner, a substance 720 can be dispensed from a reservoir of the micro-pump unit 300 coupled to the COPA device 100 in response to a sensing element determining that the intended user's unique dentition is positioned within the recess of the COPA device 100.
In some embodiments, the COPA device 100 may include one or more status indicators that can provide feedback and/or alerts to the user when the COPA device 100 is in use. The status indicator(s) may include a vibrating component, a sound generation component (e.g., speaker), and/or a visual indicator component. For example, the vibrating component can cause the COPA device 100 to vibrate with different pulsing patterns to indicate the different statuses of the COPA device (e.g., one vibration to indicate proper user authentication and initiation of dispensing, two vibrations to indicate completion of dispensing, patterned or repeated vibrations to indicate an error with the COPA device, etc.). Similarly, the sound generation component can generate various tones and/or patterns to indicate the different statuses of the COPA device. Likewise, the visual indicator component can include one or more LEDs that display different colors and/or patterns to indicate the different statuses of the COPA device. The current status of the COPA device 100 may be determined based on feedback from the processor 310, the sensors 112 or 212 (e.g., correct or incorrect positioning of the COPA device 100), sensors for monitoring the dispensing of the substance (e.g., volume and/or flow sensors), the docking station 400, and/or other sensors or monitoring devices associated with the COPA device 100 and/or the docking station 400 for determining the status of the COPA device 100.
The docking compartment 410 may include a housing sized and shaped to receive at least a portion of the COPA device 100. In some instances, the docking compartment 410 includes a recess sized and shaped to receive the COPA device. In this regard, the identification unit 470 can be utilized to determine the identity of the intended user based on the received COPA device 100. In some instances, the identification unit 470 is configured to determine the identity of the intended user of the COPA device 100 based on a communication with the COPA device. For example, the identification unit 470 may obtain identification information for the COPA device 100 via an RFID tag, bar code, serial number, processing chip identification, information stored in memory of the COPA device, a communication from the COPA device, and/or any other suitable identification technique. In some implementations, the identification unit 470 matches a processor or other identifiable component of the COPA device 100 (e.g., processor 310 of the micro-pump unit 300) to an intended user based on a user identification table, a correlation to a processor or other identifiable component of the docking station 400, and/or combinations thereof.
In some instances, the identification unit 470 is configured to determine the identity of the intended user of the COPA device 100 based on a correlation between one or more structural features of the mouthpiece and one or more structural features of the intended user's dentition. For example, in some implementations at least a portion of the recess can be shaped to mimic the dentition of the intended user such that docking station 400 can determine whether the COPA device 100 is that of the intended user or another COPA. For example, pressure sensors and/or position sensors similar to those used by the COPA device 100 can be utilized by the identification unit 470 to determine whether the received COPA device matches the intended user's dentition structure of the docking station 400. In some instances, the COPA device 100 itself can be used to authenticate by determining that the simulated dentition of the docking compartment matches that of the intended user based on the fit of the simulated dentition with the recess(es) of the COPA device 100. If the COPA device 100 does not match the intended user, then the docking station will alert the user to the error (e.g., via status indicator(s) 440). The subsequent operation of the docking station 400 may be dependent on the identification unit 470 verifying that the received COPA device 100 is that of the intended user.
The transceiver 420 may be configured to transmit and receive data. In this regard, the transceiver may be configured to communicate with the COPA device 100. Further, the transceiver 420 may be configured to communicate with a remote computing device over a communications network using wired/cable and/or wireless protocols. The COPA device 100 may upload prescription administration activities via the transceiver 420 to a COPA management system, as described in U.S. patent application Ser. No. 15/406,043, filed Jan. 13, 2017, which is hereby incorporated by reference in its entirety.
The charging component 430 may include a haptic charging component (e.g., for charging batteries) and may be configured to charge the COPA device 100 while the COPA device 100 is docked at the docking station 400. For example, the operations of the processor, the actuators, and the releasing of the prescribed substances by the COPA device may operate based on electrical power.
The COPA device sensing component 450 may be configured to detect whether the COPA device 100 is docked correctly. For example, the bottom side 104 of the COPA device 100 may further include a docking station sensing component, where alignment between the COPA device 100 and the docking station 400 may be detected via the COPA device sensing component 450 and the docking station sensing component. After detecting alignment, the charging component 430 may begin to charge the COPA device 100. In some instances, the COPA device sensing component 450 and the identification unit 470 are combined into a single component.
The status indicators 440 may include light-emitting diodes (LEDs). The status indicators 440 may be configured to indicate whether the COPA device 100 is positioned correctly within the docking compartment 410 for storage, charging, filling, refilling, emptying, and/or communicating over a communications network. The status indicators 440 may be further configured to indicate the charging status (e.g., power on/off) of the COPA device 100 and/or the transmission and/or reception activities of the transceiver 420.
In some embodiments, the docking station 400 provides a closed loop control system that can sense and detect the presence of the COPA device 100 at various stages of use and/or storage and provide corresponding feedback and/or alerts to the user, caregiver, doctor, and/or pharmacy. For example, the status indicators 440 may be configured to indicate that the COPA device 100 is within proximity of the docking station 400, properly docked within the docking station 400, improperly docked within the docking station 400, charging, fully charged, transferring data, operating properly, operating improperly, and/or other status indications. In some embodiments, the docking station 400 may include a sound generation component (e.g., a speaker) that can generate various tones and/or vibrations to indicate a current status, including the proximity or docking of the COPA device 100, charging activities, and/or communication activities. In some embodiments, the docking station 400 can be in communication with a computing device such as a smartphone, tablet, or computer (e.g., via a transceiver 420 or via a wired connection) and may send the feedback and/or alerts (as well as logs of prescription administration activities obtained from the COPA device 100) to a COPA smartphone or tablet application.
The COPA device 100 may be placed in the docking station 400 between dosages for storage, charging, filling, refilling, emptying, and/or communicating over a communications network as needed (e.g., multiple times per day, daily, nightly, weekly, etc.). The charging and/or power needs of the COPA device 100, including the prescription dispensing unit 120, may be minimal since the operations associated with dispensing the medications may typically span short durations (e.g., 1 minute or less). In addition to charging and communications, the docking station 400 may help prevent the COPA device 100 from being lost, misplaced, or damaged. For example, the docking station 400 may further include locking mechanisms to provide additional protocols for matching the COPA device 100 to an intended user. In an embodiment, the docking station 400 may include a thumbprint, optical (e.g., retina, cornea, etc.), and/or DNA (e.g., saliva) scanning component or any other suitable biological identification recognition mechanism configured to unlock or release the COPA device 100 based on verification against the intended user's associated biological markings.
As shown in
The actuator(s) 466 (e.g., pumps) can be utilized to dispense the prescribed substance 720 from the holding reservoir(s) 462 to the COPA device 100 via the outlet(s) 468. In this regard, the dispensing unit 460, including the actuator(s) 466, may be similar to the micro-pump unit 300 described above. The dispensing unit 460 may have a separate actuator 466 for each holding reservoir 462 or a single actuator 466 may dispense the prescribed substance from multiple holding reservoirs 462. Accordingly, the amount of the prescribed substance 720 dispensed from the holding reservoir(s) 462 to the COPA device 100 via the outlet(s) 468 can be precisely controlled. In some instances, the outlet(s) 468 are configured to engage with the access ports 122 of the COPA device 100 (e.g., via a male/female engagement, snap fit, or other suitable coupling to facilitate transfer of the prescribed substance 720) when the COPA device is docked in the docking station 400.
The dispensing unit 460 can be configured to dispense the prescribed substance 720 based on dosage instructions for the substance for the intended user. The dosage instructions can be stored in memory associated with the dispensing unit 460 and/or the docking station. The dosage instructions can include dosage amount(s), dosage timing(s), and/or other parameters. The dispensing unit 460 can also be configured to store in memory dispensing data associated with the prescribed substance 720 being dispensed into the reservoir 320 of the COPA device 100. The dispensing data can include at least a dispensed amount, a dispensed time, a dispensed location, and/or other parameters. The dispensing unit can also be configured to dispense the prescribed substance 720 into the reservoir 320 of the COPA device 100 based on an amount of the substance in the reservoir of the mouthpiece. In this regard, the dispensing unit can configured to receive a communication indicating the amount of the substance in the reservoir of the COPA device from the COPA device itself or from a central unit in communication with the dispensing unit 460 and/or docking station 400.
At a high level, the doctor 910 may prescribe a medication to a patient and the pharmacy 920 may create the mouthpiece for the patient and fill the mouthpiece and/or docking station 400 according to the prescription(s) provided by the doctor 910. The pharmacy 920 may program the micro-pump unit of the mouthpiece and/or the docking station 400 to deliver an exact dosage of the prescribed medication and/or a dosage intake time. In this regard, dosage instructions for the patient may be stored in memory of the micro-pump unit and/or the docking station 400. The patient may insert the mouthpiece into the patient's mouth and the micro-pump unit will, upon verification that the user is the intended recipient, dispense the prescribed medication as programmed. The patient may dock the mouthpiece at the docking station 400 when the mouthpiece is not in use. The docking station 400 may charge the mouthpiece, communicate with the doctor 910 and/or the pharmacy 920 via wireless and/or wired connections, and/or fill, refill, and/or empty the mouthpiece in accordance with the most current treatment plan. The doctor 910 and/or the pharmacy 920 may monitor and retrieve information associated with the dispensing of the prescribed medication from the docking station 400. The doctor 910 may provide instructions to adjust the dosage instructions based on the monitoring and/or the retrieval information, and/or based on evaluations of the patient's progress. The pharmacy 920 may send instructions to the docking station 400 to adjust the dosage instructions stored in the memory of the micro-pump unit and/or the docking station 400 based on the order from the doctor 910. For example, when the mouthpiece is docked at the docking station 400, the dosage instructions stored in the memory can be updated or re-programmed accordingly. Alternatively, the dosage instructions stored in the memory of the micro-pump unit and/or the docking station 400 can be updated or re-programmed at the pharmacy 920. Similarly, the doctor 910 may prescribe new medication based on the monitoring and/or the retrieval information, and/or based on evaluations of the patient's progress. The pharmacy 920 may refill the micro-pump unit 300 and/or the docking station 400 accordingly.
The patient/authorized caregiver portal 930 may be stored on a computer server or in cloud storage on the network 940. The management system 950 may be hosted on the network 940. The management system 950 may include a master database that stores information associated with the patient and all COPA activities. For example, the management system 950 may allow doctors (e.g., the doctor 910), assembly or fulfillment technicians, pharmacists (e.g., the pharmacy 920), and any healthcare personnel that partake in the COPA process to access at least some portions of the master database, for example, based on logins. In an embodiment, different personnel may have different login profiles and the accesses to the master database may be based on login profiles. In some embodiments, the patient/authorized caregiver portal 930 may be hosted on the management system 950 and may have certain accesses to the master database. The patient information may include an identification of the patient, health history, prescription history, identification of the processor 310 within the COPA device 100, identification of the docking station 400 at which the COPA device 100 is charged, etc. The patient's identification may include a social security number (SSN) of the patient or other unique identifier. The prescription history may include identifications of doctors (e.g., the doctor 910) who prescribed medications to the patient, identifications of pharmacies (e.g., the pharmacy 920) at which the prescribed medications were filled or refilled, identifications of the prescribed medications, and an identification of the processor 310 within the micro-pump unit 300 where the medications were filled. The prescription history may also be stored and managed by the management system 950. The physicians' identifications may include national provider identifiers (NPIs) of the physicians. The NPIS are unique identification number for Health Insurance Portability and Accountability Act (HIPPA) covered physicians. The pharmacies' identifications may include an impression technician identifier (ID), an assembly technician ID, and a registered pharmacy ID. The impression technician ID identifies the technician who created the COPA device 100 for the patient. The assembly technician ID identifies the technician who assembled or filled the prescribed medication into the micro-pump unit 300 of the COPA device 100. The pharmacy ID identifies the pharmacy at which the prescribed medication was filled. The prescribed medications' identifications may include dosage IDs that identify each prescribed substance or formulation filled into the micro-pump unit 300 of the COPA device 100.
In an embodiment, the doctor 910 may examine a patient and determine whether alternative therapies may be helpful to the patient. When the doctor 910 determines that the patient is in need of a particular medication, for example, according to guidelines for drug formulations based on COPA dosing options, the doctor may order a prescription for the patient. The doctor 910 may electronically transmit the prescription to the pharmacy 920 via the network 940, for example, according to HIPPA standards of protection for data and electronic medical record (EMR) formats.
At a COPA fabricator, an impression technician may take an impression of the intended patient's mouth and teeth to create a mold for the COPA device 100, for example, according to COPA guidelines and instructions. The mold may include a sealed sleeve similar to the sealed sleeve 124. For example, the impression technician may use a dental tray filled with bio friendly polymers to create an imprint of the patient's dentition. COPA approved dentists, hygienists, and/or other trained professions (e.g., a COPA device assembly technician) may complete the creation of the mold for the COPA device 100.
An assembly technician may prepare a pre-packaged micro-pump unit 300. Each micro-pump unit 300 may be identified based on an ID of the processor 310 embedded within the micro-pump unit. The assembly technician may record the ID of the micro-pump unit 300 in the management system 950. For example, the assembly technician may enter the ID into the management system 950, query a COPA device ID database of the management system 950 that stores and tracks IDs of COPA devices (e.g., the COPA device 100), and create a new record for the COPA device 100 created for the patient. The assembly technician may activate the processor 310 within the micro-pump unit 300, for example, wirelessly. The activation may include programming the processor 310 according to the order received from the doctor 910. The programming may include the dosage instructions for the patient (e.g., a dosage amount and the dosage timing for each prescribed medication). As described above, different chambers 322 may be filled with different formulations. Thus, the programming may include a release sequence, specific release times, and/or release durations for the different formulations, and/or intervals between releases. For example, some formulations may be programmed for instant release (IR) and some formulations may be programmed for extended release (ER).
After activating the micro-pump unit 300 or the processor 310, the assembly technician may place the activated micro-pump unit 300 into the top center of the mold where the sealed sleeve is positioned. The micro-pump unit 300 may be positioned such that the access cannulas 730 extend outside the sealed sleeve through the access ports 122 and the exit cannulas 740 extend through the base of the mold. The assembly technician may place a filament or a mesh of sensors 112 into the recess 110 of the COPA device 100. The assembly technician may attach a hose from an air compressor to the access ports 122 on top of the mold such that pressurized air may be pumped through the access cannulas 730 into the micro-pump unit 300 to ensure that the flow channels 350 are not compressed during the filling of the mold. The assembly technician may pump a liquid polymer into the mold and allow the liquid polymer to set. After the liquid polymer is set, the COPA device 100 is complete.
Upon completion of the COPA device 100, the COPA device 100 can be transferred to the pharmacy 920. At the pharmacy 920, a pharmacy staff (e.g., a COPA fulfillment technician) may place the COPA device 100 on a pedestal or other structure configured to allow access to the micro-pump unit 300 for filling. Similarly, the pharmacy staff may access the docking station 400 for filling. The pedestal may be covered by a sterile sleeve each time prior to placing a COPA device on the pedestal. The pharmacy staff may retrieve a record of the COPA device 100 and/or docking station 400 based on the ID of the processor within the COPA device 100 and/or docking station 400, for example, from the COPA management system 950 via the network 940. The pharmacy staff may procure the medications (e.g., vials, pouches, bottles, etc.) from a drug manufacturer based on the dosage specified in the order received from the doctor 910. The pharmacy staff may update the record for the COPA device 100 and/or docking station 400. The pharmacy staff may activate or open control valves at the access ports of the COPA device and/or docking station 400 to inject or deposit the formulated prescription (e.g., the prescribed substance 720) into one or more reservoir(s) of the micro-pump unit 300 of the COPA device 100 and/or one or more reservoir(s) of the docking station 400. After completing the filling, the pharmacy staff may close the control valves of the micro-pump unit 300 and/or the docking station 400. The pharmacy staff may repeat the same process for filling other chambers and/or reservoirs of the micro-pump unit 300 and/or the docking station 400. Subsequently, the releasing of the formulated prescription by the COPA device 100 can be based on matching of the intended recipient's dentition and the COPA device 100 as described above. Similarly, the filling, refilling, and/or emptying of the COPA device 100 by the dispensing unit 460 of the docking station 400 can be based on matching of the COPA device 100 to the intended user (e.g., using identification unit 470) as described above. It should be noted that in some embodiments, the pharmacy 920 and the COPA fabricator may be the same entity.
The initial ID (e.g., of the processor 310) created for the COPA device 100 and/or the docking station 400 can be a permanent ID for the COPA device 100 and/or the docking station 400. Information associated with the filled prescription may be associated with the ID of the COPA device 100 and/or the docking station 400 and recorded in the management system 950 and/or an internal tracking system of the pharmacy 920. Thus, the COPA device 100 and/or the docking station 400 are fully traceable through the creation and preparation path. In addition, the mold used to craft the COPA device 100 may be assigned with a mold ID and may be stored in the management system 950 in association with the ID of the processor 310. Protocols for the use of the stored molds may be documented and records of subsequent mouthpieces may be stored in association in the management system 950. As such, misuse or fraud may be traced via the management system 950. An initial ID created for the docking station 400 can be used in a similar manner to track usage in an effort to minimize misuse and/or fraud.
The pharmacy staff may pair the COPA device 100 with the docking station 400. The pharmacy staff may record an ID of the docking station 400 in association with the COPA device 100 in the management system 950. The transceiver 420 of the docking station 400 may be recorded and registered in the management system 950 for remote access to the processor 310 embedded in the COPA device 100. For example, a pharmacy staff may adjust the dosage of the filled prescribed medication based on the instructions or an order of the prescribing doctor 910 by accessing the processor 310 via the transceiver 420 without the patient returning the mouthpiece to the pharmacy 920 prior to depletion of the active ingredient(s). The adjustment may allow for a limited number of revisions, for example, to the dosing amount per release, the timing of the release, suspension of one or more of the chambers 322.
The patient may pick up the COPA device 100 and/or the docking station 400 from the pharmacy 920 and the pharmacy staff may provide instructions of usage to the patient. The patient may insert the COPA device 100 into the patient's mouth and close the mouth to bite on the COPA device 100 so that the prescription dispensing unit 120 or the micro-pump unit 300 may release the prescribed medication for ingestion. The patient may clean the COPA device 100 and dock the COPA device 100 at the docking station 400 after use.
The patient and/or the authorized care giver may have access to an online COPA account, for example, hosted on the management system 950 via the network 940. The transceiver 420 may detect and transmit data such as activities recorded by the mouthpiece (e.g., dispensing dosages and timings for each medication) to the management system 950. The patient may view records of medications loaded into each chamber 322 of the COPA device 100 and/or the reservoir(s) of the docking station 400. The patient may view records of the administration path of medications filled in the COPA device 100 and/or the docking station 400 including the initial prescription and any subsequent revisions. The patient may view records of anticipated depletion timeline for the patient to pick up a second pre-filled COPA device and/or the docking station 400 and drop off the depleted COPA device and/or the docking station 400 if the treatment is a recurring treatment.
In an embodiment, the refill process for the COPA device 100 and/or the docking station 400 may use similar policies as today's drug refill policies. The COPA device 100 and/or the docking station 400 may be used in prolonged treatment plans. A prescribing doctor 910 may adjust and revise the prescription based on the treatment results observed from the patient. The doctor 910 may electronically transfer the revised prescription to the pharmacy 920. The pharmacy staff or the fulfillment technician may send revised instructions to the processor 310 wirelessly through the transceiver 420 of the docking station 400. The management system 950 may house a full record of all revisions. When the intended recipient has depleted the substance(s) in the COPA device 100 as planned, or as revised, the COPA device 100 may be returned to the docking station 400 and/or the pharmacy 920 for refills, for example, as directed by the prescribing doctor 910. The docking station 400 or pharmacy staff may remove any unwanted substance(s) remaining in the device. For example, the pharmacy staff may flush saline solution into the COPA device 100 through the access ports 122 into the sealed prescription dispensing unit 120 and out the exit valves 222. The docking station 400 may use a similar emptying approach or, in some instances, the docking station may remove any remaining substance(s) to a discard reservoir of the docking station 400 that can be subsequently emptied and discarded in a safe, appropriate manner by the pharmacy. After emptying any unwanted substance(s) from the COPA device 100, the docking station 400 or pharmacy staff may refill the COPA device 100 based on the order received from the doctor 910 and may update the record in the management system 950. For example, if a prescription is written for three refills, the record would indicate three dosage IDs in association with the ID of the processor 310 of the COPA device 100 and previous dosage IDs. By recording all information associated with the COPA device 100 and/or the docking station 400, the patient and the dosage information in the management system 950 may be retrieved at any time, including when the patient changes providers or pharmacies during a treatment plan.
In an embodiment, when the COPA device 100 and/or docking station 400 are no longer needed, for example, at the end of a treatment plan or change of treatment plan, the COPA device 100 and/or the docking station 400 may be deactivated and the management system 950 may be updated to indicate the deactivation. In some embodiments, when deactivation time of the COPA device 100 and/or the docking station 400 is within a certain time limit, for example, X number of months, an assembly technician may reuse the original impression to build a new COPA device 100 and/or reauthorize use of the docking station 400. The ID of the processor 310 within the new COPA device 100 may be stored in the management system 950 in association with the old ID of the old COPA device 100. In an embodiment, when a COPA device 100 needs to be recast due to actual change in the dentition of a recipient, the creation and preparation processes described above may be repeated. Information associated with the new mold may be stored on the management system 950 in association with the patient and the prescribed medications. By tracking all COPA devices 100 and/or docking stations 400 associated with a particular patient or a particular prescription, it will be rare for an unintended user to gain access to the prescribed medications or for an intended user to provide false information for misuse of a prescribed substance.
The following table lists reference numerals and corresponding reference names:
Persons skilled in the art will recognize that the apparatus, systems, and methods described above can be modified in various ways. Accordingly, persons of ordinary skill in the art will appreciate that the embodiments encompassed by the present disclosure are not limited to the particular exemplary embodiments described above. In that regard, although illustrative embodiments have been shown and described, a wide range of modification, change, and substitution is contemplated in the foregoing disclosure. It is understood that such variations may be made to the foregoing without departing from the scope of the present disclosure. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the present disclosure.
The present application claims priority to and the benefit of the U.S. Provisional Patent Application No. 62/516,307, filed Jun. 7, 2017, which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4116195 | James | Sep 1978 | A |
| 4237884 | Erickson et al. | Dec 1980 | A |
| 4353365 | Hallworth et al. | Oct 1982 | A |
| 4428502 | Veltri | Jan 1984 | A |
| 4474308 | Bergeron | Oct 1984 | A |
| 4717042 | McLaughlin | Jan 1988 | A |
| 4784288 | Jennings | Nov 1988 | A |
| 5159581 | Agans | Oct 1992 | A |
| 5583831 | Churchill et al. | Dec 1996 | A |
| 5791515 | Khan et al. | Aug 1998 | A |
| 5852590 | de la Huerga | Dec 1998 | A |
| H1782 | Wicks et al. | Feb 1999 | H |
| 5881721 | Bunce et al. | Mar 1999 | A |
| 5947329 | Bailey | Sep 1999 | A |
| 5960085 | de la Huerga | Sep 1999 | A |
| 5971594 | Sahai et al. | Oct 1999 | A |
| 5990782 | Lee | Nov 1999 | A |
| 6018289 | Sekura et al. | Jan 2000 | A |
| 6032155 | de la Huerga | Feb 2000 | A |
| 6082363 | Washburn | Jul 2000 | A |
| 6089864 | Buckner et al. | Jul 2000 | A |
| 6112942 | Deacon | Sep 2000 | A |
| 6119684 | Nohl et al. | Sep 2000 | A |
| 6145697 | Gudish | Nov 2000 | A |
| 6163736 | Halfacre | Dec 2000 | A |
| 6198383 | Sekura et al. | Mar 2001 | B1 |
| 6259654 | de la Huerga | Jul 2001 | B1 |
| 6304797 | Shusterman | Oct 2001 | B1 |
| 6332100 | Sahai et al. | Dec 2001 | B1 |
| 6335907 | Momich et al. | Jan 2002 | B1 |
| 6408330 | DeLaHuerga | Jun 2002 | B1 |
| 6431399 | Gabel et al. | Aug 2002 | B2 |
| 6529446 | de la Huerga | Mar 2003 | B1 |
| 6604650 | Sagar | Aug 2003 | B2 |
| 6611733 | De La Huerga | Aug 2003 | B1 |
| 6702146 | Varis | Mar 2004 | B2 |
| 6779024 | DeLaHuerga | Aug 2004 | B2 |
| 6834775 | Collins | Dec 2004 | B1 |
| 6958691 | Anderson et al. | Oct 2005 | B1 |
| 6988634 | Varis | Jan 2006 | B2 |
| 7006894 | de la Huerga | Feb 2006 | B2 |
| 7042807 | Breen | May 2006 | B1 |
| 7048141 | Abdulhay et al. | May 2006 | B2 |
| 7061831 | De La Huerga | Jun 2006 | B2 |
| 7072738 | Bonney et al. | Jul 2006 | B2 |
| 7073685 | Giraud et al. | Jul 2006 | B1 |
| 7100797 | Kahn et al. | Sep 2006 | B2 |
| 7104417 | Hilliard | Sep 2006 | B2 |
| 7128240 | Oesch | Oct 2006 | B1 |
| 7147127 | Lepke et al. | Dec 2006 | B2 |
| 7178688 | Naufel et al. | Feb 2007 | B2 |
| 7182955 | Hart et al. | Feb 2007 | B2 |
| 7213721 | Abdulhay et al. | May 2007 | B2 |
| 7216802 | De La Huerga | May 2007 | B1 |
| 7269476 | Ratnakar | Sep 2007 | B2 |
| 7295890 | Jean-Pierre | Nov 2007 | B2 |
| 7302311 | Varis | Nov 2007 | B2 |
| 7359765 | Varvarelis et al. | Apr 2008 | B2 |
| 7366675 | Walker et al. | Apr 2008 | B1 |
| 7392918 | Holloway et al. | Jul 2008 | B2 |
| 7404500 | Marteau et al. | Jul 2008 | B2 |
| 7648093 | Kruger | Jan 2010 | B2 |
| 7711449 | Abdulhay et al. | May 2010 | B2 |
| 7715277 | de la Huerga | May 2010 | B2 |
| 7719927 | Robinson et al. | May 2010 | B1 |
| 7801745 | Walker et al. | Sep 2010 | B2 |
| 7810673 | Lancesseur et al. | Oct 2010 | B2 |
| 7831336 | Gumpert | Nov 2010 | B2 |
| 7844361 | Jean-Pierre | Nov 2010 | B2 |
| 7885725 | Dunn | Feb 2011 | B2 |
| 7941534 | de la Huerga | May 2011 | B2 |
| 7978564 | De La Huerga | Jul 2011 | B2 |
| 7988016 | Klein et al. | Aug 2011 | B2 |
| 7996106 | Ervin | Aug 2011 | B2 |
| 8019471 | Bogash et al. | Sep 2011 | B2 |
| 8028856 | Erdelyi et al. | Oct 2011 | B2 |
| 8029538 | Burroughs et al. | Oct 2011 | B2 |
| 8033422 | Estrada | Oct 2011 | B2 |
| 8055509 | Walker et al. | Nov 2011 | B1 |
| 8062248 | Kindel | Nov 2011 | B2 |
| 8069056 | Walker et al. | Nov 2011 | B2 |
| 8135497 | Joslyn | Mar 2012 | B2 |
| 8195330 | Coe | Jun 2012 | B2 |
| 8212677 | Ferguson | Jul 2012 | B2 |
| 8226978 | Palmer et al. | Jul 2012 | B2 |
| 8269613 | Lazar | Sep 2012 | B2 |
| 8279076 | Johnson | Oct 2012 | B2 |
| 8284068 | Johnson | Oct 2012 | B2 |
| 8319613 | Lazar | Nov 2012 | B2 |
| 8326455 | Dunn | Dec 2012 | B2 |
| 8357114 | Poutiatine et al. | Jan 2013 | B2 |
| 8391104 | de la Huerga | Mar 2013 | B2 |
| 8392020 | Terzini | Mar 2013 | B2 |
| 8417378 | Joslyn | Apr 2013 | B2 |
| 8483872 | Ratnakar | Jul 2013 | B2 |
| 8499966 | Palmer et al. | Aug 2013 | B2 |
| 8502671 | Marcovici | Aug 2013 | B2 |
| 8502692 | Johnson | Aug 2013 | B2 |
| 8511478 | Terzini | Aug 2013 | B2 |
| 8548623 | Poutiatine et al. | Oct 2013 | B2 |
| 8552868 | Ferguson | Oct 2013 | B1 |
| 8574189 | Poutiatine et al. | Nov 2013 | B2 |
| 8600548 | Bossi et al. | Dec 2013 | B2 |
| 8636172 | Dunn | Jan 2014 | B2 |
| 8666539 | Ervin | Mar 2014 | B2 |
| 8666543 | MacVittie et al. | Mar 2014 | B2 |
| 8669863 | Alhuwaishel | Mar 2014 | B2 |
| 8670865 | Coe | Mar 2014 | B2 |
| 8725291 | Czaja et al. | May 2014 | B2 |
| 8727180 | Zonana et al. | May 2014 | B2 |
| 8734061 | Terzini | May 2014 | B2 |
| 8753308 | Palmer et al. | Jun 2014 | B2 |
| 8778393 | Palmer et al. | Jul 2014 | B2 |
| 8807131 | Tunnell et al. | Aug 2014 | B1 |
| 8821454 | Kriesel et al. | Sep 2014 | B2 |
| 8854225 | Johnson | Oct 2014 | B2 |
| 8874260 | Saltsov | Oct 2014 | B2 |
| 8905964 | Poutiatine et al. | Dec 2014 | B2 |
| 8922367 | Denny et al. | Dec 2014 | B2 |
| 8973338 | Terzini | Mar 2015 | B2 |
| 8976036 | Johnson | Mar 2015 | B2 |
| 8985388 | Ratnakar | Mar 2015 | B2 |
| 9010584 | Law et al. | Apr 2015 | B2 |
| 9014847 | Dunn | Apr 2015 | B2 |
| 9019097 | Choi et al. | Apr 2015 | B2 |
| 9037291 | Terzini | May 2015 | B2 |
| 9043015 | Ratnakar | May 2015 | B2 |
| 9066847 | Poutiatine et al. | Jun 2015 | B2 |
| 9066849 | Fung et al. | Jun 2015 | B2 |
| 9155682 | Boyd | Oct 2015 | B2 |
| 9161885 | Zhou | Oct 2015 | B1 |
| 9211559 | Law et al. | Dec 2015 | B2 |
| 9218458 | Baarman et al. | Dec 2015 | B2 |
| 9235689 | Ervin | Jan 2016 | B2 |
| 9283363 | Scorzelli et al. | Mar 2016 | B1 |
| 9289583 | Palmer et al. | Mar 2016 | B2 |
| 9346068 | Knight et al. | May 2016 | B2 |
| 9361772 | Johnson | Jun 2016 | B2 |
| 9381139 | Fung et al. | Jul 2016 | B2 |
| 9414899 | Altounian | Aug 2016 | B2 |
| 9418207 | Patton et al. | Aug 2016 | B1 |
| 9436298 | Draper et al. | Sep 2016 | B2 |
| 9566402 | Djupesland | Feb 2017 | B2 |
| 9636195 | Wolpo | May 2017 | B2 |
| 9731103 | Rouse et al. | Aug 2017 | B1 |
| 9795296 | Imran | Oct 2017 | B2 |
| 9839500 | Flyash et al. | Dec 2017 | B2 |
| 9968777 | Demarest et al. | May 2018 | B1 |
| 20010009398 | Sekura et al. | Jul 2001 | A1 |
| 20010022758 | Howard | Sep 2001 | A1 |
| 20030174554 | Dunstone et al. | Sep 2003 | A1 |
| 20040008123 | Carrender et al. | Jan 2004 | A1 |
| 20040117062 | Bonney et al. | Jun 2004 | A1 |
| 20040158349 | Bonney et al. | Aug 2004 | A1 |
| 20050230409 | Von Schuckmann | Oct 2005 | A1 |
| 20060138162 | Anderson et al. | Jun 2006 | A1 |
| 20060184271 | Loveless | Aug 2006 | A1 |
| 20060213921 | Abdulhay et al. | Sep 2006 | A1 |
| 20060218015 | Walker et al. | Sep 2006 | A1 |
| 20060282010 | Martin | Dec 2006 | A1 |
| 20070075842 | Russell et al. | Apr 2007 | A1 |
| 20070093932 | Abdulhay et al. | Apr 2007 | A1 |
| 20070095851 | Anderson et al. | May 2007 | A1 |
| 20070135790 | Auerbach | Jun 2007 | A1 |
| 20070138195 | Anderson et al. | Jun 2007 | A1 |
| 20070145065 | Anderson et al. | Jun 2007 | A1 |
| 20070170199 | York | Jul 2007 | A1 |
| 20070228065 | Anderson et al. | Oct 2007 | A1 |
| 20070261985 | Allen | Nov 2007 | A1 |
| 20070271001 | Ratnakar | Nov 2007 | A1 |
| 20080017658 | Wright | Jan 2008 | A1 |
| 20080027291 | Williams-Hartman | Jan 2008 | A1 |
| 20080027579 | van der Hoop | Jan 2008 | A1 |
| 20080054008 | Wright | Mar 2008 | A1 |
| 20080059228 | Bossi et al. | Mar 2008 | A1 |
| 20080140250 | Dave | Jun 2008 | A1 |
| 20080251530 | Holloway et al. | Oct 2008 | A1 |
| 20080283542 | Lanka et al. | Nov 2008 | A1 |
| 20090127157 | Costa et al. | May 2009 | A1 |
| 20090208898 | Kaplan | Aug 2009 | A1 |
| 20090210032 | Beiski et al. | Aug 2009 | A1 |
| 20090223994 | Getz | Sep 2009 | A1 |
| 20090277461 | Gallagher, Jr. | Nov 2009 | A1 |
| 20090277921 | Angelucci et al. | Nov 2009 | A1 |
| 20100006589 | Klein | Jan 2010 | A1 |
| 20100096399 | Ratnakar | Apr 2010 | A1 |
| 20100100237 | Ratnakar | Apr 2010 | A1 |
| 20100185456 | Kansal | Jul 2010 | A1 |
| 20100318218 | Muncy, Jr. et al. | Dec 2010 | A1 |
| 20100332023 | Tripathi et al. | Dec 2010 | A1 |
| 20110011883 | Nakkouri | Jan 2011 | A1 |
| 20110027746 | McDonough | Feb 2011 | A1 |
| 20110060455 | Bogash et al. | Mar 2011 | A1 |
| 20110060457 | De Vrught et al. | Mar 2011 | A1 |
| 20110142554 | Terzini | Jun 2011 | A1 |
| 20110146835 | Terzini | Jun 2011 | A1 |
| 20110160901 | Abrams, Jr. et al. | Jun 2011 | A1 |
| 20110202174 | Bogash et al. | Aug 2011 | A1 |
| 20110259910 | Knudsen | Oct 2011 | A1 |
| 20110295416 | Aquilonius et al. | Dec 2011 | A1 |
| 20110307592 | de la Huerga | Dec 2011 | A1 |
| 20120055948 | Leifeld et al. | Mar 2012 | A1 |
| 20120160716 | Chan et al. | Jun 2012 | A1 |
| 20120165975 | Yi et al. | Jun 2012 | A1 |
| 20130025607 | Altounian | Jan 2013 | A1 |
| 20130088328 | DiMartino et al. | Apr 2013 | A1 |
| 20130116818 | Hamilton | May 2013 | A1 |
| 20130120115 | Valls Chaparro et al. | May 2013 | A1 |
| 20130165828 | Sullivan | Jun 2013 | A1 |
| 20130168405 | Yuyama et al. | Jul 2013 | A1 |
| 20130211270 | St. Laurent et al. | Aug 2013 | A1 |
| 20130253286 | Fridman | Sep 2013 | A1 |
| 20130256331 | Giraud et al. | Oct 2013 | A1 |
| 20130280671 | Brawn et al. | Oct 2013 | A1 |
| 20130304255 | Ratnakar | Nov 2013 | A1 |
| 20130306191 | Metzmaker | Nov 2013 | A1 |
| 20130345859 | Omura et al. | Dec 2013 | A1 |
| 20140031975 | Poutiatine et al. | Jan 2014 | A1 |
| 20140046676 | Kibler et al. | Feb 2014 | A1 |
| 20140072932 | Brawn | Mar 2014 | A1 |
| 20140074283 | Blackburn | Mar 2014 | A1 |
| 20140114472 | Bossi et al. | Apr 2014 | A1 |
| 20140195043 | Ervin | Jul 2014 | A1 |
| 20140203021 | Zill | Jul 2014 | A1 |
| 20140207278 | Czaja et al. | Jul 2014 | A1 |
| 20140263423 | Akdogan et al. | Sep 2014 | A1 |
| 20140263425 | Akdogan et al. | Sep 2014 | A1 |
| 20140267719 | Akdogan et al. | Sep 2014 | A1 |
| 20140277705 | Czaja et al. | Sep 2014 | A1 |
| 20140277707 | Akdogan et al. | Sep 2014 | A1 |
| 20140277710 | Akdogan et al. | Sep 2014 | A1 |
| 20140278508 | Akdogan et al. | Sep 2014 | A1 |
| 20140278510 | McLean et al. | Sep 2014 | A1 |
| 20140303989 | Ferguson | Oct 2014 | A1 |
| 20140305963 | Zonana et al. | Oct 2014 | A1 |
| 20140316799 | Cosgrove et al. | Oct 2014 | A1 |
| 20140324216 | Beg et al. | Oct 2014 | A1 |
| 20140326744 | Ratnakar | Nov 2014 | A1 |
| 20140339248 | Reddy et al. | Nov 2014 | A1 |
| 20140339249 | Reddy et al. | Nov 2014 | A1 |
| 20140346184 | Bae et al. | Nov 2014 | A1 |
| 20140346186 | Reddy et al. | Nov 2014 | A1 |
| 20140350720 | Lehmann et al. | Nov 2014 | A1 |
| 20140371904 | Parviainen | Dec 2014 | A1 |
| 20150012131 | Saltsov | Jan 2015 | A1 |
| 20150021349 | Sanders | Jan 2015 | A1 |
| 20150038898 | Palmer et al. | Feb 2015 | A1 |
| 20150048101 | Reddy et al. | Feb 2015 | A1 |
| 20150072300 | Wolpo | Mar 2015 | A1 |
| 20150072306 | Barnard | Mar 2015 | A1 |
| 20150079533 | Lowe | Mar 2015 | A1 |
| 20150174348 | Tunnell et al. | Jun 2015 | A1 |
| 20150174349 | Tunnell et al. | Jun 2015 | A1 |
| 20150191268 | Paz | Jul 2015 | A1 |
| 20150191294 | Paz | Jul 2015 | A1 |
| 20150221086 | Bertram | Aug 2015 | A1 |
| 20150232256 | Hoover et al. | Aug 2015 | A1 |
| 20150257980 | Fung et al. | Sep 2015 | A1 |
| 20150259110 | Blackburn | Sep 2015 | A1 |
| 20150266654 | Baarman et al. | Sep 2015 | A1 |
| 20150272825 | Lim et al. | Oct 2015 | A1 |
| 20150273165 | Hadash | Oct 2015 | A1 |
| 20150291344 | MacVittie et al. | Oct 2015 | A1 |
| 20150305671 | Yong-Kyu et al. | Oct 2015 | A1 |
| 20150317455 | Lehmann et al. | Nov 2015 | A1 |
| 20150320643 | Zhou | Nov 2015 | A1 |
| 20150328084 | Cash | Nov 2015 | A1 |
| 20150342830 | Bujalski et al. | Dec 2015 | A1 |
| 20150347713 | Seeger | Dec 2015 | A1 |
| 20150359667 | Brue | Dec 2015 | A1 |
| 20160012249 | Keppler | Jan 2016 | A1 |
| 20160016720 | Paz | Jan 2016 | A2 |
| 20160022542 | Lehmann et al. | Jan 2016 | A1 |
| 20160029962 | Hyde | Feb 2016 | A1 |
| 20160037916 | Hermann | Feb 2016 | A1 |
| 20160038377 | Tegborg et al. | Feb 2016 | A1 |
| 20160042150 | Moloughney | Feb 2016 | A1 |
| 20160066776 | Weiss et al. | Mar 2016 | A1 |
| 20160096014 | Ajiki | Apr 2016 | A1 |
| 20160107820 | MacVittie et al. | Apr 2016 | A1 |
| 20160113747 | Almutairi | Apr 2016 | A1 |
| 20160117480 | Ervin | Apr 2016 | A1 |
| 20160128906 | Baarman et al. | May 2016 | A1 |
| 20160132660 | Barajas et al. | May 2016 | A1 |
| 20160136056 | Lapham | May 2016 | A1 |
| 20160145031 | Reinhold et al. | May 2016 | A1 |
| 20160158107 | Dvorak et al. | Jun 2016 | A1 |
| 20160166766 | Schuster et al. | Jun 2016 | A1 |
| 20160180693 | Johnson | Jun 2016 | A1 |
| 20160203292 | Kamen et al. | Jul 2016 | A1 |
| 20160211693 | Stevens et al. | Jul 2016 | A1 |
| 20160213606 | Palmer et al. | Jul 2016 | A1 |
| 20160228333 | Bukstein et al. | Aug 2016 | A1 |
| 20160278899 | Heller | Sep 2016 | A1 |
| 20160366946 | Murison | Dec 2016 | A1 |
| 20170027675 | Nahshon | Feb 2017 | A1 |
| 20170028178 | Skoda | Feb 2017 | A1 |
| 20170265978 | Borotto et al. | Sep 2017 | A1 |
| 20170312181 | Davis et al. | Nov 2017 | A1 |
| 20170333649 | Djupesland | Nov 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 102014114601 | Apr 2016 | DE |
| 101221415 | Jan 2013 | KR |
| WO2004062717 | Jul 2004 | WO |
| WO2011151056 | Dec 2011 | WO |
| WO2015150240 | Oct 2015 | WO |
| WO2015172962 | Nov 2015 | WO |
| WO2015181693 | Dec 2015 | WO |
| WO2015196293 | Dec 2015 | WO |
| WO2015196336 | Dec 2015 | WO |
| WO2016064592 | Apr 2016 | WO |
| WO2016064688 | Apr 2016 | WO |
| WO2016064786 | Apr 2016 | WO |
| WO2016064906 | Apr 2016 | WO |
| WO2016064908 | Apr 2016 | WO |
| WO2016116591 | Jul 2016 | WO |
| WO2017064709 | Apr 2017 | WO |
| 2017218947 | Dec 2017 | WO |
| Entry |
|---|
| International Search Report issued in PCT/US2018/013440 dated Mar. 9, 2018. |
| Written Opinion issued in PCT/US2018/013440 dated Mar. 9, 2018. |
| International Search Report issued in PCT/US2019/022287 dated Jul. 16, 2019. |
| Written Opinion issued in PCT/US2019/022287 dated Jul. 16, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20180353388 A1 | Dec 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62516307 | Jun 2017 | US |
