1 ISBT 128 Industry Standard and Implementation Process Overview.

Slides:



Advertisements
Similar presentations
Barcoding For Beginners
Advertisements

FDA QS reg/CLIA Comparison: Overview
ASYCUDA Overview … a summary of the objectives of ASYCUDA implementation projects and features of the software for the Customs computer system.
U.S. Food and Drug Administration Notice: Archived Document The content in this document is provided on the FDAs website for reference purposes only. It.
DATA PROCESSING SYSTEMS
Going Almost Paperless in 2009 Three Offices Leading the Way.
Hospital Emergency Management
NEW CHALLENGES IN LABORATORY INFORMATION SYSTEMS DR. MILIND M. BHIDE.
Review Questions Business 205
INTRODUCTION OF FACT/JACIE COMPLIANT ISBT 128 BARCODE LABELS FOR
Summer IAVA1 NATIONAL INFORMATION ASSURANCE TRAINING STANDARD FOR SYSTEM ADMINISTRATORS (SA) Minimum.
Spillman Sentryx 6.0.
The Impact of MAK Implementation at a Hospital Transfusion Service Laboratory S.Delanghe, K. Eckert, K.Leigh, H. Elgie, K. Hodgins, L Thomson London Laboratory.
CBER 1 Blood Establishment Computer Software (BECS) Michael Gorman, BA, MT(ASCP)SBB Consumer Safety Officer, CBER, OBRR, DBA September 15, 2009.
CBER Whole Blood and Blood Component Labeling Jennifer Jones Consumer Safety Officer CBER, OBRR, DBA September 16, 2009.
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Building Information Systems Chapter 13 VIDEO CASES Video Case 1: IBM: Business.
Update: M-Pathways Financials v.9.1 Upgrade Financial Unit Liaisons July 20, 2011.
Planning the Implementation of Campus Community. Rules for Campus Community  Keep an open mind  Understand other’s processes  Realize the impact on.
Americas Technical Advisory Group ICCBBA ISBT 128 Blood Product Labeling – A Hospital Perspective Americas Technical Advisory Group ICCBBA.
Chapter 2: IS Building Blocks Objectives
Responsible CarE® Employee health and Safety Code David Sandidge Director, Responsible Care American Chemistry Council June 2010.
ISBT 128 Labelling Standard for Blood Components
SMT Proprietary and Confidential
Integrated Hospital Management System. Integrated Hospital Management System software is user-friendly software. The main objectives of the system is.
Paul Ashford. Safe Blood? Ensuring the provision of safe blood is a high priority Donor selection Testing Processing Quality assurance But...
PhRMA Presentation to FDA: Bar Codes to Reduce Medication Errors
Laboratory Information Management Systems (LIMS) Lindy A. Brigham Div of Plant Pathology and Microbiology Department of Plant Sciences PLS 595D Regulatory.
Introduction to the ISBT 128 Labelling Standard for Blood Components
Instructions and forms
Bar Code Label Requirements for Human Drug Products
Fermilab Computing Division 1 f Oracle Project Accounting System Implementation Overview.
GOODWILL OF NORTHWEST NORTH CAROLINA, INC. EMPLOYEE TRAINING DATABASE PROTOTYPE.
Use of ISBT 128 in the Labeling of Cellular Therapy Products Pat Distler Technical Director, ICCBBA
Warranty Working Group Update. Warranty Working Group's Mission Review both new and existing technologies and business processes to develop a warranty.
1 ISBT-128: It’s Finally Happening! KABB Spring Meeting March 10, 2007 Debra Bowman, MT(ASCP)SBB Quality Assurance Director Kentucky Blood Center.
RAISING THE BAR Meeting CSA Guidelines And Preparing for Health Canada
IT Governance Purpose: Information technology is a catalyst for productivity, creativity and community that enhances learning opportunities in an environment.
GMP on blood/plasma collection establishments Group 2.
Apheresis Blood Components
REGULATIONS FOR BLOOD and BLOOD PRODUCTS JILL HOAG BS, SBB(ASCP) CQA(ASQ) AABB STAFF LEAD ASSESSOR 1.
ISBT 128 Implementation Changes to Blood Component Labels Spring 2009 Val Paulson, Hospital Liaison Specialist Prairie Region.
Leukocyte-Reduced Blood Components Lore Fields MT(ASCP)SBB Consumer Safety Officer, DBA, OBRR, CBER September 16, 2009.
CBER 1 Review Considerations on Additional Centers under an Approved License Rosia E. Nesbitt, BS, SBB(ASCP), CQA(ASQ) Consumer Safety Officer CBER, OBRR,
Developing Policy and Procedure Management System إعداد برنامج سياسات وإجراءات العمل 8 Safar February 2007 HERA GENERAL HOSPITAL.
Implementing an Institutional Repository: Part III 16 th North Carolina Serials Conference March 29, 2007 Resource Issues.
Introduction to the ISBT 128 Labelling Standard for Blood Components.
Mercury. One single online platform: Mercury Highlights – USP’s Web-based platform: accessible from any computer in any location without installing any.
IGCSE ICT Stock Control.
Learning Objectives Understand the concepts of Information systems.
Project management Topic 8 Configuration Management.
Patricia Alafaireet  Lecture 2 – Implementation and go-live strategies Data conversion Communication Planning Downtime.
ICD-10 Operational and Revenue Cycle Impacts Wendy Haas, MBA, RN Dell Services Healthcare Consulting.
? Training removes doubt, instills confidence, and lays the foundation for everyone’s skill and experience level.
Scientific data storage: How are computers involved in the following?
Hospital Accreditation Documentation Process & Standard Requirements
Managing multiple projects or services? Have a mix of Microsoft Project and more simple tasks? Need better visibility and control?
Foreign Barcode.
Presented by: University of Rochester Medical Center
The Components of Information Systems
ISBT 128 Blood Product Labeling Americas Technical Advisory Group ICCBBA © Copyright ICCBBA, Inc.
Display Item Information
The Components of Information Systems
Complying With CLIA Competency Requirements
CLINICAL INFORMATION SYSTEM
Unit# 6: ICT Applications
Implementing an Institutional Repository: Part III
Operations and Safety Committee
LabCraft A complete IT system for Blood banks and transfusion service.
Information System Building Blocks
CHemical Inventory Management and
Presentation transcript:

1 ISBT 128 Industry Standard and Implementation Process Overview

2 Speaker Susan Schene, MBA, MT(ASCP) Validation and Implementation Liaison (405)

3 Purpose To understand the issues facing hospitals as they prepare for the conversion to ISBT 128-labeled blood products.

4 Outline What is ISBT? Why change to ISBT 128? Highlights of ISBT changes More detail about the changes Other changes taking place Assess organizational impact How should hospitals plan for conversion? Additional references

5 What is ISBT? I nternational S ociety of B lood T ransfusion Utilizing code 128

6 Why change to ISBT 128?  AABB requirement by May 2008  All major blood centers will convert

7 Why change to ISBT 128?  Limitations of Codabar  Codabar is susceptible to scan errors  Product code structure is not updated to reflect proliferation of new blood products  No provision to maintain the system

8 Highlights of ISBT 128 Changes  Appearance of the label  Layout will be different than current label  Globally consistent appearance  Different bar code technology  From ABC Codabar to ISBT 128 symbology  Globally consistent bar code symbology  Structure of blood unit number (BUI)  13 digits instead of 7  Globally unique number

9 Highlights of ISBT Changes  Product code  From 5 digits to 8 digits  From 100 product codes to  Globally consistent product codes  Expiration date  May show the time of expiration  Globally consistent expiration dating

10 More Detail About the Changes Full Face Label

11 Blood Unit Identification Number W Y Country Code Four digit center code Year Serial Number (formerly BUI number) Flag character Check character

12 More Detail About the Changes  Product codes  Globally recognized  ISBT 128 product codes  8-digit product code represents Product class (RBC, plasma) Modifiers (washed, frozen) Additional information (irradiated) Donation type Divided unit status (first division, second division)

13

14

15 More Detail About the Changes Comparison of Codabar to ISBT 128 Product Codes

16

17

18

19

20 Flag Characters Used in process control Should not be recorded as part of the BUI number in facility records The flag characters are non-data characters.They are used to convey specific information other than the unique identification of the blood product. W Y 00

21 Flag Characters Used to identify bags (Container 1, 2, 3, etc.), tubes (EDTA, clot, NAT, etc.), donor record label May be icons W Y

22 Check Character Not a part of the BUI Not in the bar code because it’s meant to check KEYBOARD entry May want to record in manually written records Will create an error message if there are any errors in data entry 00 Y W

23 Check character Look up table on the ICCBBA web page ( Quick K calculator

24 More Detail About the Changes Expiration Labels

25 Other Changes Taking Place  21 CFR (c)(13) states the following information on labels must be machine readable as well as eye-readable after 4/26/2006  Includes aliquoting, pooling, or relabeling Unique facility ID BUI number Product Code ABO/Rh  Does not include expiration dates  Does not differentiate between Codabar and ISBT 128

26 Other Changes Taking Place  AABB regulations  Have written plan for conversion by November 2006  Implement ISBT 128 by May 2008

27 Other Changes Taking Place  ICCBBA  Who are they? Formerly known as International Council on Commonality in Blood Banking Automation. Today, they are known by their acronym.  What do they do? Responsible for worldwide administration Maintain databases of product codes, locations Assign site registration numbers Host technical advisory groups

28 Assess Organizational Impact  Software impact  Computer systems Blood bank system, lab system, billing system Ensure computer can read, translate, store, and process ISBT 128 data 13 character BUI 8 character product code Expiration time and date Computer must read both Codabar and ISBT 128

29 Assess Organizational Impact  Software impact  Computer interfaces and interfaced systems Ensure interfaces and interfaced systems can manage data Billing systems Lab equipment Viral marker testing transfers Reports (workload, operational, statistics)  Even hospitals without computer systems will be impacted

30 Assess Organizational Impact  Procedure and forms impact:  Review procedures Will ISBT 128 changes require modifications?  Review forms Accommodate 13 character BUI? Accommodate 8 character product code?

31 Assess Organizational Impact  Staff training impact:  Blood bank staff  Transfusion staff  Floor staff  OR staff  Accounting/billing  Anyone who touches blood products  Anyone who scans blood product bar codes

32 Assess Organizational Impact  Equipment impact  Ensure equipment can read ISBT 128 bar codes Scanners Printers On-demand label printers Lab equipment i.e. Hematology, microbiology, chemistry  Validation impact  Consider any changes to hardware, software, and equipment  Processes may need validation Aliquots, pools, modifications SOP’s

33 Assess Organizational Impact  Financial impact  Software development cost  Upgrade/replace on-demand label printers  Upgrade/replace bar code scanners  Product impact  Both Codabar and ISBT 128-labeled products will be shipped to hospitals  Codabar products with extended dates in inventory Frozen products

34 How should hospitals plan for conversion?  Establish a committee of stakeholders  Determine anticipated conversion date  Develop a plan  AABB members must have written plan by November 2006  AABB and ICCBBA have example plans  A web search will identify example plans

35 How should hospitals plan for conversion?  Develop a budget  Create a project management plan listing specific tasks, responsible people, and timeframes for completion  Work back from an anticipated conversion date

36 How should hospitals plan for conversion?  Develop a communication plan  Notify management Medical director/pathologist Hospital administrator IT manager  Notify other hospital departments Impacted departments Nursing, dialysis, anesthesiologists Anyone who touches a blood bag Impacted laboratories Microbiology, chemistry, hematology Anybody who scans an ISBT 128 bar code

37 Additional References  AABB  Sample ISBT 128 implementation plan  FDA 