Canvas Medical
Canvas Medical is a developer-first EHR platform built for virtual and value-based care, offering a comprehensive FHIR R4 REST API with 41 resources for clinical workflows, patient management, and care team coordination. The platform combines a standards-based FHIR API with a native Python SDK that enables plugins to execute synchronously within the EMR, supporting scheduling, charting, billing, and custom workflow automation across more than 650 clinical and operational events.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Canvas Medical the way a machine reads it — 51 machine-readable artifacts across 30 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Canvas Medical scores 56.4/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Canvas Medical
Each block below is one kind of artifact we hold for Canvas Medical. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 30
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Canvas Medical FHIR API
A FHIR R4-compliant REST API providing secure access to electronic health record data including 41 FHIR resources (21 with write capabilities) covering clinical, administrative,...
Canvas Medical SDK
A Python SDK that enables developers to build plugins that execute natively within the Canvas EMR infrastructure. Supports an event-driven architecture with over 650 clinical an...
Canvas Medical AllergyIntolerance API
Allergy and intolerance records
Canvas Medical Appointment API
Appointment scheduling and management
Canvas Medical CarePlan API
Care plan management
Canvas Medical CareTeam API
Care team coordination
Canvas Medical Claim API
Insurance claims and billing
Canvas Medical Communication API
Communications with or about a patient
Canvas Medical Condition API
Patient conditions, problems, and diagnoses
Canvas Medical Consent API
Patient consent records
Canvas Medical Coverage API
Insurance coverage records
Canvas Medical DiagnosticReport API
Diagnostic test reports
Canvas Medical DocumentReference API
Clinical documents and attachments
Canvas Medical Encounter API
Clinical encounters and visits
Canvas Medical Goal API
Patient care goals
Canvas Medical Immunization API
Immunization records
Canvas Medical Location API
Physical practice locations
Canvas Medical MedicationRequest API
Medication prescriptions and orders
Canvas Medical Metadata API
FHIR server capabilities
Canvas Medical Observation API
Clinical observations, vitals, and lab results
Canvas Medical Organization API
Healthcare organization information
Canvas Medical Patient API
Patient demographic and administrative data
Canvas Medical Practitioner API
Healthcare provider information
Canvas Medical Procedure API
Clinical procedures performed
Canvas Medical Questionnaire API
Structured data collection forms
Canvas Medical QuestionnaireResponse API
Patient responses to questionnaires
Canvas Medical Schedule API
Practitioner availability schedules
Canvas Medical ServiceRequest API
Orders for laboratory, imaging, and referrals
Canvas Medical Slot API
Available appointment time slots
Canvas Medical Task API
Clinical and administrative tasks
Scroll within the panel for all 30 ·
Arazzo Workflows 7
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Canvas Medical Appointment Scheduling
Locate a patient, find a practitioner's schedule, search for a free slot, then book and confirm an appointment.
ARAZZOCanvas Medical Care Plan Management
Read the patient, record a care Goal, then retrieve the active CarePlan and the CareTeam coordinating it.
ARAZZOCanvas Medical Lab Order to Results
Place a laboratory order with a ServiceRequest, then retrieve the resulting DiagnosticReport and the discrete Observation results.
ARAZZOCanvas Medical Medication Prescribing
Read the patient, check existing allergies and active medications for safety, then write a new prescription and confirm it.
ARAZZOCanvas Medical Patient Registration (Upsert)
Search for an existing patient by identifier and update it if found, otherwise create a new US Core Patient.
ARAZZOCanvas Medical Questionnaire Assessment Capture
Find a questionnaire by title, submit a completed QuestionnaireResponse, then read it back to confirm capture.
ARAZZOCanvas Medical SMART on FHIR US Core Retrieval
Discover server capabilities, locate a patient, then pull the US Core clinical summary - problems, vitals/labs, medications, and allergies.
ARAZZOScroll within the panel for all 7 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Canvas Medical GraphQL Schema
This conceptual GraphQL schema represents the Canvas Medical EHR platform's data model, derived from its FHIR R4 REST API and Python SDK capabilities. Canvas Medical is a develo...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Canvas Medical Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Canvas Medical Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Canvas Medical Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Canvas Medical API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Canvas Medical FHIR Patient
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Canvas Medical — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/canvas-medical · machine-readable index on apis.io