The following is a list of new features and improvements in the 2.0 release. You should also check Known Issues and the Implementation Checklist.
Major Features in this release include:
OpenVPMS now includes an online booking API, kindly donated by Australian Animal Hospitals.
This has been integrated into MyHealth1st's PetYeti Find A Vet portal.
See Online Bookings for more details.
Patient reminders have been enhanced to:
The Smart Flow Sheet integration has been improved to:
NOTE: Users of the Smart Flow Sheet integration in OpenVPMS 1.9 need to co-ordinate with Smart Flow Sheet support prior upgrading to OpenVPMS 2.0.
This is because any Smart Flow Sheet account created for OpenVPMS 1.9 needs to be reconfigured to work with OpenVPMS 2.0.
In addition, Smart Flow Sheet support should be notified when synchronising products for the first time as it affects existing billing parameters and treatment templates.
OpenVPMS can now:
Practices with multiple locations can now limit clinician, work list and printer selection to those available at the current practice location.
For clinicians and work lists, an All Locations option is provided to enable selection outside of the current practice location.
For printers, the available printers can be listed on the Practice Location.
Patient alerts can now be automatically created when a product is charged, by adding Patient Alert Types to Medication, Merchandise, or Service products.
SMS messages longer than 160 characters can now be sent, by setting the Maximum Parts field of the SMS Configuration. This determines the maximum number of parts that may be sent in a single message. These are sent as multiple SMS by the SMS provider, but are concatenated together so that the recipient sees a single message.
See:
Reports may now be scheduled to run automatically, with the output written to a directory, emailed and/or printed.
See Scheduled Report for more details.
The Patient Medical Records Summary and Problems now include a Search field. This performs a case-insensitive search on patient records for the input text. The following fields are searched:
The Practice now has a Use Logged In Clinician option that determines how Clinician fields are populated. When:
This is the preferred choice.
Only use this if workstations are shared. This reflects the existing behaviour.
To save time and reduce errors when creating prescriptions, support has been added to create new prescriptions from existing patient Medication records via a New Prescription button.
If a medication has dispensing instructions, these will be displayed when editing prescriptions.
The Visit reason can now be specified when using Add Visit & Note to add a new Visit and Note to the patient history.
The Attach button of the email Write window now supports selecting multiple attachments at a time.
Macros can now include {__} tokens that indicate text that needs to be replaced by the user. Pressing:
This allows users to progressively fill in text. E.g. a macro could generate:
Reason: {__} History: {__} Current medications: {__} What Preventative health cover is being used and do you need to purchase any today? {__} Vaccination: {__} Worming: {__} Flea control: {__} Heartworm Prevention: {__} Examine: {__} Mentation: {__} Body condition score: {__} MM: {__} CRT: {__} HR: {__} RR: {__} LN: {__} Temperature: {__}
NOTE: this facility is not supported in the Mail editor.
The Practice now has a Restrict Ordering option. When enabled, supplier orders must be finalised by a clinician.
This can be used in jurisdictions that require restricted drug ordering to be limited to clinicans.
An address format may now used to specify how addresses are displayed in reports.
The party:getBillingAddress(), party:getCorrespondenceAddress() and party:getPracticeAddress() functions each now support formatting addresses on single or multiple lines.
JXPath extension functions have been added to improve reporting:
The following is a checklist for existing users upgrading to the 2.0 release and is aimed at both the person doing the upgrade and the administrators responsible for systems operations.
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 (such as the Online Booking) are not included here.
This page documents any known issues that may cause problems. Note that it does not list problems reported against earlier releases of OpenVPMS that are not yet resolved, but rather issues that may cause you problems with this release.
If you use Studio 6.2.0 you may find that the backspace key acts a 'delete-on-right' rather than 'delete-on-left'.
You need to remap the key. See http://community.jaspersoft.com/jaspersoft-studio/issues/6451 comment #5
If you create an Email Template using an Open Office odt document as its content, and that document contains two adjacent User Fields separated by one space, eg
(here shown after using Ctrl-F9 to reveal the field content)
Then when this shows in the email you may see "Dear MrBloggs" rather than the expected "Dear Mr Bloggs".
The work-around is either to replace the space by a non-breaking space (entered using Ctrl-Shift-space on Windows or Option-Space on a Mac) or use two spaces instead of one. [In the second case, normal HTML processing will replace consecutive spaces by a single space.]
If you use the External Edit facility to edit an Open Office document, AND you are using Java 8 update 112 or later then a Java security check window appears each time you use External Edit and its 'do not show this again' checkbox does not work. See also OVPMS-1889