HL7 NSC Application Status Change
HL7 field reference NSC fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| NSC.1 | Application Change Type | Yes | No | IS | 0409 |
| NSC.2 | Current CPU | No | No | ST | |
| NSC.3 | Current Fileserver | No | No | ST | |
| NSC.4 | Current Application | No | No | HD | |
| NSC.5 | Current Facility | No | No | HD | |
| NSC.6 | New CPU | No | No | ST | 0206 |
| NSC.7 | New Fileserver | No | No | ST | |
| NSC.8 | New Application | No | No | HD | |
| NSC.9 | New Facility | No | No | HD |
NSC reports an application status change such as start, stop, or other state transition.
The standard describes NSC this way: The NSC segment is used to inform (NMR query response) or announce (NMD unsolicited update) the start up, shut down, and/or migration (to a different CPU or file server/file system) of a particular application.
Equipment and specimen-control segments are used around instruments, analyzers, containers, device commands, device status, and test configuration. They are practical plumbing for lab and automation workflows.
The main trap is treating an equipment status as if it were a clinical result, or treating a specimen/container identifier as if it were interchangeable with a patient or order identifier. Keep the layers separate.
The v2.5.1 structures show NSC in NMD_N02 - Application management data message (unsolicited), NMQ_N01 - Application management query message, and NMR_N01 - Application management query message. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
NSC-1 qualifies the equipment or specimen workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0409. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
NSC-2 carries Current CPU for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
NSC-3 carries Current Fileserver for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
NSC-4 carries Current Application for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
NSC-5 places the equipment or specimen workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
NSC-6 carries New CPU for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0206; many real interfaces narrow that list further, so follow the receiver's implementation guide.
NSC-7 carries New Fileserver for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
NSC-8 carries New Application for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
NSC-9 places the equipment or specimen workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.