Elation Health Imaging Orders API

The Imaging Orders API from Elation Health — 4 operation(s) for imaging 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 /imaging_orders/{id} Get an imaging order (legacy endpoint) · Get Imaging Order #

Ask an LLM

“Can I look up one imaging order on the legacy imaging orders path?”

“What does the older get-imaging-order call show about the ordered tests?”

Tell an agent

Open imaging order {id} using the legacy endpoint.

Show the clinical reason on old-path imaging order {id}.

PUT /imaging_orders/{id} Replace an imaging order (legacy PUT) · Update Imaging Order #

Ask an LLM

“How do I resend a whole imaging order through the legacy PUT?”

“Can the older full update change which imaging center an order goes to?”

Tell an agent

With the legacy PUT, rewrite imaging order {id} for patient {patient} at practice {practice}, prescribed by {prescribing_user}, sent to {ancillary_company}.

Fully replace the old-path imaging order with reason {clinical_reason}, document date {document_date}, chart date {chart_date}.

PATCH /imaging_orders/{id} Patch an imaging order (legacy PATCH) · Update Imaging Order #

Ask an LLM

“Can I change only the ICD-10 codes on an imaging order with the legacy PATCH?”

“What's the older way to mark an imaging order STAT without resending it?”

Tell an agent

Using the legacy PATCH, set imaging order {id}'s ICD-10 codes to {icd10_codes}.

Patch the old-path imaging order to send to imaging center {imaging_center} via {statmethod}.

DELETE /imaging_orders/{id} Delete an imaging order (legacy endpoint) · Delete Imaging Order #

Ask an LLM

“Is there a legacy call to delete an imaging order entered by mistake?”

“Can I remove a radiology order through the original imaging orders path?”

Tell an agent destructive · confirm first

Delete imaging order {id} with the legacy endpoint.

Remove the mistaken old-path radiology order {id}.

GET /imaging_orders/ Find imaging orders (legacy endpoint) · Find Imaging Orders #

Ask an LLM

“Can I find all of a patient's imaging orders with the older lookup?”

“Which radiology orders has my practice placed, via the legacy search?”

Tell an agent

Using the legacy lookup, find imaging orders for patient {patient}.

Find old-path imaging orders placed by practice {practice}.

POST /imaging_orders/ Place an imaging order (legacy endpoint) · Create Imaging Order #

Ask an LLM

“How do I order an X-ray or MRI for a patient through the legacy endpoint?”

“What's required to place an imaging order on the older path?”

Tell an agent

Via the legacy endpoint, order imaging for patient {patient} at practice {practice}, prescribed by {prescribing_user}, with {ancillary_company}.

Place an old-path imaging order for tests {tests} because {clinical_reason}, dated {document_date} and charted {chart_date}.

GET /api/2.0/imaging_orders/ List imaging orders in API 2.0 · List Imaging Orders #

Ask an LLM

“How do I page through imaging orders in the 2.0 API?”

“Can API 2.0 list imaging orders for a single patient, sorted?”

Tell an agent

List 2.0 imaging orders for patient {patient} ordered by {order_by}.

List API 2.0 imaging orders for practice {practice}, {limit} per page.

POST /api/2.0/imaging_orders/ Create an imaging order in API 2.0 · Create Imaging Order #

Ask an LLM

“How do I create a new imaging order with the 2.0 API?”

“Can I attach ICD-10 codes and a test date when ordering imaging?”

Tell an agent

In API 2.0, order imaging tests {tests} for patient {patient} at practice {practice}, prescribed by {prescribing_user}, with {ancillary_company}.

Create a 2.0 imaging order for reason {clinical_reason}, document date {document_date}, chart date {chart_date}, codes {icd10_codes}.

DELETE /api/2.0/imaging_orders/{id}/ Delete an imaging order in API 2.0 · Delete Imaging Order #

Ask an LLM

“How do I delete an imaging order with the 2.0 API?”

“Can I cancel out an imaging order by deleting it in API 2.0?”

Tell an agent destructive · confirm first

Delete API 2.0 imaging order {id}.

Remove 2.0 imaging order {id} from the chart.

GET /api/2.0/imaging_orders/{id}/ Retrieve an imaging order in API 2.0 · Retrieve Imaging Order #

Ask an LLM

“How do I retrieve a single imaging order by ID in API 2.0?”

“Does a 2.0 imaging order show its resolution and test date?”

Tell an agent

Retrieve API 2.0 imaging order {id}.

Get the resolution status of 2.0 imaging order {id}.

PATCH /api/2.0/imaging_orders/{id}/ Partially update an imaging order in API 2.0 · Partially Update Imaging Order #

Ask an LLM

“Can I record a test date on an existing imaging order without replacing it?”

“Is there a 2.0 PATCH to change an imaging order's follow-up method?”

Tell an agent

Patch 2.0 imaging order {id} with test date {test_date}.

Partially update API 2.0 imaging order {id} to follow up by {follow_up_method}.

PUT /api/2.0/imaging_orders/{id}/ Replace an imaging order in API 2.0 · Update Imaging Order #

Ask an LLM

“Can I replace an entire imaging order with a 2.0 PUT?”

“Which fields must be resent when fully replacing an imaging order?”

Tell an agent

Replace 2.0 imaging order {id} with tests {tests} for patient {patient} at practice {practice}, prescribed by {prescribing_user} with {ancillary_company}.

Overwrite API 2.0 imaging order {id}: reason {clinical_reason}, document date {document_date}, chart date {chart_date}.

Elation Health Imaging 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