This
page
is
part
of
the
FHIR
Specification
(v4.0.1:
R4
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
(v5.0.0-snapshot1:
R5
Snapshot
#1).
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
Orders
and
Observations
Work
Group
|
Maturity Level : 0 | Informative | Use Context : Any |
This is a value set defined by the FHIR project.
Summary
| Defining URL: |
http://hl7.org/fhir/ValueSet/secondary-finding
|
| Version: |
|
| Name: | ObservationCategoryCodes |
| Title: | Observation Category Codes |
| Definition: |
Codes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding. |
| Committee: |
Orders
and
Observations
Work
Group
|
| OID: | 2.16.840.1.113883.4.642.3.1285 (for OID based terminology systems) |
| Source Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/secondary-finding
This
expansion
generated
01
Nov
2019
19
Dec
2021
This value set contains 2 concepts
Expansion
based
on
http://hl7.org/fhir/secondary-finding
version
4.0.1
Genetic
Observation
Secondary
Findings
v5.0.0-snapshot1
(CodeSystem)
All
codes
in
this
table
are
from
the
system
http://hl7.org/fhir/secondary-finding
| Code | Display | Definition |
| acmg-version1 | ACMG Version 1 | First release (2013): ACMG Recommendations for Reporting of Incidental Findings in Clinical Exome and Genome Sequencing. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3727274/ |
| acmg-version2 | ACMG Version 2 | Second release (2016): Recommendations for reporting of secondary findings in clinical exome and genome sequencing, 2016 update (ACMG SF v2.0): a policy statement of the American College of Medical Genetics and Genomics. https://www.ncbi.nlm.nih.gov/pubmed/27854360 |
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 |