Change Appointment Status Colour

Hi,

I can't figure out how to change the colours of the Appointment Status options (ie billed)

I would like to make the colours a bit more obvious on the worklist so the receptionists know when an account is completed.

Perhaps it isn't a thing users can change?

Thanks,

Greta

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Change Appointment Status Colour

Re: Change Appointment Status Colour

Thanks Tim, that's perfect.

Greta

Re: Change Appointment Status Colour

Hi guys,

Thanks to Tim's help, I have created a new Status 'Unpaid'.

This is for patients that have been discharged, but we are waiting for the funds to appear in our account (either by funds transfer or insurance)

This new status 'Unpaid' cannot be allocated a colour, which is fine.

However, I am wondering is the status can be allocated to the class - Incomplete

The current logic would appear to be:
  If status == Completed or Cancelled class as Completed
  Else if status == Pending, In Progress or Billed then class as Incomplete
 
What I need is:
  If status == Completed or Cancelled class as Completed
  Else class as Incomplete
 
Thus any new status would be classed as Incomplete.
 
Would it be possible for this to be changed in the code?

Thanks

Re: Change Appointment Status Colour

Assuming the new status code is UNPAID, I think you should be able to assign a new status colour by adding the following to your default.stylesheet:

<style name="ScheduleTable.UNPAID" type="nextapp.echo2.app.Component">
    <properties>
        <property name="layoutData">
            <layout-data type="nextapp.echo2.app.layout.TableLayoutData">
                <properties>
                    <property name="background" value="${schedule.unpaid.colour}"/>
                    <property name="insets" value="${padding.small} ${padding.tiny}"/>
                </properties>
            </layout-data>
        </property>
    </properties>
</style>

And the following to site.properties:

schedule.unpaid.colour = '#ff4040'

I'm not sure I understand your subsequent point. If your appointment has status code UNPAID, then you won't be able to Check-In, Check-out or Consult, but I expect that is the desired behaviour anyway.

You will be able to delete the appointment, which may not be desirable. Appointments with Completed status can't be deleted, but setting the status to Unpaid circumvents this.

 

Re: Change Appointment Status Colour

Tim - what Greta is talking about with the 'class as incomplete' bit is how tasks are displayed. On the Workflow|Work Lists screen, the status selection is All, Incomplete, or Complete.

As the code currently is, if you add a new status Unpaid by changing the local lookup list in the act.customerTask archetype, then tasks with this status do not show unless you select Status=All. What Greta wants is for them to also appear if you select Status=Incomplete.

I must admit that I had not thought about the allowed state transitions, and I also had not considered the workflow implications.

As Greta said in our email exchange:

It is for clients that have picked up their pet, but they have paid by GE or Funds Transfer or Insurance.

That way, those clients can remain on the worklist for a day or so until their funds transfer comes through. 

Or for those clients that the reception staff need to call the next morning to get payment.

They aren’t debtors, because they should only remain on the worklist for 1 day or so, but the patient is not in hospital anymore.

So perhaps the best way to handle these situations is via a follow-up task list, rather that adding a new status to the task. That is, when this situation arises, you create a new task in a Follow-Up worklist as a aide-memoire.

Note that there are in fact two different situations here:

1) customer has paid - but funds have not yet been received
2) customer has not paid (and reception needs to call to get payment)

In the first case, as far as OpenVPMS is concerned, all is complete. In the second, all is also complete (as far as the workflow is concerned) except that the customer still owes money.

Greta - remember that as far as OpenVPMS is concerned, whether or not the customer has paid does not effect that fact that the checkout process is complete - because in OpenVPMS we don't pay off individual invoices, but rather pay off account balances.

My recomendation: go with the follow-up task list approach

Regards, Tim G

Syndicate content