Skip to content

View Appointment

1. What does this feature do? (High-Level Overview)

Section titled “1. What does this feature do? (High-Level Overview)”

This feature allows users to open an existing calendar appointment and review its session details in a modal. It gives a single, fast checkpoint to confirm schedule information and continue with related actions such as creating or opening the linked note, editing, deleting, or duplicating.

  • Provider roles (for example RBT/BCBA/Analyst): Can open and view appointments visible in their own calendar context.
  • Admin-style roles (for example Superadmin/Admin/Owner/Manager) or any role with manage_notes: Can view appointments in shared calendars after selecting a provider or patient context.

Permission-related behavior:

  • manage_notes enables shared-calendar context (provider/patient switching) that determines which appointments can be opened from the calendar.
  • Appointment access is scoped to the current location context.
  • Edit availability in the modal is conditional: when an appointment already has a related note, the edit action is hidden.
  • Rule 1: Opening an appointment in the modal refreshes appointment data from the API (appointments/:id) before displaying final action states.
  • Rule 2: The modal checks whether the session is in the future (/v2/validate-date-time) to control note creation availability.
  • Rule 3: If the appointment already has a related note, the modal shows Go to note and hides edit.
  • Rule 4: If no related note exists and the session is not in the future, the modal shows Create RBT Note (CPT 97153) or Create Analist Note (other CPT values).
  • Rule 5: If no related note exists and the session is still in the future, note creation is blocked and the UI shows when note creation becomes available.
  • Rule 6: If appointment data cannot be loaded (or the modal has no appointment input), the modal closes to prevent working with stale or incomplete data.
  • Rule 7: POS display uses the saved POS description when present; otherwise it falls back to the standard POS name.
  1. Medical > Calendar.
  2. Route: /calendar/view.
  3. In month/week/day views, click an appointment event chip/card to open the View Appointment modal (ModalCalendarV2Component).
  4. The modal displays patient name, DOS, time in/out, provider, POS with description, and CPT code badge, plus contextual actions (copy, delete, edit, note).

Scenario A: Provider views an appointment and creates a note

  1. Open Medical > Calendar.
  2. Click an existing appointment in month, week, or day view.
  3. Review appointment details in the modal.
  4. If no note exists and the session is already eligible by time, click Create RBT Note or Create Analist Note.
  5. Confirm navigation to the corresponding note route and continue documentation.

Scenario B: Manager/Admin reviews an appointment in shared-calendar mode

  1. Open Medical > Calendar.
  2. Select a provider or patient to load the target shared calendar.
  3. Click the appointment event.
  4. Review session details and use the available action:
  5. Use Go to note if a note already exists, or use copy/delete/edit based on need and availability.
  • Q: What happens if the appointment already has a related note?
    A: The modal shows a message that a note already exists, offers Go to note, and hides edit for that appointment.

  • Q: What happens if I open a future appointment and try to create a note?
    A: The create-note button is not shown yet; the modal displays the date/time when note creation becomes available.

  • Q: What if appointment details fail to load when opening the modal?
    A: The modal closes automatically, avoiding interaction with incomplete appointment data.