Implementation Checklist

The following is a checklist for existing users upgrading to the 1.8 release.  It provides a list of things that you may need to do in order to take advantages of the new features in this release.  They are in no particular order. Note that the totally new features (like the HL7 stuff) are not included here.

  • If you use estimates, then you should review your templates to set high/low quantities.
  • If you want to include staff on emails, then you need to add email contacts for each staff member.
  • If you want to SMS customers in another country, ensure that their contact phone number includes the + prefix and country code.
  • Review your product templates to see if you can take advantage of the ability of templates to include other templates.
  • Review your product templates to see if you can make use of the weight-based inclusion facility.
  • Review your product templates to see if you can make use of the zero price facility. Note that if you do not want zero-priced items to appear on the customer’s invoice, then you will need to adjust your invoice etc document templates to suppress line items that have a zero price.
  • If you wish invoices etc to show product templates with an aggregated amount rather than the individual products that the template included, then you need to set the Print Aggregate flag on those templates for which you want this to occur. If your invoices etc order products via their Product Type's Invoice Order field, then you also need to set the Product Type for those templates where you set the Print Aggregate flag. Your invoice etc (ie invoice, credit, counter sale and estimate) document templates will also need to be updated. The templates in the release package support aggregation but not the Invoice Order field.
  • If you have a setup which has multiple practice locations, with customers normally associated with a specific location, then consider setting the Practice Location field for those customers. This will allow you to generate Reminders and Statements for customers selected via their Practice Location. You could also use the customer's Practice Location to allow the use of location specific information in invoices etc.  If so, you will need to make changes to your invoice etc document templates to take advantage of this facility.
  • If you want to take advantage of the transaction hide facility, you will need to adjust your statement document template(s).
  • If you want to use location based pricing, then you need to set up the Pricing Groups - see here.  If you already using location based pricing by selling different products at different locations (eg xxxxx for normal customers, and HC-xxxxx for house call customers) then you will need to also deactivate the HC- versions of each product.
  • If you want to use the At-Cost discount facility to allow you to sell to staff at a Cost-Plus rate, then you will need to set up the At-Cost discount(s) – and almost certainly adjust the maximum discounts set for the products. See here.
  • If you want to SMS reminders, then all document templates used for reminders need to have their SMS field set.
  • If you want to personalise or add identifiers to generated document names, then you need to edit the document templates to have a File Name Format.
  • If you currently use a cron job or the windows task scheduler to regularly run the docloader utility to import documents, then you should switch to using the OpenVPMS scheduled version (because it is more efficient).
  • If you are going to use the new Customer Notes facility and you wish these notes to appear on your printed invoices and estimates, then you will need to amend their document templates.  Note that the invoice templates packaged with the release (in the <OpenVPMS-Home>\reports\Customer\Invoice folders include Customer Note printing.
  • If you use fine grained authorities to control who can do what, you will need to check the following:
  1. users who have to manage appointments need to be able to create/remove/save the act.customerAppointmentSeries archetype as well as the act.customerAppointment archetype
  2. users who previously needed the Entity Relationships Create/Remove/Save authorities will also need Entity Links Create/Remove/Save authorites for the archetypes entityLink.*
  3. users who have to manage HL7 messages need to be given the HL7 Message Act Create/Remove/Save authorities.

The database migration script will do some of the work required, in that it will create or modify the authorities, but you will need to check that the Roles that you use have the required authorities.

Syndicate content