NOTE: this project requires the "home practice" support provided by the Location-specific reminders project.

Statements are currently processed at the Practice level, which means that printed and emailed statements cannot have Location specific content.

To support Location specific content a Location filter will be added to Reporting|Statements that:

• filters statements based on the selected location; and
• provides a "No Location" option, to process customers that have no "home practice"; and
• supports processing all statements, to support the current behaviour

Practices can then:

• use letterhead according to the selected Practice Location
• examine the customer's home practice within statement templates

When statements are emailed, the Location will be used to select a BILLING email address to reply to. If there is none for the Location, the Practice BILLING email address will be used.

JIRA: OVPMS-1457

Related projects:

• http://www.openvpms.org/project/location-specific-reminders
• http://www.openvpms.org/project/report-logos

Patient documents are currently automatically loaded into OpenVPMS using the docload tool.

This is a command line tool that is typically run using Task Scheduler on Windows or cron on unix.

This project will integrate the docload tool into the web app, using the scheduling feature developed in 1.7.

This will:

• simplify upgrades
• improve performance

Initially, the -byid form of docload will be supported.

The tool will be configured via Administration|Organisation, with a new type named "Job Configuration: Document Loader".

This will provide the following fields:

• name - a name for the configuration. E.g. "Load IDEXX Investigations"
• description - a description of the configuration
• active - if selected, schedules the job to run, otherwise prevents it from running
• source directory - the directory to look for documents
• destination directory - the directory to move loaded documents to
• error directory - the directory to move documents that have failed to load
• regular expression - the regular expression for parsing identifiers from file names
• log - if selected, logs output to the log files
• overwrite - if selected, indicates to overwrite attachments
• runAs  - the user to load documents as
• types - a list of types to load documents to. One or more of act.*Document*, act.patientInvestigation
• notify - if selected, sends a message to the runAs user on completion, indicating the number of loaded documents, the number of errors, and the path of the documents that failed to load. If no documents have loaded and there are no errors, no message is sent.
• scheduling information (e.g. see the ESCI Inbox Reader configuration)

Multiple configurations will be supported. This is useful if documents are coming from different sources

JIRA: OVPMS-1557

This project will add support for tracking product batches.

Product batches are used to identify the:

• batch number
• expiry date
• manufacturer

of a product.

This will enable charge items and patient medication to be linked to a particular batch of a product.

This can be used to:

• auto-fill the expiration date of medication, based on the batch of a product at the current stock location
• record the rabies vaccination details given to a patient
• determine who has been sold a particular product batch being recalled
• report on stock about to expire

Creation

A Product Batch has:

• a batch number (optional)
• an expiry date   (optional)
• a manufacturer (optional)
• a link to the product
• a link to the stock location where the batch resides

It can be created:

• in a new screen, Products|Batches
• by finalising a delivery

Deliveries

Delivery items will need the 3 new fields to support product batch creation

• a batch number
• an expiry date
• a manufacturer

Each will be optional.

If a delivery item has a batch number or expiry date, a Product Batch for the item will be created when the delivery item is finalised.

ESCI will need to be extended to support these fields.

Charging and Dispensing

Charge items and medications will have a new optional dropdown field, "Product Batch" that indicates the batch of a product.

When a product is selected the list of available batches for the product at the stock location will be displayed, ordered on ascending expiry date.

The batch expiring soonest will be selected by default.

If there are no batches available, the Product Batch field will display "None".

When a medication product is being charged, the selected Product Batch will be copied to the dispensing act.

When dispensing, the selection of a Product Batch will:

• set the Expiry Date to that of the batch
• make the Expiry Date field read-only

Batch Managment

A new screen, Product|Batches will be developed to manage batches. This will:

• list available batches for the current stock location
• provide filters on:
  • product name
  • batch number
  • expiry date

By default, only batches that haven't expired will be displayed.

Batch Expiration

Batches whose expiry date has passed will be automatically expired, and will no longer appear for selection in new charges or dispensing acts.

Where a charge item or dispensing act being edited is dated in the past, batches not expired at that date will be available for selection.

This helps cover the case where a rabies shot was incorrectly recorded initially, but the correct batch used has subsequently expired for example.

Stock Control

Product Batches won't directly be linked to stock control.

After transferring stock, Product Batches need to be manually updated to indicate which Batches were included in the transfer by changing their Stock Locations.

JIRA: OVPMS-1484

Reminders are currently processed at the Practice level, which means that reminders cannot have Location specific content.

To support Location specific content:

• a new optional relationship will be added between Customer and Practice Location to denote the customer's "home practice". This will be populated automatically when the customer is created
• a Location filter will be added to Reporting|Reminders that:
  • filters reminders based on the selected location; and
  • provides a "No Location" option, to process customers that have no "home practice"; and
  • supports processing all reminders, to support the current behaviour

Practices can then:

• use letterhead according to the selected Practice Location
• examine the customer's home practice within reminder templates

When reminders are emailed, the Location will be used to select a REMINDER email address to reply to. If there is none for the Location, the Practice REMINDER email address will be used.

JIRA: OVPMS-1456

Related projects:

• http://www.openvpms.org/project/location-specific-statements
• http://www.openvpms.org/project/report-logos

This project will simplify the invoicing of customers for boarding services.

It will:

• automatically charge pets based on the number of nights that a pet has boarded for at Check-Out
• allow multiple pets to be housed in a single kennel/cage, charged at different rates e.g.:
  • Luxury Suite Charge - $65/day
  • Luxury Suite 2nd Pet - $30/day
• support day and overnight boarding rates
• support a late-checkout charge
• prompt to check-out all patients belonging to a customer
• ensure that only a single Visit is created for pets staying for an extended period

This project will include a new product field on patient investigations.

This can be used within investigation templates to order the appropriate test.

When charging, the product field will be set to the product that generated the investigation.

When creating investigations via the Medical Records|Summary, it will be restricted to those products that are linked to the investigation type.

The product field will be read-only if the investigation was created via charging.

JIRA: http://jira.openvpms.org/jira/browse/OVPMS-1383

This project will provide support for user preferences.

Initially it will:

• enable the Home Page to be specified on a per-user basis. This is the screen that is displayed when the user logs in
• enable the scheduling, worklist and patient history display preferences to be specified
• store the My Recent customers and patients, between sessions

User preferences will be accessed by a 'gear' icon, located on the top-right of the screen.

This project will add support to auto-logout users, if their session is inactive for a period of time.

The time period will configurable on the Practice, and default to 30 minutes.

A key requirement of this project is that semi-autonomous tasks, such as statement and reminder generation aren't affected by the auto-logout.

JIRA: OVPMS-1388

When performing till balancing, the current approach is to suspend finalising payments and refunds so that the uncleared till balance isn't changing as the till is being balanced and cleared.

This is fine for practices that close down for the night, but not ideal for those that run 24/7.

This project will introduce a new till balance status "In Progress", used to indicate that a Till Balance is in the process of being cleared.

Once in an "In Progress" state, newly finalised payments and refunds will be added to a new till balance, leaving the "In Progress" till balance unchanged.

In this state, the till balance may have adjustments applied.

A new button "Start Clear" will be added to Reporting|Till Balancing to set an uncleared till balance status to "In Progress".

The "Clear" button may be used to clear both "Uncleared" and "In Progress" balanances.

JIRA: OVPMS-1367

When a microchip or rabies vaccination product is used, the patient must be edited and the corresponding Microchip or Rabies Tag identity added to the patient via its Identities tab.

This project will enable Microchips, Rabies tags and other patient identities to be entered when a corresponding product is charged.

In addition, a button will be added to the Patient Summary to add a microchip for the patient, if one isn't present.

Product Changes

Medication, Merchandise and Service products will be assigned a new field, "Patient Identity" that indicates what type of patient identity should be created when the product is charged. This field will:

• be optional
• list the identity types that a patient can have (Microchip, Pet Tag, and in the US, Rabies Tag; Alias will be excluded)
• allow the selection of one of these types (a single product cannot create both a Microchip and Rabies tag for example) 

Charging Changes

When charged, a product with a Patient Identity will:

1. display an editor for the corresponding identity (Microchip/Pet Tag/Rabies Tag)
2. immediately add the entered identity to the patient

The editor may be skipped. If skipped, no identity is added to the patient.

The editor will be displayed if a product with a Patient Identity is:

• included by a product template
• invoiced from an Estimate

Patient Summary Changes

If a patient doesn't have a microchip, an Add button will be displayed in the patient summary e.g.:

When clicked, this will:

1. display a Microchip editor
2. add the Microchip to the patient when OK is clicked

This is a shortcut for:

1. Going to Patients - Information
2. Editing the patient
3. Clicking the Identities tab
4. Clicking Add to add a new Microchip

Exclusions

If a product with a Patient Identity is charged, and the Identity added to the patient, it will not be removed from the patient if the charge is removed.

This must be done by editing the patient in Patients - Information.

JIRA: OVPMS-1786