# Appointment slot is already used

**URL:** <https://community.open-emr.org/t/appointment-slot-is-already-used/1325>\
**Category:** Management and Administration\
**Created:** [June 6, 2013, 6:08pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325 "2013-06-06T18:08:25Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 6, 2013, 6:08pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/1 "2013-06-06T18:08:25Z")

</div>

**[tobiall](https://sourceforge.net/u/tobiall/)** wrote on [Thursday, June 06, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#79ca):

We upgraded from 4.0.0 to 4.1.1 when we try to make appointments we are getting the message (This appointment slot is already used, Use it anyway?). We are still able to schedule the appointment by clicking OK but this is annoying. Would anyone know what is causing this and how to fix it? We are running OpenEMR on Ubuntu 11.04. Please see attachment.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 6, 2013, 6:20pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/2 "2013-06-06T18:20:52Z")

</div>

**[yehster](https://sourceforge.net/u/yehster/)** wrote on [Thursday, June 06, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#3e3d):

In 4.1.1 if you don’t define IN/OUT of Office times for a provider that warning message is displayed.  
I consider it a bug, but others disagree.  
Here is a change you can make to disable that verification step.

> <https://github.com/yehster/openemr-archive/commit/a4cee0a8ab9a5a71eabdfe3d80f47b142b835494>

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 6, 2013, 6:37pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/3 "2013-06-06T18:37:55Z")

</div>

**[drkay](https://sourceforge.net/u/drkay/)** wrote on [Thursday, June 06, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#8119):

Yes, this is very annoying. We get this warning even if we are only changing the appointment status (to “arrived”, “in room 1”, etc.) I would also vote for it being considered a bug.

It might be less of a problem if the IN/OUT office times for providers were easier to use. As is, once they are on the calendar, you can’t click on them to change them. You have to search for them using the search function to be able to change them.

We need the ability to click and drag IN/OUT office times, or to click on them to change them in a dialogue window.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 6, 2013, 11:29pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/4 "2013-06-06T23:29:21Z")

</div>

**[tmccormi](https://sourceforge.net/u/tmccormi/)** wrote on [Thursday, June 06, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#bf5c):

Oh … Visolve did a fix for me for that issue in one of my projects. Perhaps they can post it here. We added a right click that lets you select to edit the Provider setting (IN/OUT)

–Tony

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 7, 2013, 3:32am UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/5 "2013-06-07T03:32:23Z")

</div>

**[yehster](https://sourceforge.net/u/yehster/)** wrote on [Friday, June 07, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#d26e):

The IN/OUT selection bug is my fault. Here’s a proposed fix.

> <https://github.com/yehster/openemr/commit/4a2a88dc8c1e7f60db7babf974fe5fc27f5f437b>

Sorry it took so long.  
This re-arranges the z-index of IN/OUT so that they are no longer obscured by the direct date selector.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 7, 2013, 4:43am UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/6 "2013-06-07T04:43:09Z")

</div>

**[drkay](https://sourceforge.net/u/drkay/)** wrote on [Friday, June 07, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#a36b):

Thanks, Kevin. Your fix seems to address well the inability to click on provider availability times.

However, I’m thinking that it would be better to only warn users that the appointment slot is already used when they are creating a new appointment, and not when they are just changing the status, or add a note to the appointment, for example.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 7, 2013, 4:46am UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/7 "2013-06-07T04:46:53Z")

</div>

**[drkay](https://sourceforge.net/u/drkay/)** wrote on [Friday, June 07, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#e0ce):

And maybe I should stop double-booking patients. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [June 7, 2013, 10:03am UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/8 "2013-06-07T10:03:29Z")

</div>

**[fsgl](https://sourceforge.net/u/fsgl/)** wrote on [Friday, June 07, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#48b4):

The “already used” message will disappear after proper setup according to the directions of [the video tutorial, “Using your calendar”](http://www.open-emr.org/wiki/index.php/OpenEMR_4.1_Users_Guide).

Using the Demo, there was no problem altering IN & Out times by double clicking them. A dialog box popped up asking: “Apply the changes to the Current event only, to this and all Future occurrences, or to All occurrences?”. Modifying an existing appointment or changing the status to “arrived” did not resulted in the “already used” message with the Demo calendar.

This problem will come up each time users upgrade from 4.1.0 to 4.1.1. It would be more efficient to have sticky posts, but El Jefe has been silent on that enhancement. Absent sticky posts, an advisory can be added to the Upgrade webpage.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [November 15, 2013, 6:45pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/9 "2013-11-15T18:45:58Z")

</div>

**[juggernautsei](https://sourceforge.net/u/juggernautsei/)** wrote on [Friday, November 15, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#bc71):

Hi, I just did an upgrade from 4.1.0(8) to 4.1.2(3) and I get this message now. Is there a patch for this anomaly or does the IN/OUT times need to be setup for all calendars?

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [November 16, 2013, 12:58pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/10 "2013-11-16T12:58:50Z")

</div>

**[fsgl](https://sourceforge.net/u/fsgl/)** wrote on [Saturday, November 16, 2013](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#e014):

Seems to be an ongoing problem, so the 2 events have be set up.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [March 9, 2014, 10:37am UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/11 "2014-03-09T10:37:44Z")

</div>

**[merlinsilk](https://sourceforge.net/u/merlinsilk/)** wrote on [Sunday, March 09, 2014](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#096c):

I am curious about the current situation about this behavior as it’s now about 4 month after the last post up here. I just installed and should have the latest version (where could I find out what version I run?) and I have set up the in/out/lunch times for my provider and I do get the warning of double booking.  
What do I have to do to avoid this warning?  
Thanks  
Merlin

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [March 9, 2014, 1:59pm UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/12 "2014-03-09T13:59:21Z")

</div>

**anonymous** wrote on [Sunday, March 09, 2014](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#1173):

Your current version can be found on the login page.

As far as the appointment alert, you are not alone. We have also experienced this issue for quite some time with a properly configured calendar. I haven’t had much time to troubleshoot, but the behavior seems somewhat inconsistent. Sometimes it happens, sometimes it doesn’t.

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [March 11, 2014, 11:09am UTC](https://community.open-emr.org/t/appointment-slot-is-already-used/1325/13 "2014-03-11T11:09:04Z")

</div>

**[fsgl](https://sourceforge.net/u/fsgl/)** wrote on [Tuesday, March 11, 2014](https://sourceforge.net/p/openemr/discussion/202505/thread/8935a604/#e89d):

Merlin,

We have a solo practice. Never had a problem after proper setup.

If you spell out the setup steps, perhaps we can determine the problem. Provide screenshots if possible.
