Cancelled 10/1/2020. This project is made redundant by the Investigation support in OpenVPMS 2.2 which allows multiple tests to be submitted in a single investigation.

The HL7 General Orders project added support to enable investigations to submit laboratory orders to providers via HL7. Investigations may be used to submit a single order.

This project will extend that functionality to allow a single investigation to submit multiple orders. This is required for laboratories that perform a battery of tests on a single sample (e.g. bloods).

This will be supported by extending:

• Investigation Type to contain zero or more Panels. These represent the tests that can be performed.
• Investigation, to contain zero or more Investigation Panels. Each Investigation Panel links to a Panel from the Investigation Type, and represents the tests that will actually be performed.

When an Investigation Type is selected that contains Panels, an Investigation Panel will be created for each corresponding Panel.

E.g. given an Investigation Type "Test Battery" with Panels "Complete Blood Count" and "Chemistry T4 - Thyroid function" is selected, the Investigation will be pre-populated with 2 Investigation Panels, "Complete Blook Count" and ""Chemistry T4 - Thyroid function".

Investigation Panels cannot be added to an Investigation, as this would affect charging. They can however be removed.

HL7 Changes

The Universal Service Identifier used to identify the test to order will be moved from the Investigation Type to the Investigation Panel.

For each Panel present in an Investigation, the HL7 order will include an ORC segment with the Panel's Universal Service Identifier.

Migration

For each existing Investigation Type instances with a Universal Service Identifier:

• a corresponding Panel will be created, and linked to the Investigation Type. It will be given a name derived from the Investigation Type Name e.g. for an Investigation Type of "Complete Blood Count", the Panel name would be "Complete Blood Count - Panel".

Existing investigations won't be migrated?

This project is cancelled:

• support to edit the visit reason was added for 2.0, OVPMS-1988
• other requirements are covered by OVPMS-2010 Prevent Add Visit & Note if there is an existing visit

The "Add Visit & Note" button in Patients - Medical Records and the Visit editor is a shortcut for creating a new Note linked to a new Visit.

This project will improve this feature by:

1. Allowing the Visit Reason to be edited

Currently, only the Note may edited. To set the Visit Reason, the Visit must be edited separately.

To simplify this, a new dialog 'New Visit & Note' will be created that supports editing both the Reason of the Visit, and the Note.

2. Prompting if an active Visit exists

Currently, "Add Visit & Note" will always add a new Visit. This can lead to multiple active Visits being created, when only one is desired.

This will be changed so that if an active Visit exists, a prompt is displayed:

There is currently an 'In Progress' Visit dated dd/mm/yyyy. Do you want to create a new Visit?
 

Pressing 'Yes' will create a new Visit and Note.

Pressing 'No' will create just the Note.

Presssing 'Cancel' will abort.

Update 27/5/15: This project has been cancelled as similar functionality can be obtained using:

• http://www.openvpms.org/project/nested-product-templates
• http://www.openvpms.org/project/printing-invoices-and-estimates-grouped-...

UPDATE 9/5/2020. In OpenVPMS 2.2, unlimited notes are supported using the existing document support. See https://openvpms.atlassian.net/browse/OVPMS-2292

Patient clinical note fields are limited to 5000 characters at present, requiring long notes to be split accross multiple Note records.

This project will add support for large text documents that can be used to store notes of practically unlimited length.

Initially, the text documents will be used to store patient clinical notes, but could be used to store any text record in future, including html.

This will require a modification to the OpenVPMS database schema to add a new text_documents table. This will be similar to the documents table but have a longtext column instead of a longblob. The longtext column will be easier to search and report.

Changes required:

• add text_documents table to store text
• add framework support for text documents
• change act.patientClinicalNote archetype to use a text document for its note field
• change act.patientClinicalNote editor to edit text documents
• add support to migrate existing databases. This includes:
  • updating the schema to include the text_documents table
  • migrating existing act.patientClinicalNote data

Update 27/5/15: This project has been cancelled as the functionality can be achieved using the features introduced by http://www.openvpms.org/project/add-support-multiple-cc-and-bcc-addresse...

21/12/2015 - The functionality of this project has been rolled into SMS Appointment Reminders (Automatic), available in OpenVPMS 1.9