Example
ValueSet/gender-identity
(XML)
FHIR
Infrastructure
Vocabulary
Work
Group
|
Maturity
Level
:
N
N/A
|
Normative
(from
v4.0.0)
Use
Context
Standards
Status
:
Any
This
page
has
been
approved
as
part
of
an
ANSI
standard.
See
the
Conformance
Package
for
further
details.
This
is
a
value
set
defined
by
the
FHIR
project.
Summary
Defining
URL:
http://hl7.org/fhir/ValueSet/reference-handling-policy
Version:
4.0.1
Name:
ReferenceHandlingPolicy
Informative
|
Title:
ReferenceHandlingPolicy
|
Definition:
A
set
of
flags
that
defines
how
references
are
supported.
Committee:
FHIR
Infrastructure
-
Narrative
Work
Group
OID:
2.16.840.1.113883.4.642.3.202
(for
OID
based
terminology
systems)
Source
Resource
-
XML
/
JSON
This
value
set
is
used
in
the
following
places:
CodeSystem:
This
value
set
is
the
designated
'entire
code
system'
value
set
for
ReferenceHandlingPolicy
Resource:
CapabilityStatement.rest.resource.referencePolicy
(code
/
Required
)
4.4.1.500.1
Content
Logical
Definition
-
JSON
This
value
set
includes
codes
from
the
following
code
systems:
-
Include
all
codes
defined
in
http://hl7.org/fhir/reference-handling-policy
TTL
Raw
XML
4.4.1.500.2
Expansion
(
canonical
form
This
expansion
generated
01
Nov
2019
This
value
set
contains
5
concepts
Expansion
based
on
http://hl7.org/fhir/reference-handling-policy
version
4.0.1
All
codes
from
system
http://hl7.org/fhir/reference-handling-policy
+
also
see
XML
Format
Specification
)
Code
Display
Definition
literal
Literal
References
The
server
supports
and
populates
Literal
references
(i.e.
using
Reference.reference)
where
they
are
known
(this
code
does
not
guarantee
that
all
references
are
literal;
see
'enforced').
logical
Logical
References
The
server
allows
logical
references
(i.e.
using
Reference.identifier).
resolves
Resolves
References
The
server
will
attempt
to
resolve
logical
references
to
literal
references
-
i.e.
converting
Reference.identifier
to
Reference.reference
(if
resolution
fails,
the
server
may
still
accept
resources;
see
logical).
enforced
Reference
Integrity
Enforced
The
server
enforces
that
references
have
integrity
-
e.g.
it
ensures
that
references
can
always
be
resolved.
This
is
typically
the
case
for
clinical
record
systems,
but
often
not
the
case
for
middleware/proxy
systems.
Value
SetGender
Identity
<?xml version="1.0" encoding="UTF-8"?>
<ValueSet xmlns="http://hl7.org/fhir">
<id value="gender-identity"/>
<meta>
<lastUpdated value="2022-09-10T04:52:37.223+10:00"/>
<profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<p> This value set includes codes based on the following rules:</p>
<ul>
<li> Import all the codes that are contained in http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.11
3762.1.4.1021.106</li>
<li> Include these codes as defined in
<a href="http://terminology.hl7.org/3.1.0/CodeSystem-v3-NullFlavor.html">
<code> http://terminology.hl7.org/CodeSystem/v3-NullFlavor</code>
</a>
<table class="none">
<tr>
<td style="white-space:nowrap">
<b> Code</b>
</td>
<td>
<b> Display</b>
</td>
<td>
<b> Definition</b>
</td>
</tr>
<tr>
<td>
<a href="http://terminology.hl7.org/3.1.0/CodeSystem-v3-NullFlavor.html#v3-NullFlavor-UNK">UNK</a>
</td>
<td> Unknown</td>
<td> **Description:**A proper value is applicable, but not known.
<br/>
<br/> **Usage Notes**: This means the actual value is not known. If the only thing that
is unknown is how to properly express the value in the necessary constraints (value
set, datatype, etc.), then the OTH or UNC flavor should be used. No properties
should be included for a datatype with this property unless:
<br/>
<br/> 1. Those properties themselves directly translate to a semantic of "unknown".
(E.g. a local code sent as a translation that conveys 'unknown')
<br/> 2. Those properties further qualify the nature of what is unknown. (E.g. specifying
a use code of "H" and a URL prefix of "tel:" to convey that
it is the home phone number that is unknown.)
</td>
</tr>
</table>
</li>
</ul>
</div>
</text>
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="pa"/>
</extension>
<url value="http://terminology.hl7.org/ValueSet/gender-identity"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.3.3291"/>
</identifier>
<version value="5.0.0-ballot"/>
<name value="genderIdentity"/>
<title value="Gender Identity"/>
<status value="draft"/>
<experimental value="false"/>
<publisher value="FHIR Project team"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org/fhir"/>
</telecom>
</contact>
<description value="Codes that indicate a individual's gender identity."/>
<copyright value="This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is
copyright of the International Health Terminology Standards Development Organisation
(IHTSDO). Implementers of these specifications must have the appropriate SNOMED
CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snome
d-ct or info@snomed.org"/>
<compose>
<include>
<valueSet value="http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1021.106"/>
</include>
<include>
<system value="http://terminology.hl7.org/CodeSystem/v3-NullFlavor"/>
<concept>
<code value="UNK"/>
<display value="Unknown"/>
</concept>
</include>
</compose>
</
ValueSet
>
local
Local
References
Only
The
server
does
not
support
references
that
point
to
other
servers.
See
the
full
registry
of
value
sets
defined
as
part
of
FHIR.
Explanation
of
the
columns
that
may
appear
on
this
page:
Lvl
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
For
value
sets,
levels
are
mostly
used
Usage
note:
every
effort
has
been
made
to
organize
codes
for
user
convenience,
but
may
follow
code
system
hierarchy
-
see
Code
System
for
further
information
Source
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).
If
the
code
is
in
italics,
this
indicates
ensure
that
the
code
is
examples
are
correct
and
useful,
but
they
are
not
selectable
('Abstract')
Display
The
display
(used
in
the
display
element
of
a
Coding
).
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
normative
part
of
the
concept
Comments
Additional
notes
about
how
to
use
the
code
specification.