Laboratory Barcode Labeling (LBL) Integration Profile

Transcription

1 GMSIH, SFIL, IHE-J and JAHIS Integrating the Healthcare Enterprise IHE Laboratory Technical Framework Supplement Laboratory Barcode Labeling (LBL) Integration Profile March 26, 2007 Draft for Public Comment Comments due for April 26, 2007 Draft for Public Comment - March 26, 2007 Copyright 2006: GMSIH, SFIL, IHE-J, JAHIS

2 Foreword Integrating the Healthcare Enterprise (IHE) is an initiative designed to stimulate the integration of the information systems that support modern healthcare institutions. Its fundamental objective is to ensure that in the care of patients all required information for medical decisions is both correct and available to healthcare professionals. The IHE initiative is both a process and a forum for encouraging integration efforts. It defines a technical framework for the implementation of established messaging standards to achieve specific clinical goals. It includes a rigorous testing process for the implementation of this framework. And it organizes educational sessions and exhibits at major meetings of medical professionals to demonstrate the benefits of this framework and encourage its adoption by industry and users. The approach employed in the IHE initiative is not to define new integration standards, but rather to support the use of existing standards, HL7, DICOM, IETF, and others, as appropriate in their respective domains in an integrated manner, defining configuration choices when necessary. IHE maintain formal relationships with several standards bodies including HL7, DICOM and refers recommendations to them when clarifications or extensions to existing standards are necessary. This initiative has numerous sponsors and supporting organizations in different medical specialty domains and geographical regions. In North America the primary sponsors are the American College of Cardiology (ACC), the Healthcare Information and Management Systems Society (HIMSS) and the Radiological Society of North America (RSNA). IHE Canada has also been formed. IHE Europe (IHE-EUR) is supported by a large coalition of organizations including the European Association of Radiology (EAR) and European Congress of Radiologists (ECR), the Coordination Committee of the Radiological and Electromedical Industries (COCIR), Deutsche Röntgengesellschaft (DRG), the EuroPACS Association, Groupement pour la Modernisation du Système d'information Hospitalier (GMSIH), Société Francaise de Radiologie (SFR), Società Italiana di Radiologia Medica (SIRM), the European Institute for health Records (EuroRec), and the European Society of Cardiology (ESC). In Japan IHE-J is sponsored by the Ministry of Economy, Trade, and Industry (METI); the Ministry of Health, Labor, and Welfare; and MEDIS- DC; cooperating organizations include the Japan Industries Association of Radiological Systems (JIRA), the Japan Association of Healthcare Information Systems Industry (JAHIS), Japan Radiological Society (JRS), Japan Society of Radiological Technology (JSRT), and the Japan Association of Medical Informatics (JAMI). Other organizations representing healthcare professionals are invited to join in the expansion of the IHE process across disciplinary and geographic boundaries. The IHE Technical Frameworks for the various domains (IT Infrastructure, Cardiology, Laboratory, Radiology, etc.) defines specific implementations of established standards to achieve integration goals that promote appropriate sharing of medical information to support optimal patient care. It is expanded annually, after a period of public review, and maintained regularly through the identification and correction of errata. The current version for these Technical Frameworks may be found at and Page 1 of 28 Draft for Public Comment - March 26, 2007 Copyright 2006: GMSIH, SFIL, IHE-J, JAHIS

3 60 IHE Laboratory TF Supplement Laboratory Barcode Labeling for public comment The IHE Technical Framework identifies a subset of the functional components of the healthcare enterprise, called IHE Actors, and specifies their interactions in terms of a set of coordinated, standards-based transactions. It describes this body of transactions in progressively greater depth. The volume I provides a high-level view of IHE functionality, showing the transactions organized into functional units called Integration Profiles that highlight their capacity to address specific clinical needs. The subsequent volumes provide detailed technical descriptions of each IHE transaction. This supplement to theihe Laboratory Technical Framework is submitted for Public Comment between March 26, 2007 and April 26, 2007, per the schedule announced in December Comments shall be submitted before April to: under the IHE forum Select the Laboratory Supplements for Public Review sub-forum. The IHE Laboratory Technical Committee will address these comments and publish the Trial Implementation version in end June Page 2 of 28

4 Introduction 80 This supplement introduces the new Integration Profile, Laboratory Barcode Labeling (LBL) to the Laboratory Technical Framework. This profile involves two new Actors and two new Transactions. This new Integration Profile will be added to Volume I of the IHE Laboratory Technical Framework. The two new Transactions will be added to Volume II. Profile Abstract 90 The Laboratory Barcode Labeling Integration Profile supports this workflow: A robotic system delivers specimen containers pre-identified with a bar coded label, for the specimen collection related to a laboratory test order. This robotic system receives patient, test order and specimen data from another system (HIS, CIS, LIS), and issues a label for each (specimen, container) needed, with the specimen identifier bar coded on the label, and possibly other information printed on this label. This workflow is supported by two new actors, Label Information Provider and Label Broker. The Label Broker receives label information, and delivers these labels in appropriate operations, and may notify the status of this process. The Label Information Provider is usually grouped with the Order Filler or the Order Placer from the Laboratory Scheduled WorkFlow Integration Profile. The Label Broker may be notified passively with the labeling instructions as well as by querying the Label Information Provider. Scope This profile addresses only specimen container labeling within the scope of the Laboratory Domain. It does not address labeling workflows in other domains. Page 3 of 28

5 Volume I Integration Profiles 100 X Laboratory Barcode Labeling Profile X.1 Scope of LBL Integration Profile The robotic system which automatically issues specimen labels and sticks them on the sampling containers is used in the specimen collection room in the medical institution. It is connected with either one of these systems: Hospital Information system (HIS), Clinical Information System (CIS), Laboratory Information system (LIS). The robotic systems receives patient demographics and specimen information related to a laboratory test orders for this patient, including the specimen identifiers. It prints out the labels with the specimen ID bar coded on each, selects the appropriate containers and sticks each label on a container. This Integration Profile provides the message exchange that support this workflow. This profile does not address the labeling process outside of the laboratory domain. Two new actors are introduced in this profile. The first actor is the Label Broker (LB). It issues the specimen label and sticks it on the collection container. The second actor is the Label Information Provider (LIP). It transmits the label information and instructions to the Label Broker. The Label Information Provider Actor is grouped either with the Order Placer actor or with the Order Filler actor from the Laboratory Scheduled Workflow (LSWF) Integration Profile. Two alternative transactions are defined in this profile. The first transaction, Label delivery request, enables the Label Information Provider to notify the Label Broker with the label delivery instructions related to laboratory test orders, when these test orders are placed and registered. The second transaction, Query for label delivery instruction enables the Label Broker to get these label delivery instructions by querying the Label Information Provider, when the patient arrives in the specimen collection room. Page 4 of 28

6 X.2 Use cases 5 use cases are addressed by this profile, depending upon which system implements the business rules to compute the needed specimen and containers for a particular test order. X.2.1 Use case The Label Information Provider is grouped with the Order Placer, generates the label information, and sends it to the Label Broker a) The Order Placer generates a test order and calculates the needed containers and associated barcode labels for this order. b) The Order Placer places the order to the Order Filler, and the Order Filler accepts it. c) In due time, the Label Information Provider sends the labeling instructions to the Label Broker. d) The Label Broker issues the containers with barcode labels. e) The labeled containers are then used for specimen collection and then sent to the laboratory for testing X.2.2 Use case 2 The Label Information Provider is grouped with the Order Filler, generates label information, and sends it to the Label Broker a) A test order is generated either on the Order Placer side or on the Order Filler side.. b) In both cases, the Order Filler gets this order, and in due time, schedules it and calculates the needed containers and associated barcode labels for this order. Then the Order Filler sends the labeling instructions to the Label Broker. c) The Label Broker issues the containers with barcode labels. d) The labeled containers are then used for specimen collection and and then sent to the laboratory for testing. X.2.3 Use case 3 The Order Filler generates label information. The Label Information Provider is grouped with the Order Placer to send label information to the Label Broker. a) A test order is generated either on the Order Placer side or on the Order Filler side. b) The Order Filler accepts this order and generates the specimen information, and sends the confirmation back to the Order Placer. This confirmation carries the specimen information. Draft for Public Comment - March 26, 2007 Page 5 of 28 Copyright 2006: GMSIH, SFIL, IHE-J, JAHIS

7 160 IHE Laboratory TF Supplement Laboratory Barcode Labeling for public comment c) In due time, the Label Information Provider grouped with the Order Placer sends the labeling instructions to the Label Broker. d) The Label Broker issues the containers with barcode labels. e) The labeled containers are then used for specimen collection and then sent to the laboratory for testing. X.2.4 Use case The Label Broker requests label information from the Label Information Provider grouped with the Order Placer. a) A test order is generated either on the Order Placer side or on the Order Filler side. b) The patient arrives at the specimen collection point. The patient id is entered (scanned) into the Label Broker. This triggers a query from the Label Broker to the Label Information Provider to get labeling instructions for the specimens to be collected from this patient. c) The Label Information Provider grouped with the Order Placer responds with the labeling instructions. d) The Label Broker issues the containers with barcode labels. e) The labeled containers are then used for specimen collection and then sent to the laboratory for testing. X.2.5 Use case The Label Broker requests label information from the Label Information Provider grouped with the Order Filler. a) A test order is generated either on the Order Placer side or on the Order Filler side. b) In both cases, the Order Filler gets this order, and in due time, schedules it and calculates the needed containers and associated barcode labels for this order. c) The patient arrives at the specimen collection point. The patient id is entered into the Label Broker. This triggers a query from the Label Broker to the Label Information Provider to get labeling instructions for the specimens to be collected from this patient. d) The Label Information Provider grouped with the Order Filler responds with the labeling instructions. e) The Label Broker issues the containers with barcode labels. f) The labeled containers are then used for specimen collection and then sent to the laboratory for testing. Page 6 of 28

8 X.3 Actors/ Transactions X.3.1 Workflow Diagram Label Information Provider LAB-62 Query for label delivery instruction LAB-61 Label delivery request Label Broker Figure X.3-1. Laboratory Barcode Labeling Diagram Table X.3-1. LBL Integration Profile - Actors and Transactions Actors Transactions Optionality Section in Vol. 2 Label Information Provider Transaction LAB-61 R Transaction LAB-62 R Label Broker Transaction LAB-61 R 200 Note 1: Transaction LAB-62 O (Note 1) The Label Information Provider SHALL support both request mode and query mode. For the Label Broker the request mode is mandatory, and the query mode is optional. The query mode supported by Transaction LAB-62 corresponds to use cases 4 and 5. X.3.2 Transactions LAB-61: Label delivery request: This transaction contains the messages for label delivery sent by the Label Information Provider to the Label Broker. These messages include the Label information, patient information and specimen information. 210 LAB-62: Query for label delivery instruction: This transaction contains the message used by the Label Broker to query the Label Information Provider with a patient identification, and the response message sent back by the Label Information Provider, including the label information, patient information and specimen information. Page 7 of 28 Draft for Public Comment - March 26, 2007 Copyright 2006: GMSIH, SFIL, IHE-J, JAHIS

9 Table X.3-2 Laboratory Barcode Labeling - Actors and Options Actor Options Vol & Section Label Broker Query for labeling instructions Query for labeling instructions: A Label Broker operating in query mode uses transaction LAB-62 to support the workflows of use cases 4 and 5. Page 8 of 28

10 X.4 LBL Integration Profile Process Flow X.4.1 Use case 1 The Label Information Provider grouped with the Order Placer, generates the labeling instructions, and sends the label delivery request to the Label Broker. OF OP LIP LB LAB -1 In due time Label Delivery Request LAB Figure X.4-1. Label Information Provider grouped with Order Placer request mode Page 9 of 28

11 X.4.2 Use case 2 The Label Information Provider grouped with the Order Filler generates the labeling instructions, and sends the label delivery request to the Label Broker. OP OF LIP LB LAB 1 / LAB-2 In due time Label Delivery Request LAB-61 Figure X.4-2. Label Information Provider grouped with Order Filler request mode Page 10 of 28

12 X.4.3 Use case The Order Filler generates label information and sends it to the Order Placer within transaction LAB-1 or LAB-2. The Label Information Provider grouped with the Order Placer sends it to Label Broker This process flow is based on use case X.2.3. OF OP LIP LB LAB -1 without Specimen information In due time Label Delivery Request LAB-61 Figure X.4-3. Order Filler generates label information; Order Placer sends it to Label Broker Page 11 of 28

13 X.4.4 Use case 4 Upon arrival of the patient in the collection room the Label Broker queries label delivery instructions from the Label Information Provider grouped with the Order Placer. 240 This process flow is based on use case X.2.4. OF OP LIP LB LAB -1 Query for label delivery instruction LAB-62 In due time Figure X.4-4. Label Information Provider grouped with Order Placer query mode Page 12 of 28

14 X.4.5 Use case 5 Upon arrival of the patient in the collection room the Label Broker queries label delivery instructions from the Label Information Provider grouped with the Order Filler. This process flow is based on sub-use case X.2.5. OP OF LIP LB LAB 1/LAB-2 Query for label delivery instruction LAB-62 In due time Figure X.4-5. Label Information Provider grouped with Order Placer query mode 250 Page 13 of 28

15 Volume 2 - Transactions X.5 Transaction LAB-61: Label delivery request This section describes Transaction LAB-61 of the IHE Laboratory Technical Framework. X.5.1 Scope This transaction is used by the Label Information Provider to send label delivery instructions to the Label Broker. X.5.2 Use Case Roles Label Broker Label Information Provider Label delivery request 260 Actor: Label Broker Role: The Label Broker receives labeling instructions to issue the specimen container labels and stick them on the appropriate containers. Actor: Label Information Provider Role: The Label Information Provider transmits the labeling instructions to the Label Broker. X.5.3 Referenced Standard HL7 v2.5, Chapter 4 X.5.4 Interaction Diagram Page 14 of 28

16 Label Information Provider Label Broker OML^O33 New Order (ORC-1: NW) ORL^O34 Application accept (MSA-1: AA) Application error (MSA-1: AE) Application reject (MSA-1:AR) X Label delivery request (OML^O33, ORL^O34) 270 This transaction contains the messages used to send labeling instructions from the Label Information Provider to the Label Broker. X Trigger Events OML (O33): Label information sent by the Label Information Provider. ORL (O34): Application acknowledgement of the Label information sent by Label Broker. X Message Semantics Refer to the HL7 standard for the OML, ORL message of HL7 2.5 Chapter 4 and the general message semantics. Table: OML^O33 Segment Meaning Usage Card. HL7 chapter MSH Message Header R [1..1] 2 [ --- PATIENT begin R [1..1] PID Patient Identification R [1..1] 3 [ PV1 ] Patient Visit RE [0..1] 3 ] --- PATIENT end { --- SPECIMEN begin R [1..*] SPM Specimen R [1..1] 7 [{SAC}] Specimen Container O [0..*] { --- ORDER begin R [1..*] Draft for Public Comment - March 26, 2007 Page 15 of 28 Copyright 2006: GMSIH, SFIL, IHE-J, JAHIS

17 ORC Common Order (for one battery) R [1..1] 4 [{TQ1}] Timing Quantity RE [0..1] 4 [ --- OBSERVATION REQUEST begin O [O..1] OBR Observation Request R [1..1] 4 [TCD] Test Code Details O [0..1] 13 [{OBX}] Observation Result O [0..*] 7 ] --- OBSERVATION REQUEST end } --- ORDER end } --- SPECIMEN end 280 MSH-9 - Message Type (MSG) shall have its three components respectively valued to "OML", "O33" and OML_O33. This message carries the specimen container labeling instructions in the SPECIMEN segment group: The SPM segment contains the specimen ID (SPM-2), specimen type (SPM-4), specimen source site (SPM-8), specimen collection amount (SPM-12), container type (SPM-27) Optionally, the SAC segment may be used to deliver additional information on the physical container to be selected by the Label Broker. Table: ORL^O34 Segment Meaning Usage Card. HL7 chapter MSH Message header R [1..1] 2 MSA Message Acknowledgement R [1..1] 2 [{ERR}] Error C [0..*] 2 [ --- RESPONSE begin O [0..1] [PID] Patient Identification O [0..1] 3 { --- SPECIMEN begin O [0..*] SPM Specimen R [1..1] 7 [{SAC}] Specimen Container O [0..*] 13 [{ --- ORDER begin O [0..*] ORC Common Order R [1..1] 4 [{TQ1}] Timing/Quantity RE [0..1] 4 [OBR] Observation Request R [1..1] 4 }] --- ORDER end } --- SPECIMEN end ] --- RESPONSE end 290 MSH-9 - Message Type (MSG) shall have its three components respectively valued to Page 16 of 28

18 "ORL", "O34" and ORL_O34. Condition predicate for use of the ERR segment: The ERR segment SHALL be used whenever the Label Broker does not accept the labeling instruction (MSA-1 = AE or AR) OBR segment Table : OBR Segment SEQ LEN DT Usage Card. TBL# ITEM# Element name 1 4 SI O [0..1] Set ID OBR 2 22 EI R [1..1] Placer Order Number 3 22 EI RE [0..1] Filler Order Number CE R [1..1] Universal Service Identifier 5 2 ID X [0..0] Priority OBR 6 26 TS X [0..0] Requested Date/Time 7 26 TS X [0..0] Observation Date/Time # 8 26 TS X [0..0] Observation End Date/Time # 9 20 CQ X [0..0] Collection Volume * XCN O [0..*] Collector Identifier * 11 1 ID RE [0..1] Specimen Action Code * CE X [0..0] Danger Code ST X [0..0] Relevant Clinical Information TS X [0..0] Specimen Received Date/Time * SPS X [0..0] Specimen Source XCN R [1..1] Ordering Provider XTN RE [0..2] Order Callback Phone Number ST X [0..0] Placer Field ST X [0..0] Placer Field ST X [0..0] Filler Field ST X [0..0] Filler Field TS X [0..0] Results Rpt/Status Chng - Date/Time MOC X [0..0] Charge to Practice ID C [0..1] Diagnostic Serv Sect ID 25 1 ID X [0..0] Result Status PRL X [0..0] Parent Result TQ X [0..0] Quantity/Timing XCN O [0..*] Result Copies To EIP X [0..0] Parent ID X [0..0] Transportation Mode CE O [0..1] Reason for Study NDL O [0..1] Principal Result Interpreter + Page 17 of 28

19 SEQ LEN DT Usage Card. TBL# ITEM# Element name NDL O [0..1] Assistant Result Interpreter NDL O [0..1] Technician NDL O [0..1] Transcriptionist TS O [0..1] Scheduled Date/Time NM O [0..1] Number of Sample Containers * CE O [0..1] Transport Logistics of Collected Sample * CE O [0..1] Collector's Comment * CE X [0..0] Transport Arrangement Responsibility ID X [0..0] Transport Arranged 42 1 ID X [0..0] Escort Required CE X [0..0] Planned Patient Transport Comment CE O [0..1] Procedure Code CWE O [0..1] Procedure Code Modifier CE O [0..1] Placer Supplemental Service Information CE O [0..1] Filler Supplemental Service Information CWE X [0..0] Medically Necessary Duplicate Procedure Reason IS O [0..1] Result Handling X Expected Actions 300 The OML message with Order Control Code NW received from the Label Information Provider, contains the specimen container labeling instructions for the Label Broker. The Label Broker will reply with an ORL^O34 message with either Accept (MSA-1 = AA) or Reject (MSA-1 = AR) or Error (MSA-1 = AE). Page 18 of 28

20 X.6 Transaction LAB-62: Query for label delivery instruction This section describes Transaction LAB-62 of the IHE Laboratory Technical Framework. X.6.1 Scope 310 This transaction is used by the Label Broker to query the specimen container labeling instructions from the Label Information Provider. X.6.2 Use Case Roles Label Broker Label Information Provider Query for label delivery instruction Actor: Label Broker Role: The Label Broker sends a query to the Label Information Provider in order to get the labeling instructions related to the laboratory test orders for a patient. Actor: Label Information Provider Role: The Label Information Provider responds to the query with the labeling instructions. X.6.3 Referenced Standard HL7 version 2.5: 320 X.6.4 Interaction Diagram Page 19 of 28

21 Label Information Provider Label Broker QBP^SLI^QBP_Q11 Query for label delivery In due time RSP^SLI^RSP_K11 Label Delivery Request X Query For Label Delivery (QBP^SLI^QBP_Q11, RSP^SLI^RSP_K11) This Message is sent by the Label Broker to the Label Information Provider to request specimen container labeling instructions related to a patient. X Trigger Events QBP(Q11) : Query for specimen container labeling instructions sent by the Label Broker. RSP(K11) : Response including the labeling instructions sent by the Label Information Provider. X Message Semantics 330 Refer to the HL7 standard for the QBP message of HL7 2.5 Chapter 5 and the general message semantics. Table : QBP^SLI^QBP_Q11 Segment Meaning Usage Card. HL7 chapter MSH Message header R [1..1] 2 [{SFT}] Software Segment O [0..*] 2 QPD Query Parameter Definition R [1..1] 5 RCP Response Control Parameter R [1..1] 5 [DSC] Continuation Pointer O [0..1] 2 MSH-9 - Message Type (MSG) shall be valued as: QBP^SLI^QBP_Q11 Page 20 of 28

22 Table : RSP^SLI^RSP_K11 Segment Meaning Usage Card. HL7 chapter MSH Message header R [1..1] 2 [{SFT}] Software Segment O [0..*] 2 MSA Message Acknowledgement R [1..1] 2 [ERR] Error O [0..1] 2 QAK Query Acknowledgement R [1..1] 5 QPD Query Parameter Definition R [1..1] 5 { --- SPECIMEN begin R [1..*] SPM Specimen R [1..1] 7 [{OBX}] Observation related to specimen O [0..*] 7 [{SAC}] Specimen Container O [0..*] 13 [ --- PATIENT begin R [1..1] PID Patient Identification R [1..1] 3 [{OBX}] Observation related to the patient O [0..*] 7 ] --- PATIENT end { --- ORDER begin R [1..*] ORC Common Order R [1..1] 4 [{TQ1}] Timing/Quantity RE [0..1] 4 [ --- OBSERVATION REQUEST begin O [0..1] OBR Observation Request R [1..1] 4 [ TCD ] Test Code Details O [0..1] 13 [{OBX}] Observation Result O [0..*] 7 ] --- OBSERVATION REQUEST end } --- ORDER end } --- SPECIMEN end MSH-9 - Message Type (MSG) shall have its two first components respectively valued to "RSP" and "K11". Page 21 of 28

23 IHE Laboratory TF Supplement Laboratory Barcode Labeling for public comment QPD segment Table: QPD segment SEQ LEN DT Usage Card. TBL# ITEM# Element name 1 60 CE R [1..1] Message Query Name 2 32 ST R [1..1] Query Tag 3 80 CK C [0..1] Patient ID CX C [0..1] Patient Visit Number 5 22 EI C [0..1] Placer Group Number 6 22 EI C [0..1] Placer Order Number, 7 22 EI C [0..1] Filler Order Number QPD-1 Message Query Name (CE), required Must be valued SLI^Specimen Labeling Instructions^IHE_LABTF QPD-2 Query Tag (ST), required Unique to each query message instance. This identifies the query instance. It is used to match the response with the query. QPD-3 Patient Identifier, conditional Contains a patient unique identifier. QPD-4 Patient Visit Number, conditional Contains a patient visit number, as defined in LSWF. QPD-5 Placer Group Number, conditional Contains a placer group number, as defined in LSWF. QPD-6 Placer Order Number, conditional Contains a placer order number, as defined in LSWF. QPD-7Filler Order Number, conditional Contains a filler order number, as defined in LSWF. 360 Condition predicate: At least one of the fields QPD-3, QPD4, QPD-5, QPD-6, QPD-7 must be valued. In case QPD-3 or QPD-4 is used and there is more than one pending test order for the patient id or the visit number, it is the responsibility of the application implementing the Label Information Provider Actor to decide whether to pick up one or all of the pending orders. The business rules governing this decision are out of the scope of this Integration Profile. Page 22 of 28

24 RCP segment Table : RCP segment SEQ LEN DT Usage Card. TBL# ITEM# Element name 1 1 ID R [1..1] Query Priority 2 10 CQ O [0..1] Quantity Limited Request NM CE 3 60 CE R [1..1] Response Modality ID O [0..*] Segment group inclusion 370 RCP-1 Query Priority(ID), required Shall be fixed to "I" (=Immediate). RCP-2 Quantity Limited Request (CQ), optional As for the 1st component "Quantity"(NM), Number of records that will be returned in each increment of the response. If no value is given, the entire response will be returned in a single increment. As for the 2nd component "Units"(CE), "RD"(=Records) is always set. If no value is given, the default is RD. RCP-3 Response Modality (CE), required Shall be fixed to "R" (=Realtime). RCP-7 Segment group inclusion (ID), optional Specifies those optional segment groups which are to be included in the response. If this field is not valued, all segment groups will be included. X Expected Actions 380 The Label Information Provider parses the query parameters, and selects the appropriate pending test order(s) matching these parameters, according to its own business rules, and builds the response, which is sent back immediately to the Label Broker. Page 23 of 28

25 X.7 Examples X.7.1 Example for use case X Storyboard 1. Dr. Yamada examines the patient (ID: ) and orders liver function tests and blood count through the HIS terminal. 2. The patient goes to the blood collecting room. 3. The receptionist for blood collecting checks the test orders and accepts the reception through the HIS terminal. 4. The HIS sends the label information to the barcode labeling robotic system. 5. The robotic system issues the containers with barcode label. 6. The blood collector takes blood of the patient. Human actors and organizations participating to the process: Assigning authority: Placer: Label Broker: Ordering facility: Patient: Suzuki national hospital Enter-gastric department LBL system Enter-gastric department Taro Toyota, Patient hospital identifier: , Patient visit number: , class = outpatient Orderer: Dr. Yamada. ID number ID numbers used by the workflow: ID number Value Assigned by Patient hospital ID Admission office (ADT) Patient visit number Admission office (ADT) Observation Order Code: liver function test Enter-gastric department (OP) Observation Order Code: Blood count Enter-gastric department (OP) Page 24 of 28

26 400 X Interaction diagram Label Information Provider Label Broker Blood collect reception OML^O33 ORL^O34 X Message LAB-61(LIP LB): New Label Delivery Request transmitted to the LB MSH ^~\& LIP Enter-gastric department LB LBL system OML^O33^OML_O P 2.5 USA EN PID ^^^Suzuki National Hospital^PI Toyota^Taro^^^^^L M PV1 1 O SPM ^Venous blood P ^Chemistry ORC NW ^Yamada^Jiro 14789^Yamada^Jiro 051^Entergastric department TQ1 R OBR ^liver function^local ^Yamada^Jiro SPM ^Venous blood P ^hematology ORC NW ^Yamada^Jiro 14789^Yamada^Jiro 051^Entergastric department TQ1 R OBR ^blood count^local ^Yamada^Jiro The related acknowledgement message isn t shown. Page 25 of 28

27 X.7.2 Example for use case X Storyboard 1. Dr. Yamada examines the patient (ID: ) and orders liver function tests and blood count through the HIS terminal. 2. The patient goes to the blood collecting room. 3. The patient inserts his ID card to the reception machine for blood collecting. 4. The barcode labeling robotic system sends the query for label delivery to the HIS 5. The HIS sends the label information back to the barcode labeling robotic system. 6. The robotic system issues the containers with barcode label. 7. The blood collector takes blood of the patient. Human actors and organizations participating to the process: Assigning authority: Placer: Label Broker: Ordering facility: Patient: Suzuki national hospital Enter-gastric department LBL system Enter-gastric department Taro Toyota, Patient hospital identifier: , Patient visit number: , class = outpatient Orderer: Dr. Yamada. ID number ID numbers used by the workflow: ID number Value Assigned by Patient hospital ID Patient visit number Observation Order Code(liver function test) Observation Order Code(Blood count) Admission office (ADT) Admission office (ADT) Enter-gastric department (OP) Enter-gastric department (OP) Page 26 of 28

28 X Interaction diagram Label Information Provider Label Broker QBP^SLI^QBP_Q11 Query for label delivery Blood collect Reception RSP^SLI^RSP_K11 Label Delivery Request X Message 440 LAB-62(LB LIP): Query for label delivery MSH ^~\& LB LBL system LIP Enter-gastric department QBP^SLI^QBP_Q P 2.5 USA EN QPD SLI^Specimen Labeling Instructions^IHE_LABTF RCP I R LAB-62(LIP LB): Label Delivery Request transmitted to the LB MSH ^~\& LIP Enter-gastric department LB LBL system RSP^SLI^RSP_K P 2.5 USA EN PID ^^^Suzuki National Hospital^PI Toyota^Taro^^^^^L M PV1 1 O SPM ^Venous blood P ^Chemistry ORC NW ^Yamada^Jiro 14789^Yamada^Jiro 051^Entergastric department TQ1 R OBR ^liver function^local ^Yamada^Jiro SPM ^Venous blood P ^hematology ORC NW ^Yamada^Jiro 14789^Yamada^Jiro 051^Entergastric department TQ1 R OBR ^blood count^local ^Yamada^Jiro Page 27 of 28