VieCure

Moat is the content library, which is this index's most used grading precedent. VieCure's differentiating asset is a codified clinical knowledge base the company reports at more than 5,000 rules, plus a licence to NCCN treatment templates, sitting inside an oncology electronic medical record that functions as a system of record regardless of what reasons over it.

The inference engine applies codified rules to patient specific data, which is legitimately artificial intelligence in the expert system sense and is not machine learning, and the company's own language says so: codified clinical content, codified rules, clinical inference engine. That is a precision worth recording rather than an accusation of inflation, because rules based inference over curated guidelines is a defensible architecture for oncology and arguably a safer one. But the durable asset a competitor could not easily replicate is the curated content and the NCCN relationship, not a model. Same reasoning applied to Reveleer and the credentialing lane.

The architecture supports oversight well and the disclosure stops short of demonstrating it. Output is positioned as point of care decision support: the system generates a personalised treatment plan and the oncologist adopts, modifies or rejects it, and plans are continuously monitored and updated as the patient's state changes.

Because reasoning runs over codified rules rather than a learned model, any given recommendation is in principle traceable to the rule and the guideline behind it, which is a stronger oversight property than an opaque score. What is not published: how often clinicians override recommendations, what the system does when a patient's situation falls outside the codified pathways, which is common in oncology, how rule conflicts resolve, and how quickly the library is updated when a guideline changes. That last question is load bearing for a product whose value rests on currency of content.

Better than most clinical decision support vendors because VieCure names its knowledge source rather than hiding behind a model. The NCCN licensing agreement means a clinician can trace a substantial part of any recommendation back to a published guideline they can independently read and disagree with, which is the same structural property that earns Avo credit in this index and that anchors Nym Health's coding approach to published AMA and CMS guidance rather than to institutional patterns.

The company also states the scale and composition of the rule base and describes the inference architecture in general terms. Held at B because the curation methodology is undisclosed: who authors and reviews non NCCN rules, what evidence standard admits a rule, how the New Century Pathways and other licensed content are reconciled with NCCN where they diverge, and what the patented AI engine actually does beyond rule evaluation.

Nothing published addresses patient data handling, and the document that would ordinarily carry it was not written for this product. The privacy policy on the company website describes itself as governing an e commerce site, uses a credit card number as its example of personal information, and cites a transport protocol and a certificate authority brand that has not operated that business under that name for well over a decade.

It is a generic commercial template, published by a company whose product is the medical record system for community oncology practices managing a reported eighteen thousand patients daily across more than a hundred locations, and it says nothing about protected health information at all. A fairness point belongs alongside that.

A record system vendor is a business associate, and its actual obligations live in the agreement it signs with each practice rather than in a website notice, so the absence of a public statement is not evidence of an absence of controls and should not be read that way. What it does establish is that a prospective buyer can learn nothing before entering a sales process. One question deserves particular attention because the company has answered part of it publicly.

The platform includes analytics spanning a reported seventeen thousand fields with immediate access to curated datasets, and life sciences partnering is identified as a growth area. A community oncology outcomes dataset has clear commercial value. Establish who owns the data in your instance, whether de identified derivatives may be licensed, and whether the practice shares in that.

Substantial deployment, no published outcomes. VieCure names real customers at real scale, including American Oncology Network, The Oncology Institute, Oncology Care Partners and Summit Cancer Centers, and reports more than 18,000 patients managed daily across a network exceeding 100 community cancer centre locations. What does not exist publicly is any measurement of whether the platform changes anything.

No peer reviewed study, no guideline adherence rate before and after adoption, no variability reduction figure, no outcome or survival data, and no comparison against practices using conventional tools. For a product whose central claim is reducing unwarranted variation in cancer treatment, guideline concordance is the obvious measurable endpoint and it is not reported. Graded C on the standing precedent that deployment scale does not substitute for evidence of benefit.

Nothing published addresses patient data handling, and the document that would ordinarily carry it does not appear to have been written for this product at all.

The privacy policy published on the company website describes itself as governing an e commerce site, uses a credit card number as its example of personal information, and cites the Secure Sockets Layer protocol and a certificate authority brand that has not operated that business under that name for well over a decade. It is a generic commercial website template. For a company whose product is the electronic medical record for community oncology practices, managing a reported eighteen thousand patients daily across more than a hundred locations, the public privacy document says nothing about protected health information at all.

A fairness point belongs alongside that observation. An electronic medical record vendor is a business associate, and its actual patient data obligations live in the agreement it signs with each practice rather than in a website notice. The absence of a public statement is therefore not evidence of an absence of controls, and should not be read that way. What it does mean is that a prospective buyer can learn nothing about data handling before entering a sales process.

One question deserves particular attention. The platform includes an analytics capability spanning a reported seventeen thousand fields of patient data and promises immediate access to curated datasets, and the company has publicly identified life sciences partnering as a growth area. A community oncology outcomes dataset has clear commercial value. Practices should establish in writing who owns the data in their instance, whether de identified derivatives may be used or licensed, and whether they share in that.

No HIPAA statement, business associate agreement, template or summary of terms was located in any public material, and the company does not describe the relationship anywhere retrieved.

The grade should be read against what this product is. VieCure sells an electronic medical record, so it is not adjacent to protected health information, it holds the record itself for the practices that use it. That makes it a business associate as a matter of law rather than as a matter of interpretation, and a practice cannot deploy it without an executed agreement. One certainly exists in the contracting process.

The gap is entirely one of public visibility, and it is more consequential in this category than it would be elsewhere. The buyer here is a community oncology practice, which is typically a smaller organisation without a dedicated privacy office or a mature vendor review function, evaluating a system that will hold every one of its patients' records. Those are precisely the buyers least equipped to extract compliance detail through negotiation and most helped by finding it published.

Buyers should request the business associate agreement before any evaluation proceeds, ask whether its terms are negotiable, and ask specifically how it treats data used for the platform's analytics and any life sciences work, since a single agreement covering both the record keeping function and a secondary data use function needs to distinguish them clearly.

No trust centre, security page, certification or third party attestation was located across two separate searches, and no security controls are described in any public material.

The absence carries more weight here than for most records in this category, for two reasons. This is a cloud based electronic medical record holding the complete oncology chart for a reported hundred plus community cancer centre locations, so the concentration of protected health information is at the high end of anything assessed in this lane. And the customers being sold to are provider organisations whose own contracting requirements, and those of the health plans they work with, commonly treat a healthcare specific attestation as a precondition rather than a preference.

The only security related content located anywhere on the company's public site sits in a generic website privacy template referring to the Secure Sockets Layer protocol and a certificate authority brand long since divested, which is a description of website transport from another era rather than a statement about the platform holding the records.

This records what was found rather than asserting that no attestation exists. A company at this stage of commercial deployment, having raised substantial growth financing, may well hold certifications it has chosen not to publish. Buyers should ask what is held, request the report with its scope section, and confirm the assessment boundary covers the record system, the analytics platform and the patient mobile application rather than corporate systems alone.

No device authorisation and no published regulatory position, and this is the highest stakes scoping question among the vendors assessed on this sourcing list.

The product generates personalised cancer treatment plans at the point of care, which is squarely the territory the clinical decision support exclusions under the 21st Century Cures Act were written to delimit. The exclusion turns on whether a clinician can independently review the basis for the recommendation rather than relying on it, and VieCure's architecture gives it the strongest available argument: recommendations derive from codified rules traceable to NCCN guidelines a physician can read. That argument is available and the company has not made it publicly.

Ask for the documented regulatory analysis rather than inferring it from the architecture, and ask specifically how the position holds for recommendations drawn from non NCCN codified content where the underlying source is not independently publishable.

No fairness, subgroup or equity disclosure was located, and two specific issues sit underneath that absence.

The first is inherited. NCCN guidelines and the precision oncology evidence base rest substantially on trial populations that underrepresent Black, Hispanic and older patients, so a system that faithfully implements published guidance also faithfully inherits the representation gaps in the evidence behind it. A rules based architecture does not create that bias, but it does propagate it consistently and at scale, and nothing published acknowledges the limitation.

The second is structural and more concerning. VieCure states that its rule base includes payer rules alongside clinical plans, pathways, protocols and formularies, and separately markets cost optimisation through algorithmic molecular testing decision support. A single engine blending clinical guidance with coverage and cost logic must make clear which is which, because a clinician viewing a recommended plan cannot otherwise tell whether an option is absent for clinical reasons or reimbursement ones. That distinction is the difference between decision support and utilisation management, and no disclosure separating them was located. It should be the first question a practice asks.

Naming the knowledge source is what carries this, and it is the same structural property this index credits wherever it appears. A licensing agreement with a named national guideline body means a clinician can trace a substantial part of any recommendation back to a published guideline they can independently read and disagree with, which is a form of contestability no learned model offers.

The company also states the scale and composition of the rule base and describes the inference architecture in general terms. Held at C because the curation is undisclosed and one part of it matters more than the rest. Who authors and reviews the rules that do not come from the licensed guideline, and what evidence standard admits a rule, is unstated.

So is the reconciliation question, which is the sharp one: the platform carries licensed content from more than one source, guidelines diverge on real clinical questions, and when two sources disagree something decides which a clinician sees. Nothing published says what that something is or whether the clinician is told a divergence existed. In oncology that is not a corner case, since guideline disagreement is common and consequential.

No operating characteristics and no warranty, indemnity or remediation commitment were located. Ask how divergent sources are reconciled, whether the clinician sees that a conflict existed, and who authors non guideline rules.

VieCure does not integrate with the oncology record, it IS the oncology record, which changes the shape of this axis. Within its footprint the consolidation is genuinely deep: medical records, treatment planning, imaging, labs, next generation sequencing, molecular pathology and medical, radiation and surgical oncology in one system, with physician and patient mobile applications and an analytics environment on top.

The company states a flexible approach allowing integration with existing systems and multiple data sources, and reports implementing at a new customer within 60 days. Held at B because no external EHR, standard or named integration partner appears anywhere public, and for a practice inside a larger health system the question of how VieCure coexists with the enterprise record, and who holds the source of truth, is unanswered.

Cloud based by the company's own description, with mobile applications for physicians and patients. No hosting provider, region, tenancy model, residency commitment or single tenant option is published, which is a gap of some weight for a product acting as the system of record for a practice's entire oncology population.

No price, tier or licensing unit is published. The unit question is consequential for a combined record system and decision support platform: per provider, per practice, per patient under management and per location produce very different economics for a network growing by acquisition, which is exactly how several named customers are expanding.

Partial credit for one disclosed operational commitment, a stated 60 day implementation timeline at a named new customer, which is more than most enterprise platforms will put in writing. VieCure also provides implementation services and ongoing support alongside the software, and whether those are bundled or separately charged is not stated.

Deliberately and coherently narrow. The target is COMMUNITY oncology rather than academic cancer centres, and the company's stated purpose is closing the gap between the two, which is a real and defensible problem since most United States cancer care is delivered in community settings while precision oncology expertise concentrates elsewhere.

Within oncology the coverage is broad, spanning medical, radiation and surgical disciplines across the continuum from diagnosis through therapy to survivorship, at more than 100 locations. The boundaries: single disease area, ambulatory rather than inpatient, United States only, and the platform is a system of record commitment rather than an adjunct tool, so it is not an option for a practice unwilling to change its EMR.