C-MIMCore Glossary:
See
CMET Message
Information Model.
Capability
Defined in Personnel Management:
A quantitative, semi-quantitative, or qualitative assessment of the ability of an instance of a Party in a Role to perform
and/or participate in a specific activity or task. An a subtype of Credential, a Capability is assigned to an instance of
a Party (the instance with the ability) by another instance of Party (the Person or Organization assessing the capability).
A Capability is often a specific (e.g. 'can do this task' (Person), or 'has 5 slots available' (Organization)).
cardinalityCore Glossary:
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
Hierarchical Message Description (the minimum and
maximum number of occurrences of the
message element).
Certificate
Defined in Personnel Management:
A subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the Certificate. A Certificate is often viewed as
'less formal' than a Credential. However, in this model, a Credential is an abstract concept that captures the notion of
verifiable documentation various types of skills, etc. claimed to be possessed by a Person or Organization (see Credential)
Certificate of Verification
Defined in Personnel Management:
A collection of data documenting that a specific instance of a Credential has been verified/validated in association with
the requirement for that credential for either an Assignment of a Party in a Role to a Position or the requirement for a particular
instance of a Credential in order for a Party in a Role to qualify for a specific instance of a Privilege. A Certificate
of Verification will minimally include a definitive identification of the verifier, a date/time stamp of verification, and
(optionally) a structured or unstructured statement of the verification process, contacts, etc.
Character DataCore Glossary: Text in a particular coding (e.g., ASCII), as distinguished from binary data.
choiceCore Glossary:
A
message 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.
choice due to specializationCore Glossary:
A choice that arises when a
Hierarchical Message
Description includes (a) an object view which is associated
with a
class that is a
superclass 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
message instances may contain
different object views. The choice structure is used to
accommodate the alternatives.
classCore Glossary:
An abstraction of a thing or concept in a particular
application
domain.
For more information refer to the
Classes
section of the V3 Guide.
classifier attributeCore Glossary:
An
attribute used in
generalization
hierarchies to indicate which of the
specializations
is the focus of the
class
.
For more information refer to the
Attributes section of the V3 Guide.
cloneCore Glossary:
A
class from the
Reference
Information Model
(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.
CMETCore Glossary:
See
Common Message Element Type.
CMET Message Information ModelCore Glossary:
A form of
Refined Message Information Model (R-MIM) constructed
to represent the totality of concepts embodied in the individual R-MIMs
needed to support the definition of HL7's
Common Message Element Types.
coded attributeCore Glossary:
An
attribute in the
Reference
Information Model
(RIM) with a base
data type of
CD, CE, CS, or CV.
coding strengthCore Glossary:
An
extensibility qualifier
that specifies whether or not a code set can be expanded to meet
local implementation needs.
coding systemCore Glossary:
A scheme for representing concepts using (usually) short
concept identifiers to denote
the concepts that are members of the system; defines a set of
unique concept codes. Examples of coding systems are ICD-9,
LOINC and SNOMED.
collectionCore Glossary:
An aggregation of similar
objects.
The forms of collection used by HL7 are
set
,
bag, and
list. Objects which may be
found in collections include
data types
and
message element
types.
common message element type (CMET)Core Glossary:
A
message type in a
Hierarchical
Message Description (HMD) that may be included
by reference in other HMD's.
For more information refer to the
Common Message Element Types section
of the V3 Guide.
composite aggregationCore Glossary:
A type of
association between
objects, indicating a
whole-part relationship.
composite data typeCore Glossary:
A
data type assigned to a
message element type that
contains one or more components, each of which is represented
by an assigned data type.
composite message element typeCore Glossary:
A
message element type
that contains subordinate heterogeneous
message
types.
concept identifierCore Glossary:
A unique identification assigned to a concept by the
HL7 organization.
conformance claimCore Glossary:
A
specification 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
application role. 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
messages it
sends or receives. This may include the
Implementation Technology
Specifications that it supports, the use of specific
optional protocols or character sets, or many other
behaviors.
conformance claim setCore Glossary:
A list of the identifiers of specific HL7
conformance claims, used by a
sponsor to describe the conformance of its application.
conformance requirementCore Glossary:
A column in the
Hierarchical Message
Description (HMD) that designates whether the
system must communicate an
attribute's
value if a value is available. Allowed values are
required (must be included),
not required (may be left out) or
not
permitted (may never be included.) Items listed as
not required in the HL7 specification must be declared by a
vendor as either required or not permitted when a
conformance claim is asserted
for that
message type.
connectionCore Glossary:
In an
information model, a
specified relationship between two
classes
.
constraintCore Glossary:
Narrowing down of the possible values for an
attribute; a suggestion of
legal values for an attribute (by indicating the
data type that applies, by
restriction of the data type, or by definition
of the
domain 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
association may limit the
cardinality of the association
or alter the navigability of the association (direction in which
the association can be navigated). A
Refined Message Information Model (R-MIM)
class may be constrained by
choosing a subset of its
Reference
Information Model (RIM) properties (i.e., classes
and attributes) or by cloning, in which the class’ name is
changed.
For more information refer to the
Constraints section of the V3 Guide.
control event wrapperCore Glossary:
A
wrapper that contains
domain specific administrative
information related to the "controlled event" which is being
communicated as a messaging interaction. The control event
wrapper is used only in
messages
that convey status, or in commands for logical operations being
coordinated between applications (e.g., the coordination of
query specification/query response interactions).
couplingCore Glossary:
1. An interaction between systems or between properties of a system.
Core Glossary:
2. With regard to
application roles
, refers to whether or not additional information
about the
subject classes
participating in a
message may be
commonly available to system components outside of the specific message.
Credential (Definition and Instantiation)
Defined in Personnel Management:
An abstract concept (i.e. there are no physical instances of Credential per se) that represents the various collections of
data associated with a verifiable claim by a Person or Organization as to one or more skills, abilities, education, experience,
etc. A Credential collects (at minimum) the date/time of issuance and an associated expiration date after which the credential
must be renewed to remain valid. The important differentiator between a Credential (or, more correctly, one of its concrete
subtypes) and a Qualification is that the former (Credential) can always be verified in terms of the Credential being issued
by/associated with a 'credentialing organization' responsible for issuing an instance of a particular credential to an instance
of a Party, whereas the latter (Qualification) is simply a statement by the Party of a particular skill, ability, etc. (NOTE:
The notion of 'verifiable' that differentiates a Credential from a Qualification is similar to the difference between a Responsibility
and a Privilege in that both a Credential and a Privilege involve a formal relationship between at least two instances of
Party, whereas a Qualification and a Responsibility do not possess this level of 'contract' formalism.)
Criterion
Defined in Personnel Management:
A rule which defines the manner in which a particular Qualification (including a Credential) or collection of Qualifications
are associated with a given Position. An instance of a Criterion may be either a Time-based Criterion (e.g. <xxx> for at
least 3 years) or a Non-time-based Criterion (e.g. certified as either an <x> or a <y>).
(Return to glossary index)