Hi all,
D-tree is working on a maternal health protocol that includes ANC, PNC, and
NNC in a single application, that will create separate linked cases for both
mother and child. We would like a limited amount of information shared
between the cases (e.g. mother's name, etc.). There are 2 use cases:
1) Mother is registered during ANC. At the first PNC visit, the case
loader is used to select the mother, and the health worker registers the
child (preloaded with some of the mother's info) and performs initial
postpartum and neonatal checkups. The child registration could be split out
from the PNC/NNC forms, but might be better in terms of usability if not
(still deciding on this).
2) Mother is not registered until the first PNC visit. Similar to above,
but can potentially package mother and child registrations together into the
same form.
In both situations, the question is how to work with 2 cases in a single
xform. In #2, we possibly create 2 cases in the xform (although can keep
separate if simpler). In #1 and #2, we pre-load mother's info, copy some of
it into child's case, then do referrals and case closing on either.
Depending on whether this is possible in CommCare and how difficult it is
(can use the formbuilder?), we can work to simplify our design as well.
Thanks,
Jon
Jon,
The notion of working with multiple cases in a single form is well supported
by CommCare's clients, but I don't believe that it's a well supported
operation in the HQ Application builder.
The current feasibility sets for CommCare's multiple case support are (in
order of how supported it is)
- Supported by HQ's Building Tools
- One case per module
- All actions (search-select/open/edit) are against the module's case type
- Supported by Client but not build tools
- Multiple case actions per-form (open one case, update another, open
multiple, etc)
- Using one case's preloaded case details in the case actions of another
case (IE: Open a child case which has a field containing the mother case's
case ID)
- Not supported by the client - Prospective work
- Tiered/Connected case search (IE: Select mother -> select child -> Enter
form)
- preloading multiple cases in one form
Is that enough information to work off of?
-Clayton
···
On Tue, Jun 21, 2011 at 2:03 AM, Jonathan Payne wrote:
Hi all,
D-tree is working on a maternal health protocol that includes ANC, PNC, and
NNC in a single application, that will create separate linked cases for both
mother and child. We would like a limited amount of information shared
between the cases (e.g. mother's name, etc.). There are 2 use cases:
1) Mother is registered during ANC. At the first PNC visit, the case
loader is used to select the mother, and the health worker registers the
child (preloaded with some of the mother's info) and performs initial
postpartum and neonatal checkups. The child registration could be split out
from the PNC/NNC forms, but might be better in terms of usability if not
(still deciding on this).
2) Mother is not registered until the first PNC visit. Similar to above,
but can potentially package mother and child registrations together into the
same form.
In both situations, the question is how to work with 2 cases in a single
xform. In #2, we possibly create 2 cases in the xform (although can keep
separate if simpler). In #1 and #2, we pre-load mother's info, copy some of
it into child's case, then do referrals and case closing on either.
Depending on whether this is possible in CommCare and how difficult it is
(can use the formbuilder?), we can work to simplify our design as well.
Thanks,
Jon
I think we will be able to go with option #2. We have already started
building this application in the form builder (you are actually helping
Peter troubleshoot this today). How would you recommend that we move this
application over from HQ to bitbucket (both xforms and application files)?
Jon
···
On Tue, Jun 21, 2011 at 6:39 PM, Clayton Sims wrote:
Jon,
The notion of working with multiple cases in a single form is well
supported by CommCare's clients, but I don't believe that it's a well
supported operation in the HQ Application builder.
The current feasibility sets for CommCare's multiple case support are (in
order of how supported it is)
- Supported by HQ's Building Tools
- One case per module
- All actions (search-select/open/edit) are against the module's case type
- Supported by Client but not build tools
- Multiple case actions per-form (open one case, update another, open
multiple, etc)
- Using one case's preloaded case details in the case actions of another
case (IE: Open a child case which has a field containing the mother case's
case ID)
- Not supported by the client - Prospective work
- Tiered/Connected case search (IE: Select mother -> select child -> Enter
form)
- preloading multiple cases in one form
Is that enough information to work off of?
-Clayton
On Tue, Jun 21, 2011 at 2:03 AM, Jonathan Payne paynejd@gmail.com wrote:
Hi all,
D-tree is working on a maternal health protocol that includes ANC, PNC,
and NNC in a single application, that will create separate linked cases for
both mother and child. We would like a limited amount of information shared
between the cases (e.g. mother's name, etc.). There are 2 use cases:
1) Mother is registered during ANC. At the first PNC visit, the case
loader is used to select the mother, and the health worker registers the
child (preloaded with some of the mother's info) and performs initial
postpartum and neonatal checkups. The child registration could be split out
from the PNC/NNC forms, but might be better in terms of usability if not
(still deciding on this).
2) Mother is not registered until the first PNC visit. Similar to
above, but can potentially package mother and child registrations together
into the same form.
In both situations, the question is how to work with 2 cases in a single
xform. In #2, we possibly create 2 cases in the xform (although can keep
separate if simpler). In #1 and #2, we pre-load mother's info, copy some of
it into child's case, then do referrals and case closing on either.
Depending on whether this is possible in CommCare and how difficult it is
(can use the formbuilder?), we can work to simplify our design as well.
Thanks,
Jon