Systems, methods, and computer program products for providing quick response (QR) codes for injection systems.
The QR code system addresses the challenge of accessing infusion system information by generating and displaying critical data, ensuring efficient communication and understanding of malfunctions, thus improving support services.
Patent Information
- Application Number
- JP2026028612
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-05-19
- Filing Date
- 2026-02-25
- Publication Date
- 2026-07-07
Smart Images

Figure 2026113462000001_ABST
Abstract
Description
Technical Field
[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 62 / 704,627, filed on May 19, 2020, the disclosure of which is hereby incorporated in its entirety by reference.
[0002] This disclosure generally relates to systems, devices, products, apparatuses, and methods used in connection with Quick Response (QR) codes (registered trademark), and in one particular embodiment, to systems, products, and methods for providing QR codes related to an infusion system.
Background Art
[0003] In medical diagnostic procedures and / or medical treatment procedures, infusion devices such as fluid infusion devices (e.g., drug delivery devices) may be used by medical personnel such as physicians. For example, medical personnel may use a fluid infusion device to inject one or more drugs into a patient. Fluid infusion devices can be used for the pressure injection of chemical solutions such as radiological contrast agents (e.g., contrast agents, radiological contrast agents, and / or cleaning agents such as physiological saline) in medical imaging procedures such as angiography, computed tomography (CT), ultrasound, magnetic resonance imaging (MRI), and positron emission tomography (PET). In some cases, fluid infusion devices are designed to deliver a preset amount of chemical solution at a preset flow rate.
Summary of the Invention
Means for Solving the Problems
[0004] Therefore, there is provided a system, device, product, apparatus, and / or method for providing a Quick Response (QR) code related to an infusion system, which improves the availability and / or accessibility of information related to the infusion system.
[0005] More embodiments or aspects not limited to this will be described in the following numbered sections.
[0006] Item 1: An injection system for providing a quick response (QR) code, comprising at least one processor that receives data relating to the injection system, generates network resources based on the data relating to the injection system, and when generating the network resources, the at least one processor is programmed or configured to encode the data relating to the injection system into network resources, generates a QR code based on the network resources, and is programmed or configured to display the QR code on the display screen of the injection system.
[0007] Item 2: The injection system according to Item 1, wherein the data relating to the injection system includes data relating to one or more operations of the injection system, and the QR code includes static data elements and dynamic data elements, the static data elements include data relating to an identifier of the injection system, and the dynamic data elements include data relating to one or more operations of the injection system.
[0008] Item 3: The injection system described in Item 1 or 2, wherein at least one processor is programmed or configured to encrypt network resources when generating a URL.
[0009] Item 4: The injection system according to any one of items 1 to 3, wherein at least one processor is programmed or configured to encode data relating to anomalies encountered during one or more operations of the injection system into network resources when encoding data relating to the injection system into network resources.
[0010] Item 5: The injection system according to any one of items 1 to 4, wherein, when displaying a QR code on a display screen, at least one processor is programmed or configured to display a QR code on a graphical user interface (GUI) displayed on the display screen of the injection system.
[0011] Item 6: The injection system according to any one of items 1 to 5, wherein the data relating to the injection system includes data relating to one or more operations of the injection system, and at least one processor is further programmed or configured to record data relating to one or more operations of the injection system.
[0012] Item 7: An injection system as described in any one of items 1 to 6, wherein the data relating to the injection system includes the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, the identifier of one or more software patches applied to the injection system, the media access control (MAC) address of the network interface controller (NIC) of the injection system, the identifier of an error relating to the operation of the injection system, or any combination thereof, and when encoding the data relating to the injection system into a network resource, at least one processor is programmed or configured to encode at least one of the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, the identifier of one or more software patches applied to the injection system, the MAC address of the NIC of the injection system, or the identifier of an error relating to the operation of the injection system into a network resource.
[0013] Item 8: An injection system according to any one of items 1 to 7, wherein the network resource includes a uniform resource locator (URL), and when generating the network resource, at least one processor is programmed or configured to encode data relating to the injection system into a URL.
[0014] Item 9: The injection system according to any one of items 1 to 8, wherein when generating a QR code, at least one processor is programmed or configured to generate a QR code based on a URL.
[0015] Item 10: A system for providing a quick response (QR) code relating to an injection system, comprising: an injection system; and at least one processor, which receives data relating to the injection system, generates network resources based on the data relating to the injection system, and when generating the network resources, is programmed or configured to encode the data relating to the injection system into network resources, generates a QR code based on the network resources, and is programmed or configured to display the QR code on a display screen of the injection system.
[0016] Item 11: The system according to Item 10, wherein the data relating to the injection system includes data relating to one or more operations of the injection system, and the QR code includes static data elements and dynamic data elements, the static data elements include data relating to an identifier of the injection system, and the dynamic data elements include data relating to one or more operations of the injection system.
[0017] Item 12: The system according to item 10 or 11, wherein at least one processor is programmed or configured to encrypt network resources when generating them.
[0018] Item 13: The system according to any one of items 10 to 12, wherein at least one processor is programmed or configured to encode data relating to anomalies encountered during one or more operations of the injection system into network resources when encoding data relating to the injection system into network resources.
[0019] Item 14: The system according to any one of items 10 to 13, wherein, when displaying a QR code on a display screen, at least one processor is programmed or configured to display a QR code on a graphical user interface (GUI) displayed on the display screen of the injection system.
[0020] Item 15: The system according to any one of items 10 to 14, wherein data relating to the injection system includes data relating to one or more operations of the injection system, and at least one processor is further programmed or configured to record data relating to one or more operations of the injection system.
[0021] Item 16: A system as described in any one of items 10 to 15, wherein data relating to an injection system includes the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, the identifier of one or more software patches applied to the injection system, the media access control (MAC) address of the network interface controller (NIC) of the injection system, the identifier of an error relating to the operation of the injection system, or any combination thereof, and when encoding the data relating to the injection system into a network resource, at least one processor is programmed or configured to encode the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, the identifier of one or more software patches applied to the injection system, the MAC address of the NIC of the injection system, or the identifier of an error relating to the operation of the injection system into a network resource.
[0022] Item 17: The system described in any one of items 10 to 16, wherein the network resource includes a uniform resource locator (URL), and when generating the network resource, at least one processor is programmed or configured to encode data relating to an injection system into a URL.
[0023] Item 18: The system described in any one of items 10 to 17, wherein, when generating a QR code, at least one processor is programmed or configured to generate a QR code based on a URL.
[0024] Item 19: A computer program product for providing a quick response (QR) code related to an injection system, the computer program product including at least one non - transient computer - readable medium containing one or more instructions which, when executed by at least one processor, cause the at least one processor to receive data related to the injection system, generate network resources based on the data related to the injection system, and when generating the network resources, the at least one processor is programmed or configured to encode the data related to the injection system into the network resources, generate a QR code based on the network resources, and display the QR code on a display screen of the injection system.
[0025] Item 20: The computer program product according to item 19, wherein the data related to the injection system includes data related to one or more operations of the injection system, the QR code includes static data elements and dynamic data elements, the static data elements include data related to an identifier of the injection system, and the dynamic data elements include data related to one or more operations of the injection system.
[0026] Item 21: The computer program product according to item 19 or 20, wherein one or more instructions that cause the at least one processor to generate network resources cause the at least one processor to encrypt the network resources.
[0027] Item 22: The computer program product according to any one of items 19 to 21, wherein one or more instructions that cause the at least one processor to encode data related to the injection system into network resources cause the at least one processor to encode data related to an abnormality encountered during one or more operations of the injection system into network resources.
[0028] Item 23: A computer program product according to any one of items 19 to 22, wherein one or more instructions for causing at least one processor to display a QR code on a display screen cause the at least one processor to display a QR code on a graphical user interface (GUI) displayed on the display screen of the injection system.
[0029] Item 24: A computer program product according to any one of items 19 to 23, wherein data related to the injection system includes data related to one or more operations of the injection system, and one or more instructions cause the at least one processor to further record data related to one or more operations of the injection system.
[0030] Item 25: Data related to the injection system includes the model number of the injection system, the serial number of the injection system, the software version of the injection system, the revision number of the software of the injection system, the identifier of one or more software patches applied to the injection system, the media access control (MAC) address of the network interface controller (NIC) of the injection system, the identifier of an error related to the operation of the injection system, or any combination thereof, and one or more instructions for causing at least one processor to encode data related to the injection system into a network resource cause the at least one processor to encode at least one of the model number of the injection system, the serial number of the injection system, the software version of the injection system, the revision number of the software of the injection system, the identifier of one or more software patches applied to the injection system, the MAC address of the NIC of the injection system, or the identifier of an error related to the operation of the injection system into a network resource. A computer program product according to any one of items 19 to 24.
[0031] Item 26: A computer program product as described in any one of items 19 to 25, wherein the network resource includes a uniform resource locator (URL), and one or more instructions causing at least one processor to generate the network resource cause at least one processor to encode data relating to an injection system into a URL.
[0032] Item 27: A computer program product as described in any one of items 19 to 26, wherein one or more instructions causing at least one processor to generate a QR code causes at least one processor to generate a QR code based on a URL.
[0033] Item 28: A method for providing a quick response (QR) code relating to an injection system, comprising: receiving data relating to an injection system with at least one processor; generating a network resource based on the data relating to the injection system with at least one processor, wherein the step of generating the network resource includes a step of encoding the data relating to the injection system into a network resource; generating a QR code based on the network resource with at least one processor; and displaying the QR code on a display screen with at least one processor.
[0034] Sub-sub
[0035] 30: The method according to 30 of the paragraph, wherein the step of generating a network resource includes the step of encrypting the network resource.
[0036] Item 31: The method according to any one of items 28 to 30, wherein the step of encoding data relating to the injection system into a network resource includes the step of encoding data relating to anomalies encountered during one or more operations of the injection system into a network resource.
[0037] Item 32: The method according to any one of items 28 to 31, wherein the injection system includes a display screen, and the step of displaying a QR code on the display screen includes the step of displaying a QR code on the display screen of the injection system.
[0038] Item 33: The method according to any one of items 28 to 32, wherein the data relating to the injection system includes data relating to one or more operations of the injection system, and the method further includes the step of recording data relating to one or more operations of the injection system.
[0039] Item 34: The method according to any one of items 28 to 33, wherein data relating to an injection system includes the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, the identifier of one or more software patches applied to the injection system, the media access control (MAC) address of the network interface controller (NIC) of the injection system, the identifier of an error relating to the operation of the injection system, or any combination thereof, and the step of encoding the data relating to the injection system into a network resource includes the step of encoding at least one of the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, the identifier of one or more software patches applied to the injection system, the MAC address of the NIC of the injection system, or the identifier of an error relating to the operation of the injection system into a network resource.
[0040] Item 35: The method according to any one of items 28 to 34, wherein the network resource includes a uniform resource locator (URL), and the step of generating the network resource includes the step of encoding data relating to an injection system into a URL.
[0041] Item 36: The method according to any one of items 28 to 35, wherein the step of generating a QR code includes the step of generating a QR code based on a URL.
[0042] These other features and characteristics of this disclosure, as well as the methods of operation and function of the relevant components of the structure, the combination of components, and the economics of manufacture, will become clearer when considered in light of the following description and the attached claims with reference to the attached drawings, all of which form part of this specification, and in various drawings, the same reference numerals refer to the corresponding components. However, it should be particularly understood that the drawings are for illustrative and illustrative purposes only and are not intended to define any limitations of this disclosure. As used herein and in the claims, the singular forms "a," "an," and "the" include plural references unless the context should be otherwise interpreted.
[0043] Further advantages and details of this disclosure will be described in more detail below with reference to the exemplary embodiments or aspects shown in the accompanying schematic drawings and appendices. [Brief explanation of the drawing]
[0044] [Figure 1] The diagrams herein illustrate not-limited embodiments or aspects of systems, devices, products, apparatus, and / or methods described herein in an environment in which they may be implemented in accordance with the principles of this disclosure. [Figure 2] Figure 1 shows a diagram of one or more systems or components of one or more devices, which are not limited to specific embodiments or aspects. [Figure 3A] This is a flowchart of an unspecified embodiment of the anticipated maintenance process. [Figure 3B]This is a flowchart illustrating how a quick response (QR) code may be generated, displayed, and scanned according to an embodiment not limited to the present disclosure. [Figure 4A] The following are not limited embodiments of a fluid injection system. [Figure 4B] The following are not limited embodiments of a fluid injection system. [Figure 4C] Another, not-limited, embodiment of the fluid injection system is shown. [Figure 5] This figure shows an unspecified embodiment of a uniform resource locator (URL) and an unspecified embodiment of a QR code. [Figure 6] This is a diagram of an unspecified embodiment of a graphical user interface including a QR code. [Figure 7] This is a diagram of an unspecified embodiment of a graphical user interface including a QR code. [Figure 8] This is a diagram of an unspecified embodiment of a graphical user interface including a QR code. [Figure 9] This is a diagram of an unspecified embodiment of a graphical user interface including a QR code. [Modes for carrying out the invention]
[0045] For the purposes of the following description, the terms “end,” “up,” “down,” “right,” “left,” “vertical,” “horizontal,” “upper,” “lower,” “lateral,” and “vertical,” and their derivatives, shall be used in this disclosure as they are oriented in the drawings. However, it should be understood that this disclosure assumes a variety of alternative variations and sequences of steps unless otherwise specified. It should also be understood that certain apparatuses and processes shown in the accompanying drawings and described below are merely exemplary embodiments or aspects of this disclosure. Accordingly, specific dimensions or other physical features relating to embodiments or aspects disclosed herein should not be construed as limiting unless otherwise indicated.
[0046] None of the aspects, components, elements, structures, actions, steps, functions, instructions, etc., used herein should be considered material or essential unless expressly stated otherwise. Also, as used herein, the articles "a" and "an" are intended to include one or more and may be used interchangeably with "one or more" and "at least one." Furthermore, as used herein, the term "set" is intended to include one or more (e.g., related, unrelated, a combination of related and unrelated) and may be used interchangeably with "one or more" or "at least one." When only one is intended, "one" or a similar word is used. Also, as used herein, "has," "have," "having," etc., are intended to be unrestrictive terms. Furthermore, the phrase "based on" is intended to mean "at least partially based on" unless expressly stated otherwise.
[0047] As used herein, the terms “communicate” and “communicate” may refer to the reception, acceptance, transmission, forwarding, provision, etc., of information (data, signals, messages, instructions, commands, etc.). When one unit (device, system, component of device or system, combination thereof, etc.) communicates with another unit, it means that one unit can directly or indirectly receive information and / or transmit information to the other unit. This may actually refer to direct or indirect wired and / or wireless connections. Also, two units may communicate with each other even if the transmitted information is modified, processed, relayed, and / or routed between the first unit and the second unit. For example, the first unit can be said to be communicating with the second unit even if the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit can be said to be communicating with a second unit if at least one intermediate unit (for example, a third unit positioned between a first unit and a second unit) processes information received from the first unit and transmits the processed information to the second unit. In some non-limited embodiments, a message may refer to a network packet containing data (such as a data packet). It will be understood that many other configurations are possible.
[0048] As used herein, the term “system” may refer to one or more computer devices, or a combination of computer devices such as processors, servers, client devices, software applications, and / or other similar components, but not limited to these. In addition, as used herein, “server” or “processor” may refer to a previously described server and / or processor, another server and / or processor, and / or a combination of servers and / or processors, as described as performing the steps or functions described herein. For example, as used in the specification and claims, a first server and / or first processor described as performing the first step or function may refer to the same or a different server and / or processor described as performing the second step or function.
[0049] In some cases, a fluid injection system may be part of a group of devices used in medical facilities such as hospitals during patient treatment. However, information about the fluid injection system may not be readily available while it is in operation. For example, a fluid injection system may malfunction during fluid injection, and information about the malfunction may not be readily available to the user of the fluid injection system or to the support staff responsible for providing technical support for the fluid injection system. In addition, the fluid injection system may not display enough information for the user to understand the details of the malfunction. For example, the display screen of the fluid injection system may contain only limited space for displaying information to the user. Furthermore, the user may encounter difficulties when trying to relay information about the malfunction to technical support.
[0050] In some non-limited embodiments, a Quick Response (QR) code may include a type of matrix barcode (e.g., a two-dimensional barcode) which is a machine-readable optical label containing information about an object (e.g., the object to which the QR code is attached). In some non-limited embodiments, a QR code may include data relating to a locator, identifier, or tracker pointing to a website and / or application. A QR code may use one of four standardized encoding modes (numeric, alphanumeric, byte / binary, and kanji) to store the data. Alternatively, a QR code may consist of black squares arranged within a grid of squares on a white background and can be read by a reader such as a camera. The image received by the reader based on the reading of the QR code may be processed using Reed-Solomon coding until the image of the QR code can be properly interpreted. The data encoded in the QR code may be retrieved based on patterns present in the horizontal and / or vertical components of the image.
[0051] Embodiments or aspects not limited to this disclosure relate to systems, devices, products, apparatus, and / or methods for providing quick response (QR) codes relating to an injection system. In some non-limited embodiments, the QR code system includes an injection system and at least one processor, the at least one processor being programmed or configured to receive data relating to the injection system, generate a uniform resource locator (URL) based on the data relating to the injection system, and, when generating the URL, encode the data relating to the injection system into one or more fields of the URL, generate a QR code based on the URL, and be programmed or configured to display the QR code on the display screen of the injection system. In some non-limited embodiments, the QR code includes static data elements and dynamic data elements, the static data elements including data relating to an identifier of the injection system, and the dynamic data elements including data relating to one or more operations of the injection system. In some non-limited embodiments, when generating the URL, the at least one processor is programmed or configured to encrypt one or more fields of the URL. In some non-limited embodiments, when encoding data relating to the injection system into one or more fields of a URL, at least one processor is programmed or configured to encode data relating to anomalies encountered during one or more operations of the injection system into one or more fields of a URL. In some non-limited embodiments, when displaying a QR code on a display screen, at least one processor is programmed or configured to display the QR code on the graphical user interface (GUI) displayed on the display screen of the injection system. In some non-limited embodiments, the data relating to the injection system includes data relating to one or more operations of the injection system, and at least one processor is further programmed or configured to record the data relating to one or more operations of the injection system.In some non-limited embodiments, data relating to the injection system includes the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, identifiers of one or more software patches applied to the injection system, the media access control (MAC) address of the network interface controller (NIC) of the injection system, identifiers of errors relating to the operation of the injection system, or any combination thereof, and when encoding data relating to one or more operations of the injection system into one or more fields of the URL, at least one processor is programmed or configured to encode at least one of the model number of the injection system, the serial number of the injection system, the software version of the injection system, the software revision number of the injection system, identifiers of one or more software patches applied to the injection system, the MAC address of the NIC of the injection system, or identifiers of errors relating to the operation of the injection system into one or more fields of the URL.
[0052] In this way, embodiments of the present disclosure, not limited to this one, enable immediate access to information about the fluid injection system. In particular, when the fluid injection system malfunctions during fluid injection operation, information about the malfunction can be immediately made available via a QR code to the user of the fluid injection system and / or the person providing support services for the fluid injection system. In addition, information about the malfunction may be provided to the user of the fluid injection system and / or the person providing support services for the fluid injection system via the URL on which the QR code is derived, thereby enabling a more accurate understanding of the malfunction. Furthermore, information about malfunctions in the fluid injection system can be provided more accurately than if the user were to attempt to relay the information to the person providing support services. Moreover, the user of the fluid injection system is not required to maintain redundant physical records of many aspects of the fluid injection system, including warranty information, license information, and service history records.
[0053] Referring here to Figure 1, which is a diagram of an exemplary environment 100 in which the equipment, systems, and / or methods described herein may be implemented. As shown in Figure 1, the environment 100 includes a quick response (QR) code system 102, an injection system 104, a workstation device 106, a remote support system 108, a user device 110, and a communication network 112. In some non-limited embodiments, the QR code system 102, the injection system 104, the workstation device 106, the remote support system 108, and / or the user device 110 may be interconnected by wired connections, wireless connections, or a combination of wired and wireless connections.
[0054] In some non-limited embodiments, the QR code system 102 includes one or more devices capable of communicating with the injection system 104, the workstation equipment 106, the remote support system 108, and / or the user equipment 110 via a communication network 112. For example, the QR code system 102 may include computer equipment such as a computer, a server, a group of servers, and / or other similar devices. In some non-limited embodiments, the QR code system 102 may be configured to receive data about the injection system (e.g., the injection system 104), generate a uniform resource locator (URL), and / or generate a QR code based on the URL. In some non-limited embodiments, the QR code system 102 may be a component of the injection system 104 and / or the workstation equipment 106.
[0055] In some non-limited embodiments, the infusion system 104 includes one or more devices capable of communicating with a QR code system 102, a workstation device 106, a remote support system 108, and / or user device 110 via a communication network 112. For example, the infusion system 104 may include computer equipment such as one or more computers, servers, server clusters, and / or other similar devices. In some non-limited embodiments, the infusion system 104 includes one or more infusion devices (e.g., one or more fluid infusion devices). In some non-limited embodiments, the infusion system 104 is configured to administer (e.g., inject, deliver, etc.) a contrast fluid containing a contrast agent to a patient, and / or to administer an aqueous fluid such as saline to the patient before, during, and / or after the administration of the contrast fluid. For example, the infusion system 104 may directly inject one or more predetermined doses of contrast fluid into the patient's bloodstream via a subcutaneous needle and syringe. In some non-limited embodiments, the infusion system 104 may be configured to continuously administer aqueous fluid to the patient through a peripheral venous line (PIV) and catheter, and one or more predetermined doses of contrast fluid may be introduced into the PIV and administered to the patient via the catheter. In some non-limited embodiments, the infusion system 104 is configured to infuse a single dose of contrast fluid to the patient, followed by the administration of a specific amount of aqueous fluid.
[0056] In some non-limited embodiments, the injection system 104 is issued as U.S. Patent Application No. 09 / 715,330, filed November 17, 2000, issued as U.S. Patent No. 7,094,216, filed October 18, 2001, issued as U.S. Patent Application No. 09 / 982,518, filed April 16, 2004, issued as U.S. Patent No. 7,556,619, filed April 16, 2004, and issued as U.S. Patent No. 8,337,456. This application may include one or more exemplary injection systems or injectors disclosed in U.S. Patent Application No. 12 / 437,011, filed on 7 May 2009 and issued as U.S. Patent No. 8,147,464, U.S. Patent Application No. 12 / 476,513, filed on 2 June 2009 and issued as U.S. Patent No. 8,540,698, U.S. Patent Application No. 11 / 004,670, filed on 3 December 2004, each of these disclosures is incorporated in whole by reference. In some non-limited embodiments, the injection system 104 may include the MEDRAD® Stellant CT Injection System, the MEDRAD® Stellant Flex CT Injection System, the MEDRAD® MRXperion MR Injection System, the MEDRAD® Mark 7 Arterion Injection System, the MEDRAD® Intego PET Infusion System, or the MEDRAD® Centargo CT Injection System, all of which are supplied by Bayer.
[0057] In some non-limited embodiments, the workstation equipment 106 includes one or more devices capable of communicating with the QR code system 102, the injection system 104, the remote support system 108, and / or user equipment 110 via a communication network 112. For example, the workstation equipment 106 may include computer equipment, such as one or more computers including desktop computers, laptop computers, and tablets. In some non-limited embodiments, the workstation equipment 106 may provide a control interface for controlling the operation of the injection system 104, including providing input to the injection system 104. In addition to or instead of this, the workstation equipment 106 may display operating parameters of the injection system 104 during its operation (e.g., during real-time operation). In some non-limited embodiments, the workstation equipment 106 may provide interconnectivity between the injection system 104 and other devices or systems, such as a scanner device (not shown). In some non-limited embodiments, the workstation equipment 106 may include a Certegra® Workstation provided by Bayer.
[0058] In some non-limited embodiments, the remote support system 108 may include one or more devices capable of communicating with the QR code system 102, the injection system 104, the workstation equipment 106, and / or the user equipment 110 via the communication network 112. For example, the remote system 108 may include computer equipment such as a computer, a server (e.g., a web server), a group of servers, and / or other similar devices. In some non-limited embodiments, the remote support system 108 may include a backend system relating to the QR code system 102, the injection system 104, and / or the workstation equipment 106. In some non-limited embodiments, the remote support system 108 may include a cloud computing system that stores data in an associated database. In some non-limited embodiments, the remote support system 108 may be capable of interacting with the injection system 104 to provide functions such as remote device services for the injection system 104 (e.g., VirtualCARE® remote device support services for the injection system, and equipment provided by Bayer). In some non-limited embodiments, the remote support system 108 may be operated by or on behalf of the original equipment manufacturer (OEM) of the injection system 104 (e.g., an OEM of one or more components or devices of the injection system 104), the provider of the injection system 104, the filming location or hospital where the injection system 104 is operated, or a service technician in charge of the injection system 104.
[0059] In some non-limited embodiments, the user device 110 may include one or more devices capable of communicating with the QR code system 102, the injection system 104, the workstation device 106, and / or the remote support system 108 via the communication network 112. For example, the user device 110 may include computer equipment, such as a computer including a desktop, laptop, or tablet, or a mobile device such as a smartphone. In some non-limited embodiments, the user device 110 may be capable of reading (e.g., scanning) barcodes such as QR codes.
[0060] In some non-limited embodiments, the communication network 112 may include one or more wired and / or wireless networks. For example, the communication network 112 may include cellular networks (such as Long-Term Evolution (LTE) networks, 3G networks, 4G networks, 5G networks, and Code Division Multiple Access (CDMA) networks), public land mobile networks (PLMNs), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), telephone networks (e.g., public switched telephone networks (PSTNs)), private networks, ad hoc networks, intranets, the Internet, fiber optic-based networks, cloud computing networks, short-range wireless communication networks (e.g., Bluetooth® networks, near-field communication (NFC) networks), and / or combinations thereof, and other types of networks.
[0061] The number and configuration of systems, devices, and networks shown in Figure 1 are provided as examples. There may be additional systems and / or devices, fewer systems and / or devices, different systems and / or devices, and / or systems and / or devices with different configurations than those shown in Figure 1. Furthermore, two or more systems or devices shown in Figure 1 may be implemented within a single system or single device, or a single system or single device shown in Figure 1 may be implemented as multiple dedicated systems or devices. In addition to or instead of this, a set of systems or devices in environment 100 (e.g., one or more systems, one or more devices) may perform one or more functions that have been described as being performed by another set of systems or another set of devices in environment 100.
[0062] Referring now to Figure 2, which is a diagram of exemplary components of the device 200. The device 200 may correspond to one or more devices of the QR code system 102, one or more devices of the injection system 104, a workstation device 106, one or more devices of the remote support system 108, and / or user equipment 110. In some non-limited embodiments, the QR code system 102, the injection system 104, the workstation device 106, the remote support system 108, and / or user equipment 110 may include at least one device 200, and / or at least one component of the device 200. As shown in Figure 2, the device 200 may comprise a bus 202, a processor 204, memory 206, storage component 208, input component 210, output component 212, and a communication interface 214.
[0063] Bus 202 may include components that enable communication between components of the device 200. In some non-limited embodiments, the processor 204 may be implemented in hardware, software, or a combination of hardware and software. For example, the processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an acceleration processing unit (APU), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC)). Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, optical memory) that store information and / or instructions used by the processor 204.
[0064] The storage component 208 may store information and / or software relating to the operation and use of the device 200. For example, the storage component 208 may include, along with a corresponding drive, a hard disk (such as a magnetic disk, optical disk, magneto-optical disk, or solid-state disk), a compact disc (CD), a digital multipurpose disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of computer-readable media.
[0065] The input component 210 may include components that allow the device 200 to receive information via user input (such as a touch screen display device, keyboard, keypad, mouse, button, switch, microphone, etc.). In addition to or instead of this, the input component 210 may include sensors that sense information (such as a Global Positioning System (GPS) component, accelerometer, gyroscope, actuator, etc.). The output component 212 may include components that provide output information from the device 200 (such as a display device, speaker, one or more light-emitting diodes (LEDs), etc.).
[0066] The communication interface 214 may include transceiver-like components (such as a transceiver, separate transmitter and receiver) that enable the device 200 to communicate with other devices via wired connection, wireless connection, or a combination of wired and wireless connections. The communication interface 214 may enable the device 200 to receive information from and / or provide information to other devices. For example, the communication interface 214 may include an Ethernet interface, optical interface, coaxial interface, infrared interface, radio frequency (RF) interface, general-purpose serial bus (USB) interface, Wi-Fi® interface, cellular network interface, etc.
[0067] The apparatus 200 may perform one or more processes described herein. These processes may be performed based on a processor 204 that executes software instructions stored in a computer-readable medium, such as memory 206 and / or storage component 208. A computer-readable medium (e.g., a non-temporary computer-readable medium) is defined herein as a non-temporary memory device. A memory device may include a memory space located within a single physical storage device, or a memory space spanning multiple physical storage devices.
[0068] Software instructions may be read into memory 206 and / or storage component 208 from another computer-readable medium or another device via the communication interface 214. When executed, the software instructions stored in memory 206 and / or storage component 208 may cause the processor 204 to execute one or more processes described herein. In addition to or instead of this, direct-coupled circuits may be used in place of or in combination with software instructions to execute one or more processes described herein. Therefore, the embodiments or aspects described herein are not limited to any particular combination of hardware circuits and software.
[0069] The number and configuration of components shown in Figure 2 are provided as examples. In some non-limiting embodiments, the apparatus 200 may have additional components, fewer components, different components, or components with different configurations than those shown in Figure 2. In addition to or instead of this, a set of components of the apparatus 200 (such as one or more components) may perform one or more functions that have been described as being performed by another set of components of the apparatus 200.
[0070] Referring here to Figure 3A, Figure 3A is a flowchart of an unlimited embodiment or aspect of a process 300 for providing a QR code relating to an injection system. In some unlimited embodiments, one or more steps of process 300 are performed (e.g., entirely or partially) by the QR code system 102 (e.g., one or more devices of the QR code system 102). In some unlimited embodiments, one or more steps of process 300 are performed (e.g., entirely or partially) by another device or group of devices that are separated from or include the QR code system 102, such as the injection system 104 (e.g., one or more devices of the injection system 104), workstation equipment 106, remote support system 108 (e.g., one or more devices of the remote support system 108), and / or user equipment 110. Aspects of unlimited embodiments described herein may be described with respect to a uniform resource locator (URL). According to some unlimited embodiments, a uniform resource indicator (URI) may be replaced with a URL where a URL is described.
[0071] As shown in Figure 3A, in step 302, process 300 includes the step of receiving data relating to the infusion system. For example, the QR code system 102 may receive data relating to the infusion system 104. In some non-limited embodiments, the QR code system 102 may receive data relating to the infusion system 104 from the infusion system 104, the workstation equipment 106, the remote support system 108, the user equipment 110, and / or one or more other devices relating to the operation, medical procedures, patient, and / or user or operator of the infusion system 104 (e.g., a power system, imaging devices or scanners such as computed tomography (CT) systems and magnetic resonance imaging (MRI) systems, patient devices such as patient identification devices (wearable radio frequency identification (RFID) tags, and / or computer equipment)). In some non-limited embodiments, the QR code system 102 may receive data relating to the injection system 104 on a continuous, periodic, and / or basis for operations performed on the injection system 104, such as operations performed by the injection system 104, diagnostic operations performed by the injection system 104, benchmark services performed by the injection system 104, startup (e.g., boot-up, power-on, power-up) operations performed by the injection system 104, and / or user requests for shutdown (e.g., power-off, power-down) of the injection system 104. In some non-limited embodiments, the QR code system 102 may receive data relating to the injection system 104 by retrieving data relating to the injection system 104 from memory such as the injection system 104, workstation equipment 106, or remote support system 108 (e.g., cloud data storage location of remote support system 108). In some non-limited embodiments, the QR code system 102 may use a log scrubber to remove certain data from the data relating to the injection system 104.For example, the QR code system 102 may use a log scrubber to remove sensitive data (e.g., sensitive personal data such as protected health information (PHI) and personal information (PII)) from the data relating to the injection system 104.
[0072] In some non-limited embodiments, data relating to the injection system 104 may include data relating to the identification of the injection system 104. For example, data relating to the injection system 104 may include data relating to the identifier of the injection system 104 (e.g., device identifier of the injection system 104, such as the model number of the injection system 104 or the serial number of the injection system 104), data relating to the software or hardware of the injection system 104 (e.g., software configuration of the injection system 104, hardware configuration of the injection system 104, software version of the injection system 104, such as the software version of the operating system of the injection system 104, revision number of the software of the injection system 104, identifiers of one or more software patches applied to the injection system 104, etc.), and / or data relating to the network connectivity of the injection system 104 (e.g., Media Access Control (MAC) address of the network interface controller (NIC) of the injection system 104, Internet Protocol (IP) address of the injection system 104). In some non-limited embodiments, data relating to the injection system 104 may include data relating to one or more operations of the injection system 104. Data relating to one or more operations of the injection system 104 may include data related to operations performed by the injection system 104 (e.g., the number of fluid injection operations performed by the injection system 104, the number of fluid injection operations performed by the injection system 104, the operation parameters of the fluid injection operations performed by the injection system 104, and data relating to patient demographics for patients to whom fluid injection operations were performed by the injection system 104), data relating to the configuration of the injection system 104 (e.g., the configuration of the fluid delivery components of the injection system 104, the cybersecurity bill of materials (CBOM) of the injection system 104), and / or data relating to anomalies encountered during one or more operations of the injection system 104. In some non-limited embodiments, the QR code system 102 may record data relating to the injection system 104 (e.g., stored in a data log). For example, the QR code system 102 may record data relating to one or more operations of the injection system 104.It should be noted that the embodiments of this disclosure comply with all legal requirements, such as the Health Insurance Portability and Accountability Act (HIPAA), and as a result, the data relating to the infusion system 104 that is stored or communicated may not include, where necessary, patient personal health information such as PHI or PII.
[0073] In some non-limiting embodiments, the operating parameters of the fluid injection operation performed by the injection system 104 may include one or more exemplary data types disclosed in U.S. Patent Application No. 10 / 143,562, filed on 10 May 2002, issued as U.S. Patent No. 7,457,804; U.S. Patent Application No. 12 / 254,318, filed on 20 October 2008, issued as U.S. Patent No. 7,996,381; and U.S. Patent Application No. 13 / 180,175, filed on 11 July 2011, issued as U.S. Patent No. 8,521,716, each of which is incorporated in whole by reference.
[0074] In some non-limited embodiments, data relating to an anomaly encountered during one or more operations of the injection system 104 may include an identifier for an error relating to the operation of the injection system 104. The identifier for an error relating to the operation of the injection system 104 may include an error code (e.g., a specific error code relating to the type of anomaly encountered). In addition to or instead of this, data relating to an anomaly encountered during one or more operations of the injection system 104 may include operating parameters of the injection system 104 relating to the anomaly. For example, data relating to an anomaly encountered during one or more operations of the injection system 104 may include temperature measurements of components of the injection system 104, measurements of electrical characteristics of electrical components of the injection system 104 (e.g., voltage, current, power, etc.), and / or variables and / or other relevant values of system components.
[0075] As further shown in Figure 3A, in step 304, process 300 includes the step of generating network resources. For example, the QR code system 102 may generate network resources (e.g., secure network resources) based on data relating to the injection system 104. In some non-limited embodiments, network resources may include uniform resource locators (URLs) (e.g., secure URLs), emails, messaging service messages (e.g., short message service (SMS) messages or text messages), files on the network system, etc. In some non-limited embodiments, the QR code system 102 may generate network resources (e.g., automatically) based on the step of receiving data relating to the injection system 104. In some non-limited embodiments, the QR code system 102 may generate network resources based on the step of receiving a request to generate a QR code (e.g., a user request) or a request to generate network resources.
[0076] In some non-limited embodiments, network resources include URLs, and URLs may include links to services. For example, URLs may include links to services that enable users to obtain equipment services from technical support for injection system 104, services that enable users to obtain documentation about injection system 104, and services that enable users to upload data about injection system 104 (e.g., product and / or warranty registration data for injection system 104, such as the model number of injection system 104, the serial number of injection system 104, and the purchase date of injection system 104, and licensing data for the functions of injection system 104, such as data for license renewal applications for the functions of injection system 104) to a location (e.g., a secure server location associated with remote support system 108). In some non-limited embodiments, the URL may include a link to a website (e.g., a webpage of the website) containing equipment-specific files for the injection system 104, such as product documentation data files (e.g., user manuals, operating instructions, training videos, function orders, work instructions, part numbers, software versions, software licenses, etc.), sales documentation data files (e.g., invoices, warranty certificates, service plan documents), and / or service history documentation data files (e.g., documents describing previously performed maintenance and / or repair services, and installation documents). In some non-limited embodiments, the URL may include a link to a remote support system 108. For example, the URL may include a link to an entity of the remote support system 108 that provides equipment services for the injection system 104. In some non-limited embodiments, the URL may include a link to an Enterprise Resource Planning (ERP) system (e.g., an ERP system relating to the remote support system 108). In some non-limited embodiments, the URL may include a link to an application and / or service (e.g., a web service) that performs a function, such as performing a function to locate the injection system 104.
[0077] In some non-limited embodiments, the QR code system 102 may encode data relating to the injection system 104 into one or more fields of a network resource (e.g., a URL) (e.g., into one or more values of one or more fields). For example, the QR code system 102 may encode data relating to anomalies encountered during one or more operations of the injection system 104 into one or more fields of the network resource. In some non-limited embodiments, the network resource may include multiple fields. In one example, the network resource may include a first field for an identifier of the injection system 104, a second field for an identifier of a service to which the network resource provides a link, and a third field containing data relating to the injection system 104 to the service to which the network resource provides a link. In such an example, the first field may include a model number or serial number of the injection system 104, the second field may include an identifier of a service providing technical support for the injection system 104, and the third field may include an error code relating to anomalies encountered during the operation of the injection system 104.
[0078] In some non-limited embodiments, the QR code system 102 may encrypt one or more fields of a network resource (for example, to one or more values of one or more fields). For example, the QR code system 102 may encrypt one or more fields of a network resource using Pretty Good Privacy (PGP) encryption technology. In some non-limited embodiments, the remote support system 108 may decrypt one or more encrypted fields of a network resource. For example, the remote support system 108 may decrypt one or more encrypted fields of a network resource using the PGP encryption technology used to encrypt the one or more encrypted fields.
[0079] As further shown in Figure 3A, in step 306, process 300 includes the step of generating a quick response (QR) code. For example, the QR code system 102 may generate a QR code based on network resources. In some non-limited embodiments, the QR code system 102 may generate (e.g., automatically) a QR code based on the step of generating network resources. In some non-limited embodiments, the QR code system 102 may generate a QR code that is displayed on a display screen. For example, the QR code system 102 may generate a QR code that is displayed as part of a graphical user interface (GUI), which is displayed on the display screens of the injection system 104, workstation equipment 106, remote support system 108, and / or user equipment 110.
[0080] In some non-limited embodiments, the QR code may include one or more static data elements relating to the injection system 104 and one or more dynamic data elements relating to the injection system 104. In some non-limited embodiments, the static data elements relating to the injection system 104 may include data elements whose values do not change after the injection system 104 is set up (e.g., initial activation for performing a fluid injection operation). In some non-limited embodiments, the dynamic data elements relating to the injection system 104 may include data elements whose values change after the injection system 104 is set up. In some non-limited embodiments, the static data elements may include data relating to an identifier of the injection system, such as the model number or serial number of the injection system 104. In some non-limited embodiments, the dynamic data elements may include data relating to one or more operations of the injection system, such as data relating to anomalies encountered during one or more operations of the injection system 104, and / or data relating to one or more operations of the injection system 104.
[0081] In some non-limited embodiments, the QR code system 102 can generate a QR code, and when the QR code is scanned, the QR code causes the user device 110 to perform a function. For example, the QR code system 102 can generate a QR code, and when the QR code is scanned, the QR code causes the user device 110 to open a web browser containing a web page based on the URL from which the QR code was generated. In another example, the QR code system 102 can generate a QR code, and when the QR code is scanned, the QR code causes the user device 110 to synchronize data about the injection system 104 with the remote support system 108 when the injection system 104 is not connected to the remote support system 108 (for example, when it is not connected via the communication network 112). In yet another example, the QR code system 102 can generate a QR code, and when the QR code is scanned, the QR code causes the user device 110 to register data about the injection system 104 with the remote support system 108 when the injection system 104 is not connected to the remote support system 108 (for example, when it is not connected via the communication network 112). In yet another example, the QR code system 102 can generate a QR code, and when scanned, the QR code causes the user device 110 to send data about an anomaly encountered during the operation of the injection system 104 to the remote support system 108. In yet another example, the QR code system 102 can generate a QR code, and when scanned, the QR code causes the user device 110 to create a license file for the injection system 104 (for example, a file of licensed functions) to send to the remote support system 108. In yet another example, the QR code system 102 can generate a QR code, and when scanned, the QR code causes the user device 110 to activate the warranty registration of the injection system 104 to the remote support system 108. In yet another example, the QR code system 102 can generate a QR code, and when scanned, the QR code causes the user device 110 to send data about the injection system 104 to upload to the remote support system 108.
[0082] In some non-limited embodiments, the QR code system 102 may generate QR codes based on user profiles. For example, the QR code system 102 may generate QR codes based on levels of access to user profiles (e.g., a user profile of a user relating to user equipment 110). In some non-limited embodiments, levels of access to user profiles may include a first access level for a user profile for a field service engineer, a second access level for a user profile for a service support personnel, a third access level for a user profile for a purchaser (e.g., a user who purchased the injection system 104), and a fourth access level for a user profile for a seller (e.g., a wholesaler or distributor of the injection system 104). In some non-limited embodiments, the QR code system 102 may generate QR codes so that only specified user profiles associated with specified access levels can scan the QR codes and access network resources associated with the QR codes (e.g., network resources based on the generated QR code).
[0083] In some non-limited embodiments, the QR code system 102 may generate a QR code and one or more cryptographic keys for accessing the network resources associated with the QR code. For example, the QR code system 102 may generate a QR code and a private cryptographic key of a public / private cryptographic key pair so that a user can access the network resources associated with the QR code (e.g., access its services). In some non-limited embodiments, the private cryptographic key may provide access to the injection system 104.
[0084] In some non-limited embodiments, the QR code system 102 may generate a first QR code and a second QR code. For example, the QR code system 102 may generate a first QR code that is displayed as part of a GUI, which is displayed on the display screens of the injection system 104, workstation equipment 106, and / or user equipment 110. In addition, the QR code system 102 may generate a second QR code that is displayed as part of a GUI, which is displayed on the display screen of the remote support system 108. In some non-limited embodiments, the QR code system 102 may generate a first QR code and a second QR code such that the first QR code is identical to the second QR code. For example, the QR code system 102 may generate a first QR code and a second QR code based on the same network resource.
[0085] As further shown in Figure 3A, in step 308, process 300 includes the step of displaying a QR code on a display screen. For example, the QR code system 102 may display (e.g., be made to display) a QR code on the display screens of the injection system 104, workstation equipment 106, remote support system 108, and / or user equipment 110. In some non-limited embodiments, the QR code system 102 may display a QR code within a GUI displayed on the display screens of the injection system 104, workstation equipment 106, remote support system 108, and / or user equipment 110.
[0086] In some non-limited embodiments, the user device 110 may read (e.g., scan) the QR code. For example, the user device 110 may read the QR code using a reader on the user device 110, such as a camera. In some non-limited embodiments, the user device 110 may generate a message based on the reading of the QR code. For example, the user device 110 may generate a short message service (SMS) message (e.g., a text message) and / or an email message based on the reading of the QR code. In some non-limited embodiments, the message may have a template to add data about the injection system 104, which is encoded in the QR code. In addition to or instead of this, the message may have one or more fields that the user can input to add one or more fields. In some non-limited embodiments, the user device 110 may send (e.g., automatically send) the message based on the reading of the QR code. In some non-limited embodiments, the user device 110 may send a message based on the receipt of user input.
[0087] In some non-limited embodiments, the user device 110 may perform actions (e.g., automatically) related to services associated with the network resource from which the QR code was generated, based on the reading of the QR code. In one example, the user device 110 may open a web browser containing a web page based on the network resource from which the QR code was generated, based on the reading of the QR code. In another example, when the injection system 104 is not connected to the remote support system 108 (e.g., not connected via the communication network 112), the user device 110 may synchronize data about the injection system 104 with the remote support system 108. In yet another example, when the injection system 104 is not connected to the remote support system 108 (e.g., not connected via the communication network 112), the user device 110 may register data about the injection system 104 with the remote support system 108. In yet another example, the user device 110 may transmit data about anomalies encountered during the operation of the injection system 104 to the remote support system 108. In yet another example, user device 110 may create a file for the injection system 104 (e.g., a license file) to send to the remote support system 108. In yet another example, user device 110 may use the remote support system 108 to activate the warranty registration for the injection system 104. In yet another example, user device 110 may send data about the injection system 104 to upload to the remote support system 108.
[0088] In some non-limited embodiments, the user device 110 may provide (e.g., transmit) data relating to the user device 110, the injection system 104, and / or the workstation device 106 based on the reading of the QR code. For example, the user device 110 may open a web page based on the URL from which the QR code was generated based on the reading of the QR code, and the user device 110 may transmit location data (e.g., GPS data relating to location) relating to the location of the user device 110, the injection system 104, and / or the workstation device 106 via the web page.
[0089] Referring now to Figure 3B, Figure 3B is a flowchart of an embodiment 310 of a process (e.g., process 300) showing how a QR code can be generated, displayed, and scanned by a user (e.g., a user of user device 110).
[0090] Referring here to Figures 4A and 4B, Figure 4A shows an unlimited embodiment of the fluid injector system 400, such as a MEDRAD® Stellant Flex CT Injection System located in the CT suite 1000. In some unlimited embodiments, the fluid injector system 400 may be the same as or similar to the injection system 104. As shown in Figure 4A, the fluid injector system 400 may include a branched system including a scan room unit and its control room unit located in the scan room 1001 and the control room 1002 of the CT suite 1000, respectively. In an unlimited embodiment, the scan room unit may include an injector head unit 401, and the control room unit may include a workstation 414, such as a Certegra® Workstation, having a display screen 416. As shown in Figure 4B, the injector head unit 401 may include a housing 402 and at least one fluid reservoir 404, such as a syringe or fluid pump container. In some non-limited embodiments, the fluid injector system 400 may include drive components that control the flow of fluid into and out of the fluid reservoirs, such as a piston associated with each fluid reservoir 404 that drives a plunger 406 in the barrel of the fluid reservoir 404, as best shown in Figure 4B. In some non-limited embodiments, each fluid reservoir 404 is fitted to be detachably joined to the housing 402 at a port 408. Each fluid reservoir 404 of the fluid injector system 400 is configured to be filled with at least one drug solution, such as a contrast agent, saline solution, or any desired drug solution. Each fluid reservoir 404 may be filled with a different drug solution F. In some non-limited embodiments, the fluid injector system 400 may be a multiple syringe injector as shown, with several fluid reservoirs 404 oriented in parallel or in a different spatial relationship, and actuated individually by each piston associated with the injector system 400.
[0091] In some non-limited embodiments, the fluid injector system 400 may be used during a medical procedure to inject at least one drug solution F into the patient's vascular system by driving a plunger 406 associated with a fluid reservoir 404 with a drive component. The drive component may move the plunger 406 toward the distal end 410 of the fluid reservoir 404 to drain the fluid F from the fluid reservoir 404 and into and through a fluid pathway set 412 during priming, purging, and / or fluid delivery procedures. In some non-limited embodiments, the fluid pathway set 412 may include flexible dosing tubes for delivering the fluid F from each fluid reservoir 404 to the patient at a vascular access site, and at least one tube or set of tubes configured to communicate with each fluid reservoir 404 in order to position each fluid reservoir 404 in fluid communication with an associated catheter.
[0092] Referring here to Figure 4C, which shows another, not-limited, embodiment of the fluid injector system 400, namely a multi-fluid delivery system such as the MEDRAD® Centargo CT Injection System, and having a display screen 418. As shown in Figure 4C, the fluid injector system 400 may be configured (e.g., adapted) to provide feedback on compliance with the instructions for use. In some, not-limited embodiments, the fluid injector system 400 includes a motorized fluid injector 101' connected to a fluid delivery set intended to be associated with an injector device for delivering fluid under pressure into the patient's body from one or more single-dose or multi-dose containers and a fluid pathway set. In some, not-limited embodiments, the motorized fluid injector 101' comprises an injector housing 102' having opposing sides 104', a distal or upper end 106', and a proximal or lower end 108'. The injector housing 102' encloses various mechanical drive components, electrical and power components necessary to drive the mechanical drive components, and control components such as electronic memory and electronic control devices (hereinafter, (one or more) electronic control devices) used to control the operation of reciprocating drive components such as drive members associated with the fluid injector system 400. Such drive members may be made reciprocating by electromechanical drive components such as motor-driven ball screw shafts, voice coil actuators, rack and pinion gear drives, and linear motors.
[0093] In some non-limited embodiments, the fluid injector system 400 may include at least one bulk fluid connector 118' for connecting to at least one bulk fluid source 120'. Alternatively, the fluid source may not be a bulk source but a single-dose vial. In some examples or embodiments, multiple bulk fluid connectors 118' may be provided. In some non-limited embodiments, three bulk fluid connectors 118' may be provided in parallel or in other arrangements. In some non-limited embodiments, at least one bulk fluid connector 118' may be a spike configured to be detachably connected to at least one bulk fluid source 120', such as a vial, bottle, or bag. At least one bulk fluid connector 118' may have a reusable or non-reusable connection point to each of the new bulk fluid sources 120'. As described herein, at least one bulk fluid connector 118' may be formed on a multi-patient disposable set or attached by piping. At least one bulk fluid source 120' may be configured to receive a drug solution, such as saline, contrast agent, or other drug solution, for delivery to the fluid injector system 400. The injector housing 102' may have at least one support member 122' for supporting the at least one bulk fluid source 120' when it is connected to the fluid injector system 400. In some non-limited embodiments, the fluid injector system 400 may include a connection port 128'.
[0094] Referring now to Figure 5, which is a diagram of URL 502 and QR code 510. As shown in Figure 5, URL 502 may include multiple fields, which may include data elements 504, 506. As further shown in Figure 5, QR code 510 is generated based on the values of the multiple fields of URL 502. In some non-limited embodiments, data element 504 may include a static data element, and data element 506 may include a dynamic data element. As shown in Figure 5, data element 504 includes a static data element which has an identifier value relating to the injection system 104 from which the error report is being generated. As further shown in Figure 5, data element 506 includes a dynamic data element which has an error code value relating to an anomaly encountered during the operation of the injection system 104.
[0095] Referring here to Figure 6, which is a diagram of the GUI 600 including a QR code 610. In some non-limited embodiments, the QR code 610 is the same as or similar to the QR code 510. As shown in Figure 6, the GUI 600 may be displayed to the user on a display screen (e.g., the display screen of the injection system 104 or the display screen of the workstation equipment 106) in order to provide the user with a QR code 610 that allows the user to access services related to obtaining product documentation and / or equipment support services. Furthermore, the QR code 610 may be encoded to include a URL that includes a link to a website where the user can select and purchase licenses for such equipment support services or obtain upgrades to existing licenses for enhanced equipment support services. Examples of such support services offered by Bayer include VirtualCARE® Remote Support, which enables secure and reliable remote monitoring of its contrast agent injection systems and software to minimize downtime, and SelectCARE®, which provides enhanced services and features. 、This includes the PartnerCARE® and DirectCARE® service contract programs, the TechCARE® NxT obsolescence program, and the services and features provided through the listed service contract programs.
[0096] Referring here to Figure 7, which is a diagram of the GUI 700 including a QR code 710. In some non-limited embodiments, the QR code 710 is the same as or similar to the QR code 510 and / or the QR code 610. As shown in Figure 7, the GUI 700 may be displayed to the user on a display screen (e.g., the display screen of the infusion system 104 or the display screen of the workstation equipment 106) in order to provide the user with a QR code 710 that allows the user to access services related to obtaining product documentation and / or licensed functions of the infusion system 104. An example of such functions includes the Patient Protocol Personalization Technology (P3T) provided by Bayer. To automatically adapt injection protocols to patients, P3T® Software for Abdomen automates the calculation of injection protocols for CT imaging of the liver, pancreas, and kidneys based on contrast agent concentration and patient characteristics (such as body weight); P3T® Software for Cardiac automates the calculation of injection protocols for CT angiography of cardiac structures such as the coronary arteries, aorta, and ventricles; and P3T® Software for Pulmonary Angiography enables the individualization of injection protocols for CT angiography of the pulmonary vascular system.
[0097] Referring here to Figure 8, which is a diagram of the GUI 800 including a QR code 810. In some non-limited embodiments, the QR code 810 is the same as or similar to the QR code 510, the QR code 610, and / or the QR code 710. As shown in Figure 8, the GUI 800 may be displayed to the user on a display screen (e.g., the display screen of the injection system 104 or the display screen of the workstation equipment 106) in order to provide the user with a QR code 810 that allows the user to access a service for renewing the license for the functions of the injection system 104.
[0098] Referring here to Figure 9, Figure 9 is a diagram of the GUI 900 including a QR code 910. In some non-limited embodiments, the QR code 910 is the same as or similar to the QR code 510, QR code 610, QR code 710, and / or QR code 810. As shown in Figure 9, the GUI 900 may be displayed to the user on a display screen (e.g., the display screen of the injection system 104 or the display screen of the workstation equipment 106) in order to provide the user with a QR code 910 that allows the user to access services related to equipment support services after an anomaly encountered during the operation of the injection system 104.
[0099] This disclosure provides details for illustrative purposes based on what is currently considered the most practical and preferred embodiments or aspects; however, such details are for illustrative purposes only, and it should be understood that this disclosure is not limited to the embodiments or aspects disclosed, but rather is intended to include modifications and equivalent configurations within the spirit and scope of the appended claims. For example, it should be understood that, where possible, this disclosure assumes that one or more features of any embodiment or aspect can be combined with one or more features of any other embodiment or aspect. [Explanation of Symbols]
[0100] 100 Environment 101' Electric fluid injector 102 Quick Response (QR) Code System 102' Injector Housing 104 Injection System 104' Opposing side 106 Workstation Equipment 106' Distal or upper end 108 Remote Support System 108' Proximal or lower end 110 User equipment 112 Communication Networks 118' Bulk Fluid Connector 120' bulk fluid supply source 122' Support member 128' Connection Port 200 equipment Bus 202 204 Processors 206 memory 208 Memory Components 210 Input Components 212 Output Components 214 Communication Interface Process to provide QR codes for 300 injection systems 400 Fluid Injector System 401 Injector Head Unit 402 Housing 404 Fluid Reservoir 406 Plunger 408 ports 410 Distal end 412 Fluid Path Set 414 Workstations 416 Display screen 418 Display screen 502 Uniform Resource Locator (URL) 504 Data Element 506 Data Element 510 QR code 600 Graphical User Interfaces (GUI) 610 QR code 700 GUI 710 QR code 800 GUI 810 QR code 900 GUI 910 QR code 1000 Computed Tomography (CT) Suite 1001 Scanning Room 1002 Control Room
Claims
1. An injection system for providing quick response (QR) codes, Includes at least one processor, The at least one processor is programmed or configured to receive data relating to the injection system, and the data relating to the injection system is Data relating to the identifier of the injection system, This includes data relating to one or more operations of the injection system, The at least one processor is programmed or configured to automatically generate network resources based on the data relating to the injection system, and the network resources include a uniform resource locator (URL), and when generating the network resources, the at least one processor, A log scrubber is used to remove sensitive data from the data relating to the injection system. The program or configuration encodes the data relating to one or more operations of the injection system and the data relating to the identifier of the injection system into the URL, The at least one processor is programmed or configured to generate a QR code based on the URL, the QR code comprising static data elements and dynamic data elements, the static data elements comprising the data relating to the identifier of the injection system, the dynamic data elements comprising the data relating to one or more operations of the injection system, and the QR code is configured to cause the user device to transmit the data relating to one or more operations of the injection system and the data relating to the identifier of the injection system to a remote support system when the user device scans the QR code. An injection system in which at least one processor is programmed or configured to display the QR code on a graphical user interface (GUI) displayed on the display screen of the injection system.
2. The data relating to one or more operations of the injection system is The number of fluid injection operations performed by the injection system, The number of fluid injection operations performed by the injection system, Operating parameters of the fluid injection operation performed by the injection system, Data on patient demographics for patients who underwent fluid infusion procedures using an infusion system. Data relating to the configuration of the injection system, and Data relating to anomalies encountered during the operation of one or more of the injection systems. The injection system according to claim 1, comprising at least one of the following.
3. The data relating to an anomaly encountered during the operation of one or more injection systems is An identifier for an error related to the operation of the injection system, and Operating parameters of the injection system relating to the aforementioned abnormality The injection system according to claim 2, comprising at least one of the following.
4. The operating parameters of the injection system relating to the aforementioned abnormality are, Temperature measurements of the components of the injection system, and Measurement values of the electrical characteristics of the electrical components of the injection system. The injection system according to claim 3, comprising at least one of the following.
5. The data relating to the injection system is Data relating to the software or hardware of the injection system, and Data relating to the network connection of the injection system The injection system according to claim 1, further comprising at least one of the following.
6. The data relating to the software or hardware of the injection system is Software configuration of the injection system, The hardware configuration of the injection system, and Software version of the injection system The injection system according to claim 5, comprising at least one of the following.
7. The software version of the injection system is The software version of the operating system of the injection system, The revision number of the software for the injection system, and Identifier of one or more software patches applied to the injection system The injection system according to claim 6, comprising at least one of the following.
8. The aforementioned at least one processor, Further programmed or configured to generate one or more cryptographic keys for accessing the URL associated with the QR code, When generating the network resources, at least one processor The injection system according to claim 1, which is programmed or configured to encrypt the aforementioned URL.
9. The aforementioned at least one processor, The injection system according to claim 1, further programmed or configured to record the data relating to one or more operations of the injection system.
10. The data relating to the injection system is The software version of the injection system, The revision number of the software for the aforementioned injection system, Identifiers of one or more software patches applied to the injection system, The media access control (MAC) address of the network interface controller (NIC) of the injection system, An identifier for an error related to the operation of the injection system, and Any combination of these It includes at least one of the following: When encoding the data relating to the injection system into the network resource The at least one processor, The software version of the injection system, The revision number of the software of the injection system, The identifiers of one or more software patches applied to the injection system, The MAC address of the NIC of the injection system, and The identifier of the error relating to the operation of the injection system The injection system according to claim 1, which is programmed or configured to encode at least one of the following into the network resource.
11. A computer program for providing a quick response (QR) code relating to an injection system, wherein the computer program includes one or more instructions, and when the one or more instructions are executed by at least one processor, the at least one processor is provided with The system receives data relating to the injection system, and the data relating to the injection system is Data relating to the identifier of the injection system, This includes data relating to one or more operations of the injection system, The one or more instructions described above are directed to the at least one processor, The injection system automatically generates network resources based on the data relating to the injection system, and the network resources include a uniform resource locator (URL), and when generating the network resources, at least one processor, A log scrubber is used to remove sensitive data from the data relating to the injection system. The program or configuration encodes the data relating to one or more operations of the injection system and the data relating to the identifier of the injection system into the URL, The one or more instructions described above are directed to the at least one processor, A QR code is generated based on the aforementioned URL, the QR code includes a static data element and a dynamic data element, the static data element includes the data relating to the identifier of the injection system, the dynamic data element includes the data relating to one or more operations of the injection system, and the QR code is configured such that when a user device scans the QR code, the user device transmits the data relating to one or more operations of the injection system and the data relating to the identifier of the injection system to a remote support system. The one or more instructions described above are directed to the at least one processor, A computer program that displays the QR code on the graphical user interface (GUI) shown on the display screen of the injection system.
12. An injection system for providing quick response (QR) codes, Includes at least one processor, The at least one processor is programmed or configured to receive data relating to the injection system, and the data relating to the injection system is Data relating to the identifier of the injection system, Data relating to the software or hardware of the injection system, and Data relating to the network connection of the injection system It includes at least one of the following: The at least one processor is programmed or configured to automatically generate network resources based on the data relating to the injection system, and the network resources include a uniform resource locator (URL), and when generating the network resources, the at least one processor, A log scrubber is used to remove sensitive data from the data relating to the injection system. The program or configuration is configured to encode the data relating to the injection system into the URL, The at least one processor is programmed or configured to generate a QR code based on the URL, wherein the QR code includes static data elements and dynamic data elements, the static data elements include data elements whose values do not change after the injection system is set up, and the dynamic data elements include data elements whose values change after the injection system is set up, and the QR code is configured to allow the user device to access at least one of the following when the user device scans the QR code: (i) a service for obtaining product documentation for the injection system, (ii) a service for device support after an anomaly encountered during the operation of the injection system, and (iii) a licensed function relating to the injection system. An injection system in which at least one processor is programmed or configured to display the QR code on a graphical user interface (GUI) displayed on the display screen of the injection system.
13. The injection system according to claim 12, wherein the QR code is further configured to cause the user device to access a link to a website that enables the selection and purchase of licenses for the services relating to device support, and to obtain an upgrade of an existing license to an extended service relating to device support.
14. The injection system according to claim 12, wherein the QR code is further configured to allow the user device to access a service relating to the license renewal of the functions of the injection system.
15. The static data element whose value does not change after the injection system is set includes the data relating to the identifier of the injection system, and the data relating to the identifier of the injection system is The model number of the injection system, and Serial number of the injection system The injection system according to claim 12, comprising at least one of the following.
16. The injection system according to claim 12, wherein the dynamic data element whose value changes after the injection system is set up includes data relating to one or more operations of the injection system.
17. The data relating to one or more operations of the injection system is The number of fluid injection operations performed by the injection system, The number of fluid injection operations performed by the injection system, Operating parameters of the fluid injection operation performed by the injection system, Data on patient demographics for patients who underwent fluid infusion procedures using an infusion system. Data relating to the configuration of the injection system, and Data relating to anomalies encountered during the operation of one or more of the injection systems. The injection system according to claim 16, comprising at least one of the following.
18. The data relating to an anomaly encountered during the operation of one or more injection systems is An identifier for an error related to the operation of the injection system, and Operating parameters of the injection system relating to the aforementioned abnormality The injection system according to claim 17, comprising at least one of the following:
19. The operating parameters of the injection system relating to the aforementioned abnormality are, Temperature measurements of the components of the injection system, and Measurement values of the electrical characteristics of the electrical components of the injection system. The injection system according to claim 18, comprising at least one of the following.
20. The data relating to the injection system is Data relating to the software or hardware of the injection system, and Data relating to the network connection of the injection system The injection system according to claim 12, further comprising at least one of the following.
21. The data relating to the software or hardware of the injection system is Software configuration of the injection system, The hardware configuration of the injection system, and Software version of the injection system The injection system according to claim 20, comprising at least one of the following.
22. The software version of the injection system is The software version of the operating system of the injection system, The revision number of the software for the injection system, and Identifier of one or more software patches applied to the injection system The injection system according to claim 21, comprising at least one of the following.
23. The aforementioned at least one processor, Further programmed or configured to generate one or more cryptographic keys for accessing the URL associated with the QR code, When generating the network resources, at least one processor The injection system according to claim 12, which is programmed or configured to encrypt the aforementioned URL.
24. The aforementioned at least one processor, The injection system according to claim 12, further programmed or configured to record the data relating to one or more operations of the injection system.
25. A computer program for providing a quick response (QR) code relating to an injection system, wherein the computer program includes one or more instructions, and when the one or more instructions are executed by at least one processor, the at least one processor is provided with The system receives data relating to the injection system, and the data relating to the injection system is Data relating to the identifier of the injection system, Data relating to the software or hardware of the injection system, and Data relating to the network connection of the injection system It includes at least one of the following: The one or more instructions described above are directed to the at least one processor, The injection system automatically generates network resources based on the data relating to the injection system, and the network resources include a uniform resource locator (URL), and when generating the network resources, at least one processor, A log scrubber is used to remove sensitive data from the data relating to the injection system. The program or configuration is configured to encode the data relating to the injection system into the URL, The one or more instructions described above are directed to the at least one processor, A QR code is generated based on the aforementioned URL, and the QR code includes static data elements and dynamic data elements, wherein the static data elements include data elements whose values do not change after the injection system is configured, and the dynamic data elements include data elements whose values change after the injection system is configured, and the QR code is configured to allow the user device to access at least one of the following when the user device scans the QR code: (i) a service for obtaining product documentation for the injection system, (ii) a service for device support after an anomaly encountered during the operation of the injection system, and (iii) a licensed function related to the injection system. The one or more instructions described above are directed to the at least one processor, A computer program that displays the QR code on the graphical user interface (GUI) shown on the display screen of the injection system.