VAPORIZATION DEVICE

Abstract

A system and method for practitioner tracking of patient substance intake and controlling of substance dosing for patients is provided. A controlled dosing platform displays patient profiles under the practitioner's care and upon selecting a particular patient one or more streams of usage statistics from use of a vaporization device is displayed. The usage statistics may include a regression value, a control period and a quit date. The regression value may be a linear or an exponential regression value. The practitioner can manipulate any or all of the usage statistics to modify a smoking cessation plan.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 16/251,968, filed Nov. 18, 2018 which is incorporated by reference herein in its entirety for all purposes.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to a vaporization device and a system for implementing a smoking cessation plan utilizing the vaporization device.

BACKGROUND

Vaporizer devices have been frequently used as a cigarette replacement or as a means to wean users of cigarettes. For example, vaporizer devices may be a battery-operated device that is specially configured to mimic or simulate the feeling of smoking a cigarette. However, rather than burning actual tobacco, the vaporizer device is configured to burn a liquid solution, thereby creating a vapor inhalable by the user. Such liquid solutions may include a nicotine-containing substances similar to that of cigarettes.

SUMMARY

Embodiments disclosed herein generally relate to a system and method for facilitating a smoking cessation plan. In some embodiments, a vaporization device is disclosed herein. The vaporization device includes a first portion and a second portion. The second portion is selectively coupled with the first portion. The first portion includes a first body, a first half of a split-pod, a second half of a split-pod, an opening, a first heating apparatus, and a second heating apparatus. The first body defines a first interior volume. The first half of the split-pod and the second half of the split-pod are formed in the first interior volume. The first half of the split-pod is configured to hold a nicotine-containing liquid. The second half of the split-pod configured to hold a non-nicotine-containing liquid. The opening is formed in the first body. The opening separates the first half of the split-pod from the second half of the split-pod. The first heating apparatus is dedicated to the first half of the split-pod. The second heating apparatus is dedicated to the second half of the split-pod. The second portion includes a second body and a computing system. The second body defines a second interior volume. The computing system is disposed within the second interior volume. The computing system is configured to vary an amount of current supplied to the first heating apparatus and the second heating apparatus.

In some embodiments, a smoking cessation system is disclosed herein. The smoking cessation system includes a vaporization device and a server system. The vaporization device includes a first half of a split-pod and a second half of a split-pod. The first half of the split-pod is configured to hold a nicotine-containing liquid. The second half of the split-pod is configured to hold a non-nicotine-containing liquid. The vaporization device is configured to deliver a vapor mixture. The vapor mixture includes a first vapor formed from the non-nicotine-containing liquid and a second vapor formed from the nicotine-containing liquid. The server system is in communication with the vaporization device. The server system is configured to generate a smoking cessation plan for the vaporization device based on at least usage statistics associated with the vaporization device.

In some embodiments, a computer-implemented method of facilitating a smoking cessation plan is disclosed herein. A server system generates an initial smoking cessation plan based on one or more inputs provided by a client device in communication with a vaporization device. The initial smoking cessation plan includes one or more phases. Each phase is associated with a predefined ratio of a vapor mixture for the vaporization device to deliver to a user. The server system transmits the initial smoking cessation plan to the client device. The server system receives one or more streams of usage statistics associated with the user's use of vaporization device. The server system analyzes the one or more streams of usage statistics to determine whether the user's use of vaporization device is in accordance with the initial smoking cessation plan. The server system determines that the user's use of the vaporization device deviates from the initial smoking cessation plan. The server system modifies the initial smoking cessation plan based on the usage statistics.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrated only typical embodiments of this disclosure and are therefore not to be considered limiting of its scope, for the disclosure may admit to other equally effective embodiments.

FIG. 1 is a block diagram illustrating a computing environment, according to example embodiments.

FIG. 2 is a perspective view of a vaporization device, according to example embodiments.

FIG. 3A is a cross-sectional view of first portion of vaporizer device, according to example embodiments.

FIG. 3B is an exploded view of first portion of vaporizer device, according to example embodiments.

FIG. 3C is a cross-sectional view of first portion of vaporizer device, according to example embodiments.

FIG. 4A is a cross-sectional view of second portion of vaporizer device, according to example embodiments.

FIG. 4B is a cross-sectional view of second portion of vaporizer device, according to example embodiments.

FIG. 5 is a partial cross-sectional view of a vaporization device, according to example embodiments.

FIG. 6 is a perspective view of vaporization device, according to example embodiments.

FIG. 7A is a block diagram illustrating a method of generating a smoking cessation plan, according to example embodiments.

FIG. 7B is a block diagram illustrating one or more operations associated with use of vaporization device, according to example embodiments.

FIG. 8A is a block diagram illustrating a graphical user interface, according to example embodiments.

FIG. 8B is a block diagram illustrating a graphical user interface, according to example embodiments.

FIG. 9 is a block diagram illustrating a computing environment, according to example embodiments.

FIG. 10A is a block diagram illustrating a computing device, according to example embodiments.

FIG. 10B is a block diagram illustrating a computing device, according to example embodiments.

FIG. 11 is a perspective view of a vaporization device, according to example embodiments.

FIG. 12A is a perspective view of a vaporization device, according to example embodiments.

FIG. 12B is a perspective view of a vaporization device from an opposite view of that shown in FIG. 12A.

FIG. 13 is a perspective view of a cross-sectional view of first portion of vaporizer device, according to example embodiments.

FIG. 14A is a cross-sectional view of first portion of vaporizer device, according to example embodiments.

FIG. 14B is an exploded view of first portion of vaporizer device, according to example embodiments.

FIG. 15A is an end view of first portion of vaporizer device, according to example embodiments.

FIG. 15B is a perspective end view of first portion of vaporizer device, according to example embodiments.

FIG. 16 shows a screenshot of a portal used with a controlled dosing platform of the present invention.

FIGS. 17A& 17B shows a screenshot of a user profile associated with the controlled dosing platform of the present invention.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one embodiment may be beneficially utilized on other embodiments without specific recitation.

DETAILED DESCRIPTION

One or more embodiments disclosed herein generally relate to a vaporization device and a system for implementing a smoking cessation plan utilizing the vaporization device. The vaporization device may include a first portion that is selectively coupled to a second portion. The first portion may include a body. The body may include a split-pod configuration. For example, the body may include a split-pod with the first half of the split-pod configured to hold a nicotine-containing substance and a second half of the split-pod configured to hold a non-nicotine-containing substance. Each half of the split-pod may include a respective heating apparatus, configured to create a vapor mixture from the nicotine-containing substance and the non-nicotine-containing substance. The second portion may include a computing system disposed therein. The computing system may be configured to vary the amount of current provided to each respective heating apparatus, such that a predefined ratio of nicotine-containing substance to non-nicotine-containing substances is delivered to the user. Such ratio may be generated as part of an overall smoking cessation plan stored on the vaporization device.

The vaporization device may be configured to communicate with a user's client device (e.g., mobile phone). For example, vaporization device may provide client device with the user's usage statistics. Such usage statistics may include a number of uses of vaporization device, as well as the duration of each use. Client device may provide the usage statistics to a server system. The server system may adjust the smoking cessation plan based on the usage statistics provided by the client device. For example, if a user is too heavily relying on the vaporization device (e.g., higher usage rate than expected), the server system may adjust the smoking cessation plan accordingly, FIG. 1 is a block diagram illustrating a computing environment 100, according to example embodiments. Computing environment 100 may include vaporization device 102, organization computing system 104, and client device 106 communicating via network 105.

Network 105 may be of any suitable type, including individual connections via the Internet, such as cellular or Wi-Fi networks. In some embodiments, network 105 may connect terminals, services, and mobile devices using direct connections, such as radio frequency identification (RFID), near-field communication (NFC), Bluetooth™, low-energy Bluetooth™ (BLE), Wi-Fi™, ZigBee™, ambient backscatter communication (ABC) protocols, USB, WAN, or LAN. Because the information transmitted may be personal or confidential, security concerns may dictate one or more of these types of connection be encrypted or otherwise secured. In some embodiments, however, the information being transmitted may be less personal, and therefore, the network connections may be selected for convenience over security.

Network 105 may include any type of computer networking arrangement used to exchange data. For example, network 105 may include any type of computer networking arrangement used to exchange information. For example, network 105 may be the Internet, a private data network, virtual private network using a public network and/or other suitable connection(s) that enables components in computing environment 100 to send and receive information between the components of environment 100.

Client device 106 may be operated by a user. For example, client device 106 may be a mobile device, a tablet, a desktop computer, or any computing system having the capabilities described herein. Client device 106 may belong to or be provided to a user or may be borrowed, rented, or shared. Users may include, but are not limited to, individuals such as, for example, subscribers, clients, prospective clients, or customers of an entity associated with organization computing system 104, such as individuals who have obtained, will obtain, or may obtain a product, service, or consultation from an entity associated with organization computing system 104.

Client device 106 may include at least application 112. Application 112 may be representative of a web browser that allows access to a website or a stand-alone application. Client device 106 may access application 112 to access functionality of organization computing system 104. Client device 106 may communicate over network 105 to request a webpage, for example, from web client application server 114 of organization computing system 104. For example, client device 106 may be configured to execute application 112 to access content managed by web client application server 114. The content that is displayed to client device 106 may be transmitted from web client application server 114 to client device 106, and subsequently processed by application 112 for display through a graphical user interface (GUI) of client device 106.

Client device 106 may communicate with vaporization device 102. For example, client device 106 may communicate with vaporization device 102 via network 105. Vaporization device 102 may be a split-pod vaporization device configured to deliver a vapor mixture formed from a nicotine-containing substance and a non-nicotine-containing substance. Vaporization device 102 is discussed in further detail below in conjunction with FIGS. 2-6.

Vaporization device 102 may include computing system 110. Computing system 110 may be configured to communicate with client device 106. In some embodiments, computing system 110 may be further configured to communicate with organization computing system 104. Computing system 110 may be configured to track user of vaporization device 102 may an end user. For example, computing system 110 may track a number of uses of vaporization device 102 and a duration of each user. In some embodiments, vaporization device 102 may transmit the usage information to client device 106. Client device 106 may, in turn, transmit the usage information to organization computing system 104. In some embodiments, vaporization device 102 may transmit usage information directly to organization computing system 104.

Organization computing system 104 may include at least web client application server 114, a machine learning module 116, a cessation module 118, and handler 120. Each of machine learning module 116, cessation module 118, and handler 120 may be comprised of one or more software modules. The one or more software modules may be collections of code or instructions stored on a media (e.g., memory of organization computing system 104) that represent a series of machine instructions (e.g., program code) that implements one or more algorithmic steps. Such machine instructions may be the actual computer code the processor of organization computing system 104 interprets to implement the instructions or, alternatively, may be a higher level of coding of the instructions that is interpreted to obtain the actual computer code. The one or more software modules may also include one or more hardware components. One or more aspects of an example algorithm may be performed by the hardware components (e.g., circuitry) itself, rather as a result of the instructions.

Cessation module 118 may be configured to communicate with client device 106. In some embodiments, cessation module 118 may be configured to communicate with vaporization device 102. Cessation module 118 may receive usage information from vaporization device 102. Cessation module 118 may work in conjunction with machine learning module 120 to generate a smoking cessation plan for each user based, in part, on user input and usage information. For example, cessation module 118 may work in conjunction with machine learning module 120 to generate a cessation plan that includes a ratio of nicotine-containing substance to non-nicotine-containing substance to deliver to a user. Based off received usage information, cessation module 118 may work in conjunction with machine learning module 120 to update the cessation plan for each user.

Machine learning module 116 may include one or more instructions to train a prediction model used by cessation module 118. To train the prediction model, machine learning module 120 may receive, as input, usage activity of each user. In some embodiments, machine learning module 120 may further receive, as input, one or more parameters specified by each user via application 112. Machine learning module 116 may implement one or more machine learning algorithms to train the prediction model. For example, machine learning module 116 may use one or more of a decision tree learning model, association rule learning model, artificial neural network model, deep learning model, inductive logic programming model, support vector machine model, clustering mode, Bayesian network model, reinforcement learning model, representational learning model, similarity and metric learning model, rule based machine learning model, and the like.

Account handler 120 may be configured to manage an account associated with each user. For example, account handler 120 may be configured to communicate with database 108. As illustrated, database 108 may include one or more user profiles 124. Each user profile 124 may correspond to a user with an account with organization computing system 104. Each user profile 124 may include at least one or more of personal identification information 126, a cessation plan 128, and statistics 130. Personal identification information 126 may include information associated with the user. In some embodiments, personal identification information 126 may include a name, home address, billing address, mailing address, telephone number, e-mail address, social security number, and the like. Cessation plan 128 may correspond to a cessation plan generated for each user by cessation module 118 and machine learning module 116. Cessation plan 128 may include one or more phases, wherein each phase of cessation plan 128 may include a specific ratio of nicotine-containing substance to non-nicotine-containing substance in a vapor mixture as well as a duration for each phase. Statistics 130 may include one or more statistics associated with a user's usage. Such statistics may include usage information tracked by computing system 110.

FIG. 2 is a perspective view of a vaporization device 200, according to example embodiments. Vaporization device 200 may be an example of vaporization device 102 discussed above, in conjunction with FIG. 1. As illustrated, vaporization device 200 may include a first portion 202 and a second portion 204. First portion 202 may be selectively coupled with second portion 204.

First portion 202 may generally include a first end 206 and a second end 208, opposite first end 206. First end 206 may include an opening 218 formed therein. In some embodiments, first portion 202 may taper from second end 208 to first end 206. As discussed in further detail below, first portion 202 may be configured to store one or more fluids used for delivery of a vapor mixture to users of vaporization device 200. For example, first portion 202 may be configured to store at least two liquids: a non-nicotine containing liquid and a nicotine containing liquid. In operation, a vapor mixture formed from at least a portion of the non-nicotine containing liquid and the nicotine containing liquid may be delivered to user of vaporization device 200.

First portion 202 may be formed from a thermoplastic material (e.g., high-temperature thermoplastic material). Generally, first portion 202 may be formed from a food-safe, chemical (e.g., oil) resistant material. Exemplary materials may include, but are not limited to, nylon-based plastic (or equivalent), polyphenylene sulfide (PPS), polyether ether ketone (PEEK), polyetherimide (PEI), and the like.

Second portion 204 may generally include a first end 210 and a second end 212, opposite first end. Although not shown in this particular figure, second end 212 may include a charging slot formed therein. Exemplary charging slots may include, but are not limited to, universal serial bus (USB) port, lightening port, and the like. As discussed in further detail below, second portion 204 may be configured to house one or more electronic components of vaporizer device 202.

Second portion 204 may be formed from extruded aluminum alloy, a material having an anodized or powder coating, and the like.

As illustrated in FIG. 2, when in selective communication, first portion 202 may create an interface 214 with second portion 204. Interface 214 may not be uniform about vaporizer device 210. For example, formed between first portion 202 and second portion 204 may be one or more air passages 216. Each air passage 216 may allow air to flow from outside vaporizer device 200 to an interior volume defined therein. For example, when a user inhales via opening 218, air may be pulled within vaporizer device 200 via one or more air passages 216.

Generally, first portion 202 may be configured as a disposable component of vaporizer device 102. For example, first portion 202 may be disposed by end user when first portion 202 no longer contains at least one of a nicotine-containing substance or a non-nicotine-containing substance. However, rather than having the user physically refill first portion 202, the user may purchase a new first portion 202 for use with vaporizer device 102.

In some embodiments, first portion 202 may be self-destructing. In other words, first portion 202 may be configured such that a user cannot tamper with first portion 202 (e.g., re-fill or re-use first portion 202, take liquid out of first portion 202, etc.).

FIG. 3A is a cross-sectional view of first portion 202 of vaporizer device 200, according to example embodiments. First portion 202 may include a body 302. Body 302 may include a first region 301 and second region 303. First region 301 may include a split-pod formed therein. For example, first region 301 may include a first half of a split-pod 304a and a second half of a split-pod 304b. First half the pod 304a may be separated from second half of the split-pod 304b via opening 118, which may extend from first end 206 of first portion 202 to second region 303. Both first half of the split-pod 304a and second half of the split-pod 304b may be configured to hold a liquid. For example, first half of the split-pod 304a may be configured to hold a nicotine-containing liquid; second half of the split-pod 304b may be configured to hold a non-nicotine-containing liquid.

Second portion 303 of body 302 may include one or more electric contacts 308 and one or more heating coils 310. In some embodiments, each of one or more heating coils 308 may be positioned adjacent a respective half of the split-pod 304a, 304b. For example, second portion 303 of body 302 may include a first heating coil 310 dedicated to first half of the split-pod 304a and a second heating coil 310 dedicated to second half of the split-pod 304b. Each heating coil 310 may be configured to heat the liquid contained in a respective half of the split-pod 304a, 304b to create a vapor mixture. Each heating coil 310 may be formed from a metal material that is used for resistive heating. Exemplary metal materials may include, but are not limited to, Nichrome, KANTHAL®, stainless steel, and the like.

Each electrical contact 308 may be configured to deliver power to each heating coil 310. For example, each electric contact 308 may be configured to deliver a defined amount of power to each coil 308, such that a specific ratio of non-nicotine-containing liquid to nicotine-containing liquid is vaporized. In some embodiments, each electrical contact 308 may be positioned adjacent a respective half of the entire split-pod 304a, 304b. For example, second portion 303 of body 302 may include a first electrical contact 308 dedicated to a first heating coil 310 for first half of the split-pod 304a and a second electrical contact 308 dedicated to a second heating coil 310 for the second half of the split-pod 304b.

As illustrated, each electrical contact 308 may be configured to support a respective heating coil 310. For example, each electric contact 308 may include an opening (not shown) formed therein. Electrical coil 310 may at least partially extend within the opening, such that electrical coil 310 may be supported by electrical contact 308.

Body 302 may further include one or more divider walls 306. Each of divider wall 306 may be positioned in such a way as to separate each heating coil 310 from a respective half of the split-pod 304a, 304b. For example, as illustrated, a first divider wall 306 may be positioned between first half of the split-pod 304a and first heating coil 310 and a second divider wall 306 may be positioned between second half of the split-pod 304b and second heating coil 310. Each divider wall 306 may include an opening (not shown) formed therein. Each opening may be formed as to allow passage of a wicking material between each half of the split-pod 304a, 304b and a respective heating coil 310. Wicking material may be used to deliver fluid from a respective half of the split-pod 304a, 304b to a respective heating coil 310. Exemplary wicking materials may include, but are not limited to, silica, cotton, or other porous materials).

Body 302 may further include a mixing chamber 316, one or more vapor vents 312, and one or more air vents 314 formed therein. Mixing chamber 316 may be defined within second region 303. Mixing chamber 316 may be in fluid communication with opening 218. For example, mixing chamber 316 may be formed in second region 303, such that mixing chamber 316 may separate each respective set of electrical contacts 308 and heating coils 310. Each vapor vent 312 may be formed within an interior of first portion 202. For example, each vapor vent 312 may be formed proximate a respective heating coil 310. In operation, vapor formed from fluid in one half of the split-pod 304a may enter mixing chamber 316 via a first vapor vent 312, and vapor formed from fluid in second half of the split-pod 304b may enter mixing chamber 316 via a second vapor vent 312. Within mixing chamber 316, vapor formed from a non-nicotine-containing fluid may mix with vapor formed from a nicotine-containing fluid to form a vapor mixture. The vapor mixture may be delivered to an end user via opening 218.

Each air vent 314 may be formed in body 302. For example, as illustrated, each air vent 314 may be formed such that each air vent 314 may provide fluid communication between an interior of body 302 and an exterior of body 302. One or more air vents 314 may be configured to draw ambient air into vaporizer device 200. For example, one or more air vents 314 may be configured to draw ambient air into vaporizer device 200 via one or more air passages 216, upon inhalation of an end user.

FIG. 3B is an exploded view of first portion 202 of vaporizer device 200, according to example embodiments. As discussed above, in some embodiments, first portion 202 may be self-destructing. In other words, first portion 202 may be configured such that a user cannot tamper with first portion 202 (e.g., re-fill or re-use first portion 202, take liquid out of first portion 202, etc.).

As illustrated, first region 301 is shown detached from second region 303. Between first region 301 and second region 303 are one or more divider walls 306 and heating coils 310. To configure first portion 202 such that first portion 202 is tamper-proof, a sealant 350 may be used to couple first region 301 to second region 303. In some embodiments, sealant 350 may be applied to first region 301, such that after first region 301 and second region 303 are attached, sealant 350 prevents disassembly of second region 303 from first region 301. Sealant 350 may be any sealant able to prevent fluid leakage from first region 301. Exemplary sealants may include, but are not limited to silicon, epoxy, a combination of the two, or any other suitable material.

FIG. 3C is a front perspective view of first portion 202 of vaporizer device 200, according to example, embodiments. As discussed above, in some embodiments, first portion 202 may be self-destructing. In other words, first portion 202 may be configured such that a user cannot tamper with first portion 202 (e.g., re-fill or re-use first portion 202, take liquid out of first portion 202, etc.).

As illustrated, first region 301 is shown attached to second region 303. Second region 303 may include one or more internal snap hooks 370 integrated therein. As illustrated each of the one or more internal snap hooks 370 may secure second region 303 to first region 301 by interfacing with one or more internal walls 372 of first region 301. As such, use of one or more internal snap hooks 370 may result in a single-use first portion 202 (i.e., single-use pod). In some embodiments, first portion 202 may implement a combination of one or more snap hooks 370 and sealant 350 to prevent tampering with first region 301.

FIG. 4A is a cross-sectional view of second portion 204 (FIG. 5) of vaporizer device 200, according to example embodiments. Second portion 204 may include a body 402. Body 402 may include a first region 401 and second region 403. First region 401 may be configured to receive first portion 202 (FIG. 5) of vaporizer device 200. For example, when selectively coupled, second region 303 of first portion 202 (FIG. 5) of vaporizer device 200 may be positioned at least partially within first region 401 of second portion 204 of vaporizer device 200.

Second region 403 may define interior volume 404. Disposed within interior volume 404 may be at least computing system 110. Computing system 110 may include a printed circuit board 406 and a power source 408. Printed circuit board 406 may include at least one or more of power control circuitry, current sensing circuitry, voltage sensing circuitry, charging interface, battery charging circuity, network interface (e.g., radio frequency identification (RFID) module, near-field communication (NFC) module, Bluetooth™ module, low-energy Bluetooth™ (BLE) module, Wi-Fi™ adapter, ZigBee™ module, etc.), microcontroller, and one or more safety mechanisms.

Microcontroller may be configured to communicate with a remote computing server. For example, microcontroller may be configured to communicate user consumption information to a remote computing server and receive, from the remote computing server, dosage instructions. The dosage instructions (described in further detail below) provide the microcontroller with instructions directed to a target temperature of each heating coil 310 and a duration each heating coil 310 is heated. The dosage instructions may be a part of a larger cessation plan generated by remote computing server.

Microcontroller may instruct the power control circuitry regarding the amount of power to be provided to one or more electrical contacts 308. Power control circuitry may be configured to control the amount of power provided by power source 408 to one or more electrical contacts 308. For example, temperature of heating coils 310 may be measured using the resistance change of the coil, and implementing a feedback loop with the microcontroller to adjust the power output to meet the target temperature (e.g., proportional-integral-derivative (PID) control loop). In some embodiments, power control circuitry may be a metal oxide silicon field effect transistor (MOSFET). The amount of power provided by power source 408 to each electrical contact 308 affects the amount of vapor produced by first portion 202 of vaporizer device 200. In some embodiments, power source 408 may be a re-chargeable battery (e.g., 3.7 V battery).

In some embodiments, microcontroller may use a regression-based algorithm programmed locally on each device, which may be loaded to microcontroller via application 112 executing on client device 106 associated with vaporization device 200. The regression-based algorithm may include instructions on how and when to reduce a user's nicotine intake. In some embodiments, for each user, there may be a control period in which organization computing system 104 learns and understands a user's smoking behaviors. For example, organization computing system 104 may learn the amount of time, milligrams of nicotine taken per day, and the number of times vaporization device 200 is used. This data may be used to design each user's cessation plan.

The formula for each users cessation plan is calculated using: D_n=D0* e^(tn_t0_c)*k

For each user, the variables that are stored may be:

Start date (t0)—this may represent the date when the user started the smoking cessation program.

k—this may represent a constant that will be used to control how steep the regression will be for the patient. k may be a negative value. For example, k may be in the range between about −0.05 and −0.5. The higher the absolute value, the steeper the regression of the nicotine, and the quicker the patient will quit smoking. In some embodiments, the default value of k may be about −0.2.

Control period (c)—this may represent the length of the initial period, during which no regression takes place, but the patient's current smoking habits are being monitored. In some embodiments, the maximum nicotine dose may be applied during each hit.

After the control period, the following values may be calculated:

Average initial daily dose (D0)—this may represent the average daily nicotine dose during the control period, calculated from the hits made during that period.

Current daily dose (D_n)—this may represent the daily nicotine dose for the n^th day (t_n).

This may be calculated using: D_n=D0*e^(tn_t0_c)*k

Average number of hits (h_n)—this may represent the average number of hits made per day during the program up until the n^th day (including the hits made during the control period).

Current hit dose (d_n)—this may represent the nicotine dose for the current hit, calculated

using the formula: d_n=D_n/h_n.

In some embodiments, the program may end when d_n falls below a threshold value (e.g., 0.005 mg). Adjustment of the k value would adjust the rate of regression.

FIG. 4A contains a printed circuit board 406 may further include one or more contacts 410 coupled thereto. As illustrated, one or more contacts 410 may take the form of a pin-shaped contact. In some embodiments, one or more contacts 410 may be soldered to printed circuit board 406. One or more contacts 410 may be configured to contact each electrical contact 308, when first portion 202 and second portion 204 are in selective communication. One or more contacts 410 may be configured to transfer current provided by battery 408 to one or more electrical contacts to raise a temperature of one or more heating coils 308. In some embodiments, each contact 410 may be spring actuated to ensure solid contact with each electrical contact 308.

Further, although not shown, in some embodiments, second portion 204 may include a fingerprint sensor located on an exterior surface of body 402. Fingerprint sensor may be in communication with computing system 110. For example, when a user wants to use vaporization device 102, the user may unlock vaporization device 102 using fingerprint sensor located thereon. FIG. 4B is a partial cross-sectional view of vaporization device 200, according to example embodiments. As illustrated, first portion 202 is selectively coupled to second portion 204. In some embodiments, such as that shown in FIG. 5, second portion 204 may include one or more pressure sensors 450a, 450b (generally, “pressure sensor 450”) disposed therein. For example, second portion 204 may include a first pressure sensor 450a selectively positioned in the path of airflow during inhalation and a second pressure sensor 450b placed in the main housing. First pressure sensor 450a may be positioned in second portion 204, such that first pressure sensor 450a is exposed to airflow during inhalation as a result of the pressure drop in interior volume 404.

Second pressure sensor 450b may be configured to observe atmospheric pressure. Second pressure sensor 450b may be used in conjunction with first pressure sensor 450b to determine the differential pressure between atmosphere and that of the inhalation path. By doing so, accuracy is improved, most notable in situations when vaporization device 200 is taken to locations with different atmospheric pressures.

FIG. 5 is a partial cross-sectional view of a vaporization device 200, according to example embodiments. As illustrated, first portion 202 is selectively coupled to second portion 204. Second region 303 of first portion 202 may be positioned at least partially within first region 401 of second portion 204. In some embodiments, mating between first portion 202 and second portion 204, via second region 303 and first region 401, may be secured via natural friction, a lever tab, a snap hook, a magnet, and the like. When selectively coupled, one or more contacts 410 may be in physical contact with one or more electrical contacts 308.

FIG. 6 is a perspective view of vaporization device 200, according to example embodiments. As illustrated, first portion 202 is detached from second portion 204. As may not have been visible in previous Figures, another view of first region 301 and second region 303 of first portion 202 is shown. Further, as previously recited but now shown in detail, second portion 204 may include changing slot 602 formed in second end 212 of second portion 204. Exemplary charging slots may include, but are not limited to, universal serial bus (USB) port, lightening port, and the like.

FIG. 11 is a perspective view of a vaporization device 1100, according to example embodiments. Vaporization device 1100 may be an example of vaporization device 102 discussed above, in conjunction with FIG. 1. As illustrated, vaporization device 1100 may include a first portion 1102 and a second portion 1104. First portion 1102 may be selectively coupled with second portion 1104. First portion 1102 may include an opening 1118 formed therein.

As discussed in further detail below, first portion 1102 may be configured to store one or more fluids used for delivery of a vapor mixture to users of vaporization device 1100. For example, first portion 1102 may be configured to store at least two liquids: a non-nicotine containing liquid and a nicotine containing liquid. In operation, a vapor mixture formed from at least a portion of the non-nicotine containing liquid and the nicotine containing liquid may be delivered to user of vaporization device 1100.

As discussed in further detail below, second portion 1104 may be configured to house one or more electronic components of vaporizer device 1102. When in selective communication, first portion 1102 may create an interface with second portion 1104. Interface 1102 may not be uniform about vaporizer device 1110. For example, formed between first portion 1102 and second portion 1104 may be one or more air passages 1116. Each air passage 1118 may allow air to flow from outside vaporizer device 1100 to an interior volume defined therein. For example, when a user inhales via opening 1118, air may be pulled within vaporizer device 1100 via one or more air passages 1116.

First portion 1102 may include a body 1104. Body 1104 may include a split-pod formed therein. For example, body 1152 may include a first half of a split-pod 1154a and a second half of a split-pod 1154b. First half the pod 1154a may be separated from second half of the split-pod 1154b via opening 1118, which may extend through first portion 1102. Both first half of the split-pod 1154a and second half of the split-pod 1154b may be configured to hold a liquid. For example, first half of the split-pod 1154a may be configured to hold a nicotine-containing liquid; second half of the split-pod 1154b may be configured to hold a non-nicotine-containing liquid.

Body 1152 may further include one or more electrical contacts 1158, a heating coil 1160, and a wick mechanism 1162. In some embodiments, heating coil 1160 may be positioned proximate each half of the split-pod 1154a, 1154b. For example, heating coil 1160 may be positioned between first half of split-pod 1154a and second half of split-pod 1154b. In some embodiments, heating coil 1160 may be positioned about wick mechanism 1162. For example, heating coil 1160 may be wrapped around wick mechanism 1162. Heating coil 1160 may be configured to heat the liquid contained in each respective half of the split-pod 304a, 304b to create a vapor mixture. Heating coil 1160 may be formed from a metal material that is used for resistive heating. Exemplary metal materials may include, but are not limited to, Nichrome, KANTHAL®, stainless steel, and the like.

Each electrical contact 1158 may be configured to deliver power to heating coil 1160. For example, each electric contact 1158 may be configured to deliver a defined amount of power to each coil 308, such that a specific amount of liquid is vaporized.

Body 1152 may further include one or more air vents 1164. Each air vent 1164 may be formed in body 1152. For example, as illustrated, each air vent 1164 may be formed such that each air vent 1164 may provide fluid communication between an interior of body 1152 and an exterior of body 1152. One or more air vents 1164 may be configured to draw ambient air into vaporizer device 1100.

Second portion 1104 may include a body 1172. Body 1172 may define interior volume 1174. Disposed within interior volume 1174 may be at least computing system 1180. Computing system 1180 may be substantially similar to computing system 110 discussed above in conjunction with FIG. 4A.

As illustrated, vaporization device 1100 may include one or more piston assemblies 1190a, 1190b (generally “piston assembly 1190”) that extends from first portion 1102 to second portion 1104. Each piston assembly 1190 may be configured to selectively deliver a dosage of liquid to a user of vaporization device 1100. Each piston assembly may include a rod 1192a, 1192b (generally “rod 1192”) which is configured to move linearly and a plate 1194a, 1194b (generally “plate 1194”) coupled to each rod 1192a, 1192b, respectively. As illustrated, piston assembly 1190a may be positioned within first half of split-pod 1154a. Piston assembly 1190a may extend from first half of split-pod 1154a into interior volume 1174 of second portion 1104. Piston assembly 1190b may be positioned within second half of split-pod 1154b. Piston assembly 1190b may extend from second half of split-pod 1154b into interior volume 1174 of second portion 1104.

In operation, computing system 1180 may control each piston assembly 1190, such that each rod 1192 may move linearly to control the amount of fluid provided to wick mechanism 1162. The distance each rod 1192 moves is translated to an amount of fluid provided to wick mechanism 1162. For example, the movement of rod 1192a down within first half of split-pod 1154a may push fluid in first half of split-pod 1154a down and out to wick mechanism 1162.

Computing system 1180 may control each piston assembly 1190 individually, such that a certain ratio of nicotine-containing fluid to non-nicotine-containing fluid is delivered to the user.

In operation, air may be drawn from outside of vaporization device 1100 via one or more air vents 1164, such that the air flows past heating coil 1160 and wick mechanism 1162, into opening 1118, and into the user's mouth.

FIG. 7A is a logical diagram illustrating a method 700 of generating a smoking cessation plan, according to exemplary embodiments. For example, method 700 of generating a smoking cessation plan may involve use of vaporization device 102 discussed above in conjunction with FIGS. 1-6. Method 700 may begin at step 702.

At step 702, client device 702 may access organization computing system 104 to initialize a smoking cessation plan. For example, client device 702 may access functionality of organization computing system 104 via application 112. In some embodiments, initializing a smoking cessation plan may include an end user to register a vaporization device 102 and enroll in a plan. Further, in some embodiments, initializing a smoking cessation plan includes client device 106 transmitting initializing information. Such initializing information may include, but is not limited to, a user's age, gender, smoking habits (e.g., how many times per day, how many packs per week, how long the user has smoked for, etc.), occupation, smoking cessation goals, and the like.

At step 704, organization computing system 104 may generate a smoking cessation plan for the user. In some embodiments, organization computing system 104 may generate a smoking cessation plan based on the initializing information. Cessation module 118 may leverage a prediction model generated by machine learning module 116 to generate a smoking cessation plan for the user. For example, cessation module 118 may provide one or more items of initializing information to prediction model to generate the smoking cessation plan. As such, the user's smoking cessation plan may be individualized to the user's attributes and goals. The smoking cessation plan may include one or more phases, such that each phase may include a specific ratio of nicotine-containing substance to non-nicotine-containing substance in a vapor mixture. Over time (e.g., as the user progress through the various phases), the ratio of substances within the vapor mixture may change, until a user is almost entirely consuming a vapor formed from the non-nicotine-containing substance.

At step 706, organization computing system 104 may transmit the smoking cessation plan to client device 106 of the user. In some embodiments, organization computing system 104 may provide client device 106 with access to the smoking cessation plan via one or more application programming interfaces (APIs) that allow client device 106 to access the smoking cessation plan.

At step 708, client device 106 may communicate the smoking cessation plan to vaporizer device 102. For example, client device 106 may interface with computing system 110 in vaporization device 102, such that vaporization device 102 may store at least a portion of the smoking cessation plan in memory. The portion of the smoking cessation plan transmitted from client device 106 to computing system 110 may include instructions as to how much power to deliver to each heating coil 310. Accordingly, computing system 110 may control the amount of current provided by a battery source to each electrical contact 308.

At step 712 vaporization device 102 may deliver a vapor mixture formed from a predefined ratio of a nicotine-containing substance and a non-nicotine containing substance to the end user. For example, when a user attempts to consume a vapor mixture, computing system 110 may deliver a predefined amount of current to each electric contact 308 to heat each heating coil 310. Heating each heating coil 310 to a predetermined level aims in producing an amount of vapor from each half of the split-pod 304a, 304b, such that the predefine ratio is achieved.

At step 712, vaporization device 102 may transmit user data to client device 106. For example, vaporization device 102 may transmit usage statistics that include a number of inhalations and a duration for each inhalation to client device 106. In some embodiments, vaporization device 102 may transmit usage statistics in real-time (or near real-time), whenever vaporization device 102 is connected to client device 106 via one or more networks. In some embodiments, vaporization device 102 may transmit usage statistics in one or more batches. For example, vaporization device 102 may transmit usage statistics periodically (e.g., daily).

At step 714, client device 106 may forward the user data to organization computing system 104. For example, client device 106 may provide the user data to organization computing system 104, such that organization computing system 104 may analyze the user's usage of vaporization device 102, and update the smoking cessation plan accordingly.

At step 716, organization computing system 104 may receive the user data from client device 106. Organization computing system 104 may analyze the user date to determine whether the smoking cessation plan should be adjusted. For example, cessation module 118 may be configured to provide the user data, as input, to prediction model to determine whether the initial smoking cessation plan should be adjusted. Such adjustments may be made, for example, if the user is consuming more vapor mixture than previously expected. The adjustments may results in an extension of certain phases to the smoking cessation plan, such that the user is more slowly weaned off the nicotine-containing substance.

At step 718, organization computing system 104 may transmit the updated smoking cessation plan to client device 106 of the user. In some embodiments, organization computing system 104 may provide client device 106 with access to the updated smoking cessation plan via one or more APIs that allow client device 106 to access the updated smoking cessation plan.

At step 720, client device 106 may communicate the updated smoking cessation plan to vaporizer device 102. For example, client device 106 may interface with computing system 110 in vaporization device 102, such that vaporization device 102 may store at least a portion of the updated smoking cessation plan in memory. The portion of the smoking cessation plan transmitted from client device 106 to computing system 110 may include updated instructions as to how much power to deliver to each heating coil 310. Accordingly, computing system 110 may control the amount of current provided by a battery source to each electrical contact 308.

In some embodiments, logical diagram 700 may further include one or more steps 722-726. At step 722, client device 106 may access functionality of organization computing system 104 to access user statistics. For example, client device 106 may access application 112 to view usage statistics corresponding to vaporization device 102. Client device 106 may request access to usage statistics by requesting access via a log-in prompt. For example, via client device 106, a user may log into his or her account.

At step 724, organization computing system 104 may receive the request from client device 106 to view usage statistics corresponding to vaporization device 102 and the user's account. For example, upon receiving a request from client device 106, organization computing system 104 may generate one or more graphical user interfaces (GUIs) that visually display usage statistics to end user. Exemplary GUIs are discussed below in conjunction with FIG. 8.

At step 726, organization computing system 104 may provide client device 106 with access to the one or more GUIs. For example, in some embodiments, organization computing system 104 may transmit the one or more GUIs to client device 106 for rendering and display. In some embodiments, organization computing system 104 may provide client device 106 with access to the one or more GUIs via one or more APIs that allow client device 106 to access the one or more GUIs to display the usage statistics.

FIG. 7B is a block diagram 750 illustrating one or more operations associated with use of vaporization device 200, according to example embodiments. As shown, block diagram 750 includes a microcontroller 752, a network interface 754, a battery 756, a first power control 755, a second power control 760, a first heating coil 762, a second heating coil 764, a first temperature sensor 766, and a second temperature senor 768.

As illustrated, a user, via network interface 754, may update target values like temperature and time for vaporization device usage. Such target values may be input to microcontroller 752. Microcontroller 752 may determine the amount of power to be delivered from battery 756 to each heating coil 762, 764, based on the target values. First power controller 758 (e.g., first MOSFET) may control the amount of power provided to first heating coil 762, in accordance with instructions received from microcontroller 752. Second power controller 760 (e.g., second MOSFET) may control the amount of power provided to second heating coil 764, in accordance with instructions received from microcontroller 752. First temperature sensor 766 may monitor the temperature of first heating coil 762, and provide the temperature readings to microcontroller 752, thus creating a first feedback loop between microcontroller 752 and first heating coil 762. Second temperature sensor 768 may monitor the temperature of second heating coil 764, and provide the temperature readings to microcontroller 752, thus creating a second feedback loop between microcontroller 752 and second heating coil 764.

FIG. 8A is a block diagram illustrating an exemplary graphical user interface (GUI) 800, according to example embodiments. GUI 800 may be generated by organization computing system 104. Organization computing system 104 may provide GUI 800 to client device 106 via application 112. Client device 106 may render and display GUI 800.

GUI 800 may be representative of a smoking cessation initialization screen. For example, via GUI 800, users can provide input directed to the type of smoke the user is. GUI 800 may include one or more graphical elements 802. Each graphical element 802 may be representative of a category of smoker associated with the user. In some embodiments, a user may select multiple graphical elements 802 to provide organization computing system with a better overview of the user's smoking habits. Exemplary options may include, but are not limited to: long term smoker, heavy smoker, short term smoker, rarely, low smoker, menthol smoker, drunk smoker, social smoker, and the like.

FIG. 8B is a block diagram illustrating an exemplary graphical user interface (GUI) 830, according to example embodiments. GUI 830 may be generated by organization computing system 104. Organization computing system 104 may provide GUI 830 to client device 106 via application 112. Client device 106 may render and display GUI 830.

GUI 830 may be representative of a screen that provides the user with smoking cessation plan statistics. For example, GUI 830 may include one or more graphical elements 834, 836, 838, and 848. Graphical element 834 may correspond to statistics associated with a hit count (i.e., the number of times a user used vaporization device 102). Graphical element 836 may correspond to statistics associated with the user's nicotine intake (i.e., how much nicotine the user is inhaling from vaporization device 102). As illustrated, the user has selected graphical element 834 associated with hit count statistics.

Graphical element 838 may include one or more graphical elements 840-846 associated with graphical element 834. Graphical element 842 may allow the user to select a year for which to view statistics. Graphical element 840 may allow the user to select a month for which to view statistics. Graphical element 844 may include one or more statistics directed to how long the user has been on the smoking cessation plan. As illustrated, this particular user has been on the plan for 23 days. Graphical element 846 may include one or more statistics directed to the goal of the individual. For example, as illustrated, this particular user will be (or should be) nicotine free in 29 days, based on the generated smoking cessation plan.

Graphical element 848 may provide weekly and/or daily data associated with graphical element 834. For example, graphical element 848 may be representative of a line graph that illustrates the user's weekly and/or daily hit count data. As illustrated, on Oct. 30, 2018, the user took 5 hits from vaporization device 102.

FIG. 9 is a block diagram illustrating an exemplary computing environment 900, according to some embodiments. Computing environment 900 includes computing system 902 and computing system 952. Computing system 902 may be representative of client device 106. Computing system 752 may be representative of organization computing system 104.

Computing system 902 may include a processor 904, a memory 906, a storage 908, and a network interface 910. In some embodiments, computing system 902 may be coupled to one or more I/O device(s) 912 (e.g., keyboard, mouse, etc.) and vaporization device 102. In some embodiments, computing system 902 may communicate with vaporization device 102 via network 905.

Processor 904 may retrieve and execute program code 920 (i.e., programming instructions) stored in memory 906, as well as stores and retrieves application data. Processor 904 may be included to be representative of a single processor, multiple processors, a single processor having multiple processing cores, and the like. Network interface 910 may be any type of network communications allowing computing system 902 to communicate externally via computing network 905. For example, network interface 710 is configured to enable external communication with computing system 952.

Storage 908 may be, for example, a disk storage device. Although shown as a single unit, storage 908 may be a combination of fixed and/or removable storage devices, such as fixed disk drives, removable memory cards, optical storage, network attached storage (NAS), storage area network (SAN), and the like.

Memory 906 may include application 916, operating system 918, program code 920, and messaging application 922. Program code 920 may be accessed by processor 904 for processing (i.e., executing program instructions). Program code 920 may include, for example, executable instructions for communicating with computing system 952 to display one or more pages of website 964. As another example, processor 904 may access program code 920 to perform operations for implementing a smoking cessation plan. In another example, processor 904 may access program code 920 to perform operations for selectively providing adjusting power delivered to each heating coil in vaporizer device 102. Application 916 may enable a user of computing system 902 to access a functionality of computing system 952. For example, application 916 may access content managed by computing system 952, such as website 964. The content that is displayed to a user of computing system 902 may be transmitted from computing system 952 to computing system 902, and subsequently processed by application 916 for display through a graphical user interface (GUI) of computing system 902

Computing system 952 may include a processor 954, a memory 956, a storage 958, and a network interface 960. In some embodiments, computing system 952 may be coupled to one or more I/O device(s) 962. In some embodiments, computing system 952 may be in communication with database 108.

Processor 954 may retrieve and execute program code 968 (i.e., programming instructions) stored in memory 956, as well as stores and retrieves application data. Processor 954 is included to be representative of a single processor, multiple processors, a single processor having multiple processing cores, and the like. Network interface 960 may be any type of network communications enabling computing system 952 to communicate externally via computing network 905. For example, network interface 960 allows computing system 952 to communicate with computer system 902.

Storage 958 may be, for example, a disk storage device. Although shown as a single unit, storage 958 may be a combination of fixed and/or removable storage devices, such as fixed disk drives, removable memory cards, optical storage, network attached storage (NAS), storage area network (SAN), and the like.

Memory 956 may include website 964, operating system 966, program code 968, machine learning module 970, cessation module 972, and handler 974. Program code 968 may be accessed by processor 954 for processing (i.e., executing program instructions). Program code 968 may include, for example, executable instructions configured to perform steps discussed above in conjunction with FIG. 7. As an example, processor 954 may access program code 968 to perform operations for generating a smoking cessation plan. In another example, processor 954 may access program code 968 to perform operations adjusting a smoking cessation plan based on usage information associated with each user. Website 964 may be accessed by computing system 902. For example, website 964 may include content accessed by computing system 902 via a web browser or application.

Cessation module 972 may be configured to communicate with client device 106. In some embodiments, cessation module 972 may be configured to communicate with vaporization device 102. Cessation module 972 may receive usage information from vaporization device 102. Cessation module 972 may work in conjunction with machine learning module 970 to generate a smoking cessation plan for each user based, in part, on user input and usage information. For example, cessation module 972 may work in conjunction with machine learning module 970 to generate a cessation plan that includes a ratio of nicotine-containing substance to non-nicotine-containing substance to deliver to a user. Based off received usage information, cessation module 972 may work in conjunction with machine learning module 970 to update the cessation plan for each user.

Machine learning module 970 may include one or more instructions to train a prediction model used by cessation module 972. To train the prediction model, machine learning module 970 may receive, as input, usage activity of each user. In some embodiments, machine learning module 970 may further receive, as input, one or more parameters specified by each user via application 916 executing on computing system 902. Machine learning module 970 may implement one or more machine learning algorithms to train the prediction model. For example, machine learning module 970 may use one or more of a decision tree learning model, association rule learning model, artificial neural network model, deep learning model, inductive logic programming model, support vector machine model, clustering mode, Bayesian network model, reinforcement learning model, representational learning model, similarity and metric learning model, rule based machine learning model, and the like.

Account handler 974 may be configured to manage an account associated with each user. For example, account handler 974 may be configured to communicate with database 108. For example, account handler 974 may be configured to update each user profile stored in database 108.

FIG. 10A illustrates a system bus computing system architecture 1000, according to example embodiments. System 1000 may be representative of at least a portion of computing system 110 in vaporization device 102. One or more components of system 1000 may be in electrical communication with each other using a bus 1005. System 1000 may include a processing unit (CPU or processor) 1010 and a system bus 1005 that couples various system components including the system memory 1015, such as read only memory (ROM) 1020 and random access memory (RAM) 1025, to processor 1010. System 1000 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of processor 1010. System 1000 can copy data from memory 1015 and/or storage device 1030 to cache 1012 for quick access by processor 1010. In this way, cache 1012 may provide a performance boost that avoids processor 1010 delays while waiting for data. These and other modules can control or be configured to control processor 1010 to perform various actions. Other system memory 1015 may be available for use as well. Memory 1015 may include multiple different types of memory with different performance characteristics. Processor 1010 can include any general purpose processor and a hardware module or software module, such as service 1 1032, service 2 1034, and service 3 1036 stored in storage device 1030, configured to control processor 1010 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 1010 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing device 1000, an input device 1045 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 1035 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with computing device 1000. Communications interface 1040 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 1030 may be a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 1025, read only memory (ROM) 1020, and hybrids thereof

Storage device 1030 can include services 1032, 1034, and 1036 for controlling the processor 1010. Other hardware or software modules are contemplated. Storage device 1030 can be connected to system bus 1005. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 1010, bus 1005, display 1035, and so forth, to carry out the function.

FIG. 10B illustrates a computer system 1050 having a chipset architecture that may represent at least a portion of computing system 110 of vaporization device 102. Computer system 1050 may be an example of computer hardware, software, and firmware that can be used to implement the disclosed technology. System 1050 can include a processor 1055, representative of any number of physically and/or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified computations. Processor 1055 can communicate with a chipset 1060 that can control input to and output from processor 1055. In this example, chipset 1060 outputs information to output 1065, such as a display, and can read and write information to storage device 1070, which can include magnetic media, and solid state media, for example. Chipset 1060 can also read data from and write data to RAM 1075. A bridge 1080 for interfacing with a variety of user interface components 1085 can be provided for interfacing with chipset 1060. Such user interface components 1085 can include a keyboard, a microphone, touch detection and processing circuitry, a pointing device, such as a mouse, and so on. In general, inputs to system 1050 can come from any of a variety of sources, machine generated and/or human generated.

Chipset 1060 can also interface with one or more communication interfaces 1090 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 1055 analyzing data stored in storage 1070 or 1075. Further, the machine can receive inputs from a user through user interface components 1085 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 1055.

It can be appreciated that example systems 1000 and 1050 can have more than one processor 1010 or be part of a group or cluster of computing devices networked together to provide greater processing capability.

FIGS. 12A-15B show an alternate embodiment of a first portion 2020. These figures will be discussed with similar reference numbers to other parts of the application. FIG. 13 shows a close-up perspective view of a first portion 2020 of vaporizer device 200, according to example embodiments. First portion 2020 may include a body 3020. The body 3020 may include a first region 3010 and second region 3030. See also FIGS. 14A and 14B. First region 3010 may include a split-pod formed therein. For example, first region 3010 may include a first half of a split-pod 3040a and a second half of a split-pod 3040b. First half the pod 3040a may be separated from second half of the split-pod 3040b via opening 1180, which may extend from first end 2060 of first portion 2020 to second region 3030. Both first half of the split-pod 3040a and second half of the split-pod 3040b may be configured to hold a liquid. For example, first half of the split-pod 3040a may be configured to hold a nicotine-containing liquid; second half of the split-pod 3040b may be configured to hold a non-nicotine-containing liquid.

Second region 3030 of body 3020 may include one or more electric contacts 3080, one or more heating coils 3100 and one or more temperature sensor such as a thermistor 3022. In some embodiments, each of one or more thermistor 3022 is disposed between each of one or more heating coils 3100 that may be positioned adjacent a respective half of the split-pod 3040a, 3040b. For example, second region 3030 of body 3020 may include a first heating coil 3100 and a first thermistor 3022 dedicated to first half of the split-pod 3040a and a second heating coil 3100 and a second thermistor 3022 dedicated to second half of the split-pod 3040b. Each heating coil 3100 may be configured to heat the liquid contained in a respective half of the split-pod 3040a, 3040b to create a vapor mixture. Each heating coil 3100 may be formed from a metal material that is used for resistive heating. Exemplary metal materials may include, but are not limited to, Nichrome, KANTHAL®, stainless steel, and the like.

Each thermistor 3022 may be disposed adjacent the heating coil 3100 to measure the temperature of the coil 3100. In one embodiment the thermistor 3022 is electrically contacted with the metal contact pins and fed into microcontroller in a constant temperature feedback loop. In another embodiment the thermistor 3022 is wired through the contact 3080, through which information such as temperature information is fed into the microcontroller. Specifically, temperature information is fed from the contacts 3080 to the pins 410 in second portion 204. See FIGS. 12A and 12B. When the heating coil causes a rise in temperature, the microcontroller will process the temperature information as a voltage reading. The microcontroller will determine the temperature by measuring the resistance of thermistors 3022. When the temperature rises a translation is made to the temperature values via code to get an accurate temperature. By positioning the thermistor 3022 right next to the coil 3100, accurate temperature measurements can be obtained.

In one embodiment, the thermistor may be a Negative Temperature Coefficient (NTC) thermistor that that can limit the current that can flow once a resistance level is met. The NTC thermistor allows for a reduction in resistance as temperature increases. In one embodiment the NTC is a glass encapsulated NTC thermistor. In one embodiment, the temperature sensor or thermistor 3022 may be used in a range from −55° C. to 200° C. In another embodiment, the temperature sensor 3022 may be used at temperatures approaching absolute zero (−273.15° C.) as well as those specifically designed for use above 150° C. The temperature sensor thermistor 3200 allows for the accurate detection of coil temperatures in the device 200. In one embodiment, the temperature sensor or thermistor 3200 may be made of 315L stainless steel, ceramics, polymers or other materials depending on desired temperature response.

In another embodiment, a Positive Temperature Coefficient (PTC) thermistor may be used. The PCT thermistor allows for an increase in resistance as temperature increases. In one embodiment, other temperature sensors may be used instead of the thermistors.

In one embodiment, the thermistor is placed electrically contacted with the metal contact pins and fed into microcontroller creating a constant temperature feedback loop. This loop enables precise temperature readings that enables safer and sharper and focused dosing. Thus, the loop now created by the combination of the thermistor, metal contact pins microcontroller allows for accurate dosing in relation to the temperature schedule.

In one instance, the thermistor 3022 can detect when the split pods 3040a and 3040b are dry, lack liquids. This may be called a “dry hit.” A dry hit occurs if there is not enough liquid in chamber 3160 and metal coils 3100 are allowed to exponentially increase in temperature. In these situations, the coil 3100 heats up faster and if there is no liquid the thermistor can shut the pods 3040a, 3040b off before any harmful chemicals are released. “Dry hits” can be dangerous to patients as metals that are heated up to a point can release chemicals such as formaldehyde. By using thermistors 3022, it is possible to achieve an accurate dosing versus temperature schedule and apply accurate dosing using the present invention.

Each electrical contact 3080 may be configured to deliver power to each heating coil 310. For example, each electric contact 3080 may be configured to deliver a defined amount of power to each coil 3080, such that a specific ratio of non-nicotine-containing liquid to nicotine-containing liquid is vaporized. In some embodiments, each electrical contact 3080 may be positioned adjacent a respective half of the entire split-pod 3040a, 3040b. For example, second region 3030 of body 3020 may include a first electrical contact 3080 dedicated to a first heating coil 3100 for first half of the split-pod 3040a and a second electrical contact 3080 dedicated to a second heating coil 3100 for the second half of the split-pod 3040b.

As illustrated, each electrical contact 3080 may be configured to support a respective heating coil 3100. For example, each electric contact 3080 may include an opening (not shown) formed therein. Electrical coil 3100 may at least partially extend within the opening, such that electrical coil 3100 may be supported by electrical contact 3080. In another embodiment, the thermistor 3022 is wired through the contact and a wick is disposed through the coil. See FIGS. 15A and 15B.

Body 3020 may further include one or more divider walls 3060. Each of divider wall 3060 may be positioned in such a way as to separate each thermistor 3022 and heating coil 3100 from a respective half of the split-pod 3040a, 3040b. For example, as illustrated, a first divider wall 3060 may be positioned between first half of the split-pod 3040a and both the first thermistor 3022 and first heating coil 3100. Likewise, a second divider wall 3060 may be positioned between second half of the split-pod 3040b and both the second thermistor 3022 and second heating coil 3100. Each divider wall 3060 may include an opening 3070 formed therein. Each opening 3070 may be formed as to allow passage of a wicking material between each half of the split-pod 3040a, 3040b and a respective heating coil 3100. Wicking material may be used to deliver fluid from a respective half of the split-pod 3040a, 3040b to a respective heating coil 3100. Exemplary wicking materials may include, but are not limited to, silica, cotton, or other porous materials.

Body 3020 may further include a mixing chamber 3160, one or more vapor vents 3120, and one or more air vents 3140 formed therein. Mixing chamber 3160 may be defined within second region 3030. Mixing chamber 3160 may be in fluid communication with opening 1180. For example, mixing chamber 3160 may be formed in second region 3030, such that mixing chamber 3160 may separate each respective set of electrical contacts 3080, thermistors 3022 and heating coils 3100. Each vapor vent 3120 may be formed within an interior of first portion 2020. For example, each vapor vent 3120 may be formed proximate a respective heating coil 3100 and thermistors 3022. In operation, vapor formed from fluid in one half of the split-pod 3040a may enter mixing chamber 3160 via a first vapor vent 3120, and vapor formed from fluid in second half of the split-pod 3040b may enter mixing chamber 3160 via a second vapor vent 3120. Within mixing chamber 3160, vapor formed from a non-nicotine-containing fluid may mix with vapor formed from a nicotine-containing fluid to form a vapor mixture. The vapor mixture may be delivered to an end user via opening 1180.

Each air vent 3140 may be formed in body 3020. For example, as illustrated, each air vent 3140 may be formed such that each air vent 3140 may provide fluid communication between an interior of body 3020 and an exterior of body 3020. One or more air vents 3140 may be configured to draw ambient air into vaporizer device 200. For example, one or more air vents 3140 may be configured to draw ambient air into vaporizer device 200 via one or more air passages 216, upon inhalation of an end user.

FIG. 14B is an exploded view of first portion 2020 of vaporizer device 200, according to example embodiments. As discussed above, in some embodiments, first portion 2020 may be self-destructing. In other words, first portion 2020 may be configured such that a user cannot tamper with first portion 2020 (e.g., re-fill or re-use first portion 2020, take liquid out of first portion 2020, etc.).

As illustrated, first region 3010 is shown detached from second region 3030. Between first region 3010 and second region 3030 are one or more divider walls 3060, thermistors 3022 and heating coils 3100. To configure first portion 2020 such that first portion 2020 is tamper-proof, a sealant 350 may be used to couple first region 3010 to second region 303. In some embodiments, sealant (not shown) may be applied to first region 3010, such that after first region 3010 and second region 3030 are attached, sealant prevents disassembly of second region 3030 from first region 3010. Sealant may be any sealant able to prevent fluid leakage from first region 3010. Exemplary sealants may include, but are not limited to silicon, epoxy, a combination of the two, or any other suitable material.

The device 200 with the thermistors 3022 has an advantage of definitive accuracy over existing prior art current-temperature sensing mechanisms in current-closed pods designs. In smaller prior art designs similar to the size of device 200, thinner shorter wires are required. These short thinner wires make the current way of using ohms law and reading resistance then applying a temperature coefficient very inconsistent and inaccurate (error of close to 100° C.). In order to achieve very accurate temperature readings, such devices would require sub-ohm thicker vaping wire which would not fit in smaller designs. Also note, that sub-ohm vaping is not recommended and comes with it's own set of risks as current is less limited by resistance.

As stated above, vaporization device 102, 200 may transmit user data to client device 106. In another embodiment, user data may be transmitted from vaporization device 102, 200 to a controlled dosing platform, which in one embodiment will be disposed within ORGANIZATION COMPUTING SYSTEM 104 as shown in FIG. 1. User data may be held in device 102, 200 until it connects over the network 105 to the server. Once connected over the network, the device 102, 200 will send updates on user data to server and ultimately to the controlled dosing platform on ORGANIZATION COMPUTING SYSTEM 104. The controlled dosing platform enables the physician/practitioner to login and select a patient to see how much nicotine or other substance was used by the patient. The physician/practitioner further is able to adjust dosing schedule/nicotine intake of that patient based on the data as viewed on the controlled dosing platform.

FIGS. 16-17B show screenshots provided when using the controlled dosing platform. The practitioner/physician updates or adjusts dosing schedule that will eventually be transmitted to vaporization device 120, 200. If the physician wants to change patients dosing the practitioner updates it on the portal, which is then downloaded by application 112 of the client device 106 and ultimately the vaporization device 102, 200 downloads and updates the new dosing schedule once connected over the network 105. The practitioner/physician can mark data and date/time changes and see how a patient's behaviors and intake changes over a new schedule.

In use, a physician or practitioner logs into a portal and views dashboard 50. See FIG. 16. The dashboard 50 provides a view of user data under the control of the practitioner. This data includes total users 52, number of active devices 54, number of hits 56 taken, a snapshot of activity in a twenty-four hour period 58, types of smokers 60, user overview 62, for instance, number of users that completed the program of the present invention, number of active users, number of new users. The dashboard 50 is not limited to the ways data is aggregated and may be shown in numerous other ways. Also provided on the dashboard 50 is a user list 64.

By clicking on any user name in the user list 64, the practitioner may view user data on a particular user/patient. The practitioner may see how much nicotine or other substance was used by the selected user/patient and adjust dosing schedule/nicotine intake for the user/patient. The practitioner can view and adjust dosing in a variety of ways and can adjust the plan if the user is not happy with their current schedule.

FIG. 17A&B show a screenshot of a user profile 70, here showing a user named Gregory 66 which was a user selected from the user list 64 in FIG. 16. User data from the device 200 is updated to the server and displayed on user profile 70. For example, looking at Gregory's user profile 70 page information such as all usage data or stats 80 (ie: average hit, dose average, total hits during program, hits taken today), user feedback 82 and a hit history 84 are provided. The profile 70 also provides data such as regression formula 72, a control period 76 and an end or quit date 78. Each of the regression formula or regression value 72, a control period 76 and an end or quit date 78 can be adjusted by the practitioner to increase or decrease the nicotine dose on a per use basis.

It should be noted that regression formula 72 is shown in FIG. 17 as a k value, however, a t_e value may be used in the alternative. When the regression formula 72 is a k value, exponential regression algorithm, the formula of D_n=D0*e^{(tn−t0−c)*k} is used. Alternatively, if regression formula 72 uses a linear regression algorithm, t_e value 74 the variables that are stored for each user under the t_e value may be:

Start Date (t₀)—this may represent the date when the user started using the smoking cessation program.

Control Period (c)—this may represent the length of the initial period, during which no regression takes place, but the user's current smoking habits are being recorded. In some embodiments, the control period will be 2 days.

End date (t_e)—this is the date when the user finishes the program.

Initial daily dose (d₀)—this is the initial nicotine dose that will be applied at the beginning of the program.

During the control period, d₀ will be applied during each hit.

After the control period, the following values will be calculated:

m—this may represent the constant that determines how steep the regression is. The higher the absolute value of m, the quicker the regression.

It is calculated using the following formula:

t_e=d₀/m+(t₀+c)

Current dose (d_n)—this is the nicotine dose for the n^th day, calculated using the following formula:

d_n=d₀−m*(t_n−(t₀+c))

where t_n is the n^th day of the program.

When the program ends, d_n will have a value of 0.

Changing the end date, t_e value, affects the slope of the m value. Thus, if the t_e value is moved up the slope of the m value will be increased and the regression will be quicker. However, if the t_e value is moved back (made lower) the slope of the m value will decrease and the regression will be slower. Thus, in one example, if a practitioner step downs a patient 0.2 MG per day over 30 days, instead of over a 90 day period, the slope would be steeper for the 30 day selection.

While the foregoing is directed to embodiments described herein, other and further embodiments may be devised without departing from the basic scope thereof. For example, aspects of the present disclosure may be implemented in hardware or software or a combination of hardware and software. One embodiment described herein may be implemented as a program product for use with a computer system. The program(s) of the program product define functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory (ROM) devices within a computer, such as CD-ROM disks readably by a CD-ROM drive, flash memory, ROM chips, or any type of solid-state non-volatile memory) on which information is permanently stored; and (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive or any type of solid state random-access memory) on which alterable information is stored. Such computer-readable storage media, when carrying computer-readable instructions that direct the functions of the disclosed embodiments, are embodiments of the present disclosure.

It will be appreciated to those skilled in the art that the preceding examples are exemplary and not limiting. It is intended that all permutations, enhancements, equivalents, and improvements thereto are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of the present disclosure. It is therefore intended that the following appended claims include all such modifications, permutations, and equivalents as fall within the true spirit and scope of these teachings.

Claims

1. A computer-implemented method for practitioner tracking of patient substance intake and controlling of substance dosing for patients participating in a smoking cessation plan, said smoking cessation plan based on one or more inputs provided by a client device in communication with a vaporization device, the initial smoking cessation plan comprising one or more phases, wherein each phase is associated with a predefined ratio of a vapor mixture for the vaporization device to deliver to a user, said method comprising:

displaying, over a server system, at least one patient profile on a controlled dosing platform, said patient profile including one or more streams of usage statistics, said patient profile being under control of said practitioner;

receiving, by the server system, updates to said one or more streams of usage statistics associated with patient usage of the vaporization device;

selecting, over the server system, one patient profile from said controlled dosing platform;

viewing, over the server system, said one or more streams of usage statistics for said selected patient profile;

modifying, by the server system, the initial smoking cessation plan based on selecting at least one of said one or more streams of usage statistics; and

transmitting, by the server system, the modified initial smoking cessation plan to the client device.

2. The computer-implemented method of claim 1, wherein the usage statistics comprise one or more uses of vaporization device and a duration associated with each use of the one or more uses.

3. The computer-implemented method of claim 1, wherein one of said one or more streams of usage statistics is a regression value.

4. The computer-implemented method of claim 1, wherein one of said one or more streams of usage statistics is a control period.

5. The computer-implemented method of claim 1, wherein one of said one or more streams of usage statistics is a quit date.

6. The computer-implemented method of claim 2, wherein said regression value is a linear regression.

7. The computer-implemented method of claim 6, wherein said linear regression is defined using wherein said tc is when the patient finishes the smoking cessation plan, wherein said d0 is an initial daily nicotine dose, wherein said m is a constant, wherein t0 is when the patient started using the smoking cessation plan and wherein c is a control period.

tc=d0/m+(t0+c)

8. The computer-implemented method of claim 2, wherein said regression value is an exponential regression.

9. The computer-implemented method of claim 8, wherein said exponential regression is defined using wherein said Dn is a current daily dose, wherein said D0 is an average daily nicotine dose during the control period, wherein e is the base of the natural logarithm, also called Euler's constant.,

Dn=D0*e((tn−t0−c)*k

wherein said to is the nth day of the program

, wherein said t0 is when the patient started using the smoking cessation plan and wherein said c is a control period and wherein said k is a constant.

10. A nicotine intake tracking and nicotine dosing controlling system comprising:

a vaporization device configured to deliver a vapor mixture comprising a first vapor formed from a non-nicotine-containing liquid and a second vapor formed from a nicotine-containing liquid, wherein the vaporization device comprises a computing system disposed therein, the computing system comprising:

a printed circuit board, comprising: a microcontroller in selective communication with the server system, the microcontroller storing dosage instructions for a smoking cessation plan stored thereon;

a server system in communication with the vaporization device, the server system configured to generate a smoking cessation plan for the vaporization device based on at least usage statistics associated with the vaporization device; and

an organization computing device, the organization computing device including a controlled dosing platform, said controlled dosing platform displaying at least one patient profile, said patient profile including one or more streams of usage statistics.

11. The system of claim 10 wherein said patient profile is under control of a practitioner.

12. The system of claim 10 wherein said patient profile provides one or more streams of usage statistics associated with patient usage of the vaporization device.

13. The system of claim 12 wherein one of said one or more streams of usage statistics is a regression value.

14. The system of claim 12 wherein one of said one or more streams of usage statistics is a control period.

15. The system of claim 12 wherein one of said one or more streams of usage statistics is a quit date.

16. The system of claim 13 wherein said regression value is a linear regression.

17. The system of claim 16, wherein said linear regression is defined using wherein said te is when the patient finishes the smoking cessation plan, wherein said d0 is an initial daily nicotine dose, wherein said m is a constant, wherein t0 is when the patient started using the smoking cessation plan and wherein c is a control period.

te=d0/m+(t0+c)

18. The system of claim 12 wherein said regression value is an exponential regression.

19. The system of claim 18, wherein said exponential regression is defined using wherein said Dn is a current daily dose, wherein said D0 is an average daily nicotine dose during the control period, wherein e is the base of the natural logarithm, also called Euler's constant,

Dn=D0*e((tn−t0−c)*k

, wherein said to is the nth day of the program, wherein said t0 is when the patient started using the smoking cessation plan and wherein said c is a control period and wherein said k is a constant.

20. The system of claim 12, wherein the server system is further configured to be able to modify the smoking cessation plan based on selecting at least one of said one or more streams of usage statistics and transmit the modified smoking cessation plan to the client device.