Used to request or announce the start-up, shut-down, or migration of an HL7 application to a different CPU or file system. It appears in NMQ and NMD messages and carries the current and new application, facility, and CPU identifiers. Primarily used by application management tools to coordinate operational changes across networked healthcare systems.
from zato.hl7v2.v2_9 import NSC
nsc = NSC()
nsc.application_change_type = 'U'
nsc.current_cpu = 'WELLNESS-SRV-01'
nsc.current_application = 'FITNESS-APP'How to construct and work with real-world NSC segments.
Application coming online
from zato.hl7v2.v2_9 import NSC
nsc = NSC()
nsc.application_change_type = 'U'
nsc.current_facility = 'WELLNESS-SRV-01'
nsc.new_fileserver = 'FITNESS-APP'Application moving to new server
from zato.hl7v2.v2_9 import NSC
nsc = NSC()
nsc.application_change_type = 'M'
nsc.current_cpu = 'NUTR-SRV-01'
nsc.current_fileserver = 'FS-OLD'
nsc.current_application = 'DIET-APP'
nsc.new_cpu = 'NUTR-SRV-02'
nsc.new_fileserver = 'FS-NEW'
nsc.new_application = 'DIET-APP'Application going offline
from zato.hl7v2.v2_9 import NSC
nsc = NSC()
nsc.application_change_type = 'D'
nsc.current_cpu = 'SCREEN-SRV-01'
nsc.current_fileserver = 'FS-SCREEN'
nsc.current_application = 'PREV-CARE-APP'Step-by-step guides for working with HL7 v2 in Zato.
NSC contains application status change information including state transitions and server details for monitoring wellness system changes.
Common change types include U (up/startup), D (down/shutdown), and M (migration). These track wellness application state transitions.
Use current and new fields to track the migration:
nsc.application_change_type = 'M'
nsc.current_cpu = 'OLD-SERVER'
nsc.new_cpu = 'NEW-SERVER'NSC contains status changes while NST contains statistics. Both are used for monitoring wellness application health.
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 NSC segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | application_change_type | CWE | Required | No | HL70409 |
| 2 | current_cpu | ST | Optional | No | - |
| 3 | current_fileserver | ST | Optional | No | - |
| 4 | current_application | HD | Optional | No | HL70361 |
| 5 | current_facility | HD | Optional | No | HL70362 |
| 6 | new_cpu | ST | Optional | No | - |
| 7 | new_fileserver | ST | Optional | No | - |
| 8 | new_application | HD | Optional | No | HL70361 |
| 9 | new_facility | HD | Optional | No | HL70362 |
Get started with Zato and connect your systems in minutes.