Announcing OpenClinica 3.9!

Hi Everyone,

We are SO EXCITED to announce OpenClinica 3.9

We have some remarkable new features which include
OpenClinica Randomize (that’s right - randomization)
Edit capabilities in Participate

We also have loads of enhancements and fixes in Rules!

Click for OpenClinica 3.9 release notes.

Cheers!
Alicia
«1

Comments

  • kristiakkristiak Posts: 1,248 ✭✭✭
    via Email
    Hi Alicia,

    This is very good news indeed, Will take a look tomorrow.
  • skwalerskwaler Posts: 49
    Hi,

    Well done guys. can we have some more details of OpenClinica Randomize
  • rrittbergrrittberg Posts: 109 admin
    Hi @skwaler, more details coming very soon. Keep an eye on openclinica.com. Rob
  • skwalerskwaler Posts: 49
    Any news on the Randomize module?
  • rrittbergrrittberg Posts: 109 admin
    Hi @skwaler. More information on Randomize is available at https://docs.openclinica.com/node/2048 Please feel free to reach out to me with any additional questions. Thank you!
  • kristiakkristiak Posts: 1,248 ✭✭✭
    via Email
    Hi Rob,

    Can you do this with the Community version as well or do we need the Enterprise version? The question relates also to participate. If we need the Enterprise version what does it involve to run it on our own servers. We will have to do that due to the ever increasing privacy legislation in the EU and sever restrictions on soring any data outside of the country.

    Best regards

    Krister
  • toskriptoskrip Posts: 247 ✭✭
    Hi @rrittberg ,

    I would like to see how the randomisation rule definition looks like. Which version of rule designer do you use for this?

    Just a crazy idea... if the randomisation rule definition is generic enough, it may allow to setup different randomisation backends.

    T
  • lindsay.stevenslindsay.stevens Posts: 402 ✭✭✭
    via Email
    @krister

    I interpret this as, "OpenClinica LLC now offers randomisation
    integrations, and there's some starter code if you want to do it yourself
    or have someone else code it", rather than "OpenClinica (the product) now
    has randomisation". Same thing for Participate. It's good to have a start
    so it can be made more generic later, as Tomas suggested. But its not
    currently a feature like discrepancy notes are.

    It looks like the current implementation is with "sealedenvelope.com" (for
    which an evaluation username and password was committed to the github
    codebase, anyway). A few years ago, the Clinovo guys were doing this sort
    of thing with "randomize.net" if that's preferred.
  • kristiakkristiak Posts: 1,248 ✭✭✭
    via Email
    Thanks Lindsay for this useful info. We will have to consider it. We are very keen on the participate functionality, so far we have built APPS ourself and iåprted data via WEB services.

    Best wishes

    Krister
  • ccollinsccollins Posts: 366 admin
    edited January 2016
    @lindsay.stevens

    That's a pretty accurate description. It's an available module of the Enterprise product, and may be available as a (paid) module for open source users in the future, but full randomization capabilties are not a baked-in part of the main code base. Instead as you said, there are a set of hooks in the code that tie to Sealed Envelope or, potentially, to your own in-house randomization service.

    We need more developers contributing!! The more that happens, the more stuff will be open source :) Apart from that, there are a lot of good technical reasons to separate these services/modules. The OpenClinica codebase had gotten more monolithic than Krikor and I preferred and over the past 18 months we've been emphasizing a service-oriented architecture approach. The advantages in terms of faster development, higher quality, the ability to integrate with other systems, and a better user experience are great, especially as more of the world moves towards web services.

    @toskrip - for the reasons described, Rule Designer doesn't have support for the randomization action in its UI. We felt it would create a false impression that it's an out-of-the box feature. However you can upload an XML randomization rule. It won't do anything until there's a service on the other side listening, but the rule definition, APIs, etc are all there in the code. Here's what an example randomization rule looks like:

    <RuleImport>
    <RuleAssignment>
    <Target>
    F_RANDOMIZATIO.IG_RANDO_RANDOMIZATION.I_RANDO_RCONFIRM
    </Target>
    <RuleRef OID="RANDOMIZATION">
    <RandomizeAction IfExpressionEvaluates="true">
    <Run AdministrativeDataEntry="false" InitialDataEntry="true" DoubleDataEntry="false" ImportDataEntry="false" Batch="false"/>
    <DestinationProperty OID="I_RANDO_RASSIGN"/>
    <StratificationFactors>
    <StratificationFactor>I_RANDO_R1AGE</StratificationFactor>
    <StratificationFactor>I_RANDO_R1GENDER</StratificationFactor>
    <StratificationFactor>I_RANDO_R1BMI</StratificationFactor>
    </StratificationFactors>
    </RandomizeAction>
    </RuleRef>
    </RuleAssignment>
    <RuleDef OID="RANDOMIZATION" Name="RANDOMIZATION">
    <Description>Perform randomization if confirmation is "Yes"</Description>
    <Expression>I_RANDO_RCONFIRM eq 1</Expression>
    </RuleDef>
    </RuleImport>
    Happy Hunting!
    Cal
Sign In or Register to comment.