Besa HL7 2.x Help File

Getting Started

Units

Class Hierarchy

Classes, Interfaces, Objects and Records

Types

Variables

Constants

Functions and Procedures

Identifiers

Unit BSHL7DT251

DescriptionUsesClasses, Interfaces, Objects and RecordsFunctions and ProceduresTypesConstantsVariables

Description

HL7 2.5.1 Data Type definition

Overview

Classes, Interfaces, Objects and Records

Name Description
Class TbsAD_251 Address
Class TbsAUI_251 Authorization Information
Class TbsCCD_251 Charge Code and Date
Class TbsCCP_251 Channel Calibration Parameters
Class TbsCD_251 Channel Definition
Class TbsCE_251 Coded Element
Class TbsCF_251 Coded Element with Formatted Values
Class TbsCNE_251 Coded with No Exceptions
Class TbsCNN_251 Composite ID Number and Name Simplified
Class TbsCP_251 Composite Price
Class TbsCQ_251 Composite Quantity with Units
Class TbsCSU_251 Channel Sensitivity
Class TbsCWE_251 Coded with Exceptions
Class TbsCX_251 Extended Composite ID with Check Digit
Class TbsDDI_251 Daily Deductible Information
Class TbsDIN_251 Date and Institution Name
Class TbsDLD_251 Discharge Location and Date
Class TbsDLN_251 Driver_s License Number
Class TbsDLT_251 Delta
Class TbsDR_251 Date/Time Range
Class TbsDT_251  
Class TbsDTM_251  
Class TbsDTN_251 Day Type and Number
Class TbsED_251 Encapsulated Data
Class TbsEI_251 Entity Identifier
Class TbsEIP_251 Entity Identifier Pair
Class TbsELD_251 Error Location and Description
Class TbsERL_251 Error Location
Class TbsFC_251 Financial Class
Class TbsFN_251 Family Name
Class TbsFT_251  
Class TbsGTS_251  
Class TbsHD_251 Hierarchic Designator
Class TbsICD_251 Insurance Certification Definition
Class TbsID_251  
Class TbsIS_251  
Class TbsJCC_251 Job Code/Class
Class TbsLA1_251 Location with Address Variation 1
Class TbsLA2_251 Location with Address Variation 2
Class TbsMA_251 Multiplexed Array
Class TbsMO_251 Money
Class TbsMOC_251 Money and Code
Class TbsMOP_251 Money or Percentage
Class TbsMSG_251 Message Type
Class TbsNA_251 Numeric Array
Class TbsNDL_251 Name with Date and Location
Class TbsNM_251  
Class TbsNR_251 Numeric Range
Class TbsOCD_251 Occurrence Code and Date
Class TbsOSD_251 Order Sequence Definition
Class TbsOSP_251 Occurrence Span Code and Date
Class TbsPIP_251 Practitioner Institutional Privileges
Class TbsPL_251 Person Location
Class TbsPLN_251 Practitioner License or Other ID Number
Class TbsPPN_251 Performing Person Time Stamp
Class TbsPRL_251 Parent Result Link
Class TbsPT_251 Processing Type
Class TbsPTA_251 Policy Type and Amount
Class TbsQIP_251 Query Input Parameter List
Class TbsQSC_251 Query Selection Criteria
Class TbsRCD_251 Row Column Definition
Class TbsRFR_251 Reference Range
Class TbsRI_251 Repeat Interval
Class TbsRMC_251 Room Coverage
Class TbsRP_251 Reference Pointer
Class TbsRPT_251 Repeat Pattern
Class TbsSAD_251 Street Address
Class TbsSCV_251 Scheduling Class Value Pair
Class TbsSI_251  
Class TbsSN_251 Structured Numeric
Class TbsSPD_251 Specialty Description
Class TbsSPS_251 Specimen Source
Class TbsSRT_251 Sort Order
Class TbsST_251  
Class TbsTM_251  
Class TbsTQ_251 Timing Quantity
Class TbsTS_251 Time Stamp
Class TbsTX_251  
Class TbsUVC_251 UB Value Code and Amount
Class TbsVARIES_251  
Class TbsVH_251 Visiting Hours
Class TbsVID_251 Version Identifier
Class TbsVR_251 Value Range
Class TbsVTQ_251 Virtual Table Query Request
Class TbsWVI_251 Channel Identifier
Class TbsWVS_251 Waveform Source
Class TbsXAD_251 Extended Address
Class TbsXCN_251 Extended Composite ID Number and Name for Persons
Class TbsXON_251 Extended Composite Name and Identification Number for Organizations
Class TbsXPN_251 Extended Person Name
Class TbsXTN_251 Extended Telecommunication Number
Class TbsABS_251 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_251 Accident The ACC segment contains patient information relative to an accident in which the patient has been involved.
Class TbsADD_251 Addendum The ADD segment is used to define the continuation of the prior segment in a continuation message. See Section2.10.2, " Continuation messages and segments ," for details.
Class TbsAFF_251 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_251 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_251 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_251 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_251 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_251 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_251 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_251 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 TbsAUT_251 Authorization Information This segment represents an authorization or a pre-authorization for a referred procedure or requested service by the payor covering the patients health care.
Class TbsBLC_251 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_251 Billing The BLG segment is used to provide billing information, on the ordered service, to the filling application.
Class TbsBPO_251 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_251 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_251 Blood Product Transfusion/Disposition HL7 Attribute Table - BTX - Blood Product Transfusion/Disposition
Class TbsCDM_251 Charge Description Master The Technical Steward for the CDM segment is FM.
Class TbsCER_251 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_251 Clinical Study Master The Technical Steward for the CM0 segment is ORDERS.
Class TbsCM1_251 Clinical Study Phase Master The Technical Steward for the CM1 segment is ORDERS.
Class TbsCM2_251 Clinical Study Schedule Master The Technical Steward for the CM2 segment is ORDERS.
Class TbsCNS_251 Clear Notification The clear equipment notification segment contains the data necessary to allow the receiving equipment to clear any associated notifications.
Class TbsCSP_251  
Class TbsCSR_251 Clinical Study Registration The CSR segment will contain fundamental administrative and regulatory information required to document a patients 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_251 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_251 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_251 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_251 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_251 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 TbsDRG_251 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_251 Continuation Pointer The DSC segment is used in the continuation protocol.
Class TbsDSP_251 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_251 Equipment Command The equipment command segment contains the information required to notify the receiving component what is to happen.
Class TbsECR_251 Equipment Command Response The equipment command response segment contains the receiving component's response to the previously received command.
Class TbsEDU_251 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_251 Embedded Query Language
Class TbsEQP_251 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_251 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_251 Event replay query
Class TbsERR_251 Error The ERR segment is used to add error comments to acknowledgment messages.
Class TbsEVN_251 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_251 Facility HL7 Attribute Table - FAC - Facility
Class TbsFT1_251 Financial Transaction The FT1 segment contains the detail data necessary to post charges, payments, adjustments, etc. to patient accounting records.
Class TbsGOL_251 Goal Detail The goal detail segment contains the data necessary to add, update, correct, and delete the goals for an individual.
Class TbsGP1_251 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_251 Grouping/Reimbursement - Procedure Line Item This segment is used for items that pertain to each HCPC/CPT line item.
Class TbsGT1_251 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_251 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.14.4.2. The AL1 segment is used to support Snapshot mode update definition as defined in 2.14.4.1.
Class TbsIIM_251 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 TbsIN1_251 Insurance The IN1 segment contains insurance policy coverage information necessary to produce properly pro-rated and patient and insurance bills.
Class TbsIN2_251 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_251 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_251 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_251 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 TbsISD_251 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 TbsLAN_251 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_251 Location Charge Code The Technical Steward for the LCC segment is PA.
Class TbsLCH_251 Location Characteristic The Technical Steward for the LCH segment is PA.
Class TbsLDP_251 Location Department The Technical Steward for the LDP segment is PA.
Class TbsLOC_251 Location Identification The Technical Steward for the LOC segment is PA.
Class TbsLRL_251 Location Relationship The Technical Steward for the LRL segment is PA.
Class TbsMFA_251 Master File Acknowledgment The Technical Steward for the MFA segment is CQ.
Class TbsMFE_251 Master File Entry The Technical Steward for the MFE segment is CQ.
Class TbsMFI_251 Master File Identification The Technical Steward for the MFI segment is CQ.
Class TbsMRG_251 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_251 Message Acknowledgment The MSA segment contains information sent while acknowledging another message.
Class TbsMSH_251 Message Header The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message.
Class TbsNCK_251 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_251  
Class TbsNK1_251 Next of Kin / Associated Parties The NK1 segment contains information about the patients 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_251 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_251 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_251 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_251 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_251 Observation Request General (taken from ASTM E1238)
Class TbsOBX_251 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_251 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_251 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_251 General Segment The Technical Steward for the OM1 segment is ORDERS.
Class TbsOM2_251 Numeric Observation The Technical Steward for the OM2 segment is ORDERS.
Class TbsOM3_251 Categorical Service/Test/Observation The Technical Steward for the OM3 segment is ORDERS.
Class TbsOM4_251 Observations that Require Specimens The Technical Steward for the OM4 segment is ORDERS.
Class TbsOM5_251  
Class TbsOM6_251 Observations that are Calculated from Other Observations The Technical Steward for the OM6 segment is ORDERS.
Class TbsOM7_251 Additional Basic Attributes The OM7 segment contains additional basic attributes that apply to the definition of most observations/services.
Class TbsORC_251 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). The ORC segment is required in the Order (ORM) message. ORC is mandatory in Order Acknowledgment (ORR) messages if an order detail segment is present, but is not required otherwise.
Class TbsORG_251 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_251 Override Segment Definition: This segment allows a sender to override specific receiving applications business rules to allow for processing of a message that would normally be rejected or ignored.
Class TbsPCR_251 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_251 Patient Additional Demographic The patient additional demographic segment contains demographic information that is likely to change about the patient.
Class TbsPDA_251 Patient Death and Autopsy This segment carries information on a patients death and possible autopsy.
Class TbsPDC_251 Product Detail Country HL7 Attribute Table - PDC - Product Detail Country
Class TbsPEO_251 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_251 Product Experience Sender HL7 Attribute Table - PES - Product Experience Sender
Class TbsPID_251 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 TbsPR1_251 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_251 Practitioner Detail The Technical Steward for the PRA segment is PA and Personnel Management.
Class TbsPRB_251 Problem Details The problem detail segment contains the data necessary to add, update, correct, and delete the problems of a given individual.
Class TbsPRC_251 Pricing The Technical Steward for the PRC segment is PA.
Class TbsPRD_251 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 TbsPSH_251 Product Summary Header HL7 Attribute Table - PSH -Product Summary Header
Class TbsPTH_251 Pathway The pathway segment contains the data necessary to add, update, correct, and delete from the record pathways that are utilized to address an individuals health care.
Class TbsPV1_251 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_251 Patient Visit - Additional Information The PV2 segment is a continuation of information contained on the PV1 segment.
Class TbsQAK_251 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 5.10.4), 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_251 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_251 Query Parameter Definition The QPD segment defines the parameters of the query.
Class TbsQRD_251 Original-Style Query Definition
Class TbsQRF_251 Original style query filter
Class TbsQRI_251 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_251 Response Control Parameter The RCP segment is used to restrict the amount of data that should be returned in response to query.
Class TbsRDF_251 Table Row Definition The RDF segment defines the content of the row data segments (RDT) in the tabular response (RTB).
Class TbsRDT_251 Table Row Data The RDT segment contains the row data of the tabular data response message (TBR).
Class TbsRF1_251 Referral Information This segment represents information that may be useful when sending referrals from the referring provider to the referred-to provider.
Class TbsRGS_251 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_251 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_251 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_251 Requisition Detail-1 RQ1 contains additional detail for each nonstock requisitioned item. This segment definition is paired with a preceding RQD segment.
Class TbsRQD_251 Requisition Detail RQD contains the detail for each requisitioned item. See assumptions above.
Class TbsRXA_251 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_251 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_251 Pharmacy/Treatment Dispense HL7 Attribute Table - RXD - Pharmacy/Treatment Dispense
Class TbsRXE_251 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_251 Pharmacy/Treatment Give HL7 Attribute Table - RXG - Pharmacy/Treatment Give
Class TbsRXO_251 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_251 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_251 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 TbsSCH_251 Scheduling Activity Information The SCH segment contains general information about the scheduled appointment.
Class TbsSFT_251 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_251 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 TbsSPM_251 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_251 Stored Procedure Request Definition
Class TbsSTF_251 Staff Identification The Technical Steward for the STF segment is PA and Personnel Management.
Class TbsTCC_251 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_251 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_251 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_251 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_251 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 TbsUB1_251 UB82 The UB1 segment contains the data necessary to complete UB82 bills specific to the United States; other realms may choose to implement using regional code sets. Only UB82 fields that do not exist in other HL7 defined segments appear in this segment. Patient Name and Date of Birth are required for UB82 billing; however, they are included in the PID segment and therefore do not appear here. The UB codes listed as examples are not an exhaustive or current list. Refer to a UB specification for additional information.
Class TbsUB2_251 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 UB82 and UB92 fields that do not exist in other HL7 defined segments appear in this segment. Just as with the UB82 billing, Patient Name and Date of Birth are required; they are included in the PID segment and therefore do not appear here. When the field locators are different on the UB92, as compared to the UB82, the element is listed with its new location 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_251 Results/update Definition
Class TbsURS_251 Unsolicited Selection
Class TbsVAR_251 Variance The variance segment contains the data necessary to describe differences that may have occurred at the time when a healthcare event was documented.
Generated by PasDoc 0.14.0.