Duplicate of https://openvpms.org/project/reminder-generation-enhancements

When sending reminders, customer contact preferences and rules determine how reminders are sent. The rules that determine how reminders are sent are inflexible, making customisation difficult. 

This project will change the Reminder Type templates to allow:

• up to 5 rules to be specified to indicate how reminders should be processed. Rules will be evaluated in order, and the first rule that is satisfied determines how the reminder is processed.
• multiple reminders to be sent (e.g. send both an email and an SMS)

Each rule will contain the following options, one or more of which may be selected:

• Contact - use the customer's reminder contact or if none defined, use their preferred contact, or if none defined use the first available contat
• Post - using the customer's Location contact, print and the reminder for posting to the customer
• Email - using the customer's Email contact, email the reminder to the customer
• SMS - using the customer's Phone contact with Allow SMS enabled, send the reminder via SMS
• List - the reminder will be listed on the Patient Reminders Report
• Export - the reminder will be included in the exported CSV file

If no rule is satisfied, then the Reminder will be processed as per List.

E.g. A Reminder Type might specify 2 templates:

• Template 1, Reminder Count = 0
  • Rule 1: SMS
  • Rule 2: Email, Post
• Template 2, Reminder Count = 1
  • Rule 1: Post

In the above, the first reminder will be sent:

• via SMS, if the customer has a phone contact with Allow SMS set; else
• via email, if the customer has an email contact and/or via post, if the customer has a location contact; else
• it will be Listed

The second reminder will be sent:

• via Post, if the customer has a location contact; else
• it will be Listed

This project will add support for insurance claims.

It will enable the user to:

• create a new Insurance Claim for a patient; and
• add some/all invoice items to the claim; and
• automatically total those items being claimed
• print or email the claim

NOTE: this project has been rolled into http://www.openvpms.org/project/patient-insurance and will soon be removed

This project has been replaced by: http://www.openvpms.org/project/charge-and-estimate-minimum-quantities

This project will add a minimum quantity to charges to prevent undercharging. When a minimum quantity is present, entering a Quantity less than this will not be permitted.

This facility will apply to:

• Customer Invoices
• Counter Sales
• Customer Credits
• Estimates

For Estimates neither the Low nor High Qty fields may be less than the minimum quantity.

Duplicate of http://www.openvpms.org/project/customer-communications-log

NOTE: this project has been superseded by the Reminder Generation Enhancements project

Jira : http://jira.openvpms.org/jira/browse/OVPMS-1100

Add ability to have multiple grouped reminder templates, one per each reminder group.

This is an extension of the exsiting grouped reminder capability which only allows one template for the application.

Forum: None

Jira : https://openvpms.atlassian.net/browse/OVPMS-1100

Add ability to have multiple grouped reminder templates, one per each reminder group.

This is an extension of the exsiting grouped reminder capability which only allows one template for the application.

THIS PROJECT HAS BEEN REPLACED BY the USER INTERFACE IDEAS ongoing project

Hi everyone,
When we originally talked about the design of OpenVPMS we had in mind the cut back efficiency of text based Netvet with the richness of a mouse based, graphical interface. We said we wanted the best of both worlds. The netvet users amongst us were getting a modern product that did heaps more but we were going to sacrifice some speed and efficiency for it.

I think we have got a very speedy solution that indeed has added a rich graphical interface with good efficiency. But OpenVPMS never intended to be just "Good".

So I am hoping to collate a set of little workflow tweaks that might speed up some common processes. Ideally I want to cut the number of clicks and where possible make a click into a keystroke.

On their own that don't justify a project but together they could really speed up our product.

I'm not after major work flow changes, just little things in the current implementation that could be cutback or made more efficient.

I'll start the ball rolling but for those interested in reducing the clicks, start counting the clicks and think of ways to cut them out!
"Focus" just refers to where the cursor goes.

Current List

1. Having the contents of a text box selected, so you can overwrite straight away rather then selecting or deleting as a default behaviour for any dialog where the focus goes to a text box

eg. When making a new appointment, having the contents of the Customer box selected so you can overwrite straight away rather then selecting or deleting. (Infact ).

2. When adding an appointment, if the user uses the combination of Patient and Customer to find a Customer, both get entered in the New appointment dialog rather then having to enter the patient again.

3. Having the "Search" buttons (the ones with binoculars) taken out of the tab order.

4. In Schedule Views and Worklist Views, have a default Highlight option to prevent having to select it each time you log-in/out.

5. New Invoice Box where it says 'select the type of invoice you want to create', set a default.

eg: Automatically highlight invoice so an ENTER would accept it.

6.  Under Administration when you go to  Administration -> Templates -> Select, automatically set focus to the the text box.