The Data COUNTS™ (Collect Data Once, Use Numerous Times)
Key Dates
Due Date
-
Posted Date
-
Agency & Value
Agency
NATIONAL INSTITUTES OF HEALTH NIAID
Contract Value
Not provided
Codes & Classification
Solicitation Number
75N95C26R00005
NAICS
-
Classification Code
DA10
Additional Details
Documents2
The National Institutes of Health (NIH), under the Department of Health and Human Services, has issued a Request for Information (RFI) to gather insights and capabilities from industry stakeholders in support of the Data COUNTS™ (Collect Data Once, Use Numerous Times) initiative. This RFI, identified by procurement number 75N95C26R00005, is not a solicitation for proposals but rather an exploratory effort to inform future project planning and potential requirements for the Data COUNTS program. The notice is active and responses are due by September 22, 2026.
**Purpose and Scope**
The Data COUNTS™ program is a collaborative effort designed to advance the NIH’s Real-World Data initiative by enabling the collection, standardization, and secure sharing of high-quality, provenanced healthcare data. The program’s overarching goal is to facilitate research by making standardized, de-identified data available to the research community through approved access mechanisms. The initiative emphasizes collaboration among patients, advocates, government entities, health systems, technology providers, and the private sector.
The contemplated solution will initially focus on extracting data from Healthcare Partner electronic medical record (EMR) systems, with the flexibility to extend to other authorized data sources such as laboratory information systems, pharmacy systems, picture archiving and communication systems, vendor-neutral archives, and specialty systems. A key requirement is the preservation of source data, provenance metadata, permissions, and ontology fields without modification or loss, except for authorized de-identification processes. The program will not create or standardize ontology mappings.
**Key Requirements and Objectives**
Respondents are asked to address the availability and technical capabilities of solutions that can meet the following core requirements:
1. **Healthcare Partner Leave Behind Technology**: The solution must be a durable, on-premises technology that remains with the Healthcare Partner after contract completion, operable by trained staff without ongoing vendor involvement. It should be free for use by partners during program participation and include comprehensive documentation, operational runbooks, credential-transfer procedures, update protocols, and training materials.
2. **Data Extraction and Provenance**: The system must support deep, approved queries from EMR and other authorized systems, capturing timestamps and maintaining an immutable provenance chain for all extracted data.
3. **Specification-Driven Architecture**: The solution should consume a machine-readable, version-controlled Data Request Specification, validating data availability, identifying unavailable or ambiguous fields, avoiding silent substitutions, and supporting reproducible reruns.
4. **Automated Data Quality Checks**: Initial automated checks must validate data completeness, uniqueness, types, sequencing, and records-per-patient, with all anomalies reported prior to any corrections. Source data must remain unmodified.
5. **De-identification**: Compliance with 45 CFR §164.514(b) is required, including removal of all 18 direct identifiers, documentation of de-identification pathways, and per-patient date-shifting that preserves temporal order.
6. **Privacy Preserving Record Linkage (PPRL)**: The solution must support on-premises, institutionally-contained PPRL tokenization for cross-site linkage, ensuring consistent, irreversible patient tokens without creating shared trust boundaries.
7. **Preservation of Metadata and Ontology Fields**: All source provenance metadata, permissions, and ontology fields (e.g., SNOMED CT, LOINC, ICD-10, RxNorm, UCUM) must be preserved, with clear traceability and no unauthorized modifications.
8. **Authorization and Eligibility Management**: The system must apply authoritative eligibility criteria, record governing permissions, distinguish between cohort and permission exclusions, and enforce revocations in subsequent data refreshes.
9. **Data Extraction and Refresh Management**: Capabilities must include full and incremental extracts, stable patient tokens, unique snapshot and refresh IDs, idempotent reruns, and identification of record changes across refresh cycles.
10. **Workflow Integrity and Audit**: Comprehensive audit records must be maintained for each processing stage, with mechanisms to halt transmission upon failed reconciliations or incomplete processing.
11. **Security and Compliance**: The solution must attest to HIPAA Security Rule compliance as a Business Associate, generate SIEM-compatible security logs, and ensure logs are protected against unauthorized modification or deletion.
12. **Encryption and Attack Surface Minimization**: Data in transit must be encrypted (TLS 1.3 preferred, TLS 1.2 minimum), with application-level and VM-level encryption for output files. The system should minimize attack surfaces, allowing only outbound TLS connections to the Data COUNTS program.
13. **On-Site Data Processing**: All identifiable data processing must be confined to the Healthcare Partner’s environment, with no contractor credentials, remote access, or management capabilities included.
14. **Performance and Resource Requirements**: Respondents should describe solution performance at baseline, 2X, and 5X expected workloads, including data volumes, throughput, processing times, and resource requirements.
15. **Data Packaging and Delivery**: The solution must reliably package, transmit, reconcile, and retry data deliveries, supporting schema versioning and robust error resolution.
**Business Information Requested**
Respondents are asked to provide detailed information on their ability to meet the specified capabilities, distinguishing between commercial off-the-shelf (COTS), minor modifications, and custom development features. Additional requested information includes billing models, pricing structures, relevant implementation experience (with healthcare partners, federal agencies, and other sectors), and business size/status.
**Contracting Entity and Contact Information**
- **Contracting Entity**: National Institutes of Health (NIH), NIAID Office
- **Department**: Health and Human Services, Department of
- **Place of Performance**: Bethesda, Maryland, United States
- **Product Service Code**: DA10
- **Set-Aside**: None
**Primary Contacts**:
- Susan Gregurick, [email protected], 240.381.3566
- Chris Ray, [email protected], 240.627.3365
**Submission Instructions and Considerations**
Responses must be submitted in PDF or MS Word format by September 22, 2026, at 3:00 PM Eastern Standard Time to [email protected], with the subject line “Company Name RFI Response.” Questions may be submitted by September 15, 2026. Responses should be organized according to the numbered requests in the RFI. No proprietary, classified, or sensitive information should be included, as the Government may use any non-proprietary technical information in future solicitations.
**Special Considerations**
This RFI is for information gathering only and does not obligate the Government to award a contract or pay for information provided. The Government may follow up with respondents for clarification or demonstrations but is not required to do so. Any future solicitation will be announced publicly, and responses to this RFI will not be considered proposals.
For further details and updates, interested parties are encouraged to visit the official notice at [SAM.gov](https://sam.gov/opp/976be5e51f7a4e2fa13e7fac79df789b/view) and the program website at www.nih.gov/data-counts.
This opportunity is particularly relevant for organizations with expertise in healthcare data extraction, de-identification, privacy-preserving record linkage, and secure, compliant data management solutions, especially those with experience supporting large-scale, multi-institutional research data initiatives.