This project will add a Product Type filter to the patient history display. This can be used to quickly display medication and charges for one or more product types. e.g. it could be used to show all vaccinations that a patient has received.

The filter will be added to:

• Patients - Medical Records - Summary
• Visit Editor - Summary

It will:

• enable Medication and Customer Invoice Item records to be displayed based on their Product Type
• allow multiple Product Types to be selected, via check boxes
• default to All product types

Exclusions

The filter will not be available in the patient Problem history displays i.e. in:

• Patients - Medical Records - Problems
• Visit Editor - Problems

If your practice operates at multiple sites, you will have clinicians, worklists and printers relevant only to specific sites.

In the current system:

1. when using the clinician selection to select the clinician for an appointment, task or visit,  all clinicians are available - even those who cannot access the practice location because it is not one of the locations set on their Administration|Users record.
2. when transferring a task from one worklist to another, all the practice's worklists are available - not just those in the worklist view(s) for the current practice location.
3. when selecting a printer, all printers are available - though in a multi-site practice it makes sense to select just from those printers located athe the currently set practice location.

This project will add an All Locations check box to the Clinician, Work List and printer browsers. By default this will be unchecked, excluding repectively clinicians who do not have access to the current practice location, work lists not linked to the current practice location via a Work List View, and printers not at the current location.

To select a clinician, work list or printer from the full set, you would therefore have to click on the binoculars button, tick All Locations, and select it from the list.

Note that having selected an 'out-of-location' clinician, the clinician would be used automatically as is the case currently.

Note also that the selection of the Customer's Preferred Vet (controlled via Administration|Lookups|Customer Vet) will be unaffected by this change.

To support the printer selection, a Printers tab will be added to the practice location, and this will be used to specify the printers available at this location. If this tab is empty, then all printers will be available at the location.

JIRA: OVPMS-1910

Summary

This project will allow patient alerts to be automatically created, when a product is charged.

Background

The sale of certain products implies that the patient has some condition – for example there are various special diet foods for patients with kidney, liver, etc problems.

One also may want to indicate that a patient has had some procedure performed.

We run a manual system in which certain products are given a category/product group that indicates that it this product is invoiced then the patient should be given a corresponding alert.
We have a report that looks for sales of certain products and checks that the patient has the associated alert set - if not the staff need to manually set this alert.

This project will automate this process. That is, one will be able to specify that if a given product is sold then the associated alert is set for the patient.

Archetype Changes

Patient Alert Type

The existing Patient Alert Type lookup lookup.patientAlertType will be replaced with an entity.patientAlertType, and extended to add the following fields:

• Duration - if specified, this sets the duration for the alert. If not set, then the alert is  open ended
• Interactive - check this box if you want confirmation when this type of alert is generated as a result of selling a product to which the alert is attached
• Extend - this flag determines what happens if a new sale results in the creation of an alert that is already set for the patient. 
  If extend is:
  • not checked, any existing alert will be set to Completed and a new In Progress alert created.
  • checked, then the existing alert is updated to reflect the product sold, and has its end date adjusted to reflect the alert's duration setting.
    One can thus choose between leaving a trail of alerts set via previous sales, and just having one active alert to reflect one or more prior sales.
• Reason - you can provide a default reason for the alert (such as 'Product Sale')

Hence when a product that has associated patient alert(s) is sold, the process is just like that for reminders. If the Interactive flag is set for the alert, then the alert details are presented and can be modified.
The alert's:

• End Date is set from the Duration (blank if no duration has been set, or the current date plus the duration),
• Reason is set to that (if any) on the Patient Alert Type
• Status is set to In Progress
• Priority is set from the Patient Alert Type,
• Start Date is set to the current date

Products

The existing product.medication, product.merchandise and product.service  archetypes will have a Patient Alerts node added to allow multiple patient alerts to be specified.

Patient Alert

The existing act.patientAlert archetype will be extended to add a Product node.

Invoice Item

The existing act.customerAccountInvoiceItem will be extended to link to any alerts created when a product was invoiced. This will allow the alerts to be removed if the product is changed, or the item removed.

Limitations

• If an alert sets an existing alert Completed, but is then subsequently deleted (either via manual deletion, changing the product on the invoice item, or removing the invoice item), the existing alert is not set In Progress.
• If invoicing a product extends an existing alert, the alert will be deleted if the invoice item is deleted or the product is changed 

Reporting

A Patient Alert Check report will be provided as a standard report to allow sales to be checked to see if the patient has the appropriate alert(s) set.

Migration

Migration will be required to:

• convert lookup.patientAlertType to entity.patientAlertType
• replace the existing alertType node of act.patientAlert with a participation relationship

JIRA: OVPMS-1885

This project will enhance the existing Smart Flow Sheet integration to:

• charge treatments given to a patient in Smart Flow Sheet
• synchronise products and clinicians with Smart Flow Sheet
• add notes entered in Smart Flow Sheet to the corresponding patient's history
• add support to specify a department on Check-In
• add support to associate a default department with a work list
• add support to import anaesthetic sheets
• automatically discharge patients from Smart Flow Sheet on Check-Out
• automatically import documents on discharge

Billing

When a treatment is entered into Smart Flow Sheet, a corresponding Customer Pharmacy Order will be automatically created in OpenVPMS. If the order is complete, this will be charged automatically during the normal Check-In/Consult/Check-Out workflows.

If the order is incomplete (e.g the product doesn't correpond to one in OpenVPMS, the units are different, or the quantity is unset), an error will be displayed during invoicing, as is the case with the existing Pharmacy Order support.

Notes

When a note is entered into Smart Flow Sheet, these will be automatically added to the patient's history.

Product Synchronisation

Where a practice location is configured to use Smart Flow Sheet, a new Synchronise with Smart Flow Sheet button will be added to the Products - Information workspace.

This will add or update all medication, merchandise and service products that are available at the current practice location to Smart Flow Sheet.

If a product is no longer active, it will be deleted from Smart Flow Sheet.

Mapping

Medications in Smart Flow Sheet require concentration, concentration units and concentration volume. These will be source from the medication product's Concentration, Dispensing Units and the Weight Units of the first dose associated with the medication, if any.   

Clinician Synchronisation

Where a practice location is configured to use Smart Flow Sheet, a new Synchronise with Smart Flow Sheet button will be added to the Administration - Users workspace.

This will add or update all clinicians that are available at the current practice location to Smart Flow Sheet.

If a clinician is no longer active, it will be deleted from Smart Flow Sheet.

Departments

Smart Flow Sheet supports departments. This project will:

• allow the user to select from a list of departments on check-in
• default the department to one associated with the work list, if any

Event Mechanism

Smart Flow Sheet provides two mechanisms to send events, web hooks and Azure Service Bus. The former requires the practice to open up a port in the firewall, whereas the latter is polled. This project will use the Azure Service Bus option, as it is more secure and typically requires no additional network configuration.

Anaesthetic sheets

Support will be added to import anaesthetic sheets, along with the existing Flow Sheet, Medical Records, Notes and Billing documents.

Check-Out

At present, patients must be manually discharged from Smart Flow Sheet.

This will be changed so that at the start of check-out, the patient will automatically be be discharged from Smart Flow Sheet.

Document import at discharge

When a patient is discharged from Smart Flow Sheet, Flow Sheet, Medical Records, Notes, Anaesthic and Billing documents will be automatically imported to the patient history. This replaces the manual import currently performed as part of the Check-Out workflow.

If a document has been previously imported, it will be versioned.

Outstanding Issues

• SFS doesn't support display names for units, so if the code is submitted (e.g. GRAMS) this is what will be displayed in the UI. The alternative is to submit the display name, and then map this back to the appropriate lookup when performing charging.
• Need to determine if billing can be disabled in SFS if Cubex is connected

JIRA: OVPMS-1871

This project will extend the Templates support in Schedules and Work Lists to include a Print check-box. This will determine which documents will be pre-selected for printing:

• at check-in
• when using Transfer in Workflow - Scheduling to transfer a patient from an appointment to a work-list
• when using Transfer in Workflow - Worklists to transfer a patient from one work-list to another

At present, only a single charge or estimate item may be deleted. This is done by selecting it in the Items table, and pressing the Delete button.

This project will add support to select and delete multiple charge and estimate items by introducing a checkbox column to identify which items to delete.

To delete items, tick the corresponding checkbox and then press Delete.

When a single item is selected for deletion, a prompt will only be displayed if the item has been saved previously:

Are you sure you want to delete the Customer Invoice Item?

When multiple items are selected for deletion, a prompt will always be displayed.

Are you sure you want to delete these 3 Items?

If an item cannot be deleted (e.g. it has a minimum quantity), no item will be deleted.

Multiple pages

If there are multiple pages of items, only those items on the current page will be deleted. Selections will be retained when changing pages.

JIRA: OVPMS-2099

This project will provide a practice-level option to restrict editing of charge or estimate item quantities, so that they don't fall below a set minimum.
This will reduce invoicing errors.

Charge Minimum Quantity

For Invoices, Counter Sales, and Credits, the low quantity of an item generated from an estimate or template will be stored in a new hidden Minimum Quantity field on the item.

The charge quantity will not be permitted to be set below this value. Doing so will trigger a validation error e.g.:

The Quantity cannot be set below the minimum quantity of 1

When a charge item has a non-zero minimum quantity set, a warning will be displayed when deleting it e.g.:

       Carprofen Tablets 20mg has a minimum quantity of 3.
       Are you sure you want to delete it?

Estimate Minimum Quantity

The low quantity of an item generated from a template will be stored in a new hidden Minimum Quantity field on the estimate item.

The estimate item low quantity will not be permitted to be set below this value. Doing so will trigger a validation error:

The Low Quantity cannot be set below the minimum quantity of X

When an estimate item has a non-zero minimum quantity set, a warning will be displayed when deleting it e.g.:

       Desex - Dog < 20kg has a minimum quantity of 1.
       Are you sure you want to delete it?

Invoicing Estimates

When an estimate is invoiced, an estimate item's Low Qty becomes the minimum quantity for the corresponding invoice item.

Changing Products

• changing a Service product with a minimum quantity will not be permitted.
• changing a Medication or Merchandise product with a minimum quantity to another product will be permitted, so long as the new product is of the same type (i.e. Medication/Merchandise). The minimum quantity will be retained. This is to support instances where the preferred product is out of stock.

Configuration

The minimum quantity restriction will be enabled by a new option on the Practice, Minimum Quantities.

By default, it is not selected.

Migration

There will be no migration required for this project.

Existing charges and estimates will have no minimum quantity restriction.

JIRA: OVPMS-1768

To see a medication batch number, the corresponding Medication record must be edited or viewed.

This project will provide an option to display product batch numbers in the patient history in:

• Medical Records - Summary
• Medical Records - Problems
• Visit Editor - Summary

E.g.:

The option will be configured in user preferences.

When charging and estimating, all medication, merchandise products are available for selection, even if there is no stock record for the product at the location. The first use of any product automatically creates the stock record.
Similarly, all services and product templates are available, even if they aren't performed or used at a location.

To support multi-location practices using different products, this project will:

• add a Use Location Products flag to the Practice
  When enabled, any medication or merchandise product that doesn't have a stock record for the location will be excluded from selection during charging and estimating.
• add a Locations field to services and templates
  This is only available if Use Location Products is selected.
  This lists the practice locations that a service or template may be used at. If a service or template lists no locations, it may be used at all practices.
• add a Location option to Product Template Includes
  This is only available if Use Location Products is selected.
  It is evaluated if an included product meets any patient weight range criteria.
  It will have 3 options:
  • Always Include - the default. The product is included regardless of stock availability.
  • Fail if Missing - the template will fail to expand if there is no stock or location relationship, with an error:

The template cannot be expanded: product X is not available at this location.

Note that this does not take into account stock counts

• Skip if Missing - the product will be excluded from the invoice or estimate if there is no stock or location relationship.
   

• add a Locations option to Services and Product Templates
  This allows services and product templates to be excluded at specific locations. Locations need to be explicitly selected for exclusion. E.g.:

  Locations
   

  Available At		Excluded At
  Main Clinic	->	Branch Clinic 2
  Branch Clinic 1	<-	Branch Clinic 3
  		Branch Clinic 4

   

If set, the Use Location Products flag also restricts products when creating:

• Medications
• Reminders
• Patient Forms
• Customer Orders and Returns

The Use Location Products flag is ignored:

• when performing orders and deliveries
• in Products - Information, Stock Management and Batches

JIRA: OVPMS-1787

This project will enhance boarding support.

It will:

• associate an optional Cage Type with a schedule, to classify schedules as being cages/kennels

• provide a cage type view:

  • displays availability by cage type, per day
  • displays overall availability, per day
  • clicking on a cage type shows all schedules for that cage type with their correponding appointments
     
• provide a summary view:
  • displays availability by cage type, per day
• provide options to filter views by:
  • Checkouts
  • Checkins
• in addition to the existing Month, Week and Day options, provide a Fortnight option to view 2 weeks worth of dates. This will be the default
• better support multiple pets per schedule