<?xml version="1.0" encoding="ISO-8859-1"?>
<spec xsi:noNamespaceSchemaLocation="../../support/dtd/v3spec.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <header>
      <title>Glossary</title>
      <version>2.5</version>
      <date>January 2005</date>
      <authlist>
         <author>
            <role>Editor</role>
            <name>Various Contributors</name>
            <affiliation>HL7 Publishing Technical Committee</affiliation>
         </author>
      </authlist>
   </header>
   <body>
      <div1 id="glossaryintroduction">
         <head>Introduction to the Glossary</head>
         <p>The HL7 Glossary provides "core" definitions of words and terms used throughout HL7 standards and documents.  These definitions are maintained by the Modeling and Methodology (MnM) and Publishing Technical Committees (TC) and are identified in the glossary as "Core Glossary".</p>
         <p>It should be noted that while the Modeling and Methodology and Publishing Technical Committees maintain the glossary definitions, the definitions themselves originate from within the various technical committees and special interest groups and are not constrained or veted in any way by the MnM or Publishing TCs.  It is expected that each committee and its balloters know their business best and that, should an imprecise or incorrect definition be put forward, it will be corrected through the domain balloting process.</p>
         <p>It should further be noted that this glossary does not include all the definitions from the Reference Information Model (RIM) as the RIM definitions are already available in the RIM publication and are in context there.</p>
         <p>Readers may also note that "core" definitions may be constrained or narrowed within the context of specific domains.  For instance, the PM domain includes a definition for Person that is constrained from the RIM definition of Person.  In these cases, the PM:Person is perfectly consistent with the RIM:Person, albeit as a specialized subset of the larger group.  So while all instances of a PM:Person will also be members of RIM:Persons, not all instances of RIM:Person will fall within the group of PM:Persons.</p>
         <p>The MnM and Publishing TCs encourage all members to review the definitions put forward by committees as part of the balloting process with an eye towards correcting and refining them as necessary and appropriate.</p>
      </div1>
      <div1 id="glossary">
         <head>Alphabetic Index</head>
         <div2 id="glossary-a">
            <head>A</head>
            <glist>
               <gitem id="annotation">
                  <label> annotation</label>
                  <def>
                     <p>
								A note following a <termref ref="domain_message_information_model">
								Domain Message Information Model</termref> (D-MIM) diagram that 
								explains the D-MIM or the modeling behind the D-MIM.
							</p>
                  </def>
               </gitem>
               <gitem id="ansi">
                  <label>ANSI</label>
                  <def>
                     <p>
                        <loc href="http://www.ansi.org/">American National Standards Institute</loc>
                     </p>
                  </def>
               </gitem>
               <gitem id="application">
                  <label> application</label>
                  <def>
                     <p>
								A software program or set of related programs that provide 
								some useful healthcare capability or functionality.
							</p>
                  </def>
               </gitem>
               <gitem id="application_role">
                  <label>application role</label>
                  <def>
                     <p>
								An abstraction that expresses a portion of the messaging behaviour of an 
								information system.
							</p>
                  </def>
               </gitem>
               <gitem id="artifact">
                  <label> artifact</label>
                  <def>
                     <p>
								Any deliverable resulting from the discovery, analysis, and design activities         
								leading to the creation of <termref ref="message">message</termref> specifications.
							</p>
                  </def>
               </gitem>
               <gitem id="association">
                  <label> association</label>
                  <def>
                     <p>
								A reference from one <termref ref="class">class</termref> to 
								another class or to itself,  or a connection between two 
								<termref ref="object">objects</termref> (instances of classes).
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlstructrelations">
								 Relationships section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="association_composition">
                  <label>association composition</label>
                  <def>
                     <p>
								See <termref ref="composite_aggregation">composite 
								aggregation</termref>
                     </p>
                  </def>
               </gitem>
               <gitem id="association_role_name">
                  <label>association role name</label>
                  <def>
                     <p>
								A name for each end of an <termref ref="association">association</termref>. 
								The name is a short verb phrase depicting the <termref ref="role">
								role</termref> of the <termref ref="class">class</termref> at 
								the opposite end of the association from the perspective of 
								the class adjacent to the role.
							</p>
                  </def>
               </gitem>
               <gitem id="attribute">
                  <label>attribute</label>
                  <def>
                     <p>
								An abstraction of a particular aspect of a <termref ref="class">
								class</termref>. Attributes become the 
								data values that are passed in HL7 <termref ref="message">messages</termref>.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlattrib">
								 Attributes section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="attribute_type">
                  <label>attribute type</label>
                  <def>
                     <p>
								A classifier for the meaning of an <termref ref="attribute">
								attribute</termref>. In HL7 Version 3, attribute type is 
								indicated by a suffix added to the attribute name.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-b">
            <head>B</head>
            <glist>
               <gitem id="bag">
                  <label>bag</label>
                  <def>
                     <p>
								A form of <termref ref="collection">collection</termref> whose 
								members are unordered, and need not be unique. 
							</p>
                  </def>
               </gitem>
               <gitem id="blank">
                  <label> blank</label>
                  <def>
                     <p>
								One of the allowed values for 
								<termref ref="conformance_requirement">conformance 
								requirements</termref>. Blank means that conformance for this 
								element is to be negotiated on a site-specific basis. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-c">
            <head>C</head>
            <glist>
               <gitem id="cardinality">
                  <label> cardinality</label>
                  <def>
                     <p>
								Property of a data element (the number of times a data element 
								MAY repeat within an individual occurrence of an object view) 
								or column in the <termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref> (the minimum and 
								maximum number of occurrences of the 
								<termref ref="message_element">message element</termref>). 
							</p>
                  </def>
               </gitem>
               <gitem id="character_data">
                  <label>Character Data</label>
                  <def>
                     <p>Text in a particular coding (e.g., ASCII), as distinguished from binary data.</p>
                  </def>
               </gitem>
               <gitem id="choice">
                  <label> choice</label>
                  <def>
                     <p>
								A <termref ref="message">message</termref> construct that includes 
								alternative portions of the message. For a choice due to 
								specialization, the sender picks one of the alternatives and 
								sends it along with a flag. 
							</p>
                  </def>
               </gitem>
               <gitem id="choice_due_to_specialization">
                  <label> choice due to specialization</label>
                  <def>
                     <p>
								A choice that arises when a 
								<termref ref="hierarchical_message_description">Hierarchical Message
								Description</termref> includes (a) an object view which is associated         
								with a <termref ref="class">class</termref> that is a 
								<termref ref="superclass">superclass</termref> of two or more object 
								views, or (b) an object view which is a superclass of one or more object
								views and MAY itself be instantiated. Under this circumstance different
								<termref ref="message_instance">message instances</termref> MAY contain 
								different object views. The choice structure is used to 
								accommodate the alternatives.          
							</p>
                  </def>
               </gitem>
               <gitem id="class">
                  <label> class</label>
                  <def>
                     <p>
								An abstraction of a thing or concept in a particular 
								application <termref ref="domain">domain</termref>. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlstructclasses">Classes
								 section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="classifier_attribute">
                  <label> classifier attribute</label>
                  <def>
                     <p>
								An <termref ref="attribute">attribute</termref> used in 
								<termref ref="generalization_hierarchy">generalization 
								hierarchies</termref> to indicate which of the 
								<termref ref="specialization">specializations
								</termref> is the focus of the <termref ref="class">class
								</termref>. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlattrib">
								 Attributes section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="clone">
                  <label> clone</label>
                  <def>
                     <p>
								A <termref ref="class">class</termref> from the 
								<termref ref="reference_information_model">Reference 
								Information Model</termref> 
								(RIM) that has been used in a specialized context and whose 
								name differs from the RIM class from which it was replicated. 
								This makes it possible to represent specialized uses of more 
								general classes to support the needs of messaging. 
							</p>
                  </def>
               </gitem>
               <gitem id="cmet">
                  <label> CMET</label>
                  <def>
                     <p>
								See <termref ref="common_message_element_type">Common Message Element Type</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="cmet_message_information_model">
                  <label> CMET Message Information Model</label>
                  <def>
                     <p>
								A form of <termref ref="refined_message_information_model">
								Refined Message Information Model</termref> (R-MIM) constructed 
								to represent the totality of concepts embodied in the individual R-MIMs 
								needed to support the definition of HL7's 
								<termref ref="common_message_element_type">
								Common Message Element Types</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="c-mim">
                  <label>C-MIM</label>
                  <def>
                     <p>
								See <termref ref="cmet_message_information_model">CMET Message 
								Information Model</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="coded_attribute">
                  <label>coded attribute</label>
                  <def>
                     <p>
								An <termref ref="attribute">attribute</termref> in the 
								<termref ref="reference_information_model">Reference 
								Information Model</termref> 
								(RIM) with a base <termref ref="data_type">data type</termref> of 
								CD, CE, CS, or CV. 
							</p>
                  </def>
               </gitem>
               <gitem id="coding_strength">
                  <label>coding strength</label>
                  <def>
                     <p>
								An <termref ref="extensibility_qualifier">extensibility qualifier</termref> 
								that specifies whether or not a code set can be expanded to meet 
								local implementation needs.
							</p>
                  </def>
               </gitem>
               <gitem id="coding_system">
                  <label>coding system</label>
                  <def>
                     <p>
								A scheme for representing concepts using (usually) short 
								<termref ref="concept_identifier">concept identifiers</termref> to denote 
								the concepts that are members of the system; defines a set of 
								unique concept codes. Examples of coding systems are <loc href="http://www.cdc.gov/nchs/icd9.htm">ICD-9</loc>, 
								<termref ref="loinc">LOINC</termref> and <termref ref="snomed">SNOMED.</termref>
                     </p>
                  </def>
               </gitem>
               <gitem id="collection">
                  <label>collection</label>
                  <def>
                     <p>
								An aggregation of similar <termref ref="object">objects</termref>. 
								The forms of collection used by HL7 are <termref ref="set">set
								</termref>, <termref ref="bag">bag</termref>, and 
								<termref ref="list">list</termref>. Objects which MAY be 
								found in collections include <termref ref="data_type">data types
								</termref>and <termref ref="message_element_type">message element 
								types</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="common_message_element_type">
                  <label>common message element type (CMET)</label>
                  <def>
                     <p>
								A <termref ref="message_type">message type</termref> in a 
								<termref ref="hierarchical_message_description">Hierarchical 
								Message Description</termref> (HMD) that MAY be included 
								by reference in other HMD's. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gcmet">
								 Common Message Element Types section</ilxspecref> 
								 of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="composite_aggregation">
                  <label>composite aggregation</label>
                  <def>
                     <p>
								A type of <termref ref="association">association</termref> between 
								<termref ref="object">objects</termref>, indicating a 
								whole-part relationship. 
							</p>
                  </def>
               </gitem>
               <gitem id="composite_data_type">
                  <label>composite data type</label>
                  <def>
                     <p>
								A <termref ref="data_type">data type</termref> assigned to a 
								<termref ref="message_element_type">message element type</termref> that 
								contains one or more components, each of which is represented 
								by an assigned data type. 
							</p>
                  </def>
               </gitem>
               <gitem id="composite_message_element_type">
                  <label>composite message element type</label>
                  <def>
                     <p>
								A <termref ref="message_element_type">message element type
								</termref> that contains subordinate heterogeneous 
								<termref ref="message_type">message 
								types</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="concept_identifier">
                  <label>concept identifier</label>
                  <def>
                     <p>
								A unique identification assigned to a concept by the 
								HL7 organization. 
							</p>
                  </def>
               </gitem>
               <gitem id="conformance_claim">
                  <label>conformance claim</label>
                  <def>
                     <p>
								A <termref ref="specification">specification</termref> written by HL7 
								to precisely define the behavior of an application with respect 
								to its HL7 interfaces, and which MAY be designated functional 
								or technical. A functional conformance claim is simply a 
								statement that an application conforms to a particular 
								<termref ref="application_role">application role</termref>. A technical         
								conformance claim (also referred to as a Technical Statements of Performance
								Criteria) defines the behavior of an application in some
								other sense than the <termref ref="message">messages</termref> it 
								sends or receives. This MAY include the 
								<termref ref="implementation_technology_specification">
								Implementation Technology 
								Specifications</termref> that it supports, the use of specific 
								optional protocols or character sets, or many other
								behaviors. 
							</p>
                  </def>
               </gitem>
               <gitem id="conformance_claim_set">
                  <label>conformance claim set</label>
                  <def>
                     <p>
								A list of the identifiers of specific HL7 <termref ref="conformance_claim">
								conformance claims</termref>, used by a <termref ref="sponsor">
								sponsor</termref> to describe the conformance of its application. 
							</p>
                  </def>
               </gitem>
               <gitem id="conformance_requirement">
                  <label>conformance requirement</label>
                  <def>
                     <p>
								A column in the <termref ref="hierarchical_message_description">
								Hierarchical Message
								Description</termref> (HMD) that designates whether the 
								system SHALL communicate an <termref ref="attribute">attribute's
								</termref>value if a value is available. Allowed values are 
								<termref ref="required">required</termref> (must be included), 
								not required (may be left out) or <termref ref="not_permitted">not 
								permitted</termref> (may never be included.)  Items listed as 
								not required in the HL7 specification SHALL be declared by a 
								vendor as either required or not permitted when a 
								<termref ref="conformance_claim">conformance claim</termref> is asserted 
								for that <termref ref="message_type">message type</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="conformance_verb">
                  <label>conformance verb</label>
                  <def>
                     <p>In HL7 Version 3 Specifications, the correct verb form for indicating a requirement is "SHALL." The correct verb form for indicating a recommendation is "SHOULD." The correct verb form for an option is "MAY."</p>
                     <p>Universally accepted "standardese" does not recognize "must". Use "SHALL" to indicate a mandatory aspect or an aspect on which there is no option.</p>
                     <p>The negatives are SHALL NOT, SHOULD NOT, MAY NOT.</p>
                     <p>The Publishing Facilitator's Guide requires the Conformance Verbs to be captialized when they are used to indicate conformance criteria, to differentiate from common usage of the words.</p>
                     <p>The source for this usage is <termref ref="ansi">ANSI.</termref>
                     </p>
                  </def>
               </gitem>
               <gitem id="connection">
                  <label>connection</label>
                  <def>
                     <p>
								In an <termref ref="information_model">information model</termref>, a 
								specified relationship between two <termref ref="class">classes
								</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="constraint">
                  <label>constraint</label>
                  <def>
                     <p>
								Narrowing down of the possible values for an 
								<termref ref="attribute">attribute</termref>; a suggestion of 
								legal values for an attribute (by indicating the 
								<termref ref="data_type">data type</termref> that applies, by 
								restriction of the data type, or by definition 
								of the <termref ref="domain">domain</termref> of an attribute as 
								a subset of the domain of its data type). MAY also include 
								providing restrictions on data types. A constraint imposed on 
								an <termref ref="association">association</termref> MAY limit the 
								<termref ref="cardinality">cardinality</termref> of the association 
								or alter the navigability of the association (direction in which 
								the association can be navigated). A 
								<termref ref="refined_message_information_model">
								Refined Message Information Model</termref> (R-MIM) 
								<termref ref="class">class</termref> MAY be constrained by 
								choosing a subset of its 
								<termref ref="reference_information_model">Reference
								Information Model</termref> (RIM) properties (i.e., classes 
								and attributes) or by cloning, in which the class&#8217; name is 
								changed. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlconstr">
								 Constraints section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="control_event_wrapper">
                  <label>control event wrapper</label>
                  <def>
                     <p>
								A <termref ref="wrapper">wrapper</termref> that contains 
								<termref ref="domain">domain</termref> specific administrative 
								information related to the "controlled event" which is being 
								communicated as a messaging interaction. The control event 
								wrapper is used only in <termref ref="message">messages</termref> 
								that convey status, or in commands for logical operations being 
								coordinated between applications (e.g., the coordination of 
								query specification/query response interactions).
							</p>
                  </def>
               </gitem>
               <gitem id="coupling">
                  <label>coupling</label>
                  <def>
                     <p>
								1.  An interaction between <termref ref="system">systems</termref> or between properties of a system.
							</p>
                  </def>
                  <def>
                     <p>
								2.  With regard to <termref ref="application_role">application roles
								</termref>, refers to whether or not additional information 
								about the <termref ref="subject_class">subject classes</termref> 
								participating in a <termref ref="message">message</termref> may be 
								commonly available to system components outside of the specific message.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-d">
            <head>D</head>
            <glist>
               <gitem id="data_type">
                  <label>data type</label>
                  <def>
                     <p>
								The structural format of the data carried in an 
								<termref ref="attribute">attribute</termref>. 
								It MAY <termref ref="constraint">constrain</termref> the set of 
								values an attribute may assume.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gdt">
								 Data Types section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="default_value">
                  <label>default value</label>
                  <def>
                     <p>
								In HL7 <termref ref="message">messages</termref>, the value for an 
								<termref ref="attribute">attribute</termref> that is to be used by 
								message receivers if no value is given.          
							</p>
                  </def>
               </gitem>
               <gitem id="distal_class">
                  <label>distal class</label>
                  <def>
                     <p>
								From the perspective of a <termref ref="class">class</termref> 
								in an <termref ref="information_model">information model</termref>, it is 
								the class at the opposite end of an <termref ref="association">
								association</termref> between the two.  
							</p>
                  </def>
               </gitem>
               <gitem id="d-mim">
                  <label>D-MIM</label>
                  <def>
                     <p>
								See <termref ref="domain_message_information_model">
								Domain Message Information Model</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="domain">
                  <label>domain</label>
                  <def>
                     <p>
								1. A particular area of interest. For example, the domain for HL7 is 
								healthcare.
							</p>
                  </def>
                  <def>
                     <p>
								2.  The set of possible values of a <termref ref="data_type">data type
								</termref>, <termref ref="attribute">attribute</termref>, or data 
								type component. See also <termref ref="vocabulary_domain">vocabulary domain
								</termref>.
							</p>
                  </def>
                  <def>
                     <p>
								3.  A special interest group within HL7,
								such as Pharmacy, Laboratory, or Patient Administration.
							</p>
                  </def>
               </gitem>
               <gitem id="domain_expert">
                  <label>domain expert</label>
                  <def>
                     <p>
								An individual who is knowledgeable about the concepts in a 
								particular problem area within the healthcare arena and/or is 
								experienced with using or providing the functionality of that area. 
							</p>
                  </def>
               </gitem>
               <gitem id="domain_message_information_model">
                  <label>Domain Message Information Model</label>
                  <def>
                     <p>
								A form of <termref ref="refined_message_information_model">Refined Message 
								Information Model</termref> (R-MIM) constructed to represent 
								the totality of concepts embodied in the individual R-MIMs 
								needed to support the communication requirements of a particular 
								HL7 domain.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdltypes">Information Model
								 section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="domain_name">
                  <label>domain name</label>
                  <def>
                     <p>
								The name assigned to a <termref ref="vocabulary_domain"> 
								vocabulary domain</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="domain_specification">
                  <label>domain specification</label>
                  <def>
                     <p>
								The specification of a <termref ref="vocabulary_domain"> 
								vocabulary domain</termref>.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-e">
            <head>E</head>
            <glist>
               <gitem id="entry_point">
                  <label>entry point</label>
                  <def>
                     <p>
								The point at which a <termref ref="common_message_element_type">
								Common Message Element Type</termref> (CMET) is inserted into a 
								<termref ref="refined_message_information_model">Refined Message Information Model
								</termref> (R-MIM). 
							</p>
                  </def>
               </gitem>
               <gitem id="event">
                  <label>event</label>
                  <def>
                     <p>
								1. A stimulus that causes a noteworthy change in the 
								<termref ref="state">state</termref> of an <termref ref="object">
								object</termref>, or a signal that invokes the behavior of an 
								object. See also <termref ref="trigger_event">trigger event</termref>.
							</p>
                  </def>
                  <def>
                     <p>
								2.  A <termref ref="vocabulary_domain">vocabulary domain 
								</termref> value for Mood.
							</p>
                  </def>
               </gitem>
               <gitem id="extensibility_qualifier">
                  <label>extensibility qualifier</label>
                  <def>
                     <p>
								A <termref ref="vocabulary_domain_qualifier">vocabulary domain qualifier</termref> 
								used in a <termref ref="domain_specification">domain specification</termref>, 
								which indicates whether or not the existing 
								<termref ref="vocabulary_domain">vocabulary domain</termref> can be 
								extended with additional values. There are two possible 
								values: CNE (coded, no extension) and CWE (coded with extension). 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gvocabqualify">
								 Vocabulary Domain Qualifiers section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="extensible_markup_language">
                  <label>Extensible Markup Language</label>
                  <def>
                     <p>
								A meta-language that defines a
								syntax used to define other <termref ref="domain">domain</termref>
								-specific, semantic, structured markup languages. Based on 
								SGML (Standard Generalized Markup Language), it 
								consists of a set of rules for defining semantic tags used to 
								mark up the content of documents. Abbreviated as XML.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-f">
            <head>F</head>
            <glist>
               <gitem id="function_point">
                  <label>function point</label>
                  <def>
                     <p>
								Any function, <termref ref="user">user</termref> transaction, 
								or other <termref ref="interaction">interaction</termref> or 
								<termref ref="event">event</termref> in the <termref ref="sponsor">
								sponsor&#8217;s</termref> application which, when it occurs, does 
								or may correspond to an HL7 <termref ref="trigger_event">trigger 
								event</termref>. Used to describe the conformance of an 
								information system with the HL7 standard. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-g">
            <head>G</head>
            <glist>
               <gitem id="generalization">
                  <label>generalization</label>
                  <def>
                     <p>
								An <termref ref="association">association</termref> between two 
								<termref ref="class">classes</termref>, referred to as 
								<termref ref="superclass">superclass</termref> and 
								<termref ref="subclass">subclass</termref>, in which the subclass 
								is derived from the superclass. The subclass inherits all
								properties from the superclass, including <termref ref="attribute">
								attributes</termref>, relationships, and <termref ref="state">
								states</termref>, but also adds new ones to extend the 
								capabilities of the parent class. Essentially, a 
								<termref ref="specialization">specialization</termref> from the 
								point-of-view of the subclass. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlstructrelations">
								 Relationships section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="generalization_hierarchy">
                  <label>generalization hierarchy</label>
                  <def>
                     <p>
								All <termref ref="superclass">superclasses</termref> and 
								<termref ref="subclass">subclasses</termref> with a common 
								root superclass. 
							</p>
                  </def>
               </gitem>
               <gitem id="graphical_expression">
                  <label>graphical expression</label>
                  <def>
                     <p>
								A visual representation of a <termref ref="model">model</termref> 
								that uses graphic symbols to represent
								the components of the model and the relationships that exist
								between those components. 
							</p>
                  </def>
               </gitem>
               <gitem id="grid_view">
                  <label>grid view</label>
                  <def>
                     <p>
								A complete view of the <termref ref="message_type">message type
								</termref> definition, which, due to its size, is presented in 
								a scrollable format.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-h">
            <head>H</head>
            <glist>
               <gitem id="hierarchical_message_description">
                  <label>Hierarchical Message Description</label>
                  <def>
                     <p>
								A <termref ref="specification">specification</termref> of the exact 
								fields of a <termref ref="message">message</termref> and their
								grouping, sequence, optionality, and <termref ref="cardinality">
								cardinality</termref>. This specification contains         
								<termref ref="message_type">message types</termref> for one or more 
								<termref ref="interaction">interactions</termref>, or that represent one or
								more <termref ref="common_message_element_type">common message 
								element types</termref>. This is the primary normative 
								structure for HL7 messages. 
							</p>
                  </def>
               </gitem>
               <gitem id="hmd">
                  <label>HMD</label>
                  <def>
                     <p>
								See <termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="html">
                  <label>HTML</label>
                  <def>
                     <p>Hypertext Markup Language, a specification of the <termref ref="w3c">W3C</termref> that provides markup of documents for display in a web browser</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-i">
            <head>I</head>
            <glist>
               <gitem id="identifier_attribute">
                  <label>identifier attribute</label>
                  <def>
                     <p>
								An <termref ref="attribute">attribute</termref> used to identify an 
								<termref ref="instance">instance</termref> of a 
								<termref ref="class">class</termref>. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlattrib">
								 Attributes section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="implementation_technology">
                  <label>implementation technology</label>
                  <def>
                     <p>
								A technology selected for use in encoding and sending HL7 
								<termref ref="message">messages</termref>. For example, <termref ref="xml">XML</termref> is being 
								used as an implementation technology for Version 3. 
							</p>
                  </def>
               </gitem>
               <gitem id="implementation_technology_specification">
                  <label>Implementation Technology Specification</label>
                  <def>
                     <p>
								A <termref ref="specification">specification</termref> that describes 
								how HL7 <termref ref="message">messages</termref> are sent using a
								specific <termref ref="implementation_technology">implementation technology
								</termref>. It includes, but is not
								limited to, specifications of the method of encoding the messages,
								rules for the establishment of <termref ref="connection">connections
								</termref>and transmission timing and procedures for dealing 
								with errors. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gits">
								 Implementation Technology Specifications section</ilxspecref> 
								 of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="inclusion">
                  <label>inclusion</label>
                  <def>
                     <p>
								The <termref ref="specification">specification</termref> in the 
								<termref ref="hierarchical_message_description">Hierarchical 
								Message Description</termref> indicating whether an element of a 
								<termref ref="message_type">message type</termref> MAY be null in some         
								<termref ref="message_instance">message instances</termref>. Contrast 
								this with conformance. 
							</p>
                  </def>
               </gitem>
               <gitem id="information_model">
                  <label>information model</label>
                  <def>
                     <p>
								A structured <termref ref="specification">specification</termref>, 
								expressed graphically and/or narratively, of the information 
								requirements of a <termref ref="domain">domain</termref>. An 
								information model describes the <termref ref="class">classes
								</termref> of information required and the <termref ref="property">properties</termref> of those 
								classes, including <termref ref="attribute">attributes</termref>, 
								relationships, and <termref ref="state">states</termref>. 
								Examples in HL7 are the <termref ref="domain_message_information_model">Domain Reference Information Model,</termref>
                        <termref ref="reference_information_model">Reference Information Model</termref>, 
								and <termref ref="refined_message_information_model">Refined Message Information 
								Model</termref>.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdl">Information Model
								 section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="inheritance">
                  <label>inheritance</label>
                  <def>
                     <p>
								In a <termref ref="generalization">generalization</termref> relationship, 
								the <termref ref="subclass">subclass</termref> inherits all 
								properties from the <termref ref="superclass">superclass</termref>, 
								including <termref ref="attribute">attributes</termref>, 
								relationships, and <termref ref="state">states</termref>, 
								unless otherwise specified. 
							</p>
                  </def>
               </gitem>
               <gitem id="instance">
                  <label>instance</label>
                  <def>
                     <p>
								A case or an occurrence. For example, an instance of a 
								<termref ref="class">class</termref> is an 
								<termref ref="object">object</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="interaction">
                  <label>interaction</label>
                  <def>
                     <p>
								A single, one-way information flow that supports a communication
								requirement expressed in a <termref ref="scenario">scenario</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="interaction_diagram">
                  <label>interaction diagram</label>
                  <def>
                     <p>
								A graphical representation of communications between 
								<termref ref="application_role">application roles</termref>. An 
								interaction diagram may also be referred to as a ladder diagram, 
								sequence diagram, or storyboard interaction diagram.
							</p>
                  </def>
               </gitem>
               <gitem id="interaction_list">
                  <label> interaction list</label>
                  <def>
                     <p>
								A list of the <termref ref="interaction">interactions</termref> that 
								appear in an <termref ref="interaction_diagram">interaction diagram</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="interaction_model">
                  <label>interaction model</label>
                  <def>
                     <p>
								A <termref ref="specification">specification</termref> of the 
								responsibilities of <termref ref="message">message</termref> senders 
								and receivers. 
							</p>
                  </def>
               </gitem>
               <gitem id="interaction_narrative">
                  <label> interaction narrative</label>
                  <def>
                     <p>
								A narrative description of each <termref ref="interaction">interaction
								</termref>contained in an <termref ref="interaction_list">interaction list
								</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="internal_data_type">
                  <label>internal data type</label>
                  <def>
                     <p>
								An HL7 <termref ref="data_type">data type</termref> defined to 
								support the definition of other data
								types, but which may not be assigned as the type for a data
								field itself.
							</p>
                  </def>
               </gitem>
               <gitem id="interoperability">
                  <label>interoperability</label>
                  <def>
                     <p>In this context, interoperability refers to the ability of two or more computer systems to exchange information.</p>
                     <list role="unordered">
                        <item>Main Entry: in·ter·op·er·a·bil·i·ty
									<list role="unordered">
                              <item>Function: noun</item>
                              <item>Date: 1977</item>
                              <item>ability of a system (as a weapons system) to use the parts or equipment of another system</item>
                              <item>Source: Merriam-Webster web site</item>
                           </list>
                        </item>
                        <item> interoperability
								  <list role="unordered">
                              <item>ability of two or more systems or components to exchange information and to use the information that has been exchanged.</item>
                              <item>Source: IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries, IEEE, 1990</item>
                           </list>
                        </item>
                     </list>
                     <p>&#8220;Functional&#8221; interoperability is the capability to reliably exchange information without error</p>
                     <p>&#8220;Semantic" interoperability is the ability to interpret, and, therefore, to make effective use of the information so exchanged.</p>
                     <p>In our context, "effective use" means that the information can be used in any type of computable algorithm (appropriate) to that information </p>
                  </def>
               </gitem>
               <gitem id="its">
                  <label>ITS</label>
                  <def>
                     <p>
								See <termref ref="implementation_technology_specification">
								Implementation Technology Specification</termref>.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-j">
            <head>J</head>
            <glist>
               <gitem id="joint_state">
                  <label>joint state</label>
                  <def>
                     <p>
								A summarization of multiple partial <termref ref="state">states
								</termref>in a <termref ref="state_machine">state machine</termref>. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-k">
            <head>K</head>
         </div2>
         <div2 id="glossary-l">
            <head>L</head>
            <glist>
               <gitem id="ladder_diagram">
                  <label>ladder diagram</label>
                  <def>
                     <p>
								See <termref ref="interaction_diagram">interaction 
								diagram</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="life_cycle">
                  <label>life cycle</label>
                  <def>
                     <p>
								See <termref ref="state_machine">state machine</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="lifo">
                  <label>LIFO</label>
                  <def>
                     <p>
								Last in-first out.  See <termref ref="push-down_stack">
								push-down stack</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="list">
                  <label>list</label>
                  <def>
                     <p>
								A form of <termref ref="collection">collection</termref> whose 
								members are ordered, and need not be unique. 
							</p>
                  </def>
               </gitem>
               <gitem id="literary_expression">
                  <label>literary expression</label>
                  <def>
                     <p>
								A representation of a <termref ref="model">model</termref> in 
								text. The literary expression seeks to 
								balance the need for a rigorous, unambiguous description 
								of the model with the need for a rendition that can be easily read and
								interpreted by individuals who understand the general concepts         
								underlying object-oriented models, but who may not be schooled in
								formal model definition languages. 
							</p>
                  </def>
               </gitem>
               <gitem id="loinc">
                  <label>LOINC</label>
                  <def>
                     <p>
                        <loc href="http://www.regenstrief.org/loinc" target="_blank">Logical Observations, Identifiers, Names, and Codes</loc>
                     </p>
                  </def>
               </gitem>
               <gitem id="loosely_coupled">
                  <label>loosely coupled</label>
                  <def>
                     <p>
								Loosely coupled <termref ref="application_role">application roles</termref> 
								do not assume that common information about the subject 
								<termref ref="class">classes</termref> participating in a 
								<termref ref="message">message</termref> is available to system 
								components outside of the specific message.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-m">
            <head>M</head>
            <glist>
               <gitem id="mandatory">
                  <label>mandatory</label>
                  <def>
                     <p>
								If an <termref ref="attribute">attribute</termref> is
								designated as mandatory, all <termref ref="message_element">message 
								elements</termref> which make use of this         
								attribute SHALL contain a non-null value or they SHALL have a default
								that is not null. This requirement is indicated in the "mandatory" column in 
								the <termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="mandatory_association">
                  <label>mandatory association</label>
                  <def>
                     <p>
								An <termref ref="association">association</termref> with a 
								<termref ref="multiplicity">multiplicity</termref> minimum greater 
								than zero on one end.  A fully mandatory association is one with 
								a multiplicity minimum greater than zero on both ends. 
							</p>
                  </def>
               </gitem>
               <gitem id="markup">
                  <label>markup</label>
                  <def>
                     <p>Computer-processible annotations within a document. Markup encodes a description of a document&#8217;s storage layout and logical structure. In the context of HL7 Version 3, markup syntax is according to the <termref ref="xml">XML</termref> Recommendation.</p>
                  </def>
               </gitem>
               <gitem id="master_files">
                  <label>Master Files</label>
                  <def>
                     <p>
								Common lookup tables used by one or more application systems. 
							</p>
                  </def>
               </gitem>
               <gitem id="may">
                  <label>MAY</label>
                  <def>
                     <p>The conformance verb MAY is used to indicate a possibility. See the <termref ref="conformance_verb">conformance verb</termref> definition for more information.</p>
                  </def>
               </gitem>
               <gitem id="mdf">
                  <label>MDF</label>
                  <def>
                     <p>
								See <termref ref="message_development_framework">Message 
								Development Framework</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="message">
                  <label>message</label>
                  <def>
                     <p>
								A package of information communicated from one application to another. See 
								also <termref ref="message_type">message type</termref> and 
								<termref ref="message_instance">message instance</termref>.  
							</p>
                  </def>
               </gitem>
               <gitem id="message_development_framework">
                  <label>Message Development Framework</label>
                  <def>
                     <p>
								The collection of <termref ref="model">models</termref>, 
								methods, and tools that comprise the
								<termref ref="methodology">methodology</termref> for specifying 
								HL7 Version 3 messages. This         
								framework is used by the developers of the HL7 standards. 
							</p>
                  </def>
               </gitem>
               <gitem id="message_element">
                  <label>message element</label>
                  <def>
                     <p>
								A unit of structure within a <termref ref="message_type">
								message type</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="message_element_type">
                  <label>message element type</label>
                  <def>
                     <p>
								A portion of a <termref ref="message_type">message type</termref> 
								that describes one of the elements of the
								<termref ref="message">message</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="message_instance">
                  <label>message instance</label>
                  <def>
                     <p>
								A <termref ref="message">message</termref>, populated with data 
								values, and formatted for a specific 
								transmission based on a particular <termref ref="message_type"> 
								message type</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="message_payload">
                  <label>message payload</label>
                  <def>
                     <p>
								Data carried in a <termref ref="message">message</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="message_type">
                  <label>message type</label>
                  <def>
                     <p>
								A set of rules for constructing a <termref ref="message">message
								</termref> given a specific set of instance data. As such, it 
								also serves as a guide for parsing 
								a message to recover the instance data.
							</p>
                  </def>
               </gitem>
               <gitem id="meta-model">
                  <label>meta-model</label>
                  <def>
                     <p>
								A <termref ref="model">model</termref> used to specify other models. For         
								example, the meta-model for a relational database system might specify
								elements of type &#8216;Table&#8217;, &#8216;Record&#8217;, and 
								&#8216;Field.&#8217;. 
							</p>
                  </def>
               </gitem>
               <gitem id="methodology">
                  <label>methodology</label>
                  <def>
                     <p>
								Methods or rules followed in a particular discipline.
							</p>
                  </def>
               </gitem>
               <gitem id="mime">
                  <label>MIME</label>
                  <def>
                     <p>Multipurpose Internet Mail Extensions (MIME, <loc href="http://www.ietf.org/rfc/rfc2046.txt" target="_blank">RFC 2046</loc>)</p>
                  </def>
               </gitem>
               <gitem id="model">
                  <label>model</label>
                  <def>
                     <p>
								A representation of a <termref ref="domain">domain</termref> that 
								uses abstraction to express the relevant concepts. In HL7, the 
								model consists of a collection of <termref ref="schema">schema
								</termref>and other documentation. 
							</p>
                  </def>
               </gitem>
               <gitem id="multiplicity">
                  <label>multiplicity</label>
                  <def>
                     <p>
								1.  In the <termref ref="information_model">information model</termref>, 
								multiplicity is a <termref ref="specification">specification</termref> 
								of the minimum and maximum number of <termref ref="object">objects
								</termref>from each <termref ref="class">class</termref> that 
								can participate in an <termref ref="association">association</termref>.  
								Multiplicity is specified for each end of the association.
							</p>
                  </def>
                  <def>
                     <p>
								2.  In the <termref ref="hierarchical_message_description"> 
								Hierarchical Message Description</termref> (HMD), multiplicity  
								depicts the minimum and maximum number of occurrences of a 
								<termref ref="message_element">message element</termref>  
								expression in a <termref ref="collection">collection</termref>.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-n">
            <head>N</head>
            <glist>
               <gitem id="navigability">
                  <label>navigability</label>
                  <def>
                     <p>
								Direction in which an <termref ref="association">association 
								</termref>can be navigated (either one way or both ways). 
							</p>
                  </def>
               </gitem>
               <gitem id="not_permitted">
                  <label>not permitted</label>
                  <def>
                     <p>
								One of the allowed values in <termref ref="conformance_requirement"> 
								conformance requirements</termref>. Abbreviated as NP, it
								means that the <termref ref="message_element">message element</termref> 
								is never sent for that <termref ref="message_type">message type</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="null">
                  <label>null</label>
                  <def>
                     <p>
								A value for a data element which indicates the absence of data. A number
								of &#8220;flavors&#8221; of null are possible and are enumerated in the
								<termref ref="domain">domain</termref> NullFlavor. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-o">
            <head>O</head>
            <glist>
               <gitem id="object">
                  <label>object</label>
                  <def>
                     <p>
								An <termref ref="instance">instance</termref> of a 
								<termref ref="class">class</termref>. A part of an information 
								system containing a collection of related data (in the form of 
								<termref ref="attribute">attributes</termref>) and
								procedures (methods) for operating on that data.  
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlstructclasses">Classes
								 section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="object_identifier">
                  <label>object identifier</label>
                  <def>
                     <p>
								A scheme to provide globally unique identifiers. This object 
								identifier (OID) scheme is an ISO
								standard (ISO 8824:1990), and has been adopted as a CSA standard         
								(Z243.110).
							</p>
                     <p>The <loc href="http://www.hl7.org/oid/index.cfm" target="_blank">HL7 OID Registry</loc> is available online.</p>
                  </def>
               </gitem>
               <gitem id="object_identity">
                  <label>object identity</label>
                  <def>
                     <p>
								The feature that the existence of an <termref ref="object">object
								</termref> is independent of any values associated with the object. 
							</p>
                  </def>
               </gitem>
               <gitem id="object-based">
                  <label>object-based</label>
                  <def>
                     <p>
								Any method, language, or system that supports 
								<termref ref="object_identity">object identity</termref>, 
								classification, and encapsulation. An object-based system does 
								not support <termref ref="specialization">specialization
								</termref>. Ada is an example of an object-based 
								implementation language. 
							</p>
                  </def>
               </gitem>
               <gitem id="obsolescent_message_type">
                  <label>obsolescent message type</label>
                  <def>
                     <p>
								A <termref ref="message_type">message type</termref> that has been 
								marked for deletion in a future version of HL7. 
							</p>
                  </def>
               </gitem>
               <gitem id="obsolete_message_type">
                  <label>obsolete message type</label>
                  <def>
                     <p>
								A <termref ref="message_type">message type</termref>, previously 
								declared obsolescent, that has been removed or replaced in a 
								particular version of HL7. 
							</p>
                  </def>
               </gitem>
               <gitem id="oid">
                  <label>OID</label>
                  <def>
                     <p>
								See <termref ref="object_identifier">object identifier</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="optional">
                  <label>optional</label>
                  <def>
                     <p>
								See <termref ref="inclusion">inclusion</termref>.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-p">
            <head>P</head>
            <glist>
               <gitem id="partial_state">
                  <label>partial state</label>
                  <def>
                     <p>
								Part of a <termref ref="state_machine">state machine</termref>. A 
								state machine MAY have multiple partial <termref ref="state">
								states</termref> effective at the same time; the multiple 
								partial states can be summarized to one <termref ref="joint_state">
								joint state</termref> of the state machine. 
							</p>
                  </def>
               </gitem>
               <gitem id="predicate_reference">
                  <label>predicate reference</label>
                  <def>
                     <p>
								In the <termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref>, 
								a <termref ref="message_element">message element</termref> 
								that is referred to in the predicate defining the conditional 
								presence of another message element. 
							</p>
                  </def>
               </gitem>
               <gitem id="primitive_data_type">
                  <label>primitive data type</label>
                  <def>
                     <p>
								A <termref ref="data_type">data type</termref> that is defined as a 
								single entity, and whose full semantic is contained in its definition. 
							</p>
                  </def>
               </gitem>
               <gitem id="primitive_message_element_type">
                  <label>primitive message element type</label>
                  <def>
                     <p>
								A <termref ref="message_element_type">message element type
								</termref> that contains a single datum, with no subordinate 
								components. Examples include String and Number. 
							</p>
                  </def>
               </gitem>
               <gitem id="property">
                  <label>property</label>
                  <def>
                     <p>
								1. Any <termref ref="attribute">attribute</termref>, 
								<termref ref="association">association</termref>, method, or 
								<termref ref="state">state</termref> model defined for a
								<termref ref="class">class</termref> or <termref ref="object">
								object</termref>.
							</p>
                  </def>
                  <def>
                     <p>
								2. In a <termref ref="hierarchical_message_description"> 
								Hierarchical Message Description</termref> (HMD), the column 
								that states the name of the class, attribute or 
								<termref ref="association_role_name">association 
								role name</termref> as it appears in the 
								<termref ref="reference_information_model">Reference 
								Information Model</termref> (RIM).
							</p>
                  </def>
               </gitem>
               <gitem id="push-down_stack">
                  <label>push-down stack</label>
                  <def>
                     <p>
								Also known as a &#8220;last in-first out&#8221; (LIFO) 
								<termref ref="list">list</termref>, a list 
								maintained by a Technical Committee as it analyses the 
								<termref ref="refined_message_information_model">
								Refined Message Information Model
								</termref> (R-MIM) and builds a 
								<termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref>, in which the last 
								<termref ref="class">class</termref> added 
								is always the first class removed. (A metaphoric reference to the spring-loaded 
								plate carriers used in institutional dining halls, where the new
								plates added to the top of the stack push down the earlier plates, so
								the newest plate is taken off the stack first). 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-q">
            <head>Q</head>
            <glist>
               <gitem id="query">
                  <label>query</label>
                  <def>
                     <p>Queries are the primary mechanism for retrieving information from computer systems. Many database management systems use the Structured Query Language (SQL) standard query format.</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-r">
            <head>R</head>
            <glist>
               <gitem id="realm">
                  <label>realm</label>
                  <def>
                     <p>
								A <termref ref="vocabulary_domain_qualifier">vocabulary 
								domain qualifier</termref> used in a 
								<termref ref="domain_specification">domain specification</termref>, 
								which allows the <termref ref="vocabulary_domain">vocabulary 
								domain</termref> of a <termref ref="coded_attribute">
								coded attribute</termref> to be 
								specialized according to the geographical, organizational, or 
								political environment where the HL7 standard is being used. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gvocabqualify">
								 Vocabulary Domain Qualifiers section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="receiver_responsibility">
                  <label>receiver responsibility</label>
                  <def>
                     <p>
								An obligation on an <termref ref="application_role">application 
								role</termref> that receives an <termref ref="interaction">
								interaction</termref>as defined in the 
								<termref ref="interaction_model">interaction model</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="recursion">
                  <label>recursion</label>
                  <def>
                     <p>
								An <termref ref="association">association</termref> that leads 
								from a <termref ref="class">class</termref> directly or indirectly 
								back to that class. 
							</p>
                  </def>
               </gitem>
               <gitem id="reference_information_model">
                  <label>Reference Information Model</label>
                  <def>
                     <p>
								The HL7 <termref ref="information_model">information model
								</termref> from which all other information models 
								(e.g., R-MIMs) and <termref ref="message">messages</termref> 
								are derived.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdltypes">Information Model
								 section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="refined_message_information_model">
                  <label>Refined Message Information Model</label>
                  <def>
                     <p>
								An information structure that represents the requirements for a 
								set of <termref ref="message">messages</termref>.  A 
								<termref ref="constraint">constrained</termref> 
								subset of the <termref ref="reference_information_model">
								Reference Information Model</termref> (RIM) which MAY contain additional 
								<termref ref="class">classes</termref> that are cloned from 
								RIM classes. Contains those classes, <termref ref="attribute">
								attributes</termref>, <termref ref="association">associations</termref>, 
								and <termref ref="data_type">data types</termref> that are needed to 
								support one or more <termref ref="hierarchical_message_description">
								Hierarchical Message Descriptions</termref> (HMD). A single 
								message can be shown as a particular pathway through the 
								classes within an R-MIM. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdltypes">Information Model
								 section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="required">
                  <label>required</label>
                  <def>
                     <p>
								One of the allowed values in 
								<termref ref="conformance_requirement">conformance 
								requirements</termref>. Abbreviated as 
								R, it means that the <termref ref="message_element">message elements
								</termref> SHALL appear every time that particular 
								<termref ref="message_type">message type</termref> is used for an 
								<termref ref="interaction">interaction</termref>. If the data is
								available, the element SHALL carry the data, otherwise a 
								<termref ref="blank">blank</termref> MAY be sent. 
							</p>
                  </def>
               </gitem>
               <gitem id="responsibility">
                  <label>responsibility</label>
                  <def>
                     <p>
								An action required of the receiver of a <termref ref="message">
								message</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="rim">
                  <label>RIM</label>
                  <def>
                     <p>
								See <termref ref="reference_information_model">Reference 
								Information Model</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="r-mim">
                  <label>R-MIM</label>
                  <def>
                     <p>
								See <termref ref="refined_message_information_model">
								Refined Message Information Model</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="r-mim_diagram">
                  <label>R-MIM diagram</label>
                  <def>
                     <p>
								A diagrammatic representation of a 
								<termref ref="refined_message_information_model">
								Refined Message Information Model</termref> (R-MIM). Possible 
								formats include <termref ref="uml">UML</termref> and the HL7 R-MIM graphic format. 
							</p>
                  </def>
               </gitem>
               <gitem id="role">
                  <label>role</label>
                  <def>
                     <p>
								1. A function or position. 
							</p>
                  </def>
                  <def>
                     <p>
								2.  A <termref ref="reference_information_model">
								Reference Information Model</termref>
                        <termref ref="class">class</termref> that defines the 
								competency of an Entity class. 
								Each <termref ref="role">role</termref> is played by one 
								Entity (the Entity that is in the 
								role) and is usually scoped by another.
							</p>
                  </def>
                  <def>
                     <p>
								3. In <termref ref="uml">UML</termref>, each end of an <termref ref="association">association
								</termref> is designated as a role to 
								reflect the function that class plays in the association.
							</p>
                  </def>
               </gitem>
               <gitem id="role_name">
                  <label>role name</label>
                  <def>
                     <p>
								See <termref ref="association_role_name">association role 
								name</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="root_class">
                  <label>root class</label>
                  <def>
                     <p>
								The <termref ref="class">class</termref> on which a 
								<termref ref="message">message</termref> is based. Usually the 
								root class for a family of messages is either the 
								<termref ref="subject_class">subject class</termref> or the 
								class that will be first represented in the set of messages 
								to be built. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-s">
            <head>S</head>
            <glist>
               <gitem id="scenario">
                  <label>scenario</label>
                  <def>
                     <p>
								A statement of relevant <termref ref="event">events</termref> 
								from the problem <termref ref="domain">domain</termref>, defined 
								as a sequence of <termref ref="interaction">interactions</termref>. 
								The scenario provides one set of interactions that the
								modeling committee expects will typically occur in the domain.
								Usually, a <termref ref="sequence_diagram">sequence diagram</termref> is 
								constructed to show a group of
								interactions for a single <termref ref="scenario">scenario</termref>. 
								Each scenario is displayed
								as a subset of the <termref ref="interaction_model">interaction model</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="schema">
                  <label>schema</label>
                  <def>
                     <p>
								1. A diagrammatic presentation, a structured framework, or a plan.
							</p>
                  </def>
                  <def>
                     <p>
								2.  A set of requirements that need to be met in order for a
								document or set of data to be a valid expression within the
								context of a particular grammar. For example, XML Schema is a 
								<termref ref="specification">specification</termref> in SGML 
								of the structure of a document or set of data.
							</p>
                  </def>
               </gitem>
               <gitem id="schema_view">
                  <label>schema view</label>
                  <def>
                     <p>
								A link to the <termref ref="schema">schema</termref> used to 
								validate XML messages that conform to a particular 
								<termref ref="message_type">message type</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="scope">
                  <label>scope</label>
                  <def>
                     <p>
								1.  A definition of the range or extent of a project undertaken 
								by a Technical Committee.
							</p>
                  </def>
                  <def>
                     <p>
								2.  A means of <termref ref="constraint">constraining</termref> a 
								<termref ref="role">role</termref> 
								(ie. a role is &#8220;scoped by&#8221; an entity).
							</p>
                  </def>
               </gitem>
               <gitem id="section">
                  <label>section</label>
                  <def>
                     <p>
								In the HL7 Version 3 Guide, a method of grouping related information 
								into <termref ref="domain">domains</termref>. 
								These domains include Infrastructure Management,
								Administrative Management, and Health &amp; Clinical Management.       
							</p>
                  </def>
               </gitem>
               <gitem id="semantic">
                  <label>Semantic</label>
                  <def>
                     <p>In the context of a technical specification, semantic refers to the meaning of something as distinct from its exchange representation. Syntax can change without affecting semantics.</p>
                  </def>
               </gitem>
               <gitem id="sequence_diagram">
                  <label>sequence diagram</label>
                  <def>
                     <p>
								See <termref ref="interaction_diagram">interaction diagram
								</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="set">
                  <label>set</label>
                  <def>
                     <p>
								A form of <termref ref="collection">collection</termref> which 
								contains an unordered <termref ref="list">list</termref> of 
								unique elements of a single type.   
							</p>
                  </def>
               </gitem>
               <gitem id="sgml">
                  <label>SGML</label>
                  <def>
                     <p>Standard Generalized Markup Language, ISO 8879:1986(E) as amended and corrected</p>
                  </def>
               </gitem>
               <gitem id="shall">
                  <label>SHALL</label>
                  <def>
                     <p>The conformance verb SHALL is used to indicate a requirement. See the <termref ref="conformance_verb">conformance verb</termref> definition for more information.</p>
                  </def>
               </gitem>
               <gitem id="should">
                  <label>SHOULD</label>
                  <def>
                     <p>The conformance verb SHOULD is used to indicate a recommendation. See the <termref ref="conformance_verb">conformance verb</termref> definition for more information.</p>
                  </def>
               </gitem>
               <gitem id="snomed">
                  <label>SNOMED</label>
                  <def>
                     <p>
                        <loc href="http://www.snomed.org/" target="_blank">Systematized Nomenclature of Medicine</loc>
                     </p>
                  </def>
               </gitem>
               <gitem id="specialization">
                  <label>specialization</label>
                  <def>
                     <p>
								An <termref ref="association">association</termref> between two 
								<termref ref="class">classes</termref> (designated 
								<termref ref="superclass">superclass</termref> and 
								<termref ref="subclass">subclass</termref>),
								in which the subclass is derived from the superclass. The 
								subclass inherits all properties from the superclass, 
								including <termref ref="attribute">attributes</termref>, 
								relationships, and <termref ref="state">states</termref>, but 
								also adds new ones to extend the capabilities of the superclass. 
							</p>
                  </def>
               </gitem>
               <gitem id="specification">
                  <label>specification</label>
                  <def>
                     <p>
								A detailed description of the required characteristics of a product. 
							</p>
                  </def>
               </gitem>
               <gitem id="sponsor">
                  <label>sponsor (of an application)</label>
                  <def>
                     <p>
								In the context of <termref ref="conformance_claim">conformance claims
								</termref>, the vendor, in-house developer, or provider of 
								public domain software for a healthcare information system. 
							</p>
                  </def>
               </gitem>
               <gitem id="state">
                  <label>state</label>
                  <def>
                     <p>
								A named condition of a <termref ref="class">class</termref>
                        <termref ref="instance">instance</termref> (<termref ref="object">
								object</termref>) that can be tested by
								examination of the instance's <termref ref="attribute">attributes
								</termref>and <termref ref="association">associations</termref>.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlbehave">
								 Dynamic Behavior section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="state_attribute">
                  <label>state attribute</label>
                  <def>
                     <p>
								An <termref ref="attribute">attribute</termref> describing the 
								current <termref ref="state">state</termref> of an 
								<termref ref="object">object</termref>. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlattrib">
								 Attributes section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="state_diagram">
                  <label>state diagram</label>
                  <def>
                     <p>
								A graphical representation of a <termref ref="state_transition_model"> 
								state transition model</termref> showing <termref ref="state">states
								</termref>as vertices (nodes) and <termref ref="state_transition">
								state transitions</termref> as directed arcs (arrows) between the nodes. 
							</p>
                  </def>
               </gitem>
               <gitem id="state_flag">
                  <label>state flag</label>
                  <def>
                     <p>
								A discrete value of a single enumerated <termref ref="domain">domain
								</termref>of partial <termref ref="state">states</termref>. State 
								flags are included in a state <termref ref="attribute">attribute
								</termref> in a <termref ref="message_instance">message instance</termref> 
								that indicates the <termref ref="joint_state">joint state</termref> 
								of an object. 
							</p>
                  </def>
               </gitem>
               <gitem id="state_machine">
                  <label>state machine</label>
                  <def>
                     <p>
								A description of the life cycle for <termref ref="instance">instances
								</termref>of a <termref ref="class">class</termref>, defined by a 
								<termref ref="state_transition_model">state transition model</termref>.  
							</p>
                  </def>
               </gitem>
               <gitem id="state_transition">
                  <label>state transition</label>
                  <def>
                     <p>
								A change in the <termref ref="state">state</termref> of an 
								<termref ref="object">object</termref>, as a result of a change 
								in its <termref ref="attribute">attributes</termref> 
								or <termref ref="association">associations</termref>.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3ginfomdlbehave">
								 Dynamic Behavior section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="state_transition_model">
                  <label>state transition model</label>
                  <def>
                     <p>
								A graphical representation of the life cycle of a 
								<termref ref="class">class</termref>. The <termref ref="model">
								model</termref> depicts all of the relevant <termref ref="state">
								states</termref> of a class, and the valid transitions 
								from state to state. 
							</p>
                  </def>
               </gitem>
               <gitem id="steward_committee">
                  <label>steward committee</label>
                  <def>
                     <p>
								The Technical Committee within HL7 which has primary responsibility
								for specifying properties for a <termref ref="class">class
								</termref> in the <termref ref="reference_information_model">
								Reference Information Model</termref> (RIM). The steward 
								committee must be consulted on any proposed changes to the 
								properties of classes under its stewardship.
							</p>
                  </def>
               </gitem>
               <gitem id="stewardship_representative">
                  <label>stewardship representative</label>
                  <def>
                     <p>
								An individual member of the <termref ref="steward_committee">
								steward committee</termref>, authorized by the
								committee to speak on behalf of the committee, and to represent the
								interests of the steward committee. 
							</p>
                  </def>
               </gitem>
               <gitem id="storyboard">
                  <label>storyboard</label>
                  <def>
                     <p>
								A narrative of relevant <termref ref="event">events</termref> 
								defined using <termref ref="interaction_diagram">interaction  
								diagrams</termref>or use cases.  The storyboard provides one set
								of <termref ref="interaction">interactions</termref> that the 
								modeling committee expects will typically
								occur in the <termref ref="domain">domain</termref>.  
							</p>
                  </def>
               </gitem>
               <gitem id="storyboard_diagram">
                  <label>storyboard diagram</label>
                  <def>
                     <p>
								See <termref ref="interaction_diagram">interaction diagram</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="structural_attribute">
                  <label>structural attribute</label>
                  <def>
                     <p>
								An <termref ref="attribute">attribute</termref> whose coded 
								values are needed to fully interpret the 
								<termref ref="class">class</termref> with which it is 
								associated.
							</p>
                  </def>
               </gitem>
               <gitem id="stylesheet">
                  <label>stylesheet</label>
                  <def>
                     <p>A file that describes how to display an XML document of a given type</p>
                  </def>
               </gitem>
               <gitem id="subclass">
                  <label>subclass</label>
                  <def>
                     <p>
								A <termref ref="class">class</termref> that is the 
								<termref ref="specialization">specialization</termref> of 
								another class (<termref ref="superclass">superclass</termref>). 
							</p>
                  </def>
               </gitem>
               <gitem id="subject_area">
                  <label>subject area</label>
                  <def>
                     <p>
								A convenient aggregation of <termref ref="model">model</termref>
                        <termref ref="class">classes</termref> used to partition large 
								models into manageable subsets. 
							</p>
                  </def>
               </gitem>
               <gitem id="subject_class">
                  <label>subject class</label>
                  <def>
                     <p>
								A <termref ref="class">class</termref> that a Technical 
								Committee designates as the central focus of a 
								<termref ref="collection">collection</termref> of 
								<termref ref="message">messages</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="sub-section">
                  <label>sub-section</label>
                  <def>
                     <p>
								In the HL7 Version 3 Guide, a <termref ref="section">section</termref> 
								within a major section.
							</p>
                  </def>
               </gitem>
               <gitem id="sub-state">
                  <label>sub-state</label>
                  <def>
                     <p>
								An identifiable <termref ref="state">state</termref> of a 
								<termref ref="class">class</termref> that has a more specific
								definition than, and is entirely encompassed within the scope         
								of, its <termref ref="super-state">super-state</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="superclass">
                  <label>superclass</label>
                  <def>
                     <p>
								A <termref ref="class">class</termref> that is the 
								<termref ref="generalization">generalization</termref> of one or more 
								other classes (<termref ref="subclass">subclasses</termref>). 
							</p>
                  </def>
               </gitem>
               <gitem id="super-state">
                  <label>super-state</label>
                  <def>
                     <p>
								A <termref ref="state">state</termref> of a <termref ref="class">
								class</termref> that encompasses two or more independent 
								<termref ref="sub-state">sub-states</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="surface_form">
                  <label>surface form (of a concept)</label>
                  <def>
                     <p>
								A code value or textual description that represents a concept
								identified by an HL7 <termref ref="concept_identifier">
								concept identifier</termref>. There MAY be many different         
								surface forms associated with a single concept identifier. 
							</p>
                  </def>
               </gitem>
               <gitem id="system">
                  <label>system</label>
                  <def>
                     <p>
								1. An end user <termref ref="application">application.</termref>
                     </p>
                  </def>
                  <def>
                     <p>
								2. In HL7, a group of <termref ref="message">messages</termref> 
								that work together. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-t">
            <head>T</head>
            <glist>
               <gitem id="table_view">
                  <label>table view</label>
                  <def>
                     <p>
								An expression of the <termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref> (HMD) common and 
								<termref ref="message_type">message type</termref> definition 
								condensed in size to fit on a printed page.
							</p>
                  </def>
               </gitem>
               <gitem id="tightly_coupled">
                  <label>tightly coupled</label>
                  <def>
                     <p>
								Tightly coupled <termref ref="application_role">
								application roles</termref> assume that 
								common information about the <termref ref="subject_class">
								subject classes</termref> participating in a 
								<termref ref="message">message</termref> is available to 
								system components outside of the specific message. 
							</p>
                  </def>
               </gitem>
               <gitem id="transaction">
                  <label>transaction</label>
                  <def>
                     <p>
								A complete set of <termref ref="message">messages</termref> for a 
								particular <termref ref="trigger_event">trigger event</termref>, 
								e.g., a message and a response. 
							</p>
                  </def>
               </gitem>
               <gitem id="transport_wrapper">
                  <label>transport wrapper</label>
                  <def>
                     <p>
								A <termref ref="wrapper">wrapper</termref> that contains 
								information needed by a sending <termref ref="application">application</termref> or 
								<termref ref="message">message</termref> handling service to route 
								the <termref ref="message_payload">message payload</termref> to the
								designated receiver. All HL7 Version 3 messages SHALL have an 
								appropriately configured transport wrapper.  
							</p>
                  </def>
               </gitem>
               <gitem id="trigger_event">
                  <label>trigger event</label>
                  <def>
                     <p>
								An <termref ref="event">event</termref> which, when recorded
								or recognized by an <termref ref="application">application</termref>, 
								indicates the need for an information flow to one or more other 
								applications, resulting in one or more <termref ref="interaction">
								interactions</termref>. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-u">
            <head>U</head>
            <glist>
               <gitem id="uml">
                  <label>UML</label>
                  <def>
                     <p>
								See <termref ref="unified_modeling_language">
								Unified Modeling Language</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="unified_modeling_language">
                  <label>Unified Modeling Language</label>
                  <def>
                     <p>
								A language for the creation of <termref ref="domain">domain</termref>
                        <termref ref="model">models</termref>. <loc href="http://www.uml.org" target="_blank">UML</loc> was created in order to 
								unify several well-known object-oriented modeling 
								<termref ref="methodology">methodologies</termref>, 
								including those of Booch, Rumbaugh, Jacobson, and others. 
							</p>
                  </def>
               </gitem>
               <gitem id="union_message">
                  <label>union message</label>
                  <def>
                     <p>
								A <termref ref="message_type">message type</termref> that contains 
								the elements of several <termref ref="message">message</termref> 
								structures drawn from the same 
								<termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref>.  A union message 
								includes all the <termref ref="message_element">message elements 
								</termref>that SHALL be sent from one <termref ref="application_role">
								application role</termref> to all other application roles in 
								response to a <termref ref="trigger_event">trigger event</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="user">
                  <label>user</label>
                  <def>
                     <p>
								In the context of <termref ref="conformance_claim">conformance 
								claims</termref>, the organization that uses an
								<termref ref="application">application</termref>. This is  
								frequently the buyer but in some cases the user and 
								<termref ref="sponsor">sponsor</termref> organizations may be 
								parts of the same organization, or otherwise have a business 
								relationship other then vendor-buyer. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-v">
            <head>V</head>
            <glist>
               <gitem id="v3_guide">
                  <label>Version 3 Guide</label>
                  <def>
                     <p>
								A companion to the Version 3 Standard which contains the 
								<termref ref="methodology">methodological</termref> information
								an HL7 member needs to understand the Version 3 standard.
							</p>
                  </def>
               </gitem>
               <gitem id="valid_document">
                  <label>Valid Document</label>
                  <def>
                     <p>A document which meets all of the validity constraints in the XML Specification</p>
                  </def>
               </gitem>
               <gitem id="value_set">
                  <label>value set</label>
                  <def>
                     <p>
								A <termref ref="vocabulary_domain">vocabulary domain</termref> 
								that has been <termref ref="constraint">constrained</termref> 
								to a particular <termref ref="realm">realm</termref> and 
								<termref ref="coding_system">coding system</termref>. 
							</p>
                  </def>
               </gitem>
               <gitem id="vocabulary">
                  <label>vocabulary</label>
                  <def>
                     <p>
								The set of valid values for a <termref ref="coded_attribute">
								coded attribute</termref> or field.
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gvocab">
								 Vocabulary section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="vocabulary_domain">
                  <label>vocabulary domain</label>
                  <def>
                     <p>
								The set of all concepts that can be taken as valid values in an 
								<termref ref="instance">instance</termref> of a 
								<termref ref="coded_attribute">coded attribute</termref> or field; a 
								<termref ref="constraint">constraint</termref> applicable to code 
								values. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="mbf4vocabudomrim">
								 Vocabulary Domains section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="vocabulary_domain_qualifier">
                  <label>vocabulary domain qualifier</label>
                  <def>
                     <p>
								Part of a <termref ref="vocabulary_domain_specification">
								vocabulary domain specification</termref>. The two existing 
								qualifiers are <termref ref="extensibility_qualifier">
								extensibility</termref> and <termref ref="realm">realm</termref>. 
							</p>
                     <p>
							   For more information refer to the 
								<ilxspecref spec="../../help/v3guide/v3guide" ref="v3gvocabqualify">
								 Vocabulary Domain Qualifiers section</ilxspecref> of the Version 3 Guide.
							</p>
                  </def>
               </gitem>
               <gitem id="vocabulary_domain_specification">
                  <label>vocabulary domain specification</label>
                  <def>
                     <p>
								A column in the <termref ref="hierarchical_message_description">
								Hierarchical Message Description</termref> that specifies the 
								<termref ref="vocabulary_domain">vocabulary domain</termref> 
								associated with a <termref ref="coded_attribute">
								coded attribute</termref>. 
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-w">
            <head>W</head>
            <glist>
               <gitem id="w3c">
                  <label>W3C</label>
                  <def>
                     <p>
                        <loc href="http://www.w3c.org/" target="_blank">The World Wide Web Consortium, an international industry consortium </loc>
                     </p>
                  </def>
               </gitem>
               <gitem id="w3c_schema">
                  <label>W3C Schema</label>
                  <def>
                     <p>The three-part schema specification issued by the W3C<br/>
                        <list role="unordered">
                           <item>
                              <loc href="http://www.w3.org/TR/xmlschema-0/" target="_blank">XML Schema Part 0: Primer , W3C Recommendation, 2-May-2001</loc>
                           </item>
                           <item>
                              <loc href="http://www.w3.org/TR/xmlschema-1/" target="_blank">XML Schema Part 1: Structures, W3C Recommendation, 2-May-2001</loc>
                           </item>
                           <item>
                              <loc href="http://www.w3.org/TR/xmlschema-2/" target="_blank">XML Schema Part 2: Datatypes, W3C Recommendation, 2-May-2001</loc>
                           </item>
                        </list>
                     </p>
                  </def>
               </gitem>
               <gitem id="well_formed_document">
                  <label>Well-formed document</label>
                  <def>
                     <p>A document which meets all of the well-formedness constraints in the XML Specification</p>
                  </def>
               </gitem>
               <gitem id="wrapper">
                  <label>wrapper</label>
                  <def>
                     <p>
								The control or envelope information in which the 
								<termref ref="message_payload">message payload</termref> 
								resides. See <termref ref="transport_wrapper">
								transport wrapper</termref> and 
								<termref ref="control_event_wrapper">control event wrapper
								</termref>.
							</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-x">
            <head>X</head>
            <glist>
               <gitem id="xhtml">
                  <label>XHTML</label>
                  <def>
                     <p>
                        <loc href="http://www.w3.org/TR/xhtml1/" target="_blank">XHTML 1.0. A Reformulation of HTML 4 in XML 1.0. W3C Recommendation 26-January-2000, revised 1 August 2002</loc>
                     </p>
                  </def>
               </gitem>
               <gitem id="xml">
                  <label>XML</label>
                  <def>
                     <p>
								See <termref ref="extensible_markup_language">Extensible 
								Markup Language</termref>.
							</p>
                  </def>
               </gitem>
               <gitem id="xml_declaration">
                  <label>XML Declaration</label>
                  <def>
                     <p>An XML document consists of a prolog, root document element, and other objects.  A data object is an XML document if it is well-formed, as defined in the XML specification. </p>
                  </def>
               </gitem>
               <gitem id="xsl">
                  <label>XSL</label>
                  <def>
                     <p>
                        <loc href="http://www.w3.org/Style/XSL/)" target="_blank">Extensible Style Language, a specification of the W3C</loc> An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary.</p>
                  </def>
               </gitem>
               <gitem id="xslt">
                  <label>XSLT</label>
                  <def>
                     <p>
                        <loc href="http://www.w3.org/TR/xslt/" target="_blank">XSL transformation language, a specification of the W3C</loc> 
A language for transforming XML documents into other XML documents.

					</p>
                  </def>
               </gitem>
            </glist>
         </div2>
         <div2 id="glossary-y">
            <head>Y</head>
         </div2>
         <div2 id="glossary-z">
            <head>Z</head>
         </div2>
      </div1>
   </body>
</spec>