Overview

Schedule blocking enables date and time ranges on schedules to be marked as unavailable.

This can be used to prevent appointments being made outside business hours or public holidays for example.

Currently OpenVPMS supports limited schedule blocking by defining a start and end time between which appointments can be created. There is no support to prevent scheduling between these times or on particular days.

Users currently work around this by creating dummy appointments.

This project will enable users to create blocks on a schedule, such that:

• a warning is displayed if an attempt is made to schedule an appointment where there is a block e.g. if the appointment is scheduled outside hours, or on a public holiday.
• schedules can be reserved so that appointments can only be created for customers with specific classifications e.g. it could be used to reserve boarding cages during holidays for valued customers

Block Creation

Schedule blocks will be created within the Workflow - Scheduling screen, via a new Block button.

A block:

• may optionally be named (e.g. Public Holiday, Team Meeting etc)
• must have have start and end dates
• may be recurring. It has the same recurrence options as appointments
• may have a Block Type. This provides
  • a default name for the Block
  • customer classifications that the Block is restricted to (e.g. Puppy Class, Valued Customer, Health Club Member)
  • a colour for the Block when it is displayed
• may not be created if it overlaps an existing appointment
• may not be created if it overlaps an existing block

Block Display

Blocks are displayed as contiguous regions, with a name, if one has been specified, and the colour of the Block Type, if any.

If an appointment overlaps a block, it hides the portion of the block it overlaps.

Saving Appointments

When an appointment is saved, an additional check will be made to determine if it overlaps a block. If so, and the block has no Block Type with customer classifications, a warning will be displayed e.g.:

This appointment overlaps a schedule block (Public Holiday). Do you want to save it?

If the block has a Block Type with customer classifications, and the appointment is for a customer with one of those classifications, then no message is displayed.

If the block has a Block Type with customer classifications, and the appointment customer doesn't have any of those classifications, then an error message will be displayed e.g.:

This appointment overlaps a schedule block (Reserved for Puppy Class) and cannot be saved.

JIRA: OVPMS-1763

Related JIRA:  JIRA 884
Summary :

This Investigations Management project relates directly to the Investigation Module working group (http://www.openvpms.org/investigation-module).

The aims of the Investigation Module working group is:
"...to provide clinical staff with sufficient functionality to streamline management of investigation orders and results, provide suitable viewers to view these results as part of the patients clinical record and provide extensible interfaces to facilitate a broad range of internal and external communication protocols and applications."
 

The steps are as follows:

1. User bills product linked to Investigation type.

2. Form created, printed and sent with unique document_act or ibvestigation_act id as lab request number.

3. Lab result returned via electronic means

4. Scheduled import into Investigations and updating of the investigation status.

This particular development will establish the necessary automatic generation of Laboratory request forms during billing (Steps 1 & 2).

Products will be linked to an Investigation Type which in turn will have an associated Lab Request form template. When a linked product is billed, there will be an option to print the appropriate form and an Investigation event will appear in the Medical Record of the patient.

This project is fully funded!

The idea is a brilliant one and very simple.

The Dispensing Units (eg. tablets) as set up in the Products section appear whilst billing next to the "quantity" entry field and before the "Total" label.

 Forum: www.openvpms.org/forum/seeing-dispensing-units-during-invoicing

 Jira: jira.openvpms.org/jira/browse/OVPMS-896

The idea is a brilliant one and very simple.

The Dispensing Units (eg. tablets) as set up in the Products section appear whilst billing next to the "quantity" entry field and before the "Total" label.

 Forum: www.openvpms.org/forum/seeing-dispensing-units-during-invoicing

 Jira: jira.openvpms.org/jira/browse/OVPMS-896

The project has been sent to the developers for costing with the following requirement:

"..The Dispensing Units (eg. tablets) as set up in the Products section appear whilst billing next to the "quantity" entry field and before the "Total" label..."

This project has been costed at $300 to develop. It has been fully funded.

It was suggested that a recently selected customer list would be a great timesaver. The final draft features included;

1. A button will be added to the bottom of the screen below the customer/patient summary, and to the left of New/Edit etc buttons.

2. Clicking on the button will show a popup. History items are displayed in the popup when the button is pressed. The button can have a keyboard shortcut

Funding has been acheived! Development is underway. Congratutulations to all those who helped the idea become reality!

JIRA: OVPMS-869

This initiative includes the following features;

A) Grouped Reminders - http://jira.openvpms.org/jira/browse/OVPMS-862

This is the ability to merge reminders for patients owned by the same patient.

B) Modified Reminder Update - http://jira.openvpms.org/jira/browse/OVPMS-870

This initiative includes the following features;

A) Grouped Reminders - https://openvpms.atlassian.net/browse/OVPMS-862

This is the ability to merge reminders for patients owned by the same patient.

B) Modified Reminder Update - https://openvpms.atlassian.net/browse/OVPMS-870

This is the ability to handle errors/interruptions during the reminder process.

C) Reprinting Reminders - https://openvpms.atlassian.net/browse/OVPMS-871

This is the ability to to allow printing and re-printing of reminders from Patient Reminders workspace

Current % Funded: 100%

60 hours @ $75/hr = $4500

Thank you for all those that contributed to funding this user driven development!

Completed and scheduled for deployment in Version 1.4

For some time now, some veterinary wholesalers have been keen to investigate automating price updates and integrating ordering and receipt of stock. Our hope is that in working this process through in the Ope VPMS user community may create the opportunity to create a solution that will have application for other forward thinking veterinary wholesalers.

There are at the moment, 2 broad aims;

1. Ordering
- Allow orders generated within OpenVPMS to be submitted electronically or as a printed document to a wholesaler. Ideally electronic submission is ideal to allow automatic processing at the wholesaler end.

2. Deliveries
- Allow Deliveries to be automatically uploaded into OpenVPMS. This is intended to automtically update inventory and prices based on wholesaler list price.

User forums:Current forum and Older associated forum

At this stage we believe we have enough information to turn this discussion into  a development project and start to seek funding. 

We have created an overall project JIRA for what we have now called the Electronic Supply Chain Interface project (ESCI).  You can find it here https://openvpms.atlassian.net/browse/ESCI-1 .  We will divide the overall project into a number of smaller sub projects so we can manage releases and funding better.  Our intention is to build up the complete ESCI over time using a number of these sub projects according to priorities based on community input.  

The first sub project will deal with developing the interface used to send Orders to and receive Order Responses from suppliers.  We have called this Simple Ordering Services (https://openvpms.atlassian.net/browse/ESCI-2)  as it only deals with sending of orders and receiving simple accept and reject messages.  It does not deal with the more complex process of order changes and cancellations. This sub project includes developing the definitions of all the documents that will be transmitted between supply chain partners , the development of the interface components and also development of a test application.Once completed suppliers can use the provided documents and applications to start building and testing their side of the interface. 

The second sub-project deals with integrating the Simple Ordering services with OpenVPMS (https://openvpms.atlassian.net/browse/ESCI-3).  It will utilise the interfaces we developed above and per supplier configuration information to send orders from the Orders Workspace , manage Order status and provide notifications to users on any order status changes.  The reason we have decided to separate this from the development of the core ordering services is it will hopefully speed supplier development and adoption. 

Estimated times to deliver these two sub-projects have been provided in the JIRA's noted above.  Aproximately 30% of this time will dedicated to elaborating the specifications for the projects and building common components that will be utilised in subsequent ESCI projects such as deliveries, invoices and catalogue requests.

We are now looking for funding to get development of these first projects underway. We look forward to your involvement and contributions.

Auto-capitalisation would mean that the application would automatically try and create correct case when entering data such as names and addresses.

eg. gary newman of 11 glitter st, melbourne => Gary Newman of 11 Glitter St, Melbourne

The ability to search appointments within the scheduler has been a popular request. The proposed solution would allow users to check if a customers patients have any future/past appointments. Furthermore the list will act as a set of links allowing the user to directly jump to the schedule day in question.

This development is fully funded

Please email me (mpcosta[at]boroniavet.com[dot]au) with the maximum contribution you are willing to make either a percentage or as a $ amount.

1. The Customer workspace

1.1 A new tab that contains a list of appointments for any patients with a patient-customer relationship.

- Current data required: Date, Time, Patient and Reason

1.2 Filtering

- This tab would contain a list that could be filtered by status (pending/in progress/complete). Default would be Pending (this would pick up future appts)

- Alternatively (or inclusively) we could filter by date. (Future/Past).

- Inclusive Filter by Active patient-customer relationship.

1.3 Jump to schedule linking

- Have the appointment listed in 1.1 linked so that the user can click on it, and it will jump to that schedule and that date.

This development will allow users to search for patients and customers using their unique IDs. These ID numbers are assigned by OpenVPMS when the customer or patient is created.

Clinics can use these IDs to uniquely identify customers or patients for purposes such as invoice/payment tracking.

Searching would occur when using the current Patient and Customer selection screens. This feature would include a refinement of the current "thinking" the program currently does when trying to understand what the user is trying to search for.

This development is fully funded.

Please email me (mpcosta[at]boroniavet.com[dot]au) with the maximum contribution you are willing to make either a percentage or as a $ amount.