×

HL7's new AMS is live!   We are working with Fonteva to resolve log in issues. My Account

Section 1e: Version 3 (V3)
Section 4: Rules and References

HL7 Version 3 Standard: Identification Service (IS), Release 1

DESCRIPTION

The Identification Service (IS) also known as the Identification and Cross-Reference Service (IXS) Service Functional Model define the functional requirements which provides a set of capabilities to manage and retrieve identifying information for various kinds of entities (people, organizations, devices etc.).

ALTERNATIVE NAMES

HL7 Version 3 Standard: Identification Service (IS), Release 1 may also go by the following names or acronyms:

"Entity Identification Service, R1", EIS, IS, IXS

TARGETS

  • Standards Development Organizations (SDOs)
  • Regulatory Agency
  • Pharmaceutical Vendors
  • EHR, PHR Vendors
  • Equipment Vendors
  • Health Care IT Vendors
  • Lab Vendors
  • HIS Vendors
  • Emergency Services Providers
  • Local and State Departments of Health
  • Medical Imaging Service Providers
  • Healthcare Institutions (hospitals, long term care, home care, mental health)

BENEFITS

  • Provides a robust and complete means for defining, updating and managing identities (linking, merging etc.), along with an associated set of identifying information
  • Occupies the portion of the technology stack that is dedicated to the service space.
  • By means of Semantic Signifier mechanism, IS can manage different structures of identifying information and it’s independent from the locally used standard (e.g. HL7 v3, HL7 v2.x or FHIR resources)

IMPLEMENTATIONS/CASE STUDIES

  • Software Partners (USA) MachMerge Patient Identification
  • Mirth (USA) MirthMatch
  • Dedalus (ITA) IXS Implementation in HealthSOAF project
  • Veneto Regional Administration (ITA) IXS Project

DEVELOPMENT BACKGROUND

As an interface specification, IS may be implemented and used in various different topologies. It may be access directly via web or other User Interface (UI) mechanisms by users, or system-to-system via other applications such as Hospital Information Systems. This does not affect the interface or behavior specification.

A relevant design goal of IS is its flexibility and adaptability to different semantic content. So a relevant concept assumed in IS is the Semantic Signifier.  The purpose of the Semantic Signifier is to separate the functional capabilities of RLUS from the semantic content. In this way RLUS can support different information objects and different metadata sets in a flexible but standardized and consistent interface.

More generally the IS Service Functional Model standard is a functional interface specification suitably designed to support service-oriented architectures (SOA), and it established the basis for the collaboration with the Object Management Group (OMG) that has realized the complementary technical specifications in WS* technologies.

RELATED DOCUMENTS

HL7 Version 3 Standard: Identification Service (IS), Release 1

(Download) (1.20 MB)

ADDITIONAL DETAILS

The standard is also available as part of the Health Level Seven Version 3 (V3) Normative Edition. See the HL7 Version 3 Product Suite for downloads.

BALLOT TYPE

  • Normative

STATUS DATE

2014-04-01

RESPONSIBLE WORK GROUP

Services Oriented Architecture

PRODUCT TYPE

  • Services

STAKEHOLDERS

  • EHR, PHR Vendors
  • Emergency Services Providers
  • Equipment Vendors
  • Health Care IT Vendors
  • Healthcare Institutions
  • HIS Vendors
  • Lab Vendors
  • Local and State Departments of Health
  • Medical Imaging Service Providers
  • Pharmaceutical Vendors
  • Regulatory Agency
  • Standards Development Organizations (SDOs)

FAMILY

  • V3

CURRENT STATE

  • Stable

REALM

  • Universal