This
page
is
part
of
the
Continuous
Integration
Build
of
FHIR
Specification
(v4.0.1:
R4
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
(will
be
available
incorrect/inconsistent
at
this
URL).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
Content
Examples
Detailed
Descriptions
Mappings
Profiles
&
Extensions
R3
Conversions
13.7.8
Resource
ClaimResponse
-
Extensions
&
Profiles
Example
ValueSet/yesnodontknow
(XML)
Financial
Management
Responsible
Owner:
Terminology
Infrastructure
Work
Group
|
Maturity
Level
:
N/A
Standards
Status
:
Informative
|
Security
Category
:
Patient
Compartments
:
Patient
,
Practitioner
This
table
lists
profiles
and
extensions
for
the
ClaimResponse
resource.
For
background
information,
see
Profiling
Resources
and
Extensibility
.
Additional
profiles
and
extensions
may
be
found
in
published
Implementation
Guides
,
or
in
the
Conformance
resource
registry
.
13.7.8.1
Profiles
No
Profiles
defined
for
this
resource
13.7.8.2
Extensions
No
Extensions
defined
for
this
resource
Extensions
for
all
resources
or
elements
compartments
|
resource-pertainsToGoal
pertainsToGoal
for
Resource
HL7
Extensions
Extensions
that
reference
this
resource:
request-insurance
insurance
for
Request
Pattern
HL7
Extensions
Extensions
that
refer
to
Any
resource
cqf-relativeDateTime
relativeDateTime
for
Clinical
Reasoning
Extensions
event-basedOn
-
basedOn
for
Event
Pattern
HL7
Extensions
Narrative
event-partOf
-
partOf
for
Event
Pattern
HL7
Extensions
XML
flag-detail
-
detail
for
Flag
HL7
Extensions
JSON
relative-date
-
Relative
Date
Criteria
for
General
Extensions
for
use
by
FHIR
Implementers
TTL
replaces
replaces
for
General
Extensions
for
use
by
FHIR
Implementers
Raw
XML
request-replaces
(
canonical
form
replaces
for
Request
Pattern
HL7
Extensions
+
also
see
XML
Format
Specification
)
workflow-supportingInfo
Jump
past
Narrative
supportingInfo
Yes/No/Don't
know,
for
Workflow
Pattern
HL7
Extensions
capturing
a
common
answer
set
in
questionnaires
(id
=
"yesnodontknow")
<?xml version="1.0" encoding="UTF-8"?>
<ValueSet xmlns="http://hl7.org/fhir"> <id value="yesnodontknow"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p class="res-header-id"> <b> Generated Narrative: ValueSet yesnodontknow</b> </p> <a name="yesnodontknow"> </a> <a name="hcyesnodontknow"> </a> <p> This value set expansion contains 3 concepts.</p> <table class="codes"> <tr> <td> <b> System</b> </td> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> <a name="yesnodontknow-http://terminology.hl7.org/CodeSystem/v2-0532-Y"> </a> <code> http://terminology.hl7.org/CodeSystem/v2-0532</code> </td> <td style="white-space:nowrap"> <a href="http://terminology.hl7.org/7.0.1/CodeSystem-v2-0532.html#v2-0532-Y">Y</a> </td> <td> Yes</td> <td> Yes</td> </tr> <tr> <td> <a name="yesnodontknow-http://terminology.hl7.org/CodeSystem/v2-0532-N"> </a> <code> http://terminology.hl7.org/CodeSystem/v2-0532</code> </td> <td style="white-space:nowrap"> <a href="http://terminology.hl7.org/7.0.1/CodeSystem-v2-0532.html#v2-0532-N">N</a> </td> <td> No</td> <td> No</td> </tr> <tr> <td> <a name="yesnodontknow-http://terminology.hl7.org/CodeSystem/data-absent-reason-asked-unknown"> </a> <code> http://terminology.hl7.org/CodeSystem/data-absent-reason</code> </td> <td style="white-space:nowrap"> <a href="http://terminology.hl7.org/7.0.1/CodeSystem-data-absent-reason.html#data-absent-reason-asked-
unknown">asked-unknown</a>
</td> <td> Don't know</td> <td> The source was asked but does not know the value.</td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="vocab"/> </extension> <url value="http://hl7.org/fhir/ValueSet/yesnodontknow"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.3.3149"/> </identifier> <version value="6.0.0-ballot3"/> <name value="YesNoDontKnow"/> <title value="Yes/No/Don't Know"/> <status value="draft"/> <experimental value="true"/> <publisher value="HL7 International / Terminology Infrastructure"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/Vocab"/> </telecom> </contact> <description value="For Capturing simple yes-no-don't know answers"/> <compose> <include> <valueSet value="http://terminology.hl7.org/ValueSet/v2-0136"/> </include> <include> <system value="http://terminology.hl7.org/CodeSystem/data-absent-reason"/> <concept> <code value="asked-unknown"/> <display value="Don't know"/> </concept> </include> </compose> <expansion> <identifier value="urn:uuid:bf99fe50-2c2b-41ad-bd63-bee6919810b4"/> <timestamp value="2015-07-14T10:00:00Z"/> <contains> <system value="http://terminology.hl7.org/CodeSystem/v2-0532"/> <code value="Y"/> <display value="Yes"/> </contains> <contains> <system value="http://terminology.hl7.org/CodeSystem/v2-0532"/> <code value="N"/> <display value="No"/> </contains> <contains> <system value="http://terminology.hl7.org/CodeSystem/data-absent-reason"/> <code value="asked-unknown"/> <display value="Don't know"/> </contains> </expansion>
</
ValueSet
13.7.8.3
>
Search
Extensions
No
Search
Extensions
defined
for
this
resource
Usage
note:
every
effort
has
been
made
to
ensure
that
the
examples
are
correct
and
useful,
but
they
are
not
a
normative
part
of
the
specification.