- Org
- MDAndersonPS
- Type
- RFP
- Title
- Whole Slide Imaging Devices and Service
- Number
- MS-A-01707-RFP
- Source
- MD_ANDERSON
- Status
- Open
- Event Id
- 1399402
- Open Str
- 7/23/2026, 4:45 PM CDT
- Pdf Text
- 23 July 2026
Whole Slide Imaging Devices and Service
RFP for Whole Slide Imaging Scanners and Related Services that optimize department workflow and allow for the
transformation of work to a digital first workflow, across numerous use cases.
23 July 2026
Released 7/23/2026, 4:30 PM CDT Type Request for Proposal
Open 7/23/2026, 4:45 PM CDT Number MS-A-01707-RFP
Close 8/24/2026, 2:00 PM CDT Currency US Dollar
Sealed Until 8/24/2026, 2:00 PM CDT
23 July 2026
Contacts
Sheila Vershier
SVershier@mdanderson.org
Phone +1 346-834-4412
23 July 2026
Commodity Codes
Commodity Code Description
41100000 Laboratory and scientific equipment
42261500 Pathology dissection instruments and supplies
43211711 Scanners
23 July 202623 July 202623 July 202623 July 202623 July 202623 July 202623 July 202623 July 2026
Request for Proposal (RFP) for Whole Slide scanners and related services services that optimize the Division of Pathology
and Laboratory Medicine Department workflow and allow for the transformation of work to a digital first workflow,
prioritized across numerous use cases described in the Scope of Work.
Description
Required to View Event
Prerequisites Required to Enter Bid
There are no Prerequisites added to this event.
23 July 202623 July 202623 July 202623 July 202623 July 202623 July 202623 July 2026
Buyer Attachments
1. About MD Anderson
2. Facts and History
3. General Information
4. References
23 July 202623 July 202623 July 202623 July 202623 July 202623 July 2026
Questions Required Questions
Group 1.1: Facts & History
Instructions:
1.1.1
WARNING: To answer this question, you will be navigating away from this page to the
"Buyer Attachments" section of this event. Be sure that you have saved all previous
answers by clicking on the "Save Progress" button before navigating away from this
page.
<\p>
1) Please download and review the MD Anderson's Facts & History under the "Buyer
Attachments" section. The "Buyer Attachments" section can be located on the menu of
contents to the left.
<\p>
2) When complete reviewing, you can return to this page and acknowledge that you
have read it.
<\p>
Group 1.2: About MD Anderson
Instructions:
1.2.1
WARNING: To answer this question, you will be navigating away from this page to the
"Buyer Attachments" section of this event. Be sure that you have saved all previous
answers by clicking on the "Save Progress" button before navigating away from this
page.
<\p>
1) Please download and review About MD Anderson under the "Buyer Attachments"
section. The "Buyer Attachments" section can be located on the menu of contents to
the left.
<\p>
2) When complete reviewing, you can return to this page and acknowledge that you
have read it.
<\p>
Group 2.1: Addendums
Instructions:
2.1.1
This page contains any new information about the RFP after the published date. If there
are any changes to the RFP, it will be documented here. If you receive an e-mail or an
online notification (if logged into MD Anderson Sourcing Director) with the subject the
line "The Sourcing Event is Amended", please visit this page for any important changes
to the event.
Group 3.1: Scope of Work
Instructions:
3.1.1 Please download and review Scope of Work. After reviewing, acknowledge that you
have read it.
Group 4.1: General Information
Instructions:
4.1.1
WARNING: To answer this question, you will be navigating away from this page to the
"Buyer Attachments" section of this event. Be sure that you have saved all previous
answers by clicking on the "Save Progress" button before navigating away from this
page. <\p>
Please download and review the General Information. After reviewing, acknowledge
that you have read it.
Group 4.2: Point-of-Contact
Instructions:
4.2.1
The Owner designates the following person, as its representative and Point-of-Contact
for this RFP. Respondents shall restrict all contact with the Owner and direct all
questions regarding this RFP, including questions regarding terms and conditions, to
the Point-of-Contact person: Sheila Vershier - Sourcing Specialist,
svershier@mdanderson.org. Address: MD Anderson Cancer Center, 7007 Bertner
Ave., Houston, Texas 77030-3907 - Note: All communication should be through the MD
Anderson Sourcing Director Q&A area.
Group 4.3: Pre-Proposal Meeting
Instructions:
23 July 202623 July 202623 July 202623 July 202623 July 2026
4.3.1
A Pre-Proposal Meeting will be held at the time and location described:
DATE: Tuesday, August 4, 2026, at 2:00 PM (CST). LOCATION: Zoom Meeting
(details below). This will be the only opportunity for potential respondents to meet and
ask questions directly from the users before submitting a Proposal. Attendance at the
Pre-Proposal Meeting is "highly recommended". Suppliers will need to RSVP no later
than Monday, August 3, 2026, at 4:00 PM (CST), to svershier@mdanderson.org.
Suppliers are limited to no more than two (2) representatives per company.
UNAUTHORIZED USE OF RECORDING DEVICES: "All video and audio recordings,
including any AI or bot note-taking, of any meetings and/or presentations are prohibited
by MD Anderson. Join Zoom Meeting:
https://mdacc.zoom.us/j/99368799362?pwd=h4elksbHTQrnCWTOjVCbVDRq5zaERw.
1 Meeting ID: 993 6879 9362 Password: 619781
Dial: US: +1 346 248 7799 or +1 253 215 8782 or +1 669 900 6833 or + 877 853 5257
(Toll Free) or 888 475 4499 (Toll Free)
Group 4.4: Disclosure of Interested Parties Mandated by House Bill 1295
Instructions:
4.4.1
MD Anderson must comply with the Disclosure of Interested Parties mandated by
House Bill 1295 and as implemented by the Texas Ethics Commission. Before MD
Anderson may execute a contract exceeding $1M, the Supplier(s) with which MD
Anderson is contracting must submit a completed Form 1295 before or concurrent with
Supplier submission of the signed contract to MD Anderson. For more information,
please use the following link: https://www.ethics.state.tx.us/filinginfo/1295/
Group 4.5: Disclosure of Interested Parties Mandated Senate Bill 475
Instructions:
4.5.1 Please read and review the attached Disclosure of Interested Parties Mandated Senate
Bill 475. Upon completion please acknowledge.
Group 4.6: Public Information Act (PIA)
Instructions:
4.6.1
All information, documentation, and other material submitted in response to this RFP
solicitation is considered non-confidential and/or non-proprietary and is subject to public
disclosure under the Texas Public Information Act (Texas Government Code, Chapter
552.001, et seq.) after the agreement is executed. MD Anderson strictly complies with
all statutes, court decisions, and opinions of the Texas Attorney General with respect to
disclosure of RFP information.
Group 4.7: Best Value
Instructions:
4.7.1
MD Anderson may select the Proposal(s) that offers the "Best Value" for the institution
based on the published selection criteria, its evaluation ranking, and the terms of Texas
Government Code 2155.074.
MD Anderson may first attempt to negotiate a contract with the selected Supplier(s).
MD Anderson may also discuss with the selected Supplier(s) options for a scope or
time and price change modification.
If MD Anderson and/or its governing Board(s) are unable to reach a contract with the
selected Supplier(s) in a timely manner, MD Anderson may formally end negotiations
with that Supplier(s) and proceed to the next "Best Value" Supplier(s) in order of the
selection ranking until a contract is reached or all Proposals are rejected.
Group 4.8: Historically Underutilized Business Submittal Requirements
Instructions:
4.8.1
It is the policy of The University of Texas System, and each of it component institutions,
to promote and encourage contracting and subcontracting opportunities for Historically
Underutilized Businesses (HUB) in all contracts. Accordingly, MD Anderson has
adopted the Rider 104-HUB Subcontracting Plan, Policy on Utilization of Historically
Underutilized Businesses. This Policy applies to all contracts with an expected
(cumulative) value of $100,000 or more. If MD Anderson determines that
subcontracting opportunities are probable, then a HUB Subcontracting Plan is a
required element of the Proposal. Failure to submit a required HUB Subcontracting
Plan will result in rejection of the Proposal.
Group 4.9: HUB Statement of Probability
Instructions:
4.9.1
MD Anderson has determined that subcontracting opportunities are probable in
connection with this procurement solicitation; therefore, a HUB Subcontracting Plan
(HSP) is required as part of your Proposal. Each RFP Respondent shall develop and
administer an HUB Subcontracting Plan as part of the Proposal in accordance with MD
Anderson's Policy on Utilization of Historically Underutilized Businesses (HUB) and
Rider 104-HUB Subcontracting Plan.
23 July 202623 July 202623 July 202623 July 202623 July 2026
Group 4.10: Type of Contract
Instructions:
4.10.1
Any contract resulting from this solicitation will be governed by MD Anderson's
Standard Terms and Conditions referenced in the Summary Agreement attached to this
RFP.
The work associated with this RFP will be awarded as a contract to the Supplier(s)
offering the "Best Value" to MD Anderson.
Group 4.11: Selection Criteria
Instructions:
4.11.1
The successful Supplier(s) selected by MD Anderson, in accordance with the
requirements and specifications set forth in this RFP, will be the Supplier(s) which is
most advantageous to MD Anderson. MD Anderson's committee members, comprised
of key personnel as well as Supply Chain professionals, will evaluate and score
approved Proposals.
Group 4.12: MD Anderson's Reservation of Rights
Instructions:
4.12.1
MD Anderson may evaluate the Proposals based on the anticipated completion of all or
any portion of the RFP. MD Anderson reserves the right to divide the RFP into multiple
parts, to reject any and all Proposals and re-solicit for new Proposals, or to reject any
and all Proposals and temporarily or permanently abandon the RFP. MD Anderson
makes no representations, written or oral, that will enter into any form of agreement
with Supplier(s) for this RFP. No such representation is intended or should be
construed by the issuance of this RFP.
Group 4.13: Obligation
Instructions:
4.13.1
Neither the transmission of this RFP to a prospective Supplier(s), nor the acceptance of
a reply, implies any obligation or commitment by MD Anderson to enter into any
contract or undertake any financial obligations with respect to this RFP. After evaluation
of all Proposals, MD Anderson intends to conduct negotiations with the Supplier(s)
considered best qualified and "Best Valued" to meet its requirements. MD Anderson
reserves the right to reject any or all proposals whenever such actions are in its best
interest.
Group 4.14: No Reimbursement for Costs
Instructions:
4.14.1 Supplier(s) acknowledges and accepts that any cost incurred from the Supplier(s)
participation in this RFP process shall be at the sole risk and responsibility of the
Supplier(s). Supplier(s) submit Proposals at their own risk and expense.
Group 4.15: Clarification and Interpretation
Instructions:
4.15.1
Any clarifications or interpretations of this RFP that materially affect or change its
requirements will be issued by MD Anderson as an Addendum.
It is the responsibility of all Supplier(s) to obtain this information in a timely manner. All
such Addenda will be due prior to the RFP Close Date.
Addenda may be issued by the RFP Point-of-Contact via the SciQuest Sourcing
Director Q&A Board or in the Addendum section of this RFP.
All communication specific to this RFP shall be exchanged within the SciQuest tool.
Group 4.16: Certain Proposals and Contracts Prohibited
Instructions:
4.16.1
Under Section 2155.004, Texas Government Code, a state agency may not accept a
Proposal or award a contract that includes proposed financial participation by a person
with received compensation from the agency to participate in preparing the
specifications or request for Proposal on which the Proposal or contract is based.
All Supplier(s) must certify their eligibility by acknowledging the following statement:
"Under Section 2155.004, Government Code, Supplier(s) certifies that the individual or
business entity named in this RFP or contract is not ineligible to receive the specified
contract and acknowledges that this contract may be terminated and payment withheld
if this certification is inaccurate.
Group 4.17: Certain Proposals and Contracts Prohibited (cont...)
Instructions:
23 July 202623 July 202623 July 202623 July 202623 July 2026
4.17.1
If a state agency determines that an individual or business entity holding a state
contract was ineligible to have the contract, yet accepted the award as described
above, the state agency may immediately terminate the contract without further
obligation to the Supplier(s). This does not create a cause of action to contest a
Proposal or award of a state contract.
Group 4.18: Acceptance or Rejection of Proposal
Instructions:
4.18.1
This RFP is not an offer to contract. Acceptance of a Proposal neither commits MD
Anderson to award a contract to any RFP Respondent, nor limits MD Anderson's rights
to negotiate terms in its best interest. MD Anderson reserves the right to accept or
reject any or all Proposals in part or whole. MD Anderson reserves the right to request
clarification on responses, omissions, or claims made in the RFP. MD Anderson further
reserves the right to request modification to a Supplier(s) Proposal in order to provide
the optimum solution for strategic team planning.
Respondents submitting a Proposal do so with the understanding that MD Anderson
reserves the right to select one or more "Supplier(s) of choice" based solely on their
RFP response or to evaluate one or more Supplier(s) via additional interviews, site
visits, reference checks, and other evaluations.
MD Anderson will notify Suppliers of the results when final decisions have been made.
Group 4.19: Electronic Information and Technology (EIT)
Instructions:
4.19.1
Any acquisition considered EIT as defined by Section 508 (36 CFR Part 1194) requires
the submission of a completed Voluntary Accessible Product Template so that can MD
Anderson can ascertain conformance with the applicable EIT standards developed by
the U.S. Access Board. MD Anderson reserves the right to perform real-world testing of
a Supplier's product or service in order to validate claim regarding Section 508
conformance.
In order to facilitate this testing, Supplier(s) shall, upon request, provide MD Anderson a
copy of the product being considered for purchase for a period of at least 30 calendar
days. The version of the product being provided for testing purposes must be
equivalent in functionality and features to the commercial version that is under
consideration for purchase.
MD Anderson, at its sole discretion, will determine the level of conformance with
Section 508 on all products being reviewed.
Group 4.20: Submission of Proposals
Instructions:
4.20.1
MD Anderson is to receive all Supplier(s) Proposals by the RFP close date
communicated within the SciQuest Sourcing Director tool.
Proposals not received within the specified time frame, and prior to the RFP close date
and time, will not be accepted. Supplier(s) are urged not to wait until the last minute to
submit their final Proposal.
Proposals and final HUB Plans submitted via telephone, fax, or electronic mail (email)
will be rejected. Only those submitted via this tool will be accepted.
Respondents must provide a response to all "REQUIRED" questions or the system will
not accept the submission.
Group 4.21: Group Purchasing
Instructions:
4.21.1
MD Anderson is an institution of System which consists of nine academic and six health
institutions. Texas law authorizes institutions of higher education (defined by Section
61.003, Education Code) to use the group purchasing procurement method (ref.
Sections 51.9335, 73.115 and 74.008, Education Code).
With this, if an Agreement results from this competitive procurement method, the RFP
Respondent acknowledges that additional Texas institutions of higher education may
procure from the RFP Respondent and/or Contractor the goods and services set forth
in this RFP/Agreement on the same terms and conditions attached herein by entering
into a separate contract with RFP Respondent/Contractor, or by concluding an
appropriate addendum to the Agreement.
Group 4.22: Group Purchasing (cont...)
Instructions:
23 July 202623 July 202623 July 202623 July 202623 July 2026
4.22.1
It is understood that:
(I) Unless specifically stated otherwise, any volume of goods or services stated in the
final Agreement reflects only goods and/or services to be purchased by MD Anderson
and does not include potential purchases by other System institutions, and
(II) Each System institution is a financially separate entity and will be solely responsible
for its own commitments to Contractor.
Group 5.1:
Instructions:
5.1.1 Please read and review the attached Summary Agreement. Upon completion, please
acknowledge.
5.1.2 Please explain any exceptions to Summary Agreement above by uploading your
redlines for this document in a MSWord. If you have no exceptions, please upload the
document with the words "NO EXCEPTIONS" written on it.
5.1.3 Please read and review Rider 107 - Travel Policy. Upon completion, please
acknowledge
5.1.4 Please explain any exceptions to Rider 107 - Travel Policy by uploading your redlines
for this document in a MSWord. If you have no exceptions, please upload the document
with the words "NO EXCEPTIONS" written on it.
5.1.5 Please read and review Rider 111 - Business Associates Agreement. Upon completion,
please acknowledge
5.1.6 Please explain any exceptions to Rider 111 - Business Associates Agreement by
uploading your redlines for this document in a MSWord. If you have no exceptions,
please upload the document with the words "NO EXCEPTIONS" written on it.
5.1.7 Please read and review Rider 114 - Network Connection. Upon completion, please
acknowledge
5.1.8 Please explain any exceptions to Rider 114 - Network Connections by uploading your
redlines for this document in a MSWord. If you have no exceptions, please upload the
document with the words "NO EXCEPTIONS" written on it.
5.1.9 Please read and review Rider 114 - Supply Chain User Acknowledgement. Upon
completion, please acknowledge
5.1.10
Please explain any exceptions to Rider 114 - Supply Chain User Acknowledgement by
uploading your redlines for this document in a MSWord. If you have no exceptions,
please upload the document with the words "NO EXCEPTIONS" written on it.
5.1.11 Please read and review Rider 116 - Invoice Payment Requirements. Upon completion,
please acknowledge.
5.1.12 Please explain any exceptions to Rider 116 - Invoice Payment Requirements by
uploading your redlines for this document in a MSWord. If you have no exceptions,
please upload the document with the words "NO EXCEPTIONS" written on it.
5.1.13
WARNING: To answer this question, you will be navigating away from this page to the
"Buyer Attachments" section of this event. Be sure that you have saved all previous
answers by clicking on the "Save Progress" button before navigating away from this
page. <\p>
1) Please download and follow the instructions on the attached Rider 118 Information
Security under the "Buyer Attachments" section. The "Buyer Attachments" section can
be located on the menu of contents to the left. <\p>
2) Return to this page to upload the completed Rider 118 Information Security<\p>
5.1.14 Please download the attached Rider 121 - TX-RAMP INFORMATION FORM. After
reviewing, please complete and upload the document.
5.1.15 Please read and review RIDER 200 -KEY PERFORMANCE INDICATOR(S). Upon
completion, please acknowledge.
5.1.16 Please explain any exceptions to RIDER 200 -KEY PERFORMANCE INDICATOR(S)
by uploading your redlines for this document in a MSWord. If you have no exceptions,
please upload the document with the words "NO EXCEPTIONS" written on it.
5.1.17 Please download the attached EO-GA-48 Supplier Certification Form. After reviewing,
please complete and upload your signed document.
Group 6.1:
Instructions:
6.1.1 Please download the attached Supplier Rider Attestation Form. After reviewing, please
complete and upload your signed acknowledgement.
23 July 202623 July 202623 July 202623 July 202623 July 2026
Group 7.1:
Instructions:
7.1.1
Please download, complete all applicable pages, "sign and date" the attached Rider
104 HUB Subcontracting Plan.
NOTE: A NEW Rider 104 "must be" submitted with each new RFP.
ALL submissions to this RFP without a properly completed/attached HUB Plan will be
“REJECTED” and will not be eligible for consideration by MD Anderson.
7.1.2 Please download and follow the instructions on the attached Rider 104 HUB
Subcontracting Plan Tip Sheet. This Tip Sheet is designed to aid in the completion of
Rider 104.
Group 8.1: Collaboration & Innovation
Instructions:
8.1.1 Does your company have experience in implementing and managing your proposed
solution into a large complex organization with multiple locations? If so, please describe
this experience.
8.1.2 State any challenges your company experienced implementing hardware in similar
environments and describe how you overcame them?
8.1.3 What percentage of your company's revenue is devoted to Research and
Development?
8.1.4
What is your 2–5 year roadmap for whole slide imaging scanners? For each planned
capability added or improvement, indicate whether if it will be available as a software
upgrade to current hardware, will require a hardware upgrade purchasable separately,
or require a full system replacement. Identify any changes that may affect DICOM
output format, Sectra PACS compatibility, LIS integration, and describe how existing
customers will be supported through these transitions.
8.1.5 What major technological advancements (e.g., imaging, automation, Robotics, AI
integration) are you prioritizing?
8.1.6 Do you offer early access programs, beta testing, or co-development opportunities?
8.1.7 Please share a timeline (even approximate) for key roadmap milestones?
Group 8.2: Delivery and Lead Time
Instructions:
8.2.1 Do you have local dealers/ distributors to supplement the M&O needs?
8.2.2 How does your company deal with unexpected product shortages?
8.2.3 Please describe your company's procedure for notifying MD Anderson in advance of
any partial orders or shipping delays.
8.2.4 What communication methods does your company typically use for notification?
8.2.5 What is the on-time delivery performance for major project shipments?
8.2.6 Do you have a courier communication/ tracking system in place?
8.2.7 Please describe your company’s standard delivery criteria.
8.2.8 Is your company able to provide 24/7 services?
8.2.9 Does your company have a process for order tracking? If yes, please describe it.
8.2.10 Is your company able to accommodate MD Anderson's delivery schedule?
Group 8.3: Quality, Health and Safety
Instructions:
8.3.1 Provide scanner dimensions, weight, and footprint for each model in the proposed
solution, including space needed around/ between instruments.
8.3.2 Describe the bench, table, or floor requirements for each model in the proposed
solution.
8.3.3 List the power, electrical, and UPS requirements for each model in the proposed
solution.
8.3.4
Specify environmental operating conditions for each model in the proposed solution,
including temperature, humidity, and vibration sensitivity. Specify whether scanners
require vibration isolation. Describe observed performance degradation if the scanner is
placed near automated stainers, centrifuges, or other equipment that generate
mechanical vibration.
8.3.5 Specify heat dissipation requirements, and thermal output under peak scanning
conditions. Specify whether supplemental cooling or a dedicated HVAC system is
required. 23 July 202623 July 202623 July 202623 July 202623 July 2026
8.3.6 Specify the minimum ceiling height required and overhead clearance for slide loading,
lid opening, or service.
8.3.7 Does the scanner require dedicated plumbing, drain access, or compressed air? If oil
immersion is supported, describe the oil reservoir capacity, refill procedure, and
drainage and waste management requirements.
8.3.8 Describe installation and relocation requirements for each model in the proposed
solution.
8.3.9 Describe the expected noise levels produced by each device, in decibels (dB).
8.3.10 State the slide capacity and supported glass slide dimensions.
8.3.11 Describe the scanning mechanism (i.e. Line scanning, tiled, etc.) and lens capability
(20x, 40x, 60x, 80x, 100x)?
8.3.12 Provide the scanning speed, throughput, and automation capabilities. If applicable,
provide both 15x15 standard times and "real" world scan throughput times.
8.3.13 Detail resolution, focus, Z-stacking, and tissue detection mechanisms.
8.3.14 Describe barcode, metadata capture, and supported output formats.
8.3.15 Can slides without barcodes be scanned? How are these handled?
8.3.16 Describe the slide transport and loading mechanism.
8.3.17 Does the scanner support direct loading from staining racks or cover slipper output?
8.3.18 Are slide "racks" proprietary, or standard based on common vendor sizes, and what are
replacement costs?
8.3.19 Describe how the scanner detects and handles broken or cracked slides, skewed
coverslips, slide jams, etc. Can the system isolate the affected slide without interrupting
the remainder of the batch? Are there audible alerts? Email Alerts? On-Device Alerts?
8.3.20 What type of light source is used (LED, halogen, etc.)? If available, list the color
temperature and color rendering index (CRI) for the light source.
8.3.21 What is the expected stability and lifetime of the illumination system?
8.3.22 Does the scanner support un-coverslipped slides for scanning.
8.3.23 Is there "on-device" automated image quality assessment during scanning?
8.3.24 List metrics evaluated automatically (focus, contrast, tissue detection) prior to, during
and immediately after scanning, prior to unloading of the slides.
8.3.25 How closely does the scanner reproduce true stain colors (e.g., H&E, IHC
chromogens)?
8.3.26 Do you provide quantitative metrics (e.g., ΔE, color error relative to reference targets)?
8.3.27 Is white balance fixed, adaptive, or user-configurable?
8.3.28 What calibration standards are used (e.g., NIST-traceable targets, IT8 color targets,
custom pathology slides)?
8.3.29 How often is recalibration required in routine use?
8.3.30 Does the system include automated or user-triggered calibration routines?
8.3.31 How does the system handle color variation across different tissue types or staining
intensities?
8.3.32 How do you compensate for illumination aging or drift?
8.3.33 Is illumination uniform across the entire field of view?
8.3.34 What happens if calibration drifts and how is this detected and corrected?
8.3.35 How do you ensure color consistency across multiple scanners of the same model?
Different Models? Do you provide tools for color harmonization?
8.3.36 Can images from different scanners (same or different models) be normalized to the
same color profile?
8.3.37 Which standardized color spaces are supported (e.g., sRGB, Adobe RGB, ICC
profiles)?
8.3.38 Are ICC profiles embedded in the output images?
8.3.39 Does the scanner apply any color correction, normalization, or enhancement
automatically?
8.3.40 Can color correction algorithms be turned off or adjusted?
8.3.41 Are stain normalization algorithms available for downstream analysis?
8.3.42 Is raw (uncompressed) image data accessible?
8.3.43 What QC procedures are recommended for ongoing color validation?
8.3.44 Do you provide calibration slides or QC kits?
23 July 202623 July 202623 July 202623 July 202623 July 2026
8.3.45 Can the system generate quality control (QC) reports or logs tracking color
performance over time?
8.3.46 Are there built-in alerts if color drift or illumination inconsistency is detected?
8.3.47 Can slides or batches be dynamically prioritized?
8.3.48 Can scanning order adapt based on case priority or tissue size?
8.3.49 Is there support for cross scanner coordination for parallel or multi-core support to
prioritize scanning?
8.3.50 Does throughput scale linearly with capacity growth?
8.3.51 Does your system include Robotic Rack or Slide handling?
8.3.52 Does your solution support using a 3rd party robotics vendor for slide and rack
handling?
8.3.53 Briefly detail your experience utilizing robotics for slides and/or racks.
8.3.54 How are scanning protocols assigned (e.g., by device, run/Batch, Rack, and/or slide)?
8.3.55 Can different scanning protocols be assigned automatically/dynamically based on
Laboratory Information System (LIS) order type or barcode without requiring operator
intervention at time of loading? If not, can it be done manually by an operator?
8.3.56 Is the control software on the device or on a separate control pc/server?
8.3.57 Can control software control more than one scanner at a time? If so, how many?
8.3.58 If control software can control multiple scanners, does it automate load balancing
between scanners?
8.3.59 What is the native capture format for the scanner? If it is not DICOM, please describe
your DICOM conversion process?
8.3.60 Provide the DICOM Conformance Statement for each scanner proposed.
8.3.61 Please provide 1-3 deidentified whole slide images in DICOM for testing.
8.3.62 Specify how accession numbers, case/specimen/block/slide identifiers, stain, tissue
type, magnification, and barcode data are represented in DICOM attributes.
8.3.63 Proprietary dependency: If native output is proprietary, identify the conversion step,
conversion licensing, expected lag, failure handling, and validation of responsibility.
8.3.64 Does your scanner include a Basic Offset Table in the DICOM file?
8.3.65 Has DICOM C-STORE been validated in a clinical setting with Sectra PACS or another
PACS?
8.3.66 Does your scanner support the Integrating the Healthcare Enterprise Digital Pathology
Image Acquisition (IHE DPIA) profile for Imaging Work Order Step (IWOS)?
8.3.67 Please describe specific network requirements for connectivity, bandwidth
requirements, encryption, or wireless network capabilities for the scanner.
8.3.68 Describe interfaces supported by each scanner for integration with the LIS (HL7, FHIR,
XML, JSON, etc.).
8.3.69 Is LIS Metadata ingested by barcode only, barcode trigger to an interface, or via an
interface only?
8.3.70 Detail LIS integration standards supported (HL7/FHIR) with scanners or control
software.
8.3.71 If the scanner connectivity is lost to the IMS, can the scanner continue to capture and
store images locally until the connection is restored?
8.3.72 Describe scanner control software updates and deployment processes. Are updates
pushed automatically, or does the laboratory control timing? What is the rollback
procedure if an update causes a system issue?
8.3.73 How often are scanner firmware updates deployed?
8.3.74 Does the scanner require a static IP address?
8.3.75 Can the scanner be remotely accessed by in-house IT personnel?
8.3.76 State FDA regulatory status and cleared indications. Provide the 510(k) number,
cleared intended use statement, and specific stain types and specimen types covered
by the clearance if the device has FDA clearance.
8.3.77 Please provide a summary of the validation studies supporting FDA clearance,
including analytical, clinical, software, and performance validation data relevant to the
proposed device.
8.3.78 Describe inspection-ready audit and quality systems. Describe the format, retention
period, and exportability of logs for scan errors, QC outcomes, operator actions, and
configuration changes.
23 July 202623 July 202623 July 202623 July 202623 July 2026
8.3.79 If the scanner proposed is not covered by an existing FDA clearance, what support is
provided to the laboratory for an LDT-framework validation? Describe any validation
templates, reference datasets, or assistance programs available.
8.3.80 State the FDA clearance status of the scanner specifically for the clinical interpretation
of peripheral blood smears. If the device is not FDA cleared, describe any validation
support that may be provided for implementing the scanner as a LDT workflow.
8.3.81 Does the scanner support dry scanning and/or oil immersion scanning for bone marrow
aspirate smears? If oil-immersion, describe the automated oil delivery, cleaning and
other aspects that need technologist intervention.
8.3.82 What levels of magnification (objectives) are supported and validated: 40x vs. 60x (if
dry), 50x vs 100x (if oil immersion)?
8.3.83
Does the system support capture of the entire marrow smear or selected ROIs?
Describe how the system identifies and scans the diagnostically important areas of a
bone marrow aspirate smear (particle-rich areas, cellular streaming, etc.). How does
the system detect marrow spicules (what criteria are used: size, density, contrast)?
8.3.84 For aparticulate/hemodilute/hypocellular smears, thick smears, how does the system
select areas of interest and focal plane? Does the system support automatic flagging of
sub-optimal quality slides, initiate rescanning or needs manual intervention?
8.3.85 Does the scanner capture a macroscopic overview of the full slide in addition to
scanned ROIs?
8.3.86 Does the system support z-stack acquisition for marrow aspirate smears and touch
imprints? Specify the number of planes, space between the planes, impact on scan
time, and additional storage requirements?
8.3.87 Outline recommended maintenance procedures for scanners. Please include specific
instructions for oil immersion runs, if supported, and objective cleaning if required
(peripheral bloods, or Hematopathology specific use cases).
8.3.88 Describe image retention, retrieval, audit trail, user access control, and
connectivity/integration with Sectra for long term storage.
8.3.89 What is the minimum and maximum objective supported for Wright-Giemsa-stained
bone marrow aspirate smears, crush preparations and touch imprints?
8.3.90 Does the scanner support scanning of coverslipped or noncoverslipped aspirate
smears and touch imprints?
8.3.91 Does the scanner support scanning of cytochemical stains: Prussian blue (iron),
myeloperoxidase and butyrate esterase-stained slides?
8.3.92 Can the scanner accept slides prepared directly from bone marrow laboratory stainer
system workflow? Provide a list of compatible slide labeling/stainers/cover slippers,
slide racks, etc.
8.3.93
Does the system support capture of the entire marrow smear or selected ROIs?
Describe how the system identifies and scans the diagnostically important areas of a
bone marrow aspirate smear (particle-rich areas, cellular streaming etc.). How does the
system detect marrow spicules (what criteria are used: size, density, contrast)?
8.3.94 Per-slide scan time for a bone marrow aspirate smear and touch imprint at the available
magnifications (40x and 60X dry; 50x and 100x oil)?
8.3.95 What is the actual hands-on time for techs per slide and per batch during scanning?
What is the process for failed scans, jams, focus failures, insufficient tissue detection,
oil delivery issues (if available)?
8.3.96 Does the system support z-stack acquisition for marrow aspirate smears and touch
imprints? Specify the number of planes, space between the planes, impact on scan
time, additional storage requirements.
8.3.97 For STAT cases, does the system support prioritization of urgent bone marrow cases
by bypassing ongoing scanning (if already in progress)? What is the process of loading
a STAT slide mid-run?
8.3.98 How to link the images from a case to the matched hemepath BM case in Epic beaker
and also to the corresponding CBC/diff data, and ongoing orders in the flow cytometry,
cytogenetics, molecular labs?
8.3.99 Does the system allow retrieval of the images from prior bone marrow cases from the
same patient for comparison?
8.3.100
When a slide is loaded for scanning, describe how the system checks for a prior scan
of the same accession or slide identifier before initiating acquisition. Specify whether
this check queries the local scan queue only, the IMS, or both. Describe what action the
system takes when a duplicate is detected: does it skip scanning automatically, require
an override, or proceed regardless? For unattended overnight batch runs where
operator intervention is not immediate, describe how duplicate detection failures are
flagged and how the resulting duplicate images are managed in the IMS.
23 July 202623 July 202623 July 202623 July 202623 July 2026
8.3.101
Does the platform allow annotation of regions that contributed to the diagnosis
(increased blasts, abnormal cells like promonocytes, dysplastic cells, hemophagocytic
histiocytes, metastatic tumor cell aggregates for second review or for recording
purposes? Is there an audit trail?
8.3.102 Can the system support semi-automated BM differential count? Describe the workflow
and performance characteristics, validation/publication data, supported cell categories,
pathologist correction step, audit trail, and limitations.
8.3.103 Is remote review supported for centralized hematopathology interpretation of cases
scanned in a remote facility?
8.3.104 Describe image-specific QC metrics for bone marrow smears (focus, stain quality, cell
detection, oil adequacy, and artifact detection).
8.3.105 Describe user-facing QC flags for scanning functions such as barcode mismatch,
broken slide, failed/incomplete scans, oil delivery failure, etc.
8.3.106 Describe preventive and routine maintenance procedure for slide cleaning, objective
cleaning, oil system check, etc.
8.3.107 What is the FDA clearance status for clinical interpretation of bone marrow? If not, is
validation support available to implement as LDT?
8.3.108 Describe storage requirements for bone marrow WSI files for high dry and oil scans
with and without z-stacking.
8.3.109 If your viewer uses a proprietary image format, do you have a converter to export the
image as a dicom image for long term storage in Sectra?
8.3.110 What is the per slide scan time for a peripheral smear at 40x, 50x oil, and 60x dry?
8.3.111 Does the system support capture of the whole slide, including feathered edges?
8.3.112 Does the scanner capture a macro-overview of the full slide image in addition to the
high-magnification scan?
8.3.113 Are you able to integrate with Caresphere and the CellaVision DI60 platform?
8.3.114 Can DI60 cell classifications be overlaid onto the WSI image?
8.3.115 Does the scanner support non cover slipped slides?
8.3.116 What is the per slide scan time for a body fluid cytospin at 40x, 50x oil, and 60x dry?
8.3.117 Does z-stack acquisition affect scan time? If so, provide scan time with and without
z-stack enabled.
8.3.118 What is the per slide file size for each PB scanned at 40x, 50x, and 60x?
8.3.119 What is the per slide file size for each CSF/BF slide scanned at 40x, 50x, and 60x?
Provide file size estimates both with z-stack and without.
8.3.120 For hypocellular cytospin slides, describe how the system handles cells outside of the
focus tolerance. Are these flagged for rescan automatically?
8.3.121 Describe scanner performance for cytospin preparations, including how the system
detects and focuses on the area of interest. What is the minimum detectable tissue
area for automated tissue finding?
Group 8.4: Service and Support
Instructions:
8.4.1 Can your company service MD Anderson and all of its satellites and affiliates?
8.4.2 Will your company assign a senior account manager to manage the overall contractual
relationship?
8.4.3 What is the average response time for an account manager(s) to respond to initial
requests?
8.4.4 Will your company offer an onsite representative for service to MD Anderson at no
cost? If no, please explain.
8.4.5 Please detail your company's problem resolution process for customer compla
- Close Str
- 8/24/2026, 2:00 PM CDT
- Contact Name
- Sheila Vershier
- Description
- RFP for Whole Slide Imaging Scanners and Related Services that optimize department workflow and allow for the transformation of work to a digital first workflow, across numerous use cases.
- Contact Email
- svershier@mdanderson.org
- Sci Docs Fetched
- Yes
