Integrating the Healthcare Enterprise (IHE) Patient Care Device Domain (PCD) FDA UDI Considerations IHE PCD 2013 Fall F2F, Boca Raton, FL Monroe Pattillo.

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise IHE Overview Keith W. Boone Interoperability Architect, GE Healthcare Co-chair, IHE Patient Care Coordination PC.
Advertisements

Integrating the Healthcare Enterprise (IHE) Patient Care Devices Domain (PCD) Alarm Communication Management (ACM) IHE PCD 2011 Fall Face-to-Face Kansas.
Philips PCCI EPIS, Boca Raton, FL, USA IHE Patient Care Devices Domain
HIBC UDI IMPLEMENTATION FOR THE DENTAL INDUSTRY Presented to: Dental Trade Alliance March 5, 2014 Robert A. Hankin, Ph.D. HIBCC President.
Integrating the Healthcare Enterprise (IHE) Patient Care Devices Domain (PCD) Alarm Communication Management (ACM) Requirements for AM – AC Interoperability.
IHE PCD MEM-DMC CMMS & RTLS Vendor Perspective
IHE Integrating the Healthcare Enterprise PATIENT CARE DEVICE Overview of PCD DEC Profile Presented by Monroe Pattillo – PHI, LLC (PCD PC)
Unique Device Identifier (UDI) - Overview 6/21/2014
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
IHE PCD Interoperability Mini-Showcase at AAMI 2013 Long Beach, CA CMMS New Directions Demonstrations Monroe Pattillo Practical Health Interoperability,
HUG HUG Auto-ID Data Work Team - Update Berlin, 1 st Feb 2007 Mark Hoyle, Tyco Healthcare & Mark Walchak, Pfizer.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
3/18/19990© 1999, Health Level Seven, Inc. Introduction: Vocabulary domains Marital Status –single (never married) –married –divorced –separated “Vocabulary”
Unique Device Identification and Global Medical Device Nomenclature Jay Crowley Senior Advisor for Patient Safety Food and Drug Administration
1 Unique Device Identification (UDI) – Enabling the Transformation of Medical Device Safety Terrie Reed, MSIE Associate Director, Informatics
DDI Best Practices Technical Best Practices. High Level Architecture URNs and Entity Resolution Managing Unique Identifiers DDI as Content for Repositories.
Benefits of IHE PCD Standards-Based Interoperability June 1, 2014 | 8:30 AM Jeff McGeath – Iatric Systems, Inc. John Garguilo – NIST Monroe Pattillo –
June-September 2009www.ihe.net IHE 2010 Educational Webinar Series Preparations for the 2010 N.A. Connectathon & HIMSS11 Interoperability Showcase
ONC FACA HIT Standards Committee Clinical Operations Workgroup Hearing on Barriers & Enablers for Medical Device Interoperability March 28, 2011 ~ Washington,
DICOM and ISO/TC215 Hidenori Shinoda Charles Parisot.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
Emanuel Furst, PhD, CCE President, Improvement Technologies, LLC Technical Project Manager, IHE Patient Care Devices Domain IHE Patient Care Device Domain.
IHE PCD MEM-DMC CMMS & RTLS User Perspective Monroe Pattillo Practical Health Interoperability, LLC 6/21/2013.
1 October, 2015 HL 7 Working Group Meeting. FDA UDI Rule – 9/24/2013 Unique device identifier (UDI) means an identifier that adequately identifies a device.
Integrating the Healthcare Enterprise (IHE) Patient Care Devices Domain (PCD) Alarm Communication Management (ACM) Opportunities Manny Furst, Technical.
1 October, 2015 HL 7 Working Group Meeting. FDA UDI Rule – 9/24/2013 Unique device identifier (UDI) means an identifier that adequately identifies a device.
Uniformal barcode processing for patient safety and efficiency Brief Proposal Esther Peelen, GS1 en Erik Zwarter, ErasmusMC 19 October 2015.
SSCC (Serial Shipping Container Code) How to format an SSCC.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
Author : Elliot B. Sloane, Ph.D. American College of Clinical Engineering, President Villanova University Department of Decision.
When Supply Chain meets Care Delivery: Background on GS1 and HL7 Ulrike Kreysa Director Healthcare, GS1 Global Office.
IHE Pharmacy domain Profiles for Community and Hospital Pharmacy Jürgen Brandstätter IHE Pharmacy co-chair.
NOTE: To change the image on this slide, select the picture and delete it. Then click the Pictures icon in the placeholder to insert your own image. National.
ISO Liaison Report Hidenori Shinoda Charles Parisot.
IEEE 11073/HL7 HCD Work Group – January 2016 Meeting Minutes Summary
IP Addressing Introductory material.
IEEE Personal Health Devices work group update
Object Hierarchy Containment Tree
John J. Garguilo April 27, IHE-PCD Spring F2F – San Diego, CA
Cross Enterprise TeleHomeMonitoring Workflow Definition (XTHM-WD)
IHE PCD 2016 Spring F2F Profile PC and TC Updates ACM, MEMDMC, MEMLS
ISO/IEEE Support for UDI
MEM Cybersecurity Working Group Update to PCD Technical Committee
Practical Health Interoperability, LLC IHE Patient Care Devices Domain
IT Infrastructure Plans
HIBC UDI IMPLEMENTATION FOR THE DENTAL INDUSTRY
IHE PCD 2015 Fall F2F Profile PC and TC Updates ACM, MEMDMC, MEMLS
IHE PCD F2F San Diego, America’s Finest City
Point-of-Care Identity Management
CMS Policy & Procedures
IHE PCD 2016 Fall F2F Profile PC and TC Updates ACM, MEM: DMC, LS, RDC
Philips PCCI EPIS, Boca Raton, FL, USA IHE Patient Care Devices Domain
MEM Cybersecurity Working Group Update to PCD Technical Committee
UDI Key Features: Medical Device Integration
HITSP C80 / C83 Briefing and Update
IHE Eye Care Process and Timeline
Healthcare Product Supply Interoperability
WP1: D 1.3 Standards Framework Status June 25, 2015
IHE PCD 2015 Spring F2F Profile Updates ACM, MEMDMC, MEMLS
ACM Across Domains and the Enterprise
How to format a Generic UPC
IHE-PCD 2006 Survey Final Results 171 Responses 68 Vendors
IP Addressing Introductory material.
IP Addressing Introductory material.
Proposal for a Regulation on medical devices and Proposal for a Regulation on in vitro diagnostic medical devices Key Provisions and GIRP Assessment.
HL7 International January Working Group Meeting Health Care Device WG
Spencer Crosswy Paul Schluter The Center for Medical Interoperability
Frank Oemig, Bernd Blobel
Crossing the Chasm Toward RFID and Bar Code Co-existence
CMS’ Approach to E-Health Connectivity
Presentation transcript:

Integrating the Healthcare Enterprise (IHE) Patient Care Device Domain (PCD) FDA UDI Considerations IHE PCD 2013 Fall F2F, Boca Raton, FL Monroe Pattillo Practical Health Interoperability, LLC Fort Lauderdale, FL, USA IHE Patient Care Devices Domain Planning Committee Co-Chair monroe.pattillo@gmail.com © 2013 ACCE, HIMSS, IHE

PCD FDA UDI Considerations FDA released final guideline on UDI Deadlines in guideline (1yr implants, 2yrs others) UDI based upon ISO 15459 Unique Identifiers FDA GUDID requires only DI portion of UDI DI not device instance unique PI portion of UDI to be tracked by hospital Full FDA UDI (DI+PI) contains special characters Guideline expects full UDI used in CMMS & recalls Guideline offers no help mapping UDI to HL7 v2.6 PCD requires EUI-64 & UDI DI + SN in messages Final mapping determination by HL7 Ords & Obs PCD should develop an opinion whitepaper ASAP 2

A PCD means of including UDI DI & SN FDA deadlines – Need means of mapping DI + SN in HL7 v2.6 Communicating full UDI (DI+PI) would require new HL7 data type (FDA UDI) to accommodate special characters in UDI FDA guideline hints that UDI registering agencies likely to be GS1 and HIBCC, possibly others GS1 GTIN – low cost, short lived items (consumables) GS1 GIAI – high cost, long lived items (medical devices) Registered OID exists for GS1 GIAI (2.51.1.5.giai.sn) Using GIAI as DI could allow PCD to use EI data type to map a GS1 GIAI.SN to ISO dot notation HIBCC & others could register an OID to map their values Usable in HL7 v2.6 OBX-18 equipment field (PRT-10 in v2.7) PCD TF EUI-64 in 1st occurrence, GIAI in 2nd occurrence Could be basis for whitepaper to HL7 Ords & Obs 3

HL7 v2.6 Basis for DI+SN mapping HL7 data type is EI – Entity Identifier, containing the following components EI comp 1 – Identifier (HL7 2.A.25) Entity Identifier (ST) GIAI_value.serialno Assigning Authority or Assigning Facility, HD (Hierarchic Designator) data type (HL7 2.A.33) EI comp 2 (HD comp 1) - Namespace ID (IS) empty EI comp 3 (HD comp 2) - Universal ID (ST) GIAI dot notation EI comp 4 (HD comp 3) - Universal ID Type (ID) ISO 4

HL7 v2.6 Mapping Example Following assumes GS1 as assignor. Similar workup needed for other assignors, e.g. HIBCC. If HIBCC would register an OID for value communication that would be appreciated. Example: 0876543ABC12345^^2.51.1.5.0876543.ABC12345^ISO Where “876543” is UPC assigned to manufacturer for product (essentially DI) Zero “0” added to UPC Company Prefix to make GS1 Company Prefix “ABC12345” is manufacturer assigned product instance serial number (not the entire PI) “2.51.1.5” OID established by GS1 for communication of GIAI value See http://oid-info.com/get/2.51.1.5 for details 5

Next Steps Use PCD TC WG to verify that mapping is workable Develop whitepaper Ballot the whitepaper (might make sense) Pass whitepaper up to ITI for their assessment Change as needed for ITI comments Pass whitepaper to HL7 Ords & Obs as the PCD recommended solution Do it all ASAP to avoid solution handed to PCD 6