Instructs receiving laboratory equipment or automation systems to clear previously issued notification messages, specified by a range of notification reference numbers or time window. It is sent in laboratory automation workflows to allow an LIS or automation manager to acknowledge and dismiss alerts or status notifications from instruments after they have been reviewed.
from zato.hl7v2.v2_9 import CNS
cns = CNS()
cns.starting_notification_reference_number = '1001'
cns.ending_notification_reference_number = '1005'How to construct and work with real-world CNS segments.
Clear one notification message
from zato.hl7v2.v2_9 import CNS
cns = CNS()
cns.starting_notification_reference_number = '1001'
cns.ending_notification_reference_number = '1001'Clear multiple notifications
from zato.hl7v2.v2_9 import CNS
cns = CNS()
cns.starting_notification_reference_number = '1001'
cns.ending_notification_reference_number = '1005'Clear notifications with timestamp
from zato.hl7v2.v2_9 import CNS
from zato.hl7v2.v2_9 import DTM
cns = CNS()
cns.starting_notification_reference_number = '2001'
cns.ending_notification_reference_number = '2010'
cns.starting_notification_date_time = DTM('20240115093000')
cns.ending_notification_date_time = DTM('20240115100000')Step-by-step guides for working with HL7 v2 in Zato.
CNS contains clear notification information including starting and ending reference numbers for acknowledging laboratory automation messages.
Set both starting and ending reference numbers to the same value:
cns.starting_notification_reference_number = '1001'
cns.ending_notification_reference_number = '1001'Set starting and ending reference numbers to define the range:
cns.starting_notification_reference_number = '1001'
cns.ending_notification_reference_number = '1005'CNS clears notifications while EQU reports equipment status. Both are used in laboratory automation messaging workflows.
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.
Complete list of fields in the CNS segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | starting_notification_reference_number | NM | Optional | No | - |
| 2 | ending_notification_reference_number | NM | Optional | No | - |
| 3 | starting_notification_date_time | DTM | Optional | No | - |
| 4 | ending_notification_date_time | DTM | Optional | No | - |
| 5 | starting_notification_code | CWE | Optional | No | HL70585 |
| 6 | ending_notification_code | CWE | Optional | No | HL70586 |
Get started with Zato and connect your systems in minutes.