By Eric Andrew Kristof, RN, CAHIMS | Healthcare IT Professional | HIMSS Arkansas Chapter Member
About This Series: The HIMSS Word of The Day is a running blog series drawing from the HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025) — the authoritative reference for healthcare IT professionals and the primary study resource for CAHIMS and CPHIMS certification. Each post paraphrases the term in plain language, grounds it in real-world healthcare IT context, and adds a bedside nursing perspective you won’t find in a textbook.
📖 The Term: USHIK (United States Health Information Knowledgebase)
Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)
🔍 Plain-Language Definition
The HIMSS Dictionary describes USHIK (United States Health Information Knowledgebase) in the past tense. It was a registry that listed data elements defined by standards groups, with AHRQ (the Agency for Healthcare Research and Quality) providing support, and the Dictionary notes that the site is archived.
AHRQ’s own page confirms and expands on that. It describes USHIK as an online, publicly accessible registry and repository of health care metadata, specifications, and standards. Its content came from many initiatives, including administrative items and other artifacts for the Centers for Medicare & Medicaid Services (CMS) quality reporting programs, state all-payer claims databases, the Children’s Electronic Health Record Format, and the AHRQ Patient Safety Common Formats, as well as standards from Accredited Standards Committee X12, the National Council for Prescription Drug Programs (NCPDP), and the Health Information Technology Standards Panel (HITSP).
A metadata registry is a catalog of data about data. For each data element, it records its name, its definition, its allowed values, and how it is represented, so people can see whether two systems mean the same thing by the same label. AHRQ says USHIK’s core components and attributes were based on Part 3 of the ISO/IEC 11179 standard for metadata registries. The agency describes USHIK as a neutral repository of metadata from authoritative sources: it did not try to change the content, but gave users a structured way to view and compare it.
AHRQ lists the goals of USHIK as providing a tool to compare metadata across standards, a one-stop display for researchers, clinicians, policymakers, and developers, support for HHS efforts to improve the quality of data used in care, harmonization across standards, and support for HHS standards-based initiatives. A separate AHRQ digital health project page lists the 2011 to 2014 support work and names collaborating federal partners, including CMS, the Department of Defense’s Military Health System, the National Cancer Institute, and the HHS Office of the Assistant Secretary for Planning and Evaluation.
AHRQ now says USHIK is being archived because some of the metadata is maintained on other sites, so duplication is unnecessary. That is a practical reminder for anyone who finds an old reference to it: the idea lives on, but the place to look has moved.
| Former USHIK content | Where AHRQ says it can be found now |
|---|---|
| X12 and NCPDP standards metadata | The X12 and NCPDP websites |
| AHRQ Patient Safety Common Formats | The AHRQ Patient Safety Organization Privacy Protection Center |
| CMS quality reporting and eCQM metadata | The Electronic Clinical Quality Improvement (eCQI) Resource Center, with value sets at the NLM Value Set Authority Center |
| State all-payer claims database specifications | Individual state APCD websites |
| HITSP materials | No longer available from other sites, according to AHRQ |
| Children’s EHR Format metadata and final report | Not available from other sites, according to AHRQ |
⚠️ Exam Alert: USHIK was a metadata registry for comparing data elements across standards, and it is archived. It is not a terminology like SNOMED CT, a value set repository like the NLM Value Set Authority Center, or a data warehouse. Do not confuse it with the UMLS, which links terminologies, or with the cancer Data Standards Registry and Repository (caDSR), a separate metadata registry run by the National Cancer Institute.
🌐 Why It Matters: Real-World Healthcare IT Context
USHIK is a tool that no longer operates, so this section draws on AHRQ’s pages, which were read for this post, and on peer-reviewed papers about metadata registries. The AHRQ pages describe what the registry held and why it was archived. The papers show why shared data definitions matter, and how other registries have been built and used. Each source was checked against its published text or abstract, and the type of study is noted.
What AHRQ says it held. AHRQ’s page lists six portals: Standards, HITSP, Common Formats, CMS Quality Reporting Programs, All-Payer Claims Databases, and the Children’s EHR Format. The Common Formats portal covered standardized definitions and formats for collecting patient safety data, including incidents that reached the patient, near misses, and unsafe conditions. The CMS portal covered specifications for electronic clinical quality measures. AHRQ says the all-payer claims portal was last updated in 2014. These are the agency’s own descriptions, not an outside evaluation.
Two public registries compared. Park and Kim, in Studies in Health Technology and Informatics (2010), name USHIK and the National Cancer Institute’s cancer Data Standards Registry and Repository (caDSR) as two public metadata registries in the biomedical field, both built on ISO/IEC 11179. They argue that most registries are extended in organization-specific ways, which makes interoperability among registries difficult. They propose an integrated metadata object model and built an XML-based exchange format to test it. This is a development paper from the registry era, and its abstract does not report how widely the model was adopted.
Reuse of data elements in research. Dugas, in Trials (2016), tested whether a case report form editor could connect to a public ISO/IEC 11179-compliant registry so that trial designers could reuse data elements. The registry was built from the Medical Data Models portal, and three reuse scenarios were implemented at the form, item group, and data element levels. The author concludes that the approach is feasible and that the main limitation is the amount of content available in the registry. It is a technical feasibility study, not an evaluation of trial quality.
Linking registries to semantic technology. Sinaci and Laleci Erturkmen, in the Journal of Biomedical Informatics (2013), described a federated framework that extends ISO/IEC 11179 and uses linked open data principles so that each common data element can be referenced, queried, and linked to terminologies and content models. The aim was to bridge the gap between clinical care and research and to allow secondary use of electronic health record data, and the framework became part of the semantic layer of a post-marketing drug safety project. The abstract describes a design and an implementation, not measured results.
An earlier clinical trials example. Park and Kim, in the AMIA Annual Symposium Proceedings (2006), described a metadata-based system to manage data elements for cancer clinical trials, built to ISO 11179 and evaluated with 1,625 data elements extracted from College of American Pathologists cancer protocols for 20 major cancers. The abstract reports the evaluation set but not further results, and the work is two decades old.
Taken together, the sources show that registries like USHIK addressed a real problem, which is that the same concept is defined and stored differently across systems. They also show the recurring limits: registries depend on keeping content current, on agreement across organizations, and on users actually reusing what they find.
Common metadata registry problems:
- Content that falls out of date or is archived when funding and ownership change
- Local extensions that make one registry hard to link to another
- Data elements defined in several places with slightly different meanings
- Limited content, so users do not find what they need and do not return
- Confusing a registry of data element definitions with a terminology or value set service
- Old references and links to retired sites
What supports shared data definitions:
- A standard framework for describing data elements, such as ISO/IEC 11179
- A named steward for each registry and each data element
- Links between data elements and the terminologies and value sets they use
- Reuse of existing elements when new forms and reports are designed
- Plans for where content will live when a registry is retired
- Clear version information so users know which definition applied when
🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow
Nurses rarely open a metadata registry, but they depend on the definitions it holds.
At the Bedside
Every field a nurse completes, from a pain score to a fall risk, has a definition behind it. When definitions are shared across settings, data can move with the patient and mean the same thing at the next facility. When they are not, the number on the screen may not match the number the nurse recorded.
In Clinical Workflow
Nurses file patient safety event reports, and AHRQ’s Common Formats, described on the USHIK pages, are a set of standard definitions and formats for collecting such reports. Nurse informaticists and quality staff map local event categories to those definitions so that data can be compared across units and organizations. They also help clarify the exact meaning of data elements that feed quality measures.
In EHR Implementation (Go-Live Perspective)
During an Epic Go-Live, analysts at the elbow field questions about where data is captured and what a field is meant to hold. When a quality measure or safety report depends on a particular element, correct definitions and training prevent months of poor data later. Recording those questions for the build team helps keep data definitions consistent.
🎓 CAHIMS / CPHIMS & HIMSS Perspective
CAHIMS Exam Domain Mapping
USHIK connects data standards, quality reporting, and registry design:
| CAHIMS Domain | How USHIK Appears |
|---|---|
| Healthcare & Technology Environments | Federal health IT initiatives, standards bodies, and archived resources |
| Clinical Informatics | Data elements, quality measure specifications, and patient safety event definitions |
| Healthcare Information & Systems Management | Metadata management, harmonization, and registry design |
| Management & Leadership | Governance of data definitions, stewardship, and planning when resources are retired |
Key Terms to Know Alongside USHIK
- Metadata — data that describes other data
- Metadata Registry (MDR) — catalog of data element definitions and attributes
- ISO/IEC 11179 — international standard for metadata registries
- Data Element — a single unit of data with a defined meaning and format
- AHRQ Common Formats — standard definitions for collecting patient safety event data
- Value Set — list of codes that define a clinical concept for quality measures
HIMSS Organizational Position
HIMSS offers education and research on health information and technology topics through its Resource Center. Members can find related information on the HIMSS Resource Center page.
🧭 More HIMSS Word of The Day Terms
Related terms in the Data and Analytics series:
Browse all Data and Analytics terms or the A–Z glossary.
🔗 Explore Further: External References
- AHRQ — United States Health Information Knowledgebase https://www.ahrq.gov/data/ushik.html
- AHRQ Digital Healthcare Research — United States Health Information Knowledgebase (USHIK) project https://digital.ahrq.gov/ahrq-funded-projects/united-states-health-information-knowledgebase-ushik
- Park and Kim (2010), Studies in health technology and informatics — Achieving interoperability for metadata registries using comparative object modeling https://pubmed.ncbi.nlm.nih.gov/20841861/
- Dugas (2016), Trials — Design of case report forms based on a public metadata registry: re-use of data elements to improve compatibility of data https://pubmed.ncbi.nlm.nih.gov/27899162/
- Sinaci and Laleci Erturkmen (2013), Journal of biomedical informatics — A federated semantic metadata registry framework for enabling interoperability across clinical research and care domains https://pubmed.ncbi.nlm.nih.gov/23751263/
- Park and Kim (2006), AMIA … Annual Symposium proceedings. AMIA Symposium — Metadata registry and management system based on ISO 11179 for Cancer Clinical Trials Information System https://pubmed.ncbi.nlm.nih.gov/17238675/
- HIMSS — Resource Center https://www.himss.org/resource-center
Term source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025). All definitions in this series are paraphrased for editorial purposes. Readers are encouraged to consult the primary source for exact language.
Eric Andrew Kristof, RN, CAHIMS is a Healthcare IT professional and HIMSS Arkansas Chapter member based in Hot Springs Village, AR, with hands-on Epic Go-Live experience and a diverse healthcare and IT background. He writes at kristof.org at the intersection of clinical care and healthcare technology.
Leave a Reply