<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[The (In)Validator’s Dilemma - Medium]]></title>
        <description><![CDATA[Valid or InValid? - Medium]]></description>
        <link>https://medium.com/the-in-validators-dilemma?source=rss----e6c55a1bf75---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The (In)Validator’s Dilemma - Medium</title>
            <link>https://medium.com/the-in-validators-dilemma?source=rss----e6c55a1bf75---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:06:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-in-validators-dilemma" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[49 Ways to Leave Your eImpact]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-in-validators-dilemma/49-ways-to-leave-your-eimpact-9909ecbaa438?source=rss----e6c55a1bf75---4"><img src="https://cdn-images-1.medium.com/max/600/1*NupW0-TH28D6w0XKRonVDA.png" width="600"></a></p><p class="medium-feed-snippet">Appendix I: The eValidator&#x2019;s Solution</p><p class="medium-feed-link"><a href="https://medium.com/the-in-validators-dilemma/49-ways-to-leave-your-eimpact-9909ecbaa438?source=rss----e6c55a1bf75---4">Continue reading on The (In)Validator’s Dilemma »</a></p></div>]]></description>
            <link>https://medium.com/the-in-validators-dilemma/49-ways-to-leave-your-eimpact-9909ecbaa438?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/9909ecbaa438</guid>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Wed, 14 Apr 2021 16:48:20 GMT</pubDate>
            <atom:updated>2021-04-17T15:11:53.705Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[To: Alex Gorsky; Subject: ethical Validation and Our Credo]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-in-validators-dilemma/to-alex-gorsky-subject-ethical-validation-and-our-credo-3e44902dca6a?source=rss----e6c55a1bf75---4"><img src="https://cdn-images-1.medium.com/max/2012/1*kdy9wFpT3svsBf-JvS3-3g.jpeg" width="2012"></a></p><p class="medium-feed-snippet">Dear Alex,</p><p class="medium-feed-link"><a href="https://medium.com/the-in-validators-dilemma/to-alex-gorsky-subject-ethical-validation-and-our-credo-3e44902dca6a?source=rss----e6c55a1bf75---4">Continue reading on The (In)Validator’s Dilemma »</a></p></div>]]></description>
            <link>https://medium.com/the-in-validators-dilemma/to-alex-gorsky-subject-ethical-validation-and-our-credo-3e44902dca6a?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/3e44902dca6a</guid>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 05:01:01 GMT</pubDate>
            <atom:updated>2020-01-19T15:48:47.985Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Conceptual Integrity of The Corporation: The Manifesto]]></title>
            <link>https://medium.com/the-in-validators-dilemma/the-conceptual-integrity-of-the-corporation-the-manifesto-8c1218e76b3a?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c1218e76b3a</guid>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Fri, 23 Aug 2019 15:10:25 GMT</pubDate>
            <atom:updated>2019-08-23T15:22:18.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p-suxSrmR02qYvx-3rAZog.jpeg" /><figcaption>The Sagrada Familia, Gaudi’s ecosystem with Conceptual Integrity (iStockPhoto)</figcaption></figure><h3><strong>Preamble: Inspiration from The Masters</strong></h3><p>What happens when Peter F. Drucker’s <a href="https://en.wikipedia.org/wiki/Concept_of_the_Corporation"><em>Concept of The Corporation</em></a> meets Frederick P. Brooks, Jr.’s <em>The Mythical Man-Month</em> “<a href="https://en.wikipedia.org/wiki/The_Mythical_Man-Month#Conceptual_integrity">Conceptual Integrity</a>”?</p><p>Around the same time Drucker penned <a href="https://hbr.org/1994/09/the-theory-of-the-business"><em>The Theory of the Business</em></a>, Brooks was writing <a href="https://en.wikipedia.org/wiki/No_Silver_Bullet"><em>No Silver Bullet: Essence and Accident in Software Engineering</em></a> and issuing the second edition of his seminal book, <a href="https://en.wikipedia.org/wiki/The_Mythical_Man-Month"><em>The Mythical Man-Month</em></a>. One can imagine Peter meeting Fred and an integration of their collective theses; we’d have even greater quality products and we’d have more-engaged workers and workplaces. An opportunity?</p><p>Success in the digital transformation era mandates more integration, greater engagement, and a common decision-making framework…at all levels. It’s the workers closest to the customer who are making decisions on behalf of the organization, mostly decisions in software code. Consistency of method is required.</p><p><em>The Conceptual Integrity of The Corporation</em> is a synthesis of Drucker’s Theory of the Business (ToB) and Brooks’ Conceptual Integrity (CI). It’s a melding of business architectural principles — doing <em>right things</em>, with emphasis on the importance of knowledge workers, and computer/software architectural principles — doing <em>right things</em>, with emphasis on simplicity and straightforwardness; both implored consistent and continuous management of change, knowing what to leave in and what to leave out.</p><p>This is a tribute to the memory of Dr. Peter Drucker and the continuing legacy of Dr. Frederick Brooks, <em>The Conceptual Integrity Manifesto</em>; a meta-framework for making decisions, decisions of validation.</p><p>Brooks’ elusive “silver bullet” has by and large been resolved in the “accidental” (later termed incidental), (software) construction portion of the equation; e.g., Agile, open source, integrated development environments. It is in the “essence”, the “mental crafting of the conceptual construct” (Brooks) where Drucker and Brooks converge. CoC explored the social aspects of the productive work environment and observed the conundrum of “<a href="https://en.wikipedia.org/wiki/Brooks%27s_law">Brooks’ Law</a>” (before it became “law”) and advocated horizontal decision-making. Brooks’ thesis doesn’t explicitly consider people first, however, in applying an architect’s conceptual integrity mindset, and teaching and entrusting that mindset in others and in micro and macro decision-making, results a win-win for organizations and associates whether high-tech or otherwise.</p><p>Continuous decision-making, that is, continuous validation of the organization’s conceptual integrity, results in doing more <em>right things</em> (essence) and less waste — doing <em>right things right</em> (incidental) and in <em>not</em> doing wrong, wasteful things right. In essence, your ladder will be “leaning against the right building” (Drucker) and you’ll be able to recognize and move it quickly if not.</p><h3><strong>The Manifesto: The Map</strong></h3><p>In <a href="https://www.amazon.com/Linchpin-Are-Indispensable-Seth-Godin/dp/1591844096"><em>Linchpin</em></a>, author/systems thinker, Seth Godin, goads us into “making a map” for others. The map and its pieces have been researched and many of its proofs with objective evidence confirmed by others. 80% of the work is leverageable; 20% of the remaining creative work, learning, and customization is, as they say in Ontario, CA, “yours to discover”. Or, recently, it’s “<a href="https://www.cbc.ca/news/canada/toronto/ontario-licence-plate-slogan-place-to-grow-yours-discover-1.5090614">a place to grow</a>”.</p><p><strong>A Conceptual Integrity Framework (CIF):</strong></p><p>Step 0 (zero): Don’t throw out anything you’re already doing!! Agile? Keep doing it! CMMI? Keep doing it! 6-Sigma? Keep doing it! Don’t know or nothing? Start here: start with validation! Remember, doing more decisions of validation will lead to less verification (and wasted verification). The “secret” (Peter Thiel’s <a href="https://www.amazon.com/Zero-One-Notes-Startups-Future/dp/0804139296/ref=sr_1_3?crid=39OBN51WFT5T3&amp;keywords=zero+to+one+peter+thiel&amp;qid=1566504611&amp;s=gateway&amp;sprefix=zero+to+one%2Caps%2C152&amp;sr=8-3"><em>Zero to One</em></a>) and the paradox of <em>doing more with less</em>: doing more (validation) results in doing less (verification) and less overall.</p><ol><li>Define your conceptual integrity with inspiration and guidance from Simon Sinek’s <a href="https://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447/ref=sr_1_3?crid=3P1FNWQ3ISTHO&amp;keywords=start+with+why&amp;qid=1566504872&amp;s=gateway&amp;sprefix=start+%2Caps%2C149&amp;sr=8-3"><em>Start With Why</em></a> and <a href="https://www.amazon.com/Find-Your-Why-Practical-Discovering/dp/0143111728/ref=pd_bxgy_14_img_3/130-8973772-5402539?_encoding=UTF8&amp;pd_rd_i=0143111728&amp;pd_rd_r=7be6bf6a-a039-446f-ba3c-a76878a15e87&amp;pd_rd_w=Xws49&amp;pd_rd_wg=GS4xP&amp;pf_rd_p=a2006322-0bc0-4db9-a08e-d168c18ce6f0&amp;pf_rd_r=XF2VJGS32CNZA7F3D03G&amp;psc=1&amp;refRID=XF2VJGS32CNZA7F3D03G"><em>Find Your Why</em></a>. Your “why” leads the way to your conceptual integrity.</li><li>Once you’ve found your why, apply Miller’s Law — <a href="https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two">the magical number of seven plus or minus two</a> — using it to define your 7 +/- 2 one-word Conceptual Integrity Attributes (CIAs). Use the Pareto principle as espoused in Richard Koch’s <a href="https://www.amazon.com/80-20-Principle-Secret-Achieving/dp/0385491743/ref=sr_1_2?crid=23IN0GAL0JK4Y&amp;keywords=koch+80%2F20&amp;qid=1566505004&amp;s=gateway&amp;sprefix=koch+80%2Caps%2C150&amp;sr=8-2"><em>The 80/20 Principle</em></a> to refine down to your “about 7” CIAs.</li><li>Once you’ve defined your attributes, your CIA1-CIAn, develop your CI/validation checklist of questions. Ask: <em>What is the potential impact of &lt;doing something (or not doing something)&gt;?</em> In considering each of your CIAs; the total impact on your product’s/organization’s conceptual integrity. Impacts consider customers, associates, and the organization’s reputation. (For an example of “Bailey’s Law of TRACS”, see <a href="https://medium.com/the-in-validators-dilemma/time-for-the-fda-to-in-validate-modernize-its-thinking-on-validation-723565937f60"><em>Time for the FDA to Update its Thinking on Validation?</em></a> or an update in <a href="https://secure.asq.org/perl/msg.pl?prvurl=http://asq.org/software-quality/2019/05/software-quality/should-the-fda-modernize-its-thinking-on-validation.pdf">ASQ Software Quality Professional — June 2019</a>.)</li><li>Now, for every decision, implicit (micro) and explicit (macro), ask the questions; develop the mindset and the habit. <em>“What is the potential impact…?”</em> Allow yourself to exercise Daniel Kahneman’s “system 1” and “system 2” from <a href="https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow"><em>Thinking, Fast and Slow</em></a>, being aware that your immediate (system 1) reaction is often incorrect or too narrowly focused and that waiting on your methodical (system 2) analysis will more often yield a better outcome. Caution: Avoid groupthink and “what you see is all there is”/WYSIATI (Kahneman) by applying “Janusian thinking” thereby challenging the directly opposing viewpoint. It’s our human nature to imagine only the good impacts, but the potential bad impacts can be elusive and sometimes devastating. (See Dorie Clark’s <a href="https://www.amazon.com/Stand-Out-Breakthrough-Following-Around/dp/1591847400/ref=sr_1_2?keywords=stand+out+clark&amp;qid=1566506219&amp;s=gateway&amp;sr=8-2"><em>Stand Out</em></a> and <a href="https://bit.ly/2Z22oh4">Albert Rothenberg’s original paper</a> for more on Janusian thinking. Also, Dorie’s Chapter 5, Create a Framework, inspired this meta-framework.) (In <em>TF&amp;S</em>, also see section <em>The Illusion of Validity</em>.)</li><li>Now, in considering alternatives and impacts, “Farrell’s Law of 3 Alternatives”: for every needed-solution (requirement, feature, bug/problem fix, acquisition consideration, &lt;a thing to do&gt;), posit 3 alternative solutions: 1) a good, finite quick fix/minimum viable product (Eric Ries, <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898/ref=sr_1_3?crid=3Q7CN1Z7MJFK0&amp;keywords=the+lean+startup&amp;qid=1566506607&amp;s=gateway&amp;sprefix=the+lean+s%2Caps%2C149&amp;sr=8-3"><em>The Lean Startup</em></a>); 2) a long-term better alternative; 3) a best infinite alternative. Optionally, Alternative 0 (Zero)) the do-nothing alternative, a documented decision/choice as to why it’s not worth pursuing…at this time.</li><li>Make the decision, document it, communicate it, and…revisit it. Build your knowledge-base. (See Ray Dalio’s <a href="https://www.amazon.com/Principles-Life-Work-Ray-Dalio/dp/1501124021/ref=sr_1_3?crid=78YB5MHLS5U3&amp;keywords=principles+ray+dalio&amp;qid=1566506780&amp;s=gateway&amp;sprefix=principles%2Caps%2C1149&amp;sr=8-3"><em>Principles</em></a>; collect and then connect your “dots”.)</li><li>Make the plan, then Execute the plan. Expect iteration. (See Safi Bahcall’s <a href="https://www.amazon.com/s?k=loonshots+by+safi+bahcall&amp;crid=3BT87LFBC7650&amp;sprefix=loonshots+%2Caps%2C979&amp;ref=nb_sb_ss_i_4_10"><em>Loonshots</em></a><em>; </em>actively manage your “dynamic equilibrium”, the recursive validation to verification phase transitions. Drucker’s ToB spec#4: “The theory of the business has to be tested constantly.”)</li></ol><p>In summary, when problems occur or opportunities present, don’t delay. Apply the CI framework — ask your 7 questions; think fast; think slow; think Janusian; consider 3 solutions — then decide!</p><p>Embrace conceptual integrity thinking and actions — <em>continuous validation</em> — as your new organizational culture. Most of all, protect your associates, and their dignity, by consistently applying the framework and entrusting them to do so as well.</p><h3><strong>The Possibility</strong></h3><p>Vision: Products achieving true validation and valuation; <em>validation beyond quality</em></p><p>Outcome: <em>Valid and validated products if and only if valid and validated workers</em>; win-win</p><p>Formula: <em>Quality = Validation &amp; Valuation</em>; no longer only Verification &amp; (then) Validation</p><p>(ɔ)2019 Conceptual Integrity Group LLC</p><p><em>Gregory Keyes is Chief Validation Officer at Conceptual Integrity Consulting, located near Rochester, NY USA. He assists companies and organizations in applying the Conceptual Integrity Framework to their decision-making, design/development, and organization development practices. He is author/curator of </em><a href="https://medium.com/the-in-validators-dilemma"><em>The (In)Validator’s Dilemma</em></a><em> publication. Connect with him on </em><a href="https://www.linkedin.com/in/gregorykeyescva/"><em>LinkedIn</em></a><em> or greg@conceptualintegrityconsulting.com.</em></p><p>This article also appears on <a href="https://www.linkedin.com/pulse/conceptual-integrity-corporation-manifesto-gregory-keyes/?published=t">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c1218e76b3a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-in-validators-dilemma/the-conceptual-integrity-of-the-corporation-the-manifesto-8c1218e76b3a">The Conceptual Integrity of The Corporation: The Manifesto</a> was originally published in <a href="https://medium.com/the-in-validators-dilemma">The (In)Validator’s Dilemma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Medical Devices: Does Validation End?]]></title>
            <link>https://medium.com/the-in-validators-dilemma/medical-devices-does-validation-end-51d0b0a07073?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/51d0b0a07073</guid>
            <category><![CDATA[validation]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[safety]]></category>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[fda]]></category>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Tue, 30 Jul 2019 03:54:14 GMT</pubDate>
            <atom:updated>2019-07-30T03:52:01.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I3sxUMqT8PMyssrJ" /><figcaption>Photo by <a href="https://unsplash.com/@jairlazaro?utm_source=medium&amp;utm_medium=referral">Jair Lázaro</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Product Development: When Does Validation End?</p><p>A recent NY Times Editorial, <a href="https://www.nytimes.com/2019/05/04/opinion/sunday/medical-devices.html"><em>80,000 Deaths. 2 Million Injuries. It’s Time for a Reckoning on Medical Devices</em></a>, presents three proposals aimed at improving medical device quality: <strong>Tighten approval standards</strong>; <strong>Fix post-market surveillance</strong>; and, <strong>Loosen industry’s grip</strong>.</p><p>Yes, “<a href="https://www.nytimes.com/2019/05/10/opinion/letters/safety-medical-devices.html">F.D.A. oversight is the gold standard the world over”,</a> however, as a #seasoned medical devices professional, I believe our profession, both manufacturers and regulators, can step up to this challenge. It’s time we show each other and the world how to use an existing superpower that’s been too infrequently exercised, our decisions of <em>validation</em>.</p><p>Described simply, we know the typical phased medical device product life cycle starts with the definition of a product concept, proceeds with requirements and architecture, development and verification, and concludes with validation. Thereafter, a product is in the maintenance phase and a period of post-market surveillance.</p><p>I advocate our adopting a position of <em>continuous validation</em> — validation from cradle to grave — of our medical device products. Through continuous validation, we can resolve many of the remaining quality problems ailing our industry. Using the editorial’s proposals, I’ll explain how together we can make it can work.</p><p><strong>Tightening Approval Standards</strong></p><p>According to FDA Quality Systems Regulation (QSR) 21 CFR 820, “Validation means confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use can be consistently fulfilled”. A waterfall-based development tradition by manufacturers has inspired our <em>verification then validation</em> culture. Generating a mountain of verification results then coupling with a validation phase at the end of development results in an implied decision to validate by the manufacturer and, subsequently, by the FDA. Once a manufacturer validates a device and achieves FDA regulatory clearance or approval it can be made available for sale.</p><p>Embracing a protocol of continuous validation throughout the life-cycle inherently imposes a greater emphasis, i.e., tightening, of the already existing review-and-approve requirements of the QSR. If our industry adopts a consistent means to validate medical devices, perhaps using the MDIC’s <a href="https://medium.com/the-in-validators-dilemma/time-for-the-fda-to-in-validate-modernize-its-thinking-on-validation-723565937f60">Domains of Quality</a> (DoQ) as an example, I contend it will yield products of greater quality while hindering products of inferior quality from entering the market. Employing the DoQ establishes a set of validation questions to be asked throughout the development of the device; asked of its main features, of its requirements, of its design, of its implementation, of its verification procedures, and, especially, of its defects discovered during development.</p><blockquote>Employing the DoQ: A framework for consistent decision-making/validation:</blockquote><blockquote>Is Safety impacted?</blockquote><blockquote>Is Effectiveness impacted?</blockquote><blockquote>Is Reliability impacted?</blockquote><blockquote>Is Patient Satisfaction impacted?</blockquote><blockquote>Is Usability impacted?</blockquote><blockquote>Is Availability impacted?</blockquote><blockquote>Is Compatibility impacted?</blockquote><blockquote>An answer of Yes to one or more is an indication of increased risk and should trigger the question, “are we doing the right thing?”.</blockquote><p>When done properly, continuous validation becomes a creative process of multiple participants who experience a state of flow and excitement much like an improv event.</p><p>In our medical devices culture, professionals at all levels should always be asking these questions. The questions serve to ask and inform us of all the known impacts and potential impacts of both expected behavior and potential side-effect behavior. By the end of development, if done properly, virtually every facet of a medical device’s behavior will have been uncovered, documented, and validated. Validation not only becomes a data set implying a device has been verified and validated, its documented decisions of validation objectively support the manufacturer’s final decision to validate the device. Validation becomes as the QSR definition intended, a confirmation, a subjective decision supported by continuously gathered objective evidence — data and decisions, that the requirements for a device designed for a specific intended use can be consistently fulfilled.</p><p>Again, it doesn’t take tightening of the approval standards, only a better method of practicing and executing a process of the already existing regulation. When our industry agrees on a consistent validation method, one embracing continuous validation, we as medical device professionals can practice an effective and transparent means to ensure better safety, efficacy, and overall quality; <em>our industry</em> earns the respect of the general public.</p><p><strong>Fix Post-Market Surveillance</strong></p><p>A requirement to perform post-market surveillance is also expressed by the QSR, an expectation of the manufacturer to track complaints. A “Complaint means any written, electronic, or oral communication that alleges deficiencies related to the identity, quality, durability, reliability, safety, effectiveness, or performance of a device after it is released for distribution”. Further, an “Appropriate statistical methodology shall be employed where necessary to detect recurring quality problems.” As such, a manufacturer must have a means for professionals to log and actively monitor product complaints in order to recognize impending quality problems and prevent them from escalating.</p><p>Building off the first recommendation, I propose we recast post-market surveillance as <em>post-market validation</em>, employing the same continuous validation process and criteria to both confirm expected behavior and confirm or deny defective behavior. Continuous validation gives us a qualitative assessment and quantitive measure of potential impact and harm, perhaps a DoQ-risk score. Defects occurring with frequency and/or having high DoQ-risk inherently become the ones that must be addressed; another decision of validation.</p><p>Fixing post-market surveillance by employing continuous post-market validation amounts to extending surveillance already established during development. Further, our industry is anticipating big-data, analytics, artificial intelligence, and the like to fuel Industry/Quality 4.0. In having a means to react to and track complaints employing DoQ-risk assessments enhances post-market validation and enables statistical models to more rapidly detect and recurring quality problems and, ideally, prevent unnecessary downstream effects to a greater population of patients and users. Tracking complaints can be done electronically, but it will require us medical device professionals, exercising appropriate validation judgment and process, to assess the complaints.</p><p><strong>Loosen Industry’s (Manufacturers’) Grip</strong></p><p>Both manufacturers and regulators have empathetic medical device professionals and we are united by similar cause: bringing innovative, life-changing, and timely products to market and making sure they are reasonably safe and efficacious; that is, valid and validated products. We have many good regulations, standards, and guidances already in place to help us effectively do our jobs. As manufacturers, we do our best to interpret and align our policies and procedures to ensure compliance and training to assure quality medical devices. As regulators, we are nonpartisan advocates for both manufacturers and the patients and users whose lives are impacted by medical devices. Working together, the risk of serious injury or death is not something we take lightly.</p><p>Up until now, our industry has predominantly measured quality via compliance (to regulations, standards, and guidelines), which essentially verifies we’re using a good practice appropriately and its artifacts can be measured quantitatively. Inspired by W. Edwards Deming, quality is measured via verification.</p><p>In applying a greater focus on validation, continuous validation, we gain the benefit from focusing on what Joseph Juran referred to as the vital few; the most critical 20% of criteria, e.g., MDIC’s DoQ, driving 80% of product quality. In measuring subjectively against a vital few criteria, quality is measured via validation.</p><p>Paradoxically, doing more validation results in the need to do less verification. Philip Crosby said, “quality is free”; I say “continuous validation provides a rebate” and enables saying “we’re done! It’s valid!” with confidence. With rapidly advancing innovation on many fronts is bringing more solutions and more players into the market, FDA budget and resourcing most likely won’t keep pace. Doing more with less becomes an ever-building dilemma. The way to greater efficiency is better-evaluation by way of better-validation. The primary, least-burdensome objective evidence in regulatory submissions is the product of continuous validation.</p><p>Loosening industry’s (manufacturers’) grip can be achieved through better alignment of validation expectations of medical device professionals on both sides of the manufacturer/regulator relationship. There are already plenty of eyes and minds employed in doing the <em>thing right</em>, verification and compliance. The same eyes and minds can be entrusted and empowered in doing more of the <em>right thing</em>, validation beyond quality.</p><p>Does validation end? Verification is finite. Validation is infinite.</p><p>Continuous validation is <em>your</em> superpower as medical device professional.</p><p><em>Gregory Keyes is a 35-year medical device professional and consultant focused on systems engineering, software engineering, and validation.Write to him: </em><a href="/service/mailto:greg@conceptualintegrityconsulting.com"><em>greg@conceptualintegrityconsulting.com</em></a><em>. Connect with him: </em><a href="https://www.linkedin.com/in/gregorykeyescva/"><em>https://www.linkedin.com/in/gregorykeyescva/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51d0b0a07073" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-in-validators-dilemma/medical-devices-does-validation-end-51d0b0a07073">Medical Devices: Does Validation End?</a> was originally published in <a href="https://medium.com/the-in-validators-dilemma">The (In)Validator’s Dilemma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rethinking V&V: Validation & Verification]]></title>
            <link>https://medium.com/the-in-validators-dilemma/rethinking-v-v-validation-verification-143e6fa13822?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/143e6fa13822</guid>
            <category><![CDATA[culture-change]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[validation]]></category>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Thu, 06 Dec 2018 18:12:38 GMT</pubDate>
            <atom:updated>2018-12-06T18:11:38.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*ScQu8rugjoVIv9b0AyTPVg.png" /><figcaption>Validation &amp; Verification: [Right {Thing] Right}</figcaption></figure><p>Simon Sinek says, <a href="https://www.linkedin.com/feed/update/urn:li:activity:6476121942368800769">“Simple ideas are easier to understand</a>. Ideas that are easier to understand are repeated. Ideas that are repeated change the world.”</p><p>Today, to reiterate a simple theme and principle presented in my <a href="https://medium.com/the-in-validators-dilemma/time-for-the-fda-to-in-validate-modernize-its-thinking-on-validation-723565937f60">last article</a>, Barry Boehm’s view of validation — doing the <em>right thing</em> — and verification — doing the <em>thing right</em>.</p><p>I propose that we place most of our emphasis on the more difficult <em>thing</em>, the <em>right thing</em>, ahead of the easier <em>thing</em>, the <em>thing right</em>.</p><p>Let’s start by calling it <em>Validation &amp; Verification</em>, reorienting our thinking doing a “180” on validation and verification; the new V&amp;V is <em>Va&amp;Ve</em>. (My experience working with Swiss and German medical device engineers has led me to validate acronyms containing Upper and lower case. Does it work?)</p><p>The concept is simple, whenever we’re ensuring we’re doing the <em>thing right</em>, verification, it should always be with doing the <em>right thing</em>, validation, in mind. But, the traditional way of thinking, verification and validation, would often lead to the conclusion that validation is a step that occurs after verification is complete. That may have been acceptable in the pre-digital-transformation era, but now it’s inadequate.</p><p>When solutions become digital and implicitly malleable, it’s much easier to change course, pivot, and go in a new direction. How do we know the direction is right? Validation.</p><p>In <a href="http://theleanstartup.com/book"><em>The Lean Startup</em></a> , Eric Ries exposes <em>validated learning</em>; “Validated learning is not after-the-fact rationalization… It is a rigorous method for demonstrating progress…”. He advocates validating with frequency such as with the conclusion of every sprint.</p><p>I it’s a good time for a quick pause and to ask ourselves, “Are we still doing the <em>right thing</em>?” Is <em>it</em>, the <em>thing</em>, as it’s defined, still valid? The best time to ask is today, not next week, not next month, or not next year.</p><p>To conclude, if you’re doing the <em>right thing</em>, and you’re committed, it makes doing the <em>thing right</em> easier. But, how do we remember this?</p><p>Do the <em>right thing</em>, and the <em>thing right</em> follows: [Right {Thing] Right}.</p><p>Facing an (in)validator’s dilemma? Write to me at <a href="/service/mailto:gregory@in-validator.com">gregory@in-validator.com</a>.</p><p>Until next time, Be Valid! Be an In-Validator!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=143e6fa13822" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-in-validators-dilemma/rethinking-v-v-validation-verification-143e6fa13822">Rethinking V&amp;V: Validation &amp; Verification</a> was originally published in <a href="https://medium.com/the-in-validators-dilemma">The (In)Validator’s Dilemma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Time for The FDA to In-Validate/ Modernize Its Thinking on Validation?]]></title>
            <link>https://medium.com/the-in-validators-dilemma/time-for-the-fda-to-in-validate-modernize-its-thinking-on-validation-723565937f60?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/723565937f60</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[fda]]></category>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 03:01:38 GMT</pubDate>
            <atom:updated>2018-11-30T03:00:47.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QXRjsDA0pmucWBfQoP2sPg.jpeg" /><figcaption>Time’s up for legacy predicate devices?</figcaption></figure><p>On Monday, The FDA announced <a href="https://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm626572.htm">their plan</a> to make significant changes to the 510(k) process, which is the most common pathway to approval for medical devices in the U.S. market. Coincidently, the announcement followed several recent articles in the general press questioning the FDA’s approval history, including an <a href="https://www.apnews.com/86ba45b0a4ad443fad1214622d13e6cb">AP article</a> scrutinizing the approval of devices that later incurred dubious safety records.</p><p>The FDA and its announced changes are further being criticized by the public in light of the published findings.</p><p>Manufacturers are open to FDA process improvements which enable greater safety and efficacy of their devices, but are wary of implications of proposed changes regarding comparison to predicate devices, the means for a new/updated device to indicate <em>substantial equivalence</em> to a previously marketed device.</p><p>According to 21 CFR 820, <a href="https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=820&amp;showFR=1">The Quality System Regulation</a> (QSR), validation means “confirmation by examination and provision of objective evidence that the particular requirements for a specific <em>intended use</em> can be <em>consistently fulfilled</em>”. (Note that consistently fulfilled leaves the door open for an occasional hiccup; valid does not mean perfect.)</p><p>According to FDA guidance <a href="https://www.fda.gov/downloads/MedicalDevices/.../UCM284443.pdf"><em>Evaluating Substantial Equivalence in Premarket Notifications</em></a>, substantial equivalence means that the intended use of the new/updated device is the same as the predicate and that “the principles of <em>safety</em> and <em>effectiveness</em> underlie the substantial equivalence determination in every 510(k) review”.</p><p>While there was an emphasis on modern and modernization (mentioned 32 times in the PR), the FDA has apparently not provided any hints as to their plans to update/modernize definitions of <em>validation</em> or <em>substantial equivalence</em>.</p><p>I suggest there’s modernization opportunity here as well. It is time for the FDA and the medical devices industry to modernize thinking on validation; that is, in-validate thinking on validation. The modern pathway, as suggested, continues with a narrow emphasis on safety and effectiveness (mentioned 15-times in the PR).</p><p>The need for validation is not new, but the industry needs to think differently about it. 21 CFR 820 states manufacturers must validate designs and validate design changes. Further, it states that validation must be done <em>prior</em> to implementation of the design/design change.</p><p>You may be asking, “Wait, isn’t validation done at the end as a confirmation?How can I confirm the change before I make the change?”</p><blockquote>The terms verification and validation, despite being part of the common development vernacular, continue to befuddle some of the best engineers and quality professionals. The simplest way to understand them, according to Barry Boehm, is verification means “doing the thing right” and validation means “doing the right thing”.</blockquote><blockquote>Verification, doing the thing right, is a compliance activity, checking off a box that says, “yeah, it worked right”. Validation, doing the right thing, is a decision activity that says, “yeah, we did the right thing”. According to Peter Drucker “Management is doing things right. Leadership is doing the right things.”</blockquote><p>By implication, managers are responsible for verification, ensuring compliance. Leaders are responsible for validation, making decisions.</p><p>In establishing the <a href="https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/MedicalDeviceQualityandCompliance/ucm378185.htm">Case for Quality</a> (CfQ), FDA has suggested there’s been too much focus on compliance and not enough on quality. Manufacturers are producing products that are “compliant” but still suffer from quality issues.</p><p>Working in collaboration with the FDA on the CfQ, The Medical Device Innovation Consortium (MDIC), has identified the <a href="http://mdic.org/wp-content/uploads/2016/08/Final.MDIC-Product-Quality-Outcomes-Analytics-Report.pdf">domains of quality (DoQ)</a> as follows:</p><p><strong>Safety</strong>: device does not compromise the clinical condition or the safety of patients, or the safety and health of users</p><p><strong>Effectiveness</strong>: device produces the effect intended by the manufacturer relative to the medical condition(s)</p><p><strong>Reliability</strong>: device system or component is able to function under stated conditions for a specified period of time</p><p><strong>Patient Satisfaction</strong>: device is perceived to meet or exceed patient expectations of usability and outcome</p><p><strong>Usability</strong>: device minimizes the risk of user errors by patients or clinicians</p><p><strong>Availability</strong>: device is available to fill first request orders</p><p><strong>Compatibility</strong>: device is compatible with related devices or drugs, the use environment or relevant standards</p><p>I suggest the complete DoQ — adding to safety and effectiveness — provides the basis and a framework of consistent decision-making &amp; validation whereby every validation decision and substantial equivalence assessment employs the following asks:</p><p>Is <strong>Safety</strong> potentially impacted by this change?</p><p>Is <strong>Effectiveness</strong> potentially impacted by this change?</p><p>Is <strong>Reliability</strong> potentially impacted by this change?</p><p>Is <strong>Patient</strong> Satisfaction potentially impacted by this change?</p><p>Is <strong>Usability</strong> potentially impacted by this change?</p><p>Is <strong>Availability</strong> potentially impacted by this change?</p><p>Is <strong>Compatibility</strong> potentially impacted by this change?</p><p>An answer of “Yes” to more than one of these is an indication of increased risk and should trigger the questions, “Are we doing the right thing? Is there a better alternative? Is doing nothing (for now) acceptable?”</p><p>When making multiple changes, the total qualitative impact provides an objective risk assessment whereby the overall decision to validate or invalidate can be made.</p><p>In the years 2009–2012, while at Ortho Clinical Diagnostics (OCD), then a Johnson &amp; Johnson company, our devices were suffering numerous software defects, some resulting in field actions and recalls. While analyzing the root cause, I discovered many of the defects resulted from inadequate software validation, validation that did not occur prior to the design/code changes being made.</p><p>Our compliant software development and V&amp;V processes were being followed and documented as prescribed, but software defects were still occurring. We were an example of case for quality.</p><p>After I instituted a software validation practice similar to the above, using OCD’s internal equivalent of domains of quality, our software quality improved markedly.</p><p>A minimal change to a manufacturer’s process, one that’s already a requirement of the QSR (validation <em>prior</em> to change), can have a significant impact on product quality. One of my colleagues told me, years later, “We hated you when you gave us more work to do, but today I’m telling you it was the right thing to do.”</p><p>I advocate the above simple, fast, cost-effective means to increase quality, quality beyond compliance. The process easily fits within the existing product development process — start, middle, and end. It achieves consistent and continuous validation.</p><p>Until next time, Be valid! Be an in-validator!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=723565937f60" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-in-validators-dilemma/time-for-the-fda-to-in-validate-modernize-its-thinking-on-validation-723565937f60">Time for The FDA to In-Validate/ Modernize Its Thinking on Validation?</a> was originally published in <a href="https://medium.com/the-in-validators-dilemma">The (In)Validator’s Dilemma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marketing is Validation]]></title>
            <link>https://medium.com/the-in-validators-dilemma/marketing-is-validation-287c45e3b286?source=rss----e6c55a1bf75---4</link>
            <guid isPermaLink="false">https://medium.com/p/287c45e3b286</guid>
            <category><![CDATA[think-different]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[seth-godin]]></category>
            <category><![CDATA[validation]]></category>
            <dc:creator><![CDATA[Gregory Keyes]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 15:25:33 GMT</pubDate>
            <atom:updated>2018-11-15T16:58:20.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6aCueM1vQJbsFg3zTn2b4Q.jpeg" /></figure><p>Hey, it’s Gregory, The In-Validator, and <a href="https://medium.com/u/f9ac9806e153">Seth Godin</a>’s got a new book, <a href="https://www.amazon.com/dp/0525540830/?tag=permissionmarket"><em>This Is Marketing</em></a>, and it just shipped! Its theme is creating <em>better things</em> by doing <em>things better.</em></p><p>This is my blurb, not on the book, but on Seth and his influence on me and my new blog on <em>validation</em>. <strong>Better things also need to be valid things.</strong></p><p>Like many people I know, even those with careers in marketing, I’d never heard of Seth Godin.</p><p>It’s hard to imagine not being aware of an author and personality who’s written 18…er, 19 <a href="https://smile.amazon.com/Seth-Godin/e/B000AP9EH0/ref=sr_tc_2_0?qid=1527817246&amp;sr=8-2-ent">books</a> and over 7,400 <a href="https://seths.blog/">blog</a> posts.</p><p>Somehow, Seth carved out a smallest viable audience (SVA) for himself, one that’s grown drip-by-drip to eventually include people like me. Maybe, people like us?</p><p>After following Seth’s daily blog for several weeks, and then his new <a href="https://www.akimbo.me/">Akimbo</a> podcast from inception, I applied for his <a href="https://altmba.com/">altMBA</a> workshop with:</p><blockquote>“I’m committed to starting a revolutionary movement aimed at improving quality — product, software, life — based on a simple, innovative framework for decision-making and validation.”</blockquote><p>altMBA gave me and my cohort a safe place in which to try out our ideas and receive feedback from “generous skeptics”, many of whom have become friends, allies, and kindred spirits.</p><p>This is my first weekly blog article in <em>The In-Validator’s Dilemma</em>, a publication on Medium. The emphasis is on <em>in</em>, as in it’s <em>in</em> to be a <em>validator</em>, while acknowledging it’s also proper to invalidate when necessary. Its theme will be focused on doing the <em>right thing </em>while not neglecting doing the <em>thing right</em>. The <em>right thing right</em> is both <strong>better</strong> and <strong>valid</strong>.</p><p>As a <a href="https://www.linkedin.com/in/gregkeyes62304/">recognized expert</a> in medical device software validation, I’ll be defining the framework of <em>The In-Validator’s Dilemma,</em> showing you how to apply it to what you’re validating, whether it’s your software, your business’s digital transformation, or something even bigger in your life.</p><p>Until next week, Be valid! Be an in-validator!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=287c45e3b286" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-in-validators-dilemma/marketing-is-validation-287c45e3b286">Marketing is Validation</a> was originally published in <a href="https://medium.com/the-in-validators-dilemma">The (In)Validator’s Dilemma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>