using System.Linq; using System.Collections.Generic; namespace ExpressionEvaluatorForDotNet { public class HL7V27SegmentLOC { public HL7V2Message message { get; init; } public string Id { get { return @"LOC"; } } public string SegmentId { get { return @"LOC"; } } public string LongName { get { return @"Location Identification"; } } public string Description { get { return @"The LOC segment can identify any patient location referenced by information systems. This segment gives physical set up information about the location. This is not intended to include any current occupant or current use information. There should be one LOC segment for each patient location. If desired, there can also be one LOC segment for each nursing unit and room."; } } public string Sample { get { return @""; } } public IList<string> Chapters { get { return new[] { "CH_08", }; } } public HL7V27SegmentLOC(HL7V2Message message) { this.message = message; } internal HL7V27Field _primaryKeyValueLoc; public HL7V27Field PrimaryKeyValueLoc { get { if (_primaryKeyValueLoc != null) { return _primaryKeyValueLoc; } var fieldData = new HL7V27FieldData { Id = @"LOC.1", Type = @"Field", Position = @"LOC.1", Name = @"Primary Key Value - Loc", Length = 0, Usage = @"R", Rpt = @"1", DataType = @"PL", DataTypeName = @"Person Location", TableId = null, TableName = null, Description = @"This field contains the institution's identification code for the location. The identifying key value. Must match MFE-4 -Primary Key Value - MFE. This field has the same components as the patient location fields in the PV1 segment (except that bed status is not included here). At least the first component of this field is required. The first component can be an identifying code for the nursing station for inpatient locations, or clinic, department or home for patient locations other than inpatient ones. ", Sample = @"", Fields = new[] { new HL7V2FieldData { Id = @"LOC.1.1", Type = @"Component", Position = @"LOC.1.1", Name = @"Point Of Care", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0302", TableName = @"Point of Care", Description = @"This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of Care for suggested values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.1.1", Type = @"SubComponent", Position = @"LOC.1.1.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.1.2", Type = @"SubComponent", Position = @"LOC.1.1.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.1.3", Type = @"SubComponent", Position = @"LOC.1.1.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.2", Type = @"Component", Position = @"LOC.1.2", Name = @"Room", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0303", TableName = @"Room", Description = @"This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.2.1", Type = @"SubComponent", Position = @"LOC.1.2.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.2.2", Type = @"SubComponent", Position = @"LOC.1.2.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.2.3", Type = @"SubComponent", Position = @"LOC.1.2.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.3", Type = @"Component", Position = @"LOC.1.3", Name = @"Bed", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0304", TableName = @"Bed", Description = @"This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.3.1", Type = @"SubComponent", Position = @"LOC.1.3.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.3.2", Type = @"SubComponent", Position = @"LOC.1.3.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.3.3", Type = @"SubComponent", Position = @"LOC.1.3.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.4", Type = @"Component", Position = @"LOC.1.4", Name = @"Facility", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = null, TableName = null, Description = @"This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation. See Section 2.A.33, “HD - hierarchic designator” for discussion of data type. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.4.1", Type = @"SubComponent", Position = @"LOC.1.4.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.4.2", Type = @"SubComponent", Position = @"LOC.1.4.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.4.3", Type = @"SubComponent", Position = @"LOC.1.4.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.5", Type = @"Component", Position = @"LOC.1.5", Name = @"Location Status", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0306", TableName = @"Location Status", Description = @"This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location Status for suggested values.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.6", Type = @"Component", Position = @"LOC.1.6", Name = @"Person Location Type", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0305", TableName = @"Person Location Type", Description = @"Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.7", Type = @"Component", Position = @"LOC.1.7", Name = @"Building", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0307", TableName = @"Building", Description = @"This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.7.1", Type = @"SubComponent", Position = @"LOC.1.7.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.7.2", Type = @"SubComponent", Position = @"LOC.1.7.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.7.3", Type = @"SubComponent", Position = @"LOC.1.7.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.8", Type = @"Component", Position = @"LOC.1.8", Name = @"Floor", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0308", TableName = @"Floor", Description = @"This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.8.1", Type = @"SubComponent", Position = @"LOC.1.8.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.8.2", Type = @"SubComponent", Position = @"LOC.1.8.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.8.3", Type = @"SubComponent", Position = @"LOC.1.8.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.9", Type = @"Component", Position = @"LOC.1.9", Name = @"Location Description", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component describes the location in free text.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.10", Type = @"Component", Position = @"LOC.1.10", Name = @"Comprehensive Location Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"EI", DataTypeName = @"Entity Identifier", TableId = null, TableName = null, Description = @"The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.10.1", Type = @"SubComponent", Position = @"LOC.1.10.1", Name = @"Entity Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, ""HD - hierarchic designator"".", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.10.2", Type = @"SubComponent", Position = @"LOC.1.10.2", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0363", TableName = @"Assigning Authority", Description = @"The component intentionally remains associated with the IS data type in v2.7. The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Refer to User-defined Table 0363 – Assigning Authority for suggested values. Note: When the HD is used as a part of another data type, in this case as part of the EI data type, this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first component", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.10.3", Type = @"SubComponent", Position = @"LOC.1.10.3", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.10.4", Type = @"SubComponent", Position = @"LOC.1.10.4", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type. Refer to HL7 Table 0301 - Universal ID Type for valid values.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.1.11", Type = @"Component", Position = @"LOC.1.11", Name = @"Assigning Authority For Location", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0363", TableName = @"Assigning Authority", Description = @"The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning Authority for suggested values for the first sub-component of the HD component, <namespace ID>. This component makes it possible for codes to be differentiated when the field in which this data type is used repeats. Note:When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.1.11.1", Type = @"SubComponent", Position = @"LOC.1.11.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.11.2", Type = @"SubComponent", Position = @"LOC.1.11.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.1.11.3", Type = @"SubComponent", Position = @"LOC.1.11.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, } } _primaryKeyValueLoc = new HL7V27Field { field = message[@"LOC"][1], fieldData = fieldData }; // check for repetitions if (_primaryKeyValueLoc.field.FieldRepetitions != null && _primaryKeyValueLoc.field.FieldRepetitions.Count > 0) { _primaryKeyValueLoc.fieldRepetitions = HL7V2FieldGenerator.GenerateV27FieldRepetitions(_primaryKeyValueLoc, fieldData); } return _primaryKeyValueLoc; } } internal HL7V27Field _locationDescription; public HL7V27Field LocationDescription { get { if (_locationDescription != null) { return _locationDescription; } var fieldData = new HL7V27FieldData { Id = @"LOC.2", Type = @"Field", Position = @"LOC.2", Name = @"Location Description", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This field contains the optional free text description of the location, to elaborate upon LOC primary key value.", Sample = @"", Fields = null } _locationDescription = new HL7V27Field { field = message[@"LOC"][2], fieldData = fieldData }; // check for repetitions if (_locationDescription.field.FieldRepetitions != null && _locationDescription.field.FieldRepetitions.Count > 0) { _locationDescription.fieldRepetitions = HL7V2FieldGenerator.GenerateV27FieldRepetitions(_locationDescription, fieldData); } return _locationDescription; } } internal HL7V27Field _locationTypeLoc; public HL7V27Field LocationTypeLoc { get { if (_locationTypeLoc != null) { return _locationTypeLoc; } var fieldData = new HL7V27FieldData { Id = @"LOC.3", Type = @"Field", Position = @"LOC.3", Name = @"Location Type - Loc", Length = 0, Usage = @"R", Rpt = @"*", DataType = @"CWE", DataTypeName = @"Coded With Exceptions", TableId = @"0260", TableName = @"Patient Location Type", Description = @"This field contains the code identifying what type of location this is. Refer to User-defined Table 0260 - Patient Location Type for suggested values.", Sample = @"", Fields = new[] { new HL7V2FieldData { Id = @"LOC.3.1", Type = @"Component", Position = @"LOC.3.1", Name = @"Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CWE.2. Different coding schemes will have different elements here.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.2", Type = @"Component", Position = @"LOC.3.2", Name = @"Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The second component contains the descriptive or textual name of the identifier, e.g., ""myocardial infarction"" or ""X-ray impression"".", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.3", Type = @"Component", Position = @"LOC.3.3", Name = @"Name Of Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"The third component contains the code for the name of the coding system from which the value in CWE.1 is obtained. Each coding system is assigned a unique identifier. As of v2.7 this component is required when CWE.1 is populated and CWE.14 is not populated. Both CWE.3 and CWE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CWE.3 and/or CWE.14, the ""Coding System"" component or the ""Coding System OID"" for the tuple. Refer to HL7 Table 0396 – Coding System in Chapter 2C, section ""Coding System Table"" for valid values. Refer to section 2.A.8.3, ""Name of Coding System (ID)"" for a discussion of coding system conventions.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.4", Type = @"Component", Position = @"LOC.3.4", Name = @"Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies an alternate code. Analogous to CWE.1- Identifier. Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.5", Type = @"Component", Position = @"LOC.3.5", Name = @"Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.6", Type = @"Component", Position = @"LOC.3.6", Name = @"Name Of Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 - Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.4 is populated and CWE.17 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.6 and/or CWE.17, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.7", Type = @"Component", Position = @"LOC.3.7", Name = @"Coding System Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.8", Type = @"Component", Position = @"LOC.3.8", Name = @"Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.9", Type = @"Component", Position = @"LOC.3.9", Name = @"Original Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.10", Type = @"Component", Position = @"LOC.3.10", Name = @"Second Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.11", Type = @"Component", Position = @"LOC.3.11", Name = @"Second Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.12", Type = @"Component", Position = @"LOC.3.12", Name = @"Name Of Second Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.13", Type = @"Component", Position = @"LOC.3.13", Name = @"Second Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.14", Type = @"Component", Position = @"LOC.3.14", Name = @"Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.15", Type = @"Component", Position = @"LOC.3.15", Name = @"Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.16", Type = @"Component", Position = @"LOC.3.16", Name = @"Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.17", Type = @"Component", Position = @"LOC.3.17", Name = @"Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.18", Type = @"Component", Position = @"LOC.3.18", Name = @"Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.19", Type = @"Component", Position = @"LOC.3.19", Name = @"Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.20", Type = @"Component", Position = @"LOC.3.20", Name = @"Second Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.21", Type = @"Component", Position = @"LOC.3.21", Name = @"Second Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.3.22", Type = @"Component", Position = @"LOC.3.22", Name = @"Second Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated.", Sample = @"", FieldDatas = null }, } } _locationTypeLoc = new HL7V27Field { field = message[@"LOC"][3], fieldData = fieldData }; // check for repetitions if (_locationTypeLoc.field.FieldRepetitions != null && _locationTypeLoc.field.FieldRepetitions.Count > 0) { _locationTypeLoc.fieldRepetitions = HL7V2FieldGenerator.GenerateV27FieldRepetitions(_locationTypeLoc, fieldData); } return _locationTypeLoc; } } internal HL7V27Field _organizationNameLoc; public HL7V27Field OrganizationNameLoc { get { if (_organizationNameLoc != null) { return _organizationNameLoc; } var fieldData = new HL7V27FieldData { Id = @"LOC.4", Type = @"Field", Position = @"LOC.4", Name = @"Organization Name - Loc", Length = 0, Usage = @"O", Rpt = @"*", DataType = @"XON", DataTypeName = @"Extended Composite Name And Identification Number For Organizations", TableId = null, TableName = null, Description = @"This field contains the organization(s) of which this location is a part. For inpatient locations, this can be the hospital or institution name. For outpatient locations, this can be the clinic or office name.", Sample = @"", Fields = new[] { new HL7V2FieldData { Id = @"LOC.4.1", Type = @"Component", Position = @"LOC.4.1", Name = @"Organization Name", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The name of the specified organization.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2", Type = @"Component", Position = @"LOC.4.2", Name = @"Organization Name Type Code", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"CWE", DataTypeName = @"Coded With Exceptions", TableId = @"0204", TableName = @"Organizational Name Type", Description = @"A code that represents the type of name i.e., legal name, display name. Refer to User-defined Table 0204 - Organizational Name Type for suggested values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.4.2.1", Type = @"SubComponent", Position = @"LOC.4.2.1", Name = @"Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CWE.2. Different coding schemes will have different elements here.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.2", Type = @"SubComponent", Position = @"LOC.4.2.2", Name = @"Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The second component contains the descriptive or textual name of the identifier, e.g., ""myocardial infarction"" or ""X-ray impression"".", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.3", Type = @"SubComponent", Position = @"LOC.4.2.3", Name = @"Name Of Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"The third component contains the code for the name of the coding system from which the value in CWE.1 is obtained. Each coding system is assigned a unique identifier. As of v2.7 this component is required when CWE.1 is populated and CWE.14 is not populated. Both CWE.3 and CWE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CWE.3 and/or CWE.14, the ""Coding System"" component or the ""Coding System OID"" for the tuple. Refer to HL7 Table 0396 – Coding System in Chapter 2C, section ""Coding System Table"" for valid values. Refer to section 2.A.8.3, ""Name of Coding System (ID)"" for a discussion of coding system conventions.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.4", Type = @"SubComponent", Position = @"LOC.4.2.4", Name = @"Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies an alternate code. Analogous to CWE.1- Identifier. Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.5", Type = @"SubComponent", Position = @"LOC.4.2.5", Name = @"Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.6", Type = @"SubComponent", Position = @"LOC.4.2.6", Name = @"Name Of Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 - Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.4 is populated and CWE.17 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.6 and/or CWE.17, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.7", Type = @"SubComponent", Position = @"LOC.4.2.7", Name = @"Coding System Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.8", Type = @"SubComponent", Position = @"LOC.4.2.8", Name = @"Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.9", Type = @"SubComponent", Position = @"LOC.4.2.9", Name = @"Original Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.10", Type = @"SubComponent", Position = @"LOC.4.2.10", Name = @"Second Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.11", Type = @"SubComponent", Position = @"LOC.4.2.11", Name = @"Second Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.12", Type = @"SubComponent", Position = @"LOC.4.2.12", Name = @"Name Of Second Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.13", Type = @"SubComponent", Position = @"LOC.4.2.13", Name = @"Second Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.14", Type = @"SubComponent", Position = @"LOC.4.2.14", Name = @"Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.15", Type = @"SubComponent", Position = @"LOC.4.2.15", Name = @"Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.16", Type = @"SubComponent", Position = @"LOC.4.2.16", Name = @"Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.17", Type = @"SubComponent", Position = @"LOC.4.2.17", Name = @"Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.18", Type = @"SubComponent", Position = @"LOC.4.2.18", Name = @"Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.19", Type = @"SubComponent", Position = @"LOC.4.2.19", Name = @"Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.20", Type = @"SubComponent", Position = @"LOC.4.2.20", Name = @"Second Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.21", Type = @"SubComponent", Position = @"LOC.4.2.21", Name = @"Second Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.2.22", Type = @"SubComponent", Position = @"LOC.4.2.22", Name = @"Second Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.4.3", Type = @"Component", Position = @"LOC.4.3", Name = @"Id Number", Length = 0, Usage = @"W", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"Attention: The XON.3 component was deprecated as of v2.5 and the detail was withdrawn and removed from the standard as of v 2.7. Refer to XON.10 Organization Identifier.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.4", Type = @"Component", Position = @"LOC.4.4", Name = @"Identifier Check Digit", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"NM", DataTypeName = @"Numeric", TableId = null, TableName = null, Description = @"This component contains the digit, or digits, exclusive of the identifier in XON.1, usually calculated by applying an algorithm to all or some of the digits in the number, which may be used to test validity of the non-check-digit identifier. This component may also be used to transmit information intended to validate the veracity of the supplied identifier or the presenter of the identifier. For example, this component may be used to ensure that the presenter of a credit card is an authorized user of that card.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.5", Type = @"Component", Position = @"LOC.4.5", Name = @"Check Digit Scheme", Length = 3, Usage = @"O", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0061", TableName = @"Check Digit Scheme", Description = @"Contains the code identifying the check digit scheme employed. The check digit scheme codes are defined in HL7 Table 0061 - Check Digit Scheme.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.6", Type = @"Component", Position = @"LOC.4.6", Name = @"Assigning Authority", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = @"0363", TableName = @"Assigning Authority", Description = @"The assigning authority is a unique identifier of the system (or organization or agency or department) that creates the data. Assigning authorities are unique across a given HL7 implementation. Refer to User-defined Table 0363 - Assigning Authority for suggested values. Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment. By site agreement, implementers may continue to use User-defined Table 0300 – Namespace ID for the first sub-component.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.4.6.1", Type = @"SubComponent", Position = @"LOC.4.6.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.6.2", Type = @"SubComponent", Position = @"LOC.4.6.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.6.3", Type = @"SubComponent", Position = @"LOC.4.6.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.4.7", Type = @"Component", Position = @"LOC.4.7", Name = @"Identifier Type Code", Length = 5, Usage = @"O", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0203", TableName = @"Identifier Type", Description = @"A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the ""Assigning authority"" component. Refer to HL7 Table 0203 - Identifier Type for suggested values.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.8", Type = @"Component", Position = @"LOC.4.8", Name = @"Assigning Facility", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"HD", DataTypeName = @"Hierarchic Designator", TableId = null, TableName = null, Description = @"The place or location identifier where the identifier was first assigned to the person. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems. Note:When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.4.8.1", Type = @"SubComponent", Position = @"LOC.4.8.1", Name = @"Namespace Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"IS", DataTypeName = @"Coded Value For User-defined Tables", TableId = @"0300", TableName = @"Namespace ID", Description = @"The local coded item for the entity. The component intentionally remains associated with the IS data type in v2.7. User-defined Table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. Note: When the HD is used in a given segment (either as a field or as a component of another data type) this table may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.8.2", Type = @"SubComponent", Position = @"LOC.4.8.2", Name = @"Universal Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The HD’s second component, <universal ID> (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time within the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UIDs (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.8.3", Type = @"SubComponent", Position = @"LOC.4.8.3", Name = @"Universal Id Type", Length = 6, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0301", TableName = @"Universal ID Type", Description = @"The third component governs the interpretation of the second component of the HD. If the third component is a known UID refer to HL7 Table 0301 - Universal ID type for valid values, then the second component is a universal ID of that type.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.4.9", Type = @"Component", Position = @"LOC.4.9", Name = @"Name Representation Code", Length = 1, Usage = @"O", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0465", TableName = @"Name/Address Representation", Description = @"Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: This new component remains in “alphabetic” representation with each repetition of the field using these data types, i.e. even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address Representation Code for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.4.10", Type = @"Component", Position = @"LOC.4.10", Name = @"Organization Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the sequence of characters (the code) that uniquely identifies the item being referenced by XON.1 Organization Name. This component replaces XON.3 ID Number as of v 2.5. Note: The check digit and code identifying check digit scheme are null if Organization identifier is alphanumeric.", Sample = @"", FieldDatas = null }, } } _organizationNameLoc = new HL7V27Field { field = message[@"LOC"][4], fieldData = fieldData }; // check for repetitions if (_organizationNameLoc.field.FieldRepetitions != null && _organizationNameLoc.field.FieldRepetitions.Count > 0) { _organizationNameLoc.fieldRepetitions = HL7V2FieldGenerator.GenerateV27FieldRepetitions(_organizationNameLoc, fieldData); } return _organizationNameLoc; } } internal HL7V27Field _locationAddress; public HL7V27Field LocationAddress { get { if (_locationAddress != null) { return _locationAddress; } var fieldData = new HL7V27FieldData { Id = @"LOC.5", Type = @"Field", Position = @"LOC.5", Name = @"Location Address", Length = 0, Usage = @"O", Rpt = @"*", DataType = @"XAD", DataTypeName = @"Extended Address", TableId = null, TableName = null, Description = @"This field contains the address of the patient location, especially for use for outpatient clinic or office locations.", Sample = @"", Fields = new[] { new HL7V2FieldData { Id = @"LOC.5.1", Type = @"Component", Position = @"LOC.5.1", Name = @"Street Address", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"SAD", DataTypeName = @"Street Address", TableId = @"Street", TableName = @"Street", Description = @"This component contains the house number, apartment number, street name, street direction, P.O. Box number, and similar address information. ", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.5.1.1", Type = @"SubComponent", Position = @"LOC.5.1.1", Name = @"Street Or Mailing Address", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.1.2", Type = @"SubComponent", Position = @"LOC.5.1.2", Name = @"Street Name", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = null, Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.1.3", Type = @"SubComponent", Position = @"LOC.5.1.3", Name = @"Dwelling Number", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = null, Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.5.2", Type = @"Component", Position = @"LOC.5.2", Name = @"Other Designation", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.3", Type = @"Component", Position = @"LOC.5.3", Name = @"City", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = @"City", TableName = @"City", Description = @"This component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.4", Type = @"Component", Position = @"LOC.5.4", Name = @"State Or Province", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = @"State", TableName = @"State", Description = @"This component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.5", Type = @"Component", Position = @"LOC.5.5", Name = @"Zip Or Postal Code", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = @"ZipCode", TableName = @"Zip Code", Description = @"This component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.6", Type = @"Component", Position = @"LOC.5.6", Name = @"Country", Length = 3, Usage = @"O", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0399", TableName = @"Country Code", Description = @"This component specifies the country where the addressee is located. HL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. Refer to HL7 Table 0399 – Country Code for valid values.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.7", Type = @"Component", Position = @"LOC.5.7", Name = @"Address Type", Length = 3, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0190", TableName = @"Address Type", Description = @"This component specifies the kind or type of address. Refer to HL7 Table 0190 - Address Type for valid values. XAD.7 is required if there are multiple occurrences of XAD in a field.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.8", Type = @"Component", Position = @"LOC.5.8", Name = @"Other Geographic Designation", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component specifies any other geographic designation. It includes county, bioregion, SMSA, etc.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9", Type = @"Component", Position = @"LOC.5.9", Name = @"County/Parish Code", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"CWE", DataTypeName = @"Coded With Exceptions", TableId = @"0289", TableName = @"County/Parish", Description = @"A code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7). Allowable values: codes defined by government.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.5.9.1", Type = @"SubComponent", Position = @"LOC.5.9.1", Name = @"Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CWE.2. Different coding schemes will have different elements here.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.2", Type = @"SubComponent", Position = @"LOC.5.9.2", Name = @"Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The second component contains the descriptive or textual name of the identifier, e.g., ""myocardial infarction"" or ""X-ray impression"".", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.3", Type = @"SubComponent", Position = @"LOC.5.9.3", Name = @"Name Of Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"The third component contains the code for the name of the coding system from which the value in CWE.1 is obtained. Each coding system is assigned a unique identifier. As of v2.7 this component is required when CWE.1 is populated and CWE.14 is not populated. Both CWE.3 and CWE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CWE.3 and/or CWE.14, the ""Coding System"" component or the ""Coding System OID"" for the tuple. Refer to HL7 Table 0396 – Coding System in Chapter 2C, section ""Coding System Table"" for valid values. Refer to section 2.A.8.3, ""Name of Coding System (ID)"" for a discussion of coding system conventions.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.4", Type = @"SubComponent", Position = @"LOC.5.9.4", Name = @"Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies an alternate code. Analogous to CWE.1- Identifier. Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.5", Type = @"SubComponent", Position = @"LOC.5.9.5", Name = @"Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.6", Type = @"SubComponent", Position = @"LOC.5.9.6", Name = @"Name Of Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 - Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.4 is populated and CWE.17 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.6 and/or CWE.17, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.7", Type = @"SubComponent", Position = @"LOC.5.9.7", Name = @"Coding System Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.8", Type = @"SubComponent", Position = @"LOC.5.9.8", Name = @"Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.9", Type = @"SubComponent", Position = @"LOC.5.9.9", Name = @"Original Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.10", Type = @"SubComponent", Position = @"LOC.5.9.10", Name = @"Second Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.11", Type = @"SubComponent", Position = @"LOC.5.9.11", Name = @"Second Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.12", Type = @"SubComponent", Position = @"LOC.5.9.12", Name = @"Name Of Second Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.13", Type = @"SubComponent", Position = @"LOC.5.9.13", Name = @"Second Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.14", Type = @"SubComponent", Position = @"LOC.5.9.14", Name = @"Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.15", Type = @"SubComponent", Position = @"LOC.5.9.15", Name = @"Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.16", Type = @"SubComponent", Position = @"LOC.5.9.16", Name = @"Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.17", Type = @"SubComponent", Position = @"LOC.5.9.17", Name = @"Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.18", Type = @"SubComponent", Position = @"LOC.5.9.18", Name = @"Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.19", Type = @"SubComponent", Position = @"LOC.5.9.19", Name = @"Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.20", Type = @"SubComponent", Position = @"LOC.5.9.20", Name = @"Second Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.21", Type = @"SubComponent", Position = @"LOC.5.9.21", Name = @"Second Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.9.22", Type = @"SubComponent", Position = @"LOC.5.9.22", Name = @"Second Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.5.10", Type = @"Component", Position = @"LOC.5.10", Name = @"Census Tract", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"CWE", DataTypeName = @"Coded With Exceptions", TableId = @"0288", TableName = @"Census Tract", Description = @"A code that represents the census tract in which the specified address resides. User-defined Table 0288 - Census Tract is used as the HL7 identifier for the user-defined table of values for this component. Allowable Values: codes defined by government.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.5.10.1", Type = @"SubComponent", Position = @"LOC.5.10.1", Name = @"Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CWE.2. Different coding schemes will have different elements here.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.2", Type = @"SubComponent", Position = @"LOC.5.10.2", Name = @"Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The second component contains the descriptive or textual name of the identifier, e.g., ""myocardial infarction"" or ""X-ray impression"".", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.3", Type = @"SubComponent", Position = @"LOC.5.10.3", Name = @"Name Of Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"The third component contains the code for the name of the coding system from which the value in CWE.1 is obtained. Each coding system is assigned a unique identifier. As of v2.7 this component is required when CWE.1 is populated and CWE.14 is not populated. Both CWE.3 and CWE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CWE.3 and/or CWE.14, the ""Coding System"" component or the ""Coding System OID"" for the tuple. Refer to HL7 Table 0396 – Coding System in Chapter 2C, section ""Coding System Table"" for valid values. Refer to section 2.A.8.3, ""Name of Coding System (ID)"" for a discussion of coding system conventions.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.4", Type = @"SubComponent", Position = @"LOC.5.10.4", Name = @"Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies an alternate code. Analogous to CWE.1- Identifier. Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.5", Type = @"SubComponent", Position = @"LOC.5.10.5", Name = @"Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.6", Type = @"SubComponent", Position = @"LOC.5.10.6", Name = @"Name Of Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 - Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.4 is populated and CWE.17 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.6 and/or CWE.17, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.7", Type = @"SubComponent", Position = @"LOC.5.10.7", Name = @"Coding System Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.8", Type = @"SubComponent", Position = @"LOC.5.10.8", Name = @"Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.9", Type = @"SubComponent", Position = @"LOC.5.10.9", Name = @"Original Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.10", Type = @"SubComponent", Position = @"LOC.5.10.10", Name = @"Second Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.11", Type = @"SubComponent", Position = @"LOC.5.10.11", Name = @"Second Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.12", Type = @"SubComponent", Position = @"LOC.5.10.12", Name = @"Name Of Second Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.13", Type = @"SubComponent", Position = @"LOC.5.10.13", Name = @"Second Alternate Coding System Version Id", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.14", Type = @"SubComponent", Position = @"LOC.5.10.14", Name = @"Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.15", Type = @"SubComponent", Position = @"LOC.5.10.15", Name = @"Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.16", Type = @"SubComponent", Position = @"LOC.5.10.16", Name = @"Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.17", Type = @"SubComponent", Position = @"LOC.5.10.17", Name = @"Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.18", Type = @"SubComponent", Position = @"LOC.5.10.18", Name = @"Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.19", Type = @"SubComponent", Position = @"LOC.5.10.19", Name = @"Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.20", Type = @"SubComponent", Position = @"LOC.5.10.20", Name = @"Second Alternate Coding System Oid", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.21", Type = @"SubComponent", Position = @"LOC.5.10.21", Name = @"Second Alternate Value Set Oid", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where ""####"" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.10.22", Type = @"SubComponent", Position = @"LOC.5.10.22", Name = @"Second Alternate Value Set Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"This component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated.", Sample = @"", FieldDatas = null },} }, new HL7V2FieldData { Id = @"LOC.5.11", Type = @"Component", Position = @"LOC.5.11", Name = @"Address Representation Code", Length = 1, Usage = @"O", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0465", TableName = @"Name/Address Representation", Description = @"Different <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Note: Also note that this new component remains in ""alphabetic"" representation with each repetition of the fields using these data types. I.e. even though the address may be represented in an ideographic character set, this component will remain represented in an alphabetic character set. Refer to HL7 Table 0465 – Name/address Representation for valid values. In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.12", Type = @"Component", Position = @"LOC.5.12", Name = @"Address Validity Range", Length = 0, Usage = @"W", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"Attention: The XAD.12 component was retained for backward compatibility as of v2.5 and the detail was withdrawn and removed from the standard as of v2.7. Refer to 2.A.86.13, ""Effective Date (DTM)"" and 2.A.86.14, ""Expiration Date (DTM)"" components.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.13", Type = @"Component", Position = @"LOC.5.13", Name = @"Effective Date", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"The first date, if known, on which the address is valid and active for the ‘owning’ entity.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.14", Type = @"Component", Position = @"LOC.5.14", Name = @"Expiration Date", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"DTM", DataTypeName = @"Date/time", TableId = null, TableName = null, Description = @"The last date, if known, on which the address is valid and active for the ‘owning’ entity.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15", Type = @"Component", Position = @"LOC.5.15", Name = @"Expiration Reason", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"CWE", DataTypeName = @"Coded With Exceptions", TableId = @"0616", TableName = @"Address Expiration Reason", Description = @"This identifies why this address was marked as ""ended"". Refer to User-defined Table 0616 – Address Expiration Reason for valid values.", Sample = @"", FieldDatas = new []{new HL7V2FieldData { Id = @"LOC.5.15.1", Type = @"SubComponent", Position = @"LOC.5.15.1", Name = @"Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The first component contains the sequence of characters (the code) that uniquely identifies the item being referenced by the CWE.2. Different coding schemes will have different elements here.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15.2", Type = @"SubComponent", Position = @"LOC.5.15.2", Name = @"Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The second component contains the descriptive or textual name of the identifier, e.g., ""myocardial infarction"" or ""X-ray impression"".", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15.3", Type = @"SubComponent", Position = @"LOC.5.15.3", Name = @"Name Of Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"The third component contains the code for the name of the coding system from which the value in CWE.1 is obtained. Each coding system is assigned a unique identifier. As of v2.7 this component is required when CWE.1 is populated and CWE.14 is not populated. Both CWE.3 and CWE.14 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the codingSystem as specified in CWE.3 and/or CWE.14, the ""Coding System"" component or the ""Coding System OID"" for the tuple. Refer to HL7 Table 0396 – Coding System in Chapter 2C, section ""Coding System Table"" for valid values. Refer to section 2.A.8.3, ""Name of Coding System (ID)"" for a discussion of coding system conventions.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15.4", Type = @"SubComponent", Position = @"LOC.5.15.4", Name = @"Alternate Identifier", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"A sequence of characters that uniquely identifies an alternate code. Analogous to CWE.1- Identifier. Usage Notes: The Alternate Identifier is used to represent the local or user seen code as described. If present, it obeys the same rules of use and interpretation as described for component 1. If both are present, the identifiers in component 4 and component 1 should have exactly the same meaning, i.e., they should be exact synonyms.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15.5", Type = @"SubComponent", Position = @"LOC.5.15.5", Name = @"Alternate Text", Length = 0, Usage = @"O", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"The descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15.6", Type = @"SubComponent", Position = @"LOC.5.15.6", Name = @"Name Of Alternate Coding System", Length = 12, Usage = @"C", Rpt = @"1", DataType = @"ID", DataTypeName = @"Coded Value For Hl7 Defined Tables", TableId = @"0396", TableName = @"Coding System", Description = @"Identifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 - Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.4 is populated and CWE.17 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.6 and/or CWE.17, the ""Coding System"" component or the ""Coding System OID"", for the tuple.", Sample = @"", FieldDatas = null }, new HL7V2FieldData { Id = @"LOC.5.15.7", Type = @"SubComponent", Position = @"LOC.5.15.7", Name = @"Coding System Version Id", Length = 0, Usage = @"C", Rpt = @"1", DataType = @"ST", DataTypeName = @"String Data", TableId = null, TableName = null, Description = @"This component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may