HL7 - REFACTORED

Chapter Chair:	Hans Buitendijk Cerner Corporation
Chapter Chair:	Lorrain Constable Constable Consulting Inc.
Chapter Chair:	Robert Hausam MD Hausam Consulting
Chapter Chair:	Patrick Lloyd ICode Solutions
Chapter Chair:	Ken McCaslin Accenture Federal
Chapter Chair:	Riki Merrick Vernetzt, LLC
Chapter-Chair	J.D. Nolen Mercy Children’s Hospital
Chapter Chair	David Burgess LabCorp
Editor:	Riki Merrick Vernetzt, LLC
Sponsoring TC:	Orders & Observations
List Server:	ord@lists.hl7.org

PURPOSE

This Materials Management chapter defines abstract messages for the purpose of communicating various events related to the transactions derived from supply chain management within a healthcare facility. There are two basic types of messages defined in this chapter: inventory item master file updates, and supply item sterilization messages.

The inventory item master file segments published in this chapter are based on master file add and update messages between applications such as materials management, scheduling, and sterilization applications.

The sterilization and decontamination messages published in this chapter are based on a request, response, or unsolicited update. These transactions occur between an instrument-tracking system and a sterilizer or washer.

This chapter describes various roles under which applications might operate. The roles discussed in this chapter illustrate the underlying model used to develop this specification. They do not imply the need for a particular application model or method of implementation.

This chapter defines the transactions at the seventh level, that is, the abstract message. Various schemes are used to generate the actual characters that comprise the messages according to the communication environment. The HL7 Encoding Rules will be used where there is not a complete Presentation Layer. This is described in Chapter 1, "Relationship to Other Protocols." The examples included in this chapter were constructed using the HL7 Encoding Rules.

Inventory Item Master Updates

The goal of the Inventory Item Master Update message specifications is to facilitate the communication of inventory item master catalog and lot information between applications. The main subject of such communication is the supply item. These inventory item master segments are used with trigger event M15 – Inventory Item Master File Message , and M16 – Inventory Item Master File Message – Enhanced. The message structures of these events are published in Chapter 8 - Master Files.

Item Master Catalog

The item master catalog provides a catalog of supplies used for ordering to replenish inventory at supply locations, for general usage in a healthcare facility for scheduled appointments, surgery, and to provide identifiers for instrument-tracking used for the sterilization process. The catalog consists of numerous attributes related to a supply item. Supply items and associated attributes can be specific to a domain such as Inventory, Scheduling, Pharmacy, and Sterilization.

Inventory Locations

Inventory locations contain a list of items that are stocked at the location, or that can be ordered from the location (but not stocked on a regular basis). Inventory locations receive updates to the attributes of supply items from the general supply location's item master catalog. Even though the general supply location's item master catalog and the other inventory locations item master both share the majority of the supply item attributes, those attributes can have a different value in each location. For example, the status of a supply item (active, inactive, pending inactive), can be inactive in the general supply location item master catalog (meaning it cannot be ordered), but the same item may be pending inactive at another inventory location that still has the supply item in stock, and will issue the supply item until the stock is depleted, but cannot order to replenish the stock at this location.

The following are the primary attributes of a supply item:

Sterilization and Decontamination

Sterilization and decontamination messages in this chapter are exchanged between a sterilizer or washer and an Instrument-tracking System. The main focus of the sterilization and decontamination process is a load or grouping of supply items. These messages communicate sterilizer configuration, sterilizer lot, and device and cycle data messages related to instances of sterilizing and decontaminating supply items.

Sterilization is a process used to render a product free from viable microorganisms in order to meet infection prevention standards. Sterilizers are defined as apparatus used to sterilize medical devices, equipment and supplies by direct exposure to the sterilizing agent. The typical sterilizing agent for high temperature sterilization is saturated steam under pressure; low temperature sterilizing agents are peracetic acid or ethylene oxide gas.

Decontamination is defined by the Occupational Safety and Health Administration (OSHA) as the use of physical or chemical means to remove, inactivate or destroy blood-borne pathogens on a surface or item to the point where they are no longer capable of transmitting infectious particles and the surface or item is rendered safe for handling, use or disposal. {29 CFR 1910.1030} Washers provide decontamination services in order to render items safe for handling.

Steam sterilizers have defined cycles that achieve sterilization by attaining certain temperatures for specific lengths of time. These cycles are validated using AAMI (Association for Advancement of Medical Instrumentation) standards.

Ethylene Oxide gas and peracetic acid sterilizers have defined cycles that are validated by the manufacturer's research to achieve sterilization at specific temperatures and exposure times to the sterilant.

Sterilization and decontamination cycles are defined as a sequence of steps or phases that are designed to achieve sterilization or decontamination.

Typical phases for steam sterilization include Condition, Sterilize and Exhaust. Phases for Ethylene Oxide sterilization include Condition, Sterilize, Exhaust and Aerate. Peracetic acid sterilizers also have similar phases.

The following tables contain examples of typical cycles for sterilizers and washers.

Representative Steam Sterilization Cycles
Cycles	Sterilize Temperature	Sterilize Time	Dry Time	Recommended Load
Express	270°F (132°C)	4.0 Min	3.0 MIN.	Single wrapped instrument tray with a single instrument. Non-porous good, only.
Flash	270°F (132°C)	3.0 MIN	1.0 MIN	Unwrapped instrument tray with a single instrument

Prevacuum Testing Cycles for Steam Sterilizers
Prevacuum Testing Cycles	Sterilizer Temperature	Sterilize Time	Dry Time	Recommended Load
Leak Test	270°F (132°C)	N/A	N/A	N/A
Dart Test	270°F (132°C)	3½ MIN.	1.0 MIN	Bowie-Dick Test or DART
Dart Warmup	270°F (132°C)	3.0 MIN.	1.0 MIN.	N/A

Application roles

In the sterilization and decontamination specification, there are two roles that an application can assume: a filler application role, and a placer application role. These application roles define the interaction that an application will have with other applications in the messaging environment. In many environments, any one application may take on more than one application role.

In this specification, the definition of application roles is not intended to define or limit the functionality of specific products developed by vendors of such applications. Instead, this information is provided to help define the model used to develop this specification, and to provide an unambiguous way for applications to communicate with each other.

Trigger Events

This chapter defines trigger events used to communicate supply item information between applications.

The inventory item master file notification trigger events are defined in Chapter 8, Master Files. The sterilization and decontamination related trigger events in this chapter are defined in section 17.4, "Inventory Item Master Messages Segments," and 17.5, "Placer Application Requests and Trigger Events."

Statuses

The status of a supply item describes the state of the supply item in the item master catalog and at an inventory location. Typical statuses of a supply item may include the following: Active, Pending Inactive, and Inactive.

The status of a load describes the state of a load during a sterilization cycle. Typical statuses of a load may include the following: Pending, Active, Complete, and Canceled.

Glossary

Bowie-Dick Test

A diagnostic test of a dynamic-air-removal steam sterilizer's ability to remove air from the sterilizer chamber and prevent air reentrainment.

Catalog Item

Supply items that are available to be ordered from the item master catalog.

Cycle - Sterilization

A define sequence of operational events designed to achieve sterilization which are carried out in a sealed chamber.

Cycle - Steam Sterilization, Gravity Displacement Type

Type of sterilization cycle in which incoming steam displaces residual air through a port or drain in or near the bottom of the sterilizing chamber.

Cycle Time

The total elapsed time of a sterilization cycle from the time the process is initiated until the cycle is completed. Cycle time may include heat-up time, exposure time, come-down time, cooling and drying time and on appropriate equipment, pre- and post-vacuum time.

Decontamination

The use of physical or chemical means to remove, inactivate or destroy blood borne pathogens on a surface or item to the point where they are no longer capable of transmitting infectious particles and the surface or item is rendered safe for handling, use or disposal.

Entrainment

Collecting or transporting of solid particles or a second fluid or vapor by the flow of the primary fluid or vapor at high velocity.

EO

Ethylene Oxide Gas used as low temperature sterilizing agent.

Exposure Time

Period of time during a sterilization process in which items are exposed to the sterilant at the specified sterilization parameters.

Lot Control

Numbers, letters or a combination of both by which a particular group of products can be traced to a particular sterilization operation.

Nonstocked Items

Supply items that are not routinely ordered and issued at a specific supply location, but are available to be ordered depending on the item status.

NonCatalog Item

Supply items that are ordered and issued at a specific supply location, but are not available to be ordered through the item master catalog.

Par Level

Par Level refers to an inventory location specific to a particular area of the healthcare facility, such as Surgery.

Sterile

State of being free from all living microorganisms.

Sterilization

The process used to render a product free from viable microorganisms.

Note: In a sterilization process, the nature of a microbiological death is described by an exponential function. Therefore, the presence of microorganisms on any individual item can be expressed in terms of probability. While this probability can be reduced to a very low number, it can never be reduced to zero.

Sterilizer

An apparatus used to sterilize medical devices, equipment and supplies by direct exposure to the sterilizing agent.

Stocked Items

Supply items that are routinely ordered and issued at a specific supply location.

TDC

Tubes, Drains and Catheters

Washer

An apparatus that provides decontamination services in order to render items safe for handling.

Organization of This Chapter: Trigger Events and Message Definitions

This specification contains four functional groupings of trigger events and message definitions. The trigger events within each of the placer, filler, and query functional groupings share the same or similar message definitions.

The first functional grouping of trigger events and message definitions describes the common master file notification messages for use of the record level events for adds, deletes, updates, deactivations, and reactivations. This functional grouping is specific to the item master inventory messages.

The second functional grouping of trigger events and message definitions describes placer request transactions. This grouping defines the trigger events and message definitions for transactions from applications acting in a placer application role, and also defines the related filler application response messages sent back by applications fulfilling the auxiliary role. These messages are described in section 17.5, "Placer Application Requests and Trigger Events."

The second functional grouping describes trigger events and message definitions for unsolicited transactions from applications acting in the filler application role. This grouping describes the unsolicited messages originating from an application fulfilling the filler role, and the response messages sent back by applications fulfilling the auxiliary role. These messages are described in section 17.6, "Filler Application Messages and Trigger Events Unsolicited."

The notation used to describe the sequence, optionality, and repetition of segments is described in Chapter 2, "Format for defining abstract messages."

Update mode

This chapter uses the "Action code/unique identifier" mode for updating via repeating segments. For more information on updating via repeating segments, please see section 2.15.4, "Modes for updating via repeating segments," in Chapter 2. The definition of the "Action code/unique identifier" update mode can be found in Chapter 2, section 2.15.4.2, "Action code/unique identifier mode update definition."

Inventory Item Master Messages Segments

This section describes the segments described in the Inventory Item Master File Message (Event M15) and Inventory Item Master File Message - Enhanced (Event M16) master file messages. The description of these events and the messages structures are published in Chapter 8, Master Files. The M15 Inventory Item Master File trigger event and the IIM inventory item master segment is a limited implementation. The M16 Inventory Item Master File - Enhanced trigger event is a comprehensive Materials Management message.

The enhanced inventory item master message communicates additions and updates of supply items and their attributes from a general supply location to additional supply locations within a healthcare facility.

The general supply inventory location sends a transaction to multiple inventory locations with this trigger event, communicating adds and changes to item master catalog and inventory supply items.

The ILT segment formerly published in v2.5 Chapter 8, Master Files, will now be published in this chapter because of its use in the Materials Management domain.

IIM - Inventory Item Master Segment

The Inventory Item Master segment (IIM) contains information about the stock of product that can be used to fulfill an ordered test/service. All of the fields in this segment describe the test/service and other basic attributes pertaining to Service Item defined within an Other Observation/Service Item master file. This segment is related to centrally stocked or supply management concerns.

HL7 Attribute Table - IIM - Inventory Item Master Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	C.LEN	Flags
IIM
1	Primary Key Value - IIM	CWE	R		[1..1]	01897
2	Service Item Code	CWE	R		[1..1]	01799
3	Inventory Lot Number	ST	O		[0..1]	01800	250	#
4	Inventory Expiration Date	DTM	O		[0..1]	01801
5	Inventory Manufacturer Name	CWE	O		[0..1]	01802
6	Inventory Location	CWE	O		[0..1]	01803
7	Inventory Received Date	DTM	O		[0..1]	01804
8	Inventory Received Quantity	NM	O		[0..1]	01805	12	#
9	Inventory Received Quantity Unit	CWE	O	0818 Package	[0..1]	01806
10	Inventory Received Item Cost	MO	O		[0..1]	01807
11	Inventory On Hand Date	DTM	O		[0..1]	01808
12	Inventory On Hand Quantity	NM	O		[0..1]	01809	12	#
13	Inventory On Hand Quantity Unit	CWE	O	0818 Package	[0..1]	01810
14	Procedure Code	CNE	O		[0..1]	00393
15	Procedure Code Modifier	CNE	O		[0..*]	01316

IIM-1: Primary Key Value - IIM (CWE) 01897

FIXME

IIM-2: Service Item Code (CWE) 01799

FIXME

IIM-3: Inventory Lot Number (ST) 01800

FIXME

IIM-4: Inventory Expiration Date (DTM) 01801

FIXME

IIM-5: Inventory Manufacturer Name (CWE) 01802

FIXME

IIM-6: Inventory Location (CWE) 01803

FIXME

IIM-7: Inventory Received Date (DTM) 01804

FIXME

IIM-8: Inventory Received Quantity (NM) 01805

FIXME

IIM-9: Inventory Received Quantity Unit (CWE) 01806

FIXME

IIM-10: Inventory Received Item Cost (MO) 01807

FIXME

IIM-11: Inventory On Hand Date (DTM) 01808

FIXME

IIM-12: Inventory On Hand Quantity (NM) 01809

FIXME

IIM-13: Inventory On Hand Quantity Unit (CWE) 01810

FIXME

IIM-14: Procedure Code (CNE) 00393

FIXME

IIM-15: Procedure Code Modifier (CNE) 01316

FIXME

ITM - Material Item Segment

The Material Item segment (ITM) contains information about inventory supply items (stocked or non-stocked).

HL7 Attribute Table - ITM - Material Item Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	C.LEN	Flags
ITM
1	Item Identifier	EI	R		[1..1]	02186
2	Item Description	ST	O		[0..1]	02274	999	#
3	Item Status	CWE	O	0776(S) Item Status(Suggested)	[0..1]	02187
4	Item Type	CWE	O	0778 Item Type	[0..1]	02188
5	Item Category	CWE	O		[0..1]	02189
6	Subject to Expiration Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02190
7	Manufacturer Identifier	EI	O		[0..1]	02191
8	Manufacturer Name	ST	O		[0..1]	02275	999	#
9	Manufacturer Catalog Number	ST	O		[0..1]	02192	20	#
10	Manufacturer Labeler Identification Code	CWE	O		[0..1]	02193
11	Patient Chargeable Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02070
12	Transaction Code	CWE	O	0132 Transaction Code	[0..1]	00361
13	Transaction Amount - Unit	CP	O		[0..1]	00366
14	Stocked Item Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02197
15	Supply Risk Codes	CWE	O	0871 Supply Risk Codes	[0..1]	02266
16	Approving Regulatory Agency	XON	O	0790 Approving Regulatory Agency	[0..*]	02199
17	Latex Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02200
18	Ruling Act	CWE	O	0793 Ruling Act	[0..*]	02201
19	Item Natural Account Code	CWE	O	0320 Item Natural Account Code	[0..1]	00282
20	Approved To Buy Quantity	NM	O		[0..1]	02203	6	#
21	Approved To Buy Price	MO	O		[0..1]	02204
22	Taxable Item Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02205
23	Freight Charge Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02206
24	Item Set Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02207
25	Item Set Identifier	EI	O		[0..1]	02208
26	Track Department Usage Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02209
27	Procedure Code	CNE	O		[0..1]	00393
28	Procedure Code Modifier	CNE	O		[0..*]	01316
29	Special Handling Code	CWE	O	0376(S) Special Handling Code(Suggested)	[0..1]	01370
30	Hazardous Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	03388
31	Sterile Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	03304
32	Material Data Safety Sheet Number	EI	O		[0..1]	03305
33	United Nations Standard Products and Services Code	CWE	O	0396(R) Coding System(Required)	[0..1]	03306
34	Contract Date	DR	O		[0..1]	02415
35	Manufacturer Contact Name	XPN	O		[0..1]	02416
36	Manufacturer Contact Information	XTN	O		[0..1]	02417
37	Class of Trade	ST	O		[0..1]	02418
38	Field Level Event Code	ID	O	0180(R) Record-level Event Code(Required)	[0..1]	02419

ITM-1: Item Identifier (EI) 02186

FIXME

ITM-2: Item Description (ST) 02274

FIXME

ITM-3: Item Status (CWE) 02187

FIXME

ITM-4: Item Type (CWE) 02188

FIXME

ITM-5: Item Category (CWE) 02189

FIXME

ITM-6: Subject to Expiration Indicator (CNE) 02190

FIXME

ITM-7: Manufacturer Identifier (EI) 02191

FIXME

ITM-8: Manufacturer Name (ST) 02275

FIXME

ITM-9: Manufacturer Catalog Number (ST) 02192

FIXME

ITM-10: Manufacturer Labeler Identification Code (CWE) 02193

FIXME

ITM-11: Patient Chargeable Indicator (CNE) 02070

FIXME

ITM-12: Transaction Code (CWE) 00361

FIXME

ITM-13: Transaction Amount - Unit (CP) 00366

FIXME

ITM-14: Stocked Item Indicator (CNE) 02197

FIXME

ITM-15: Supply Risk Codes (CWE) 02266

FIXME

ITM-16: Approving Regulatory Agency (XON) 02199

FIXME

ITM-17: Latex Indicator (CNE) 02200

FIXME

ITM-18: Ruling Act (CWE) 02201

FIXME

ITM-19: Item Natural Account Code (CWE) 00282

FIXME

ITM-20: Approved To Buy Quantity (NM) 02203

FIXME

ITM-21: Approved To Buy Price (MO) 02204

FIXME

ITM-22: Taxable Item Indicator (CNE) 02205

FIXME

ITM-23: Freight Charge Indicator (CNE) 02206

FIXME

ITM-24: Item Set Indicator (CNE) 02207

FIXME

ITM-25: Item Set Identifier (EI) 02208

FIXME

ITM-26: Track Department Usage Indicator (CNE) 02209

FIXME

ITM-27: Procedure Code (CNE) 00393

FIXME

ITM-28: Procedure Code Modifier (CNE) 01316

FIXME

ITM-29: Special Handling Code (CWE) 01370

FIXME

ITM-30: Hazardous Indicator (CNE) 03388

FIXME

ITM-31: Sterile Indicator (CNE) 03304

FIXME

ITM-32: Material Data Safety Sheet Number (EI) 03305

FIXME

ITM-33: United Nations Standard Products and Services Code (CWE) 03306

FIXME

ITM-34: Contract Date (DR) 02415

FIXME

ITM-35: Manufacturer Contact Name (XPN) 02416

FIXME

ITM-36: Manufacturer Contact Information (XTN) 02417

FIXME

ITM-37: Class of Trade (ST) 02418

FIXME

ITM-38: Field Level Event Code (ID) 02419

FIXME

STZ - Sterilization Parameter Segment

The STZ segment contains sterilization-specific attributes of a supply item.

HL7 Attribute Table - STZ - Sterilization Parameter Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #
STZ
1	Sterilization Type	CWE	O	0806 Sterilization Type	[0..1]	02213
2	Sterilization Cycle	CWE	O	0702 Cycle Type	[0..1]	02214
3	Maintenance Cycle	CWE	O	0809 Maintenance Cycle	[0..1]	02215
4	Maintenance Type	CWE	O	0811 Maintenance Type	[0..1]	02216

STZ-1: Sterilization Type (CWE) 02213

FIXME

STZ-2: Sterilization Cycle (CWE) 02214

FIXME

STZ-3: Maintenance Cycle (CWE) 02215

FIXME

STZ-4: Maintenance Type (CWE) 02216

FIXME

VND - Purchasing Vendor Segment

This segment contains purchasing vendors that supply the inventory supply item specified in the ITM segment.

HL7 Attribute Table - VND - Purchasing Vendor Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length	C.LEN	Flags
VND
1	Set Id – VND	SI	R		[1..1]	02217	[1..4]
2	Vendor Identifier	EI	R		[1..1]	02218
3	Vendor Name	ST	O		[0..1]	02276		999	#
4	Vendor Catalog Number	EI	O		[0..1]	02219
5	Primary Vendor Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02220
6	Corporation	EI	O		[0..*]	02420
7	Primary Contact	XCN	O		[0..1]	02421
8	Contract Adjustment	MOP	O		[0..1]	02422
9	Associated Contract ID	EI	O		[0..*]	02423
10	Class of Trade	ST	O		[0..*]	02424
11	Pricing Tier Level	CWE	O		[0..1]	02425

VND-1: Set Id – VND (SI) 02217

FIXME

VND-2: Vendor Identifier (EI) 02218

FIXME

VND-3: Vendor Name (ST) 02276

FIXME

VND-4: Vendor Catalog Number (EI) 02219

FIXME

VND-5: Primary Vendor Indicator (CNE) 02220

FIXME

VND-6: Corporation (EI) 02420

FIXME

VND-7: Primary Contact (XCN) 02421

FIXME

VND-8: Contract Adjustment (MOP) 02422

FIXME

VND-9: Associated Contract ID (EI) 02423

FIXME

VND-10: Class of Trade (ST) 02424

FIXME

VND-11: Pricing Tier Level (CWE) 02425

FIXME

PKG - Packaging Segment

This segment contains the type of packaging available for the inventory supply item to be ordered and/or issued to a department or other supply location for a specified Purchasing Vendor. It would be recommended to send this segment in descending unit of measure order corresponding with the ascending Set ID.

HL7 Attribute Table - PKG - Packaging Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length	C.LEN	Flags
PKG
1	Set Id - PKG	SI	R		[1..1]	02221	[1..4]
2	Packaging Units	CWE	O	0818 Package	[0..1]	02222
3	Default Order Unit Of Measure Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02223
4	Package Quantity	NM	O		[0..1]	02224		12	#
5	Price	CP	O		[0..1]	02225
6	Future Item Price	CP	O		[0..1]	02226
7	Future Item Price Effective Date	DTM	O		[0..1]	02227
8	Global Trade Item Number	CWE	O		[0..1]	03307
9	Contract Price	MO	O		[0..1]	02426
10	Quantity of Each	NM	O		[0..1]	02427
11	Vendor Catalog Number	EI	O		[0..1]	02428

PKG-1: Set Id - PKG (SI) 02221

FIXME

PKG-2: Packaging Units (CWE) 02222

FIXME

PKG-3: Default Order Unit Of Measure Indicator (CNE) 02223

FIXME

PKG-4: Package Quantity (NM) 02224

FIXME

PKG-5: Price (CP) 02225

FIXME

PKG-6: Future Item Price (CP) 02226

FIXME

PKG-7: Future Item Price Effective Date (DTM) 02227

FIXME

PKG-8: Global Trade Item Number (CWE) 03307

FIXME

PKG-9: Contract Price (MO) 02426

FIXME

PKG-10: Quantity of Each (NM) 02427

FIXME

PKG-11: Vendor Catalog Number (EI) 02428

FIXME

PCE - Patient Charge Cost Center Exception Segment

The Patient Charge Cost Center Exception segment identifies the Patient Price associated with Cost Center and Patient Charge Identifier combinations that should be used in an instance that the item is billed to a patient. The grouping of Cost Center accounts, Patient Charge Identifier, and Patient Price is unique.

HL7 Attribute Table - PCE - Patient Charge Cost Center Exception Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length
PCE
1	Set ID – PCE	SI	R		[1..1]	02228	[1..4]
2	Cost Center Account Number	CX	O	0319 Department Cost Center	[0..1]	00281
3	Transaction Code	CWE	O	0132 Transaction Code	[0..1]	00361
4	Transaction Amount - Unit	CP	O		[0..1]	00366

PCE-1: Set ID – PCE (SI) 02228

FIXME

PCE-2: Cost Center Account Number (CX) 00281

FIXME

PCE-3: Transaction Code (CWE) 00361

FIXME

PCE-4: Transaction Amount - Unit (CP) 00366

FIXME

IVT - Material Location Segment

The Material Location segment (IVT) contains information specific to an inventory location for the inventory supply item in the Material Item (ITM) segment.

HL7 Attribute Table - IVT - Material Location Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length	C.LEN	Flags
IVT
1	Set Id – IVT	SI	R		[1..1]	02062	[1..4]
2	Inventory Location Identifier	EI	R		[1..1]	02063
3	Inventory Location Name	ST	O		[0..1]	02277		999	#
4	Source Location Identifier	EI	O		[0..1]	02064
5	Source Location Name	ST	O		[0..1]	02278		999	#
6	Item Status	CWE	O	0625(S) Item Status Codes(Suggested)	[0..1]	02065
7	Bin Location Identifier	EI	O		[0..*]	02066
8	Order Packaging	CWE	O	0818 Package	[0..1]	02067
9	Issue Packaging	CWE	O		[0..1]	02068
10	Default Inventory Asset Account	EI	O		[0..1]	02069
11	Patient Chargeable Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02070
12	Transaction Code	CWE	O	0132 Transaction Code	[0..1]	00361
13	Transaction Amount - Unit	CP	O		[0..1]	00366
14	Item Importance Code	CWE	O	0634 Item Importance Codes	[0..1]	02073
15	Stocked Item Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02074
16	Consignment Item Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02075
17	Reusable Item Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02076
18	Reusable Cost	CP	O		[0..1]	02077
19	Substitute Item Identifier	EI	O		[0..*]	02078
20	Latex-Free Substitute Item Identifier	EI	O		[0..1]	02079
21	Recommended Reorder Theory	CWE	O	0642 Reorder Theory Codes	[0..1]	02080
22	Recommended Safety Stock Days	NM	O		[0..1]	02081		4	#
23	Recommended Maximum Days Inventory	NM	O		[0..1]	02082		4	#
24	Recommended Order Point	NM	O		[0..1]	02083		8	#
25	Recommended Order Amount	NM	O		[0..1]	02084		8	#
26	Operating Room Par Level Indicator	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02085

IVT-1: Set Id – IVT (SI) 02062

FIXME

IVT-2: Inventory Location Identifier (EI) 02063

FIXME

IVT-3: Inventory Location Name (ST) 02277

FIXME

IVT-4: Source Location Identifier (EI) 02064

FIXME

IVT-5: Source Location Name (ST) 02278

FIXME

IVT-6: Item Status (CWE) 02065

FIXME

IVT-7: Bin Location Identifier (EI) 02066

FIXME

IVT-8: Order Packaging (CWE) 02067

FIXME

IVT-9: Issue Packaging (CWE) 02068

FIXME

IVT-10: Default Inventory Asset Account (EI) 02069

FIXME

IVT-11: Patient Chargeable Indicator (CNE) 02070

FIXME

IVT-12: Transaction Code (CWE) 00361

FIXME

IVT-13: Transaction Amount - Unit (CP) 00366

FIXME

IVT-14: Item Importance Code (CWE) 02073

FIXME

IVT-15: Stocked Item Indicator (CNE) 02074

FIXME

IVT-16: Consignment Item Indicator (CNE) 02075

FIXME

IVT-17: Reusable Item Indicator (CNE) 02076

FIXME

IVT-18: Reusable Cost (CP) 02077

FIXME

IVT-19: Substitute Item Identifier (EI) 02078

FIXME

IVT-20: Latex-Free Substitute Item Identifier (EI) 02079

FIXME

IVT-21: Recommended Reorder Theory (CWE) 02080

FIXME

IVT-22: Recommended Safety Stock Days (NM) 02081

FIXME

IVT-23: Recommended Maximum Days Inventory (NM) 02082

FIXME

IVT-24: Recommended Order Point (NM) 02083

FIXME

IVT-25: Recommended Order Amount (NM) 02084

FIXME

IVT-26: Operating Room Par Level Indicator (CNE) 02085

FIXME

ILT - Material Lot Segment

The Material Lot segment (ILT) contains material information specific to a lot within an inventory location associated with the item in the IVT segment. This segment is similar to the IIM segment used with the limited inventory item master message.

Note: Note that on-hand quantities do NOT refer to a continuously updated quantity. The expectation is for periodic physical inventory.

HL7 Attribute Table - ILT - Material Lot Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length	C.LEN	Flags
ILT
1	Set Id - ILT	SI	R		[1..1]	02086	[1..4]
2	Inventory Lot Number	ST	R		[1..1]	01800		250	#
3	Inventory Expiration Date	DTM	O		[0..1]	01801
4	Inventory Received Date	DTM	O		[0..1]	01804
5	Inventory Received Quantity	NM	O		[0..1]	01805		12	#
6	Inventory Received Quantity Unit	CWE	O	0818 Package	[0..1]	01806
7	Inventory Received Item Cost	MO	O		[0..1]	01807
8	Inventory On Hand Date	DTM	O		[0..1]	01808
9	Inventory On Hand Quantity	NM	O		[0..1]	01809		12	#
10	Inventory On Hand Quantity Unit	CWE	O	0818 Package	[0..1]	01810

ILT-1: Set Id - ILT (SI) 02086

FIXME

ILT-2: Inventory Lot Number (ST) 01800

FIXME

ILT-3: Inventory Expiration Date (DTM) 01801

FIXME

ILT-4: Inventory Received Date (DTM) 01804

FIXME

ILT-5: Inventory Received Quantity (NM) 01805

FIXME

ILT-6: Inventory Received Quantity Unit (CWE) 01806

FIXME

ILT-7: Inventory Received Item Cost (MO) 01807

FIXME

ILT-8: Inventory On Hand Date (DTM) 01808

FIXME

ILT-9: Inventory On Hand Quantity (NM) 01809

FIXME

ILT-10: Inventory On Hand Quantity Unit (CWE) 01810

FIXME

Placer Application Requests and Trigger Events

Placer request and filler response transactions are the messages and trigger events used between placer applications and filler applications. The placer application initiates transactions using the SLR, STI, SDR, or SMD message types, requesting information with the given trigger event message detail. The filler application responds to these requests, using the SLS, STS, SDS, or SMS message types, to either grant or deny the requests from the placer application.

When initiating a request, the placer application will generate and send a message type containing all of the information necessary to communicate the desired action to the filler application. All required segments and fields (both explicitly required and conditionally required) should be provided to the filler application, as defined in this chapter. When the filler application receives the transaction, it acknowledges it with the appropriate accept acknowledgment using an ACK message (assuming that the enhanced acknowledgment mode is in use).

After processing the request at the application level, the filler acknowledges the transaction with the appropriate application acknowledgment in a response message type (again assuming that an application acknowledgment was requested under the enhanced acknowledgment mode or that the original acknowledgment mode is in use). Applying the explanations of the various application acknowledgment codes in the context of this chapter, an application accept from the filler means that the request was processed and accepted by the filler.

An application error from the filler means that the request was processed and denied. An application reject from the filler means that the request was not, and could not be, processed due to one or more reasons unrelated to its content (for example, it fails the basic application protocol validation, the filler system is down, or there was an internal error).

There are no unsolicited messages initiated from a filler application defined in this set of trigger events. Those messages and trigger events are defined below, in section 17.6, "Filler Application Messages and Trigger Events Unsolicited."

All of the trigger events associated with placer request and filler response transactions use the message definitions that follow:

SLR/ACK/SLS - Request New Sterilization Lot (Event S28)

A placer application (Sterilizer) sends a transaction with this trigger event to a filler application (Instrument-tracking system) to request that a new sterilization lot be added. If it is successful, the filler application returns an application acknowledgment (if requested under the enhanced acknowledgment mode, or if the original acknowledgment mode is in use).

SLR^S28^SLR_S28: Request New Sterilization

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for SLR^S28^SLR_S28

Send Application Ack: SLS^S28^SLR_S28

Enhanced Mode Acknowledgement Choreography for SLR^S28^SLR_S28

When the MSH-15 value of a SLR^S28^SLR_S28 message is AL or ER or SU, an ACK^S28^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SLR^S28^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SLR^S28^SLR_S28 message is AL or ER or SU, a SLS^S28^SLR_S28 message SHALL be sent as an application ack.

When the MSH-16 value of a SLR^S28^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S28^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: SLS^S28^SLR_S28
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

SLS^S28^SLR_S28: Request New Sterilization

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for SLS^S28^SLR_S28

Send An Acknowlegment is never sent in original mode.

Enhanced Mode Acknowledgement Choreography for SLS^S28^SLR_S28

When the MSH-15 value of a SLS^S28^SLR_S28 message is AL or ER or SU, an ACK^S28^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SLS^S28^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SLS^S28^SLR_S28 message is AL or ER or SU, a message SHALL be sent as an application ack.

When the MSH-16 value of a SLS^S28^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S28^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack:
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

SLR/ACK/SLS - Request Sterilization Lot Deletion (Event S29)

A request sterilization lot deletion is sent by the placer application to the filler application to request that a lot that had been created in error be removed from the system. A delete trigger event differs from a cancel trigger event in that a delete acts to remove an error, whereas a cancel acts to prevent a valid request from occurring. If it is successful, an application acknowledgment is returned.

The delete trigger event should be implemented with careful forethought, as it typically has different effects and repercussions in various applications. In some applications, a delete event cannot be undone. This means that if a delete transaction was sent erroneously, recovery will be difficult or impossible. In other applications, a delete transaction will not result in the physical deletion of the record(s), but will set a status or a flag. In these cases, the filler and/or placer appointment identifiers (the numbers or codes that uniquely identify the sterilization lot or request to the placer and filler applications) probably cannot be reused. Since an application may maintain a record of deleted sterilization lots, the reuse of an identifier may cause a conflict in the applications' processing of transactions.

SLR^S29^SLR_S28: Request Sterilization Lot Deletion

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for SLR^S29^SLR_S28

Send Application Ack: SLS^S29^SLR_S28

Enhanced Mode Acknowledgement Choreography for SLR^S29^SLR_S28

When the MSH-15 value of a SLR^S29^SLR_S28 message is AL or ER or SU, an ACK^S29^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SLR^S29^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SLR^S29^SLR_S28 message is AL or ER or SU, a SLS^S29^SLR_S28 message SHALL be sent as an application ack.

When the MSH-16 value of a SLR^S29^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S29^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: SLS^S29^SLR_S28
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

SLS^S29^SLR_S28: Request New Sterilization

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for SLS^S29^SLR_S28

Send An Acknowlegment is never sent in original mode.

Enhanced Mode Acknowledgement Choreography for SLS^S29^SLR_S28

When the MSH-15 value of a SLS^S29^SLR_S28 message is AL or ER or SU, an ACK^S29^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SLS^S29^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SLS^S29^SLR_S28 message is AL or ER or SU, a message SHALL be sent as an application ack.

When the MSH-16 value of a SLS^S29^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S29^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack:
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

STI/ACK/STS - Request Item (Event S30)

A request item is sent by the placer application to the filler application to request the ID and description of an item to be sterilized or decontaminated. If it is successful, the filler application returns an application acknowledgment (if requested under the enhanced acknowledgment mode, or if the original acknowledgment mode is in use).

STI^S30^SLR_S28: Sterilization Item Request

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for STI^S30^SLR_S28

Send Application Ack: STS^S30^SLR_S28

Enhanced Mode Acknowledgement Choreography for STI^S30^SLR_S28

When the MSH-15 value of a STI^S30^SLR_S28 message is AL or ER or SU, an ACK^S30^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a STI^S30^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a STI^S30^SLR_S28 message is AL or ER or SU, a STS^S30^SLR_S28 message SHALL be sent as an application ack.

When the MSH-16 value of a STI^S30^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S30^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: STS^S30^SLR_S28
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

STS^S30^SLR_S28: Sterilization Item Request

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for STS^S30^SLR_S28

Send An Acknowlegment is never sent in original mode.

Enhanced Mode Acknowledgement Choreography for STS^S30^SLR_S28

When the MSH-15 value of a STS^S30^SLR_S28 message is AL or ER or SU, an ACK^S30^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a STS^S30^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a STS^S30^SLR_S28 message is AL or ER or SU, a message SHALL be sent as an application ack.

When the MSH-16 value of a STS^S30^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S30^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack:
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

SDR/ACK/SDS - Request Anti-Microbial Device Data (Event S31)

This trigger event is sent by the placer application to the filler application to request anti-microbial device data created during the decontamination/sterilization of medical supplies. In the context of this message segment, the term 'device' refers to a sterilizer or a washer. Sterilizers perform a sterilization process and washers perform a decontamination process.

SDR^S31^SDR_S31: Anti-Microbial Device Data Request

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SDR_S31
Segment	Cardinality	Must Implement	Status
SDR_S31
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
	1..1	Yes	additional
SDD	1..1	Yes	additional

SCD	0..*		additional

Original Mode Acknowledgement Choreography for SDR^S31^SDR_S31

Send Application Ack: SDS^S31^SDR_S31

Enhanced Mode Acknowledgement Choreography for SDR^S31^SDR_S31

When the MSH-15 value of a SDR^S31^SDR_S31 message is AL or ER or SU, an ACK^S31^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SDR^S31^SDR_S31 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SDR^S31^SDR_S31 message is AL or ER or SU, a SDS^S31^SDR_S31 message SHALL be sent as an application ack.

When the MSH-16 value of a SDR^S31^SDR_S31 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S31^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: SDS^S31^SDR_S31
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SDR_S31-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SDR_S31 -->
  <!-- .. message definition SDR_S31 -->
  <xsd:complexType name="SDR_S31.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA"
      minOccurs="1" maxOccurs="1" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SDR_S31" type="SDR_S31.CONTENT" />
  <xsd:complexType name="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA.CONTENT">

    <xsd:choice>
      <xsd:element ref="SDD" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SCD" minOccurs="0" maxOccurs="unbounded" />
    </xsd:choice>
  </xsd:complexType>
  <xsd:element name="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA"
  type="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA.CONTENT" />
</xsd:schema>

Download

SDS^S31^SDR_S31: Anti-Microbial Device Data Request

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SDR_S31
Segment	Cardinality	Must Implement	Status
SDR_S31
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
	1..1	Yes	additional
SDD	1..1	Yes	additional

SCD	0..*		additional

Original Mode Acknowledgement Choreography for SDS^S31^SDR_S31

Send An Acknowlegment is never sent in original mode.

Enhanced Mode Acknowledgement Choreography for SDS^S31^SDR_S31

When the MSH-15 value of a SDS^S31^SDR_S31 message is AL or ER or SU, an ACK^S31^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SDS^S31^SDR_S31 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SDS^S31^SDR_S31 message is AL or ER or SU, a message SHALL be sent as an application ack.

When the MSH-16 value of a SDS^S31^SDR_S31 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S31^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack:
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SDR_S31-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SDR_S31 -->
  <!-- .. message definition SDR_S31 -->
  <xsd:complexType name="SDR_S31.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA"
      minOccurs="1" maxOccurs="1" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SDR_S31" type="SDR_S31.CONTENT" />
  <xsd:complexType name="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA.CONTENT">

    <xsd:choice>
      <xsd:element ref="SDD" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SCD" minOccurs="0" maxOccurs="unbounded" />
    </xsd:choice>
  </xsd:complexType>
  <xsd:element name="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA"
  type="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA.CONTENT" />
</xsd:schema>

Download

SMD/ACK/SMS - Request Anti-Microbial Device Cycle Data (Event S32)

This trigger event is sent by the placer application to the filler application to request anti-microbial device cycle data created during the decontamination/sterilization of medical supplies. In the context of this message segment, the term 'device' refers to a sterilizer or a washer. Sterilizers perform a sterilization process and washers perform a decontamination process.

SMD^S32^SDR_S32: Anti-Microbial Device Cycle Data Request

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SDR_S31
Segment	Cardinality	Must Implement	Status
SDR_S31
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
	1..1	Yes	additional
SDD	1..1	Yes	additional

SCD	0..*		additional

Original Mode Acknowledgement Choreography for SMD^S32^SDR_S32

Send Application Ack: SMS^S32^SDR_S32

Enhanced Mode Acknowledgement Choreography for SMD^S32^SDR_S32

When the MSH-15 value of a SMD^S32^SDR_S32 message is AL or ER or SU, an ACK^S32^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SMD^S32^SDR_S32 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SMD^S32^SDR_S32 message is AL or ER or SU, a SMS^S32^SDR_S32 message SHALL be sent as an application ack.

When the MSH-16 value of a SMD^S32^SDR_S32 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S32^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: SMS^S32^SDR_S32
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SDR_S32-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SDR_S32 -->
  <!-- .. message definition SDR_S32 -->
  <xsd:complexType name="SDR_S32.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA"
      minOccurs="1" maxOccurs="1" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SDR_S32" type="SDR_S32.CONTENT" />
  <xsd:complexType name="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA.CONTENT">

    <xsd:choice>
      <xsd:element ref="SDD" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SCD" minOccurs="0" maxOccurs="unbounded" />
    </xsd:choice>
  </xsd:complexType>
  <xsd:element name="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA"
  type="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA.CONTENT" />
</xsd:schema>

Download

SMS^S32^SDR_S32: Anti-Microbial Device Cycle Data Request

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SDR_S31
Segment	Cardinality	Must Implement	Status
SDR_S31
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
	1..1	Yes	additional
SDD	1..1	Yes	additional

SCD	0..*		additional

Original Mode Acknowledgement Choreography for SMS^S32^SDR_S32

Send An Acknowlegment is never sent in original mode.

Enhanced Mode Acknowledgement Choreography for SMS^S32^SDR_S32

When the MSH-15 value of a SMS^S32^SDR_S32 message is AL or ER or SU, an ACK^S32^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SMS^S32^SDR_S32 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SMS^S32^SDR_S32 message is AL or ER or SU, a message SHALL be sent as an application ack.

When the MSH-16 value of a SMS^S32^SDR_S32 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S32^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack:
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SDR_S32-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SDR_S32 -->
  <!-- .. message definition SDR_S32 -->
  <xsd:complexType name="SDR_S32.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA"
      minOccurs="1" maxOccurs="1" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SDR_S32" type="SDR_S32.CONTENT" />
  <xsd:complexType name="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA.CONTENT">

    <xsd:choice>
      <xsd:element ref="SDD" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SCD" minOccurs="0" maxOccurs="unbounded" />
    </xsd:choice>
  </xsd:complexType>
  <xsd:element name="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA"
  type="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA.CONTENT" />
</xsd:schema>

Download

Filler Application Messages and Trigger Events Unsolicited

Unsolicited transactions from filler applications are the messages and trigger events used between filler applications and auxiliary applications. Transactions are initiated by the filler application, using the STC message to notify auxiliary applications of a sterilization configuration set. The auxiliary application responds to these notifications, using the ACK message, either to acknowledge receipt of the transaction, or to signal that an interfacing error of some kind has occurred.

As the discussion of application roles has indicated above, any one application can have more than one application role. If it is important that the application acting in the placer application role in your messaging environment be notified of unsolicited sterilization configurations, then it must also support the role of an auxiliary application.

When initiating a notification transaction, the filler application will generate and send an STC, SLN, SDN, or SCN message containing all of the information necessary to communicate the desired information to the auxiliary application. All required segments and fields (both explicitly required and conditionally required) should be provided by the filler application, as defined in this chapter. When the auxiliary application receives the transaction, it acknowledges with the appropriate accept acknowledgment using an ACK message (assuming that the enhanced acknowledgment mode is in use). After processing the notification at the application level, the auxiliary application acknowledges the transaction with the appropriate application acknowledgment in an ACK message (assuming that an application acknowledgment was requested under the enhanced acknowledgment mode or that the original acknowledgment mode is in use). Applying the explanations of the various application acknowledgment codes (detailed in Chapter 2) in the context of this chapter, an application accept from the auxiliary application means that the notification was processed and accepted. An application error from the auxiliary application means that the auxiliary application was unable to process the notification at the application level. An application reject from the auxiliary application means that the request was not, and could not be, processed due to one or more reasons unrelated to its content (for example, it fails the basic application protocol validation, the system is down, or there was an internal error).

STC/ACK - Notification of Sterilization Configuration (Event S33)

This message is sent from a filler application to notify other applications of a new sterilization configuration. The information in the STC segment describes the detail of the new sterilization configuration.

STC^S33^STC_S33: Sterilization Configuration Notification

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - STC_S33
Segment	Cardinality	Must Implement	Status
STC_S33
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SCP	1..*	Yes	additional

Original Mode Acknowledgement Choreography for STC^S33^STC_S33

Send Application Ack: ACK^S33^ACK

Enhanced Mode Acknowledgement Choreography for STC^S33^STC_S33

When the MSH-15 value of a STC^S33^STC_S33 message is AL or ER or SU, an ACK^S33^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a STC^S33^STC_S33 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a STC^S33^STC_S33 message is AL or ER or SU, an ACK^S33^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a STC^S33^STC_S33 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S33^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^S33^ACK
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: STC_S33-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE STC_S33 -->
  <!-- .. message definition STC_S33 -->
  <xsd:complexType name="STC_S33.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SCP" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="STC_S33" type="STC_S33.CONTENT" />
</xsd:schema>

Download

SLN/ACK - Notification of New Sterilization Lot (Event S34)

This message is sent from a filler application to notify other applications that a new sterilization lot has been created. The information provided in the SLT segment describes the new sterilization lot that has been created by the filler application.

SLN^S34^SLR_S28: Notification of New Sterilization Lot

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for SLN^S34^SLR_S28

Send Application Ack: ACK^S34^ACK

Enhanced Mode Acknowledgement Choreography for SLN^S34^SLR_S28

When the MSH-15 value of a SLN^S34^SLR_S28 message is AL or ER or SU, an ACK^S34^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SLN^S34^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SLN^S34^SLR_S28 message is AL or ER or SU, an ACK^S34^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a SLN^S34^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S34^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^S34^ACK
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

SLN/ACK - Notification of Sterilization Lot Deletion (Event S35)

This message is sent from a filler application to notify other applications that a sterilization lot has been deleted. The information provided in the SLT segment describes the sterilization lot that has been deleted by the filler application.

SLN^S35^SLR_S28: Notification of Sterilization Lot Deletion

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SLR_S28
Segment	Cardinality	Must Implement	Status
SLR_S28
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
SLT	1..*	Yes	additional

Original Mode Acknowledgement Choreography for SLN^S35^SLR_S28

Send Application Ack: ACK^S35^ACK

Enhanced Mode Acknowledgement Choreography for SLN^S35^SLR_S28

When the MSH-15 value of a SLN^S35^SLR_S28 message is AL or ER or SU, an ACK^S35^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SLN^S35^SLR_S28 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SLN^S35^SLR_S28 message is AL or ER or SU, an ACK^S35^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a SLN^S35^SLR_S28 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S35^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^S35^ACK
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SLR_S28-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SLR_S28 -->
  <!-- .. message definition SLR_S28 -->
  <xsd:complexType name="SLR_S28.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SLT" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SLR_S28" type="SLR_S28.CONTENT" />
</xsd:schema>

Download

SDN/ACK - Notification of Anti-Microbial Device Data (Event S36)

This message is sent from a filler application to notify other applications that anti-microbial device data has been generated. The information in the SDN segment and the other detail segments as appropriate describe the detail of a device during a sterilization or decontamination cycle.

SDN^S36^SDR_S31: Anti-Microbial Device Data Notification

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SDR_S31
Segment	Cardinality	Must Implement	Status
SDR_S31
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
	1..1	Yes	additional
SDD	1..1	Yes	additional

SCD	0..*		additional

Original Mode Acknowledgement Choreography for SDN^S36^SDR_S31

Send Application Ack: ACK^S36^ACK

Enhanced Mode Acknowledgement Choreography for SDN^S36^SDR_S31

When the MSH-15 value of a SDN^S36^SDR_S31 message is AL or ER or SU, an ACK^S36^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SDN^S36^SDR_S31 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SDN^S36^SDR_S31 message is AL or ER or SU, an ACK^S36^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a SDN^S36^SDR_S31 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S36^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^S36^ACK
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SDR_S31-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SDR_S31 -->
  <!-- .. message definition SDR_S31 -->
  <xsd:complexType name="SDR_S31.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA"
      minOccurs="1" maxOccurs="1" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SDR_S31" type="SDR_S31.CONTENT" />
  <xsd:complexType name="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA.CONTENT">

    <xsd:choice>
      <xsd:element ref="SDD" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SCD" minOccurs="0" maxOccurs="unbounded" />
    </xsd:choice>
  </xsd:complexType>
  <xsd:element name="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA"
  type="SDR_S31.ANTI-MICROBIAL_DEVICE_DATA.CONTENT" />
</xsd:schema>

Download

SCN/ACK - Notification of Anti-Microbial Device Cycle Data (Event S37)

This message is sent from a filler application to notify other applications that anti-microbial device cycle data has been generated. The information in the SCN segment and the other detail segments as appropriate describe details of a sterilization or decontamination cycle.

SCN^S37^SDR_S32: Anti-Microbial Device Cycle Data Notification

Message Structure
Acknowlegment Choreography
v2.xml XSD

HL7 MessageStructure Table - SDR_S31
Segment	Cardinality	Must Implement	Status
SDR_S31
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
	1..1	Yes	additional
SDD	1..1	Yes	additional

SCD	0..*		additional

Original Mode Acknowledgement Choreography for SCN^S37^SDR_S32

Send Application Ack: ACK^S37^ACK

Enhanced Mode Acknowledgement Choreography for SCN^S37^SDR_S32

When the MSH-15 value of a SCN^S37^SDR_S32 message is AL or ER or SU, an ACK^S37^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SCN^S37^SDR_S32 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SCN^S37^SDR_S32 message is AL or ER or SU, an ACK^S37^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a SCN^S37^SDR_S32 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^S37^ACK
MSH-15	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^S37^ACK
MSH-16	NE, AL, ER, SU	(none)

<?xml version="1.0"?>
<!--   v2.xml Message Definitions for Version 2.8.2 - here: SDR_S32-->
<!--   Copyright (c) 1999-2019, Health Level Seven. All rights reserved.   -->
<!--   (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml"
targetNamespace="urn:hl7-org:v2xml" version="1.1">
  <!-- import segment definition for version -->
  <xsd:include schemaLocation="segments.xsd" />
  <!-- MESSAGE SDR_S32 -->
  <!-- .. message definition SDR_S32 -->
  <xsd:complexType name="SDR_S32.CONTENT">
    <xsd:sequence>
      <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" />
      <xsd:element ref="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA"
      minOccurs="1" maxOccurs="1" />
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SDR_S32" type="SDR_S32.CONTENT" />
  <xsd:complexType name="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA.CONTENT">

    <xsd:choice>
      <xsd:element ref="SDD" minOccurs="1" maxOccurs="1" />
      <xsd:element ref="SCD" minOccurs="0" maxOccurs="unbounded" />
    </xsd:choice>
  </xsd:complexType>
  <xsd:element name="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA"
  type="SDR_S32.ANTI-MICROBIAL_DEVICE_CYCLE_DATA.CONTENT" />
</xsd:schema>

Download

Sterilization and Decontamination Message segments

SCP - Sterilizer Configuration Segment

The sterilization configuration segment contains information specific to configuration of a sterilizer or washer for processing sterilization or decontamination loads.

HL7 Attribute Table - SCP - Sterilizer Configuration Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	C.LEN	Flags
SCP
1	Number Of Decontamination/Sterilization Devices	NM	O		[0..1]	02087	2	#
2	Labor Calculation Type	CWE	O	0651 Labor Calculation Type	[0..1]	02088
3	Date Format	CWE	O	0653(S) Date Format(Suggested)	[0..1]	02089
4	Device Number	EI	O		[0..1]	02090
5	Device Name	ST	O		[0..1]	02279	999	#
6	Device Model Name	ST	O		[0..1]	02091	2	#
7	Device Type	CWE	O	0657 Device Type	[0..1]	02092
8	Lot Control	CWE	O	0659 Lot Control	[0..1]	02093

SCP-1: Number Of Decontamination/Sterilization Devices (NM) 02087

FIXME

SCP-2: Labor Calculation Type (CWE) 02088

FIXME

SCP-3: Date Format (CWE) 02089

FIXME

SCP-4: Device Number (EI) 02090

FIXME

SCP-5: Device Name (ST) 02279

FIXME

SCP-6: Device Model Name (ST) 02091

FIXME

SCP-7: Device Type (CWE) 02092

FIXME

SCP-8: Lot Control (CWE) 02093

FIXME

SLT - Sterilization Lot Segment

The SLT segment defines requests, responses, and notifications of sterilization lots and supply item descriptions. This message may be used for CPD (Central Supply) and OR (Sub-sterile area outside of an Operating Room) mode.

HL7 Attribute Table - SLT - Sterilization Lot Segment
Seq#	Data Element Name	DataType	Usage	Cardinality	Item #	C.LEN	Flags
SLT
1	Device Number	EI	O	[0..1]	02094
2	Device Name	ST	O	[0..1]	02280	999	#
3	Lot Number	EI	O	[0..1]	02095
4	Item Identifier	EI	O	[0..1]	02096
5	Bar Code	ST	O	[0..1]	02097	30	#

SLT-1: Device Number (EI) 02094

FIXME

SLT-2: Device Name (ST) 02280

FIXME

SLT-3: Lot Number (EI) 02095

FIXME

SLT-4: Item Identifier (EI) 02096

FIXME

SLT-5: Bar Code (ST) 02097

FIXME

SDD - Sterilization Device Data Segment

The SDD segment contains the attributes of an instance of a cycle that provides sterilization or decontamination of medical supplies.

HL7 Attribute Table - SDD - Sterilization Device Data Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	C.LEN	Flags
SDD
1	Lot Number	EI	O		[0..1]	02098
2	Device Number	EI	O		[0..1]	02099
3	Device Name	ST	O		[0..1]	02281	999	#
4	Device Data State	CWE	O	0667(S) Device Data State(Suggested)	[0..1]	02100
5	Load Status	CWE	O	0669(S) Load Status(Suggested)	[0..1]	02101
6	Control Code	NM	O		[0..1]	02102	3	#
7	Operator Name	ST	O		[0..1]	02103	15	#

SDD-1: Lot Number (EI) 02098

FIXME

SDD-2: Device Number (EI) 02099

FIXME

SDD-3: Device Name (ST) 02281

FIXME

SDD-4: Device Data State (CWE) 02100

FIXME

SDD-5: Load Status (CWE) 02101

FIXME

SDD-6: Control Code (NM) 02102

FIXME

SDD-7: Operator Name (ST) 02103

FIXME

SCD - Anti-Microbial Cycle Data Segment

The SCD segment contains cycle data representing an instance of a sterilization or decontamination.

HL7 Attribute Table - SCD - Anti-Microbial Cycle Data Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	C.LEN	Flags
SCD
1	Cycle Start Time	TM	O		[0..1]	02104
2	Cycle Count	NM	O		[0..1]	02105	16	#
3	Temp Max	CQ	O		[0..1]	02106
4	Temp Min	CQ	O		[0..1]	02107
5	Load Number	NM	O		[0..1]	02108	16	#
6	Condition Time	CQ	O		[0..1]	02109
7	Sterilize Time	CQ	O		[0..1]	02110
8	Exhaust Time	CQ	O		[0..1]	02111
9	Total Cycle Time	CQ	O		[0..1]	02112
10	Device Status	CWE	O	0682 Device Status	[0..1]	02113
11	Cycle Start Date/Time	DTM	O		[0..1]	02114
12	Dry Time	CQ	O		[0..1]	02115
13	Leak Rate	CQ	O		[0..1]	02116
14	Control Temperature	CQ	O		[0..1]	02117
15	Sterilizer Temperature	CQ	O		[0..1]	02118
16	Cycle Complete Time	TM	O		[0..1]	02119
17	Under Temperature	CQ	O		[0..1]	02120
18	Over Temperature	CQ	O		[0..1]	02121
19	Abort Cycle	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02122
20	Alarm	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02123
21	Long in Charge Phase	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02124
22	Long in Exhaust Phase	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02125
23	Long in Fast Exhaust Phase	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02126
24	Reset	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02127
25	Operator - Unload	XCN	O		[0..1]	02128
26	Door Open	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02129
27	Reading Failure	CNE	O	0532(R) Expanded Yes/no Indicator(Required)	[0..1]	02130
28	Cycle Type	CWE	O	0702 Cycle Type	[0..1]	02131
29	Thermal Rinse Time	CQ	O		[0..1]	02132
30	Wash Time	CQ	O		[0..1]	02133
31	Injection Rate	CQ	O		[0..1]	02134
32	Procedure Code	CNE	O		[0..1]	00393
33	Patient Identifier List	CX	O		[0..*]	00106
34	Attending Doctor	XCN	O	0010 Physician ID	[0..1]	00137
35	Dilution Factor	SN	O		[0..1]	01356
36	Fill Time	CQ	O		[0..1]	02139
37	Inlet Temperature	CQ	O		[0..1]	02140

SCD-1: Cycle Start Time (TM) 02104

FIXME

SCD-2: Cycle Count (NM) 02105

FIXME

SCD-3: Temp Max (CQ) 02106

FIXME

SCD-4: Temp Min (CQ) 02107

FIXME

SCD-5: Load Number (NM) 02108

FIXME

SCD-6: Condition Time (CQ) 02109

FIXME

SCD-7: Sterilize Time (CQ) 02110

FIXME

SCD-8: Exhaust Time (CQ) 02111

FIXME

SCD-9: Total Cycle Time (CQ) 02112

FIXME

SCD-10: Device Status (CWE) 02113

FIXME

SCD-11: Cycle Start Date/Time (DTM) 02114

FIXME

SCD-12: Dry Time (CQ) 02115

FIXME

SCD-13: Leak Rate (CQ) 02116

FIXME

SCD-14: Control Temperature (CQ) 02117

FIXME

SCD-15: Sterilizer Temperature (CQ) 02118

FIXME

SCD-16: Cycle Complete Time (TM) 02119

FIXME

SCD-17: Under Temperature (CQ) 02120

FIXME

SCD-18: Over Temperature (CQ) 02121

FIXME

SCD-19: Abort Cycle (CNE) 02122

FIXME

SCD-20: Alarm (CNE) 02123

FIXME

SCD-21: Long in Charge Phase (CNE) 02124

FIXME

SCD-22: Long in Exhaust Phase (CNE) 02125

FIXME

SCD-23: Long in Fast Exhaust Phase (CNE) 02126

FIXME

SCD-24: Reset (CNE) 02127

FIXME

SCD-25: Operator - Unload (XCN) 02128

FIXME

SCD-26: Door Open (CNE) 02129

FIXME

SCD-27: Reading Failure (CNE) 02130

FIXME

SCD-28: Cycle Type (CWE) 02131

FIXME

SCD-29: Thermal Rinse Time (CQ) 02132

FIXME

SCD-30: Wash Time (CQ) 02133

FIXME

SCD-31: Injection Rate (CQ) 02134

FIXME

SCD-32: Procedure Code (CNE) 00393

FIXME

SCD-33: Patient Identifier List (CX) 00106

FIXME

SCD-34: Attending Doctor (XCN) 00137

FIXME

SCD-35: Dilution Factor (SN) 01356

FIXME

SCD-36: Fill Time (CQ) 02139

FIXME

SCD-37: Inlet Temperature (CQ) 02140

FIXME

Material Management Segments

DEV - Device Segment

The Device segment identifies an instance or a type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc.

HL7 Attribute Table - DEV - Device Segment
Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length	C.LEN	Flags
DEV
1	Action Code	ID	R	0206(R) Segment Action Code(Required)	[1..1]	00816	[2..2]
2	Unique Device Identifier	EI	C		[0..1]	02457
3	Device Type	CNE	C	0961 Device Type	[0..*]	03483
4	Device Status	CNE	O	0962(S) Device Status(Suggested)	[0..*]	02501
5	Manufacturer/Distributor	XON	O		[0..1]	01247
6	Brand Name	ST	O		[0..1]	01249		60	#
7	Model Identifier	ST	O		[0..1]	01252		60	#
8	Catalogue Identifier	ST	O		[0..1]	01253		60	#
9	UDI Device Identifier	EI	O		[0..1]	03476
10	Device Lot Number	ST	O		[0..1]	03479
11	Device Serial Number	ST	O		[0..1]	03480
12	Device Manufacture Date	DTM	O		[0..1]	03477
13	Device Expiry Date	DTM	O		[0..1]	03478
14	Safety Characteristics	CWE	O	0963 Device Safety	[0..*]	02465
15	Device Donation Identification	EI	O		[0..1]	03481
16	Software Version Number	ST	O		[0..1]	02502
17	Implantation Status	CNE	O	0795	[0..1]	02459

DEV-1: Action Code (ID) 00816

FIXME

DEV-2: Unique Device Identifier (EI) 02457

FIXME

DEV-3: Device Type (CNE) 03483

FIXME

DEV-4: Device Status (CNE) 02501

FIXME

DEV-5: Manufacturer/Distributor (XON) 01247

FIXME

DEV-6: Brand Name (ST) 01249

FIXME

DEV-7: Model Identifier (ST) 01252

FIXME

DEV-8: Catalogue Identifier (ST) 01253

FIXME

DEV-9: UDI Device Identifier (EI) 03476

FIXME

DEV-10: Device Lot Number (ST) 03479

FIXME

DEV-11: Device Serial Number (ST) 03480

FIXME

DEV-12: Device Manufacture Date (DTM) 03477

FIXME

DEV-13: Device Expiry Date (DTM) 03478

FIXME

DEV-14: Safety Characteristics (CWE) 02465

FIXME

DEV-15: Device Donation Identification (EI) 03481

FIXME

DEV-16: Software Version Number (ST) 02502

FIXME

DEV-17: Implantation Status (CNE) 02459

FIXME

Example Transactions

Inventory Item Master Catalog Add - Event M16

An inventory clerk in the General Supply Inventory location has added a new supply item to the item master catalog. A Master File Add message is sent (MAD) to notify selected inventory locations that this supply item has been added to the item master catalog

MSH|^~VALUEamp;|MATERIALSYS|FACA|INVSYS|CENSUPPLY|200408150900||MFN^M16^MFN_M16|090849SUPITM|P|2.9|||AL|AL|||

MFI|INV|MATERIALSYS|UPD|200408121100|SU|

MFE|MAD|F589|200408121100|JMC090387^^JMFcr>

SFT|COMPAPP|9.0.0|MATIERALSYS|4500|200401010700|

UAC| KERB|MATSYS|AP|Octet-stream|A|Clerk|

ITM|10001|Formula 8oz|A|SUP|DietaryFormula|Y|ALR|MANUFACTURER|F589|ALR900||Y|300-0001^FormulaAlim_8oz|4.92|Y||FDA|N||100-9088-37887|20|29.75|N|N|N||||REF|

VND|001|M00933|VENDOR|FV9975|Y|

VND|002|M00934|VENDOR2|FV9976|N|

PKG|001|CS|6|Y|5|29.50|30.25|200409030100|

PKG|002|EA|N|1|4.92|5.04|200409030100|

PCE|001|9188|300-0002|5.35|

ITV|001|GS^General Stores|CS^Central Supply|1|GS-031|CS|EA|100-9200-00000|Y|300-0001|4.95||Y|N|N||||M|30|450|100|400|N|

MSH|^~VALUEamp;|MATERIALSYS|FACA|INVSYS|CENSUPPLY|200408150900||MFN^M16^MFN_M16|090849SUPITM|P|2.9|||AL|AL|||

MSA|CA|8000|||||

Request New Sterilization Lot - Event S28

The sterilizer operator is preparing to run a flash sterilizer load. The sterilizer requests a lot number from the instrument-tracking system to assign to the load.

MSH|^~VALUEamp;|Sterila|FacilB|Instrutrak|FacilA|200410010800||SLR^S28 SLR_S28|021244STER|P|2.9|||AL|AL||||||

SFT|Hospital A|9.0|Sterila|10101010|9.0 999|New Load|200402140900|

UAC|KERB|MATSYS|AP|Octet-stream|A|Clerk|

SLT|87995|DEVICE NAME|A46|LF4|1435567677

MSH|^~VALUEamp;|Sterila|FacilB|Instrutrak|FacilA|200410010800||ACK^S28^ACK|021244STER|P|2.9|||NE|NE||||||

MSA|CA|021244STER||||

MSH|^~VALUEamp;|Instrutrak|FacilB|Sterila|FacilA|2004010010801||SLS^S28 SLR_S28|021244STER|P|2.9|||AL|NE|||||

SFT|Hospital A|9.0|Sterila|10101010|9.0 999|New Load|200402140900|

UAC|KERB|MATSYS|AP|Octet-stream|A|Admin|

SLT|01||||

MSH|^~VALUEamp;|Instrutrak|FacilB|Sterila|FacilA|2004010010801||SLS^S28|021244STER|P|2.9|||NE|NE||||||

MSA|CA|021244STER||||

Implementation Considerations

None

OUtstanding Issues

None

Draft Website - For Review Purposes Only

Materials Management

PURPOSE

Inventory Item Master Updates

Item Master Catalog

Inventory Locations

Sterilization and Decontamination

Application roles

Trigger Events

Statuses

Glossary

Bowie-Dick Test

Catalog Item

Cycle - Sterilization

Cycle - Steam Sterilization, Gravity Displacement Type

Cycle Time

Decontamination

Entrainment

EO

Exposure Time

Lot Control

Nonstocked Items

NonCatalog Item

Par Level

Sterile

Sterilization

Sterilizer

Stocked Items

TDC

Washer

Organization of This Chapter: Trigger Events and Message Definitions

Update mode

Inventory Item Master Messages Segments

IIM - Inventory Item Master Segment

IIM-1: Primary Key Value - IIM (CWE) 01897

IIM-2: Service Item Code (CWE) 01799

IIM-3: Inventory Lot Number (ST) 01800

IIM-4: Inventory Expiration Date (DTM) 01801

IIM-5: Inventory Manufacturer Name (CWE) 01802

IIM-6: Inventory Location (CWE) 01803

IIM-7: Inventory Received Date (DTM) 01804

IIM-8: Inventory Received Quantity (NM) 01805

IIM-9: Inventory Received Quantity Unit (CWE) 01806

IIM-10: Inventory Received Item Cost (MO) 01807

IIM-11: Inventory On Hand Date (DTM) 01808

IIM-12: Inventory On Hand Quantity (NM) 01809

IIM-13: Inventory On Hand Quantity Unit (CWE) 01810

IIM-14: Procedure Code (CNE) 00393

IIM-15: Procedure Code Modifier (CNE) 01316

ITM - Material Item Segment

ITM-1: Item Identifier (EI) 02186

ITM-2: Item Description (ST) 02274

ITM-3: Item Status (CWE) 02187

ITM-4: Item Type (CWE) 02188

ITM-5: Item Category (CWE) 02189

ITM-6: Subject to Expiration Indicator (CNE) 02190

ITM-7: Manufacturer Identifier (EI) 02191

ITM-8: Manufacturer Name (ST) 02275

ITM-9: Manufacturer Catalog Number (ST) 02192

ITM-10: Manufacturer Labeler Identification Code (CWE) 02193

ITM-11: Patient Chargeable Indicator (CNE) 02070

ITM-12: Transaction Code (CWE) 00361

ITM-13: Transaction Amount - Unit (CP) 00366

ITM-14: Stocked Item Indicator (CNE) 02197

ITM-15: Supply Risk Codes (CWE) 02266

ITM-16: Approving Regulatory Agency (XON) 02199

ITM-17: Latex Indicator (CNE) 02200

ITM-18: Ruling Act (CWE) 02201

ITM-19: Item Natural Account Code (CWE) 00282

ITM-20: Approved To Buy Quantity (NM) 02203

ITM-21: Approved To Buy Price (MO) 02204

ITM-22: Taxable Item Indicator (CNE) 02205

ITM-23: Freight Charge Indicator (CNE) 02206

ITM-24: Item Set Indicator (CNE) 02207

ITM-25: Item Set Identifier (EI) 02208

ITM-26: Track Department Usage Indicator (CNE) 02209

ITM-27: Procedure Code (CNE) 00393

ITM-28: Procedure Code Modifier (CNE) 01316

ITM-29: Special Handling Code (CWE) 01370

ITM-30: Hazardous Indicator (CNE) 03388