MD-Staff

A credentialing software company that added an engine.

The platform dates to 1982 and its core is a relational credentialing, privileging, enrollment and peer review system with modular tools around it: an application portal, a drag and drop privileging interface, committee software, reporting and a provider data collection module. Those modules are the system of record a medical staff services office runs, and they work without a model.

Aiva Credentialing is a distinct component rather than a label applied to existing automation, trademarked in 2018 as an artificial intelligence engine for automating processing and credential verification, and the current site markets the whole platform as AI powered. What it does is described task by task: automated verification against issuing sources such as the American Medical Association and state licensing boards, document gathering and upload, reminders, summarizing provider histories for committee review, and flagging files with potential issues.

Remove the engine and the product remains a working credentialing platform with the verification work done by hand, which is how it ran for most of its life.

The company's own pages make an absolute claim about correctness. The primary source verification page states that the verification process ensures all credentialing information is accurate and up to date, and the home page says its algorithms ensure providers meet the precise requirements for privileging, guaranteeing patient safety and strict compliance with regulations. A buyer who believes that does not build the review step that catches a failure.

Set against that, the division of labor the product describes is real but thin: the engine runs automated license, sanction and certification checks against issuing sources, gathers and uploads documents, sends reminders and flags files with potential issues, and medical staff professionals work the flags and take files to committee. What is not published anywhere is the boundary: no confidence threshold, no statement of which verifications complete without a person, no description of what happens to a check the engine cannot complete, and no route for correcting a file the engine flagged wrongly.

An earlier company statement that the artificial intelligence does not make decisions and only highlights where human attention is needed no longer appears on the home page, the credentialing and verification pages, the product page or the legal pages, and the live marketing there runs the other way.

The engine is named and its function is described task by task, and a 2018 trademark filing puts its stated purpose in the public record, which is a small piece of documentation outside the company's own marketing. The site describes intelligent algorithms, advanced automation and verification directly from issuing organizations, and names the sources those checks run against.

Below that, nothing is identified. No model or model family, no method, no training data, no accuracy or false positive rate for automated verification or for the flags, no evaluation method, and no versioning or update practice. The claim that carries the most weight, that the system analyzes historical patterns to anticipate issues before they occur, is the one with nothing behind it at all: a pattern based system implies a corpus and an error profile, and neither is described.

That gap matters more on this product than on a documentation tool, because the output is a judgment about a named clinician's file. A buyer cannot tell whether a flag is a rule firing on a date field or a learned signal, and those call for different scrutiny.

No party in the chain is identified beyond the verification sources.

What is visible: a hosted platform with an engine over it, modules that synchronize through a central hub, and outbound connections to verification sources, with the American Medical Association named and state licensing boards named as a class. Those are the parties a provider record is checked against rather than parties that hold it, and they are the only names published anywhere.

What is not named is anything underneath. No model or model provider for the engine, no cloud or hosting provider, no document processing or identity matching supplier, and no subprocessor register. The privacy policy covers the website, so it enumerates nothing about the platform's chain either.

The training question sits in the same gap. The engine is described as identifying discrepancies across provider data and anticipating issues from historical patterns, which implies a corpus; nothing states whose files form it, whether it is built in house or bought, or whether data from one client organization informs flags at another.

Adoption and a customer satisfaction award, with no measured performance behind either.

What the company publishes about itself: more than 3,000 clients, more than 100 employees, four decades in the market since 1982, and a number one ranking by KLAS Research. KLAS is a named third party and its credentialing recognition reflects direct customer feedback on the software business, culture and relationships. It is external validation of customer satisfaction, and it says nothing about whether the engine verifies correctly.

What is absent is any outcome figure at all. No turnaround time, no reduction in days to credential, no verification accuracy, no flag precision, no audit finding rate at a named customer, and no study or benchmark of any kind for the engine specifically. For a product sold on speed and accuracy in credentialing, the two figures a medical staff office would use to compare vendors, days to complete a file and how often a verification has to be redone, are not published.

Client count measures adoption, not benefit.

General assurances, and a data set that is mostly not patient data.

The scoping point comes first. What this platform holds is provider identity data: licenses, certifications, sanctions history, training, references and application documents. That is sensitive and it is not patient data, so the privacy regime that governs most of it is not the health information one.

What the company publishes is the assurance level. It describes encryption, secure data management, stringent access controls and centralized storage, and says automation reduces the risk of human error and unauthorized access. Nothing states how long verification source documents are kept, what is deleted when a provider leaves or an application is withdrawn, how data is classified, or which third parties process it.

The training question is the live one here and is unaddressed in either direction. The engine is described as identifying discrepancies across provider data and anticipating issues from historical patterns, which implies learning from a corpus, and nothing says whose files form it or whether one customer's provider history informs flags at another.

No statement of status and no privacy document that reaches the product. The legal page lists the terms of use, two product specific terms of service, the privacy policy, an accessibility statement and a fulfillment policy, and none of them is a business associate agreement or mentions health information obligations.

The privacy policy, last updated 1 January 2026, states its own scope plainly: it covers the website and contact with customer service by phone, email or video, and does not apply to information collected elsewhere. So the document a buyer can read governs marketing contacts rather than the credentialing data the platform holds. Nothing on the product, verification, integration or solution pages states business associate status, references a business associate agreement, or describes how health information is handled.

The scoping point that softens this: most of what the platform holds is provider identity data rather than patient data. It is not none, though, since credentialing touches peer review and quality files, and any hospital deployment will want the instrument in writing.

Third party software directories attach health privacy and security labels to this platform; the company's own documents do not.

Controls are asserted and nothing independent stands behind them on anything the company publishes. The pages describe advanced encryption, stringent access controls, secure data management and a secure integration hub, and the legal page lists terms, a privacy policy, an accessibility statement and a fulfillment policy. There is no trust center, no attestation named anywhere, no report availability statement, no penetration testing cadence and no vulnerability disclosure policy.

Third party software directories reference a service organization control report for this platform, without a report type or period; the company itself names none.

The gap matters for this product. A credentialing system of record holds licenses, sanctions history, peer review material and application documents for every clinician on a medical staff, at more than 3,000 client organizations, and it connects out to regulatory data sources on their behalf. Procurement at that scale routinely asks for an attestation, so the artifacts very likely exist and are simply not published.

No clearance is claimed, none applies, and credentialing is administrative rather than clinical.

The credential that matters for credentialing work is accreditation as a credentials verification organization, and its absence here is structural rather than a shortfall. Verification organizations that work on a customer's behalf can themselves be accredited; this company sells the system of record that a hospital's own medical staff services office, or its own verification organization, runs. A software vendor is not performing delegated verification, so it cannot hold that accreditation, and comparing the two on the same basis would penalize a business model rather than a posture.

The fair test for a platform is whether it is built to the standard its customer will be surveyed against, and on that narrower test the record does reasonably well. The platform is sold as supporting compliance with hospital accreditation and health plan standards, automates verification directly against issuing sources including the American Medical Association and state licensing boards, and the company publishes education for medical staff professionals on the standards themselves, including the shift to continuous monitoring of licenses and sanctions.

Supporting a standard is not being certified against one, and nothing external verifies the platform's conformance.

Nothing published describes how the engine's behavior is governed or tested: no framework, no evaluation, no accuracy or error rate for the matching and flagging logic, no error taxonomy and no fairness work.

The exposure the product's own description creates is specific. The engine automatically flags files with potential issues and identifies discrepancies across provider data to surface risks earlier. Flagging is a classification decision even when a person makes the final call, because a flagged file gets different scrutiny and usually a slower path. If flag rates vary by name origin, license jurisdiction, training country or international medical graduate status, some clinicians are systematically routed into the slow lane and their privileges are delayed, and nothing published addresses whether they do.

Matching makes it sharper. Sanctions and exclusion checks run against national databases on name and identifier matching, and common names and transliterated names collide more often, so the false positive burden is not evenly distributed by construction.

An earlier company statement that the artificial intelligence does not make decisions is no longer on the pages a buyer reads first, and the live marketing claims the process ensures all credentialing information is accurate, which is the opposite posture.

Nothing published says what happens when the engine is wrong, and the company's pages promise the opposite: that the process ensures all credentialing information is accurate and up to date, and that the algorithms guarantee compliance. No accuracy figure, no false positive rate, no service level, no warranty, no indemnity and no remediation commitment appears anywhere, and the published legal documents are website terms, two module terms of service and a fulfillment policy rather than a customer agreement a buyer can read.

The false positive rate is the figure that matters most here, and it is absent. A risk signal raised against a named clinician is not a queue item: it prompts extra scrutiny, can delay privileging and therefore income, and enters a file other reviewers read afterward. A signal raised in error is not obviously retracted from the impression it created. A system that anticipates issues before they occur is by construction flagging people against whom nothing has yet happened, which is exactly the setting where precision matters and where a low base rate makes most positives false unless the model is very good. Nothing says what a flagged provider is told or whether they can contest it.

The mirror failure is quieter and worse: a verification the engine reports as clean that was not, which surfaces at a survey or after an incident.

The connections that matter for this product are to verification sources rather than to record systems, and those are named.

What the company publishes: verification runs directly against issuing organizations, with the American Medical Association named and state licensing boards named as a class, and the platform is presented as the central hub that synchronizes credentialing, privileging, peer review and enrollment data across its own modules and out to connected systems. Primary source verification is only automatable where those connections exist, so naming them matters.

What is not named is a record system. No electronic health record, provider directory or human resources system is named, no interface standard is described, and no public interface documentation exists, so integration looks configured by the vendor rather than programmable by the customer. Third party software directories list record system, signature and document tool integrations for this platform, which the company's own pages do not name.

One line describes the deployment and nothing commits to anything. The product page says the platform's cloud based architecture makes expansion cost effective, and the modules are described as scaling from a small clinic to a large state health system. That establishes a hosted service and implies a single delivery model.

Everything specific is missing. No hosting provider, no region, no residency statement, no tenancy or segregation model, no backup, continuity or recovery position, and no uptime commitment appears anywhere on the site, and the privacy policy covers the website rather than the platform.

One of the company's integration partners describes a self hosted option for some international customers; the company itself does not. Such an option would answer the residency question by architecture for a customer that cannot send provider data to United States infrastructure.

The offer is legible and unpriced.

The catalog is fully enumerated: MD-Staff as the core credentialing system, with MD-Stat, MD-App, MD-Query, E-Priv, Virtual Committee, Managed Care and Enrollment, MD-Staff Passport and Checksome sold as named modules alongside it, and solution pages for credentialing, privileging, enrollment, peer review and verification organizations. The product is described as modular and scaled from small clinics to large state systems, so scope, and therefore price, follows the module list a customer licenses. The legal page also publishes product specific terms of service for two of those modules and a fulfillment policy.

What is not published is any figure or unit of charge: nothing states whether cost follows providers under management, facilities, users or modules, and no implementation, configuration, data migration or training fee, or contract term, appears, although the company sells implementation support, an academy and a certification program around the product. Third party software directories describe a monthly subscription varying by organization size with implementation charged separately; the company does not say so itself.

Scope is stated by function and by organization size, and part of it is supported.

The functions are credentialing, privileging, enrollment, peer review and quality, with dedicated solution pages for each and a page for verification organizations, so the buyer inside a hospital is named precisely: medical staff services professionals, quality teams and the people who run a credentials verification office. The modular design is described as scaling from a small clinic taking one module to a large state health system taking the full suite, and that range across organization size is the coverage claim the company makes most consistently.

Support for it is adoption rather than deployment detail: more than 3,000 client organizations over four decades, more than 100 employees, and a number one ranking by KLAS Research for the credentialing category. Those are real and they validate the breadth of the customer base rather than performance in any one setting.

What is not named anywhere is a customer. No health system, clinic or verification organization is named, and no case study ties a module to a setting.

Scope is administrative rather than clinical, and international customers are referred to without a country or region named.