Injection System and Method

• US 20180130552A1
• Filed: 07/06/2017
• Published: 05/10/2018
• Est. Priority Date: 07/14/2011
• Status: Abandoned Application

• Current Assignee: Liebel-Flarsheim Company (Mallinckrodt plc)
• Original Assignee: Liebel-Flarsheim Company (Mallinckrodt plc)
• Inventors: Ziemba, Robert J.
• Application Number:
  US15/643,270
• Publication Number:
  US 20180130552A1
• Time in Patent Office: Days
• CPC Class Codes: A61M 2005/14553 comprising a pressure jacket
• CPC Class Codes: A61M 2205/50 with microprocessors or computers
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 2205/60 with identification means
• CPC Class Codes: A61M 5/14546 Front-loading type injectors
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring

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

1. A method, comprising:

operating a first injection device that is located at a first facility operated by a first customer;

generating first injection data that is associated with said operating a first injection device step;

outputting said first injection data and addressed to an injection data system;

outputting a first request for a first customer injection data selection and addressed to said injection data system, wherein said first customer injection data selection is specific to said first customer;

entering authenticating data; and

receiving said first customer injection data selection in response to said first request, wherein said receiving step is only executed when said authenticating data matches first authentication data that is associated only with first customer injection data on said injection data system, wherein said first customer injection data is both specific to said first customer and comprises said first injection data, wherein said first customer injection data selection is based on at least a portion of said first customer injection data, and wherein said first authentication data being specific to said first customer injection data precludes injection data from all other customers on said injection data system from being included in said first customer injection data selection, said injection data from said all other customers on said injection data system being associated with other injection devices located at other facilities that are operated by said all other customers.

2. An injection data system, comprising:

one or more data storage devices;

first customer injection data stored on said one or more data storage devices and in association with a first customer that operates a first facility comprising a first injection device;

first customer authentication data stored on said one or more data storage devices and associated with said first customer injection data, wherein access to said first customer injection data on said one or more data storage devices requires receipt of customer authenticating data by said injection data system that matches said first customer authentication data;

second customer injection data stored on said one or more data storage devices and in association with a second customer that operates a different second facility comprising a second injection device;

second customer authentication data stored on said one or more data storage devices and associated with said second customer injection data, wherein access to said second customer injection data on said one or more data storage devices requires receipt of customer authenticating data by said injection data system that matches said second customer authentication data; and

a web-based customer interface associated with said one or more data storage devices, wherein receipt of customer authenticating data by said injection data system that matches said first customer authentication data only provides access to said first customer injection data that is stored on said one or more data storage devices and does not provide access to injection data of any other customers on said one or more data storage devices, and wherein receipt of customer authenticating data by said injection data system that matches said second customer authentication data only provides access to said second customer injection data that is stored on said one or more data storage devices and does not provide access to injection data of any other customers on said one or more data storage devices.

3. The system of claim 2, further comprising at least one server in communication with said one or more data storage devices.

4. The system of claim 2, further comprising at least one web-based application in communication with said one or more data storage devices.

5. The system of claim 2, wherein said first and second customer injection 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.

6. The system of claim 2, 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.

7. A method, comprising:

receiving first injection data at an injection data system, wherein said first injection data relates to a first injection device disposed a first facility that is operated by a first customer;

storing said first injection data on said injection data system;

associating first customer authentication data with all first customer injection data that is stored on said injection data system, wherein said first customer injection data is both specific to said first customer and comprises said first injection data;

receiving second injection data at said injection data system, wherein said second injection data relates to a second injection device disposed at a second facility that is operated by a second customer;

storing said second injection data on said injection data system, wherein said first and second customers are different from one another;

associating second customer authentication data with all second customer injection data that is stored on said injection data system, wherein said second customer injection data is both specific to said second customer and comprises said second injection data; and

providing access to customer injection data stored by said injection data system on a customer-by-customer basis such that receipt by said injection data system of first customer authenticating data that matches said first customer authentication data only provides access to said first customer injection data that is stored by said injection data system and does not provide access to injection data of any other customers on said injection data system, and such that receipt by said injection data system of second customer authenticating data that matches said second customer authentication data only provides access to said second customer injection data that is stored by said injection data system and does not provide access to injection data of any other customers on said injection data system.

8. The method of claim 7, wherein said first injection data and second injection 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.

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

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

11. The method of claim 7, wherein said storing said first injection data step comprises linking said first injection data with said first customer on said injection data system, and wherein said storing second injection data step comprises linking said second injection data with said second customer on said injection data system.

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

13. The method of claim 7, further comprising:

providing at least one web-based application for communicating with said injection data system.

14. The method of claim 7, further comprising:

providing a web-based interface for communicating with said injection data system.

15. The method of claim 7, further comprising:

granting said first customer access to said injection data system such that access to an entirety of said second customer injection data is prohibited; and

granting said second customer access to said injection data system such that access to an entirety of said first customer injection data is prohibited.

16. The method of claim 7, further comprising:

receiving a first request for a first customer injection data selection over the Internet and at said injection data system;

outputting said first customer injection data selection via the Internet and in response to said first request, wherein an entirety of said first customer injection data selection is based on at least a portion of said first customer injection data.

17. The method of claim 16, further comprising:

receiving a second request for a second customer injection data selection over the Internet and at said injection data system;

outputting said second customer injection data selection via the Internet and in response to said second request, wherein an entirety of said second customer injection data selection is based on at least a portion of said second customer injection data.

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

19. The method of claim 17, wherein said second customer injection data selection is specific to one injection device.

20. The method of claim 17, wherein said second customer injection data selection pertains to a plurality of different injection devices.

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

22. The method of claim 16, wherein said first customer injection data selection is specific to one injection device.

23. The method of claim 16, wherein said first customer injection data selection pertains to a plurality of different injection devices.