# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | FREE TEXT | B | This is the name of the HL7 field. | |
2 | segment(+) | 0;2 | POINTER | 771.3 | C | The three character HL7 segment name (e.g., MSH). |
4 | dhcp file | 0;4 | POINTER | 1 | ||
5 | sequence(+) | 0;5 | NUMERIC | The HL7 sequence number associated witht the HL7 field (e.g., 7). | ||
6 | maximum length(+) | 0;6 | NUMERIC | The maximum length of the HL7 field (e.g., 8). | ||
7 | data type(+) | 0;7 | POINTER | 771.4 | The HL7 data type associated with the HL7 field (e.g., DATE). | |
8 | required?(+) | 0;8 | SET OF CODES | 1:REQUIRED 0:NOT REQUIRED | This field specifies whether the HL7 field is required. | |
9 | repetition | 0;9 | NUMERIC | The number of times the HL7 field can repeat within an HL7 segment. If the field cannot repeat, leave this field blank. | ||
10 | table number | 0;10 | FREE TEXT | Only fields that have an HL7 data type of ID (Coded Value) have a table number. The ID data type is equivalent to a Set of Codes or Pointer data type in VA FileMan. For locally defined fields, the table number should begin with the 2-4 character DHCP package namespace. | ||
11 | item number | 0;11 | FREE TEXT | The HL7 item number associated with the HL7 field (e.g., 00043). | ||
12 | parent | 0;12 | POINTER | 771.1 | MUMPS code that is used to validate values in this field. This code is applicable across all DHCP applications. | |
13 | application | APPL;0 | MULTIPLE | 771.113 | This multiple valued field contains information realted to use of this HL7 filed by a specific application. | |
50 | version | V;0 | MULTIPLE | 771.12 | ||
101 | sample dhcp value | 101;E1,245 | FREE TEXT | |||
102 | sample hl7 value | 102;E1,245 | FREE TEXT | |||
150 | description | D;0 | WORD-PROCESSING |