Besa HL7 2.x Help File

Getting Started

Units

Class Hierarchy

Classes, Interfaces, Objects and Records

Types

Variables

Constants

Functions and Procedures

Identifiers

Unit BSHL7DT24

DescriptionUsesClasses, Interfaces, Objects and RecordsFunctions and ProceduresTypesConstantsVariables

Description

HL7 2.4 Data Type definition

Overview

Classes, Interfaces, Objects and Records

Name Description
Class TbsAD_24 Address
Class TbsAUI_24 Authorization Information
Class TbsCCD_24 Charge Time
Class TbsCCP_24 Channel Calibration Parameters
Class TbsCD_24 Channel Definition
Class TbsCE_24 Coded Element
Class TbsCF_24 Coded Element With Formatted Values
Class TbsCK_24 Composite ID With Check Digit
Class TbsCN_24 Composite ID Number And Name
Class TbsCNE_24 Coded With No Exceptions
Class TbsCNN_24  
Class TbsCP_24 Composite Price
Class TbsCQ_24 Composite Quantity With Units
Class TbsCSU_24 Channel Sensitivity/units
Class TbsCWE_24 Coded With Exceptions
Class TbsCX_24 Extended Composite ID With Check Digit
Class TbsDDI_24 Daily Deductible
Class TbsDIN_24 Activation Date
Class TbsDLD_24 Discharge Location
Class TbsDLN_24 Driver's License Number
Class TbsDLT_24 Delta Check
Class TbsDR_24 Date/time Range
Class TbsDT_24  
Class TbsDTN_24 Day Type And Number
Class TbsED_24 Encapsulated Data
Class TbsEI_24 Entity Identifier
Class TbsEIP_24 Parent Order
Class TbsELD_24 Error
Class TbsFC_24 Financial Class
Class TbsFN_24 Family Name
Class TbsFT_24  
Class TbsHD_24 Hierarchic Designator
Class TbsID_24  
Class TbsIS_24  
Class TbsJCC_24 Job Code/class
Class TbsLA1_24  
Class TbsLA2_24  
Class TbsMA_24 Multiplexed Array
Class TbsMO_24 Money
Class TbsMOC_24 Charge To Practise
Class TbsMOP_24 Money Or Percentage
Class TbsMSG_24 Message Type
Class TbsNA_24 Numeric Array
Class TbsNDL_24 Observing Practitioner
Class TbsNM_24  
Class TbsNR_24 Wertebereich
Class TbsOCD_24 Occurence
Class TbsOSD_24 Order Sequence
Class TbsOSP_24 Occurence Span
Class TbsPCF_24 Pre-certification Required
Class TbsPI_24 Person Identifier
Class TbsPIP_24 Privileges
Class TbsPL_24 Person Location
Class TbsPLN_24 Practitioner ID Numbers
Class TbsPN_24 Person Name
Class TbsPPN_24 Performing Person Time Stamp
Class TbsPRL_24 Parent Result Link
Class TbsPT_24 Processing Type
Class TbsPTA_24 Policy Type
Class TbsQIP_24 Query Input Parameter List
Class TbsQSC_24 Query Selection Criteria
Class TbsRCD_24 Row Column Definition
Class TbsRFR_24 Reference Range
Class TbsRI_24 Repeat Interval
Class TbsRMC_24 Room Coverage
Class TbsRP_24 Reference Pointer
Class TbsSAD_24 Street Address
Class TbsSCV_24 Scheduling Class Value Pair
Class TbsSI_24  
Class TbsSN_24 Structured Numeric
Class TbsSPD_24 Specialty
Class TbsSPS_24 Specimen Source
Class TbsSRT_24 Sort Order
Class TbsST_24  
Class TbsTM_24  
Class TbsTN_24  
Class TbsTQ_24 Timing Quantity
Class TbsTS_24 Time Stamp
Class TbsTX_24  
Class TbsUVC_24 Value Code And Amount
Class TbsVARIES_24  
Class TbsVH_24 Visiting Hours
Class TbsVID_24 Version Identifier
Class TbsVR_24 Value Qualifier
Class TbsWVI_24 Channel Identifier
Class TbsWVS_24 Waveform Source
Class TbsXAD_24 Extended Address
Class TbsXCN_24 Extended Composite ID Number And Name For Persons
Class TbsXON_24 Extended Composite Name And Identification Number For Organizations
Class TbsXPN_24 Extended Person Name
Class TbsXTN_24 Extended Telecommunication Number
Class TbsABS_24 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_24 Accident The ACC segment contains patient information relative to an accident in which the patient has been involved.
Class TbsADD_24 Addendum The ADD segment is used to define the continuation of the prior segment in a continuation message.  See Section2.15.2, “Continuation messages and segments,” for details.
Class TbsAFF_24 Professional Affiliation
Class TbsAIG_24 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_24 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_24 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_24 Appointment Information - Service 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_24 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_24 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_24 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_24 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_24 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_24 Billing The BLG segment is used to provide billing information, on the ordered service, to the filling application.
Class TbsCDM_24 Charge Description Master The Technical Steward for the CDM segment is PAFM.
Class TbsCM0_24 Clinical Study Master The Technical Steward for the CM0 segment is ORDERS.
Class TbsCM1_24 Clinical Study Phase Master The Technical Steward for the CM1 segment is ORDERS.
Class TbsCM2_24 Clinical Study Schedule Master The Technical Steward for the CM2 segment is ORDERS.
Class TbsCNS_24 Clear Notification The clear equipment notification segment contains the data necessary to allow the receiving equipment to clear any associated notifications.
Class TbsCSP_24  
Class TbsCSR_24 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_24 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_24 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_24 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_24 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_24 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_24 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_24 Continuation Pointer The DSC segment is used in the continuation protocol.
Class TbsDSP_24 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_24 Equipment Command The equipment command segment contains the information required to notify the receiving component what is to happen.
Class TbsECR_24 Equipment Command Response The equipment command response segment contains the receiving component’s response to the previously received command.
Class TbsEDU_24 Educational Detail
Class TbsEQL_24 Embedded Query Language
Class TbsEQP_24 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_24 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_24 Event Replay Query
Class TbsERR_24 Error The ERR segment is used to add error comments to acknowledgment messages.
Class TbsEVN_24 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_24 Facility HL7 Attribute Table – FAC – Facility
Class TbsFT1_24 Financial Transaction The FT1 segment contains the detail data necessary to post charges, payments, adjustments, etc. to patient accounting records.
Class TbsGOL_24 Goal Detail The goal detail segment contains the data necessary to add, update, correct, and delete the goals for an individual.
Class TbsGP1_24 Grouping/Reimbursement - Visit These fields are used in grouping and reimbursement for HCFA APCs.  Please refer to the “Outpatient Prospective Payment System Final Rule” (“OPPS Final Rule”) issued by HCFA.
Class TbsGP2_24 Grouping/Reimbursement - Procedure Line Item This segment is used for items that pertain to each HCPC/CPT line item.
Class TbsGT1_24 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_24 Patient adverse reaction information - unique iden 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 TbsIN1_24 Insurance The IN1 segment contains insurance policy coverage information necessary to produce properly pro-rated patient and insurance bills.
Class TbsIN2_24 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 HCFA or other regulatory agencies.
Class TbsIN3_24 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 HCFA, or other regulatory agencies.
Class TbsINV_24 Inventory Detail The inventory detail segment is the data necessary to track the inventory of substances (e.g. reagent, tips, waste) on equipment.
Class TbsISD_24 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_24 Language Detail
Class TbsLCC_24 Location Charge Code The Technical Steward for the LCC segment is PAFM.
Class TbsLCH_24 Location Characteristic The Technical Steward for the LCH segment is PAFM.
Class TbsLDP_24 Location Department The Technical Steward for the LDP segment is PAFM.
Class TbsLOC_24 Location Identification The Technical Steward for the LOC segment is PAFM.
Class TbsLRL_24 Location Relationship The Technical Steward for the LRL segment is PAFM.
Class TbsMFA_24 Master File Acknowledgment The Technical Steward for the MFA segment is CQ.
Class TbsMFE_24 Master File Entry The Technical Steward for the MFE segment is CQ.
Class TbsMFI_24 Master File Identification The Technical Steward for the MFI segment is CQ.
Class TbsMRG_24 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_24 Message Acknowledgment The MSA segment contains information sent while acknowledging another message.
Class TbsMSH_24 Message Header The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message.
Class TbsNCK_24 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_24  
Class TbsNK1_24 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_24 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_24 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_24 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_24 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_24 Observation Request General (taken from ASTM E1238)
Class TbsOBX_24 Observation/Result The OBX segment is used to transmit a single observation or observation fragment.  It represents the smallest indivisible unit of a report.  Its structure is summarized in Figure 7-5.
Class TbsODS_24 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_24 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_24 General Segment The Technical Steward for the OM1 segment is ORDERS.
Class TbsOM2_24 Numeric Observation The Technical Steward for the OM2 segment is ORDERS.
Class TbsOM3_24 Categorical Service/Test/Observation The Technical Steward for the OM3 segment is ORDERS.
Class TbsOM4_24 Observations that Require Specimens The Technical Steward for the OM4 segment is ORDERS.
Class TbsOM5_24  
Class TbsOM6_24 Observations that are Calculated from Other Observ The Technical Steward for the OM6 segment is ORDERS.
Class TbsOM7_24 Additional Basic Attributes The OM7 segment contains additional basic attributes that apply to the definition of most observations/services.
Class TbsORC_24 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_24 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 TbsPCR_24 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_24 Patient Additional Demographic The patient additional demographic segment contains demographic information that is likely to change about the patient.
Class TbsPDA_24 Patient death and autopsy This segment carries information on a patient’s death and possible autopsy.
Class TbsPDC_24 Product Detail Country HL7 Attribute Table – PDC – Product Detail Country
Class TbsPEO_24 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_24 Product Experience Sender HL7 Attribute Table - PES – Product Experience Sender
Class TbsPID_24 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_24 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_24 Practitioner Detail The Technical Steward for the PRA segment is PAFM and Personnel Management
Class TbsPRB_24 Problem Details The problem detail segment contains the data necessary to add, update, correct, and delete the problems of a given individual.
Class TbsPRC_24 Pricing The Technical Steward for the PRC segment is PAFM.
Class TbsPRD_24 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_24 Product Summary Header HL7 Attribute Table – PSH –Product Summary Header
Class TbsPTH_24 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_24 Patient visit
Class TbsPV2_24 Patient visit - additional information The PV2 segment is a continuation of information contained on the PV1 segment.
Class TbsQAK_24 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_24 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_24 Query Parameter Definition
Class TbsQRD_24 Original-Style Query Definition
Class TbsQRF_24 Original Style Query Filter
Class TbsQRI_24 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_24 Response Control Parameter The RCP segment is used to restrict the amount of data that should be returned in response to query.
Class TbsRDF_24 Table Row Definition The RDF segment defines the content of the row data segments (RDT) in the tabular response (RTB).
Class TbsRDT_24 Table Row Data The RDT segment contains the row data of the tabular data response message (TBR).
Class TbsRF1_24 Referral Information This segment represents information that may be useful when sending referrals from the referring provider to the referred-to provider.
Class TbsRGS_24 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_24 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_24 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_24 Requisition Detail-1 RQ1 contains additional detail for each nonstock requisitioned item.  This segment definition is paired with a preceding RQD segment.
Class TbsRQD_24 Requisition Detail RQD contains the detail for each requisitioned item.  See assumptions above.
Class TbsRXA_24 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_24 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_24 Pharmacy/Treatment Dispense HL7 Attribute Table – RXD – Pharmacy/Treatment Dispense
Class TbsRXE_24 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_24 Pharmacy/Treatment Give HL7 Attribute Table – RXG – Pharmacy/Treatment Give
Class TbsRXO_24 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_24 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_24 Specimen and 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_24 Scheduling Activity Information The SCH segment contains general information about the scheduled appointment.
Class TbsSID_24 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 TbsSPR_24 Stored Procedure Request Definition
Class TbsSTF_24 Staff Identification The Technical Steward for the STF segment is PAFM and Personnel Management.
Class TbsTCC_24 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_24 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 TbsTXA_24 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 is used to update other healthcare systems 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_24 UB82 The UB1 segment contains the data necessary to complete UB82 bills.  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_24 UB92 Data The UB2 segment contains data necessary to complete UB92 bills.  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_24 Results/update Definition
Class TbsURS_24 Unsolicited Selection
Class TbsVAR_24 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 TbsVTQ_24 Virtual Table Query Request
Generated by PasDoc 0.14.0.