In LinkedIn, I recently forwarded a post by Martin Lush entitled “Don’t Blame the Person – Fix the System!” One outcome for me from that is that it started a variety of side conversations with other people in the industry. One area of conversation that came up is that of testing, as a general topic and, today, I want to share my own thoughts on testing.
Some time ago, I made a post here about the levels of configuration and the misconceptions around them. What led-up to this post were conversations with customers and the continued realization that customers are still not being educated on what the term “configuration” means in our industry.
In a past post, I mentioned systems that let themselves become non-compliant. The issues I spoke about are actually issues for non-regulated systems, as well. All systems need some amount of maintenance and proper usage. However, there are other symptoms I hear among those groups who aren’t properly maintaining or using their systems. Here are some warning signs.
Some companies will write, generially, by their company names. Others will tell the names of the people who write the articles. I use my name for these posts, not merely the generic “GeoMetrick Entperprises” and I have some reasons for that.
Many companies are upgrading to Labvantage V8 or planning to do so. One of the features that looks especially tempting is the Workflows.
Compliance is so important that even those people such as myself who are not compliance people must to do what we can to help customers work toward this goal. Today, I will give you three documentation tips from the implementation side of the project.
Along the way, in trying to sell my services, I hear a variety of stories about systems and their problems. Recently, I’ve been hearing stories of non-compliance. I hope this is a coincidence rather than a trend.
Most of us in the laboratory informatics industry end up working on projects that aren’t close to home. I’m mainly talking about the area of services I work with, which are product selection, requirements gathering, and implementation services, such as configuration/customization. While I occasionally run into people who are getting local work, they’re the minority.
In my last post, I mentioned LabWare’s name and I noticed some things about the types of posts people were reading that leads me to make some statements about the current state of that product.
For some reason, there are people and companies in this world who think that my company, GeoMetrick Enterprises, has some kind of relationship with the company LabWare. This is not true. I work with the LabWare software not the LabWare company.