XML User Dictionary

XML User Dictionary

Custom User-Dictionaries

Central registries with locally defined data items are expected to create and provide user dictionaries to vendors by October 1, 2021.

A user dictionary is an XML file that defines key metadata about NAACCR data items as they relate to a NAACCR XML data exchange file, their valid XML parent elements, and processing rules. The user dictionaries should include all current registry-specific data items, and any new items planned for implementation in NAACCR v22. This will help vendors prepare customized files and software applications and reduce the chance of delay for deployment of NAACCR v22 software.

 

All central registries should do the following:

  1. Determine if a user dictionary needs to be created or updated (refer to FAQ)
    1. If your registry determines it does not need a user dictionary, you should still use the form on the XML Dictionary Submission Clearinghouse(MyNAACCR Login Required) to communicate this information (e.g. [Your Registry] is not creating a user dictionary for V22)
  2. Review existing registry-specific data items to determine if their reporting needs have changed and remove items that are no longer needed.
  3. Identify and define new registry-specific data items for inclusion.
  4. Download and fill out the Data Dictionary Details Template with details of all registry-specific data items.
  5. Use the Data Dictionary Details Template and a recommended software tool  to create an XML User Dictionary with all registry-specific data items
  6. Validate the user dictionary (refer to FAQ)
  7. Upload the completed Data Dictionary Details Template and XML User Dictionary to the XML Dictionary Submission Clearinghouse(MyNAACCR Login Required).

 

Important Links

Data Dictionary Details Template

XML Dictionary Submission Clearinghouse(MyNAACCR Login Required)

NAACCR Data Exchange Standard: XML Specifications

NAACCR XML Homepage

NAACCR Edits Metafile Clearinghouse

Organization NameUploaded FilesUpload Date/TimeUser Account
Alaska XML User Dictionary
Data Dictionary Details
2020-10-05David O'Brien
Alaska Native Tumor Registry XML User Dictionary
Data Dictionary Details
2021-09-13Garrett Zimpelman
Arkansas XML User Dictionary
Data Dictionary Details
2020-09-28 Christopher Fisher
California XML User Dictionary
Data Dictionary Details
2021-02-11 Ben Wormeli
CoC XML User Dictionary
Data Dictionary Details
2021-02-11 Jeff Reed
Colorado XML User Dictionary
Data Dictionary Details
2020-10-01 John Arend
Connecticut XML User Dictionary
Data Dictionary Details
2021-08-10Cathryn Phillips
Delaware Delaware Cancer Registry is not creating a user dictionary at this time2020-02-01 Elaine Flores
Florida XML User Dictionary
Data Dictionary Details
2020-11-12 Gary Levin
GeorgiaGeorgia Cancer Registry is not creating a user dictionary at this time2020-09-28 Jan Kres
Idaho (CDRI) XML User Dictionary
Data Dictionary Details
2021-06-28 Randi Rycroft
IllinoisNo V22 state-specific XML dictionary for Illinois State Cancer Registry2021-09-13Larry Hebert
Iowa XML User Dictionary
Data Dictionary Details
2020-12-22 Jason Brubaker
IndianaIndiana is not creating a user dictionary.2020-09-25 shebbar@isdh.in.gov
Kansas XML User Dictionary
Data Dictionary Details
2021-03-05 Evan Reitter
KentuckyKentucky is not creating a user dictionary.2020-10-16 Isaac Hands
Louisiana XML User Dictionary2020-02-11 Brent Mumphrey
MaineMaine is not creating a user dictionary2021-09-13Carolyn Bancroft
Maryland XML User Dictionary
XML User Dictionary
2020-01-29 Rebecca LI
Michigan XML User Dictionary
Data Dictionary Details
2021-08-10 Stacey Coltrain
MinnesotaMinnesota is not creating a user dictionary at this time.2020-11-12 Mona Highsmith
Missouri XML User Dictionary
Data Dictionary Details
2020-09-24 Nancy Rold
Montana XML User Dictionary
Data Dictionary Details
2020-11-30 Debbie Lemons
NebraskaThe Nebraska Cancer Registry doesn't have state-specific data items and is not creating a user dictionary.2021-09-13Lifeng Li
New Hampshire XML User Dictionary
Data Dictionary Details
2020-10-02 Cathleen Geiger
New JerseyNew Jersey is not creating a user dictionary at this time2021-09-13Kamal Johnson
New Mexico XML User Dictionary
Data Dictionary Details
2021-05-03Barbara Evans
New York XML User Dictionary
Data Dictionary Details
2020-10-19 Stefan Winden
North Carolina XML User Dictionary
Data Dictionary Details
2021-05-10Brian Knox
North Dakota XML User Dictionary
Data Dictionary Details
2021-06-28Yung Zeng
Ohio XML User Dictionary
Data Dictionary Details
10/01/2020 Kaitlin Kruger
Oklahoma Oklahoma Cancer Registry is not creating a user dictionary at this time2020-12-16 Christy Dabbs
Ontario XML User Dictionary
Data Dictionary Details
2020-11-24 Isabela Olaru
Pennsylvania XML User Dictionary
Data Dictionary Details
2020-12-23 Christina McEachern
PRCCR XML User Dictionary
Data Dictionary Details
2020-10-28 Janos Baksa
Rhode Island XML User Dictionary
Data Dictionary Details
2021-01-25 Lisa Marie Garcia
South CarolinaSouth Carolina is not creating a user dictionary.2020-11-24 Michael Castera
South DakotaSouth Dakota does not plan to have state specific items.2021-09-13Kay Dosch
Tennessee Tennessee is not creating a user dictionary at this time.2020-11-13 Anne Llewellyn
Utah XML User Dictionary
Data Dictionary Details
2020-09-02 Valerie Yoder
Vermont Data Dictionary Details2020-09-28Alison Johnson
Virginia XML User Dictionary
2020-09-06 Larry Kirkland
West VirginiaWest Virginia Cancer Registry is not creating a user dictionary at this time2020-02-01 Myra Fernatt
WisconsinWisconsin Cancer Registry is not creating a user dictionary at this time2021-09-13Jenna Staehler

Frequently Asked Questions

  • Yes, if your registry transmits or receives abstracts with data items that are not defined in the NAACCR base dictionary (Data Standards & Data Dictionary, Volume II)
    • If a standard setter requires a new field for annual data submissions or special projects, they typically provide a user dictionary
  • Yes, if your central registry database vendor requires a user dictionary to define custom data items for central registry use only.
  • No, if your registry only transmits or receives abstracts with data items that are defined in the NAACCR base dictionary (Data Standards & Data Dictionary, Volume II). Please submit the form indicating your registry does not maintain a user dictionary.
  • No, if your user dictionary only contained NPCR data items and you won’t continue collecting any of them. Please submit the XML Dictionary Submission Clearinghouse form indicating your registry did not create a user dictionary.
  • If you receive or transmit NAACCR Vol V pathology items in abstracts, you should not include them in your user dictionary. You should inform your vendors that you use the NAACCR Vol V pathology dictionary (under development)

 

 

  • Yes, if you transmit or receive those data items in NAACCR abstracts received from reporting facilities.
  • No, if you don’t require that data item in abstracts from reporting facilities and don’t include that field in abstract submissions to other agencies. For example your registry database might contain a “Do Not Contact” field for patients.
  • Some vendors of central registry software may require the custom data items for central registry use only be included in a user dictionary for editing, extracting data, etc. These should be indicated in the Data Dictionary Details Template’s Required Status from Reporting Facilities column.
  • The Data Dictionary Details Template which will prompt you for the following details. Refer to NAACCR Data Exchange Standard for more details on these attributes.
  • NAACCR ID
    • Maximum 32 characters, start with lowercase, include no punctuation
    • For example, BIRTHPLACE—STATE’s NAACCR ID is birthplaceState
  • Item Name
  • Item Number (recommended 9000+)
  • Parent XML Element (Tumor, Patient, NaaccrData)
  • Length
  • Record Types (A, M, C, I)
  • Data type (digits, alpha, mixed, numeric, date, text)
  • Additionally, the following items are not ultimately defined in the user dictionary, but are included in the Data Dictionary Details Template as they are critical information for software vendors
    • Codes and description
    • Required Status from Reporting Facilities
  • The NAACCR XML workgroup recommends registries review their user dictionary or decision not to create a user dictionary with the release of every NAACCR version
  • Five NPCR data items moved to the Version 22 base dictionary. If your current user dictionary contains any of these data items you must create a new one for version 22.
    • EDP MDE Link Date [530], EDP MDE Link [531], IHS PRCDA [194], Urban Indian Health Organization (UIHO) [284], UIHO City [285]
  • NPCR will no longer be requiring or requesting the following data items. Cancer registries can continue to collect the items if desired by defining them in a user dictionary.
    • Height, Weight, Tobacco Use Cigarettes, Tobacco Use Other Smoke, Tobacco Use Smokeless, Tobacco Use NOS, ECC Flag
    • Note that NPCR has defined a new data item for Version 22, Tobacco Use Smoking Status [344], that is a combination and new definition of the four tobacco data items previously included in the NPCR-Specific Field. Tobacco Use Smoking Status [344] is included in the Version 22 NAACCR base dictionary.
    • Open or register your dictionary in a recommended software tool
    • Open your user dictionary in a browser (Chrome, Firefox) and check:
      • Verify the Custom Uniform Resource Identifier (URI) follows naming conventions specified in the XML Data Exchange Standard and includes user dictionary version
      • Ensure all data items and corresponding attributes for your dictionary are included in your Data Dictionary Details Template
  • According to the XML Data Exchange Standard, the filename for a user dictionary should match the last part of the dictionary Uniform Resource Identifier (URI).
    • For example, if the URI is https://mystate.gov/state-cancer-registry/mystate-naaccrdictionary-v1.xml the filename is mystate-naaccrdictionary-v1.xml
  • URI is a unique string that defines the dictionary. It acts as an identifier and is referenced by the NAACCR XML data files. User dictionaries should reference the organization that created them.
  • According to the XML Data Exchange Standard, the custom user dictionaries use the format [custom URI]/[organization]-naaccr-dictionary[-xxx][-v#.#].xml where xxx is the corresponding NAACCR version, which is only required if the custom dictionary depends on a specific NAACCR version. v#.# is your organization’s version of the dictionary (semantic versioning recommended). The suggested custom user dictionary’s file name is the same as the end of this URI.
    • For example: https://mystate.gov/state-cancer-registry/mystate-naaccrdictionary-180-v1.xml
  • Though they look like internet addresses, they do not need to point to an existing web location.

Help with User Dictionaries

NAACCR has established this website as a User Dictionary Clearinghouse to show examples of user dictionaries from other central registries and provide the Data Dictionary Details Template that will help central registries gather information needed to define their own XML User Dictionary. Central registries with registry-specific data items are encouraged to fill out the Excel template and upload it to the XML Dictionary Submission Clearinghouse with a corresponding XML User Dictionary so that registry software vendors can get access to these required files and deploy software changes in a timely manner.

 

Once uploaded, these files will be publicly available with the intent of allowing registry software vendors the registry-specific customizations, including codes and definitions, for registry-specific data items in their software. While codes and descriptions and item required status are not defined in a user dictionary, central registry-assigned codes and descriptions must be shared with vendors in order to generate look up tables in software displays.

 

Please note that the Data Dictionary Details Template does not take the place of a user dictionary. The template provides a reference with information needed to successfully implement registry-specific data items in software with the end goal of bringing all of the information together in one place to create a user dictionary file. Once the spreadsheet is filled out, central registries with registry-specific data items must also create and maintain the actual XML user dictionary file. The workgroup recommends that each registry store a copy of past user dictionaries at their registry, as this Clearinghouse only publishes the most recent upload per for each registry.

 

Additional help can be received by posting to the NAACCR XML Forum, which is monitored by the NAACCR XML Data Exchange Workgroup

Copyright © 2018 NAACCR, Inc. All Rights Reserved | naaccr-swoosh-only See NAACCR Partners and Sponsors