HT003824R0006_QAs.pdf
PDF 150 KB Posted
- Attached to
- LEGACY DATA CONSOLIDATION SOLUTION – HEALTH INFORMATION ARCHIVE Federal contract opportunity
- Solicitation number
- HT003824R0006
- Issued by
- Defense Health Agency
About this file
This document is a Request for Information (RFI) from the Defense Health Agency (DHA) regarding a Legacy Data Consolidation Solution - Health Information Archive (LDCS-HIA) system. The DHA is seeking information on how contractors could support this requirement, which aims to consolidate and archive legacy clinical data systems such as Essentris, AHLTA, CHCS, and EBMS into a secure, cloud-based repository.
The RFI provides background on the LDCS-HIA initiative, including the planned production period of November 1, 2024 to October 31, 2025. It requests information on software, hardware, infrastructure, program management, data transformation, testing, operational support, and experience with the DoD's Risk Management Framework. Interested parties are asked to submit a white paper response by August 5, 2024, which should address the requested information. The government may or may not choose to meet with potential offerors for further clarification. This RFI is for information gathering purposes only and does not commit the government to a procurement action.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| DRAFT_PWS_HT003824R0006.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions and Answers – HT003824R0006 LEGACY DATA CONSOLIDATION SOLUTION – HEALTH
INFORMATION ARCHIVE
Q1. Is there a current incumbent contract associated with LEGACY DATA CONSOLIDATION SOLUTION – HEALTH INFORMATION ARCHIVE requirement or is this a new requirement?
A1. ECS Federal is currently performing the work in support of NIWC Atlantic. TO# N652362393014.
Q2. What software is currently being used to perform the HIA capabilities?
A2. The following table includes software currently leveraged in the solution.
Item # Description Unit/Issue Quantity L47232 Oracle Advanced Compression EA 4 L47232-S Oracle Advanced Compression - SULS EA 4 L101635 Oracle Secure Backup EA 4 L101634-S Oracle Secure Backup - SULS EA 4
DBF-TOD-
KS
TOAD for Oracle DBA Edition per seat maintenance
EA 10
Windows 2016 RDS Client Access Licenses
EA 15
Mediquant DataArk (OpenArk, ArkLoad, ApplicationArk, PatientArchive, ArchiveInsights, & ArchiveMPI)
Bed/Providers Beds:
11,958 Providers:
17,772
Q3. Does the Government have an existing solution for the LDCS initiative? If so, please identify the software technologies used in that solution.
A3. See A2.
Q4. Please identify the incumbent contractor for this initiative.
A4. See A1.
Q5. Does the Government intend to continue use of the existing LDCS solution on this contract? Will the Government consider alternate software technology for this contract?
A5. The Government intends to continue use of existing solution. Alternate software technologies will be reviewed to determine adequacy.
Q6. If vendor propose alternate software technology for the LDCS initiative, will the Government sponsor security accreditation for the solution?
A6. Yes, accreditation of the system will be required if the Government determines a change to the software solution is preferable.
Q7. Completing the remaining data archive sites within 12 months seems aggressive if vendors need to obtain an authority to operate during the PoP. What recommendations does the Government have for vendors seeking to propose an alternate software technology for the LDCS initiative?
A7. The data archive of legacy sites is based on the financial need to disconnect the legacy sites.
Q8. Please identify the GFE/GFI available for vendors in support of this initiative.
A8. No GFE will be provided. Access to Government resources through AVHE will be provided.
Access controls to perform administrative and sustainment tasks will be provided.
Q9. For the legacy data, please identify the number of instances and percentage complete for each application:
Composite Health Care System (CHCS) Clinical Information System CIS-Essentris Anesthesia Reporting Monitoring Devices (ARMD) Enterprise Blood Management System – Transfusion (EBMS-T) Armed Forces Health Longitudinal Technology Application (AHLTA) Central Data Repository (CDR)
A9. Percentage complete for each application:
Composite Health Care System (CHCS) (DQ/DV 75% and in HIA 25%) Clinical Information System CIS-Essentris (DQ/DV 75% and in HIA 53%) Anesthesia Reporting Monitoring Devices (ARMD) (HIA 100%) Enterprise Blood Management System – Transfusion (EBMS-T) (100%) Armed Forces Health Longitudinal Technology Application (AHLTA) Central Data Repository
(CDR) (0%)
Q10. The background state that: IDS requires the contractor to finalize development and deployment of a cloud-native LDCS-HIA solution that will provide a secure and active health data repository for DHA’s legacy clinical systems”. Reference PWS 3.2.3 State that “The contractor shall conduct database management activities for the Oracle and MS SQL Servers necessary to support all development, testing, and production activities for HIA”. Is Oracle or MS SQL a requirement or can a COTS Content and Records management System that is NARA ERM compliant be proposed? Page 5 indicates that Records Management Certification of the solution must be facilitated by JTTC. It seems that it might be a costs savings to the government a system was proposed that already met RM standards as opposed to building a system and getting it certified after the fact.
A10. The Government will review alternate technology solutions.
Q11. Paragraph 3.4.16.1 indicates that digitization of paper records is required to PDFs. It is suggested that PDF/A be specified as this files type is a type of PDF file especially designed for archiving by ensuring long term file accessibility and reproduction and is an ISO standard? The paragraph does not indicate the volume of paper to be digitized. The volume will be needed to be able to price this as a fixed price task.
A11. Currently only PDF files being digitized. Volume: S3 storage buckets and consume ~6.4TB within the MIP
Q12. Has an initial design been architected/approved for the LDSC – HIA solution? Would the government be willing to provide system architecture diagrams of the designs/initial solution?
A12. The approved design will be included if the Government releases an RFP. This is a RFI only.
Q13. Will the government provide access to an AWS environment within the GovCloud or will it be the contractor’s responsibility to implement and host an AWS environment?
A13. Yes, access to the govCloud environment will be available. See A8.
Q14. Page 7 (PWS) – Section 3.3.1.3.2 - If the solution is to be developed and maintained in the cloud, please clarify the need for a contractor to provide equipment support?
A.14 This allows solution providers the ability to set up their own AWS gateway to access the AWS Gov cloud via their own connection setup and run by the vendor in lieu of GFE’s on the GOV’s side.
Q15. Please clarify whether the government anticipates a contractor to complete all capabilities/requirements (PWS 3.4.1 – 3.4.22.1) in a single 12 month time period (PoP: Nov 1, 2024 - Oct 31, 2025). If not, what requirements/system functionality is needed within the first year?
A15. See A7.
Q16. Is there an incumbent for this work?
A16. See A1.
Q17. PWS 3.1 Program Management: Please provide definition for acronyms: SDP, PMP
A.17 SDP: Software Development Plan, PMP: Program Management Plan
Q18. PWS 3.4 Technical Capability: Please provide Annex 1 RTM.
A18. Contents of RTM are duplicated in PWS 3.4.
File details come from the government source that posted it. Updated .