Staff Time Off
Hi all
Yes its me again. I was just wondering how everyone else block off their vet on the work flow. I am wondering this as i black them out using an appointment type i created call time off and the put in the times they are not avaliable. The problem with this is for some reason when you change the time ie to afternoon or eveningetc it seems that the blackout no longer apears on some of my vets. I dont get it. HELP
Jocelyn
Re: Staff Time Off
One of the developers will confirm if it is a bug or if we are both wrong :)
Matt C
On Mon, 31 Aug 2009 08:55:00 +0000 (UTC), kingswayvet@bigpond.com wrote: > Hi all > > Yes its me again. I was just wondering how everyone else block off their > vet on the work flow. I am wondering this as i black them out using an > appointment type i created call time off and the put in the times they are > not avaliable. The problem with this is for some reason when you change the > time ie to afternoon or eveningetc it seems that the blackout no longer > apears on some of my vets. I dont get it. HELP > > Jocelyn > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Staff Time Off
This is definitely a bug. I've raised a JIRA for it at https://openvpms.atlassian.net/browse/OVPMS-893
One thing this does highlight is that there should be a standard way of marking schedules unavailable for appointments.
Creating dummy appointments to do this is not ideal.
A facility that enables users to mark blocks of time unavailable, with an option to specify a recurrence (e.g daily, weekly, monthly etc) would be a better approach.
-Tim
Re: Staff Time Off
Cheers, Matt C
On Tue, 1 Sep 2009 12:42:42 +0000 (UTC), tma@netspace.net.au wrote: > This is definitely a bug. I've raised a JIRA for it at > https://openvpms.atlassian.net/browse/OVPMS-893 > One thing this does highlight is that there should be a standard way of > marking schedules unavailable for appointments. > Creating dummy appointments to do this is not ideal. > A facility that enables users to mark blocks of time unavailable, with an > option to specify a recurrence (e.g daily, weekly, monthly etc) would be a > better approach. > > -Tim > > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Re: Staff Time Off
M 0408 811 883
F (08) 6311 7431
E gerrie@essentia-consulting.com
Schedule blocking
Hi everyone. Hey Gerrie,
A development project has been created for this feature (www.openvpms.org/project/schedule-blocking).
Below are my responses to Gerries suggestions.
Points 1-3
Hey Gerrie just to clarify points 2 & 3. Did you mean for a particular blocking period to be able to be applied against multiple schedules or against all schedules in a particular schedule view ?
I wonder if it might be a simpler development task to have a single option "Apply to All Schedules in this View". To be able to apply the blocking to one or more arbitary schedules would mean having a schedule selector in the appointment dialog.
Copying the schedule blocking
I think this idea is great. Did you envision being able to copy specific date periods? Like setting a start date and an end date and saying copy all the blocking periods to this particular date? Again we could have the option of "Apply to All Schedules in this View".
I wonder if these changes should not apply generally to the "Edit Appointment" dialog. In other words when making any appointment, an option"Is Recurring" reveals the option to have it apply at some recurring interval. Say a series of injections. The problem would be in handling conflicts. Will they throw up a single "OK", "Overwrite" or "Cancel" dialog per conflict? Would they offer other slots at the same time with availability in the schedule view?
Matt C
Schedule blocking and rostering
Is schedule blocking being used as a way to do limited rostering within OpenVPMS?
If so, perhaps a better approach would be to add support for calendaring and rostering.
Calendars
Each vet would have a calendar, indicating their availability on any given day and time.
E.g it would track their annual leave.
Calendars could also inherit a system wide calendar that keeps track of public holidays so they only need to be defined once.
Rosters
A roster indicates which vets are available to work and when. It uses a vet's calendar to determine if they can be rostered on.
Appointment scheduling uses the roster to determine if any vet is available for a given date or time. If not, it is blocked out automatically.
When selecting a vet for an appointment, only those currently rostered on (and not scheduled for another appointment) would be listed.
The above could be expanded to have calendars and rosters for resources. A resource could be a vet, nurse, a surgery room, equipment, or a group of resources.
E.g a group resource named 'Surgery' might require a vet, a nurse and a surgery room to be rostered on before it can be selected for an appointment.
Re: Schedule blocking and rostering
I would have thought that this would be a fairly substantial development task. Is the blocking a reasonable cost effective middle step? Or is it wasted development funds as it would ultimately be superseded by rostering?
Data entry for rostering is always a bit of a trick. The use of templates to time effectively populate future dates and then allow ad hoc changes to be made as swaps etc occur. Also data import options for those wanting to import their rosters from spread sheets etc. How do people currently store their roster? Do they use spreadsheets? Printed paper versions? Purpose written software? If software, what export options do you have?
For the business analysts amongst us, a bonus of eventually having rostering in OpenVPMS is time and motion studies. We have had a computerised roster for some time now and it has allowed some very useful business analysis where we collate the OpenVPMS billing data vs our roster. Shift types can be assessed for productivity at different times of the day at different times of year. Having the roster in the same database as OpenVPMS would undoubtedly make this sort of analysis much easier.
Matt C
On Wed, 2 Sep 2009 23:42:08 +0000 (UTC), tma@netspace.net.au wrote: > Is schedule blocking being used as a way to do limited rostering within > OpenVPMS? > If so, perhaps a better approach would be to add support for calendaring > and rostering. > > Calendars > Each vet would have a calendar, indicating their availability on any given > day and time. > E.g it would track their annual leave. > Calendars could also inherit a system wide calendar that keeps track of > public holidays so they only need to be defined once. > > Rosters > A roster indicates which vets are available to work and when. It uses a > vet's calendar to determine if they can be rostered on. > Appointment scheduling uses the roster to determine if any vet is available > for a given date or time. If not, it is blocked out automatically. > When selecting a vet for an appointment, only those currently rostered on > (and not scheduled for another appointment) would be listed. > > The above could be expanded to have calendars and rosters for resources. A > resource could be a vet, nurse, a surgery room, equipment, or a group of > resources. > E.g a group resource named 'Surgery' might require a vet, a nurse and a > surgery room to be rostered on before it can be selected for an > appointment. > > > > a 'Surgery' resource group might > require a vet, nurse and surgery room > > > > > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Re: Schedule blocking and rostering
We would want to incorporate nurse and receptionist rostering in the project, which is a far worse job than rostering the vets in our experience.
It would certainly be a substantial project but if it was to come to fruition OpenVPMS would have a substantial advantage over other offerings.
_______________________________ Craig Challen Vetwest Animal Hospitals
Re: Schedule blocking and rostering
I agree. Non veterinary staff rostering is far more dynamic in our clinic. We have a web based system of requesting swaps, marking fill-ins as urgent, allocating leave etc all through a web site that staff can access from home. It is integrated into a messaging system (tho I am yet to fully implement the total capacity of messaging yet). I see us still using this but I will create integration that synchronizes the changes in the system with OpenVPMS.
We update the roster from spreadsheets in which, our rosters have been traditionally created. Spreadsheets are the user interface of choice of the staff that do our roster and I have found it better to accommodate their preferences rather then insisting on them using a purpose written interface. They tend to create templates (say a 4 or 8 week rotation), use them to populate 6 months or more, then adjust for individual requests/requirements and leave. "Search and Replace" is one feature they use very frequently (the ability to select a bunch of cells and replace one value with another).
I'm not sure what if any of these features would be of use in this development or if we just leave the user interface to the users and have a more options for import (CSV, XML, etc etc).
Matt C
On Thu, 3 Sep 2009 09:55:27 +0800, "Craig Challen"
wrote: > I would favour at least scoping a rostering solution at this stage and > finding out what we might be up for in costs to get it developed. This > would probably be cheaper in the long run I imagine than developing an > interim solution. > > We would want to incorporate nurse and receptionist rostering in the > project, which is a far worse job than rostering the vets in our > experience. > > It would certainly be a substantial project but if it was to come to > fruition OpenVPMS would have a substantial advantage over other offerings. > > > > _______________________________ > Craig Challen > Vetwest Animal Hospitals > > -----Original Message----- > From: users-bounces@lists.openvpms.org > [mailto:users-bounces@lists.openvpms.org] On Behalf Of mpcosta > Sent: Thursday, 3 September 2009 09:04 > To: OpenVPMS User Mailing List > Subject: Re: [OpenVPMS Users] Schedule blocking and rostering > > > Hey Tim, > This has always been the end point for the scheduler hasn't it. I remember > the resource model being included in the graphical scheduler requirement > document. > > I would have thought that this would be a fairly substantial development > task. Is the blocking a reasonable cost effective middle step? Or is it > wasted development funds as it would ultimately be superseded by rostering? > > Data entry for rostering is always a bit of a trick. The use of templates > to time effectively populate future dates and then allow ad hoc changes to > be made as swaps etc occur. Also data import options for those wanting to > import their rosters from spread sheets etc. How do people currently store > their roster? Do they use spreadsheets? Printed paper versions? Purpose > written software? If software, what export options do you have? > > For the business analysts amongst us, a bonus of eventually having > rostering in OpenVPMS is time and motion studies. We have had a > computerised roster for some time now and it has allowed some very useful > business analysis where we collate the OpenVPMS billing data vs our roster. > Shift types can be assessed for productivity at different times of the day > at different times of year. Having the roster in the same database as > OpenVPMS would undoubtedly make this sort of analysis much easier. > > Matt C > > > On Wed, 2 Sep 2009 23:42:08 +0000 (UTC), tma@netspace.net.au wrote: >> Is schedule blocking being used as a way to do limited rostering within >> OpenVPMS? >> If so, perhaps a better approach would be to add support for calendaring >> and rostering. >> >> Calendars >> Each vet would have a calendar, indicating their availability on any > given >> day and time. >> E.g it would track their annual leave. >> Calendars could also inherit a system wide calendar that keeps track of >> public holidays so they only need to be defined once. >> >> Rosters >> A roster indicates which vets are available to work and when. It uses a >> vet's calendar to determine if they can be rostered on. >> Appointment scheduling uses the roster to determine if any vet is > available >> for a given date or time. If not, it is blocked out automatically. >> When selecting a vet for an appointment, only those currently rostered on >> (and not scheduled for another appointment) would be listed. >> >> The above could be expanded to have calendars and rosters for resources. > A >> resource could be a vet, nurse, a surgery room, equipment, or a group of >> resources. >> E.g a group resource named 'Surgery' might require a vet, a nurse and a >> surgery room to be rostered on before it can be selected for an >> appointment. >> >> >> >> a 'Surgery' resource group might >> require a vet, nurse and surgery room >> >> >> >> >> _______________________________________________ >> OpenVPMS User Mailing List >> users@lists.openvpms.org >> To unsubscribe or change your subscription visit: >> http://lists.openvpms.org/listinfo/users >> Posts from this mailing list can be viewed online and replied to in the >> OpenVPMS User's forum- http://tinyurl.com/openvfu >> > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu > > > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Re: Schedule blocking and rostering
The resource model was one approach considered for the scheduler.
It is more complex to implement and so the current solution was taken as it does most of what people want in a much simpler fashion.
Implementing blocking would ultimately be superceded by rostering.
-Tim
Staff Time Off
The above bug is now fixed. The fix will be in the 1.4 release.
-Tim
Schedule Blocking
Sandra @ Bellarine
We would love the ability to add multiple appointment entries and recurring appointments! It's been one of those things I've been meaning to get around to request. By this I mean adding an appointment and being able to select which dates I want the entry copied to or alternatively just giving it a start and end date.
The rostering sounds good, the data entry and editing would be challenging because as Matt indicated we also have lots of changes and swaps happening. I'm not involved in the rostering here but I'll mention it to the rostering person at this end and she can get on and put her two bobs worth in.
Sandra.
Rostering/Blocking project - should we stage it?
Hi guys,
This project has been cooking for a while. I have extended the discussion period for this project by a month as it has turned into something more substantial then the original blocking appointment suggestion. If we are to indeed scope the ideal features for a rostering inclusion into OpenVPMS then it may take a while to work through the various features that will come up. We may even need interested parties to workshop the concepts in person once the project is mature enough.
To keep it simple, lets start with Tims grouping.
1. Calendars
2. Rosters
If we begin with a discussion about Calendars, Tims summary was
"...
Each vet would have a calendar, indicating their availability on any given day and time.
E.g it would track their annual leave.
Calendars could also inherit a system wide calendar that keeps track of public holidays so they only need to be defined once...."
Does anyone have any suggestions as to have they might enter such a calendar for say a vet.
Questions:
1. How do people currently store their vet "calendar". Excel? Word?
2. To what detail do people currently assign their vet availability? Down to a specific date? day of week? hour of day? shift types?
That should do for now :)
Matt C
Re: Rostering/Blocking project - should we stage it?
Currently we use Excel for the vet rosters, we only go down to day detail because we have multiple clinics and use a dimension for that, so it would all get too big and ugly if we tried to put in timeslots within the day. We would really like being able to go down to hourly though.
_______________________________ Craig Challen Vetwest Animal Hospitals
-----Original Message----- From: users-bounces@lists.openvpms.org [mailto:users-bounces@lists.openvpms.org] On Behalf Of mpcosta@boroniavet.com.au Sent: Monday, 14 September 2009 20:48 To: users@lists.openvpms.org Subject: [OpenVPMS Users] Rostering/Blocking project - should we stage it?
Hi guys, This project has been cooking for a while. I have extended the discussion period for this project by a month as it has turned into something more substantial then the original blocking appointment suggestion. If we are to indeed scope the ideal features for a rostering inclusion into OpenVPMS then it may take a while to work through the various features that will come up. We may even need interested parties to workshop the concepts in person once the project is mature enough.
To keep it simple, lets start with Tims grouping. 1. Calendars 2. Rosters
If we begin with a discussion about Calendars, Tims summary was
"...
Each vet would have a calendar, indicating their availability on any given day and time. E.g it would track their annual leave. Calendars could also inherit a system wide calendar that keeps track of public holidays so they only need to be defined once...."
Does anyone have any suggestions as to have they might enter such a calendar for say a vet. Questions: 1. How do people currently store their vet "calendar". Excel? Word? 2. To what detail do people currently assign their vet availability? Down to a specific date? day of week? hour of day? shift types?
That should do for now :)
Matt C _______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Rostering/Blocking project - should we stage it?
There would be 2 approaches for entering time off:
1. By specifying an absolute date/time range
You would use this to enter annual leave etc. This would have the following fields:
2. By specifying recurring days/time
You would use this to indicate days or times that can't be worked. E.g to indicate that an employee can't work weekends.
This would have the following fields:
E.g, to specify that an employee can't work evening shifts for the next 6 months, you might specify the following:
Days: All
From time: 6pm
To time: 12am
Start date: 1/Oct/09
Repeat Interval: 6 month
Staff Time Off
Hi,
I am not sure if there is an updated forum for this project, but Advanced Vetcare would like to pledge for this project if it is still requiring funding.
Thanks
Re: Staff Time Off
The project is quite large as it has expanded to include rostering. Rostering is such a big project it probably needs a working group and a sit down meeting with some one like Tony. If there is enough interest in getting appointment blocking as an interim feature as described at the start of this forum topic, I can create a separate development project for that.
Cheers, Matt C
On Mon, 26 Jul 2010 00:37:40 +0000 (UTC), gretalloyd@advancedvetcare.com.au
wrote: > Hi, > I am not sure if there is an updated forum for this project, but Advanced > Vetcare would like to pledge for this project if it is still requiring > funding. > Thanks > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Recurring Appointments
From the recent meeting
htp://www.openvpms.org/project/schedule-blocking
o It was suggested that this could be redefined to provide for recurring appointments.
o Using recurring appointments the users present felt that it would be possible to “block” the schedule easily.
o The ability to create a recurring appointment will be specified as;
o Daily, Weekly, Monthly, Yearly
o The number of recurrences as Infinite or Defined (eg. Once, twice etc)
o When editing/deleting a recurring appointment it should be
§ Visible in some way (eg. A symbol).
§ Prompt the user if the change should occur for all instances.
o If there is nothing more to add then Tony will move it to Developer Review and get it costed with a specification of his own.
o It shall move to Developer Review
Blocking schedules and Recurrent Appointments
Hi everyone,
Some of you may have noticed the discussion happening at the Development project associated with this Forum. (http://www.openvpms.org/project/schedule-blocking).
The project has been
a) Split into 2 projects:
1. http://www.openvpms.org/project/schedule-blocking
2. http://www.openvpms.org/project/add-recurrence-appointments
b) Has been costed @
1. $6790
2. $2170
Public pledges can be made to this forum topic or email me directly by clicking here (link only works in the forum).
Development will not commence until fully funded.
Matt C