ODK and repeated household surveys

We are looking to use ODK for a series of household surveys, where we
would visit the same household multiple times.

It wasn't clear to me whether ODK could manage the repeat visits with
some information about the household retained, or whether every visit
was treated as a clean slate.

Does anyone have any insight into this

Thanks

Daniel

One approach to handle this is to give each household you visit a
unique ID when you first visit them, then when you revisit the
household you enter their ID into the survey.

Actually implementing this is incredibly difficult. Curious to hear
from anyone with experience implementing something like this with ODK.

Andrew

··· On Wed, Mar 2, 2011 at 10:56 PM, dreidpath wrote: > We are looking to use ODK for a series of household surveys, where we > would visit the same household multiple times. > > It wasn't clear to me whether ODK could manage the repeat visits with > some information about the household retained, or whether every visit > was treated as a clean slate. > > Does anyone have any insight into this > > Thanks > > Daniel > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Daniel,

We've rolled our CommCare workflow (used for tracking patients and other
longitudinal entities like households) onto Android using ODK as the
backend. Essentially CommCare would let you create users for each data
collector, have each one register the household, and then search and select
households before entering a survey about them.

CommCare also uses encrypted secure storage on the device and lets you track
information by Users.

A few downsides to using CommCare compared to stock ODK are

  1. It's pretty alpha. We can only offer somewhat limited support
  2. You'd have to "build" your application through our server,
    www.commcarehq.org (or read the spec and roll out the config on your own).
  3. CCODK is running against a slightly older build of ODK. We had to roll a
    custom one to ensure that the encryption works correctly, and we're working
    on catching up with stock ODK. Not there yet, though.

In theory, you should be able to use any existing ODK xforms that you've
designed, or you should be able to use the form designer built into
commcarehq.

Let me know if you're interested. I can send more details to the list.

-Clayton

··· On Wed, Mar 2, 2011 at 10:56 PM, dreidpath wrote:

We are looking to use ODK for a series of household surveys, where we
would visit the same household multiple times.

It wasn't clear to me whether ODK could manage the repeat visits with
some information about the household retained, or whether every visit
was treated as a clean slate.

Does anyone have any insight into this

Thanks

Daniel

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Daniel,

CommCare ODK is up publicly for you to test out. You can follow the
instructions here:

https://confluence.dimagi.com/display/commcarepublic/Installing+CommCareODK

to give it a shot. You'll need to create a CommCare domain and create an
application in the designer to test it out.

-Clayton

··· On Thu, Mar 3, 2011 at 11:11 AM, Clayton Sims wrote:

Daniel,

We've rolled our CommCare workflow (used for tracking patients and other
longitudinal entities like households) onto Android using ODK as the
backend. Essentially CommCare would let you create users for each data
collector, have each one register the household, and then search and select
households before entering a survey about them.

CommCare also uses encrypted secure storage on the device and lets you
track information by Users.

A few downsides to using CommCare compared to stock ODK are

  1. It's pretty alpha. We can only offer somewhat limited support
  2. You'd have to "build" your application through our server,
    www.commcarehq.org (or read the spec and roll out the config on your
    own).
  3. CCODK is running against a slightly older build of ODK. We had to roll a
    custom one to ensure that the encryption works correctly, and we're working
    on catching up with stock ODK. Not there yet, though.

In theory, you should be able to use any existing ODK xforms that you've
designed, or you should be able to use the form designer built into
commcarehq.

Let me know if you're interested. I can send more details to the list.

-Clayton

On Wed, Mar 2, 2011 at 10:56 PM, dreidpath dreidpath@gmail.com wrote:

We are looking to use ODK for a series of household surveys, where we
would visit the same household multiple times.

It wasn't clear to me whether ODK could manage the repeat visits with
some information about the household retained, or whether every visit
was treated as a clean slate.

Does anyone have any insight into this

Thanks

Daniel

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Clayon,

Thanks for sharing this. It looks very exciting and I look forward to trying
it out.

One of the things, that excites me about ODK Clinic is the potential ability
to download a list of things and then link them to a form. Since this is a
pretty abstract and useful idea, I'm hoping this feature eventually finds
its way into ODK collect.

I realize ODK Clinic is currently under development but one of the earlier
constraints is that ODK Clinic really only supported lists generated by a
java binary coming from OpenMRS. Long term it would be exciting if this
could be done via simple xml/json. I realize too that this is part of the
openrosa spect that still needs to be defined.

With the commcare ODK client how did you address this issue? Are you using
java binaries? Since CommCare HQ is python/django I'm hoping you might have
come up with something a bit more flexible that would allow us to write
different backends for.

Thanks,

Matt

··· On Thu, Mar 10, 2011 at 12:28 PM, Clayton Sims wrote:

Daniel,

CommCare ODK is up publicly for you to test out. You can follow the
instructions here:

https://confluence.dimagi.com/display/commcarepublic/Installing+CommCareODK

to give it a shot. You'll need to create a CommCare domain and create an
application in the designer to test it out.

-Clayton

On Thu, Mar 3, 2011 at 11:11 AM, Clayton Sims csims@dimagi.com wrote:

Daniel,

We've rolled our CommCare workflow (used for tracking patients and other
longitudinal entities like households) onto Android using ODK as the
backend. Essentially CommCare would let you create users for each data
collector, have each one register the household, and then search and select
households before entering a survey about them.

CommCare also uses encrypted secure storage on the device and lets you
track information by Users.

A few downsides to using CommCare compared to stock ODK are

  1. It's pretty alpha. We can only offer somewhat limited support
  2. You'd have to "build" your application through our server,
    www.commcarehq.org (or read the spec and roll out the config on your
    own).
  3. CCODK is running against a slightly older build of ODK. We had to roll
    a custom one to ensure that the encryption works correctly, and we're
    working on catching up with stock ODK. Not there yet, though.

In theory, you should be able to use any existing ODK xforms that you've
designed, or you should be able to use the form designer built into
commcarehq.

Let me know if you're interested. I can send more details to the list.

-Clayton

On Wed, Mar 2, 2011 at 10:56 PM, dreidpath dreidpath@gmail.com wrote:

We are looking to use ODK for a series of household surveys, where we
would visit the same household multiple times.

It wasn't clear to me whether ODK could manage the repeat visits with
some information about the household retained, or whether every visit
was treated as a clean slate.

Does anyone have any insight into this

Thanks

Daniel

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Matt,

All data served up to CommCare ODK follows the transactional XML
specifications outlined on our bitbucket wiki at:
https://bitbucket.org/commcare/commcare/wiki/Home . Specifically "Patient"
data is fed down to the phone as CaseXML transactions, which are formatted
for display by the Suite file's blocks, and then used inside of the
individual XForms.

It's easy to create a server which can feed data down to a CommCare ODK (or
CommCare J2ME, they share the same XML specifications for Application and
User Data) client as long as that data is served up at a (generally digest
authenticated) GET url in the CaseXML transactional format on the wiki.

The data coming down currently is very, very limited, basically a list of
flat tuples. This has worked well for our representations of patients and
households, given the limited amount of data needed by our users to select
patients and provide context for the various XForms.

-Clayton

··· On Fri, Mar 11, 2011 at 2:56 PM, Matt Berg wrote:

Clayon,

Thanks for sharing this. It looks very exciting and I look forward to
trying it out.

One of the things, that excites me about ODK Clinic is the potential
ability to download a list of things and then link them to a form. Since
this is a pretty abstract and useful idea, I'm hoping this feature
eventually finds its way into ODK collect.

I realize ODK Clinic is currently under development but one of the earlier
constraints is that ODK Clinic really only supported lists generated by a
java binary coming from OpenMRS. Long term it would be exciting if this
could be done via simple xml/json. I realize too that this is part of the
openrosa spect that still needs to be defined.

With the commcare ODK client how did you address this issue? Are you using
java binaries? Since CommCare HQ is python/django I'm hoping you might have
come up with something a bit more flexible that would allow us to write
different backends for.

Thanks,

Matt

On Thu, Mar 10, 2011 at 12:28 PM, Clayton Sims csims@dimagi.com wrote:

Daniel,

CommCare ODK is up publicly for you to test out. You can follow the
instructions here:

https://confluence.dimagi.com/display/commcarepublic/Installing+CommCareODK

to give it a shot. You'll need to create a CommCare domain and create an
application in the designer to test it out.

-Clayton

On Thu, Mar 3, 2011 at 11:11 AM, Clayton Sims csims@dimagi.com wrote:

Daniel,

We've rolled our CommCare workflow (used for tracking patients and other
longitudinal entities like households) onto Android using ODK as the
backend. Essentially CommCare would let you create users for each data
collector, have each one register the household, and then search and select
households before entering a survey about them.

CommCare also uses encrypted secure storage on the device and lets you
track information by Users.

A few downsides to using CommCare compared to stock ODK are

  1. It's pretty alpha. We can only offer somewhat limited support
  2. You'd have to "build" your application through our server,
    www.commcarehq.org (or read the spec and roll out the config on your
    own).
  3. CCODK is running against a slightly older build of ODK. We had to roll
    a custom one to ensure that the encryption works correctly, and we're
    working on catching up with stock ODK. Not there yet, though.

In theory, you should be able to use any existing ODK xforms that you've
designed, or you should be able to use the form designer built into
commcarehq.

Let me know if you're interested. I can send more details to the list.

-Clayton

On Wed, Mar 2, 2011 at 10:56 PM, dreidpath dreidpath@gmail.com wrote:

We are looking to use ODK for a series of household surveys, where we
would visit the same household multiple times.

It wasn't clear to me whether ODK could manage the repeat visits with
some information about the household retained, or whether every visit
was treated as a clean slate.

Does anyone have any insight into this

Thanks

Daniel

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en