Class TbsAD_22 |
Address |
Class TbsCE_22 |
Coded Element |
Class TbsCF_22 |
Coded Element with Formatted Values |
Class TbsCK_22 |
Composite Id With Check Digit |
Class TbsCM_ABS_RANGE_22 |
Absolute Range |
Class TbsCM_AUI_22 |
Authorization Information |
Class TbsCM_BATCH_TOTAL_22 |
Cm For Batch Totals |
Class TbsCM_CCD_22 |
Charge Time |
Class TbsCM_DDI_22 |
Daily Deductible |
Class TbsCM_DIN_22 |
Activation Date |
Class TbsCM_DLD_22 |
Discharge Location |
Class TbsCM_DLT_22 |
Delta Check |
Class TbsCM_DTN_22 |
Day Type And Number |
Class TbsCM_EIP_22 |
Parent Order |
Class TbsCM_ELD_22 |
Error |
Class TbsCM_FILLER_22 |
Number Of Processing Power Point |
Class TbsCM_FINANCE_22 |
Cm Of Finance |
Class TbsCM_GROUP_ID_22 |
Order Group Number |
Class TbsCM_INTERNAL_LOCATION_22 |
Cm For Location Information In Hospital |
Class TbsCM_JOB_CODE_22 |
Job Title |
Class TbsCM_LA1_22 |
Location With Address Information |
Class TbsCM_LICENSE_NO_22 |
Cm For Driving License |
Class TbsCM_MOC_22 |
Charge To Practise |
Class TbsCM_MSG_22 |
Message Type |
Class TbsCM_NDL_22 |
Observing Practitioner |
Class TbsCM_OCD_22 |
Occurence |
Class TbsCM_OSD_22 |
Order Sequence |
Class TbsCM_OSP_22 |
Occurence Span |
Class TbsCM_PAT_ID_22 |
Patient Id |
Class TbsCM_PAT_ID_0192_22 |
Patient Id With Table 0192 |
Class TbsCM_PCF_22 |
Pre-certification Required |
Class TbsCM_PEN_22 |
Penalty |
Class TbsCM_PIP_22 |
Privileges |
Class TbsCM_PLACER_22 |
Order Number Of The Client / The Contracting Authority |
Class TbsCM_PLN_22 |
Practitioner Id Numbers |
Class TbsCM_POSITION_22 |
Seat Or Room / Table / Chair |
Class TbsCM_PRACTITIONER_22 |
Action Carried Out By |
Class TbsCM_PRL_22 |
Parent Result Link |
Class TbsCM_PTA_22 |
Policy Type |
Class TbsCM_RANGE_22 |
Range Of Values |
Class TbsCM_RFR_22 |
Reference Range |
Class TbsCM_RI_22 |
Interval |
Class TbsCM_RMC_22 |
Room Coverage |
Class TbsCM_SPD_22 |
Specialty |
Class TbsCM_SPS_22 |
Specimen Source |
Class TbsCM_UVC_22 |
Value Code And Amount |
Class TbsCM_VR_22 |
Value Qualifier |
Class TbsCN_PERSON_22 |
Cn For Person |
Class TbsCN_PHYSICIAN_22 |
Cn For Physicians |
Class TbsCOMP_ID_DIGIT_22 |
|
Class TbsCP_22 |
Composite Price |
Class TbsCQ_22 |
Composite Quantity With Units |
Class TbsCX_22 |
Extended Composite ID With Check Digit |
Class TbsDLN_22 |
Driver's License Number |
Class TbsDT_22 |
|
Class TbsEI_22 |
Entity Identifier |
Class TbsFC_22 |
Financial Class |
Class TbsFT_22 |
|
Class TbsHD_22 |
Hierarchic Designator |
Class TbsID_22 |
|
Class TbsIS_22 |
|
Class TbsJCC_22 |
Job Code Class |
Class TbsMO_22 |
Money |
Class TbsNM_22 |
|
Class TbsPL_22 |
Person Location |
Class TbsPN_22 |
Person Name |
Class TbsPT_22 |
Processing Type |
Class TbsRP_22 |
Reference Pointer |
Class TbsSI_22 |
|
Class TbsST_22 |
|
Class TbsTM_22 |
|
Class TbsTN_22 |
|
Class TbsTQ_22 |
Timing Quantity |
Class TbsTS_22 |
Time Stamp |
Class TbsTX_22 |
|
Class TbsVARIES_22 |
|
Class TbsXAD_22 |
Extended Address |
Class TbsXCN_22 |
Extended Composite ID Number And Name |
Class TbsXON_22 |
Extended Composite Name And ID For Organizations |
Class TbsXPN_22 |
Extended Person Name |
Class TbsXTN_22 |
Extended Telecommunication Number |
Class TbsACC_22 |
Accident The ACC segment contains patient information relative to an accidentin which the patient has been involved. |
Class TbsADD_22 |
Addendum The ADD segment is used to define the continuation of the prior segment in a continuation message |
Class TbsAL1_22 |
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 TbsBHS_22 |
Batch Header The BHS segment defines the start of a batch |
Class TbsBLG_22 |
Billing The BLG segment is used to provide billing information, on the ordered service, to the filling application |
Class TbsBTS_22 |
Batch Trailer The BTS segment defines the end of a batch. |
Class TbsDG1_22 |
Diagnosis The DG1 segment contains patient diagnosis information of various types. For example: Admitting, Current, Primary, Final, etc. Coding methodologies are also defined |
Class TbsDSC_22 |
Continuation Pointer The DSC segment is used in the continuation protocol. |
Class TbsDSP_22 |
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 TbsERR_22 |
Error The ERR segment is used to add error comments to acknowledgement messages |
Class TbsEVN_22 |
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 table 0003 - event type code |
Class TbsFHS_22 |
File Header The FHS segment is used to head a file (group of batches) as defined in Section 2.9.3. |
Class TbsFT1_22 |
Financial Transaction The FT1 segment contains detail data necessary to post charges, payments, adjustments, etc. to patient accounting records. |
Class TbsFTS_22 |
File Trailer The FTS segment defines the end of a file |
Class TbsGT1_22 |
Guarantor The GT1 segment contains guarantor (e.g., person with financial responsibility for payment of a patient account) data for patient and insurance billing applications |
Class TbsIN1_22 |
Insurance The IN1 segment contains insurance policy coverage information necessary to produce properly pro-rated and patient and insurance bills. |
Class TbsIN2_22 |
Insurance Additional Info 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 HICFA or other regulatory agencies. |
Class TbsIN3_22 |
Insurance Additional Info-certification The IN3 segment contains additional insurance information for certifying the need for patient care. Fields used by this segment are defined by HICFA or other regulatory agencies |
Class TbsMFA_22 |
Master File Acknowledgement |
Class TbsMFE_22 |
Master File Entry |
Class TbsMFI_22 |
Master File Identification |
Class TbsMRG_22 |
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_22 |
Message Acknowledgment The MSA segment contains information sent while acknowledging another message |
Class TbsMSH_22 |
Message Header The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message. Note: If MSH-15 and MSH-16 are omitted (or are both null), the original Acknowledgement Mode rules are used. |
Class TbsNCK_22 |
System Clock the NCK segment is used to allow the various systems on the network to synchronize their system clocks (system date and time). |
Class TbsNK1_22 |
Next Of Kin 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_22 |
Bed Status Update The NPU segment allows the updating of census (bed status) data without sending patient specific data. For example: changing the status of a bed from housekeeping to unoccupied. |
Class TbsNSC_22 |
Status Change The NSC segment can be used to request the start-up, shut-down, and/or migration (to a different cpu or file-server/file-system) of a particular application. It can also be used in an unsolicited update from one system to another to announce the start-up, shut-down, or migration of an application |
Class TbsNST_22 |
Statistics The NST segment allows network 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 network management applications monitoring the state of various network links. |
Class TbsNTE_22 |
Notes And Comments The NTE segment is defined here for inclusion in messages defined in other chapters. It is a common format for sending notes and comments |
Class TbsOBR_22 |
Observation Request The Observation Request (OBR) segment is used to transmit information specific to an order for a diagnostic study or observation, physical exam, or assessment. The daggered (+) items in this segment are not created by the placer. They are created by the filler and valued as needed when the OBR segment is returned as part of a report. Hence on a new order sent to the filler, they are not valued. There is an exception when the filler initiates the order. In that case, the filler order number is valued and the placer order number may be blank. The starred (*) fields are only relevant when an observation is associated with a specimen. These are completed by the placer when the placer obtains the specimen. They are completed by the filler when the filler obtains the specimen. OBR-7-observation date/time and OBR-8-observation end date/time are the physiologically relevant times. In the case of an observation on a specimen, they represent the start and end of the specimen collector. In the case of an observation obtained directly from a subject (eg., BP, Chest Xray), they represent the start and end time of the observation |
Class TbsOBX_22 |
Observation Result |
Class TbsODS_22 |
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-11verified 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-4-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_22 |
Diet Tray Instruction This segment addresses tray instructions. These are independent of diet codes, supplements, and preferences and therefore get separate order numbers |
Class TbsOM1_22 |
General - Fields That Apply To Most Observations The OM1 segment contains attributes that apply to the definition of most observations. This segment also contains the field attributes that specify what additional segments might also be defined for this observation |
Class TbsOM2_22 |
Numeric Observation This segment contains attributes of observations with continuous values (including those with data types of numeric, date, or time stamp). It can be applied to observation batteries of type A and C (see OM1-19nature of test/observation). |
Class TbsOM3_22 |
Categorical Test/observation This segment applies to free text and other non-numeric data types |
Class TbsOM4_22 |
Observation That Require Specimens |
Class TbsOM5_22 |
Observation Batteries This segment contains information about batteries and supersets (a nature code of F, P or S, as described in OM119-nature of test/observation). |
Class TbsOM6_22 |
Observations That Are Calculated From Other Obersvations This segment contains information about quantities that are derived from one or more other quantities or direct observations by mathematical or logical means |
Class TbsORC_22 |
Commom Order The Common Order segment (ORC) is used to transmit data elements that are common to all orders (all types of services that are requested). The ORC segment is required in both the Order (ORM) and Order Acknowledgement (ORR) messages. |
Class TbsPID_22 |
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_22 |
Procedures The PR1 segment contains information relative to various types of procedures that can be performed on a patient. For example: Surgical, Nuclear Medicine, X-Ray with contrast, etc |
Class TbsPRA_22 |
Practitioner Detail |
Class TbsPV1_22 |
Patient Visit The PV1 segment is used by Registration/ADT applications to communicate information on a visit specific basis. This segment can be used to send multiple visit statistic records to the same patient account, or single visit records to more than one account. Individual sites must determine this segment's use |
Class TbsPV2_22 |
Patient Visit - Additional Information The PV2 segment is a continuation of visit specific information contained on the PV1 segment. |
Class TbsQRD_22 |
Query Definition |
Class TbsQRF_22 |
Query Filter The QRF segment is used with the QRD segment to refine the content of a query further |
Class TbsRQ1_22 |
Requisition Detail 1 RQ1 contains additional detail for each nonstock requisitioned item. This segment definition is paired with a preceeding RQD segment. |
Class TbsRQD_22 |
Requisition Detail RQD contains the detail for each requisitioned item. |
Class TbsRXA_22 |
Pharmacy Aadministration 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_22 |
Pharmacy Component Order If the drug ordered with the RXO segment is a compound drug OR an IV solution, AND there is not a coded value for the 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 application on substitutions at the RXC level is identical to that for the RXO level. |
Class TbsRXD_22 |
Pharmacy Dispense |
Class TbsRXE_22 |
Pharmacy Encoded Order The RXE segment details the pharmacy application's encoding of the order. It also contains several pharmacyspecific order status fields, such as RXE-16-number of refills remaining, RXE-17-number of refills/doses dispensed, RXE-18-date/time of most recent refill/dose, and RXE-19-total daily dose. |
Class TbsRXG_22 |
Pharmacy Give |
Class TbsRXO_22 |
Pharmacy Prescription Order This is the "master" pharmacy 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. It can be used for any type of pharmacy order, including inpatient (unit dose and compound unit dose), outpatient, IVs, and hyperalimentation IVs (nutritional IVs). In addition to the pharmaceutical information, this segment contains additional data such as provider and text comments. |
Class TbsRXR_22 |
Pharmacy Route The Pharmacy Route segment contains the alternative combination of route, site, administration device, and administration method that are prescribed. The pharmacy and/or nursing staff has a choice between the routes based on either their professional judgment or administration instructions provided by the physician |
Class TbsSTF_22 |
Staff Identification Segment |
Class TbsUB1_22 |
Ub82 Data The UB1 segment contains data necessary to complete UB82 bills. Only UB82 data elements that do not exist in other HL7 defined segments will 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 |
Class TbsUB2_22 |
Ub92 Data The UB2 segment contains data necessary to complete UB92 bills. Only UB92 data elements that do not exist in other HL7 defined segments will 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. Where the field locators are different on the UB92, when compared to the UB82, the element is listed with its new location in parentheses (). |
Class TbsURD_22 |
Results/update Definition The URD segment is used in sending unsolicited updates about orders and results. It's purpose is similar to that of the QRD segment, but from the results/unsolicited update point of view. Some of the fields have parallels in the QRD segment |
Class TbsURS_22 |
Unsolicited Selection The URS segment is identical with the QRF segment, except that, if the name of any field contains Query (of QRY), this word has been changed to Results (See URS-5-R/U other results subject definition). |
Class TbsZxx_22 |
Any Z Segment |