Referral in Commcare 2.0

i am building an app which i want to have cases and referrals, but since
Commcare 2.0 doesn’t support referrals is there another way which i can use
for referrals?

Hi Ralph,

You’re right that 2.0 does not yet support referrals, but there are a few
good workarounds. I’m curious to hear what other users have come up with,
but here are a few tricks we’ve learned:

Workaround 1: Child Cases

Many partners open a “child case” rather than a referral. This child case
is different from a referral in that:
a) you can open the child case into a different case list
b) the child case will not close automatically when the parent case closes.
c) if you want any data from the parent to be saved to the child case, you
have to do this explicitly in the case configuration when you open the
child case. The child case also cannot update the case properties of the
parent case.

You can open a “referral” child case into a different “referrals” module,
which contains forms associated with referrals.

Advantage: on the data side it is easy to see and evaluate referrals, since
they are tracked as separate cases
Disadvangate: If you close the parent case, the referral child case will
still be open. Once the child case is created, it cannot update its
parents’ case properties (and vice versa)

Workaround 2: Form Display Condition

··· * * You put a display condition on a form - just like display conditions on questions - that sets the form to display based on the values of case properties. You can then include referral followup forms right in the same module, and set them to display only when, for example, the case property referral = 'yes'.

Advantage: Easy to use, doesn’t add other modules to your application
Disadvantage: Hard to evaluate referrals historically, since they are not
tracked as separate cases, but are just a flag in the case.

see documentation here:
https://confluence.dimagi.com/display/commcarepublic/Common+Logic+and+Calculations#CommonLogicandCalculations-DisplayLogicforForms
*
*
Workaround 3: Case List Filtering
*
*
You can put a filter on a case list so that it only shows cases based on
the value of their case properties. Similar to workaround 2, you would have
a “referral” case property in the case. You would then create a separate
"referral" module that was filtered to show cases only if the case property
referral = ‘yes’. Optionally, you could set your main followup module to
filter out referred cases, only showing cases if the case property referral
does not equal ‘yes’.

Advantages: Visually separates out referred cases from regular cases, good
if you want to have a completely separate workflow for referrals
Disadvantage: Hard to evaluate referrals historically, since they are not
tracked as separate cases, but are just a flag in the case.

see documentation here:
https://confluence.dimagi.com/display/commcarepublic/Case+List+and+Case+Detail+View+Configuration

I know this is a lot of information, so feel free to ask followup
questions! Let us know if you come up with other ideas too.

Thanks,
Amelia

On Wed, Mar 13, 2013 at 10:44 AM, Ralph kawatira rkfraaz@gmail.com wrote:

i am building an app which i want to have cases and referrals, but since
Commcare 2.0 doesn’t support referrals is there another way which i can use
for referrals?


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Dear Amelia,

These are wonderful suggestions! I’m working on developing a CommCare app
that manages referrals for a network of service providers. This means that
if we have organizations A to E, a client could access services at A and
then (if necessary) receive a referral for additional services at
organization B, C, D, and/or E. I cannot imagine that multiple referrals
would be likely, but we have to have the option. It seems that the
situations below are for one-way referrals (i.e., A always refers to B).
Any thoughts on how to best set up an app to deal with the situation that
I have?

I’m happy to add more information and can also send our a general request
to the group.

Thanks!!

Clinton

··· On Wednesday, March 13, 2013 7:55:24 PM UTC+2, Amelia Sagoff wrote: > > Hi Ralph, > > You're right that 2.0 does not yet support referrals, but there are a few > good workarounds. I'm curious to hear what other users have come up with, > but here are a few tricks we've learned: > > *Workaround 1: Child Cases* > > Many partners open a "child case" rather than a referral. This child case > is different from a referral in that: > a) you can open the child case into a different case list > b) the child case will not close automatically when the parent case closes. > c) if you want any data from the parent to be saved to the child case, you > have to do this explicitly in the case configuration when you open the > child case. The child case also cannot update the case properties of the > parent case. > > You can open a "referral" child case into a different "referrals" module, > which contains forms associated with referrals. > > Advantage: on the data side it is easy to see and evaluate referrals, > since they are tracked as separate cases > Disadvangate: If you close the parent case, the referral child case will > still be open. Once the child case is created, it cannot update its > parents' case properties (and vice versa) > > *Workaround 2: Form Display Condition* > > You put a display condition on a form - just like display conditions on > questions - that sets the form to display based on the values of case > properties. You can then include referral followup forms right in the same > module, and set them to display only when, for example, the case property > referral = 'yes'. > > Advantage: Easy to use, doesn't add other modules to your application > Disadvantage: Hard to evaluate referrals historically, since they are not > tracked as separate cases, but are just a flag in the case. > > see documentation here: > https://confluence.dimagi.com/display/commcarepublic/Common+Logic+and+Calculations#CommonLogicandCalculations-DisplayLogicforForms > > *Workaround 3: Case List Filtering* > > You can put a filter on a case list so that it only shows cases based on > the value of their case properties. Similar to workaround 2, you would have > a "referral" case property in the case. You would then create a separate > "referral" module that was filtered to show cases only if the case property > referral = 'yes'. Optionally, you could set your main followup module to > filter out referred cases, only showing cases if the case property referral > does not equal 'yes'. > > Advantages: Visually separates out referred cases from regular cases, good > if you want to have a completely separate workflow for referrals > Disadvantage: Hard to evaluate referrals historically, since they are not > tracked as separate cases, but are just a flag in the case. > > see documentation here: > https://confluence.dimagi.com/display/commcarepublic/Case+List+and+Case+Detail+View+Configuration > > I know this is a lot of information, so feel free to ask followup > questions! Let us know if you come up with other ideas too. > > Thanks, > Amelia > > > > On Wed, Mar 13, 2013 at 10:44 AM, Ralph kawatira <rkf...@gmail.com wrote: > >> i am building an app which i want to have cases and referrals, but since >> Commcare 2.0 doesn't support referrals is there another way which i can use >> for referrals? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Hi Clinton,

I think any of these workarounds could work for you.

Workaround 1: You can open multiple child cases of different case types to
represent the different kinds of referrals. In your application, you would
have 1 module for each organization. The visit form in the module for
organization A can conditionally open a child case for each of the
organization modules if a referral to that organization was given.

Workaround 2 and 3: Each patient case has a case property for each
organization representing whether or not they have been referred to that
organization. If a referral is given to organization B, the case property
B_referral will be set to yes, and the same for C, D, etc. You can use form
display conditions or case filtering on these case properties to determine
whether these patients appear for the other organizations.

My answer was a bit abstract, but hopefully it was helpful! Let me know if
you have any followup questions.

Thanks,
Amelia

··· On Mon, Feb 10, 2014 at 10:17 AM, Clinton Sears wrote:

Dear Amelia,

These are wonderful suggestions! I’m working on developing a CommCare app
that manages referrals for a network of service providers. This means that
if we have organizations A to E, a client could access services at A and
then (if necessary) receive a referral for additional services at
organization B, C, D, and/or E. I cannot imagine that multiple referrals
would be likely, but we have to have the option. It seems that the
situations below are for one-way referrals (i.e., A always refers to B).
Any thoughts on how to best set up an app to deal with the situation that
I have?

I’m happy to add more information and can also send our a general request
to the group.

Thanks!!

Clinton

On Wednesday, March 13, 2013 7:55:24 PM UTC+2, Amelia Sagoff wrote:

Hi Ralph,

You’re right that 2.0 does not yet support referrals, but there are a few
good workarounds. I’m curious to hear what other users have come up with,
but here are a few tricks we’ve learned:

Workaround 1: Child Cases

Many partners open a “child case” rather than a referral. This child
case is different from a referral in that:
a) you can open the child case into a different case list
b) the child case will not close automatically when the parent case
closes.
c) if you want any data from the parent to be saved to the child case,
you have to do this explicitly in the case configuration when you open the
child case. The child case also cannot update the case properties of the
parent case.

You can open a “referral” child case into a different “referrals” module,
which contains forms associated with referrals.

Advantage: on the data side it is easy to see and evaluate referrals,
since they are tracked as separate cases
Disadvangate: If you close the parent case, the referral child case will
still be open. Once the child case is created, it cannot update its
parents’ case properties (and vice versa)

Workaround 2: Form Display Condition

You put a display condition on a form - just like display conditions on
questions - that sets the form to display based on the values of case
properties. You can then include referral followup forms right in the same
module, and set them to display only when, for example, the case property
referral = ‘yes’.

Advantage: Easy to use, doesn’t add other modules to your application
Disadvantage: Hard to evaluate referrals historically, since they are not
tracked as separate cases, but are just a flag in the case.

see documentation here: https://confluence.dimagi.com/display/
commcarepublic/Common+Logic+and+Calculations#CommonLogicandCalculations-
DisplayLogicforForms

Workaround 3: Case List Filtering

You can put a filter on a case list so that it only shows cases based on
the value of their case properties. Similar to workaround 2, you would have
a “referral” case property in the case. You would then create a separate
"referral" module that was filtered to show cases only if the case property
referral = ‘yes’. Optionally, you could set your main followup module to
filter out referred cases, only showing cases if the case property referral
does not equal ‘yes’.

Advantages: Visually separates out referred cases from regular cases,
good if you want to have a completely separate workflow for referrals
Disadvantage: Hard to evaluate referrals historically, since they are not
tracked as separate cases, but are just a flag in the case.

see documentation here: https://confluence.dimagi.com/display/
commcarepublic/Case+List+and+Case+Detail+View+Configuration

I know this is a lot of information, so feel free to ask followup
questions! Let us know if you come up with other ideas too.

Thanks,
Amelia

On Wed, Mar 13, 2013 at 10:44 AM, Ralph kawatira rkf...@gmail.comwrote:

i am building an app which i want to have cases and referrals, but since
Commcare 2.0 doesn’t support referrals is there another way which i can use
for referrals?


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.