Announcement

Collapse
No announcement yet.

COVERs Produce Duplicates

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • COVERs Produce Duplicates

    From: Greg Wagner
    Sent: Wednesday, April 11, 2007
    To: JG@ar.com; Support
    Subject: RE: Duplicate queries question

    Hi Jane,

    The system recognizes duplicate queries based on the text of the query that is generated. If the text of the query is modified later, even by adding a comma, the system does not see this as a duplicate and will create another query, unless the condition is no longer present.

    Regards,
    Greg-

    --------------------------------------------------------------------------

    From: JG@ar.com
    Sent: Tue 4/10/2007
    To: Support@ClinPlus.com
    Subject: Duplicate queries question

    Hi,

    When COVER programs first run, the queries that are created are with the Pending status. Sometimes after the query is created, we need to change the message. Then we usually save the query as Outstanding. When we run COVER programs again, the system does not recognize these queries as duplicates.

    Is there a way for ClinPlus to recognize queries as already created even though we edited them after the first run?

    Thanks,
    Jane

  • #2
    Hi,

    Are duplicates determined only by the text of the query or are other items checked as well?

    I have just run a COVER process on all records. Some of the programming for this process was modified since the last time it was run. Most of the changes made were for the assignment of variables to "VARIABLE1="; none of the query texts were changed in this process. Yet, there are 183 duplicates in this batch compared to previous batches, based on comparing query text only.

    On a side note, one of the standard study Listings is called QUERIES. The set of variables available for this Listing does not include either SEQUENCE or VARIABLE1. Is there a way to add these variables to the Listing setup?

    Thanks,
    Ed

    Comment


    • #3
      Hi Ed,

      Queries are de-duped in the system on the variables recordheaderskey1-recordheaderskey5 variables1-variables5 and question.

      So if any of the record links, variable specifications or the question text should change, the query will be issued again.

      Regards,
      Greg-

      Comment

      Working...
      X