phone: (646) 815-3747
email: RFP_contacts@nychhc.org
PIN#2763 Due:
- NYC Health + Hospitals BAA
- NYC Health + Hospitals Standard Terms and Conditions
- MWBE Waiver Request Form
- MWBE Utilization Plan Form
- NYC Health + Hospitals Security Requirements
- RFP 2763 - Enterprise Legacy Data Archive
- RFP 2763 - Enterprise Legacy Data Archive Addendum 1
- RFP 2763 Enterprise Legacy Data Archive - Q&A Addendum
New York City Health and Hospitals Corporation (NYC Health + Hospitals) is seeking proposals for an Enterprise Legacy Data Archival solution/platform to archive data from retired or decommissioned legacy systems while maintaining user access to this data. The goal is to seamlessly migrate and centralize data from the legacy system(s) to the proposed solution, ensuring zero data loss or corruption, while minimizing downtime and disruption to business operations. This process must decommission legacy system(s) and equipment, to reduce maintenance costs, and enable end users to access archived data smoothly while preserving the same functionality as if the legacy applications were still operational. The proposed solution must be capable of domain-agnostic archiving across a variety of domains, including Clinical, Financial, Revenue Cycle, Human Resources (HR), Maintenance, and Security/Badge Access, and must support data archival from diverse database technologies, including, but not limited to, Cache, Microsoft SQL Server, Oracle, and Mainframe Systems. Archived data must be accessible via API solutions such as RESTful, FHIR, SOAP, OData, HL7, and other secure data access protocols to facilitate seamless integration with current and future systems.
The proposed solution should include application-generated data lifecycle management to handle data intake, verification, and retirement processes, ensuring secure removal of data when no longer required and facilitating the linking of archived data to active systems for reference purposes. Special consideration will be given to solutions that can integrate with existing platforms such as Epic, Snowflake, and Tableau. Additionally, the proposed solution should be flexible enough to accommodate future decommissioned applications, ensuring its long-term sustainability. Finally, the proposed solution should include comprehensive support services during and after implementation to ensure successful deployment and ongoing operations, along with training for in-house resources on solution maintenance and future legacy application archiving