Seq# | Description | Data Type | Usage | Vocabulary | Length | C.LEN | Flags |
---|---|---|---|---|---|---|---|
TM | |||||||
1 | Time | [2..16] | 13 |
The time zone of the sender may be sent optionally as an offset from the coordinated universal time (previously known as Greenwich Mean Time). Where the time zone is not present in a particular TM field but is included as part of the date/time field in the MSH segment, the MSH value will be used as the default time zone. Otherwise, the time is understood to refer to the local time of the sender.
Examples:
Time | Description |
|0000| | midnight |
|235959+1100| | 1 second before midnight in a time zone eleven hours ahead of Universal Coordinated Time (i.e., East of Greenwich). |
|0800| | Eight AM, local time of the sender. |
|093544.2312| | 44.2312 seconds after Nine thirty-five AM, local time of sender. |
|13| | 1pm (with a precision of hours), local time of sender. |
Prior to v 2.3, this data type was specified in the format HHMM[SS[.SSSS]][+/-ZZZZ]. As of v 2.3 minutes are no longer required. By site-specific agreement, HHMM[SS[.SSSS]][+/-ZZZZ] may be used where backward compatibility must be maintained.This corresponds a minimum length of 4.
The TM data type does not follow the normal truncation pattern, and the truncation character is never valid in the TM data type. Instead, the truncation behavior is based on the semantics of times.
Unless otherwise specified in the context where the DTM type is used, the DTM type may be truncated to a particular minute. When a TM is truncated, the truncated form SHALL still be a valid TM type. Refer to Chapter 2, section 2.5.5.2, "Truncation Pattern", for further information.