ELLKAY

ELLKAY is a healthcare data interoperability and data-management company that connects disparate health IT systems so clinical and financial data can move where it is needed. Its LKOpera, LKOrbit, and LKOasis product lines provide interface-engine integration, orders and results, payer data retrieval, network/lab connectivity, and data archiving/migration across 750+ EMR/PM systems, 400+ hospitals, 58k+ practices, and 725+ laboratories. For developers, ELLKAY exposes the LKCloud platform: a single-endpoint Interop API (proprietary LK* operations) and a full HL7 FHIR R4 RESTful API, both authenticated with OAuth 2.0 against the LKIdentity authorization server and routed with a SiteServiceKey.

ELLKAY publishes 2 APIs on the APIs.io network. Tagged areas include Company, Healthcare, Interoperability, FHIR, and HL7.

ELLKAY’s developer surface includes documentation, API reference, authentication, changelog, engineering blog, support, sandbox, and 13 more developer resources.

🌐 Visit website 📡 Source on GitHub

28.5/100 thin ▬ flat Agent 12/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessSelf serve

2 APIs

Company Healthcare Interoperability FHIR HL7 EHR Integration Health Data

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 28.5/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 6.7 / 17

Access Clarity 2.9 / 17

Operational Transparency 4.1 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 5.4 / 15

Agent readiness — 12/100 · agent aware

Machine-Readable Contract 0 / 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 0 / 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

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/.

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 github.com/api-evangelist/ellkay: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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

LKCloud Interop API

Single-endpoint healthcare interoperability API exposing proprietary LK* operations (appointments, patient bridge/search, documents, charges, patient balance, master lists) that...

LKCloud FHIR R4 API

HL7 FHIR R4 RESTful API (read/search/create/update/delete across R4 resources) over the ELLKAY interoperability platform, with a published CapabilityStatement. OAuth 2.0 Bearer ...

Rate Limits 1

Documented rate limits and quota policies.

Ellkay Rate Limits

1 limits

RATE LIMITS

Security Posture 2

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

Ellkay Authentication

oauth2 · 3 schemes

SECURITY

Ellkay Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

RateLimits

RateLimits

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: ellkay
name: ELLKAY
description: 'ELLKAY is a healthcare data interoperability and data-management company that connects disparate health IT systems
  so clinical and financial data can move where it is needed. Its LKOpera, LKOrbit, and LKOasis product lines provide interface-engine
  integration, orders and results, payer data retrieval, network/lab connectivity, and data archiving/migration across 750+
  EMR/PM systems, 400+ hospitals, 58k+ practices, and 725+ laboratories. For developers, ELLKAY exposes the LKCloud platform:
  a single-endpoint Interop API (proprietary LK* operations) and a full HL7 FHIR R4 RESTful API, both authenticated with OAuth
  2.0 against the LKIdentity authorization server and routed with a SiteServiceKey.'
url: https://raw.githubusercontent.com/api-evangelist/ellkay/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- insight-partners
x-tier: stub
x-tier-reason: portfolio-lead
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
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://cdn.prod.website-files.com/68470d9028f4a074323fde70/689b3ac60177b4bae93d407b_Asset%2028.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Healthcare
- Interoperability
- FHIR
- HL7
- EHR Integration
- Health Data
tags_raw:
- Company
- Healthcare
- Interoperability
- FHIR
- HL7
- EHR Integration
- Health Data
- API
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: LKCloud Interop API
  description: Single-endpoint healthcare interoperability API exposing proprietary LK* operations (appointments, patient
    bridge/search, documents, charges, patient balance, master lists) that bi-directionally connect applications to hundreds
    of EHR/PM data sources. JSON over HTTPS, invoked as POST operations; OAuth 2.0 Bearer + SiteServiceKey.
  humanURL: https://lkcloud-api.readme.io/docs/lk-cloud-overview
  baseURL: https://services.lkcloud.com
  tags:
  - Interoperability
  - EHR Integration
  - Healthcare
  properties:
  - type: Documentation
    url: https://lkcloud-api.readme.io/docs/lk-cloud-overview
  - type: APIReference
    url: https://lkcloud-api.readme.io/reference
- name: LKCloud FHIR R4 API
  description: HL7 FHIR R4 RESTful API (read/search/create/update/delete across R4 resources) over the ELLKAY interoperability
    platform, with a published CapabilityStatement. OAuth 2.0 Bearer + SiteServiceKey; errors returned as FHIR OperationOutcome
    resources.
  humanURL: https://lkcloud-api.readme.io/docs/lk-cloud-overview
  baseURL: https://fhir.lkcloud.com/R4
  tags:
  - FHIR
  - HL7
  - Healthcare
  properties:
  - type: APIReference
    url: https://lkcloud-api.readme.io/reference
  - type: CapabilityStatement
    url: https://fhir.lkcloud.com/R4/metadata
common:
- type: Website
  url: https://www.ellkay.com/
- type: DeveloperPortal
  url: https://lkcloud-api.readme.io/
- type: Documentation
  url: https://lkcloud-api.readme.io/docs/lk-cloud-overview
- type: APIReference
  url: https://lkcloud-api.readme.io/reference
- type: Authentication
  url: authentication/ellkay-authentication.yml
- type: ChangeLog
  url: changelog/ellkay-changelog.yml
- type: Blog
  url: https://www.ellkay.com/news
- type: Support
  url: https://www.ellkay.com/support
- type: Login
  url: https://dashboard.ellkay.com/Login
- type: PrivacyPolicy
  url: https://www.ellkay.com/privacy-policy
- type: LLMsTxt
  url: llms/ellkay-llms.txt
- type: WellKnown
  url: well-known/ellkay-well-known.yml
- type: Conventions
  url: conventions/ellkay-conventions.yml
- type: ErrorCatalog
  url: errors/ellkay-error-codes.yml
- type: RateLimits
  url: rate-limits/ellkay-rate-limits.yml
- type: Lifecycle
  url: lifecycle/ellkay-lifecycle.yml
- type: Conformance
  url: conformance/ellkay-conformance.yml
- type: Sandbox
  url: sandbox/ellkay-sandbox.yml
- type: X-MCPServerCandidate
  url: mcp/ellkay-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: DomainSecurity
  url: security/ellkay-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/ellkay"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/ellkay/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.