Concentration data QC - use of Phoenix
Posted 01 January 2020 - 06:42 PM
Posted 02 January 2020 - 04:48 PM
I beleive the request for a lag function or similar that would enable this is logged as QC 11694, I'll drop a note to remind the Product Manager to look at this and/or suggest a workaround within Phoenix.
I am thinking even an option on import to carry forward a value until it is next set could be a useful improvement that might be relatively quick to implement.
Posted 11 January 2020 - 12:27 AM
nice to meet you in cyberspace. I hope you survived “Trumpistan” last month.
I think that drag/drop in Excel is prone to errors. IMHO, a lag-function (Simon’s QC 11694) is hardly better. What if you have complete missings (vial broken in centrifugation, no result at all, blahblah)?
I would say the only solution which does not require a lot of QC-work (do it twice, 100% data check, etc) is to politely but assertive ask the lab to provide complete data. The samples are labeled with all the required information which is carried through all sample processing steps until it ends up in the CDS. Why the heck do these guys/gals leave you out in the rain with incomplete data?
They should revise their data transfer procedure. Makes not only you happy but the life of inspectors easier. I don’t expect that they will like any ad hoc “solution”. Good luck writing an SOP for it. Opens a can of worms.
I would refuse to work with such a pile of pooh. I provide the lab before with my required data format. Yep, CSV – not bloody Excel. I also require a checksum. If the format is not correct or no checksum is provided, I ring up the sponsor.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users