-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
DDC (direct data capture) support #253
Comments
@rkrenn We're implementing this using Apple's ResearchKit, it's working well so far. |
so you implemented a dedicated iOS app using ResearchKit framework. sounds like quite some work! |
Yes I got it working the other day. I need to refactor it majorly to sanitize it of anything specific to our trials (and get our app done first), but once that happens I'll put it up on our GH page, along with a few other things that we've set up for Phoenix. Basically I wrote a library that wraps the API calls and did a circular buffer from the ResearchKit survey module. |
In the future we're planning to pull data from the watches too and upload those into Phoenix, when we get there, I'll let you know and post that repo as well. |
after long discussions, we try to avoid implementin a (android/iOS) app for DDC.
instead, we will introduce a "Synchronize" service or job, which can be activated for a trial (one shot or periodic etc.).
this job is supposed to synchronize eCRF data between 2 Phoenix CTMS instances via Rest-API.
For DDC, the mobile device will then run a local Phoenix instance, which will synchronize with the central one.
The text was updated successfully, but these errors were encountered: