Canvas Medical Communication API
Communications with or about a patient
Canvas Medical Communication API is one of 30 APIs that Canvas Medical publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Communication. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 3 operations across 2 paths, and defines 9 schemas. It is described by OpenAPI 3.0.3, at version 4.0.
Requests are made against a single base URL, https://fumage-{canvas-instance}.canvasmedical.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Canvas Medical Communication API declares
3 security schemes
for authenticating requests.
It supports OAuth 2.0 (OAuth2ClientCredentials) using the clientCredentials flow, exposing 8 scopes.
It supports OAuth 2.0 (OAuth2AuthCode) using the authorizationCode flow, exposing 3 scopes.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
OAuth2ClientCredentials— Machine-to-machine authentication using client credentials grant. Obtain clientid and clientsecret from Canvas admin panel.OAuth2AuthCode— User-delegated access using Authorization Code flow with SMART on FHIR scopes.
Paths & Operations 3
Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Communications with or about a patient
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Bundle (6 properties), Coding (5 properties), Meta (5 properties), FHIRResource (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Canvas Medical 12
Other APIs Canvas Medical publishes across the network.