Clician selection - improvement suggestion - FIXED

Submitted by Guest on Wed, 02/01/2013 - 19:56

Implementation discussion

I have a solution for this - see the bottom comment to this post. Regards, Tim G

In the current (1.6) system, the clinician has a login id, and a name. The name is used for both clinician selection and printing on documents.

Because of the 'print on document' function, one wants the name to be as formal as possible, eg Dr Joe Bloggs, B.VSc(Melb) [or whatever the proper qualifications are].

However doing this means that the clinician selection is sub-optimum (because everone starts "Dr ").

Suggestion:
a) add a "Printed Name" field (just like products have a printed names as well as a name)

b) adjust the clinician.entity.name retrieval code to return the clinician Printed Name and if this is null, the clinician Name. [This will ensure that existing systems are unaffected.]

Then one can set the clinician name to jb and the printed name to Dr Joe Bloggs, B.VSc(Melb).

Regards, Tim

Re: Clician selection - improvement suggestion

Submitted by tanderson on Mon, 07/01/2013 - 10:40.

It may be simpler to support queries by login name as well as name. The name would continue to be used for display.

So both "jb" and "Dr Joe" would fetch "Dr Joe Blogs, B.VSc(Melb)".

-Tim A

Re: Clinician selection - improvement suggestion - FIXED

Submitted by tgething (not verified) on Fri, 18/01/2013 - 09:25.

The solution (or rather the workaround) to this problem is to do as follows:

a) in the user definition, set the 'Full Name' field to the name by which you want to access the clinician (eg JB), and set the 'Description' field to the full formal name (eg "Dr Joe Blogs, B.VSc(Melb)")

b) in any patient reports (eg invoices, estimates) where you need the formal name, use 'clinician.entity.description'.

Regards, Tim G