CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Serial No. 61/471,380, filed April 4, 201 1, titled " Systems and Methods for Compliance Based Distribution of Regulated Products," and to U.S. Patent Application Serial No. 61/471,398, filed April 4, 201 1, titled " Systems and Methods for Regulated Product Dispensing Payments," both of which are incorporated herein by reference.

FIELD

This invention relates to a dispensing machine, more particularly relates to the dispensing of regulated products from a dispensing machine, and most particularly relates to payment for regulated products dispensed by a dispensing machine in compliance with regulations for the dispensing thereof.

BACKGROUND

A significant amount of money is spent each year on regulated products such as prescription medication. A large amount of the money spent is actually spent by parties other than the intended users of the regulated products (the patients, in the case of prescription medication); insurance companies and employers spend vast amounts of money paying for regulated products, or reimbursing their customers or employees for their purchases.

Although regulated products are important and money spent is vital to maintain a healthy society, much of the money spent on regulated products turns out to be wasteful - without any knowledge of which amounts, or how much, actually is wasted.

In essence, there is a disconnect between the payment for regulated products, and the compliant use of, and effectiveness of, those regulated products. As long as the regulated product consumer becomes healthier, in their opinion at least, they do not tend to worry whether they have wasted regulated products or used less-than-optimal regulated products. There is no incentive for them to track either factor accurately. For those footing the bill however, there is tremendous incentive.

As the population ages, and as people's time becomes increasingly important, healthcare and other regulated product industries, are likely to experience strain in meeting society's needs. In particular, regulated products, such as prescription medication, need to be accessed by many people that may be immobile or remotely located. While it is becoming increasingly simple to reach immobile and remotely located people in some instances (such as the Internet being accessible by satellite virtually anywhere), regulated products may only be accessed or dispensed to particular people meeting particular requirements. This becomes even more difficult when the regulated products are tangible items that cannot be electronically transported.

In some such instances society has developed specialized ways to maintain control of dispensing while reaching immobile and remote people. However, such approaches tend to be very expensive and require significant capital investments.

Given the foregoing problems, in would be an advance in the relevant arts to provide solutions to these problems.

SUMMARY

In one implementation, there is provided a method for compliance-based distribution of a regulated product comprising receiving a request from a regulated product consumer to dispense a regulated product to the regulated product consumer, accessing a compliance/efficacy data source, determining, from the compliance/efficacy data source, whether the regulated product consumer has been taking the regulated product as prescribed and whether the regulated product is being effective, and, if so then dispensing the regulated product to the regulated product consumer.

In another implementation, there is provided a method for compliance-based distribution of a regulated product comprising, receiving a request to dispense a regulated product to a regulated product consumer, accessing a compliance/efficacy data source, determining, from the compliance/efficacy data source, whether there is authorization to dispense the requested regulated product to the regulated product consumer, and, if there is authorization then dispensing the regulated product to the regulated product consumer. Whether there is authorization in the determining may comprise ensuring that there has been compliance and efficacy in any previous dispenses of the regulated product to be dispensed or one or more related regulated products to the regulated product consumer. Whether there is authorization in the determining may further comprise ensuring that a regulated product purchaser has provided authorization. In yet another implementation, a method may further comprise establishing requirements for inputting compliance/efficacy data into the compliance/efficacy data source, and inputting compliance/efficacy data into the compliance/efficacy data source. Whether there is authorization in the determining may comprise ensuring that a regulated product purchaser for the regulated product to be dispensed has provided authorization and wherein the regulated product purchaser may be different from the regulated product consumer. The ensuring may be from, or with reference to, the compliance/efficacy data source.

In a further implementation, the method may further comprise obtaining a payment for the regulated product from the regulated product purchaser, and the method may further comprise inputting compliance/efficacy data into the compliance/efficacy data source and may involve doing so recursively as regulated products are continually authorized, paid for, dispensed, taken, monitored and so on. The method may further comprise establishing requirements for inputting compliance/efficacy data into a compliance/efficacy data source, and, issuing reminders to input compliance/efficacy data. Establishing requirements may be done by one or more regulators.

In another implementation, there is provided a system for compliance based distribution for regulated products comprising a regulated product data source comprising one or more datasets of payment authorization information further comprising compliance/efficacy data, for a regulated product for a regulated product consumer, configured to receive compliance/efficacy data from one or more compliance/efficacy data gathering devices and provide compliance/efficacy data or payment authorization information to one or more of a regulated product purchaser, regulated product dispenser or regulated product dispenser device. The provided compliance/efficacy data may indicate to the regulated product purchaser to issue payment for a regulated product, wherein the payment may be issued to a regulated product dispenser or regulated product dispenser device and wherein the payment may be for a "to be dispensed" regulated product and the compliance/efficacy data relates to "previously dispensed" regulated product. In a further implementation, the system further comprises a regulated product dispenser device further comprising the regulated product and a dispenser to dispense the regulated product, configured to communicate with the regulated product data source. The system may further comprise configuring the regulated product data source to receive a payment for the regulated product from the regulated product purchaser and provide such payment to a regulated product dispenser. The system may further comprise the regulated product data source comprising the regulated product dispenser device.

In a still further implementation, the system for compliance based dispensing of regulated products comprises a regulated product data source comprising authorization information for a regulated product for a regulated product consumer configured to receive compliance data from one or more compliance/efficacy data gathering devices and provide compliance/efficacy data or authorization information to a regulated product dispenser device, and a regulated product dispenser device comprising regulated product, configured to query the regulated product data source for authorization information and to dispense the regulated product to the regulated product consumer if the queried authorization information indicates to dispense. The regulated product data source or the regulated product dispenser device may be configured to receive payment from a regulated product purchaser and the authorization information may comprise authorization from the regulated product purchaser to dispense the regulated product. The payment may be for a "to be dispensed" regulated product and the compliance/efficacy data may relate to "previously dispensed" regulated product.

In one implementation, there is provided a method for paying for a regulated product dispenser device containing regulated products comprising placing a regulated product dispenser device, having a regulated product contained therein that is authorized to be dispensed to a regulated product consumer, at the regulated product consumer's living quarters, receiving a request to dispense the regulated product to the regulated product consumer and a payment, for the regulated product to be dispensed, from a regulated product purchaser, dispensing the regulated product to the regulated product purchaser, and, providing a transaction fee to a regulated product dispenser device manufacturer until the regulated product dispenser device manufacturer has received payment in full for the agreed upon price of the regulated product dispenser device.

In another implementation, there is provided a method for paying for a regulated product dispenser device containing regulated products comprising, placing a regulated product dispenser device at a consumer accessible location, receiving payment for regulated products, dispensing the regulated products, and, providing a transaction fee to a regulated product dispenser device manufacturer. The method may further comprise obtaining dispensing authorization, from a regulated product regulator. The dispensing and providing may occur after the obtaining and receiving have successfully occurred. The receiving, obtaining, dispensing and providing are performed by a regulated product dispenser. The consumer accessible location may be at a regulated product dispenser device location provider. The consumer accessible location may be at a regulated product consumer's living quarters and the regulated product dispenser device may comprise regulated products that a regulator has authorized the consumer to take or receive for some period or following some requirements. The providing may occur after the dispensing.

In yet another implementation, there is provided a system for paying for a controlled product dispenser comprising a regulated product dispenser, located at a regulated product dispenser location provider, configured to house regulated products and dispense regulated products upon receiving authorization from a regulated product regulator and payment from a regulated product purchaser and further configured to provide a transaction fee to a regulated product dispenser device manufacturer upon receiving payment from a regulated product purchaser.

In a further implementation, there is provided a system for paying for a controlled product dispenser comprising, a regulated product dispenser, further comprising regulated products to be received by a consumer upon obtaining an authorization from a regulated product regulator, configured to receive a dispensing request, verify the authorization, receive payment for the regulated product, dispense the regulated product and provide a transaction fee to a controlled product dispenser device manufacturer from the payment for the regulated product. Verifying the authorization comprises scanning the authorization and identifying the consumer, sending the scan and identifying information to a regulated product regulator station, and obtaining verification from the regulated product regulator station.

BRIEF DESCRIPTION OF THE DRAWINGS

Advantages, features and characteristics of the present invention, as well as methods, operation and functions of related elements, will become apparent upon consideration of the following description and claims with reference to the accompanying drawing, all of which form a part of the specification. The invention is illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting.

FIG. 1 is a diagram of a system for compliance-based distribution of regulated products according to a non-limiting implementation;

FIG. 2 is a diagram of known distribution interactions for regulated products;

FIG. 3 illustrates a configuration of the compliance-based distribution of regulated products method and system in accordance with a non-limiting implementation; FIG. 4 illustrates a flow diagram of the compliance-based distribution of regulated products and system according to a non-limiting implementation;

FIG. 5 illustrates a configuration of the compliance-based distribution of regulated products method and system in accordance with a non-limiting implementation;

FIG. 6 illustrates a flow diagram of the compliance-based distribution of regulated products method and system according to a non-limiting implementation;

FIG. 7 illustrates a configuration of the compliance/efficacy data gathering system of the compliance-based regulated products method and system in accordance with a non-limiting implementation; and

FIG. 8 illustrates a configuration of the compliance/efficacy data of the compliance- based regulated products method and system in accordance with a non-limiting implementation;

FIG. 9 is a diagram of a system for compliance-based distribution of regulated products according to a non-limiting implementation;

FIG. 10 is a diagram of known distribution interactions for regulated products;

FIG. 1 1 illustrates a first configuration of the regulated product dispensing method and system in accordance with a non-limiting implementation;

FIG. 12 illustrates a flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation;

FIG. 13 illustrates a further flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation;

FIG. 14 illustrates a second configuration of the regulated product dispensing method and system in accordance with a non-limiting implementation;

FIG. 15 illustrates a flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation;

FIG. 16 illustrates a further flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation; and

FIG. 17 illustrates a generalized flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation.

FIG. 16 illustrates a DETAILED DESCRIPTION

FIG. 1 is a diagram of a system for compliance-based distribution of regulated products according to a non-limiting implementation. System 100 comprises regulated product dispenser location provider (RPDLP) 106 which may further comprise regulated product dispenser device (RPDD) 108 and regulator (pharmacist) 110b, regulated product purchaser (RPP) 112, regulated product consumer (RPC) 114, regulated product dispenser (RPD) 116 which may further comprise regulator (pharmacist) 1 10b, regulator (doctor) 110a, regulated product data source (RPDS) 118 further comprising compliance/efficacy data (CED) 120, and communication network 122.

The elements of system 100 may interact, in many ways, to provide a new system and method for distribution of regulated products. Each element in figure 1 may be a person or entity, may be one or more physical elements of a network (such as computers, servers, cell phones and other computing devices as described herein), or some combination thereof. The connotation will largely dictate which is being referred to but clarification will be added if needed.

Before proceeding to describe system 100, regulated products (RP) should be described. A regulated product, as used herein, shall mean a product that is regulated in at least one way, and by at least one regulator. Regulation of a regulated product may impose requirements on use, distribution, dispensing, purchasing, sale, and other factors relating to regulated products. Exemplary regulated products may include prescription or other medications, alcohol or tobacco products, building permits, parking passes for disabled persons, notary public seals or stamps, and firearms.

In addition, regulated products may have one or more authorization documents that prove suitability, or allow dispensing, for example. Exemplary authorization documents may include prescriptions, documents that prove age, medical certificates, hunting licenses, and the like.

RPDLP 106 may be any company, retailer or other location that provides a location for RPDD 108. Exemplary RPDLP 106 may include big-box stores, doctor's offices or clinics, hospitals, convenience stores, government locations, pharmacies that wish to upgrade their systems and methods, and the like. RPDLP 106 may have many of their own systems, computer and otherwise, that may interact with RPDD 108.

RPDLP 106 may further comprise regulated product dispenser device RPDD 108 and regulator (pharmacist) 1 10b. RPDD 108 may be similar to implementations that may be described in US 12/551,456 and/or US 61/320,772. RPDD 108 may be able to communicate with RPDLP 106 and regulator 110b, with or without communication network 122 (such as via private networks, direction connections, or being local to one or more of them). Regulator 110b may be required to dispense a RP. In Figure 1, regulator 110b is shown as partially within RPDLP 106 as it/they may be at the location or may be remote from the location. Regulator 110b may perform substantially the same functions as a pharmacist or other regulator and may be able to perform those functions locally or remotely via the functionality of system 100.

Regulated product purchaser (RPP) 112 may be any party that is the final payer for the RP. This may be RPC 114, an insurance company that may insure RPC 1 14 or their employer, for example through an employer health care plan.

Regulated product consumer (RPC) 1 14 may be the actual person who is going to use or take the RP. This may be the patient in the case of medication, a disabled person, a person who is legal age to drink, or the like.

Regulated product dispenser (RPD) 1 16 may be any party that can dispense regulated products and may include similar parties to those of RPDLP. RPD 116 may be a pharmacy, for example. RPD 1 16 may be able to distribute or dispense RP without an external regulator 110b as it may further comprise a regulator (pharmacist) 110b of its own. RPD 116 may be a corporation having a large enough workforce to service as a pharmacy, for example.

Regulator (doctor) 110a may be any regulator that can authorize RPC 114 to receive or be dispensed a given RP. By way of example, regulator 110a may be a doctor that can prescribe RP to RPC 114.

Regulator (pharmacist) 1 10b may be any pharmacist that can dispense RP to RPC 114. Regulator 110b may be physically located where RP is dispensed or may be remote from dispensing. For example, as shown in Figure 1, regulator 1 10b is partially inside RPDLP 106 and RPD 116 - meaning that they may be physically present or may simply be accessible, providing the access allows them to dispense in accordance with applicable regulations.

It is to be understood that regulators 110 may also be government agencies, or other parties vested with power to determine suitability of RPs. They may or may not be directly involved in the dispensing transaction; they may be involved simply in setting the procedures or policies under which RP are dispensed.

Regulated product data source (RPDS) 118 may be one or more computer systems configured to communicate with one or more entities of system 100. RPDS 1 18 may store data relating to RP, RPC 1 14, usage, efficacy, and other data, such as compliance/efficacy data (CED) 120 which it further comprises, as described herein.

Communication network 122 may be any one or more communication networks that enable communication between entities and computer systems. Communication network may be one or more WANs, LANs or combinations thereof. It may be implemented as wired or wireless networks or private networks. They may be encrypted, for example, to protect the data being transmitted.

Any of the entities may have one or more computer systems that may form part of system 100 but may also serve as part of the other functions of that entity.

FIG. 2 is a diagram of known distribution interactions for regulated products.

Like references refer to like references and are as described herein - both with respect to Figure 2 and the other figures included in this application.

RPC 114 would physically go to a pharmacy with the prescription they got from a doctor. They would return home with their prescription medication (RP). Their insurer or employer would either pay the pharmacy for the RP or would reimburse RPC 1 14 after RPC 114 submitted the receipt and appropriate reimbursement form. As long as a prescription was obtained, receipts and forms filled out properly, the insurer or employer would pay for the RP. RPP 114 would not necessarily know the doctor or pharmacy. RPP 1 14 would never know the outcome of having taken the RP, and would never know whether the doctor or pharmacist ever knew. In effect the people that paid for the RP never knew whether it worked - if anyone ever did. Certainly on a large and continuous scale and basis there was never any feedback on substantial outlays of money.

FIG. 3 illustrates a configuration of the compliance-based distribution of regulated products method and system in accordance with a non-limiting implementation.

Hashed lines indicate logical or data movement - typically electronic movement of information or money. These may be over communication network 122 or may be via other methods. Solid lines indicate physical movement - the physical flow of people or paper predominantly. Where both types of lines exist there may be options to undertake the activity either logically or physically.

The system in Figure 3 may be one implementation of a system to practice the method shown in Figure 4. In the system 300 shown in Figure 3, retailer or RPD 1 16 has a pharmacist on duty (regulator 1 10b) that receives a prescription for a regulated product from RPC 1 14. Typically this involves RPC 1 14 physically going to the pharmacy.

RPD 1 16 may have an RPP 112 on file for RPC 114, such as in computer systems operated by RPD 116 that may be specifically for a pharmacy or may be part of a larger retail system, and may provide them information to determine whether they will be paying for the RP.

RPDS 118 may be consulted, by RPD 116 or RPP 1 12, before or after RPD 116 determines whether RPP 112 will be paying for RP. Whoever consults with RPDS 118 may have an access code, such as a user ID and password, to allow them to see the required CED.

As discussed herein, CED may allow RPDS 1 18 to respond to the inquiry and indicate whether there is authorization - such as RPP 1 12 authorization, regulator 110a authorization, compliance authorization, etc. - to dispense RP.

Upon dispensing, RPD 1 16 may be paid by RPP 1 12 electronically, scenario (2), or may be paid by RPC 1 14, scenario (1) (in either case, RPD 1 16 will not typically dispense without simultaneously receiving payment, though they could operate on account etc.) RPC 1 14 may then return home with their RP.

If RPC 114 paid for the RP, they may submit, electronically or via paper forms, a request to be reimbursed for the purchase of the RP. This may prompt RPP 1 12 to consult RPDS 1 18 and CED 120, which may be a first consultation or a further consultation, for example if RPP 1 12 did not provide RPD 1 16 authorization for it to pay for the RP.

FIG. 4 illustrates a flow diagram of the compliance-based distribution of regulated products and system according to a non-limiting implementation. The flow diagram in Figure 4 may be implemented, for example, by a system such as shown in Figure 3.

Method 400 begins at 402 where RPC 114 interacts with a regulator 1 10a, such as a doctor, to obtain an authorization, such as a prescription, for a RP. This may occur at virtually any physical location, such as at regulator 110a (for example a doctor's office or clinic). This may also occur remotely, where regulator 110a may be able to determine the validity of providing the RP authorization without being physically in the same location as RPC 1 14.

It should be noted that method 400 may also start at 404, for example if an authorization has already been obtained from regulator 1 10a and now the RP simply need to be obtained. This may occur, for example, if a prescription was previously obtained or if a prescription was previously obtained and now a refill is sought to be obtained. Assuming an RP authorization is provided at 402 (or else method 400 terminates), method 400 continues to 404. At 404 RPC 1 14 takes RP authorization to obtain the RP. This may involve going to a retailer, such as a pharmacy or other RPD 116, or RPDLP 106.

At 406, method 406 queries whether RPC 114 has a known RPP 112. This may be performed, for example, by RPD 1 16, RPDLP 106 or RPDD 108. Preferably, this is done using one or more computer systems, such as in system 100, and may involve consulting a profile of RPC 1 14 or some such database. Alternatively, RPC 114 may present a card or other form of identifying their RPP 1 12 to RPD 116, at 406. It is assumed that by RPC 114 having, or providing the identify of, their RPC 112, they intend to have RPP 112 pay for their RP.

As will be seen herein, such as at 422-430, RPC 1 14 may have an RPP 1 12 but not have them provide payment initially - seeking instead to be reimbursed at a later time.

If RPC 1 14 has an RPP 112 the method 400 continues to 408 where payment information is provided to RPP 1 12. As with 406, this may preferably be done with computer systems and may involve, for example, RPD 1 16 providing the required payment amount, and medication(s) involved, to RPP 1 12. At 408 other information may also be provided, such as the medication, amount of medication, dosage, prescribing doctor, usage instructions and alternatives considered. Any of this information may be input into a RPDS 1 18, which may allow for future authorization and compliance or efficacy determinations to be made. This inputting may be done as part of 408 or 410.

At 410 CED is consulted. This may be done by RPP 112 and/or by RPD 116 (or whatever is responsible for dispensing RP). Consulting at 410 is intended to determine whether the dispenser is authorized to dispense RP. Authorization may be based on previously dispensed RP, if any previously dispensed RP data exists, for example.

Authorization may be based on many factors. The first factor may be whether RPP 112 will pay for the RP. This may be based on the healthcare coverage available to RPC 1 14 through their insurance. However, this may also be based on whether RPC 1 14 has been compliant in taking their medication, and/or whether RPC 1 14, or others, have been inputting CED that shows that RP has been taken and has been effective in dealing with whatever concern was identified by regulator 1 10a in prescribing RP. Although further examples will be discussed herein, if RP is intended to lower RPC 114 blood pressure but has not been doing so, then authorization may not be received (RPP 1 12 may not authorize, the dispenser may not authorize, or even regulator 1 10a may not authorize the continued use of RP). At 410, RPC 1 14 may not have yet taken the RP they are seeking to have dispensed to them. In such a situation there may be little compliance or efficacy data to consult to get authorization. However there may still be relevant CED, for example relating to RPC's 1 14 past compliance data or other RP that may cause undesired reactions. These, and other reasons as described herein, may still cause a lack of authorization at 410.

At 410 RPC 1 14 may have already taken the RP they are seeking to have dispensed to them. They may be starting a new dosage, may be filling a refill, or may be starting a new prescription (for example an antibiotic that was prescribed two years earlier for an infection). In such situations there may be meaningful CED relating to the specific RP that will form the basis for authorization.

At 412 authorization, as described with respect to 410 and as described herein, is either received or not. Authorization, at 412, may be from one or more of regulator 110a, regulator 1 10b, and RPP 1 12.

If authorization is received then method 400 continues to 414 where a query is made to determine whether payment is received by the dispenser, such as RPD 116. In normal course, if all required authorizations are received at 412, payment will be received at 414. However, in certain situations, such as any payment network problems, payment may still not be received. Payment at 414 is for the RP that is to be dispensed, for example by RPD 116.

If payment is received then at 416 the dispenser dispenses RP to RPC 1 14. Dispensing at 416 may also trigger for some of the requirements or additional information that may have been provided at 408, to be entered into RP data source 1 18. This may be done by RPP 112 or dispenser.

If payment is not received at 414, or authorization is not received at 412, method 400 continues to 418 where RPC 1 14 may be authorized to pay for RP. It is to be understood that a variety of circumstances may preclude RPC 1 14 from purchasing RP should authorization not have been received, or even should payment not have been received from RPP 112. For example, authorization may not have been received at 412 because regulator 1 10a did not provide authorization. This would make it inappropriate for RPC 114 to pay for, and receive, RP.

If RPC 1 14 is not authorized then method 400 ends with no dispensing. If RPC 1 14 is authorized to purchase RP then method 400 continues at 420 to determine whether RPC 114 will pay for RP. If they will not then process 400 ends. If they will then payment is provided to the dispenser and method 400 continues at 422 where RP is dispensed. Similar to 416, requirements or other information may be provided to RP data source 118 when RP is dispensed.

Continuing at 424, RPC 1 14 may submit a receipt from their payment for RP to their RPP 1 12. This may be done via regular mail, or electronically.

Method continues to 426 and 428, which may be substantially similar to 410 and 412, as described herein. If authorization is received at 428 then RPP 112 reimburses RPC 1 14— electronically or via mail. If authorization is not received then RPP 1 12 denies the claim and does not reimburse RPC 1 14, at 430, and method 400 ends.

FIG. 5 illustrates a configuration of the compliance-based distribution of regulated products method and system in accordance with a non-limiting implementation.

Hashed lines indicate logical or data movement - typically electronic movement of information or money. These may be over communication network 122 or may be via other methods. Solid lines indicate physical movement - the physical flow of people or paper predominantly. Where both types of lines exist there may be options to undertake the activity either logically or physically.

The system in Figure 5 may be one implementation of a system to practice the method shown in Figure 6.

In the implementation shown in Figure 5, RPDD 108 may be co-located with RPC 114— for example in their home, attached or attachable to their person, at their living quarters. Instead of co-located with RPC 114, RPDD 108 may be located somewhere they otherwise have to visit frequently - such as their work environment.

Locating RPDD 108 proximate to RPC 1 14 may make dispensing RP to RPC 114 more convenient. It may also encourage and support compliance, by RPC 1 14, to requirements set forth in the prescription. This may also encourage efficacy of the RP.

RPDD 108 may be able to communicate with one or more of RPDS 118, or RPDP 502.

Although not shown, RPDD 108 may be able to communicate, directly or indirectly, with virtually any entity through communication network 122 (not explicitly shown in Figure 5 but implied as one approach to enabling communication). By way of example, although RPP 1 12 is not shown, they may also be able to communicate with RPDS 118, view CED, and provide or withdraw their authorization - which may allow or prevent RPDD 108, proximate to RPC 1 14, to dispense RP to RPC 114. As RPDD 108 may communicate with RPDS 1 18, it may consult RPDS 1 18 for authorization prior to dispensing. That way, if RPC 114 is not being compliant in taking their course of RP RPP 1 12 does not need to authorize further dispensing. In this way RPP 1 12 is not paying for RP that is not being taken, not being taken properly, or is not having the desired affect, for example. As described herein, and as would be known to those of skill in the art, there are many reasons why RPP 1 12 would not want to pay for RP dispensed to a given RPC 114.

RPD Provider 502 may be substantially any party that provides RPC 114 with RPDD 108. Although RPC 1 14 may pay for RPDD 108 themselves, this is unlikely given the meaningful upfront cost. As such, and given the benefits of RPDD 108 being proximate to RPC 1 14, RPDD 108 may be paid for by, for example, RPD manufacturers, RP manufacturers, RPD 116, or others. RP inside RPDD 108 may be owned by RPD Provider 502 or by another party. As shown in Figure 5, RPDD 108 and RP may be owned by RPD Provider 502, and RPDD 108 may issue payment (optionally on behalf of RPP 1 12) to RPD Provider 502. This payment may then be split between the owner of the RP and the owner of RPDD 108, which may be the same entity.

FIG. 6 illustrates a flow diagram of the compliance-based distribution of regulated products method and system according to a non-limiting implementation. The flow diagram in Figure 6 may be implemented, for example, by a system such as shown in Figure 5.

Method 600 begins at 602 where RPC 114 seeks dispensing of a RP. Method 600 may begin with an action similar to 402, where an authorization, such as a prescription, is obtained. However, as contemplated in Figure 6, a prescription has already been issued; such prescription may have been issued by RPDD 108 in fact.

Additionally, in method 600, RPDD 108 may be located proximate to RPC 1 14, such as at their home, such that seeking dispensing may involve interacting with RPDD 108 as opposed to travelling to a remote location, possibly with a prescription.

At 604 a query is made whether an authorization, such as a prescription, has already been submitted.

If a prescription has not been submitted then method 600 continues at 616 to determine whether RPC 1 14 has one to submit. If there is no prescription on file, and RPC 114 does not have on to submit then method 600 ends. However, if RPC 114 has one to submit then at 618 RPC 114 provides it to RPDD 108 at 618. This may be done, for example, by submitting it to a scanner, or other input device, associated with or connected to RPDD 108. When a prescription is provided to RPDD at 618, method 600 continues at 630 where CED 120 is updated. This may involve adding a new RPC 114, adding a new RP, adding a new refill, or some other addition or combination thereof. Further examples may be described herein, and with respect to Figures 7 and 8. Updating CED at 620 may assist in the dispensing decision that will be reached.

It is to be understood that in normal course, a first time through method 600 would involve submitting a prescription and having CED updated. Subsequent times RPC 1 14 seeks RP to be dispensed, during the course, would involve an already submitted prescription.

Returning to 604, if a prescription has been submitted then method 600 continues to 606 to query whether RPDD 108 has a payment source for the RP. A payment source for RPDD may mean that all RP to be dispensed have been paid for already or may be paid for as they are dispensed. A payment source may be RPP 112, RPC 114, or any owner of the RP in RPDD 108, such as RPD 1 16 or RP manufacturer. Essentially at 606 RPDD 108 is attempting to make sure that dispensing does not occur for "free".

Continuing to 608, CED 120 is consulted. CED may be located at RPDS 118, though it could be at RPP 1 12, RPDD 108, or another entity. Method 600, at 608, 610 and 622 may be substantially similar to 410 and 412.

At 612 a query may be made whether payment has been received. Although similar to 414, the RP in RPDD 108 in method 600 may already have been paid for, so they may not require payment on dispensing. Assuming payment is received, or they are already paid for, RP is dispensed at 614 and method 600 terminates.

FIG. 7 illustrates a configuration of the compliance/efficacy data gathering system (CEDGS) of the compliance-based regulated products method and system in accordance with a non-limiting implementation.

CEDGS 700 comprises CED gathering entity 702 which further comprises diagnostic apparatus 704 and compliance data gatherer 706, communication network 122 as described herein, and RPDS 1 18 which further comprises CED 120, both as described herein.

CEDGS 700 may allow compliance, efficacy, and authorization data, among other things, to be input (or uploaded, determined, stored, etc.) into RPDS 1 18 and CED 120. In one example, CEDGS 700 may input when RPC 1 14 takes RP, and may input diagnostic data that can be, or can be interpreted (for example by regulator 1 10a) as, efficacy data. CED gathering entity 702 may be any entity that allows for some data to be gathered and eventually sent to RPDS 118 - such as regulator 1 10b, regulator 110a, RPD 116, RPDD 108, etc. CED gathering entity 702 may also be other entities that happen to have, support, and house or otherwise be affiliated with diagnostic apparatus 704 or compliance data gatherer 706.

Diagnostic apparatus 704 may be any apparatus that may measure, determine, observe, test, monitor, etc., a characteristic of RPC 114 that relates to determining efficacy of one or more RP. Exemplary diagnostic apparatus may include blood pressure monitors, blood sugar monitors, heart rate monitors, respiration rate monitors, reflex testing device, strength testing devices, scales, and the like.

Compliance data gatherers 706 may be any apparatus that assists in determining whether

RPC 114 has complied with the requirements relating to a course of RP - such as when RPs were taken, how much or many, if they entered the body or bloodstream, etc. Exemplary compliance data gatherers 706 may include dispensers that dispense one dosage at a time or apparatuses that allow an observer to enter data relating to the above. For example, regulator 110a or regulator 1 10b, RPP 1 12 or RPC's employers may have compliance data gatherers in their locations so when RPC 114 takes their RP the other party can send compliance data to RPDS 1 18 to update CED 120. Alternatively an RPC 1 14 may have either compliance data gatherers 706 or diagnostic apparatus 704 connected to them, inserted within them (such as under the skin), etc. Any compliance data gatherer 706 may also be a diagnostic apparatus 702, and the reverse.

It is to be understood that CEDGE 702 may communicate with RPDS 118 or diagnostic apparatus 704 or compliance data gatherer 706 may do so - either independently or through CEDGE 702.

In certain implementations the necessity to provide CED 120 to RPDS 1 18 may be imposed on RPC 1 14 and/or regulator 110b in order to continue receiving RP at the expense of RPP 1 12. Having a diagnostic apparatus 704 or compliance data gatherer 706 that is proximate to, or wearable by, RPC 1 14 may be preferred.

FIG. 8 illustrates a configuration of the compliance/efficacy data of the compliance-based regulated products method and system in accordance with a non-limiting implementation.

It is to be understood that CED table 800 is one implementation of an organization that may exist within CED 120.

CED table 800 comprises column headings 802 which may include: Patient Name: name of RPC; Patient ID/#: ID number, such as insurance numbers or employee number; Medication/RP: what RP is being taken; Prescribing Dr: what regulator 110a prescribed the RP; Prescription Date: when the prescription was written; Diagnostic Data: what diagnostic data is being sought to measure or determine efficacy or compliance; Date: date of a reading of diagnostic or compliance data; Diagnostic Data Reading #: what number in the sequence of readings for a given piece of diagnostic data; Value: the measured value for the diagnostic data; Regulator Authorization: A Boolean value for whether a regulator, such as regulator 110a, has authorized for further RP to be dispensed (either for a refill or for a further single-dosage dispensing); and RP Purchaser Authorization: A Boolean value for whether RPP 112 has authorized for further RP to be dispensed or paid for by RPP 1 12.

By way of example, row 804 has CED for Jane Smith and row 806 has a further example of CED for Jane Smith - involving a different RP. In 804 Jane Smith is taking an RP called BP Helper that requires blood pressure to be monitored to determine its efficacy. On successive days a blood pressure monitor (a diagnostic apparatus 704) was used and sent her data to RPDS 118 and her value was recorded. Both authorizations were provided on the continued use or dispensing of BP Helper, for all three days/readings. In row 806 we see that Jane Smith is also taking BS Monitor to help maintain her blood sugar level. Again a diagnostic apparatus, perhaps at her local pharmacy or doctor's office, was used to record her blood sugar and send it to RPDS 1 18. On the third day, reading 3, her blood sugar level fell to 34. This prompted regulator 110a authorization to be withheld, which also caused RPP authorization to be withheld. Jane Smith would then not be dispensed further BS Monitor. CEDGS 700, for example by way of RPDS 118 or diagnostic apparatus 704 that may be attached to RPC 114, may indicate to Jane Smith that she needs to visit regulator 1 10a or go to a hospital to get new RP.

In a further example, row 808 has CED for David John. David John is taking ABC Medication and the diagnostic data is whether it has been dispensed (as a proxy for whether he has taken the RP). He took the first two, and authorizations were provided. He missed his third, and authorizations were withheld. Upon taking his forth, authorizations were re-instated. It is to be understood, from this example, that a rather complex set of requirements and authorizations can be used; perhaps two consecutive authorizations need to be negative before dispensing stops, perhaps more. Perhaps lack of compliance cannot be overcome at all. Perhaps taking RPs later than intended (say five hours late) but still taking them obviates authorization being withheld. In any event, regulator's authorization and RPP's authorization can be tracked and affect dispensing and payment for RP. Although aspects of the invention were described largely with respect to medication as the RP, many other RP may be applicable.

In a further example, alcohol may be the RP. The regulators are government and retailers that assure that purchasers are the required age. In some jurisdictions, for example, only 18 year olds and older may purchase alcohol but anyone can sell alcohol if they have gone through the proper registration. In other jurisdictions, only 19 year olds and older may purchase alcohol and only government-run stores can sell alcohol. In either situation, systems and methods as described herein may be used, such as system 300. Alcohol may be stored in RPDD 108 at RDPLP 106. This may be particularly useful where RPDLP would not be allowed to sell alcohol through its own store. When RPC 114 desires alcohol they would visit RPDLP. Selecting a particular product from RPDD 108 would lead RPDD 108 to confirm whether the person was old enough to purchase alcohol. This may involve RPC 1 14 providing their ID to RPDD 108. A regulator 110, such as an age verifier, a government official, a police officer, etc., may be available to RPDD 108 where the ID may not match the person presenting themselves to RPDD 108. The next step may be to consult CED to determine whether, for example, RPC 114 has obtained too much alcohol recently (or even a high blood-alcohol level) or if they are driving or have liver problems, or some other reason that alcohol should not be dispensed, as captured by one or more CED Gathering Entities (which may even be RPDD 108) and input into CED. Once dispensing is determined to be appropriate, RPC 114 may provide payment to RPDD 108 and RP may be dispensed. Such an approach may allow a government to make RP available in more remote locations without relinquishing control of the dispensing and may further allow denial of service at appropriate times.

In a further example, stickers for disabled parking may be the RP. The regulators are government officials that assure RPC 1 14 have a qualifying disability. Systems and methods as described herein may be used, for instance system 300. Stickers may be stored in RPDD 108 at RDPLP 106. When RPC 1 14 requires a sticker they would visit RPDLP. RPDD 108 may query RPC 1 14 what their disability they have and what sticker they require (perhaps a sticker with a two-week duration, or that will last until they have given birth, etc.) RPDD 108 would then attempt to confirm whether the person was entitled to the sticker. This may involve accepting a doctor's note or disability form, or other form of proof. Entitlement may also involve querying CED - such as to make sure that the doctor still believed RPC 114 required the sticker, had not abused the privilege, received any tickets, etc. Also, CED Gathering Entities may be employed to retrieve old, expired stickers to make sure that such stickers are not being improperly redistributed. Once old stickers are received CED may reflect that RPDD 108 is authorized to dispense a new one. A regulator 1 10, such as a doctor or a government official may be available to RPDD 108 where RPDD 108 cannot conclusively determine entitlement. Such an approach may allow a government to make RP available in more remote locations without relinquishing control of the dispensing. System 600 may be used, for example, for a remotely-located RPC 114 having a recurring need for a sticker.

FIG. 9 is a diagram of a system for compliance-based distribution of regulated products according to a non-limiting implementation. System 900 comprises regulated product dispenser device manufacturer (RPDDM) 102, regulated product manufacturer (RPM) 104, regulated product dispenser location provider (RPDLP) 106 which may further comprise regulated product dispenser device (RPDD) 108 and regulator (pharmacist) 110b, regulated product purchaser (RPP) 112, regulated product consumer (RPC) 114, regulated product dispenser (RPD) 116 which may further comprise regulator (pharmacist) 110b, regulator (doctor) 110a, regulated product data source (RPDS) 118 further comprising compliance/efficacy data (CED) 120, and communication network 122.

The elements of system 900 may interact, in many ways, to provide a new system and method for distribution of regulated products. Each element in figure 1 may be a person or entity, may be one or more physical elements of a network (such as computers, servers, cell phones and other computing devices as described herein), or some combination thereof. The connotation will largely dictate which is being referred to but clarification will be added if needed.

Before proceeding to describe system 900, regulated products (RP) should be described. A regulated product, as used herein, shall mean a product that is regulated in at least one way, and by at least one regulator. Regulation of a regulated product may impose requirements on use, distribution, dispensing, purchasing, sale, and other factors relating to regulated products. Exemplary regulated products may include prescription or other medications, alcohol or tobacco products, building permits, parking passes for disabled persons, notary public seals or stamps, and firearms.

In addition, regulated products may have one or more authorization documents that prove suitability, or allow dispensing, for example. Exemplary authorization documents may include prescriptions, documents that prove age, medical certificates, hunting licenses, and the like. RPDDM 102 may be any entity that manufactures RPDD. They may also design, own, and operate RPDDs 108, RPDS 1 18 and RPDLP 106 or RPD 1 16.

RPM 104 may be any entity that manufactures RP. Typically they may be drug companies, tobacco companies, firearms companies, and the like. Often RPM 104 are heavily involved in R&D and manufacturing of RP and are less involved in retailing or selling RP to RPC 1 14, though they certainly could be. Similarly, RPM 104 do not typically design, own or operate RPDDs 108, RPDS 1 18, RPDLP 106 or RPD 116. These entities are typically customers of RPM 104.

RPDLP 106 may be any company, retailer or other location that provides a location for RPDD 108. Exemplary RPDLP 106 may include big-box stores, doctor's offices or clinics, hospitals, government locations, pharmacies that wish to upgrade their systems and methods, and the like. RPDLP 106 may have many of their own systems, computer and otherwise, that may interact with RPDD 108.

RPDLP 106 may further comprise regulated product dispenser device RPDD 108 and regulator (pharmacist) 1 10b. RPDD 108 may be similar to embodiments as described in US 12/551,456 and/or US 61/320,772. RPDD 108 may be able to communicate with RPDLP 106 and regulator 110b, with or without communication network 122 (such as via private networks, direction connections, or being local to one or more of them). Regulator 110b may be required to dispense a RP. In Figure 1, regulator 1 10b is shown as partially within RPDLP 106 as it/they may be at the location or may be remote from the location. Regulator 110b may perform substantially the same functions as a pharmacist or other regulator and may be able to perform those functions locally or remotely via the functionality of system 900.

Regulated product purchaser (RPP) 112 may be any party that is the final payer for the RP. This may be RPC 114, an insurance company that may insure RPC 1 14 or their employer, for example through an employer health care plan.

Regulated product consumer (RPC) 1 14 may be the actual person who is going to use or take the RP. This may be the patient in the case of medication, a disabled person, a person who is legal age to drink, or the like.

Regulated product dispenser (RPD) 1 16 may be any party that can dispense regulated products and may include similar parties to those of RPDLP 106. RPD 1 16 may be a pharmacy, for example. RPD 116 may be able to distribute or dispense RP without an external regulator 1 10b as it may further comprise a regulator (pharmacist) 1 10b of its own. RPD 116 may be a corporation having a large enough workforce to service as a pharmacy, for example.

Regulator (doctor) 1 10a, may be any regulator that can authorize RPC 1 14 to receive or be dispensed a given RP. By way of example, regulator 110a may be a doctor that can prescribe RP to RPC 114.

Regulator (pharmacist) 1 10b may be any pharmacist that can dispense RP to RPC 114. Regulator 110b may be physically located where RP is dispensed or may be remote from dispensing. For example, as shown in Figure 1, regulator 1 10b is partially inside RPDLP 106 and RPD 116 - meaning that they may be physically present or may simply be accessible, providing the access allows them to dispense in accordance with applicable regulations.

It is to be understood that regulators 110 may also be government agencies, or other parties vested with power to determine suitability of RPs. They may or may not be directly involved in the dispensing transaction; they may be involved simply in setting the procedures or policies under which RP are dispensed.

Regulated product data source (RPDS) 118 may be one or more computer systems configured to communicate with one or more entities of system 900. RPDS 118 may store data relating to RP, RPC 1 14, usage, efficacy, and other data, such as compliance/efficacy data (CED) 120 which it further comprises, as described herein.

Communication network 122 may be any one or more communication networks that enable communication between entities and computer systems. Communication network may be one or more WANs, LANs or combinations thereof. It may be implemented as wired or wireless networks or private networks. They may be encrypted, for example, to protect the data being transmitted.

Any of the entities may have one or more computer systems that may form part of system 900 but may also serve as part of the other functions of that entity.

FIG. 10 is a diagram of known payment flows for regulated products, where like references refer to like references and are as described herein - as with the other figures included in this application.

RPC 1 14 would physically go to a pharmacy with the prescription they got from a doctor (regulator 1 10a). They would submit their prescription to a pharmacist (regulator 110b) that may have been located at a RPD 1 16 such as a retailer. The pharmacist would check whether they had an insurer (RPP 112) on file for RPC 114. If so, they would submit the payment details to the insurer (RPP 112) and wait to see if RPP 1 12 would pay for the RP. If so, the parties would settle the transaction, less any amount not covered by RPP 1 12. This amount would then be charged to RPC 1 14. Once all amounts owed for the RP were paid to the pharmacist, they would dispense the RP to RPC 114 and RPC 1 14 would return home with their prescription medication (RP).

If the pharmacist did not have an insurer on file for RPC 1 14 then RPC 1 14 could choose to pay for their prescription, the pharmacist would dispense the medication, and RPC 1 14 would return home. If RPC 114 did have an insurer they would submit their receipt for reimbursement - with the insurer providing the reimbursement if the RP was covered and RPC 114 had submitted the proper paperwork.

These flows involve a significant amount of physical travel and require pharmacists 1 10b, at RPDs 116, to be placed near each RPC 1 14 to minimize difficulties in obtaining RP. This presents problems on at least two fronts: having regulators 110b at each RPD 1 16, and having adequate numbers of RPDs 1 16 in less densely-populated areas or simply close enough to RPCs 1 14 (having varied mobility constraints) to be helpful.

FIG. 1 1 illustrates a first configuration of the regulated product dispensing method and system in accordance with a non-limiting implementation.

System 1100 in Figure 11 may be one embodiment of a system to practice the payment flow shown in Figures 12 and 13.

Hashed lines indicate logical or data movement - typically electronic movement of information or money. These may be over communication network 122 or may be via other methods. Solid lines indicate physical movement - the physical flow of people or paper predominantly. Where both types of lines exist there may be options to undertake the activity either logically or physically.

In system 1 100, RPD 116 from Figure 10 may be replaced by RPDLP 106 and RPDD

108 which may further comprise RPs 202 and dispenser 204 through which RPs 202 may be dispensed from RPDD 108 to RPC 114, and by regulator 110b that may be remote from RPDLP 106 and RPDD 108. Of course RPDD 108 comprises more than is shown in Figure 1 1, and may be as shown and described in US Patent Application Publication No. 2010/0268380, published on October 21, 2010, and/or International Application Publication No. WO201 1/123933, published on October 13, 201 1. RPDLP 106 may be in a more consumer accessible location, making it easier for RPC 114 to obtain RPs. When RPC 1 14 seeks dispensing, they arrive at RDPLP 106 and interact with RPDD 108. This may obviate the need for one or more employees to tend to RPC 1 14 during the transaction. A prescription (authorization documents) may be provided to RPDD 108 and through interaction with remote regulator 110b, it may be confirmed. Interaction may be via scanners, cameras, instant messaging, and the like - substantially any way that two remote parties may communicate - providing the communication allows regulator 110b to properly dispense RPs. Regulator 1 10b, upon being satisfied of the propriety of dispensing, may indicate such authorization to RPDD 108.

RPDD 108 may then query RPC 114 to pay for RP to allow dispensing to occur. Such payment may be as described herein, for example as will be described with respect to Figures 12 and 13. After dispensing has occurred, RPC 114 may return home with their RP.

FIG. 12 illustrates a flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation. The flow diagram in Figure 12 may be implemented, for example, by a system such as shown in Figure 1 1.

Hashed lines indicate payment relating to RPDD 108 - typically money to purchase or pay for RPDD 108. Solid lines indicate payment relating to RPs - typically money to pay for retail or wholesale/discounted costs of the RP. All of these payments may be electronically, such as over communication network 122, or may be via other methods. Of course the parties involved may implicate that both types of payments are involved in a given line or transaction. This paragraph applies generally to Figures 12, 13, 15 and 16.

With respect to system 1 100, RPC 114 may get to a point where RPDD 108 seeks payment - after, just before, or simultaneous to, regulator 1 10b and/or RPDD 108 approving or authorizing the dispensing. RPC 1 14 may then provide payment themselves (such as by providing cash or credit) or may instruct RPDD 108 to charge their RPP 1 12. When the retail payment (the payment received from RPC 1 14 or RPP 112) is provided then dispensing may occur.

Upon dispensing, a series of payment flows may occur depending on who owns the RPDD and whether it has been fully paid for, and who owns the RP and whether it has been fully paid for.

Assuming RPM 104 owns the RP in RPDD and RPDDM 102 owns RPDD 108, the following payment flows may occur: RPDDM receives a fractional fee (such as a RPDD transaction fee). This may be directed to RPDDM or, for example, a distributor that purchases RPDDs 108 from RPDDM; Regulator may receive a fee (a regulator fee) if they are remote from, or economically separate from, RPDLP; RPM receives a fee for each RP dispensed (such as a wholesale price offered to RPDLP or RPDD; RPDLP may receive the remaining payment (retail payment; RPDD transaction fee - regulator fee - RP wholesale price per unit); or, alternatively, RPDLP may receive a 'lease' fee for providing space, electricity and communication mechanisms for RPDD. In such case a larger portion of the retail payment may be directed to RPDDM or RPDDM distributor.

FIG. 13 illustrates a further flow diagram of payments in a product dispensing method and system in accordance with a non-limiting embodiment of the present invention. The flow diagram in Figure 13 may be implemented, for example, by a system such as shown in Figure 1 1.

Similar to the description of Figure 4, RPC 114 may get to a point where RPDD 108 seeks payment. RPC 114 may then provide payment themselves (such as by providing cash or credit) or may instruct RPDD 108 to charge their RPP 112. When the retail payment (the payment received from RPC 1 14 or RPP 1 12) is provided then dispensing may occur.

Upon dispensing, a series of payment flows may occur. In the payment flow of Figure 13

RPDLP 106 has purchased, up-front, RPDD 108 from RPDDM 102 and has also purchased RP from RPM 104, possibly both at wholesale prices. Payment flows, on dispensing, are therefore: RPDDM 102 may receive a fractional fee (a small RPDD transaction fee); Regulator 100b may receive a fee (a regulator fee) if they are remote from, or economically separate from, RPDLP; RPDLP may receive the remaining payment (retail payment - small RPDD transaction fee - regulator fee).

Of course it is to be understood that other variations for distributing the payments (in addition to Figures 12-13 for system 1100) are possible in consideration of the business relationships entered into between these, and possibly other entities - providing the appropriate regulations are adhered to, if required. These may also further the objective of making RP more accessible.

FIG. 14 illustrates a second configuration of the regulated product dispensing method and system in accordance with a non-limiting embodiment of the present invention. System 1400 in Figure 6 may be one embodiment of a system to practice the payment flow shown in Figures 15- 16.

Hashed lines indicate logical or data movement - typically electronic movement of information or money. These may be over communication network 122 or may be via other methods. Solid lines indicate physical movement - the physical flow of people or paper predominantly. Where both types of lines exist there may be options to undertake the activity either logically or physically.

In system 1400, RPC 1 14 may further comprise RPDD 108, which may further comprise RPs 202 and dispenser 204 through which RPs 202 may be dispensed from RPDD 108 to RPC 1 14. As above, RPDD 108 comprises more than is shown in Figure 14, and may be as shown and described in US Patent Application Publication No. 2010/0268380, published on October 21, 2010, and/or International Application Publication No. WO2011/123933, published on October 13, 201 1.

RPDD 108 may be co-located with, or proximate to, RPC 114 - for example in their home, attached or attachable to their person, at their living quarters. Instead of co- located with RPC 114, RPDD 108 may be located somewhere they otherwise have to visit frequently - such as their work environment. In fact RPDD 108 may be RPC's 1 14 personal RPDD 108, storing and dispensing RPs specifically need by RPC 1 14 and/or their family. All of these options may be varying degrees of consumer accessible locations. Locating RPDD 108 proximate to RPC 1 14 may make dispensing RPs to RPC 114 more convenient. It may also encourage and support RPC 1 14 following their prescriptions, which may make RPs more effective.

In use, RPC 114 may not yet have RPDD 108. In such case they may visit regulator 1 10a, as in system 1000 and system 1100. RPC 1 14 may receive a prescription and visit RPDDM 102 (or a distributor for example) to acquire RPDD 108. They may then visit regulator 110b (such as at RPD 116) to have their prescription for RP filled and added to their RPDD 108. Any number of refills may also be added, or other RP that may be required by RPC 1 14 or their family.

In use, if RPC 114 has RPDD 108 at their home, they may wish to have RP dispensed that they have already been prescribed. They may request dispensing, and providing their request fits with directions of the prescription, it may be dispensed (with payments for RP optionally as described with respect to Figures 7 and 8). RPC 1 14, with RPDD 108 already at home, may also consult with regulator 1 10a using communication network 122 (shown in Figure 1) and optional features of RPDD 108 (such as a scanner, video camera, diagnostics, etc.) that allow regulator 1 10a to properly assess RPC 1 14 and prescribe RP. If RPDD 108 already has the newly prescribed RP then RPC 1 14 need not visit regulator 1 10b for RP to be inserted into RPDD 108 according to their prescription. As above, if RPDD 108 has the required RP, RPC 114 may request dispensing, and providing their request fits with directions of the prescription, it may be dispensed and the payments described in Figures 15-16 may occur.

In various uses for system 1400 RP may be dispensed. Although payments may result from dispensing, RPC 1 14 may make them or be unaware of them. For example, RPP 1 12 may be involved and not RPC 114; RPP 1 12 may have programs for the provision of RPDDs 108 with RPDDMs 102, RPMs 104 or other entities.

FIG. 15 illustrates a flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation. The flow diagram in Figure 15 may be implemented, for example, by a system such as shown in Figure 14.

With respect to system 1400, RPC 1 14 may get to a point where RPDD 108 seeks payment - after, just before, or simultaneous to, regulator 1 10b and/or RPDD 108 approving or authorizing the dispensing. RPC 1 14 may then provide payment themselves (such as by providing cash or credit) or may instruct RPDD 108 to charge their RPP 1 12. When the retail payment (the payment received from RPC 1 14 or RPP 112) is provided then dispensing may occur. Alternatively RPDD 108 may not seek payment but may simply initiate payments after dispensing. Upon dispensing, a series of payment flows may occur depending on who owns the RPDD and whether it has been fully paid for, and who owns the RP and whether it has been fully paid for.

Assuming RPM 104 owns the RP in RPDD and RPDDM 102 owns RPDD 108, the following payment flows may occur: RPDDM receives a fractional fee (such as a RPDD transaction fee). This may be directed to RPDDM or, for example, a distributor that purchases RPDDs 108 from RPDDM; Regulator 1 10a and/or regulator 1 10b may receive a fee (a regulator fee) or may be paid, for example, by RPP 112 or RPDDM (or their distributor); RPM receives a fee for each RP dispensed (such as a wholesale price offered to RPDLP or RPDD; RPDLP may receive the remaining payment (retail payment); RPDD transaction fee - regulator fee - RP wholesale price per unit); or alternatively, RPDLP may receive a 'lease' fee for providing space, electricity and communication mechanisms for RPDD. In such case a larger portion of the retail payment may be directed to RPDDM or RPDDM distributor.

FIG. 16 illustrates a further flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation. The flow diagram in Figure 16 may be implemented, for example, by a system such as shown in Figure 14. Similar to the description of Figure 15, RPC 114 may get to a point where dispensing occurs from RPDD 108 and/or payment is sought. Upon dispensing, a series of payment flows may occur. In the payment flow of Figure 16, RPP 1 12 has purchased, up-front, RPDD 108 from RPDDM 102 and has also purchased RP from RPM 104 possibly both at wholesale prices. Payment flows, on dispensing, are therefore: Regulator 100b may receive a fee (a regulator fee) if they are remote from, or economically separate from, RPP 112; Note: RPP 1 12 may receive premiums to pay for their payments (if they are an insurer, for example, this may occur; or alternatively, regulator 1 10b may purchase RP from RPM 104. In such a case the regulator fee may further include a wholesale price per unit of RP.

Of course it is to be understood that other variations for distributing the payments (in addition to Figures 15-16 for system 1400) are possible in consideration of the business relationships entered into between these, and possibly other entities - providing the appropriate regulations are adhered to. These variations may also further the objective of making RP more accessible.

FIG. 17 illustrates a generalized flow diagram of payments in a product dispensing method and system in accordance with a non-limiting implementation. The flow diagram in Figure 17 may be implemented, for example, by a system such as shown in Figures 9, 1 1, or 14.

Method 1700 may be used to determine what payments are required after substantially any dispensing of an RP, from any type of dispenser. Parts of method 1700 may be implemented by one or more aspects of one or more of the systems herein. In addition, there may be a controlling entity or aspect, such as RPDS 118, that may control the overall functioning of the payments. As such, method 900 may be implemented within RDPS 118 so that substantially any dispensing, and substantially any payment arrangement, can be accommodated.

Method 1700 begins at 902 where a determination of the party that is paying for the RP. That may be RPP 112, RPC 114, or some other party. At 904 a dispenser is selected. The dispenser may be RPD 116, or RPDD 108 (either at RPC 1 14 or RPDLP 106), or may be another dispenser. At 906 regulatory approval may be sought. If the regulator (such as regulator 1 10b) does not approve or authorize the dispensing that method 900 may end. Also at 906, RPP 112 approval may be sought, if they are paying for the RP. They may withhold authorization, for example, if the RP that RPC 1 14 is attempting to obtain is not covered by RPP's 1 12 insurance coverage for RPC 1 14. If authorization is received then method 900 continues at 908. If a retail payment (the amount paid by one or more of RPC 114 and RPP 1 12 for the RP) is not received by the dispenser then method 900 may end. If payment is received then the payment flows may continue.

At 910 a query is made whether the dispenser is RPDD 108. If not then the dispenser is likely a RPD 116 and method 900 continues at 912 to determine whether regulator (such as regulator 110b) has been paid. In one example, RPD 1 16 may have onsite regulators that are salaried employees. In such a case, regulator may not need to be paid based on the dispensing and method 900 continues at 916. However, if they are not salaried, or if they are outsourced in some fashion (such as being remote) then a fee is paid to them at 914 before method 900 continues to 916.

At 916 a query is made whether RPM has already been paid for the RP. If RPD 106 purchased RP up-front then the response is yes. If RPD 106, who is likely receiving the retail payment, does not own the RP then a portion of the retail payment likely needs to be re-directed at 916. At 918 a wholesale price (or some agreed upon portion of RP) is provided to RPM or any other entity that substantially owns RP.

This branch of method 1700 then ends at 920 with the remaining amount from the retail RP payment is kept by RPD 106.

Returning to 910, if the dispenser is RPDD then method 1700 continues to 922 to determine whether RPDD is RPC-proximate. This determination may invoke, suggest, or require differences in the number, nature, or existence of the various transaction fees or tariffs described herein.

Method 1700 continues at 924. Method 1700 at 924, 926, 928, and 930 (until it reaches 932) is substantially similar to 912, 914, 916, 918.

At 932 a determination is made whether RPDDM has already been paid for RPDD? If not then a transaction fee is paid to RPDDM. This determination may include whether the full purchase price has been paid and/or whether an on-going transaction fee is to be provided. If RPDDM 102 has been fully paid, or the relevant RPDDM fee is paid at 934, then method 900 continues at 936.

As with all fees, payments, transaction levies, or other distributions of portions of the retail payment, payment may be effected electronically or with physical payment (cash or check, etc.) One or more of the entities in system 100 may be part of electronic transactions or payments. In one example, regulator 110b, RPM 102, and RDDPM 104 all have PayPal accounts, or other electronically accessible accounts, that RPD 116 or RPDD 106 can deposit payment to in response to dispensing occurring. Further, any of the fees (regulator fee, RPM fee, RPDDM fee, RPD fee, etc.) may be transaction-based, tied to ownership of involved assets (RP, RPDDM, location of RPDDM or RPD, etc.), or may be tied to on-going revenue streams resulting from on-going dispensing of RP.

Although aspects of the invention were described largely with respect to medication as the RP, many other RP may be applicable.

In a further example, alcohol may be the RP. The regulators are government and retailers that assure that purchasers are the required age. In some jurisdictions, for example, only 18 year olds and older may purchase alcohol but anyone can sell alcohol if they have gone through the proper registration. In other jurisdictions, only 19 year olds and older may purchase alcohol and only government-run stores can sell alcohol. In either situation, systems and methods as described herein may be used: System 1 100 may be used. Alcohol may be stored in RPDD 108 at RDPLP 106. This may be particularly useful where RPDLP would not be allowed to sell alcohol through its own store. When RPC 1 14 desires alcohol they would visit RPDLP. Selecting a particular product from RPDD 108 would lead RPDD 108 to confirm whether the person was old enough to purchase alcohol. This may involve RPC 114 providing their ID to RPDD 108. A regulator 110, such as an age verifier, a government official, a police officer, etc., may be available to RPDD 108 where the ID may not match the person presenting themselves to RPDD 108. Once dispensing is determined to be appropriate, RPC 114 may provide payment to RPDD 108. Upon dispensing payments may be made to the parties having interest in the transaction, as may be described in Figures 4 and 5. Such an approach may allow a government to make RP available in more remote locations without relinquishing control of the dispensing.

In a further example, stickers for disabled parking may be the RP. The regulators are government officials that assure RPC 1 14 have a qualifying disability. Systems and methods as described herein may be used: System 1100 may be used. Stickers may be stored in RPDD 108 at RDPLP 106. When RPC 114 requires a sticker they would visit RPDLP. RPDD 108 may query RPC 114 what their disability they have and what sticker they require (perhaps a sticker with a two-week duration, or that will last until they have given birth, etc.) RPDD 108 would then attempt to confirm whether the person was entitled to the sticker. This may involve accepting a doctor's note or disability form, or other form of proof. A regulator 1 10, such as a doctor or a government official may be available to RPDD 108 where RPDD 108 cannot conclusively determine entitlement. Upon dispensing payments may be made to the parties having interest in the transaction, as may be described in Figures 12-13. Such an approach may allow a government to make RP available in more remote locations without relinquishing control of the dispensing.

System 1400 may be used, for example, for a remotely-located RPC 114 having a recurring need for a sticker.

It should be understood implementations can be in the form of control logic, in a modular or integrated manner, using software, hardware or a combination of both. The steps of a method, process, or algorithm described in connection with the implementations disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two.

The various steps or acts in a method or process may be performed in the order shown, or may be performed in another order. Additionally, one or more process or method steps may be omitted or one or more process or method steps may be added to the methods and processes. An additional step, block, or action may be added in the beginning, end, or intervening existing elements of the methods and processes. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods for various implements.

It is further understood that the examples and implementations described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims.