340b Rebate Split Billing Software Solution

The vendor required to provide 340b rebate split billing software solution for include:
- Project implementation plan
•    General implementation approach
•    Project management approach
•    Implementation tasks and activities
•    Department staffing and roles needed for the project
•    The approach to data conversion and
•    Training approach including supporting documentation
•    The quality assurance plan
- Network architect and design document
•    Once the contractor has completed analyzing the requirements, the contractor will develop a network architect and design document. 
•    This document will identify exactly how the solution meets the requirements, and the work required to implement each requirement. 
•    Develop and manage all configuration and integration activities against the network architect and design document.
- Data conversion and migration
•    Prior to performing the data conversion and migration services, contractor will identify the data conversion services required. 
•    The project implementation plan, the approach of how the conversion of the historical data to the new solution will be provided, identify risks regarding data migration and how those risks will be avoided or mitigated. 
•    The project implementation plan, the contractor will also include identification of the roles and responsibilities between the contractor’s team and department related to data conversion activities.
- System interfaces
•    Interface the new solution with multiple department databases and systems, and pharmaceutical manufacturers as necessary to meet 340b program requirements. 
•    The project implementation plan, the contractor will describe their approach towards interfacing and integration with other solutions (e.g., xml, web services) including use of specific tools, methods and standards. 
•    The requirements matrix for specific system interface requirements.
- System testing
•    assist department in conducting testing (“user acceptance testing” or “UAT”) as part of their quality assurance plan for the solution, including but not limited to: security, functional, unit, regression, smoke, load, performance and stability tests. 
•    Each applicable test shall be identified by the department, and the use of industry-standard automated testing software is strongly encouraged. 
•    The software will be flexible to handle changes and requirements of any complexity and allow for ensuring that all requirements are met and that regressing testing will fully test all previous functionality.
- Environments
•    Support distinct and isolated environments for testing and production. 
•    The testing environment must mirror production in terms of functionality and configuration to the extent practical but must operate independently to prevent any impact on live systems.
- Go-live and initial operation support
•    Completion of all testing, the solution must be deployed into production. 
•    Provide initial go-live support and prepare for successful ongoing solution use. 
•    Final deployment acceptance, department desires to have the solution enter a 30-day system stabilization period with a 30-day warranty period to follow.
- Documentation and guides
•    Provide department the functional specification documents and provide electronic documentation or web-based formal user guide including but not limited to screen shots of user interface, step by step guide to login and procedures, and reports guide. 
•    Provide additional reference guides such as system design diagram and the technical requirements reference guides.

- Contract Period/Term: 2 years
- Voluntary Pre-Proposal Teleconference Date: November 19, 2025
- Questions/Inquires Deadline: November 24, 2025