This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
STU
3).
(v3.5.0:
R4
Ballot
#2).
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:
R4B
R4
R3
R2
Work
Group
|
Maturity Level : 0 | Informative | Use Context : Not Intended for Production use |
This
is
a
value
set
defined
at
http://healthit.gov
.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/dataelement-sdcobjectclassproperty |
| Version: | 3.5.0 |
| Name: | DataElementSDCObjectClass |
| Title: | DataElement SDC Object Class |
| Definition: |
The allowed codes for identifying the ISO 11179 ObjectClass Property for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. |
| Committee: |
FHIR
Infrastructure
Work
Group
|
| OID: |
|
| Copyright: |
This
value
set
includes
content
from
LOINC®,
which
is
copyright
©
1995
Regenstrief
Institute,
Inc.
and
the
LOINC
Committee,
and
available
at
no
cost
under
the
license
at
http://loinc.org/terms-of-use.
This
|
| Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
http://snomed.info/sct
http://loinc.org
http://www.nlm.nih.gov/research/umls/rxnorm
This
expansion
generated
19
Apr
2017
Aug
2018
This value set cannot be expanded because of the way it is defined - it has an infinite number of members
| Code | System | Display |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
|
|
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
|
| 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 |