Veradigm (Allscripts)

Allscripts, now operating as Veradigm, is a healthcare IT company providing REST and FHIR APIs for EHR data exchange, clinical workflows, patient portal, and practice management integrations. The Veradigm Developer Program (formerly Allscripts Developer Program) offers FHIR R4 APIs covering 28 clinical resources as well as a Unity API for clinical, scheduling, demographic, and practice management functions across Allscripts EHR products.

Veradigm (Allscripts) is listed with 3 APIs on the APIs.io network. Tagged areas include Healthcare IT, Electronic Health Records, FHIR, Clinical Data, and Practice Management.

The Veradigm (Allscripts) catalog on APIs.io includes 1 JSON-LD context.

Veradigm (Allscripts)’s developer surface includes authentication, sandbox, signup flow, engineering blog, and 28 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

49.8/100 developing ▬ flat Agent 22/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

AccessFreemiumOpen⚡ Free to try

3 APIs 1 Agent Skills

Healthcare IT Electronic Health Records FHIR Clinical Data Practice Management HL7

Kin Score

Kin Score How this is scored →
scored 2026-11-02 · rubric v0.26.0

Composite quality — 49.8/100 · developing

Contract Quality 8.7 / 21

Developer Ergonomics 9.2 / 17

Access Clarity 11.2 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.7 / 9

Regulatory Posture 5.6 / 15

Agent readiness — 22/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/veradigm/"><img src="https://apis.io/badge/veradigm/card.svg" alt="Veradigm (Allscripts) on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 40.9 — up to +14.8 composite points
Operational Transparency scores 13.2 — up to +11.3 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/veradigm/apis.yml: open an issue on github.com/api-evangelist/veradigm to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Medical Technology (certified health IT, FDA-authorized AI devices)	regulated	50.4	-	-
Data Marketplaces (data providers on cloud data platforms)	regulated	50.4	-	-
Certified Health IT (health IT accreditation and certification registers)	regulated	50.4	-	-
Payer Interoperability (CAQH CORE, X12, Da Vinci, WEDI)	regulated	50.4	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Veradigm FHIR R4 API

The Veradigm FHIR R4 API provides RESTful access to clinical, demographic, and facility data using the HL7 FHIR R4 standard. It supports 28 FHIR resources including Patient, Con...

Veradigm Unity API

The Veradigm Unity API exposes clinical, scheduling, demographic, and practice management functions across Allscripts EHR product lines including Touchworks, Professional EHR, a...

Veradigm Paragon Open API

The Paragon Open API provides FHIR-compliant access to data from the Veradigm Paragon acute care EHR platform. It enables third-party applications to integrate with Paragon to a...

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

veradigm-fhir-patient-summary

AGENT SKILL

Pricing Plans 2

Published pricing tiers and plan structures.

Unity Api Plans

3 plans

PLANS

Veradigm Fhir Plans

6 plans

PLANS

Rate Limits 2

Documented rate limits and quota policies.

Unity Api Rate Limits

0 limits

RATE LIMITS

Veradigm Fhir Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Allscripts Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Allscripts Context

0 classes · 19 properties

JSON-LD

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Allscripts Authentication

0 schemes

SECURITY

Allscripts Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Allscripts Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

Sandbox

DeveloperPortal

DeveloperPortal

DeveloperPortalLegacy

DeveloperPortalLegacy

Signup

Signup

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

Packages

Packages

GitHubOrganization

GitHubOrganization

MasterClientAgreement

MasterClientAgreement

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

SecurityProgram

ComplianceONC

Learn 1

Tutorials, courses, talks, and written guidance

APIWorkshop

APIWorkshop

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Deprecation

Deprecation

Commercial 4

Pricing, plans, and the legal terms of use

Plans

TermsOfService

PrivacyPolicy

FinOps

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityStatement

CapabilityStatement

AppExpo

AppExpo

Source (apis.yml)

name: Veradigm (Allscripts)
description: Allscripts, now operating as Veradigm, is a healthcare IT company providing REST and FHIR APIs for EHR data exchange,
  clinical workflows, patient portal, and practice management integrations. The Veradigm Developer Program (formerly Allscripts
  Developer Program) offers FHIR R4 APIs covering 28 clinical resources as well as a Unity API for clinical, scheduling, demographic,
  and practice management functions across Allscripts EHR products.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
specificationVersion: '0.23'
accessModel:
  pricing: freemium
  onboarding: open
  trial: false
  try_now: true
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Open access
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-02'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/allscripts.png
url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/apis.yml
version: '0.19'
created: '2026-06-13'
modified: '2026-08-14'
tags:
- Healthcare IT
- Electronic Health Records
- FHIR
- Clinical Data
- Practice Management
- HL7
tags_raw:
- Healthcare IT
- EHR
- FHIR
- Clinical Data
- Practice Management
- HL7
apis:
- name: Veradigm FHIR R4 API
  description: The Veradigm FHIR R4 API provides RESTful access to clinical, demographic, and facility data using the HL7
    FHIR R4 standard. It supports 28 FHIR resources including Patient, Condition, Observation, MedicationRequest, Encounter,
    and more. Authentication uses OAuth 2.0 with SMART on FHIR Application Launch Framework 2.0. Endpoints are available for
    both patient-facing (ending in /open) and provider-facing (ending in /fhir) applications.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.veradigm.com/Fhir/Introduction
  baseURL: https://open.platform.veradigm.com
  tags:
  - FHIR
  - Clinical Data
  - Electronic Health Records
  - HL7
  - Patient Data
  - Healthcare
  tags_raw:
  - FHIR
  - Clinical Data
  - EHR
  - HL7
  - Patient Data
  - Healthcare
  properties:
  - type: Documentation
    url: https://developer.veradigm.com/Fhir/Introduction
  - type: GettingStarted
    url: https://developer.veradigm.com/Content/fhir/GetStarted/Concepts/Considerations.html
  - type: Sandbox
    url: sandbox/allscripts-sandbox.yml
  - type: EndpointDirectory
    url: https://developer.veradigm.com/Fhir/EndpointDirectory
  - type: Authentication
    url: authentication/allscripts-authentication.yml
  - type: OAuthScopes
    url: scopes/allscripts-scopes.yml
  - type: CapabilityStatement
    url: conformance/allscripts-fhir-r4-capabilitystatement.json
  - type: Conformance
    url: conformance/allscripts-conformance.yml
  - type: Resources
    url: https://developer.veradigm.com/Fhir/Resources
  - type: Plans
    url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/plans/veradigm-fhir-plans.yml
  - type: RateLimits
    url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/rate-limits/veradigm-fhir-rate-limits.yml
  - type: TermsOfService
    url: https://developer.veradigm.com/Content/fhir/Allscripts_FHIR_API_License_2017.2.pdf
  contact:
  - FN: Veradigm Connect Support
    email: VeradigmConnect@veradigm.com
    url: https://developer.veradigm.com/
- name: Veradigm Unity API
  description: The Veradigm Unity API exposes clinical, scheduling, demographic, and practice management functions across
    Allscripts EHR product lines including Touchworks, Professional EHR, and acute care solutions. It supports both SOAP and
    REST endpoints with an action-based dispatch model. The Unity API is available to certified Integrator members and provides
    read-write access to cloud-hosted Allscripts solutions for building custom healthcare integrations.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.allscripts.com/
  baseURL: https://remotecentral.allscripts.com
  tags:
  - Electronic Health Records
  - Clinical
  - Scheduling
  - Practice Management
  - REST
  - SOAP
  - Healthcare IT
  tags_raw:
  - EHR
  - Clinical
  - Scheduling
  - Practice Management
  - REST
  - SOAP
  - Healthcare IT
  properties:
  - type: Documentation
    url: https://developer.allscripts.com/
  - type: GettingStarted
    url: https://developer.allscripts.com/Home/LearnMore
  - type: Plans
    url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/plans/unity-api-plans.yml
  - type: RateLimits
    url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/rate-limits/unity-api-rate-limits.yml
  - type: TermsOfService
    url: https://veradigm.com/img/legal/pm/Unity-API-EULA.pdf
  - type: AppExpo
    url: https://expo.veradigm.com/apps
  contact:
  - FN: Veradigm Connect Support
    email: VeradigmConnect@veradigm.com
    url: https://developer.veradigm.com/
- name: Veradigm Paragon Open API
  description: The Paragon Open API provides FHIR-compliant access to data from the Veradigm Paragon acute care EHR platform.
    It enables third-party applications to integrate with Paragon to access patient clinical data, supporting interoperability
    requirements for hospital and acute care settings.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.veradigm.com/Content/fhir/paragon/ParagonOpenAPI_Index.html
  baseURL: https://open.platform.veradigm.com
  tags:
  - FHIR
  - Acute Care
  - Electronic Health Records
  - Paragon
  - Hospitals
  - Healthcare
  tags_raw:
  - FHIR
  - Acute Care
  - EHR
  - Paragon
  - Hospital
  - Healthcare
  properties:
  - type: Documentation
    url: https://developer.veradigm.com/Content/fhir/paragon/ParagonOpenAPI_Index.html
  - type: EndpointDirectory
    url: https://developer.veradigm.com/Fhir/EndpointDirectory
  - type: Plans
    url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/plans/veradigm-fhir-plans.yml
  - type: RateLimits
    url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/rate-limits/veradigm-fhir-rate-limits.yml
  - type: TermsOfService
    url: https://developer.veradigm.com/Content/fhir/Allscripts_FHIR_API_License_2017.2.pdf
  contact:
  - FN: Veradigm Connect Support
    email: VeradigmConnect@veradigm.com
    url: https://developer.veradigm.com/
common:
- type: RateLimits
  url: rate-limits/unity-api-rate-limits.yml
- type: Website
  url: https://veradigm.com/
- type: DomainSecurity
  url: security/allscripts-domain-security.yml
- type: Authentication
  url: authentication/allscripts-authentication.yml
- type: OAuthScopes
  url: scopes/allscripts-scopes.yml
- type: CapabilityStatement
  url: conformance/allscripts-fhir-r4-capabilitystatement.json
- type: Conformance
  url: conformance/allscripts-conformance.yml
- type: WellKnown
  url: well-known/allscripts-well-known.yml
- type: Packages
  url: packages/allscripts-packages.yml
- type: X-MCPServerCandidate
  url: mcp/allscripts-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/allscripts-llms.txt
- type: ErrorCatalog
  url: errors/allscripts-problem-types.yml
- type: Lifecycle
  url: lifecycle/allscripts-lifecycle.yml
- type: Deprecation
  url: lifecycle/allscripts-lifecycle.yml
- type: Conventions
  url: conventions/allscripts-conventions.yml
- type: DataModel
  url: data-model/allscripts-data-model.yml
- type: Sandbox
  url: sandbox/allscripts-sandbox.yml
- type: AgentSkill
  url: skills/allscripts-fhir-patient-summary.md
- type: GitHubOrganization
  url: https://github.com/veradigm
- type: DeveloperPortal
  url: https://developer.veradigm.com/
- type: DeveloperPortalLegacy
  url: https://developer.allscripts.com/
- type: AppExpo
  url: https://expo.veradigm.com/apps
- type: Signup
  url: https://developer.veradigm.com/Content/fhir/content/Developer_Signup/
- type: Plans
  url: https://developer.veradigm.com/Home/LearnMore
- type: TermsOfService
  url: https://veradigm.com/legal/terms-of-use/
- type: PrivacyPolicy
  url: https://veradigm.com/legal/privacy-notice/
- type: MasterClientAgreement
  url: https://veradigm.com/img/legal/Client-Master-Agreement.pdf
- type: SecurityProgram
  url: https://veradigm.com/legal/privacy-and-security-program/
- type: ComplianceONC
  url: https://veradigm.com/legal/onc-reg-compliance/
- type: Blog
  url: https://veradigm.com/blog/
- type: APIWorkshop
  url: https://lp.veradigm.com/api-workshop-registration-april
- type: FinOps
  url: https://raw.githubusercontent.com/api-evangelist/veradigm/refs/heads/main/finops/allscripts-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
  url: https://apievangelist.com
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 16
  pass: local-v1
x-former-name: Allscripts Healthcare Solutions, Inc.

Veradigm (Allscripts) API — frequently asked questions

Does Veradigm (Allscripts) have an API?

Yes. APIs.io lists 3 APIs from Veradigm (Allscripts), including Veradigm FHIR R4 API, Veradigm Unity API and Veradigm Paragon Open API.

How do I authenticate with the Veradigm (Allscripts) API?

Veradigm (Allscripts) uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Allscripts Authentication.

How much does the Veradigm (Allscripts) API cost?

APIs.io lists 9 pricing plans for Veradigm (Allscripts), with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the Veradigm (Allscripts) API ready for AI agents?

Veradigm (Allscripts) has a Kin Score of 49.8 out of 100 (developing) and an Agent Readiness score of 21.8 (agent-aware), scored by API Evangelist on 2026-11-02.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/veradigm"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/veradigm/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/veradigm/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.