Difference between revisions of "EQIPD principles"

From EQIPD
Jump to: navigation, search
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
=Our objective=
+
=Objective=
(for the QS, our expectations, recommendation and processes)
+
The aim of the quality system is to be perceived as lean, flexible, fit-for-purpose, and user-friendly. To describe these high level terms in more details, 5 principles were phrased to present descriptive statements to describe "what the system is about".
To be perceived as lean, flexible, fit-for-purpose, and user-friendly.
 
  
=Challenge=
+
The following 5 principles summarize the essence of the EQIPD quality system.
Descriptors above are just bold statements not communicating anything about “what it is all about”. This is the question that we would like to be able to answer in a maximally concise and understandable manner.
+
They are not meant to replace the [[Core Requirements]].  Core requirements are operational implementations of these key principles.
 
 
=Solution=
 
Identify and agree on a small (5) set of key principles that are easy to understand and that summarize the essence of our QS and our work.
 
This is not to replace the Core Requirements.  Core requirements are operational implementations of these key principles.
 
Once formulated, these key principles can be presented in the white paper, in the Toolbox, on the website, included in the presentations, serve as a basis for a short commentary / paper, or just as talking point when someone is asking us “what it is all about”.
 
Last but not least, these principles will be instrumental for us to decide which practice is EQIPD compliant and which not.  To illustrate that, we will provide examples (case studies) for each principle.
 
  
 
=Key principles=
 
=Key principles=

Revision as of 08:11, 16 March 2021

Objective

The aim of the quality system is to be perceived as lean, flexible, fit-for-purpose, and user-friendly. To describe these high level terms in more details, 5 principles were phrased to present descriptive statements to describe "what the system is about".

The following 5 principles summarize the essence of the EQIPD quality system. They are not meant to replace the Core Requirements. Core requirements are operational implementations of these key principles.

Key principles

Principle Explanation Example
Engage with autonomy Decisions about specific needs and solutions are made by researchers, and not by EQIPD. EQIPD has formulated core requirements for the QS implementation and, as a partner in this process, EQIPD asks critical questions and provides recommendations that are voluntary to follow and are provided only to help the researchers throughout the implementation and use. EQIPD recommends applying randomization to all studies but it is up to the researcher to decide whether randomization is applying to a particular study or a particular study design
Grow through reflection [1] What it means to have the right quality level in place is suggested by your environment (collaborators, funders, institution, etc.). EQIPD does not “invent” needs or requirements of your funders or your collaborators. As a partner in this process, EQIPD QS only allows you to see these requirements better and suggests ways of implementing them. EQIPD identifies overlapping requirements from different stakeholders towards the use and reporting of randomization.
Focus on goal[2] Focus on the outcome (performance standards), not on the path, timelines or the tools to get there. EQIPD highlights the importance of “randomness” (lack of pattern or predictability) in the correctly developed randomization sequence but leaves it up to the user to select a specific method or tool.
Be transparent Key research processes must be transparent. This principle applies specifically to retention and accessibility of information related to key decisions related to study design, conduct or analysis (e.g., decisions to include or exclude certain data points in the analysis). If you decide not to apply randomization, the decision must be stated and must be justified, recorded and reported.
Leave a trace Key research processes must be traceable. Complementary to the principle above, this principle refers to retention and accessibility of all information that is necessary for a complete reconstruction of a key research process (e.g., Raw data related to reported data are findable, and reported data are reconstructable from raw data). If you do apply randomization, the way you apply randomization must be traceable and reported -