---
title: "Create Cardiac Order"
method: POST
path: "/api/2.0/cardiac_orders/"
tags: ["Cardiac Orders"]
---

# Create Cardiac Order

`POST /api/2.0/cardiac_orders/`

Returns a list of cardiac orders

## Request body

- CardiacOrder
  - `ancillary_company` integer, required
  - `cardiac_center` integer, nullable — The cardiac center the order is associated with.
  - `ccs` integer[] — Array of Physician IDs to copy for the order.
  - `chart_date` string, date-time, required
  - `clinical_reason` string, required — The clinical reason for the order.
  - `confidential` boolean
  - `created_date` string, date-time, nullable
  - `deleted_date` string, date-time, nullable
  - `document_date` string, date-time, required
  - `follow_up_method` string, nullable — How to notify the patient of the results.
  - `icd10_codes` ICD10Code[] — Array of ICD-10 diagnosis codes associated with the order.
    - `code` string, required
    - `description` string, nullable
  - `id` integer
  - `medications` string, nullable — Description of beta blockers/medications the patient is taking.
  - `patient` integer, required — The patient the order is associated with. Patient must belong to the specified practice.
  - `practice` integer, required — The practice the order is associated with.
  - `prescribing_user` integer, required — The user associated with the order. User ID must tie to a physician in the practice.
  - `resolution` DocumentResolutionState
    - `created_date` string, date-time, nullable — The datetime when this resolution state was created.
    - `deleted_date` string, date-time, nullable — The datetime when this resolution was deleted. Should never be null because we're providing the most updated resolution.
    - `document` integer — Will be the same as the id of the lab order.
    - `id` integer — Internal id to represent the resolution state.
    - `note` string, nullable — Any note that was added to represent why an order was cancelled.
    - `resolving_document` integer, nullable — If the order is fulfilled will indicate the document referenced. For lab orders will usually be a report. Must be an integer ID or null.
    - `state` 'outstanding' | 'fulfilled' | 'cancelled', required — * `outstanding` - Outstanding * `fulfilled` - Fulfilled * `cancelled` - Cancelled
  - `signed_by` integer, nullable
  - `signed_date` string, date-time, nullable
  - `test_date` string, date, nullable — The date on which the tests should be performed, or were performed. Can be different than document_date, create_date.
  - `tests` CardiacOrderTest[], required — An array of cardiac tests associated with the order.
    - `code` string, nullable
    - `created_date` string, date-time, nullable
    - `deleted_date` string, date-time, nullable
    - `id` integer
    - `name` string, required
    - `practice` integer, required

## Response `201`

- CardiacOrder
  - `ancillary_company` integer, required
  - `cardiac_center` integer, nullable — The cardiac center the order is associated with.
  - `ccs` integer[] — Array of Physician IDs to copy for the order.
  - `chart_date` string, date-time, required
  - `clinical_reason` string, required — The clinical reason for the order.
  - `confidential` boolean
  - `created_date` string, date-time, nullable
  - `deleted_date` string, date-time, nullable
  - `document_date` string, date-time, required
  - `follow_up_method` string, nullable — How to notify the patient of the results.
  - `icd10_codes` ICD10Code[] — Array of ICD-10 diagnosis codes associated with the order.
    - `code` string, required
    - `description` string, nullable
  - `id` integer
  - `medications` string, nullable — Description of beta blockers/medications the patient is taking.
  - `patient` integer, required — The patient the order is associated with. Patient must belong to the specified practice.
  - `practice` integer, required — The practice the order is associated with.
  - `prescribing_user` integer, required — The user associated with the order. User ID must tie to a physician in the practice.
  - `resolution` DocumentResolutionState
    - `created_date` string, date-time, nullable — The datetime when this resolution state was created.
    - `deleted_date` string, date-time, nullable — The datetime when this resolution was deleted. Should never be null because we're providing the most updated resolution.
    - `document` integer — Will be the same as the id of the lab order.
    - `id` integer — Internal id to represent the resolution state.
    - `note` string, nullable — Any note that was added to represent why an order was cancelled.
    - `resolving_document` integer, nullable — If the order is fulfilled will indicate the document referenced. For lab orders will usually be a report. Must be an integer ID or null.
    - `state` 'outstanding' | 'fulfilled' | 'cancelled', required — * `outstanding` - Outstanding * `fulfilled` - Fulfilled * `cancelled` - Cancelled
  - `signed_by` integer, nullable
  - `signed_date` string, date-time, nullable
  - `test_date` string, date, nullable — The date on which the tests should be performed, or were performed. Can be different than document_date, create_date.
  - `tests` CardiacOrderTest[], required — An array of cardiac tests associated with the order.
    - `code` string, nullable
    - `created_date` string, date-time, nullable
    - `deleted_date` string, date-time, nullable
    - `id` integer
    - `name` string, required
    - `practice` integer, required

---

[API](https://skmtc.net/elationhealth/apis/api-authentication.md) · [All operations](https://skmtc.net/elationhealth/apis/api-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/elationhealth/api-authentication/versions/c060f89d4de7/schema)