DA10--Qgenda Scheduling Software

cover letter page. Submit your response via email to peyton.wilkerson1@va.gov Submit your response NLT 15:00 (MST) on Friday, October 23rd, 2026; Mark your response as Proprietary Information if the information is considered business sensitive. VA has identified the appropriate North American Industry Classification System (NAICS) Code as 541519 Other Computer Related Services with a Small Business size of $34 million. Please identify and explain any NAICS codes your company believes would better represent the predominated work included in the attached Statement of Work draft / Salient Characteristics List; Information Requested from Industry: In response to the Sources Sought, interested Contractors shall submit the following information and any Capabilities/Qualifications Statement to include but not limited to an overview of proposed solution(s) and a description of the product your company possesses in accordance with the Statement of Work draft / Salient Characteristics List. Vendor Name: SAM UEI #: Name of Manufacturer: Manufacturer Address: Estimated Delivery Time: SAC FSS contract number Vendor Point of Contract (POC) Name POC Phone Number: STATEMENT OF WORK Brand Name or Equal - Qgenda Scheduling Software Eastern Oklahoma VA Health Care System General: Currently, the Eastern Oklahoma VA Health Care System (EOVAHCS) requires a hospital wide call scheduling program. The program will standardize how multiple services create and publish their monthly call schedules. The standardization will enable better patient care by facilitating better physician scheduling and up to date contact information throughout the hospital. Delivery Location: Muskogee Delivery Times: Delivery, implementation support, and training shall occur Monday through Friday between 7:00 AM and 4:00 PM local time, excluding federal holidays, unless otherwise coordinated with the COR. Definitions/Acronyms OKC VAHCS: Oklahoma City Veterans Affairs Health Care System Scope: The Contractor shall provide a fully hosted, cloud based, FedRAMP authorized on call scheduling solution for enterprise wide use. Multiple departments will be able to create unique call schedules, assign permissions, and manage access. Select administrators will have full editing rights, while most users will require read only access. 5.1. Must be a solution that has a valid Authorize to Operate (ATO) designation in place with the Veteran s Administration. 5.2. Must be a solution that is FedRAMP Certified by contract award date. 5.3. Must be able to support the VA s Single Sign On Vendor. 5.4. Must have the ability to connect to other systems. If the facility has Vocera, must provide a schedule integration with Vocera for Voice Group Assignment and also have an existing mobile application to mobile application integration with Vocera. 5.5. Must have the ability to offer dual integration to Vocera both for populating Vocera Voice Group as well as a deep link between each vendor mobile applications 5.6. Must assign a US based dedicated support resource that consults the facility at no additional cost, and provide additional support services via phone or online Monday through Friday 9:00AM 6:00PM (Eastern Time Zone). 5.7. Must support the ability to pull reports on-demand and be exportable to excel, pdf, and csv including number of shifts worked, call fairness, weekdays vs weekends, PTO reports, etc. 5.8. Must be able to create schedules as far out in the future as desired (Monthly, Quarterly, Annually, etc.) 5.9. Must be able to create, maintain and provide access to provider schedules through the use of a secure, facility-specific web site and mobile application. 5.10. Must be 100% Web-Based accessible by a web browser both inside the VA hospital and outside and not locally hosted and/or require additional hardware/software at the facility. 5.11. Must be accessible via native iPhone & Android mobile applications and provide full end-user functionality (schedule viewing, requesting, swapping, etc.) FedRAMP approved use from both military and personal smart phones. 5.12. Must offer multiple ways of creating the schedule including the ability to have software automations create the schedule. The automations should use a rules-based engine, powered by a configurable algorithm. 5.13. Must be a solution with interactive/intuitive logic to prevent scheduling gaps if algorithm is unable to reach "100%" during the automated build process which presents data related to conflicts and suggestions on provider availability. 5.14. Must be a solution that can take into account various preferences/rules for consecutive shifts and allows for more variable numbers of consecutive, time-based shifts. 5.15. Must be a solution with the ability to track provider targets in "real time" as it relates to the number of shifts or hours as well as consider this information in future automated schedule builds. 5.16. Must be able to incorporate individual provider scheduling preferences. 5.17. Must provide user friendly, decision support tools to aid in the efficient creation of schedules. 5.18. Must support the ability for providers to submit requests for open shifts, specific roles or time off electronically. It should also enforce any limits that a facility would like to put in place. 5.19. Must be able to support functionality which allows administrators and providers to put shifts up for pickup (Available shifts board) and ability to request to pick shifts up 5.20. Must be able to support a multi-tier approval process. 5.21. Must be able to track time worked via a mobile application and or web solution. The mobile applications should also be able to geo-verify and flag exceptions to all time punches. Finally, the time tracking capabilities should enable users to identify and report on overtime. 5.22. Must be able to filter schedule data in any format (by region, by site, by provider type, etc.). 5.23. Must be available via native mobile applications for both the iOS and Android platforms. It should provide the ability to view schedules, filter those views and integrate with other office/personal scheduling applications such as Outlook or Gmail. 5.24. Must be able to support the request process through the mobile application. It should also let providers submit shifts to a swap market for time they are looking to take off and also allow them to pick up shifts from other providers looking to change their schedule. 5.25. Must have the ability to configure various levels of user permissions and associated functionality at the enterprise, departmental and user level. 5.26. Must support the ability to create tickets when substantial changes are made to the schedule so other areas of the hospital are aware of said changes and can plan accordingly (ex. a provider requests to cancel a clinic day and a ticket is created so the patient access team knows they need to update the EMR with the clinic changes, so patients do not show. Training for VA Employees: The Contractor is required to provide comprehensive training for Qgenda or equal to software and applications. The contractor shall make the necessary arrangements with the COR to schedule training sessions. Training may be performed as dictated and agreed upon by the EOVAHCS on weekends, after normal business hours (7:00 AM to 4:00 PM), or federal holidays. The training must be completed before implementati