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
Work
Group
|
|
Use
Context
:
|
Official
URL
:
http://hl7.org/fhir/ValueSet/participation-role-type
|
|
|||
| active as of 2021-12-06 |
|
|||
|
|
|
|||
This value set is used in the following places:
This
FHIR
value
set
includes
codes
from
the
following
code
systems:
Include
these
codes
as
defined
in
http://terminology.hl7.org/CodeSystem/contractsignertypecodes
Code
Display
AMENDER
Amender
A
person
who
has
corrected,
edited,
or
amended
pre-existing
information.
COAUTH
Co-Author
The
entity
that
co-authored
content.
There
can
be
multiple
co-authors
of
content,
which
may
take
such
forms
as
a
contract,
a
healthcare
record
entry
or
document,
a
policy,
or
a
consent
directive.
CONT
Contact
A
person
or
an
organization
that
provides
or
receives
information
regarding
another
entity.
Examples;
patient
NOK
and
emergency
contacts;
guarantor
contact;
employer
contact.
EVTWIT
Event
Witness
A
person
who
attests
to
observing
an
occurrence.
For
example,
the
witness
has
observed
a
procedure
and
is
attesting
to
this
fact.
PRIMAUTH
Primary
Author
An
entity
that
is
the
primary
or
sole
author
comprised
of
information
content.
In
the
healthcare
context,
there
Actor
participation
Type
codes,
which
can
be
only
one
primary
author
of
health
information
content
in
a
record
entry
or
document.
REVIEWER
Reviewer
A
person,
device,
or
algorithm
that
has
used
approved
criteria
for
filtered
data
for
inclusion
into
the
patient
record.
Examples:
(1)
a
medical
records
clerk
who
scans
a
document
for
inclusion
in
the
medical
record,
enters
header
information,
or
catalogues
and
classifies
the
data,
or
a
combination
thereof;
(2)
a
gateway
that
receives
data
from
another
computer
system
and
interprets
that
data
or
changes
its
format,
or
both,
before
entering
it
into
the
patient
record.
SOURCE
Source
An
automated
data
source
that
generates
a
signature
along
with
content.
Examples:
(1)
the
signature
for
an
image
that
is
generated
by
a
device
for
inclusion
in
the
patient
record;
(2)
the
signature
for
an
ECG
derived
by
an
ECG
system
for
inclusion
in
the
patient
record;
(3)
the
data
from
a
biomedical
monitoring
device
or
system
that
is
for
inclusion
in
the
patient
record.
TRANS
Transcriber
An
entity
entering
the
data
into
the
originating
system.
This
includes
the
transcriptionist
for
dictated
text
transcribed
into
electronic
form.
VALID
Validator
A
person
who
validates
a
health
information
document
for
inclusion
in
the
patient
record.
For
example,
a
medical
student
or
resident
is
credentialed
to
perform
history
or
physical
examinations
and
to
write
progress
notes.
The
attending
physician
signs
the
history
and
physical
examination
to
validate
the
entry
for
inclusion
in
the
patient's
medical
record.
VERF
Verifier
A
person
who
asserts
the
correctness
and
appropriateness
of
an
act
or
the
recording
of
the
act,
and
is
accountable
for
the
assertion
that
the
act
or
the
recording
of
the
act
complies
with
jurisdictional
or
organizational
policy.
For
example,
a
physician
is
required
to
countersign
a
verbal
order
that
has
previously
been
recorded
in
the
medical
record
by
a
registered
nurse
who
has
carried
out
the
verbal
order.
Include
these
codes
as
defined
in
http://terminology.hl7.org/CodeSystem/v3-RoleClass
Code
Display
AFFL
affiliate
Player
of
the
Affiliate
role
has
a
business/professional
relationship
with
scoper.
Player
and
scoper
may
be
persons
or
organization.
The
Affiliate
relationship
does
not
imply
membership
in
a
group,
nor
does
it
exist
for
resource
scheduling
purposes.
Example:
A
healthcare
provider
is
affiliated
with
another
provider
as
a
business
associate.
AGNT
agent
An
entity
(player)
that
acts
or
is
authorized
to
act
on
behalf
of
another
entity
(scoper).
ASSIGNED
assigned
entity
An
agent
role
in
which
the
agent
is
an
Entity
acting
in
the
employ
of
an
organization.
The
focus
is
on
functional
role
on
behalf
of
the
organization,
unlike
the
Employee
role
where
the
focus
is
on
the
'Human
Resources'
relationship
between
the
employee
value
FHIR
agents,
actors,
and
the
organization.
CLAIM
claimant
Description:
A
other
role
played
by
a
party
making
a
claim
for
coverage
under
a
policy
or
program.
A
claimant
must
be
either
a
person
or
organization,
or
a
group
of
persons
or
organizations.
A
claimant
is
not
a
named
insured
or
a
program
eligible.
Discussion:
With
respect
to
liability
insurance
such
as
property
and
casualty
insurance,
a
claimant
must
file
a
claim
requesting
indemnification
for
a
loss
that
the
claimant
considers
covered
under
the
policy
of
a
named
insured.
elements.
The
claims
adjuster
for
the
policy
underwriter
will
review
the
claim
to
determine
whether
the
loss
meets
the
benefit
coverage
criteria
under
a
policy,
and
base
any
indemnification
or
coverage
payment
on
that
review.
If
a
third
party
is
liable
in
whole
or
part
for
the
loss,
the
underwriter
may
pursue
third
party
liability
recovery.
A
claimant
may
be
involved
in
civil
or
criminal
legal
proceedings
involving
claims
against
a
defendant
party
that
is
indemnified
by
an
insurance
policy
or
to
protest
the
finding
of
a
claims
adjustor.
With
respect
to
life
insurance,
a
beneficiary
designated
by
a
named
insured
becomes
a
claimant
of
the
proceeds
of
coverage,
as
in
the
case
of
a
life
insurance
policy.
However,
a
claimant
for
coverage
under
life
insurance
is
not
necessarily
a
designated
beneficiary.
Note:
A
claimant
is
not
a
named
insured.
However,
a
named
insured
may
make
a
claim
under
a
policy,
e.g.,
an
insured
driver
may
make
a
claim
for
an
injury
under
his
or
her
comprehensive
automobile
insurance
policy.
Similarly,
a
program
eligible
may
make
a
claim
under
program,
e.g.,
an
unemployed
worker
may
claim
benefits
under
an
unemployment
insurance
program,
but
parties
playing
these
covered
party
role
classes
codes
are
not,
for
purposes
of
this
vocabulary
and
in
an
effort
to
clearly
distinguish
role
classes,
considered
claimants.
In
the
case
of
a
named
insured
making
a
claim,
a
role
type
code
INSCLM
(insured
claimant)
subtypes
the
class
to
indicate
that
either
a
named
insured
or
an
individual
insured
has
filed
a
claim
for
a
loss.
In
the
case
of
a
program
eligible,
a
role
type
code
INJWKR
(injured
worker)
subtypes
the
class
to
indicate
that
the
covered
party
in
a
workers
compensation
program
is
an
injured
worker,
and
as
such,
has
filed
a
"claim"
under
the
program
for
benefits.
Likewise,
a
covered
role
type
code
UNEMP
(unemployed
worker)
subtypes
the
program
eligible
class
intended
to
indicate
that
express
how
the
covered
party
agent
participated
in
an
unemployment
insurance
program
has
filed
a
claim
for
unemployment
benefits.
Example:
A
claimant
under
automobile
policy
that
is
not
the
named
insured.
COVPTY
covered
party
A
role
class
played
by
a
person
who
receives
benefit
coverage
under
the
terms
of
a
particular
insurance
policy.
The
underwriter
of
that
policy
is
the
scoping
entity.
The
covered
party
receives
coverage
because
of
some
contractual
or
other
relationship
with
the
holder
of
that
policy.
Discussion:This
reason
for
coverage
is
captured
in
'Role.code'
and
a
relationship
link
with
type
code
of
indirect
authority
should
be
included
using
the
policy
holder
role
as
the
source,
and
the
covered
party
role
as
the
target.
Note
that
a
particular
policy
may
cover
several
individuals
one
of
whom
may
be,
but
need
not
be,
the
policy
holder.
Thus
the
notion
of
covered
party
is
a
role
that
is
distinct
from
that
of
the
policy
holder.
DEPEN
dependent
Description:
A
role
played
by
a
person
covered
under
a
policy
or
program
based
on
an
association
with
a
subscriber,
which
is
recognized
by
the
policy
holder.
Note:
The
party
playing
the
role
of
a
dependent
is
not
a
claimant
in
the
sense
conveyed
by
the
RoleClassCoveredParty
CLAIM
(claimant).
However,
a
dependent
may
make
a
claim
under
a
policy,
e.g.,
a
dependent
under
a
health
insurance
policy
may
become
the
claimant
for
coverage
under
that
policy
for
wellness
examines
or
if
injured
and
there
is
no
liable
third
party.
In
the
case
of
a
dependent
making
a
claim,
a
role
type
code
INSCLM
(insured
claimant)
subtypes
the
class
to
indicate
that
the
dependent
has
filed
a
claim
for
services
covered
under
the
health
insurance
policy.
Example:
The
dependent
has
an
association
with
the
subscriber
such
as
a
financial
dependency
or
personal
relationship
such
as
that
of
a
spouse,
or
a
natural
or
adopted
child.
The
policy
holder
may
be
required
by
law
activity.
Sometimes
refered
to
recognize
certain
associations
or
may
have
discretion
about
the
associations.
For
example,
a
policy
holder
may
dictate
the
criteria
for
the
dependent
status
of
adult
children
who
are
students,
such
as
requiring
full
time
enrollment,
or
may
recognize
domestic
partners
as
dependents.
Under
certain
circumstances,
the
dependent
may
be
under
the
indirect
authority
of
a
responsible
party
acting
as
a
surrogate
for
the
subscriber,
for
example,
if
the
subscriber
is
differently
abled
or
deceased,
a
guardian
ad
Lidem
or
estate
executor
may
be
appointed
agent
functional-role
relative
to
assume
the
subscriberaTMs
legal
standing
in
the
relationship
with
the
dependent.
activity.
Generated Narrative: ValueSet participation-role-type
Last updated: 2025-12-17T09:50:17.012Z
This
role
is
scoped
by
the
party
responsible
for
the
investigation.
NAMED
named
insured
Description:
A
role
played
by
a
party
to
an
insurance
policy
to
which
the
insurer
agrees
to
indemnify
for
losses,
provides
benefits
for,
or
renders
services.
A
named
insured
may
be
either
a
person,
non-person
living
subject,
or
an
organization,
or
a
group
of
persons,
non-person
living
subjects,
or
organizations.
Discussion:
The
coded
concept
NAMED
should
not
be
used
where
a
more
specific
child
concept
in
this
Specializable
value
set
applies.
In
some
cases,
the
named
insured
may
not
be
the
policy
holder,
e.g.,
where
a
policy
holder
purchases
life
insurance
policy
in
which
another
party
is
the
named
insured
and
the
policy
holder
is
the
beneficiary
of
the
policy.
Note:
The
party
playing
the
role
of
a
named
insured
is
not
a
claimant
in
the
sense
conveyed
by
the
RoleClassCoveredParty
CLAIM
(claimant).
However,
a
named
insured
may
make
a
claim
under
a
policy,
e.g.,
e.g.,
a
party
that
is
the
named
insured
and
policy
holder
under
a
comprehensive
automobile
insurance
policy
may
become
the
claimant
for
coverage
under
that
policy
e.g.,
if
injured
in
an
automobile
accident
and
there
is
no
liable
third
party.
In
the
case
of
a
named
insured
making
a
claim,
a
role
type
code
INSCLM
(insured
claimant)
subtypes
the
class
to
indicate
that
a
named
insured
has
filed
a
claim
for
a
loss.
Example:
The
named
insured
under
a
comprehensive
automobile,
disability,
or
property
and
casualty
policy
that
is
the
named
insured
and
may
or
may
not
be
the
policy
holder.
NOK
next
of
kin
An
individual
designated
for
notification
as
the
next
of
kin
for
a
given
entity.
PAT
patient
A
Role
of
a
LivingSubject
(player)
as
an
actual
or
potential
recipient
of
health
care
services
from
a
healthcare
provider
organization
(scoper).
Usage
Note:
Communication
about
relationships
between
patients
and
specific
healthcare
practitioners
(people)
is
not
done
via
scoper.
Instead
this
is
generally
done
using
the
CareProvision
act.
This
allows
linkage
between
patient
and
a
particular
healthcare
practitioner
role
and
also
allows
description
of
the
type
of
care
involved
in
the
relationship.
PROV
healthcare
provider
An
Entity
(player)
that
is
authorized
to
provide
health
care
services
by
some
authorizing
agency
(scoper).
NOT
notary
public
notary
public
Include
these
includes
codes
as
defined
in
http://terminology.hl7.org/CodeSystem/v3-RoleCode
Code
Display
CLASSIFIER
classifier
An
individual
authorized
to
assign
an
original
classification
to
information,
including
compilations
of
unclassified
information,
based
on
a
determination
that
the
information
requires
protection
against
unauthorized
disclosure.
The
individual
marks
the
information
with
immutable,
computable,
and
human
readable
security
labels
in
accordance
with
applicable
security
labeling
policies.
The
labeling
policies
provide
instructions
on
whether
and
if
so
how
the
security
labels
may
be
later
reclassified
[i.e.,
upgraded,
downgraded,
used
in
derivative
classification,
or
declassified]
in
a
manner
that
preserves
the
overridden
original
classification
binding
and
provenance.
CONSENTER
consenter
An
entity
or
an
entity's
delegatee
who
is
the
grantee
in
an
agreement
such
as
a
consent
for
services,
advanced
directive,
or
a
privacy
consent
directive
in
accordance
with
jurisdictional,
organizational,
or
patient
policy.
CONSWIT
consent
witness
An
entity
which
has
witnessed
and
attests
to
observing
another
entity
being
counseled
about
an
agreement
such
as
a
consent
for
services,
advanced
directive,
or
a
privacy
consent
directive.
COPART
co-participant
An
entity
which
participates
in
the
generation
of
and
attest
to
veracity
of
content,
but
is
not
an
author
or
coauthor.
For
example
a
surgeon
who
is
required
by
institutional,
regulatory,
or
legal
rules
to
sign
an
operative
report,
but
who
was
not
involved
in
the
authorship
of
that
report.
DECLASSIFIER
declassifier
An
individual
which
is
authorized
to
declassify
information
based
on
a
determination
that
the
information
no
longer
requires
protection
against
unauthorized
disclosure.
The
individual
marks
the
information
being
declassified
using
computable
and
human
readable
security
labels
indicating
that
this
is
copy
of
previously
classified
information
is
unclassified
in
accordance
with
applicable
security
labeling
policies.
The
labeling
policies
provide
instructions
on
whether
and
if
so
how
the
security
labels
may
be
later
reclassified
[i.e.,
upgraded
or
used
in
derivative
classification]
in
a
manner
that
preserves
the
overridden
original
classification
binding
and
provenance.
DELEGATEE
delegatee
A
party
to
whom
some
right
or
authority
is
granted
by
a
delegator.
DELEGATOR
delegator
following
rules:
http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction
http://dicom.nema.org/resources/ontology/DCM
http://terminology.hl7.org/CodeSystem/extra-security-role-type
version
📦1.0.1
This expansion generated 17 Dec 2025
Application
Launcher
ValueSet
Audit
participant
role
ID
of
software
application
launcher,
i.e.,
the
entity
that
started
or
stopped
an
application
Expansion performed internally based on:
This
value
set
contains
76
24
concepts
|
|
|
Display | Definition |
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
enterer
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
performer
|
|
An
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
author
|
|
An
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
editor
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
verifier
|
Verifier |
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
legal
|
|
An
agent
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
attester
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
informant
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
custodian
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
transmitter
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
assembler
|
|
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
transformer
|
|
A
|
http://terminology.hl7.org/CodeSystem/provenance-participant-type
|
composer
|
|
|
http://dicom.nema.org/resources/ontology/DCM
|
110150
|
|
Audit
participant
role
|
http://dicom.nema.org/resources/ontology/DCM
|
110151
|
|
Audit
participant
role
ID
of
|
http://dicom.nema.org/resources/ontology/DCM
|
110152
|
|
Audit
participant
role
ID
of
the
|
http://dicom.nema.org/resources/ontology/DCM
|
110153
|
|
Audit
participant
role
ID
of
|
http://dicom.nema.org/resources/ontology/DCM
|
110154
|
|
Audit
participant
role
ID
of
|
http://dicom.nema.org/resources/ontology/DCM
|
110155
|
|
Audit
participant
role
ID
of
media
providing
data
during
an
|
http://terminology.hl7.org/CodeSystem/extra-security-role-type
|
authserver
|
|
An entity providing authorization services to enable the electronic sharing of health-related information based on resource owner's preapproved permissions. For example, an UMA Authorization Server[UMA] |
http://terminology.hl7.org/CodeSystem/extra-security-role-type
|
datacollector
|
|
An entity that collects information over which the data subject may have certain rights under policy or law to control that information's management and distribution by data collectors, including the right to access, retrieve, distribute, or delete that information. |
http://terminology.hl7.org/CodeSystem/extra-security-role-type
|
dataprocessor
|
|
An entity that processes collected information over which the data subject may have certain rights under policy or law to control that information's management and distribution by data processors, including the right to access, retrieve, distribute, or delete that information. |
http://terminology.hl7.org/CodeSystem/extra-security-role-type
|
datasubject
|
|
A person whose personal information is collected or processed, and who may have certain rights under policy or law to control that information's management and distribution by data collectors or processors, including the right to access, retrieve, distribute, or delete that information. |
http://terminology.hl7.org/CodeSystem/extra-security-role-type
|
humanuser
|
|
The human user that has participated. |
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 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 that the code is 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 of the concept |
| Comments | Additional notes about how to use the code |