Sample Preparation Validation

The use of computing devices and panel designer software to validate and execute sample preparation specifications addresses the issue of improper sample preparation, enhancing the accuracy and reliability of analysis results.

JP2024545126APending Publication Date: 2024-12-05BECKMAN COULTER INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024534251
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-04-29
Filing Date
2022-12-08
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Sample analysis can be compromised if the sample is not properly prepared, leading to inaccuracies in the analysis results.

Method used

A computing device and panel designer software are used to generate and verify sample preparation specifications, ensuring compliance with validation criteria, and a sample preparation instrument performs the preparation based on these specifications while monitoring for errors and generating notifications.

Benefits of technology

Ensures accurate and reliable sample preparation by validating user input specifications against predefined criteria, reducing errors and improving the quality of analysis results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024545126000001_ABST
    Figure 2024545126000001_ABST
Patent Text Reader

Abstract

The sample analysis system analyzes the samples. The panel design generates a sample preparation specification. The preparation instrument prepares the samples using the sample preparation specification and generates a prepared sample. The sample analyzer analyzes the prepared sample. The verifier verifies the operation of the sample analysis system. The sample analysis system has a transfer station that controls movement of the probe relative to the reaction plate. A probe washing module is also disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 287,327, filed December 8, 2021, and U.S. Provisional Patent Application No. 63 / 336,815, filed April 29, 2022, which were filed as PCT international patent applications on December 8, 2022, the entire disclosures of which are incorporated herein by reference in their entireties. [Background technology]

[0002] Before a sample is analyzed by a sample analyzer such as a flow cytometer, the sample undergoes a preparation process to prepare the sample. For example, the sample may be stained with a targeting reagent that targets components in the sample to facilitate analysis of the targeted components. As a more specific example, the target may be a subset of white blood cells in a blood sample, and the labeling reagent may be an antibody that attaches to the subset of white blood cells. Other sample preparation techniques may also be used. Sample analysis may be compromised if the sample is not properly prepared. Summary of the Invention [Means for solving the problem]

[0003] Generally speaking, the present disclosure is directed to sample preparation. In some embodiments, by way of non-limiting example, the present disclosure relates to sample preparation validation. Sample preparation operations are also disclosed. Various aspects are described in the present disclosure, including, but not limited to, the following aspects:

[0004] One aspect is a panel design system comprising a computing device and panel designer software executable by the computer to cause the panel design system to generate a sample preparation specification and to validate the sample preparation specification.

[0005] Another aspect is a method for panel validation that includes defining a user input specification, comparing the user input specification to validation criteria, determining that the user input specification does not comply with the validation criteria, generating at least one notification, and generating and outputting a sample preparation specification.

[0006] A further aspect is a sample preparation instrument comprising sample preparation hardware and sample preparation software executable by a computer of the sample preparation hardware to cause the sample preparation instrument to receive a sample preparation specification, define the sample preparation based on at least the sample preparation specification, validate the sample preparation, and generate a prepared sample based on the sample preparation.

[0007] Yet another aspect is a sample preparation method that includes receiving a sample preparation specification, defining a sample preparation based at least on the sample preparation specification, comparing the sample preparation to a sample preparation validation criterion, determining that the sample preparation does not comply with the sample preparation validation criterion, generating at least one notification, and sending at least one command to sample preparation hardware.

[0008] Another aspect is a sample analysis system comprising a panel design system that generates a sample preparation specification, a sample preparation instrument that prepares a sample using the sample preparation specification and generates a prepared sample, a sample analyzer configured to analyze the prepared sample, and at least one verifier configured to verify operation of the sample analysis system.

[0009] A further aspect is a non-transitory computer readable storage medium of a sample analysis system, the computer readable storage medium storing data instructions that, when executed by a processing device, cause the sample analysis system to perform the operations set forth in any one of the methods disclosed herein.

[0010] Yet another aspect is a panel design system that compares user input specifications to validation criteria and generates a notification when the user input specifications do not comply with the validation criteria.

[0011] Another aspect is a sample preparation instrument that uses a sample preparation specification to evaluate the sample preparation and generates a notification in response to detecting an error. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a schematic block diagram depicting an exemplary sample analysis system.

[0013] [Diagram 2] FIG. 2 is a flow chart illustrating an exemplary method for analyzing a sample.

[0014] [Diagram 3] FIG. 3 illustrates an example architecture of a computing device that may be used to implement aspects of the present disclosure.

[0015] [Figure 4] FIG. 4 is a schematic block diagram depicting one embodiment of a sample preparation specification system.

[0016] [Diagram 5] FIG. 5 is a flow chart illustrating an exemplary method for validating sample preparation specifications.

[0017] [Figure 6]FIG. 6 illustrates an exemplary user interface for validating at least a portion of the sample preparation specifications with respect to white blood cell concentration.

[0018] [Figure 7] FIG. 7 illustrates another exemplary user interface for validating at least a portion of the sample preparation specifications with respect to white blood cell concentration.

[0019] [Figure 8] FIG. 8 is a flow chart illustrating an exemplary method for verifying at least a portion of a sample preparation specification with respect to white blood cell concentration.

[0020] [Figure 9] FIG. 9 is a flow chart illustrating an exemplary method for verifying at least a portion of a sample preparation specification with respect to a reagent.

[0021] [Figure 10] FIG. 10 illustrates an exemplary user interface for verifying at least a portion of a sample preparation specification with respect to a reagent.

[0022] [Figure 11] FIG. 11 illustrates another exemplary user interface for verifying at least a portion of a sample preparation specification with respect to a reagent.

[0023] [Figure 12] FIG. 12 illustrates yet another exemplary user interface for verifying at least a portion of a sample preparation specification with respect to a reagent.

[0024] [Figure 13] FIG. 13 illustrates a further example of a user interface for verifying at least a portion of the sample preparation specifications with respect to reagents.

[0025] [Figure 14]FIG. 14 is a flow chart illustrating an exemplary method for verifying at least a portion of a sample preparation specification with respect to a reagent.

[0026] [Figure 15] FIG. 15 is a schematic block diagram depicting one embodiment of the sample preparation hardware.

[0027] [Figure 16] FIG. 16 is a cross-sectional view of one embodiment of sample preparation hardware.

[0028] [Figure 17] FIG. 17 is a schematic block diagram depicting one embodiment of a sample preparation instrument.

[0029] [Figure 18] FIG. 18 is a flow chart illustrating an exemplary method for validating sample preparation.

[0030] [Figure 19] FIG. 19 illustrates an exemplary user interface for validating sample preparation.

[0031] [Figure 20] FIG. 20 is a flow chart illustrating an exemplary method for verifying sample preparation in a sample loading procedure.

[0032] [Figure 21] FIG. 21 is a flow chart illustrating an exemplary method for verifying sample preparation when initiating a sample preparation procedure.

[0033] [Figure 22] FIG. 22 is a flow chart illustrating an exemplary method for predictively validating sample preparation.

[0034] [Diagram 23]FIG. 23 is a diagram illustrating an exemplary configuration of probes for use with reaction plate wells in a reaction station.

[0035] [Figure 24] FIG. 24 is a diagram illustrating another exemplary configuration of probes for use with reaction plate wells in a reaction station.

[0036] [Diagram 25] FIG. 25 is a schematic diagram depicting a portion of the sample preparation hardware that contains a probe washing module.

[0037] [Figure 26] FIG. 26 is a diagram depicting the probe washing module in more detail. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] Detailed Description Various embodiments will now be described in detail with reference to the drawings, in which like reference numerals represent like parts and assemblies throughout the several views. Reference to various embodiments does not limit the scope of the claims appended hereto. Additionally, any examples described herein are not intended to be limiting, but merely describe some of the many possible embodiments of the appended claims.

[0039] FIGURE 1 is a schematic block diagram depicting an exemplary sample analysis system 100. In the illustrated embodiment, the sample analysis system 100 includes a panel design system 102, a sample preparation instrument 104, and a sample analyzer 106. The exemplary panel design system 102 includes a computer 112 and panel designer software 114. The exemplary sample preparation instrument 104 includes sample preparation hardware 122 and sample preparation software 124. Also shown in FIGURE 1 are an operator 80, a sample 90, sample preparation consumables 92, prepared samples 94, a data transfer system 108, and a sample preparation specification 116.

[0040] In general terms, the sample analysis system 100 is operable to analyze a sample 90. Exemplary samples can include whole blood, bone marrow, dissociated tissue, peripheral mononuclear cells, fine needle aspirates, cerebrospinal fluid, and other single cell suspensions. Other samples or combinations of samples can also be analyzed in other embodiments.

[0041] The panel design system 102 generates a sample preparation specification 116. The sample preparation instrument 104 receives the sample preparation specification 116 via the data transfer system 108. Using the sample preparation specification 116, the sample preparation instrument 104 prepares the sample 90, which sometimes involves the use of sample preparation consumables 92, to produce a prepared sample 94. The sample analyzer 106 then analyzes the prepared sample 94.

[0042] In some embodiments, the panel design system 102 includes a computer 112 and panel designer software 114 executed by and operating on the computer 112. One example of the computer 112 is illustrated in FIG. 3. The panel designer software 114 can receive input from an operator 80 and define a sample preparation specification 116. The sample preparation specification 116 can then be used by the sample preparation instrument 104 to process the sample 90 and generate a prepared sample 94.

[0043] In some embodiments, the panel designer software 114 also includes a sample preparation specification verifier (e.g., sample preparation specification verifier 256 shown in FIG. 4) that operates to validate the sample preparation specification 116. The sample preparation specification 116 can then be provided to the sample preparation instrument 104.

[0044] An embodiment of the panel design system 102 is illustrated and described in further detail herein with reference to Figures 4-14.

[0045] The data transfer system 108 can be used to transfer the sample preparation specification 116 from the panel design system 102 to the sample preparation instrument 104. In one embodiment, the data transfer system 108 is a data communications network, such as the Internet or other network or combination of networks. In another embodiment, the data transfer system 108 can be a manual transfer method. For example, the sample preparation specification 116 can be stored on a computer readable storage device, such as a disk or flash drive, and then delivered to the sample preparation instrument 104 by an operator 80, etc.

[0046] In the illustrated example, the sample preparation instrument 104 includes sample preparation hardware 122 and sample preparation software 124. In some embodiments, the sample preparation software 124 is executed by and operates on the sample preparation hardware 122 (such as using the sample preparation computer 118 of the sample preparation hardware 122).

[0047] In some embodiments, the sample preparation software 124 includes a sample preparation verifier (e.g., sample preparation verifier 586 shown in FIG. 17) that operates to verify the sample preparation. For example, some sample preparations utilize sample preparation consumables 92, so the sample preparation verifier can operate to check whether the required sample preparation consumables 92 are present and available in sufficient quantities. The sample preparation software 124 is operable to communicate with the sample preparation hardware 122 and cause the sample preparation hardware 122 to prepare the sample 90 using the sample preparation consumables 92 according to the verified sample preparation. In another embodiment, the sample preparation software 124 is operable to verify the status of the sample preparation hardware 122 with respect to the sample preparation specification 116. Examples of sample preparation instruments 104 are illustrated and described in further detail herein with reference to FIGS. 15-26.

[0048] The sample analyzer 106 is an instrument that is operable to analyze the prepared sample 94. In some embodiments, the sample analyzer 106 is a laboratory instrument. One specific example of a sample analyzer 106 is a flow cytometer. Another example of a sample analyzer is a hematology analyzer. Other embodiments include other types of sample analyzers.

[0049] 2 is a flow chart illustrating an exemplary method 150 of analyzing a sample. In one example, method 150 is operated by the sample analysis system 100 shown in FIG. 1. In this example, method 150 includes operations 152, 154, and 156. Some embodiments also include one or more of operations 162 and 164.

[0050] An operation 152 is performed to generate the sample preparation specification 116. In some embodiments, the operation 152 is performed by the panel design system 102, such as shown in FIG.

[0051] Operation 154 is performed to prepare the sample 90 using the sample preparation specification 116 (shown in FIG. 1). In some embodiments, operation 154 is performed by a sample preparation instrument 104, such as shown in FIG.

[0052] An operation 156 is performed to analyze the prepared sample 94, prepared by operation 154. In some embodiments, operation 156 is performed by the sample analyzer 106, shown, for example, in FIG.

[0053] Further, some embodiments include one or more validation operations. For example, operation 152 may also include operation 162. Operation 162 is performed to validate the sample preparation specification 116.

[0054] As another example, operation 154 can include operation 164. Operation 164 is performed to verify sample preparation.

[0055] FIG. 3 illustrates an example architecture of a computing device that may be used to implement aspects of the disclosure, including any of computer 112 (FIGS. 1 and 4) and sample preparation computer 118 (FIGS. 1, 15, and 17) of sample preparation hardware 122. The computing device illustrated in FIG. 3 can be used to execute the operating systems, application programs, and software modules (including software engines) described herein. As an example, the computing device will be described below as computer 112. To avoid excessive repetition, this description of the computing device will not be repeated separately for each of the other computing devices herein, although such devices may also be configured as illustrated and described with reference to FIG. 3.

[0056] The computer 112, in some embodiments, includes at least one processing device 180, such as a central processing unit (CPU). Various processing devices are available from various manufacturers, such as Intel or Advanced Micro Devices. In this example, the computer 112 also includes a system memory 182 and a system bus 184, which couples various system components, including the system memory 182, to the processing device 180. The system bus 184 may be one of any number of types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.

[0057] Examples of computing devices suitable for computer 112 include a server computer, a desktop computer, a laptop computer, a tablet computer, a mobile computing device (such as a smartphone, an iPod® or iPad® mobile digital device, or other mobile device), or other device configured to process digital instructions.

[0058] The system memory 182 includes a read-only memory 186 and a random access memory 188. A basic input / output system 190, containing the basic routines that act to transfer information within computer 112, such as during start-up, is typically stored in the read-only memory 186.

[0059] The computer 112 also includes a secondary storage device 192, in some embodiments, such as a hard disk drive for storing digital data. The secondary storage device 192 is connected to the system bus 184 by a secondary storage interface 194. The secondary storage device 192 and their associated computer-readable media provide non-volatile storage of computer-readable instructions (including application programs and program modules), data structures, and other data for the computer 112.

[0060] Although the exemplary environment described herein employs a hard disk drive as a secondary storage device, other types of computer-readable storage media are used in other embodiments. Examples of these other types of computer-readable storage media include magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, compact disk read-only memory, digital versatile disk read-only memory, random access memory, or read-only memory. Some embodiments include non-transitory media. In addition, such computer-readable storage media can include local storage or cloud-based storage.

[0061] A number of program modules may be stored in the secondary storage device 192 or memory 182, including an operating system 196, one or more application programs 198, other program modules 200 (such as the software engine described herein), and program data 202. One example of an application program 198 is the sample preparation software 124. The computer 112 may be running an operating system such as Microsoft Windows, Google Chrome, or the like. TM Any suitable operating system may be utilized, such as the Apple OS, and any other operating system suitable for computing devices.

[0062] In some embodiments, a user provides input to the computer 112 through one or more input devices 204. Examples of input devices 204 include a keyboard 206, a mouse 208, a microphone 210, and a touch sensor 212 (such as a touchpad or a touch-sensitive display). Other embodiments include other input devices 204. The input devices are connected to the processing device 180 through an input / output interface 214, which is often coupled to the system bus 184. These input devices 204 can be connected by any number of input / output interfaces, such as a parallel port, a serial port, a game port, or a universal serial bus. Wireless communication between the input devices and the interface 214 is also possible, and in some possible embodiments includes infrared, BLUETOOTH wireless technology, 802.11a / b / g / n, cellular, or other radio frequency communication systems.

[0063] In the exemplary embodiment, a display device 216, such as a monitor, liquid crystal display device, projector, or touch-sensitive display device, is also connected to the system bus 184 via an interface, such as a video adapter 218. In addition to the display device 216, computer 112 may include various other peripheral devices (not shown), such as speakers or printers.

[0064] When used in a local area networking environment or a wide area networking environment (such as the Internet), the computer 112 is typically connected to the network through a network interface 220, such as an Ethernet interface. Other possible embodiments use other communication devices. For example, some embodiments of the computer 112 include a modem for communicating across the network.

[0065] Computer 112 typically includes at least some form of computer-readable media. Computer-readable media includes any available media that can be accessed by computer 112. By way of example, computer-readable media include computer-readable storage media and computer-readable communication media.

[0066] Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any device configured to store information such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, random access memory, read-only memory, electrically erasable programmable read-only memory, flash memory or other memory technology, compact disc read-only memory, digital versatile disks or other optical storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by computer 112. Computer-readable storage media does not include computer-readable communication media.

[0067] Computer-readable communication media typically embodied computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information within the signal. By way of example, computer-readable communication media includes wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, radio frequency, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer-readable media.

[0068] The computing device illustrated in FIG. 3 is also an example of a programmable electronic device, which may include one or more such computing devices, and when multiple computing devices are included, such computing devices can be coupled together with a suitable data communications network to collectively perform various functions, methods, or operations disclosed herein.

[0069] FIG. 4 is a schematic block diagram illustrating one example of the panel design system 102 shown and described in FIG. 1. In this example, the panel design system 102 includes a computer 112. In some embodiments, the computer 112 includes a panel designer software 114, a file storage device 252, and validation criteria 254. The panel designer software 114 is executed by and operates on the computer 112. Also shown in this illustrated example is a sample preparation specification 116. In some embodiments, the panel designer software 114 includes a sample preparation specification verifier 256 and a sample preparation specification composer 258. The exemplary sample preparation specification verifier 256 includes a WBC range verifier 264 and a reagent block verifier 266. The exemplary sample preparation specification composer 258 includes a user input specification 268.

[0070] In some embodiments, the user input specification 268 can be from, for example, a manual input of a user. The sample preparation specification verifier 256 then operates to validate the user input specification 268 against the validation criteria 254 using the WBC range verifier 264 and the reagent block verifier 266, respectively. In the illustrated example, the validation criteria 254 are provided by the file storage 252. After validation, the panel designer software 114 is operable to generate the sample preparation specification 116 and output the sample preparation specification 116 via the file storage 252. An exemplary method of using the WBC range verifier 264 is illustrated and described in further detail herein with reference to FIG. 8. Another exemplary method of using the reagent block verifier 266 is illustrated and described in further detail herein with reference to FIG. 9 and FIG. 14.

[0071] 5 is a flow chart illustrating an example method 280 of validating a sample preparation specification. In one embodiment, the method 280 is performed by the panel design system 102 shown in FIG 4. In this embodiment, the method 280 includes operations 282, 284, 286, 288, and 290.

[0072] An operation 282 is performed to define a user input specification 268 for sample preparation. In some embodiments, operation 282 is performed by the sample preparation specification composer 258, shown, for example, in FIG.

[0073] An operation 284 is performed to compare the user input specification 268 with the validation criteria 254. In some embodiments, operation 284 is performed by the sample preparation specification validator 256, shown, for example, in FIG.

[0074] An operation 286 is performed to determine that the user input specification 268 does not comply with the validation criteria 254. In some embodiments, operation 286 is performed by the sample preparation specification validator 256, shown, for example, in FIG.

[0075] An operation 288 is performed to generate a notification to alert the user of any errors found by validating the user input specification 268 according to the determination made by operation 286. In some embodiments, operation 288 is performed by the sample preparation specification validator 256, shown, for example, in FIG.

[0076] An operation 290 is performed to generate and output the sample preparation specification 116. In some embodiments, operation 290 is performed by the sample preparation specification verifier 256, shown, for example, in FIG.

[0077] In some further embodiments, the sample preparation specification 116 generated and output by operation 290 is configured to contain an indicator. If any portion of the user input specification 268 does not comply with the validation criteria 254, the indicator operates to indicate an error status with respect to the definition of the user input specification 268. In some examples, such an indicator can be a flag variable having a value that can be "true" or "false". To indicate an error status, the value of the flag variable will be "true", otherwise the value of the flag variable will be "false". In other examples, the sample preparation specification 116 contains a hash code. In some embodiments, the hash code is generated by processing the sample preparation specification 116. The hash code can be used to demonstrate that no unauthorized modifications have been made to the sample preparation specification 116. For example, it can be edited only by using the panel designer software 114.

[0078] FIG. 6 illustrates and describes an exemplary user interface 320 for using the WBC range verifier 264, such as shown in FIG. 4, to check and verify at least a portion of the user input specification 268 in the sample preparation specification composer 258, i.e., the portion related to white blood cells. In this illustrated example, the user interface 320 displays a drop-down menu selector 322. With the drop-down menu selector 322, the user can select to expand the design options for the user to enter the portion of the user input specification 268 related to white blood cells. In some embodiments, the design options include a first WBC upper limit field 324 and a second WBC upper limit field 326. After the user, for example, enters data into fields 324 and 326, the WBC range verifier 264 operates to check the data against some predefined rules. In some examples, the rules checked by WBC range verifier 264 include that the data in fields 324 and 326 must be within a defined range (e.g., between 1,000 and 150,000 cells per microliter). In some further examples, the rules include that the data in second WBC upper limit field 326 must exceed the data in first WBC upper limit field 324 by at least 1,000 cells per microliter.

[0079] In some further embodiments, the exemplary user interface 320 includes a volume field 328 corresponding to the second WBC upper limit field 326, a first process checkbox 334 corresponding to the first WBC upper limit field 324, and a second process checkbox 336 corresponding to the second WBC upper limit field 326. For both checkboxes 334 and 336, the user has the option to check or not check. A user check of the first process checkbox 334 indicates that the user specifies that the sample is to be processed if the white blood cell concentration found in the sample is lower than or equal to the data in the first WBC upper limit field 324. A user check of the second process checkbox 336 indicates that the user specifies that the sample is to be processed if the white blood cell concentration found in the sample is lower than or equal to the data in the second WBC upper limit field 326 but higher than the data in the first WBC upper limit field 324. Some other examples of rules checked by the WBC range verifier 264 include that if one of the processing checkboxes (e.g., the second checkbox 336) is checked by the user, the data in the corresponding volume field 328 must be within a specified range (e.g., within 25-400 microliters).

[0080] In some other embodiments, the exemplary user interface 320 includes an add row button 342 and a delete row button 344. The user has the option to delete a row of data by clicking the delete row button 344 and add a row of data by clicking the add row button 342. Some other examples of rules checked by the WBC range verifier 264 include that if an additional row of data is added by the user, the sample volume is less than the sample volume from the previous row.

[0081] In some further embodiments, the example user interface 320 includes a dilution checkbox 346 and a dilution volume field 348. The user has the option to enter data into the dilution volume field 348 only if the user checks the dilution checkbox 346.

[0082] In some other embodiments, the WBC range verifier 264 operates to highlight (e.g., using a color-coded indication, such as changing the color to red) the outer boundaries of any fields that have data checked and determined to be incorrect by the WBC range verifier 264. This operation of the WBC range verifier 264 is configured to inform the user of the fields in which the user has entered incorrect data.

[0083] In some further embodiments, the WBC range verifier 264 operates to cause the exemplary user interface 320 to display an information box 352 containing rule information about data to be entered into a field if or when a user hovers a mouse indicator of the mouse 208, such as shown in Figure 3, in an area proximate to the corresponding data field. A mouse pointer is one example of a pointer, and other pointers (e.g., touch input pointers, trackpad pointers, and the like) can also be used in other embodiments.

[0084] 7 illustrates and describes an exemplary dialog box 360 for using the WBC range verifier 264, such as that shown in FIG. 4, to display all errors found by the WBC range verifier 264 when validating a portion of the user input specification 268 for white blood cells. In the illustrated embodiment, the dialog box 360 displays a drop-down list selector 362 and an error count indicator 364. The error count indicator 364 operates to inform the user of the number of errors the WBC range verifier 264 has found after validating the portion of the user input specification 268 for white blood cells.

[0085] In some embodiments, using a drop down list selector 362, a user can select to have the example dialog box 360 display a WBC error list 366 that contains detailed information about any errors that the WBC range validator 264 finds after validating the portion of the user input specification 268 for the white blood cells. In other examples, the dialog box 360 also displays a close WBC error list button 368. By clicking the close WBC error list button 368, a user can select to have the example dialog box 360 close.

[0086] 8 is a flow chart illustrating an exemplary method 380 for validating a portion of a sample preparation specification with respect to white blood cells. In one embodiment, method 380 is performed by WBC range verifier 264, shown in FIG. 4. In this embodiment, method 380 includes operations 382, ​​384, 386, 388, and 390.

[0087] In the illustrated embodiment, operation 382 is performed to check the data entered by the user for the WBC concentration upper limit. Operation 384 is performed to check the data entered by the user for the sample volume. To highlight errors found by operations 382 and 384, operation 386 is performed to highlight (e.g., change the color to red) the outer boundaries of all data fields that are determined to contain errors. To provide more relevant information to the user, operation 388 is performed to display rule information for the data fields around which the user hovers the user's mouse indicator. To summarize all errors found in the notification, operation 390 is performed to list all errors to be displayed in a dialog box.

[0088] 9 is a flow chart illustrating an exemplary method 420 of validating at least a portion of a sample preparation specification for a reagent. Examples of reagents include antibodies, lysing agents, wash buffers, diluents, etc. In one example, the method 420 is operated by the reagent block verifier 266, shown in FIG. 4. In some embodiments, the reagent block verifier 266 operates to validate at least a portion of the user input specifications 268 for a reagent, i.e., portions that are organized by the panel designer software 114 to have multiple hierarchies. The user input specifications 268 for a sample include specifications for at least one tube. Each tube specification includes specifications for at least one block, and each block specification further includes specifications for at least one reagent.

[0089] In the illustrated embodiment, the method 420 includes operations 422, 424, 426, 428, 430, 432, 434, 436, 438, 440, and 442. Operation 422 is performed to begin verifying a portion of the sample preparation specification for a reagent. Operation 424 is then performed to begin verifying the specifications for the current tube as part of the current sample. Operation 426 is then performed to begin verifying the specifications for the current block as part of the current tube. Following operation 426, operation 428 is performed to verify the specifications for the current reagent as part of the current block. After operation 428, operation 430 is performed to check whether the verification of all reagents in the current block has been completed. If no, operation 432 is performed to move on to the next reagent in the current block and prepare that reagent for verification as the new current reagent. Operation 428 is then performed again to verify the specifications for the new current reagent.

[0090] If the answer to operation 430 is "yes", operation 434 is performed to check whether verification of all blocks in the current block has been completed. If "no", operation 436 is performed to move to the next block in the current block and prepare that block for verification as the new current block. Operation 426 is then performed again to begin verifying the specifications for the new current block.

[0091] If the answer to operation 434 is "yes," then operation 438 is performed to check whether verification of all tubes in the current sample has been completed. If "no," then operation 440 is performed to move on to the next tube in the current sample and prepare that tube for verification as the new current tube. Operation 424 is then performed again to begin verifying the specifications for the new current tube.

[0092] If the answer to operation 438 is yes, operation 442 is performed to finish validating the current sample and mark it as complete.

[0093] 10 illustrates and describes an example user interface 450 for using the reagent block verifier 266, such as shown in FIG. 4, to check and verify at least a portion of the user input specification 268, i.e., the portion relating to reagents. In this illustrated example, the user interface 450 includes a reagent name field 452. In some examples, the rules checked by the reagent block verifier 266 include that the reagent name field 452 requires input of a reagent name or identification string, etc. In some embodiments, the user interface 450 includes a minimum incubation minutes field 454.

[0094] In some other embodiments, the reagent block verifier 266 operates to highlight (e.g., change color to red) the outer boundary of any field that has data checked and determined to be incorrect by the reagent block verifier 266. This operation of the reagent block verifier 266 is configured to notify the user of the fields in which the user has entered incorrect data.

[0095] In some further embodiments, the reagent block verifier 266 operates to cause the exemplary user interface 450 to display an information box 456 containing rule information about the data to be entered into the field if and when the user hovers the mouse indicator of the mouse 208, such as shown in FIG. 3, within an area near a corresponding data field.

[0096] 11 illustrates and describes another example user interface 460 for using the reagent block verifier 266, such as shown in FIG. 4, to check and verify at least a portion of the user input specification 268, i.e., the portion relating to reagents. In this illustrated embodiment, the user interface 460 includes a reagent volume field 462. In some embodiments, the rules checked by the reagent block verifier 266 include that the data in the reagent volume field 462 must be within a defined range (e.g., 3-100 microliters).

[0097] In some embodiments, the user interface 460 includes a minimum incubation minutes field 454. In some examples, the rules checked by the reagent block verifier 266 include that the minimum incubation minutes field 454 requires entry of a numerical value, for example. Another example of a rule checked by the reagent block verifier 266 is that the data in the minimum incubation minutes field 454 must not exceed 58 when the units for the data are minutes.

[0098] In some other embodiments, the reagent block verifier 266 operates to highlight (e.g., change color to red) the outer boundary of any field that has data checked and determined to be incorrect by the reagent block verifier 266. This operation of the reagent block verifier 266 is configured to notify the user of the fields in which the user has entered incorrect data.

[0099] In a further embodiment, the reagent block verifier 266 operates to cause the exemplary user interface 460 to display an information box 456 containing rule information about the data to be entered into the field if and when the user hovers the mouse indicator of the mouse 208, such as shown in FIG. 3, within an area near the corresponding data field.

[0100] 12 illustrates and describes yet another exemplary user interface 470 for using the reagent block verifier 266, such as shown in FIG. 4, to check and verify at least a portion of the user input specification 268, i.e., the portion relating to the reagents. In this illustrated embodiment, the user interface 470 includes a wash sample selector 472. The wash sample selector 472 allows the user to select to have the user input specification 268 include and record the user's selection among various wash cycle options. Some examples of wash cycle options include "no wash" or "one wash cycle", etc. If the user selects an option other than "no wash", the user interface 470 can display a maximum incubation minutes field 474 adjacent to the minimum incubation minutes field 454.

[0101] In further embodiments, if the user selects an option for the wash sample selector 472 that is not "no wash," the user interface 470 may display a wash resuspension checkbox 476. For the wash resuspension checkbox 476, the user has the option to check or not check. A user's checking of the wash resuspension checkbox 476 indicates that the user is specifying that the sample will be resuspended using, for example, a wash buffer. If the wash resuspension checkbox 476 is checked by the user, the user interface 470 may display a resuspension volume field 478. Some examples of rules checked by the reagent block verifier 266 include that the data in the resuspension volume field 478 must be within a specified range (e.g., 450-1,500 microliters).

[0102] In some other embodiments, the reagent block verifier 266 operates to highlight (e.g., change color to red) the outer boundary of any field that has data checked and determined to be incorrect by the reagent block verifier 266. This operation of the reagent block verifier 266 is configured to notify the user of the fields in which the user has entered incorrect data.

[0103] In yet a further embodiment, the reagent block verifier 266 operates to cause the exemplary user interface 470 to display an information box 456 containing rule information about the data to be entered into the field if and when the user hovers the mouse indicator of the mouse 208, such as shown in FIG. 3, within an area near a corresponding data field.

[0104] 13 illustrates and describes another exemplary dialog box 490 for use with the reagent block verifier 266, such as that shown in FIG. 4, to display all errors found by the reagent block verifier 266 when validating a portion of the user input specification 268 for a reagent. In the illustrated embodiment, the dialog box 490 displays a reagent drop-down list selector 492 and a reagent error count indicator 494. The reagent error count indicator 494 operates to inform the user of the number of errors the reagent block verifier 266 has found after validating a portion of the user input specification 268 for a reagent.

[0105] In some embodiments, the example dialog box 490 includes an error status indicator 502. If at least one error is present as found by the reagent block verifier 266, the error status indicator 502 operates to indicate the error status, for example, by displaying an icon.

[0106] In a further embodiment, using the reagent drop down list selector 492, the user can select to have the exemplary dialog box 490 display a reagent error list 496 that contains detailed information about any errors that the reagent block validator 266 finds after validating the portion of the user input specification 268 for the reagent. In another example, the dialog box 490 also displays a close reagent error list button 498. By clicking the close reagent error list button 498, the user can select to have the exemplary dialog box 490 close.

[0107] 14 is a flow chart illustrating an exemplary method 520 of validating a portion of a sample preparation specification with respect to a reagent. In one embodiment, method 520 is operated by the reagent block verifier 266, shown in FIG. 4. In this embodiment, method 520 includes operations 522, 524, 526, 528, 530, 532, and 534.

[0108] In the illustrated example, operation 522 is performed to check the data in the Reagent Name field. Operation 524 is performed to check the data in the Reagent Volume field. Operation 526 is performed to check the data in the Incubation Minutes field. Operation 528 is performed to check the data for the Resuspension option.

[0109] In some embodiments, to highlight errors found by operations 522, 524, 526, and 528, operation 530 is performed to highlight (e.g., change color to red) the outer boundaries of all data fields that are determined to contain errors. To provide more relevant information to the user, operation 532 is performed to display rule information for the data fields around which the user hovers the user's mouse indicator. To summarize all errors found in the notification, operation 534 is performed to list all errors to be displayed in a dialog box.

[0110] 15 is a schematic block diagram illustrating and describing one example of sample preparation hardware 122 (also illustrated in FIG. 1). In this illustrated example, sample preparation hardware 122 includes a cell concentration estimator 550, a reagent station 552, a reaction station 554, and a lysis station 556. In some embodiments, sample preparation hardware 122 can further include a transfer station 558 with one or more probes 560, a sample preparation computer 118 with memory 182 and at least one processing device 180, a touch display 216, an input station 562, a single tube loader 564, a cell washer 566, a liquid reagent housing 568 and a dry reagent carousel 570 in the reagent station 552, a bead mixer 571, a plate mixer 572 in the reaction station 554, a probe wash station 573, and an output station 574.

[0111] The probe 560 of the transfer station 558 can aspirate, transport, and dispense various substances between components of the sample preparation instrument 104. The substances can include samples, labeling reagents, lysis reagents, diluent reagents, and buffers, among other examples. The probe 560 can puncture a capped or sealed tube, vial, cartridge, bottle, or other similar container and aspirate or be inserted into the material in the open-top tube, vial, cartridge, bottle, or other similar open-top container.

[0112] The sample preparation computer 118, which is described in more detail in FIG. 3, is the controller and information processor of the sample preparation instrument 104. In some embodiments, the sample preparation computer 118 can store previously authored panels received from a remote computing device. For example, a user, such as a laboratory technician or analyst, can utilize a panel authoring and management application running on a remote computing device to author panels for different types of samples and different types of analyses for execution by the sample preparation instrument 104. The authored panels can then be transmitted to the sample preparation instrument 104 via a network or wired connection or a physical memory device, such as a USB drive. In other embodiments, the sample preparation computer 118 can run a panel authoring and management application to enable a user to author panels using the sample preparation instrument 104 (e.g., via a user interface provided via the touch display 216), which are then stored by the sample preparation computer 118. Each panel can define a particular workflow to be performed when preparing samples for the samples for the panel. For example, a panel may include a set of rules, hereafter referred to as a predefined set of rules, that defines a particular workflow associated with sample preparation.

[0113] The sample preparation computer 118 can operate the sample preparation software 124 to provide the authored panels for display through a sample loading user interface, shown and described with reference to FIG. 19, and allow a user to select one or more of the panels for pairing with a received sample. In some embodiments, the sample loading user interface can be provided through the touch display 216 of the sample preparation instrument 104. The selected one or more panels can then be used to manage the operations of the sample preparation instrument 104 during sample preparation. For example, a set of predefined rules associated with each panel can provide, among other embodiments, the order of operations, the types and volumes of samples and reagents involved in each operation, the time associated with each operation, and the components of the sample preparation instrument 104 involved in each operation. Based on the selected one or more panels, the sample preparation computer 118 can generate signals for transmission to individual components of the sample preparation instrument 104 providing instructions for performing the operations.

[0114] Additionally, the sample preparation computer 118 can operate in conjunction with the cell concentration estimator 550 to determine the white blood cell concentration in the sample. Based on a set of predefined rules associated with one or more selected panels, the sample preparation computer 118 can further determine whether to process the sample, the sample volume of the sample based on the white blood cell concentration estimate, and whether the sample should be diluted, among other decisions discussed herein.

[0115] In some embodiments, the input station 562 accepts an input cassette that is inserted into the sample preparation instrument 104 by a user. The input cassette can hold one or more capped tubes containing a sample. In some embodiments, each tube contains a different sample (e.g., a sample from a different patient). The input station 562 can accept different types of cassettes corresponding to different types of tubes. The input station 562 includes a reader or scanner capable of reading machine-readable codes such as bar codes, QR codes, or radio frequency identification (RFID) tags, among other similar embodiments. In some embodiments, each tube has an associated code that is scanned by the reader or scanner to identify the sample in the tube.

[0116] FIG. 16 depicts in a cross-sectional view an example of the hardware components shown and described in FIG. 15. In this illustrated example, in addition to the hardware components described in FIG. 15, FIG. 16 further depicts a waste container 575, a diluent reagent container 576, and a condensate collector 577. Waste associated with the sample preparation process, including sample waste from the cell concentration estimator 550, is dispensed into the waste container 575. The diluent reagent can be used in several steps throughout the preparation process, including cell concentration estimation and reconstituting dry reagents, among other examples. The condensate collector 577 can collect any condensate resulting from cooling of the labeled reagent (e.g., generated by the liquid reagent housing 568).

[0117] 17 is a schematic block diagram illustrating an example of a sample preparation instrument 104. In this illustrated example, the sample preparation instrument 104 includes an example of sample preparation hardware 122, including a sample preparation computer 118, a sensor 602, and an actuator 604. In some embodiments, the sample preparation computer 118 includes sample preparation software 124, a sample preparation file storage 582, and a sample preparation validation criteria 584. The sample preparation software 124 is executed by and operates on the sample preparation computer 118. Also shown in this illustrated example is a sample preparation specification 116. In some examples, the sample preparation software 124 includes a sample preparation verifier 586, a sample preparation 588, and a serpentine pattern generator 590. The exemplary sample preparation verifier 586 includes a loading verifier 592, a start-up verifier 594, and a prediction verifier 596.

[0118] In some embodiments, the sample preparation computer 118 is operable to import the sample preparation specification 116 generated and output by the panel designer software 114, as shown and described in FIG. 4. Through the sample preparation file storage 582, the sample preparation software 124 is operable to take the sample preparation specification 116 as its first input. The sample preparation software 124 is also operable to take a user selection (e.g., by manual entry) as its second input. With the inputs including at least the sample preparation specification 116 and the user selection, the sample preparation software 124 can then generate a sample preparation 588, which can be an ordered list of actions for the sample preparation instrument 104 to perform.

[0119] In some embodiments, the sample preparation verifier 586 can verify the sample preparation 588 against sample preparation verification criteria 584, which can be provided by the sample preparation file storage 582. The sensor 602 operates to provide information when requested by the sample preparation verifier 586 for verification. If the sample preparation verifier 586 determines that the sample preparation 588 fails to comply with the sample preparation verification criteria 584, the sample preparation verifier 586 can generate a notification to alert the user.

[0120] In other embodiments, the sample preparation verifier 586 can send commands to the sample preparation hardware 122 to change the operation of the sample preparation instrument 104. With the command, the sample preparation verifier 586 can operate with the aid of the actuator 604 to disable the sample preparation 588 from being performed or occurring. For example, the sample preparation verifier 586 can use the loading verifier 592 to prevent the sample preparation instrument 104 from loading the sample to be prepared. In other examples, the sample preparation verifier 586 can use the activation verifier 594 to cause the sample preparation instrument 104 to stop operating according to the sample preparation 588. In further examples, the sample preparation verifier 586 can use the prediction verifier 596 to cause the sample preparation instrument 104 to stop operating or loading in view of other operations being activated or scheduled to be activated on the sample preparation instrument 104.

[0121] Examples of sensors 602 include floats in the waste container 575, diluent reagent container 576, and condensate collector 577, optical cameras for reagent identification, or any other type of sensor. Examples of actuators 604 include input station 562, probe 560, single tube loader 564, or any other type of actuator.

[0122] 18 is a flow chart illustrating an exemplary method 620 for validating sample preparation. In one embodiment, the method 620 is operated by the sample preparation instrument 104 shown in FIG. 17. In this embodiment, the method 620 includes operations 622, 624, 626, 628, 630, and 632.

[0123] An operation 622 is performed to import the sample preparation specification 116 to prepare the sample. In some embodiments, operation 622 is performed by the sample preparation computer 118, shown, for example, in FIG.

[0124] An operation 624 is performed to define the sample preparation 588 based on the selections made regarding the sample preparation specification 116. In some embodiments, operation 624 is performed by the sample preparation software 124, such as shown in FIG.

[0125] An operation 626 is performed to compare the sample preparation 588 to the sample preparation validation criteria 584. In some embodiments, operation 626 is performed by the sample preparation verifier 586, shown, for example, in FIG.

[0126] Operation 628 is performed to determine whether the sample preparation 588 does not comply with the sample preparation validation criteria 584. In some embodiments, operation 628 is performed by a sample preparation verifier 586, shown, for example, in FIG.

[0127] An operation 630 is performed to generate a notification to a user according to the determination made by operation 628. In some embodiments, operation 630 is performed by the sample preparation verifier 586, shown, for example, in FIG.

[0128] An operation 632 is performed to send a command to the sample preparation hardware 122 to alter the operation of the sample preparation instrument 104 according to the determination made by operation 628. In some embodiments, operation 632 is performed by the sample preparation verifier 586, shown, for example, in FIG.

[0129] 19 illustrates and describes an exemplary user interface 650 for using the sample preparation verifier 586, such as shown in FIG. 17, to check and verify a sample preparation 588. In this illustrated embodiment, the exemplary user interface 650 includes a sample preparation ID field 652 and a sample preparation error status indicator 654. If a sample preparation defined by the sample preparation software 124 that corresponds to the data in the sample preparation ID field 652 (e.g., an identification string, etc.) is determined by the sample preparation verifier 586 to contain an error, the sample preparation error status indicator 654 operates to notify the user of the error status. For example, the sample preparation error status indicator 654 may display an icon indicating an error.

[0130] In some embodiments, the exemplary user interface 650 displays a sample preparation error window 656 that contains information about all errors found from the currently selected sample preparation by the sample preparation verifier 586. The sample preparation error window 656 also corresponds to the currently selected sample preparation ID field 652. In some examples, the user interface 650 includes a remove sample preparation button 658. By clicking on the remove sample preparation button 658, the user can remove the corresponding sample preparation from the current selection. In other examples, the user interface 650 displays a global error status indicator 660. When any selected sample preparation is determined by the sample preparation verifier 586 to contain any errors, the global error status indicator 660 operates to inform the user of the error status. For example, the global error status indicator 660 can display an icon indicating an error. In an exemplary scenario, the user can use the remove sample preparation button 658 to remove all sample preparation selections that have errors. When all sample preparations remaining in the selection are error-free, the global error status indicator 660 may change its indication to reflect the status change.

[0131] In other embodiments, the exemplary user interface 650 includes a load button 662. A user can click the load button 662 to send a command to the sample preparation instrument 104 to execute in loading the sample to be prepared. If the sample preparation verifier 586 determines that the currently selected sample preparation contains any errors, the sample preparation verifier 586 can disable the load button 662 and prevent the user from sending the command to load. In an exemplary scenario, if the global error status indicator 660 indicates an error status, the load button 662 will be disabled.

[0132] In some embodiments, validations to be checked by the sample preparation verifier 586 using the loading verifier 592 include checking error status variables of the sample preparation specification 116, checking the file format and hash code of the sample preparation specification 116, checking the white blood cell concentration in the sample against the user-entered WBC range of the sample preparation specification 116, checking the presence and expiration date of the sample preparation consumables 92, checking the status of the sample preparation hardware 122 (e.g., instrument syringe QC status), checking the reagent type of any custom reagents, and checking the sample preparation specification 116 against expected index values ​​for tubes, blocks, and reagent order. In further embodiments, additional rules checked by the loading verifier 592 include that all blocks of the sample preparation specification 116 must contain at least one reagent or a single reagent kit.

[0133] 20 is a flow chart illustrating an exemplary method 680 of verifying at least a portion of the sample preparation 588 at the time of loading the sample. In one embodiment, the method 680 is operated by the loading verifier 592 shown in FIG. 17. In this embodiment, the method 680 includes operations 682, 684, 686, 688, 690, 692, 694, and 696.

[0134] An operation 682 is performed to define the relevant portions of the sample preparation 588 based on the selections regarding the imported sample preparation specification 116 .

[0135] In some embodiments, any combination of one or more of operations 684, 686, 688, 690, and 692 may be performed. Operation 684 may be performed to check the error status of the selected sample preparation specification 116. Operation 686 may be performed to check the white blood cell concentration against a user-input WBC range contained in the sample preparation specification 116. Operation 688 may be performed to check the status of the sample preparation consumables 92. For example, the loading verifier 592 may be operable to check the volume of the remaining consumables in the diluent reagent container 576 by using information obtained by the float sensor. Operation 690 may be performed to check the status of the sample preparation hardware 122. Operation 692 may be performed to check the composition of the sample preparation specification 116. For example, the loading verifier 592 may be operable to check whether the order of the tubes, reagent blocks, and reagents conforms to expected index values.

[0136] In other embodiments, operation 694 is performed to generate a notification to alert the user of any error status. If an error status is determined by the load verifier 592, operation 696 is performed to send a command to the sample preparation hardware 122 to cause the sample preparation hardware 122 to act according to the error found.

[0137] 21 is a flow chart illustrating an example method 710 of verifying at least a portion of a sample preparation 588 when a sample preparation instrument 104 is initiating a procedure to prepare one or more samples. In one embodiment, the method 710 is operated by the initiation verifier 594 shown in FIG. 17. In this embodiment, the method 710 includes operations 712, 714, 716, 718, 720, and 722.

[0138] An operation 712 is performed to define the relevant portions of the sample preparation 588 based on the currently active sample preparation procedure.

[0139] In some embodiments, any combination of one or more of operations 714, 716, and 718 can be performed. Operation 714 can be performed to check for space in the waste container 575. For example, the start-up verifier 594 can be operable to check the remaining space in the waste container 575 by using information obtained by a float sensor. Operation 716 can be performed to check the remaining supply of the sample preparation consumables 92. For example, the start-up verifier 594 can be operable to check the remaining supply volume in the diluent reagent container 576 by using information obtained by a float sensor. Operation 718 can be performed to check the remaining amount of reaction plate wells available in the reaction station 554.

[0140] In other embodiments, operation 720 is performed to generate a notification to alert a user of any error status. If an error status is determined by the activation verifier 594, operation 722 is performed to send a command to the sample preparation hardware 122 to cause the sample preparation hardware 122 to act in accordance with the error found.

[0141] 22 is a flow chart illustrating an exemplary method 740 of predictively validating at least a portion of a sample preparation 588. In one embodiment, the method 740 is operated by the predictive validator 596 shown in FIG. 17. In this embodiment, the method 740 includes operations 742, 744, 746, 748, 750, and 752.

[0142] An operation 742 is performed to define the relevant portions of the sample preparation 588 based on sample preparation procedures that are currently running or scheduled to be run.

[0143] In some embodiments, any combination of one or more of operations 744, 746, and 748 may be performed. Operation 744 may be performed to predictively check for space in waste container 575 in light of procedures currently running or scheduled to be started. For example, prediction verifier 596 is operable to use a computer executable algorithm and information obtained by a float sensor in waste container 575 to predict the remaining space after currently running and scheduled procedures are completed.

[0144] An operation 746 can be performed to predictively check the remaining supply of sample preparation consumables 92. For example, the prediction verifier 596 is operable to use a computer-executable algorithm and information obtained by a float sensor in the diluent reagent container 576 to predict the volume of the remaining supply after currently active and scheduled procedures are completed.

[0145] Operation 748 can be performed using a computer executable algorithm and information obtained by the sensors to predictively check the remaining quantity of available reaction plate wells in the reaction station 554 after currently active and scheduled procedures are completed.

[0146] In another embodiment, operation 750 is performed to generate a notification to alert a user of any error status. Once an error status is determined by the prediction verifier 596, operation 752 is performed to send a command to the sample preparation hardware 122 to cause the sample preparation hardware 122 to act in accordance with the found error.

[0147] 23 is a schematic diagram illustrating an example configuration of a probe 560 in a transfer station 558 for use with a reaction plate well in a reaction station 554. In some embodiments, the sample preparation instrument 104 operates to transfer a sample from, for example, an input station 562 or a cell washer 566 to a reaction plate well in the reaction station 554.

[0148] In other embodiments, when sample is to be transferred to more than one well, the sample preparation instrument 104 operates to aspirate the sum of all volumes required per well in one aspiration. The sample preparation instrument 104 then operates to dispense the individual volumes into the wells. For example, when 100 microliters of sample are required in each of four wells in the reaction station 554, the probe 560 will aspirate 400 microliters plus some additional adjustment volume. The probe 560 operates to discard a small amount of the adjustment volume at the probe wash station 573. The probe 560 then operates to move the reaction station 554 and add 100 microliters to the first well, 100 microliters to the second well, 100 microliters to the third well, and 100 microliters to the fourth well.

[0149] 23, the reaction station 554 includes 48 wells 770, numbered 1-48, as shown. When transferring samples, the sample preparation computer 118 operates to control the probe 560 to move in a pattern as shown by arrow 772. For example, the probe 560 is configured to sequentially transfer the sample to fill wells 770 numbered 1-48.

[0150] When transferring samples to multiple wells according to the pattern illustrated by Fig. 23, a small droplet at the tip of one of the probes 560 may fall while the probe is traveling across another well that contains or is planned to contain a different sample. As a result, the droplet will contaminate that different sample. Therefore, a different pattern of moving the probe 560 is desirable to reduce cross-contamination between different samples in the wells of the reaction station 554.

[0151] 24 is a schematic diagram illustrating another exemplary configuration of a probe 560 in a transfer station 558 for use with reaction plate wells in a reaction station 554. In this illustrated embodiment, the sample preparation computer 118 operates to control the probe 560 to move in a pattern as illustrated by arrows 774. For example, the probe 560 is configured to transfer samples to fill wells 770 in the order of numbers 1, 7, 13, 19, 25, 31, 37, 43, 44, 38, 32...4, 5, 11, 17, 23, 29, 35, 41, 47, 48, 42, 36, 30, 24, 18, 12, and 6. The serpentine pattern as illustrated by arrows 774 is operable to cause the probe 560 to progress through wells containing the same sample. As a result, cross-contamination from one sample to another is mitigated. The serpentine pattern is not implemented solely for sample transfer. All specimens, samples, and reagents are configured to be transferred in this serpentine pattern to wells in the reaction station 554. By not treating sample transfer as a special case, the software complexity of the sample preparation software 124 can be reduced.

[0152] In some embodiments, the serpentine pattern generator 590 operates to generate the serpentine pattern illustrated in FIG.

[0153] In other embodiments, after transferring the sample, the probe 560 is configured to proceed to a probe washing station 573, illustrated in FIG. 15, to be washed.

[0154] FIG. 25 is a schematic diagram depicting a portion of the sample preparation hardware 122 in the vicinity of a probe washing station 573 , which contains a probe washing module 800 .

[0155] 26 is a close-up view depicting the probe washing module 800. The probe washing module 800 includes a trough for receiving unused sample or reagent fluid dispensed from several probes, and sheath or wash fluid dispensed from the probes to clean the inner surfaces of the probes. Fluid in the trough is drawn by a pump through an outlet port at the bottom of the trough and delivered to a bulk waste container outside of the instrument.

[0156] In some embodiments, the probe washing module 800 also includes one or more wells adjacent to the valleys for washing the exterior surface of the probe. The probe is lowered into one or more wells and filled with sheath or washing solution from the probe. This dispensed sheath or washing fluid overflows into the valleys and is then pumped out to a bulk waste container. The flow of fluid into the wells during the dispense aids in washing the exterior surface. In this illustrated example, the probe washing module 800 includes three wells for washing a three-channel probe.

[0157] In other embodiments, the valley of the probe washing module 800 includes an internal chamber with a level sensing device, such as a float valve, that acts as a safety shut-off valve to prevent dispensed sheath or washing fluid from overflowing onto the instrument deck if there is a flow blockage between the probe washing module 800 and the bulk waste reservoir.

[0158] The present disclosure should be understood to include (by way of illustration and not by way of limitation) the subject matter set forth in the following numbered appendices:

[0159] Appendix 1. A panel design system, comprising: A computing device; A panel designer software, comprising: Generate sample preparation specifications, Have sample preparation specifications verified; and a Panel Designer software, which is executable as follows: A panel design system comprising:

[0160] Appendix 2. The panel design system of Appendix 1, wherein the panel designer software is further executable to output the sample preparation specification to a file.

[0161] Appendix 3. A panel validation method comprising: Defining a user input specification; comparing the user input specifications to validation criteria; determining that the user input specification does not comply with the validation criteria; generating at least one notification; and generating and outputting a sample preparation specification; A panel validation method comprising:

[0162] Clause 4. The panel validation method of clause 3, wherein the user input specifications include white blood cell range specifications and reagent specifications.

[0163] Appendix 5. checking the first data for at least one upper WBC concentration limit; or checking the second data for the at least one sample volume; The panel validation method of any one of claims 3-4, further comprising any combination of one or more of the following:

[0164] Appendix 6. highlighting at least a portion of the first data and the second data, the first data and the portion of the second data being determined to contain at least an error; Display information about the error, or Enumerating errors in messages, The panel validation method of claim 5, further comprising any combination of one or more of the following:

[0165] Appendix 7. checking first data for at least one reagent name; checking second data for at least one reagent volume; checking a third data for at least one incubation duration; or checking fourth data for at least one resuspension option; The panel validation method of any one of claims 3-6, further comprising any combination of one or more of the following:

[0166] Appendix 8. highlighting at least a portion of the first data, the second data, the third data, and the fourth data, where the portion of the data has been determined to contain at least an error; Display information about the error, or Enumerating errors in messages, The panel validation method of claim 7, further comprising any combination of one or more of the following:

[0167] Appendix 9. A sample preparation device comprising sample preparation hardware and sample preparation software, the sample preparation software providing the sample preparation device with: Receive sample preparation specifications; Define sample preparation based at least on the sample preparation specification; Verify sample preparation, generating a prepared sample based on the sample preparation; The sample preparation hardware is executable by a computer, such as a sample preparation instrument.

[0168] Addendum 10. The sample preparation software further controls the sample preparation instrument to: 10. The sample preparation instrument of claim 9, wherein the sample preparation instrument is executable to cause validation of an error status of a sample preparation specification.

[0169] Appendix 11. A sample preparation method, comprising: receiving a sample preparation specification; defining a sample preparation based at least on a sample preparation specification; Comparing sample preparation with sample preparation validation standards; Determining that the sample preparation is not in compliance with the sample preparation validation criteria; generating at least one notification; and Sending at least one command to the sample preparation hardware; A method comprising:

[0170] Appendix 12. Checking the error status of the sample preparation specification; checking first data for at least one white blood cell concentration; checking a first status of at least one sample preparation consumable; or checking a second status of the sample preparation hardware; 12. The sample preparation method of claim 11, further comprising any combination of one or more of the following:

[0171] Appendix 13. causing at least one notification to occur; or sending at least one command to the sample preparation hardware; 13. The sample preparation method of any one of claims 11 or 12, further comprising any combination of one or more of the following:

[0172] Addendum 14. A sample preparation method according to any of Addendums 11-13, wherein the sample preparation specification is received by the sample preparation instrument via a data transfer system.

[0173] Clause 15. The sample preparation method of any one of clauses 11-14, further comprising preparing the sample using a sample preparation consumable.

[0174] Addendum 16. The sample preparation method of any one of Addendums 11-15, wherein the sample preparation specifications are defined by input from an operator.

[0175] Appendix 17. The sample preparation method of Appendix 12, wherein the error status is indicated by a flag variable, the value of which may be "true" or "false".

[0176] Addendum 18. The sample preparation method of any one of Addendums 11-17, wherein the sample preparation specification includes a hash code.

[0177] Appendix 19. A sample preparation method as described in Appendix 18, wherein the hash code is used to verify that no unauthorized modifications have been made to the sample preparation specifications.

[0178] Addendum 20. The sample preparation method of Addendum 14, wherein sending at least one command to the sample preparation hardware causes the sample preparation hardware to alter the operation of the sample preparation instrument.

[0179] Clause 21. The sample preparation method of clause 20, wherein sending at least one command to the sample preparation hardware causes the sample preparation hardware to be disabled from performing sample preparation.

[0180] Addendum 22. The sample preparation method of any one of Addendums 11-21, further comprising displaying an icon indicating an error on the sample preparation error status indicator.

[0181] Addendum 23. The sample preparation method of any one of Addendums 11-22, further comprising displaying a sample preparation error window containing information about errors in the sample preparation.

[0182] Addendum 24. The sample preparation method of any one of Addendums 11-23, wherein comparing the sample preparation to the sample preparation validation criteria includes checking the white blood cell concentration in the sample preparation against a user-input WBC range in the sample preparation specifications.

[0183] Appendix 25. The sample preparation method of Appendix 15, wherein comparing the sample preparation to a sample preparation validation standard includes checking for the presence and expiration date of a sample preparation consumable.

[0184] Addendum 26. A sample analysis system, comprising: a panel design system that generates a sample preparation specification; a sample preparation instrument for preparing the sample using a sample preparation specification to generate a prepared sample; a sample analyzer configured to analyze the prepared sample; at least one verifier configured to verify operation of the sample analysis system; A sample analysis system comprising:

[0185] Addendum 27. A sample analysis system, comprising: A panel design system according to claim 1; A sample preparation device according to claim 9; A sample analysis system comprising:

[0186] Clause 28. The sample analysis system of clause 27, further comprising a sample analyzer configured to analyze a prepared sample generated by the sample preparation instrument.

[0187] Clause 29. The sample analysis system of clause 28, wherein the sample analyzer is a flow cytometer.

[0188] Addendum 30. A sample analysis system according to any one of Addendums 28-29, wherein the sample analyzer is a hematology analyzer.

[0189] Addendum 31. A method comprising: A panel validation method as described in Appendix 3; A sample preparation method according to claim 11; A method comprising:

[0190] Addendum 32. A non-transitory computer readable storage medium of a sample analysis system, the computer readable storage medium storing data instructions that, when executed by a processing device, cause the sample analysis system to perform the operations described in any one of Addendums 3-8, 11-25, or 31.

[0191] Addendum 33. A panel design system, the panel design system comparing a user input specification to a validation criterion and generating a notification when the user input specification does not comply with the validation criterion.

[0192] Addendum 34. The panel design system of Addendum 33, wherein the notification is selected from highlighting a field of the user input specification with a color-coded indicator, displaying an information box based on a pointer being positioned over a corresponding data field, and displaying an error message.

[0193] Addendum 35. A sample preparation apparatus that evaluates a sample preparation using a sample preparation specification and generates a notification in response to detecting an error.

[0194] Addendum 36. The sample preparation device of Addendum 35, wherein detecting the error is detected based on predicted operation of the sample preparation device using a sample preparation specification and a current status of the sample preparation device.

[0195] The various embodiments described above are provided by way of example only and should not be construed as limiting the claims appended hereto. Those skilled in the art will readily recognize various modifications and changes that may be made without following the exemplary embodiments and applications illustrated and described herein and without departing from the true spirit and scope of the following claims.

Claims

1. 1. A sample preparation method comprising the steps of: receiving a sample preparation specification; defining a sample preparation based on at least said sample preparation specification; comparing said sample preparation to a sample preparation validation standard; determining that the sample preparation does not comply with the sample preparation validation standard; generating at least one notification; sending at least one command to the sample preparation hardware; A method comprising:

2. checking the error status of said sample preparation specification; checking first data for at least one white blood cell concentration; checking a first status of at least one sample preparation consumable; or Checking the secondary status of the sample preparation hardware 2. The sample preparation method of claim 1, further comprising any combination of one or more of the following:

3. generating at least one notification; or Sending at least one command to the sample preparation hardware.

3. The sample preparation method of claim 1, further comprising any combination of one or more of the following:

4. The sample preparation method according to any one of claims 1-2, wherein the sample preparation specification is received by the sample preparation instrument via a data transfer system.

5. The sample preparation method of any one of claims 1-2, further comprising preparing the sample using a sample preparation consumable.

6. The sample preparation method of any one of claims 1-2, wherein the sample preparation specification is defined by input from an operator.

7. The sample preparation method of claim 2 , wherein the error status is indicated by a flag variable having a value that can be "true" or "false."

8. The sample preparation method of claim 1 , wherein the sample preparation specification includes a hash code.

9. 9. The sample preparation method of claim 8, wherein the hash code is used to verify that no unauthorized modifications have been made to the sample preparation specification.

10. The sample preparation method of claim 4 , wherein sending the at least one command to the sample preparation hardware causes the sample preparation hardware to alter an operation of the sample preparation instrument.

11. 11. The sample preparation method of claim 10, wherein sending the at least one command to the sample preparation hardware causes the sample preparation hardware to be disabled from performing sample preparation.

12. The sample preparation method of claim 1 , further comprising displaying an icon indicating the error on the sample preparation error status indicator.

13. The sample preparation method of any one of claims 1-2, further comprising displaying a sample preparation error window containing information about errors in the sample preparation.

14. The sample preparation method of any one of claims 1-2, wherein comparing the sample preparation with the sample preparation validation criteria includes checking the white blood cell concentration in the sample preparation against a user-input WBC range in the sample preparation specification.

15. The sample preparation method of claim 5 , wherein comparing the sample preparation to the sample preparation validation criteria includes checking the presence and expiration date of the sample preparation consumable.