Axuall
Cleveland based clinical workforce intelligence company built on a real-time clinician data network spanning a reported 19,000 primary sources and tens of billions of claims and encounters across roughly six million clinicians. Its Clinician Wallet is a vendor-agnostic digital credential wallet letting practitioners collect verified credentials once from primary source issuers and reuse them across employers, which reframes credentialing as portable identity rather than repeated verification. Holds US Patent 12,079,891 for digital credential verification and management.
Deliberately integrates with incumbent credentialing platforms including HealthStream CredentialStream rather than replacing them, and extends beyond credentialing into workforce supply and demand analytics.
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
The company launched next generation AI functions for the Clinician Wallet in September 2025, but the foundational asset it describes and patents is the data network itself, spanning a reported 19,000 primary sources and tens of billions of claims across roughly six million clinicians, plus the credential wallet architecture. Removing the AI layer would leave a substantial verification network and portable credential product intact. Graded C consistently with CertifyOS and Andros: real AI, but the network effect and the patented wallet are the defensible assets.
Verification runs at machine scale within a determinate task: the company reports consistently delivering more than 200,000 primary source verifications per day at a 99 percent plus PSV match rate. A published match rate is a more useful autonomy disclosure than most vendors offer, because it quantifies how often the automated path succeeds and by implication how often human handling is required. Credentialing and privileging decisions remain with the medical staff office; the platform supplies verified data rather than approvals.
Stronger than category peers on the mechanism, weaker on the AI. The credential verification and management method is covered by US Patent 12,079,891, which places a detailed technical description in the public record where a buyer or competitor can actually read it, and the network is quantified specifically at 19,000 sources with a stated 99 percent plus match rate. What is not disclosed is anything about the newer AI functions themselves, including what they do differently from rules based matching or how they were evaluated.
The data network is described with specific architectural properties rather than assurances, being stated as fault tolerant, highly auditable and tamperproof. Auditability and tamper resistance matter more than usual in credentialing and the reason is worth stating, because it inverts the usual priority of this axis. For most records here the governing concern is confidentiality, keeping data from reaching parties who should not see it.
Here the record establishes a clinician's right to practise, so its integrity is the product: an altered or unverifiable credential record is a worse failure than a disclosed one, because a hospital acts on it and a patient is treated by someone whose qualifications were never really confirmed. A vendor naming tamper resistance has identified the right property for what it holds.
Held at C because nothing else is enumerated: no retention or deletion schedule for verification source documents, no statement on whether provider data trains or improves the newer artificial intelligence functions, no sub processor list, and no model or hosting arrangement named.
The scoping point that applies across this segment applies here too, since credential data is professional rather than clinical information, which changes which regime governs it and does not make it less sensitive. Ask for retention on source documents, the training position on provider data, and who else in the chain holds it.
Better substantiated than most in this category because customers are named and an integration partner independently reports results. Lehigh Valley Health Network is a named deployment across a 13 hospital system, and HealthStream CredentialStream customers reported up to 70 percent reduction in application processing time following the integration, which is a partner reported figure rather than purely self reported.
Other claims, including up to 100 million dollars in revenue capture opportunity across enterprises and roughly 70 percent year to date wallet growth, are vendor stated and unverified. No peer reviewed or audited study was located.
The data network is described with specific architectural properties rather than assurances: fault tolerant, highly auditable, and tamperproof. Auditability and tamper resistance matter more than usual for credentialing, since the record establishes a clinician's right to practice and its integrity is the product. Credential data is professional rather than clinical information. No AI specific safety documentation was located for the newer AI functions.
No business associate agreement statement, terms or execution path was located, and no explicit HIPAA compliance assertion was found in the public material reviewed. Public documentation for this vendor was thinner than for comparable platforms in this segment, so this reflects what can be established from outside rather than a confirmed gap. The wider point matters more than the grade.
A credentialing platform's core dataset is provider identity data rather than patient data: national provider identifiers, DEA registrations, state licences, board certifications, training history, malpractice and sanctions records, and commonly Social Security numbers.
That is highly sensitive, but it sits largely outside HIPAA and is governed instead by state breach notification law, the FTC Act and payer contract terms, so a low grade on this axis does not carry the meaning it would for a clinical product. Axuall's architecture may also change the shape of the question.
A network built on verified, provider held credentials raises different issues about what the vendor itself persists, and on whose behalf, than a conventional vendor side repository does. Worth establishing whether a business associate agreement is executed as standard, what Axuall retains once verification is complete, and for how long.
The only vendor in the credentialing group with a security attestation located in public materials: the company states its data network is SOC 2 standards compliant, alongside fault tolerant, auditable, and tamperproof design. Note the wording is standards compliant rather than a stated completed SOC 2 Type II audit with a report available under NDA, so a buyer should ask which report exists and request it. Still materially ahead of peers here, none of whom publish any attestation.
No FDA clearance, and none is applicable. Credentialing is an administrative and network integrity function rather than a clinical one, so nothing in this product diagnoses, treats or informs the treatment of a patient. The regulatory weight in this segment sits elsewhere: NCQA and URAC accreditation standards govern primary source verification, verification timeframes and recredentialing cycles, alongside CMS conditions of participation, state licensure boards and payer network requirements.
A credentialing platform automating verification operates directly against those standards, and buyers are often required by state law or contract to work with an accredited or certified vendor. No NCQA or URAC accreditation was located for Axuall in the public material reviewed, and four of the five comparable vendors in this index do hold one.
There is also a structural question that shapes how this should be read: a delegated verification organisation performing credentialing on a customer's behalf is itself accreditable, while a network or software layer that enables a customer's own credentialing is not.
Axuall operates a digital credentialing network rather than a conventional outsourced verification service, so it may fall on the platform side of that line, in which case the relevant test is whether the network is built to the standard its customers are surveyed against. Two questions settle it: whether Axuall holds NCQA or URAC certification, and whether it operates as a delegated entity or as infrastructure.
No responsible AI statement, bias or fairness position, matching accuracy or error rate, error taxonomy or published evaluation output was located, and public documentation for this vendor was thinner than for comparable platforms in this segment. The exposure specific to automated credentialing is worth understanding regardless of which vendor a buyer selects.
Credentialing automation rests on identity resolution and sanctions screening against state licensing boards, the DEA registry, the OIG exclusion list, the National Practitioner Data Bank and malpractice records. Name matching error rates are not evenly distributed: false positives cluster on common surnames, on names transliterated from non Latin scripts, and on hyphenated or compound surnames. The consequences fall in opposite directions.
A false positive delays credentialing, which delays network participation and income, and lands on the provider rather than the patient. A false negative is the patient safety failure. One aspect of Axuall's design may address the first directly.
A network built on verified, provider held credentials puts a clinician in possession of their own verified record, which creates a correction path that outsourced verification models do not have, since the person best placed to notice an error can see the file. Worth asking whether providers can view and dispute what is held about them, what the false positive rate on sanctions matching is, whether it varies by name origin, and which determinations are made without human review.
The verification method is covered by a granted patent, which places a detailed technical description in the public record where a buyer or a competitor can actually read it, and this is the second vendor in this backfill to use that route.
It is a good one for exactly the reason it is underused: a granted patent had to describe the method well enough for someone skilled in the field to work it, so a company pointing at one has published more real detail than most datasheets contain, at no additional cost to itself. Around it the network is quantified specifically at a stated number of primary sources with a stated match rate, which lets a buyer judge coverage rather than accept a claim of comprehensiveness.
Held below the top grade because the newer artificial intelligence functions are undescribed: nothing states what they do differently from rules based matching, how they were evaluated, or what their error characteristics are, and no warranty, indemnity or remediation commitment attaches.
That gap matters because the affected party is a clinician whose right to practise at an organisation depends on the output, and a false negative on a credential verification delays or blocks someone's employment while a false positive admits an unverified provider. Neither error is visible to the clinician as an error rather than a delay. Ask what the newer functions decide, their error rates in both directions, and what recourse a clinician has when a verification fails incorrectly.
The strategy is explicitly to integrate rather than displace, and it is evidenced by a named partnership rather than asserted. The Clinician Wallet is described as vendor agnostic and connects into HealthStream's hStream ecosystem, giving CredentialStream customers access without replacing their credentialing system, and the company states integration with leading credentialing software vendors generally.
Connecting to 19,000 primary sources on one side and incumbent credentialing platforms on the other is a genuine interoperability position, and the willingness to sit underneath competitors' workflows is what earns the A.
Delivered as a network service with a clinician facing wallet and enterprise integrations, so customers consume rather than host it. The architecture is described as fault tolerant and auditable, but specific hosting, tenancy, and data residency terms are not published. The credential wallet model means practitioner controlled data sits with the vendor's network by design, which is the intended portability mechanism rather than an oversight.
No pricing is published. The company frames value as revenue capture, citing up to 100 million dollars in opportunity across enterprises, and time savings of 15 or more days on onboarding, which are vendor calculated. Because the product integrates with rather than replaces an existing credentialing platform, a buyer is adding cost to an existing stack rather than substituting, and should model it against the onboarding time saved rather than against CVO fees.
Spans credentialing, privileging, enrollment, and onboarding across health systems, telehealth companies, and staffing organizations, with coverage extending to physicians, advanced practice providers, specialists, and registered nurses. Beyond credentialing it extends into workforce intelligence, publishing supply and demand gap analysis from its network of 19,000 sources and billions of encounters. That analytics dimension is a genuine differentiator within this group, since peers largely stop at credentialing operations.
Compared With
Each comparison carries a written verdict, the buyer conditions that favor each vendor, and a graded side by side. Pairs that cross a category boundary are grouped separately, and their verdicts state where the boundary sits rather than manufacturing a head to head.
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 |
|---|---|---|---|---|
|
Contact the vendor
|
Undisclosed. Data network access plus Clinician Wallet, sold to health systems, telehealth, and staffing organizations alongside existing credentialing platforms. | Not disclosed. The data handled is predominantly practitioner credential and practice pattern information rather than patient PHI. | Not disclosed. Integration into existing credentialing software is the intended path, including a named connection into HealthStream's hStream ecosystem for CredentialStream customers. | Vendor Published |
No pricing is published. The commercial framing differs from CVO competitors in a way that matters: because this product integrates with an existing credentialing platform rather than replacing it, a buyer is adding to the stack rather than substituting for a CVO, and should model it against onboarding time saved, a stated 15 or more days and up to 70 percent faster application processing per partner reporting, rather than against credentialing service fees. Vendor claims of up to 100 million dollars in revenue capture opportunity across enterprises are unverified and should be treated as illustrative.