Are you managing a ResearchKit app and website for the same study

The COPD Foundation currently has a web portal where participants can join the COPD PPRN (Patient Powered Research Network) research study – http://www.copdpprn.org. When ResearchKit was released we decided we were going to develop a ResearchKit app for the COPD PPRN to target iOS devices. Our app is called stopCOPD. During our initial analysis and requirements gathering it was decided that we wanted to keep our web portal to allow individuals to participate in our study through a traditional website and develop our ResearchKit app as an ‘extension’ of the COPD PPRN, rather than treat it as a separate entity. In other words, we wanted to provide a seamless user experience between the two. Same data repository, same authentication, users can switch between the two with the same account, etc.

My question is - has anyone else faced this scenario? If so, I’m curious to hear more about how you have addressed managing both a website and an app for the same research study?

Up vote post of Vinny M. Down vote post of Vinny M.
520 views
Posted by
Vinny M.
Reply
Add a Comment

Replies

What in particular is the concern in terms of managing both?


One thing that would make it easier is to have the same backend for storing and managing the data. Have the app feed into the same place as the website does. If your website portal is already live and working, when you roll out the app, that's a good time to update the portal to make sure they match in terms of functionality. Alignment matters if you want to remain sane 🙂


From a regulatory standpoint, you'll have to demonstrate that they are both the same an give the IRB evidence of that. Same goes for if you change something in one of them; you'll likely have to change it in both.

Posted by
JeremyBlock
Up vote reply of JeremyBlock Down vote reply of JeremyBlock
Add a Comment