HINGE-Oracle_Interface_DRAFT SOW.docx

1. Purpose: The Department of Veterans Affairs (VA) is seeking information from qualified contractors regarding the continued development, testing, implementation, Go-Live support, and post-Go-Live support for enhancements to the Health Information and Gateway Exchange (HINGE) interface with Oracle Health.

The requested period of performance is September 24, 2026, through April 19, 2027, for a total of seven months. This period is intended to support completion of the remaining interface development activities through the planned Oracle Health production Go-Live for the Wisconsin market on January 16, 2027, followed by post-Go-Live stabilization and support.

2. Background:

HINGE is a VA radiation oncology information and analytics platform that interfaces with VA clinical information systems to support collection, integration, and use of clinical data.

The HINGE–Oracle Health interface is currently in development. The remaining work under this scope of work primarily consists of:

· Completion of the HINGE FHIR ChargeItem enhancement;

· Build and unit testing;

· Interface Solution Test (IST);

· Resolution and retesting of interface defects;

· Interface documentation updates;

· Cutover planning and rehearsals;

· EHRVIP readiness activities;

· Production cutover and Go-Live support; and

· Post-Go-Live stabilization and issue resolution.

The objective of this effort is to complete and successfully deploy the HINGE Oracle Health ChargeItem interface enhancement and support the interface through production Go-Live and the post-Go-Live stabilization period.

The contractor shall work collaboratively with the VA HINGE team and Oracle Health team to complete the interface implementation in accordance with Oracle Health interface requirements and the project schedule.

3. Scope of work:

3.1 ChargeItem Interface development

The contractor shall complete the HINGE FHIR Service enhancement required to submit charges to Oracle Health using the FHIR ChargeItem resource.

Activities shall include:

· Work with the Oracle Health team and HINGE team to finalize ChargeItem interface specifications.

· Implement modifications to the HINGE FHIR Service to generate ChargeItem resources in the structure and format required by Oracle Health.

· Implement appropriate validation checks to verify that ChargeItem resources are complete, correctly structured, and transmitted successfully.

· Support integration of the ChargeItem submission workflow into HINGE.

· Conduct unit testing of the completed implementation.

· Document relevant interface changes.

3.2 Interface Solution Test (IST)

Following completion of development and unit testing, the contractor shall perform Interface Solution Testing to verify that the completed interface operates as intended.

Activities shall include:

· Execute approved IST test cases.

· Validate the ChargeItem workflow and associated interface processing.

· Document test results and defects.

· Troubleshoot and resolve defects identified during testing.

· Retest corrected defects.

· Provide final IST results and evidence of successful testing.

3.3 Interface Documentation

The contractor shall maintain interface documentation throughout development, testing, and deployment.

Required documentation includes:

· Interface Control Document (ICD): Maintain and update the ICD with the Oracle Health team to reflect the current interface design, data flow, and implementation.

· IST Test Cases: Develop and maintain test cases with the Oracle Health team covering the ChargeItem workflow and required interface functionality.

· Update the ICD and associated documentation based on findings from IST and prior to the EHRVIP readiness activities.

3.4 Cutover Planning

The contractor shall support planning and preparation for production implementation.

Activities shall include:

· Develop and maintain the interface cutover plan in coordination with the Oracle Health team.

· Conduct a cutover dry run.

· Conduct tabletop/walkthrough sessions.

· Define sequencing, responsibilities, dependencies, validation activities, and rollback procedures with the Oracle Health team.

· Confirm production readiness prior to the scheduled cutover.

3.5 EHRVIP Readiness

The contractor shall support the project activities required for EHRVIP (EHR-Specific, Veteran-Focused, Integration Process) readiness with the VA EHRM program and Oracle Health teams, including:

· Quality assurance readiness activities.

· Verification of interface readiness.

· Support preparation of the Go Memo.

· Address outstanding technical issues and dependencies required for production implementation.

3.6 Production Cutover and Go-Live

The contractor shall provide technical support for the scheduled production implementation.

Activities shall include:

· Participate in production cutover activities with the VA EHRM program and Oracle Health.

· Validate interface connectivity and functionality following deployment.

· Monitor initial production transactions.

· Troubleshoot and resolve issues encountered during cutover.

· Support the HINGE and Oracle Health teams during Go-Live.

3.7 Post-Go-Live Support

The contractor shall provide post-Go-Live technical support to identify, troubleshoot, and resolve issues associated with the Oracle Health interface.

Activities shall include:

· Monitor and troubleshoot production interface issues.

· Investigate issues not identified during testing.

· Correct interface defects within the contractor's scope.

· Coordinate with VA, HINGE, and Oracle Health personnel.

· Document production issues and resolutions.

· Support stabilization of the interface following Go-Live.

3.8. Cybersecurity and ATO Support

The contractor shall provide cybersecurity project management and support for continuous monitoring and maintenance of the applicable Authority to Operate (ATO) requirements associated with the HINGE interface.

Activities may include:

· Support cybersecurity project coordination.

· Support required security documentation and artifacts.

· Support continuous monitoring activities.

· Coordinate with VA cybersecurity and project stakeholders.

· Address cybersecurity-related findings associated with the interface within the contractor's scope.

· Provide technical information required to maintain the operational authorization of the system.

4. Project Schedule and Milestones

To be completed by the contractor

To be completed by the contractor

To be completed by the contractor

To be completed by the contractor

5. Required Deliverables