Yes, that's the method I have tried, and it works just fine. The problem is
the use of the CRF in 10 different Events on 15 sites, so I have to hide
the old version 150 times... it would be nice if a faster (and safer) way
exists for doing this? Perhaps a "Hide" button could be introduced on the
/ListCRF page, which would work as a "soft archive"...
Sent by: "[email protected]
" [email protected]
25-10-2012 23:59 Re: [Users] How to introduce a new
CRF version,replacing the old
one, but allowing old version to be
Please respond to completed? [email protected]
I'm sure someone will correct me if I'm wrong, but if you hide version 1 of
the CRF, then that CRF will not show up for Data Entry personnel, unless
data entry has already begun on version 1 for a particular subject.
1923 Landings Dr.
Mountain View, CA 94043
This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use, copy, or disclose to anyone the message or any information
contained in the message. If you have received this message in error,
please advise the sender by reply e-mail and delete the message.
On Behalf Of Janus Engstrøm
Sent: Thursday, October 25, 2012 2:34 PM
To: [email protected]
Subject: [Users] How to introduce a new CRF version, replacing the old one,
but allowing old version to be completed?
Say I have a CRF named "Test" and it is versioned as "Version 1". The CRF
is included in 10 Events and has been taken into use for 50 study subjects.
The study consists of 15 sites.
Now, some changes were needed on the "Test" CRF, so I create and upload a
"Version 2" of the CRF. I would like to allow the "Test Version 1" CRF to
be completed for all of the 10 Events, but new Events being scheduled
containing the "Test" CRF should from now on only be allowed to use the
"Version 2" of the CRF.
If I choose to Archive the "Version 1", then OpenClinica won't allow data
entry on the already uncompleted instances of the CRF. If I choose to edit
a Site's access to which versions of the "Test" CRF (using the
/InitUpdateSubStudy?id=), I can obtain the above mentioned scenario. Only
problem with this approach, is that since the study has 15 sites and each
site has 10 Events using the "Test" CRF, I need to do editing in 150
Is there a better way to allow continued data entry on already started CRFs
of some version, but disallow further instantations of this version?