HL7 NDL Name with Date and Location
HL7 datatype components NDL components from HL7 v2.5.1 Hide components
These are the generated components for the version selected at the top of the page. The article stays practical, and this panel follows the chosen HL7 version.
Components
| Pos | Component | Name | Type | Table | Description |
|---|---|---|---|---|---|
| 1 | NDL.1 | Name | CNN | Name; Type CNN. | |
| 2 | NDL.2 | Start Date/time | TS | Start Date/time; Type TS. | |
| 3 | NDL.3 | End Date/time | TS | End Date/time; Type TS. | |
| 4 | NDL.4 | Point of Care | IS | 0302 | Point of Care; Type IS; HL7 table 0302. |
| 5 | NDL.5 | Room | IS | 0303 | Room; Type IS; HL7 table 0303. |
| 6 | NDL.6 | Bed | IS | 0304 | Bed; Type IS; HL7 table 0304. |
| 7 | NDL.7 | Facility | HD | Facility; Type HD. | |
| 8 | NDL.8 | Location Status | IS | 0306 | Location Status; Type IS; HL7 table 0306. |
| 9 | NDL.9 | Patient Location Type | IS | 0305 | Patient Location Type; Type IS; HL7 table 0305. |
| 10 | NDL.10 | Building | IS | 0307 | Building; Type IS; HL7 table 0307. |
| 11 | NDL.11 | Floor | IS | 0308 | Floor; Type IS; HL7 table 0308. |
NDL combines a person name, timing, and location. It commonly appears around result-copy and provider participation fields where the message needs to say who, when, and where.
In this guide, NDL appears in OBR.32, OBR.33, OBR.34, OBR.35. That used-by list is a good reality check: the datatype is only half the story, and the field that uses it tells you the workflow.
The component panel above is expanded by default because most datatype pages are used as quick lookup pages. Start there for the exact HL7 v2.5.1 shape, then use the notes below for the practical gotchas.
NDL-1 to NDL-11: Component Quick Read
The generated component panel above is the formal quick lookup. The short version is below so you can scan the shape without counting carets by eye.
The table-backed components here are NDL-4, NDL-5, NDL-6, NDL-8, NDL-9, NDL-10, NDL-11. Keep those values to the table or value set your implementation guide names, especially when the field is crossing organization boundaries.
- NDL-1 Name - Name. Type CNN.
- NDL-2 Start Date/time - Start Date/time. Type TS.
- NDL-3 End Date/time - End Date/time. Type TS.
- NDL-4 Point of Care - Point of Care. Type IS. Table 0302.
- NDL-5 Room - Room. Type IS. Table 0303.
- NDL-6 Bed - Bed. Type IS. Table 0304.
- NDL-7 Facility - Facility. Type HD.
- NDL-8 Location Status - Location Status. Type IS. Table 0306.
- NDL-9 Patient Location Type - Patient Location Type. Type IS. Table 0305.
- NDL-10 Building - Building. Type IS. Table 0307.
- NDL-11 Floor - Floor. Type IS. Table 0308.
Practical Notes
Date and time precision matters. If you only know the date, send the date. If you know the time and timezone, agree how that timezone should be represented. In Integration Soup, date helpers such as GetHL7Date and GetDateFromHL7Date are useful because they keep date formatting and parsing explicit instead of hand-built string slicing.
In HL7 Soup Web, click a field that uses NDL and the interpretation view will show which component you are sitting in and where that value lives in the raw message. That is especially handy with compact datatypes because one missing caret can move every value after it.
Official and Reference Notes
For formal reference, compare the generated HL7 v2.5.1 panel above with the HL7 v2.5.1 datatype list and the HL7 Terminology data type code system. Local implementation guides can narrow allowed values, tables, and component usage.