How to write queries unambiguously expressing what is asked for? Using short, polite sentences? Objectively explaining the underlying inconsistency?

First of all my general guidelines.

My preference is to use no more capitals then needed. Capitals in the middle of a query text, e.g. for CRF fields or for tick box options, could distract from getting the actual question asked. E.g. compare the same query texts, with and without extra capitals. Please verify stop date. (Ensure that stop date is after or at start date and that stop date is not a future date.) Please verify Stop date. (Ensure that Stop date is after or at Start date AND that Stop date is not a future date.)

Referring to CRF fields as they are shown on the CRF. To easily find the involved field(s).

I prefer to leave any ‘the’ before a CRF field referral out of the query text. For more to-the-point query texts. E.g. compare the same query texts, with and without ‘the’ before data fields. Please verify stop date. (Ensure that stop date is after or at start date and that stop date is not a future date.) Please verify the stop date. (Ensure that the stop date is after or at the start date and that the stop date is not a future date.)

Consistency in phrasing a query text can help to quickly write query texts or pre-program query texts in a structured, familiar way. That’s the thought behind the following 6 template sentences for query texts. Which you can use to help you write or program your queries.

The six ‘template’ sentences for query texts:

Please provide…

For asking the study site people to provide required data from patient care recordings. Examples: Please provide date of visit. Please provide date of blood specimen collection. Please provide platelet count. Please provide % plasma cells bone marrow aspirate. Please provide calcium result.

Please complete… For asking the study site people to complete required data as required by the study CRF design. (Not necessarily required for patient care). Examples: Please complete centre number. Please complete subject number. Other frequency is specified, please complete frequency drop-down list accordingly.

Please verify…

For asking the study site people to check date and time fields fulfilling expected timelines. Or for asking the study site people to check field formats. Examples: Please verify start date. (Ensure that start date is before date of visit.) Please verify stop date. (Ensure that stop date is after or at start date and that stop date is not a future date.) Please verify date of blood specimen collection. (Ensure that date of blood specimen collection is before or equal to date of visit and after date of previous visit.) Please verify date last pregnancy test performed. Please verify date of informed consent. (Ensure date of informed consent is equal to date of screening or prior to date of screening.) Please verify date as DDMMYYY.

…., please correct.

For asking the study site people to correct a data recording inconsistent with another data recording. Example: Visit number should be greater than 2, please correct.

…., please tick…

For asking the study site people to complete required tick boxes. Examples: Gender, please tick male or female. Pregnancy test result, please tick negative or positive. Any new adverse events or changes in adverse events since the previous visit, please tick yes or no. Laboratory assessment performed since the previous visit, please tick yes or no. LDH, please tick normal, abnormal or not done.

Please specify…

For asking the study site people to specify the previous data recording. Examples: Please specify other dose. Please specify other frequency. Please specify other method used. Please specify other indication for treatment.

Finally, for query texts popping up during CRF data recording, it could be helpful to put location information in it. Like: Page 12: Please verify start date. (Ensure that start date is after or at start date on page 11.)

Good luck finding your way to structure query texts…

Source:

This article is written by Maritza Witteveen of ProCDM. For clinical data management. You can subscribe to her blog posts at www.procdm.nl.”

Comments? Join us at {EDC Developer}

Anayansi Gamboa, MPM, an EDC Developer Consultant and clinical programmer for the Pharmaceutical and Biotech industry with more than 13 years of experience.

Available for short-term contracts or ad-hoc requests. See my specialties section (Oracle, SQL Server, EDC Inform, EDC Rave, OpenClinica, SAS and other CDM tools)

As the 3 C’s of life states: Choices, Chances and Changes- you must make a choice to take a chance or your life will never change. I continually seek to implement means of improving processes to reduce cycle time and decrease work effort.

Subscribe to my blog’s RSS feed and email newsletter to get immediate updates on latest news, articles, and tips. I am available on LinkedIn. Connect with me there for technical discussions.

Fair Use Notice: This article/video contains some copyrighted material whose use has not been authorized by the copyright owners. We believe that this not-for-profit, educational, and/or criticism or commentary use on the Web constitutes a fair use of the copyrighted material (as provided for in section 107 of the US Copyright Law. If you wish to use this copyrighted material for purposes that go beyond fair use, you must obtain permission from the copyright owner. Fair Use notwithstanding we will immediately comply with any copyright owner who wants their material removed or modified, wants us to link to their website or wants us to add their photo.

Disclaimer: The EDC Developer blog is “one man’s opinion”. Anything that is said on the report is either opinion, criticism, information or commentary. If making any type of investment or legal decision it would be wise to contact or consult a professional before making that decision.

Disclaimer:De inhoud van deze columns weerspiegelen niet per definitie de mening van {EDC Developer}.

Advertisements