When one hears the word
flexibility, the image coming to mind is the one of those acrobats bending and rolling over themselves.
In an
organization, flexibility should be more like gearing up and down in a car depending on the road and the traffic's conditions.
Of course, every organization would like to be at
full throttle.
This is not possible.
Why? As we all know organizations are based on individuals. Full throttle for an individual can not last long and the most important when dealing with PV is
consistency.
Regulation, do not forget Pharmaco-Vigilance is a
regulated activity, so regulation does not expect you to be good at 80% or 95%. Auditors, sent by management, or authorities, look for every single defect in your organization and they expect you to be at 100% compliance (reports on time). So if you want to be there, you need every one available and focused. You do not want exhausted individuals, painful meetings, passive-agressive approaches.
Question: How do you make your organization flexible enough to bend itself to outer constraints (regulation, compliance) inner constraints (data quality, team management) and achieving sustainability in the proceeding?
First Step: Closer is Better
Everyone agrees when it comes to information you need to be close to the source of it. Not only when people are using their own language it helps understanding the subtilitites )localization/translation) but it also insures you can provide protection under local laws to privacy.
Second Step: Doing good once better than doing several
Processing information must b an industrialized activity. Yes you may end up having queries (questions to the source of the information). Definitely if you control the quality of the data entered compared to the data given (called QC) you should do it once.
Third Step: Beat it when it's hot
When you have to correct/fix something you should do it as close to the step when this information/action was entered/done. More you wait, more expensive the fix will be.
Fourth Step: Empower thy users
You will have to build throughout your orgnization a structure/tool to enhance the knowledge about the defects/failures it achieved previously. If you know why somethign went wrong and if you describe it precisely, chances are you won't repeat it.
In a nutshell, you'll start being
flexible when you'll be
empowering sooner, closer and better. Giving power to users to make decisions, helping them to understand the failures, collecting the information where it should, doing things in order and once, that the first phase to gain flexibility.
The next one (in another post) will be
adaptation.