An EVV Proprietary System is an approved EVV system that a program provider or financial management services agency (FMSA) may use instead of the state provided EVV system and:
- Has been purchased or developed by a program provider or an FMSA.
- Is used to exchange EVV data with the EVV Aggregator.
- Complies with HHSC EVV Policy as it relates to EVV proprietary systems.
- Complies with the HHSC EVV Business Rules for proprietary systems.
- Complies with the requirements of 1 Texas Administrative Code (TAC) § 354.4009 (Part 15, Chapter 354, Subchapter O, Electronic Visit Verification).
- Complies with the requirements of Texas Government Code (TCG) § 532.0251 (Chapter 532, Subchapter F).
An EVV Proprietary System Operator (PSO) is a program provider or FMSA that is approved to operate an EVV proprietary system.
Refer to the EVV Policy Handbook, including Section 5000, for more information.
EVV PSO Onboarding Process
Step 1: Submit an EVV Proprietary System Request Form
Program providers and FMSAs that select to use an EVV proprietary system instead of the state provided EVV system must complete, sign, and submit the EVV Proprietary System Request Form located in the EVV Portal to start the PSO onboarding process.
Note: Program providers and FMSAs that select to transfer to a new EVV proprietary system from the state provided EVV system or from a different proprietary system must submit an EVV Proprietary System Request Form.
Program providers and FMSAs must have EVV Portal access to submit a request form. HHSC and TMHP will not accept forms that are emailed. For information on how to access the EVV Portal, refer to the Accessing the EVV Portal for Program Providers and FMSAs job aid.
After the request form is submitted, program providers and FMSAs receive a confirmation number (Request Form ID) and a confirmation date and time (Request Form Submission Date and Time).
For instructions on submitting an EVV Proprietary System Request Form, refer to the EVV Proprietary System Request Form Job Aid located in the TMHP Learning Management System (LMS).
Note: The submission of a request form does not guarantee an assignment to a PSO Operational Readiness Review (ORR) session. TMHP will notify program providers and FMSAs of their assignment status after the request form and PSO ORR session requirements are reviewed and validated.
EVV PSO Onboarding Paths
On the EVV Proprietary System Request Form, program providers and FMSAs must select an onboarding path based on the EVV system they have chosen:
- The standard path is for program providers that are requesting approval to use an EVV system that has not been previously approved.
Important: TMHP strongly encourages proprietary system vendors that are preparing for demonstrations during the Standard Path ORR to consider all EVV system functionality that onboarding program providers or FMSAs may require to support their EVV-required service delivery. A program provider or FMSA that wants to onboard with a proprietary system that hasn’t been approved for EVV functionality that the program provider or FMSA requires must complete a modified Standard Path ORR with the proprietary system vendor to get approval to use the new functionality.
- The expedited path is for program providers that are requesting approval to use an EVV system that has already been approved and is operational.
Important: Program providers and FMSAs must contact the selected EVV proprietary system vendor and confirm their availability to participate in an expedited path before submitting the request form.
Note: The Approved EVV Proprietary Systems document lists the approved EVV proprietary systems for expedited onboarding.
Step 2: Complete the ORR Session
TMHP will assign the program provider or FMSA to an ORR session after reviewing and approving the EVV Proprietary System Request Form. The ORR session is a validation process to determine approval for a PSO. Depending on the availability of sessions, TMHP may add the program provider or FMSA to a waitlist for the next open ORR session.
Note: TMHP may request that the program provider or FMSA provide additional information about what they entered on an EVV Proprietary System Request Form. The program provider or FMSA must provide the requested information before TMHP can assign them to an ORR.
EVV ORR Sessions
The following PSO Onboarding Process Overview and Timeline documents outline the steps and timeframes that are required for a program provider or FMSA to onboard their EVV proprietary system in the Texas EVV operating environment that is managed by HHSC and TMHP:
- EVV PSO Onboarding Overview and Timeline Standard Path Process
- EVV PSO Onboarding Overview and Timeline Expedited Path Process
The final submission date of the EVV Proprietary System Request Form and the availability of ORR session slots determine ORR session assignment. TMHP will contact program providers and FMSAs that submitted an EVV Proprietary System Request Form when they have been assigned to an ORR Session.
View the high-level schedule for PSO onboarding in 2025 and early 2026 in the following table:
Session | Slots Available | Planning Meeting Date | ORR Start Date | Session Approval Date | Earliest Go-Live Date |
---|---|---|---|---|---|
2025-1: Standard | 3 PS vendors | Jan. 21, 2025 | Feb. 3, 2025 | Mar. 19, 2025 | May 1, 2025 |
2025-2: Standard | 10 PS vendors | Apr. 15, 2025 | April 28, 2025 | Jun. 11, 2025 | Jul. 15, 2025 |
2025-3: Expedited | 200 program providers or FMSAs | Jul. 1, 2025 | Jul. 7, 2025 | Aug. 4, 2025 | Sept. 1, 2025 |
2025-4: Standard | 10 PS vendors | Sept. 9, 2025 | Sept. 22, 2025 | Nov. 28, 2025 | Dec. 1, 2025 |
2025-5: Expedited | 200 program providers or FMSAs | Jan. 6, 2026 | Jan. 12, 2026 | Feb. 9, 2026 | Mar. 15, 2026 |
Important: TMHP has a limited number of slots based on the available capacity. The schedule is subject to change.
A program provider or FMSA must have developed a compliant EVV proprietary system that meets all requirements by the ORR start date.
Refer to the PSO Business Rules to learn more about the compliance standards for EVV proprietary systems in Texas Medicaid.
EVV Proprietary System Maintenance
PSOs are fully responsible for the ongoing maintenance and compliance of their EVV proprietary systems.
The PSO must ensure that updates to the EVV proprietary system that conflict with any EVV standards and policy requirements are completed and approved. The PSO must inform HHSC and TMHP within two business days of discovery if the EVV proprietary system is not compliant with any EVV standards and policy requirements. The PSO must inform TMHP of any planned system changes that alter an approved component of the EVV proprietary system. Depending on the nature of the change, TMHP may need to approve the change before the PSO implements it.
HHSC may modify EVV standards and policy requirements, including the HHSC EVV Business Rules for Proprietary Systems. HHSC will notify PSOs of any such changes. The PSO must ensure that the EVV proprietary system complies with the latest versions of policy and the HHSC EVV Business Rules for Proprietary Systems within the approved time frame and that the system receives proper certification.
HHSC will specify a time frame to update the EVV proprietary systems with changes that result from modifications to policies, requirements, and HHSC EVV Business Rules for Proprietary Systems. HHSC typically provides a minimum of 90 calendar days to complete the modifications that are necessary to comply with updated standards and requirements but may provide a different time frame depending on the nature of the change. If HHSC requires an emergency system or policy change, HHSC and the PSO will mutually agree on an earlier effective date. HHSC may require that changes be made in less than 90 days if the change concerns an immediate need. The PSO must meet with the EVV proprietary system vendor to address an immediate need.
The PSO must ensure that the EVV proprietary system vendor meets all required deadlines related to ongoing maintenance.
TMHP will assist the PSO in resolving production problems in their EVV proprietary system that are related to data exchange with the EVV Aggregator, as needed.