How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
drchrono

drchrono Clinical API

Create and manage clinical resources

Documentation Provider Profile APIs.io OpenAPI GitHub

drchrono Clinical API is one of 7 APIs that drchrono publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Clinical. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 231 operations across 110 paths, and defines 49 schemas. It is described by OpenAPI 3.2.0, at version v4 - Hunt Valley.

Requests are made against a single base URL, https://app.drchrono.com.

231 operations 110 paths 49 schemas 17 DELETE106 GET34 PATCH43 POST31 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v4 - Hunt Valley
Base URL
https://app.drchrono.com/api
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

drchrono Clinical API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (drchrono_oauth2) using the authorizationCode flow, exposing 22 scopes.

Paths & Operations 231

Across 110 paths, the API surfaces 231 operations — 17 DELETE, 106 GET, 34 PATCH, 43 POST, 31 PUT. Each is listed below with its method, path, parameters, and response codes.

Clinical 231

Create and manage clinical resources

POST
/api/claim_billing_notes
Create a new billing note
claim_billing_notes_create 2 params → 201405404403401400500
GET
/api/claim_billing_notes
Retrieve or search billing notes
claim_billing_notes_list 4 params → 200405404403401400500
POST
/api/signed_consent_forms
signedconsentforms Create
signed_consent_forms_create 4 params body → 201405404403401400500
PATCH
/api/signed_consent_forms
signedconsentforms Update
signed_consent_forms_partial_update 2 params body → 204405404403401400500
GET
/api/signed_consent_forms
signedconsentforms Get
signed_consent_forms_list 4 params body → 200405404403401400500
POST
/api/custom_appointment_fields
Create custom appointment fields
custom_appointment_fields_create 1 param → 201405404403401400500
GET
/api/custom_appointment_fields
Retrieve or search custom appointment fields
custom_appointment_fields_list 3 params → 200405404403401400500
PUT
/api/lab_orders/{id}
Update an existing lab order
lab_orders_update 3 params → 204405404403401400500
PATCH
/api/lab_orders/{id}
Update an existing lab order
lab_orders_partial_update 3 params → 204405404403401400500
GET
/api/lab_orders/{id}
Retrieve an existing lab order
lab_orders_read 3 params → 200405404403401400500
DELETE
/api/lab_orders/{id}
Delete an existing lab order
lab_orders_delete 3 params → 204405404403401400500
POST
/api/clinical_notes_list
Create clinical note list request. Use the UUID returned in the response to retrieve the batch of records. Results returned in order of ID.
clinical_notes_list_create 10 params → 201404403401400500
GET
/api/clinical_notes_list
Retrieve or search clinical notes in batches. Results returned in order of ID.
clinical_notes_list_list 1 param → 200404403401400500
GET
/api/custom_vitals/{id}
Retrieve an existing custom vital type
custom_vitals_read 2 params → 200405404403401400500
PUT
/api/sublabs/{id}
Update an existing sub vendor
sublabs_update 1 param → 204405404403401400500
PATCH
/api/sublabs/{id}
Update an existing sub vendor
sublabs_partial_update 1 param → 204405404403401400500
GET
/api/sublabs/{id}
Retrieve an existing sub vendor
sublabs_read 1 param → 200405404403401400500
DELETE
/api/sublabs/{id}
Delete an existing sub vendor
sublabs_delete 1 param → 204405404403401400500
GET
/api/patients/{id}/qrda1
Retrieve patient QRDA1
patients_qrda1 12 params → 200405404403401400500
POST
/api/problems
Create patient problems
problems_create 2 params → 201405404403401400500
GET
/api/problems
Retrieve or search patient problems
problems_list 4 params → 200405404403401400500
GET
/api/staff
staff_list 3 params → 200405404403401400500
PUT
/api/patient_messages/{id}
patient_messages_update 4 params → 204405404403401400500
PATCH
/api/patient_messages/{id}
patient_messages_partial_update 4 params → 204405404403401400500
GET
/api/patient_messages/{id}
patient_messages_read 5 params → 200405404403401400500
POST
/api/medications
Create patient medications
medications_create 2 params → 201405404403401400500
GET
/api/medications
Retrieve or search patient medications
medications_list 4 params → 200405404403401400500
POST
/api/custom_demographics
Create custom demographics fields
custom_demographics_create 1 param → 201405404403401400500
GET
/api/custom_demographics
Retrieve or search custom demographics fields
custom_demographics_list 3 params → 200405404403401400500
POST
/api/appointments_list
appointments_list_create 9 params → 201405404403500401400409
GET
/api/appointments_list
appointments_list_list 10 params → 200405404403401400500
POST
/api/appointment_profiles
Create appointment profiles for a doctor's calendar
appointment_profiles_create 1 param → 201405404403401400500
GET
/api/appointment_profiles
Retrieve or search appointment profiles for a doctor's calendar
appointment_profiles_list 3 params → 200405404403401400500
POST
/api/patient_communications
Create patient communication for CQM
patient_communications_create 2 params → 201405404403401400500
GET
/api/patient_communications
Retrieve or search patient communications for CQM
patient_communications_list 4 params → 200405404403401400500
PUT
/api/appointment_profiles/{id}
Update an existing appointment profile
appointment_profiles_update 2 params → 204405404403401400500
PATCH
/api/appointment_profiles/{id}
Update an existing appointment profile
appointment_profiles_partial_update 2 params → 204405404403401400500
GET
/api/appointment_profiles/{id}
Retrieve an existing appointment profile
appointment_profiles_read 2 params → 200405404403401400500
DELETE
/api/appointment_profiles/{id}
Delete an existing appointment profile
appointment_profiles_delete 2 params → 204405404403401400500
PUT
/api/clinical_note_field_values/{id}
Update an existing clinical note field value
clinical_note_field_values_update 6 params → 204405404403401400500
PATCH
/api/clinical_note_field_values/{id}
Update an existing clinical note field value
clinical_note_field_values_partial_update 6 params → 204405404403401400500
GET
/api/clinical_note_field_values/{id}
Retrieve an existing clinical note field value
clinical_note_field_values_read 6 params → 200405404403401400500
GET
/api/fee_schedules_v2
fee_schedules_v2_list 9 params → 200405404403401400500
GET
/api/care_team_members
care_team_members_list 5 params → 200405404403401400500
POST
/api/consent_forms/{id}/unapply_from_appointment
Unassign (unapply) a consent form from appointment
consent_forms_unapply_from_appointment 2 params → 204405404403401400500
POST
/api/consent_forms/{id}/apply_to_appointment
Assign (apply) a consent form to appointment
consent_forms_apply_to_appointment 2 params → 204405404403401400500
POST
/api/consent_forms
Create a patient consent form
consent_forms_create 1 param → 201405404403401400500
GET
/api/consent_forms
Retrieve or search patient consent forms
consent_forms_list 3 params → 200405404403401400500
PUT
/api/reminder_profiles/{id}
Update an existing reminder profile
reminder_profiles_update 2 params → 204405404403401400500
PATCH
/api/reminder_profiles/{id}
Update an existing reminder profile
reminder_profiles_partial_update 2 params → 204405404403401400500
GET
/api/reminder_profiles/{id}
Retrieve an existing reminder profile
reminder_profiles_read 2 params → 200405404403401400500
DELETE
/api/reminder_profiles/{id}
Delete an existing reminder profile
reminder_profiles_delete 2 params → 204405404403401400500
POST
/api/patients_list
Submit patient list request. Use the UUID returned in the response to retrieve the batch of patients.
patients_list_create 13 params → 201403500401400
GET
/api/patients_list
Retrieve or search patients in batches. This resource returns identical data to GET /api/patients but uses an asynchronous batch-based approach to data delivery. This is an efficient choice for large…
patients_list_list 1 param → 200404403401400500
POST
/api/patient_interventions
Create patient intervention for CQM
patient_interventions_create 2 params → 201405404403401400500
GET
/api/patient_interventions
Retrieve or search patient interventions for CQM
patient_interventions_list 4 params → 200405404403401400500
POST
/api/patient_messages
patient_messages_create 3 params → 201405404403401400500
GET
/api/patient_messages
patient_messages_list 5 params → 200405404403401400500
PUT
/api/patient_physical_exams/{id}
Update an existing patient physical exam for CQM
patient_physical_exams_update 3 params → 204405404403401400500
PATCH
/api/patient_physical_exams/{id}
Update an existing patient physical exam for CQM
patient_physical_exams_partial_update 3 params → 204405404403401400500
GET
/api/patient_physical_exams/{id}
Retrieve an existing patient physical exam for CQM
patient_physical_exams_read 3 params → 200405404403401400500
POST
/api/clinical_note_field_values
Create clinical note field value
clinical_note_field_values_create 5 params → 201405404403401400500
GET
/api/clinical_note_field_values
Retrieve or search clinical note field values
clinical_note_field_values_list 7 params → 200405404403401400500
POST
/api/patients
Create patient
patients_create 12 params → 201405404403401400500
GET
/api/patients
Retrieve or search patients
patients_list 14 params → 200405404403401400500
GET
/api/implantable_devices/{id}
Retrieve an existing implantable device
implantable_devices_read 5 params → 200405404403401400500
PUT
/api/patient_communications/{id}
Update an existing patient communication for CQM
patient_communications_update 3 params → 204405404403401400500
PATCH
/api/patient_communications/{id}
Update an existing patient communication for CQM
patient_communications_partial_update 3 params → 204405404403401400500
GET
/api/patient_communications/{id}
Retrieve an existing patient communication for CQM
patient_communications_read 3 params → 200405404403401400500
GET
/api/prescription_messages/{id}
Retrieve an existing prescription message
prescription_messages_read 5 params → 200405404403401400500
GET
/api/implantable_devices
Retrieve or search implantable devices
implantable_devices_list 6 params → 200405404403401400500
POST
/api/patient_risk_assessments
patient_risk_assessments_create 2 params → 201405404403401400500
GET
/api/patient_risk_assessments
patient_risk_assessments_list 4 params → 200405404403401400500
POST
/api/patients_summary
patients_summary_create 6 params → 201405404403401400500
GET
/api/patients_summary
patients_summary_list 8 params → 200405404403401400500
PUT
/api/documents/{id}
Update an existing patient document
documents_update 4 params → 204405404403401400500
PATCH
/api/documents/{id}
Update an existing patient document
documents_partial_update 4 params → 204405404403401400500
GET
/api/documents/{id}
Retrieve an existing patient document
documents_read 4 params → 200405404403401400500
DELETE
/api/documents/{id}
Delete an existing appointment template
documents_delete 4 params → 204405404403401400500
POST
/api/patients/{id}/onpatient_access
Send new onpatient invite to patient
patients_onpatient_access_create 12 params → 201405404403401400500
GET
/api/patients/{id}/onpatient_access
Retrieve or search existing onpatient access invites
patients_onpatient_access_read 12 params → 200405404403401400500
DELETE
/api/patients/{id}/onpatient_access
Revoke sent onpatient invites
patients_onpatient_access_delete 12 params → 204405404403401400500
PUT
/api/lab_results/{id}
Update an existing lab result
lab_results_update 3 params → 204405404403401400500
PATCH
/api/lab_results/{id}
Update an existing lab result
lab_results_partial_update 3 params → 204405404403401400500
GET
/api/lab_results/{id}
Retrieve an existing lab result
lab_results_read 3 params → 200405404403401400500
DELETE
/api/lab_results/{id}
Delete an existing lab result
lab_results_delete 3 params → 204405404403401400500
PUT
/api/medications/{id}
Update an existing patient medications
medications_update 3 params → 204405404403401400500
PATCH
/api/medications/{id}
Update an existing patient medications
medications_partial_update 3 params → 204405404403401400500
GET
/api/medications/{id}
Retrieve an existing patient medications
medications_read 3 params → 200405404403401400500
PATCH
/api/medications/{id}/append_to_pharmacy_note
Append a message to the "pharmacynote" section of the prescription, in a new paragraph
medications_append_to_pharmacy_note 3 params → 204405404403401400500
PUT
/api/patient_vaccine_records/{id}
Update an existing patient vaccine records
patient_vaccine_records_update 5 params → 204405404403401400500
PATCH
/api/patient_vaccine_records/{id}
Update an existing patient vaccine records
patient_vaccine_records_partial_update 5 params → 204405404403401400500
GET
/api/patient_vaccine_records/{id}
Retrieve an existing patient vaccine records
patient_vaccine_records_read 5 params → 200405404403401400500
PUT
/api/patient_flag_types/{id}
Update an existing patient flag type
patient_flag_types_update 2 params → 204405404403401400500
PATCH
/api/patient_flag_types/{id}
Update an existing patient flag type
patient_flag_types_partial_update 2 params → 204405404403401400500
GET
/api/patient_flag_types/{id}
Retrieve an existing patient flag type
patient_flag_types_read 2 params → 200405404403401400500
PATCH
/api/clinical_note_field_types/{id}
Update the freedrawimagesize of an existing clinical note FreeDraw Field
clinical_note_field_types_update 1 param body → 204405404403401400500
GET
/api/clinical_note_field_types/{id}
Retrieve an existing clinial note field type
clinical_note_field_types_read 3 params → 200405404403401400500
GET
/api/fee_schedules
fee_schedules_list 7 params → 200405404403401400500
PUT
/api/patient_risk_assessments/{id}
patient_risk_assessments_update 3 params → 204405404403401400500
PATCH
/api/patient_risk_assessments/{id}
patient_risk_assessments_partial_update 3 params → 204405404403401400500
GET
/api/patient_risk_assessments/{id}
patient_risk_assessments_read 3 params → 200405404403401400500
PUT
/api/lab_documents/{id}
Update an existing lab order document
lab_documents_update 3 params → 204405404403401400500
PATCH
/api/lab_documents/{id}
Update an existing lab order document
lab_documents_partial_update 3 params → 204405404403401400500
GET
/api/lab_documents/{id}
Retrieve an existing appointment template
lab_documents_read 3 params → 200405404403401400500
DELETE
/api/lab_documents/{id}
Delete an existing lab order document
lab_documents_delete 3 params → 204405404403401400500
PUT
/api/appointment_templates/{id}
Update an existing appointment template
appointment_templates_update 4 params → 204405404403401400500
PATCH
/api/appointment_templates/{id}
Update an existing appointment template
appointment_templates_partial_update 4 params → 204405404403401400500
GET
/api/appointment_templates/{id}
Retrieve an existing appointment template
appointment_templates_read 4 params → 200405404403401400500
DELETE
/api/appointment_templates/{id}
Delete an existing appointment template
appointment_templates_delete 4 params → 204405404403401400500
PUT
/api/patient_interventions/{id}
Update an existing patient intervention for CQM
patient_interventions_update 3 params → 204405404403401400500
PATCH
/api/patient_interventions/{id}
Update an existing patient intervention for CQM
patient_interventions_partial_update 3 params → 204405404403401400500
GET
/api/patient_interventions/{id}
Retrieve an existing patient intervention for CQM
patient_interventions_read 3 params → 200405404403401400500
PUT
/api/allergies/{id}
Update an existing patient allergy
allergies_update 3 params → 204405404403401400500
PATCH
/api/allergies/{id}
Update an existing patient allergy
allergies_partial_update 3 params → 204405404403401400500
GET
/api/allergies/{id}
Retrieve an existing patient allergy
allergies_read 3 params → 200405404403401400500
GET
/api/patients/{id}/ccda
Retrieve patient CCDA
patients_ccda 12 params → 200405404403401400500
GET
/api/lab_orders_summary
lab_orders_summary_list 5 params → 200405404403401400500
GET
/api/clinical_note_field_values_list
Retrieve or search clinical note values (soap notes) in batches. Results returned in order of ID or by updatedat.
clinical_note_field_values_list_list 1 param → 200404403401400500
GET
/api/care_plans/{id}
Retrieve an existing care plan
care_plans_read 4 params → 200405404403401400500
GET
/api/fee_schedules/{id}
fee_schedules_read 6 params → 200405404403401400500
PUT
/api/appointments/{id}
Update an existing appointment or break
appointments_update 1 param body → 404403409401400500
PATCH
/api/appointments/{id}
Update an existing appointment or break
appointments_partial_update 1 param body → 204404403500401400409
GET
/api/appointments/{id}
Retrieve an existing appointment or break
appointments_read 1 param → 200404403500401
DELETE
/api/appointments/{id}
Delete an existing appointment or break
appointments_delete 1 param → 404403500401
POST
/api/telehealth_appointments
telehealth_appointments_create 2 params → 201405404403401400500
GET
/api/telehealth_appointments
telehealth_appointments_list 4 params → 200405404403401400500
GET
/api/care_plans
Retrieve or search care plans
care_plans_list 5 params → 200405404403401400500
POST
/api/patient_physical_exams
Create patient physical exam for CQM
patient_physical_exams_create 2 params → 201405404403401400500
GET
/api/patient_physical_exams
Retrieve or search patient physical exams for CQM
patient_physical_exams_list 4 params → 200405404403401400500
GET
/api/signed_consent_forms/{id}
signedconsentforms Read
signed_consent_forms_read 1 param → 200405404403401400500
GET
/api/clinical_note_templates/{id}
Retrieve an existing clinical note tempalte
clinical_note_templates_read 2 params → 200405404403401400500
POST
/api/lab_results
Create lab results. An example lab workflow is as following: - When you get orders, submit them via /api/laborders, such that doctors can see them in drchrono. - When results come in, submit the resu…
lab_results_create 2 params → 201405404403401400500
GET
/api/lab_results
Retrieve or search lab results
lab_results_list 4 params → 200405404403401400500
PUT
/api/problems/{id}
Update an existing patient problems
problems_update 3 params → 204405404403401400500
PATCH
/api/problems/{id}
Update an existing patient problems
problems_partial_update 3 params → 204405404403401400500
GET
/api/problems/{id}
Retrieve an existing patient problems
problems_read 3 params → 200405404403401400500
POST
/api/amendments
Create patient amendments to a patient's clinical records
amendments_create 3 params → 201405404403401400500
GET
/api/amendments
Retrieve or search patient amendments. You can only interact with amendments created by your API application
amendments_list 5 params → 200405404403401400500
POST
/api/lab_orders
Create lab orders. An example lab workflow is as following: - When you get orders, submit them via /api/laborders, such that doctors can see them in drchrono. - When results come in, submit the resul…
lab_orders_create 2 params → 201405404403401400500
GET
/api/lab_orders
Retrieve or search lab orders
lab_orders_list 5 params → 200405404403401400500
POST
/api/patient_flag_types
Create patient flag types
patient_flag_types_create 1 param → 201405404403401400500
GET
/api/patient_flag_types
Retrieve or search patient flag types
patient_flag_types_list 3 params → 200405404403401400500
GET
/api/recurring_appointment_instances
List all instances (materialized and virtual) within a recurring appointment series. Returns the same appointment response format as /api/appointments. Materialized instances have a real id; virtual…
recurring_appointment_instances_list 5 params → 200400
PUT
/api/custom_appointment_fields/{id}
Update an existing custom appointment field
custom_appointment_fields_update 2 params → 204405404403401400500
PATCH
/api/custom_appointment_fields/{id}
Update an existing custom appointment field
custom_appointment_fields_partial_update 2 params → 204405404403401400500
GET
/api/custom_appointment_fields/{id}
Retrieve an existing custom appointment field
custom_appointment_fields_read 2 params → 200405404403401400500
POST
/api/eobs
Create EOB object
eobs_create 1 param → 201405404403401400500
GET
/api/eobs
Retrieve or search EOB objects
eobs_list 3 params → 200405404403401400500
GET
/api/insurances
insurances_list 4 params → 200405404403401400500
POST
/api/telehealth_appointment_history
telehealth_appointment_history_create 1 param → 201405404403401400500
GET
/api/telehealth_appointment_history
telehealth_appointment_history_list 3 params → 200405404403401400500
PUT
/api/patients_summary/{id}
patients_summary_update 7 params → 204405404403401400500
PATCH
/api/patients_summary/{id}
patients_summary_partial_update 7 params → 204405404403401400500
GET
/api/patients_summary/{id}
patients_summary_read 7 params → 200405404403401400500
DELETE
/api/patients_summary/{id}
patients_summary_delete 7 params → 204405404403401400500
POST
/api/lab_documents
Create lab order documents. An example lab workflow is as following: - When you get orders, submit them via /api/laborders, such that doctors can see them in drchrono. - When results come in, submit…
lab_documents_create 2 params → 201405404403401400500
GET
/api/lab_documents
Retrieve or search lab order documents
lab_documents_list 5 params → 200405404403401400500
PUT
/api/consent_forms/{id}
Update an existing patient consent form
consent_forms_update 2 params → 204405404403401400500
PATCH
/api/consent_forms/{id}
Update an existing patient consent form
consent_forms_partial_update 2 params → 204405404403401400500
GET
/api/consent_forms/{id}
Retrieve an existing patient consent form
consent_forms_read 2 params → 200405404403401400500
PUT
/api/lab_tests/{id}
Update an existing lab test
lab_tests_update 3 params → 204405404403401400500
PATCH
/api/lab_tests/{id}
Update an existing lab test
lab_tests_partial_update 3 params → 204405404403401400500
GET
/api/lab_tests/{id}
Retrieve an existing lab test
lab_tests_read 3 params → 200405404403401400500
DELETE
/api/lab_tests/{id}
Delete an existing lab test
lab_tests_delete 3 params → 204405404403401400500
POST
/api/prescription_messages_list
Create prescription messages list request. Use the UUID returned in the response to retrieve the batch of records. Results returned in order of id or updatedat.
prescription_messages_list_create 8 params → 201404403401400500
GET
/api/prescription_messages_list
Retrieve or search prescription messages in batches. Results returned in order of ID or updatedat.
prescription_messages_list_list 1 param → 200404403401400500
PUT
/api/patients/{id}
Update an existing patient
patients_update 12 params → 204405404403401400500
PATCH
/api/patients/{id}
Update an existing patient
patients_partial_update 12 params → 204405404403401400500
GET
/api/patients/{id}
Retrieve an existing patient
patients_read 12 params → 200405404403401400500
DELETE
/api/patients/{id}
Delete an existing patient
patients_delete 12 params → 204405404403401400500
GET
/api/patients/{id}/ccda_async
Retrieve patient CCDA async.
patients_ccda_async 13 params → 200405404403401400500
GET
/api/custom_vitals
Retrieve or search custom vital types
custom_vitals_list 3 params → 200405404403401400500
POST
/api/schedule_blocks
Create a schedule block
schedule_blocks_create body → 201403500401400
GET
/api/schedule_blocks
Retrieve and search schedule blocks
schedule_blocks_list 6 params → 200403500401400
GET
/api/care_team_members/{id}
care_team_members_read 4 params → 200405404403401400500
GET
/api/claim_billing_notes/{id}
Retrieve an existing billing note
claim_billing_notes_read 3 params → 200405404403401400500
PUT
/api/patient_lab_results/{id}
patient_lab_results_update 5 params → 204405404403401400500
PATCH
/api/patient_lab_results/{id}
patient_lab_results_partial_update 5 params → 204405404403401400500
GET
/api/patient_lab_results/{id}
patient_lab_results_read 5 params → 200405404403401400500
DELETE
/api/patient_lab_results/{id}
patient_lab_results_delete 5 params → 204405404403401400500
PUT
/api/amendments/{id}
Update an existing patient amendment, you can only interact with amendments created by your API application
amendments_update 4 params → 204405404403401400500
PATCH
/api/amendments/{id}
Update an existing patient amendment, you can only interact with amendments created by your API application
amendments_partial_update 4 params → 204405404403401400500
GET
/api/amendments/{id}
Retrieve an existing patient amendment, you can only interact with amendments created by your API application
amendments_read 4 params → 200405404403401400500
DELETE
/api/amendments/{id}
Delete an existing patient amendment, you can only interact with amendments created by your API application
amendments_delete 4 params → 204405404403401400500
POST
/api/lab_tests
Create lab tests. An example lab workflow is as following: - When you get orders, submit them via /api/laborders, such that doctors can see them in drchrono. - When results come in, submit the result…
lab_tests_create 2 params → 201405404403401400500
GET
/api/lab_tests
Retrieve or search lab tests
lab_tests_list 4 params → 200405404403401400500
PUT
/api/appointments_list/{id}
appointments_list_update 8 params → 204405404403500401400409
PATCH
/api/appointments_list/{id}
appointments_list_partial_update 8 params → 204405404403500401400409
GET
/api/appointments_list/{id}
appointments_list_read 8 params → 200405404403401400500
DELETE
/api/appointments_list/{id}
appointments_list_delete 8 params → 204405404403401400500
POST
/api/patient_lab_results
patient_lab_results_create 4 params → 201405404403401400500
GET
/api/patient_lab_results
patient_lab_results_list 6 params → 200405404403401400500
GET
/api/fee_schedules_v2/{id}
fee_schedules_v2_read 1 param → 200405404403401400500
GET
/api/insurances/{id}
insurances_read 3 params → 200405404403401400500
GET
/api/clinical_notes
clinical_notes_list 9 params → 200405404403401400500
POST
/api/eligibility_checks_list
Create eligibility checks list request. Use the UUID returned in the response to retrieve the batch of records. Results returned in order of id or updatedat.
eligibility_checks_list_create 11 params → 201404403401400500
GET
/api/telehealth_appointment_history/{id}
telehealth_appointment_history_read 2 params → 200405404403401400500
GET
/api/clinical_notes/{id}
clinical_notes_read 7 params → 200405404403401400500
GET
/api/clinical_note_field_types
Retrieve or search clinical note field types
clinical_note_field_types_list 4 params → 200405404403401400500
POST
/api/documents
Create documents
documents_create 3 params → 201405404403401400500
GET
/api/documents
Retrieve or search documents
documents_list 5 params → 200405404403401400500
GET
/api/staff/{id}
staff_read 2 params → 200405404403401400500
PUT
/api/schedule_blocks/{id}
Update a schedule block
schedule_blocks_update 1 param body → 200204404403401400500
PATCH
/api/schedule_blocks/{id}
Partially update a schedule block
schedule_blocks_partial_update 1 param body → 200204404403401400500
GET
/api/schedule_blocks/{id}
Retrieve a schedule block
schedule_blocks_read 1 param → 200404403500401
DELETE
/api/schedule_blocks/{id}
Delete a schedule block
schedule_blocks_delete 1 param → 500404403204401
GET
/api/lab_orders_summary/{id}
lab_orders_summary_read 4 params → 200405404403401400500
PUT
/api/custom_demographics/{id}
Update an existing custom demographics field
custom_demographics_update 2 params → 204405404403401400500
PATCH
/api/custom_demographics/{id}
Update an existing custom demographics field
custom_demographics_partial_update 2 params → 204405404403401400500
GET
/api/custom_demographics/{id}
Retrieve an existing custom demographics field
custom_demographics_read 2 params → 200405404403401400500
GET
/api/eobs/{id}
Retrieve an existing EOB object
eobs_read 2 params → 200405404403401400500
POST
/api/allergies
Create patient allergy
allergies_create 2 params → 201405404403401400500
GET
/api/allergies
Retrieve or search patient allergies
allergies_list 4 params → 200405404403401400500
POST
/api/appointments
Create a new appointment or break on doctor's calendar
appointments_create body → 201403409401400500
GET
/api/appointments
Retrieve or search appointment or breaks. Note: Either since, occurredsince, date or daterange parameter must be specified. results returned in order of scheduled date.
appointments_list 13 params → 200403500401400
GET
/api/clinical_note_templates
Retrieve or search clinical note templates
clinical_note_templates_list 3 params → 200405404403401400500
POST
/api/reminder_profiles
Create reminder profile
reminder_profiles_create 1 param → 201405404403401400500
GET
/api/reminder_profiles
Retrieve or search reminder profiles
reminder_profiles_list 3 params → 200405404403401400500
POST
/api/appointment_templates
Create appointment templates for a doctor's calendar
appointment_templates_create 3 params → 201405404403401400500
GET
/api/appointment_templates
Retrieve or search appointment templates for a doctor's calendar
appointment_templates_list 7 params → 200405404403401400500
POST
/api/patient_vaccine_records
Create patient vaccine records
patient_vaccine_records_create 4 params → 201405404403401400500
GET
/api/patient_vaccine_records
Retrieve or search patient vaccine records
patient_vaccine_records_list 6 params → 200405404403401400500
PUT
/api/telehealth_appointments/{id}
telehealth_appointments_update 3 params → 204405404403401400500
PATCH
/api/telehealth_appointments/{id}
telehealth_appointments_partial_update 3 params → 204405404403401400500
GET
/api/telehealth_appointments/{id}
telehealth_appointments_read 3 params → 200405404403401400500
GET
/api/prescription_messages
Retrieve or search prescription messages
prescription_messages_list 7 params → 200405404403401400500
POST
/api/sublabs
Create sub-vendors - When you get orders, submit them via /api/laborders, such that doctors can see them in drchrono. - When results come in, submit the result document PDF via /api/labdocuments and…
sublabs_create → 201405404403401400500
GET
/api/sublabs
Retrieve or search sub vendors
sublabs_list 2 params → 200405404403401400500
POST
/api/yellow_notepad
Create or update yellow notepad content for a specific appointment and template combination. This endpoint has different behavior based on the template's workflowkey: Regular templates (workflowkey !…
yellow_notepad_create 2 params body → 201405404403500401400409
GET
/api/yellow_notepad
Retrieve yellow notepad content for a specific appointment and template combination. Both appointmentid and templateid must be provided as query parameters.
yellow_notepad_retrieve 2 params → 200405404403401400500

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are Patient (65 properties), Appointment (57 properties), PatientVaccineRecord (28 properties), DoctorFeeSchedule (24 properties). Each schema is shown below with its type and property counts.

ReminderProfile
object
4 properties 2 required
Patient
object
65 properties 2 required
SoapNoteLineItemFieldType
object
8 properties
PatientIntervention
object
12 properties 2 required
LabVendorLocation
object
4 properties 2 required
CustomVitalType
object
10 properties
SignedConsentFormUpdate
object
5 properties
PatientAmendment
object
7 properties 4 required
Staff
object
12 properties
LabTest
object
12 properties 1 required
Insurance
object
3 properties
PatientFlagType
object
8 properties 2 required
ClaimBillingNotes
object
5 properties 1 required
AppointmentTemplate
object
Appointment templates are blocks of time during which a doctor usually sees appointments with the same profile. These may have a longer duration then the corre…
11 properties 4 required
CustomPatientFieldType
object
7 properties 2 required
PatientVaccineRecord
object
28 properties 3 required
SignedConsentForm
object
8 properties 3 required
TelemedicineAppointmentEventLog
object
3 properties
TelemedicineAppointment
object
The Telehealth Appointment endpoint is an extension of the existing Appointment endpoint.
7 properties 1 required
ClinicalNote
object
5 properties
PatientProblem
object
19 properties 2 required
LabOrder
object
13 properties 3 required
CareTeamMember
object
5 properties
PrescriptionMessage
object
10 properties
DoctorFeeSchedule
object
24 properties
ConsentForm
object
10 properties 5 required
FeeSchedule
object
11 properties
PatientLabResultSet
object
19 properties 2 required
CustomAppointmentFieldType
object
8 properties
EOBObject
object
12 properties 4 required
PatientRiskAssessment
object
12 properties 2 required
PatientCommunication
object
12 properties 2 required
CarePlan
object
12 properties
PatientDrug
object
24 properties 2 required
ImplantableDevice
object
16 properties
ScannedClinicalDocument
object
9 properties 5 required
AppointmentProfile
object
Appointment profiles are for common kinds of appointments a doctor might have, such as "physical exam", which have a standard duration and should show up as th…
9 properties 3 required
LabResult
object
17 properties 5 required
SoapNoteCustomReport
object
10 properties
AsyncResourceError
object
3 properties
SoapNoteLineItemFieldValue
object
Values entered by doctor when charting a particular appointment
6 properties 3 required
PatientPhysicalExam
object
12 properties 2 required
ScheduleBlock
object
Schedule blocks are used to block off time on a provider's calendar, preventing appointments from being scheduled during those times. They can be associated wi…
11 properties 4 required
PatientMessage
object
10 properties 3 required
PatientAllergy
object
11 properties 2 required
LabOrderDocument
object
6 properties 3 required
Appointment
object
57 properties 5 required
YellowNotepad
object
3 properties 3 required
PatientMessage_2
object
9 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

drchrono-clinical-api-openapi.yml Raw ↑

Other APIs drchrono publishes across the network.

drchrono Administrative API
AE Profile APIs.io
drchrono Audit API
AE Profile APIs.io
drchrono Availability API
AE Profile APIs.io
drchrono Billing API
AE Profile APIs.io
drchrono Practice Management API
AE Profile APIs.io
drchrono SMART on FHIR R4 API
AE Profile APIs.io
#Clinical
← Back to D APIs
API Details
ID
drchrono:drchrono-clinical-api
Base URL
https://app.drchrono.com/api
Docs
https://app.drchrono.com/api-docs/tutorial/
Provider
drchrono
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=drchrono-clinical-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/drchrono-clinical-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of drchrono Clinical API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.