XMDR Content Survey - HL7 Version 3 Terminology

II. Core Content Characterization

Title*

Health Level Seven (HL7) Version 3 Terminology

Acronym

HL7 V3

Web page(s)

http://www.hl7.org/

Identifier

URI:ISO:2.16.840.1.113883.5

Contact Information

Health Level Seven, Inc.

3300 Washtenaw Avenue, Suite 227
Ann Arbor, MI 48104

Phone: 734-677-7777
Fax: 734-677-6622
E-mail: hq@hl7.org

Inclusion Rationale*

Health Level Seven is the American National Standards Institute (ANSI) -accredited Standards Developing Organization (SDO) operating in the healthcare domain ofclinical and administrative data.

Subject*

• biological, biomedical, medical or healthcare
• economic (medical)
• administrative, including organizational and personal names (medical)

Kind of Metadata*

• Term Lists
  • code sets - e.g., country codes, CAS numbers, airport codes
• Relationship Groups
  • Ontologies

Size statistics(estimated)*

~7400 concepts (some are included from other code sets)
~6000 Edges

Initial Submitter*

Harold Solbrig solbrig@mayo.edu

Date of Initial Survey*

2005-03-10

III. Supplementary Content Characterization

Date*

2005-03-11

Creator

Health Level Seven, Inc.

Publisher*

Health Level Seven, Inc.

Description*

The HL7 Version 3 Terminology exists primarily to support the HL7 Version 3 Reference Information Model (RIM). The current HL7 policy is to reference external terminological content whenever possible, so the Version 3 Terminology consists of resources that:

• Coorelate with and identify the RIM class structure
• Aren't externally available (or have license restrictions that aren't compatible with HL7's mission and requirements
• Are replicated for the convenience of the membership

Language(s)*

English (although the architecture will support multiple languages.)

Graph-theoretic Classification*

Indicate type of metadata according to the following graph-theoretic classification scheme:

• partial order (e.g., is-a, and part-of relations) Partial order = DAG + transitivity

Format / Schemas(s)*

• Microsoft Access tables (Members only)
• XML
• HTML

Media / Download*

Yes - DTD is available on the HL7 site

Constraint Specifications

?

Protocol(s)

The HL7 Version 3 Terminology is available online via. implementations the Common Terminology Services (CTS) standard Downloadable implementations are available that support:

• SOAP
• SQL
• LDAP

Licensing Issues*

HL7 Version 3 Terminology is freely available for public use.

Export restrictions

None

Subsets

The HL7 Version 3 Terminology contains a representation of the Unified Code for Units of Measure (UCUM)

Versions, Updates

Versions are typically done on a quartely cycle. Intermittent and new releases are available on the HL7 site

Documentation

Various tutorials, tools, etc are available on the HL7 Web Site

Character Set Encoding*

UTF-8

Measurement units

While the HL7 Version 3 Terminology doesn't utilize reference units, it DOES contain an interesting terminology of measurement units (UCUM)

Dataset / Standards Dependencies

HL7 Version 3 references many different code sets, including SNOMED-CT, LOINC, ICD-9, etc.

Related Datasets

Other similar or related metadata resources.

Software tools

See: HL7 Applications list for a partial set of tools.
Tools are also available at Mayo LexGrid site

Audience(s)

Medical Software Providers, Clinicians and anyone else involved in the Biomedical community

Citation

HL7 HL7 Version 3 Terminology. Available at: www.hl7.org.

Surveyor*

Harold Solbrig

Date of Survey*

2005-03-11

IV. Content Characterization by XMDR Staff

The following data elements are to be supplied by XMDR project staff/collaborators.

Attributes marked with an asterisk (*) are considered mandatory.

XMDR Participant Expertise

Names of persons (if any) on XMDR project (and contact info) who are familiar with this data set. XMDR participant organizations who have copies of this metadata resource.

XMDR Evaluator*

Names of persons on XMDR project (and contact info) who evaluated this metadata resource for inclusion (e.g., if the content survey was completed by someone at the content repository).

Inclusion Priority*

Priority suggested for acquisition and ingestion of this metadata resource.