Abstract
Keywords
Introduction
Inhibitory concentration at half maximum (IC50) refers to the concentration of a drug that inhibits 50% of the activity between baseline and maximum after a specific exposure time. 1 Effective concentration at half maximum (EC50) refers to the concentration of a drug that induces 50% of the response between baseline and maximum after a specific exposure time. 1 IC50 and EC50 are commonly used pharmacological parameters to evaluate the potency of drugs.2–7 In the drug development process, these assays are usually conducted in the early discovery stage for compound screening and triage.
In principle, determining the IC50/EC50 values is a straightforward process: Obtain a dose–response curve for the drug, then calculate the IC50 or EC50 value. To obtain the dose–response curve, the typical IC50/EC50 assay process usually involves the following: First, design a preparation scheme for the spiking solutions and the final matrix solutions; then, decreasing concentration levels of the drug-spiking solutions are prepared in neat solvent such as DMSO and then spiked into blank matrix. Afterward, aliquots of the matrix solutions are incubated at specific temperatures for a specific amount of time. At the end of incubation, samples are processed and/or extracted, then followed by analytical measurement of the response. Dose and response data are plugged into software such as GraphPad Prism (GraphPad Software, San Diego, CA) to calculate the IC50/EC50 values one compound at a time. To increase throughput in dedicated high-throughput screening (HTS) labs, these assays usually follow certain very specific procedures and sometimes even use specific hardware. 8
IC50/EC50 assays do not fall in the traditional realm of typical mass spectrometry (MS)-centric bioanalytical labs because they are screening assays. However, with the widespread adoption of molecular biomarkers in drug research, more and more MS labs have become involved in biomarker-related work,9–11 including efficacy biomarker assays that can be used directly for IC50/EC50 determination. Thus, the duties of HTS labs and MS bioanalytical labs are overlapping in regard to IC50/EC50 assays. For IC50/EC50 assays, MS-centric bioanalytical/biomarker labs differ from dedicated HTS labs in terms of equipment, methodology, and procedure. For example, HTS labs routinely screen a large library of compounds against a few fixed targets using fixed procedures, whereas bioanalytical/biomarker labs are often requested to screen a much smaller set of compounds at a time, but the biomarker and its assay may change from run to run. Therefore, smaller screening size and large variability of assay details are key differentiators of IC50/EC50 assays conducted in bioanalytical/biomarker labs.
What bioanalytical/biomarker labs do have in common with HTS labs, though, as far as IC50/EC50 assays are concerned, is the throughput requirement. Undoubtedly, IC50/EC50 assays’ wet chemistry work, if done manually, is repetitive, tedious, and error prone and should be automated. In the HTS field, there have been many reports of using new technologies, including automation, to increase IC50/EC50 assay throughput.12–17 From a MS-centric bioanalytical/biomarker lab’s point of view, for each individual compound, there is nothing in the IC50/EC50 experimental procedure that cannot be automated with current state-of-the-art bioanalytical automated sample preparation systems.18,19 However the challenge lies in the overall production throughput. Existing bioanalytical sample preparation automation systems18,19 can only handle discrete or cassette compound analysis, whereas in a typical IC50/EC50 batch, there are multiple (sometimes 20–30) compounds to screen. In this situation, running an automated procedure for one compound at a time is not efficient. To increase IC50/EC50 assay throughput, parallel processing of multiple compounds is essential. Computation of spiking and the matrix solution concentrations and preparation scheme should be automated, as well as the actual preparation and sample extraction procedure. IC50/EC50 value computation, graphing, and reporting need to be automated as well. In this article, we report our integrated, automation-assisted system that achieves all of the above. For ease of reference, we named the system IC50/EC50 automation platform, or ICECAP. ICECAP is composed of a Windows graphical user interface (GUI) program and a Hamilton script program executing on the Hamilton (Reno, NV) MicroLab STAR liquid handling robot.
ICECAP Windows GUI
The ICECAP GUI serves the following functions: collect user input, validate user input, compute entire liquid handling scheme, output Hamilton run file and sample analysis sequence file, compute IC50/EC50 values when data come back, and generate experimental report. The GUI was developed using Microsoft (Redmond, WA) Visual Basic .NET 2010.
Experimental Design Input
Figure 1 shows the Assay Parameters page of the GUI. The number of compounds and time points of the experiment in the Study group box would affect user input in the second GUI page (vide infra). Taking into consideration the robot hardware limitations, plate layout design, and later on sample analysis time (vide infra), the maximum number of compounds for each experiment is set at 32. The Assay Solutions group box tells the program the sample extraction solutions to use and the processing order. Because IC50/EC50 assays are screening assays, the system is intentionally designed to be capable of handling only simple sample extraction procedures such as protein precipitation and liquid–liquid extraction. All selections of solutions are populated in the Solution Processing Order group box, which allows users the full flexibility of arranging the solution processing order, including shake, pause, vortex, and centrifuge steps, at will. (Vortex and centrifuge steps are done offline due to hardware limitations.) The above mechanism effectively encapsulates the vast majority of IC50/EC50 sample extraction procedures. Even if a particular sample extraction procedure goes beyond the capability of this system, the samples can be taken offline for additional processing and analysis. The results could still be taken back for data extraction and analysis (vide infra). In the Mixing group box, spiking solution and matrix solution preparation mixing are separated because their different solution viscosities may require different degrees of mixing.

Graphical User Interface Assay Parameters Input.
Figure 2 shows the second GUI input page, where more experimental details could be specified. The number of time points specified in the first GUI page becomes editable in groups of five in the Time Points group box. The wells corresponding to the number of compounds specified in the first GUI page are activated for input in the Compound Stock Plate Map group. Compound names input here are used in the Hamilton run file, sample sequence list, and final report. In the Matrix Solution Preparation group box, the volume percentage of spiking solution in the final matrix solution (p value) is an important user input parameter that would affect the solution preparation scheme computation. The spiking volume percentage is limited to be between 0.5% and 5%. The user-specifiable number of matrix solution concentration levels ranges from 6 to 10. The lower limit of 6 is the very conservative minimum data points needed to capture a fully developed IC50/EC50 curve. 20 The upper limit of 10 is due to the 96-well plate layout (vide infra) limitation. One of three ways of specifying the matrix solution concentrations needs to be selected. In the first way, the highest matrix solution concentration and the dilution factor between any two concentration levels are specified. This is the most commonly used approach because in typical IC50/EC50 dose–response curves, the dose (x-axis) is presented in logarithm scale. A fixed dilution factor between any two concentration levels produces evenly spaced x values on the logarithm scale. In the second way, the lowest and the highest concentrations are set. Values in between are computed automatically, and the dilution factor is shown as a read-only value. This approach also produces evenly spaced x values in the dose–response curve. In the third way, input fields corresponding to the number of concentration levels are activated for user input of any concentration levels desirable. These matrix solution concentration input options offer maximum flexibility and encompass all practical IC50/EC50 dose preparation needs. In the Email Notifications group box, users have the option to have the system send out notification emails when a run needs operator attention.

Graphical User Interface Assay Details Input.
Internal Computation
Experimental design input by users only sets the framework and goal of the experiment. To actually carry out the experiment, many more experimental details need to be worked out before starting. ICECAP uses a much more comprehensive parameters list in addition to user input to describe the experiment ( Table 1 ). In Table 1 , parameters shown in bold are user input; parameters in italic could be either user input or calculated. The rest are used for internal computation.
Parameters Used for ICECAP Internal Computation.
ICECAP, IC50/EC50 automation platform.
The internal computation process starts with validation of user input ( Fig. 3 , section II). For example, ICECAP has an empirical global minimum liquid handling volume of 5 µL (using 10 µL tips) and maximum liquid handling volume of 1000 µL (using 1000 µL tips). Therefore, the maximum single-step dilution factor is 200. ICECAP allows one intermediate solution. Thus, the maximum dilution ICECAP can achieve from weighing stock solution to highest concentration spiking solution is 200 × 200 = 40,000. From spiking solutions to matrix solutions, there is another maximum dilution factor of 200. So the overall maximum dilution factor from weighing stock solution to highest concentration matrix stock is 8,000,000. The ICECAP GUI enforces the rule.

Algorithm Flowchart.
After all validation is done, all target matrix solution concentrations are computed first using the user-specified approach ( Fig. 2 ). Then, using the user input value p, corresponding spiking solution concentrations are computed. The empirical global minimum liquid handling volume 5 µL is 0.5% of 1000 µL, which is why the lowest allowable p value is set at 0.5% (vide supra). With both matrix and spiking solution concentrations known, the matrix solution preparation scheme is then computed, taking into consideration the global minimum liquid handling volume, safety volume (to avoid liquid handling errors), and total matrix solution volume needed for all time point experiments. Next is the spiking solution preparation scheme computation, which starts at the lowest concentration level and progressively up. In each cycle, the volume needed for actual use is combined with the safety volume needed to avoid liquid handling errors when computing the volume needed coming from the next higher concentration solution. When reaching the highest concentration spiking solution, if an intermediate solution is needed, its preparation scheme is computed as well. All user input and computation results are stored in a Microsoft Access database *.mdb file, which has four tables in it: an assay parameters table ( Fig. 4 ); a calculations table of all computation results; a matrix solutions table of concentrations, dilution factors, and preparation volumes; and a spiking solutions table with detailed information on spiking solution preparation, such as source and target lab ware and positions, preparation volume, and so on. A sample list is then exported into a Microsoft Excel file ( Fig. 5 ) for sample analysis purposes.

Hamilton Run File Assay Parameters Table.

Sample Analysis Sequence List.
ICECAP Hamilton Script Program
The ICECAP Hamilton script (
Fig. 3
, Section III) was developed in Venus 2.0 and executes on the Hamilton MicroLab STAR robot to carry out spiking solution preparations, matrix solution preparations, and sample extractions after incubation. After system initialization and taking the Access database file, it prompts the user to decide the program flow: whether to start a new run from the beginning or to resume a run at specific time points (
Fig. 6
). If it’s a new run, the program starts from spiking solution preparation, followed by matrix solution preparation. There are 2×4 integrated shakers on the MicroLab STAR extended deck: 4 for spiking solutions and 4 for matrix solutions (
Fig. 7
). Considering the deck space needed for other solutions, tips, and reservoirs, and the fact that both spiking and matrix solutions preparations need shaking, this is about the maximum number of shakers that could be accommodated on a single robot without further sacrificing plate space (i.e., four shakers take up five 96-well plate spaces and are wider than a normal plate carrier). Each plate can handle eight compounds up to 10 concentration levels (
Fig. 8
). Therefore, ICECAP can process up to 32 compounds per run. If time 0 sample processing is requested along with the new run, immediately after matrix solutions preparation, the Hamilton program will pause and prompt the user to set up the deck before time 0 sample extraction would take place (

Hamilton Program Flow Selection.

Hamilton Deck Layout for Spiking and Matrix Solution Preparations.

Typical Spiking and Matrix Solution Plate Map.
Experimental
ICECAP testing follows this process: First, the GUI program was tested for enforcement of business and validation rules, and correct output of the Access file tables and the sample analysis sequence list. Then, the Hamilton script was tested in simulation mode, the trace file of which was closely examined to ensure the absence of programming logic errors. On the Hamilton deck, the first liquid tested was tap water dyed with food color to check that dilution was happening, followed by real blank solvents tests to ensure liquid classes were appropriate such that no dripping was occurring during liquid transfers.
When all of the above tests passed successfully, the system was used in a series of real studies to perform IC50 experiments, and the results were compared with manually obtained ones. The background of the real studies involves autotaxin, an enzyme that catalyzes lysophosphatidylcholine (LPC) to lysophosphatidic acid (LPA) conversion.21–25 Compounds were screened to evaluate their autotaxin enzyme inhibition potency (IC50 values). Experimental endpoint was the measurement of biomarker LPA (20:4 and 18:1) concentrations in rat plasma.
Materials
Compounds 1 through 4 and compound internal standard (IS) were internally synthesized. 18:3 LPA was from Echelon Biosciences (Salt Lake City, UT); 17:0 LPA was from Avanti Polar Lipids Inc. (Alabaster, AL); ammonium formate was from Sigma-Aldrich (St. Louis, MO); pooled rat plasma (lots RAT225586 and RAT225588) were from Bioreclamation (Westbury, NY); high-performance liquid chromatography (HPLC)-grade methanol and acetonitrile were from Fisher Chemical (Hampton, NH); 99% formic acid was from Acros Organics (Fisher Scientific, Hampton, NH); 2 mL 96-well plates were from Analytical Sales and Services (Pompton Plains, NJ); and 96-head Nalgene polypropylene solvent reservoirs were from Fisher Scientific (Hampton, NH). HPLC columns used were ACE 3.0 µm 50×2.1 mm C18-AR from Mac-Mod Analytical (Chadds Ford, PA), and Atlantis 5.0 µm 50×2.1 mm HILIC Silica from Waters (Milford, MA). Compound mobile phase A was 0.1% formic acid in 95:5 water–acetonitrile; compound mobile phase B was 0.1% formic acid in 50:50 acetonitrile–methanol. LPA mobile phase A was 10 mM ammonium formate in water; LPA mobile phase B was 10 mM ammonium formate in 95:5 acetonitrile–methanol.
Instruments and Liquid Chromatography–Tandem Mass Spectrometry (LC-MS/MS) Methods
The Hamilton MicroLab STAR liquid handling robot was running Venus 2.0 robot control software and was equipped with eight vendor integrated INHECO shakers. Three types of conductive, disposable tips were used: 10 µL and 1 mL tips were in ordinary racks, whereas 300 µL tips were in nested tip racks ( Fig. 7 ).
Quantitative analyses of both compounds and LPA were carried out using the same LC-MS/MS system. The triple quadruple mass spectrometer was Applied Biosystems (Carlsbad, CA) Sciex API 5500 running in ESI+ mode for compounds and ESI− mode for LPAs. The HPLC system used was Shimadzu Prominence LC-20AD XR pumps with SIL-20 AC XR Prominence refrigerated autosampler and rack changer. Prior to running ICECAP experiments, LC-MS/MS methods for compounds 1–4, compound IS, and all LPAs were first manually optimized using neat solutions. MRM transitions for compounds, compound IS, and the LPAs were listed in Table 2 . Compounds quantitation was conducted on the ACE column with the following optimized HPLC gradient: 0.01–0.5 min 40% B; 1.9–2.4 min 95% A; 2.5–3.0 min 40% B; and run time was 3.0 min. LPA analyses were conducted on the Atlantis column with the following optimized HPLC gradient: 0.01–0.5 min 100% B; 1.9–2.4 min 40% A; 2.5–3.0 min 100% B; and run time was 3.0 min. Ion chromatogram peak integrations were carried out with Analyst version 1.6.2.
MRM Transitions for Compounds, IS, and LPAs.
IS, internal standard; LPA, lysophosphatidic acid; MRM, multiple reaction monitoring.
Sample Procedures
ICECAP handles three wet chemistry experimental types: spiking solution preparation, matrix solution preparation, and sample extraction. Spiking solution preparations follow their preparation schemes saved in the Microsoft Access database file and usually use serial dilutions from the concentrated stock, with the help of one possible intermediate solution. Whenever possible, eight-channel parallel processing is used to improve system throughput. Matrix solution preparations also follow the preparation scheme saved in the Microsoft Access database file, but in general are done using the 96 CORE head to boost throughput.
For compounds’ sample extractions in the test experiment, at time zero, 300 µL of IS (100 ng/mL of compound IS in ACN) was added to 50 µL of samples, then capped, vortexed, and centrifuged. 25 µL of supernatant was mixed with 500 µL water; 5 µL was injected for analysis.
ICECAP Workflow and Data Flow
Figure 9 is the workflow and data flow diagram. ICECAP GUI input could be manual (step 1a). To save time, the input could also be saved to a template (step 1b) for later retrieval (step 1c). After saving the Microsoft Access database file (step 2), the Generate LC-MS/MS Run List button on the GUI would be activated, allowing users to save (step 3) a LC-MS/MS run sequence file like the one in Figure 5 . The Access database file is manually input to the ICECAP Hamilton script for execution (step 4). While that is happening, users would use the LC-MS/MS run list to set up the LC-MS/MS analyses batch and the like on the LC-MS/MS system (step 5). After sample extractions are done, the extracted plates are analyzed on the LC-MS/MS (step 6). Ion chromatogram peak integration results are saved in *.txt or *.rdb format (step 7), then fed into the ICECAP GUI (step 8a) along with the original Access database file (step 8b) for nonlinear regression curve fitting, IC50/EC50 values computation, and experimental report generation (step 9).

Workflow and Data Flow.
Results and Discussions
System Performance
ICECAP performance testing was aimed at addressing the following key points: quality of the matrix solution preparation automation, quality of built-in nonlinear regression curve fitting functions, and overall system performance compared to manual experiments (i.e., the correlation between EC50 or IC50 values obtained through ICECAP versus manual experiments).
Matrix solution preparation quality
To test the performance of ICECAP liquid handling functions, time zero matrix samples were aliquot and processed using the compound extraction procedure, and analyzed on the LC-MS/MS for compound concentrations. Eight replicates of manually prepared compound 1 matrix curves were used as standards (STD), and eight replicates of ICECAP prepared matrix samples were used as QCs. Table 3 is a compilation of the STD and QC accuracy and precision. Note that the 30 µM samples saturated the MS detector; therefore, their data are not used. These data demonstrate production-quality liquid handling accuracy and precision [19], and are sufficient for IC50/EC50 screening assays.
Comparison of Compound 1 Manual versus Automated Matrix Sample Preparations.
The 30,000 nM data level is not shown because it saturated the MS detector.
CV, coefficient of variation; QC, quality control; STD, standard.
Built-in nonlinear regression curve fitting quality
In a non-high-throughput screening lab, the final IC50/EC50 value is traditionally obtained through a commercial nonlinear regression curve fitting software package such as the GraphPad Prism. Scientists would copy and paste dose and response data into Prism one compound at a time, compute the IC50/EC50 value, then export the value and curve fitting graph into a container file for reporting purposes. Repeated processes like this could easily lead to scientist mental and physical fatigue and error. In ICECAP, this entire process (i.e., getting data, nonlinear curve fitting, and IC50/EC50 value computation, graphing, and reporting) is automated. Figure 10 is the ICECAP report function input form, which takes two files as input. The first is the Microsoft Access file ( Fig. 4 ) of the experiment. The second is the analysis results file. Because Sciex mass spectrometers are our main quantitative analyses instruments and Analyst is their instrument control and data acquisition software, the ICECAP reporting module was coded to be able to read Analyst results files (*.rdb) directly through its application programming interface (API). This eliminates one additional step of copying and pasting, and the potential clerical errors associated with it, and significantly improves data processing throughput (vide infra). To achieve automated data processing, the same mechanism reported in the literature 26 was used to encode or decode sample IDs. All experimental details about any particular sample, such as plate number, compound name, concentration, matrix, time point, well position on the 96-well plate, time stamp, and that experiment’s global unique identifier (GUID), were encoded into that sample’s name ( Fig. 5 ). The Microsoft Access file is also tagged with the same GUID ( Fig. 4 ). The ICECAP reporting algorithm reads the Access file (*.mdb) and the results file (e.g., Analyst *.rdb file), and would only proceed when their respective GUIDs match ( Fig. 3 , Section VI). This mechanism ensures correct reporting of experimental results each time. After decoding the sample IDs and analyses results into data table, ICECAP passes data to the Microsoft Excel Solver engine to conduct nonlinear regression curve fitting 27 using either the four-parameter logistic (or Sigmoidal) equation (4-PL): 28
where y is the response, x is the dose, B is the bottom of the curve, T is the top of the curve, H is the Hill’s slope, and C is the IC50 or EC50 value; or the five-parameter logistic equation (5-PL): 29
where A is the asymmetry factor. 5-PL reduces to 4-PL when A = 1. On the reporting GUI (
Fig. 10
), users can choose one of the above two curve fitting equations, along with response type (peak area or peak area ratio) and graph y-axis type (absolute or relative
30
). The “no dose response” (NDR) cutoff is a user-specified value of the percentage change of response from the top to the bottom of the curve, at less than which the experiment would be reported as NDR.
27
The outlier cutoff is a user-defined value of the difference between experimental data and curve fitting data, beyond which the data point would be marked in the data table as an outlier.
27
Curve fitting results and graphs are passed into Crystal Reports for report generation (
Fig. 3
, Section IV). A complete ICECAP report consists of assay information, the extraction procedure (

Graphical User Interface Report Input.
To compare the ICECAP built-in nonlinear regression curve fitting algorithm results with those obtained through GraphPad Prism, one ICECAP experiment’s dose–response data set of eight replicates of compound 1 was processed in two ways respectively (both using the 4-PL equation): through ICECAP’s Analyst API and built-in nonlinear regression curve fitting algorithm, as well as manually through copying and pasting data into GraphPad Prism 6.0.1. Table 4 is the comparison of the results. As demonstrated in the table, the percentage difference of the IC50 values obtained through ICECAP and GraphPad Prism is small enough that ICECAP’s built-in nonlinear regression curve fitting algorithm can function as a replacement of GraphPad Prism.
ICECAP versus GraphPad Prism 4-PL Algorithm Comparison Using Compound 1 Robot Run Data.
CV, coefficient of variation; ICECAP, IC50/EC50 automation platform; LPA, lysophosphatidic acid.
Manual vs. ICECAP comparison
To test the overall performance of ICECAP versus manual IC50 experiments, the following experiments were conducted: eight replicates of compound 1 were processed automatically through ICECAP and used its built-in data processing algorithm for IC50 values; another eight replicates were processed manually (sample extraction, incubation, and the LC-MS/MS analyses were done in the exact same procedure as the automated ones) and used GraphPad Prism to obtain IC50 values. These two sets of IC50 values were compared in Table 5 . As demonstrated in the table, IC50 values obtained through ICECAP correlate well with manually obtained ones, and so ICECAP is performing as expected.
ICECAP versus Manual Experiment Comparison for Compound 1.
CV, coefficient of variation; ICECAP, IC50/EC50 automation platform; LPA, lysophosphatidic acid.
Messaging
A desired feature of bioanalytical wet chemistry automation is minimum user attendance at the robots. To reduce operator attendance at the robot, the integration of small hardware accessories—for example, capping, vortex, centrifuge, and decapping—into the existing robot platform would be desirable. However, with the current robot hardware, this is still done case by case instead of as the norm. Therefore, even though most of the wet chemistry steps of an assay are automated in existing systems, there would still be sparing offline steps that are not automated and need manual intervention. The timing of these steps during an automated run varies from assay to assay. To free up users as much as possible for other intellectual tasks, system messaging capability is being added into ICECAP to only alert users when the robot needs manual intervention. To achieve this, operators’ email addresses are first collected through either their corporate network login, which is tied to the enterprise active directory, or user input of alternative email addresses (
Fig. 2
, bottom) before the automated run starts. During the execution of robotic scripts, just before each message box pops up prompting users for manual intervention, such as the one shown in
System Flexibility
Several features of ICECAP make it a versatile IC50/EC50 automation platform. First is the flexible input of target matrix solution concentration levels ( Fig. 2 ). In most IC50/EC50 experiments, concentration levels of adjacent doses follow a fixed dilution factor pattern such that the final dose–response semilogarithm plot will have a data set evenly distributed across the x-axis. However, the exact concentration range that would capture the fully developed response curve (determined by the starting concentration and subsequent dilution factors) could vary from compound to compound. This change, if done manually, requires meticulous recalculation of the matrix solution preparation scheme and, throughout time, becomes a burden. Also, there might be times when unevenly distributed doses are desired to capture the top or bottom plateau of the curve. ICECAP’s flexible matrix concentration input capabilities ( Fig. 2 ) make these changes effortless.
Second is the flexible solution processing order. IC50/EC50 sample processing details such as solution type, volume, and order of addition could vary from assay to assay. ICECAP encapsulates all of the above into its algorithm ( Fig. 1 ) and supports unlimited variations of those details.
Third is that sample analysis is not limited to LC-MS/MS only. Because ICECAP outputs encoded sample IDs in sample analysis sequence lists, and decodes and processes quantitative data using those sample IDs, the actual quantitative analysis method does not matter as long as the returned data contain those sample IDs.
Fourth is the experimental resume function ( Fig. 6 ). A large portion of any IC50/EC50 experiment is incubation, which is typically overnight. Even though incubator hardware could be integrated with existing robots, and the incubation step automated, that route was not taken because it was deemed inefficient. Instead, the resume algorithm was implemented to free up the robot for other applications during the long IC50/EC50 incubation period. We believe this is a better use of the capital equipment.
System Throughput Improvement
To gauge ICECAP’s full capacity, a 32-compound run was performed in the 4×8 fashion: each of the four plates consists of eight replicates of the same compound (1–4), respectively ( Fig. 8 ). Manual preparation of the spiking solutions of all four plates, manual spiking into the blank matrix, and the manual sample extraction procedures would take an average bioanalyst at least a full working day (and possibly longer) to complete, in addition to the preparation scheme design. With ICECAP, all of the above was done in less than 2 h, thanks to the eight-channel parallel processing of the compounds’ spiking solution preparation and the 96-well simultaneous handling of spiking and sample extractions ( Fig. 8 ).
In manual IC50/EC50 experiments, copying and pasting the data into Excel for graphing, copying and pasting data into GraphPad Prism for IC50/EC50 value calculation, and putting together everything in a report take our analyst at least 2 min per compound on average, with possibilities for analyst clerical error. For 32 compounds, the manual process would take at least 1 h to finish. In ICECAP, with GUID implementation, direct data retrieval through Analyst API, plus built-in nonlinear regression curve fitting capabilities, running a guaranteed error-free 32-compound report (4-PL nonlinear regression curve fitting, graphing, and reporting) on an ordinary office laptop (Intel Core i5-3320M CPU: 2 cores, 4 logical processors, 2.60 GHz, 4 GB RAM) under Windows 7 Enterprise edition took only 3 min and 23 s.
Conclusions and Future Perspectives
Until commercial turnkey automation solutions are readily and widely available, there are needs, and it is value added to customize general-purpose robots and make them easier to use for targeted applications. While doing so, many labs do piecemeal automation, that is, they automate and perfect one step or a few steps of the workflow to achieve high throughput to the extreme while neglecting the interconnection, the interoperation of those disparate automation silos and pieces, and the usability, which results in poor user experiences. What we have been doing here is to integrate those individual automation pieces into a user-friendly automation solution.
ICECAP provides a general-purpose automation platform for non-high-throughput screening labs when conducting IC50/EC50 assays. Its flexible matrix solution concentration levels designation and concentration values input, flexible solution processing order, automated computation of liquid handling schemes, and automation-assisted parallel processing of wet chemistry procedures can handle the majority of IC50/EC50 assay situations. Its automated data extraction, nonlinear regression curve fitting, and reporting functions greatly improve data-processing efficiency. The combination of wet chemistry automation and data-processing automation capabilities improves IC50/EC50 assay productivity tremendously. Although, strictly speaking, each of the individual automation pieces in ICECAP may not be “new” per se (i.e., they have been published before), the integration of all those approaches and pieces into a general-purpose IC50/EC50 automation platform is new, as far as we know.
Like previous systems,19,26 ICECAP uses a GUI program plus robot script approach to achieve automation, and it separates user input verification, business logic, liquid handling error prevention algorithms, and liquid handling scheme computation from actual liquid handling logic. The GUI program can be seen as the abstraction layer, and the robot script the execution layer. The link between the two layers is a parameters file, which, for all practical purposes, could be Microsoft Access, Excel, or other common file types. This design of separated abstraction and execution layers inherently makes the system’s rapid retargeting onto other robotic platforms possible: As long as a new robot-specific scripting environment supports the above common file types as input, and the said new robot platform has all the equivalent liquid handling functionalities as the original robot the system was developed on, then new robot-specific scripts could be developed relatively quickly following the same modular design as the original robot script. This saves much development resources and time when porting the application to other robotic platforms.
Because IC50/EC50 assays are for screening purposes, current ICECAP sample extraction functionalities were designed to handle simple sample extractions only. This fit-for-purpose approach suits our current needs. However, as more complex biomarker assays are developed, sample handling requirements might change, which might necessitate more advanced sample extraction automation capabilities. ICECAP could certainly be improved in that area.
Another area of improvement would be use of better nonlinear regression curve fitting algorithms. There are commercially available software components with optimized algorithms tailored for nonlinear regression curve fitting purposes. 31 ICECAP could integrate those software components and make nonlinear regression curve fitting even faster.
Finally, if we examine the general approach of ICECAP closely, many of the ICECAP ideas such as flexible spiking solutions preparation through serial dilutions, spiking of compounds into blank matrix, flexible solution processing order, flexible selection of resume time points of experiments, automated data processing, and so on are directly applicable to assorted ADME binding–stability–inhibition screening assays as well, with the help of respective special-purpose lab ware in a 96-well format. This clearly points to algorithm reuse. Conceivably, existing ICECAP core programs could be expanded to include those assay types to form a time point assay suite. That would be yet another class of assays that could be automated on the same robotic liquid handling platform.19,26 If the all-in-one, so-called “bioanalytical wet chemistry kiosk”32,33 were a mountain to be conquered, then we would be another step closer to the pinnacle covered with the ice cap.
Key Terms
Footnotes
Declaration of Conflicting Interests
The authors declared no potential conflicts of interest with respect to the research, authorship, and/or publication of this article.
Funding
The authors received no financial support for the research, authorship, and/or publication of this article.
