# US 2014/0156310 A1 · Injection Data Management System and Method

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0156310 A1
- Document ID: US20140156310A1
- Status: Published application
- Kind: A1
- Application number: 14/131,764
- Filed: 2012-07-03
- Published: 2014-06-05
- Earliest claimed: 2011-07-14
- Inventors: Robert J. Ziemba
- Web page: https://patentgrep.com/patent/US20140156310A1

## CPC

- A61M 5/14546: {Front-loading type injectors}
- G16H 20/17: delivered via infusion or injection
- A61M 2005/14553: {comprising a pressure jacket}
- A61M 2205/50: with microprocessors or computers
- A61M 2205/52: with memories providing a history of measured variating parameters of apparatus or patient
- A61M 2205/60: with identification means
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 40/67: for remote operation
- G16H 80/00: ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
- A61M: DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY (introducing media into or onto the bodies of animals A61D7/00; means for inserting tampons A61F13/26; devices for administering food or medicines orally A61J; containers for collecting, storing or administering blood or medical fluids A61J1/05); DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY (surgery A61B; chemical aspects of surgical articles A61L); DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR {(Electrotherapy, e.g. producing anaesthesia by the use of alternating or intermittent currents A61N1/36021)}
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

An injection data management system (172) is disclosed. Injection-related data (182) is stored on the injection data management system (172) on a customer-by-customer (122) basis. A given customer (122) may communicate with the injection data management system (172) over the Internet (160) using an appropriate data communications device (124). Upon providing appropriate authenticating data (146) to the system (172), a customer (122) can access, view, and/or assess its own injection-related data (182) that is stored on the system (172) over the Internet (160).

## Claims

### Claim 1

A method of managing injection-related data, comprising:
operating a first injection device;
generating first injection-related data that is associated with said operating a first injection device step;
outputting said first injection-related data to the Internet and addressed to an injection data management system;
outputting a first request for a first customer injection-related data selection to the Internet and addressed to said injection data management system, wherein said first customer injection-related data selection is specific to a single customer;
entering authenticating data; and
receiving said first customer injection-related data selection via the Internet and in response to said first request, wherein said receiving step is only executed when said authenticating data matches authentication data associated with said first customer injection-related data selection on said injection data management system, wherein said first customer injection-related data selection is at least partially based on at least a portion of said first injection-related data.

### Claim at position 2

2-35. (canceled)

### Claim 36

A method of managing injection-related data, comprising:
receiving first injection-related data at an injection data management system, wherein said first injection-related data relates to a first injection device which in turn is associated with a first customer;
storing said first injection-related data on said injection data management system;
receiving second injection-related data at said injection data management system, wherein said second injection-related data relates to a second injection device which in turn is associated with a second customer;
storing said second injection-related data on said injection data management system, wherein said first and second customers are different from one another; and
providing access to customer injection-related data stored by said injection data management system on a customer-by-customer basis such that each customer having access to said injection data management system only has access to their own said customer injection-related data that is stored by said injection data management system.

### Claim 37 (depends on 36)

The method of claim 36, wherein said first injection-related data and second injection-related data each relate to an injection procedure in which a fluid is injected and are each selected from a programmed fluid injection rate, an achieved fluid injection rate, date of injection, time of injection, a programmed volume of fluid to be injected, an achieved volume of said injected fluid, a type of said injected fluid, contrast media usage, a minimum fluid pressure that was generated, a maximum fluid pressure that was generated, an average fluid pressure that was generated, fluid injection rate as a function of time, injection pressure as a function of time, a lot number of said injected fluid, an iodine content of said injected fluid, an identity of a facility responsible for manufacturing said injected fluid, an identity of a facility responsible for packaging said injected fluid, a manufacturing date of said injected fluid, an expiration date of said injected fluid, the National Drug Code associated with said injected fluid, a volume of fluid remaining for use by said injection device upon completion of said injection procedure, and any combination thereof.

### Claim 38 (depends on 36)

The method of claim 36, wherein said injection data management system comprises at least one server on the Internet.

### Claim 39 (depends on 36)

The method of claim 36, wherein said receiving first injection-related data step and said receiving second injection-related data step each comprise utilizing the Internet.

### Claim 40 (depends on 36)

The method of claim 36, wherein said storing said first injection-related data step comprises linking said first injection-related data with said first customer on said injection data management system, and wherein said storing second injection-related data step comprises linking said second injection-related data with said second customer on said injection data management system.

### Claim 41 (depends on 36)

The method of claim 36, wherein said providing access step comprises restricting access to customer injection-related data, that is stored by said injection data management system in association with said first customer, to said first customer, and wherein said providing access step further comprises restricting access to customer injection-related data, that is stored by said injection data management system in association with said second customer, to said second customer.

### Claim 42 (depends on 36)

The method of claim 36, further comprising:
providing at least one web-based application for communicating with said injection data management system.

### Claim 43 (depends on 36)

The method of claim 36, further comprising:
providing a web-based interface for communicating with said injection data management system.

### Claim 44 (depends on 36)

The method of claim 36, further comprising:
associating first customer authentication data with all injection-related data stored by said injection data management system in association with said first customer; and
associating second customer authentication data with all injection-related data stored by said injection data management system in association with said second customer.

### Claim 45 (depends on 44)

The method of claim 44, further comprising:
receiving first customer authenticating data at said injection data management system, wherein said providing access step comprises providing access to said injection-related data stored by said injection data management system and associated with said first customer only when said first customer authenticating data matches said first customer authentication data.

### Claim 46 (depends on 45)

The method of claim 45, further comprising:
receiving second customer authenticating data at said injection data management system, wherein said providing access step further comprises providing access to said injection-related data stored by said injection data management system and associated with said second customer only when said second customer authenticating data matches said second customer authentication data.

### Claim 47 (depends on 36)

The method of claim 36, further comprising:
granting said first customer access to said injection data management system such that access to an entirety of said second injection-related data is prohibited; and
granting said second customer access to said injection data management system such that access to an entirety of said first injection-related data is prohibited.

### Claim 48 (depends on 36)

The method of claim 36, further comprising:
receiving a first request for a first customer injection-related data selection over the Internet and at said injection data management system;
outputting said first customer injection-related data selection via the Internet and in response to said first request, wherein said first customer injection-related data selection is at least partially based on at least a portion of said first injection-related data.

### Claim 49 (depends on 48)

The method of claim 48, further comprising:
receiving a second request for a second customer injection-related data selection over the Internet and at said injection data management system;
outputting said second customer injection-related data selection via the Internet and in response to said second request, wherein said second customer injection-related data selection is at least partially based on at least a portion of said second injection-related data.

### Claim 50 (depends on 49)

The method of claim 49, wherein said second customer injection-related data selection comprises data that relates to at least one injection procedure performed by said second customer.

### Claim 51 (depends on 49)

The method of claim 49, wherein said second customer injection-related data selection is specific to one injection device.

### Claim 52 (depends on 49)

The method of claim 49, wherein said second customer injection-related data selection pertains to a plurality of different injection devices.

### Claim 53 (depends on 48)

The method of claim 48, wherein said first customer injection-related data selection comprises data that relates to at least one injection procedure performed by said first customer.

### Claim 54 (depends on 48)

The method of claim 48, wherein said first customer injection-related data selection is specific to one injection device.

### Claim 55 (depends on 48)

The method of claim 48, wherein said first customer injection-related data selection pertains to a plurality of different injection devices.

### Claim 56

An injection data management system, comprising:
a platform in communication with the Internet;
first customer injection-related data stored on said platform and in association with a first customer;
first customer authentication data stored on said platform and associated with said first customer injection-related data, wherein access to said first customer-injection related data on said platform requires receipt of customer authentication data by said injection data management system that matches said first customer authentication data;
second customer injection-related data stored on said platform and in association with a second customer;
second customer authentication data stored on said platform and associated with said second customer injection-related data, wherein access to said second customer-injection related data on said platform requires receipt of customer authentication data by said injection data management system that matches said second customer authentication data; and
a web-based customer interface associated with said platform.

### Claim 57 (depends on 56)

The system of claim 56, wherein said platform comprises at least one server.

### Claim 58 (depends on 56)

The system of claim 56, wherein said platform comprises at least one web-based application.

### Claim 59 (depends on 56)

The system of claim 56, wherein said first and second customer injection-related data each relate to an injection procedure and are each selected from a programmed fluid injection rate, an achieved fluid injection rate, date of injection, time of injection, a programmed volume of fluid to be injected, an achieved volume of said injected fluid, a type of fluid injected, contrast media usage, customer contrast media inventory data, a minimum fluid pressure that was generated, a maximum fluid pressure that was generated, an average fluid pressure that was generated, fluid injection rate as a function of time, injection pressure as a function of time, a lot number of said injected fluid, an iodine content of said injected fluid, an identity of a facility responsible for manufacturing said injected fluid, an identity of a facility responsible for packaging said injected fluid, a manufacturing date of said injected fluid, an expiration date of said injected fluid, the National Drug Code associated with said injected fluid, a volume of fluid remaining for use by said injection device upon completion of said injection procedure, and any combination thereof.

### Claim 60 (depends on 56)

The system of claim 56, wherein said first customer authentication data comprises at least one of first user name and a first password, and wherein said second customer authentication data comprises at least one of second user name and a second password.

### Claim 61

(canceled)