Enhancement Request - add breed to Select Patient screen

I have been asked if it is possible to add search on breed to the Select Patient screen. [I am doing an RxWorks port and breed search is commonly used in this practice - necessitated by the large number of common names - there are 379 patients called Bo Bo, and 38 clients named Chan with a pet called Bo Bo.]

I think that the best way to implement this is to add the same type of 'search contact' facility as is available on the Select Customer screen.

However, for patients its simpler - no need to change the data display (since the description already contains the breed).  In fact if the search was a search of the description field (if this is possible), then one could  search for species, breed and colour.  The extra search box would be labeled Description, and would work the same way as the Client Contact search - ie has an implicit % at the beginning of the text entered as well as the trailing one.

I would be really interested in a costing for this enhancement.

Regards, Tim

Comment viewing options

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

Re: Enhancement Request - add breed to Select Patient screen

The main issue with searching on description is that it is not an indexed field. If you don't add any other criteria, this will result in a linear (i.e. slow) search of all patients.

Searching on the breed node is possible, but cannot be implemented in a straight forward manner due to the way dynamic nodes are implemented. By dynamic node, I mean any node that is not part of the database schema, but are added via a mapping table. This table describes the node name, type and value.

E.g. the breed node of party.patientpet is a dynamic node:

 <node name="breed" path="/details/breed" type="java.lang.String" maxLength="30">

Any node with a "/details" in the path is a dynamic node.

These nodes cannot be searched using OpenVPMS' normal query support; a named SQL query must be used instead. We use these queries sparingly, as they reduce flexibility.

-Tim A

Syndicate content