5th Standard Dictionary

[Raymond Freedman]

HMISdata standards have been established by the U.S. Department of Housing and Urban Development (HUD), the U.S. Department of Health and Human Services (HHS), and the U.S. Department of Veterans Affairs (VA) to allow for standardized data collection across systems about individuals and families experiencing homelessness. The HMIS Data Dictionary and the HMIS Data Standards Manual are the documentation of requirements for the programming and use of all HMIS and comparable database software.

The HMIS Data Standards Manual supports data collection and reporting efforts of HMIS Leads/System Administrators, Continuums of Care (CoCs), and HMIS End Users to help them understand the data elements that are required in an HMIS to meet participation and reporting requirements established by HUD and the federal partners. The HMIS Data Dictionary is designed for HMIS vendors and HMIS Leads/System Administrators to identify the data elements required in an HMIS and understand the function and specific use of each element by the appropriate federal partner. The Interactive HMIS Data Standards Tool is an interactive, web-based combination of the guidance from both the HMIS Data Manual and the HMIS Data Dictionary.

The NTDS standardizes trauma registry data collection to improve patient care and trauma training as well as define a standard on which to measure care. Hospitals across the United States are able to share the key elements of their data collection nationally.

For all practical purposes, the Data Standard (formerly known as the National Trauma Registry or NTR) is a dataset defining standardized data elements collected by the American College of Surgeons (ACS) within the NTDB and ACS Trauma Quality Improvement Program (TQIP). This standardized dataset includes only core variables that would prove useful if aggregated on a national level.

Each individual hospital trauma registry will likely collect additional variables important to patient care. However, the NTDB Data Standard should be collected by all hospitals and submitted to the NTDB. The NTDB is the national repository used to store trauma data from potentially every state in the U.S.

The NTDB releases the National Trauma Data Standard (formerly National Trauma Registry) data dictionary, developed in collaboration with HRSA, state trauma managers, trauma registry vendors, and other stakeholders in the trauma community.

The NAACCR Data Standards and Data Dictionary is intended for hospital and central cancer registries, programmers, and analysts. It provides detailed specifications and codes for each data item in the NAACCR data exchange record layout.

Click here to go to the archive of versions of Standards Volume II prior to Version 15. The archive includes the Volume II PDF, Access database, and revision page(s) for each of the previous versions.

The NAACCR Standards Implementation Timeline provides deadlines to facilitate successful implementation of revisions to NAACCR Standards for Cancer Registries Volume II, Data Standards and Data Dictionary. Revisions to the standards include, but are not limited to, changes to existing data items and proposing new data items for implementation.

Any change to standards has an impact on registry operations, funding agencies, and users of the data. A multidisciplinary group from central registries, software vendors, and standard setters developed a change management process. The purpose of the change management process is to facilitate successful implementation of change to cancer registry data collection standards, requirements, and systems. Mid-Level Tactical Group (MLTG) will review, evaluate and approve requests for change through an assessment process intended to determine the feasibility of the change and assess the impact on the cancer surveillance community.

This document may be used as an implementation guide for the NAACCR standard CRC CHECKSUM. This field will help ensure integrity of NAACCR records when they are transmitted electronically. The CRC CHECKSUM field should be implemented beginning with NAACCR Record Layout Version 7.

NCHS codes are commonly used to identify place of birth on death certificates. The NCHS to ISO Code Crosswalk spreadsheet provides the ISO equivalents, where they exist, for NCHS codes. The ISO alpha-3 codes are used for the data items below, effective with Volume II, Version 13.

The NAACCR Data Standards and Data Dictionary content is developed collaboratively by standard setting agencies including the CDC NPCR, NCI SEER, American College of Surgeons, and the Canadian Council of Cancer Registries

Center-to-center (C2C) communications spans the entire ITS domain, covering the exchange of data between computers physically located in different transportation management center facilities. Such facilities include: traffic management centers, transit management centers, public safety, incident management centers, parking management centers, and so forth. C2C standards enable this data exchange, specifying what information is exchanged, how and when it is exchanged, and the underlying transport mechanisms. C2C standards can be divided into two categories: (1) the message and data content, and (2) the rules for exchanging the messages and data. The two categories of standards work together to successfully exchange meaningful ITS-related information.

Consensus-based working groups from American Association of State Highway and Transportation Officials (AASHTO), Institute of Transportation Engineers, (ITE) and National Electrical Manufacturers Association (NEMA) have been chartered with developing a set of underlying Center-to-Center (C2C) communications standards for the transportation community. The two categories for C2C communications standards are generally referenced as informational and protocol standards. The Traffic Management Data Dictionary (TMDD) is an information standard, while National Transportation Communications for ITS Protocol (NTCIP) standards address protocol standards. In general, NTCIP organizes its standards using a layered approach (as shown in Figure 1), similar to the ISO Open System Interconnection (OSI) framework model. While message/data standards address the Information Level, protocol standards primarily address the Applications, Transport, and Subnetwork Levels.

The TMDD for Traffic Management Center-to-Center Communication standards were developed by a joint ITE and AASHTO working group, which resulted in two types of Information Level encodings (XML and ASN.1). The type of encoding used affects the selection of possible protocol level standards. TMDD v3.03b is the latest version of the standard and it defines both types of encodings. The TMDD standard defines the information (messages) and sequence of messages (Dialogs) that are shared between centers, while using the NTCIP Application, Transport, and Subnetwork Levels to define how the information is to be carried.

The first version of the TMDD Standard (v1.0) focused on the development of a data dictionary for traffic management systems. It further used those data elements in the construction of message sets, called Message Set for External Traffic Management Center Communications (MS/ETMCC) to exchange information regarding traffic conditions, devices, and incidents, as well as support for shared control of ITS devices between systems. Consequently, version 1 contained 2 parts: (1) the TMDD and (2) the MS/ETMCC. Version 2.1 corrected deficiencies in the Standard and applied the Systems Engineering process1 by identifying user operational needs and developing requirements and dialogs. Version 2.1 also combined the TMDD and MS/ETMCC standards into one standard.

This new TMDD v3.03b reflects the Systems Engineering process approach, restructures the design for the standard, and has added new features. In addition, the TMDD V3.03b has been used as the basis for the development of a reference implementation that can be used by agencies and developers to verify conformance to the TMDD standard. During that development, the TMDD standard was adjusted to correct ambiguities, missing entries in the various tables for consistency, and clarification of the conformance statements.

TMDD v3.03b ascribes a Systems Engineering Process to the Standard. A linkage is created between user-identified operational needs and the system requirements to support those needs. This Systems Engineering Process enhances the usability of the Standard to create comprehensive specifications for procurements.

USDOT strongly encourages State and local agencies to use the TMDD v3.03b Standard. The Standard is mature and offers immediate benefits for agencies by enabling interoperability between centers. Additionally, TMDD v3.03b supports both the NTCIP 2304 Standard covering DATEX/ASN implementations and the NTCIP 2306 Standard covering WSDL/XML implementations. Check the resources in the "Standards Resources" section below for help with systems assessment, migration, integration, and procurement. In particular, assistance is available to help implement standards-based TMDD v3.03b.

A web-based reference implementation called the Center-to-Center Reference Implementation (RI) is being developed to assist users in use of the Standard in implementations. This tool can be used to verify system conformance to the Standard. It is anticipated to be available in early 2014.

Professional Capacity Building (PCB) training for ITS Standards specific for TMDD v3.0 procurements and testing is being developed. This training will be modular and is available on the PCB/Standards and ITE sites. Specific modules and anticipated availability are as follows:

Region-wide distribution of transportation management information is a key function at the core of a transportation agency's ability to generate benefits from ITS. Agencies are executing C2C projects across the country primarily using the WSDL/XML. Therefore, TMDD v3.03b is extremely beneficial to users. It will also support DATEX/ASN as the underlying communication protocols, however; most systems today are using the web services approach identified in NTCIP 2306.

3a8082e126