Elation Health

Elation Health Lab Orders API

Laboratory order management

GitHub OpenAPI
Business capability
Computerised Provider Order Entry BC-2830.20

Operations 18

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 /lab_orders/ Find lab orders (legacy endpoint) · Find Lab Orders #
Ask an LLM
“Where can I look up a patient's lab orders on the legacy unversioned endpoint?”
“Can the older lab order search show only orders that are still unsigned?”
Tell an agent
Find legacy lab orders for patient {patient}.
Search the old lab orders endpoint for orders signed between {from} and {to}.
POST /lab_orders/ Place a lab order (legacy endpoint) · Create Lab Order #
Ask an LLM
“How do I place a new lab order for a patient through the legacy endpoint?”
“What does the original lab order create call need besides the patient and ordering physician?”
Tell an agent
Create a legacy lab order for patient {patient} ordered by physician {physician} in practice {practice} dated {date}.
Use the old lab orders endpoint to send patient {patient}'s order to lab vendor {vendor}.
GET /lab_orders/{id}/printable Get a printable lab order (legacy path) · Retrieve the Printable Lab Order View #
Ask an LLM
“Can I get a print-ready view of a lab order from the legacy printable path?”
“Is there a way to print a lab order without the page header on the older endpoint?”
Tell an agent
Get the legacy printable view of lab order {lab_order}.
Print lab order {order} from the old path with print_header set to {header}.
GET /lab_orders/{id} Get a lab order (legacy endpoint) · Get Lab Order #
Ask an LLM
“Can I fetch a single lab order by id on the legacy unversioned path?”
“What details come back for one lab order from the original endpoint?”
Tell an agent
Get legacy lab order {id}.
Pull up lab order {id} from the older lab orders endpoint.
PUT /lab_orders/{id} Replace a lab order (legacy PUT) · Update Lab Order #
Ask an LLM
“Can I overwrite a whole lab order through the legacy PUT endpoint?”
“Which legacy call does a full replacement of a lab order record?”
Tell an agent
Replace legacy lab order {id} in full, keeping patient {patient} and ordering physician {physician}.
Overwrite every field of old-endpoint lab order {id} with test date {test_date}.
PATCH /lab_orders/{id} Edit fields on a lab order (legacy PATCH) · Update Lab Order #
Ask an LLM
“Can I change just the facility or follow-up method on a lab order with the legacy PATCH?”
“Which legacy call edits only some fields of a lab order?”
Tell an agent
Patch legacy lab order {id} to set the follow-up method to {method}.
On the old endpoint, mark lab order {id} as confidential {confidential}.
DELETE /lab_orders/{id} Delete a lab order (legacy endpoint) · Delete Lab Order #
Ask an LLM
“How do I remove a lab order using the legacy unversioned endpoint?”
“Can I delete a lab order that was placed by mistake through the old path?”
Tell an agent destructive · confirm first
Delete legacy lab order {id}.
Remove lab order {id} via the original lab orders endpoint.
GET /api/2.0/lab_orders/ List lab orders (v2.0) · List Lab Orders #
Ask an LLM
“Is it possible to page through all lab orders in a practice with the 2.0 API?”
“Can I list lab orders by document date range in version 2.0?”
Tell an agent
List v2.0 lab orders for patient {patient}.
List 2.0 lab orders with a document date after {after}, {limit} per page.
POST /api/2.0/lab_orders/ Place a lab order (v2.0) · Create Lab Order #
Ask an LLM
“How do I create a lab order with specimens and special insurance in the 2.0 API?”
“What fields are required to place a lab order in version 2.0?”
Tell an agent
Create a v2.0 lab order for patient {patient} by physician {physician} in practice {practice} dated {date}.
Place a 2.0 lab order for patient {patient} with specimens {specimens}.
DELETE /api/2.0/lab_orders/{id}/ Delete a lab order (v2.0) · Delete Lab Order #
Ask an LLM
“What's the 2.0 way to delete a lab order?”
“Can I remove a lab order entered on the wrong patient in version 2.0?”
Tell an agent destructive · confirm first
Delete v2.0 lab order {id}.
Remove lab order {id} using the 2.0 lab orders endpoint.
GET /api/2.0/lab_orders/{id}/ Get a lab order (v2.0) · Retrieve Lab Order #
Ask an LLM
“Which v2.0 call returns one lab order with its requisition and submissions?”
“Does the v2.0 lab order record show who signed it and when?”
Tell an agent
Get v2.0 lab order {id}.
Retrieve lab order {id} from the 2.0 API including its signed date.
PATCH /api/2.0/lab_orders/{id}/ Update some fields of a lab order (v2.0) · Partially Update Lab Order #
Ask an LLM
“Can I change only the test date on a lab order in the 2.0 API?”
“Which v2.0 call edits a few lab order fields without resending the rest?”
Tell an agent
Patch v2.0 lab order {id} to set test date {test_date}.
Update the tags on 2.0 lab order {id} to {tags}.
PUT /api/2.0/lab_orders/{id}/ Replace a lab order (v2.0 PUT) · Update Lab Order #
Ask an LLM
“Can I fully replace a lab order record in the v2.0 API?”
“Which 2.0 call overwrites an entire lab order rather than patching it?”
Tell an agent
Replace v2.0 lab order {id} in full for patient {patient}.
Overwrite 2.0 lab order {id} with vendor {vendor} and all required fields.
GET /api/2.0/lab_orders/{id}/printable/ Get a printable lab order (v2.0) · Retrieve the Printable Lab Order View #
Ask an LLM
“How do I get a print-ready lab order from the 2.0 printable endpoint?”
“Can I leave the header off a printed lab order in version 2.0?”
Tell an agent
Get the v2.0 printable view of lab order {id}.
Print lab order {id} from the 2.0 API with print_header {header}.
GET /lab_orders/{id}/ Get a lab order with its tests and status · Retrieve a lab order #
Ask an LLM
“Which tests and status does a lab order have on the trailing-slash lab orders path?”
“What clinical notes and lab vendor are recorded on a given lab order record?”
Tell an agent
Show the tests and status on lab order record {id}.
Look up legacy lab order {id} with its clinical notes and lab vendor.
PUT /lab_orders/{id}/ Replace a lab order's tests and status · Update a lab order #
Ask an LLM
“Can I replace the test list and status of a lab order in one call?”
“How do I overwrite a lab order's clinical notes, physician and tests together on the legacy endpoint?”
Tell an agent
Replace lab order record {id} with physician {physician}, tests {tests} and status {status}.
Overwrite lab order {id} for patient {patient} with clinical notes {notes}.
PATCH /lab_orders/{id}/ Change a lab order's status or lab vendor · Partially update a lab order #
Ask an LLM
“How do I change only the status of a lab order?”
“Can I switch the lab vendor on an existing lab order without replacing it?”
Tell an agent
Set the status of lab order {id} to {status}.
Switch lab order {id} to lab vendor {vendor}.
DELETE /lab_orders/{id}/ Delete a lab order record with tests · Delete a lab order #
Ask an LLM
“Can I delete a lab order record from the trailing-slash lab orders path?”
“Can I permanently drop a lab order along with its tests?”
Tell an agent destructive · confirm first
Delete lab order record {id} and its tests.
Drop lab order {id} from the tests-and-status lab orders path.

Documentation

📖
Documentation
https://docs.elationhealth.com/reference/api-overview
📖
Authentication
https://docs.elationhealth.com/reference/oauth

Specifications

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

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-lab-order-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-patched-lab-order-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-lab-order-create-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-paginated-lab-order-list-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-lab-order-2-schema.json

Other Resources

🔗
Sandbox
https://www.elationhealth.com/contact-us/sandbox/

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-lab-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-lab-orders-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Elation Health Lab Orders API
  version: '1.0'
  description: 'Operations tagged Lab Orders across 3 of this provider''s published API definitions: elation-api-settings.json, elation-health-api-full-openapi.yaml, elation-health-elation-health-api-openapi.yml. 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
- url: https://app.elationemr.com/api/2.0
  description: Production
tags:


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