This project will add report functions that enable patient medication acts to be queried, in order to report on a patient's vaccinations.

The functions are as follows:

• history:medication(patient)

Returns all medication acts for a patient, ordered on descending start time.

E.g.:

history:medication(openvpms:get(., 'patient.entity'))

• history:medication(patient, productTypeName)

Returns all medication acts for a patient, that have the specified product type name, ordered on descending start time

E.g.:

history:medication(openvpms:get(., 'patient.entity'), 'Vaccinations')

• history:medication(patient, from, to)

Returns all medication acts for a patient between the specified dates, inclusive, ordered on descending start time

E.g.:

history:medication(openvpms:get(., 'patient.entity'), java.sql.Date.valueOf('2013-01-01'), java.util.Date.new())

• history:medication(patient, productTypeName, from, to)

Returns all medication acts for a patient that have the specified product type name, between the specified dates, inclusive, ordered on descending start time

E.g.:

history:medication(openvpms:get(., 'patient.entity'), 'Vaccinations', java.sql.Date.valueOf('2013-01-01'), java.util.Date.new())

The functions may be to used in a JasperReports dataSourceExpression to be passed to a sub-report. E.g.:

<subreport>                               
    <dataSourceExpression>$P{dataSource}.getExpressionDataSource(history:medication(openvpms:get(., 'patient.entity')))</dataSourceExpression>
    <subreportExpression class="net.sf.jasperreports.engine.JasperReport">vaccinations.jrxml</subreportExpression>
</subreport>

JIRA: OVPMS-1361

This project will:

• display a warning message in charges if a selected product has no stock
• display the On Hand quantity in customer charges and supplier orders
• display an On Hand column in the Items table after the Quantity column
• display a warning message if an order contains duplicate products

Out of stock warning message

An out of stock warning message will be displayed in customer charges if:

• a product is selected that has no stock
• the entered quantity exceeds the available stock

The message will display the no. of items out of stock. E.g.:

On Hand Quantity

The On Hand quantity will be displayed next to the Quantity field, in both customer charges and supplier orders. E.g.:

On Hand column

For charges and supplier orders, an On Hand column will be added to the Items table, to indicate the current On Hand quantity.

For charges, if a Quantity exceeds the On Hand quantity, the On Hand quantity will be displayed with a red background.

Duplicate order item warning message

If a supplier order contains duplicate items, a message indicating the first duplicate will be displayed e.g.:

Acepromazine 25mg Tablets appears in the order 2 times.

Duplicate checks will be performed when:

• editing an existing order
• an item is added or deleted

This project will:

1. Make the Problems tab in Patients|Medical Records have a similar look and feel to the Summary tab

• Problems will be displayed in bold, with the form:

Date - Problem - Clinician - (Unresolved) or (Resolved dd/mm/yyyy)

• The 'current' Problem is displayed with a small arrow icon, the same as the current Visit is displayed in the Summary tab.
• Notes and Medications will be nested under problems, and display the same as they do in the Summary tab.
• editing a Problem only edits the act.patientClinicalProblem act. It doesn't touch the child act.patientClinicalNote or act.patientMedication acts. This is to reduce the likelihood that two users will edit the same Problem at once
• Problems, Notes and Medications are edited by double clicking, or pressing Edit
• Problems may only be deleted if they have no child acts
• Sort order will by problem status then descending date, so that Unresolved problems appear first

2. Add a Problems tab to the Visit Editor, next to the Summary tab

JIRA: OVPMS-1466

This project will enable reports normally run through the Reporting|Reports workspace to be scheduled to run automatically using the Quartz scheduling support.

This will be configured via the Administration|Organisation workspace, using a "Job Configuration: Reporting" configuration archetype.

This will use cron-like syntax to specify the day/time when the job should be run.

It will also include fields to determine how the report will be output, i.e. to:

• file
• printer
• email

File Output

When file output is selected, the following fields specify the location and type of the output file:

• directory
• file type (.csv, .pdf)
• file name. If no extension is provided, the file type determines the extension

If the report template has a File Name Format, this will be used to generate the file name. This can be used to append a date/time to the file name for example.

If the file exists, it will be overwritten.

Print Output

When print output is selected, the following fields specify the printer location:

• location. The practice location. This is constrained to those locations specified by the report document template.

The interactive flag specified by the template's Document Template Printer will be ignored.

Email Output

When email output is selected, the following fields apply:

• from - the from email address. Defaults to the email address of the current user
• to - the email address to mail to. Defaults to the email address of the current user
• file type (.csv, .pdf)
• file name. If no extension is provided, the file type determines the extension

If the report template has a File Name Format, this will be used to generate the file name. This can be used to append a date/time to the file name for example.

Report Parameters

Available report parameters will be determined from the report.

Values for these parameters will be configurable, but the values must be string constants. Up to 5 parameters will be supported.

Dynamic parameter values, evaluated via an expression, can be handled as a separate project.

Permissions

The Run As configuration determines the user that the report is run as. This user must have appropriate permissions to execute the report.

Logging

On completion/failure of the job, a system message will be sent to the Run As user.

JIRA: OVPMS-1964

This project will enable End Period processing to be scheduled to run automatically.

This will be configured via Administration - Jobs workspace, using a "Job Configuration: End Period" configuration archetype.

This will use cron-like syntax to specify the day/time when the job should be run.
The statement date will be the day when the job is run, -1.

It will also include a flag, "Finalise Completed Invoices", to determine if Completed invoices should be finalised prior to running End Period.

Permissions

The Run As configuration determines the user that the job is run as. This user must have appropriate permissions to perform End Period.

Logging

On completion/failure of the job, a system message will be sent to the Run As user.

JIRA: OVPMS-2595

This project will preserve the selection displayed when viewing an item, so that it appears when the item is edited.

E.g., if a customer location contact is being viewed, a Location contact is selected from the Contacts tab.

When editing the customer, the Contacts tab will be displayed, and the Location contact automatically selected.

The selection will be preserved to arbitrary depth. E.g. if a Reminder linked to an Invoice Item is being viewed, this will be selected when the Invoice is edited.

JIRA: OVPMS-1352

When macros are expanded, the cursor jumps to the end of the text. This is annoying if the macro is inserted into the middle of the text, as the cursor must then be moved back, either with the keys or by mouse.

This project will extend the javascript text field components so that they:

• track the cursor position
• enable the cursor position to be set

This can be used to move the cursor psition back to where it was, prior to macro expansion. If the cursor was at the end of a macro, then it will be moved to the end of the macro expansion.

Note that web browsers don't handle cursor positioning in the same manner. This project will initially support  Firefox, Chrome and Safari.

JIRA: OVPMS-1349

Many searches include a checkbox "Include Deactivated" (e.g. Customer, Patient and Product searches). When selected, the search will return both active and inactive results.

However there is no way to determine if a result is active or inactive, without selecting it.

Similarly, there is no way to search only inactive results.

This project will:

• replace the Include Deactived checkbox with a dropdown list named "Active", with the options:
  • Yes - only include active results. This is the default
  • No - only include inactive results
  • Both - include both active and inactive results
• add a "Active" column in the results when Active/Inactive is selected. It will display a checkbox indicating if a result is active/inactive.

The column will be displayed when searching for deactivated:

• customers
• patients
• products
• suppliers
• all organisational items in Administation|Organisation
• all types in Administration|Types
• document templates
• users
• groups
• roles
• authorities
• archetypes

JIRA: OVPMS-1385

This project will enhance the email window to enable:

• multiple attachments to be selected when clicking Attach in the email editor
• better support for deleting attachments on tablets
• customer account documents to be attached
• customer estimates to be attached

Multiple Attachments

The Attach Documents window will allow multiple documents to be attached by displaying a check-box next to each document. 

Attachment Deletion

Currently, attachments are deleted by clicking on them and pressing the Delete key.

To better support tablets, an X icon will be displayed next to the attachment when it is selected. Clicking it will cause the attachment to be deleted.

Customer Account Documents

For customer and patient workspaces, the The Attach Documents window will include a Customer Account tab displaying invoices, payments, refunds etc to attach.

The tab will include:

• a dropdown to filter documents by type
  This will allow multiple selection. By default, it will show all invoices and payments. 
• a status filter
  By default, it will show all Finalised documents
• a date range filter
  This will allow documents to be filtered on date. It will default to all documents

Multiple documents may be selected.

Customer Estimate Documents

For customer and patient workspaces, the The Attach Documents window will include a Customer Estimates tab displaying estimates. 

The tab will include:

• a status filter
  By default, it will show all Finalised and Invoiced estimates
• a date range filter
  This will allow estimates to be filtered on date. It will default to all estimates
• Multiple documents may be selected.

Exclusions

Multiple attachments won't be supported when clicking Attach File. This is due to a limitation of the web framework, echo2.