Diagram showing Digimarc Barcodes

Date: March, 2020 | CategoryqualityAuthor:Kayla Caticchio


 

A new era of barcodes is here. With big-name retailers and consumer goods companies replacing traditional barcodes with Digimarc barcodes, printers are facing more challenges than ever when it comes to verifying these modern codes. 

GlobalVision’s latest integration, Digimarc Verify, gives users the ability to verify and grade all Digimarc barcodes with or without the use of a scanner, speeding up and simplifying the quality control process. 

Read Now: Digimarc Verify for GlobalVision Press Release

What is a Digimarc Barcode?

A Digimarc Barcode is an advanced barcode that can be applied to any print or packaging material. It links interactive content, like product information, when scanned with an enabled scanner or mobile device. Known as the ‘Invisible Barcode’, Digimarc codes on labels and packaging contain the same information as a UPC barcode but generally can’t be detected by the human eye.

Digimarc barcodes offer several benefits over traditional ones. Many retailers are making the switch because they’re faster, more secure, more reliable, and more versatile than traditional barcodes. They also occupy no space on a product’s packaging, giving the company more space to work with when it comes to artwork and branding. Retailers appreciate the fact that Digimarc Barcodes speed up the checkout process as people can scan their products without having to locate a barcode on the packaging.

Inspection report screenshot

The Importance of Barcode Inspections

Although barcodes have significantly evolved since their introduction in the 1970s, the importance of ensuring barcode functionality has never been lost.

First and foremost, barcodes must be checked to ensure that they’re present and scannable. Next, the barcode on a printed packaging material has to match the product inside. Finally, printers must give their clients the assurance that their products will scan at the store. If a barcode doesn’t scan, both the retailer and the brand run the risk of losing money. 

For prepress operators and printers, the main challenge with checking Digimarc codes is that they can’t be located just by looking at the packaging. This makes it difficult for any traditional barcode reader to verify the functionality of the barcode.  

With Digimarc Verify for GlobalVision, prepress operators and printers now have an easy and efficient way to validate that the packaging containing Digimarc Barcodes is ready to hit the shelves. This integration gives them the ability to automatically confirm that the Global Trade Identification Number (GTIN) in Digimarc Barcodes matches the GTIN in the UPC or EAN barcode. Overall, Digimarc Verify is designed to speed up and simplify the quality control process for those in charge of proofreading barcodes.

“The integration of Digimarc’s quality assurance tools directly in our platform will help our customers speed up their production process by streamlining all barcode checks,” says Reuben Malz, Founder and CEO, GlobalVision.

This integration is critical as any errors that occur when printing Digimarc Barcodes can now be caught early on to save money and time for prepress customers.

“Integrating Digimarc Verify into GlobalVision will help operators save time and also ensure the quality of their clients’ packaging, while also enabling further industry adoption of Digimarc Barcode,” says Bruce Davis, CEO, Digimarc.

Running a Digimarc Inspection

Illustration of GlobalVision Barcode inspection tool

To run a Digimarc inspection in GlobalVision’s Barcode Inspection mode, users start by loading their electronic prepress files or printed samples into the software and selecting the Digimarc Inspection mode.

The software will then run an inspection to determine if a Digimarc Barcode is indeed present and to ensure that the enhanced separation values are matching or are similar. Once completed, a comprehensive inspection report will be generated that contains the results of both the Digimarc and linear barcode inspection (if present).

Users can then save the report and share it with the customer for approval, allowing them to sign off faster and with confidence.

Digimarc Verify for GlobalVision comes as an additional tool for the Barcode Inspection mode. For more information regarding this add-on, download the Remote Barcode Inspection whitepaper.

Watch Now: How to Verify Digimarc Barcodes with GlobalVision Webinar

_________________________________________________________________________________________

Ensure your content is always error-free in record time with GlobalVision. Try it now for free. 

Keep up with the latest updates in automated quality control. Sign up for our newsletter. 

Laptop uploading account and password info to cloud

Date: August, 2019 | Categoryquality Author: Ryan Szporer


“Just” backing up data isn’t enough to keep data intact anymore. While it’s a necessary step and a good start at that, a backup means little if there aren’t adequate safeguards in place to protect the integrity of the data that might have to be recovered. Even if back-ups themselves are a safeguard, they must be seen as an asset in their own right. After all, it’s estimated 100 mb of company data is worth $1 million on average. Half the firms that cannot recover lost data in 10 days cannot recover themselves.

It just makes good strategic sense to have a backup plan in the most literal sense as a result. Here are the top five strategies to keep data intact, for the sake of keeping your data integrity intact:

1. Know What to Back Up

It’s not only files that must be backed up but programs, including Operating System software as well. After all, if a newer version of a program has been released, it may not be able to read your data.

The fix simply requires that an image, or a carbon copy of all critical information including programs and their data saved into a single file, be backed up. That way no synchronization issues arise, preventing you from using the data even if you may have successfully recovered it. It would be like having the keys to the wrong car. Only this car can’t be hot-wired to run.

There is an admitted caveat: If you upgrade your hardware, the image may no longer be compatible itself. So, an alternative solution would be to just stay up to date with your program versions and continue to back up data as you normally would (i.e., thoroughly).

2. Encrypt Your Back-Ups

It almost goes without saying in this day and age, information must be kept secure for its data integrity to stay intact. One way to avoid confidential information from being compromised is to encrypt it into code, which is of course standard practice. It’s a standard practice for a reason though, namely its effectiveness. As a result, it’s significant enough in importance to rank on this list.

3. Make Regular Back-Ups

You can’t simply back up data before an upgrade. Ideally scheduled for when there is low network activity to prevent slowdown, back-ups should be made every day, with daily snapshots taken as well to monitor performance. Furthermore, at least two weeks of daily backups should be kept at any one time, as it represents a manageable time frame in case a file does get lost or corrupted.

Meanwhile, once-a-month back-ups should be preserved for one year, while annual back-ups should be kept for seven years in case a governmental request is made. In each case, consideration should also be made with regard to how much space is available, with old backups deleted to make room for new ones.

4. Store Your Back-Ups Properly

It goes beyond storing your backups in environmentally controlled facilities, even if that’s admittedly a good practice. You would also want to store your backups off-site, separately from the original data. Every good plan has redundancies built in and a backup/ data recovery plan is no different.

The reasoning is simple, as they represent contingencies in case of disaster. Imagine a worst-case scenario in which a literal natural disaster strikes. You would want as large of a chance as being able to pick up right where you left off as soon as possible. You don’t want to lose your backups and the original data all in one fell swoop. That would truly be a disaster.

5. Validate the Recovery Procedure

Validation can take many forms. With regard to the GlobalVision Quality Control Platform, for example, Installation, Operational, and Performance Qualification procedures serve to verify the application works as it should.

As the definition of validation suggests, it “provides a high degree of assurance that a specific process will consistently produce a product meeting its pre-determined specifications and quality attributes.” In the case of backups, the process in question is the recovery procedure. The back-ups themselves are the product.

Verifying the viability of the backup data is critical. Test runs ensure that, in a worst-case scenario like the one outlined in Point No. 4, the data and operations can be picked up in a reasonable amount of time, even if off-site. Restoring back-ups on a regular basis helps validate the recovery procedure. Restoring back-ups to an alternative server before so doing is actually the best practice as it validates the ability of the data to be recovered. Seeing as the data would have just been validated in a new environment, it also provides you with a backup you can be sure is viable, should you ever need to use it. Knock on wood.

_________________________________________________________________________________________

Ensure your content is always error-free in record time with GlobalVision. Try it now for free. 

Keep up with the latest updates in automated quality control. Sign up for our newsletter. 

Illustration of quality control process

Date: July, 2019 | CategoryQuality Author: Ryan Szporer


 
 

When you hear the word “security,” what comes to mind? Maybe you think of the stereotypical security measures that have crept into our collective consciousness as clichés to show how hard getting into specific places can be.

I mean, when the suave James Bond smooth talks and sneaks his way into a top-secret facility, everyone watches in amazement. It turns out there’s a reason because it’s never so simple. The truth is, however many guards, walls, doors, and Closed Circuit Television (CCTV) cameras there may be, they only represent half the battle. When it comes to data integrity, half won’t suffice.

Physical vs. Logical System Security

Of course, “integrity” here refers to the state of data over its entire lifecycle, during which it must stay reliable and accurate to meet compliance requirements with regulatory bodies like the Food and Drug Administration (FDA). Those aforementioned measures meanwhile make up the physical component of security.

While physical security is undeniably important, so is logical system security, which manages access to computer systems. In fact, the two can actually complement each other in more ways than one. At least if it’s done right.

Imagine a computer system containing confidential data that can only be accessed by entering a valid username and password combination. That’s logical system security at work, at least in one form. It’s nevertheless harder to gain access to the data when there’s a locked door standing between the system and someone with malicious intent, regardless of how difficult it might be for them to simply log in to the computer were the door not there in the first place.

an illustration of a hand writing on a clip board

The Convergence of Physical and Logical System Security

However, what if cybersecurity measures were taken to lock the door instead? In that way, both types of security integrate perfectly with one another to give companies the best of both worlds when it comes to limiting system access. Of course, limited system access is one way to secure data, with at least two unique pieces of information ideally being required (two-factor authentication; username, password, etc.).

Both limited system access and the protection of the physical and logical security of systems are also two ways to help ensure data integrity.

There are undeniable barriers to integrating the two, even if the payoff would theoretically be worth it. The cost of updating systems is huge, while compatibility and communication between systems are just as big of a consideration. However, while costs do loom large, certain industries are being forced into automating and converging their physical and logical security technologies to a greater degree.

Chief among them, for example, would be the banking industry, in which corporations are being held to a greater standard with regard to how they handle client data in a post-GDPR world.

Ultimately, it comes down to whether or not corporations should invest now to update their security systems or pay for it after the fact. Penny-pinching only goes so far when the resulting grainy CCTV footage ends up being worth less than a grain of salt as far as its value in preventing security breaches, even as a mere deterrent.

That goes double for logical security measures. In today’s day and age, you need to keep up with the latest in encryption and/ or login management. The latter of which should feature a hierarchy of access levels requiring unique user ID and password combinations, like in the GlobalVision Quality Control Platform.

The Information Technology Angle to Security

Both of the above features are examples of requirements to comply with FDA regulations. However, just like software itself doesn’t ensure compliance and is only a tool used to achieve it, physical and logical security measures alone are not enough.

It takes a concerted effort on the part of a company to not only oversee the implementation of proper security protocols but enforce them to boot.

From an IT departmental perspective, enforcement implies a whole lot more than keeping up with software updates and patches. Strengthening security depends on a variety of methods available to IT professionals, including:

  • Permissions, whereby users are allowed to perform tasks in specific applications based on their responsibilities and
  • Detective controls, like anti-virus and/ or error-detection software to help improve response time when something is actually determined to be amiss.

Obviously, technology, by its very definition, is ever-changing. All the precautions and security requirements that go into protecting it and assets like data must evolve at the same time. Otherwise, however secure they might have been yesterday won’t matter.

It’s not about thinking outside the box to keep people from getting in, but keeping up on trends to make sure you and everyone else who’s been granted access stay one step ahead instead. It can get tiresome, but it beats the alternative: an unavoidable degree of uncertainty with regard to the future of your business prospects. Insecurity comes in many different forms, after all.


Related articles:

The Top Back-Up Strategies to Keep Data Integrity Intact

3 Ways Error-Detection Software Ensures Data Integrity

Monitor with data integrity checklist

Date: June, 2019 | CategoryQuality Author: Ryan Szporer


Consistency is a trademark of both validation and data integrity. In fact, without validation and the consistency for which it strives, forget data integrity. It’s like there is no data at all.

What Is Validation?

To be clear, validation is defined as, “evidence that provides a high degree of assurance that a specific process will consistently produce a product meeting its pre-determined specifications and quality attributes.” The “consistently” is key. There is no good use for a system that cannot do what it promises every single time.

Think along the lines of a phone that only dials the right number four out of five times. Eighty percent is a good mark on a test, but not so much in case of an emergency when you need to call 9-1-1 and you get the local pizza place instead. That’s in large part why system validation is so thorough, with Installation, Operational, and Performance Qualification processes entering into the equation.

For its part, data must be consistent throughout its entire lifecycle for it to have integrity. It plays into the need for data to also be accurate, which is one of the Food and Drug Administration’s expectations for Good Manufacturing Practices. Altogether, data is expected to be “Attributable,” “Legible,” “Contemporaneous,” “Original,” and, of course, “Accurate,” or “ALCOA” for short.

Data itself can be validated too. For example, to achieve compliance with the FDA (21 CFR Part 11, specifically) in pharma and life sciences, companies must ensure integrity is maintained with regard to drug safety data as it is collected, stored, and transmitted. This is done through preliminary planning, risk identification, and testing. After the fact, everything is regularly verified as working as expected, while regular audits and reports are made to improve processes after the fact.

What Must Be Validated?

In essence, while validation is an admittedly and justifiably complex process, it boils down to that same simple premise: It all has to be verified as working as expected. Anything less and the resulting data can’t be trusted. It would be useless and just as good as if it were non-existent.

Now, confusion may admittedly arise over what exactly is being validated. In a word almost “everything.” For example, in pharma, every piece of equipment that touches or impacts the development of a drug during the manufacturing process must be validated.

While equipment validation is nothing specific to pharma and is important in other industries, IT systems and processes also qualify as requiring validation here. Even proofreading software like GlobalVision, which helps to verify packaging as being accurate but may not actually come into physical contact with the product itself, would fall into this category.

Audit trails and the like within applications are generally designed to keep excellent records. And, if they are validated as being reliable without fail, it’s safe to operate under the assumption the data they keep is as well. And, as mentioned earlier, the data must be validated too.

Data Integrity vs. Data Validation

Data integrity and data validation are two separate concepts, but they effectively have the same end goal. Data validation covers the testing and processes that lead to data complying with regulations put in place by the FDA (for example). Data integrity is what you get once it has been deemed to be secure as a result, along with several other qualifications.

In other words, much like data security is a basic tenet of data integrity and not vice versa, the same goes for data validation. If your data has been validated and/or you have proper security precautions in place, the threat of a breach or malicious attack has been mitigated. There has been no such breach with regard to data that has integrity. It has to be kept that way.

It’s similar to how a ship’s hull has integrity until it hits an iceberg. Steps are taken to avoid contact or keep water from breaching. Since there are measures in place and the ship is afloat, to begin with, it means the ship is secure. Meanwhile, validation determines how effective those measures are. If they aren’t any consistency, the ship shouldn’t have even made it out of the shipyard.

In that sense, the ship is like any other manufactured product. Only its best possible, viable version should be made available. Validation helps ensure that is the case. Consistently.

_________________________________________________________________________________________

Ensure your content is always error-free in record time with GlobalVision. Try it now for free. 

Keep up with the latest updates in automated quality control. Sign up for our newsletter. 

Error detection of quality control software ensuring data integrity

Date: June, 2019 | CategoryQuality Author: Ryan Szporer


 

There are many ways to ensure data integrity. As automation becomes increasingly prevalent in the 21st century, software, especially on the back end, is as important as ever. Not only does it serve as the driving force behind technology in all of its incarnations, but it can also act as a fail-safe. As the term implies, “error-detection software” is one viable way to catch and stop errors that risk corrupting data in their tracks.

So, how can you ensure data integrity? We give you three ways error-detection software can help you out. 

1. Enhances Security

While data security is different than data integrity, the two go hand in hand. Like data quality, data security is a single facet of data integrity (but not vice versa). Nevertheless, without the proper degree of security, data can become compromised due to breaches, among other threats. In other words, for data to have integrity, it must first be secure.

As a result, error-detection software can be considered a key component of any complement of tools designed and implemented to enhance the security of data. Errors are simply outliers or anomalies, which are defined as observations that lie outside of norms. Error-detection software can build baselines of systems, their users, and the data they create, leading to the easy detection of behavioral deviations, whether there is malicious intent or not.

2. Reduces Human Error

There’s an inherent risk whenever you rely on human resources. There are some things a machine will likely never be able to do as well, but analyzing data is not one of them. It’s similar to the situation with manual proofreading, where, the longer the process is, the less likely errors are to get caught. Fatigue sets in eventually and the effectiveness of proofreaders declines over time.

In much the same way, the automated analysis of unstructured data saves time, thereby improving the overall efficiency of the process. Employees wouldn’t be replaced, either. There would still be a need to oversee the analysis. The right error-detection software would all the while keep all relevant parties apprised of how the data behaves. As described in Point 1 above, that’s critical.

3. Prevents Issues from Recurring

It isn’t just the errors software might catch, but the ones in the future that would otherwise slip through the cracks. Consider digital proofreading software as an example. A form of error-detection software, GlobalVision features an audit trail for compliance with FDA 21 CFR Part 11.

So, the platform doesn’t just go over the document pixel by pixel or character by character to detect graphics and text differences (among other types). The application tracks parameter changes and log-ins, so data becomes “attributable” (which is one of the five principles of data integrity). The others are “Legible,” “Contemporaneous,” “Original,” and “Accurate” (spelling ALCOA).

The End Result?

Error detection or detected differences between master and sample files from the printer can be tied to individual departments and testers. The exact origin of any error can be easily discovered and addressed. Similar errors can be prevented in the future. In that way, the number of potential mistakes gets dwindled down. Proper company quality standards get corrected and set moving forward.

As another example, a Corrective And Preventive Action (CAPA) system prevents the recurrence of product and quality problems. In manufacturing, it can become a vicious cycle of sorts. If high-quality products aren’t routinely manufactured, there is pressure to falsify data so that it passes. That leads to a lack of data integrity. So, it can be argued, a lack of data integrity is a sign of a lack of quality.

In contrast, verifying all possible data sources for the root cause of errors keeps the chances of them recurring low. From a data integrity perspective, that means fewer lapses. Product quality and customer satisfaction, whatever the industry in question, can only improve as a result.

_____________________________________________________________________

Learn how GlobalVision can help ensure data integrity using Automated Proofreading.

Request a free trial for GlobalVision Digital Inspection Solution

Learn More about How to Ensure a Successful Printer-Pharma Relationship

Cartoon computer work on the digital inspection fast and efficient comparing to manual work

Date: April, 2019 | CategoryQuality Author: Mike Malz


Regardless of the industry, all companies have the same goal in mind: to provide high-quality products to keep customers loyal and attract new ones. To accomplish this, each product must go through a strict proofreading process to ensure the accuracy of all labeling and packaging.

This can be time-consuming. As a result, some early adopters have switched to proofreading software due to time constraints. In fact, sticking with human proofreaders has proven to be a potentially costly mistake, one that may even lead to expensive recalls.

Avoid Manual Errors

Although they do their best, human proofreaders are not able to catch all errors that can be found on a label. In a North Carolina State University article about errors in food manufacturing, 25% to 50% of recalls were due to human error. There are many reasons why these errors were missed; For one, a proofreader could have been tired or simply unfocused.

With new technologies continuously introduced into every aspect of our lives, people can be distracted by an email alert or text message. When an error is detected in packaging, companies must issue a recall on their product, costing them thousands of dollars and leaving them with a ton of unsellable inventory. Fortunately, there are measures to ensure each packaging component is error-free. These measures can be combined into a single solution: an automated proofreading platform.

Proofreading That Checks Every Word

Human brains are trained to skip words. So, no matter how fluent they are in a language, they can overlook one that’s misspelled. Most people use spell-checking software such as the spellcheck feature in Microsoft Word or maybe even an online solution like Grammarly. These tools help catch those mistakes, but they do have flaws. For example, some English words are spelled differently, such as “color” and “colour.” One solution would be proofreading software that automatically detects errors in a loaded file.

Catch Discrepancies in Color

Despite evidence to the contrary, some may argue human proofreaders do catch misspelled words. Nevertheless, color differences are a different kind of animal. It’s important that the labels of packaging have a consistent color pattern. This helps promote brand awareness and identity. If the color has faded or the hue is slightly different, the product will come off as rushed. Color-detection software is one way to identify any issues before the file gets sent to the printing press.

A+ Barcode Grading

Every company wants to send out Grade “A” barcodes and nothing less, as recalls can be issued if they will not scan. And, yet, despite the very real need, human proofreaders are unable to tell if a barcode will scan properly when it reaches the customer. Leveraging technology is the only option here, and it makes sense to opt for the best solution possible. Having a process in place to digitally check barcodes saves you time and money. This is especially true when it comes to consumer goods.

Checking Labels Even After Printing

There is still a chance some errors or color differences will slip through the cracks even after the job is done and the labels are printed. The best way to review your printed files is by reverifying them, using proofreading software. This way the user can find any differences and decide to reprint if necessary.

It’s important to make sure that, even when the final label is produced, it remains error-free. It would be infinitely preferable to find errors in labels immediately after they’ve been printed instead of having a customer find them while in line at a store.

Making sure your products are high-quality extends to the packaging. Errors are not only costly but embarrassing. People are far from infallible, and companies that rely on human proofreaders risk having their products recalled and losing customers.

Making the switch to automated proofreading, like with GlobalVision, can save you time and money by sparing your firm from having to issue recalls. Businesses should consider spending a little more money now on solutions that help maintain their reputation and brand integrity. It’s not about short-term gains, but rather the long game, in which everyone is a winner.

_________________________________________________________________________________________

Get your complete guide to meeting FDA labeling requirements here

Take the first step towards error-free packaging and labels by starting your free trial of GlobalVision

Learn how some of the world’s top pharma companies have cracked the efficiency code with automation

Man working on compliance with a laptop

Date: January, 2019 | Categoryquality Author: Ryan Szporer


In spite of the term Software Development Lifecycle (SDLC), there aren’t concrete steps to follow when coding. Each case is somewhat different, even if there is one universal truth: Certain standards apply across the board. Data integrity is one such standard.

The Ultimate Software Development Lifecycle Goal

It may not be the ultimate goal, as that would be releasing a functional piece of software. However, as a key consideration of any successful Software Development Lifecycle (SDLC), data integrity is a requirement that must not be ignored. That goes for GlobalVision’s proofreading software, which follows an SDLC approach, too.

The term “data” is relatively straightforward: information collected and potentially used by the application. “Integrity” is, of course, the end result achieved through the process of keeping that data uncorrupted and unchanged. It goes hand in hand with the concept of data security, which is sought after through the act of taking the necessary measures to protect it.

For example, individual lifecycles have proper security precautions built into them and controls added at each step. One precaution would be the act of defining early on the sensitivity of the data a given system will require. As James E. Purcell writes in his paper, “Defining and Understanding Security in the Software Development Life Cycle”, this enables the security needs of the firm to be considered come the time for decisions to be made later on in the process. Failure to do so leads to potentially unforeseen consequences and add-ons and patches after the fact. Almost by definition, those should be the last resorts.

The Software Development Process

Taking the development process one meticulous step at a time is a way to avoid them. As alluded to earlier, there is a variety that can be followed, but, generally speaking, as a list, it looks like the one below:

Analyze and Plan, which should include preliminary risk assessment. Relevant regulations that will come into play should be looked at and a plan of action as to how to address them should be devised. This should be reflected in the resulting software-requirement-specification document that comes out of these two phases.

Design, where whatever needs to be in the software gets included in the design specification document. Depending on the system being designed and compliance considerations, it may end up including failsafes with regard to the database, so it is easily backed up and restored. Furthermore, as a security precaution to protect against data being stolen or corrupted, encryption, if applicable, is identified as a necessity at this stage.

Build the Software, presumably using secure code to eliminate any potential vulnerabilities that may surface.

Test, with regard to all aspects of the software in a thorough, structured fashion. Testing is as universal as it gets and becomes a focal point of a product’s development regardless of the industry. When it comes to software though, aspects like code quality and security testing are just two of many that should be considered here, ideally by a dedicated quality-assurance team.

Unit testing, where the smallest testable parts of an application are verified for bugs and vulnerabilities independently, is also a popular pre-emptive strike against breaches but can be automated. Meanwhile, black-box testing, which places the application under the microscope of a tester who does not look at its internal workings (as if it were in a black box), seeks to test a variety of things, including external database access and the software for data-structure errors.

Deploy or Release, finally. That’s assuming all tests have passed and any security shortcomings that had been documented during the testing phase have been resolved. As part of the final quality checks of the software, further security testing may actually be done.

Maintain and Evaluate, which translates to updating the software via security upgrades and improvements whenever necessary. It turns out, sometimes there are good reasons behind those Apple iPhone updates.

Dispose, as, even in obsolescence, software must be handled with discretion. If the software is in the midst of being replaced, caution must be exercised to ensure any sensitive data is archived securely or disposed of in its entirety.

After all, any SDLC seeks to create software that is useful to the organization. Logically, software that can be superseded by a newer version has outlived that usefulness. By the same token, an application without the appropriate level of security is relatively useless, to begin with.

The Importance of Data Integrity

As a result data integrity becomes increasingly paramount, depending on the industry in which the software will be used. Expensive changes may be called for at a later date by auditors, but that’s only if the organization in question is relatively lucky.

In a worst-case scenario, hackers could find a way in, compromising not just the integrity of the data but the brand equity of the company too. That could cut any software development cycle drastically short. It doesn’t have to be that way, as the above steps show.

Capitalized letter, checklist, chart and calculator

Date: January, 2019 | CategoryQuality Author: Ryan Szporer


It’s easier to think of an audit trail as a collection of breadcrumbs leading out of the woods.

The Bright Side of Being Audited

Admittedly, the word “audit” gets a bad reputation. It’s usually associated with the unpleasant process of the same name that can be initiated by the U.S. Internal Revenue Service. In actuality, audits are an unavoidable part of life for many corporations in the sense that they can take place not once but multiple times a year. With an audit trail, they don’t have to be nearly as grueling as people have come to expect, though.

For the uninitiated, trails are the lists of transactions or events kept track of to help auditors and, in many ways, those being audited too. Of course, at its most fundamental level, a company’s audit trail does contain financial transactions. However, they can be chronological catalogs of so many more types of events. An audit is simply an investigation of accounts and records in general. They aren’t limited to those of the financial variety.

For example, audits can be key to achieving and maintaining regulatory compliance, which is in turn critical to operating in sectors like pharma. For a company that develops software intended to meet ISO compliance, perhaps for use within that same pharmaceutical industry, regular internal and external audits are to be expected.

External vs. Internal Audits

External audits can either be initiated by the relevant regulatory body (for certification purposes) or even a client that relies on the given software. Take a digital proofreading application for example.

Continuing within pharma, each piece of equipment that enters into a drug’s chain of custody has to be “validated” as meeting pre-determined specifications and attributes. Obviously, software qualifies as equipment in that context. It makes sense that a firm with as much at stake from a quality perspective as a pharmaceutical company would want to get assurances that a piece of equipment on which they rely comes as advertised as being compliant. It’s theoretically similar to how consumers depend on medication and accurate information on its packaging.

In contrast, an internal audit serves as an evaluation of the company’s effectiveness, from risk-management, governance, and process standpoints. As data integrity arguably touches on all three areas, its importance in a corporate environment cannot be understated. In fact, audits specifically aimed at examining data integrity are a real thing.

Benefiting from an Audit Trail

Regardless of the focus of an audit, trials are undeniably critical to their success. And success is what all parties should strive for, whether they’re doing the auditing or being audited. No one wins however unnecessarily hard one becomes to complete.

That’s one of the misconceptions regarding audit trails that is generally associated with the earlier IRS example. Obviously, an audit isn’t exactly something to look forward to, but it can be made less of a headache if all required records have been kept and are easily accessible to the auditors. Automated trails that are easily searchable make smooth audits more of a reality.

Trails are theoretically included in the software as one of many required technical controls that enable users to achieve compliance with 21 CFR Part 11 with the Food and Drug Administration (in the United States; equivalent to Annex 11 in the European Union). Compliance here ensures companies implement good business practices through reliable electronic records, which must be able to be accurately displayed and exported. Here, the audit trail serves to log what changes to application data were made, when, and by whom and be available for review.

Whoever ends up conducting that review, whether it’s an agency or the company itself, the auditor will no doubt thank you as the bigger picture begins to take shape. Identifying the individual trees is key to seeing the forest as a whole, though. Finding your way through can be hard, but an audit trail can clearly reveal the right path to take.

_________________________________________________________________________________________

Ensure your content is always error-free in record time with GlobalVision. Try it now for free. 

Keep up with the latest updates in automated proofreading software. Sign up for our newsletter. 

Why Error-Free Packaging, Labeling Is a Must

Date: November, 2018 | CategoryProofreading Author: Ryan Szporer


Pristine, error-free packaging, and labeling undeniably look good, but it’s more than that. It’s a necessity, regardless of the industry in question. Of course, it conveys brand strength, but, more importantly, it’s about respecting regulations that were put in place for a reason.

Mislabeling Misadventures

The strength of those regulations (and the severity of the penalties for breaking them) depends on the country. For example, in the United States, the Fair Packaging and Labeling Act with the Uniform Packaging and Labeling Regulation (UPLR; and National Institute of Standards and Technology Handbook 130) require consumer commodities to clearly disclose packaging’s contents and manufacturer info. The goal is for customers to be able to make informed purchasing decisions through the comparison of accurate price and quantity information on packaging.

Additional regulations meanwhile outlaw deceptive packaging and labeling. At both the federal and state levels, false advertising and labeling laws exist, with offenders risking additional liability to any victims. Victims can include consumers who are harmed by the product or businesses further down the supply chain who unwittingly purchased the product. If, on the other hand, a party down the supply chain discovers the fraud but fails to take action, they could be responsible too.

The aforementioned laws are admittedly not all-encompassing. State laws can differ and the FPLA sometimes delegates regulatory and enforcement responsibilities to the agencies who oversee individual industries instead. For example, the Food and Drug Administration regulates packaging and labeling in the food & beverage, cosmetics, medical devices, and pharmaceuticals sectors.

Food and Drug Labeling as a Case Study

Taking the food & beverage sector as an example, put simply, the packaging must contain what the label says it does. If the FDA has reason to believe packaging is inaccurate, that it falsely claims the product inside is 100% fruit juice, for example, imports can be detained without physical examination. The product effectively gets prevented from being distributed (and sold).

When a manufacturer is a guilty party, the FDA may issue a warning. In the event the manufacturer does not comply and correct the issue, the FDA takes additional legal action to ensure the product gets removed from the market, without it being permitted to return until the issue has been corrected. Criminal fines and even prosecution may result depending on the infraction.

Fines up to $500,000 for misdemeanors that result in death can be doled out. A misdemeanor, which would not require proven intent, can also result in up to one year in prison. A felony, which implies intent or a subsequent violation after the first, can lead to a maximum of three years instead.

In the case of the pharmaceutical industry, which is also under the purview of the FDA and whose customers depend on packaging for accurate dosage information, it’s easy to see why penalties need to be especially severe. A single misplaced period can have huge negative ramifications.

Performing Labeling and Packaging Inspections

A packaging or label error doesn’t have to be fraudulent to be costly. In fact, a great deal of mistakes are simply caused by human error. Market research indicates that 60% of product recalls are caused by workers. And it’s easy to see why. Typos can easily be created and then missed due to proofing fatigue during the artwork-creation and printing processes.

It only reinforces the need for failsafes, like a digital inspection platform, to improve upon the efficiency of a company’s quality control. Performing labeling and packaging inspections at each stage of the workflow reduces the risk of a recall and the number of required revision cycles, so products get to market faster, without any errors.

Inspections are going to be performed anyway, including potentially by the governing body in the question itself. It only makes sense that a company would want to put its best foot forward in preparation. Having previously integrated robust quality systems is one key to success in such an instance. Not having to correct an error after the fact is another key to success in general.

There is obviously a difference between fraudulent practices and innocent errors that simply do not get caught in time. Unfortunately, they can each have severe consequences. What separates them from one another is how, instead of actively trying to skirt regulations, companies can actively try to prevent mistakes. It just takes a conscious effort to improve upon internal processes.

_________________________________________________________________________________________

Get your complete guide to meeting FDA labeling requirements here

Take the first step towards error-free packaging and labels by starting your free trial of GlobalVision

Learn how some of the world’s top pharma companies have cracked the efficiency code with automation

Cartoon of the quality management system for ISO regulation

Date: August, 2018 | CategoryQuality Author: Marvin Magasura


 
 
 
 

What is a Quality Management System? 

A quality management system (QMS) is a term that refers to a system in charge of documenting all processes, responsibilities, and procedures for achieving quality objectives and policies. A QMS allows companies to direct and coordinate their operations to meet both regulatory and customer requirements while also improving their efficiency and effectiveness on a regular basis.

ISO 9001:2015 is the international standard that specifies all the requirements needed to implement a quality management system. In fact, most people use the term QMS as a synonym for the ISO 9001 family even though the latter is only a document that describes the former.

The Importance of a Quality Management System

Why is it so important to implement a quality management system into your quality processes? Quality management systems actually serve plenty of purposes, including:

  • Engaging staff
  • Lowering costs
  • Reducing wasted materials
  • Setting company-wide direction
  • Identifying and facilitating training opportunities
  • Improving processes

Benefits of Quality Management Systems

What are the advantages of using a Quality Management System?

Once implemented, quality management systems have the power to affect all aspects of your company’s performance. However, the design and implementation of a QMS will bring you two overarching benefits:

  1. Meeting the organization’s requirements ensures that your company complies with industry regulations and provisions of services and products in the most cost-effective way. In the end, this will create room for growth, expansion, and profit.
  2. Meeting customers’ needs will help to build trust in your company, in turn engaging even more customers, sales, and profits.

Other advantages include preventing errors, reducing costs, helping to communicate a willingness to produce consistent results, improving your company’s offerings, and ensuring all processes are completely controlled and defined.

 

 

Quality Management Standards

As we previously mentioned, the ISO 9001:2015 standard describes all the requirements that a company must meet to implement its own quality management system. By far ISO 9001:2015 is the most implemented and recognized QMS standard on the planet that counts for complete international acceptance.

However, there are plenty of other QMS standards available, such as the ISO 14000 family that deals with environmental management systems, the rest of the ISO 9000 family (including both ISO 9004 and ISO 9000), ISO/TS 16949 for QMS intended for automotive-related products, ISO 13485 for medical devices, and ISO 19011 for auditing management systems.

Requirements to Implement a Quality Management System

All quality management systems must address a company’s unique set of needs; however, we can name a few general elements that all QMS have in common, such as:

  • The creation of a quality manual.
  • The existence of quality objectives and policies.
  • A set of procedures, records, and instructions about all internal processes, data management, quality analysis, improvement opportunities, and customer satisfaction.

Each aspect of a QMS is intended to serve a specific purpose that in the end will help to achieve the final goal: meeting both the organization’s and customer’s needs.

How to Implement a Quality Management System

Before establishing a QMS, you must consider several elements. To begin, make sure that your decision to implement a quality management system is a strategic choice only influenced by your needs, objectives, services, and products provided. Now that you’re clear about what to do, here are the basic steps to implement a QMS:

  • Design and Build: They deal with the structure of the QMS, along with the plan for implementation and all its processes.
  • Deploy: In this stage, you’ll need to break each process into multiple sub-processes. It also includes staff education and documentation, training tools, and metrics.
  • Control and Measure: These stages are accomplished by systematic, routine audits of your QMS.
  • Review and Improve: In this stage, you’ll deal with the results of the audits. The goal is to determine the efficiency and effectiveness of all your processes regarding your objectives.

Conclusion

A product’s quality can be measured in terms of durability, reliability, and performance. Quality is a crucial element that differentiates your company from its competitors. By implementing proper quality management systems, you are ensuring that all necessary changes in your processes are implemented, which eventually leads to superior quality products and, in the end, bigger profits.

Are you ready to streamline your workflows by implementing a quality management system? Learn more by requesting a demo of GlobalVision here or try our web-based proofreading software, Verify, for free!


Maintaining Data Integrity with GlobalVision Software

Read our whitepaper on how GlobalVision complies with data integrity requirements, such as:
electronic signatures, different access levels and security, and an audit trail with full traceability.

Related articles:

What is data integrity? 

Automated Quality Control

Quality inspection system