Should clinician choice be limited by location

We are in the middle of setting up another clinic in a different part of the city.

This has revealed (to us) that with a practice that has multiple real locations, that not every vet works at every location, and although one can limit the locations that a user has access to, the system does not limit the clinician that can be selected for an appointment or visit or invoice line item etc.

What do people think about limiting the selection of the available clinician to those who have access to the current location - ie have the current location set as one of their possible locations in their Administration|User record?

Regards, Tim G

Comment viewing options

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

Re: Should clinician choice be limited by location

Yes, that would be great for us too.

Re: Should clinician choice be limited by location

This could be supported by adding an All Clinicians check box to the Clinician browser.

By default this would be unchecked, excluding clinicians not linked to the current practice Location. To enter a clinician linked to another location, you would therefore have to click on the binoculars button, tick All Clinicians, and select it from the list.

Once selected, the clinician would be used automatically as is the case now.

 

Re: Should clinician choice be limited by location

Tim A - I concur with this approach - as well as a similar approach for worklist selection.

Would you like me to create a single project for both of these enhancements?

Regards, Tim G

Re: Should clinician choice be limited by location

Yes please.

Re: Should clinician choice be limited by location

Re: Should clinician choice be limited by location

Little late to the party, but we would like this as well.

Alan

Re: Should clinician choice be limited by location

Alan - it is the 'developer review' stage at the moment. When Tim A gets a chance, I hope it will be reviewed and costed and then we can start pledging money.

Regards, Tim G

Re: Should clinician choice be limited by location

As part of the implementation for those of us with single location clinics with lots of users, could we

a) Config/Option this as part of the Practice Organisation

b) Have as part of the migration an option to add locations to users so we don't have to go thru and add them manually.

 

Cheers,

matt

Re: Should clinician choice be limited by location

Matt - sorry for the delay. To respond to your points above:

a) Wilco - as is says in the project description "Since the customer selection restriction facility will not be required by multi-site practices who use a non-restricted customer pool, a 'Use Location Customers' switch will be added to the Practice. If this is unchecked (the default) then the 'All Locations' checkbox on the customer selection window will be checked; if checked, then the All Locations' checkbox on the customer selection window will be unchecked."

b) add locations to users with none. When I did the work on our system, we already had different account types for the housecall (CC) and street (EIAH) practices. Below is what I used simplified to set all customers with no practice location set to some standard practice location.

/* get locations */
select * from entities pl where pl.arch_short_name = 'party.organisationLocation';

/* from above output, get entity_id of required practice location */

/* set Customer location for all active customers with none */
/* NOTE - replace 165 in the following with the entity_id or the practice location to be used */
insert into entity_links (version,linkId,arch_short_name,arch_version,name,description,sequence,source_id,target_id)
select 
    0,
    UUID(),
    'entityLink.customerLocation',
    '1.0',
    'Customer Location',
    'Customer Location',
    0,
    e.entity_id,
    165
from entities e
left join entity_links el on el.source_id = e.entity_id and el.arch_short_name = 'entityLink.customerLocation'
where e.arch_short_name = 'party.customerperson'
and e.active = 1
and isnull(el.id);

Hope this helps.

Regards, Tim G

Syndicate content