ESBD_576825_1794865813762_Attachment B_Joint Tech - Technical Review with AI Questions.xlsx

XLSX spreadsheet 100 KB Posted

Attached to
Government, Risk and Compliance Platform
Solicitation number
2711-001
Issued by
Travis County, Austin City, Texas

About this file

This is a technical review document with AI-generated questions for a joint technology procurement effort involving multiple state and local agencies. The file appears to be an Excel spreadsheet designed to facilitate technical evaluation of proposals, containing structured questions and assessment criteria for evaluating vendor responses to a technology-related solicitation. The document serves as a standardized tool for a consortium review process, enabling consistent evaluation across participating jurisdictions. While the specific response dates, due dates, site visits, and bidders' meetings are not detailed in the filename or file type description provided, this technical review framework would typically be used during the evaluation phase following proposal submission to ensure comprehensive and uniform assessment of bidder qualifications and proposed solutions.

The document focuses on establishing standardized technical evaluation criteria rather than pricing terms or contract award details. No specific set-asides, incumbent information, funding amounts, or pricing structures are indicated by the filename or document type. This tool would be used by a joint review panel to assess technical merit and capability before final award decisions are made, allowing multiple agencies within the consortium to apply consistent standards to vendor proposals and ensure that selected contractors meet established technical requirements across all participating jurisdictions.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Tech Review

Version6/18/26
CATEGORYQUESTION NO.QUESTIONOFFEROR'S COMMENTS
DATA CENTER SECURITY & COMPLIANCE1Describe data center security standards for the hosted solution.
2Describe data center compliance with those standards, including independent audit results or certifications.
3Attach a security architecture diagram.
4Attach a copy of the most recent data center SOC audit or other self-attestation regarding security and compliance.
REDUNDANCY & DISASTER RECOVERY5Describe data center tier rating(s) and resiliency for redundancy and failover.
6Describe the physical locations of data centers that will host our data, including those for redundancy. If the actual locations cannot be revealed, describe them geographically in terms of distance.
7Describe any locations that are off-shore from the Continental United States.
8Describe failover design.
9Describe disaster recovery protocols and how data is restored.
10Describe the thresholds and protocols to notify the customer when disaster recovery protocols are triggered.
SECURITY OPERATIONS11Is there a dedicated Information Security Officer or CISO responsible for security architecture and operations?
12Describe incident response protocols and how security events are investigated and remediated.
13Describe Risk Management and Risk Assessment protocols, including any 3rd party Risk Assessments.
14Describe Penetration Testing protocols including frequency.
15Describe physical security controls for any facilities in which our data may be processed.
16Are internal systems protected with dedicated firewalls and anti-virus software?
17Describe security within your development lifecycle - are DAST or SAST tools implemented?
18Describe State and Federal Security Audit Certifications obtained such as TX-RAMP, FedRAMP, StateRAMP, FISMA, etc.
AUTHENTICATION19Describe any SSO or Federation capabilities.
20Describe any MFA or 2FA capabilities.
21Describe any other integration capabilities.
BACK-UP, MAINTENANCE22Describe the backup process, including but not limited to, frequency and method (e.g., incremental/full, onsite/offsite).
23If the backup process involves a third party network/server/vendor, please identify the third party(ies).
24Describe routine and emergency maintenance protocols.
AVAILABILITY, MONITORING & ALERTS25Describe up-time.
26Describe the protocol for monitoring services.
27Describe Service Level Agreement.
DATA PROTECTION, RETENTION & USE28Describe data retention protocols.
29If data is not retained indefinitely, describe the alternatives for storage and destruction.
30Describe scalability for growth of data.
31Describe our ownership rights to the data while under contract and in the event the contractual relationship is terminated.
32Is data used for any other purpose other than our stated purpose?
33Is data encrypted during transit?
34Is data encrypted at rest?
PROTECTED HEALTH INFORMATION / HIPAA35Describe measures or architecting strategies to protect health-related data for HIPAA compliance.
36Describe data separation environment and/or shared computing resources so that we fully understand the physical or virtual machine environment that supports its data.
37Describe the protocol to notify customers of security breaches.
WEB-BASED, OS & BROWSER COMPATABILITY38Is this a web-based application? If not, describe the application such as locally installed on computers or on-premise environment.
39Identify all compatible operating systems.
40Identify all compatible browsers.
41Identify all compatible devices, such as PC, laptops, tablets, etc.
42Is there a mobile app? If yes, describe whether it is available for iPhones, Windows, Android.
SUPPORT, ON-GOING ADMINISTRATION & TALENT43Describe the service desk support process and resources, including but not limited to customer portal, hours of operation, escalation paths.
44If available, describe the various levels of support plans and their cost.
45Describe recommended certifications to properly administer the services from the customer side.
46Describe training and continuous learning resources to properly administer the services from the customer side.
AGREEMENTS47Attach a copy of, or provide an online link, to the following documents:

a. All Terms and Conditions which may include, but not be limited to,

i. Business Associate Agreement

ii. End User License Agreement and/or all other licensing agreements

iii. Service Level Agreement

iv. Support and Warranty Agreements

b. All other documents and/or agreements not listed above that will require signature or attestation by Central Health in order to secure a contract.

AI (If Applicable)48Technical: Describe the end-to-end architecture for the solutionDescribe the E2E architecture of your solution, including key components (e.g., data ingestion, processing, model layers, storage, integration points, and user interfaces), deployment model (cloud/on-prem/hybrid), and how data flows across each stage. Include any dependencies, scalability mechanisms, and high-availability design considerations.
49Technical: Does the AI "learn" from our patient data? If so, how do you ensure PHI isn't leaked ?Does the AI "learn" from our patient data? If so, how do you prevent PHI leakage, including data isolation, de-identification, access controls, encryption. Is customer data used to train shared models?
50Technical: Where is the processing happening? Is any data being sent to third-party LLM providers? If so, do you have a BAA in place?Where is data processing hapenning and is data being sent to third-party LLM providers? If Yes, identify the providers, data shared, and confirm whether a BAA is in place.
51Technical: HITL (Human-in-the-Loop) what is the confidence score threshold for straight-through processing?For HITL workflows, what confidence score thresholds trigger straight-through processing vs. human review, and how are these thresholds defined, calibrated, and monitored?
52Technical: Does the solution support active learning or feedback-based improvement? If so, describe: (a) the mechanism by which corrections or user feedback are incorporated; (b) how model updates are validated before redeployment (including regression testing); (c) the approval process for model retraining using our data; and (d) how the System (Central Health, Sendero, CUC) is notified of material model changes.
53Technical: How does the system handle unstructured data?How does the system ingest, process, and extract insights from unstructured data (e.g., text, PDFs, images, audio), and what techniques are used to ensure accuracy and data quality?
54Explainability: If an application is rejected, can the system generate a "Reason Code" or a natural language explanation ?If yes, describe how these outputs are generated, validated for accuracy, and audited for consistency and compliance.
55Bias Mitigation: Have you tested the model for bias in general? How have you tested the model for bias against certain demographics ? Is there any documented bias testing performed?Bias can

include but is not limited to biases on human factors such as gender, race, socioeconomic status, disability, culture, age, or other protected classes, or biases on general factors such as a sampling bias, survivorship bias, detection bias, or observer bias.

56Model Versioning: How do you manage "Model Drift"? If the new document needs to be added or format of existing document changes, how quickly can the model be updated and re-validated?How do you detect and manage model drift, and what is your process for updating and re-validating models when, for example, new document types are introduced or existing formats change? Include typical turnaround time, validation approach, and version control practices
57Auditability: Does the system maintain a thread of evidence? Can an auditor see, for example, exactly which part of a scanned document the AI used to extract a specific data point?
58Hallucination Prevention: What specific guardrails are in place to prevent the AI from "hallucinating" a date or address when the scan is unreadable?What guardrails and validation checks are in place to prevent hallucinated values (e.g., dates, addresses), for example, when source data is missing or unreadable, how does the system detect, flag, and handle low-confidence or incomplete inputs?
59Input Validation: How does the system handle "adversarial" inputs or fraudulent documents?How does the system detect and handle adversarial or fraudulent inputs (e.g., tampered or synthetic documents), include validation techniques, fraud detection methods, and escalation workflows?
60AI Model Training: Copy of the policy of the AI model training data usage
61Incident Response Plan: Copy of the plan documented

tc={CE03A99F-10A4-4805-A9B9-A149D6C75237}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

IC MGMT Plan in place - IT Specific. Fortify IT Response Plan.

62Business continuity/disaster recovery plan documented
DPAData Processing Agreement (DPA) (if applicable)Other Data protection Frameworks Vendor complies with (e.g., NIST 800-53, NIST AI

RMF) and certifications (e.g., SOC II, HIPAA (R42C1), FERPA, CJIS (R72C1).

CJISCJIS Security Addendum (If applicable)
Insurance CertificatesCyber Liability and E&O
RegulatoryRegulatory: Has this AI solution been assessed for classification as Software as a Medical Device (SaMD) under FDA guidelines? If applicable, describe any FDA submissions, clearances, or 510(k) exemptions. Does the solution comply with ONC HTI-1 regulations regarding AI-generated clinical decision support (effective 2025)?
Please share any relevant information, links, or resources regarding your organization’s responsible AI strategy

IC MGMT Plan in place - IT Specific. Fortify IT Response Plan.

image1.png

File details come from the government source that posted it. Updated .