Amida Technology Solutions, Inc. has launched Saraswati, a cloud-native healthcare quality measurement platform designed to give health plans, managed care organisations and state Medicaid programmes near-real-time visibility into HEDIS performance. Announced on July 22, 2026, the platform continuously recalculates digital quality measures as new healthcare records arrive, allowing quality teams to identify performance gaps before the annual reporting and audit cycle closes.
The launch addresses a long-standing operational weakness in healthcare quality measurement. HEDIS scores may influence benchmarking, contracting, plan ratings and quality-improvement priorities, yet many organisations still rely on reporting processes that reveal performance problems months after the underlying care occurred. Saraswati attempts to move HEDIS from a retrospective compliance exercise into a year-round management function.
That distinction matters. A platform that calculates measures faster does not automatically improve care, raise ratings or increase quality-linked payments. Its value will depend on whether health plans can connect reliable data, interpret emerging gaps correctly and turn the resulting information into timely interventions involving providers and members.
Why does real-time HEDIS measurement matter when health plans already submit annual quality reports?
HEDIS is among the most widely used healthcare performance measurement systems in the United States. The National Committee for Quality Assurance says more than 235 million people are enrolled in health plans that report HEDIS results, with the measurement set covering more than 90 measures across areas including effectiveness of care, access, patient experience and healthcare utilisation.
Traditional HEDIS operations frequently concentrate significant effort around data collection, measure calculation, validation, remediation, audit preparation and final submission. Amida said health plans commonly collect data during the first part of the year, undergo audits during the summer and receive final ratings later in the year. This creates a lag between the care being measured and the point at which decision-makers gain a consolidated view of performance.
The strategic argument behind Saraswati is that plans should not wait for the reporting season to discover that a preventive screening measure, follow-up measure or chronic-disease indicator is moving in the wrong direction. Earlier visibility could give quality teams more time to investigate missing records, contact providers, support member outreach or direct resources toward populations with widening care gaps.
The practical difference is similar to replacing an annual financial close with a continually refreshed management dashboard. The annual audited result still matters, but managers no longer need to operate for most of the year without a current performance view.
What does Saraswati calculate from claims, clinical, enrolment and FHIR-based healthcare data?
Saraswati continuously ingests information from claims, encounters, enrolment systems, clinical sources and data structured using Fast Healthcare Interoperability Resources, commonly known as FHIR. Amida says the platform calculates 76 National Committee for Quality Assurance-certified measures for Measurement Year 2025 and uses Clinical Quality Language to execute measure logic.
The platform provides views across measures, health plans, geographical areas and population groups. Users can examine results at the member level, compare managed care organisation performance, assess trends against benchmarks and filter results by demographic characteristics or clinical categories.
Amida has also positioned predictive analytics as an important part of the platform. Rather than displaying only a current calculated rate, Saraswati is intended to identify measures that may be at risk before the measurement year ends. Chief architect Mike Hiner said the system was designed to let analysts observe score changes, compare managed care organisations and act while there is still time to affect the final reporting period.
This forecasting layer could become one of Saraswati’s most commercially useful features, but it also requires careful interpretation. A projected measure outcome depends on the completeness and timeliness of incoming records, assumptions about remaining eligible members and the platform’s treatment of data that have not yet been received or reconciled.
A health plan could therefore see an apparently weak measure because care was not delivered, because the relevant clinical data have not arrived or because records from different systems have not been matched correctly. Saraswati’s effectiveness will depend not only on its measure engine, but also on the quality of the pipelines feeding it.
How should health plans interpret Amida’s speed, uptime and remediation claims?
Amida reported that Saraswati can process two million records per hour, maintain 99.9 percent uptime and deliver results in fewer than four hours. The company also said teams using the platform have experienced a 30 percent faster path to National Committee for Quality Assurance submission through the Integrated Data Submission System and a 75 percent reduction in remediation cycle time.
These figures suggest that the platform has been built for large payer datasets and frequent recalculation rather than occasional reporting runs. For health plans managing several products, states or managed care contracts, the ability to rerun measures rapidly could reduce the operational friction created by data corrections and late-arriving records.
However, the announcement did not disclose the number of organisations behind the reported efficiency improvements, the baseline workflows used for comparison or whether the figures were evaluated independently. It is also unclear whether the remediation result applies across full enterprise deployments, selected measures or controlled implementation settings.
The distinction is important because processing speed is a technical performance measure, not evidence that members received better care. Similarly, uptime demonstrates platform availability but does not establish data completeness, calculation accuracy in each client environment or successful adoption by quality teams.
Prospective customers will therefore need to examine deployment references, implementation timelines, data volumes, audit outcomes and performance under their own operating conditions. The commercial proof will come from repeatable improvements across multiple plans, not from maximum processing capacity alone.
Why does NCQA measure certification matter without proving clinical or financial outcomes?
The National Committee for Quality Assurance’s Measure Certification programme assesses whether software logic correctly calculates quality measures. Vendors process test datasets containing member-level scenarios, and the organisation compares the resulting numerators, denominators, exclusions and risk adjustments with expected results. Software passes when its code computes the measures correctly.
That certification is strategically important because HEDIS reporting requires consistency and comparability. Health plans submitting HEDIS rates generally need to use certified vendor logic or certify their own code through the applicable review process. Certified software can also reduce the burden associated with validating calculation code.
Certification does not remove every implementation risk. The National Committee for Quality Assurance notes that auditors may still examine organisation-to-vendor field mapping, data cleansing routines, coding issues and other data-integrity concerns that fall outside the certified calculation logic.
In practical terms, Saraswati may correctly calculate a measure using the data supplied while still producing an incomplete operational picture if the underlying records are delayed, duplicated, incorrectly mapped or missing. The certification validates an essential part of the system, but it does not certify a health plan’s entire data environment or guarantee higher ratings.
It also does not establish that using the platform improves patient outcomes, lowers medical costs or generates quality bonus payments. Those results would require evidence linking faster measurement to successful interventions and measurable changes in care delivery.
Can Saraswati close healthcare gaps or does it primarily identify where intervention is required?
Amida describes Saraswati as a platform that can surface care gaps, identify disparities and allow users to drill into individual member records. It can also segment performance by age, race, ethnicity, geography and condition category, potentially giving quality teams a more precise view of where performance is weakening.
This can be operationally valuable because aggregate rates often conceal substantial differences between providers, populations and regions. A plan may perform well overall while underperforming among members with behavioural health needs, residents of a particular county or patients attributed to specific provider groups.
Nevertheless, identifying a gap is only the first step. Closing it may require accurate provider contact information, member engagement, appointment availability, transportation, culturally appropriate communication, clinical capacity and cooperation across multiple organisations. Some gaps may also reflect documentation or interoperability problems rather than missing care.
Saraswati should therefore be understood as decision-support infrastructure rather than an autonomous quality-improvement solution. It can help organisations decide where to investigate and intervene, but it does not replace clinical judgement, provider operations or member-facing programmes.
The strongest deployment model would connect the platform’s member-level findings to established workflows for case management, provider engagement, care coordination and outreach. Without those connections, even highly current measurement may become another dashboard that accurately describes a problem without changing it.
What data integration and governance barriers could limit Saraswati adoption?
Near-real-time measurement requires near-real-time access to usable data. Claims, enrolment, laboratory, pharmacy, encounter and electronic health record systems were often developed for different purposes, use different identifiers and update on different schedules.
Health plans implementing Saraswati will need to map these sources into a consistent model, resolve duplicate or conflicting records and establish controls for data lineage and versioning. They will also need to determine how corrected records affect previously calculated results and how users can trace a measure back to its supporting evidence.
FHIR can make healthcare data exchange more standardised, but adoption remains uneven across organisations and data types. The National Committee for Quality Assurance’s digital HEDIS framework uses FHIR and Clinical Quality Language to provide computable, interoperable measure specifications, reducing the need for organisations to translate narrative requirements into local code.
Standardised specifications do not automatically standardise every source system. Organisations may still face incomplete FHIR resources, inconsistent coding and differences in how clinical concepts are represented. Integration effort could therefore vary significantly between a health plan with mature interoperability infrastructure and one dependent on fragmented legacy systems.
Security and governance will be equally important because member-level drill-through requires access to sensitive healthcare information. Buyers will need clarity on role-based permissions, audit logs, encryption, incident response, data retention and the division of responsibility between Amida, the health plan and cloud infrastructure providers.
How does Saraswati fit the healthcare industry’s wider shift toward digital HEDIS?
Saraswati is entering the market as the National Committee for Quality Assurance moves HEDIS toward a more digital and interoperable model. Digital HEDIS measures are built using FHIR and Clinical Quality Language, allowing measure logic to be processed by machines and connected to reporting, analytics and population-health workflows.
The transition is already changing reporting requirements. Several measures have moved to Electronic Clinical Data Systems-only reporting, with additional measures joining the category in Measurement Year 2026. The National Committee for Quality Assurance has also outlined an objective of making HEDIS fully digital by Measurement Year 2030 and phasing out the hybrid reporting method by Measurement Year 2029.
This direction supports Amida’s argument that health plans need platforms capable of continuously processing digital measure logic. As more measures rely on electronic clinical information, payer quality departments may need closer integration with interoperability, data engineering and population-health teams.
Competition is likely to extend beyond traditional HEDIS vendors. Health plans may evaluate specialised measure engines, enterprise analytics platforms, population-health systems and internally developed solutions. Saraswati will need to demonstrate that it offers more than compliant calculations, particularly through forecasting, cross-plan benchmarking and member-level actionability.
Its positioning toward state Medicaid agencies and managed care organisations may provide a focused route to market. Medicaid environments involve complex reporting obligations, multiple contractors and populations whose care can be affected by social and access barriers. A platform capable of comparing participating managed care organisations and identifying disparities could be useful to both state oversight teams and individual plans.
What will determine whether Saraswati becomes core infrastructure for health plans?
Amida has made Saraswati available as a standalone platform or as part of its broader data-management product suite. The company has not publicly disclosed pricing, named launch customers or provided detailed commercial deployment numbers in the announcement.
The immediate commercial test will be whether Amida can convert its technical and Medicaid data expertise into repeatable enterprise deployments. Health plans will expect the company to maintain measure certification as specifications change, support annual updates without disrupting workflows and document how results remain reproducible during audits.
Buyers will also look for evidence that the platform shortens implementation and remediation timelines outside early customer environments. Reference deployments showing successful data integration, reliable audit preparation and earlier intervention would carry greater weight than raw processing benchmarks.
Saraswati’s larger opportunity is to make quality measurement part of everyday health-plan operations rather than a seasonal reporting burden. Achieving that will require more than near-real-time calculation. The platform must earn trust across data engineering, quality management, compliance and clinical operations while producing information that teams can act on before the measurement window closes.
If Amida can demonstrate that Saraswati consistently turns current quality data into faster operational decisions, the platform could become valuable infrastructure for the digital HEDIS era. Until those deployment outcomes are documented across a broader customer base, the launch should be viewed as a credible technology and workflow proposition whose commercial and care-delivery impact remains to be proven.