SOW- draft.docx

Statement of Work (SOW) Payer Compliance Tool (PCT)

Introduction and Background Purpose The purpose of this Statement of Work (SOW) is to outline the requirements for procuring a VA Community Care Payer Compliance Tool (PCT) for the Department of Veterans Affairs (VA). This tool is needed to mitigate ongoing risks of undetected improper payments within VA Community Care healthcare claims payments.

Background The VA Community Care program has seen significant growth over the past several years, driven by the passing of the VA Mission Act, PACT Act, and the Elizabeth Dole Act, as well as an increase in the number of Veterans eligible for VA care. This surge in demand has led to Veterans utilizing VA Community Care at higher rates each year, necessitating a robust system for payment integrity and improper payment detection.

The current post-payment analysis for improper claims detection and validation process face numerous challenges. The Payment Integrity teams lack the technological enablement to handle the scale and volume of claims processed. Currently, these processes rely heavily on manual data analysis and specific monitoring capabilities for improper payments. Consequently, the program is unable to systematically and comprehensively scan the entire claims dataset to isolate improper payments in the aggregate. Furthermore, these manual and retrospective analyses often result in the identification of improper payments only after payments have been rendered, sometimes long after the transactions have occurred. This delay hampers the VA's ability to take timely corrective actions, complicates recoupment efforts, and ultimately affects the overall efficiency, accuracy, and compliance of healthcare delivery.

The primary goal of implementing the VA PCT within VA Community Care is to leverage advanced technology and systems to timely identify improper payments, including potential fraud, waste, and abuse (FWA). By deploying this tool, the VA aims to mitigate potential overpayments and ensure that all healthcare claims are processed accurately and compliantly. The PCT will address the identified challenges by providing a comprehensive solution for analyzing and validating the entire universe of VA Community Care claims data. This system will enable the VA to systematically identify improper payments in a timely manner, enhancing overall payment integrity.

The key stakeholders involved in this project include Payment and Business Integrity within Integrated Veteran Care. These teams are responsible for identifying improper payments, coordinating with relevant stakeholders on corrective action plans, and managing recoupment or offset activities to uphold the VA’s fiduciary responsibilities. This project will greatly benefit several stakeholder groups. Veterans will receive enhanced quality of care through accurate and timely payment and reimbursement processing. Healthcare providers will benefit from timely and correct payments, reducing the administrative burden associated with resolving payment disputes and recoupments. VA staff will experience streamlined workflows, allowing them to focus on higher-value activities, such as analyzing complex cases and developing strategies to prevent future improper payments.

The outcomes and impacts expected with the implementation of the PCT are clear: identify improper payments and potential FWA quickly and efficiently. The VA anticipates significant potential cost savings and cost avoidance through the early detection and prevention of improper payments. Additionally, the PCT will enable VA teams to react swiftly and work with various internal and external stakeholders on mitigation strategies to prevent future improper payments and, if applicable, offset or recoup improperly paid funds. To ensure the success of the PCT project, several key outcomes will be measured and evaluated regularly. These include the detection of improper payments, cost savings and avoidance, timeliness of detection, stakeholder engagement, and the efficiency of recoupment efforts. Regular progress reports, performance metrics, and stakeholder feedback will be utilized to evaluate these outcomes and ensure continuous improvement of the PCT system and processes.

Scope Overview of Project Scope The VA Payer Compliance Tool (PCT) is intended to enhance the VA’s ability to detect improper payments and ensure proper payment integrity and compliance with established reimbursement policies and guidelines. The project entails the design, development, deployment, and ongoing support of a scalable and efficient PCT that integrates with existing VA systems, ingests a wide variety of claims and healthcare data, and leverages advanced analytics and machine learning to identify improper payments.

Key Objectives The key objectives of this project include:

· Ensure Compliance: Validate claims post-adjudication against CMS and VA pricing, coding/billing, coverage, and business rules to ensure compliance.

· Enhance Efficiency: Automate post-payment auditing processes to transition from manual and retrospective approaches to proactive, scalable, and efficient methods.

· Detect Improper Payments: Utilize advanced analytics, machine learning, and AI to identify improper payments, including fraud, waste, and abuse at various levels (claim, provider, patient, and service).

· Improve Data Utilization: Aggregate, parse and normalize data from diverse sources to facilitate comprehensive analysis and ensure consistency.

· Provide Actionable Insights: Develop dashboards and reporting tools to give VA staff the visibility needed to manage flagged issues, track potential savings, and support decision-making processes.

· Support Continuous Improvement: Incorporate Human-in-the-Loop (HITL) learning and other feedback mechanisms to refine and improve AI models, rules logic, and overall system performance.

· Integrate Seamlessly: Ensure seamless integration with existing VA systems via APIs or other secure methods for data sharing and interoperability.

Functionality and Feature Requirements Data Ingest The tool must have the ability to receive and parse 837P, 837I, and 837D post-adjudicated internal claims history, and ingest data from various sources such as, but not limited to, CMS Physician Specialty Code Set, NPPES/PECOS specialty files, OIG LEIE list, CMS Frequency/utilization reports, Prospective Payment Systems (PPS), CMS/VA Fee schedules, VA eligibility systems, referral/authorization systems, provider file information, and other relevant healthcare databases. The tool should gather data from diverse sources, including healthcare claims data, eligibility system, referral/authorization system, provider file information, and other relevant databases as needed. The tool should aggregate, parse, and normalize this data to ensure consistency and facilitate comprehensive analysis.

Rule Engine All ingested claims must be processed through the rule engine based on their specific types to ensure accurate validation. The tool must have a customizable logic engine capable of executing and continuously updating rules, including but not limited to, CMS edits, PPS logic, VA business rules, and Fee Schedule validations. The engine must support rule threshold tuning (e.g., frequency limits, provider specialties) to adapt to ever-changing rules and coverage criteria and ensure accurate and up-to-date compliance. The system must apply different sets of rules based on the type of claim and service provided. The rule engine must execute rules in real-time as claims are ingested to identify improper payments, errors, or anomalies efficiently. Each type-specific rule must validate claims against applicable business rules, fee schedules, and other industry standards. The system must allow for the prioritization and sequencing of rules to ensure critical rules are applied first, followed by secondary checks. The system must provide access to supporting information for each rule, including but not limited to, the necessary statutes, CMS guidelines/manual sections that justify and explain the rule's implementation. This documentation should be easily accessible and clearly linked to the corresponding rules to ensure transparency and ease of reference for users.

The system must integrate with a comprehensive set of compliance rules to ensure alignment with VA, CMS, and contractual reimbursement policies and guidelines. This includes, but is not limited to, CMS compliance edits such as NCCI, MUE, MPPR, global surgical package rules, etc.; VA-specific policies including VA Payment Policies, Clinical Determinations and Indications guidelines, and other VA reimbursement guidelines. The system must incorporate relevant industry standards and guidelines for correct coding compliance, such as AMA coding manuals, X12 standard edits, Strategic National Implementation Process (SNIP) edits, and other authoritative coding references. The system must incorporate additional industry rules and edits to ensure compliance with all applicable statutes, regulations, and reimbursement frameworks to facilitate the identification of improper claims adjudication. The system must account for geographic adjustments and apply any local rules specific to different regions or provider types.

The system must have built-in modules for key prospective payment systems (PPS) to ensure accurate pricing and compliance. These modules must include, at a minimum, IPPS, OPPS, SNF PPS, IRF PPS, and ESRD PPS. The system must utilize these modules to price claims accurately according to the respective payment system guidelines. Additionally, the system must check pricing against CMS, CMS Medicare Administrative Contractor (MAC), CMS/MAC Critical Access Hospital rates, VA Fee Schedules, and CHAMPUS Maximum Allowable Charge (CMAC), including any necessary geographic adjustments.

Pattern Recognition Engine The payer compliance tool must analyze post-adjudicated claims at the provider, patient, and service levels to identify billing behaviors inconsistent with peer norms and other suspicious billing activity, such as but not limited to, excessive use of unlisted/NOC codes, high-frequency repeat procedures, modifier misuses, and billing outside provider specialty norms. The tool shall incorporate artificial intelligence (AI) and machine learning (ML) capabilities to support scalable, accurate, and proactive detection of improper payments effectively including but not limited to:

· Anomaly Detection Models: To identify billing outliers, unusual claim patterns, and provider behavior inconsistent with peer benchmarks.

· Predictive Modeling: To score the likelihood of improper payments at the claim, provider, and facility levels.

· Dynamic Rules Engine: That leverages both static business rules and continuously updated ML models to improve detection accuracy over time.

· Adaptive learning: Utilize AI/ML patterns to frequently retrain and adapt based on new data, improving accuracy in detecting improper payments and ensuring compliance with evolving standards.

· Human-in-the-Loop Learning: The system shall support a feedback loop where human reviewers can confirm or dismiss AI-generated flags, with outcomes logged and used to retrain and refine future model performance.

· Tagging of Cases: Enabling user tagging of cases for further model review or escalation.

· Explainability and Transparency: Include Explainable AI (XAI) features that provide plain-language reasoning for why claims or providers are flagged by the system, ensuring transparency and audit-readiness.

· Continuous Improvement: Supporting the continuous improvement of both AI models and rules logic based on investigator outcomes.

The contractor will continuously evaluate and monitor these capabilities, including:

· Regular Reporting: On false positives, model drift, and financial impact.

· Retraining Schedule: Featuring a quarterly retraining schedule based on labeled investigator outcomes.

· Bias Mitigation: Implementing mechanisms to ensure that AI recommendations do not introduce bias based on provider location, specialty, or population served.

Rule Flags and Workflow The system must flag improperly paid procedures based on rules that have fired, and support efficient resolution workflows for investigating flagged claims/activities. This includes providing clear escalation pathways for further review and resolution of potential issues. The system must ensure that all rule flags have their own dedicated dashboards and workflows that VA staff can review, providing organized and user-friendly interfaces for detailed investigation and resolution of flagged issues. The system must support integration with other tools and systems within the VA via APIs or other secure connection methods, enabling seamless data sharing and interoperability. Additionally, the system must include features for exporting data/dashboards and specific claims related to fired rules and flagged issues, to facilitate comprehensive analysis, resolution, and reporting across the VA.

Recoupments The tool shall ingest and track recoupment data, tying each recoupment to the original improper payment. The system should integrate with existing VA systems and technologies to ensure accountability by maintaining detailed records of findings versus recoupments realized by VA, providing clear traceability and reconciliation of improper payments.

Audit and Cost Savings Tracking The system must provide full documentation of fired rules, including the logic, claim line items affected, and the financial impact of each. This comprehensive audit trail must be maintained to ensure transparency, accountability, and traceability of all rule applications and their outcomes. The audit trail must document fired rules, rule logic, claim line items affected, and financial impact for each claim. The system must include dashboards that display flagged improper payments and potential savings calculations. Maintain traceability from claim ingestion through rule application, flagging, investigation, and resolution, ensuring clear and detailed reporting. Dashboards should facilitate effective monitoring and management of flagged issues, offering insights and streamlined access to necessary information for timely and accurate resolution. The system must include features to track and analyze costs associated with claims processing, flagging, and resolution. The system should provide tools for performing ROI analysis, demonstrating the financial impact and benefits of the PCT, including cost savings, recovered payments, and efficiency gains.

Security and Access Control The system must implement role-based permissions to ensure that users have appropriate access levels based on their roles and responsibilities. The system must be compliant with Personally Identifiable Information (PII) regulations to safeguard sensitive data. The system must maintain detailed audit logs to record and monitor all user activities, ensuring accountability and traceability. Implement advanced security protocols, including encryption for data in transit and at rest, to safeguard sensitive information. Continuously monitor and ensure compliance with relevant data privacy and security regulations, including HIPAA, FISMA, and other federal standards.

User Interface and Usability The system must provide an intuitive and user-friendly interface that facilitates easy navigation and use for all types of users, including auditors, analysts, and administrators. Users should be able to customize dashboards to display relevant data and metrics according to their specific needs and roles.

Data Quality and Integrity The system must perform data validation and integrity checks to ensure the accuracy and completeness of the ingested data. The system should be able to handle updates to data sources and ensure that changes are accurately reflected in analyses and reports.

Collaboration and Communication The system must include collaborative tools, such as but not limited to, commenting, task assignment, and notifications, to facilitate communication and teamwork among users. The system should have the ability to integrate with VA communication platforms to streamline workflows and ensure timely notifications. Generate real-time notifications and alerts for flagged claims and potential issues, enabling timely intervention and resolution. Allow users to customize alert settings and notification preferences based on their roles and priorities.

Training and Support The vendor must provide comprehensive training programs, including initial onboarding, ongoing training sessions, and access to training materials for new users. The system must include an easily accessible knowledge base and help resources, such as FAQs, tutorials, and troubleshooting guides, to provide users with self-service support options. The vendor must offer dedicated support services, including technical support, troubleshooting, and system maintenance, to ensure continuous and reliable operation.

Disaster Recovery and Business Continuity The system must include robust backup and recovery processes to ensure data integrity and availability in case of system failures or disasters. The vendor must provide a business continuity plan to ensure that the system remains operational and accessible during unforeseen events or disruptions.

Integration and Interoperability The Payer Compliance Tool (PCT) must integrate seamlessly with existing VA systems, including financial systems, corporate data warehouses, eligibility systems, referral/authorization systems, and provider information systems. This integration should ensure real-time synchronization of data, maintaining consistency and accuracy across all platforms. By supporting real-time data feeds, the PCT will provide up-to-date information essential for effective decision making and detection of improper payments.

To ensure interoperability with other healthcare systems and datasets, the PCT must employ standards-based integration. It should utilize established protocols such as Health Level Seven (HL7) and Fast Healthcare Interoperability Resources (FHIR). Furthermore, the system must incorporate industry standard edits, including CMS, VA, X12 standard edits and Strategic National Implementation Process (SNIP) edits, for precise and compliant claims processing.

The tool must also provide robust APIs to allow secure access to its data and functionalities from other systems. These APIs will facilitate broader analytics and reporting efforts by enabling seamless data sharing. Secure connection methods, such as data encryption and secure communication protocols, are essential to protect data integrity and security during interactions between the PCT and other systems.

Additionally, the PCT must be capable of integrating with relevant external databases. It should support the ingestion of data from these external sources and enable the export of system data to external databases, supporting comprehensive analysis and reporting.

Finally, scalability and performance monitoring are critical. The PCT must be designed with a scalable architecture that can handle increasing data volumes and transactions without performance degradation. Performance monitoring tools should be included to track and optimize system performance, ensuring efficient load balancing, quick response times, and optimal resource utilization.

Compliance and Security Standards The Payer Compliance Tool (PCT) must adhere to stringent compliance and security standards to ensure the integrity and confidentiality of sensitive healthcare data. The system must be compliant with relevant federal laws and regulations, including the Health Insurance Portability and Accountability Act (HIPAA) and the Federal Information Security Management Act (FISMA), among other federal standards.

To safeguard sensitive data, the PCT must employ advanced security measures, including but not limited to data encryption for information both in transit and at rest. This ensures that sensitive information is protected from unauthorized access and breaches.

Role-based access control is essential to ensure that users have appropriate access levels according to their roles and responsibilities within the system. This minimizes the risk of data breaches and ensures that critical functions and data are only accessible to authorized personnel. The system should log all user activities in detailed audit logs to provide a comprehensive trail of actions taken within the system, ensuring accountability and traceability.

The PCT must continuously monitor and ensure compliance with all relevant data privacy and security regulations. This includes implementing necessary controls and performing regular audits to verify compliance. Additionally, the system should include tools for regulatory compliance monitoring, ensuring adherence to evolving regulations and standards.

The vendor must deliver a business continuity plan to ensure the system remains operational and accessible during unforeseen events or disruptions. Robust backup and recovery processes must be implemented to ensure data integrity and availability in case of system failures or disasters.

Performance and Scalability The Payer Compliance Tool (PCT) must be designed with robust performance and scalability in mind to accommodate the growing volume and complexity of VA Community Care claims. The system should employ a scalable architecture capable of handling increasing data volumes and transaction loads without compromising performance or responsiveness. To ensure optimal performance, the PCT must include performance monitoring tools that track key metrics such as load balancing, response times, and resource utilization. These tools will enable continuous optimization of system performance, ensuring that the system remains efficient and effective even under high load conditions.

Load balancing capabilities are essential to distribute processing loads evenly across the system, preventing bottlenecks and ensuring smooth operation during peak usage times. The system should be able to dynamically allocate resources based on current demands to maintain high performance levels. The PCT must also include tools for real-time performance monitoring to detect and address any issues promptly. This ensures that potential performance degradation can be identified and mitigated before it impacts system usability or user experience.

To support scalability, the system should be easily expandable to accommodate future growth in data volumes, transaction loads, and user numbers. This includes the ability to integrate additional data sources, handle more complex processing tasks, and support a larger user base as needed. Furthermore, the system must be designed to support high availability and reliability. This includes implementing redundancy measures and failover mechanisms to ensure that the system remains operational even in the event of hardware or software failures.

Vendor Responsibilities and Deliverables System development and Customization The vendor will be responsible for the design and development of the PCT, ensuring that it meets all specified requirements and integrates seamlessly with existing VA systems. The vendor must work closely with VA stakeholders to tailor the system according to VA-specific processes, workflows, and rules. This includes creating, modifying, and implementing custom rules and workflows as needed.

Training The vendor must provide comprehensive training programs to ensure that all users are proficient in using the PCT. This includes initial onboarding training, role-specific training sessions, and ongoing education to keep users informed of system updates and new features. The vendor must deliver detailed training materials, including user manuals, video tutorials, and quick reference guides, to support the user experience and facilitate self-service learning.

User Support and Documentation The vendor must offer dedicated support services, including technical support, troubleshooting, and system maintenance. This support should be available through multiple channels such as phone, email, and online support portals. The vendor must develop an easily accessible knowledge base containing FAQs, tutorials, troubleshooting guides, and other help resources to provide users with self-service support options.

Business Continuity and Disaster Recovery The vendor must implement robust backup and recovery processes to ensure data integrity and availability in case of system failures or disasters. The vendor must provide a detailed business continuity plan to ensure that the PCT remains operational and accessible during unforeseen events or disruptions.

Regular Updates and Enhancements The vendor must routinely update the system to incorporate the latest CMS and VA updates, technological advancements, security enhancements, and compliance with regulatory changes. This includes both scheduled updates and urgent patches. The vendor must incorporate feedback from VA users to continuously improve the system’s functionality, usability, and performance.

Performance and Compliance Monitoring The vendor must conduct regular audits to ensure the system’s compliance with relevant regulations and standards. This includes security audits, performance evaluations, and reviews of system usage. The vendor must provide regular performance and compliance reports to VA, detailing key metrics such as system uptime, response times, user activity, and compliance status.

Project Management The vendor must develop a comprehensive project plan that outlines the timeline, milestones, and deliverables for the PCT implementation. The vendor must provide regular progress reports to VA stakeholders to keep them informed of the project status and any potential issues or delays.

Project Management and Timeline The vendor selected for implementing the Payer Compliance Tool (PCT) must follow a structured project management approach to ensure the successful delivery and deployment of the system. This section outlines the key phases, activities, and timeline milestones required for the project.

Initiation Conduct a project kickoff meeting to introduce key stakeholders, define roles and responsibilities, and review project objectives and deliverables. Collaboratively gather and clarify all requirements, ensuring alignment with VA needs and objectives.

Planning Create a detailed project plan, including timeline, milestones, resource allocation, and risk management strategies. Define a stakeholder engagement plan to maintain regular communication and updates throughout the project lifecycle.

Design Develop detailed system design documentation, including architecture, integration points, and user interface design. Present the system design to VA stakeholders for review and obtain necessary approvals.

Development Execute the development of the PCT according to the approved design, ensuring adherence to technical and functional requirements. Implement any VA-specific customizations, workflows, and rules as identified during the requirements gathering phase.

Testing Conduct unit testing to verify the functionality of individual components. Perform integration testing to ensure seamless interaction between the PCT and existing VA systems. Facilitate UAT with VA stakeholders to validate the system against business requirements and obtain feedback for any necessary adjustments.

Deployment Develop a comprehensive deployment plan detailing the steps, timeline, and contingency measures for the system go-live. Execute the deployment plan to launch the PCT into the production environment. Provide immediate post-deployment support to address any issues encountered during the initial usage phase.

Training Deliver training programs to ensure all users are proficient in the system's functionality. Provide comprehensive training materials, including user guides, video tutorials, and quick reference guides.

Maintenance and Support Offer ongoing technical support, system maintenance, and regular updates to ensure the system remains functional and up-to-date. Establish a feedback loop to continually improve the system based on user input and changing requirements.

Evaluation Criteria Technical Approach and Methodology: Demonstration of a thorough understanding of the VA’s requirements, objectives, and challenges. Clarity, feasibility, and completeness of the proposed technical solution, including system architecture, integration approach, and compliance with requirements. Incorporation of innovative approaches, industry best practices, and advanced technologies to enhance the solution’s effectiveness.

Experience and Expertise: Demonstrated experience in developing and implementing similar payer compliance tools or healthcare analytics systems. Familiarity with healthcare industry standards, compliance requirements, and reimbursement guidelines (e.g., CMS, VA policies). Qualifications, skills, and experience of the proposed project team, including technical, project management, and support staff.

Project Management and Execution: Detailed project plan outlining phases, activities, milestones, and timelines for the project’s successful execution. Identification of potential risks and proposed mitigation strategies to ensure project success. Effective communication and stakeholder engagement plan to maintain alignment with VA needs throughout the project lifecycle.

System Functionality and Performance: Degree to which the proposed solution meets the specified requirements, including data ingest, rule engine, compliance checks, PPS modules, audit trail, savings tracking, and security. Ability of the system to scale and perform efficiently under increasing data volumes and transaction loads. Design and usability of the system’s interface to ensure a positive user experience for all roles.

Integration and Interoperability: Capability to integrate seamlessly with existing VA systems and external databases. Support for standards-based integration protocols (e.g., HL7, FHIR) to ensure interoperability with other healthcare systems and datasets.

Compliance and Security: Adherence to all relevant compliance and security standards, such as HIPAA, FISMA, and VA policies. Implementation of robust security measures to protect sensitive data and ensure data integrity.

Training and Support: Comprehensive training programs and materials to ensure user proficiency. Availability of dedicated support services, including technical support, troubleshooting, system maintenance, and regular updates.

Cost and Value: Detailed cost proposal, including all fees, expenses, and potential additional costs. Overall value offered by the proposal, considering the cost, quality, and anticipated benefits of the solution.

Vendor Reputation and References: Assessment of the vendor’s reputation and track record in delivering similar projects. Positive references from previous clients, demonstrating successful implementations and satisfied customers.