Afrezza: inhaled delivery brings a pulmonary workflow

Afrezza demonstrates why delivery belongs in both the product profile and the care pathway. FDA's June 27, 2014 approval covered inhaled human insulin for glycemic control in adults with diabetes mellitus. The original label also contained a boxed warning about acute bronchospasm in patients with chronic lung disease. A route that avoids an injection still creates its own clinical requirements. [1, 2]

The route changes the work

The 2014 label required assessment for underlying lung disease before initiation, including spirometry. It called for pulmonary-function assessment after six months and annually thereafter. These historical requirements are useful evidence for an operating-model analysis; readers should use the current label for current prescribing decisions. [1]

A trial endpoint is only one component

An inhaled-insulin proposition must join glycemic efficacy, pulmonary safety, device handling, and suitable patient selection. Convenience should be tested with the intended user and routine workflow rather than assumed from the absence of a needle. A comparison that examines only administration preference can miss the cost and effort of the surrounding pathway.

Translate monitoring into adoption questions

For a launch team, the practical questions include who arranges testing, whether a test is readily available, how an abnormal result is handled, and how follow-up is remembered. Track these handoffs before interpreting prescription interest as completed adoption. The approval letter also required postmarketing work; authorization did not eliminate the need for longer-term evidence. [2]

A delivery-development scorecard

Separate product performance from pathway performance. The first asks whether the formulation and inhaler deliver the intended therapeutic result. The second asks whether eligible patients can complete screening, receive training, obtain the product, and sustain appropriate use. Linking those measures early can identify a route-specific bottleneck while a program still has options to address it.