> ## Documentation Index
> Fetch the complete documentation index at: https://ekacare-mintlify-dfb0ffc0.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Appointment

> Scheduled patient–doctor interactions within Core EMR

## Appointment

An **Appointment** represents a scheduled meeting between a **patient** and a **doctor**. Appointments are core operational entities used to organize consultations, procedures, and follow-up visits across healthcare settings.

Each appointment captures key details such as identifiers, participant information, location, timing, and current status.

Read more : ([API Reference - Appointment](/api-reference/doc-tool/Actors/actors)) section.

Read more : ([API Reference - communication-flow-appointment-clinical-events ](/communication-flow-appointment-clinical-events)) section.

***

## Use Cases

### Patient Consultation Scheduling

Schedule in-person or virtual consultations between patients and doctors with defined time slots.

### Walk-In and Emergency Bookings

Record and manage walk-in or urgent appointments alongside scheduled visits.

### Rescheduling and Cancellations

Update appointment timings, reassign doctors, or cancel appointments while maintaining an audit trail.

### Teleconsultation Coordination

Link appointments to virtual consultation platforms for remote care delivery.

### Clinic and Resource Planning

Use appointment data to manage clinic capacity, room usage, and clinician availability.

### Notifications and Reminders

Trigger reminders and updates for patients and doctors to reduce no-shows and improve attendance.

***

## Notes & Considerations

* **Status lifecycle**\
  Appointments typically move through states such as scheduled, confirmed, completed, cancelled, or no-show.

* **Participant linkage**\
  Appointments should be correctly linked to patient and doctor profiles to ensure data consistency.

* **Time and location accuracy**\
  Ensure correct timezone, clinic location, or virtual meeting details are captured.

* **Operational dependencies**

Read more : ([API Reference - Appointment](/api-reference/doc-tool/Actors/actors)) section.

Read more : ([API Reference - communication-flow-appointment-clinical-events ](/communication-flow-appointment-clinical-events)) section.