Elation Health

Elation Health Sleep Orders API

The Sleep Orders API from Elation Health — 4 operation(s) for sleep orders.

GitHub OpenAPI
Business capability
Computerised Provider Order Entry BC-2830.20

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

GET /sleep_orders/{id} Look up a sleep study order (legacy) · Get Sleep Order #
Ask an LLM
“Can I pull one sleep study order by id from the older unversioned endpoint?”
“What does the legacy sleep orders path return for a single order?”
Tell an agent
Fetch legacy sleep order {id}.
Open sleep study order {id} from the original route.
PUT /sleep_orders/{id} Replace a sleep study order (legacy PUT) · Update Sleep Order #
Ask an LLM
“Which legacy PUT overwrites an entire sleep study order?”
“Must I resend the clinical reason and prescriber when replacing a sleep order on the old path?”
Tell an agent
Replace legacy sleep order {id} for patient {patient} with sleep lab {ancillary_company} and reason {clinical_reason}.
Overwrite an old-route sleep order prescribed by {prescribing_user} at practice {practice}.
PATCH /sleep_orders/{id} Patch a sleep study order (legacy PATCH) · Update Sleep Order #
Ask an LLM
“Can I change only the sleep center on an order with the legacy PATCH?”
“Is there an old-path partial edit for a sleep order's diagnosis codes?”
Tell an agent
Move legacy sleep order {id} to sleep center {sleep_center}.
Patch the ICD-10 codes on an old-route sleep order to {icd10_codes}.
DELETE /sleep_orders/{id} Delete a sleep study order (legacy) · Delete Sleep Order #
Ask an LLM
“Can I cancel a sleep study order by deleting it on the unversioned API?”
“Which old call removes a sleep order?”
Tell an agent destructive · confirm first
Delete legacy sleep order {id}.
Remove sleep study order {id} via the original route.
GET /sleep_orders/ Search sleep study orders (legacy) · Find Sleep Orders #
Ask an LLM
“Can I find a patient's sleep study orders on the legacy unversioned path?”
“Does the old sleep order search filter by practice?”
Tell an agent
Find legacy sleep orders for patient {patient}.
Search old-route sleep orders at practice {practice}.
POST /sleep_orders/ Order a sleep study (legacy) · Create Sleep Order #
Ask an LLM
“What must I send to place a sleep study order through the legacy endpoint?”
“Can the old create call include ICD-10 codes and a follow-up method?”
Tell an agent
Create a legacy sleep order for patient {patient} at sleep lab {ancillary_company} for {clinical_reason}, prescribed by {prescribing_user}.
Place an old-route sleep order at practice {practice} with follow-up by {follow_up_method}.
GET /api/2.0/sleep_orders/ List sleep study orders · List Sleep Orders #
Ask an LLM
“How do I list the sleep study orders for one patient?”
“Can I page and sort sleep orders across a practice in v2.0?”
Tell an agent
List v2.0 sleep orders for patient {patient}.
Show sleep orders at practice {practice} ordered by {order_by}, {limit} per page.
POST /api/2.0/sleep_orders/ Place a sleep study order · Create Sleep Order #
Ask an LLM
“What's required to order a sleep study for a patient in API v2.0?”
“Can I set a test date and specific sleep tests on a new order?”
Tell an agent
Order sleep tests {tests} for patient {patient} at sleep lab {ancillary_company}, reason {clinical_reason}.
Create a v2.0 sleep order for patient {patient} prescribed by {prescribing_user} with test date {test_date}.
DELETE /api/2.0/sleep_orders/{id}/ Delete a sleep study order · Delete Sleep Order #
Ask an LLM
“Can I delete a sleep order placed in error through API v2.0?”
“What removes a sleep study order in the current API?”
Tell an agent destructive · confirm first
Delete v2.0 sleep order {id}.
Remove the mistaken sleep study order {id}.
GET /api/2.0/sleep_orders/{id}/ Get one sleep study order · Retrieve Sleep Order #
Ask an LLM
“What does a single v2.0 sleep order record include?”
“Can I check the resolution of a sleep study order?”
Tell an agent
Retrieve v2.0 sleep order {id}.
Show the tests and resolution on sleep order {id}.
PATCH /api/2.0/sleep_orders/{id}/ Edit part of a sleep study order · Partially Update Sleep Order #
Ask an LLM
“Can I record the resolution of a sleep order without resending it all?”
“Is there a v2.0 partial update to sign a sleep order?”
Tell an agent
Set the resolution of sleep order {id} to {resolution}.
Mark v2.0 sleep order {id} signed by {signed_by}.
PUT /api/2.0/sleep_orders/{id}/ Replace a sleep study order · Update Sleep Order #
Ask an LLM
“Which v2.0 call fully replaces a sleep order?”
“Do I have to resend the tests list when replacing a sleep order?”
Tell an agent
Replace sleep order {id} with tests {tests} for patient {patient}.
Do a full v2.0 PUT on sleep order {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-sleep-orders-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-sleep-order-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-patched-sleep-order-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-paginated-sleep-order-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-sleep-orders-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-sleep-orders-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Elation Health Sleep Orders API
  version: '1.0'
  description: 'Operations tagged Sleep Orders 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 (34 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-sleep-orders-api-openapi.yml