Synchronizing OpenClinica Instances: Another Option for Using OpenClinica in Disconnected Settings

While tablet software maker Mi-Co is showcasing an integration of their Mi-Forms tablet-based forms software with OpenClinica that can be used in “offline” settings, elsewhere within the OpenClinica community, Raymond Omollo and Michael Ochieng have developed a separate option for using OpenClinica in settings without internet connectivity. Their method synchronizes multiple locally deployed instances of OpenClinica with a central OpenClinica database. Michael and Raymond recently presented their work at the OC13 conference. You can access their presentation slides here to see how they address key issues such as synchronization, back-ups, encryption, and user training.

Synchronization Flow Chart
Synchronization Flow Chart

While working for Drugs for Neglected Diseases initiative (DNDi), Michael and Raymond devised this approach for a WHO study of Buruli ulcers in West Africa (Ghana and Benin). The study, which is ongoing as of the date of this post, is a randomized controlled trial comparing the efficacy of 8 weeks treatment with clarithromycin and rifampicin versus streptomycin and rifampicin. It involves 430 subjects across 5 sites. The participating sites have limited or unstable internet connectivity, so a solution is needed that provided timely, auditable, and quality data entry given this constraint. A positive byproduct is enhancing the capacity of these disconnected sites to utilize EDC.

As they say, necessity is the mother of invention. And open source makes it easier for people to believe that what is necessary can in fact be accomplished. Kudos to Raymond and Michael for devising a solution that works for them. Perhaps it may work for others as well.  If you’d like to access the source code and documentation for their work, you can download these from the OpenClinica Tools and Tips page (scroll to bottom).  You can reach Raymond and Michael on the OpenClinica Developers mailing list: developers@openclinica.org.

– Ben Bauman

More About DNDi

Headquarted in Geneva, DNDi is a global organization that develops safe, effective, and affordable treatments for neglected diseases. The neglected diseases that DNDi tackles afflict many of the world’s poorest people (Malaria, Leishmaniasis, Chagas disease, Sleeping Sickness, Paediatric HIV, Filaria). DNDi’s goal to develop 11 to 13 new treatments by 2018. More at www.dndi.org.

Webinar: Tablet-based Offline EDC for OpenClinica – July 24

Offline Data Capture for OpenClinica – Demo of Mi-Forms Tablet Integration with OpenClinica

Date: July 24, 2013
Time: 2:00PM – 3:00PM EST

Attend this webinar to see, first hand, the use of tablets in offline, disconnected settings to capture and verify CRF data, and transmit them back into OpenClinica. See how the Mi-Forms/OpenClinica integration allows for easy design, deployment and verification of data at the point of capture.

RegisterButtonAt this webinar you’ll discover how to:

  • Enable multi-site offline data capture
  • Reduce query rates & speed trial completion
  • Cut clinical trial costs with mobile data capture

Presenters:
Ben Baumann, OpenClinica COO
Chris DiPierro, Mi-Co Director of Software Development
Gautham Pandiyan, Mi-Co VP of Sales & Marketing

OC13 Wrap Up – The Fruits of an Awesome Community

DSC02823It’s hard to believe that OpenClinica’s Global Conference, OC13 happened one week ago. What a memorable experience! Excellent sessions, great workshops, and an amazing Boston Harbor Dinner Cruise–here’s a recap:

P6210325The Highlights

Doug Bain delivered a insightful keynote presentation that challenged attendees on how to think about about patient engagement in today’s clinical trials. The discussion looked at the use of social media and the many systems and websites such as WebMD, PatientsLikeMe, etc., that are regularly referenced by patients and how this trend is setting new standards for communication.

DSC02816The multitude of OC13 sessions were delivered by an incredibly diverse background of presenters. With presenters from Africa,  Netherlands, Germany and Japan and wide representation from both industry and academia, a wide breadth of relevant, helpful and interesting topics were covered.

cruise1

Visit the conference page to view presentation slides.

I will be posting photos on Facebook highlighting the event. If you are not currently linked to our Facebook account, please “like” us and feel free to post and share your OC13 experiences.

IMG_0298

Thank you for attending and making OC13 a great event! Until next year!

– Rob

Doug Bain – OpenClinica Keynote address – Boston, 6/21/2013

Doug Bain - CEO and Co-Founder

Doug Bain is proud to be invited to give the keynote address at the annual OpenClinica User group meeting schedule for Friday 21st June in Boston – just prior to the annual DIA 2013.

“As a former developer of an open source EDC solution,  I have the greatest respect for the work completed, and success that OpenClinica have had in recent years.   It is very difficult to get an Open Source solution off the ground, and to gain a critical momentum to move the solution forward.   Despite working within a tightly regulated environment, with an audience often verging on the conservative when approaching technology,  the platform has evolved and extended with a solid user base.

One of the areas I will be focusing on during my keynote address is the field of Patient Engagement.  In the development of technologies, we have often fallen back to a role of attempting to replicate a paper world.  To some extent, we have done this with CRFs.  We have stuck the ‘e’ on the front to create eCRF’s…  but have we really changed how clinical trials function?

I look forward to meeting the OpenClinica community, and to discuss the opportunities that exist for reaching out and involving patients more intimately in research.”

Doug Bain, CEO, eClinicalHealth Limited.

Kool-Aid > Coffee

Over the last few weeks, the OpenClinica LLC team has spent a lot of time on future-based thinking. We have been taking an introspective approach and asking ourselves difficult questions. What kind of value should we deliver? What kind of community do we want to develop? What exciting possibilities exist for those who use our products? How do we get there and how do we start? Why are we spending time thinking about such heady things? Simply put, we are laser-focused on taking OpenClinica into the next generation.

As OC’s Software Applications Manager, I am uniquely positioned at the confluence of OpenClinica’s Ghosts of Software past, present, and future. In one sense, we are challenegd with a tangled web of brittle legacy code which, while stable, needs to be refactored. As such, we face the daily conundrum of “bandaid and patch” vs. “rip and replace” whenever we encounter unscalable and unsavory implementations. We literally make these decisions every day as we work on the new and improved Print CRF. The “New Print CRF” Kool-Aid has officially replaced our coffee machine and we are fully invested in a more modular architecture, which makes it hard to not dig in and REFACTOR ALL THE THINGS!

 

 

 

 

33636429

 

 

 

In addition to the above, we are in the midst of a tool suite change. We are moving away from Mantis as our IssueTracker and have been making the transition over to GreenHopper for JIRA for tracking our projects. Cal touched on this in his last email, as well. This process is taking more time than we originally anticipated, but for good reasons. First, we are busy getting 3.1.4 wrapped up and release ready. Second, we have been growing our staff and recently welcomed our new DevOps/Release engineering guru, Rob M. Rob has been carefully architecting a scalable role-based SSO solution for OpenClinica LLC’s internal tool suite, among many other things. Rob’s top priority is to make JIRA accessible and secure to allow for maximum visibility into our development process. We hope to continue growing our staff this summer to give us some much needed development horse power.

“Mantis seems to work fine, why change tools?” you may ask. JIRA provides vital project metrics and, more importantly, clear audit logs, traceability, and valuable integrations which help us cut down on documentation and release overhead and communicate more clearly with you, our community.

This is all a means to an end, friends! We realize we need to make the participation process easy, transparent, and engaging in order to foster a stronger community. Our community is what drives our innovation. You create our mission. You push our product forward. You are the reason I come to work every day. Just like you, I am passionate about what we are doing with OpenClinica, but passion doesn’t count for much without a proper bearing to know where the next step is. It is up to all of us to author our product’s story. Together, we are greater than the sum of our parts and together we have the power to change the world of clinical trial EDC.

OC13 Boston – Less than a month to go!

Please excuse our excitement! There’s less than one month to go for OC13 — if you haven’t registered, now is the time to do it. Come learn about the world’s most widely used clinical trial software. All are welcome — whether you’re new to OpenClinica or already a seasoned expert.

  • Improve your effectiveness
  • Hone your skills at workshops
  • Hear case studies and best practices
  • Establish valuable connections

We looking forward to seeing you in Boston!

Odyssey Cruise
After a jam-packed day of presentations, tutorials, case studies and workshops, enjoy a relaxing dinner and drinks aboard the Odyssey. Explore Boston from the vantage point of this historical harbor. Sign up.Odyssey Cruise Ship

The Open Source Way

The OpenClinica LLC team subscribes to a core set of values we do our best to live and work by in everything we do. They are primarily based around what it means to us to be open source. In the spirit of living by the first one (be radically open), here they are!

————————

At OpenClinica, we believe that a successful business depends on a successful and growing open source community. We aspire to be part of a community that is as accomplished as Linux, Drupal, and Apache. We want to achieve a similar level of innovation, quality, collaboration, and transparency. To travel this journey (and build a great product along the way!) we constantly strive to put in practice the following values:

  • Be radically open.
  • Release early and often. Not always production releases, but find ways to get code in the hands of users and testers.
  • With enough eyeballs, all bugs are shallow. Follows from release early and often.
  • Keep barriers low!! For distribution, evaluation, adoption, contribution. Question complexity. Some is necessary but favor simplicity where at all possible.
  • If you need it, then build it. Or find it (see next one).
  • Share and re-use other’s work. Avoid not-invented-here (NIH) syndrome. Somebody has done it before. Or, someone has done something similar but not thought of using it for what you need. Here’s where radical innovation and gigantic leaps forward happen.
  • Keep at it. There are no substitutes for persistence and perspiration.
  • Reward good ideas and good contributions. Let leadership and accountability thrive.
  • Maximize participants’ strengths.
  • Avoid community anti-patterns.
  • Make it yours. You are your personality.
  • Most of all, find your passion and let your love for what you do shine through!

There are hundreds, if not thousands of articles, presentations, and academic papers on what makes open source communities work. Here are a few that best articulate the values described above:

Eric Raymond, The Cathedral and the Bazaar. It all started here. Read the summary or the full paper.
Matthew Mascord, How to Build an Open Source Community
Joel Dietz, How to build a vibrant open source community
David Neary, Open Source community building: a guide to getting it right
Jonathan Corbet, How to destroy your community
David Nalley, Leadership in open source communities
Stephen Walli, Open Source: No one is working for free
Ben Baumann, OpenClinica Community Surpasses 10,000 Members …and oh yeah, what is this open source thing?

 

 

A Fresh Perspective on Upcoming OpenClinica Events

GrassGuy_KickedBackWhat a great time of year! The sun is out and the flowers, trees, and grass are blooming. There is no better time to spread the news about our fresh perspective on electronic data capture.

What are we up to?

  • We’ll be at SCT – Society for Clinical Trials 34th Annual Meeting in Boston next week, talking with over 650 professionals dedicated to the design, conduct and analysis of clinical trials.
  • Going to Shanghai! We will be holding our Central User training in Shanghai, China from May 28-31. This follows the DIA China Annual meeting, where OpenClinica was featured in numerous presentations.
  • We hope to see you at the OC13 Global Conference in Boston on June 21. We have an exciting lineup of great workshops, sessions, demos and training classes–there is something useful for everyone. We are really looking forward to the Boston Harbor Dinner Cruise for a chance to kick back after the event and visit with our OpenClinica friends. Sign up! You don’t want to miss this.
  • Capping off our spring events and immediately following OC13 is DIA 2013 in Boston, June 23-27. We are bracing ourselves for 7,000 life science professionals converging on our booth to take in our fresh perspective and enjoy some espresso, demonstrations and some very competitive games of cornhole (yes, this is a real game!). We have some great giveaways and prizes in an outdoor-themed space. Will you be there? If so, stop by Booth #122 and have some fun.

OpenClinica Next Generation

EnterpriseDo you want to boldly go where OC is going? Engage! Check out Nick Sophino’s blog on next generation OpenClinica. This is where to find information on prototype design and development for OpenClinica Next Generation. Nick is going to be showing off this work at OC13 so be sure to check out his session!

Throw a few steaks on the grill and kick back and enjoy the season. And, remember to always look for a fresh perspective.

Warm Regards,
Rob

New OpenClinica Developer Release: Revamped Print Module

A new developer release is available for OpenClinica. While it contains a number of significant improvements, one of the more fundamental changes is a reconstruction of OpenClinica’s print CRF functionality. To date, all printable screens resembled the existing web form interface for the eCRF, whereas now, this engine has been completely redesigned to more closely follow industry standard for printable views of web forms.

Why This Matters To Developers

Ok, I get it. You are a developer, so what’s the big deal about being able to send CRFs to the printer?  It is the technology behind this improvement that will hopefully catch your attention. Important changes have been occurring in the sphere of web apps, and I don’t mean just a sprinkling of AJAX here and there along with a UI that looks like Facebook. The real revolution goes much deeper.

Setting a precedent for OpenClinica: Completely Decoupled Client Technology using Web Services

The notion is simple. Create a browser-based client with the same decoupled technology that a iOS or Android mobile client requires. In plain English, this means that only data is sent back and forth between the client and the server. Just as is expected with a native OS mobile client, the browser-based client never relies on the server to generate or send any part of itself except when the URL is first accessed and loaded into the browser. The client is therefore completely decoupled and can be in complete control of their own state. This results in a more reliable, speedier, feature-packed, and easier to maintain platform for both the client and server. Another way to put it … in the not too distant future, our 400 or so JSP pages will be replaced by one or two main HTML templates and about a dozen small (less than 100 lines each) HTML component files.  But for now, take a look at our printable CRF design as an example of the way forward.

Getting to the Point: REST, JSON, JQuery, HTML, and CSS

What follows is a description of the processing path that starts with a REST URL and ends with a printable CRF.

  1. A user will click on a print icon that is part of many of the CRF view forms. The RESTful URL referenced in the link will be in the form of rest/metadata/html/print/{StudyOID}/{StudyEventOID}/{FormDefOID}. Using this combination, a wildcard asterisk character (*) can be placed as a specifier for all studies, all study events, and all CRFs, respectively.
  2. The first path element in the URL named “rest,” indicates that this is handled by our implementation of org.akaza.openclinica.web.restful.ODMMetadataRestResource, our Jersey JAX-WS controller servlet. The “metadata” in the second path element indicates that is for metadata only and no clinical data will be transmitted. The “html” in the third path element indicates that this will result in a rather simple JSP page at /WEB-INF/jsp/printcrf.jsp. This JSP page is the container for the JQuery code that will make a second REST call to the back-end to retrieve the CDISC ODM in JSON form and is also the container for the Javascript and JQuery code that converts the information contained in the ODM JSON into an HTML DIV element with the rendered printable CRF.
  3. The AJAX call that the Javascript method getPrintableContent() in js/app.js references is a URL in the form of rest/metadata/json/view/{StudyOID}/{StudyEventOID}/{FormDefOID}. It is the 3rd path element of “json” which indicates that the same ODMMetadataRestResource servlet will now fetch the relevant ODM XML metadata, convert it to JSON, and send it back to the callback portion of getPrintableContent(). In the callback portion, a call to app_odmRenderer.renderPrintableStudy() kicks off the process by which JavaScript inspects the JSON ODM object returned by the server and builds a DOM element that represents the portion of the metadata that is meant to be displayed as one or more CRFs.
  4. The DOM HTML is rendered with the help of JQuery Templates. This allows HTML fragments such as template/print_item_def.html, which are initially loaded in memory, to be combined with certain extracted key/value pairs to render an individual or list of components.

What’s on the Horizon

This first release extends to printing blank CRFs. Then, we will work to extend this to handle printing CRFs containing clinical data and very large printable form sets. The process described above will be similar, with the exception that all large documents, typically over 100 pages long, will be rendered using a Java rendering class that builds off of Velocity templates. The resulting server-side HTML page will be converted to a downloadable PDF.

– Nick Sophinos, Senior Developer

Click here for Developer Release