RFI 720-5250-126446_WaMS Modernization_Offeror Questions and DBHDS Responses.pdf
PDF 125 KB Posted
- Solicitation number
- RFI-126751
- Issued by
- Virginia
About this file
This document is a Q&A response record from the Virginia Department of Behavioral Health and Developmental Services (DBHDS) related to the Waiver Management System (WaMS) Modernization RFI (Request for Information), Solicitation Number 720-5250-126446. The RFI seeks to gather insights on costs, procedures, and challenges associated with implementing a modernized waiver management system that aligns with new transparency and timeliness standards. The modernized system will include key functional areas such as Service Authorization, Individual Support Plan management, Waiver Wait List, Slot Management, Virginia's assessment tool (VIDES), Support Intensity Scale, and connections to related systems including the DMAS Medicaid Enterprise System, Licensing system, Critical Incident Management System, HCBS Compliance Portal, HCBS Grievance System, and Enterprise Data Warehouse. The document does not specify response deadlines, site visits, bidders' conferences, or award dates within the Q&A responses provided.
The responses clarify several technical and operational parameters for future solicitation. DBHDS will handle cost allocation and separation between Medicaid and non-Medicaid components, so offerors need not structure separate cost estimates for this split. The modernized WaMS or its modules will be subject to CMS Medicaid Enterprise System certification under Streamlined Modular Certification. DBHDS indicated that data quality, validation, and reconciliation functions will not be separated into a distinct component but will be part of the overall platform scope. Connected systems can utilize APIs in the future solution, though the current status of documented APIs versus file-based or manual processes varies across the referenced systems. Reporting obligations will be driven by the Interoperability and Prior Authorization Final Rule, ACCESS Final Rule, HCBS Final Rule measures, and additional State and VITA requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 720-5297- RFI WaMS Modernization_with Updates reflected in Addendum 01_09.01.26.docx | DOCX document | |
| RFI 720-5297_WaMS_Modernization.docx | DOCX document | |
| RFI 720-5297 – Addendum #1 RFI Waiver Management System (WaMS) Modernization.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Offeror Questions
DBHDS Solicitation Number and Name 720-5250-126446 / Waiver Management System (WaMS) Modernization
QUESTION:
RFI PAGE
RFP SECTION/
PARAGRAPH:
QUESTION: DBHDS RESPONSE:
1 N/A N/A
Would DBHDS consider specifying data quality, validation, and reconciliation, for example reconciliation of service authorization awards to Individual Service
Plans and validation of billing against authorized hours, as a separately scoped and separately evaluated component of the future solicitation, so that it may be delivered either by the platform vendor or by a specialized provider working alongside the platform?
No
2 N/A N/A
Does DBHDS anticipate that the modernized WaMS, or individual modules within it, will be subject to CMS Medicaid
Enterprise System certification under
Streamlined Modular Certification? If so, which of the functional areas identified in the RFI does DBHDS expect to fall within certification scope?
Yes, included but not limited to Service Authorization, Individual Support Plan, Waiver Wait List, Slot
Management, Virginian’s assessment (VIDES), Support
Intensity Scale, etc.
3 N/A N/A
How does DBHDS intend to separate
Medicaid and non-Medicaid components, for example Individual and Family Support
Program functions, for cost allocation and enhanced federal financial participation?
Should respondents structure their cost estimates to reflect that split?
No, DBHDS would takes care of this
4 N/A N/A
Of the systems referenced in the Key
Functional Areas table, being DMAS MES, the Licensing system, the Critical Incident
All can be APIs in future solution.
Management System, the HCBS
Compliance Portal, the HCBS Grievance
System, and the Enterprise Data Warehouse, which currently expose documented APIs or standard extracts, and which are file-based or manual today?
5 N/A N/A
Can DBHDS identify the specific reporting obligations driving the transparency and timeliness standards referenced in the
Purpose section, so that respondents can align reporting, audit, and data retention capabilities to those measures?
1. Interoperability and Prior Authorization Final
Rule, ACCESS Final Rule, HCBS Final Rule measures
2. Additional State and VITA requirements
File details come from the government source that posted it. Updated .