New Commcare Adaptor Doc #580
Conversation
christad92
requested review from
mtuchi,
aleksa-krolls,
hunterachieng,
ritazagoni and
AishaHassen
| 8. Exclude any (eg. test) users | ||
|
|
||
|  | ||
|
|
||
| ## Data Forwarding and OpenFn Workflow Design |
There was a problem hiding this comment.
@christad92 i think some of these information might be useful to someone. I will suggest we turn them into a community post and it's okay if we can have a banner saying this is outdated information.
There was a problem hiding this comment.
Added back for now until we figure out where to put this info
There was a problem hiding this comment.
@christad92 looks good to me, I left one suggestion if we could create a community post using the old content in Integration tips & Unique Identifiers
| data to and from CommCare HQ. | ||
| - Syncing data from CommCare to DHIS2: This integration allows for seamless | ||
| transfer of health data collected in CommCare to DHIS2 for comprehensive | ||
| analysis, visualization and reporting. | ||
|
|
There was a problem hiding this comment.
Suggestions to add:
- Syncing data from CommCare to a Shared Health Repository: Health facilities that use CommCare as an EMR can integrate with national shared health repositories to send individual patient data.
Thanks! We should build ID management in CommCare into a different tutorial/community post. Please can you approve the PR if everything is good for you? @mtuchi |
update commcare docs, add more dimagi docs links, add data model diagram (#586)
|
hey @christad92 please do not delete any content from old adaptor docs (e.g., info on unique identifiers) unless you immediately move it somewhere else, otherwise we risk forgetting about it. I've added back this content for now, because I don't want to lose valuable content and learnings. Let's please discuss the question on "where to put other helpful integration tips" in our next adaptor sync. |
New adaptor overview documentation