This
page
is
part
of
the
FHIR
Specification
(v1.0.2:
DSTU
(v3.0.2:
STU
2).
3).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
R3
R2
A
structured
set
of
questions
intended
to
guide
the
collection
of
answers.
The
questions
are
ordered
answers
from
end-users.
Questionnaires
provide
detailed
control
over
order,
presentation,
phraseology
and
grouped
into
coherent
subsets,
corresponding
to
the
structure
of
the
grouping
of
the
underlying
questions.
to
allow
coherent,
consistent
data
collection.
4.26.1
2.38.1
Scope
and
Usage
A
Questionnaire
is
an
organized
collection
of
questions
intended
to
solicit
information
from
patients,
providers
or
other
individuals
involved
in
the
healthcare
domain.
They
may
be
simple
flat
lists
of
questions
or
can
be
hierarchically
organized
in
groups
and
sub-groups,
each
containing
questions.
The
Questionnaire
defines
the
questions
to
be
asked,
how
they
are
ordered
and
grouped
grouped,
any
intervening
instructional
text
and
what
the
constraints
are
on
the
allowed
answers.
The
results
of
a
Questionnaire
can
be
communicated
using
the
QuestionnaireResponse
resource.
Questionnaires
cover
the
need
to
communicate
data
originating
from
forms
used
in
medical
history
examinations,
research
questionnaires
and
sometimes
full
clinical
specialty
records.
In
many
systems
this
data
is
collected
using
user-defined
screens
and
forms.
Questionnaires
define
specifics
about
data
capture
-
exactly
what
questions
were
asked,
in
what
order,
what
choices
for
answers
were,
etc.
Each
of
these
questions
is
part
of
the
Questionnaire,
and
as
such
the
Questionnaire
is
a
separately
identifiable
Resource,
whereas
the
individual
questions
are
not.
(Questionnaire
questions
can
be
linked
to
shared
data
elements
using
the
Questionnaire.item.definition
element.)
Examples
of
Questionnaires
include:
Past
medical
history
(PMH)
Family
diseases
Social
history
Research
questionnaires/Clinical
research
forms
(CRFs)
Quality
and
evaluation
forms
Patient
intake
form
(e.g.
clipboard)
Insurance
claim
form
This
resource
is
limited
in
scope
to
support
the
characteristics
of
simple
questionnaires.
However,
common
extensions
have
been
defined
to
allow
more
sophisticated
behavior.
This
includes:
Questionnaire
core
extensions
which
defines
the
additional
descriptive
characteristics
for
questionnaires
and
their
groups
and
questions
Element
extensions
which
can
describe
additional
constraints
on
allowed
answers
for
questionnaires
such
as
string
length
and
date
and
numeric
ranges
Questionnaires
differ
from
Lists
because
Lists
group
existing
resources,
while
Questionnaires
group
arbitrary
questions.
In
theory,
a
Questionnaire
could
be
expressed
as
a
List
or
Composition
containing
DataElement
resources.
However,
the
former
would
disregard
the
"wholeness"
associated
with
a
questionnaire
where
questions
must
generally
be
maintained
as
a
single
structure.
The
latter
would
focus
on
rendering
of
the
data
elements
rather
than
organizing
the
capture
of
information.
Questionnaires
are
distinct
from
Observations
and
DiagnosticReports
in
that
both
of
these
resources
are
intended
to
capture
only
certain
types
of
information
(lab,
imaging,
vitals,
etc.)
and
should
not
be
used
to
capture
the
full
breadth
of
healthcare
information
(allergies,
medications,
care
plans,
etc.),
while
Questionnaires
are
able
to
capture
any
information
at
all.
More
importantly,
Observation
and
DiagnosticReport
focus
on
capturing
the
discrete
information
in
a
standardized
form
so
that
the
information
can
be
used
consistently
regardless
of
where
or
how
it
is
captured.
Questionnaire
focuses
on
information
capture.
The
same
information
can
be
captured
using
a
wide
variety
of
questionnaires
with
differently
phrased
questions
organized
in
different
manners.
As
such,
the
Questionnaire
resource
provides
a
means
to
standardize
the
information
gathering
process
(how
information
is
captured),
but
not
the
actual
information
collected.
Observation
and
DiagnosticReport
standardize
what
information
is
actually
captured,
but
not
how
the
information
is
gathered.
Questionnaires
are
similar
to
the
notion
of
"logical
models"
supported
by
the
StructureDefinition
resource.
Both
support
the
representation
of
a
collection
of
data
points
with
labels,
data
types
and
hierarchy.
It
will
be
common
to
find
the
two
of
them
mapped
together.
The
primary
difference
is
that
Questionnaire
is
focused
on
user-facing
data
collection.
It
describes
specific
questions
and
includes
information
such
as
what
number/label
should
be
displayed
beside
each
question,
conditions
in
which
questions
should
be
displayed
(or
not),
what
instructions
should
be
provided
to
the
user,
etc.
StructureDefinition,
on
the
other
hand,
merely
defines
a
data
structure
with
no
guidance
on
display
or
rules
around
capture
mechanism,
only
what
data
should
exist
in
the
end.
As
well,
logical
models
are
not
intended
to
capture
data
directly.
Rather,
they
provide
a
basis
for
mapping
between
data
capture
structures.
4.26.3
2.38.3
Background
and
Context
Groups
and
questions
that
make
up
a
Questionnaire
can
be
explicitly
coded
use
the
definition
element
to
refer
to
externally
defined
numbering
or
identification
data
elements
in
external
code
systems,
DataElements
and
StructureDefinitions
.
In
this
way,
it's
possible
to
leverage
standard
definitions
of
questions
and
sections
on
formally
defined
their
associated
data
types
and
answer
sets
across
questionnaires.
This
also
allows
extraction
of
the
data
on
from
a
form
and
questionnaire
response
into
other
data
structures
(e.g.
populating
a
ReferralRequest
or
CarePlan
from
information
in
a
completed
questionnaire
response.
It
can
also
support
other
sorts
of
post-processing
of
the
data
contained
in
a
Questionnaire.
Such
coding
questionnaire
response.
However,
use
of
the
definition
element
is
not
required
however
and
Questionnaires
may
be
quite
loosely
defined.
The
section
Questionnaire
versus
Resources
below
discusses
the
issues
of
collecting
data
in
such
loosely
defined
Questionnaires
versus
collecting
data
as
well-defined
separate
Resources.
Questions
and
sections
within
the
Questionnaire
Groups
may
either
contain
questions
or
+
Read-only
can't
be
specified
for
"display"
items
+
Default
values
can't
be
specified
for
groups
but
not
or
display
items
+
Required
and
repeat
aren't
permitted
for
display
items
+
Only
'choice'
items
can
have
options
+
A
question
cannot
have
both
option
and
options
+
Display
items
cannot
have
a
"code"
asserted
+
Maximum
length
can
only
be
declared
for
simple
question
types
+
Group
items
must
have
nested
items,
display
items
cannot
have
nested
items
Questions
and
sections
within
the
Questionnaire
Groups
may
either
contain
questions
or
+
Read-only
can't
be
specified
for
"display"
items
+
Default
values
can't
be
specified
for
groups
but
not
or
display
items
+
Required
and
repeat
aren't
permitted
for
display
items
+
Only
'choice'
items
can
have
options
+
A
question
cannot
have
both
option
and
options
+
Display
items
cannot
have
a
"code"
asserted
+
Maximum
length
can
only
be
declared
for
simple
question
types
+
Group
items
must
have
nested
items,
display
items
cannot
have
nested
items
que-1
:
On
Questionnaire.group:
Groups
may
either
contain
questions
or
groups
but
not
both
(xpath
Questionnaire.item:
Group
items
must
have
nested
items,
display
items
cannot
have
nested
items
(
expression
on
f:Questionnaire/f:group:
Questionnaire.item:
not(exists(f:group)
(type='group'
implies
item.empty().not())
and
exists(f:question))
(type.trace('type')='display'
implies
item.trace('item').empty())
)
que-10
:
On
Questionnaire.item:
Maximum
length
can
only
be
declared
for
simple
question
types
(
expression
on
Questionnaire.item:
(type
in
('boolean'
|
'decimal'
|
'integer'
|
'string'
|
'text'
|
'url'))
or
maxLength.empty()
)
que-2
:
The
link
ids
for
groups
and
questions
must
be
unique
within
the
questionnaire
(xpath:
(
expression
:
count(descendant::f:linkId/@value)=count(distinct-values(descendant::f:linkId/@value))
descendants().linkId.isDistinct()
)
que-3
:
If
root
group
must
be
"required"
(xpath:
On
Questionnaire.item:
Display
items
cannot
have
a
"code"
asserted
(
expression
on
Questionnaire.item:
f:group/f:required/@value=true()
type!='display'
or
code.empty()
)
que-4
:
On
Questionnaire.group.question:
Questionnaire.item:
A
question
cannot
have
both
option
and
options
(
expression
on
Questionnaire.item:
option.empty()
or
options.empty()
)
que-5
:
On
Questionnaire.item:
Only
'choice'
items
can
have
options
(
expression
on
Questionnaire.item:
(type
='choice'
or
type
=
'open-choice')
or
(options.empty()
and
option.empty())
)
que-6
:
On
Questionnaire.item:
Required
and
repeat
aren't
permitted
for
display
items
(
expression
on
Questionnaire.item:
type!='display'
or
(required.empty()
and
repeats.empty())
)
que-7
:
On
Questionnaire.item.enableWhen:
enableWhen
must
use
contain
either
option
a
'answer'
or
options,
not
both
(xpath
a
'hasAnswer'
element
(
expression
on
f:Questionnaire/f:group/f:question:
Questionnaire.item.enableWhen:
not(f:options
hasAnswer.exists()
xor
answer.exists()
)
que-8
:
On
Questionnaire.item:
Default
values
can't
be
specified
for
groups
or
display
items
(
expression
on
Questionnaire.item:
(type!='group'
and
f:option)
type!='display')
or
initial.empty()
)
que-9
:
On
Questionnaire.item:
Read-only
can't
be
specified
for
"display"
items
(
expression
on
Questionnaire.item:
type!='display'
or
readOnly.empty()
)
4.26.5
2.38.5
Notes:
Questionnaires
may
be
used
to
represent
predefined
forms
or
panels,
referenced
using
Questionnaire.group.concept.
items
of
type
"group"
A
Questionnaire's
contents
are
placed
inside
its
single
nested
Group,
which
may
contain
Questions
or
subgroups
with
Questions.
may
be
nested.
The
Questionnaire
resource
supports
nested
items
beneath
both
items
of
type
"group"
(which
doesn't
capture
an
answer
of
its
own)
as
well
as
beneath
questions
Groups
and
Questions
may
have
linkIds
allowing
groups
and
question
answers
captured
in
a
QuestionnaireResponse
to
be
associated
with
their
corresponding
group
or
question.
Questionnaire
allows
for
flexible
naming
and
structuring
of
its
contents
to
reflect
the
flexible
and
varying
nature
of
forms
and
questionnaires.
It
explicitly
does
not
try
to
standardize
or
streamline
exchange
of
its
contents
outside
its
context
of
use,
although
exchanging
partners
may
further
constrain
its
structure
and
flexibility
using
profiles
to
define
standardized,
reusable
forms.
Because
of
the
lack
of
explicit
support
for
Questionnaires
in
HL7
v3
,
CDA
Documents
frequently
used
named
sections
with
Observations
to
model
Questionnaires.
Such
use
cases
should
now
utilize
use
the
Questionnaire
Resource
instead.
The
order
of
questions
within
groups,
groups
within
groups
and
groups
within
questions
is
relevant
and
must
be
retained
for
display
and
capture.
Display
items
allow
the
inclusion
of
instructions,
background
information
and
similar
content
within
a
questionnaire.
4.26.5.1
2.38.5.1
Using
Questionnaires
versus
using
Resources
There
is
considerable
overlap
between
the
information
covered
by
Questionnaires
and
other
Resources
(especially
FamilyMemberHistory
,
MedicationStatement
,
Observation
,
Procedure
,
etc.):
etc.).
Questionnaire's
flexible
structure
can
easily
be
misused
to
capture
any
data,
even
data
that
should
be
captured
as
separate
Resources.
The
choice
between
using
Questionnaires
or
separate
Resources
may
be
dictated
by
the
procedure
of
collection
and
recording;
e.g.
if
the
data
is
captured
as
a
physician-agreed
(electronic)
form,
it
might
be
impossible
or
undesirable
to
distill
separate
resources
from
it
and
capturing
the
data
in
a
Questionnaire
would
be
most
appropriate.
However,
data
captured
only
in
Questionnaires
can
be
difficult
to
query
after-the-fact.
Queries
against
other
Resources
will
not
return
data
captured
only
in
Questionnaires
,
and
querying
against
Questionnaires
directly
may
not
find
all
desired
data,
depending
on
how
the
questions
may
have
been
phrased
or
encoded
over
time
or
by
different
clinicians.
Moreover,
interoperability
of
such
Questionnaires
is
limited
limited,
as
interpretation
of
its
contents
is
only
known
to
the
circle
of
parties
that
were
involved
in
its
definition:
encoding
data
from
such
Questionnaires
using
other,
more
specific,
Resources
specific
resources
increases
the
ability
and
consistency
with
which
it
can
be
understood
and
queried.
availability
of
the
information
they
contain.
It
is
entirely
possible
for
data
to
exist
in
both
QuestionnaireResponse
and
in
other
resources.
For
example,
data
may
be
captured
in
QuestionnaireResponse
as
part
of
an
intake
questionnaire.
That
data
may
then
be
propagated
into
the
Patient
resource
(demographics),
FamilyMemberHistory
,
AllergyIntolerance
,
MedicationStatement
and
Observation
resources
to
allow
the
data
to
be
queried
and
analyzed.
The
original
QuestionnaireResponse
instance
can
be
retained
for
traceability
purposes.
If
desired,
a
Provenance
resource
can
be
used
to
identify
the
Questionnaire
as
the
data
source
for
the
other
resources.
For
example,
if
a
questionnaire
question
asks
"what
is
your
weight",
that
can
then
result
in
the
creation
of
an
Observation
with
the
appropriate
Observation.code
and
the
specified
answer
as
the
Observation.valueQuantity
.
can
be
created.
4.26.5.2
2.38.5.2
Structure
of
the
Questionnaire
A
Questionnaire
is
built
out
of
three
components:
two
components,
Questionnaire
and
item:
The
main
component
is
Questionnaire,
which
holds
information
about
the
Questionnaire,
like
the
identifier,
publisher,
date
authored,
title,
etc.
The
Questionnaire
contains
one
"root"
Group,
zero
or
more
items
which
contains
all
define
the
content
of
the
questionnaire.
This
"root"
group
contains
elements
that
apply
to
the
entire
questionnaire
-
the
title
(zero
items
allows
for
the
questionnaire,
possibility
of
narrative-only
questionnaires,
though
these
provide
little
computable
information).
Items
have
one
of
three
sub-types,
distinguished
by
the
concept
type
that
represents
element:
display
items
convey
text
to
be
rendered
on
the
meaning
form
that
won't
capture
data
and
which
won't
contain
nested
items.
This
might
include
copyright
or
authorship
information,
instructions
or
other
background
information.
group
items
organize
content
of
the
overall
questionnaire
(e.g.
into
sections,
sub-sections,
etc.
Groups
don't
have
answers
associated
with
them
directly,
but
generally
contain
child
'question'
items
which
do.
question
items
ask
a
code
for
"family
history"),
the
specific
question
to
which
an
answer
may
be
given.
There
isn't
a
single
text
type
to
display
at
for
question
items.
Instead,
the
top
type
conveys
the
data
type
of
the
questionnaire,
etc.
(In
most
cases,
required
would
be
'true'
and
repeats
would
be
false
answer
for
the
root
group
This
Group
can
contain
either
nested
Groups
(to
represent
sections
and
subsections
on
question.
If
an
item
isn't
a
questionnaire
form)
or
Questions.
This
way,
any
form
containing
sections
'display'
or
subsections
can
be
represented,
down
a
'group',
then
it's
a
question
which
allows
a
particular
type
of
answer
to
the
actual
questions.
The
Questions
themselves
may
be
simple
questions
with
a
prompt
text
and
one
expected
answer,
but
they
gathered.
Questions
may
also
contain
nested
groups,
each
containing
sets
of
have
nested
content
-
groups
and/or
other
questions.
This
way,
one
can
model
"panels"
of
questions
which
would
only
be
relevant
(and
thus
would
only
be
displayed)
depending
on
the
answers
of
a
parent
question;
e.g.
a
question
"Did
the
patient
receive
treatment
in
the
past
six
months?"
would
contain
a
nested
group
of
questions
asking
for
further
details
about
the
treatment.
See
an
example
from
the
Australian
New
South
Wales
blue
book
Specific
controls
on
dynamic
display
of
groups,
questions,
etc.
based
on
the
answers
to
other
questions
is
outside
the
scope
of
the
base
resource
and
are
expected
to
be
introduced
as
handled
using
extensions.
4.26.5.3
2.38.5.3
Identifiers
within
Questionnaire
There
are
three
different
"identifying"
elements
within
Questionnaire:
identifier
,
id
and
linkId
.
Each
serves
very
distinct
purposes:
The
identifier
element
is
used
to
reference
the
overall
questionnaire
in
business
terms.
It
is
the
number
printed
across
the
top
of
the
form
or
listed
beside
the
form
when
making
a
choice
between
alternate
forms.
The
id
attribute
supported
on
each
element
is
used
for
references
within
a
resource,
for
example
linking
narrative
to
discrete
elements
elements.
Ids
are
not
generally
displayed
to
end
users
The
linkId
element
on
questions
and
groups
establishes
a
link
between
elements
in
a
QuestionnaireAnsers
QuestionnaireResponse
and
their
definition
inside
a
Questionnaire.
This
is
the
only
way
to
link
between
the
groups
and
questions
in
a
Questionnaire
and
QuestionnaireResponse
QuestionnaireResponse.
These
are
also
not
displayed
to
end
users
4.26.5.4
2.38.5.4
Question
Definitions
Questionnaires
can
be
crafted
using
any
questions
the
author
can
conceive
and
can
be
phrased
in
whatever
manner
is
appropriate
or
convenient.
However,
standardization
of
questions
and
the
constraints
enforced
on
the
accompanying
answers
increases
the
ability
to
compare
data
gathered
across
questionnaires.
There
are
two
mechanisms
defined
in
the
specification
for
linking
a
Question
(or
Group)
Items
can
be
directly
linked
to
an
ElementDefinition
using
Questionnaire.item.definition
which
provides
details
for
the
item.
If
a
standardized
definition
is
provided,
then
the
following
element
values
can
be
derived
from
the
definition:
The
concept
element
on
both
Group
and
Question
allows
(from
ElementDefinition.code)
type
(from
ElementDefinition.type)
required
(from
ElementDefinition.min)
repeats
(from
ElementDefinition.max)
maxLength
(from
ElementDefinition.maxLength)
options
(from
ElementDefinition.binding)
Any
information
provided
in
these
elements
overrides
the
information
from
the
definition.
The
url
refers
to
a
an
individual
question,
ElementDefinition
in
either
a
group
of
questions
StructureDefinition
or
even
the
questionnaire
as
a
whole
to
be
associated
DataElement
,
and
always
starts
with
the
canonical
URL
for
the
target
resource.
When
referring
to
a
pre-defined
terminology
of
questions
and
question
groups
such
as
LOINC
The
deReference
extension
allows
StructureDefinition,
a
question
or
group
fragment
identifier
is
used
to
be
associated
with
specify
the
DataElement
(DE)
resource
that
formally
defines
element
definition
by
its
id
(Element.id).
E.g.
http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x].
In
the
data
element.
Linking
to
formal
definitions
absence
of
a
question
allows
data
captured
by
distinct
questionnaires
to
be
compared.
If
systems
have
fragment
identifier,
the
necessary
mappings
to
first/root
element
definition
in
the
formal
definition,
linkages
to
formal
target
is
the
matching
element
definition.
Note
that
LOINC
codes
implicitly
define
DataElement
resources.
The
definitions
may
also
be
used
to
automatically
pre-populate
answers,
or
extract
data
from
a
corresponding
QuestionnaireResponse
resource.
NOTE:
Even
if
a
standard
question
definitions
are
referenced
using
concept
or
the
deReference
extension,
definition
is
provided
,
information
such
as
the
question
text,
data
type
and
value
set
SHOULD
still
be
declared
for
the
question.
Systems
processing
the
questionnaire
may
not
have
access
to
or
support
the
ability
to
look
up
the
question
definitions
from
external
sources.
If
the
information
is
not
included
in-line
within
the
questionnaire,
other
systems
may
not
be
able
to
to
render
or
use
the
Questionnaire.
If
an
external
reference
(
concept
or
deReference
extension)
definition
is
included
along
with
question
information
such
as
question
text,
data
type
or
value
set,
it
is
expected
that
the
content
for
the
question
and
the
referenced
definition
would
be
in
alignment.
However,
FHIR
does
not
dictate
what
degree
of
alignment
is
required;
e.g.
Does
the
question
text
need
to
match
exactly?
Is
it
legitimate
for
a
question
to
constrain
the
allowed
value
set
of
possible
answers?
These
rules
will
need
to
be
established
within
implementation
environments.
4.26.5.5
2.38.5.5
Question
types
The
codes
for
the
data
type
for
each
question
are
slightly
different
than
the
data
types
allowed
in
the
QuestionnaireResponse
resource.
Where
the
names
are
the
same
(ignoring
case),
the
"answer"
must
use
the
specified
type.
Where
the
names
are
different,
the
mappings
are
as
follows:
Coding
(if
choosing
from
one
of
the
listed
choices)
or
string
(if
a
different
value
is
provided)
4.26.5.6
2.38.5.6
Permitted
values
for
questions
Many
questionnaires
place
constraints
on
the
allowed
list
of
values
for
a
given
question.
FHIR
supports
this
notion
through
the
...question.choices
item.options
or
the
item.option
element.
However,
rather
The
"option"
mechanism
is
simplest
-
all
options
are
listed
in-line
with
the
question
using
the
item.option
element.
Maintenance
of
the
set
of
permitted
question
answers
involves
maintenance
of
the
questionnaire
itself.
The
"options"
mechanism
is
more
sophisticated.
Rather
than
listing
the
choices
options
directly,
the
choices
item.options
element
points
to
a
ValueSet
resource.
This
approach
adds
complexity
for
questionnaires
having
a
simple
list
of
strings
as
choices
for
a
question,
but
provides
several
benefits:
benefits,
including:
Questionnaires
that
reference
codes
from
externally
defined
code
systems
have
a
means
of
doing
so
Answer
sets
can
be
shared
across
questions
(and
there
are
many
questionnaires
where
this
capability
is
useful)
The
full
capability
of
value
sets
can
be
brought
into
play,
including
the
ability
to
use
ConceptMap
to
link
and
translate
from
questionnaire-specific
codes
to
other
codes,
the
use
of
multiple
display
names
(e.g.
different
languages),
the
ability
to
use
coded
ordinals,
and
the
ability
to
allow
choices
from
larger
value
sets
(e.g.
"all
SNOMED
CT
procedure
codes")
etc.
In
many
cases,
the
set
of
code
choices
will
be
specific
to
a
given
questionnaire
and
should
be
maintained
as
part
of
the
questionnaire.
In
this
case,
the
referenced
ValueSet
can
be
included
as
a
contained
resource.
All
contained
ValueSets
are
listed
together
and
then
are
referenced
by
the
individual
questions
as
necessary.
Alternatively,
the
item.options
element
can
reference
the
value
set
in
a
version-specific
manner.
This
ensures
that
the
Questionnaire
will
not
adopt
a
new
version
of
the
referenced
value
set
without
revising
the
Questionnaire
to
point
to
that
new
version
-
putting
the
author
of
the
Questionnaire
in
control
of
any
changes.
4.26.5.7
2.38.5.7
Useful
Value
Sets
Many
questions
have
a
common
set
of
possible
codes
for
their
answer.
These
value
sets
may
be
useful
to
help,
and
when
referenced
by
full
URL,
do
not
need
to
be
provided
as
part
of
the
questionnaire:
4.26.5.8
2.38.5.8
Questions
with
multiple
answer
types
In
some
questionnaires,
it
may
be
possible
to
respond
to
a
question
with
multiple
types
of
answers.
For
example,
capturing
a
coded
answer
plus
free
text,
capturing
a
coded
value
plus
a
numeric
priority,
etc.
In
FHIR,
this
is
handled
through
nested
questions.
Each
question
has
a
single
data
type.
However,
each
question
can
have
nested
child
questions.
These
nested
child
questions
can
have
text
(e.g.
"Please
specify")
or
can
have
no
text
at
all
if
the
appropriate
guidance
is
provided
by
the
parent
question
or
group.
4.26.5.9
2.38.5.9
Questionnaires
with
Math
While
not
defined
(yet)
at
the
international
level,
extensions
may
be
defined
to
perform
mathematical
functions
Many
questionnaires
involve
computations
on
questionnaire
responses.
For
example,
answers,
e.g.
tabulating
scores.
One
extension
that
is
defined
that
may
be
useful
in
this
process
is
the
Ordinal
extension.
This
allows
a
To
help
with
associating
numeric
value
values
to
be
associated
with
a
coded
data
element.
There
answers,
there
are
two
extensions
defined
-
one
for
defining
the
numeric
weighting
of
a
code
defined
in
a
value
set
-
valueset-ordinalValue
and
the
other
is
for
defining
a
code
that
can
appear
within
a
Coding
itself
-
iso21090-CO-value
.
4.26.5.10
Extensions
for
Additional
capabilities
The
core
elements
defined
in
the
questionnaire
resource
In
addition,
there
are
sufficient
extensions
for
simple
questionnaires.
defining
the
dynamic
value
of
an
element
usings
expressions.
For
more
sophisticated
capabilities,
a
number
of
"common"
extensions
are
defined
in
information,
see
the
Questionnaire
Core
extensions
Using
Expressions
and
the
Element
extensions
Documentation
Template
profiles.
For
example,
strict
control
over
allowed
number
of
conditions,
conditional
display
of
questionnaire
content,
etc.
The
conditional
display
extension
[enable-when]
can
be
used
to
enable
groups
nested
beneath
a
question
based
on
the
selection
of
a
specific
answer,
giving
topics
in
the
behavior
of
"questions
under
answers"
where
this
sort
of
more
sophisticated
behavior
is
needed.
Clinical
Reasoning
module.
4.26.6
2.38.6
Search
Parameters
Search
parameters
for
this
resource.
The
common
parameters
also
apply.
See
Searching
for
more
information
about
searching
in
REST,
messaging,
and
services.
Foundation
.
Page
versions:
R5
R4B
R4
Questionnaire
url
identifier
item
answer[x]
answerReference
item
<!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension -->
0..* Questions and sections within the Questionnaire --> <linkId value="[string]"/><!-- 1..1 Unique id for item in questionnaire --> <definition value="[uri]"/><!-- 0..1 ElementDefinition - details for the item --> <code><!--
|
Propose
a
change