Part VI. Quality Assurance and Utilization Control
12VAC30-141-560. Quality assurance.
A. Each provider entity shall meet requirements for the following either as administered by DMAS or as determined by contract with DMAS: access to well-child health services, immunizations, provider network adequacy, a system to provide enrollees urgent care and emergency services, systems for complaints, grievances and reviews, a data management system and quality improvement programs and activities.
B. Each MCHIP shall meet requirements determined by the contract for the internal and external quality monitoring and reporting of access to services, timeliness of services, and appropriateness of services, as determined by DMAS.
Statutory Authority
§§ 32.1-324 and 32.1-325 of the Code of Virginia.
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003.
12VAC30-141-570. Utilization control.
A. Each MCHIP shall implement a utilization review system as determined by contract with DMAS, or administered by DMAS.
B. For the fee-for-service program, DMAS shall use the utilization controls already established and operational in the State Plan for Medical Assistance.
C. DMAS may collect and review comprehensive data to monitor utilization after receipt of services.
Statutory Authority
§ 32.1-325 of the Code of Virginia; 42 USC § 1396 et seq.
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003; amended, Virginia Register Volume 30, Issue 12, eff. March 28, 2014.
12VAC30-141-580. [Reserved].
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003.
12VAC30-141-600. Recipient audit unit.
A. Pursuant to Chapter 9 (§ 32.1-310 et seq.) of Title 32.1 of the Code of Virginia, the recipient audit unit shall investigate allegations of acts of fraud or abuse, committed by persons enrolled in the FAMIS program or the parent, adult caretaker relative, guardian, legal custodian or authorized representative on behalf of a person or persons enrolled in the FAMIS program, which result in misspent funds.
B. Any FAMIS enrollee, parent, adult caretaker relative, guardian, legal custodian or authorized representative of a FAMIS enrollee who, on the behalf of others, attempts to obtain benefits to which the enrollee is not entitled by means of a willful false statement or by willful misrepresentation, or by willful concealment of any material facts, shall be liable for repayment of any excess benefits received and the appropriate interest charges.
C. Upon the determination that fraud or abuse has been committed, criminal or civil action may be initiated.
D. When determining the amount of misspent funds to be recovered, capitation fees shall be included for FAMIS enrollees who received benefits through managed care.
E. Access to FAMIS enrollees' records by authorized DMAS representatives shall be permitted upon request.
Statutory Authority
§§ 32.1-324 and 32.1-325 of the Code of Virginia.
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003.
12VAC30-141-610. [Reserved].
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003.
12VAC30-141-650. Provider review.
A. The provider review unit shall be responsible for reviewing enrolled FAMIS providers to identify potential inappropriate utilization of services and potential billing errors.
B. Providers agree to keep such records as DMAS determines necessary. The providers shall furnish DMAS, upon request, information regarding payments claimed for providing services under the State Plan for Title XXI.
C. Access to records and facilities by authorized DMAS representatives shall be permitted upon request.
D. Providers shall be required to refund payments made by DMAS if they are found to have billed DMAS contrary to policy, failed to maintain records or adequate documentation to support their claims, or billed for medically unnecessary services.
E. A review of adverse actions concerning provider reimbursement shall be heard in accordance with the Administrative Process Act (§ 2.2-4000 et seq. of the Code of Virginia) and the Virginia Administrative Code, 12VAC30-10-1000 and 12VAC30-20-500 through 12VAC30-20-560.
F. MCHIPs shall be responsible for keeping provider profile and utilization mechanisms to monitor provider activities. MCHIPs shall be reviewed by DMAS.
Statutory Authority
§§ 32.1-324 and 32.1-325 of the Code of Virginia.
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003; amended, Virginia Register Volume 23, Issue 7, eff. January 10, 2007.
12VAC30-141-660. Assignment to managed care.
A. Except for children enrolled in the Virginia Birth-Related Neurological Injury Compensation Program established pursuant to Chapter 50 (§ 38.2-5000 et seq.) of Title 38.2 of the Code of Virginia, all eligible enrollees shall be assigned in managed care through the department or CPU. FAMIS individuals, during the preassignment period to an MCHIP, shall receive Title XXI benefits via fee-for-service utilizing a FAMIS card issued by DMAS. After assignment to an MCHIP, benefits and the delivery of benefits shall be administered specific to the managed care program in which the individual is enrolled. DMAS shall contract with MCHIPs to deliver health care services for infants born to mothers enrolled in FAMIS for the month of birth plus two additional months regardless of the status of the newborn's application for FAMIS. If federal funds are not available for those months of coverage, DMAS shall use state funding only.
1. MCHIPs shall be offered to enrollees in all areas.
2. All enrollees shall be assigned to the contracted MCHIPs.
3. Applicants for FAMIS may choose an MCHIP at the time of application. If a choice is not made at application, enrollees shall be assigned through a random system algorithm; provided however, all children within the same family shall be assigned to the same MCHIP.
4. All children enrolled in the Virginia Birth-Related Neurological Injury Compensation Program shall be assigned to the fee-for-service component.
5. Enrolled individuals will receive a letter indicating that they may select one of the contracted MCHIPs that serve such area. Enrollees who do not select an MCHIP as described above, shall be assigned to an MCHIP as described in subdivision 3 of this subsection.
6. Individuals assigned to an MCHIP who lose and then regain eligibility for FAMIS within 60 days will be reassigned to their previous MCHIP.
B. Following their initial assignment to an MCHIP, those enrollees shall be restricted to that MCHIP until their next annual eligibility redetermination, unless appropriately disenrolled by the department.
1. During the first 90 calendar days of managed care assignment, an enrollee may request reassignment for any reason. Such reassignment shall be effective no later than the first day of the second month after the month in which the enrollee requests reassignment.
2. Enrollees may only request reassignment to another MCHIP serving that geographic area.
3. After the first 90 calendar days of the assignment period, the enrollee may only be reassigned from one MCHIP to another MCHIP upon determination by DMAS that good cause exists pursuant to subsection C of this section or for any reason at annual renewal.
C. Disenrollment for good cause, defined in 12VAC30-120-370, may be requested at any time.
1. After the first 90 calendar days of assignment in managed care, enrollees may request disenrollment from DMAS based on good cause. The request must cite the reasons why the enrollee wishes to be reassigned. The department shall establish procedures for good cause reassignment through written policy directives.
2. DMAS shall determine whether good cause exists for reassignment.
Statutory Authority
§ 32.1-325 of the Code of Virginia; 42 USC § 1396 et seq.
Historical Notes
Derived from Virginia Register Volume 19, Issue 21, eff. August 1, 2003; amended, Virginia Register Volume 22, Issue 8, eff. April 3, 2006; Volume 25, Issue 16, eff. May 13, 2009; Volume 25, Issue 25, September 16, 2009; Volume 30, Issue 12, eff. March 28, 2014; Volume 35, Issue 20, eff. June 26, 2019.