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: UDDI (Universal Description, Discovery, and Integration)
Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)
🔍 Plain-Language Definition
The HIMSS Dictionary describes UDDI (Universal Description, Discovery, and Integration) as a web-based, distributed directory in which businesses can list themselves on the Internet and find one another, comparable to the white and yellow pages of a phone book. Its entry spells the middle word “Discover,” while the standard itself uses “Discovery.”
The OASIS specification describes UDDI as a set of web services for describing and finding businesses and organizations that offer web services, the services they provide, and the technical interfaces needed to use them. It says UDDI builds on HTTP, XML, XML Schema, and SOAP, and that it can serve public services or services kept within an organization. That last point matters, because the dictionary’s phrase about listing on the Internet describes only one use.
The dictionary’s present tense also needs context. IBM, Microsoft, and SAP operated a public demonstration registry called the UDDI Business Registry, and according to a 2005 FAQ posted to an OASIS mailing list, publication to it was disabled on January 12, 2006. The FAQ says the three companies considered the registry’s goal of proving interoperability and scale to be met after five years, and that their product support for UDDI was unaffected. The same FAQ describes UDDI versions 2 and 3 as OASIS standards. Whether any organization uses UDDI today was not established for this post.
| Item | Detail |
|---|---|
| What it is | A standard for publishing and discovering web services in a registry |
| Standards body | OASIS; version 3 became an OASIS Standard on February 3, 2005, per the committee page |
| Built on | HTTP, XML, XML Schema, and SOAP, per the specification |
| Core data types | businessEntity, businessService, bindingTemplate, and tModel |
| Public registry | The IBM, Microsoft, and SAP public registry stopped accepting publication on January 12, 2006 |
| Relation to HIMSS | None verified for this post, so none is claimed |
⚠️ Exam Alert: UDDI is a directory for locating web services, not a protocol for sending clinical messages. It is related to SOAP, which carries messages, and WSDL, which describes a service’s interface, but it does none of their jobs. Questions often pair it with service-oriented architecture, where a registry helps providers publish services and requesters find them.
🌐 Why It Matters: Real-World Healthcare IT Context
This section relies on the OASIS specification, an OASIS committee page, a 2005 FAQ, a Microsoft archive page, and a W3C note. This post found no health care research on UDDI, so it makes no claim about its use in clinical systems.
The data model. The OASIS specification defines four core data types. A businessEntity describes a business or other provider. A businessService groups related services from that provider. A bindingTemplate holds the technical details needed to connect to a specific service. A tModel represents a reusable concept, such as a specification, protocol, or classification scheme. The main interfaces are Inquiry, for searching and retrieving data, Publication, for adding and changing it, and Security, for obtaining and discarding authentication tokens. The specification also covers custody transfer, subscription, and replication between nodes. The copy read for this post is the Version 3.0.2 technical committee draft dated October 19, 2004, and the committee page says Version 3 became an OASIS Standard in February 2005.
Where it fits in the larger picture. A W3C Working Group Note from February 2004 on web services architecture defines discovery as locating a machine-processable description of a web service resource that matches functional criteria, and says discovery can be static, at development time, or dynamic, at run time. It describes a discovery service as one that helps agents retrieve those descriptions and says using one is optional. The portion of the note read for this post does not mention UDDI, so the note supports the general idea of discovery and not UDDI specifically.
What happened to the public registry. The 2005 FAQ says IBM, Microsoft, and SAP stopped publication to the public UDDI Business Registry on January 12, 2006, and that users could retrieve public information until then. It says the registry was meant as a public demonstration that UDDI implementations interoperate and scale, and that it had more than 50,000 replicated entries after five years. The FAQ does not address private registries directly.
Vendor product status. A Microsoft archive page, last updated May 31, 2018 and marked as no longer maintained, says Microsoft removed the UDDI Services role from Windows Server 2008 R2, and that later UDDI Services releases would come with BizTalk Server, beginning with UDDI v3.0 in BizTalk Server 2009. It says UDDI v3.0 is backward compatible with UDDI 2.0. The OASIS committee page labels the committee “Completed” while still listing a meeting schedule, so its current status is unclear.
Why it matters to health IT readers. UDDI is mainly background for service-oriented architecture, where systems expose services that others can find and call. Modern health data exchange discussions more often center on other standards, and this post did not verify any current health IT standard that depends on UDDI. Anyone evaluating a product that claims to use it should ask the vendor which version and registry it uses.
Common UDDI problems:
- Treating the dictionary’s description as proof that a public UDDI directory is currently available
- Confusing a registry that lists services with a protocol that carries messages
- Mixing up UDDI, which finds services, with WSDL, which describes them
- Assuming UDDI is used in every service-oriented design, when a W3C note describes discovery services as optional
- Misspelling the standard’s middle word as “Discover”
What supports using UDDI:
- A defined data model for describing providers, services, and technical bindings
- Inquiry and publication interfaces defined in an OASIS specification
- Support for public or organization-internal registries, per the specification
- Replication and subscription features described in the specification
🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow
Nurses do not use UDDI directly, and it is rarely visible on a clinical unit. Its relevance is indirect, through how systems find and call one another.
At the Bedside
At the bedside the effect shows up as whether information from one system reaches another, such as a result arriving in the chart. When something fails to arrive, nurses report what they saw, such as the time, the patient’s location, and the missing item, without trying to diagnose the integration.
In Clinical Workflow
Nurse informaticists often sit between clinicians and integration analysts. Knowing that systems can locate each other’s services through a registry, a configuration file, or a direct address helps them ask which method a given interface uses and who owns it.
In EHR Implementation (Go-Live Perspective)
During an Epic Go-Live, analysts at the elbow hear reports about missing or delayed data, and the cause usually sits in an interface rather than in anything the nurse did. Writing down the source system, the destination, and the time helps the integration team. This post does not claim that any specific go-live used UDDI.
🎓 CAHIMS / CPHIMS & HIMSS Perspective
CAHIMS Exam Domain Mapping
UDDI supports architecture and standards knowledge:
| CAHIMS Domain | How UDDI Appears |
|---|---|
| Healthcare & Technology Environments | Web services concepts and the standards around them |
| Clinical Informatics | How systems find services that exchange clinical data |
| Healthcare Information & Systems Management | Service registries, interfaces, and integration design |
| Management & Leadership | Judging legacy standards and vendor claims about them |
Key Terms to Know Alongside UDDI
- Web services — software services that systems call over a network using standard interfaces
- SOAP — a messaging protocol often used to carry web service requests
- XML — a markup language used to structure data and messages
- Service-oriented architecture — a design in which systems expose reusable services
- Registry — a store of descriptive entries that can be searched
- Interoperability — the ability of systems to exchange and use information
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.
🔗 Explore Further: External References
- OASIS — UDDI Version 3.0.2 Specification (Technical Committee Draft, October 19, 2004) https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi_v3.htm
- OASIS — UDDI Specification Technical Committee https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=uddi-spec
- OASIS mailing list archive — UDDI Business Registry shutdown FAQ (December 2005) https://lists.oasis-open.org/archives/uddi-spec/200512/msg00020.html
- Microsoft Learn — Removal of UDDI Services from Server Operating System https://learn.microsoft.com/en-us/previous-versions/windows/win32/win7appqual/removal-of-uddi-services-from-server-os
- W3C — Web Services Architecture, Working Group Note (February 11, 2004) https://www.w3.org/TR/ws-arch/
- 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