Reminders-All reminders for a client printing on one card, not one card for each patient
At present we print and email our reminders. We are new to OpenVPMS and have been used to being able to pool all the reminders for a client onto one card or into one email. Eg: Mr Smith has 3 dogs due for worming and they are also all due for vaccination. These 6 reminders would pool into one reminder email or letter. I would love this to happen on OpenVPMS. Today I printed approx 500 postcards and we will now sort through these (well my kids will) for the clients with more than one reminder card and I will hand write the other patient names onto the one card for postage. We end up discarding at least 50% of the postcards that are printed on which is such a waste. We get a lot of negative feedback from clients if we post the multiple cards, due to the wastage of the paper and waste of money with the cost of the stamps. As we can't sort through the emails we often get replies requesting only one email instead of 3, 4,5 or 6 - which we cannot do. Does anybody know a better way to tackle this. Tony suggested I add this to the forum to see what everybody else thinks/wants.
Re: Reminders-All reminders for a client printing on one card,
As an interim measure, we could add support to suppress generation of more than one reminder. i.e if a reminder has been generated for a customer, don't generate any others.
-Tim
sandra@bellvet.com.au wrote: > At present we print and email our reminders. We are new to OpenVPMS > and have been used to being able to pool all the reminders for a > client onto one card or into one email. Eg: Mr Smith has 3 dogs due > for worming and they are also all due for vaccination. These 6 > reminders would pool into one reminder email or letter. I would love > this to happen on OpenVPMS. > Today I printed approx 500 postcards and we will now sort through > these (well my kids will) for the clients with more than one reminder > card and I will hand write the other patient names onto the one card > for postage. We end up discarding at least 50% of the postcards that > are printed on which is such a waste. We get a lot of negative > feedback from clients if we post the multiple cards, due to the > wastage of the paper and waste of money with the cost of the stamps. > As we can't sort through the emails we often get replies requesting > only one email instead of 3, 4,5 or 6 - which we cannot do. Does > anybody know a better way to tackle this. Tony suggested I add this > to the forum to see what everybody else thinks/wants. > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/listinfo/users >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/mailman/listinfo/users
Re: Reminders-All reminders for a client printing on one card,
The reminder workspace could still list pets included in the present query.
Matt C
On Wed, 14 Jan 2009 08:32:55 +1100, Tim Anderson
wrote: > I agree there does need to be a facility to collate multiple reminders > into a single email/letter per customer. > The current approach could lead to a lot of spam. > > As an interim measure, we could add support to suppress generation of > more than one reminder. > i.e if a reminder has been generated for a customer, don't generate any > others. > > -Tim > > sandra@bellvet.com.au wrote: >> At present we print and email our reminders. We are new to OpenVPMS >> and have been used to being able to pool all the reminders for a >> client onto one card or into one email. Eg: Mr Smith has 3 dogs due >> for worming and they are also all due for vaccination. These 6 >> reminders would pool into one reminder email or letter. I would love >> this to happen on OpenVPMS. >> Today I printed approx 500 postcards and we will now sort through >> these (well my kids will) for the clients with more than one reminder >> card and I will hand write the other patient names onto the one card >> for postage. We end up discarding at least 50% of the postcards that >> are printed on which is such a waste. We get a lot of negative >> feedback from clients if we post the multiple cards, due to the >> wastage of the paper and waste of money with the cost of the stamps. >> As we can't sort through the emails we often get replies requesting >> only one email instead of 3, 4,5 or 6 - which we cannot do. Does >> anybody know a better way to tackle this. Tony suggested I add this >> to the forum to see what everybody else thinks/wants. >> _______________________________________________ >> OpenVPMS User Mailing List >> users@lists.openvpms.org >> To unsubscribe or change your subscription visit: >> http://lists.openvpms.org/mailman/listinfo/users >> > > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/listinfo/users >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/mailman/listinfo/users
RE: Reminders-All reminders for a client printingon one card, n
Agree we need some way of combining reminders for a customer.
The question is how much control will people want on which reminder types get combined and which print their own document/email. Or if set to only print one reminder per customer then all reminder types behave the same ?
Also we should also support single reminder by patient options I assume ?
I think we may need to provide a single merge field that collates the patient/customer reminders i.e
Peppy C4 12/02/2009 Peppy Proheart 12/02/2009 Jimmy F3 15/02/2009
so these can be printed on the combined merge letter. Of course the template name of the combined merge letter will need to be specified somewhere as well.
Cheers Tony -----Original Message----- From: users-bounces@lists.openvpms.org [mailto:users-bounces@lists.openvpms.org]On Behalf Of Tim Anderson Sent: Wednesday, 14 January 2009 08:33 To: sandra@bellvet.com.au; OpenVPMS User Mailing List Subject: Re: [OpenVPMS Users] Reminders-All reminders for a client printingon one card, not one card for each patient
I agree there does need to be a facility to collate multiple reminders into a single email/letter per customer. The current approach could lead to a lot of spam.
As an interim measure, we could add support to suppress generation of more than one reminder. i.e if a reminder has been generated for a customer, don't generate any others.
-Tim
sandra@bellvet.com.au wrote: > At present we print and email our reminders. We are new to OpenVPMS > and have been used to being able to pool all the reminders for a > client onto one card or into one email. Eg: Mr Smith has 3 dogs due > for worming and they are also all due for vaccination. These 6 > reminders would pool into one reminder email or letter. I would love > this to happen on OpenVPMS. > Today I printed approx 500 postcards and we will now sort through > these (well my kids will) for the clients with more than one reminder > card and I will hand write the other patient names onto the one card > for postage. We end up discarding at least 50% of the postcards that > are printed on which is such a waste. We get a lot of negative > feedback from clients if we post the multiple cards, due to the > wastage of the paper and waste of money with the cost of the stamps. > As we can't sort through the emails we often get replies requesting > only one email instead of 3, 4,5 or 6 - which we cannot do. Does > anybody know a better way to tackle this. Tony suggested I add this > to the forum to see what everybody else thinks/wants. > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/listinfo/users >_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/mailman/listinfo/users
_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/mailman/listinfo/users
Reminders
Sandra @ Bellarine
Hi Guys,
I've had a read of your feedback. Regarding the suggestion from Tim "we could add support to suppress generation of more than one reminder" I assume this would mean that if a client had 3 pets all due for vacc & worming that only one single reminder would be produced, what about the other reminders would they not get produced at all? Maybe I don't follow? If this was the case I would rather keep producing the multiple cards and wait for a different solution as clients are accustomed to being notified of all treatments due for all pets.
Where Tony talked about whether we combine all or only selected reminders etc. I would be happy with a combine all and cannot think of a circumstance where I would only want to combine selected reminders. In Rx Works they had a choice of 3 options: 1.Group on Patient 2.Group on Client or 3.Do NOT Group at all . I never used the group on patient as it would still result in mulitple reminders. I just used the Group on Client.
I don't know enough about Jasper Reports, queries etc to provide input on Matt's comments.
Grouped reminders
Hey Sandra,
- Yeah I agree. We also could not think of a situation where specific reminder types would be grouped and others not.
- Grouping by client would suit our needs and the environments as well.
As for returning a single result containing all the animals with reminders and their reminder details.... this could work as an interim solution.
Ie. the reminder letter may look like;
************************
CLINIC HEADER
Dear ...... The following pets appear to be due blah blah
LIST OF PETS (in format described by Tony above)
Thak you, if you have already ... blah blah
***************************
What do you think?
Matt C
Grouped Reminders
Sandra @ Bellarine
I think that would be great!
Combined reminders - draft spec
Boronia VC and Bellarine VC have been in talks and want to get this initiative into the next release.... even the 1.3 final release if possible.
In order to get to this next stage can I propose the following draft specification:
Contents
1. Reminders are grouped by customer.
2. The reminder letter/card will contain a list of all the patients with an active owner-patient relationship which have a due reminder.
3. This grouped reminder type will use its own single template
4. Optional: To facilitate staged reminders (eg. 1st, 2nd, 3rd reminders)
Details
1. Reminders are grouped by customer.
2. The reminder letter/card will contain a list of all the patients with an active owner-patient relationship which have a due reminder.
eg. [Reminder Type] : [Patient Name] Is due for [Product] on the [Reminder Due Date]\n
Canine Annual Vaccination: Peppy Is due for a C4 on the 12/02/2009
Canine Annual Heartworm Prevention: Peppy Is due for a Proheart on the 12/02/2009
Feline Annual Vaccination: Jimmy Is due for a F3 on the 15/02/2009
This string could be returned en bloc by OpenVPMS as a function or as individual functions for each field. Individual functions would be better but more time consuming to develop. A cost scenario for each would be great.
3. This grouped reminder type will use its own single template
This means that the previous system of having staged reminders (1st, 2nd 3rd) would be lost. You can't have a second reminder template if only on of the animals ina group of three is overdue. (See next).
4. Optional: To facilitate staged reminders (eg. 1st, 2nd, 3rd reminders)
If the above functions in point 2 could return [Reminder No] then a Ireport template could have conditional text that would display based on reminder number.
eg.
1st Reminder:
Canine Annual Vaccination: Peppy Is due for a C4 on the 12/02/2009
2nd Reminder:
Canine Annual Vaccination: Peppy was due for a C4 on the 12/02/2009
If Reminder No = 2 show "Peppy is now overdue fopr vaccination. He could perish at ANY time!"
2nd Reminder:
Canine Annual Vaccination: Peppy was due for a C4 on the 12/02/2009
If Reminder No = 3 show "Peppy is now very overdue for vaccination. If Peppy is still alive, you should rush to the vets immediately!"
Bellarine & Boronia would invite urgent comment from those who may wish to add to the specification. We will be passing the spec to the OpenVPMS developers for costing by 25th Feb. Of course if you REALLY want to get your requests included then you might be willing to cofund it with us?
Matt C
Reminder Generation
Hi All,
Great to see Bellarine/Boronia working together in this way - what you have produced looks pretty spot on and the optional extras if not applied immediately should be in a follow on fairly soon. The other request I would add is (if not already available) the abilility to export the reminder data to another program such as excel so it can be sorted then meregd to email or label printing which we used to use in RxW.. On this - is there a data export facility in OpenVPMS somewhere that I have not found yet?
Cheers,
Nick
Reminders as CSV or other formats
Hey Nick,
A good request and will serve those clinics who send their reminder lists electronically to printing houses that do all their printing and mailing for them.
At the moment this capacity is not within the OpenVPMS application. We at Boronia do generate such a data dump using direct SQL queries of the database but I would suggest that this sort of interaction is best done by experienced SQL writers.
It might be the sort of request that could be done as a direct request to a developer for the moment, but eventually such choice of returned format, would have a very obvious place in our Reports workspace.
Thanks for the suggestion, keep 'em coming,
Matt C
Re: Combined reminders - draft spec
M 0408 811 883
F (08) 6311 7431
E gerrie@essentia-consulting.com
2nd, 3rd reminders and grouped reminders
Thanks Gerrie,
I agree subsequent reminders for many clinics are very important and it would be a great shame to lose the sophisticated reminder logic currently present in OpenVPMS.
Perhaps the existing setups (currently listed as "Templates" within reminder types) could be used to build the list of patients to be included in our grouped reminder template.
Matt C
RE: 2nd, 3rd reminders and grouped reminders
Regards,
Tony Vigano
-----Original Message----- From: users-bounces@lists.openvpms.org [mailto:users-bounces@lists.openvpms.org] On Behalf Of mpcosta@boroniavet.com.au Sent: Sunday, 22 February 2009 08:54 PM To: users@lists.openvpms.org Subject: [OpenVPMS Users] 2nd, 3rd reminders and grouped reminders
Thanks Gerrie, I agree subsequent reminders for many clinics are very important and it would be a great shame to lose the sophisticated reminder logic currently present in OpenVPMS. Perhaps the existing setups (currently listed as "Templates" within reminder types) could be used to build the list of patients to be included in our grouped reminder template. Matt C _______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/mailman/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/mailman/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: 2nd, 3rd reminders and grouped reminders
Sorry, I am going to jump to the defence of OpenVPMS on these ones :-)
In comparison to Netvet the OpenVPMS reminder system is light years ahead.
The ability to configure reminder types once and then have the nurse or receptionist only need to set two dates to generate all the reminders (1st, 2nd, 3rd etc) and then have the system print, email, list them without any intervention is a huge improvement. In Netvet you had to do multiple runs and remember every aspect of the previous runs to get the date and reminder ranges setup correctly each time. OpenVPMS also has automatic cancelling and a much better mechanism for dealing with automatic reminder completion via reminder groups then Netvet which used reminder ranges that relied heavily on billing item names having a similar prefix ...
The issue we are discussing here is the ability to take multiple patient reminders for the same customer and put them on one letter/email. Netvet didn't have this either ....
Also OpenVPMS has full stock control facilities as of version 1.2. Just not automatic supplier ordering and supplier integration functions. We are waiting on the wholesalers to drive this in the project ...
Cheers Tony
> Tony De Keizer > Principal Consultant > Vertical Connect Pty Ltd > Phone: + 61 (0)3 97229824 > Mobile +61 (0)4 21347105 > Email: tony@verticalconnect.net > From: Tony Vigano > Organization: Swanbourne Veterinary Centre > Reply-To: OpenVPMS User Mailing List > Date: Mon, 23 Feb 2009 08:40:10 +0800 > To: , 'OpenVPMS User Mailing List' > > Subject: RE: [OpenVPMS Users] 2nd, 3rd reminders and grouped reminders > > Hi Matt, > For those of us that used Netvet it is one aspect of OpenVPMS which is > lacking at the moment (apart from the stockcontrol). I think it is the > burning issue at the moment. > > Regards, > > Tony Vigano > > -----Original Message----- > From: users-bounces@lists.openvpms.org > [mailto:users-bounces@lists.openvpms.org] On Behalf Of > mpcosta@boroniavet.com.au > Sent: Sunday, 22 February 2009 08:54 PM > To: users@lists.openvpms.org > Subject: [OpenVPMS Users] 2nd, 3rd reminders and grouped reminders > > Thanks Gerrie, > I agree subsequent reminders for many clinics are very important and it > would be a great shame to lose the sophisticated reminder logic > currently present in OpenVPMS. > > Perhaps the existing setups (currently listed as "Templates" within > reminder types) could be used to build the list of patients to be > included in our grouped reminder template. > > Matt C > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/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/mailman/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/mailman/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Burning issues
Hey Tony,
Glad to hear this is an issue that is important to you guys at Swanbourne. Comment on the draft specification (posted today) if you have any further suggestions.
I will be counting on all interested clinics that can see that this will benefit them, when I pass the hat around aoon.
Matt C
Reminders
Sandra @ Bellarine
Hi Matt: I don't understand what you mean by "This string could be returned en bloc by OpenVPMS as a function or as individual functions for each field. Individual functions would be better but more time consuming to develop". Do I need to be able to understand this to give accurate feedback?
I think the format you suggested is great.
When you write in your previous post:
"3. This grouped reminder type will use its own single template. This means that the previous system of having staged reminders (1st, 2nd 3rd) would be lost. You can't have a second reminder template if only on of the animals in a group of three is overdue".
We were able to send reminders in RxWorks that listed due and overdue reminders for each patient. I have scanned a copy for you to see, the reminder range I selected for this print was 27/11/08 to 11/12/08, so the October listings on these reminders were overdue. (couldn't attach over 1MB so have done a print screen, very poor quality hope you can see it). Our clients seemed to be happy with this information.
When you mention:
4. Optional: To facilitate staged reminders (eg. 1st, 2nd, 3rd reminders)If the above functions in point 2 could return [Reminder No] then a Ireport template could have conditional text that would display based on reminder number. Do you mean that in further development this could be possible? I didn't quite follow the 'ireport template' conditional text bit.
If the development went through to get the first reminder for patients on the one client letter, would the 2nd and 3rd reminders continue to print on individual letters as we wouldn't want to stop sending those.
Also, it would not bother me if safety net reminders (vaccination reminders if still overdue a year later) printed on individual letters or pooled onto one letter.
Sandra.
Grouped reminders clarified a bit
Hi Sandra, hope this response clears up some of the language I've used
"I don't understand what you mean by "This string could be returned en bloc by OpenVPMS as a function or as individual functions for each
field. Individual functions would be better but more time consuming to develop".
Sorry Sandra! What a tool I am! I wrote this as a direct response to Tonys comments about returning a lump of text (a "string") which would contain all the details of the animal and their reminder dates. Just like in your sample.
eg. Fluffy Jones Due 21st September for a F3 vaccination
Note that while this would look fine in a document, it doesn't allow the author of a template to tease the individual parts apart and use them directly. So for example, if I wanted the open office template to change the format of the due date to be "Monday 21st Sep" I couldn't do that.
This approach might represent a lot less work for the developers then returning details for each individual vaccination.
"Do you mean that in further development this could be possible? I didn't quite follow the 'ireport template' conditional text bit."
So what I was trying to say here is that where as currently in OpenVPMS you can have a completely different template or layout for your first reminder and second reminder etc for a grouped reminder you couldn't have a completely different layout in our example becuase there might be a mix of overdue and non overdue reminders in the one letter.
"Conditional text" just means text that is shown if a certain condition is met. For example;
If one of the patients in the grouped reminder is up to their 3rd reminder, show a). If not show b).
I'll give you a call tommorrow or during the week Sandra.
Cheers,
Matt
Grouped Reminders
Sandra @ Bellarine
Hi Matt,
That all makes sense now!
In RxWorks we didn't have the option of editing the template for this grouped reminder and I never found that a problem with the format that was used.
We didn't have the ability to have different 1st, 2nd or 3rd reminders in RxWorks when grouping reminders and clients were fine with that. It would list due and overdue reminders in exactly the same format and we never had one complaint.
As far as Conditional Text goes, this was also not available on RxWorks and as I said not one complaint in all the time we were sending out the grouped reminders in that format!
Sandra.
Grouped reminder specification document
Hi everyone,
Thanks for everyones input on this important feature.
I have attached a document (you might need to visit the site to see it) containing the current details of this modification. Our hope is to get it included in the 1.3 official release.
The next step is for the developers to look at what we have proposed and give a costing. I will advise the community when this costing is returned.
At that time I will be seeking contributions from the user community, so if this is an important issue to you then let me know.
Cheers,
Matt C
Grouped Reminders
Hi Guys,
I have been speaking to Tim the developer about how to implement this enhancement and we have some ideas and questions we wish to have comments on.
1. The use of open office or word templates for the combined reminder format means we are restricted in the way the multiple reminders are formatted in that the program must create the format text as special merge fields and then they can be placed anywhwer in the template document. As Matt eluded in one of the posts, if we utilise a jasper reports template (the ones we use for Invoices, Statements etc) rather than an Open office or Word template we have the ability to utilse any of the passed reminder information and modify the display format to suit the practice. The only issue is to initially create the template we need to utilise IReport report designer rather than the familar word processor. Typically only implementers or experienced users utilise this tool. Are thoughts are that the flexibility of using jasper reporst woudl outweight the initial imposte of having to design the template. We also thought the templaet woudl be rarely changed so the imposte woudl only be during the initial setup period. Would people be happy with this approach ?
2. We expect the Reminder Workspace to look and behave the same and only during the Send All process will the grouped reminder process come into play. Prior to doing the processing all the reminders for reminder types that can be grouped where there are more than 1 reminder for a customer will be gathered and merged using the supplied group template. All other reminders will be processed as is. The summary screen will detail how many grouped reminders have been processed by post or email. The reminder update process will remain unchanged.
3. Do we need to have the option of group By patient as well as group by Customer with two different templates ?
4. Do we want to include the option of exporting the reminder data into a spreadsheet format so it can be used in other applications. We thought an Export button would be sufficient here and include the customer, patient and reminder information as columns and each reminder displayed in the workspace as rows. This way you can filter the reminders you wish to process this way using the workspace filters. ?
Once we have sufficient feedback on these we can review the JIRA and then get Tim to estimate time and cost to develop.
Cheers
Tony
Re: Grouped Reminders
Matt C
On 2 Mar 2009 02:51:20 -0000, tony@openvpms.org wrote: > Hi Guys, > > I have been speaking to Tim the developer about how to implement this > enhancement and we have some ideas and questions we wish to have comments > on. > > 1. The use of open office or word templates for the combined reminder > format means we are restricted in the way the multiple reminders are > formatted in that the program must create the format text as special merge > fields and then they can be placed anywhwer in the template document. As > Matt eluded in one of the posts, if we utilise a jasper reports template > (the ones we use for Invoices, Statements etc) rather than an Open office > or Word template we have the ability to utilse any of the passed reminder > information and modify the display format to suit the practice. The > only issue is to initially create the template we need to utilise IReport > report designer rather than the familar word processor. Typically only > implementers or experienced users utilise this tool. Are thoughts are > that the flexibility of using jasper reporst woudl outweight the initial > imposte of having to design the template. We also thought the templaet > woudl be rarely changed so the imposte woudl only be during the initial > setup period. Would people be happy with this approach ? > 2. We expect the Reminder Workspace to look and behave the same and only > during the Send All process will the grouped reminder process come into > play. Prior to doing the processing all the reminders for reminder types > that can be grouped where there are more than 1 reminder for a customer > will be gathered and merged using the supplied group template. All other > reminders will be processed as is. The summary screen will detail how > many grouped reminders have been processed by post or email. The > reminder update process will remain unchanged. > 3. Do we need to have the option of group By patient as well as group by > Customer with two different templates ? > 4. Do we want to include the option of exporting the reminder data into a > spreadsheet format so it can be used in other applications. We thought an > Export button would be sufficient here and include the customer, patient > and reminder information as columns and each reminder displayed in the > workspace as rows. This way you can filter the reminders you wish to > process this way using the workspace filters. ? > > Once we have sufficient feedback on these we can review the JIRA and then > get Tim to estimate time and cost to develop. > > Cheers > Tony > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/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/mailman/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Grouped Reminders
Sandra @ Bellarine
1. Would each individual clinic need ireport report designer skills for the initial setup of the template or is this done as part of the development and then provided to the clinics when it's released.
2. Sounds Good!
3. We do not require group by patient
4. This would not be a priority where the grouping of the reminders is. I don't know in what scenario I'd use this spreadsheet.
Sandra.
Re: Grouped Reminders
1. The project would provide one or maybe more sample customer reminder report template but it would then be up to the community via the shared resources group or individual practices to change to suit their own needs. I.e different size/format paper. Different headers/footers, logo's etc Expect this is typically a once off or very occasional event so could be done by an implementer or with help from community if no in-house skills.
4. Spreadsheet could be used to generate address labels using an external application etc as per Nick's request.
Cheers Tony
On 3/03/09 9:24 AM, "sandra@bellvet.com.au" :
> Sandra @ Bellarine > 1. Would each individual clinic need ireport report designer skills for the > initial setup of the template or is this done as part of the development and > then provided to the clinics when it's released. > 2. Sounds Good! > 3. We do not require group by patient > 4. This would not be a priority where the grouping of the reminders is. I > don't know in what scenario I'd use this spreadsheet. > Sandra. > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/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/mailman/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: Grouped Reminders
M 0408 811 883
F (08) 6311 7431
E gerrie@essentia-consulting.com
Re: Grouped Reminders
Grouping Reminders
Sandra @ Bellarine
Sounds Great Tony!
Sandra.
Quick update on the request for grouped reminders
Hi everyone,
Seems almost everyone has commented on the questions by Tony. Here is a compiled summary of the specification as it stands. A simple OK from the key contributors will be enough to send to developers for next round of analysis.
Please note that based on varying usefulness to those users replying, I have made option 6 & 7 optional pending discussion within the active community with respect to what costs they may add to the development process.
I am sure Tony and Tim will have other questions.
Matt C
1. Reminders are grouped by customer.
2. The reminder template will contain a list of all the patients with an active owner-patient relationship which have a due reminder.
3. This grouped reminder type will use its own single template
4. To facilitate staged reminders (eg. 1st, 2nd, 3rd reminders)
- If a reminder type has existing templates for subsequent reminders, then those reminders for those patients will be included in the grouped reminder list.
5. Group By Patient will not be included in this specification.
Optionals:
6. A seperate costing will be requested for exporting the reminder data into a spreadsheet format so it can be used in other applications.
7. A seperate costing will be requested for splitting the updating vs posting (email/other) tasks of a reminder run.
- To add a button "PROCESS/SEND" to the reminder workspace that "processes" or distrbutes reminders.
- To add a button "UPDATE" that updates the current reminder set in the workspace.
- A warning confirmation would be required on this button to emphasise that once updated, the same selection criteria will not be able to be used to Send those reminders and that PROCESS/SEND should always have been completed before pressing it.
- UPDATE ideally should not be able to be run by a different user when a PROCESS/SEND is running.
Last chance to comment before grouped reminder spec gets sent
Hi everyone,
Last chance to comment before grouped reminder spec gets sent back to the developers for costing. I will be sending on Tuesday 9th Mar.
After that, suggestions will be duly noted but not neccesarily included in this round of impending development.
Matt C
Reminder Update process
Hi matt,
I think Tim and I are pretty happy with what is required in regard grouped reminders now and we can update the JIRA to reflect the changes required and provide an estimated time and cost to develop.
In regards No 7 we are happy to cost but have discussed some alternative ideas which we think will solve some of the problems with just providing an update button and processing errors in general.
Currently we update in bulk so we have an option to repeat the generation if problems occurs. The primary example is printer errors where the printer chews up a number of pages or stops altogether and on power cycle to fix looses a number of print jobs. Even then the current approach (reprint the lot) is a bit brute force as typically you only loose a few printouts in this scenario. If a processing error occurs (bad template, bad email, email server connection problem etc) we have to start from scratchwhich is bad.
New idea is to update as we process and if we get an error we will display and give option to stop or continue. Any reminders that get erors will not be updated so they remain in the reminder list and can be easily reprocessed once the error is fixed. The summary screen that appears at the end of the process will still give an option to reprint the post and list reminders if required but there will be no update reminders button any more.
To facilitate reprinting of specifc reminders our idea is to add a Re-Send option to the Patients reminder workspace. It will allow you to reprocess a specific reminder and even reminder number. i.e if a reminder has a count of 2 (two reminders sent) you can reprint/re-email the first or second reminder.
We think these options take away the complications realted to running remidners twice ro updaets twice or concurrently and will make the reminder generation process easier and more robust.
Thoughts ?
Cheers
Tony
The Grouped Reminders Specificiation
Hi Tony and Sandra,
Sorry, been a bit busy.
Thanks for taking the ball and passing the specification on Tony.
With respect to your comments re point 7. Scrap point 7 from the list and replace with your scheme of just not updating those that generate an error with option to halt execution based on errors.
Cheers,
Matt
The List:
1. Reminders are grouped by customer.
2. The reminder template will contain a list of all the patients with an active owner-patient relationship which have a due reminder.
3. This grouped reminder type will use its own single template
4. To facilitate staged reminders (eg. 1st, 2nd, 3rd reminders)
- If a reminder type has existing templates for subsequent reminders, then those reminders for those patients will be included in the grouped reminder list.
5. Group By Patient will not be included in this specification.
Optionals:
6. A seperate costing will be requested for exporting the reminder data into a spreadsheet format so it can be used in other applications.
Grouped Reminders
Sandra @ Bellarine
Hi Matt,
Sorry, busy week only saw your last two posts now.
I am very happy with points 1 to 6 and I think point 7 is a great idea!
I wonder if it would be much more work for the developers to record somewhere a record of the reminder run dates that have been processed.
At the moment I keep a record of what date ranges I process in a book. eg: 1st-8th Feb, 9th-16th Feb, 17th-24th Feb, etc. It would be a pain if I lost the book and a good safety net to have these previous runs recorded somewhere on the system. I totally understand if it's inappropriate at this late stage to add further requests, but I thought with the work being proposed it might be easily incorporated, I say this with no knowledge of the developing process at all but I thought not to put forward this suggestion when they're about to do some fairy major work in this area would be silly.
Sandra.
Re: Grouped Reminders
I am happy to discuss how best to implement recording of previous reminder runs. I do think it would be good to move the development process forward on the current set of requirements while this is discussed and then incorporate it in a later release if the community sees it as a necessary feature.
Hope to complete JIRA's for current requirements today ready for Tim to estimate time and cost.
Cheers Tony
On 9/03/09 12:50 PM, "Sandra" :
> Sandra @ Bellarine > Hi Matt, > Sorry, busy week only saw your last two posts now. > I am very happy with points 1 to 6 and I think point 7 is a great idea! > I wonder if it would be much more work for the developers to record somewhere > a record of the reminder run dates that have been processed. > At the moment I keep a record of what date ranges I process in a book. eg: > 1st-8th Feb, 9th-16th Feb, 17th-24th Feb, etc. It would be a pain if I lost > the book and a good safety net to have these previous runs recorded somewhere > on the system. I totally understand if it's inappropriate at this late stage > to add further requests, but I thought with the work being proposed it might > be easily incorporated, I say this with no knowledge of the developing process > at all but I thought not to put forward this suggestion when they're about to > do some fairy major work in this area would be silly. > Sandra. > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/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/mailman/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu
Reminder dates
Sandra @ Bellarine
Ok Tony, that's fine. The priority is definitely to get them grouped.
Just thought I'd mention it now rather than throw the idea in later and you go all red in the face on me - because that's scary.
I'll add it on the forums another time.
Sandra.
Grouped Reminders
Sandra @ Bellarine
In reply to Tony's last post above -we must have been adding to this topic at the same time.
I like the idea.
I think being able to easily reprint 1st and subsequent reminders from the patient reminder workspace is fantastic. I also like the idea of the reminders updating as they are processed and being notified on screen of an error with a particular reminder and that particular reminder not updating. It's also a good idea for that reminder that caused the error to remain on the list at the end so we have a record.
Sandra.
Grouped Reminders - JIRA's
The following JIRA's have been updated , added to reflect the discussed specification for the Group Reminders, Improved Reminder Update and Individual patient reminder printing/reprinting features.
Grouped Reminders - https://openvpms.atlassian.net/browse/OVPMS-862
Modified Reminder Update - https://openvpms.atlassian.net/browse/OVPMS-870
Individual printing/reprinting of reminders - https://openvpms.atlassian.net/browse/OVPMS-871
Tim will now provide estimations of the time involved to develp each of these and we can then decide on priorities and funding.
Cheers
Tony
The grouped reminder costing is in! The sticky bit...
Hi everyone,
The developers expect that to develop ;
A) Grouped Reminders - //openvpms.atlassian.net/browse/OVPMS-862" href="https://openvpms.atlassian.net/browse/OVPMS-862">https://openvpms.atlassian.net/browse/OVPMS-862
Will require 40 hours of development.
This equates to $3000.
B) Modified Reminder Update - //openvpms.atlassian.net/browse/OVPMS-870" href="https://openvpms.atlassian.net/browse/OVPMS-870">https://openvpms.atlassian.net/browse/OVPMS-870
This is the ability to to handle errors/interruptions during the reminder process.
Will require 10 hours of development.
This equates to $750.
Development will not commence until we have agreements from interested parties sufficient to cover these costs.
If you are interested in supporting this features, please contact me directly at mpcosta@boroniavet.com.au
It is intended that the costs will be divided equally, but if you need to place a limit on your contribution please advise me in you email.
Also please advise if you are willing to contribute both to A & B or only one.
I will keep the community advised.
Cheers,
Matt C
An appendum to the Grouped Reminders costing
Tony has raised the point that including the ability to reprint reminders from within the Patient Reminders tab within Medical Records is an important part of the update.
This adds a third point,
C) Reprinting Reminders - https://openvpms.atlassian.net/browse/OVPMS-871
This is the ability to to allow printing and re-printing of reminders from Patient Reminders workspace
Will require 10 hours of development.
This equates to $750.
Cheers,
Matt C
Grouped Reminders progress report
Hi everyone,
Well it has been just over a week and we have had some generous contributors contact me. More would be welcome. Any qty would be helpful and allow us to get development underway.
Matt C
You can contact me directly on mpcosta[at]boroniavet.com[dot]au
Grouped Reminders development has been confirmed
Hi everyone,
Committments for funding this development have been received and the green light given to the developers.
Congratulations for all those who contributed. Your hard work will benefit everyone.
I will keep the user community informed.
Matt C
Grouped Reminders
Sandra @ Bellarine
Can't wait, thanks Matt!
Group Reminders development and testing completed
Just a note to say we have completed development and in house and beta testing of the new reminder system.
Thanks to Tim for doing a great job on the development and completing it on budget. Also to Sandra and the team at Bellarine for participating in testing. Bellarine are now using the new reminder system in production and I am sure will give the community plenty of feedback on how this new feature is working.
Thanks to everyone who funded this project for the benefit of the whole community.
Cheers
Tony
Reminders
Sandra @ Bellarine
Hi Everyone,
I have just processed my second lot of reminders with the new system and it's great! It saves us money, time & headaches from not having to sort through and discard so many cards. We can now reprint reminders very easily and have no errors during processing. Thanks to Tony & Tim for all their hard work!
Sandra.
Canine vs feline vaccination reminders
Can canine reminders be printed seperately to feline reminders ?
I gather annual health check & vac reminders can be printed directly to reminder cards, and from what this threads says, the problem of multiple reminders being printed has now been addressed. My question is can canine reminders be printed seperately to feline reminders ? We have quality species specific reminders rather than a generic reminder.
Re: Canine vs feline vaccination reminders
Matt C
On Mon, 10 Aug 2009 03:07:45 +0000 (UTC), turravet@tech2u.com.au wrote: > Can canine reminders be printed seperately to feline reminders ? > I gather annual health check & vac reminders can be printed directly to > reminder cards, and from what this threads says, the problem of multiple > reminders being printed has now been addressed. My question is can canine > reminders be printed seperately to feline reminders ? We have quality > species specific reminders rather than a generic reminder. > _______________________________________________ > 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: Reminders-All reminders for a client printing on one ...
Would appreciate if anyone has had this problem and can solve it. Since upgrading to Open 2.2.4 our reminders are now grouping but no longer print with the correct address but now say null in the name and address fields. Searching the forum I see that the grouping feature has been available for some time but had not been set up on our version until the last update. Now when we do a reminder run for clients who want a printed reminder the grouped reminder prints as null but the single reminder prints fine. I know the two reminders use different documents to generate the reminder. We do not have Jaspersoft installed on our server. I assume I need to download Jaspersoft Studio (?) and then edit the reminder document. Easiest will be to copy the correct fill in field from the reminder file that is working to the file that is not working.
Is this the correct approach ?
Stephen WPHVet
Re: Reminders-All reminders for a client printing on one ...
Hi Stephen,
I expect this is an issue with the Letterhead AddressBlock relating to the upgrade and some expression changes. I expect loading a new template for this will solve the null/null issue you are seeing.
We can do this for you if that is OK and then you can test again ?
Cheers
Tony
Re: Reminders-All reminders for a client printing on one ...
Thanks Tony. We will test on our next print reminder run on Friday. Will let you know if there are any problems.