Besa HL7 2.x Help File

Getting Started

Units

Class Hierarchy

Classes, Interfaces, Objects and Records

Types

Variables

Constants

Functions and Procedures

Identifiers

Unit BSHL7DT26

DescriptionUsesClasses, Interfaces, Objects and RecordsFunctions and ProceduresTypesConstantsVariables

Description

HL7 2.6 Data Type definition

Overview

Classes, Interfaces, Objects and Records

Name Description
Class TbsAD_26 Address
Class TbsAUI_26 Authorization Information
Class TbsCCD_26 Charge Code and Date
Class TbsCCP_26 Channel Calibration Parameters
Class TbsCD_26 Channel Definition
Class TbsCE_26 Coded Element
Class TbsCF_26 Coded Element with Formatted Values
Class TbsCNE_26 Coded with No Exceptions
Class TbsCNN_26 Composite ID Number and Name Simplified
Class TbsCP_26 Composite Price
Class TbsCQ_26 Composite Quantity with Units
Class TbsCSU_26 Channel Sensitivity
Class TbsCWE_26 Coded with Exceptions
Class TbsCX_26 Extended Composite ID with Check Digit
Class TbsDDI_26 Daily Deductible Information
Class TbsDIN_26 Date and Institution Name
Class TbsDLD_26 Discharge Location and Date
Class TbsDLN_26 Driver_s License Number
Class TbsDLT_26 Delta
Class TbsDR_26 Date/Time Range
Class TbsDT_26  
Class TbsDTM_26  
Class TbsDTN_26 Day Type and Number
Class TbsED_26 Encapsulated Data
Class TbsEI_26 Entity Identifier
Class TbsEIP_26 Entity Identifier Pair
Class TbsELD_26 Error Location and Description
Class TbsERL_26 Error Location
Class TbsFC_26 Financial Class
Class TbsFN_26 Family Name
Class TbsFT_26  
Class TbsGTS_26  
Class TbsHD_26 Hierarchic Designator
Class TbsICD_26 Insurance Certification Definition
Class TbsID_26  
Class TbsIS_26  
Class TbsJCC_26 Job Code/Class
Class TbsLA1_26 Location with Address Variation 1
Class TbsLA2_26 Location with Address Variation 2
Class TbsMA_26 Multiplexed Array
Class TbsMO_26 Money
Class TbsMOC_26 Money and Code
Class TbsMOP_26 Money or Percentage
Class TbsMSG_26 Message Type
Class TbsNA_26 Numeric Array
Class TbsNDL_26 Name with Date and Location
Class TbsNM_26  
Class TbsNR_26 Numeric Range
Class TbsOCD_26 Occurrence Code and Date
Class TbsOSD_26 Order Sequence Definition
Class TbsOSP_26 Occurrence Span Code and Date
Class TbsPIP_26 Practitioner Institutional Privileges
Class TbsPL_26 Person Location
Class TbsPLN_26 Practitioner License or Other ID Number
Class TbsPPN_26 Performing Person Time Stamp
Class TbsPRL_26 Parent Result Link
Class TbsPT_26 Processing Type
Class TbsPTA_26 Policy Type and Amount
Class TbsQIP_26 Query Input Parameter List
Class TbsQSC_26 Query Selection Criteria
Class TbsRCD_26 Row Column Definition
Class TbsRFR_26 Reference Range
Class TbsRI_26 Repeat Interval
Class TbsRMC_26 Room Coverage
Class TbsRP_26 Reference Pointer
Class TbsRPT_26 Repeat Pattern
Class TbsSAD_26 Street Address
Class TbsSCV_26 Scheduling Class Value Pair
Class TbsSI_26  
Class TbsSN_26 Structured Numeric
Class TbsSPD_26 Specialty Description
Class TbsSPS_26 Specimen Source
Class TbsSRT_26 Sort Order
Class TbsST_26  
Class TbsTM_26  
Class TbsTQ_26 Timing Quantity
Class TbsTS_26 Time Stamp
Class TbsTX_26  
Class TbsUVC_26 UB Value Code and Amount
Class TbsVARIES_26  
Class TbsVH_26 Visiting Hours
Class TbsVID_26 Version Identifier
Class TbsVR_26 Value Range
Class TbsWVI_26 Channel Identifier
Class TbsWVS_26 Waveform Source
Class TbsXAD_26 Extended Address
Class TbsXCN_26 Extended Composite ID Number and Name for Persons
Class TbsXON_26 Extended Composite Name and Identification Number for Organizations
Class TbsXPN_26 Extended Person Name
Class TbsXTN_26 Extended Telecommunication Number
Class TbsABS_26 Abstract This segment was created to communicate patient abstract information used for billing and reimbursement purposes. “Abstract” is a condensed form of medical history created for analysis, care planning, etc.
Class TbsACC_26 Accident The ACC segment contains patient information relative to an accident in which the patient has been involved.
Class TbsADD_26 Addendum The ADD segment is used to define the continuation of the prior segment in a continuation message. See Section 2.10.2, " Continuation messages and segments ," for details.
Class TbsADJ_26 Adjustment This segment describes Provider and/or Payer adjustments to a Product/Service Line Item or Response Summary.  These include surcharges such as tax, dispensing fees and mark ups.
Class TbsAFF_26 Professional Affiliation The AFF segment adds detailed information regarding professional affiliations with which the staff member identified by the STF segment is/was associated.
Class TbsAIG_26 Appointment Information - General Resource The AIG segment contains information about various kinds of resources (other than those with specifically defined segments in this chapter) that can be scheduled.  Resources included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application.  Resources not controlled by a schedule are not identified on a schedule request using this segment.  Resources described by this segment are general kinds of resources, such as equipment, that are identified with a simple identification code.
Class TbsAIL_26 Appointment Information - Location Resource The AIL segment contains information about location resources (meeting rooms, operating rooms, examination rooms, or other locations) that can be scheduled.  Resources included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application.  Resources not controlled by a schedule are not identified on a schedule request using this segment.  Location resources are identified with this specific segment because of the specific encoding of locations used by the HL7 specification.
Class TbsAIP_26 Appointment Information - Personnel Resource The AIP segment contains information about the personnel types that can be scheduled.  Personnel included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application.  Personnel not controlled by a schedule are not identified on a schedule request using this segment.  The kinds of personnel described on this segment include any healthcare provider in the institution controlled by a schedule (for example: technicians, physicians, nurses, surgeons, anesthesiologists, or CRNAs).
Class TbsAIS_26 Appointment Information The AIS segment contains information about various kinds of services that can be scheduled.  Services included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application.  Services not controlled by a schedule are not identified on a schedule request using this segment.
Class TbsAL1_26 Patient Allergy Information The AL1 segment contains patient allergy information of various types.  Most of this information will be derived from user-defined tables.  Each AL1 segment describes a single patient allergy.
Class TbsAPR_26 Appointment Preferences The APR segment contains parameters and preference specifications used for requesting appointments in the SRM message.  It allows placer applications to provide coded parameters and preference indicators to the filler application, to help determine when a requested appointment should be scheduled.  An APR segment can be provided in conjunction with either the ARQ segment or any of the service and resource segments (AIG, AIS, AIP, and AIL).  If an APR segment appears in conjunction with an ARQ segment, its parameters and preference indicators pertain to the schedule request as a whole.  If the APR segment appears with any of the service and resource segments, then its parameters and preferences apply only to the immediately preceding service or resource.
Class TbsARQ_26 Appointment Request The ARQ segment defines a request for the booking of an appointment.  It is used in transactions sent from an application acting in the role of a placer.
Class TbsARV_26 Access Restrictions segment The ARV segment is used to communicate the requested/required type of access restrictions from system to system, at both the person/patient and the encounter/visit level.
Class TbsAUT_26 Authorization Information This segment represents an authorization or a pre-authorization for a referred procedure or requested service by the payor covering the patient's health care.
Class TbsBLC_26 Blood Code The BLC segment contains data necessary to communicate patient abstract blood information used for billing and reimbursement purposes.  This segment is repeating to report blood product codes and the associated blood units.
Class TbsBLG_26 Billing The BLG segment is used to provide billing information, on the ordered service, to the filling application.
Class TbsBPO_26 Blood product order Blood product order messages require additional information that is not available in other standard HL7 order messages.  Blood product order messages need to contain accompanying details regarding the blood product component, such as special processing requirements (e.g., irradiation and leukoreduction) and the amount of the blood product to be administered.
Class TbsBPX_26 Blood product dispense status In the processing of blood products, it is necessary for the transfusion service and the placer system to communicate information.  The status messages need to contain additional information regarding the blood products requested, such as the unique donation ID, product code, blood type, expiration date/time of the blood product, and current status of the product.    This segment is similar to an OBX segment, but contains additional attributes.
Class TbsBTX_26 Blood Product Transfusion/Disposition HL7 Attribute Table – BTX – Blood Product Transfusion/Disposition
Class TbsCDM_26 Charge Description Master The Technical Steward for the CDM segment is Financial Management.
Class TbsCER_26 Certificate Detail The CER segment adds detailed information regarding the formal authorizations to provide a service (e.g. licenses, certificates) held by the health professional identified by the STF segment.
Class TbsCM0_26 Clinical Study Master The Technical Steward for the CM0 segment is Orders and Observations.
Class TbsCM1_26 Clinical Study Phase Master The Technical Steward for the CM1 segment is Orders and Observations.
Class TbsCM2_26 Clinical Study Schedule Master The Technical Steward for the CM2 segment is Orders and Observations.
Class TbsCNS_26 Clear Notification The clear equipment notification segment contains the data necessary to allow the receiving equipment to clear any associated notifications.
Class TbsCON_26 Consent Segment The consent segment provides details about a specific consent by a patient or staff member.
Class TbsCSP_26 Clinical Study Phase The CSP segment contains information on a patient’s status for a particular phase of the study.  This segment is optional and is useful when a study has different evaluation intervals within it.  (See section 7.8.1, "HL7 Attribute Table – CSR – Clinical Study Registration," and section 7.6.1.2, "Phase of a clinical trial:.")  The CSP segment is implemented on a study-specific basis for messaging purposes.  The fact that the patient has entered a phase of the study that represents a certain treatment approach may need to be messaged to other systems, like pharmacy, nursing, or order entry.  It is also important to sponsors and data management centers for tracking patient progress through the study and monitoring the data schedule defined for each phase.  It may subsume OBR and OBX segments that follow it to indicate that these data describe the phase.
Class TbsCSR_26 Clinical Study Registration The CSR segment will contain fundamental administrative and regulatory information required to document a patient’s enrollment on a clinical trial.  This segment is all that is required if one needs to message another system that an enrollment has taken place, i.e., from clinical trials to pharmacy, accounting, or order entry systems.  The CSR segment may also be used to identify that OBR, OBX, RXA, and RXR segments that follow represent data applicable to the identified study.
Class TbsCSS_26 Clinical Study Data Schedule Segment The Clinical Study Data Schedule (CSS) segment is optional depending on whether messaging of study data needs to be linked to the scheduled data time points for the study.  (See Section 7.6.1.3, " Data schedule: .")  The CSS segment enables communication of data schedules and adherence that ranges from the basic to the elaborate.  Use of the segment must be planned for each implementation.  Each CSS segment will subsume observation and drug administration segments that follow, indicating that they satisfy this scheduled time point.
Class TbsCTD_26 Contact Data The CTD segment may identify any contact personnel associated with a patient referral message and its related transactions.  The CTD segment will be paired with a PRD segment.  The PRD segment contains data specifically focused on provider information in a referral.  While it is important in an inter-enterprise transaction to transmit specific information regarding the providers involved (referring and referred-to), it may also be important to identify the contact personnel associated with the given provider.  For example, a provider receiving a referral may need to know the office manager or the billing person at the institution of the provider who sent the referral.  This segment allows for multiple contact personnel to be associated with a single provider.
Class TbsCTI_26 Clinical Trial Identification The CTI segment is an optional segment that contains information to identify the clinical trial, phase and time point with which an order or result is associated.
Class TbsDB1_26 Disability The disability segment contains information related to the disability of a person.  This segment was created instead of adding disability attributes to each segment that contains a person (to which disability may apply).  This is an optional segment that can be used to send disability information about a person already defined by the Patient Administration Chapter.  The disabled person code and identifier allow for the association of the disability information to the person.
Class TbsDG1_26 Diagnosis The DG1 segment contains patient diagnosis information of various types, for example, admitting, primary, etc.  The DG1 segment is used to send multiple diagnoses (for example, for medical records encoding).  It is also used when the FT1-19 - Diagnosis Code - FT1 does not provide sufficient information for a billing system.  This diagnosis coding should be distinguished from the clinical problem segment used by caregivers to manage the patient (see Chapter 12, Patient Care).  Coding methodologies are also defined.
Class TbsDMI_26 DRG Master File Information Segment The Technical Steward for the DMI segment is Financial Management.
Class TbsDRG_26 Diagnosis Related Group The DRG segment contains diagnoses-related grouping information of various types.  The DRG segment is used to send the DRG information, for example, for billing and medical records encoding.
Class TbsDSC_26 Continuation Pointer The DSC segment is used in the continuation protocol.
Class TbsDSP_26 Display Data The DSP segment is used to contain data that has been preformatted by the sender for display.  The semantic content of the data is lost; the data is simply treated as lines of text.
Class TbsECD_26 Equipment Command The equipment command segment contains the information required to notify the receiving component what is to happen.
Class TbsECR_26 Equipment Command Response The equipment command response segment contains the receiving component's response to the previously received command.
Class TbsEDU_26 Educational Detail The EDU segment adds detailed educational information to the staff member identified by the STF segment.  An EDU segment may optionally follow an STF segment.  An EDU segment must always have been preceded by a corresponding STF segment.
Class TbsEQL_26 Embedded Query Language
Class TbsEQP_26 Equipment/log Service The equipment log/service segment is the data necessary to maintain an adequate audit trail of events that have occurred on a particular piece of equipment.
Class TbsEQU_26 Equipment Detail The equipment detail segment contains the data necessary to identify and maintain the equipment that is being used throughout the Laboratory Automation System.
Class TbsERQ_26 Event replay query
Class TbsERR_26 Error The ERR segment is used to add error comments to acknowledgment messages.
Class TbsEVN_26 Event Type The EVN segment is used to communicate necessary trigger event information to receiving applications.  Valid event types for all chapters are contained in HL7 Table 0003 - Event Type .
Class TbsFAC_26 Facility HL7 Attribute Table – FAC – Facility
Class TbsFT1_26 Financial Transaction The FT1 segment contains the detail data necessary to post charges, payments, adjustments, etc., to patient accounting records.
Class TbsGOL_26 Goal Detail The goal detail segment contains the data necessary to add, update, correct, and delete the goals for an individual.
Class TbsGP1_26 Grouping/Reimbursement - Visit These fields are used in grouping and reimbursement for CMS APCs. Please refer to the "Outpatient Prospective Payment System Final Rule" ("OPPS Final Rule") issued by CMS.
Class TbsGP2_26 Grouping/Reimbursement - Procedure Line Item This segment is used for items that pertain to each HCPC/CPT line item.
Class TbsGT1_26 Guarantor The GT1 segment contains guarantor (e.g., the person or the organization with financial responsibility for payment of a patient account) data for patient and insurance billing applications.
Class TbsIAM_26 Patient Adverse Reaction Information The IAM segment contains person/patient adverse reaction information of various types.  Most of this information will be derived from user-defined tables.  Each IAM segment describes a single person/patient adverse reaction.  This segment is used in lieu of the AL1 - Patient Allergy Information Segment to support action code/unique identifier mode update definition of repeating segments as defined in 2.10.4.2 in chapter 2, section 2.4.10, "Protocol for interpreting repeating segments or segment groups in an update Message."  The AL1 segment is used to support Snapshot mode update definition as defined in 2.10.4.1.
Class TbsIIM_26 Inventory Item Master 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.
Class TbsILT_26 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.
Class TbsIN1_26 Insurance The IN1 segment contains insurance policy coverage information necessary to produce properly pro-rated and patient and insurance bills.
Class TbsIN2_26 Insurance Additional Information The IN2 segment contains additional insurance policy coverage and benefit information necessary for proper billing and reimbursement. Fields used by this segment are defined by CMS or other regulatory agencies.
Class TbsIN3_26 Insurance Additional Information, Certification The IN3 segment contains additional insurance information for certifying the need for patient care.  Fields used by this segment are defined by CMS, or other regulatory agencies.
Class TbsINV_26 Inventory Detail The inventory detail segment is the data necessary to track the inventory of substances (e.g. reagent, tips, waste) on equipment.
Class TbsIPC_26 Imaging Procedure Control Segment The IPC segment contains information about tasks that need to be performed in order to fulfill the request for imaging service. The information includes location, type and instance identification of equipment (acquisition modality) and stages (procedure steps).
Class TbsIPR_26 Invoice Processing Results The Invoice Processing Results (IPR) segment provides summary information about an adjudicated Product/Service Group or Product/Service Line Item.
Class TbsISD_26 Interaction Status Detail The interaction detail segment contains information about the status of specific interaction (e.g., processing — see section Glossary) on the specific equipment.
Class TbsITM_26 Material Item The Material Item segment (ITM) contains information about inventory supply items (stocked or non-stocked).
Class TbsIVC_26 Invoice The Invoice segment is used for HealthCare Services Invoices and contains header style information for an invoice including invoice numbers, Provider Organization and Payer Organization identification.
Class TbsIVT_26 Material Location The Material Location segment (IVT) contains information specific to an inventory location for the inventory supply item in the Material Item (ITM) segment.
Class TbsLAN_26 Language Detail The LAN segment adds detailed language information to the staff member identified by the STF segment.  An LAN segment may optionally follow an STF segment.  An LAN segment must always have been preceded by a corresponding STF segment.
Class TbsLCC_26 Location Charge Code The Technical Steward for the LCC segment is PA.
Class TbsLCH_26 Location Characteristic The Technical Steward for the LCH segment is Patient Administration.
Class TbsLDP_26 Location Department The Technical Steward for the LDP segment is Patient Administration.
Class TbsLOC_26 Location Identification The Technical Steward for the LOC segment is Patient Administration.
Class TbsLRL_26 Location Relationship The Technical Steward for the LRL segment is Patient Administration.
Class TbsMFA_26 Master File Acknowledgment The Technical Steward for the MFA segment is Infrastructure and Messaging.
Class TbsMFE_26 Master File Entry The Technical Steward for the MFE segment is Infrastructure and Messaging.
Class TbsMFI_26 Master File Identification The Technical Steward for the MFI segment is Infrastructure and Messaging.
Class TbsMRG_26 Merge Patient Information The MRG segment provides receiving applications with information necessary to initiate the merging of patient data as well as groups of records.  It is intended that this segment be used throughout the Standard to allow the merging of registration, accounting, and clinical records within specific applications.
Class TbsMSA_26 Message Acknowledgment The MSA segment contains information sent while acknowledging another message.
Class TbsMSH_26 Message Header The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message.
Class TbsNCK_26 System Clock The NCK segment is used to allow the various applications on the network to synchronize their system clocks (system date and time).
Class TbsNDS_26  
Class TbsNK1_26 Next of Kin / Associated Parties The NK1 segment contains information about the patient's other related parties.  Any associated parties may be identified.  Utilizing NK1-1 - set ID, multiple NK1 segments can be sent to patient accounts.
Class TbsNPU_26 Bed Status Update The NPU segment allows the updating of census (bed status) data without sending patient-specific data.  An example might include changing the status of a bed from "housekeeping" to "unoccupied."
Class TbsNSC_26 Application Status Change The NSC segment is used to inform (NMR query response) or announce (NMD unsolicited update) the start-up, shut-down, and/or migration (to a different CPU or file-server/file-system) of a particular application.
Class TbsNST_26 Application control level statistics The NST segment allows application control-level statistical information to be passed between the various systems on the network.  Some fields in this segment refer to portions of lower level protocols; they contain information that can be used by application management applications monitoring the state of various network links.
Class TbsNTE_26 Notes and Comments The NTE segment is defined here for inclusion in messages defined in other chapters. It is commonly used for sending notes and comments.
Class TbsOBR_26 Observation Request General (taken from ASTM E1238)
Class TbsOBX_26 Observation/Result The OBX segment is used to transmit a single observation or observation fragment.  It represents the smallest indivisible unit of a report.  The OBX segment can also contain encapsulated data, e.g., a CDA document or a DICOM image.
Class TbsODS_26 Dietary Orders, Supplements, and Preferences The ORC sequence items of interest to ODS are ORC-1-order control, ORC-2-placer order number, ORC-3-filler order number, ORC-7-quantity/timing, ORC-9-date/time of transaction, ORC-10-entered by, and ORC-11-verified by.  For ORC-1-order control, the values may be New (NW), Cancel (CA), Discontinue Order Request (DC), Change (XO), Hold Order Request (HD), and Release Previous Hold (RL).  The HD and RL codes could stop service for a specified length of time.  ORC-7-quantity/timing should be used to specify whether an order is continuous or for one service period only.  It is also useful for supplements which are part of a diet but only delivered, say, every day at night.
Class TbsODT_26 Diet Tray Instructions This segment addresses tray instructions.  These are independent of diet codes, supplements, and preferences and therefore get separate order numbers.
Class TbsOM1_26 General Segment The Technical Steward for the OM1 segment is Orders and Observations.
Class TbsOM2_26 Numeric Observation The Technical Steward for the OM2 segment is Orders and Observations.
Class TbsOM3_26 Categorical Service/Test/Observation The Technical Steward for the OM3 segment is Orders and Observations.
Class TbsOM4_26 Observations that Require Specimens The Technical Steward for the OM4 segment is Orders and Observations.
Class TbsOM5_26  
Class TbsOM6_26 Observations that are Calculated from Other Observations The Technical Steward for the OM6 segment is Orders and Observations.
Class TbsOM7_26 Additional Basic Attributes The Technical Steward for the OM7 segment is Orders and Observations.
Class TbsORC_26 Common Order The Common Order segment (ORC) is used to transmit fields that are common to all orders (all types of services that are requested).
Class TbsORG_26 Practitioner Organization Unit The ORG segment relates a practitioner to an organization unit and adds detailed information regarding the practitioner's practicing specialty in that organization unit.  An ORG segment may optionally follow an STF segment.  An ORG segment must always have been preceded by a corresponding STF segment.  If no organization unit is specified, this segment is used to relate practitioners with their practicing specialties, including effective and end dates.  When it is not necessary to record organization unit or dates associated with the practicing specialty, this data is recorded in PRA-3-Practitioner Category.
Class TbsOVR_26 Override Segment Definition: This segment allows a sender to override specific receiving application's business rules to allow for processing of a message that would normally be rejected or ignored.
Class TbsPCE_26 Patient Charge Cost Center Exception 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.
Class TbsPCR_26 Possible Causal Relationship The PCR segment is used to communicate a potential or suspected relationship between a product (drug or device) or test and an event with detrimental effect on a patient.  This segment identifies a potential causal relationship between the product identified in this segment and the event identified in the PEO segment.
Class TbsPD1_26 Patient Additional Demographic The patient additional demographic segment contains demographic information that is likely to change about the patient.
Class TbsPDA_26 Patient Death and Autopsy This segment carries information on a patient's death and possible autopsy.
Class TbsPDC_26 Product Detail Country HL7 Attribute Table – PDC – Product Detail Country
Class TbsPEO_26 Product Experience Observation Details related to a particular clinical experience or event are embodied in the PEO segment.  This segment can be used to characterize an event which might be attributed to a product to which the patient was exposed.   Products with a possible causal relationship to the observed experience are described in the following PCR (possible causal relationship) segments.  The message format was designed to be robust and includes many optional elements which may not be required for a particular regulatory purpose but allow a complete representation of the drug experience if needed.
Class TbsPES_26 Product Experience Sender HL7 Attribute Table - PES – Product Experience Sender
Class TbsPID_26 Patient Identification The PID segment is used by all applications as the primary means of communicating patient identification information.  This segment contains permanent patient identifying and demographic information that, for the most part, is not likely to change frequently.
Class TbsPKG_26 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.
Class TbsPMT_26 Payment Information This segment contains information that describes a payment made by a Payer organization.
Class TbsPR1_26 Procedures The PR1 segment contains information relative to various types of procedures that can be performed on a patient.  The PR1 segment can be used to send procedure information, for example: Surgical, Nuclear Medicine, X-ray with contrast, etc.  The PR1 segment is used to send multiple procedures, for example, for medical records encoding or for billing systems.
Class TbsPRA_26 Practitioner Detail The Technical Steward for the PRA segment is PA and Personnel Management.
Class TbsPRB_26 Problem Details The problem detail segment contains the data necessary to add, update, correct, and delete the problems of a given individual.
Class TbsPRC_26 Pricing The Technical Steward for the PRC segment is Financial Management.
Class TbsPRD_26 Provider Data This segment will be employed as part of a patient referral message and its related transactions.  The PRD segment contains data specifically focused on a referral, and it is inter-enterprise in nature.  The justification for this new segment comes from the fact that we are dealing with referrals that are external to the facilities that received them.  Therefore, using a segment such as the current PV1 would be inadequate for all the return information that may be required by the receiving facility or application.  In addition, the PV1 does not always provide information sufficient to enable the external facility to make a complete identification of the referring entity.  The information contained in the PRD segment will include the referring provider, the referred-to provider, the referred-to location or service, and the referring provider clinic address.
Class TbsPSG_26 Product/Service Group The Product/Service Group segment is used to form a logical grouping of Product/Service Line Items, Patients and Response Summaries for a particular Invoice.  For example, a Product/Service Group can be used to group all Product/Service Line Items that must be adjudicated as a group in order to be paid.
Class TbsPSH_26 Product Summary Header HL7 Attribute Table – PSH –Product Summary Header
Class TbsPSL_26 Product/Service Line Item The Product/Service Line Item segment is used to identify individual product/service items that typically are aggregated into an Invoice.  Each instance of a Product/Service Line Item corresponds to a unique product delivered or service rendered.
Class TbsPSS_26 Product/Service Section The Product/Service Section segment is used to form a logical grouping of Product/Service Group segments, Patients and Response Summaries for a particular Invoice.
Class TbsPTH_26 Pathway The pathway segment contains the data necessary to add, update, correct, and delete from the record pathways that are utilized to address an individual's health care.
Class TbsPV1_26 Patient Visit The PV1 segment is used by Registration/Patient Administration applications to communicate information on an account or visit-specific basis.  The default is to send account level data. To use this segment for visit level data PV1-51 - Visit Indicator must be valued to "V". The value of PV-51 affects the level of data being sent on the PV1, PV2, and any other segments that are part of the associated PV1 hierarchy (e.g., ROL, DG1, or OBX).
Class TbsPV2_26 Patient Visit - Additional Information The PV2 segment is a continuation of information contained on the PV1 segment.
Class TbsPYE_26 Payee Information This segment is used to define payee information.
Class TbsQAK_26 Query Acknowledgment The QAK segment contains information sent with responses to a query.  Although the QAK segment is required in the responses to the enhanced queries (see section Error! Reference source not found. , "Error! Reference source not found."), it may appear as an optional segment placed after the (optional) ERR segment in any query response (message) to any original mode query.
Class TbsQID_26 Query Identification The QID segment contains the information necessary to uniquely identify a query. Its primary use is in query cancellation or subscription cancellation.
Class TbsQPD_26 Query Parameter Definition The QPD segment defines the parameters of the query.
Class TbsQRD_26 Original-Style Query Definition
Class TbsQRF_26 Original style query filter
Class TbsQRI_26 Query Response Instance The QRI segment is used to indicate the weight match for a returned record (where the responding system employs a numeric algorithm) and/or the match reason code (where the responding system uses rules or other match options).
Class TbsRCP_26 Response Control Parameter The RCP segment is used to restrict the amount of data that should be returned in response to query.
Class TbsRDF_26 Table Row Definition The RDF segment defines the content of the row data segments (RDT) in the tabular response (RTB).
Class TbsRDT_26 Table Row Data The RDT segment contains the row data of the tabular data response message (TBR).
Class TbsREL_26 Clinical Relationship The Clinical Relationship segment contains the data necessary to relate two data elements within and/or external to the message at run-time. It also includes information about the relationship.
Class TbsRF1_26 Referral Information This segment represents information that may be useful when sending referrals from the referring provider to the referred-to provider.
Class TbsRFI_26 Request for Information HL7 Attribute Table – RFI – Request for Information
Class TbsRGS_26 Resource Group The RGS segment is used to identify relationships between resources identified for a scheduled event.  This segment can be used, on a site specified basis, to identify groups of resources that are used together within a scheduled event, or to describe some other relationship between resources.  To specify related groups of resources within a message, begin each group with an RGS segment, and then follow that RGS with one or more of the Appointment Information segments (AIG, AIL, AIS, or AIP).
Class TbsRMI_26 Risk Management Incident The RMI segment is used to report an occurrence of an incident event pertaining or attaching to a patient encounter.
Class TbsROL_26 Role The role segment contains the data necessary to add, update, correct, and delete from the record persons involved, as well as their functional involvement with the activity being transmitted.
Class TbsRQ1_26 Requisition Detail-1 RQ1 contains additional detail for each non-stock requisitioned item.  This segment definition is paired with a preceding RQD segment.
Class TbsRQD_26 Requisition Detail RQD contains the detail for each requisitioned item.  See assumptions above.
Class TbsRXA_26 Pharmacy/Treatment Administration The ORC must have the filler order number and the order control code RE.  As a site-specific variant, the RXO and associated RXCs and/or the RXE (and associated RXCs) may be present if the receiving application needs any of their data.  The RXA carries the administration data.
Class TbsRXC_26 Pharmacy/Treatment Component Order If the drug or treatment ordered with the RXO segment is a compound drug OR an IV solution, AND there is not a coded value for OBR-4-universal service ID , which specifies the components (base and all additives), then the components (the base and additives) are specified by two or more RXC segments.  The policy of the pharmacy or treatment application on substitutions at the RXC level is identical to that for the RXO level.
Class TbsRXD_26 Pharmacy/Treatment Dispense HL7 Attribute Table – RXD – Pharmacy/Treatment Dispense
Class TbsRXE_26 Pharmacy/Treatment Encoded Order The RXE segment details the pharmacy or treatment application's encoding of the order.  It also contains several pharmacy-specific order status fields, such as RXE-16-number of refills remaining , RXE-17-number of refills/doses dispensed, RXE-18-D/T of most recent refill or dose dispensed , and RXE-19-total daily dose.
Class TbsRXG_26 Pharmacy/Treatment Give HL7 Attribute Table – RXG – Pharmacy/Treatment Give
Class TbsRXO_26 Pharmacy/Treatment Order This is the "master" pharmacy/treatment order segment.  It contains order data not specific to components or additives.  Unlike the OBR, it does not contain status fields or other data that are results-only.
Class TbsRXR_26 Pharmacy/Treatment Route The Pharmacy/Treatment Route segment contains the alternative combination of route, site, administration device, and administration method that are prescribed as they apply to a particular order.  The pharmacy, treatment staff and/or nursing staff has a choice between the routes based on either their professional judgment or administration instructions provided by the physician.
Class TbsSAC_26 Specimen Container detail The container detail segment is the data necessary to maintain the containers that are being used throughout the Laboratory Automation System.
Class TbsSCD_26 Anti-Microbial Cycle Data The SCD segment contains cycle data representing an instance of a sterilization or decontamination.
Class TbsSCH_26 Scheduling Activity Information The SCH segment contains general information about the scheduled appointment.
Class TbsSCP_26 Sterilizer Configuration The sterilization configuration segment contains information specific to configuration of a sterilizer or washer for processing sterilization or decontamination loads.
Class TbsSDD_26 Sterilization Device Data The SDD segment contains the attributes of an instance of a cycle that provides sterilization or decontamination of medical supplies.
Class TbsSFT_26 Software Segment This segment provides additional information about the software product(s) used as a Sending Application. The primary purpose of this segment is for diagnostic use. There may be additional uses per site-specific agreements.
Class TbsSID_26 Substance Identifier The Substance Identifier segment contains data necessary to identify the substance (e.g., reagents) used in the production of analytical test results. The combination of these fields must uniquely identify the substance, i.e., depending on the manufacturer all or some fields are required (this is the reason the optionality is 'C' (conditional)). If the analysis requires multiple substances, this segment is repeated for each substance. The segment(s) should be attached to the TCD segment.
Class TbsSLT_26 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.
Class TbsSPM_26 Specimen The intent of this segment is to describe the characteristics of a specimen. It differs from the intent of the OBR in that the OBR addresses order-specific information. It differs from the SAC segment in that the SAC addresses specimen container attributes.  An advantage afforded by a separate specimen segment is that it generalizes the multiple relationships among order(s), results, specimen(s) and specimen container(s).
Class TbsSPR_26 Stored Procedure Request Definition
Class TbsSTF_26 Staff Identification The Technical Steward for the STF segment is PA and Personnel Management.
Class TbsSTZ_26 Sterilization Parameter The STZ segment contains sterilization-specific attributes of a supply item.
Class TbsTCC_26 Test Code Configuration The test (e.g., analyte) code configuration segment is the data necessary to maintain and transmit information concerning the test entity codes that are being used throughout the "automated system."
Class TbsTCD_26 Test Code Detail The test code detail segment contains the data necessary to perform operations or calculations, or execute decisions by the laboratory automation system, and which are not supported by the original HL7 segments related to orders (ORC, OBR). For detail of use see messages of laboratory orders and observations in chapters 4 and 7.
Class TbsTQ1_26 Timing/Quantity The TQ1 segment is used to specify the complex timing of events and actions such as those that occur in order management and scheduling systems. This segment determines the quantity, frequency, priority and timing of a service.  By allowing the segment to repeat, it is possible to have service requests that vary the quantity, frequency and priority of a service request over time.
Class TbsTQ2_26 Timing/Quantity Relationship The TQ2 segment is used to form a relationship between the service request the TQ1/TQ2 segments are associated with, and other service requests.  The TQ2 segment will link the current service request with one or more other service requests.
Class TbsTXA_26 Transcription Document Header The TXA segment contains information specific to a transcribed document but does not include the text of the document.  The message is created as a result of a document status change.  This information updates other healthcare systems and allows them to identify reports that are available in the transcription system. By maintaining the TXA message information in these systems, the information is available when constructing queries to the transcription system requesting the full document text.
Class TbsUAC_26 User Authentication Credential This optional segment provides user authentication credentials, a Kerberos Service Ticket or SAML assertion, to be used by the receiving system to obtain user identification data. Refer to HL7 Table 0615 - User Authentication Credential Type Code . It is to be used in when the receiving application system requires the sending system to provide end-user identification for accountability or access control in interactive applications. Since user authentication implementations often limit the time period for validity of the session authentication credentials, this segment is not intended for use in non-interactive applications.
Class TbsUB1_26 UB82 The UB1 segment contains data  specific to the United States; other realms may choose to implement using regional code sets.  Only billing/claims fields that do not exist in other HL7 defined segments appear in this segment.  The codes listed as examples are not an exhaustive or current list.
Class TbsUB2_26 UB92 Data The UB2 segment contains data necessary to complete UB92 bills specific to the United States; other realms may choose to implement using regional code sets.  Only UB92 fields that do not exist in other HL7 defined segments appear in this segment.   For example, Patient Name and Date of Birth are required; they are included in the PID segment and therefore do not appear here.  UB92 field locators are provided in parentheses (  ).  The UB codes listed as examples are not an exhaustive or current list; refer to a UB specification for additional information.
Class TbsURD_26 Results/update Definition
Class TbsURS_26 Unsolicited Selection
Class TbsVAR_26 Variance The variance segment contains the data necessary to describe differences that may have occurred at the time when a healthcare event was documented.
Class TbsVND_26 Purchasing Vendor This segment contains purchasing vendors that supply the inventory supply item specified in the ITM segment.
Class TbsVTQ_26 Virtual Table Query Request
Generated by PasDoc 0.14.0.