Tag Archives: document

Top 10 Common Findings Detected During Cannabis Laboratory Assessments: A Guide to Assist with Accreditation

By Tracy Szerszen
No Comments

With the cannabis industry growing rapidly, laboratories are adapting to the new market demand for medical cannabis testing in accordance to ISO/IEC 17025. Third-party accreditation bodies, such as Perry Johnson Laboratory Accreditation, Inc. (PJLA), conduct these assessments to determine that laboratories are following relevant medical cannabis testing standard protocols in order to detect potency and contaminant levels in cannabis. Additionally, laboratories are required to implement and maintain a quality management system throughout their facility. Obtaining accreditation is a challenge for laboratories initially going through the process. There are many requirements outlined in the standard that laboratories must adhere to in order to obtain a final certificate of accreditation. Laboratories should evaluate the ISO 17025 standard thoroughly, receive adequate training, implement the standard within their facility and conduct an internal audit in order to prepare for a third-party assessment. Being prepared will ultimately reduce the number of findings detected during the on-site assessment. Listed below is research and evidence gathered by PJLA to determine the top ten findings by clause specifically in relation to cannabis testing laboratories.

PJLA chart
The top 10 findings by clause

4.2: Management System

  • Defined roles and responsibilities of management system and its quality policies, including a structured outline of supporting procedures, requirements of the policy statement and establishment of objectives.
  • Providing evidence of establishing the development, implementation and maintenance of the management system appropriate to the scope of activities and the continuous improvement of its effectiveness.
  • Ensuring the integrity of the management system during planned and implemented changes.
  • Communication from management of the importance of meeting customer, statutory and regulatory requirements

4.3: Document Control

  • Establishing and maintaining procedures to control all documents that form the management system.
  • The review of document approvals, issuance and changes.

4.6: Purchasing Services and Supplies

  • Policies and procedures for the selection and purchasing of services and supplies, inspection and verification of services and supplies
  • Review and approval of purchasing documents containing data describing the services and supplies ordered
  • Maintaining records for the evaluation of suppliers of critical consumables, supplies and services, which affect the quality of laboratory outputs.

4.13: Control of Records

  • Establishing and maintaining procedures for identification, collection, indexing, access, filing, storage and disposal of quality and technical records.
  • Providing procedures to protect and back-up records stored electronically and to prevent unauthorized access.

4.14: Internal Audits

  • Having a predetermined schedule and procedure for conducting internal audits of its activities and that addresses all elements that verify its compliance of its established management system and ISO/IEC 17025
  • Completing and recording corrective actions arising from internal audits in a timely manner, follow-up activities of implementation and verification of effectiveness of corrective actions taken.

5.2: Personnel

  • Laboratory management not ensuring the competence and qualifications of all personnel who operate specific equipment, perform tests, evaluate test results and sign test reports. Lack of personnel undergoing training and providing appropriate supervision
  • Providing a training program policies and procedures for an effective training program that is appropriate; identification and review of training needs and the program’s effectiveness to demonstrate competence.
  • Lack of maintaining records of training actions taken, current job descriptions for managerial, technical and key support personnel involved in testing

5.4: Test and Calibration Methods and Method Validation

  • Utilization of appropriate laboratory methods and procedures for all testing within the labs scope; including sampling, handling, transport, storage and preparation of items being tested, and where appropriate, a procedure for an estimation of the measurement of uncertainty and statistical techniques for analysis
  • Up-to-date instructions on the use and operation of all relevant equipment, and on the handling and preparation of items for testing
  • Introduction laboratory-developed and non-standard methods and developing procedures prior to implementation.
  • Validating non-standard methods in accordance with the standard
  • Not completing appropriate checks in a systematic manner for calculations and data transfers

5.6: Measurement Traceability

  • Ensuring that equipment used has the associated measurement uncertainty needed for traceability of measurements to SI units or certified reference materials and completing intermediate checks needed according to a defined procedure and schedules.
  • Not having procedures for safe handling, transport, storage and use of reference standards and materials that prevent contamination or deterioration of its integrity.

5.10: Reporting the Results

  • Test reports not meeting the standard requirements, statements of compliance with accounting for uncertainty, not providing evidence for measurement traceability, inaccurately amending reports.

SOP-3: Use of the Logo

  • Inappropriate use of PJLA’s logo on the laboratories test reports and/or website.
  • Using the incorrect logo for the testing laboratory or using the logo without prior approval from PJLA.
VinceSebald
Soapbox

Automation – Planning is Everything

By Vince Sebald
No Comments
VinceSebald

Automation of processes can provide great benefits including improved quality, improved throughput, more consistency, more available production data, notifications of significant events and reduced costs. However, automation can also be expensive, overwhelm your workforce, cause future integration problems and magnify issues that you are currently experiencing. After all, if a machine can do work 100 times faster than a human, it can also produce problems 100 times faster than a human. Whether it is a benefit or a scourge depends largely on the implementation process.

There are thousands of possible technology solutions for just about any production problem. The trick to getting results that will work for your company is to use good engineering practices starting from the beginning. Good engineering practices are documented in various publications including ISPE Baseline Guides, but there are common threads among all such guides. What will the system be used for and what problem is it intended to solve?

The key is implementing a system that is fit for your intended use. As obvious as it sounds, this is often the most overlooked challenge of the process. In the grand scheme of things, it is a MUCH better proposition to spend more time planning and have a smooth operation than implement a system quickly and fight it because it isn’t a good fit for the intended use. The industry is littered with systems that were prematurely implemented and complicate rather than simplify operations. Planning is cheap, but fixing is expensive.

The most important step to getting an automated system that will work for you is also the first:

Defining “what” you need the system to do: User Requirements

Automation Runaway
Once automation is in place, it can be a boon to production, but don’t let your systems get ahead of your planning! It can be difficult to catch up.

With decades of experience in the automation industry, I have seen systems in many industries and applications and it is universally true that the definition of requirements is key to the success of the automation adventure. To clarify, the user requirements are intended to define “what” the system is required to do, rather than “how” it will do it. This means that persons that may not be familiar with the automation technologies can still be (and usually are) among the most important contributors to the user requirements document. Often, the people most familiar with the task that you wish to automate can contribute the most to the User Requirements document.

Some of the components of a User Requirements document typically include:

  • Purpose: What will the system be used for and what problem is it intended to solve?
  • Users: Who will be the users of the system and what is their relevant experience?
  • Integration: Is the system required to integrate into any existing or anticipated systems?
  • Regulatory Requirements: Is the system required to meet any regulatory requirements?
  • Functions: What is the system required to do? This may include operating ranges, operator interface information, records generation and storage, security, etc.
  • Performance: How many units per hour are required to process?  What percent non-conforming product is acceptable?
  • Environment: What environment is the system required to operate in? Indoor, outdoor, flammable, etc.
  • Documentation: What documentation is required with the system to support ongoing maintenance, calibration, etc.?
  • Warranties/Support: Will you perform work in-house, or will the manufacturer support the system?

The level of detail in the User Requirements should be scaled to the intended use. More critical operations may require more detailed and formal User Requirements. At a minimum, the User Requirements could be a punch list of items, but a detailed User Requirements may fill binders. The important thing is that you have one, and that the stakeholders in the operation have been involved in its production and approval.Once completed, the User Requirements can be a very good document to have for prospective providers of solutions to focus their attention on what is important to you, the customer.

Equally important to the process is the idea of not over-constraining the potential solutions by including “how” the system will meet the requirements within the User Requirements. If it is required to use specific technologies for integration with other existing systems, it is appropriate to include that information in the User Requirements. However, if use of a particular technology (e.g. “wireless”) is not required, the inclusion may unnecessarily eliminate viable design options for systems that may address the requirements.

Once completed, the User Requirements can be a very good document to have for prospective providers of solutions to focus their attention on what is important to you, the customer. This helps to ensure that they focus their efforts in the areas that match your needs and they don’t waste resources (which translate to your costs) in areas that don’t have tangible benefits to you, the customer. It also gives you a great tool to “value engineer”, meaning that you can consider cutting design options that do not support the User Requirements, which can reduce project costs and timelines, keeping things lean and on track.

Further steps in the project are built around the User Requirements including system specifications provided by vendors, testing documentation and the overall turnover package. An appropriately scaled User Requirements document is a low cost, easy way to ensure that your automated system will serve you well for years to come. Alternatively, the lack of a User Requirements document is an all-too-common indicator that there may be challenges ahead including scope creep, missed deadlines and unacceptable long term performance.


Feel free to reach Vince at vjs@sebaldconsulting.com with any questions you might have.

HACCP

Hazard Analysis and Critical Control Points (HACCP) for the Cannabis Industry: Part 1

By Kathy Knutson, Ph.D.
No Comments
HACCP

Hazard Analysis and Critical Control Points (HACCP) Defined

Farm-to-fork is a concept to describe the control of food safety starting in the fields of a farm and ending with deliciousness in my mouth. The more that is optimized at every step, the more food safety and quality are realized. Farm-to-fork is not a concept reserved for foodies or “eat local” food campaigns and applies to all scales of food manufacture. HACCP is like putting the last piece of a huge puzzle in the middle and seeing the whole picture develop. HACCP is a program to control food safety at the step of food processing. In states where cannabis is legal, the state department of public health or state department of agriculture may require food manufacturers to have a HACCP plan. The HACCP plan is a written document identifying food safety hazards and how those hazards are controlled by the manufacturer. While there are many resources available for writing a HACCP plan, like solving that puzzle, it is a do-it-yourself project. You can’t use someone else’s “puzzle,” and you can’t put the box on a shelf and say you have a “puzzle.”

HACCP is pronounced “ha” as in “hat” plus “sip.”

(Say it aloud.)

3-2-1 We have liftoff.

The history of HACCP starts not with Adam eating in the garden of Eden but with the development of manned missions to the moon, the race to space in the 1950s. Sorry to be gross, but imagine an astronaut with vomiting and diarrhea as a result of foodborne illness. In the 1950s, the food industry relied on finished product testing to determine safety. Testing is destructive of product, and there is no amount of finished product testing that will determine food is safe enough for astronauts. Instead, the food industry built safety into the process. Temperature was monitored and recorded. Acidity measured by pH is an easy test. Rather than waiting to test the finished product in its sealed package, the food industry writes specifications for ingredients, ensures equipment is clean and sanitized, and monitors processing and packaging. HACCP was born first for astronauts and now for everyone.HACCP

HACCP is not the only food safety program.

If you are just learning about HACCP, it is a great place to start! There is a big world of food safety programs. HACCP is required by the United States Department of Agriculture for meat processors. The Food and Drug Administration (FDA) requires HACCP for seafood processing and 100% juice manufacture. For all foods beyond meat, seafood and juice, FDA has the Food Safety Modernization Act (FSMA) to enforce food safety. FSMA was signed in 2011 and became enforceable for companies with more than 500 employees in September of 2016; all food companies are under enforcement in September 2018. FSMA requires all food companies with an annual revenue greater than $1 million to follow a written food safety plan. Both FDA inspectors and industry professionals are working to meet the requirements of FSMA. There are also national and international guidelines for food safety with elements of HACCP which do not carry the letter of law.

The first step in HACCP is a hazard analysis.

Traditionally HACCP has focused on processing and packaging. Your organization may call that manufacturing or operations. In a large facility there is metering of ingredients by weight or volume and mixing. A recipe or batch sheet is followed. Most, but not all, products have a kill step where high heat is applied through roasting, baking, frying or canning. The food is sealed in packaging, labeled, boxed and heads out for distribution. For your hazard analysis, you identify the potential hazards that could cause injury or illness, if not controlled during processing. Think about all the potential hazards:

  • Biological: What pathogens are you killing in the kill step? What pathogens could get in to the product before packaging is sealed?
  • Chemical: Pesticides, industrial chemicals, mycotoxins and allergens are concerns.
  • Physical: Evaluate the potential for choking hazards and glass, wood, hard plastic and metal.

The hazards analysis drives everything you do for food safety.

I cannot emphasize too much the importance of the hazard analysis. Every food safety decision is grounded in the hazard analysis. Procedures will be developed and capital will be purchased based on the hazard analysis and control of food safety in your product. There is no one form for the completion of a hazard analysis.

HACCP risk matrix
A risk severity matrix. Many HACCP training programs have these.

So where do you start? Create a flow diagram naming all the steps in processing and packaging. If your flow diagram starts with Receiving of ingredients, then the next step is Storage of ingredients; include packaging with Receiving and Storage. From Storage, ingredients and packaging are gathered for a batch. Draw out the processing steps in order and through to Packaging. After Packaging, there is finished product Storage and Distribution. Remember HACCP focuses on the processing and packaging steps. It is not necessary to detail each step on the flow diagram, just name the step, e.g. Mixing, Filling, Baking, etc. Other supporting documents have the details of each step.

For every step on the flow diagram, identify hazards.

Transfer the name of the step to the hazard analysis form of your choice. Focus on one step at a time. Identify biological, chemical and physical hazards, if any, at that step. The next part is tricky. For each hazard identified, determine the probability of the hazard occurring and severity of illness or injury. Some hazards are easy like allergens. If you have an ingredient that contains an allergen, the probability is high. Because people can die from ingestion of allergens when allergic, the severity is high. Allergens are a hazard you must control. What about pesticides? What is the probability and severity? I can hear you say that you are going to control pesticides through your purchasing agreements. Great! Pesticides are still a hazard to identify in your hazard analysis. What you do about the hazard is up to you.

Open For Business: California Market Launches

By Aaron G. Biros
No Comments

California’s full legal cannabis market officially opened its doors for business on January 1st, 2018. Following a relatively short time frame when they announced the first licenses awarded less than a month ago, retail stores were open for business in counties throughout California. Customers came out in full force, with long lines on the opening day, with some hundreds deep stretching around blocks.

For the quick turn around time between implementing regulations and awarding temporary licenses, the grand opening of the cannabis market in the nation’s most populous state proceeded smoothly. Only a handful of minor hiccups associated with the launch were reported throughout the state. In the grand scheme of things, that’s a pretty good job for a new regulatory agency (The Bureau) tasked with regulating such a massive fledgling market.

One major and definitely foreseeable hiccup in the launch of California’s new medical and adult use markets was the failure to implement tracking software. According to Michael Blood with The Associated Press, licensed businesses are being asked by the California Department of Food and Agriculture to manually document sales and transfers of cannabis with paper invoices.

Los Angeles
Image: Kevin Stanchfield, Flickr

While the Department said the traceability system was implemented Tuesday, Blood says, cannabis businesses are not required to use it and will be trained on how to operate it before it becomes required to use later in 2018.

Local control regulations in California means that businesses must first seek approval from local authorities before attaining a temporary license from the state to operate. That coupled with the rolling process of awarding licenses meant that only some cannabis businesses could officially open their doors. Municipalities throughout California handle regulating cannabis differently.

The handful of adult use dispensaries with temporary licenses in the Los Angeles area received a massive influx of customers on opening day. Residents of LA came in droves to the four West Hollywood dispensaries open for adult use business.

Soapbox

When the Company’s Revenue Drops, Who’s to Blame?

By Dr. Ginette M. Collazo
No Comments

The ultimate goal of any business is to produce and generate revenue. Now, when the company’s revenues drop, who’s fault is it? This question, though silent, is in the minds of everyone in an organization, especially when things start to become difficult.

Working as a consultant in productivity with different industries around the world, I have come to realize that question is not openly discussed, but everyone wants to know the answer. To answer it, we will explore the most common areas of opportunity related to this problem.

When we talk about productivity, we are talking about final tangible results, because of the production process and the effort made by each one; when speaking of income, we are talking about the difference between the purchase price and the cost of entering the market. Seeing these definitions, we might conclude that the increase in income is directly related to the increase in productivity.

On the other hand, we must not lose perspective that the increase in productivity is also directly related to the decrease of losses.

First, we have to put into perspective the goals and objectives that a business or organization may have. Many companies go on believing that everyone is clear about the goals and organizational objectives and what is expected in each one of those roles that compose the organization. The reality is that, if we do not know where we are going, the chances of reaching the goal decrease.

When organization’s objectives are properly communicated, and documented, in such a way that the evaluation of the performance is directly linked to the expected results, the chances of success increase substantially.

On many occasions, I have heard phrases such as: “we work hard, we spend many hours, all sacrifice ourselves… we should be more successful”. The question then is: what are we encouraging, efforts or results?

It is hard for organizations to translate or differentiate between organizational goals and individual objectives (expected results) for each of those roles in the company. We all agree that we want to be the first in sales, the best in service and produce the highest quality, but how is that done?

To be the first in sales, what do I have to do as a seller? Get three customers in a three-month period? As secretary, process the orders in the first three days of receiving them? As a carrier, suggest three ideas be more useful in daily deliveries? How does that translate into individual performance?

We focus too much on telling people what they must do, but we forget to be clear on what we expect them to achieve. Hence, the effort versus result dissonance. The success of an organization is the collective behavior that arises from the conduct of individuals. If we align people, we align the organization.

Other elements that we must ponder, and that are directly related to productivity, are: how much of what we do holds value? How much of what we do does not have value? Moreover, how much of what we do, though it has great value, shall be performed by the requirements of law or regulation?

An analysis of productivity is critical, particularly in a time when we want to do more with less. Lately, an area of great success for many organizations is to streamline processes to make them more simple, efficient and with less risk of error. Human errors generated many losses. Defects, the re-process, the handling of complaints and lawsuits are costing companies money equivalent to the salary of 7,200 employees every day (according to statistics in the United States).

Human errors can be avoided. The idea that to err is human has led us to ignore this problem. We think that we can do nothing and lose an infinite number of opportunities for improvement that can help us to increase our income, reducing losses.

Only 16% of organizations measure the cost of human error. The remaining 84% do not measure it and are paying a high price without knowing it. In Puerto Rico, there are no statistics that could shed light on how many local companies lose because of human error, but it is very likely that the numbers are alarming. Human error can be reduced by 60% in less than a year when an intervention is done on systems. Approximately 95% of human errors are due to the design of the company’s systems, and they can be the simplest errors even in the most complex processes.

Today, we have more information, and we know that errors are symptoms of deeper problems in the processes created by the organizations. People play a crucial role regarding how robust methods are, but, we must not lose perspective that human beings operate according to the policies, procedures, and instructions which the same organization designs. Then, if people work according to the designs of the organization, is it not easier to modify designs than eliminating people?

So, who’s fault? Organizations are responsible for providing clear guidance to individuals in the right direction, and individuals have the responsibility of translating their efforts into results. Both have to work with the same objective in mind, and both employers and employees should communicate openly about these objectives. Only by working in partnership will achieve success. Forget who is to blame and focus on the processes and goals that help us be successful.