2.4.1-A0006_Government Response to Questions_Final.pdf

Attachment 4 U.S. Department of Homeland Security (DHS) Question Template Office of the Acquisition Management (OAQ) Detention, Compliance & Removals (DCR)

500 12th St. SW, Washington, D.C. 20024

QUESTION TEMPLATE

RFP Reference (Sample. PWS Section 5.1) Offeror Questions Government Response

1 N/A Is there any incumbent/recompete or is this a brand-new project? If yes, could you please provide us with their award number or even if the customer bought similar services in the past.

This is a recompete. Current contract number is 70CDCR21D00000003. Incumbent is Valor Network, Inc.

2 N/A Can the Government please clarify whether the successful contractor is required to furnish, lease, and maintain all digital X-ray equipment at the covered IHSC facilities, or whether existing Government-leased/on-site equipment will remain in place and the contractor will primarily be responsible for interpretation, system integration, and support services?

Yes, the successful contractor is required to furnish, lease, and maintain all digital X-ray equipment at the covered IHSC facilities. Existing government-leased or on-site equipment will not be available for contractor use. The contractor is fully responsible for providing, installing, and supporting all necessary digital X-ray equipment as part of their services.

3 N/A If the contractor is responsible for equipment, please advise whether the Government can provide the anticipated number of facilities and digital X-ray systems that will require contractor support under the resulting contract.

See PWS Appendix 1 for facilities.

4 PWS Sec. II; PWS Sec. V.a.viii;

RFP Sec. L.12, Item 5

The solicitation references MiPACS and eClinicalWorks. Please confirm whether the contractor is expected to perform image acquisition, review, interpretation, reporting, and workflow activities within the Government's existing MiPACS/eCW environment, or whether the contractor is required to provide, host, accredit, and operate a separate cloud-based imaging/PACS/teleradiology platform.

Images must be saved in the ICE Azure cloud environment.

IHSC users are required to utilize MiPACS within eCW’s application to access DICOM images. The contractor must ensure that captured digital X-ray images are transmitted to MiPACS for storage and retrieval, and that radiology reports are integrated into IHSC electronic health record.

The contractor will not be required to provide, host, accredit, or operate a separate cloud-based imaging/PACS/teleradiology platform for use by the government. The contractor is expected to perform image acquisition/capture, image review, interpretation, reporting, and workflow activities within eCW. Currently, the government is transferring images from the incumbent contractor's PACS/storage to the government's cloud storage.

The future contractor will be required to continue transferring all images to the government for long-term storage. The government utilizes Apryse MiPACS for image viewing, which is connected to the government's cloud storage. The contractor is expected to continue interfacing with MiPACS for image access and management. The contractor will need their own PACS to view images for interpretation.

5 RFP Sec. L.12, Items 1-2; PWS Sec. V.a.v; PWS Sec. V.a.viii

If the contractor is required to provide a separate imaging/PACS/teleradiology platform, please confirm whether that platform must already possess FedRAMP authorization, Authority to Operate, ICE/DHS approval, or any other agency-specific security authorization at the time of proposal submission, or whether such authorization may be completed after award and prior to operational go-live.

See RFP Section L.15 for instructions relating to FedRAMP.

Also see PWS sections Image Storage and Integration, IT Security Plan, and Contractor IT Security Accreditation; RFP Section H.13; and RFP Section L, Volume II for FedRAMP requirements.

An Authority to Operate (ATO) will need to be completed after award and prior to operational go-live.

The contractor will not be required to provide, host, accredit, or operate a separate cloud-based imaging/PACS/teleradiology platform.

6 RFP Sec. L.12, Items 1-8; RFP Sec. F.2; RFP Sec. L.8

Please clarify which technical, cybersecurity, software, equipment, integration, and vendor-support requirements must be fully documented at the time of proposal submission versus which may be finalized after award and before operational go-live.

Please refer to Section L of the RFP for proposal submission requirements. Items which may be finalized after award are dependent on individual proposal submissions and will be discussed with the awardee after award.

7 RFP Sec. L.12, Items 3 and 6;

PWS Sec. V.a.v; PWS Sec.

V.a.viii; PWS Sec. V.a.x

If the contractor will use or interface with the Government's existing MiPACS/eCW environment, please clarify the contractor's specific cybersecurity responsibilities, including encryption, audit logging, vulnerability monitoring, device tracking, access control, user provisioning, credentialing, and reporting.

All hardware, software, and services provided must be compliant with DHS Security Policy. Reference Information Security Systems Program 4300A version 13.3, Feb 13, 2023.

8 PWS Sec. V.a.viii; PWS Sec.

V.a.ix; RFP Sec. L.12, Item 5

Please confirm whether the Government will provide contractor access, user accounts, workflow permissions, interface specifications, and technical onboarding support for MiPACS/eCW, if performance is expected to occur within or through the Government's existing systems.

The contractor will not be responsible for providing technical or onboarding support for MiPACS or eCW. The contractor will coordinate with ICE/IHSC technical teams to ensure that captured images are stored in the government's cloud, clinical reports with image URLs are available in eCW/EHR, and the image URLs are formatted correctly to ensure images are viewable in MiPACS.

The government will provide the appropriate access and permissions necessary to complete the required integration effort. The contractor shall coordinate with ICE/IHSC technical teams to establish the required interfaces and operational procedures. The contractor remains responsible for its own systems, connectivity, and interfaces necessary to ensure images and metadata are transferred to the government cloud environment; clinical reports and appropriately formatted image URL links are available in the eHR; and images are viewable through MiPACS.

See PWS, Image Storage and Integration and Data Exchanges/Interfaces.

9 RFP Sec. H.3; RFP Sec. L.11; RFP Sec. L.13; PWS Sec. III

Please confirm whether offerors may satisfy cloud hosting, imaging software, fixed X-ray equipment, portable X-ray equipment, local X-ray support, cybersecurity monitoring, and related technical requirements through subcontractors, equipment vendors, software vendors, local service providers, or teaming partners, provided the prime contractor remains responsible for overall contract performance.

Yes, requirements may be satisfied by partners with the understanding that the prime is responsible for overall contract performance and that all hardware, software, and services provided must be compliant with DHS Security Policy (reference Information Security Systems Program 4300A version 13.3, Feb 13, 2023) and the prime contractor is responsible for ensuring that compliance. Additionally, offerors shall note the requirements of Revolutionary Federal Acquisition Regulation Overhaul (RFO) clause 52.219-14 Limitations on Subcontracting.

10 RFP Sec. L.12, Items 4, 7, and 8;

PWS Sec. II; PWS Sec. III

Please confirm whether the Government will accept commercially available fixed and portable X-ray equipment that meets or exceeds the solicitation's stated technical requirements, supported by manufacturer specifications, or whether specific makes/models are required.

No specific make, brand or model is required.

11 RFP Sec. L.12, Items 5, 7, and 8;

PWS Sec. V.a.viii; PWS Sec.

V.a.ix

To the extent any brand-name, system-specific, platform-specific, or manufacturer-specific requirements are intended, please identify the required salient physical, functional, performance, interoperability, cybersecurity, or clinical workflow characteristics that an equivalent solution must meet to be considered acceptable.

There are no brand name requirements. The salient characteristics are outlined throughout the Performance Work Statement (PWS) and RFP.

12 RFP Sec. L.12, Items 4, 7, and 8;

RFP Sec. L.13

Please clarify whether offerors must identify the exact make/model and vendor source for all proposed fixed and portable X-ray equipment in the proposal, or whether equivalent equipment meeting the stated specifications may be finalized after award.

Yes, offerors must identify the exact make, model, and vendor source for all proposed fixed and portable X-ray equipment in their proposal.

13 RFP Sec. L.12, Items 1-8; RFP Sec. L.11; RFP Sec. L.13

Please clarify whether offerors must provide executed vendor commitments, letters of support, teaming agreements, or subcontractor documentation for imaging software, cloud hosting, X-ray equipment, cybersecurity, and local X-ray support at the time of proposal submission.

See revisions to RFP Section L.12 for requirements relating to the X-ray machines. With respect to the IT requirements, it is the responsibility of the offeror to determine the necessary documentation to illustrate compliance.

14 RFP Sec. L.14; RFP Sec. M.10;

Attachment 2

Please confirm whether relevant experience and past performance of proposed subcontractors, teaming partners, consultants, vendors, and key personnel may be submitted and evaluated, provided the proposal clearly identifies the entity or individual that performed the work and explains their role in the proposed team.

As outlined in section L.14 of the RFP, contract references may be submitted from the prime, JV, CTA, subcontractor(s), and predecessor, affiliate, or parent companies. References submitted for consultants, vendors (except for those provided by JV partners, subcontractors, or CTA members), or key personnel will not be considered. See revisions to RFP section L.14.

15 PWS Sec. V.a.viii; PWS Sec.

V.a.ix; RFP Sec. F.2; RFP Sec.

L.13

For transition and continuity planning purposes, please clarify whether there is an existing contractor, provider, technical operator, or Government-furnished system administrator currently supporting the MiPACS/eCW imaging workflow for the requirement described in the solicitation.

Yes, there is an existing contractor currently supporting the MiPACS/eCW imaging workflow for the requirement described in the solicitation.

16 RFP Sec. L.12; RFP Sec. L.13;

PWS Sec. II; PWS Sec. V.a.viii;

PWS Sec. V.a.ix

Please confirm whether the Government will consider alternative technical approaches that meet or exceed the stated performance, security, interoperability, equipment, and clinical workflow requirements, even if the proposed approach uses different commercial tools, vendors, equipment, architecture, or implementation methods than those currently deployed. Please also clarify whether the Government anticipates providing Government-furnished equipment, software access, existing licenses, interface documentation, site-specific workflow information, historical implementation materials, or a defined transition period before operational go-live.

See Section L.13, Technical Approach, if proposing to exceed or add any performance requirements.

See PWS Section VI for a description of Government Furnished Equipment (GFE) and Government Furnished Information

(GFI).

17 General Is there a current incumbent contractor? If so, please provide the contract number

See response to question 1.

18 PWS Sec. viii (Image Storage & Integration); PWS Sec. iv & v (IT Security Plan / Contractor IT Security Accreditation); Sec.

L.12 Items 1–2; Sec. M.7 Criteria 1–2

The PWS (Section viii) requires that image files and interpretation reports “be stored solely in a GSA FedRAMP compliant environment,” and Sections L.12 and M.7 establish FedRAMP authorization of the offeror’s Cloud Service Provider (CSP) and Cloud Service Offering (CSO) as a

The government requires the contractor solution to obtain IT security accreditation per requirements outlined under FISMA, NIST SP 800-37/800-53, and DHS 4300A for systems operated by the contractor for DHS, regardless of location and to support FISMA Certification and Accreditation.

See revisions to RFP Sections L.12 and M.7.

go/no-go requirement. FedRAMP authorization is a designation that applies specifically to cloud service offerings. The same PWS also requires the contractor to obtain IT security accreditation under DHS 4300A for systems “operated by the contractor for DHS, regardless of location” (Sections iv and v) and to support FISMA Certification and Accreditation (C&A), and Experience Discussion Item 1 of Attachment 2 evaluates whether prior contracts required an Authority to Operate (ATO) and how that requirement was met. Will the Government accept an on-premises (non-cloud) contractor solution that receives a DHS/ICE ATO under FISMA, NIST SP 800-37 / 800- 53, and DHS 4300A — including FIPS-validated encryption in transit and continuous monitoring per NIST SP 800-137 — as an equivalent alternative to a FedRAMP-Authorized CSP and CSO? If so, will the Government revise Section L.12 and Section M.7 Criteria 1 and 2 accordingly?

19 Sec. M.6–M.7 (Evaluation Process: Product Offering)

Because Factor 1 (Product Offering) is evaluated strictly on an Acceptable/Unacceptable basis, and failure to meet any single criterion renders the proposal Unacceptable and ineligible for award, please confirm whether an offeror proposing an on-premises solution that cannot furnish a FedRAMP Marketplace listing for a CSP and a CSO would be rated Unacceptable under Criteria 1 and 2 as currently written even where the solution meets DHS 4300A security accreditation and all remaining Product Offering criteria.

See revisions to RFP Sections L.12 and M.7.

20 Sec. H.13 (FedRAMP – Cloud and ‘as-a-Service’); PWS Sec.

viii; Sec. L.12; Sec. M.7

Section H.13 states that its FedRAMP requirements apply “when procuring or considering cloud services” and “when using cloud computing,” which reads as conditioned on the contractor’s use of cloud computing.

PWS Section viii, Section L.12, and Section M.7, however, appear to require a FedRAMP-authorized cloud environment unconditionally. Please reconcile these provisions and confirm whether use of cloud computing is mandatory, or whether a non-cloud architecture that meets the underlying security requirements is permissible.

Use of cloud computing is not mandatory. See revisions to RFP Sections L.12 and M.7.

21 PWS Sec. viii and Sec. ix (Data Exchanges/Interfaces);

Conceptual Architecture (PWS Figures 1–2, p.12–13)

The PWS provides that the contractor’s image storage is short-term (60 days) and that images are “instantaneously transferrable and synced to IHSC’s cloud storage for long-term storage,” and it references Microsoft Azure as the service-provider environment in connection with the conceptual architecture (PWS p.12 and Figure 2). Since long-term storage resides in the Government’s cloud, please clarify whether the FedRAMP-authorization requirement is intended to apply to

(a) the Government’s long-term cloud only, (b) the contractor’s short-term storage and transmission layer, or (c) both. If (b) or (c), will the Government confirm whether an on-premises short-term store with FIPS-validated encrypted transmission and instantaneous, synchronized transfer to IHSC’s Azure cloud would satisfy the requirement?

Image storage and transfer requirements apply to both the government’s cloud and the vendor’s solution, as applicable.

The contractor must maintain short-term image storage for 60 days and immediately transfer images and related metadata to IHSC’s cloud environment for long-term storage.

Both the contractor’s short-term storage environment and the Government cloud environment must meet applicable image-storage and security requirements. Image files and interpretation reports must be stored in a FedRAMP-compliant environment. The contractor must also meet applicable FISMA, NIST, and DHS 4300A requirements and obtain the required security authorization before operational go-live.

An on-premises short-term storage solution is acceptable only if it meets these FedRAMP-compliant storage and security requirements.

See PWS sections Image Storage and Integration, Data Exchanges/Interfaces, IT Security Plan, and Contractor IT Security Accreditation.

22 Sec. L.12 Items 1–2 (FedRAMP Marketplace evidence)

Section L.12 requires evidence from the FedRAMP Marketplace – Products website (e.g., a screenshot) confirming that both the CSP and the CSO are “currently FedRAMP authorized.” Where an offeror hosts its teleradiology application on a FedRAMP-Authorized commercial Infrastructure-as-a-Service (IaaS) but the application itself is not separately listed on the Marketplace, what evidence will the Government accept to satisfy Criterion 2, for example, the IaaS provider’s Marketplace listing together with an agency ATO letter, a Third-Party Assessment Organization (3PAO) assessment, or a System Security Plan (SSP) for the application?

See revisions to RFP section L.12.

23 Sec. L.12 Items 1–2; Sec. M.7 Criteria 1–2

FedRAMP is undergoing structural changes during the proposal and award period, including renaming the “FedRAMP Authorized” designation to “FedRAMP Certified” and retiring the “FedRAMP Ready” designation.

Will the Government accept a FedRAMP Marketplace listing that reflects the new “FedRAMP Certified” (formerly “FedRAMP Authorized”) designation as satisfying Criteria 1 and 2, and will it update the RFP terminology accordingly to avoid ambiguity at evaluation?

See revisions to RFP section L.12.

24 Sec. L.12; Sec. M.7; FAR 11.002;

FAR 52.219-6 (100% Small Business set-aside; NAICS 621512)

This requirement is a total (100%) Small Business set-aside under FAR 52.219-6 (NAICS 621512, $19.0M size standard). Requiring both the CSP and the specific CSO to hold full FedRAMP Authorization (with In- Process and Ready expressly unacceptable) as a pass/fail gate may limit competition, given that FedRAMP authorization typically requires 12–36 months and substantial cost, and relatively few small-business teleradiology offerings are independently FedRAMP Authorized. Consistent with FAR 11.002, will the Government consider any of the following: (a) accepting an equivalent DHS 4300A agency ATO;

(b) accepting a CSO that is “In Process” while hosted on a FedRAMP- Authorized IaaS; or (c) permitting full FedRAMP authorization to be achieved within a defined period after award (for example, by completion of the 120-day transition-in period) rather than at the time of proposal submission?

See revisions to revisions to RFP section L.12.

25 PWS Sec. viii (“only store images in a single location”);

Sec. L.12 Item 5; Sec. M.7 Criterion 5

The PWS requires the contractor to “only store images in a single location” and to integrate with the Government’s Picture Archiving and Communication System (PACS), such as MiPACS, so that the Government does not use the contractor’s PACS for image viewing. Please confirm that an on-premises contractor system that (i) maintains the short-term image store in a single on-premises location, (ii) syncs instantaneously to IHSC’s cloud, and

(iii) presents image URL links to the Government’s PACS viewer over the ICE network would satisfy PWS Section viii, Section L.12 Item 5, and Section M.7 Criterion 5.

The contractor must maintain short-term image storage, transfer images and related data to IHSC cloud storage immediately, and provide image links so government users can view images through the government PACS rather than the contractor’s PACS.

An on-premises short-term storage solution may be used only if it meets all PWS security and storage requirements, including use of a FedRAMP-compliant environment for image files and interpretation reports

An on-premises contractor system that (i) maintains the short-term image store in a single on-premises location, (ii) syncs instantaneously to IHSC’s cloud, and (iii) presents image URL links to the Government’s PACS viewer over the ICE network and that can demonstrate adherence to requirements outlined under FISMA, NIST SP 800-37/800-53, and DHS 4300A for systems operated by the contractor for DHS, regardless of location, in order to obtain an authority to operate before operational go-live and to support FISMA Certification and Accreditation would satisfy PWS Section viii, Section L.12 Item 5, and Section M.7 Criterion 5.

26 Sec. L.12 Item 3; Sec. M.7 Criterion 3 (FIPS encryption)

Criterion 3 requires that all data transmissions be encrypted using FIPS 140-2 validated modules (or NSA Type 1/2 encryption). NIST’s CMVP will move all FIPS 140-2 validations to the Historical List on September 21, 2026, within the base period of performance of this contract, after which federal agencies are advised not to include FIPS 140-2 modules in new procurements, and FIPS 140-3 is the current standard.

Will the Government confirm that FIPS 140-3 validated modules satisfy Criterion 3, and will it update the RFP language to reference FIPS 140-2 or 140-3 validated modules to avoid an evaluation ambiguity created by the sunset date?

See revisions to RFP section L.12 relating to FIPS.

27 Sec. L.10 (Page Limitations);

Sec. L.12 (Volume II); Sec. L.13 (Volume III)

Volume II (Product Offering) is limited to 8 pages, yet Criteria 1–8 each require “discussion and/or evidence,” including FedRAMP Marketplace screenshots, FIPS validation evidence, and equipment specifications. (a) Do required evidentiary materials (e.g., Marketplace screenshots, FIPS/validation certificates, manufacturer specification or ‘cut’ sheets, ATO letters) count toward the 8-page limit, or may they be submitted as clearly labeled appendices/attachments outside the page limit, consistent with the treatment of ‘front matter’? (b) Similarly, for the 10-page Volume III limit, does the required Transition-In visual implementation schedule (e.g., Gantt chart) count toward the page limit?

a) Yes, the evidentiary materials count toward the page limitations.

b) Yes, the Transition-In visual implementation schedule counts toward the page limitations. Page limitation has been increased to 12 pages.

28 Sec. L.12 Items 7–8; Sec. M.7 Criteria 7–8 (digital X-ray equipment specifications)

Criteria 7 and 8 specify imaging-plate parameters (size, pixel pitch, matrix size, bit depth, spatial resolution, SNR/DQE conformity) and a minimum source-to-detector distance. Please confirm that (a) equipment which meets or exceeds each stated parameter, including detectors employing alternative but technically equivalent technology will be rated Acceptable, and (b) what evidence the Government will accept to demonstrate compliance (for example, manufacturer specification sheets and/or FDA 510(k) documentation).

(a) RFP revised to state meet or exceed.

(b) RFP revised to outline evidence examples.

29 Sec. L.10 vs Sec. M.4–M.5 (factor numbering);

Attachment 2 (Past Performance & Experience Form)

Please clarify two administrative discrepancies: (a) Section L.10’s volume table lists “Volume III – Factor 3 – Technical Capability,” while Sections M.4 and M.5 identify Technical Capability as Factor 2 and Past Performance and Experience as Factor 3, please confirm the correct factor numbering. (b) The Past Performance and Experience Form referenced as “Attachment 2” is internally titled “Attachment 5”;

please confirm this is the correct and current form to use for Volume IV.

a) Technical Capability is Factor 2. Section L.10 has been revised to resolve discrepancy.

b) Title of Attachment 2 has been revised.

30 Sec. L.14; Sec. M.10; Attachment 2 (Past Performance & Experience)

“Relevant” is defined as “similar in scope and magnitude to the PWS requirements,” and Attachment 2 requests both total contract value and the number of X-rays performed. How will the Government assess “magnitude” by total dollar value, number of facilities/sites served, annual imaging volume, geographic dispersion, or a combination, and will a contract that is similar in scope and operational complexity but of lower total dollar value still be considered relevant?

See revisions to RFP section L.14 and Attachment 2 which define magnitude.

31 Sec. L.14 (Volume IV – Past Performance and Experience)

Section L.14 permits up to four references (prime or subcontractor), requires at least one reference from the prime/JV/CTA, and states that “a maximum of one” recent, relevant, and valid contract “for a subcontractor performing major or critical aspects of the requirements must be submitted.” Please confirm

(i) whether the one-reference maximum applies only to subcontractors performing major or critical aspects, or to all subcontractor references; and (ii) whether submitting a major/critical-

(i) Confirmed, only applies to subcontractors performing major or critical aspects.

(ii) Mandatory when a subcontractor is proposed who is performing major or critical aspects.

subcontractor reference is mandatory when such a subcontractor is proposed.

32 Sec. L.14; Attachment 2 (predecessor-company provision)

Attachment 2 provides for predecessor-company references and states that parent-company, affiliate, and subcontractor work cannot satisfy the required prime/JV/CTA reference. May an offeror also submit past performance and experience information for a parent or affiliate whose resources, systems, or personnel will be meaningfully involved in performance (analogous to the predecessor-company provision, and counting toward the four-reference limit), and if so, how will the Government evaluate such references?

Offeror’s may provide a reference from a parent or affiliate company. RFP Section L.14 and Attachment 2 have been revised to state such. However, the government maintains that references from a parent or affiliate company are not considered work performed by the prime, JV, or CTA.

33 Attachment 3 – Pricing Template (Registration Fees CLINs 0003/1003/2003/3003/4003);

Sec. M.11 (Price)

The Pricing Template instructs offerors to propose individual registration pricing for each of the eleven listed facilities (shown as “$XX.XX”), while Section A and the PWS state the contractor shall not bill the Government where a state does not require registration or charge a fee. Because these are state-determined, pass-through amounts that may be $0 and are outside the offeror’s control: (a) how should offerors populate these line items for a firm-fixed-price evaluation; (b) will the Government provide an estimated amount or a not-to-exceed value for each facility; and (c) how will the registration-fee line items be treated in the price-reasonableness and unbalanced-pricing analyses under Section M.11?

a) Offerors shall propose a firm fixed price (FFP) rate for the registration pricing which is inclusive of offeror support to facilitate registration, coordinate any inspections, etc. for each facility notated. The offeror shall add up all registration pricing and include the total overall amount as the Unit Price for the Registration Fees, i.e. total amount for all Registration Fees.

b) The rate will not be cited as a not to exceed amount nor will the government provide an estimated amount.

c) The proposed amount will be considered in the total evaluated price and will be evaluated per the evaluation process outlined in RFP Section M.12.

34 Attachment 3 – Pricing Template; PWS Appendix 2 (X- Ray Historical Data); Sec. L.12 Item 4 / Sec. M.7 Criterion 4;

Sec. M.11

Please confirm the definitive list of facilities to be served and, for each, the number of fixed (permanent) and mobile (portable) X-ray units required, since equipment, installation, and transition pricing (CLIN 0004) and Product Offering Criterion 4 depend on it. In addition, the estimated quantities (100,000 chest and 5,000 other per period) and the current facility list differ from the facilities and volumes shown in Appendix 2 – X-Ray Historical Data (for example, Appendix 2 includes Dilley South Texas Family Residential, which is not in the current facility list). Please confirm whether the estimated quantities reflect the current facility footprint and how offerors should reconcile Appendix 2 with the current requirement for pricing purposes.

For the definitive list of facilities see, Appendix 1, IHSC Facility Locations.

For number of X-ray units, see the Teleradiology Equipment section of the PWS.

The estimated quantities of 100,000 chest X-rays and 5,000 other X-rays per ordering period reflect the government’s anticipated requirement for pricing purposes, and offerors shall use these quantities for pricing unless otherwise directed in the solicitation, PWS, etc.

Appendix 2 is for reference purposes and facilities or quantities may fluctuate.

35 Section L.12, Volume II – Product Offering, Items 1–3;

Section M.7, Evaluation Process

– Product Offering

Please confirm whether the FedRAMP Authorized Cloud Service Provider (CSP), FedRAMP Authorized Cloud Service Offering (CSO), and FIPS 140- 2/NSA Type 1 or Type 2 encryption capabilities must be held directly by the prime offeror, or whether these requirements may be satisfied through a proposed teaming partner, subcontractor, or third-party service provider included in the offeror’s proposed solution.

See PWS for all subcontractor requirements.

36 Section L.12: Volume II Product Offering

Are all of the X-ray rooms at each facility built out with the lead-lining requirements to all for the permanent x-ray equipment to be stationed at the facility?

Yes, all of the X-ray rooms at each facility are built out with the required lead-lining to allow for permanent X-ray equipment to be stationed at the facility.

37 Section L.12: Volume II Product Offering

Which Electronic Health Record (eHR) system is used in ICE facilities?

Is this the same in all facilities or does it change per location?

All IHSC facilities utilize eClinicalWorks to order, transmit, and receive results from the vendor for medical diagnostic imaging.

38 Section L.12: Volume II Product Offering

Will the vendor’s staff have access to ICE eHR or will the staff be required to fax the results and interpretation to the facility?

The contractor will work with ICE/IHSC technical teams to ensure the contractor's captured images are stored in the government's cloud, clinical reports with image URLs appear in eCW/EHR, and the images URLs are formatted correctly so that images are viewable in MiPACS.

39 Section F.2 Period of Performance and Ordering Period

When is the expected award date for this RFP?

Estimated award date is early 2027, but this timeline may shift at the government’s discretion.

40 Section L.13: Volume III Technical Capability

Is the vendor required to provide an onsite radiologist technician at each location, or is there a technician already staffed at each facility through ICE?

The vendor is not required to provide an onsite radiologist technician.