IMPLEMENTATION ISSUES

Slides:



Advertisements
Similar presentations
Drug Information for Consumers and Healthcare Professionals Food and Drug Law Institute Annual Meeting Alan Goldhammer, PhD Associate VP Regulatory Affairs.
Advertisements

1 Future strategy for e-submission as seen by industry Dr Michael Colmorgen, IFAH-Europe 2nd Veterinary Workshop on E-submission 4 Dec 2009, EMEA, London.
Configuration Management
Building Bug-Free O-O Software: An Introduction to Design By Contract A presentation about Design By Contract and the Eiffel software development tool.
United Nations Statistics Division
Business Development Suit Presented by Thomas Mathews.
Process for Submission and Drug Listing Rx Human Drugs* Posting to Daily Med –SPL r3 - occurs via the FDA application process utilizing ELIPS –SPL r4 -
2015 – a forward glance 17 February South Africa has a sophisticated credit bureau system
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 11 July 2013 Meeting #6 hData Record Format Task Force 1 © 2012 The MITRE Corporation.
Use Case modelling 3 How to go from a diagram to a further definition.
UI Standards & Tools Khushroo Shaikh.
Illinois Institute of Technology
E | W | E | W | NHS e-Referral Service Referring Roles Issued: 3 June.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
Configuration Management
1 Electronic Filing System United States Patent and Trademark Office.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
Bringing XBRL tax filing to the UK Jeff Smith, Customer Contact, Online Services,
1 I n t e g r i t y - S e r v i c e - E x c e l l e n c e The Air Emissions Inventory (AEI) Project: An Update on a Universal Schema Darren Carpenter,
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
EFPIA EFPIA IT Proposals ppt Slide 1 EFPIA Proposals for IT Support to the European Regulatory Procedures Mr S. Hasler EFPIA PAT Regulation 2000.
Update on the Enterprise Initiative: e-IRB and More Riyad Naser, MS, MBA Director of Research Information Systems Karen Blackwell, MS, CIP Director, Human.
B2C Extended Packaging Bar Code Standard
1 SPL Technology Presentation The Technology of Structured Product Labeling Presented by Robert H. Wallace 06 June 2004.
Chapter 3 Working with Text and Cascading Style Sheets.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
Presented by: Heather Ward and Jason Cook Date: October 28, 2011 Presented by: > Proprietary and Confidential. For FAA Use Only. The Value of Private Loan.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Justina A. Molzon, MS Pharm, JD
Simplification of lighting and light signalling Regulations (SLR): options and issues Transmitted by the GRE Chair Informal document WP (166th.
Requirements Analysis
Industry Perspective on Challenges for Product Developers - Drugs Christine Allison, M.S., RAC Associate Regulatory Consultant, Global Regulatory Affairs.
1 Supplements and Other Changes to an Approved Application By: Richard J. Stec Jr., Ph.D. February 7, 2007.
Guidelines for the Development and Maintenance of RTF- Approved Measure Savings Estimates December 7, 2010 Regional Technical Forum Presented by: Michael.
An Introduction to Grants.gov Sponsored Programs Office February 22,
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
1 Reportnet for Noise: Feedback from member countries Colin Nugent Eionet National Reference Centres for Noise meeting Copenhagen October 2009.
Cindy Collins ETEC 665 Electronic Submissions Submitting Proposals Through Grants.Gov.
UKSMA 2005 Lessons Learnt from introducing IT Measurement Peter Thomas –
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
C++ Basics C++ is a high-level, general purpose, object-oriented programming language.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
PhRMA Perspective on FDA Final Report FDA Advisory Committee on Pharmaceutical Sciences October 20, 2004 G.P. Migliaccio, Pfizer Inc.
Introduction to the ISBT 128 Labelling Standard for Blood Components.
MATT REID JULY 28, 2014 CCDA Usability and Interoperability.
Compliance Promotion Formalizing an Approach to Support Stakeholder Compliance.
Eyeblaster’s eb.services Making Interactive Easier Than Ever.
FDA Regulatory and Compliance Symposium
Developing Electronic Resources for SACS Reaffirmation of Accreditation SACS Leadership Team Meeting September 1, 2010.
CTD Dossier Preparation K. Srikantha Reddy Sr
Labeling and Electronic Initiatives Rachel E. Behrman M.D., M.P.H. Deputy Director, Office of Medical Policy CDER FDA Science Board, April 15, 2005.
Information Architecture WG: Report of the Spring 2005 Meeting April 14, 2005 Steve Hughes, NASA/JPL.
The Solutions Exchange Bill Piatt August 17, 2004.
GCO INFORMATION SESSION: YOU ASK, WE ANSWER C OMMON R EASONS F UNDING P ROPOSALS (FP S ) ARE R ETURNED FOR C HANGES P RESENTED BY : M ICHELLE H UMPHREYS.
The standard solutions to improving environmental performance Vicki Gomersall, Product Manager.
Swissmedic Swiss Agency for Therapeutic Products Hallerstrasse 7 CH-3000 Bern Workshop 2 - Paragraph 13 TPA 2nd Follow-up Information.
© Copyright IBM 2007DIA ERS SIAC Presentation, January 2008 The HL7 RPS and SPL Standards - A High Level View Terry Hardin Sr. IT Architect Emerging Software.
Hazardous Waste Import-Export Final Rule Requirements and Implementation December 12, 2016.
FSA Conference Updates
Configuration Management
Program Quality Assurance Process Validation
Configuration Management
eCTD Lifecycle Gary M Gensinger
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
Labeling and Electronic Initiatives
Business View on eCTD v4.0 Advantages and challenges when considering implementation to overcome constrains of the current eCTD specification.
SDTM and ADaM Implementation FAQ
Presentation transcript:

IMPLEMENTATION ISSUES Industry Perspective

Content Coding Standards Will there be a depth-of-coding guideline? Or any other mechanism to ensure consistency in the depth of coding across products/companies. How would consistency be achieved if more than the items reflected under Highlights could be coded? Coding Instituting a nomenclature for coding may not be enough. May need additional rules. How will SNOMED and MedDRA play together in/behind US labeling? Should human readable words be SNOMED PTs or MedDRA PTs? Lack of codability/structurability The likelyhood that advice reaches HCPs should not depend on its codability. Where an item cannot be coded, text should be displayed. Crisp sentence may be better than full paragraph. Content of human-readable labeling compared to computer-readable labeling CRL should not contain more (more specific) information than HRL

Content Coding (continued) “Shades of grey” and nuances (must, should, consider, particularly) How can they be retained (SNOMED?) If they cannot be retained, are there compensatory solutions? Lists of examples How can they be handled? Coding compliance What if SPLs were left uncoded or partially coded? Regulatory and legal implications. Voluntary conversion of old labels Is non-conversion an option if “direct-from-label” decision support systems are widely used? Third party information for decision support systems Do they have special requirements?

Content Coding (continued) “Information brokers” How will they benefit from SPL? Text to code: Quality Can we get tools to make this process easier and more transparent? Can we get a “code viewer” that allows us to verify that our coding is consistent with full text?

General SPL Implementation Generic labeling Need realistic roll-out timelines that respect software development timelines. When will coding for highlights be required? How will FDA interact w/ industry – e.g. coding and changes to IG Lifecycle issues need to be addressed so that they can be considered in the development of systems/processes Have ballot coming – how to make decisions on comments….how to manage within RCRIM Generic labeling How will comparison document be affected? Will proposed generic labeling be refused because not coded? Could generic labeling just link to clinical content of branded label? What if generic label changes before branded label?

Process How can parallel changes be handled (e.g. CBE plus several pending PAs)? How will CBEs be handled? Definition of which label content to submit w/ annual report? Will we still have to submit history of changes and current and last approved once ELIPs has all labeling in SPL (after first year) Will industry be able to review FDA approved SPL before it is posted to NLM?(even for so-called “minor” changes?)

Physicians Labeling Rule Implementation issues – printing and paper size FDA reviewer consistency What is the most important information What gets truncated due to space

Implementation: Coding What codes will be required? What code systems will be followed? What markup is optional? What is required? Which sections/excerpts/structured content must I code? If I don’t put in an “optional” code, could that result in a refusal to file? What if “more exact encoding of concepts” begins to offer competitive advantages?

Implementation: Validation What constitutes a “valid” SPL? Valid according to schema? Entire narrative is present? All required elements, but not all optional elements, are present? Some or all codes are present and point to agency-approved code systems? Codes are congruent with narrative? Some/all/none of the above? What will the agency validate (in new and updated submissions), and how?

Implementation: Guides & Info When will the current IG be synchronized with the current (v2a) schema? (Needs to be before October!) Can we create some “helper” info? List of frequently asked questions (FAQs) “Narrative” history to facilitate baselining newcomers to the Working Group Can we centralize SPL information?

Implementation: Submission Given the hierarchical structure of SPL content, how will partial submissions (i.e., only changed components) be managed? How will changes in structured content be managed? What does a flow diagram for all submissions look like? (Start with how is an SPL submitted with an eCTD and then define the flow for every other type of submission!)

Implementation: Submission How will an SPL be delivered to the agency? What information will be packaged with it (i.e., NDA number), and how? How will an SPL be returned to the sponsor (with comments or changes)?