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, Commuity Developers, Partners, Engineers, etc) and prioritizes based on feedback.
What changes priorities – We are agile and sometimes priorities change and for a number of reasons. For example, market demands can change, and so can we. If a community contribution is made (either a new feature or fix), this could be implemented more quickly. Partnership engagements (whether business or development) can also influence priority. 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.
2014 Road Map
|Printed Subject Casebook wth Provenance data||DONE|
|Schedule Next Event Automatically||DONE|
|Tokens / Parameterized links||DONE|
Q3 / Q4
|Connect a Study to Particpant Portal (PP)||IN PROGRESS|
|Participant Portal form Design||IN PROGRESS|
|Register Participant||IN BACKLOG|
|Particpant Portal View Form and Enter Data||IN BACKLOG|
|Send email to Participant on day of the Event||IN BACKLOG |
Participant Portal skip patterns
Show participant their schedule of to-be completed events and forms
|Participant portal rules-based validation||IN BACKLOG|
|Study Build Event Definition supports tagging form as Participant form||IN BACKLOG|
|Control status on import of Event Data||IN BACKLOG|
|Normalize the colletion 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|
|VAS for pain scale in Participant Portal||IN BACKLOG|
|Support use of rule with EmailAction for Participant Portal forms||IN BACKLOG|
|Medical Coding||IN BACKLOG|
|Built-in reporting||IN BACKLOG|