Elation Health Cardiac Orders API

The Cardiac Orders API from Elation Health — 4 operation(s) for cardiac orders.

Documentation 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 /cardiac_orders/{id} Look up a cardiac order (legacy endpoint) · Get Cardiac Order #

Ask an LLM

“How do I fetch a single cardiac order from the legacy unversioned path?”

“What does the old cardiac orders endpoint return for one order?”

Tell an agent

Fetch legacy cardiac order {id}.

Show me cardiac order {id} using the original endpoint.

PUT /cardiac_orders/{id} Replace a cardiac order (legacy PUT) · Update Cardiac Order #

Ask an LLM

“Can I resend a whole cardiac order through the legacy PUT?”

“Which fields are mandatory when overwriting a cardiac order on the old endpoint?”

Tell an agent

Replace legacy cardiac order {id} for patient {patient} with clinical reason {clinical_reason}, prescribed by {prescribing_user}.

Overwrite the old-style cardiac order sent to ancillary company {ancillary_company} with document date {document_date}.

PATCH /cardiac_orders/{id} Patch a cardiac order (legacy PATCH) · Update Cardiac Order #

Ask an LLM

“Can I add ICD-10 codes to a cardiac order with the legacy PATCH?”

“What legacy call changes only a cardiac order's follow-up method?”

Tell an agent

Patch legacy cardiac order {id} to use ICD-10 codes {icd10_codes}.

Mark the old-style cardiac order confidential {confidential} and set follow-up to {follow_up_method}.

DELETE /cardiac_orders/{id} Delete a cardiac order (legacy endpoint) · Delete Cardiac Order #

Ask an LLM

“How do I remove a cardiac order with the legacy API?”

“Can the unversioned cardiac orders path delete an order?”

Tell an agent destructive · confirm first

Delete legacy cardiac order {id}.

Remove cardiac order {id} through the old endpoint.

GET /cardiac_orders/ Find cardiac orders by patient (legacy) · Find Cardiac Orders #

Ask an LLM

“How can I search cardiac orders for one patient on the legacy endpoint?”

“Can the old cardiac order finder filter by practice?”

Tell an agent

Find legacy cardiac orders for patient {patient}.

Search old-style cardiac orders at practice {practice}.

POST /cardiac_orders/ Order a cardiac test (legacy endpoint) · Create Cardiac Order #

Ask an LLM

“How do I place a cardiac order through the legacy unversioned API?”

“Which fields must a new cardiac order carry on the old endpoint?”

Tell an agent

Create a legacy cardiac order for patient {patient} at practice {practice} with reason {clinical_reason}, sent to {ancillary_company}.

Place an old-style cardiac order for tests {tests} ordered by {prescribing_user}.

GET /api/2.0/cardiac_orders/ List cardiac orders · List Cardiac Orders #

Ask an LLM

“Which cardiac orders exist for a patient in Elation?”

“Can I page through a practice's cardiac orders sorted by a field?”

Tell an agent

List cardiac orders for patient {patient}.

Show practice {practice}'s cardiac orders ordered by {order_by}, {limit} at a time.

POST /api/2.0/cardiac_orders/ Place a cardiac order · Create Cardiac Order #

Ask an LLM

“How do I order an ECG or other cardiac test for a patient through API v2?”

“Can a new cardiac order be sent to a specific cardiac center?”

Tell an agent

Order cardiac tests {tests} for patient {patient} at practice {practice}, reason {clinical_reason}.

Send a v2 cardiac order to cardiac center {cardiac_center} via {ancillary_company}, prescribed by {prescribing_user}.

DELETE /api/2.0/cardiac_orders/{id}/ Delete a cardiac order · Delete Cardiac Order #

Ask an LLM

“How do I delete a cardiac order in v2?”

“Can I cancel a cardiac order that was entered by mistake?”

Tell an agent destructive · confirm first

Delete cardiac order {id}.

Remove v2 cardiac order {id}.

GET /api/2.0/cardiac_orders/{id}/ Get one cardiac order · Retrieve Cardiac Order #

Ask an LLM

“How do I see the tests and resolution on one cardiac order?”

“What does a single v2 cardiac order record contain?”

Tell an agent

Get cardiac order {id}.

Retrieve v2 cardiac order {id} with its tests.

PATCH /api/2.0/cardiac_orders/{id}/ Update part of a cardiac order · Partially Update Cardiac Order #

Ask an LLM

“Can I record a test date on an existing cardiac order without resending it?”

“How do I sign a cardiac order in v2?”

Tell an agent

Set the test date on cardiac order {id} to {test_date}.

Mark v2 cardiac order {id} signed by {signed_by} on {signed_date}.

PUT /api/2.0/cardiac_orders/{id}/ Replace a cardiac order · Update Cardiac Order #

Ask an LLM

“Can I replace every field of a cardiac order in v2?”

“Which v2 call fully rewrites a cardiac order?”

Tell an agent

Replace cardiac order {id} with tests {tests} and reason {clinical_reason}.

Overwrite v2 cardiac order {id} in full.

Elation Health Cardiac Orders API

Operations 12

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

MCP server

Tools for apis

Call it yourself

Get an API key

OpenAPI Specification