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.
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 ELLKAY the way a machine reads it — 60 machine-readable artifacts across 2 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 — ELLKAY scores 45.9/100 (developing), with a separate agent-readiness read of 34/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from ELLKAY's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ellkay/"
title="ELLKAY on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ellkay.svg"
alt="ELLKAY Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ellkay/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ellkay/"
title="ELLKAY on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ellkay/card.svg"
alt="ELLKAY Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ELLKAY
Each block below is one kind of artifact we hold for ELLKAY. 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 42
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.
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 ...
ELLKAY Account API
The Account API from ELLKAY — 2 operation(s) for account.
ELLKAY Appointment API
The Appointment API from ELLKAY — 2 operation(s) for appointment.
ELLKAY Binary API
The Binary API from ELLKAY — 1 operation(s) for binary.
ELLKAY Clinical Impression API
The ClinicalImpression API from ELLKAY — 2 operation(s) for clinicalimpression.
ELLKAY Communication API
The Communication API from ELLKAY — 2 operation(s) for communication.
ELLKAY Communication Request API
The CommunicationRequest API from ELLKAY — 2 operation(s) for communicationrequest.
ELLKAY Condition API
The Condition API from ELLKAY — 2 operation(s) for condition.
ELLKAY Coverage API
The Coverage API from ELLKAY — 2 operation(s) for coverage.
ELLKAY Diagnostic Report API
The DiagnosticReport API from ELLKAY — 2 operation(s) for diagnosticreport.
ELLKAY Encounter API
The Encounter API from ELLKAY — 2 operation(s) for encounter.
ELLKAY Family Member History API
The FamilyMemberHistory API from ELLKAY — 2 operation(s) for familymemberhistory.
ELLKAY Immunization API
The Immunization API from ELLKAY — 2 operation(s) for immunization.
ELLKAY LK Appointments API
Ellkay Appointment endpoints
ELLKAY LK Bridge API
Ellkay Bridge
ELLKAY LK Charges API
Charge details
ELLKAY LK Documents API
LKDocuments endpoints
ELLKAY LK Master List API
Master List.
ELLKAY LK Patient Balance API
Load patient's balances. Allows patients to apply payments.
ELLKAY LK Patient Data Link API
PatientDataLink endpoint
ELLKAY Location API
The Location API from ELLKAY — 2 operation(s) for location.
ELLKAY Medication API
The Medication API from ELLKAY — 2 operation(s) for medication.
ELLKAY Medication Statement API
The MedicationStatement API from ELLKAY — 2 operation(s) for medicationstatement.
ELLKAY Metadata API
The Metadata API from ELLKAY — 1 operation(s) for metadata.
ELLKAY Observation API
The Observation API from ELLKAY — 2 operation(s) for observation.
ELLKAY Operations API
The Operations API from ELLKAY — 1 operation(s) for operations.
ELLKAY Organization API
The Organization API from ELLKAY — 2 operation(s) for organization.
ELLKAY Patient API
The Patient API from ELLKAY — 2 operation(s) for patient.
ELLKAY Person API
The Person API from ELLKAY — 2 operation(s) for person.
ELLKAY Practitioner API
The Practitioner API from ELLKAY — 2 operation(s) for practitioner.
ELLKAY Procedure API
The Procedure API from ELLKAY — 2 operation(s) for procedure.
ELLKAY Questionnaire API
The Questionnaire API from ELLKAY — 2 operation(s) for questionnaire.
ELLKAY Questionnaire Response API
The QuestionnaireResponse API from ELLKAY — 2 operation(s) for questionnaireresponse.
ELLKAY Related Person API
The RelatedPerson API from ELLKAY — 2 operation(s) for relatedperson.
ELLKAY Service Request API
The ServiceRequest API from ELLKAY — 2 operation(s) for servicerequest.
ELLKAY Slot API
The Slot API from ELLKAY — 2 operation(s) for slot.
ELLKAY Update Patient API
UpdatePatient endpoint
ELLKAY Allergy Intolerance API
The Allergy Intolerance API from ELLKAY — 2 operation(s) for allergy intolerance.
ELLKAY Document Reference API
The Document Reference API from ELLKAY — 2 operation(s) for document reference.
ELLKAY Insurance Plan API
The Insurance Plan API from ELLKAY — 2 operation(s) for insurance plan.
ELLKAY Medication Request API
The Medication Request API from ELLKAY — 2 operation(s) for medication request.
Scroll within the panel for all 42 ·
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.
Ellkay Rate Limits
RATE LIMITSSemantic 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.
Ellkay 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.
ELLKAY API Rules
SPECTRALJSON Schema 12
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.
Account
JSON SCHEMAAllergyIntolerance
JSON SCHEMAAppointment
JSON SCHEMABinary
JSON SCHEMABundle
JSON SCHEMACapabilityStatement
JSON SCHEMAScroll within the panel for all 12 ·
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.
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 ELLKAY — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ellkay · machine-readable index on apis.io
This is an independent, third-party profile of ELLKAY, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.