Here you can acces information about existing, as well as upcoming, OpenClinica releases.
The Product Vision Statement is an important document that helps guide our development
How we work – We use agile software development practices. This means that while we do keep a “long term” road map, we are always adjusting to deliver high value product(s) for our users. We break up major pieces of functionality into Minimally Releasable Features (MRFs) which we prioritize and work on in order of priority.
How we prioritize – The product owner gets feedback from all stakeholders (e.g. Enterprise customers, Community Users, Community Developers, Partners, Engineers, etc) and prioritizes based on feedback.
What changes priorities – The best way to get a feature into OpenClinica is to build it and share your code via GitHub. If it’s good we’ll get it in right away. Even if you can’t write the code, if there is something that you feel passionate about and want to engage with us, please do (the OpenClinica forums are great place to start)!
How often we prioritize – This is something we do on a perpetual basis (day to day). Although the top priorities are less likely to change (especially the ones currently being worked on), if there is a compelling reason to change them, we can. The further out a feature is the less certain its priority and release date are.
2015 Road Map
Q1
Feature Name (Click to view related stories) | Description | Status |
| OC-5730 PForm Design and View | A study designer can build a CRF and view it as a participant form. | DONE |
| OC-5741 Connect a Study to Participate | A study designer can configure a study designer to be a particpant study which sends a request to Participate. An account manager at OpenClinica can approve requests. | DONE |
| OC-5731 Enter data into PForm | A participant can enter data into a form and save it. Saved data is saved in OpenClinica and is available immediately. | DONE |
| OC-6082 User account management for Admins OCParticipate | Clinical Research Coordinators / Data Entry persons and Investigators can log into Participate with their username and password. Admins can log into participate and perform Administrative tasks. | DONE |
| OC-6026 CRC can connect a Participant | A CRC that logs into Participate can search by SSID for a subject that exists in their OpenClinica study. If the subject exists they can connect the participant. | DONE |
| OC-6131 SMS Code for Participant Login | Connecting a participant generates a code that is sent in SMS by which the partipant can “log in” and start entering data. | DONE |
| OC-6141 CRC goes to URL for a Participate study to log in | CRCs will access their Participate study via a Participate study URL. From here they will log in and can connect participants. | DONE |
| OC-6160 Securing APIs | The APIs used for sending and receiving data must be secured. | DONE |
| OC-5738 Study Build event Definition supports tagging form as PForms | A study designer can tag CRFs as participant forms. Tagging allows the designer to specify which forms will be completed by participants and which forms are not completed by participants within a given event. | DONE |
Q2
Feature Name (Click to view related stories) | Description | Status |
OC-5218 Control status on Import of Event data | Importing of data automatically sets the status of the event CRF to complete. It must be possible to define what the status should be. |
Q3 / Q4
| High Level Feature/ Functionality: | Minimally Releaseable Feature (MRF): | Status: |
2016 Road Map and beyond