In my last post, “Notes on Software Testing Habits,” I ran through a few thoughts about how to look at your software testing habits. Regulated or not, there are many commonalities.
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.
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.
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.
In all these posts about the end of my job, some of you might be surprised that I’m only now writing about the LIMS. Me, too. U of M runs the LVS Biobanking solution which I knew before I had an inkling I would work there so I guarantee I’m not passing along any secrets, here. It was easy enough to see from reading people’s LinkedIn profiles so they’re not keeping it a secret.
Many projects have a problem getting reports produced. In one sense, it seems expensive to hire a LIMS, ELN or LES expert who knows the data but who comes with a rather high rate. On the other hand, getting a cheap resource who knows the reporting tool isn’t an easy solution because it’s so incredibly difficult to teach them these massive databases and how they work. Today, I will tell you the solution to this problem.