We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

Creating rules for text fields

Is it possible thru the Rule Builder to check that a text field is the same across CRF visits? 

In this scenario there is no dropdown or standard this would be strictly a text field documenting a name and it could be many different names.  This would ensure the same person performed a specific evaluation for a patient for every visit.

 

Otherwise this would be a manual/eyeball check.

Thanks

 

Comments

  • gbraukgbrauk Posts: 8
    via Email
    I will be out of office starting from 18 May 2015 and will not be able to reply to your e-mails before 02 June 2015.

    For urgent questions and issues please get in touch with Marco Schwarzer via [email protected]
    We will reply as soon as possible.
    Kind regards,

    Gisela Braukmüller

    Data Manager


    GCP-Service International Ltd. & Co. KG

    Anne-Conway-Str. 2
    28359 Bremen, Germany

    Tel +49 (0)421 89 67 66 22
    Fax +49 (0)421 43 48 659

    Email [email protected]
    Web www.gcp-service.com
  • lindsay.stevenslindsay.stevens Posts: 404 ✭✭✭
    via Email
    Yes, it is possible. The rule definition would target e.g.
    Target=Event1.CRF.ItemGroup.Item

    The rule expression would compare the target item to other events, e.g.
    Item eq Event2.CRF.ItemGroup.Item

    There would be rules like this for every target event, comparing to every
    other event, e.g. for a study with 3 events there would be 6 rules, e.g.

    For Event1, Item eq Event2...Item, Item eq Event3...Item

    For Event2, Item eq Event1...Item, Item eq Event3...Item

    For Event3, Item eq Event2...Item, Item eq Event1...Item

    These are separate rules because if an event doesn't exist yet, that part
    of the expression becomes null (not true or false).

    If you have many events, I suggest writing these in xml so you can
    copy/paste easily, or generate most of it in Excel.

    If you haven't written rule xml before, write the first of these rules in
    designer, then export it to xml. It should be pretty straightforward which
    parts you need to change for each rule.

    Note that to upload rule xml containing more than one rule, all the ruledef
    parts must be above all the ruleref parts, like ruledef ruledef ruleref
    ruleref.

    Since these rules can only evaluate an exact text match, it might be worth
    checking this in exported data instead so you can differentiate typos from
    incorrect names.
This discussion has been closed.