Elation Health

Elation Health Lab Facility Identifiers API

The Lab Facility Identifiers API from Elation Health — 6 operation(s) for lab facility identifiers.

GitHub OpenAPI
Business capability
Laboratory Services Management BC-2860.10

Operations 12

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

DELETE /lab_facility_identifiers/{id} Delete a lab facility identifier (legacy) · Delete Lab Facility Identifiers #
Ask an LLM
“Can I remove a lab facility identifier using the older unversioned endpoint?”
“Which legacy call deletes a practice's lab facility mapping?”
Tell an agent destructive · confirm first
Delete legacy lab facility identifier {id}.
Remove facility mapping {id} through the original lab facility route.
GET /lab_facility_identifiers/{id} [WIP] Look up a lab facility identifier (legacy WIP) · Get Lab Facility Identifiers #
Ask an LLM
“What does the work-in-progress legacy endpoint return for one lab facility identifier?”
“Can I read a single lab facility mapping on the old unversioned path?”
Tell an agent
Fetch legacy lab facility identifier {id}.
Show facility mapping {id} from the WIP lab facility route.
PUT /lab_facility_identifiers/{id} [WIP] Replace a lab facility identifier (legacy WIP) · Put Lab Facility Identifiers #
Ask an LLM
“Which legacy WIP call overwrites a whole lab facility identifier?”
“Must I resend vendor, practice and both facility codes when replacing a mapping on the old path?”
Tell an agent
Replace legacy identifier {id} with vendor {vendor}, practice {practice}, lab facility {lab_facility}, practice facility {practice_facility}, active {active}.
Overwrite old-route facility mapping {id} in full.
PATCH /lab_facility_identifiers/{id} [WIP] Patch a lab facility identifier (legacy WIP) · Patch Lab Facility Identifiers #
Ask an LLM
“Can I deactivate a lab facility mapping with the legacy PATCH?”
“Is there an old WIP endpoint to change only the description of a facility identifier?”
Tell an agent
Set active to {active} on legacy facility identifier {id}.
Patch the description of old-route mapping {id} to {description}.
GET /lab_facility_identifiers/ List lab facility identifiers (legacy) · Find Lab Facility Identifiers #
Ask an LLM
“Where do I find all lab facility identifiers on the legacy unversioned API?”
“Does the old lab facility search need an Authentication header?”
Tell an agent
Using credential {auth}, list every legacy lab facility identifier.
Authenticate with {auth} and pull the old-route facility mappings.
POST /lab_facility_identifiers/ [WIP] Add a lab facility identifier (legacy WIP) · Create Lab Facility Identifiers #
Ask an LLM
“What does the old WIP endpoint need to register a new lab facility mapping?”
“Can I attach a compendium when adding a facility identifier through the legacy route?”
Tell an agent
Create a legacy identifier: vendor {vendor}, practice {practice}, lab facility {lab_facility}, practice facility {practice_facility}.
Add an old-route mapping with compendium {compendium} for vendor {vendor}.
GET /api/2.0/lab_facility_identifiers/ List lab vendor integrations · List Lab Facility Identifiers #
Ask an LLM
“How do I see every lab vendor integration configured for my practices?”
“Can I sort and page the v2.0 lab facility identifier list?”
Tell an agent
List v2.0 lab facility identifiers ordered by {order_by}.
Show the next {limit} lab vendor integrations starting at {offset}.
POST /api/2.0/lab_facility_identifiers/ Set up a lab vendor integration · Create Lab Facility Identifier #
Ask an LLM
“What's required to connect a practice to a lab vendor's facility?”
“Can I mark a new lab integration as bidirectional?”
Tell an agent
Create a v2.0 lab integration for practice {practice} with vendor {vendor}, lab facility {lab_facility}, practice facility {practice_facility}, active {active}.
Set up a user-facing lab connection {lab_connection} for practice {practice}.
DELETE /api/2.0/lab_facility_identifiers/{id}/ Remove a lab vendor integration · Delete Lab Facility Identifier #
Ask an LLM
“Can I disconnect a practice from a lab by deleting its integration?”
“What deletes a lab facility identifier in API v2.0?”
Tell an agent destructive · confirm first
Delete v2.0 lab integration {id}.
Disconnect lab vendor integration {id}.
GET /api/2.0/lab_facility_identifiers/{id}/ Get one lab vendor integration · Retrieve Lab Facility Identifier #
Ask an LLM
“Can I check the settings of a single lab vendor integration?”
“Which facility codes does one v2.0 lab integration use?”
Tell an agent
Retrieve v2.0 lab integration {id}.
Show the facility codes for lab vendor integration {id}.
PATCH /api/2.0/lab_facility_identifiers/{id}/ Edit part of a lab vendor integration · Partially Update Lab Facility Identifier #
Ask an LLM
“Can I switch a lab integration's bidirectional connection on without resending everything?”
“Is there a partial update to change a lab integration's secondary practice id?”
Tell an agent
Set bidirectional connection {bidi_connection} on lab integration {id}.
Change the practice secondary id of lab integration {id} to {practice_secondary_id}.
PUT /api/2.0/lab_facility_identifiers/{id}/ Replace a lab vendor integration · Update Lab Facility Identifier #
Ask an LLM
“Which v2.0 call fully replaces a lab vendor integration?”
“Must every required field be resent when replacing a lab integration?”
Tell an agent
Replace lab integration {id} with vendor {vendor}, practice {practice}, lab facility {lab_facility}, practice facility {practice_facility}, active {active}.
Do a full v2.0 PUT on lab integration {id}.

Documentation

📖
Documentation
https://docs.elationhealth.com/docs/oauth
📖
APIReference
https://docs.elationhealth.com/reference/get-token
📖
Documentation
https://docs.elationhealth.com/reference/scopes
📖
Documentation
https://docs.elationhealth.com/docs/api-overview
📖
APIReference
https://docs.elationhealth.com/reference
📖
APIReference
https://docs.elationhealth.com/reference/insurance-eligibility
📖
APIReference
https://docs.elationhealth.com/reference/message-threads
📖
Documentation
https://docs.elationhealth.com/docs/webhooks
📖
APIReference
https://docs.elationhealth.com/reference/event-subscriptions
📖
Documentation
https://help.elationhealth.com/articles/rest/overview/api-overview
📖
APIReference
https://help.elationhealth.com/api-reference
📖
Authentication
https://help.elationhealth.com/articles/rest/overview/oauth

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-lab-facility-identifiers-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-facility-identifier-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-patched-facility-identifier-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-paginated-facility-identifier-list-schema.json

Other Resources

🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/asyncapi/elation-health-events-webhooks.yml
🔗
OAuthScopes
https://help.elationhealth.com/articles/rest/overview/scopes
🔗
ChangeLog
https://help.elationhealth.com/articles/rest/changelog/changelog

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/elation-health:elation-health-lab-facility-identifiers-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

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.

OpenAPI Specification

elation-health-lab-facility-identifiers-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Elation Health Lab Facility Identifiers API
  version: '1.0'
  description: 'Operations tagged Lab Facility Identifiers across 2 of this provider''s published API definitions: elation-api-settings.json, elation-health-api-full-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://sandbox.elationemr.com/api/2.0
- description: Sandbox Server
  url: https://sandbox.elationemr.com
- description: Production Server
  url: https://api.app.elationemr.com
tags:


# --- truncated at 32 KB (35 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-lab-facility-identifiers-api-openapi.yml