| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | column description | 0;1 | FREE TEXT | B | The column description is the identifier that names the data element that gets mapped to a FileMan field. The RDF segment (table row definition) has a field (the 3rd sequence) that is a repeating element. The 1st component of the element is the column description. It is the column name in central repository master table. (The 2nd component is the HL7 data type. The 3rd component is the length of the field.) The RDF segment defines the format of subsequent RDT segment (table row data). The sequence of column description fields in the RDF segment maps the sequence of the corresponding data values in the RDT segment. (The 2nd field of the RDF segment is the number of columns or data elements passed in the RDF and RDT segments.) | |
| .02 | field number(+) | 0;2 | NUMERIC | This field holds the FileMan field number that corresponds to the segment sequence number in question. If this sequence component maps to a FileMan sub-file (multiple) then the SUBFILE NUMBER (#.04) is required before FIELD NUMBER to be able to validate (input transform.) | ||
| .03 | hl7 data type(+) | 0;3 | POINTER | 771.4 | This field holds the HL7 data type of the sequence. | |
| .04 | subfile number | 0;4 | NUMERIC | This field holds the FileMan sub-file number. ONLY if FIELD NUMBER relates to a field in a multiple. | ||
| .05 | subfile lkup literal | 0;5 | FREE TEXT | If this sequence is a field in a subfile and the .01 of the multiple is not included in the HL7 segment but is some literal, then provide the literal string here. If SUBFILE LKUP LITERAL is NULL then SUBFILE LKUP SEQUENCE must not be NULL. If SUBFILE LKUP LITERAL is not NULL then SUBFILE LKUP SEQUENCE must be NULL. | ||
| .06 | subfile lkup column | 0;6 | FREE TEXT | If the FIELD NUMBER is associated with a multiple field, then this field holds the COLUMN DESCRIPTION of the .01 field of the multiple. If the .01 field is not a sequence, then leave this field blank and provide a value for SUBFILE LKUP LITERAL. If SUBFILE LKUP LITERAL is NULL then SUBFILE LKUP SEQUENCE must not be NULL. If SUBFILE LKUP LITERAL is not NULL then SUBFILE LKUP SEQUENCE must be NULL. | ||
| .07 | extended pointer lkup | 0;7 | NUMERIC | If FIELD NUMBER is a pointer and you want to look-up the entry by a field other than its .01, then enter that field number. Example: Parent facility, in the association multiple of the Institution file points to Institution. The Institution NAME may not be unique. It would be more useful to look-up the Institution by STATION NUMBER. | ||
| .08 | list | 0;8 | BOOLEAN | 1:YES 0:NO | ||
| .09 | column length(+) | 0;9 | NUMERIC | This field holds the maximum column width of the column in question. The column description is the 3rd sequence of the RDF segment. It is a repeating element. The maximum column width is the 3rd component of the element. | ||
| .11 | repeating field | 0;11 | BOOLEAN | 1:YES 0:NO | If this field is repeating - a single valued multiple (a multiple field with only a .01 field) - field, then set the flag to YES. If the multiple should be cleaned out first, then also set the CLEAN MULTIPLE flag too. | |
| .12 | clean multiple | 0;12 | BOOLEAN | 1:YES 0:NO | If this field is a single valued repeating element (see REPEATING FIELD) and the existing values should be deleted before the update occurs, then set this flag to YES. By setting this flag, you indicate all the valid data is contained within the incoming message, so purge existing values and start clean. | |
| .13 | vuid prefix | 0;13 | FREE TEXT | String indicates that the field is a Pointer, and the VUID may be used instead of the value (.01). Example: Instead of Drug Class name, you may be use the VUID of the drug class such as "VUID123456", where 123456 is the VUID of the Drug Class and "VUID" is the prefix. | ||
| .14 | time zone flag | 0;14 | SET OF CODES | L:LOCAL U:UTC | If this column/field represents a date data type then MFS needs to know how to handle the time zone. This field indicates how FileMan should file the HL7 date -- local time or UTC time. Note: VUID effective date/time should always be flagged LOCAL. | |
| .15 | sequence | 0;15 | NUMERIC | ASEQ | The sequence number of the data segments returned in a query. If this field is a Sub-file record, enter the sequence of the .01. If the sequence has associated sub-record fields, use the SUBFILE SEQUENCE of this sequence number to sequence the fields of the sub-record. | |
| .16 | wp field | 0;16 | BOOLEAN | 1:YES 0:NO | If this field is a word processing field then set this flag to YES. | |
| 1 | subfile sequence | 1;0 | MULTIPLE | 4.111 |
Error: Invalid Global File Type: 4.011