Carries a single timestamp representing the current date and time of a system's internal clock. It is used in system-administration and equipment-notification messages to synchronize clocks between laboratory instruments, point-of-care devices, and the laboratory information system, ensuring that all timestamps across connected systems remain consistent.
from zato.hl7v2 import NCK
nck = NCK()
nck.system_date_time = '20260515'How to construct and work with real-world NCK segments.
Sending the current system time for clock sync between devices
from zato.hl7v2.v2_9 import NCK
nck = NCK()
nck.system_date_time = '20240515103045'Communicating the system date without a time component
from zato.hl7v2.v2_9 import NCK
nck = NCK()
nck.system_date_time = '20240515'System clock with sub-second precision for high-accuracy sync
from zato.hl7v2.v2_9 import NCK
nck = NCK()
nck.system_date_time = '20240515103045.1234'Step-by-step guides for working with HL7 v2 in Zato.
NCK carries a single system clock timestamp. It is exchanged in system-administration messages to synchronize the internal clocks of laboratory instruments, analyzers, and other automated devices with the controlling information system.
The system_date_time field uses DTM format with variable precision:
from zato.hl7v2.v2_9 import NCK
nck = NCK()
nck.system_date_time = '20240515103045'DTM supports date-only, date-time, and sub-second precision:
from zato.hl7v2.v2_9 import NCK
nck = NCK()
# Date only
nck.system_date_time = '20240515'
# Date and time
nck.system_date_time = '20240515103045'
# Sub-second
nck.system_date_time = '20240515103045.1234'Access the field directly after creating the segment:
from zato.hl7v2.v2_9 import NCK
nck = NCK()
nck.system_date_time = '20240515103045'
dt = nck.system_date_timeNCK appears in system-level messages for clock queries and updates:
from zato.hl7v2.v2_9 import NCK
nck = NCK()
nck.system_date_time = '20240515103045'
dt = nck.system_date_timeZato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.
Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.
Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.
Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.
Complete list of fields in the NCK segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | system_date_time | DTM | Required | No | - |
Get started with Zato and connect your systems in minutes.