Details
Description
Overview
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.
Options (costing is requested for these 2 options):
Option 1. The patient group is returned as a single formatted string from a single function including the details below.
Option 2. The patient group returns reminder and patient details as individual fields that can be used to populate a subreport, much the same as that technique currently used in OpenVPMS invoices for invoice items.
Details of data returned
ie. [Reminder Type] (Reminder No. [Reminder No] ): [Patient Name] Is due for [Product] on the [Reminder Due Date]\n
eg.
Canine Annual Vaccination (Reminder No. 1): Peppy Is due for a C4 on the 12/02/2009
Canine Annual Heartworm Prevention (Reminder No. 1): Peppy Is due for a Proheart on the 12/02/2009
Feline Annual Vaccination (Reminder No. 3): Jimmy Is due for a F3 on the 15/12/2008
The requirements above have been modified to allow greater flexibility for the format of the grouped reminder by utilising a jasperreport rather than a open office document for the template. This will allow each grouped reminder to displayed in any format according to reminder count and type information.
The formal development specification is as follows:
1. Add a new node to entity.reminderType to specify if the reminder type participates in grouped reminders. The default value is false.
2. Add a new entity.documentTemplate type called "Grouped Reminder". The grouped Reminder template will be a jasperreport (jrxml) format and only one will be allowed.
3. The reminder workspace will have the same look and feel.
4. When generating reminders the system will first sort all reminders by customer and within each customer find all reminders whose reminder type can participate in group reminders and whose reminder action is Post or Email. If there is more than one reminder the system will generate a grouped reminder using the group reminder template and dispatch to printer or email as per a single reminder.
5. All the reminder objects will be passed as an object set datasource to the jasper report template.
6. If there is only one reminder for the customer the standard reminder type template will be used.
7. Reminders with a list action will still list as per the current system.