US Patent 11,173,259: Claim Scope, Inhaler Data Synchronization, Exclusivity, and Patent Landscape
US Patent 11,173,259 protects a connected-inhaler ecosystem in which inhalation or usage data is collected by one mobile device, uploaded to a cloud server, and later delivered to another mobile device without requiring the second device to retrieve the full data history directly from the inhaler. The broadest commercial risk centers on the data-routing architecture, timestamp-based synchronization, QR-code onboarding, BLE authentication, and compatibility screening.
The patent is primarily a digital-health and connected-device patent. It is not principally a drug-substance patent. Its claims may affect smart inhalers, add-on electronics modules, medication-adherence platforms, caregiver applications, and combination-product programs involving albuterol, fluticasone, beclomethasone, and salmeterol.
What does US Patent 11,173,259 protect?
The independent claims cover three related system architectures.
| Independent claim |
Protected architecture |
Primary commercial target |
| Claim 1 |
Cloud server, inhaler, first mobile device, second mobile device, timestamp-based synchronization |
Shared or multi-device inhaler-data platforms |
| Claim 10 |
Cloud server, inhaler, first and second mobile devices, cloud retrieval after second-device login |
Caregiver, clinician, or patient applications |
| Claim 22 |
Cloud server, detachable electronics module, first and second mobile devices, cloud-based usage-data retrieval |
Add-on smart inhaler modules |
The claims require a combination of hardware and software elements. A product generally must satisfy the full combination of an asserted claim to create literal infringement risk.
The core claim concept is not simply recording inhaler use. It is the controlled movement of inhalation data between the inhaler, a first mobile device, the cloud server, and a second mobile device.
Claim 1: Timestamp-based synchronization
Claim 1 requires:
- An inhaler with a mouthpiece, medicament, and electronics module.
- A first mobile application that requests data from the inhaler.
- Transmission of inhalation data and a timestamp from the first mobile device to a cloud server.
- A second mobile application that reports the most recent timestamp stored locally.
- Cloud delivery of only data associated with a later timestamp.
- The second mobile device requesting cloud data before requesting data from the inhaler after entering connected mode.
This structure addresses a specific synchronization problem. A second phone does not need to download the complete historical record from the inhaler. It identifies the last data point it has, and the server returns later records.
The claim is narrower than a generic connected-inhaler claim because it requires both:
- First-device upload to the server; and
- Second-device incremental retrieval based on a timestamp.
A platform that merely synchronizes an inhaler directly with one phone may fall outside claim 1. A platform that uploads data to a server but does not transmit the second device's last timestamp may also avoid literal infringement, subject to equivalents and the specific wording of related claims.
Claim 10: Login-triggered cloud retrieval
Claim 10 covers a similar system but uses a user-login event rather than a timestamp requirement as the trigger for the second device's cloud request.
The second mobile application must:
- Detect a login event;
- Request inhalation data from the cloud;
- Make that request before requesting the data directly from the inhaler; and
- Receive the inhalation data from the server.
Claim 10 is potentially broader than claim 1 in one respect because it does not require the second device to transmit the timestamp of its most recent stored record. It remains limited by the login-triggered sequence and the requirement that the cloud request precede a direct inhaler request.
Claim 22: Detachable electronics module
Claim 22 replaces the inhaler electronics module with an electronics module configured to be attached to and removed from an inhaler. It uses "usage data" rather than expressly limiting the data to inhalation data.
This claim reaches add-on devices that monitor a conventional inhaler without requiring the electronics to be permanently integrated into the drug-delivery device. The detachable-module language creates a separate risk category for retrofit systems and reusable sensor modules.
How do the dependent claims expand the patent scope?
Claims 2 through 9, 11 through 21, and 23 through 24 add implementation details that may support narrower infringement theories or provide fallback positions during validity challenges.
| Claim group |
Technical limitation |
Business significance |
| Claims 2 and 19 |
Inhaler transmits data to a mobile device only once |
Addresses duplicate transfers and data-consistency control |
| Claims 3 and 17 |
Product ID or patient ID sent to cloud server |
Links usage data to a product or patient record |
| Claims 4 and 20 |
Periodic cloud synchronization requests |
Covers background or recurring data refresh |
| Claim 5 |
Reverse synchronization involving the second device uploading data |
Covers multi-device data exchange in both directions |
| Claim 6 |
Counter-based timing converted to local mean time |
Addresses inhalers lacking a reliable real-time clock |
| Claims 7 and 8 |
Specified respiratory medicines |
Connects the platform to commercial inhaler products |
| Claims 9 and 21 |
QR-code identification and dose reminders |
Covers onboarding and adherence-alert functions |
| Claims 11 to 13 |
Compatibility screening and pairing rejection |
Controls use by medication, strength, application, or patient |
| Claims 14 to 16 |
QR-code-based communication passkey and BLE pairing |
Removes the need for an actuator, button, or switch |
| Claim 18 |
Cloud request before direct inhaler request after connection |
Defines the synchronization sequence |
| Claims 23 and 24 |
Add-on module identification and periodic data retrieval |
Extends the architecture to detachable modules |
What formulations are protected by US Patent 11,173,259?
Claims 7 and 8 identify respiratory medicines rather than claiming a new pharmaceutical composition.
Claim 7 lists:
- Albuterol sulfate at 117 mcg per discrete dose;
- Fluticasone propionate at 55 mcg, 113 mcg, or 232 mcg per dose; and
- Fluticasone propionate combined with salmeterol xinafoate, with 55 mcg, 113 mcg, or 232 mcg of fluticasone propionate and 14 mcg of salmeterol xinafoate per dose.
Claim 8 also identifies:
- Albuterol sulfate;
- Fluticasone propionate or fluticasone furoate;
- Beclomethasone dipropionate; and
- Fluticasone propionate or fluticasone furoate combined with salmeterol.
These limitations do not independently protect those active ingredients. The medicine must be used within the claimed connected-inhaler system. A conventional inhaler containing one of these medicines, without the claimed cloud, mobile-device, and data-synchronization architecture, should not fall within the system claims solely because of the drug.
What are the strongest infringement theories?
The strongest exposure is likely to arise where a competing product has all of the following characteristics:
- A sensor-equipped inhaler or detachable sensor module;
- A mobile application that actively requests usage data;
- A cloud backend that stores usage records;
- Multiple mobile applications or multiple user devices;
- Timestamp-based incremental synchronization;
- QR-code device identification;
- BLE pairing without a physical pairing button; or
- Medication-specific compatibility checks.
A product does not necessarily avoid the claims by distributing functions across separate corporate entities. In a connected system, infringement analysis may examine combined operation, contractual control, induced infringement, and whether a party directs or controls the claimed system activities.
Which claim elements create design-around opportunities?
Potential design-around positions include:
- Direct phone-to-inhaler synchronization without cloud-mediated retrieval.
- Cloud synchronization based on record identifiers, sequence numbers, or hashes rather than timestamps.
- A second device that retrieves all available data without first reporting its last stored timestamp.
- A second device that connects directly to the inhaler before querying the cloud.
- Pairing initiated through a physical button or actuator rather than a QR-derived passkey.
- Device identification through an account token rather than a product ID or patient ID.
- A sensor that reports dose events directly to a cellular or Wi-Fi gateway without a first mobile device.
- A platform that does not limit repeated transmission of the same data to a single transmission.
These approaches require claim construction and doctrine-of-equivalents analysis. They are design considerations, not automatic safe harbors.
When does US Patent 11,173,259 lose exclusivity?
The patent's enforceable term cannot be established from the claim text alone. The relevant calculation requires the earliest effective nonprovisional priority date, any terminal disclaimer, patent-term adjustment, patent-term extension, and continuity data shown in the patent file.
The ordinary US utility-patent term is generally 20 years from the earliest effective US nonprovisional filing date, subject to statutory adjustments and exceptions under 35 U.S.C. §§ 154 and 156. Patent-term adjustment can move the expiration date later than the basic 20-year calculation. A terminal disclaimer can shorten it. [2]
The issue date does not determine expiration. The November 2021 grant date should not be used as the starting point for calculating patent life.
Does the patent have regulatory exclusivity?
The patent itself does not create FDA new-drug exclusivity, orphan-drug exclusivity, pediatric exclusivity, or biologic exclusivity. Those periods arise from the applicable NDA, BLA, or other regulatory pathway, not from a connected-device patent. [3]
The patent also does not create biosimilar exclusivity risk. Albuterol, fluticasone, salmeterol, and beclomethasone are small-molecule active ingredients. Competitive products would ordinarily enter through generic-drug or abbreviated new drug application pathways, combination-product pathways, or device-specific regulatory routes rather than the biosimilar pathway.
What is the Orange Book status of US Patent 11,173,259?
A software and connected-system patent is not automatically eligible for Orange Book listing.
FDA regulations permit NDA sponsors to submit patents that claim the drug substance, drug product, or an approved method of using the drug. Patent claims directed primarily to data handling, mobile applications, cloud servers, and device communication may face eligibility objections if submitted for listing. [4]
Claims 7 and 8 identify medicines, but the claims principally cover a system containing an inhaler and digital infrastructure. The presence of a listed active ingredient does not transform a data-system claim into a drug-substance or drug-product claim.
The practical Orange Book implications are:
- The patent should not be treated as a conventional composition-of-matter patent.
- A generic applicant's Paragraph IV analysis would depend on whether the relevant NDA sponsor listed the patent and whether FDA accepted the listing.
- If listed, a Paragraph IV certification could trigger Hatch-Waxman litigation under 21 U.S.C. § 355(j).
- If not listed, the patent could still support a separate infringement action outside the Orange Book listing mechanism.
What Paragraph IV challenges are relevant?
A Paragraph IV challenge would be relevant only if the patent is listed against an applicable NDA and the generic applicant's product is subject to the patent certification requirements.
The most plausible challenge grounds would be:
- Noninfringement because the generic inhaler lacks the cloud or multi-device architecture;
- Invalidity for lack of novelty under 35 U.S.C. § 102;
- Obviousness under 35 U.S.C. § 103;
- Indefiniteness under 35 U.S.C. § 112;
- Written-description or enablement challenges;
- Inapplicability of the claims to a conventional generic inhaler; and
- Failure of the patent to claim an Orange Book-eligible drug product or method of use.
A generic inhaler could potentially avoid the claims by omitting connected functionality. A connected generic product that deliberately reproduces the claimed synchronization workflow would face greater risk.
How strong is the patent estate?
The patent's strength is concentrated in system sequencing and data architecture rather than pharmaceutical chemistry.
| Strength factor |
Assessment |
| Core technical concept |
Meaningful protection for multi-device cloud synchronization |
| Breadth |
Moderate; independent claims require numerous system components |
| Drug coverage |
Narrow and conditional; drug presence alone is insufficient |
| Software dependence |
High; infringement turns on application and server behavior |
| Design-around potential |
Moderate to high through alternate synchronization workflows |
| Validity exposure |
Potentially material under obviousness and abstract-idea theories |
| Regulatory leverage |
Limited unless tied to a listed combination product or method |
| Manufacturing leverage |
Limited for drug manufacture; stronger for integrated smart-inhaler platforms |
| Biosimilar relevance |
None or minimal |
| Licensing relevance |
Significant for digital-inhaler platforms and adherence ecosystems |
The claims contain concrete device and communication limitations, which can support patent-eligibility arguments under 35 U.S.C. § 101. The main validity risk is likely obviousness based on known connected medical devices, cloud synchronization, Bluetooth communication, QR-code provisioning, and timestamp-based incremental data transfer.
Claim 6 has a more specialized technical limitation. It uses an electronics-module counter to reconstruct local mean time on the mobile device. That limitation may provide stronger differentiation than the more general cloud-transfer concepts, depending on the prior art.
Claims 14 through 16 also contain a defined implementation path: QR scanning, derivation of a unique communication passkey, and BLE authentication without a physical pairing actuator. Products using that exact onboarding sequence may present elevated risk.
What patent landscape surrounds connected inhalers?
The relevant landscape has several overlapping patent families.
Smart-inhaler hardware patents
These patents commonly cover:
- Dose-event sensors;
- Actuation detection;
- Flow or pressure sensors;
- Electronics integrated into inhaler bodies;
- Detachable sensor caps;
- Dose counters;
- Memory and wireless communication modules; and
- Environmental or orientation sensing.
They may be held by pharmaceutical companies, inhaler manufacturers, digital-health companies, and device suppliers.
Digital adherence and cloud-platform patents
These families generally address:
- Patient adherence monitoring;
- Medication reminders;
- Clinician dashboards;
- Caregiver access;
- Cloud storage of dose events;
- Data normalization across devices; and
- Integration with electronic health records.
US Patent 11,173,259 is most closely aligned with this category, but its claims connect the backend architecture to a specific inhaler synchronization sequence.
QR-code and BLE provisioning patents
This cluster covers:
- Device identity encoded in QR codes;
- Product and medication-strength recognition;
- Pairing credentials;
- BLE passkeys;
- Authentication without a physical pairing button;
- Application compatibility testing; and
- Rejection of unsupported device-drug combinations.
Claims 11 through 16 are important for freedom-to-operate reviews involving onboarding and device authentication.
Drug-device combination-product patents
These patents may cover:
- Smart inhalers containing a specific active ingredient;
- Dose counters integrated with approved inhalers;
- Electronic monitoring of metered-dose inhalers;
- Medication-specific dosing schedules; and
- Combination-product labeling or user-interface functions.
A competitor should review both drug patent families and device/software families. The risks are cumulative. Avoiding one patent family does not eliminate exposure to another.
What litigation, licensing, or settlement issues should be reviewed?
The claim text does not establish litigation or settlement history. A complete freedom-to-operate review should treat the patent as part of a broader family investigation covering:
- Continuation and divisional applications;
- Terminal disclaimers;
- Reexamination or post-grant proceedings;
- Patent assignments and security interests;
- Federal district-court complaints;
- ITC investigations;
- License agreements;
- Settlement agreements;
- Covenant-not-to-sue provisions; and
- Related patents with overlapping synchronization or pairing claims.
Licensing value is highest for a company commercializing a smart-inhaler platform across multiple medicines or selling a detachable electronics module to pharmaceutical sponsors. The patent is less relevant to a conventional generic manufacturer that sells an unconnected inhaler and does not operate the claimed cloud ecosystem.
What generic launch risks exist?
Generic entry scenarios divide into three categories.
| Launch scenario |
Patent risk |
| Conventional inhaler with no connected electronics |
Lower risk under these claims |
| Connected inhaler using a single phone and no cloud synchronization |
Moderate risk depending on dependent features |
| Connected inhaler with multi-device cloud synchronization, QR onboarding, and BLE passkeys |
Higher risk |
| Detachable sensor module with cloud-based usage records |
Higher risk under claim 22 and its dependents |
| Drug-only formulation or conventional inhaler manufacture |
Limited exposure to this patent specifically |
| Digital companion application sold separately |
Risk depends on whether the complete claimed system is practiced |
A generic manufacturer may avoid this patent while still confronting composition, formulation, device, method-of-use, or regulatory patents associated with the reference product.
How does this patent compare with conventional drug patents?
US Patent 11,173,259 differs from a conventional drug patent in four important ways:
- It does not claim the active ingredient as a chemical entity.
- It does not claim a formulation independently of the connected system.
- It depends heavily on software and communications behavior.
- Its commercial value is tied to digital-device adoption, not only prescription volume.
Revenue exposure therefore depends on the installed base of compatible smart inhalers and applications. The patent is unlikely to block all generic versions of albuterol or fluticasone products. It can, however, complicate a connected generic or digital-companion strategy.
Key Takeaways
- US Patent 11,173,259 is a connected-inhaler and digital-adherence patent, not a conventional drug-composition patent.
- Claims 1, 10, and 22 are the principal independent claim groups.
- The central invention is cloud-mediated synchronization of inhaler or module usage data across multiple mobile devices.
- Timestamp-based incremental retrieval is central to claim 1 and dependent claims 4, 5, 20, and 24.
- QR-code identification, BLE passkeys, compatibility screening, and pairing without a physical actuator create separate infringement vectors.
- Claims 7 and 8 identify respiratory medicines but do not independently monopolize albuterol, fluticasone, salmeterol, or beclomethasone.
- Biosimilar risk is not material because the listed products are small-molecule medicines.
- Orange Book relevance is narrower than for a drug-substance or drug-product patent and depends on actual listing and FDA acceptance.
- A conventional generic inhaler without connected functionality presents lower risk under these claims.
- Connected generic inhalers and detachable sensor modules present the greatest freedom-to-operate exposure.
- Patent-term expiration must be calculated from the effective filing and priority record, not the issue date.
FAQs About US Patent 11,173,259
Can a generic albuterol inhaler infringe US Patent 11,173,259?
Only if the product and associated system practice the claimed connected architecture. Albuterol alone is not enough. The relevant system would generally require the claimed inhaler electronics, mobile applications, cloud server, and data-transfer sequence.
Does using Bluetooth automatically create infringement risk?
No. Bluetooth or BLE is relevant mainly to the narrower pairing and passkey claims. A product using Bluetooth but lacking the claimed QR-derived passkey or synchronization sequence may not meet those claims.
Does the patent cover a smart inhaler used with one phone?
Potentially, but the strongest independent claims require cloud-server interaction and, in some claims, a second mobile device. A single-device implementation must be analyzed against each claim limitation rather than the patent as a whole.
Can the patent block a detachable inhaler sensor?
It can create risk under claim 22 and claims 23 through 24 if the module, cloud server, and mobile applications perform the claimed usage-data collection and retrieval functions.
Is a Paragraph IV filing required for every generic product containing fluticasone?
No. A Paragraph IV certification depends on whether the relevant patent is listed for the applicable NDA and whether the generic product is subject to the statutory certification framework. The active ingredient by itself does not determine Paragraph IV obligations.
References
-
United States Patent and Trademark Office. (2021). United States Patent No. 11,173,259. U.S. Department of Commerce. https://patents.google.com/patent/US11173259
-
35 U.S.C. §§ 101-103, 112, 154, 156 (2023).
-
U.S. Food and Drug Administration. (2024). Generic drug facts and data exclusivity. https://www.fda.gov/drugs
-
U.S. Food and Drug Administration. (2024). Approved drug products with therapeutic equivalence evaluations, commonly known as the Orange Book. https://www.fda.gov/drugs/drug-approvals-and-databases/approved-drug-products-therapeutic-equivalence-evaluations-orange-book
