Notification detail

NDS carries details of a system or application notification including a reference number, timestamp, alert severity, and notification code. It is used in notification messages to communicate alerts, warnings, and informational notices between HL7 applications.

The notification_alert_severity field uses the CWE datatype with HL7 table 0367:

from zato.hl7v2.v2_9 import NDS, CWE

nds = NDS()
nds.notification_alert_severity = CWE(
    identifier='C',
    text='Critical',
    name_of_coding_system='HL70367'
)

The notification_code field uses the CWE datatype with HL7 table 0610:

from zato.hl7v2.v2_9 import NDS, CWE

nds = NDS()
nds.notification_code = CWE(
    identifier='SYS-DOWN',
    text='System unavailable',
    name_of_coding_system='HL70610'
)

HL7 table 0367 defines the standard severity levels for notifications:

from zato.hl7v2.v2_9 import NDS, CWE

nds = NDS()

# C = Critical
nds.notification_alert_severity = CWE(identifier='C')

# W = Warning
nds.notification_alert_severity = CWE(identifier='W')

# I = Information
nds.notification_alert_severity = CWE(identifier='I')

All four fields are required in NDS - set the reference number, timestamp, severity, and code:

from zato.hl7v2.v2_9 import NDS, CWE

nds = NDS()
nds.notification_reference_number = (
    '1'
)
nds.notification_date_time = (
    '20240601120000'
)
nds.notification_alert_severity = CWE(
    identifier='C',
    text='Critical'
)
nds.notification_code = CWE(
    identifier='SYS-DOWN',
    text='System unavailable'
)

Zato 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.