If a facility site is known by more than one name within your local system(s), or by a name other than the one that is in the EIS Facility Inventory, you may report the alternative name(s) to the EIS using the AlternativeFacilityName component. Please note that if a name change has occurred in your local system, you should submit the new name in the FacilitySite component, and you should also include the AlternativeFacilityName component with the previous name.
Updates vs. new records. If you submit an alternative facility site name for an identified facility site, this information will be added to the inventory as an additional name by which the facility site is known. This does NOT constitute a name change when you report your data directly through the AlternativeFacilityName component. The facility site still retains its primary facility site name as indicated in the FacilitySite component.
Impact of incomplete information or critical errors. If there are critical errors relating to the dates reported, the dates will not be stored; all other data in the record will be accepted.
Complex data type which Identifies any alternative names by which the facility site is known or has been known.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity | 299 | Alternative Name Present | The alternative name is required when reporting the alternative facility name component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
|---|---|---|---|---|
| 291 | Alternative Name Data Type | Maximum allowable width of 80 characters. | Format | Critical |
Code defining the organization associated with the FacilityIdentifier.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 148 | Program System Code Present for Alternative Name | A program system code is required when reporting the alternative facility name component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 232 | Program System Code Valid for Alternative Facility Name | Must match value in list of registered codes. | Code | Critical |
| 1672 | Facility Alternative Name Unique | The combination of facility alternative name and program system code must be unique within a facility. | Conditional | Critical |
| 1389 | Unique Facility and Alternative Facility Identifier Per Program System Code | Active Alternative Facility Identifiers must be unique within a Program System Codes and a FIPS code. | Conditional | Critical |
Description of the alternative name.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 147 | Alternative Name Type Text Present | The alternative name type text is required when reporting the alternative facility name component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 292 | Alternative Name Type Text Data Type | Maximum allowable width of 20 characters. Longer submissions will be truncated. | Format | Warning |
The date the identifier became effective.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 44 | Effective Date Range for Alternative Facility Name | The effective date range for an alternative facility name is 01/01/1900 to 12/31/2050. | Range | Critical |
| 293 | Effective Date for Alternative Facility Name Data Type | Date in the format of YYYY-MM-DD. | Format | Critical |