Verato
Verato sells MDM Cloud, an identity data platform that health systems, health plans, health information exchanges and provider data teams use to decide which records belong to the same patient, member or provider. Its core Referential Matching engine compares incoming records against Verato Carbon, a reference database of more than 300 million identities, and assigns each person a persistent Link ID, and that engine runs on reference data and fixed logic rather than machine learning. The learned part is Smart Resolve, inside the stewardship queue: when a data steward opens a task involving two identities, it reads the match codes describing how the records agree and recommends Same Person, Not Same Person or Not Enough Information, or stays silent when confidence is low. General Purpose, HIE and Provider models are offered, trained on past stewardship decisions rather than identity details, with rollback to an earlier version.
Direct buyers choose among four annual plans priced to the organization, with AI stewardship workflows from the Standard plan up and hosting and implementation included; on AWS Marketplace, a month of capacity for 100,000 unique patient identities lists at $4,166.67. Connectors cover Epic, Oracle Health, athenahealth and Allscripts. Baptist Health uses the platform for provider identity, and an unnamed health system combining Epic and marketing data removed 50,000 duplicates and found 31% more matches. Verato says Smart Resolve agrees with human stewards at least 90% of the time on Same Person calls. The company was founded in 2012 as Araxid and is based in McLean, Virginia.
Capability Axes
An AI Health Index grade measures what a buyer can verify from public sources on the date shown. It is not a rating of how good the product is. A vendor can build an excellent system and grade low on an axis because it publishes nothing an outsider can check. How grades read
Matching itself is not AI. Referential Matching resolves identity against the Carbon reference database with fixed logic, and Verato says plainly that the engine works without machine learning. The learned component is Smart Resolve, which reads the match codes on an open two identity stewardship task and recommends Same Person, Not Same Person or Not Enough Information for the steward to accept or ignore.
Smart Steward, sold from the Standard plan up, packages that recommendation with task prioritization. Verification, enrichment, the Link ID and the golden record all work without the model, so the AI speeds a manual queue on a platform whose value stands apart from it.
Smart Resolve only acts on an open task involving exactly two identities, appears only when a steward opens that task, and abstains when its confidence is low, so ineligible tasks and service outages fall back to the manual queue. A steward can ignore the recommendation, accept it, which closes the task with that resolution, or accept and continue through the merge or link steps. Customers set which recommendation types are offered and can roll a model back. Bulk closing of high confidence Same Person tasks and automatic assignment are planned rather than live, so today every recommendation waits for a person to act on it.
Smart Resolve's inputs are match codes summarizing how closely two records agree, not the names, dates of birth or addresses behind them. Three models are offered, General Purpose for most organizations, HIE tuned to health information exchange match patterns and Provider tuned to provider identity, each trained on match pattern data from real stewardship decisions.
Versions are managed per customer, with rollback when a version underperforms and configuration of which recommendation types appear. That names what produces the output, what trained it and how a change is controlled, though the model architecture and the size of the training data are not given.
Verato builds and serves its own Smart Resolve models inside MDM Cloud, so no outside model provider sits between a stewardship task and its recommendation, and the models read match codes rather than identity details. The Marketplace offer names AWS as the hosting provider, and the privacy policy separates uploaded records from generated data such as Link IDs and match scores. Other platform functions reach outside services, such as CLEAR for identity verification. A full subprocessor list for the platform, and the terms covering the match pattern training data, are not public, which keeps the chain short but not fully enumerated.
The one Smart Resolve figure is a tuning target: agreement with human stewardship decisions at least 90% of the time on Same Person recommendations, with the tasks it abstains on excluded and no sample, period or method given. The other results belong to the wider platform.
An unnamed health system combining Epic and marketing data removed 50,000 duplicate records and found 31% more matches, and Baptist Health is named for provider identity matching, with Acadia Health System a named platform customer. None of these measures what the learned recommendations change in stewardship workload, accuracy or the time it takes to resolve a task.
Smart Resolve works from match codes, the structured signals describing how two records agree, and never needs names, dates of birth or addresses, and its models are trained on match patterns from stewardship decisions rather than on identity data. The product privacy policy commits Verato to return or destroy customer data within 45 calendar days of termination and certify destruction in writing, limits combining customer data across accounts and governs pseudonymized information.
The Marketplace business associate addendum requires the buyer's written approval before Verato creates deidentified data from it. Security incident timelines are stated, while handling of a harmful recommendation as its own kind of event is not.
Verato provides a business associate agreement for HIPAA covered customers. On AWS Marketplace the agreement sits in Schedule C of the public contract, readable before buying, applies to the covered entity or business associate purchasing the SaaS service, and requires subcontractors handling protected health information to accept the same restrictions and conditions. The product privacy policy defines when uploaded records and derived match data count as protected health information. Direct purchases run under the master SaaS agreement, the business associate agreement and any data processing addendum, so the tier the agreement applies at is clear on both routes.
The security program covers HITRUST r2 certification, SOC 2 Type II and PCI. Each customer gets a private tenant on segmented virtual networks, with encryption in transit and at rest, access reviews and immutable audit logs, and the privacy policy explains how buyers request certification letters or assessments and provides for an assessment after a confirmed incident.
No trust center opens the reports or the HITRUST certificate without a request, so the audit periods and the systems in scope are visible only once Verato supplies them. HITRUST r2 is the most demanding of HITRUST's assessment levels.
The product decides whether records describe the same person or provider, assigns a persistent identity and suggests how a steward should resolve a duplicate task. Those are administrative data decisions with no diagnosis, triage or treatment in them. A wrong merge can put one patient's information in another's chart, which is why the merge stays with a steward.
Identity verification for registrations and password resets, through services such as CLEAR, sits in the same administrative frame. Verato makes no device claim and the product's scope matches that, as identity management sold to health information, data and stewardship teams.
Customers choose which Smart Resolve model they run, General Purpose, HIE or Provider, and work with Verato to set which recommendation types appear and which model version is live, with rollback when a version underperforms. The model abstains when confidence is low, trading coverage for quality, and works only on tasks with exactly two identities. Verato states a tuning target of agreement with human stewardship decisions at least 90% of the time for Same Person calls.
Those controls give a stewardship lead real levers. No results show agreement or abstention rates across the three models, source systems, or patient groups whose naming and address patterns make matching harder.
Under the AWS Marketplace contract, Verato warrants that the software and SaaS service will conform materially to the documentation, and if it cannot correct a covered failure within 30 days the buyer can terminate and recover prepaid fees for the unused period, with credits where specified. The product privacy policy lets customers submit corrected records and have updated matching results flow through.
Every Smart Resolve recommendation can be ignored, and accepting one still leaves the merge or link step with the steward. Those remedies attach to the service performing as documented rather than to whether a particular recommendation was right, and no commitment covers the cost of a wrong merge.
Connectors are sold for Epic, Oracle Health, athenahealth and Allscripts, alongside REST APIs, batch files and messaging. In one health system's Epic deployment, an Epic Clarity work queue fed tasks through an integration layer and, after validation, automated merge messages went back into Epic, which shows both directions running in production at an unnamed site. Verato also describes resolving the potential duplicates Epic Identity flags for manual review. No marketplace listing confirms the connectors, the case site is not named, and Smart Resolve itself works inside Verato's own task interface rather than in the EHR.
MDM Cloud runs as a cloud service with a private tenant for each customer. The product privacy policy names primary hosting in the northeastern and southwestern United States, keeps encrypted backups in the same region, and keeps customer data in the United States unless the customer consents in writing and a transfer mechanism applies. Platform tiers set disaster recovery objectives, and the Marketplace offer runs on AWS.
Termination triggers return or destruction within 45 days with a certificate. Where data rests, how tenants are separated and when anything would cross a border are all answered in the policy a buyer can read before signing.
Direct buyers choose among Starter, Standard, Enterprise and Enterprise Plus, annual plans priced to the organization rather than a rate card, each including software, upgrades, hosting and implementation. Smart Steward, the AI stewardship workflow, starts at Standard, and platform tiers are set by throughput of up to 10, 50 or 100 transactions per second. EHR, marketplace and outbound notification connectors are bought separately.
On AWS Marketplace, a one month contract for 100,000 unique patient identities lists at $4,166.67, with capacity sized by resolved identities in production. Whether that listing includes Smart Resolve is not stated.
Buyers are health systems reconciling patients across mergers and EHR instances, health plans reconciling members, health information exchanges, and provider data teams, with Baptist Health named for provider matching and Acadia Health System as a platform customer. Smart Resolve's three models map to those settings: General Purpose for most, HIE for exchanges and Provider for provider identity.
The platform's results come from health system and provider work, while Smart Resolve's accuracy in each setting is not reported separately. Its job stays narrow, a recommendation on a two identity stewardship task.
Alternatives to Verato
Other products that do the same kind of work as Verato, and what each one does.
Lifen sends medical documents and files them in patient records for French hospitals, clinics and independent clinicians, with Lifen Documents and Lifen Intégration running in the same application.
Kyruus Health sells patient access software to both sides of the market: provider organizations and health plans buy from the same platform, which follows from an acquisition history rather than from a single product line.
Dexit is 314e Corporation's HIPAA cloud fax and intelligent document processing product for hospitals, RCM companies and physician practices.
Particle Health sells access to patients' medical records through a single API.
TeleVox is a long established patient engagement and communications business, built on automated appointment reminders and now selling an omnichannel platform across voice, SMS, RCS, email, chat and physical mail.
Courier Health gives biopharma teams a shared system for managing patient access to specialty therapies. It connects information from hubs, specialty pharmacies, payers and internal teams so staff can see enrollment progress, authorization barriers, therapy starts and ongoing adherence.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
| Entry Price | Pricing Basis | BAA Tier | Implementation | Source |
|---|---|---|---|---|
|
$4,166.67 per month for 100,000 unique identities on AWS Marketplace
$4,166.67 baseline
|
A one month AWS Marketplace contract for 100,000 unique patient identities costs $4,166.67. Direct buyers choose among four annual plans priced to the organization, each including software, upgrades, hosting and implementation. | Schedule C of the AWS Marketplace contract contains a business associate agreement for covered entities and business associates, binding subcontractors. Direct subscriptions use the business associate agreement under the master agreement. | Direct annual plans include implementation. EHR, marketplace and outbound notification connectors are bought separately. | Vendor Published |
Marketplace capacity is sized in blocks of 100,000 resolved identities. Smart Steward, the AI stewardship workflow, is included from the Standard plan up, while whether the Marketplace listing includes Smart Resolve is not stated.