There are many ways you can get data into a spreadsheet. You can type it in. You can copy and paste it in from another digital file. You can use a macro or some VBA to automatically pull it in from somewhere. You can use some of Excel's built-in features to 'connect' to an external source like a database. You could even dictate it in, cell by cell. Each of these input cases has its own hazards. Typing can be subject to typos. Copied data can be pasted into the wrong cells, or be the wrong shape entirely. Even within the categories there are different levels of hazard and risk - for example, if you're typing data in, are you reading it off of another record such as a written form? Or are you typing in an original observation such as a thermometer reading? If you're recording an original observation in a regulated capacity, then you might have to worry about protecting that as an electronic record. When you're connecting to some source outside of the spreadsheet like a database or xml file, are you in control of that source? Can you guarantee that the data format won't change between imports? Does the data needs some kind of cleaning to make it consistent, remove garbage, or to convert it to an expected format? As you might imagine, each of these scenarios might require different controls to ensure the integrity of your data. You should certainly consider how data will be input as part of the spreadsheet design. You might even need to limit how data can be input in your procedures, just to make sure you don't introduce some unknown hazards to the integrity of your data! Until next time, thanks for reading! – Brendan p.s. Enjoy this message? Read more at the Hyland Quality Systems website. |
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 week as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.
I'm excited to be presenting at the 2025 SQA Annual Meeting next week - "Is it the Right Tool for the Job? How QA and Regulatory Professionals can Guide Software Decisions in Regulated Environments" As our familiar software tools become more feature-laden and generalized, it's critical to ensure that software meets clear use cases and basic user requirements. And with generative AI being shoehorned into every platform, defining if and how software is appropriate for the intended use has never...
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...
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....