This
page
is
part
of
the
FHIR
Specification
(v1.0.2:
DSTU
2).
The
current
version
which
supercedes
this
version
is
This page is part of the FHIR Specification (v1.6.0:
STU
3 Ballot 4). The current version which supercedes this version is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
. For a full list of available versions, see the
Directory of published versions 
.
Page
versions:
. Page versions:
R4B
R4
R3
R2
1.25.2.1.9
4.3.1.concept-map-equivalence
Value
Set
http://hl7.org/fhir/ValueSet/concept-map-equivalence
Value Set http://hl7.org/fhir/ValueSet/concept-map-equivalence
This
is
a
value
set
defined
by
the
FHIR
project.
This is a value set defined by the FHIR project.
Summary
Defining
URL:
Defining URL:
|
http://hl7.org/fhir/ValueSet/concept-map-equivalence
|
|
Name:
|
ConceptMapEquivalence
|
|
Definition:
|
The
degree
of
equivalence
between
concepts.
The degree of equivalence between concepts.
|
OID:
Committee:
|
2.16.840.1.113883.4.642.2.9
(for
OID
based
terminology
systems)
System
URL:
FHIR Infrastructure
http://hl7.org/fhir/concept-map-equivalence
Work Group
|
System
OID:
|
2.16.840.1.113883.4.642.1.9
2.16.840.1.113883.4.642.2.concept-map-equivalence (for OID based terminology systems)
|
Source
Resource
Source Resource
|
XML
/
/
JSON
|
This
value
set
is
used
in
the
following
places:
This value set is used in the following places:
4.3.1.concept-map-equivalence.1
Content Logical Definition
This value set includes codes from the following code systems:
1.25.2.1.9.1
Content
Logical
Definition
4.3.1.concept-map-equivalence.2
Expansion
This expansion generated 11 Aug 2016
This
value
set
has
an
inline
code
system
http://hl7.org/fhir/concept-map-equivalence,
which
defines
the
following
codes:
This value set contains 9 concepts
All codes from system
http://hl7.org/fhir/concept-map-equivalence
Lvl
|
Code
|
Display
|
Definition
|
1
equivalent
|
Equivalent
|
The
definitions
of
the
concepts
mean
the
same
thing
(including
when
structural
implications
of
meaning
are
considered)
(i.e.
extensionally
identical).
The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical).
|
2
equal
equal
|
Equal
|
The
definitions
of
the
concepts
are
exactly
the
same
(i.e.
only
grammatical
differences)
and
structural
implications
of
meaning
are
identical
or
irrelevant
(i.e.
intentionally
identical).
The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical).
|
1
wider
|
Wider
|
The
target
mapping
is
wider
in
meaning
than
the
source
concept.
The target mapping is wider in meaning than the source concept.
|
1
subsumes
|
Subsumes
|
The
target
mapping
subsumes
the
meaning
of
the
source
concept
(e.g.
the
source
is-a
target).
The target mapping subsumes the meaning of the source concept (e.g. the source is-a target).
|
1
narrower
|
Narrower
|
The
target
mapping
is
narrower
in
meaning
that
the
source
concept.
The
sense
in
which
the
mapping
is
narrower
SHALL
be
described
in
the
comments
in
this
case,
and
applications
should
be
careful
when
attempting
to
use
these
mappings
operationally.
The target mapping is narrower in meaning than the source concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally.
|
1
specializes
|
Specializes
|
The
target
mapping
specializes
the
meaning
of
the
source
concept
(e.g.
the
target
is-a
source).
The target mapping specializes the meaning of the source concept (e.g. the target is-a source).
|
1
inexact
|
Inexact
|
The
target
mapping
overlaps
with
the
source
concept,
but
both
source
and
target
cover
additional
meaning,
or
the
definitions
are
imprecise
and
it
is
uncertain
whether
they
have
the
same
boundaries
to
their
meaning.
The
sense
in
which
the
mapping
is
narrower
SHALL
be
described
in
the
comments
in
this
case,
and
applications
should
be
careful
when
attempting
to
use
these
mappings
operationally.
The target mapping overlaps with the source concept, but both source and target cover additional meaning, or the definitions are imprecise and it is uncertain whether they have the same boundaries to their meaning. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally.
|
1
unmatched
|
Unmatched
|
There
is
no
match
for
this
concept
in
the
destination
concept
system.
There is no match for this concept in the destination concept system.
|
2
disjoint
disjoint
|
Disjoint
|
This
is
an
explicit
assertion
that
there
is
no
mapping
between
the
source
and
target
concept.
This is an explicit assertion that there is no mapping between the source and target concept.
|
See
the
full
registry
of
value
sets
defined
as
part
of
FHIR.
Explanation
of
the
columns
that
may
appear
on
this
page:
See
the full registry of value sets
defined as part of FHIR.
Explanation of the columns that may appear on this page:
|
Level
|
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
In
this
scheme,
some
codes
are
under
other
codes,
and
imply
that
the
code
they
are
under
also
applies
A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
|
|
Source
|
The
source
of
the
definition
of
the
code
(when
the
value
set
draws
in
codes
defined
elsewhere)
The source of the definition of the code (when the value set draws in codes defined elsewhere)
|
|
Code
|
The
code
(used
as
the
code
in
the
resource
instance)
The code (used as the code in the resource instance)
|
|
Display
|
The
display
(used
in
the
The display (used in the
display
element
of
a
element of a
Coding
).
If
there
is
no
display,
implementers
should
not
simply
display
the
code,
but
map
the
concept
into
their
application
). If there is no display, implementers should not simply display the code, but map the concept into their application
|
|
Definition
|
An
explanation
of
the
meaning
of
the
concept
An explanation of the meaning of the concept
|
|
Comments
|
Additional
notes
about
how
to
use
the
code
Additional notes about how to use the code
|
©
HL7.org
2011+.
FHIR
DSTU2
(v1.0.2-7202)
generated
on
Sat,
Oct
24,
2015
07:42+1100.
Links:
Search
|
Version
History
|
Table
of
Contents
|
Compare
to
DSTU1
Terminology
|
Propose a change