Thanks Tim,

This is the prescription form (ODT)... I'm thinking of the medication label (jrxml). Not entirely sure how to translate the ODT fields (repeats and get(.,'dispensing')) to jrxml.  Will this just pass through as "<field name="repeats" class="java.math.BigDecimal"/>"? I imagine if that works, I could do a "<variable ..... openvpms:get(...dispensing...)...>" or something like this.

Cheers, Paul

Thanks Tim - I just learnt two things: a) what the Number type is for; b) always read all of the stack dump. I now have things running.

However, because of the way the dispense count is being done, the information displayed on the label changes.

• if the label is printed as the item is being dispensed, then count() will be zero the first time the item is dispensed [because the dispensing record has not been written at the time the New Medication screen is presented with its Print Label button] - so on the first dispense it is not possible (in the jrxml code) to tell the difference between a medication with a perscription and one without
• if the label is printed from the Investigations tab, then the dispensing record has been created and the jrxml code can tell the difference between a medication with a perscription and one without, however, the labels for each of the individual dispenses will all see the same dispense count

Given the above, I think it best to discard the idea of putting the prescription count on the label.

One can improve the 'prescription visibility' by adjusting the description field for the act.patientMedication archetype so as to show which medications resulted from a prescription.

Changing this to

 concat(openvpms:get(.,'product.entity.name'), ' - Qty: ',/details/quantity,' Expiry: ', expr:if(boolean(/activityEndTime), date:formatDate(/activityEndTime), 'None'),expr:if(count(openvpms:get(.,'prescription.source.dispensing'))>0,' *P')) 

gets you the following (where the Baytril 150Mg was not a result of a prescription, but the others were):

If I try to be more sexy and display the repeat and dispense counts, then the derived field length exceeds 255 characters. The only way past this would be to provide a function to get the data - ie party:getDispensed(act) returns null if there was no prescription and say D/R (where D is the dispensed count and R the number of repeats) if there was.

Note that this approach (ie showing the D/R information rather than just the *P flag) is not immune from problems. If the medication record is ever edited, then the description will be recalculated and will now show the current dispense count rather than that at the time the medication record was created.

Hence it is probably better just to stay with the *P approach - this being a hint to staff that there is a prescription involved and they should look at the prescription tab for further information.

Regards, Tim G

Tim - thanks for this hint (act id=-1 if this is the label print at creation time). This has allowed me to correct the dispense count.  The attached jrxml prints the repeat number in the form "[Repeat r of t]" where r is the repeat number and t the total number of repeats.

At the initial dispense this is omitted if the label is printed as the medication record is being created. If you then select the dispensed line and again print the label it will show "[Repeat 0 of t]" - as this is the initial dispense and not a repeat.

If you dispense a second time (ie 1st repeat) it shows "[Repeat 1 of t]" irrespective of whether you print as the medication record is being created or from the dispensed line.

Note however, that if you now reprint from the FIRST dispense line, it will also show "[Repeat 1 of t]" - ie the repeat count alway shows the total number of times the prescription has been repeated.

WARNING: the attached jrxml uses the Arial Unicode MS font so that I can display chinese characters on the label. It also get the vet's name from the clinician description field (rather than using the name) - this follows our usage of initials for the clinician selection.

Regards, Tim G