Besa HL7 2.x Help FileGetting Started Units Class Hierarchy Classes, Interfaces, Objects and Records Types Variables Constants Functions and Procedures Identifiers |
Class TbsTQ2_271
Unit
BSHL7DT271
Declaration
type TbsTQ2_271 = class(TbsHL7Segment)
Description
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. There are many situations, such as the creation of a service request for a group of intravenous (IV) solutions, where the sequence of the individual intravenous solutions (each a service in itself) needs to be specified, e.g., hyperalimentation with multi-vitamins in every third bottle. There are other situations where part of the service request's instructions contains a results condition of some type, such as "PRN pain." There is currently a free text "condition" field of TQ1-10 - Condition text which allows any condition to be specified. However, to support a fully encoded version of service request sequencing, or results condition, the TQ2, Timing/Quantity Relationship segment has been defined. TQ2 Usage notes: a
Cyclic placer service request groups To implement a cyclic group of four IV service requests using the parent/child paradigm, the parent specifies a custom group of IVs, and the following occurs: - TQ2 of the second child service request specifies that it follow the first child service request. - TQ2 of the third child service request specifies that it follow the second child service request. - TQ2 of the fourth child service request specifies that it follow the third service request. To repeat the group of four child service requests in a cyclic manner, the following occurs: - TQ2 of the first child service request specifies that it is to be executed once without any dependence on the completion of other service requests. Its second execution follows the completion of the fourth service request. See example in Section 4A.5.2 RXO segment field examples. This scheme allows the following to be tracked: - The status of the whole group of service requests to be reported back at the level of the parent service request. - The status for each individual IV service request by following the status of the corresponding child service request. Separate Service requests example: - The same group of service requests can be sent as a group of four service requests (without a common parent), linked only by the data in their quantity/timing fields. In this case, there is no convenient HL7 method of transmitting the service request status of the group as a whole without transmitting the status of each of the four separate service requests. b) Inheritance of service request status Cancellation/discontinuation/hold service request control events: - This logic implies the normal execution of the referenced predecessor service request. Thus a cancel (or discontinuation or hold) of a predecessor service request implies the cancellation (or discontinuation or hold) of all subsequent service requests in the chain. - If the referenced service request has been canceled (or discontinued or held), the current service request inherits that same status. - In the case of hold, the removal of the hold of the predecessor implies a removal of the hold for the given service request (which can then be executed according to the specification in the TQ2 segment). )
Hierarchy
Overview
Methods
Properties
Description
Methods
 |
function RelatedPlacerNumberRepCount : Integer; |
|
|
|
function RelatedFillerNumberRepCount : Integer; |
|
|
|
function RelatedPlacerGroupNumberRepCount : Integer; |
|
|
Properties
|
property SetIdTq2 : TbsSI_271 read GetSetIdTq2 write SetSetIdTq2; |
|
Set Id - Tq2, Min : 0, Max : 1
|
|
property SequenceResultsFlag : TbsID_271 read GetSequenceResultsFlag write SetSequenceResultsFlag; |
|
Sequence/Results Flag, Min : 0, Max : 1
|
|
property RelatedPlacerNumber[RepCount:Integer]: TbsEI_271 read GetRelatedPlacerNumber write SetRelatedPlacerNumber; |
|
Related Placer Number, Min : 0, Max : *
|
|
property RelatedFillerNumber[RepCount:Integer]: TbsEI_271 read GetRelatedFillerNumber write SetRelatedFillerNumber; |
|
Related Filler Number, Min : 0, Max : *
|
|
property RelatedPlacerGroupNumber[RepCount:Integer]: TbsEI_271 read GetRelatedPlacerGroupNumber write SetRelatedPlacerGroupNumber; |
|
Related Placer Group Number, Min : 0, Max : *
|
|
property SequenceConditionCode : TbsID_271 read GetSequenceConditionCode write SetSequenceConditionCode; |
|
Sequence Condition Code, Min : 0, Max : 1
|
|
property CyclicEntryExitIndicator : TbsID_271 read GetCyclicEntryExitIndicator write SetCyclicEntryExitIndicator; |
|
Cyclic Entry/Exit Indicator, Min : 0, Max : 1
|
|
property SequenceConditionTimeInterval : TbsCQ_271 read GetSequenceConditionTimeInterval write SetSequenceConditionTimeInterval; |
|
Sequence Condition Time Interval, Min : 0, Max : 1
|
|
property CyclicGroupMaximumNumberOfRepeats : TbsNM_271 read GetCyclicGroupMaximumNumberOfRepeats write SetCyclicGroupMaximumNumberOfRepeats; |
|
Cyclic Group Maximum Number Of Repeats, Min : 0, Max : 1
|
|
property SpecialServiceRequestRelationship : TbsID_271 read GetSpecialServiceRequestRelationship write SetSpecialServiceRequestRelationship; |
|
Special Service Request Relationship, Min : 0, Max : 1
|
Generated by PasDoc 0.14.0.
|