IP Library Granted Patent US 12,621,177
Granted Patent B2
US 12,621,177 · App. 18/766,590 · Granted May 5, 2026

Medical injectors and systems and methods for an injection management platform

Inventors: Jay S. Walker (Stamford, CT); Timothy Scott Case (Washington, DC); Lindsey Walker (Stamford, CT); Isra Elmahdi (Washington, DC); Daniel Curaca Malito (Arlington, VA); Kristen Marie Hannon (Eldersburg, MD)
Assignee: Koska Family Limited
H04L9/50G16H10/60G06Q2220/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,621,177
App. No.
18/766,590
Granted
May 5, 2026
Kind
B2
Abstract

Systems, methods and articles of manufacture provide for an injection management platform that allows the verification and management of injection event transactions involving injectors equipped with NFC or RFID chips utilizing a distributed and secure technology such as blockchain. An injection event transaction ledger allows for digital receipts of injection event transactions to be securely verified and updated. In accordance with some embodiments, injectors may comprise blow-fill-seal (BFS) injectors that are pre-filled with a single dose of a fluid agent comprising a vaccine or medicament, allowing for tracking of individual doses of the fluid agent via the injection event transaction ledger.

Claims (36)

1 . A system for managing an injection management system, comprising:

a processor;

a memory storing a program, wherein the program, when executed by the processor causes the processor to perform a method, the method comprising:

receiving, via an injection provider platform of an Injection Management App stored on a first mobile device corresponding to first user, an indication of a dose of a fluid agent to be administered to a patient, the indication including first data comprising a unique identifier of an injector containing the dose, thereby recognizing a first injection event transaction;

authorizing the dose of the fluid agent;

generating an electronic record unique to the first injection event transaction, thereby generating a first injection event record;

receiving, from the first user and via the Injection Management App, an indication that the dose has been administered to the patient;

generating, in response to the receiving, a first passcode;

outputting the first passcode to the first user via the Injection Management App;

receiving the first passcode from a second user;

concluding, based on the receiving of the first passcode from the second user, that the second user is the patient to whom the dose of the fluid agent from the injector has been administered by the first user as part of the first injection event transaction;

updating the first injection event record to indicate that the dose of the fluid agent has been administered to the second user; and

transmitting to the second mobile device of the second user, via the patient portal of the Injection Management App, a verifiable confirmation that the dose of the fluid agent has been administered to the second user, thereby transmitting to the second mobile device a digital receipt for the first injection event, to be stored in the patient portal of the Injection Management App of the second user.

2 . The system of claim 1 , wherein the first user previously signed in to the injection provider platform via the first mobile device by providing first user credentials that allowed the electronic processing device to uniquely identify the first user and recognize the first user as a registered injection provider.

3 . The system of claim 1 , wherein the second user has previously signed in to a patient platform of the Injection Management App via a second mobile device by providing second user credentials that allowed the electronic processing device to uniquely identify the second user and recognize the second user as a registered patient.

4 . The system of claim 1 , wherein the authorizing is based on the unique identifier of the injector.

5 . The system of claim 1 , wherein the first passcode corresponds to an expiration time and is stored in association with the first injection event record.

6 . The system of claim 1 , wherein the first passcode is only accepted from the second user if it is received prior to the expiration time.

7 . The system of claim 1 , wherein the digital receipt comprises a unique digital receipt identifier that corresponds to the first injection event record, the unique digital receipt identifier for enabling the second user, via the patient portal of the Injection Management App, to communicate with the Injection Management System and verify a vaccination status of the second user based on data stored in the first injection event record.

8 . The system of claim 1 , wherein the method further comprises:

outputting, prior to receiving and via the Injection Management App and to the first user, an indication that the injection has been authorized.

9 . The system of claim 1 , wherein the first injection event record is stored as a blockchain record in a distributed network of the injection management system.

10 . The system of claim 1 , wherein the digital receipt comprises at least one of the following: (i) an indication of the fluid agent; (ii) an identifier of the injector; (iii) a time of the administration of the dose; (iv) a location of the administration of the dose; (v) an identifier of the second user; and (vi) an indication of the first user who administered the dose.

11 . The system of claim 10 , wherein the digital receipt includes a code that can, upon request of the second user, be displayed on the second user's mobile device via a Graphical User Interface (GUI) of the patient platform of the Injection Management App, the code being readable by an external electronic device in order to confirm that the dose of the fluid agent has been administered to the second user.

12 . The system of claim 10 , wherein the digital receipt comprises multiple privacy levels of information that can be shared with third parties, each privacy level of information corresponding to a respective permission requirement of the second user, such that in order for a given privacy level of information of the digital receipt to be shared with a third party, the second user must first provide a corresponding permission requirement.

13 . The system of claim 12 , wherein a first level of information of the multiple levels of information corresponds to anonymous information about the dose administered to the second user without identifying the second user and a second level of information of the multiple levels of information corresponds to information that identifies the second user as well as information about the dose administered to the second user.

14 . The system of claim 1 :

wherein the fluid agent comprises a vaccine against a particular transmittable disease that is effective for a predetermined period of time from a time of administration, such that the second user is to be considered vaccinated against the particular transmittable disease for the predetermined period of time, and

further wherein the digital receipt further comprises an expiration date of the dose that is based on the predetermined period of time, the expiration date for utilization by the patient portal of the Injection Management App, only up to a time of the expiration date, to output via a Graphical User Interface (GUI) of the Injection Management App, a confirmation that the second user is considered vaccinated against the particular transmittable disease.

15 . The system of claim 1 , wherein receiving the indication that the dose has been administered to the patient comprises receiving a photo of the second user taken during the first injection event transaction, and wherein updating the electronic record comprises transmitting a copy of the photo to the second user's mobile device, to be stored in association with the digital receipt.

16 . The system of claim 1 , wherein a copy of the photo is stored in association with the first injection event record.

17 . The system of claim 1 , wherein the method further comprises:

retrieving, based on the unique identifier of the injector, information descriptive of the fluid agent and the dose.

18 . The system of claim 17 , wherein authorizing comprises:

confirming, based on the information, that the dose is valid and approved for administration.

19 . The system of claim 1 , wherein the injector is equipped with an NFC chip and wherein the receiving is performed by reading the first data via the Near Field Communication (NFC) chip.

Assignments (2)
SECURITY INTEREST Recorded Dec 9, 2025
From: KOSKA FAMILY LIMITED
To: JEFFERIES CAPITAL SERVICES, LLC, AS COLLATERAL AGENT
Reel/Frame 073916/0895 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 16, 2024
From: WALKER, JAY S.; CASE, TIMOTHY SCOTT; WALKER, LINDSEY; ELMAHDI, ISRA; MALITO, DANIEL CURACA; HANNON, KRISTEN MARIE
To: KOSKA FAMILY LIMITED
Reel/Frame 068307/0229 →
Continuity (4)
Continuation 18051187 · Oct 31, 2022
Continuation PCTUS2021030530 · May 3, 2021
Provisional Application 63019192 · May 1, 2020
Related Publication 20240364546A1 · Oct 31, 2024
References Cited (29)
US 10398524B2 · Denny · 2019 [cited by applicant]
US 10902955B1 · Federoff · 2021 [cited by applicant]
US 10949217B1 · Nitsopoulos · 2021 [cited by applicant]
US 10991190B1 · Luthra · 2021 [cited by applicant]
US 12063318B2 · Walker · 2024 [cited by examiner]
US 20020087362A1 · Cobb · 2002 [cited by applicant]
US 20060264778A1 · Lim · 2006 [cited by applicant]
US 20150093735A1 · Smith · 2015 [cited by applicant]
US 20160063215A1 · Zamer · 2016 [cited by applicant]
US 20160246943A1 · Lake · 2016 [cited by applicant]
US 20180075202A1 · Davis · 2018 [cited by applicant]
US 20180197143A1 · Daub · 2018 [cited by applicant]
US 20190156931A1 · Skoda · 2019 [cited by applicant]
US 20190214116A1 · Eberting · 2019 [cited by applicant]
US 20200118164A1 · Defrank · 2020 [cited by applicant]
US 20210313069A1 · Williams · 2021 [cited by examiner]
US 20230081577A1 · Walker et al. · 2023 [cited by applicant]
WO 2018020382 · 2018 [cited by applicant]
WO 2018124501 · 2018 [cited by applicant]
WO 2019154600 · 2019 [cited by applicant]
WO 2021222908 · 2021 [cited by applicant]
Extended European Search Report for European Patent Application No. 21796025.1 mailed on May 3, 2024; 7 pgs. [cited by applicant]
International Search Report for Application PCT/US21/30530 dated Sep. 9, 2021; 2 pps. [cited by applicant]
International Written Opinion for Application PCT/US21/30530 dated Sep. 9, 2021; 8 pps. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/051,187 dated Mar. 20, 2024; 9 pps. [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Mar. 20, 2024 for U.S. Appl. No. 18/051,187 (pp. 1-9). [cited by applicant]
Notice of Allowance/Intention to Grant for Indonesian Patent Application No. P00202212978 mailed on Jun. 24, 2025 (1 page). [cited by applicant]
Notice of Allowance/Intention to Grant for Japanese Patent Application 2022-566002 dated Jul. 1, 2025 (2 pgs). [cited by applicant]
Office Action for Japanese Patent Application No. 2022-566002 mailed on Feb. 18, 2025 (9 pages). [cited by applicant]