Starting with version 3.5, OpenClinica will begin to support the OpenRosa API, which will let you run Enketo, ODK Collect, or any of a number of OpenRosa-compliant data capture clients. If you’re not familiar with Enketo, ODK, or OpenRosa, here’s a primer. You can also see this blog post on how OpenClinica LLC is using Enketo and the OpenRosa API in its products.
To try it yourself:
- Build/install the latest OpenClinica code from github or distros
- Install an OpenRosa client, such as enketo or ODK Collect
- Add the property ‘PortalURL’ to datainfo.properties with the URL of the OpenRosa Client
PortalURL = http://www.example.com
- Issue a /formList request from the client to the OpenClinica:
- Currently supported methods include
Note: These APIs are still experimental, may not work at all, and are certainly not suitable for production use. OpenClinica Participate uses them but the hosted environment includes tools to ensure network security and robustness for production use that are not in the enketo package. We aim to eventually support OpenRosa API as part of the standard OpenClinica API and welcome feedback, testing, and code contriutions. In particular, this is still experimental because:
- Form submission will not really work because it does not create a study subject and study event where the data can go. This will be added in the near future.
- The API is not particularly secure. There is no production-quality authentication mechanism, other than to secure network access to known safe clients.
Alternative CRF Design models using XForm
- Configure your OpenClinica datainfo.properties to activate the Xform feature
- When adding a CRF or CRF version, select the ‘Upload as Xform’ tab
- Paste your OpenRosa-compliant XForm code into the textarea (you can use XLSForm to generate the XML from a spreadsheet)
- Upload any media files (images, videos, audio, etc) that you want to be embedded in the form
The primary use case right now is to support having images & video embedded in participant forms. It also enables you to use a growing list of features available in the enketo form engine that are not available in the traditional OpenClinica CRF engine. Your CRFs should still function in the traditional OpenClinica CRF engine, though they may not look as pretty or support all the features of a typical OpenClinica CRF because only a minimal amount of required metadata is parsed from the XForm into the OpenClinica form metadata model. Most of the display/layout information as well as any edit checks and skip logic is left only in the XForm.