PSUR Repository Webinar On API: Q&A On Preparedness For Usage

3y ago
34 Views
2 Downloads
525.97 KB
82 Pages
Last View : 2m ago
Last Download : 3m ago
Upload by : Kairi Hasson
Transcription

PSUR RepositoryWebinar on API: Q&A on Preparedness for Usage21 May 15Chairs: Joris Kampmeijer (MEB) and Evdokia Korakianiti (EMA)An agency of the European Union

Agenda#TopicRespTimeChairs101Welcome and objective of the webinar2Overview of the PSUR RepositoryIR153The Post-audit functionalitiesOS104Overview of the APICEE205Expected impact of the API on your IT infrastructureOS and CEE106Expected impact of the API on your business processesIR107Feedback from the surveyIR and OS108Q&AAll309Proposed strategy to support NCAs in dealing with the impact of using the APIWrap-upChairs101

1. Welcome and objective of the webinar(1/1)Objective of today’s meeting:As part of the EMA’s commitment to assist NCAs inpreparing as much as possible for the usage of theAPI and integrating the usage of the API in yourbusiness processes, this webinar will address bothtechnical and business-process related aspects.

2. Overview of the PSUR Repository#(1/11)TopicRespTime1Welcome and objective of the webinarChairs102Overview of the PSUR RepositoryIR153The Post-audit functionalitiesOS104Overview of the APICEE205Expected impact of the API on your IT infrastructureOS and CEE106Expected impact of the API on your business processesIR107Feedback from the surveyIR and OS108Q&AAll309Proposed strategy to support NCAs in dealing with the impact of using the APIWrap-upChairs10

2. Overview of the PSUR Repository(2/11)Legal context Article 25a of Reg. (EC) 726/2004 further clarifies:The Agency shall, in collaboration with the national competent authorities and the Commission,and after consultation with the Pharmacovigilance Risk Assessment Committee, draw up thefunctional specifications for the repository. PRAC adopted the auditable requirements, which were then endorsed by EMA MB Dec 2013 The Management Board of the Agency shall, on the basis of an independent audit reportthat takes into account the recommendations of the Pharmacovigilance Risk AssessmentCommittee, confirm and announce when the repository has achieved full functionality andmeets the functional specifications drawn up pursuant to the second paragraph. Independent audit PRAC recommendation April 2015 EMA MB announcement June 20154

2. Overview of the PSUR Repository(3/11)What is the repository? Mandated by legislation Central storage place for all PSURs and associated reports, incl.outcome documents Submission point of PSURs for MAHs Access by NCAs, the Commission, the PRAC, the CMDh and theCHMP Query and download functionalities to authorised users5

2. Overview of the PSUR Repository(4/11)Network involvement during planning, development, testing,deployment and audit There has been a close collaboration with the network throughout the planning,development, testing, and deployment phases. Network was involved in the planning of the Audit activities EU Telematics Governance Structure (IT DEC, IT Directors Plenary, EUTMB) PhV Governance structure through PRAG, PMG2, CMDh, CHMP and PRAC For example: Consultation on API specifications Other initiatives throughout 2015 – 2016 to support NCAs in their change management activities tosupport business process change for mandatory use

2. Overview of the PSUR RepositoryPSUR repository benefits7(5/11)

2. Overview of the PSUR Repository(6/11)How does the PSUR repository work? Web-based user interface for NCAs, Industryand EC Master key: PSUSA procedure number for EUsingle assessment, DLP and active substancefor non-EU single assessment procedure Industry: creation of xml delivery file via UI tobe included in submission to EMA NCAs: search and download documents andupload documents8

2. Overview of the PSUR Repository(7/11)PSUR Repository - Phased Deployment and steps tomandatory useJanuary 2015Pilot Go LivePilotGo live The PSUR ‘golive in pilotphase’ inJanuary 2015 Pilot ongoingwith MAH andNCAsMarch 2015 AuditApril 2015 PRACAudit and PRACRecommendation Positive auditoutcome in March2015 PRACRecommendationadopted in April2015 Final fieldwork toconfirm EMA IPAplanned for 1stweek of June 2015May 2015EMA MBEMA MBannouncementBased onindependent auditoutcome andPRACrecommendationMarch 2015 –March 2016Post-audit releasesPlan has been audited and releasesare being developed and planned: Audit findings – delivered 4 Post-Audit functionalities incl. API(automated connection between NCAsystems and the PSUR Repository) –December 2015 release based on auditedproject plan binding for EMA New and improved functionality deliveredbased on prioritised change requests –multiple releases throughout 2015/2016June 2016Mandatory UseMandatoryUse Followingannouncement byEMA MB in June2015 mandatoryuse within 12months No furthersubmission ofPSURs toindividual NCAs

2. Overview of the PSUR RepositoryActivityActorSubmission ofPSUR/supplementaryinformation (MAH)MAHPilot(8/11)Switch-on Submission to NCA (standard requirements) Submission to EMARetrieval of PSUR/supplementaryinformationNCA Local NCA repository PSUR Repository after receipt of notificationCirculation of AR andcomments by NCAsNCA Manual email PSUR Repository uploadCirculation of AR toMAH by EMAEMAAccess toAR/Comments byNCANCAAccess committeeoutcomes NCANCAMandatoryphasePSUR RepositoryPSUR RepositoryPSUR RepositoryEudralink message Manual email PSUR RepositoryPSUR Repository MMD PSUR Repository

2. Overview of the PSUR Repository(9/11)What was the basis for the current release?10 auditable functionalities – 3 themes1.Submission2.Storage and Retrieval3.Assessment Detailed requirements based on these 10 auditable functionalities were elaboratedby the PSUR repository advisory group (PRAG)11Presentation title (to edit, click Insert Header & Footer)

2. Overview of the PSUR Repository(10/11)4 Plan on post-audit functionalities1. Automated tracking and alerting functionalities to assist the assessment procedure2. Automated two-way exchange (‘API’) of documents held in the PSUR Repositorybetween NCA systems and the PSUR Repository to reduce administrative burden for NCAs3. Work-flow support for assessors and assistance of PSUR Repository administration4. Allowing for the storage and retrieval of PSUR related documents (already deliveredin the auditable release) These additional functionalities, beyond those to be audited, are to be provided in futurepost-audit releases of the PSUR Repository.12

2. Overview of the PSUR Repository(11/11)Plan on future releases [content and timing]:MilestoneTiming“Audit Findings 2” release: EMA business admin screen (allowing for upload of late PSURs) Implementation of remaining IAPs resulting from the audit by PwCMay 2015“Additional Functionalities” release: Additional change requests as prioritised by the Project Advisory Group and PMG2, inparticular CR for additional context in Notifications when uploading ARs or commentsMid Jul 2015(contingency:mid Aug 15)“Post-Audit functionalities” release: The post-audit functionalities, especially the ‘API’ Additional change requests that will be identified during the pilot phase and during theinitial months after the “Switch-On”. These will be prioritised by the Project Advisory Groupand PMG2.Nov 2015(contingency:Dec 15)“Mandatory use” release: Additional change requests that will be identified during the pilot phase and during theinitial months after the “Switch-On”. These will be prioritised by the Project Advisory Groupand PMG2.Mar 2016(contingency:Apr 16)13

3. The Post-audit functionalities#(1/6)TopicRespTimeChairs101Welcome and objective of the webinar2Overview of the PSUR RepositoryIR153The Post-audit functionalitiesOS104Overview of the APICEE205Expected impact of the API on your IT infrastructureOS and CEE106Expected impact of the API on your business processesIR107Feedback from the surveyIR and OS108Q&AAll309Proposed strategy to support NCAs in dealing with the impact of using the APIWrap-upChairs10

3. The Post-audit functionalities(2/6)As has been agreed by a.o. the EUTMB, the PRAC and the EMA MB and documented indocument “EMA/681848/2013” (aka the “Auditable Requirements”), section 4:4. Additional functionalities of the PSUR Repository (post-audit)Taking into account the provisions set out in Article 25a of Regulation (EC) 726/2004, thefunctionalities to be audited are those outlined in section 3.As part of the consultation with Member States, the following additional key functionalities wererequested to be included in the common PSUR Repository:1. Automated tracking and alerting functionalities to assist the assessment procedure2. Automated two-way exchange of documents held in the PSUR Repository between NCAsystems and the PSUR Repository to reduce administrative burden for NCAs3. Work-flow support for assessors and assistance of PSUR Repository administration4. Allowing for the storage and retrieval of PSUR related documentsThese additional functionalities, beyond those to be audited, are to be provided in future post-auditreleases of the PSUR Repository for which further business requirements will be developed withMember States in consultation with the PRAC.15Based on the initial implementation experience, an iterative approach will be followed allowing forimprovement of functionalities if necessary.

3. The Post-audit functionalities(3/6)Agreed deliverables to fulfil the post-audit functionalities: 1. & 3.: Additional notification functionality as part of the “Post-audit” release 2.: A computer-interface (aka API) allowing NCA IT systems to perform automated two-wayexchange of documents held in the PSUR Repository between NCA systems and the PSURRepository 4.: Already provided in the current system16

3. The Post-audit functionalitiesJan 15Feb 15Post go-livesupportContingencyMar 15Apr 15May 15IntermediateReleaseAnnouncego-liveJun 15Jul 15Aug 15(4/6)Sep 15“Pilot”(Note: Period TBC)yarmmSuAudit supportSupport auditAnalyse / assessaudit findingsDevelop Switch On releaseDeploy(in prod)DeployTime permitting:Dev. prioritised CRsJan 16Feb 16Mar 16“Additional CRs”ContingencyReleaseDevelop Audit FindingsreleaseFixFixDeploySet up XCompenvironmentDeployTime permitting:Dev. prioritised CRs (Rel.”Audit-Findings”)DeployDeployDeployDeploy DeployDeployilduBFin altestSupport auditTestTech UAT Re- Fin alplanning testingEMA only test testProvision UATtest casesTech UATPerf Re- Fin altestingEMA onlytest test testNCAginstTePlan for the post-auditProject Phase Closurerelease(s)Update the plan for the post-audit release(s)Auditreportto MBAudit by PWCProgramme management / Project management / Change management&MPAPI spec consultationMC17API specpublishedTechtestingUATNCARe- Fin altest testPerftestMay 16Post-project support.Develop Prioritised CRsDevelop Post-Audit functionalities Prioritised CRsApr 16.Twelve months before mandatory usageFixDeployDec ed full usePrioritised CRsReleaseAudit findingsReleaseNov 15Oct 15TechtestingUATNCARe- Fin altest testPerftest

3. The Post-audit functionalities(5/6)Overview milestones: Nov –Mar: Work with the NCA IT reps to draft the technical API specifications Define with the Advisory Group the specifications for the Additional Notification System End Mar: Draft specifications available for API Implementing post-audit functionality 2 End Mar: Final specifications available for Additional Notification System Implementing post-audit functionality 1 & 3 Apr – May: Consultation within EMRN on the API specifications Including the EU Telematics IT Directors group, the EU Telematics EnterpriseArchitecture Board, 23 Apr – 15 May: Surveys on expected usage of the PSUR Repo API 21 May: Webinar to address both technical and business-process related aspects of the usageof the API Jun: Approved API specifications available Jun - : Other initiatives throughout 2015 – 2016 to support NCAs in their changemanagement activities related to the use of the API. The details of these will be driven by a.o.the feedback from the surveys and the 21 May webinar.

3. The Post-audit functionalities(6/6)Overview milestones (cont’d): Jul: Start development API and Additional Notification System at EMA Start preparation modification NCA IT systems and business processes to use the API Jun: Call for EoI for participation in the UAT team Jul: Work with NCA IT and Bus Reps to define the user acceptance plan (UAT) plan, test cases andscripts Oct-Nov: UAT by NCA reps Nov: Start weekly TCs for: Q&A on technical usage of the API and development of the required amendments to the NCAIT systems to consume the API. Forum for NCA IT reps to share experience in developing for the API and using the API Forum for NCA business to address questions on business processes End Nov: API and Additional Notification System available EMA will provide a dedicated test system to test NCA IT systems until Jun 2016 (at least) 2016: Successive next iterations to implement changes as required

4. Overview of the API#(1/10)TopicRespTimeChairs101Welcome and objective of the webinar2Overview of the PSUR RepositoryIR153The Post-audit functionalitiesOS104Overview of the APICEE205Expected impact of the API on your IT infrastructureOS and CEE106Expected impact of the API on your business processesIR107Feedback from the surveyIR and OS108Q&AAll309Proposed strategy to support NCAs in dealing with the impact of using the APIWrap-upChairs10

4. Overview of the API(2/10) The project must deliver a plan for implementing the Businessrequirement (BRQ-0002): Automated two-way exchange(Repository API)21Req-idNameMoSCoWDR 001Search queryMustDR 002Search query: Document typeMustDR 003Search query: Document submission dateMustDR 004Automated upload of a document related to EU single assessmentCouldDR 005Automated upload of document related to Non-EU singleassessmentCould

4. Overview of the API(3/10)Agency Representatives - as delegated by PRAG for theIT API specification workshopsNameAgencyNameAgencyAndrea JohnsonMHRAMikael FredrikssonMPARayden FosterMHRAHenriette RaflerBfArMBridget SmithMHRAClaus ViehmannBfArMGlenda GjokaMHRAJose SimarroAEMPSDavid DowlingHPRASaid IoughlissenANSMJennifer LynchHPRAUlrich KrachPEIJoris KampmeijerCBG-MEBChristophe PéeEMA2228 May 2015

4. Overview of the API(4/10)Approach to creating the API specification (1/2) Approach A:a candidate in the sub-group drafts a proposal for an API specification as a base forreview and discussions. Approach B:the EMA development team drafts a proposal for an API specification as a base forreview and discussions.The API specification sub-group voted for this approach23

4. Overview of the API(5/10)Approach to creating the API specification (2/2) 8 workshops organised weekly between 5/12/2014 and 30/01/2015 EMA: Provided weekly additions and updates to the API specification document; Circulated the document to the stakeholders; Addressed comments made by API sub-group participants. PSUR Repository API sub-group: Reviewed document and sent their comments and questions. EMA: 24On 07/04/2015, circulates draft API document of the specification to IT directors andTEAB.

4. Overview of the API(6/10)Flexibility and constraints The API must meet your needs; NCAs have typically different needs as they have different business processes, ITinfrastructures and budgets; Yet, there will be only 1 API; Important to draw the line between generic features (usable by all) vs. specificfeatures (usable just by 1 or a few); Specific features must be implemented on your side and the API must allow for that.25

4. Overview of the API(7/10)API – A definition (1/2) Some aspects of an API (from Wikipedia) “It is a set of routines, protocols, and tools for building software applications.” “It expresses a software component in terms of its operations, inputs, outputs,and underlying types.” An API is not: A software component that you install on a computer. A process that automates human activities. An end-to-end system where your NCA is 1 end and EMA the other end.26

4. Overview of the API(8/10)API – A definition (2/2)“It expresses a software component in terms of its operations, inputs, outputs, andunderlying types.”ElementDescriptionSoftware componentSystem hosted at EMAOperationsSearch, read and writeInputsSearch terms, documents, metadata attributesOutputsDocuments, metadata attributesUnderlying typesPSUR (eCTD & NeeS), Assessment Reports, AR Comments,Recommendation, substances, products, 27

4. Overview of the API(9/10)Use of controlled terms and other sources of dataAttributeSourceFormatExampleSubstance nameEURD listControlled termabacavir, lamivudine,zidovudineProcedure numberEURD listControlled termPSUSA/00003144/201312Product nameXEVMPD databaseText, as submitted by MAHJanuviaProduct short nameXEVMPD databaseExpressed from text, assubmitted by MAH.JanuviaProduct number (EV Code)XEVMPD databaseAs generated by XEVMPDPRD317097MAH nameXEVMPD databaseText, as submitted by MAHMERCK SHARP & DOHMELTD.CountryEUTCTControlled term100000000337BE28

4. Overview of the API(10/10)API – Users and technicalities Users: Registered users and with appropriate capabilities (ECD user database). Restricted to EudraNet (VPN between EMA and NCAs) Technicalities: Protocol: HTTP (secured) Message representations: JSON (JavaScript Object Notation) Architectural style: RESTful Web Services.29

5. Expected impact of the API on your IT infrastructure#Topic(1/2)RespTimeChairs101Welcome and objective of the webinar2Overview of the PSUR RepositoryIR153The Post-audit functionalitiesOS104Overview of the APICEE205Expected impact of the API on your IT infrastructureOS and CEE106Expected impact of the API on your business processesIR107Feedback from the surveyIR and OS108Q&AAll309Proposed strategy to support NCAs in dealing with the impact of using the APIWrap-upChairs10

5. Expected impact of the API on your IT infrastructure(2/2) You would need to develop functionality to: Communicate with the API from within your IT infrastructure to downloadinformation from the PSUR Repo Potentially automate the processing of the downloaded information so it isautomatically uploaded in your IT systems (e.g. your DMS or casemanagement system) Communicate with the API from within your IT infrastructure to uploadinformation to the PSUR Repo The API specification is available (Draft: now. Final: July) so you couldalready start developing your functionality EMA will make a permanently available test system available fromSeptember 2015 onwards

6. Expected impact of the API on your business processes#(1/4)TopicRespTimeChairs101Welcome and objective of the webinar2Overview of the PSUR RepositoryIR153The Post-audit functionalitiesOS104Overview of the APICEE205Expected impact of the API on your IT infrastructureOS and CEE106Expected impact of the API on your business processesIR107Feedback from the surveyIR and OS108Q&AAll309Proposed strategy to support NCAs in dealing with the impact of using the APIWrap-upChairs10

6. Expected impact of the API on your business processes(2/4)Submission§§ ‘electronic submission to the Agency’ implications: CMDh national submission requirements no longer applicable (no paper copies, CD/DVD, multiplecopies, etc.) different way of receiving, registering, distributing, saving and archiving of thesesubmissions Non-EU PSURs business process also impacted! EMA cover letter for EU single assessment also for NAPs Life cycle management of eCTD and NeeS need to identify relevant sequence in case ofdifferent sequence numbers for same PSUR in different MSs (do we want this for NeeS?) Validator/viewer tool for eCTD sequence Downloading PSURs for product life cycle management (competent NCA role) and/or forassessment (lead MS/Rapp role) avoid confusion/duplication @assessment team33

6. Expected impact of the API on your business processes(3/4)Assessment How to make the PSUR submission for assessment av

Pilot Go live . Audit and PRAC Recommendation Post-audit releases The PSUR ‘go live in pilot phase’ in January 2015 Pilot ongoing with MAH and NCAs 2015. January 2015 March 2015 Audit Pilot Go Live April 2015 PRAC. May 2015 EMA MB . Plan has been audited and releases are being developed and planned: Audit findings – delivered

Related Documents:

solaris repository description Local\ copy\ of\ the\ Oracle\ Solaris\ 11.1\ repository solaris repository legal-uris solaris repository mirrors solaris repository name Oracle\ Solaris\ 11.1\ Package\ Repository solaris repository origins solaris repository

api 20 e rapid 20e api 20 ne api campy api nh api staph api 20 strep api coryne api listeriaapi 20 c aux api 20 a rapid id 32 a api 50 ch api 50 chb/e 50 chl reagents to be ordered. strips ref microorganisms suspension inoculum transfer medium i

Latest API exams,latest API-571 dumps,API-571 pdf,API-571 vce,API-571 dumps,API-571 exam questions,API-571 new questions,API-571 actual tests,API-571 practice tests,API-571 real exam questions Created Date

3 API Industry Guide on API Design Apiary - Apiary jump-started the modern API design movement by making API definitions more than just about API documentation, allowing API designers to define APIs in the machine-readable API definition format API blueprint, then mock, share, and publish

Creating, Restoring, and Configuring the Informatica Repository 78 Starting the Informatica Repository Server 78 Creating or Restoring the Informatica Repository 79 Dropping the Informatica Repository (Optional) 81 Registering the Informatica Repository Server in Repository Server Administration Console 81 Pointing to the Informatica Repository 82

Summer 2018 SEVP InFocus Webinar—Script . 1 . Summer 2018 SEVP InFocus Webinar . Aug. 16, 2018 . Webinar Script . Slide 1: Pre-webinar Title Slide [Adobe Connect room opens approximately 15 minutes prior to webinar. Slide 1

3. Webinar 3 - Evaluation questions and indicators 4. Webinar 4 -Experimental impact evaluation 5. Webinar 5 -Non experimental impact evaluation 6. Webinar 6 - Sample size and power calculations 7. Webinar 7 - Timeline and budget 8. Webinar 8 - Rapid-fire presentations and closing remarks For all webinars except webinar 8, a learning

Jane Phillips Janice Harris John Padginton Michelle Gale Nicolle Marsh Sue Russell Wendy Cupitt Ben Lapworth Ring 10 – . Scrim - Anne Sutherland Amanda Hubbard Claire Hayes Debbie Reynolds Debbie Styles Diana Woodhouse Diane Bradley Francis Bugler Graham Avery Karen James Sue Norman Ring 8 – Jenny Slade VYNE VYNE Ring 10 – Sue Luther Little Meadows LITTLE MEADOWS Ring 12 – Sara Tuck .