Here you can acces information about existing, as well as upcoming, OpenClinica releases.
The 2014 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.
2014 Road Map
Q1
| Printed Subject Casebook wth Provenance data | DONE |
Q2
| Schedule Next Event Automatically | DONE |
| Tokens / Parameterized links | DONE |
Q3 / Q4
The primary focus of the next 2 releases over Q3 & Q4 are focused on our ePRO and portal solution, known as Participant Portal (PP). While we may address other issues, bug fixes or other minor functionality, Participant Portal is the major new functionality that we are focused on.
| High Level Feature/Functionality: | MRF: | Status: |
| PP | Connect a Study to Participant Portal (PP) | IN PROGRESS |
| PP | Participant Portal form Design | IN PROGRESS |
| PP | Register Participant | IN BACKLOG |
| PP | Participant Portal View Form and Enter Data | IN BACKLOG |
| PP | Send email to Participant on day of the Event | IN BACKLOG |
PP | Participant Portal skip patterns | IN BACKLOG |
| PP | Participant portal rules-based validation | IN BACKLOG |
| PP | Study Build Event Definition supports tagging form as Participant form | IN BACKLOG |
| PP | Control status on import of Event Data | IN BACKLOG |
| Internationalization | Normalize the collection of date-time stamps regardless of where DB or Tomcat server are hosted | IN BACKLOG |
2015 Road Map, and beyond
| Send email to participant on day of event | IN BACKLOG |
| Read only role & Sub-investigator role | IN BACKLOG |
| Send email to participant on day of event | IN BACKLOG |
| VAS for pain scale in Participant Portal | IN BACKLOG |
| Support use of rule with EmailAction for Participant Portal forms | IN BACKLOG |
| Integration with CTMS | |
| Adjudication Module | |
| Investigator Portal | IN BACKLOG |
| Medical Coding | IN BACKLOG |
| Built-in reporting | IN BACKLOG |
| Configurable user roles | IN BACKLOG |