WP1: D 1.3 Standards Framework Status June 25, 2015

Slides:



Advertisements
Similar presentations
Dipak Kalra, David Lloyd Health Record Information The information in a health record is inherently hierarchical –Clinical observations, reasoning and.
Advertisements

Supporting National e-Health Roadmaps WHO-ITU-WB joint effort WSIS C7 e-Health Facilitation Meeting 13 th May 2010 Hani Eskandar ICT Applications, ITU.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4e Basic Health Data Standards Component 9/Unit.
WG 6 «Pharmacy & Medication» Current activities Porto, Wednesday 11th June 2014.
Mpeg-21 and Medical data A strategy for Tomorrow ’ s EMR.
CIMI Modelling Taskforce Progress Report
HSCIC Data Dictionary for Care Modelling Approach Dr. Rahil Qamar Siddiqui Health and Social Care Information Centre, NHS, England.
NHS Modelling Efforts – ISO13606 adoption and beyond Dr. Rahil Qamar Siddiqui Health and Social Care Information Centre, NHS, England.
New ISO projects Joint meeting HL7, IHE and ISO Pharmacy groups Leonora Grandia, Z-Index.
PHC Meeting the global challenge of unique identification of medicinal products Overview of objectives, outcomes and process Contact:
Standardization and Interoperability in healthcare IT Export HIS Shanghai & Guangzhou seminars Juha Mykkänen Health Information Systems R & D Unit University.
Environment Change Information Request Change Definition has subtype of Business Case based upon ConceptPopulation Gives context for Statistical Program.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
What is ISO in medical informatics about? Christian Hay, Convener TC 215, WG 6 «pharmacy and medicines business» 12 September 2013.
Initial slides for Layered Service Architecture
Public Health Data Element Standardization - A Framework for Modeling Data Elements Used for Public Health Case Reporting Case Reporting Standardization.
The EHR-S FIM project plans to harmonize the EHR-S FM R2
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
Component 11/Unit 8b Data Dictionary Understanding and Development.
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
Environment Change Information Request Change Definition has subtype of Business Case based upon ConceptPopulation Gives context for Statistical Program.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
1 Incorporating Data Mining Applications into Clinical Guidelines Reza Sherafat Dr. Kamran Sartipi Department of Computing and Software McMaster University,
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Ongoing/Planned Activities for Week of 4/29 Final UCR Crosswalk due COB 4/30 Hold two working sessions to complete UCR Crosswalk on 4/30 Hold working session.
Using Detailed Clinical Models to bridge the gap between clinicians and HIT: ISO NIWP 191 open for voting ISO WG1, Edinburgh, 26/27 April 2009 William.
DICOM SR / CDA Rel.2 Mapping San Antonio WGM, May 2006 Helmut König Co-Chair II SIG / DICOM WG20 Siemens Medical Solutions.
Promoting excellence in social security Building on sector wide commonalities to enhance the benefits of Information.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
Ongoing/Planned Activities for Week of 4/29 Final UCR Crosswalk due COB 4/30 Hold two working sessions to complete UCR Crosswalk on 4/30 Hold working session.
Use Case 2 – CDS Guidance Service Transactions CDS Guidance Requestor 2. CDS Response (Clinical Data, Supporting Evidence, Supporting Reference, Actions,
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
IEC TC3 Blank Detail Specification
WP1: D 1. 3 openMedicine infostructure WP2: D 2
eHealth Standards and Profiles in Action for Europe and Beyond
Design Rules for NBD – Network Based Defence
Networking and Health Information Exchange
Code4health – Interoperability Developers
Current Framework and Fundamental Concepts
Information Systems Selection
Component 11 Configuring EHRs
Draft Recommendations & Roadmap
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.
Models & Modelling Heather Leslie Sebastian Guard Heather Grain
CDA Document ‘Executive’ Summary Section
Inaugural Expert Council Meeting at E.M.A. London June 25, 2015
Abstract descriptions of systems whose requirements are being analysed
CEN TC 251: openMedicine in a win-win perspective
13 September 2018 PHPID and its enabler role for identification of medicines for e-prescription Towards a trans-atlantic solution to univocally identify.
Networking and Health Information Exchange
Integrating the Healthcare Enterprise (IHE) IHE-EUROPE
Standard of Electronic Health Record
Electronic Health Information Systems
an alliance among HL7, CEN and OpenEHR ?
Health Information Exchange Interoperability
Frank Oemig, Bernd Blobel
Electronic Health Record Access Control 7
, editor October 8, 2011 DRAFT-D
Introduction Diagnostics Data Service Existing Standards
Session 4 Conclusions & Recommendations
EHR System Function and Information Model (EHR-S FIM) Release 2
US Core Data for Interoperability (USCDI): Data Provenance IG
Inaugural Expert Council EMA London, 25/6/2015 WP1: epSOS use cases and Conceptual Framework epSOS Problems & EMA Solutions Ida Fortino.
Presentation transcript:

WP1: D 1.3 Standards Framework Status June 25, 2015 William Goossen (NEN; wgoossen@results4care.nl) Christian Hay (NEN; christian.hay@gs1.ch )

Task 1.3 (M4 – M9) Identify a common set of descriptive attributes used to specify a medicinal or pharmaceutical in a way that it is identified Assess outcomes of T1.1 on gaps with standards to enable interoperable exchange of medication related information, e.g. periodicity, frequency, strength, route of administration, pharmaceutical form, administration form etc… Propose a standard infostructure related to medicinal and/or pharmaceutical products and based on existing standards enabling identification as well as description of the pharmaceutical products. An ‘infostructure’ is defined by the SemanticHealthNetwork project as “a formal process for the governance of interoperability resources”. It can be defined as the infrastructure to manage “information resources”. This infostructure is a rather theoretical model. D1.3 Initial openMedicine infostructure

D1.3: Standards Framework TOC 1. Executive Summary 2. Introduction 3. Methods 4. Conceptual level overall standards framework 5. Medicinal and Pharmaceutical Products Related Standards 6. Information standards / specifications for medicinal product identification 7. Dictionaries, Terminologies and Codes for Medicinal Products 8. Contexts Standards for Exchange of Medicinal Product Identifiers 9. TODO: Proposed Solution Medicinal Product Identifier in EHRs & epSOS 10. TODO: Discussion and Conclusion 11. Bibliography 12. To be removed here and place in WP 1 glossary 13. Annex 1 Specification of the Medicinal Product as DCM. 14. TO DO: Annex 2 Product identifier specified in HL7 v3 XML

D 1.3. Standards Framework Use Generic Component Model as baseline Domain n Domain 3 Domain 2 Domain 1 Enterprise View Information View Computational View Engineering View Technology View System Component Composition System Domain System Viewpoint Business Concepts Relations Networks Aggregations Details

Identification of Medicinal Products IDMP The Key Source! No Escape for anyone!

ISO TS 19256 Medicinal Product Dictionary Holds and uniqely identifies actual regulated medicinal products within jurisdictions Will be the source of the IDMP based identifiers

ICSR Implementation Guide for Europe Has pre-defined fragments in HL7 v3 message for implementation Re-usable for openMedicine after completion EU Individual Case Safety Report (ICSR)0F Implementation Guide European Medicines Agency. Publication EMA/51938/2013.

Create a full Detailed Clinical Model 4. Meta information: Author Coder Versioning 1. Medical knowledge: concept, target population, evidence, instruction, interpretation 2. Data elements 3. Unique codes, Snomed CT etc 5. Governance

Medicinal Product DCM Under Construction To do: 1. underpinning, 2 check with HL7 Common Product Model, 3. unique code for each ? In model Snomed CT? EMA? 4. express as HL 7 v3 template, 5.OID assignments

Communication Systems, Profiles, Messages HL7 EHR-S FM, IHE Medication Profile, ISO 13606 etc EHR-S FM Compositions Set of entries comprising a clinical care session or document e.g. test result, letter EHR The electronic health record for one person Folders High-level organisation of the EHR e.g. per episode, per clinical speciality Sections Clinical headings reflecting the workflow and consultation/reasoning process Clusters Compound entries, test batteries e.g. blood pressure, full blood count Elements Element entries: leaf nodes with values e.g. reason for encounter, body weight Data values Date types for instance values e.g. coded terms, measurements with units Entries Clinical “statements” about Observations, Evaluations, and Instructions IHE Medication Management, Concepts and Definitions New work item proposal 13606-1

Context: Contsys & Architecture System of concepts for continuity of care ISO 13940 (Oughtybridge, 2014).

Conclusions Appropriate identifiers => ISO IDMP series Enable use of IDMP => Detailed Clinical Model (DCM) DCM Medicinal Product => core for systems, processes, and communications (Completion in WP 2, D2.3) standards framework => various contexts & issues identified and manageable