dhis2-users team mailing list archive

[Juan M Alcántara Acosta <jmalcantara@xxxxxxxxxxxxx>]

Hi Lars
I'm sorry I think I did a poor job explaining, the selected parent and all the children I was referring to is the org unit the user is allowed to see/use, so the search would include org unit(s) assigned to the user and all the children.
Let me give you a brief description of what we are doing. We have a first contact program (IPCs) with which we register clients at a municipality level (level 4) and a clinical services program that links services to specific providers (level 6, level 5 is the clinic). When the office receives the report of clinical services they don't know where the client was first contacted by an IPC and even if they can asume this took place at the same municipality where the clinic is located (not always the case). This is the procedure they use to do this as fast as possible:

1. Search and select the provider of the clinical service (org unit)
2. Search for the client by name, it would be great if they could also search by referral number which is a DE in a program. 
3. Once the client is found, the user opens the person panel to enrole the client in the clinical program and add the event(s). At this point the person can be moved to the org unit where the clinical services were received, but they are not doing this to save time.

In this particular case a search on the selected org units (and all bellow) will not return the record of the client since it's located two levels above and it could even be on a different branch. We have to use "all visible" to get the result and this requires assigning an org unit and some or all of the children.

The users have made two more observations related to the search:
1. An advance search done with the options "Selected and bellow" and "All visible" takes at least 45 seconds
2. The search returns all the hits per word. For example, if you search for "Maria Luisa" you'll get back all the records that contain "Maria" plus all the records that contain "Luisa". Is there a way to get the results of only the records that contain all the words?

Best regards,
JM





El 09/12/2013, a las 12:22, Lars Helge Øverland <larshelge@xxxxxxxxx> escribió:

> 
> 
> 
> On Thu, Dec 5, 2013 at 12:48 AM, Juan M Alcántara Acosta <jmalcantara@xxxxxxxxxxxxx> wrote:
> I agree in part and definitely prefer to assign access to org units just by selecting the parent rather than multiple units in the same branch. The requirement to select a number of children org units came from the specifications to be able to use the advance search option "all visible" in Find/Add Person. Back in august I started a conversation with Tran to request a way to limit the scope of the search to only the org units a user can access -Thank you Tran!- I'm not familiar with the use case that resulted in the current specification but if you ask me, I'd vote to modify this option to make it work with the selected parent and all the children :-)  -not the same as selected and bellow-. We need this to keep users from searching in all system org units and getting access to person records from different countries or org units out of their allowed scope of work.
> 
> Sorry for the detour... back to the bug report. The tabular report is the only section of the system that misbehaves in the way the org unit tree is presented; data entry, visualizer, pivot tables, etc. all present the org unit tree correctly. I'm including two screen captures, one from our development server and another one from the Sierra Leone demo. To duplicate in the demo I created an account and selected National, District and PHU levels.
> 
> 
> Hi Juan,
> 
> okay, I don't quite follow.. What is the difference between "selected parent and all the children" vs "selected and below" ?
> 
>