FH-Prof. Dr. Jozef Aerts



Similar documents
Smart Dataset-XML Viewer: Web Services

Meaningful use. Meaningful data. Meaningful care. The 3M Healthcare Data Dictionary: Standardizing lab data to LOINC for meaningful use

CDISC Roadmap Outline: Further development and convergence of SDTM, ODM & Co

Udo Siegmann member of e3c, CDISC Sen. Dir. Acc. Management PAREXEL

SDTM-ETL TM. The user-friendly ODM SDTM Mapping software package. Transforming operational clinical data into SDTM datasets is not an easy process.

Implementation Guide

SDTM Validation Rules in XQuery

New features in SDTM-ETL v SDTM-ETL TM. New Features in version 1.2

ELR Clarification Document for EHR Technology Certification

CDER/CBER s Top 7 CDISC Standards Issues

Implementation of SDTM in a pharma company with complete outsourcing strategy. Annamaria Muraro Helsinn Healthcare Lugano, Switzerland

«How we did it» Implementing CDISC LAB, ODM and SDTM in a Clinical Data Capture and Management System:

ONC s Laboratory Results Interface (LRI) and Laboratory Orders Interface (LOI) Implementation Guides and LIS-EHR Data Exchange

Advanced Aspects of Hospital Information Systems

3M Health Information Systems

Understanding CDISC Basics

Electronic Submission of Regulatory Information, and Creating an Electronic Platform for Enhanced Information Management

Development of CDISC Tuberculosis Data Standards

ELR Clarification Document for EHR Technology Certification V1.1

PK IN DRUG DEVELOPMENT. CDISC management of PK data. Matteo Rossini Milan, 9 February 2010

Introduction to the CDISC Standards

SMART C CDA Collaborative Perspective & Debriefing

Generic EHR HL7 Interface Specification Abraxas v. 4

Einführung in die CDISC Standards CDISC Standards around the World. Bron Kisler (CDISC) & Andrea Rauch DVMD Tagung

Cancer Reporting Errata and Clarification Document for Electronic Health Record (EHR) Technology Certification December 2012

ADaM or SDTM? A Comparison of Pooling Strategies for Integrated Analyses in the Age of CDISC

Training/Internship Brochure Advanced Clinical SAS Programming Full Time 6 months Program

Note: See 7.7 Representations and Warranties, Limitations of Liability, and Disclaimer.

Copyright 2012, SAS Institute Inc. All rights reserved. VISUALIZATION OF STANDARD TLFS FOR CLINICAL TRIAL DATA ANALYSIS

Rationale and vision for E2E data standards: the need for a MDR

HIE Ready 2.0 SPECIFICATIONS MATRIX. Product Name: Version Number: Preferred Message and Trigger

Lessons on the Metadata Approach. Dave Iberson- Hurst 9 th April 2014 CDISC Euro Interchange 2014

Role of SNOMED CT in Public Health Surveillance

Standards and their role in Healthcare ICT Strategy. 10th Annual Public Sector IT Conference

SHIB PROJECT Coding Standards CCHI Data Dictionary

Electronic Health Record. Standards, Coding Systems, Frameworks, and Infrastructures

Clinical Data Management Overview

SDTM-ETL 3.1 New Features

Development of an open metadata schema for Prospective Clinical Research (openpcr)

And Now, Presenting...

PharmaSUG2010 Paper CD04 CD04

The Big Picture: IDNT in Electronic Records Glossary

Integration of EHRs with CDISC, CDASH and ODM A European Initiative

THE STIMULUS AND STANDARDS. John D. Halamka MD

SDTM Validation: Methodologies and Tools

Integration Information Model

LIS Interfaces: Basics, Implementation and Pitfalls

Integrating EHR and EDC systems

Meaningful Use Stage 2 as it Relates to the Lab Implementing the Public Health Agency Interface. Interface

ABSTRACT On October 1st, 2008, CDASH released the first 16 common CRF streams (or domains) for use by the Pharmaceutical Industry.

HL7 & HL7 CDA: The Implementation of Thailand s Healthcare Messaging Exchange Standards Nawanan Theera-Ampornpunt, M.D., Ph.D.

STUDY DATA TECHNICAL CONFORMANCE GUIDE

PhUSE Annual Meeting, London 2014

A Semantic Foundation for Achieving HIE Interoperability

MEDICAL NUTRITION THERAPY (MNT) CLINICAL NUTRITION THERAPY Service Time CPT Code

Clinical Laboratory Parameters for Crl:CD(SD) Rats. March, Information Prepared by Mary L.A. Giknis, Ph.D. Charles B. Clifford, D.V.M., Ph.D.

Implementing CDASH Standards Into Data Collection and Database Design. Robert Stemplinger ICON Clinical Research

4. Executive Summary of Part 1 FDA Overview of Current Environment

HealthLink Messaging Technology

The CDISC Laboratory Data Interchange Standard: Using SAS To Read and Write CDISC Compliant Data Sets and Files

Meaningful use. Meaningful data. Meaningful care. The 3M Healthcare Data Dictionary: Enabling effective health information exchange

Data Conversion to SDTM: What Sponsors Can Do to Facilitate the Process

Albumin. Prothrombin time. Total protein

Healthcare Data: Secondary Use through Interoperability

HL7 Clinical Genomics and Structured Documents Work Groups

Pharmaceutical Applications

Case 2:10-md CJB-SS Document Filed 05/03/12 Page 1 of 5 EXHIBIT 12

Meaningful Use Stage 2 Certification: A Guide for EHR Product Managers

SDTM, ADaM and define.xml with OpenCDISC Matt Becker, PharmaNet/i3, Cary, NC

The Future of Clinical Data in Clinical Research

Use of Electronic Health Records in Clinical Research: Core Research Data Element Exchange Detailed Use Case April 23 rd, 2009

ehr Sharable Data Vicky Fung Senior Health Informatician ehr Information Standards Office

Reasoning / Medical Context / Physicians Area of Competence

Business & Decision Life Sciences

ABSTRACT INTRODUCTION PATIENT PROFILES SESUG Paper PH-07

New Jersey Department of Health. Electronic Laboratory Reporting On-Boarding Manual. Version 1.4

STUDY DATA TECHNICAL CONFORMANCE GUIDE

Use of standards: can we really be analysis ready?

Implementation Guide for Study Design Structured. Document. FDA Guidance for Human Clinical Trials

Practical Image Management for

HL7 and Meaningful Use

Interoperability and Integrating the Healthcare Enterprise

Global Health Informatics Standards for Patient Safety

A white paper presented by: Barry Cohen Director, Clinical Data Strategies Octagon Research Solutions, Inc. Wayne, PA

PharmaSUG Paper HS01. CDASH Standards for Medical Device Trials: CRF Analysis. Parag Shiralkar eclinical Solutions, a Division of Eliassen Group

HL7 & KMEHR. A comparison. Medical informatics AJ 2013/2014. Authors: Tessa Borloo Nele Pien

A method for handling multi-institutional HL7 data on Hadoop in the cloud

Test Procedure for (b)(6) Transmission of electronic laboratory tests and values/results to ambulatory providers inpatient setting only

CDISC Data Standards Can Facilitate Composition of Adverse Event Narratives

Metadata Submission Guidelines Appendix to the Study Data Tabulation Model Implementation Guide

Transcription:

FH-Prof. Dr. Jozef Aerts

Use of LOINC in Healthcare Healthcare uses HL7 Standards for exchange HL7: Health Level 7 Worldwide organization With headquartes in the USA Develops semantic and syntactic standards for healthcare Major groups of standards: HL7-v2: bar delimited exchange format HL7-v3: XML based exchange format Jozef Aerts 2

HL7 v2 Messages between systems Mostly between systems in the same hospital E.g. Lab results from Lab to Hospital Information System Sometimes also between hospitals / other organizations E.g. immunization information Jozef Aerts 3

HL7-v2 example Laboratory Result Jozef Aerts 4

Usage of LOINC in healthcare Used in HL7-v2 messages MSH: message header GHH LAB: sender GHH OE: receiver 200202150930: Datetime ORU^R01: message type: Observation Result - unsollicited Jozef Aerts 5

HL7-v2 example Laboratory Result - Details OBR: Observation Request 15545^GLUCOSE: "please execute Glucose test with test code 15545" Jozef Aerts 6

HL7-v2 example Laboratory Result - Details OBX: Observation Result 1554-5^GLUCOSE^POST 12H CFST:MCNC:PT:SER/PLAS:QN Meaning: I have executed test with LOINC Code 1554-4 which is a glucose test, 12 hours calory fasting as a mass concentration as a point in time, in serum or plasma as a quantitative test Jozef Aerts 7

LOINC is not only lab tests Jozef Aerts 8

HL7-v2 example Laboratory Result 1554-5^GLUCOSE^POST 12H CFST :MCNC:PT:SER/PLAS:QN Test is very granular From the LOINC manual: Jozef Aerts 9

HL7-v2 example Laboratory Result LOINC code details: Jozef Aerts 10

DOES CDISC USE LOINC? Well, somehow Source: Study Data Tabulation Model v.1.3 Jozef Aerts 11

OIDs: object identifiers Object identifiers used in healthcare But not only there Tree structure An organization that has an OID is allowed to assign further OIDs to Associated (sub)organizations Documents Persons Jozef Aerts 12

OID tree structure Jozef Aerts 13 ITU = International Telecommunication Union (www.itu.int)

OID tree structure Microsoft = 1.3.6.1.4.1.311 Jozef Aerts 14

OID ISO country codes and ISO-3166-1 1.2.840 = ISO USA 1.2.40 = ISO Österreich 1.2.276 = ISO Deutschland 1.2.756 = ISO Schweiz Jozef Aerts 15

1.2.276 = ISO Germany OIDs Germany But! 2.16.840.1.113883.2.6 = HL7 Germany 2.16.840 = USA 2.16.840.1 = US Organization 2.16.840.1.113883 = HL7 USA Jozef Aerts 16

HL7 Austria OID = 2.16.840.1.113883.2.16 Jozef Aerts 17

Organisations can assign OIDs based on their own OID - ELGA Austria (Elektronische Gesundheitsakte) ehealth-austria: 1.2.40.0.34 ELGA CDA Implementierungsleitfaden: 1.2.40.0.34.7.1.1 ELGA CDA Implementierungsleitfäden Entlassungsbrief (Ärztlich): 1.2.40.0.34.7.2.1 7 = "Documents" Jozef Aerts 18

OIDs and Coding Systems OID = Maschine-readable and unique Each Coding System used in healthcare has an OID ICD-10 = 2.16.840.1.113883.6.3 SNOMED-CT = 2.16.840.1.113883.6.96 LOINC = 2.16.840.1.113883.6.1 Jozef Aerts 19

Use of LOINC in EHRs (HL7-CDA) Jozef Aerts 20

Use of LOINC in EHRs (HL7-CDA) Jozef Aerts 21

LOINC Code 11488-4 in codesystem 2.16.840.1.113883.6.1 Jozef Aerts 22

In the same CDA Jozef Aerts 23

In the same CDA Hey! A UCUM Unit! Jozef Aerts 24

Does CDISC use Object Identifiers? (OIDs) The CDISC Organization does not have an OID So CDISC coding systems (like CT) do not have an OID either So CDISC-CT Code is only valid within CDISC And can e.g. not be stored in an EHR Why? Jozef Aerts 25

Use of LOINC in SDTM and SEND From the SDTM-IG 3.1.3: Dictionary-derived (!!!) Permissible Jozef Aerts 26

Use of LOINC in SDTM and SEND --LOINC should not be used in: EG (ECG Test Results) IE (Inclusion/Exclusion Exceptions) PE (Physical Examination) QS (Questionnaires) SC (Subject Characteristics) DA (Drug Accountability) Jozef Aerts 27

--LOINC is permissible Description says: "Dictionary-derived LOINC Code for LBTEST" Meaning: "from the value of LBTEST", look for a LOINC code in the dictionary" This is however impossible, as there is a 1:n relationship So sponsors do not use LBLOINC However, the LOINC code is in the LIS, HIS or EHR! LIS = Laboratory Information System - HIS = hospital information system Jozef Aerts 28

LBLOINC in SDTM - possible process Investigator requests Lab test Sponsor submits Lab information using CDISC-CT Lab executes test - stores info using LOINC Somewhere here: information loss CRO or Sponsor maps EDC test code to CDISC- CT Investigator enters Lab results in EDC (with or without LOINC) Lab sends test results with or without LOINC (investigator never asked for LOINC) Jozef Aerts 29

CDISC decided to develop its own CT LBTESTCD for Laboratory tests Jozef Aerts 30

CDISC-CT for Lab tests Latest version: 2013-07-08 975 test codes LOINC > 70000 test codes CDISC-CT cannot be mapped well to LOINC We tried Granularity is completely different Jozef Aerts 31

CDISC-CT versus LOINC for Lab tests An example Source: CDISC SDTM-IG 3.1.3 Jozef Aerts 32

CDISC-CT versus LOINC for Lab tests CDISC CT Code (LBTESTCD) CDISC CT Name (LBTEST) ALB Albumin 51 (++) ALP Alkaline Phosphatase 12 (++) WBC Leukocytes 81 (++) LYMLE Lymphocytes 24 (++) NEUT Neutrophils 33 (++) PH ph 3 CHOL Cholesterol 21 (++) PROT Protein 36 (++) Nr. of LOINC Codes ++ : Exclusing similar tests, e.g. excluding "Cholesterol crystals". Jozef Aerts 33

LBTESTCD = GLUC 68 LOINC Codes CDISC-CT versus LOINC Example GLUC (Glucose) Jozef Aerts 34

OK, but we have LBCAT, LBMETHOD LBCAT, LBSCAT, LBMETHOD, LBSPEC do not have controlled terminology! Example glucose test LBTESTCD LBCAT LBSPEC LBMETHOD LBLOINC Sponsor 1 GLUC CHEMISTRY BLD QUANT 2339-0 Sponsor 2 GLUC CHEM WHOLE BLOOD ENZYMATIC 15074-8 Sponsor 3 GLUC CHEMI BLOOD HEXOKINASE 2339-0 Where these the same test? Jozef Aerts 35

Use of LOINC by the FDA Even if there is consistency in LBCAT, LBMETHOD, within a study or even a submission, how can FDA reviewers compare different submissions? If LBLOINC was made "expected" instead of "permissible" they could. Jozef Aerts 36

Arguments heard against using LOINC in FDA submissions Preclinical is not well covered by LOINC => make separate LBTESTCD-CT for SEND Not each combination of 5 variables has a test code => see following slides LOINC does not always make a distinction between Serum and Plasma => Does CDISC? Jozef Aerts 37

Once upon a time CDISC tried 2005 Document by LOINC: "Common LOINC codes used in clinical research" http://loinc.org/discussiondocuments/cdisccommonloinctests20050214.pdf Never updated afterwoods No mapping with CDISC-CT Jozef Aerts 38

Common LOINC codes used in clinical research REMARK: The CDISC-CT Code is not mentioned Jozef Aerts 39

Common LOINC codes used in clinical research Jozef Aerts 40

An alterntive for the LB domain For usage in case the source data comes from a HIS, LIS or EHR Recently proposed to CDISC But with little prospect of being accepted Based on usage of LOINC and UCUM instead of CDISC-CT HIS = Hospital Information System Jozef Aerts 41

The alternative proposal Make LBLOINC expected Remove current LBCAT, LBSCAT, LBSPEC, LBMETHOD Add (LOINC) LBPROP (property measured), LBTIMEAS (time aspect), LBSYSTEM (system), LBSCALE (scale), LBCLASS (class), LBMETHOD (method, when applicable) Jozef Aerts 42

The alternative proposal Sponsor LBLOINC LBCOMP LBPROP LBTIMEAS LBSYSTEM LBSCALE LBCLASS Sponsor 1 2339-0 Glucose MCnc Pt Bld Qn CHEM Sponsor 2 15074-8 Glucose SCnc Pt Bld Qn CHEM Sponsor 3 2339-0 Glucose MCnc Pt Bld Qn CHEM LBLOINC LBCOMP LBPROP LBTIMEAS LBSYSTEM LBSCALE LBCLASS 11217-7 Hexaporphyrin MRat 24H Urine Qn CHEM 30529-9 Hexaporphyrin ACnc Pt Urine Ord CHEM Valid LOINC combination without LOINC code Hexaporphyrin MRat 12H Urine Qn CHEM 50856-4 Hexaporphyrin SRat 24H Urine Qn CHEM Jozef Aerts 43

Use of UCUM in CDISC CDISC has own CT [UNIT] Is a list, not a system Latest version (July 2013) contains 516 "units" The list grows and grows Jozef Aerts 44

CDISC claims to use a subset of UCUM Covered by UCUM but not by CDISC, e.g. "bar", "hpa" Not covered by UCUM, e.g. "TABLET" Covered by both UCUM but with different notation, e.g. mmhg - mm[hg] CDISC- CT UCUM Covered by both CDISC-CT and UCUM, with same notation, e.g. "Pa", "kn/cm2", "psi" Jozef Aerts 45

Some differences Property CDISC UCUM (blood) pressure mmhg mm[hg] pressure cm H2O cm[h2o] count 10^9/l 10*9/l cell count cells/ul {cells}/ul energy Joule J time Years a non-si length ft [ft_i] non-si length IN [in_i] Code CDISC meaning UCUM meaning bar Dosing unit (e.g. bar of chocolate) pressure Jozef Aerts 46

CDISC [UNIT] list is problematic CDISC-CT contains: ug/g/day, ug/g/h ug/g/min ug/g Creatinine But not ug/g Jozef Aerts 47

CDISC-CT [UNIT] mixes up object and unit Object = what is measured E.g "cells", "creatinine" Unit = "ug/g" CDISC-CT: "ug/g Creatinine" UCUM: {cre} ug/g or ug/g Jozef Aerts 48

CDISC-CT [UNIT] dosing "units" Dosing units: ampule, tablet, bar, bottle, capsule, can, cylinder Jozef Aerts 49

CDISC-CT [UNIT] dosing "units" Is a "dosing unit" a "unit"? Suggestion to make this a separate codelist has been turned down Jozef Aerts 50

Why CDISC does not want to accept/support UCUM Investigators are unfamiliar with UCUM notation (e.g. "mm[hg]" versus "mmhg") SEND "units" are not covered by UCUM Some "special" units used in clinical research are not covered by UCUM Investigators, sponsors, reviewers would need to learn UCUM Not invented at CDISC Jozef Aerts 51

LOINC and UCUM for CDISC submissions - proposals Allow different "flavor" of LB domain (e.g. "LBLOINC" for cases where the laboratory information comes from LIS, HIS or EHR) For these cases, allow UCUM units to be used (documented in define.xml - "ExternalCodeList") Jozef Aerts 52

LOINC and UCUM for CDISC submissions - why we need this Investigator requests lab test Lab executes test Test results in LIS Test results in HIS Test results in EDC Test results in ecrf Test results in EHR Jozef Aerts 53

I don't think so The end? The long and winding road to interoperability Jozef Aerts 54