|
Class Summary |
| HL7SegmentABS |
This segment was created to communicate patient abstract information used for billing and reimbursement purposes. |
| HL7SegmentACC |
The ACC segment contains patient information relative to an accident in which the patient has been involved. |
| HL7SegmentADD |
The ADD segment is used to define the continuation of the prior segment in a continuation message. |
| HL7SegmentAFF |
The AFF segment adds detailed information regarding professional affiliations with which the staff member identified by the STF segment is/was associated. |
| HL7SegmentAIG |
The AIG segment contains information about various kinds of resources (other than those with specifically defined segments in this chapter) that can be scheduled. |
| HL7SegmentAIL |
The AIL segment contains information about location resources (meeting rooms, operating rooms, examination rooms, or other locations) that can be scheduled. |
| HL7SegmentAIP |
The AIP segment contains information about the personnel types that can be scheduled. |
| HL7SegmentAIS |
The AIS segment contains information about various kinds of services that can be scheduled. |
| HL7SegmentAL1 |
The AL1 segment contains patient allergy information of various types. |
| HL7SegmentAPR |
The APR segment contains parameters and preference specifications used for requesting appointments in the SRM message. |
| HL7SegmentARQ |
The ARQ segment defines a request for the booking of an appointment. |
| HL7SegmentAUT |
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. |
| HL7SegmentBHS |
The BHS segment defines the start of a batch. |
| HL7SegmentBLC |
The BLC segment contains data necessary to communicate patient abstract blood information used for billing and reimbursement purposes. |
| HL7SegmentBLG |
The BLG segment is used to provide billing information, on the ordered service, to the filling application. |
| HL7SegmentBPO |
Blood product order messages require additional information that is not available in other standard HL7 order messages. |
| HL7SegmentBPX |
In the processing of blood products, it is necessary for the transfusion service and the placer system to communicate information. |
| HL7SegmentBTS |
The BTS segment defines the end of a batch. |
| HL7SegmentBTX |
Blood Product Transfusion/Disposition Segment |
| HL7SegmentCDM |
The Technical Steward for the CDM segment is FM. |
| HL7SegmentCER |
The CER segment adds detailed information regarding the formal authorizations to provide a service (e.g. |
| HL7SegmentCM0 |
The Technical Steward for the CM0 segment is ORDERS. |
| HL7SegmentCM1 |
The Technical Steward for the CM1 segment is ORDERS. |
| HL7SegmentCM2 |
The Technical Steward for the CM2 segment is ORDERS. |
| HL7SegmentCNS |
The clear equipment notification segment contains the data necessary to allow the receiving equipment to clear any associated notifications. |
| HL7SegmentCON |
The consent segment provides details about a specific consent by a patient or staff member. |
| HL7SegmentConstants |
|
| HL7SegmentCSP |
The CSP segment contains information on a patient’s status for a particular phase of the study. |
| HL7SegmentCSR |
The CSR segment will contain fundamental administrative and regulatory information required to document a patient’s enrollment on a clinical trial. |
| HL7SegmentCSS |
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. |
| HL7SegmentCTD |
The CTD segment may identify any contact personnel associated with a patient referral message and its related transactions. |
| HL7SegmentCTI |
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. |
| HL7SegmentDB1 |
The disability segment contains information related to the disability of a person. |
| HL7SegmentDG1 |
The DG1 segment contains patient diagnosis information of various types, for example, admitting, primary, etc. |
| HL7SegmentDRG |
The DRG segment contains diagnoses-related grouping information of various types. |
| HL7SegmentDSC |
The DSC segment is used in the continuation protocol. |
| HL7SegmentDSP |
The DSP segment is used to contain data that has been preformatted by the sender for display. |
| HL7SegmentECD |
The equipment command segment contains the information required to notify the receiving component what is to happen. |
| HL7SegmentECR |
The equipment command response segment contains the receiving component's response to the previously received command. |
| HL7SegmentEDU |
The EDU segment adds detailed educational information to the staff member identified by the STF segment. |
| HL7SegmentEQL |
The EQL segment is used to define queries using select statements based on the query language of choice (e.g., SQL). |
| HL7SegmentEQP |
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. |
| HL7SegmentEQU |
The equipment detail segment contains the data necessary to identify and maintain the equipment that is being used throughout the Laboratory Automation System. |
| HL7SegmentERQ |
The ERQ segment is used to issue queries where the desired response is formatted as an event replay response message. |
| HL7SegmentERR |
The ERR segment is used to add error comments to acknowledgment messages. |
| HL7SegmentEVN |
The EVN segment is used to communicate necessary trigger event information to receiving applications. |
| HL7SegmentFAC |
7.12.6 FAC - Facility Segment |
| HL7SegmentFHS |
The FHS segment is used to head a file (group of batches) as defined in Section 2.10.3, HL7 batch protocol. |
| HL7SegmentFT1 |
The FT1 segment contains the detail data necessary to post charges, payments, adjustments, etc. |
| HL7SegmentFTS |
The FTS segment defines the end of a file. |
| HL7SegmentGOL |
The goal detail segment contains the data necessary to add, update, correct, and delete the goals for an individual. |
| HL7SegmentGP1 |
These fields are used in grouping and reimbursement for CMS APCs. |
| HL7SegmentGP2 |
This segment is used for items that pertain to each HCPC/CPT line item. |
| HL7SegmentGT1 |
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. |
| HL7SegmentIAM |
The IAM segment contains person/patient adverse reaction information of various types. |
| HL7SegmentIIM |
The Inventory Item Master segment (IIM) contains information about the stock of product that can be used to fulfill an ordered test/service. |
| HL7SegmentIN1 |
The IN1 segment contains insurance policy coverage information necessary to produce properly pro rated and patient and insurance bills. |
| HL7SegmentIN2 |
The IN2 segment contains additional insurance policy coverage and benefit information necessary for proper billing and reimbursement. |
| HL7SegmentIN3 |
The IN3 segment contains additional insurance information for certifying the need for patient care. |
| HL7SegmentINV |
The inventory detail segment is the data necessary to track the inventory of substances (e.g. |
| HL7SegmentIPC |
The IPC segment contains information about tasks that need to be performed in order to fulfill the request for imaging service. |
| HL7SegmentISD |
The interaction detail segment contains information about the status of specific interaction (e.g., processing — see section Glossary) on the specific equipment. |
| HL7SegmentLAN |
The LAN segment adds detailed language information to the staff member identified by the STF segment. |
| HL7SegmentLCC |
The Technical Steward for the LCC segment is PA. |
| HL7SegmentLCH |
The Technical Steward for the LCH segment is PA. |
| HL7SegmentLDP |
The Technical Steward for the LDP segment is PA. |
| HL7SegmentLOC |
The LOC segment can identify any patient location referenced by information systems. |
| HL7SegmentLRL |
The Technical Steward for the LRL segment is PA. |
| HL7SegmentMFA |
The Technical Steward for the MFA segment is CQ. |
| HL7SegmentMFE |
The Technical Steward for the MFE segment is CQ. |
| HL7SegmentMFI |
The Technical Steward for the MFI segment is CQ. |
| HL7SegmentMRG |
The MRG segment provides receiving applications with information necessary to initiate the merging of patient data as well as groups of records. |
| HL7SegmentMSA |
The MSA segment contains information sent while acknowledging another message. |
| HL7SegmentMSH |
The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message. |
| HL7SegmentNCK |
The NCK segment is used to allow the various applications on the network to synchronize their system clocks (system date and time). |
| HL7SegmentNDS |
The equipment notification detail segment is the data necessary to maintain an adequate audit trail as well as notifications of events, (e.g., alarms that have occurred on a particular piece of equipment. |
| HL7SegmentNK1 |
The NK1 segment contains information about the patient’s other related parties. |
| HL7SegmentNPU |
The NPU segment allows the updating of census (bed status) data without sending patient-specific data. |
| HL7SegmentNSC |
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. |
| HL7SegmentNST |
The NST segment allows application control-level statistical information to be passed between the various systems on the network. |
| HL7SegmentNTE |
The NTE segment is defined here for inclusion in messages defined in other chapters. |
| HL7SegmentOBR |
General (taken from ASTM E1238)
The Observation Request (OBR) segment is used to transmit information specific to an order for a diagnostic study or observation, physical exam, or assessment. |
| HL7SegmentOBX |
The OBX segment is used to transmit a single observation or observation fragment. |
| HL7SegmentODS |
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. |
| HL7SegmentODT |
This segment addresses tray instructions. |
| HL7SegmentOM1 |
The Technical Steward for the OM1 segment is ORDERS. |
| HL7SegmentOM2 |
The Technical Steward for the OM2 segment is ORDERS. |
| HL7SegmentOM3 |
The Technical Steward for the OM3 segment is ORDERS. |
| HL7SegmentOM4 |
The Technical Steward for the OM4 segment is ORDERS. |
| HL7SegmentOM5 |
The Technical Steward for the OM5 segment is ORDERS. |
| HL7SegmentOM6 |
The Technical Steward for the OM6 segment is ORDERS. |
| HL7SegmentOM7 |
The OM7 segment contains additional basic attributes that apply to the definition of most observations/services. |
| HL7SegmentORC |
The Common Order segment (ORC) is used to transmit fields that are common to all orders (all types of services that are requested). |
| HL7SegmentORG |
The ORG segment relates a practitioner to an organization unit and adds detailed information regarding the practitioner's practicing specialty in that organization unit. |
| HL7SegmentOVR |
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. |
| HL7SegmentPCR |
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. |
| HL7SegmentPD1 |
The patient additional demographic segment contains demographic information that is likely to change about the patient. |
| HL7SegmentPDA |
This segment carries information on a patient’s death and possible autopsy. |
| HL7SegmentPDC |
7.12.5 PDC - Product Detail Country Segment |
| HL7SegmentPEO |
Details related to a particular clinical experience or event are embodied in the PEO segment. |
| HL7SegmentPES |
7.12.1 PES - Product Experience Sender Segment |
| HL7SegmentPID |
The PID segment is used by all applications as the primary means of communicating patient identification information. |
| HL7SegmentPR1 |
The PR1 segment contains information relative to various types of procedures that can be performed on a patient. |
| HL7SegmentPRA |
The Technical Steward for the PRA segment is PA and Personnel Management. |
| HL7SegmentPRB |
The problem detail segment contains the data necessary to add, update, correct, and delete the problems of a given individual. |
| HL7SegmentPRC |
The Technical Steward for the PRC segment is PA. |
| HL7SegmentPRD |
This segment will be employed as part of a patient referral message and its related transactions. |
| HL7SegmentPSH |
7.12.4 PSH - Product Summary Header Segment |
| HL7SegmentPTH |
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. |
| HL7SegmentPV1 |
The PV1 segment is used by Registration/Patient Administration applications to communicate information on an account or visit-specific basis. |
| HL7SegmentPV2 |
The PV2 segment is a continuation of information contained on the PV1 segment. |
| HL7SegmentQAK |
The QAK segment contains information sent with responses to a query. |
| HL7SegmentQID |
The QID segment contains the information necessary to uniquely identify a query. |
| HL7SegmentQPD |
The QPD segment defines the parameters of the query. |
| HL7SegmentQRD |
The QRD segment is used to define a query. |
| HL7SegmentQRF |
The QRF segment is used with the QRD segment to further refine the content of an original style query. |
| HL7SegmentQRI |
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). |
| HL7SegmentRCP |
The RCP segment is used to restrict the amount of data that should be returned in response to query. |
| HL7SegmentRDF |
The RDF segment defines the content of the row data segments (RDT) in the tabular response (RTB). |
| HL7SegmentRDT |
The RDT segment contains the row data of the tabular data response message (TBR). |
| HL7SegmentRF1 |
This segment represents information that may be useful when sending referrals from the referring provider to the referred-to provider. |
| HL7SegmentRGS |
The RGS segment is used to identify relationships between resources identified for a scheduled event. |
| HL7SegmentRMI |
The RMI segment is used to report an occurrence of an incident event pertaining or attaching to a patient encounter. |
| HL7SegmentROL |
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. |
| HL7SegmentRQ1 |
RQ1 contains additional detail for each nonstock requisitioned item. |
| HL7SegmentRQD |
RQD contains the detail for each requisitioned item |
| HL7SegmentRXA |
The ORC must have the filler order number and the order control code RE. |
| HL7SegmentRXC |
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. |
| HL7SegmentRXD |
Dispense Segment |
| HL7SegmentRXE |
The RXE segment details the pharmacy or treatment application's encoding of the order. |
| HL7SegmentRXG |
Pharmacy Treatment Give Segment |
| HL7SegmentRXO |
This is the "master" pharmacy/treatment order segment. |
| HL7SegmentRXR |
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. |
| HL7SegmentSAC |
The container detail segment is the data necessary to maintain the containers that are being used throughout the Laboratory Automation System. |
| HL7SegmentSCH |
The SCH segment contains general information about the scheduled appointment. |
| HL7SegmentSFT |
Definition: This segment provides additional information about the software product(s) used as a Sending Application. |
| HL7SegmentSID |
The Substance Identifier segment contains data necessary to identify the substance (e.g., reagents) used in the production of analytical test results. |
| HL7SegmentSPM |
The intent of this segment is to describe the characteristics of a specimen. |
| HL7SegmentSPR |
The SPR segment is used to issue queries using stored procedure calls. |
| HL7SegmentSTF |
The Technical Steward for the STF segment is PA and Personnel Management. |
| HL7SegmentTCC |
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." |
| HL7SegmentTCD |
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). |
| HL7SegmentTQ1 |
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. |
| HL7SegmentTQ2 |
The TQ2 segment is used to form a relationship between the service request the TQ1/TQ2 segments are associated with, and other service requests. |
| HL7SegmentTXA |
The TXA segment contains information specific to a transcribed document but does not include the text of the document. |
| HL7SegmentUB1 |
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. |
| HL7SegmentUB2 |
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. |
| HL7SegmentURD |
The URD segment is used in sending unsolicited updates about orders and results. |
| HL7SegmentURS |
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). |
| HL7SegmentVAR |
The variance segment contains the data necessary to describe differences that may have occurred at the time when a healthcare event was documented. |
| HL7SegmentVTQ |
The VTQ segment is used to define queries that are responded to with the Tabular Data Message (TBR). |
This package provides classes that model the segment types defines by the HL7 standard version 2.5.1.
