api

name	api
description	API skill. Use when working with for api. Covers 327 endpoints.
version	1.0.0
generator	lapsh

API version: v4 - Hunt Valley

Auth

OAuth2

Base URL

https://app.drchrono.com

Setup

1. Configure auth: OAuth2
2. GET /api/day_sheet_charges -- verify access
3. POST /api/claim_billing_notes -- create first claim_billing_notes

Endpoints

327 endpoints across 1 groups. See references/api-spec.lap for full details.

api

Method	Path	Description
GET	/api/day_sheet_charges	Retrieve daysheet charges report for a given date range
POST	/api/claim_billing_notes	Create a new billing note
GET	/api/claim_billing_notes	Retrieve or search billing notes
POST	/api/signed_consent_forms	signed_consent_forms Create
PATCH	/api/signed_consent_forms	signed_consent_forms Update
GET	/api/signed_consent_forms	signed_consent_forms Get
POST	/api/custom_appointment_fields	Create custom appointment fields
GET	/api/custom_appointment_fields	Retrieve or search custom appointment fields
PUT	/api/lab_orders/{id}	Update an existing lab order
PATCH	/api/lab_orders/{id}	Update an existing lab order
GET	/api/lab_orders/{id}	Retrieve an existing lab order
DELETE	/api/lab_orders/{id}	Delete an existing lab order
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.
GET	/api/clinical_notes_list	Retrieve or search clinical notes in batches. Results returned in order of ID.
GET	/api/custom_vitals/{id}	Retrieve an existing custom vital type
PUT	/api/sublabs/{id}	Update an existing sub vendor
PATCH	/api/sublabs/{id}	Update an existing sub vendor
GET	/api/sublabs/{id}	Retrieve an existing sub vendor
DELETE	/api/sublabs/{id}	Delete an existing sub vendor
GET	/api/patients/{id}/qrda1	Retrieve patient QRDA1
POST	/api/problems	Create patient problems
GET	/api/problems

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "List all day_sheet_charges?" -> GET /api/day_sheet_charges
• "Create a claim_billing_note?" -> POST /api/claim_billing_notes
• "List all claim_billing_notes?" -> GET /api/claim_billing_notes
• "Create a signed_consent_form?" -> POST /api/signed_consent_forms
• "List all signed_consent_forms?" -> GET /api/signed_consent_forms
• "Create a custom_appointment_field?" -> POST /api/custom_appointment_fields
• "List all custom_appointment_fields?" -> GET /api/custom_appointment_fields
• "Update a lab_order?" -> PUT /api/lab_orders/{id}
• "Partially update a lab_order?" -> PATCH /api/lab_orders/{id}
• "Get lab_order details?" -> GET /api/lab_orders/{id}
• "Delete a lab_order?" -> DELETE /api/lab_orders/{id}
• "Create a clinical_notes_list?" -> POST /api/clinical_notes_list
• "List all clinical_notes_list?" -> GET /api/clinical_notes_list
• "Get custom_vital details?" -> GET /api/custom_vitals/{id}
• "Update a sublab?" -> PUT /api/sublabs/{id}
• "Partially update a sublab?" -> PATCH /api/sublabs/{id}
• "Get sublab details?" -> GET /api/sublabs/{id}
• "Delete a sublab?" -> DELETE /api/sublabs/{id}
• "List all qrda1?" -> GET /api/patients/{id}/qrda1
• "Create a problem?" -> POST /api/problems
• "List all problems?" -> GET /api/problems
• "List all staff?" -> GET /api/staff
• "Update a patient_message?" -> PUT /api/patient_messages/{id}
• "Partially update a patient_message?" -> PATCH /api/patient_messages/{id}
• "Get patient_message details?" -> GET /api/patient_messages/{id}
• "Create a yellow_notepad?" -> POST /api/yellow_notepad
• "List all yellow_notepad?" -> GET /api/yellow_notepad
• "List all eligibility_checks?" -> GET /api/eligibility_checks
• "Update a doctor_work_schedule?" -> PUT /api/doctor_work_schedule/{id}
• "Partially update a doctor_work_schedule?" -> PATCH /api/doctor_work_schedule/{id}
• "Get doctor_work_schedule details?" -> GET /api/doctor_work_schedule/{id}
• "Create a medication?" -> POST /api/medications
• "List all medications?" -> GET /api/medications
• "Create a custom_demographic?" -> POST /api/custom_demographics
• "List all custom_demographics?" -> GET /api/custom_demographics
• "Create a appointments_list?" -> POST /api/appointments_list
• "List all appointments_list?" -> GET /api/appointments_list
• "Create a appointment_profile?" -> POST /api/appointment_profiles
• "List all appointment_profiles?" -> GET /api/appointment_profiles

Response Tips

• Check response schemas in references/api-spec.lap for field details
• List endpoints may support pagination; check for limit, offset, or cursor params
• Create/update endpoints typically return the created/updated object

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP