Question about flow board code and database tables (appointment status)

I am trying to customize some aspects of the flow board for a simpler use case than clinic management. Basically, I want to use it to allow clinicians to set their own appointment schedules, mark attendance, and provide paperwork for the session. I have begun reading deep into several files and the data tables to understand what is going on.

I want to change some of the values for appointment status that make sense in this environment but would not be useful for the typical use case of the flowboard.

I see that appointment statuses are defined in two different places:

  1. Select * from list_options where list_id = ‘apptstat’ gives me a list in the databse

  2. add_edit_event_user.php lines 582- 595 also place values hard-coded into an array:

     $statuses = array(
     '-' => '',
     '*' => xl('* Reminder done'),
     '+' => xl('+ Chart pulled'),
     'x' => xl('x Cancelled'), // added Apr 2008 by JRM
     '?' => xl('? No show'),
     '@' => xl('@ Arrived'),
     '~' => xl('~ Arrived late'),
     '!' => xl('! Left w/o visit'),
     '#' => xl('# Ins/fin issue'),
     '<' => xl('< In exam room'),
     '>' => xl('> Checked out'),
     '$' => xl('$ Coding done'),
     );
    

Is there a reason that these were defined in two places?

Is one or the other depreciated in use?

Should these pull only from the database to allow easier customization of the appointment statuses?

I have learned enough php in the past 4 months to (barely) read the code, but I am not yet confident enough to try to implement this potential change.

Thanks Derek

@dhillison,
We assume that initially status have been hard-coded, but now it has been migrated into Administration->Lists->Appointment Statuses. So you can customize the appointment status under the administration option.
In this file [ interface/main/calendar/add_edit_event.php(762-779) ], you can find the hard-coded status code have been commented. May be failed to comment the lines in the file add_edit_event_user.php

Thanks,
ViSolve