Canada Health Infoway

Canada Health Infoway is an independent, federally funded not-for-profit organization that leads the adoption of digital health and pan-Canadian interoperability across Canada's province- and territory-fragmented healthcare system. Infoway stewards the pan-Canadian FHIR interoperability specifications - CA Core+ and the CA Baseline profiles developed with the Canadian Institute for Health Information (CIHI) - and operates the Canadian FHIR Registry, the Canadian URI Registry, and a national Terminology Gateway. Its developer-facing API surface, published through the Accelero developer portal, is a HAPI-FHIR R4 (4.0.1) Terminology Service exposing CodeSystem, ValueSet, and ConceptMap resources with $lookup, $expand, $translate, and $validate-code operations, alongside a companion RESTful Terminology API for browsing code systems, subsets, maps, and packages. Infoway is a standards steward and terminology infrastructure operator for the Canadian market rather than a commercial clinical-data platform; the terminology content APIs are gated behind free registration and a session/token login, while the FHIR CapabilityStatement is served anonymously.

Canada Health Infoway publishes 11 API contracts indexed on the APIs.io network, including Code System API, Concept Map API, Maps API, and 8 more. Tagged areas include Healthcare, Canada, FHIR, HL7, and Interoperability.

The Canada Health Infoway catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Canada Health Infoway’s developer surface includes authentication, documentation, API reference, signup flow, engineering blog, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

41.1/100 developing ▬ flat Agent 21/100 agent aware Front door AI 2/6 trace Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 3 Agent Skills

Healthcare Canada FHIR HL7 Interoperability Terminology National Health System Digital Health StandardsCA Core

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 41.1/100 · developing

Contract Quality 9.4 / 19

Developer Ergonomics 6.3 / 15

Access Clarity 5.1 / 15

Operational Transparency 0.8 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 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 0 / 7

Typed Event Surface 6 / 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 0 / 5

Distinct Operations 0 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/canada-health-infoway/"><img src="https://apis.io/badge/canada-health-infoway/card.svg" alt="Canada Health Infoway 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
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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
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):

Access Clarity scores 34.2 — up to +13.2 composite points
Contract Quality scores 50.2 — up to +12.5 composite points
Operational Transparency scores 7.9 — up to +12.0 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/canada-health-infoway/apis.yml: open an issue on github.com/api-evangelist/canada-health-infoway 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 →

Standards implemented 2

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

OpenAPI

measured — observed by APIs.io (published)

APIs 11

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

Canada Health Infoway Code System API

The CodeSystem API from Canada Health Infoway — 5 operation(s) for codesystem.

Canada Health Infoway Concept Map API

The ConceptMap API from Canada Health Infoway — 5 operation(s) for conceptmap.

Canada Health Infoway Maps API

APIs for accessing map data

Canada Health Infoway Notification API

APIs for accessing user notifications

Canada Health Infoway Packages API

APIs for accessing package data

Canada Health Infoway Session API

APIs for programmatically logging in

Canada Health Infoway Subsets API

APIs for terminology subsets

Canada Health Infoway Value Set API

The ValueSet API from Canada Health Infoway — 8 operation(s) for valueset.

Canada Health Infoway Capability Statement API

The Capability Statement API from Canada Health Infoway — 1 operation(s) for capability statement.

Canada Health Infoway code systems API

APIs for accessing code system data

Canada Health Infoway Resource Locations API

APIs for accessing resource location data

Scroll for all 11

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Terminology FHIR API

OPEN COLLECTION

Terminology API

OPEN COLLECTION

Agent Skills 3

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

Browse and download Canadian terminology content (RESTful API)

AGENT SKILL

Translate a code between code systems (FHIR $translate)

AGENT SKILL

Validate and look up a clinical code (FHIR terminology)

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Canada Health Infoway Notifications Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Canada Health Infoway API Rules

49 rules · 42 errors 6 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Canada Health Infoway Fhir Terminology Service Api Overlay

2 actions · update · infoway-fhir-terminology-service-api-openapi.json

DERIVED

Canada Health Infoway Terminology Service Api Overlay

2 actions · update · infoway-terminology-service-api-openapi.json

DERIVED

Security Posture 2

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

Canada Health Infoway Authentication

apiKey/http/session · 3 schemes

SECURITY

Canada Health Infoway Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Canada Health Infoway Agentic Access

60 operations · 5 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

About

About

Other 2

Properties that don't map to a standard resource type

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: canada-health-infoway
url: https://raw.githubusercontent.com/api-evangelist/canada-health-infoway/refs/heads/main/apis.yml
name: Canada Health Infoway
kind: company
description: Canada Health Infoway is an independent, federally funded not-for-profit organization that leads the adoption
  of digital health and pan-Canadian interoperability across Canada's province- and territory-fragmented healthcare system.
  Infoway stewards the pan-Canadian FHIR interoperability specifications - CA Core+ and the CA Baseline profiles developed
  with the Canadian Institute for Health Information (CIHI) - and operates the Canadian FHIR Registry, the Canadian URI Registry,
  and a national Terminology Gateway. Its developer-facing API surface, published through the Accelero developer portal, is
  a HAPI-FHIR R4 (4.0.1) Terminology Service exposing CodeSystem, ValueSet, and ConceptMap resources with $lookup, $expand,
  $translate, and $validate-code operations, alongside a companion RESTful Terminology API for browsing code systems, subsets,
  maps, and packages. Infoway is a standards steward and terminology infrastructure operator for the Canadian market rather
  than a commercial clinical-data platform; the terminology content APIs are gated behind free registration and a session/token
  login, while the FHIR CapabilityStatement is served anonymously.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- Canada
- FHIR
- HL7
- Interoperability
- Terminology
- National Health System
- Digital Health
- Standards
- CA Core
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: canada-health-infoway:canada-health-infoway-codesystem-api
  name: Canada Health Infoway Code System API
  description: The CodeSystem API from Canada Health Infoway — 5 operation(s) for codesystem.
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - CodeSystem
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-codesystem-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-conceptmap-api
  name: Canada Health Infoway Concept Map API
  description: The ConceptMap API from Canada Health Infoway — 5 operation(s) for conceptmap.
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - ConceptMap
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-conceptmap-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-maps-api
  name: Canada Health Infoway Maps API
  description: APIs for accessing map data
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - Maps
  tags_raw:
  - maps
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-maps-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-notification-api
  name: Canada Health Infoway Notification API
  description: APIs for accessing user notifications
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - Notification
  tags_raw:
  - notification
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-notification-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-packages-api
  name: Canada Health Infoway Packages API
  description: APIs for accessing package data
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - Packages
  tags_raw:
  - packages
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-packages-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-session-api
  name: Canada Health Infoway Session API
  description: APIs for programmatically logging in
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - Sessions
  tags_raw:
  - session
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-session-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-subsets-api
  name: Canada Health Infoway Subsets API
  description: APIs for terminology subsets
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - subsets
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-subsets-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-valueset-api
  name: Canada Health Infoway Value Set API
  description: The ValueSet API from Canada Health Infoway — 8 operation(s) for valueset.
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - ValueSet
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-valueset-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-capability-statement-api
  name: Canada Health Infoway Capability Statement API
  description: The Capability Statement API from Canada Health Infoway — 1 operation(s) for capability statement.
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - CapabilityStatement
  tags_raw:
  - Capability Statement
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-capability-statement-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-code-systems-api
  name: Canada Health Infoway code systems API
  description: APIs for accessing code system data
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - code-systems
  tags_raw:
  - code systems
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-code-systems-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
- aid: canada-health-infoway:canada-health-infoway-resource-locations-api
  name: Canada Health Infoway Resource Locations API
  description: APIs for accessing resource location data
  humanURL: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  baseURL: https://termapi.infoway-inforoute.ca/fhir/v1
  tags:
  - Resource Locations
  properties:
  - type: OpenAPI
    url: openapi/canada-health-infoway-resource-locations-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/infoway-terminology-gateway-capabilitystatement.json
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
  - type: Documentation
    url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools/terminology-service-api
  - type: APIReference
    url: https://termapi.infoway-inforoute.ca/schema/v1/swaggerui/index.html
common:
- type: DomainSecurity
  url: security/canada-health-infoway-domain-security.yml
- type: AgenticAccess
  url: agentic-access/canada-health-infoway-agentic-access.yml
- type: Authentication
  url: authentication/canada-health-infoway-authentication.yml
- type: Conventions
  url: conventions/canada-health-infoway-conventions.yml
- type: ErrorCatalog
  url: errors/canada-health-infoway-problem-types.yml
- type: Lifecycle
  url: lifecycle/canada-health-infoway-lifecycle.yml
- type: Conformance
  url: conformance/canada-health-infoway-conformance.yml
- type: DataModel
  url: data-model/canada-health-infoway-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/canada-health-infoway-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: ToolCrosswalk
  url: mcp/canada-health-infoway-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/canada-health-infoway-llms.txt
- type: Overlay
  name: FHIR Terminology Service enhancements
  url: overlays/canada-health-infoway-fhir-terminology-service-api-overlay.yaml
- type: Overlay
  name: RESTful Terminology Service enhancements
  url: overlays/canada-health-infoway-terminology-service-api-overlay.yaml
- type: Webhooks
  url: asyncapi/canada-health-infoway-notifications-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: TermsOfService
  url: https://ic.infoway-inforoute.ca/en/about/tou?title=8_UserReferencesAndSupports/Terms_And_License_Agreements
- type: PrivacyPolicy
  url: https://www.infoway-inforoute.ca/en/privacy-policy
- type: Website
  url: https://www.infoway-inforoute.ca/en/
- type: DeveloperPortal
  url: https://accelero.infoway-inforoute.ca/en/tools/developer-tools
- type: Documentation
  url: https://www.infoway-inforoute.ca/en/what-we-do/connected-care/digital-health-standards
- type: APIReference
  url: https://termapi.infoway-inforoute.ca/fhir/fhir-apidocs/v1/swagger-ui
- type: SignUp
  url: https://accelero.infoway-inforoute.ca/en/register
- type: Login
  url: https://auth-users.infoway-inforoute.ca/auth/UI/Login
- type: Blog
  url: https://www.infoway-inforoute.ca/en/blog
- type: About
  url: https://www.infoway-inforoute.ca/en/about-us
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Canada Health Infoway API — frequently asked questions

Does Canada Health Infoway have an API?

Yes. APIs.io lists 11 APIs from Canada Health Infoway, including Canada Health Infoway Code System API, Canada Health Infoway Concept Map API and Canada Health Infoway Maps API, and 8 more.

Is there an OpenAPI specification for the Canada Health Infoway API?

Yes. APIs.io indexes 11 OpenAPI specifications for Canada Health Infoway, each linked for download from this page.

How do I authenticate with the Canada Health Infoway API?

Canada Health Infoway uses bearer-token authentication (apiKey/http/session · 3 schemes). The details are profiled on APIs.io as Canada Health Infoway Authentication.

Is the Canada Health Infoway API ready for AI agents?

Canada Health Infoway has a Kin Score of 41.1 out of 100 (developing) and an Agent Readiness score of 20.5 (agent-aware), scored by API Evangelist on 2026-11-06.

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/canada-health-infoway"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/canada-health-infoway/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/canada-health-infoway/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.