This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
(v4.0.1:
R4
-
Mixed
Normative
and
STU
3).
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
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:
R4
R3
R4
R3
Vocabulary
Work
Group
|
Maturity Level : N/A | External | Use Context : Any |
This
value
set
(http://hl7.org/fhir/ValueSet/v3-RoleClassPassive)
(http://terminology.hl7.org/ValueSet/v3-RoleClassPassive)
is
defined
as
part
of
HL7
v3.
Related
FHIR
content:
RoleClassPassive
.
Summary
| Defining URL: |
|
| Version: | 2014-03-26 |
| Name: |
|
| Title: | V3 Value SetRoleClassPassive |
| Definition: |
An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity. |
| OID: | 2.16.840.1.113883.1.11.19105 (for OID based terminology systems) |
| Source Resource | XML / JSON |
This value set is not currently used
This value set includes codes from the following code systems:
http://hl7.org/fhir/v3/RoleClass
http://terminology.hl7.org/CodeSystem/v3-RoleClass
where
concept
is-a
_RoleClassPassive
http://hl7.org/fhir/v3/RoleClass
http://terminology.hl7.org/CodeSystem/v3-RoleClass
| Code | Display | |
| _RoleClassPassive | RoleClassPassive | An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity. |
This
expansion
generated
19
Apr
2017
01
Nov
2019
This value set contains 26 concepts
Expansion
based
on
http://hl7.org/fhir/v3/RoleClass
http://terminology.hl7.org/CodeSystem/v3-RoleClass
version
2016-11-11
2018-08-12
All
codes
from
system
http://hl7.org/fhir/v3/RoleClass
http://terminology.hl7.org/CodeSystem/v3-RoleClass
| Code | Display | Definition |
| ACCESS | access | A role in which the playing entity (material) provides access to another entity. The principal use case is intravenous (or other bodily) access lines that preexist and need to be referred to for medication routing instructions. |
| ADJY | adjacency | A physical association whereby two Entities are in some (even lose) spatial relationship with each other such that they touch each other in some way. Examples: the colon is connected (and therefore adjacent) to the jejunum; the colon is adjacent to the liver (even if not actually connected.) UsageConstraints: Adjacency is in principle a symmetrical connection, but scoper and player of the role should, where applicable, be assigned to have scoper be the larger, more central Entity and player the smaller, more distant, appendage. |
| CONC | connection | An adjacency of two Entities held together by a bond which attaches to each of the two entities. Examples: biceps brachii muscle connected to the radius bone, port 3 on a network switch connected to port 5 on a patch panel. UsageConstraints: See Adjacency for the assignment of scoper (larger, more central) and player (smaller, more distant). |
| BOND | molecular bond | A connection between two atoms of a molecule. Examples: double bond between first and second C in ethane, peptide bond between two amino-acid, disulfide bridge between two proteins, chelate and ion associations, even the much weaker van-der-Waals bonds can be considered molecular bonds. UsageConstraints: See connection and adjacency for the assignment of player and scoper. |
| CONY | continuity | A connection between two regional parts. Examples: the connection between ascending aorta and the aortic arc, connection between descending colon and sigmoid. UsageConstraints: See connection and adjacency for the assignment of player and scoper. |
| ADMM | Administerable Material | A material (player) that can be administered to an Entity (scoper). |
| BIRTHPL | birthplace | Relates a place (playing Entity) as the location where a living subject (scoping Entity) was born. |
| DEATHPLC | place of death | Definition: Relates a place (playing Entity) as the location where a living subject (scoping Entity) died. |
| DST | distributed material | A material (player) distributed by a distributor (scoper) who functions between a manufacturer and a buyer or retailer. |
| RET | retailed material | Material (player) sold by a retailer (scoper), who also give advice to prospective buyers. |
| EXLOC | event location | A role played by a place at which the location of an event may be recorded. |
| SDLOC | service delivery location | A role played by a place at which services may be provided. |
| DSDLOC | dedicated service delivery location |
A
role
of
a
place
(player)
that
is
intended
to
house
the
provision
of
services.
Scoper
is
the
Entity
(typically
Organization)
that
provides
these
services.
This
is
not
synonymous
with
|
| ISDLOC | incidental service delivery location | A role played by a place at which health care services may be provided without prior designation or authorization. |
| EXPR | exposed entity |
A
role
played
by
an
entity
that
has
been
exposed
to
a
person
or
animal
suffering
a
contagious
disease,
or
with
a
location
from
which
a
toxin
has
been
distributed.
The
player
of
the
role
is
normally
a
person
or
animal,
but
it
is
possible
that
other
entity
types
could
become
exposed.
The
role
is
scoped
by
the
source
of
the
exposure,
and
it
is
quite
possible
for
a
person
playing
the
role
of
exposed
party
to
also
become
the
scoper
a
role
played
by
another
person.
That
is
to
say,
once
a
person
has
become
infected,
it
is
possible,
perhaps
likely,
for
that
person
to
infect
others.
Management
of
exposures
and
tracking
exposed
parties
is
a
key
function
within
public
health,
and
within
most
public
health
contexts
-
exposed
parties
are
known
as
|
| HLD | held entity | Entity that is currently in the possession of a holder (scoper), who holds, or uses it, usually based on some agreement with the owner. |
| HLTHCHRT | health chart | The role of a material (player) that is the physical health chart belonging to an organization (scoper). |
| IDENT | identified entity | A role in which the scoping entity designates an identifier for a playing entity. |
| MANU | manufactured product | Scoped by the manufacturer |
| THER | therapeutic agent | A manufactured material (player) that is used for its therapeutic properties. The manufacturer is the scoper. |
| MNT | maintained entity | An entity (player) that is maintained by another entity (scoper). This is typical role held by durable equipment. The scoper assumes responsibility for proper operation, quality, and safety. |
| OWN | owned entity | An Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material. |
| RGPR | regulated product | A product regulated by some governmentatl orgnization. The role is played by Material and scoped by Organization. Rationale: To support an entity clone used to identify the NDC number for a drug product. |
| TERR | territory of authority |
Relates
a
place
entity
(player)
as
the
region
over
which
the
scoper
(typically
an
Organization)
has
certain
authority
(jurisdiction).
For
example,
the
Calgary
Regional
Health
Authority
(scoper)
has
authority
over
the
territory
|
| USED | used entity | Description:An entity (player) that is used by another entity (scoper) |
| WRTE | warranted product | A role a product plays when a guarantee is given to the purchaser by the seller (scoping entity) stating that the product is reliable and free from known defects and that the seller will repair or replace defective parts within a given time limit and under certain conditions. |