Single blood sampling equipment fleet management system and method

Abstract

The fleet management system includes a single blood sampling device and a fleet management device that is remote from the single blood sampling device and communicates with the single blood sampling device. Each single blood sampling device has a controller, firmware, and firmware settings. The fleet management device includes an interface that allows a user to interact with the fleet management device, a server, and a processor. The server receives information about the firmware / firmware settings and firmware files of each single blood sampling device from the user and / or a remote repository. The processor processes the information to determine which single blood sampling device needs to update the firmware / firmware settings. The server then distributes the firmware file to each single blood sampling device that needs to be updated. The system can also develop a fleet model for one or more donation centers, which includes a recommended number of devices for (one or more) locations and / or whether a device should be moved from one location to another.

Description

[0001] priority

[0002] This PCT patent application claims priority to U.S. Provisional Application No. 62 / 722,960, filed on August 26, 2018, entitled “Apheresis Devices Fleet Management,” assigned attorney docket number 130670-09501 (formerly 1611 / C95), and naming Melvin Tan as the inventor, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present invention relates to managing apheresis devices, and more particularly to supervising and managing a plurality of apheresis devices and methods thereof from a remote location. Background Art

[0004] Apheresis is a process in which individual blood components can be separated and collected from whole blood drawn from a subject, and an apheresis device is a medical device designed and intended to perform the apheresis process. Donation centers typically have more than one apheresis device, and each device is typically configured to operate in exactly the same manner to comply with the donation center's standard operating procedures and to meet regulatory requirements. The configuration of an apheresis device is determined by embedded software in the device (also known as device firmware) and a different set of firmware settings to dictate how each feature of the device operates and performs.

[0005] To change or update the firmware version of a single blood collection device, a user must currently access the device locally through the device's built-in controller, input method, and display output. The user then downloads the firmware file to the individual device and performs the firmware update from within the built-in device controller (i.e., at each device). To perform the same process on multiple single blood collection devices, the above process must be repeated locally for each device.

[0006] Similarly, to change or update the firmware setting values ​​of a single blood collection device, the user must also access the device locally through the device's built-in controller, input method, and display output. This in turn enables the user to access the firmware settings and allows the user to change (one or more) firmware setting values ​​by manual manipulation or by reading, entering, or scanning pre-coded firmware settings. To perform the same process on multiple single blood collection devices, the user must again repeat the process locally for each device.

[0007] In addition to having to update each device individually, the user must also access each device locally to simply check that the devices are configured to operate in exactly the same manner. Thus, after the user has accessed the single blood collection device through the device's built-in controls, input methods, and display outputs, the user can check the firmware version and firmware setting values ​​for the individual devices. This can be performed individually on each device by physically manipulating the controls of the single blood collection device and viewing the value of each firmware setting. Depending on the number of devices within a given donation center, this can be a very time-consuming task. Summary of the invention

[0008] In various embodiments of the present invention, a company employee can use a computer system from a remote location to supervise and manage at least one single blood sampling device in the company's fleet. From the remote location, the user can manage the single blood sampling device firmware files, firmware settings, and perform checks on the firmware settings without any physical manipulation of the controls on the built-in single blood sampling device controller itself. The system can be connected to multiple single blood sampling devices from a central location or a remote location. The connection can be persistent, or it can be intermittent.

[0009] The system can receive a firmware file from a user or from an external repository, and the file can be distributed to at least one single blood sampling device for installation on the device. The system can alert the user when the firmware file has been successfully or unsuccessfully installed. Alternatively, the user can also use the system to check the firmware version of the single blood sampling device to confirm whether the firmware file has been successfully or unsuccessfully installed.

[0010] The system can receive a firmware settings file from a user, from an external repository, or from a single blood sampling device. The firmware settings file can be used to configure multiple single blood sampling devices in a company's fleet (e.g., within a donation center or multiple donation centers). The firmware settings file can be distributed to (one or more) single blood sampling devices so that the device applies the changes represented in the firmware settings file. The system can alert the user when the firmware settings changes have been successfully or unsuccessfully applied. Alternatively, the user can also use the system to check the firmware settings of the single blood sampling device to confirm whether the changes to the firmware settings file were successfully applied or unsuccessfully applied.

[0011] In some embodiments, the system can use the connection to the single blood collection devices in the fleet to collect information about firmware versions or firmware setting values ​​from the individual devices in the fleet. The system can then aggregate, combine, and analyze the information to determine if there are any differences in firmware versions or firmware setting values ​​between the single blood collection devices. When the system detects a firmware version or firmware setting difference, the system can also create a notification, such as an email to the user.

[0012] In yet other embodiments, the system may use heuristics to create a fleet model based on the locations of single blood sampling devices in the fleet and productivity information from those locations. Fleet modeling may determine the optimal number of devices for a profile at a location, and may provide instructions to the user to add or remove devices from that location. The system may use information based on productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and / or other performance or production data thereof to determine the optimal fleet model for each location. The system may also use the location data of the single blood sampling devices to determine the plasma center locations that will need to change the placement of the devices to meet the requirements of the new fleet model, and may provide guidance to the user in the form of a digital assistant with instructions to adjust the placement of the single blood sampling devices at specific plasma center locations in the company.

[0013] Additionally or alternatively, the system can use the connection to the single blood sampling devices in the fleet to monitor for firmware version differences or firmware settings differences. Unexpected differences (i.e., changes) between single blood sampling devices can be tracked, recorded, and reported to the company user or users of the company. Alternatively, the system can self-correct any changes between single blood sampling devices by sending a firmware file of the firmware settings file to update on non-compliant single blood sampling devices.

[0014] According to yet another embodiment, a fleet management system includes a first plurality of single blood sampling devices and a fleet management device. Each single blood sampling device may have a controller, firmware, and firmware settings. The fleet management device may be remote from each single blood sampling device and communicate with each single blood sampling device. The fleet management device may include an interface, a server, and a processor. The interface may allow a user to interact with the fleet management device, and the server may receive information about firmware and firmware settings from each single blood sampling device, and may receive firmware files from a user and / or a remote repository. The processor may process the information received from the single blood sampling device to determine which single blood sampling device needs to update the firmware and / or firmware settings. The server may then distribute the firmware file to each single blood sampling device that needs to be updated.

[0015] The fleet management system may also include a second plurality of single blood sampling devices remote from and in communication with the fleet management device. The server may also receive information about firmware and firmware settings from each of the second plurality of single blood sampling devices, and the processor may process the information to determine which of the single blood sampling devices requires an update to the firmware and / or firmware settings. The server may then distribute the firmware file to each device that requires an update. The first plurality of single blood sampling devices may be located at a first donation center, and the second plurality of single blood sampling devices may be located at a second donation center.

[0016] In other embodiments, the fleet management device may allow a user to remotely manage the firmware files and / or firmware settings of each single blood collection device. For example, the fleet management device may remind the user whether the firmware files and / or firmware settings files have been successfully or unsuccessfully installed on the single blood collection device. The fleet management device may also collect additional information from each single blood collection device, such as data related to the single blood collection process performed, productivity information, utilization information, the number of single blood collection devices in the donation center, performance data, and / or inventory data. The processor may analyze the information (or other information) about the firmware and firmware settings of each single blood collection device to determine whether there are differences in the firmware versions or firmware setting values ​​of each single blood collection device. In such an embodiment, the fleet management device may notify the user of the differences.

[0017] In another embodiment, the fleet management device may generate a fleet model for one or more donation centers. For example, the fleet model may be based at least in part on information about productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and other performance or production data thereof. The fleet model may include recommended single blood sampling device changes for one or more donation centers, and the server may notify the user of the fleet model and the recommended single blood sampling device changes. The fleet management device may also include a data storage device that stores information received from the single blood sampling device.

[0018] According to yet another embodiment, the fleet management device may include an interface that allows a user to interact with the fleet management device and a server that communicates with a first plurality of single blood sampling devices. The single blood sampling devices may be located remotely from the fleet management device, and the server may receive information about firmware and firmware settings from each single blood sampling device and receive firmware files from the user and / or a remote repository. The processor may process the information received from each single blood sampling device to determine which single blood sampling device needs to update firmware and / or firmware settings. The server may then distribute the firmware file to each single blood sampling device that needs to be updated.

[0019] The server may also communicate with a second plurality of single blood sampling devices located remotely from the fleet management device. In such an embodiment, the server may also receive information about firmware and firmware settings from each of the second plurality of single blood sampling devices, and the processor may process the received information to determine which single blood sampling device needs to be updated. The server may then distribute the firmware file to each of the second plurality of single blood sampling devices that need to be updated.

[0020] The fleet management device can allow a user to remotely manage and / or monitor the firmware files and / or firmware settings of each of the first plurality of single blood sampling devices, and the server can alert the user whether the firmware files and / or firmware settings files are successfully or unsuccessfully installed. Additionally or alternatively, the server can receive additional information (e.g., single blood sampling processes performed, productivity information, utilization information, the number of single blood sampling devices in a donation center, performance data, and inventory data) from each of the first plurality of single blood sampling devices.

[0021] In some embodiments, the processor can determine whether there are differences in the firmware versions or firmware setting values ​​of the single blood sampling devices by analyzing information about the firmware and firmware settings of each single blood sampling device. The server can notify the user of any differences. Additionally or alternatively, the server and / or processor can generate a fleet model for one or more donation centers. The fleet model can be based on information about productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, average, rate, speed data, and other performance or production data. The fleet model may include recommended single blood sampling device changes for one or more donation centers, and the server may notify the user of the fleet model and recommended single blood sampling device changes. Equipment changes may include the number of devices that should be within a given donation center, the location of the equipment, and whether one or more devices should be moved from one center to another.

[0022] According to yet another embodiment, a method for managing a fleet of single blood sampling devices includes remotely connecting to a first plurality of single blood sampling devices and receiving in a server of a fleet management device (1) information about firmware and firmware settings for each of the first plurality of single blood sampling devices (e.g., from the single blood sampling device), and (2) a firmware file (e.g., from a user and / or a remote repository). The method may then process the information received from the single blood sampling device in a processor of the fleet management device to determine which single blood sampling device requires an update to the firmware and / or firmware settings. The method may then use the server of the fleet management device to distribute the firmware file to each of the first plurality of single blood sampling devices that require an update.

[0023] In some embodiments, the method may further include connecting to a second plurality of single blood sampling devices remote from the fleet management device, and receiving information related to firmware and firmware settings of each of the second plurality of single blood sampling devices in a server of the fleet management device. The method may then (1) process the information received from each of the second plurality of single blood sampling devices using a processor of the fleet management device to determine which of the second plurality of single blood sampling devices requires an update of firmware and / or firmware settings, and (2) distribute the firmware file to each of the second plurality of single blood sampling devices that requires an update using the server of the fleet management device.

[0024] Additionally, the method may use a fleet management device to manage and / or monitor the firmware files and / or firmware settings of each of the first plurality of single blood collection devices, and / or generate a reminder to the user whether the firmware files and / or firmware settings files have been successfully or unsuccessfully installed on the single blood collection device. The method may also collect and store (e.g., in a data storage device) additional information from each of the first plurality of single blood collection devices. For example, the method may collect information about blood collection processes performed, productivity information, utilization information, the number of single blood collection devices in a donation center, performance data, and inventory data. The method may also use a processor to analyze information about the firmware and firmware settings of each single blood collection device to determine whether there are differences in the firmware version or firmware setting values ​​of each single blood collection device. If there are differences, the method may notify the user of the differences.

[0025] In further embodiments, the method may generate a fleet model for one or more donation centers. The fleet model may be based at least in part on information related to productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and other performance or production data thereof. The fleet model may include recommended single blood sampling device changes for one or more donation centers, and the method may notify a user of the fleet model and the recommended single blood sampling device changes. The method may also store information received from the single blood sampling devices in a data storage device in the fleet management device. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The foregoing features of the embodiments will be more readily understood by reference to the following detailed description with reference to the accompanying drawings, in which:

[0027] Figure 1 A perspective view of a blood processing system according to some embodiments of the present invention is schematically shown.

[0028] Figure 2 Schematically shows some embodiments of the present invention Figure 1 Top view of a blood processing system.

[0029] Figure 3 Schematically illustrates an apparatus installed in a Figure 1 A disposable set within a blood processing system.

[0030] Figure 4 A single blood sampling device and its related firmware and firmware settings according to some embodiments of the present invention are schematically shown.

[0031] Figure 5Fleet management providing oversight of multiple single blood collection devices at multiple plasma center locations is schematically illustrated according to some embodiments of the present invention.

[0032] Figure 6 Fleet management modeling is schematically illustrated to determine the optimal number and placement of single blood collection devices at a plasma center location according to some embodiments of the present invention. DETAILED DESCRIPTION

[0033] In an illustrative embodiment, a fleet management system has a fleet management device that is remote from and in communication with a plurality of single blood sampling devices. The fleet management device can receive information about firmware and firmware settings and a firmware file from each of a first plurality of single blood sampling devices. The device can then process the information to determine which single blood sampling device needs to be updated, and then distribute the firmware file to each single blood sampling device that needs to be updated, for example, to ensure that each single blood sampling device has the same firmware and firmware settings.

[0034] like Figure 1 and Figure 2 As shown in , the blood processing system 100 includes a cabinet 110 that houses the major components of the system 100 (e.g., non-disposable components). Within the cabinet 110, the system 100 may include a first / blood pump 232 that draws whole blood from a subject and a second / anticoagulant pump 234 that pumps anticoagulant through the system 100 and into the drawn whole blood. In addition, the system 100 may include a plurality of valves that may be opened and / or closed to control the flow of fluid through the system 100. For example, the system 100 may include valves that may be opened and closed to selectively prevent and allow fluid to flow through the donor lines 218 (e.g., the inlet line; Figure 3 ) of the donor valve 120, and selectively preventing and allowing fluid flow through the outlet / plasma line 222 ( Figure 3 ) of the plasma valve 130. Some embodiments may also include a saline valve 135 that selectively prevents and allows saline to flow through the saline line 223.

[0035] To facilitate connection and installation of the disposable device and to support the corresponding fluid container, the system 100 may include an anticoagulant rod 150 and a saline rod 160, an anticoagulant solution container 210 ( Figure 3 ) can be suspended from the anticoagulant rod 150, and the saline solution container 217 ( Figure 3) can be suspended from saline rod 160 (e.g., if the procedure being performed requires the use of saline). In addition, in some applications, it may be necessary and / or desirable to filter whole blood drawn from a subject for processing. To this end, system 100 can include a blood filter holder 170 in which a blood filter (located on a disposable device) can be placed.

[0036] As discussed in more detail below, the single blood collection system 100 according to an embodiment of the present invention uses a blood pump 232 to enter the device 206 ( Figure 3 ) whole blood is drawn from the subject. When the system 100 draws whole blood from the subject, the whole blood enters a blood component separation device 214, such as a Latham-type centrifuge (other types of separation chambers and devices may be used, such as, but not limited to, integral blow-molded centrifuge drums as described in U.S. Pat. Nos. 4,983,158 and 4,943,273, which are incorporated herein by reference). The blood component separation device 214 separates the whole blood into its constituent components (e.g., red blood cells, white blood cells, plasma, and platelets). Therefore, in order to facilitate the operation of the separation device 214, the system 100 may also include a well 180 in which the separation device 214 may be placed and the separation device 214 rotates therein (e.g., to generate the centrifugal force required to separate the whole blood).

[0037] To allow a user / technician to monitor system operation and control / set various parameters of the process, the system 100 may include a user interface 190 (e.g., a touch screen device) that displays the operating parameters, any reminder messages, and buttons that the user / technician may press to control the various parameters. Additional components of the blood processing system 100 are discussed in more detail below (e.g., with respect to system operation).

[0038] Figure 3 1 is a schematic block diagram of a blood processing system 100 according to the present invention and a disposable collection device 200 (having an inlet disposable device 200A and an outlet disposable device 200B) that can be loaded onto / into the blood processing system 100. The collection device 200 includes a venous access device 206 (e.g., a phlebotomy needle) for drawing blood from a donor's arm 208, an anticoagulant container 210, a centrifuge bowl 214 (e.g., a blood component separation device), a saline container 217, and a final plasma collection bag 216. A blood / inlet line 218 couples the venous access device 206 to an inlet port 220 of the bowl 214, a plasma / outlet line 222 couples an outlet port 224 of the bowl 214 to the plasma collection bag 216, and a saline line 223 connects the outlet port 224 of the bowl 214 to the saline container 217. An anticoagulant line 225 connects the anticoagulant container 210 to the inlet line 218. In addition to the above and as described above, Figure 3In addition to the components shown in FIG. 1 , the blood processing system 100 also includes a controller 226, a motor 228, and a centrifugal cartridge 230. The controller 226 is operably coupled to two pumps 232 and 234, and to the motor 228, which in turn drives the cartridge 230. The controller 226 can be operably coupled to the user interface 190 and communicate with the user interface 190.

[0039] In operation, the disposable collection set 200 (e.g., the inlet disposable set 200A and the outlet disposable set 200B) can be loaded onto / into the blood processing system 100 prior to blood processing. In particular, the blood / inlet line 218 is routed through the blood / first pump 232, and the anticoagulant line 225 from the anticoagulant container 210 is routed through the anticoagulant / second pump 234. The centrifuge bowl 214 can then be securely loaded into the cartridge 230. Once the bowl 214 is secured in place, the technician can install the outlet disposable set 200B. For example, the technician can connect the bowl connector 300 to the outlet 224 of the bowl 214, install the plasma container 216 to the weight sensor 195, pass the saline line 223 through the valve 135, and pass the plasma / outlet line 222 through the valve 130 and the line sensor 185. Once the disposable set 200 is installed and the anticoagulant container and saline container 210 / 217 are connected, the system 100 is ready to start blood processing.

[0040] The blood processing system 100 (eg, a single blood collection device) and / or the various hardware components of the blood processing system 100 may include various components that control the blood processing system 100 (see Figure 4 ) and the operation of the system 100. At various times, the firmware 420 and / or firmware settings 430A / B / C may become outdated or otherwise need to be updated. To this end, the controller 226 and the input devices and display 190 of the device 100 may allow a user to access the device 100, for example, to view and / or update the firmware 420 and / or firmware settings 430A / B / C.

[0041] Figure 5A fleet management system is schematically shown that can remotely update the firmware 420 and / or firmware settings 430A / B / C of one or more blood processing systems / single blood collection devices 100. For example, the fleet management system 510 can be a remote computer system that oversees and manages some or all of the single blood collection devices 520A-F in a company's fleet. The management system 510 can include multiple components that help the system 510 monitor, communicate with, and update the firmware of various single blood collection devices. For example, the management system / device 510 can include a processor 530 that monitors each of the (one or more) single blood collection devices 520A-F and the status of the firmware (e.g., settings, version, etc.), and a memory 540 (e.g., a data storage device) for storing information related to the (one or more) single blood collection devices 520A-F (e.g., the firmware version of each device, the firmware settings, the last update date, any problems with the firmware and / or firmware settings, etc.). Additionally, the system 510 may include a server 550 that communicates with the single blood collection devices 520A-F (and possibly other remote devices / systems) and a controller interface / display 560 that provides information to a user / operator.

[0042] like Figure 5 As shown in , the single blood sampling devices 520A-F can be located in a single donation center 530A or multiple donation centers 530A / B. The fleet management system 510 allows a user to remotely manage the single blood sampling device firmware files 420, firmware settings 430A-C, and perform various checks on the firmware settings for each single blood sampling device 520A-F. For example and as discussed in more detail below, the server 550 can communicate with each of the single blood sampling devices 520A-F to monitor and download data about the firmware and firmware settings of each of the devices 520A-F. The processor 530 (or server 550) can then process the received information / data to determine whether each device 520A-F needs to update the firmware 420 and / or firmware settings 430A-C.

[0043] It is important to note that because the fleet management system 510 allows the user to remotely manage each of the single blood sampling devices 520A-F, the user does not need to be physically present at each device 520A-F to manipulate the built-in controls on each single blood sampling device (e.g., the user does not need to physically interact with the controller 226 of each device). The connection / communication between the fleet management system 510 and each of the single blood sampling devices 520A-F can be persistent / continuous, or the fleet management system 510 can connect to the single blood sampling devices 520A-F only when needed (e.g., when the user wishes to monitor or manage a particular device). For example, the fleet management system 510 can continuously receive information / data related to the firmware of each single blood sampling device 520A-F (as well as other information about the devices 520A-F), or the fleet management system 510 can only periodically receive firmware information / data (e.g., at predetermined intervals, when prompted by the user, only when there are updates to be distributed, only when prompted by the server 550 or system 510, etc.).

[0044] As described above, the fleet management system 510 can manage multiple single blood collection devices 520A-F as needed. To this end, the fleet management system 510 (e.g., server 550) can receive firmware files from a user or from an external repository (or other remote device / database). If the system 510 has not yet received firmware information / data from each of the devices 520A-F (e.g., via a continuous connection or a recent periodic connection / update), the server 550 can then connect to each of the devices 520A-F and download firmware information / data (including current firmware versions, firmware settings, and any firmware issues) for each of the devices 520A-F. Upon receiving this information, the processor 530 can then determine which device 520A-F needs to have the firmware 420 and / or firmware settings 430A-C updated, and the system 510 (e.g., server 550) can distribute the (one or more) firmware files to any of the devices 520A-F that need the (one or more) new firmware files to be installed.

[0045] In addition to sending (one or more) updated / new firmware files to each of the devices 520A-F that need it, the system 510 can also monitor the progress of the installation and / or firmware update and provide reminders to the user when the firmware file has been successfully installed and / or if the installation is unsuccessful. If the installation is unsuccessful, the system 100 can provide the user with the option to retry the download and installation. Additionally or alternatively, the fleet management system 510 can allow the user to manually check the firmware version of each of the single blood collection devices 520A-F to confirm whether the firmware file has been successfully installed or unsuccessfully installed. For example, the system 510 can display (on the interface / display 560) each of the devices 520A-F connected / maintained by the system 510, and may display the current firmware information of each device 520A-F. The user can then select a device of interest in the devices 520A-F to obtain additional information about the device, including but not limited to the location of the device, the service and usage history of the device, firmware 420 and firmware settings 430A-C information, the date of the last update, any recent error messages, and / or the progress of any ongoing installation. It should be noted that the system 510 may display the equipment 520A-F in any number of ways, including, but not limited to, a list of equipment or a floor plan of each plasma center 530A / B with icons depicting each equipment 520A-F in the appropriate location.

[0046] In some embodiments, a user may not wish to update the firmware 420 and / or firmware settings 430A-C while the single blood collection device 520A-F is in use. Therefore, any updates may be performed after the regular donation time of the plasma center 530A / B. Alternatively, the system 510 (e.g., the server 550) may receive information about the operational status of each device 520A-F (e.g., whether it is in use) and / or whether the device 520A-F is scheduled for a single blood collection procedure. The management system 510 may then decide whether to update the firmware 420 and / or firmware settings 430A-C based on the operational information. For example, if the single blood collection device 520A-F is in the middle of a procedure or is about to be used in a procedure, the system 510 may wait to distribute the firmware update to the device 520A-F. In a similar manner, when a given device 520A-F is scheduled for an update, the system 510 may notify the plasma center 530A / B to ensure that the device 520A-F is not assigned to the procedure until the update is complete.

[0047] At various times, the plasma center 530A / 530B may receive new single blood sampling devices 520A-F and / or replace existing devices 520A-F, and these new devices may require initial configuration so that their firmware and firmware settings match the other devices within the center 530A / B. To this end, the system 510 can configure these new devices (and / or configure / reconfigure existing devices 520A-F). In a manner similar to that described above, the system 510 can receive a firmware settings file from a user, from an external repository, or from at least one single blood sampling device 520A-F, and the fleet management system 510 can use the firmware settings file to configure some or all of the single blood sampling devices 520A-F in the company's fleet. For example, the system 510 can display the devices 520A-F that need to be configured on the interface / display 560, and the user can select which of the devices 520A-F to configure (or the system 510 can automatically configure the devices without input from the user). The system 510 (e.g., server 550) can then distribute the firmware settings file to the appropriate (one or more) single blood collection devices 520A-F so that each device that receives the firmware settings file can apply the changes represented in the firmware settings file. Again, the system 510 can alert the user when the firmware settings changes have been successfully applied and / or if the update was unsuccessful (e.g., an error occurred). Additionally or alternatively, as described above, the user can also use the system 510 to manually check the firmware settings of the (one or more) single blood collection devices 520A-F to confirm whether the firmware settings file changes were successfully applied or unsuccessfully applied.

[0048] In some cases, it is beneficial to ensure that each single blood collection device 520A-F within a fleet and / or within a plasma center 530A / B all operates with the same firmware version 420 and firmware settings 430A-C. Therefore, in addition to updating and sending firmware updates to each of the single blood collection devices 520A-F, the fleet management system 510 can also collect information about the firmware version 420 or firmware setting values ​​430A-C from each of the devices 520A-F in the fleet. The system 510 (e.g., the processor 530) can then aggregate, combine and / or analyze the data to determine whether there are any differences in firmware versions 420 or firmware setting values ​​430A-C between the single blood collection devices 520A-F within the fleet and / or within a particular plasma center 530A / B.

[0049] If there is a difference between the firmware versions 420 and / or firmware settings 430A-C, the system 510 can notify the user. For example, the system 210 can create an email notification and send it to the user or display a notification on the interface 560 when it detects a firmware version or firmware setting difference. The system 510 can then give the user an opportunity to correct the difference by downloading / distributing the appropriate firmware version 420 and / or settings 430A-C to the appropriate single blood collection devices 520A-F (or downloading / distributing the new firmware version and / or new firmware settings to all single blood collection devices 520A-F). Alternatively, the system 510 can automatically distribute the firmware file or firmware setting file to the single blood collection devices to correct the difference.

[0050] When planning the types and numbers of apheresis devices 520A-F, each plasma center 530A / B must consider a number of factors (e.g., geographic location, expected donor participation, cost of apheresis devices 520A-F, cost of maintaining apheresis devices 520A-F, size of plasma center 530A / B, types of donations and apheresis procedures to be performed at the donation center, desired collection volumes in a given time period, etc.) to ensure that they have enough apheresis devices 520A-F to serve the expected number of donors and meet target collection volumes without having too many unused apheresis devices 520A-F at any given time. Therefore, in addition to updating the firmware 420 and firmware settings 430A-C on the devices 520A-F, in some embodiments and as shown in FIG. Figure 6 As shown in , the fleet management system 510 can help the plasma center 530A / B determine the optimal number of single blood sampling devices 520A-F to meet its expected demand and achieve its target volume without an excess of single blood sampling devices 520A-F. For example, in such an embodiment, the system 510 can also download / receive from the plasma center 530A / B (and each of the single blood sampling devices 520A-F) information about the single blood sampling processes performed at the plasma center 530A / B, productivity information from the plasma center 530A / B, and possibly information about donor flow and plasma center 530A / B goals. The system 510 (e.g., the processor 530) can then process and analyze the information data, for example using heuristics based on the locations of the single blood sampling devices in the fleet and the productivity information from those locations, to create a fleet model for the plasma center 530A.

[0051] The fleet model determines the optimal number of single blood collection devices 520A-F for the profile of the location, and the system 510 can provide instructions to the user to add or remove devices from the location based on the fleet model. For example, if the fleet model indicates that the plasma center 530A / B does not have a sufficient number of single blood collection devices 520A-F to meet the demand / number of donors and / or to achieve the target collection volume of the center 530A / B, then the system 510 will notify the user that the plasma center 530A / B should add additional single blood collection devices 520A-F. Alternatively, if Figure 6 As shown in , if the fleet model determines that the plasma center 530A / B has too many single blood collection devices 520A-F, the system 510 can instruct the user to remove one or more of the single blood collection devices 520A-F (e.g., remove single blood collection devices 520E and 520F).

[0052] When generating an optimal fleet model for one or more locations, the system 510 may use a variety of information, including but not limited to productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and / or other performance or production data thereof. The system 510 may also use the single blood sampling device location data to determine plasma center locations that may need to change equipment placement to meet the requirements of the new fleet model. Once the new fleet model is generated, the system 510 may provide guidance to the user in the form of a digital assistant with instructions for adjusting the placement of single blood sampling devices 520A-F at a specific plasma center location 530A / B in the company. For example, if the system 510 determines that the plasma center 530A has too many single blood sampling devices 520A-F, but the plasma center 530B does not have enough single blood sampling devices, then the system 510 may instruct the user to move / position one or more machines from the plasma center 530A to the plasma center 530B.

[0053] While in many cases it may be expected that the firmware 420 and firmware settings 430A-C will become outdated (e.g., if a firmware update is released), in other cases the firmware 420 and firmware settings 430A-C may unexpectedly become corrupted and / or change. To this end, the system 510 may use connections to the single blood collection devices 520A-F in the fleet to monitor for firmware version differences or firmware setting differences. The system 510 may then track, record, and report (e.g., to a company or user) any unexpected differences / changes between the single blood collection devices 520A-F. The system 510 may maintain a history / record of the differences / changes (as well as any other information received from the single blood collection devices 520A-F or generated by the system 510) in the data storage device 440.

[0054] It should be noted that although the above embodiments relate to plasma collection devices and plasma equipment, various embodiments of the present invention can be used in other equipment fleets. For example, various embodiments of the present invention can be used in other types of donation centers (e.g., whole blood donation centers, platelet donation centers, etc.) and other types of single blood collection equipment. In addition, embodiments of the present invention can be used in other medical institutions and non-medical institutions.

[0055] It should also be noted that terms such as "controller", "processor" and "server" may be used herein to describe devices that may be used in certain embodiments of the present invention, and should not be construed as limiting the present invention to any particular device type or system unless the context requires otherwise. Thus, a system may include, but is not limited to, a client, a server, a computer, an appliance, or other types of devices. Such devices typically include one or more network interfaces for communicating over a communication network and a processor (e.g., a microprocessor with memory and other peripherals and / or dedicated hardware) configured to perform device and / or system functions accordingly. Communication networks may typically include public and / or private networks; may include local area networks, wide area networks, metropolitan area networks, storage networks, and / or other types of networks; and may employ communication technologies, including but by no means limited to analog technology, digital technology, optical technology, wireless technology, networking technology, and interconnection technology.

[0056] The various components of the control program can be implemented individually or in combination. For example, each component can be implemented, or a dedicated server or a group of servers can be configured in a distributed manner.

[0057] It should also be noted that the devices may use communication protocols and messages (e.g., messages created, transmitted, received, stored and / or processed by the system), and such messages may be communicated by a communication network or medium. Unless the context otherwise requires, the present invention should not be construed as being limited to any particular communication message type, communication message format, or communication protocol. Therefore, communication messages may generally include, but are not limited to, frames, packets, datagrams, user datagrams, cellular or other types of communication messages. Unless the context otherwise requires, references to specific communication protocols are exemplary, and it should be understood that alternative embodiments may appropriately employ variations of such communication protocols (e.g., modifications or extensions to the protocol that may sometimes be made) or other protocols known or developed in the future.

[0058] It should also be noted that logic flow may be described herein to demonstrate various aspects of the present invention, and should not be construed as limiting the present invention to any specific logic flow or logic implementation. The described logic can be divided into different logic blocks (e.g., programs, modules, interfaces, functions, or subroutines) without changing the overall result or otherwise departing from the true scope of the present invention. In general, logic elements can be added, modified, omitted, performed in different orders, or implemented using different logic constructions (e.g., logic gates, loop primitives, conditional logic, and other logic constructions) without changing the overall result or otherwise departing from the true scope of the present invention.

[0059] The present invention may be implemented in many different forms, including but not limited to computer program logic used with a processor (e.g., a microprocessor, a microcontroller, a digital signal processor, or a general purpose computer), programmable logic used with a programmable logic device (e.g., a field programmable gate array (FPGA) or other programmable logic device (PLD)), discrete components, integrated circuit systems (e.g., an application specific integrated circuit (ASIC)), or any other components, including any combination thereof. In some embodiments of the present invention, the logic described in principle is implemented as a set of computer program instructions, which are converted into a computer executable form, stored in a computer readable medium, and executed by a microprocessor under the control of an operating system.

[0060] The computer program logic that implements all or part of the functions previously described herein can be implemented in various forms, including but not limited to source code form, computer executable form, and various intermediate forms (e.g., forms generated by an assembler, compiler, linker, or locator). The source code may include a series of computer program instructions for use with various operating systems or operating environments implemented in any of a variety of programming languages ​​(e.g., object code, assembly language, or a high-level language such as FORTRAN, C, C++, JAVA, or HTML). The source code may define and use various data structures and communication messages. The source code may be in a computer executable form (e.g., via an interpreter), or the source code may be converted into a computer executable form (e.g., via a translator, assembler, or compiler).

[0061] A computer program may be fixed in any form (e.g., source code form, computer executable form, or intermediate form) permanently or temporarily in a tangible storage medium such as a semiconductor memory device (e.g., RAM, ROM, PROM, EEPROM, or flash programmable RAM), a magnetic memory device (e.g., a floppy disk or a fixed disk), an optical memory device (e.g., a CD-ROM), a PC card (e.g., a PCMCIA card), or other memory device. A computer program may be fixed in any form as a signal that can be transmitted to a computer using any of a variety of communication technologies (including, but not limited to, analog, digital, optical, wireless, networking, and interconnect technologies). A computer program may be distributed in any form as a removable storage medium with an accompanying printed or electronic document (e.g., compressed packaged software), pre-installed with a computer system (e.g., on a system ROM or fixed disk), or distributed from a server or electronic bulletin board via a communication system (e.g., the Internet or the World Wide Web).

[0062] Hardware logic that implements all or part of the functionality previously described herein (including programmable logic used with programmable logic devices) can be designed using traditional manual methods, or can be electronically designed, captured, simulated, or documented using various tools such as computer-aided design (CAD), hardware description languages ​​(e.g., VHDL or AHDL), or PLD programming languages ​​(e.g., PALASM, ABEL, or CUPL).

[0063] Programmable logic may be permanently or temporarily fixed in a tangible storage medium, such as a semiconductor memory device (e.g., RAM, ROM, PROM, EEPROM, or flash programmable RAM), a magnetic memory device (e.g., a floppy disk or a fixed disk), an optical memory device (e.g., a CD-ROM), or other memory devices. Programmable logic may be fixed in a signal that can be transmitted to a computer using any of a variety of communication technologies, including but not limited to analog technology, digital technology, optical technology, wireless technology (e.g., Bluetooth), networking technology, and interconnect technology. Programmable logic may be distributed as a removable storage medium pre-installed with a computer system (e.g., on a system ROM or fixed disk) with an accompanying printed or electronic document (e.g., compressed packaged software), or distributed from a server or electronic device bulletin board via a communication system (e.g., the Internet or the World Wide Web). In fact, some embodiments may be implemented in a software as a service model ("SAAS") or a cloud computing model. Of course, some embodiments of the present invention may be implemented as a combination of both software (e.g., a computer program product) and hardware. Still other embodiments of the present invention are implemented entirely in hardware or entirely in software.

[0064] The embodiments of the present invention described above are exemplary only; many variations and modifications will be apparent to those skilled in the art. All such variations and modifications are intended to fall within the scope of the present invention as defined by any appended claims.

Claims

1. A fleet management system, comprising: a first plurality of single blood sampling devices, each of the first plurality of single blood sampling devices having a controller, firmware, and firmware settings; A fleet management device, the fleet management device is remote from each of the first plurality of single blood sampling devices and communicates with each of the first plurality of single blood sampling devices, the fleet management device comprising: an interface configured to allow a user to interact with the fleet management device; a server configured to receive information regarding firmware and firmware settings for each of said first plurality of single blood collection devices and configured to receive firmware files from a user and / or a remote repository; and A processor is configured to monitor a first plurality of single blood collection devices and process information about firmware and firmware settings received from each of the first plurality of single blood collection devices to determine which of the first plurality of single blood collection devices requires an update of firmware and / or firmware settings, the server is configured to distribute a firmware file to each of the first plurality of single blood collection devices that requires an update, wherein the processor is further configured to compile or analyze the information about firmware and firmware settings received from each of the first plurality of blood collection devices to identify differences between the firmware and firmware settings of any device in the first plurality of blood collection devices, the fleet management device is configured to notify a user of any differences, and / or distribute the firmware file to at least one of the plurality of blood collection devices to correct the differences between the firmware and firmware settings of the first plurality of blood collection devices.

2. The fleet management system of claim 1, further comprising a second plurality of single blood sampling devices remote from the fleet management device and in communication with the fleet management device.

3. The fleet management system according to claim 2, wherein: The server is further configured to receive information regarding firmware and firmware settings for each of the second plurality of single blood collection devices, and The processor is also configured to process information received from each of the second plurality of single blood sampling devices to determine which of the second plurality of single blood sampling devices requires updating of firmware and / or firmware settings, and the server is configured to distribute the firmware file to each of the second plurality of single blood sampling devices that requires updating.

4. The fleet management system of claim 2, wherein the first plurality of single blood sampling devices are located at a first donation center, and the second plurality of single blood sampling devices are located at a second donation center.

5. The fleet management system according to claim 1, wherein the fleet management device is configured to allow a user to remotely manage and / or monitor firmware files and / or firmware settings of each of the first plurality of single blood collection devices.

6. The fleet management system according to claim 5, wherein the fleet management device is configured to alert a user if a firmware file and / or a firmware setting file is successfully or unsuccessfully installed on at least one of the first plurality of single blood collection devices.

7. The fleet management system of claim 1, wherein the fleet management device is configured to collect additional information from each of the first plurality of single blood collection devices.

8. A fleet management system according to claim 7, wherein the additional information collected includes information selected from the group consisting of: single blood collection processes performed, productivity information, utilization information, the number of single blood collection devices in the donation center, performance data and inventory data.

9. The fleet management system of claim 1, wherein the fleet management device is configured to generate a fleet model for one or more donation centers.

10. The fleet management system of claim 9, wherein the fleet model is based at least in part on information selected from the group consisting of: productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and other performance or production data.

11. The fleet management system of claim 9, wherein the fleet model comprises a recommended number of single blood collection devices for one or more donation centers, and the server is configured to notify a user of the fleet model and the recommended number of single blood collection devices.

12. The fleet management system of claim 1, wherein the fleet management device comprises a data storage device configured to store information received from the first plurality of single blood sampling devices.

13. A fleet management device, comprising: an interface configured to allow a user to interact with the fleet management device; a server in communication with a first plurality of single blood sampling devices remote from the fleet management device, the server being configured to receive information regarding firmware and firmware settings for each of the first plurality of single blood sampling devices and being configured to receive firmware files from a user and / or a remote repository; as well as A processor is configured to monitor the first plurality of single blood collection devices and process information about firmware and firmware settings received from each of the first plurality of single blood collection devices to determine which of the first plurality of single blood collection devices needs to update firmware and / or firmware settings, the server is configured to distribute the firmware file to each of the first plurality of single blood collection devices that need to be updated, wherein the processor is also configured to compile or analyze the information about firmware and firmware settings received from each of the first plurality of blood collection devices to identify differences between the firmware and firmware settings of any device in the first plurality of blood collection devices, the fleet management device is configured to notify a user of any differences, and / or distribute the firmware file to at least one of the plurality of blood collection devices to correct the differences between the firmware and firmware settings of the first plurality of blood collection devices.

14. The fleet management device of claim 13, wherein the server is further in communication with a second plurality of single blood sampling devices remote from the fleet management device.

15. The fleet management device according to claim 14, wherein: The server is further configured to receive information regarding firmware and firmware settings for each of the second plurality of single blood collection devices, and The processor is also configured to process information received from each of the second plurality of single blood sampling devices to determine which of the second plurality of single blood sampling devices requires updating of firmware and / or firmware settings, and the server is configured to distribute the firmware file to each of the second plurality of single blood sampling devices that requires updating.

16. The fleet management device of claim 14, wherein the first plurality of single blood sampling devices are located at a first donation center, and the second plurality of single blood sampling devices are located at a second donation center.

17. The fleet management device of claim 13, wherein the fleet management device is configured to allow a user to remotely manage and / or monitor firmware files and / or firmware settings of each of the first plurality of single blood collection devices.

18. The fleet management device of claim 17, wherein the server is configured to alert a user if a firmware file and / or a firmware settings file is successfully or unsuccessfully installed on at least one of the first plurality of single blood sampling devices.

19. The fleet management device of claim 13, wherein the server is configured to receive additional information from each of the first plurality of single blood sampling devices.

20. The fleet management device of claim 19, wherein the additional information includes information selected from the group consisting of: apheresis procedures performed, productivity information, utilization information, number of apheresis devices within a donation center, performance data, and inventory data.

21. The fleet management device of claim 13, wherein the server and / or the processor is configured to generate a fleet model for one or more donation centers.

22. The fleet management device of claim 21, wherein the fleet model is based at least in part on information selected from the group consisting of: productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and other performance or production data.

23. The fleet management device of claim 21, wherein the fleet model comprises a recommended number of single blood sampling devices for one or more donation centers, and the server is configured to notify a user of the fleet model and the recommended number of single blood sampling devices.

24. The fleet management device of claim 13, further comprising a data storage device configured to store information received from the first plurality of single blood sampling devices.

25. A method for managing a fleet of single blood collection devices, comprising: remotely connect to and monitor a first plurality of single blood sampling devices, each of the single blood sampling devices having a controller, firmware, and firmware settings; receiving, in a server of a fleet management device, information regarding firmware and firmware settings of each of the first plurality of single blood sampling devices; In the server of the fleet management device, receiving a firmware file from a user and / or a remote repository; In the processor of the fleet management device, processing the information about firmware and firmware settings received from each of the first plurality of single blood sampling devices to determine which of the first plurality of single blood sampling devices requires an update of firmware and / or firmware settings; using the server of the fleet management device to distribute a firmware file to each of the first plurality of single blood collection devices that require updating; compiling or analyzing information regarding firmware and firmware settings received from each of the first plurality of blood collection devices to identify differences between firmware and firmware settings of any device in the first plurality of blood collection devices; as well as A user is notified of any discrepancies, and / or a firmware file is distributed to at least one of the plurality of blood collection devices to correct the discrepancies between the firmware and firmware settings of the first plurality of blood collection devices.

26. The method of claim 25, further comprising connecting to a second plurality of single blood collection devices remote from the fleet management device.

27. The method according to claim 26, further comprising: receiving, in the server of the fleet management device, information regarding firmware and firmware settings of each of the second plurality of single blood sampling devices; processing, using the processor of the fleet management device, information received from each of the second plurality of single blood sampling devices to determine which of the second plurality of single blood sampling devices requires an update of firmware and / or firmware settings; as well as The server of the fleet management device is used to distribute the firmware file to each of the second plurality of single blood collection devices that need to be updated.

28. The method of claim 26, wherein the first plurality of single blood collection devices are located at a first donation center and the second plurality of single blood collection devices are located at a second donation center.

29. The method of claim 25, further comprising: The firmware files and / or firmware settings of each of the first plurality of single blood collection devices are managed using the fleet management device.

30. The method of claim 29, further comprising: A user is alerted if the firmware file and / or firmware settings file is successfully or unsuccessfully installed on at least one of the first plurality of single blood collection devices.

31. The method of claim 25, further comprising: Additional information is collected from each of the first plurality of single blood collection devices.

32. A method according to claim 31, wherein the additional information collected includes information selected from the group consisting of: blood collection processes performed, productivity information, utilization information, number of single blood collection devices within a donation center, performance data and inventory data.

33. The method of claim 25, further comprising generating a fleet model for one or more donation centers.

34. The method of claim 33, wherein the fleet model is based at least in part on information selected from the group consisting of: productivity, utilization, telemetry, inventory, quantity, consumption, cost, timing, averages, rates, speed data, and other performance or production data.

35. The method of claim 33, wherein the fleet model comprises a recommended number of single blood collection devices for one or more donation centers, the method further comprising notifying a user of the fleet model and the recommended number of single blood collection devices.

36. The method of claim 25, further comprising: The information received from the first plurality of single blood sampling devices is stored in a data storage device in the fleet management device.

Images