US Core Implementation Guide
7.0.0 - STU7 United States of America flag

US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 7.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of and changes regularly. See the Directory of published versions

ValueSet: USPS Two Letter Alphabetic Codes

Official URL: Version: 7.0.0
Standards status: Trial-use Maturity Level: 3 Computable Name: UspsTwoLetterAlphabeticCodes
Other Identifiers: OID:2.16.840.1.113883.4.642.3.40

Copyright/Legal: On July 1, 1963, the Post Office Department implemented the five-digit ZIP Code, which was placed after the state name in the last line of an address. To provide room for the ZIP Code, the Department issued two-letter abbreviations for all states and territories. Publication 59, Abbreviations for Use with ZIP Code, issued by the Department in October 1963. There is no copyright restriction on this value set.

This value set defines two letter USPS alphabetic codes.


Logical Definition (CLD)

  • Include all codes defined in



This value set contains 62 concepts.

  AS Samoa
  DC of Columbia
  FM States of Micronesia
  MH Islands
  NH Hampshire
  NJ Jersey
  NM Mexico
  NY York
  NC Carolina
  ND Dakota
  MP Mariana Islands
  PR Rico
  RI Island
  SC Carolina
  SD Dakota
  VI Islands
  WV Virginia
  AE Forces Europe, the Middle East, and Canada
  AP Forces Pacific
  AA Forces Americas (except Canada)

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code