I'm Brendan Hyland. I help regulated facilities transform their software, spreadsheets, workflows and documents from time-consuming, deviation-invoking, regulatory burdens, to the competitive advantage they were meant to be. Join me every weekday as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.
Behold: The low-hanging fruit!
|
We are in the middle of our "Let's Automate" series to see if we can make some simple automation improvements to our own day-to-day tasks. Hopefully this process will give us some insights that we can bring to designing, validating or auditing our regulated processes. Today, let's review what we have so far. I'm going to call this "Version 1" since it's actually quite workable as it is. Here it is in a diagram:
Notice how much time and effort we've saved just addressing these low-hanging fruit, and we haven't even mentioned AI, Large-Language Models or the Blockchain! We've also mostly used software and tools that are already available to us, though I've opted to go with a more featureful text expander software than would be otherwise available. ConvertKit is specialized to email newsletters, but otherwise its publishing workflow is nothing special and easily duplicated with a Chrome extension or Word plugin. I've marked a red x on the parts of the workflow that are still largely manual, and of course writing the blog post and coming up with examples is still all me. So what more can we do? Until next time, thanks for reading! – Brendan p.s. Enjoy this message? Read more at the Hyland Quality Systems website. |
The Daily HaiQu
A newsletter about improving the systems we use in the GxPs
I'm Brendan Hyland. I help regulated facilities transform their software, spreadsheets, workflows and documents from time-consuming, deviation-invoking, regulatory burdens, to the competitive advantage they were meant to be. Join me every weekday as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.
Last time we left off with a cliff-hanger of a question: How do you prove you're you when signing a document? There are several ways I've seen that the 3rd party providers prove that it's you who's signed the document: You clicked a link from an email. You paid for the service with a credit card. You provided some government issued photo ID. Someone, such as a notorized public or your HR department, has verified it's you in person. Obviously these are very different levels of assurance. Then...
Last time we learned about the difference between an electronic signature - basically any way of signing a document electronically - and a digital signature, which is a cryptographic mechanism that can be used to implement electronic signatures, among other things. Modern digital signatures most often use the Public Key Infrastructure, or PKI, to generate and verify keys. So for you to properly e-sign your document (and I'm really simplifying things for illustration here) you need three...
There are several levels of 'signatures' that you can apply to an electronic document. The first and most basic is just an image of your written signature. One common option for this is to print the document, sign and scan it back in again. A more convenient version is to have an image of your signature saved that you can paste into documents. This is what many free versions of pdf software and word processors offer as a basic document signing option - a 'stamp' of your saved signature image....