US Core Implementation Guide
5.0.1 - STU5 Release US

This page is part of the US Core (v5.0.1: STU5) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: USPS Two Letter Alphabetic Codes

Official URL: Version: 5.0.1
Active as of 2019-05-21 Computable Name: UspsTwoLetterAlphabeticCodes
Other Identifiers: : urn: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

All codes in this table are from the system

  ASAmerican Samoa
  DCDistrict of Columbia
  FMFederated States of Micronesia
  MHMarshall Islands
  NHNew Hampshire
  NJNew Jersey
  NMNew Mexico
  NYNew York
  NCNorth Carolina
  NDNorth Dakota
  MPNorthern Mariana Islands
  PRPuerto Rico
  RIRhode Island
  SCSouth Carolina
  SDSouth Dakota
  VIVirgin Islands
  WVWest Virginia
  AEArmed Forces Europe, the Middle East, and Canada
  APArmed Forces Pacific
  AAArmed 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