Wednesday, June 17, 2026

Introducing the Avon Marketplace

app.avonhealth.com/marketplace
Avon Marketplace
47 apps available
Search apps…
V
VBC Risk Engine
Real-time risk scoring for VBC contracts
Value-Based Care
P
Prior Auth AI
Automates prior authorization workflows
Billing
R
Remote Monitor
RPM data surfaced inside the chart
Monitoring
Clicking VBC Risk Engine…
Browse Marketplace

Healthcare organizations do not run on a single piece of software.

They run on an ecosystem.

Every clinic, specialty group, and care delivery organization has its own constellation of tools: billing vendors, labs, imaging partners, patient engagement platforms, remote monitoring devices, AI assistants, specialty-specific workflows, analytics products, communication tools, and operational automations.

Over the years, we have received dozens of requests from third-party vendors who want to integrate with Avon. At the same time, our customers have had an ever-growing list of external tools, services, and vendors they want to use inside their EMR.

Today, we are bringing both sides together.

We are excited to introduce the Avon Marketplace: a new way for third-party vendors to create apps that Avon customers can discover, install, and use directly inside their clinical and operational workflows.

With the Avon Marketplace, healthcare organizations can one-click install approved apps, connect their preferred vendors, and extend Avon without custom engineering work every time they want to add a new tool. Customers can also restrict exactly what scopes of access each third-party vendor receives.

For vendors, the Marketplace makes it dramatically easier to reach Avon customers and build deeply integrated healthcare applications. For customers, it means more choice, faster implementation, and a more flexible EMR that can adapt to the way their organization actually works.

A marketplace for healthcare workflows

The Avon Marketplace supports two major types of apps: embedded UI apps and code-only workflow apps.

Embedded UI apps appear directly inside the Avon experience. They can be surfaced inside the EMR, the patient portal, the provider portal, or other Avon workflows where users already spend their day.

For example:

  • A specialty pharmacy partner could build an embedded medication access console inside the patient chart, showing prior authorization status, affordability options, adherence signals, and next-best actions for the care team.
  • A value-based care company could embed a risk-stratification dashboard that shows rising-risk patients, suspected care gaps, quality measure performance, and recommended interventions inside the provider's daily workflow.
  • A diagnostics company could create a precision testing experience that suggests relevant lab panels based on the patient's history, payer requirements, and clinical context.
  • A care management vendor could embed a longitudinal patient timeline that combines claims data, HIE records, RPM signals, and social drivers of health into a single operational view.
  • An AI company could create a point-of-care copilot that reviews the chart, surfaces missing documentation, identifies suspected HCCs, recommends care plan updates, and explains the evidence behind each suggestion.

These apps do not need to feel like external portals awkwardly bolted onto the EMR. They can feel native, contextual, and workflow-aware.

Code-only apps, on the other hand, run behind the scenes. They do not need their own user interface. Instead, they are triggered when actions happen inside Avon.

For example:

  • When a patient completes an intake form, a code-only app could automatically generate a proprietary clinical risk score, compare the patient against value-based contract requirements, identify open care gaps, and route the patient into the appropriate care pathway.
  • When a new diagnosis is added, an app could scan the chart for supporting evidence, suggest missing HCC documentation, update the patient's risk profile, and trigger a coding review before the note is signed.
  • When a patient is discharged from the hospital, an app could ingest the ADT event, summarize the encounter, generate a transition-of-care task list, schedule follow-up, and alert the care manager if the patient is at high risk for readmission.
  • When remote monitoring data shows a concerning trend, an app could detect the anomaly, generate a patient-specific escalation recommendation, notify the care team, and prepare outreach instructions.
Avon → VBC Risk Engine
// Avon → VBC Risk Engine
 
POST /webhooks/avon HTTP/1.1
X-Avon-Event: intake_form.submitted
X-Avon-Sig: sha256=7d8f3a2b…
 
{
"event": "intake_form.submitted",
"patient": {
"id": "pt_8821",
"age": 59,
"conditions": ["T2DM", "HTN", "Obesity"]
},
"timestamp": "2026-06-17T14:32:01Z"
}
Event fires

How to get started

  • For vendors: go to avonhealth.com/marketplace to register as a vendor and create apps for Avon customers.
  • For Avon EMR users: open your Avon EMR, go to Settings, then Marketplace to browse and install apps.

We are excited to keep expanding the Avon ecosystem: helping healthcare organizations work with the partners they trust, giving vendors a direct path into care delivery workflows, and bringing customers the tools they need to deliver the best care possible.