dhis2-users team mailing list archive
-
dhis2-users team
-
Mailing list archive
-
Message #08364
Re: Setting up Point of Service sites
Hi Laura,
In South Africa we collect data at service point E.g hospital ward or
consulting room below facility or outreach team. We even have one program
where we collect data per outreach team member although due to staff
changes we have generalised the name of the orgunit not to the health
workers name but a more generic name with a no attached.
These initiatives started mostly as a data quality improvement measure
because it eliminates human error in compiling data from different service
points.
The only issue we found over the last probably 5 years of collecting
service point data is that we try to.keep the orgunits to a
On 13 Oct 2015 17:58, "Laura E. Lincks" <laura.lincks@xxxxxxxxxxxxxxxxx>
wrote:
> A point of service in our world is sort of like a specialty treatment
> center within a facility, a hospital, etc. pertaining to HIV Testing and
> Counseling. It could be as specific as "In-patient for Adult Males" or a
> general "Outpatient" or it could be "Family Planning" or "VCT". I'm dealing
> with 2 issues at the moment: addressing the immediate need of a specific
> country for reporting this week and devising a consistent way to set up all
> countries' POSs.
>
> For the specific country issue we are setting them up as another
> organisation unit level. We can change that later if need be, but we needed
> a solution now. This country has very few POS types (2 or 3) and very few
> sites with POS (14-15). We have been having some confusion with categories
> for this country and are in the midst of cleaning some of that up so I
> didn't want to add more categories.
>
> I agree that if POSs are not consistent across all Org Units a data set
> categoriy could cause potential confusion or data entry errors.
>
> Creating POSs as Org Unit levels below facility level is how we do it in
> our Universal system. Some of our countries use other sub-facility Org Unit
> levels for other purposes in their DHIS instances and deal with POS in
> other ways. Data set category is one way but they also have a form where
> they just extract the data and assign it to the proper POS in other systems
> if need be -- not very efficient. I'm trying to determine how best to apply
> a consistent structure for a Universal configuration. For now we have mixed
> solutions in place.
>
> Does DHIS have a limit in regard to the number of Org Unit levels can be
> set up?
>
> *Laura E. Lincks*
> Database Manager/Developer
> ICAP - Columbia University
> Mailman School of Public Health
> 60 Haven Ave, Floor B1
> New York, NY 10032
> Tel: 212 304 7132
>
> On Tue, Oct 13, 2015 at 11:13 AM, Lars Helge Øverland <larshelge@xxxxxxxxx
> > wrote:
>
>> Hi Laura,
>>
>> let me ask:
>>
>> - What are your "point of services" ?
>> - How many?
>> - Are the point of services consistent across all facilities, or are
>> there lots of variation?
>>
>> If the point of services are few and consistent across most facilities I
>> would use data set categories.
>>
>> If they differ a lot (most likely) I would use org units.
>>
>>
>> regards,
>>
>> Lars
>>
>>
>>
>>
>>
>> On Mon, Oct 12, 2015 at 11:34 PM, Laura E. Lincks <
>> laura.lincks@xxxxxxxxxxxxxxxxx> wrote:
>>
>>> Hello all,
>>>
>>> I am interested in knowing how teams are setting up Point of Service
>>> sites in DHIS.
>>>
>>> I have thought of a couple of ways to do so:
>>>
>>>
>>> - Create an Organisational Unit level (POS) underneath facility
>>> level which will collect Testing and Counseling data via a data set which
>>> is set up to only be accessible to Org Units at this POS level
>>>
>>>
>>> - Create a data set for Testing and Counseling data and add a Point
>>> of Service Category to it. Data will be added at the Facility level: data
>>> set, reporting period AND Point of Service Type would be selected prior to
>>> adding data on the data entry screen.
>>>
>>>
>>> I imagine this is not an issue unique to us and am curious what others'
>>> solutions are.
>>>
>>> Thanks in advance.
>>>
>>> *Laura E. Lincks*
>>> Database Manager/Developer
>>> ICAP - Columbia University
>>> Mailman School of Public Health
>>> 60 Haven Ave, Floor B1
>>> New York, NY 10032
>>> Tel: 212 304 7132
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> http://www.dhis2.org <https://www.dhis2.org>
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help : https://help.launchpad.net/ListHelp
>
>
--
*This message and any attachments are subject to a disclaimer published at
http://www.hisp.org/policies.html#comms_disclaimer
<http://www.hisp.org/policies.html#comms_disclaimer>. Please read the
disclaimer before opening any attachment or taking any other action in
terms of this electronic transmission. If you cannot access the
disclaimer, kindly send an email to disclaimer@xxxxxxxx
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
this e-mail or opening any attachment you agree to be bound by the
provisions of the disclaimer.*
Follow ups
References