Use of filename as derived value for description field in act.patientDocumentForm
Had a problem with staff unable to accurately de-select documents when checking patients out. All they could see was the "name" field saying "Patient Form" or the like.
By adding "/fileName" to the derived field of Description, now atleast gives the template name and indicates to staff what the form is.
Thought that in lieu of any other derived values that filename might be worth making a permanent addition to all the "Document" acts.
Matt C
Re: [OpenVPMS Developers] Use of filename as derived value for d
I can see the issue but Description is currently not a derived field in any of the document archetypes it is a normal field and was intended for a specific description of the document. If we make this derived I think we need another field to hold the notes ... Alternatively in the application we can display the filename if the description is null ?
Cheers Tony
> Tony De Keizer > Principal Consultant > Vertical Connect Pty Ltd > Phone: + 61 (0)3 97229824 > Mobile +61 (0)4 21347105 > Email: tony@verticalconnect.net > From: > Reply-To: , OpenVPMS Developers Mailing List > > Date: 17 Feb 2009 12:55:02 -0000 > To: > Subject: [OpenVPMS Developers] Use of filename as derived value for > description field in act.patientDocumentForm > > Had a problem with staff unable to accurately de-select documents when > checking patients out. All they could see was the "name" field saying "Patient > Form" or the like. > > By adding "/fileName" to the derived field of Description, now atleast gives > the template name and indicates to staff what the form is. > > Thought that in lieu of any other derived values that filename might be worth > making a permanent addition to all the "Document" acts. > > Matt C > _______________________________________________ > OpenVPMS Developers Mailing List > developers@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/mailman/listinfo/developers > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS Developer's forum- http://tinyurl.com/openvdf_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/mailman/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf
Use of derived fields
Hey Tony, Ahh, I see.
Yeah, that null conditional within the application would work.
For now I'm keeping the description derived as a temporary work around. In our hands description field is used in a minority of documents, mainly our attachment acts at this time.
Matt
Still on derived fields
On a related matter,
When we are editing a medical record with multiple notes (eg. a hospital patient), we get the same issue as with the printing dialog. Theer are a list of medical record items (patient clinical event items) identified only by their type "Note". To edit a particular note, one must select each and see which one contains the text you wish to edit.
I had hoped to use the empty description field next to it to have the first 30 characters or so of the medical note but can't work out a way to do this within archetypes. It seems this description field for medical record items:Notes is empty at present. Is such a derivation possible or would it need to be hard coded in the application?
Matt C
Viewing document names at checkout
Sandra @ Bellarine
We would love to have the document name listed in the PRINT box at checkout. We would save heaps of paper and our receptionists would be much happier.
Sandra.