The equipment detail segment contains the data necessary to identify and maintain the equipment that is being used throughout the Laboratory Automation System.
Seq# | DataElement | Description | Must Implement | Flags | Cardinality | Length | C.LEN | Vocabulary | DataType |
---|---|---|---|---|---|---|---|---|---|
EQU | |||||||||
1 | 01479 | Equipment Instance Identifier | SHALL | [1..*] | EI | ||||
2 | 01322 | Event Date/Time | SHALL | [1..1] | DTM | ||||
3
|
01323 | Equipment State |
MAY
True: False: |
C |
[1..1] [0..1] |
CWE | |||
4 | 01324 | Local/Remote Control State | [0..1] | CWE | |||||
5 | 01325 | Alert Level | [0..1] | CWE | |||||
6 | 03487 | Expected date/time of the next status change | [0..1] | DTM |
(Definition from OBX.18 in Ch. 7)
Definition: Retained for backwards compatibility as of v 2.7 only. This field is now represented through the PRT segment. This field identifies the Equipment Instance (e.g., Analyzer, Analyzer module, group of Analyzers, etc.) responsible for the production of the observation. This is the identifier from an institution's master list of equipment, where the institution is specified by the namespace ID or if it is blank, then by the "Producer's ID" (OBX-15). It should be possible to retrieve from this master list the equipment type, serial number, etc., however it is not planned to transfer this information with every OBX. The repeating of this field allows for the hierarchical representation of the equipment (lowest level first), e.g., module of an instrument, instrument consisting of modules, cluster of multiple instruments, etc.
(Definition from EQU.1 in Ch. 13)
Definition: This field identifies the equipment. This is the identifier from an institution's master list of equipment. The <namespace ID> identifies the institution.
The Equipment Instance Identifier shall be unique, meaning that the “Entity Identifier” component shall be unique within the Namespace ID that should accommodate hierarchical representation of equipment (recursive hierarchy like in "Russian dolls", e.g., a sub-module embedded in a module assembled in a system being a member of a cluster).
If this attribute repeats, all instances must represent the same device.
Definition: This field is the date/time that the event (e.g., state transition, issuing of command, finishing of command execution) occurred.
Definition: This field identifies the status that the equipment was in at the time that the transaction was initiated. Refer to HL7 Table 0365 – Equipment State in Chapter 2C, Code Tables, for valid values. The Equipment State is required in the ESU message and is optional otherwise.
Definition: This field identifies the current state of control associated with the equipment. An equipment can either work autonomously ('Local' control state) or it can be controlled by another system, e.g., LAS computer ('Remote' control state). Refer to HL7 Table 0366 – Local/Remote Control State in Chapter 2C, Code Tables, for valid values.
Definition: This field identifies the highest level of the alert state (e.g., highest alert severity) that is associated with the indicated equipment (e.g., processing event, inventory event, QC event). Refer to HL7 Table 0367 – Alert Level in Chapter 2C, Code Tables, for valid values.
Definition: This field is the predicted date/time of the next equipment status change (e.g. from “maintenance” back to “normal operation”).