My learned colleagues have all provided valuable insights but if I may add my two-bits here…
RA functions span the entire lifecycle of the device, which may be divided as: Pre-Market / Registration / Post-market. In addition, some RA functions sit outside the device development model and include tasks such as flagging new or revised regulations/ guidance/ standards of relevance (‘Regulatory Watchlist’), or participating in regulatory body inspections/ audits, assisting with risk management, outsourcing, or change controls, or auditing quality sub-systems for compliance, or sitting in on management reviews or safety review boards, due diligence reviews, etc.
In the Pre-Market phase RA plays a useful role in the evolving product development roadmap, by identifying both obstacles and facilitators to smooth the regulatory pathway to market. This aspect requires an in-depth knowledge of the global regulations, guidance, best practices, and compliance strategies for the particular industry segment that the product falls into. It is useful to know, for instance, how competitor products fared - both successes and failures - to provide management with viable alternative approaches in product positioning.
The Registration phase extends from compilation of submission documentation to receiving final clearance/ approval (with all in-between stages, like pre-sub meetings for example), and includes aspects such as Establishment Registration & Device Listing.
In the Post-Market phase RA is intimately involved with adverse event reporting, field safety corrective actions (Corrections & Removals), and advisory notices, and is an integral part of the team for device enhancements, promotional materials, liability or lawsuits, etc.
Depending on the organization, some of the outlier RA functions may include advising on compliance aspects of such diverse areas as EU RoHS or REACH, or cybersecurity, or interoperability, or even the ‘least burdensome’ approach to resolution of a specific issue!
To achieve all of the above, the RA professional needs to balance compliance with pragmatism, but above all have the courage to drive hard decisions, and continuous learning and networking (as in participation in this forum!) are essential to success.
------------------------------
Homi Dalal RAC
Regulatory Affairs Leader
Dynamic Controls
Christchurch
New Zealand
------------------------------
Original Message:
Sent: 11-Jan-2017 10:19
From: Nicole Landreville
Subject: Regulatory affairs for aspirants
Very good comprehensive response Clarisa! I agree with your perspective - makes sense to me! At the end of the day, each organization big or small organize their functions to protect the patients, protect the business and to partner in making the company successful!
Nicole
------------------------------
Nicole Landreville FRAPS, Eng., RAC
Regulatory Affairs Program Manager
GE Healthcare
Burlington ON
Canada
Original Message:
Sent: 10-Jan-2017 17:24
From: Clarisa Tate
Subject: Regulatory affairs for aspirants
I've worked from cradle to commercialization (not to grave yet :)) of a lot of product having worked in start-ups and small companies. I've also had an opportunity, being an engineer, to have started from manufacturing before having moved horizontally in my career from there with regards to medical devices - going to quality then to regulatory (numerous titles and positions in between under the same umbrella!).
I can tell you I agree with Ginger, Julie, and Andrea in these posts. Having worked as dual most of the time (RA & QA), I had to teach a lot of colleagues in the industry as to what I am doing is either QA or RA function. RA just as QA should be there from the beginning of product development. A seasoned start-up founder or seasoned start up R&D Engineer, knows this and one of the very first persons they hire or talk to. A regulatory professional helps map out the product from cradle to commercialization. I learned this talking to a few CEOs and a few first engineers in start-ups. They understand the business and the need for experienced voice in creating a strategy for the product. Trust me when I say, even after approvals/clearances, these folks still need RA and expect RA to help them keep up with the global requirements that the company has to meet in order to continue selling the product.
I've always believed in making things as "easy" as possible. In regards of Julie's apt description that just because an RA is doing some QA task doesn't mean that all of a sudden that task becomes an RA function. That's even more apparent in start-ups or small companies that have to make do with the minimal resources they have. Here's a list, NOT INCLUSIVE, of tasks or responsibilities attributed to RA and QA:
Quality Assurance:
- Quality Assurance or Quality Engineering (root cause investigations, contributor in risk assessments, etc.)
- Document Control (if FDA or a regulatory body ever wants to look at that type of document, Document Control should have it)
- Product quality
- 'manufacturing process quality' support (as a former manufacturing engineer, I've needed quality's voice/support in figuring out how to tackle some issues)
- Determination of the need to bring in RA into the discussion regarding product/process issues
- Management Reviews
- Supplier auditing
- Internal auditing
- Quality System management (relevant procedures should be created using ALL departments project managed by Quality)
- Relevant Quality System procedures/processes Training
- Review of product and quality related standards and/or guidances
- Complaint management
- CAPA management
- and more...
Regulatory Affairs:
- Regulatory body submissions (510(k), technical file, PMA, CE Marking, etc.) - pre-market
- Annual Reports to regulatory bodies - postmarket
- Internal auditing support (with global initiatives now being implemented, QA can't deal with this on their own, RA needs to pay attention and support QA) - pre & postmarket
- Review of advertisement and promotion pieces - postmarket
- Review of ALL applicable revised or new standards and/or guidances from regulatory bodies - pre & postmarket
- Determination of complaint reportability to regulatory bodies - postmarket
- Creation of regulatory-based Quality System procedures - premarket
- Clinical trial submissions (pre & postmarket)
- Risk Assessment contributor (pre & postmarket)
- and more...
Regulatory body auditing/inspection --> RA & QA shared responsibility
Some folks may disagree with me on this last one but I think this particular responsibility has changed from QA to now include RA in a lot of cases because of MDSAP and other global initiatives like clinical evaluation report needs. QA can't handle this alone considering the QA scope is limited primarily with regulatory compliance. RA has to really understand some of the work QA does on top of everything else (this is why a lot of companies now see the need for executive level RA&QA person or Compliance person. This person becomes the face, the management representative, who understands everything the whole organization does sometimes understand even accounting practices (Open Payments anyone?). Some of them, thankfully, finally realizes this is not a token position.
I hope that helps,
------------------------------
Clarisa Tate
Medical Device, RA & QA
Bay Area, CA
USA
Original Message:
Sent: 08-Jan-2017 21:00
From: Kadali Renu
Subject: Regulatory affairs for aspirants
I know it could be a very silly question but I really want to clear my head with this doubt.
What is a role of regulatory affair body in an organisation? How is there work or responsibility differ from QA authorities?
------------------------------
Kadali
Scientist,
Sanvita Biotechnologies Pvt. Ltd.
Hyderabad
India
------------------------------