Under Discussion

Changing reminder selection for reminder runs

Development Project Status: Under Discussion

Due date for completion of this stage: 
17/06/2015
Release: 
Future
Project funding: 

You can donate money to this project by entering the amount above and clicking the 'Add to cart' button. In the Checkout process you can either choose to pay now (via Bank Transfer, Cheque or Pay Pal) or you can pledge the amount by choosing the 'Pledge a payment for a Development Project' method. If you make a pledge, then when we have 100% funding commitments, you will be notified by email and you can then action your payment. Note that development will not commence until all funds are received.

Project description: 

At present, reminders can be generated for all reminder types, or a single reminder type.

This project will enable one, multiple or all reminder types to be selected, as shown in the mockup below:

Hide cancelled appointments

Development Project Status: Under Discussion

Due date for completion of this stage: 
17/06/2015
Release: 
Future
Project funding: 

You can donate money to this project by entering the amount above and clicking the 'Add to cart' button. In the Checkout process you can either choose to pay now (via Bank Transfer, Cheque or Pay Pal) or you can pledge the amount by choosing the 'Pledge a payment for a Development Project' method. If you make a pledge, then when we have 100% funding commitments, you will be notified by email and you can then action your payment. Note that development will not commence until all funds are received.

Project description: 

OpenVPMS always displays Cancelled appointments and makes them subject to double booking checks. For schedules that don't allow double booking, cancelled appointments must first be deleted to re-use the slot.

This limits the ability to do reporting on cancelled appointments.

This project will:

  • provide a Show Cancelled option, to show or hide Cancelled appointments. This will be ticked by default.
  • exclude Cancelled appointments from double-booking checks

To re-use the slot occupied by a Cancelled appointment, Show Cancelled needs to be unticked.

Reduce incidence of 'No Reason' Visits

Development Project Status: Under Discussion

Due date for completion of this stage: 
21/05/2015
Release: 
Future
Project funding: 

You can either donate money to this project by entering the amount above and clicking the 'Add to cart' button, or you can pledge an amount by clicking here to email your commitment. If you make a pledge, then when we have 100% funding commitments, you will be notified by email and you can then make your actual donation. Note that development will not commence until all funds are received.

Project description: 

This project is the result of two sets of forum discussions: http://www.openvpms.org/forum/add-visit-and-note-suggested-change and http://www.openvpms.org/forum/setting-visit-status-completed

These discussions indicate that most 'no reason' visits are created via two mechanisms: the "Add Visit & Note" button on the medical records & visit editor screens; the fact that generating a customer invoice creates a 'no reason' visit to record the sale to the patient.

This project will do the following to address the first:

  1. remove the 'Add Visit & Note' button from both the visit editor and medical records summary screens (note that this is already listed in OVPMS-1619)
  2. add  Note and Diagnosis buttons to these screens (which function in exactly the same way as New|Note and New|Problem)
  3. change the New|Visit screen so that you can also enter Note text so that it functions as 'Add Visit & Note'.  It thus has the convenience of the 'Add Visit & Note' button, but does not appear on the visit editor screen and thus tempt people to add a visit and a note when all they should be adding is a note.
  4. change "No Reason" to "-" in messages.properties so that only "-" is shown if there is no appointment reason available when the visit is created

This project will do the following to address the second:

If a visit is created as the result of a customer sale then:

  1. the visit reason will be set to CUSTOMER_SALE if there is such a reason in the Visit reason lookup
  2. the visit status will be initially 'In Progress' (as is the case currently)
  3. when the invoice is finalised by pressing the Finalise button on the Customers|Charges screen) then the visit complete date will be set to today and the visit status set to Completed. Note that it is possible to have one visit containing multiple invoices.  In this situation the first invoice to be finalised will complete the visit and set the completed date.

 

Invoice Edit Locks

Development Project Status: Under Discussion

Total cost estimate (ex-Tax): 
$8110
Due date for completion of this stage: 
08/05/2015
Release: 
Future
Project funding: 

You can either donate money to this project by entering the amount above and clicking the 'Add to cart' button, or you can pledge an amount by clicking here to email your commitment. If you make a pledge, then when we have 100% funding commitments, you will be notified by email and you can then make your actual donation. Note that development will not commence until all funds are received.

Project description: 

OpenVPMS uses a technique called optimistic locking to ensure that multiple users editing the same object don't overwrite each other's changes. If two users edit the same object, the first user to save wins, and the second user's changes are rolled back.

Whilst this prevents data corruption, it means that the second user to save loses their changes.

This project will introduce edit locks so that when a user edits an object, they acquire a lock. If another tries to edit the same object, a message will be displayed and editing will be prevented.

Initially, only support for invoice edit locks will be provided, but this may be extended to other objects in future.

Locks

Locks are acquired when editing an object. A lock contains:

  • the object being edited
  • the user
  • the time the lock was acquired

When editing completes, the lock is released.

If a lock has been acquired for an object, and another user tries to edit the same object, an error message will be displayed e.g.

This invoice is being currently being edited by J Smith.

Invoice Editing

Invoices are the primary cause of save conflicts, so these will be the first candidates for edit locks. It also means that deadlock detection won't be required.

Invoice locks need to be acquired when performing:

  • Customer Charges (new, edit, delete, finalisation)
  • Check-In
  • Consult
  • Check-Out
  • Estimates - Invoice
  • Customer Orders - Invoice
  • Prescriptions - Dispense

Invoices also update many other objects. These must not be edited while their associated invoice is edited. This includes:

  • medications
  • prescriptions
  • investigations
  • documents
  • reminders
  • visits

Lock Expiry

Locks will automatically expire if a user logs out or their session is terminated.

Lock Removal

A new administration workspace will be provided to:

  • query current locks
  • remove individual locks

Exclusions

This project will not support:

  • automatically releasing locks if a user is away from their terminal
  • preventing invoices or related objects being updated by background tasks e.g.:
  • Reporting - Debtors - End Period
  • Reporting - Reminders - Send All

These could cause a user's changes to be rolled back, so should be run when editing is not being performed.

Invoice Reception Notes

Development Project Status: Under Discussion

Due date for completion of this stage: 
01/05/2015
Release: 
Future
Project funding: 

You can either donate money to this project by entering the amount above and clicking the 'Add to cart' button, or you can pledge an amount by clicking here to email your commitment. If you make a pledge, then when we have 100% funding commitments, you will be notified by email and you can then make your actual donation. Note that development will not commence until all funds are received.

Project description: 

Currently, invoices support notes intended for customers using the Notes and Customer Notes fields.

This project will:

  • add a Reception Notes field to invoices, to capture notes intended for reception staff
  • copy the reception notes to patient history as a Clinical Note

if more than one patient is present on the invoice, the note will be added to each patient's history

  • update patient history if the reception notes change
  • delete the reception note from patients removed from the invoice

If a patient is removed from an invoice, any reception note in their history also needs to be removed

 

Exclusions

This project will not:

  • update the Reception Note on the invoice, if a Clinical Note is updated or removed from the patient history.

Implementation Notes

This change will require relationships between the Invoice and multiple Visits, so care needs to be taken to ensure that:

  • concurrent updates are handled to avoid updates being rejected
  • subsequent deletion of a reception note from patient history doesn't trigger business rules for finalised invoices

 

VetEnvoy Insurance Claims integration

Development Project Status: Under Discussion

Due date for completion of this stage: 
10/01/2015
Project funding: 

You can donate money to this project by entering the amount above and clicking the 'Add to cart' button. In the Checkout process you can either choose to pay now (via Bank Transfer, Cheque or Pay Pal) or you can pledge the amount by choosing the 'Pledge a payment for a Development Project' method. If you make a pledge, then when we have 100% funding commitments, you will be notified by email and you can then action your payment. Note that development will not commence until all funds are received.

Project description: 

Overview

This project is an extension to the Patient Insurance project, allowing claims to be submitted to insurers that use the VetEnvoy eClaims service.

VetEnvoy supports insurance e-claims in the UK, US and Canada.

 

Claim Submission

Any Insurance Claim that is finalised will automatically be submitted to the VetEnvoy eClaims service, if the Insurer linked to the Policy Type is a party.supplierInsurerVetEnvoy (see below).

When finalised:

Customer Order Service

Development Project Status: Under Discussion

Due date for completion of this stage: 
08/07/2014

This project will allow external systems to place orders for customers and patients within OpenVPMS via a web-service.

This can be used by in-house lab and dispensing equipment to initiate billing for products and services.

The project will deliver:

  • a web service to receive orders
  • a workspace to view and invoice orders
  • integration with the Visit editor to invoice orders
  • support to notify users that an order has been received

Web Service

The Customer Order web-service will:

Multiple active referrals

Development Project Status: Under Discussion

Due date for completion of this stage: 
31/05/2014
Project description: 

OpenVPMS currently only allows a single active referral.

This project will:

  1. allow multiple active referrals
  2. create new Referral Letter and Referral Forms that include the referral
  • These are essentially the same as the existing patient Letter and Forms but provide a mandatory Referral field.
  • The Referral field will:
    • default to the most recent referral of the patient
    • allow a new referral to be added
    • any new referral will be added to the patient's list of referrals (i.e. be displayed in Patients|Information), as a Referred To record.
  1. change reporting functions to:
  • use the Referral field if present; or
  • fall back to the referal with the closest Start Date to that of either the document act being generated, or the current time. Note that this can lead to ambiguities as its reliant on the creation order of the Referred From and Referred To records, so use of the Referral field is preferred.

Service notes

Development Project Status: Under Discussion

Due date for completion of this stage: 
28/03/2014

This project will extend Service products to include a Visit Note field. This facility is already present for Template products.

This will be used during charging in the Check-In and Consult workflows. When a Service with a Visit Note is charged, a new Note record containing the Visit Note text will be added to the patient history.

If a service is deleted from an invoice, any Note added to the history will not be removed. This mirrors the behaviour of the Template Visit Note.

Report logos

Development Project Status: Under Discussion

Due date for completion of this stage: 
06/01/2014

Currently reports access practice logos via hard-coded paths stored on the server.

This project will:

Syndicate content