Improvements and clarifications eP cross-border

Slides:



Advertisements
Similar presentations
©2008 TTW Where “Lean” principles are considered common sense and are implemented with a passion! Product Training Commissions.
Advertisements

PHC Meeting the global challenge of unique identification of medicinal products Overview of objectives, outcomes and process Contact:
July 20, 2007 Healthcare Information Technology Standards Panel Principles for Proper Use of HITSP Interoperability Specifications And Proposal for Proper.
Introducing the Medication Recording System Schedule Ed Castagna Mom & Pop’s Small Business Services.
OVERVIEW OF ENGINEERING MANUAL, Part 1 Susan Hoyler TIA, Director Standards Development and Promotion.
TECHNICAL GUIDELINES. HOW TO USE THE TIPEIL WEB-BASED PLATFORM Session 2 – Modify your Portfolio.
Multiplying and Dividing Signed Integers
Communication Technology. What is Technical Communication? Producing technical communication involves creating, designing and transmitting technical information.
Query Health Technical WG Update 1/5/2012. Agenda TopicTime Slot Administrative stuff and reminders2:00 – 2:05 pm Technical Approach Consensus Update.
Revised OSDV Tools and Processes LFA PSM expert workshop 28-30January 2014.
Creating Customized Resident Self-Evaluation Assessments in PharmAcademic TM Andrea Weeks, PharmD PGY1 Residency Co-Director and Preceptor Paoli Hospital.
Use Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
PHC Meeting the challenge of open access to medicinal products across the Union openMedicine approach: A brief demonstration illustrating the.
Stages of Research and Development
Effective Primary Teaching Practice 2016: THE IMPORTANCE OF RECEPTION
Pharmacy Practice, Fourth Edition
The Citizen in the centre in EU, Bratislava November,2005
EUROSAI Task Force on Audit & Ethics
Engineering Fundamentals and Problem Solving, 6e
Agenda – Morning Session
Use Cases Discuss the what and how of use cases: Basics Benefits
16 Basic Math Skills.
Healthcare Information Technology Standards Panel
Dangerous Prescriptions and Abbreviations
Risk Communication in Medicines
Readiness Consultations
Chapter 16 Participating in Groups and Teams.
QUALITY IMPROVEMENT [SECOND]/[THIRD] QUARTERLY COLLABORATIVE WORKSHOP
Information prescriptions: joining up the service pieces
Draft Recommendations & Roadmap
Monitoring and Evaluation Systems for NARS Organisations in Papua New Guinea Day 2. Session 6. Developing indicators.
Writing the research protocol
Lesson 7: How Documentation Can Extend the Learning
How to Communicate Assurance?
Inaugural Expert Council EMA London, 25/6/2015 WP1: epSOS use cases and Conceptual Framework epSOS Problems & EMA Solutions Ida Fortino.
Inaugural Expert Council EMA London, 25/6/2015 WP1: epSOS use cases and Conceptual Framework epSOS Problems & EMA Solutions Ida Fortino.
Multiplying and Dividing Signed Integers
Cross-Border-Cooperation in
CDA Document ‘Executive’ Summary Section
Inaugural Expert Council Meeting at E.M.A. London June 25, 2015
I need a medicine while abroad…
13 September 2018 PHPID and its enabler role for identification of medicines for e-prescription Towards a trans-atlantic solution to univocally identify.
Solve Systems of Linear Equations by Elimination
06 Master Data – Item
4. Solvency II – Own Risk and Solvency Assessment (ORSA)
an alliance among HL7, CEN and OpenEHR ?
Assessment Workshop Title of the Project (date)
Objectives Chapter 4 Define ratio and proportion
Lesson 1: Labels and Prescriptions
Standard Method for Product Description
Review Care Act 2014 This overview forms part of the suite of learning materials that have been developed to support the implementation of part one of.
Session 1, Program Introduction and Overview
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Medication in the Community
Main changes in 2018 revision of ISO/IEC Directives, Part 2
ePhyto DRAFT APPENDIX 1 TO ISPM 12:2011
AICT5 – eProject Project Planning for ICT
Teamwork.
Ch 18: Pharmacy.
Multiplying and Dividing Signed Integers
Multiplying and Dividing Signed Integers
4. Allergy severity The severity of an allergy is not displayed by the CDA Display Tool, and this is considered relevant to the HP. PT MAJOR The severity.
Lecture 1: General Communication Skills
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Gap analysis between Article 57(2) of EC Regulation and the epSOS eP
Health Capital Technical Topics
Planning Consultation
Inaugural Expert Council EMA London, 25/6/2015 WP1: epSOS use cases and Conceptual Framework epSOS Problems & EMA Solutions Ida Fortino.
© empirica – Information provided ‘Commercial in Confidence’
Presentation transcript:

Improvements and clarifications eP cross-border Annika Ohlson, Oskar Thunman 2018-03-19

Summary In the pharmaceutical and technical workgroup we are discussing findings from the implementation in wave 1. We have to decide whether this findings will affect the functional requirements or if it is most suitable to add as information. The easiest thing is to add to existing documents. We have the functional requirements, the Implementation Guide and the communication document that includes both general information and specific information to pharmacists about prerequisties both general and national. In this document we have summarized valuable information from our dicussions that we suggest will be complemented in either the Implementation Guide and/or the communication document as information for pharmacists. We have also separated possible changes in the functional requirements with suggestion that we decide what change proposals we would like to create.

Communication document general information and specific information to pharmacists about prerequisities both general and national ”Split” Implementation Guides In ART-DECOR Together with STF

General considerations Clarify in the functional requirements that all information about the product in the eD must reflect information about the dispensed product and information from the prescription about the product should not automatically go into the eD. Include this even in the Implementation Guide and information to pharmacists. Does this need a change proposal?

ATC code The functional requirements states that the ATC code may not be changed when substituting the product (nor when substitution does not take place). How should we handle that the product has different ATC codes in different countries?

Brand name Suggestion to add “MAH” to help Country B identify the product. The guidelines on ePrescription should consider “MAH” as an optional element for the next release. The functional requirements and implementation guides should be modified accordingly. Clarify in the functional requirements that the brand name may differ slightly between the eP and the eD even when the same product was dispensed due to products being marketed under different names in different countries. Add the information to Implementation Guide and information to pharmacists as well.

Change proposal Add a new field for “MAH” to help Country B identify the product.

Pharmaceutical dose form Pharmaceutical dose form should not be modified, regardless of the value of the substitution code. This is a hard rule, but necessary as a starting point. In the future, a hierarchy of dose forms should be established so simple things like ”film coated tablet  ”tablet” is equivalent and possible to dispense. Note that the work with IDMP is ongoing and that will be the solution in the future.

Strength and active ingredients Can we say something about the order of the strengths in the “epsos desc” element? In the information to pharmacists explain that for medicinal products containing several active ingredients information about strength could be both structured and in free text and that the order could be differing between those. Clarify in the Implementation Guide that all pharmaceutical products must have an ingredient identified although this can be achieved in a few different ways.

Change proposals Does the functional requirements need additional clarifications?

Package type Clarify in the functional requirements that changing the package type is not considered a substitution. Add the information to Implementation Guide and information to pharmacists as well. Does this need a change proposal?

Package size and number of packages Suggestion to add to the functional requirements that the size of the package size in the eD should be expressed using the same unit as in the eP to allow country A to calculate the total amount dispensed. Suggestion to add to the functional requirement that the package size multiplied with the number of packages should amount to the total amount dispensed to the patient. Clarify in the Implementation Guide that packages with packaging multipliers that have an inner package expressed in volume or weight should make use of the “number of packages” element to capture the package multipliers. Describe in the information to pharmacists that if the unit is filled in manually by the pharmacist they have to use this principle. Example: if 2x10x0.35ml is dispensed 20x0.35ml should be the package size/number to be transmitted in the pivot.

Package size and number of packages Suggestion to add to the functional requirements that the number of packages must be an integer and that if fractions of packages are dispensed this should be reflected through the package size. Make the package size in the Implementation Guide an integer. Include this information to pharmacists as well. Clarify in the functional requirements that changing the package size is not considered a substitution. Does this need a change proposal? Suggestion for future improvements: add new field for package size multiplier, maybe this has to be considered together with other changes towards IDMP-harmonization. add new fields for number of refills and total amount. Requires national and cross-border “rules” for partial dispensation to be clearly defined.

Change proposals Add to the functional requirements that the size of the package size in the eD should be expressed using the same unit as in the eP to allow country A to calculate the total amount dispensed. Is a change proposal needed? Clarify in the functional requirements that changing the package size is not considered a substitution. Is a change proposal needed? Add new field for package size multiplier. Add new fields for number of refills and total amount.

Agenda F2F meeting This meeting will be focused on pharmaceutical and semantic aspects. There will also be a technical bootcamp two weeks later that will have to take care of the technical parts. In the sessions before lunch the organisation and work is presented as a platform for the discussions in the afternoon. Especially the information to citizens, health care professionals and pharmacists is important to be aware of as a complement to functional specifications and the Implementation Guide. In the afternoon we have the chance to present what eP wave 1 has done and learned. We suggest that we summarize what has been added (several active ingredients) and the preparatory work in the eP-group including these issues and a brief summary of functional testing to be able to decide on necessary actions and future cooperation.

Thank you