Terminology
This
page
is
part
of
the
FHIR
Specification
(v4.3.0:
R4B
-
STU
(v5.0.0-snapshot3:
R5
Snapshot
#3,
to
support
Connectathon
32
).
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:
R5
R4B
R4
R3
R2
|
Work
Group
|
Maturity Level : N/A | Standards Status : Informative |
This
table
contains
a
list
of
all
the
value
sets
defined
as
part
of
the
core
FHIR
specification.
Some
of
these
value
sets
include
codes
defined
elsewhere,
some
contain
their
own
inline
code
system
definitions,
codes
defined
as
part
of
FHIR,
and
some
do
both.
Any
implicit
code
systems
Value
sets
that
are
case
sensitive,
though
defined
in
implementation
guides
or
the
HL7
Terminology
outside
this
core
specification
are
NOT
listed
in
this
table.
Additional
value
sets
may
be
found
in
FHIR
will
never
define
codes
that
only
differ
by
case.
implementation
guides
in
the
FHIR
registry
(https://registry.fhir.org)
Note that these value sets are available as FHIR resources - see the Downloads Page (as part of the FHIR definitions)
| Name | Definition | Source |
| Namespace: http://hl7.org/fhir/ValueSet | ||
| FHIR-version N | All published FHIR Versions. | Internal |
|
| Indicates who is expected to pay a part of the account balance. | Internal |
|
|
| Internal |
| account-billing-status |
Indicates
whether
the
|
Internal |
|
| Relationship between accounts | Internal |
| account-status | Indicates whether the account is available to be used. | Internal |
| account-type | This examples value set defines the set of codes that can be used to represent the type of an account. | V3 |
| action-cardinality-behavior | Defines behavior for an action or a group for how many times that item may be repeated. | Internal |
| action-code | Provides examples of actions to be performed. |
|
| action-condition-kind | Defines the kinds of conditions that can appear on actions. | Internal |
| action-grouping-behavior | Defines organization behavior of a group. | Internal |
|
| The function performed by the participant for the action. | Internal |
| action-participant-type | The type of participant for the action. | Internal |
| action-precheck-behavior | Defines selection frequency behavior for an action or group. | Internal |
| action-reason-code | Provides examples of reasons for actions to be performed. |
|
| action-relationship-type | Defines the types of relationships between actions. | Internal |
| action-required-behavior | Defines expectations around whether an action or action group is required. | Internal |
| action-selection-behavior | Defines selection behavior of a group. | Internal |
| action-type | The type of action to be performed. | Other |
|
| Additional Binding Purpose | Internal |
| additional-instruction-codes | This value set includes all SNOMED CT Additional Dosage Instructions. | SNOMED CT |
| address-type N | The type of an address (physical / postal). | Internal |
| address-use N | The use of an address. | Internal |
| adjudication | This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc. | Other |
| adjudication-error | This value set includes a smattering of adjudication codes. | Other |
| adjudication-reason | This value set includes smattering of Adjudication Reason codes. | Other |
| administrable-dose-form | Dose form for a medication, in the form suitable for administering to the patient, after mixing, where necessary. | Internal |
| administration-method-codes | This value set includes some method codes from SNOMED CT - provided as an exemplar | SNOMED CT |
|
| MedicationAdministration Subpotent Reason | Internal |
| administrative-gender N | The gender of a person used for administrative purposes. | Internal |
| adverse-event-actuality | Overall nature of the adverse event, e.g. real or potential. | Internal |
| adverse-event-category | Overall categorization of the event, e.g. product-related or situational. | Other |
| adverse-event-causality-assess | Codes for the assessment of whether the entity caused the event. | Other |
| adverse-event-causality-method | TODO. | Other |
|
| This value set includes codes that describe the contributing factors suspected to have increased the probability or severity of the adverse event. | SNOMED CT |
| adverse-event-mitigating-action | This value set includes codes that describe the ameliorating actions taken after the adverse event occured in order to reduce the extent of harm. | SNOMED CT |
| adverse-event-outcome |
|
|
|
| This value set includes codes that describe the type of involvement of the actor in the adverse event. | V3 |
| adverse-event-preventive-action | This value set includes codes that describe the preventive actions that contributed to avoiding the adverse event. | SNOMED CT |
| adverse-event-seriousness | Overall seriousness of this event for the patient. | Other |
|
| Codes identifying the lifecycle stage of an adverse event. | Internal |
|
|
|
|
| adverse-event-type |
This
value
set
includes
|
SNOMED CT |
| age-units | Unified Code for Units of Measure (UCUM). This value set includes all common UCUM codes used for Age - that it is, all commonly used units which have the same canonical unit as 'a' (year) | FHIR |
| all-distance-units |
Unified
Code
for
Units
of
Measure
(UCUM).
This
value
set
includes
all
possible
UCUM
codes
used
for
distance
measures
-
that
it
is,
all
units
|
FHIR |
| all-languages N | This value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47) | Other |
|
| All fhir data types (including abstract resources) | Internal |
| all-time-units |
Unified
Code
for
Units
of
Measure
(UCUM).
This
value
set
includes
all
possible
UCUM
codes
used
for
|
|
|
|
|
|
| allergen-class | This value set represents codes for food nutrients and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept has a parent of 406455002 Allergen class (substance). | SNOMED CT |
| allergy-intolerance-category | Category of an identified substance associated with allergies or intolerances. | Internal |
| allergy-intolerance-criticality | Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. | Internal |
| allergy-intolerance-type | Identification of the underlying physiological mechanism for a Reaction Risk. | Internal |
| allergyintolerance-clinical | Preferred value set for AllergyIntolerance Clinical Status. | Other |
| allergyintolerance-code | This value set includes concept codes for specific substances/pharmaceutical products, allergy or intolerance conditions, and negation/exclusion codes to specify the absence of specific types of allergies or intolerances. | Other, SNOMED CT |
| allergyintolerance-verification |
|
Other |
| animal-breeds | This example value set defines a set of codes that can be used to indicate breeds of species. | SNOMED CT |
| animal-genderstatus | This example value set defines a set of codes that can be used to indicate the current state of the animal's reproductive organs. | Internal |
| animal-species | This example value set defines a set of codes that can be used to indicate species of animal patients. | SNOMED CT |
| animal-tissue-type | A tissue type of an animal. | Internal |
| appointment-cancellation-reason | This example value set defines a set of reasons for the cancellation of an appointment. | Other |
|
| The recurrence type of a recurring appointment. | FHIR |
| appointmentstatus | The free/busy status of an appointment. | Internal |
| approach-site-codes | This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar. | SNOMED CT |
|
|
|
|
| artifact-contribution-instance-type | Artifact Contribution Instance Type |
|
| artifact-contribution-type | Citation contribution. |
|
|
| Code the reason for different URLs, eg abstract and full-text. | Internal |
|
|
|
|
|
| The type of information contained in a component of an artifact assessment. | Internal |
| artifactassessment-workflow-status | Possible values for the workflow status of the comment or assessment, typically used to coordinate workflow around the process of accepting and rejecting changes and comments on the artifact. | Internal |
| assert-direction-codes | The type of direction to use for assertion. | Internal |
| assert-operator-codes | The type of operator to use for assertion. | Internal |
| assert-response-code-types | The type of response code to use for assertion. | Internal |
| asset-availability | This value set has asset availability codes. | Internal |
| attribute-estimate-type | A statistic about a statistic, e.g. Confidence interval or p-value | Other |
| audit-event-action | Indicator for type of action performed during the event that generated the event. | Internal |
| audit-event-outcome | Indicates whether the event succeeded or failed. | Other, Internal |
|
| Indicates more detailed reason for outcome. | Other |
| audit-event-severity | The severity of the audit entry. | Internal |
| audit-event-sub-type |
More
detailed
code
concerning
the
type
of
the
audit
event
-
defined
by
DICOM
with
some
|
DICOM, Internal |
| audit-event-type |
Event
|
DICOM, Other |
|
|
|
|
| basic-resource-type | This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. | Other |
| benefit-network | This value set includes a smattering of Network type codes. | Other |
| benefit-term | This value set includes a smattering of Benefit Term codes. | Other |
| benefit-type | This value set includes a smattering of Benefit type codes. | Other |
| benefit-unit | This value set includes a smattering of Unit type codes. | Other |
| binding-strength N | Indication of the degree of conformance expectations associated with a binding. | Internal |
|
| This value set can enumerate ISBT 128 Codes published by ICCBBA as a part of the ISBT 128 standard. These example codes represent data elements defined in ST-027 ISBT 128 Dictionary of Standard Data Elements and are used to define data structure and format expectations for electronic exchange with the ISBT 128 standard. | Internal |
| biologicallyderived-product-status | Biologically Derived Product Status. | Internal |
| biologicallyderived-productcodes | This value set enumerates ISBT 128 Product Description Codes© published by ICCBBA as a part of the ISBT 128 standard. These codes support characterization and classification of medical products of human origin inclusive of processing conditions such as additives, volumes and handling conditions. | Internal |
| body-site | This value set includes all codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 442083009 (Anatomical or acquired body site (body structure)). | SNOMED CT |
| bodystructure-code | This value set includes all codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 442083009 (Anatomical or acquired body site (body structure)). | SNOMED CT |
| bodystructure-relative-location | SNOMED-CT concepts modifying the anatomic location | SNOMED CT |
| bundle-type N | Indicates the purpose of a bundle - how it is intended to be used. | Internal |
| c80-facilitycodes | This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147. | SNOMED CT |
| c80-practice-codes | This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition. | SNOMED CT |
| capability-format-type N |
| Internal, Other |
| capability-statement-kind N | How a capability statement is intended to be used. | Internal |
| care-plan-activity-kind | Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity. | Internal |
|
|
Example
codes
indicating
the
|
SNOMED CT |
| care-plan-activity-status | Codes that reflect the current state of a care plan activity within its overall life cycle. | Internal |
|
| Example codes indicating the reason why the activity isn't yet started, is on hold, was cancelled, etc. Note that these are in no way complete and might not even be appropriate for some uses. | Other |
| care-plan-category | Example codes indicating the category a care plan falls within. Note that these are in no way complete and might not even be appropriate for some uses. | SNOMED CT |
| care-plan-intent | Codes indicating the degree of authority/intentionality associated with a care plan. | Internal |
| care-team-category | Indicates the type of care team. | LOINC |
| care-team-status | Indicates the status of the care team. | Internal |
| catalogType | Description Needed Here | Internal |
| cdshooks-indicator | This value set captures the set of indicator codes defined by the CDS Hooks specification. | Other |
| certainty-rating | The assessment of quality, confidence, or certainty. | Other |
| certainty-type | The aspect of quality, confidence, or certainty. |
|
| characteristic-combination | Logical grouping of characteristics. | Internal |
|
|
|
|
| chargeitem-billingcodes | Example set of codes that can be used for billing purposes. | Other |
| chargeitem-status | Codes identifying the lifecycle stage of a ChargeItem. | Internal |
|
|
|
|
| citation-artifact-classifier | Citation artifact classifier |
|
| citation-classification-type | Citation classification type |
|
| citation-status-type | Citation status type |
|
| citation-summary-style | The format for display of the citation. |
|
| cited-artifact-abstract-type | Used to express the reason and specific aspect for the variant abstract, such as language and specific language. |
|
| cited-artifact-classification-type | Cited Artifact Classification Type |
|
| cited-artifact-part-type | To describe the reason for the variant citation, such as version number or subpart specification. |
|
| cited-artifact-status-type | Cited Artifact Status Type |
|
| cited-medium | NLM codes Internet or Print. |
|
| claim-careteamrole | This value set includes sample Claim Care Team Role codes. | Other |
|
| This value set includes Claim Adjudication Decision codes. | Internal |
| claim-exception | This value set includes sample Exception codes. | Other |
| claim-informationcategory | This value set includes sample Information Category codes. | Other |
| claim-modifiers | This value set includes sample Modifier type codes. | Other |
|
| This value set includes Claim Processing Outcome codes. | Internal |
| claim-subtype | This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation. | Other |
| claim-type | This value set includes Claim Type codes. | Other |
| claim-use | The purpose of the Claim: predetermination, preauthorization, claim. | Internal |
| clinical-findings | This value set includes all the "Clinical finding" [SNOMED CT](http://snomed.info/sct) codes - concepts where concept is-a 404684003 (Clinical finding (finding)). | SNOMED CT |
| clinical-use-definition-category | A categorisation for a clinical use information item. | Internal |
| clinical-use-definition-type | Overall defining type of this clinical use definition. | Internal |
|
|
Example
|
SNOMED CT |
|
|
|
|
|
|
|
|
| code-search-support | The degree to which the server supports the code search parameter on ValueSet, if it is supported. | Internal |
|
| Description Needed Here | Internal |
| codesystem-content-mode N | The extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource. | Internal |
| codesystem-hierarchy-meaning N | The meaning of the hierarchy of concepts in a code system. | Internal |
| codesystem-properties-mode |
| Internal |
| combined-dose-form | Dose forms for a product as a whole, considering all individual parts, but before any mixing | Internal |
| common-tags | Common Tag Codes defined by FHIR project |
|
| communication-category | Codes for general categories of communications such as alerts, instructions, etc. | Other |
| communication-not-done-reason | Codes for the reason why a communication did not happen. | Other |
|
| Example codes indicating the reason why a CommunicationRequest is on hold or revoked. Note that these are in no way complete and might not even be appropriate for some uses. | SNOMED CT |
| communication-topic | Codes describing the purpose or content of the communication. | Other |
| compartment-type | Which type a compartment definition describes. | Internal |
| composite-measure-scoring | The composite scoring method of the measure. | Other |
| composition-attestation-mode | The way in which a person authenticated a composition. | Internal |
| composition-status | The workflow/clinical status of the composition. | Internal |
| concept-map-equivalence | The degree of equivalence between concepts. | Internal |
|
| The relationship between concepts. | Internal |
| concept-property-type N | The type of a property value. | Internal |
| concept-subsumption-outcome |
|
Internal |
| conceptmap-unmapped-mode | Defines which action to take if there is no match in the group. | Internal |
|
| List of all non-abstract types, data types and resources | Internal |
| condition-category | Preferred value set for Condition Categories. | Other |
| condition-cause | Example value set for Cause of Condition codes | SNOMED CT |
| condition-clinical | Preferred value set for Condition Clinical Status. | Other |
| condition-code | Example value set for Condition/Problem/Diagnosis codes. | SNOMED CT |
|
| Value set for clinical course of a disease (how the disease behaves over time). | SNOMED CT |
| condition-outcome | Example value set for condition outcomes. | SNOMED CT |
|
| Kind of precondition for the condition. | Internal |
| condition-predecessor | Example value set for condition predecessor codes. | SNOMED CT |
|
| The use of a questionnaire. | Internal |
| condition-severity | Preferred value set for Condition/Diagnosis severity grading. | SNOMED CT |
| condition-stage | Example value set for stages of cancer and other conditions. | SNOMED CT |
| condition-stage-type | Example value set for the type of stages of cancer and other conditions | SNOMED CT |
| condition-ver-status | The verification status to support or decline the clinical status of the condition or diagnosis. | Other |
| conditional-delete-status N | A code that indicates how the server supports conditional delete. | Internal |
| conditional-read-status N | A code that indicates how the server supports conditional read. | Internal |
|
| Description Needed Here | Internal |
| consent-action | This value set includes sample Consent Action codes. | Other |
| consent-category | This value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes; HL7 VALUE SET: ActConsentType(2.16.840.1.113883.1.11.19897); examples of US realm consent directive legal descriptions and references to online and/or downloadable forms such as the SSA-827 Authorization to Disclose Information to the Social Security Administration; and other anticipated consent directives related to participation in a clinical trial, medical procedures, reproductive procedures; health care directive (Living Will); advance directive, do not resuscitate (DNR); Physician Orders for Life-Sustaining Treatment (POLST) | Other, LOINC |
| consent-content-class | This value set includes the FHIR resource types, along with some other important content class codes |
|
| consent-content-code | This example value set contains all LOINC code | LOINC |
| consent-data-meaning | How a resource reference is interpreted when testing consent restrictions. | Internal |
| consent-policy | This value set includes sample Regulatory consent policy types from the US and other regions. | Other |
| consent-provision-type | How a rule statement is applied, such as adding additional consent or removing consent. | Internal |
|
|
|
|
|
|
|
|
| consistency-type | FluidConsistencyType : Codes used to represent the consistency of fluids and liquids provided to the patient. This value set includes concepts from [SNOMED CT](http://snomed.info/sct)(US Extension) where concept is a 435681000124103 (Dietary liquid consistency diet (regime/therapy)). It is provided as a suggestive example. | SNOMED CT |
| constraint-severity N | SHALL applications comply with this constraint? | Internal |
| contact-point-system N | Telecommunications form for contact point. | Internal |
| contact-point-use N | Use of contact point. | Internal |
| container-cap | Color of the container cap. | Other |
| container-material | This value set includes SNOMED CT codes for materials that specimen containers are made of | SNOMED CT |
| contract-action | This value set includes sample Contract Action codes. | Other |
| contract-actionstatus | This value set contract specific codes for action status. | Internal |
| contract-actorrole | This value set includes sample Contract Actor Role codes. | Other |
| contract-assetcontext | This value set contract specific codes for asset context. | Internal |
| contract-assetscope | This value set contract specific codes for asset scope. | Internal |
| contract-assetsubtype | This value set contract specific codes for asset subtype. | Internal |
| contract-assettype | This value set contract specific codes for asset type. | Internal |
| contract-content-derivative | This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses. | Other |
| contract-decision-mode | This value set contract specific codes for decision modes. | Internal |
| contract-definition-subtype | This value set contract specific codes for status. | Internal |
| contract-definition-type | This value set contract specific codes for status. | Internal |
| contract-expiration-type | This value set contract specific codes for status. | Internal |
| contract-legalstate | This value set contract specific codes for status. | Internal |
| contract-party-role | This value set contract specific codes for offer party participation. | Internal |
| contract-publicationstatus | This value set contract specific codes for status. | Internal |
| contract-scope | This value set contract specific codes for scope. | Internal |
| contract-security-category | This value set contract specific codes for security category. | Internal |
| contract-security-classification | This value set contract specific codes for security classification. | Internal |
| contract-security-control | This value set contract specific codes for security control. | Internal |
| contract-signer-type | This value set includes sample Contract Signer Type codes. | Other |
| contract-status | This value set contract specific codes for status. | Internal |
| contract-subtype | This value set includes sample Contract Subtype codes. | Other |
| contract-term-subtype | This value set includes sample Contract Term SubType codes. | Other |
| contract-term-type | This value set includes sample Contract Term Type codes. | Other |
| contract-type | This value set includes sample Contract Type codes. | Other |
| contributor-role | Used to code the format of the display string. |
|
| contributor-summary-source | Used to code the producer or rule for creating the display string. |
|
| contributor-summary-style | Used to code the format of the display string. |
|
| contributor-summary-type | Used to code author list statement, contributorship statement, and such. |
|
| contributor-type | The type of contributor. | Internal |
| country | This value set defines a base set of codes for countries. Note: The codes for countries are taken from [ISO 3166](https://www.iso.org/iso-3166-country-codes.html). | Other |
| coverage-class | This value set includes Coverage Class codes. | Other |
| coverage-copay-type | This value set includes sample Coverage Copayment Type codes. | Other |
| coverage-financial-exception | This value set includes Example Coverage Financial Exception Codes. | Other |
|
|
|
|
|
|
This
value
set
includes
|
Other |
|
|
|
Other |
| currencies N | Currency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html) | Other |
| data-absent-reason N | Used to specify why the normally expected content of the data element is missing. | Other |
| data-types N |
|
Internal |
| dataelement-sdcobjectclass | The allowed codes for identifying the ISO 11179 ObjectClass for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. | SNOMED CT, LOINC, Other |
| dataelement-sdcobjectclassproperty | 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. | SNOMED CT, LOINC, Other |
| days-of-week N | The days of the week. | Internal |
|
|
|
Internal |
| definition-resource-types N |
|
Internal |
| definition-topic | High-level categorization of the definition, used for searching, sorting, and filtering. | Other |
| definition-use N | Structure Definition Use Codes / Keywords | Other |
| designation-use N | Details of how a designation would be used | SNOMED CT |
| detectedissue-category | Kinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. | V3 |
| detectedissue-mitigation-action | Kinds of mitigating actions and observations that can be associated with a detected issue or contraindication, such as 'added concurrent therapy', 'prior therapy documented', etc. | V3 |
| detectedissue-severity | Indicates the potential degree of impact of the identified issue on the patient. | Internal |
|
| Indicates the status of a detected issue | Internal |
| device-action | Example codes indicating the change that happened to the device during the procedure. Note that these are in no way complete and might not even be appropriate for some uses. | SNOMED CT |
|
| The association status of the device. | Internal |
|
|
|
|
|
| The association state of the device. | Internal |
| device-correctiveactionscope | Device - Corrective action scope | Internal |
| device-nametype | The type of name the device is referred by. | Internal |
|
| The operation mode of the device. | Internal |
|
|
|
Internal |
|
|
The
|
Internal |
| device-productidentifierinudi | Device Production Identifier in UDI | Internal |
|
| Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example. | Other, SNOMED CT |
|
| Codes used to identify medical devices safety characteristics. These codes are taken from the [NCI Thesaurus](https://ncit.nci.nih.gov/ncitbrowser/pages/home.jsf) and are provided here as a suggestive example. | Other |
| device-specialization-category |
The
|
Internal |
| device-specialization-systemtype | The type or specialization of a standard that devices can adhere to | Other |
|
| The status of the Device record. | Internal |
| device-type | Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example. | Other, SNOMED CT |
|
| Describes the type of version | Other |
| devicedefinition-regulatory-identifier-type | Regulatory Identifier type | Internal |
| devicedefinition-relationtype | Description Needed Here | Internal |
| devicedispense-status | DeviceDispense Status Codes | Internal |
| devicedispense-status-reason | DeviceDispense Status Reason Codes | Internal |
| devicemetric-type | Codes used to identify health care device metric types and units and component types as part of the ISO/IEEE 11073-10101 Medical Device Communication Nomenclature. | Other |
|
| A coded concept indicating the adherence of device usage. | Internal |
| deviceusage-adherence-reason | A coded concept indicating the adherence of device usage. | Internal |
| deviceusage-status | A coded concept indicating the current status of the Device Usage. | Internal |
| diagnosis-role | This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record. | Other |
| diagnostic-report-status | The status of the diagnostic report. | Internal |
| diagnostic-service-sections | This value set includes all the codes in HL7 V2 table 0074. | V2 |
| diet-type | Codes that can be used to indicate the type of food being ordered for a patient. This value set is provided as a suggestive example. It includes codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182922004 (Dietary regime (regime/therapy)) | SNOMED CT |
| directness | The quality of how direct the match is. | Other |
| discriminator-type N | How an element value is interpreted when discrimination is evaluated. | Internal |
| disease-status | The status of a disease or symptom. | SNOMED CT |
| disease-symptom-procedure | A symptom, disease or procedure. | SNOMED CT |
| distance-units |
Unified
Code
for
Units
of
Measure
(UCUM).
This
value
set
includes
all
common
UCUM
codes
used
for
|
|
| doc-section-codes | Document section codes (LOINC codes used in CCDA sections). | LOINC |
| doc-typecodes | FHIR Document Codes - all LOINC codes where scale type = 'DOC'. | LOINC |
| document-mode N | Whether the application produces or consumes documents. | Internal |
| document-reference-status | The status of the document reference. | Internal |
| document-relationship-type | The type of relationship between documents. | Internal |
|
|
|
|
|
| This value set represents codes for types of edible substances and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 762766007 Edible Substance (substance). | SNOMED CT |
|
|
|
|
|
| The outcome of the processing. | Internal |
| eligibilityrequest-purpose | A code specifying the types of information being requested. | Internal |
| eligibilityresponse-purpose | A code specifying the types of information being requested. | Internal |
| encounter-admit-source | This value set defines a set of codes that can be used to indicate from where the patient came in. | Other |
| encounter-diet | This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. | Other |
| encounter-discharge-disposition | This value set defines a set of codes that can be used to where the patient left the hospital. | Other |
| encounter-location-status | The status of the location. | Internal |
| encounter-participant-type | This value set defines a set of codes that can be used to indicate how an individual participates in an encounter. | V3, Other |
| encounter-reason | This examples value set defines the set of codes that can be used to indicate reasons for an encounter. | SNOMED CT |
| encounter-special-arrangements | This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit. | Other |
| encounter-special-courtesy | This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. | V3 |
| encounter-status | Current state of the encounter. | Internal |
|
| This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter | Other |
| encounter-type | This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided. | Other |
| endpoint-connection-type | This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values. | Other |
|
| The environment type of the endpoint. | Internal |
| endpoint-payload-type | This is an example value set defined by the FHIR project, that could be used to represent possible payload document types. | Other |
| endpoint-status | The status of the endpoint. | Internal |
|
| The outcome of the processing. | Internal |
| enteral-route | EnteralRouteOfAdministration: Codes specifying the route of administration of enteral formula. This value set is composed of HL7 V3 codes and is provided as a suggestive example. | V3 |
| entformula-additive | EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example. | Other |
| entformula-type | EnteralFormulaType : Codes for type of enteral formula to be administered to patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example. | SNOMED CT |
| episode-of-care-status | The status of the episode of care. | Internal |
| episodeofcare-type | This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record. | Other |
| event-capability-mode N | The mode of a message capability statement. | Internal |
| event-resource-types N |
|
Internal |
| event-status | Codes identifying the lifecycle stage of an event. | Internal |
| event-timing N | Real world event relating to the schedule. | Internal, V3 |
| evidence-classifier-code | Commonly used classifiers for evidence sets. |
|
| evidence-report-section | Evidence Report Section Type. |
|
| evidence-report-type | The kind of report, such as grouping of classifiers, search results, or human-compiled expression. |
|
|
| The event used as a base point (reference point) in time. | Internal |
| ex-benefitcategory | This value set includes examples of Benefit Category codes. | Other |
| ex-diagnosis-on-admission | This value set includes example Diagnosis on Admission codes. | Other |
| ex-diagnosisrelatedgroup | This value set includes example Diagnosis Related Group codes. | Other |
| ex-diagnosistype | This value set includes example Diagnosis Type codes. | Other |
| ex-paymenttype | This value set includes example Payment Type codes. | Other |
| ex-procedure-type | This value set includes example Procedure Type codes. | Other |
| ex-program-code | This value set includes sample Program Reason Span codes. | Other |
| ex-revenue-center | This value set includes sample Revenue Center codes. | Other |
|
|
This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. | LOINC |
|
| A value set that includes all CPT codes | Other |
|
|
This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. | LOINC |
| example-filter | ACME Codes for Cholesterol: Plasma only - demonstrating the use of a filter defined in a CodeSystem | Internal |
|
|
|
|
|
|
This
is
an
example
value
set
that
|
|
|
| This is an example value set that illustrates usage of the metadata resource elements introduced in R5 | Internal |
| examplescenario-actor-type | The type of actor - system or human. | Internal |
|
| Types of resource structures that can be passed in or out of exchange operations. Not necessarily FHIR. | Other, V2 |
| expansion-parameter-source | Description Needed Here | Internal |
| explanationofbenefit-status | A code specifying the state of the resource instance. | Internal |
| expression-language | The media type of the expression language. |
|
| extension-context-type N | How an extension context is interpreted. | Internal |
| feeding-device | Materials used or needed to feed the patient. | Internal, SNOMED CT |
|
|
|
|
| fhirpath-types N | All FHIRPath data types | Internal |
| filter-operator N | The kind of operation to perform as a part of a property based filter. | Internal |
| flag-category | Example list of general categories for flagged issues. (Not complete or necessarily appropriate.) | Other |
| flag-code | Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) | SNOMED CT |
| flag-priority | This value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority. | Internal |
| flag-status | Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error. | Internal |
| fm-status | This value set includes Status codes. | Internal |
| focal-subject | Example value set composed from SNOMED CT and HL7 V3 codes for observation targets such as donor, fetus or spouse. As use cases are discovered, more values may be added. | SNOMED CT, V3 |
| focus-characteristic-code | Evidence focus characteristic code. |
|
| food-type | This value set represents codes for types of foods and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 255620007 (Foods (substance)). | SNOMED CT |
|
|
|
Other |
|
|
|
|
| fundsreserve | This value set includes sample funds reservation type codes. | Other |
|
| The change type of the GenomicStudy analysis. | Internal |
|
|
|
Internal |
|
| The method type of the GenomicStudy analysis. | Internal |
|
|
|
|
|
| The type of the GenomicStudy. | Internal |
| goal-acceptance-status | Description Needed Here | Internal |
| goal-achievement | Describes the progression, or lack thereof, towards the goal against the target. | Other |
| goal-category | Example codes for grouping goals to use for filtering or presentation. | Other |
| goal-priority | Indicates the level of importance associated with reaching or sustaining a goal. | Other |
|
| Description Needed Here | Internal |
| goal-start-event | Identifies types of events that might trigger the start of a goal. | SNOMED CT |
| goal-status | Codes that reflect the current state of a goal and whether the goal is still being targeted. | Internal |
| graph-compartment-rule | How a compartment must be linked. | Internal |
| graph-compartment-use | Defines how a compartment rule is used. | Internal |
|
|
|
Internal |
| group-type | Types of resources that are part of group. | Internal |
|
| Example guidance module codes. | Internal |
| guidance-response-status | The status of a guidance response. | Internal |
| guide-page-generation | A code that indicates how the page is generated. | Internal |
| guide-parameter-code |
|
Internal |
| handling-condition | Set of handling instructions prior testing of the specimen. | Other |
| history-absent-reason | Codes describing the reason why a family member's history is not available. | Other |
| history-status | A code that identifies the status of the family history record. | Internal |
|
| Description Needed Here | Internal |
| http-operations | The allowable request method or HTTP operation codes. | Internal |
| http-verb N | HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details. | Internal |
|
| Link Relation Types defined at https://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 | Internal |
| icd-10 | This value set includes sample ICD-10 codes. | Internal |
| icd-10-procedures | This value set includes sample ICD-10 Procedure codes. | Internal |
| identifier-type N | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | V2 |
| identifier-use N | Identifies the purpose for this identifier, if known . | Internal |
| identity-assuranceLevel | The level of confidence that this link represents the same actual person, based on NIST Authentication Levels. | Internal |
|
| The type of 2D coordinates describing a 2D image region. | Internal |
|
| The type of coordinates describing a 3D image region. | Internal |
| imagingselection-status |
The
status
of
the
|
Internal |
|
| The status of the ImagingStudy. | Internal |
| immunization-evaluation-dose-status | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example. | Other |
| immunization-evaluation-dose-status-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example. | Other |
| immunization-evaluation-status | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the current status of the evaluation for vaccine administration event. |
|
| immunization-function | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the function a practitioner or organization may play in the immunization event. This value set is provided as a suggestive example. | V2 |
| immunization-funding-source | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example. | Other |
| immunization-origin | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the data when the report of the immunization event is not based on information from the person, entity or organization who administered the vaccine. This value set is provided as a suggestive example. | Other |
| immunization-program-eligibility | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's eligibility for a vaccination program. This value set is provided as a suggestive example. | Other |
| immunization-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was administered. This value set is provided as a suggestive example. | SNOMED CT |
| immunization-recommendation-date-criterion | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the definition of dates relevant to recommendations for future doses of vaccines. This value set is provided as a suggestive example. | LOINC |
| immunization-recommendation-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reasons why a given recommendation status is assigned. This value set is provided as a suggestive example and includes SNOMED CT concepts. | SNOMED CT |
| immunization-recommendation-status | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example. | Other |
| immunization-route | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the administrative routes used during vaccination. This value set is provided as a suggestive example. | V3 |
| immunization-site | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the body site where the vaccination occurred. This value set is provided as a suggestive example. | V3 |
| immunization-status | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the current status of the administered dose of vaccine. | Internal |
| immunization-status-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was not administered. This value set is provided as a suggestive example. |
|
| immunization-subpotent-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example. | Other |
| immunization-target-disease |
The
value
set
to
instantiate
this
attribute
should
be
drawn
from
a
terminologically
robust
code
system
that
consists
of
or
contains
concepts
to
support
describing
the
disease
that
the
dose
is
being
administered
against.
This
value
set
is
provided
as
a
suggestive
example
and
includes
|
SNOMED CT |
|
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing programs that a patient may be eligible for to cover vaccine administration costs. This value set is provided as a suggestive example. | LOINC |
| implantStatus | Description Needed Here | Internal |
| inactive | HL7 v3 ActMood Predicate codes, including inactive codes | V3 |
| ingredient-function | A classification of the ingredient identifying its precise purpose(s) in the drug product (beyond e.g. active/inactive). | Internal |
| ingredient-manufacturer-role | The way in which this manufacturer is associated with the ingredient. For example whether it is a possible one (others allowed), or an exclusive authorized one for this ingredient. Note that this is not the manufacturing process role. | Internal |
| ingredient-role | A classification of the ingredient identifying its purpose within the product. | Internal |
|
| Description Needed Here | Internal |
| insuranceplan-applicability | Whether the cost applies to in-network or out-of-network providers. | Other |
| insuranceplan-type | This example value set defines a set of codes that can be used to indicate a type of insurance plan. | Other |
| interactant | An interactant - a substance that may have an clinically significant effect on another. | SNOMED CT |
| interaction-effect | A interaction effect of clinical use of a medication or other substance. | SNOMED CT |
| interaction-incidence | A categorisation for incidence of occurence of an interaction. | Internal |
| interaction-management | A type of management for an interaction of a medication or other substance. | SNOMED CT |
| interaction-trigger | FHIR RESTful interaction codes used for SubscriptionTopic trigger. | Internal |
| interaction-type | A categorisation for an interaction between two substances. | Internal |
|
|
|
|
|
|
|
Internal |
| invoice-status | Codes identifying the lifecycle stage of an Invoice. | Internal |
| iso3166-1-2 | This value set defines the ISO 3166 Part 1 2-letter codes | Other |
| iso3166-1-3 | This value set defines the ISO 3166 Part 1 3-letter codes | Other |
| iso3166-1-N | This value set defines the ISO 3166 Part 1 Numeric codes | Other |
| issue-severity N | How the issue affects the success of the action. | Internal |
| issue-type N | A code that describes the type of issue. | Internal |
| item-type | Distinguishes groups from questions and display text and indicates data type for questions. | Internal |
| jurisdiction N | This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used. Note: The codes for countries and country subdivisions are taken from [ISO 3166](https://www.iso.org/iso-3166-country-codes.html) while the codes for "supra-national" regions are from [UN Standard country or area codes for statistical use (M49)](http://unstats.un.org/unsd/methods/m49/m49.htm). | Other |
|
|
A
|
Internal |
|
| A knowledge representation level, narrative, semi-structured, structured, and executable | Internal |
| language-preference-type | This value set defines the set of codes for describing the type or mode of the patient's preferred language. | Internal |
| languages | This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) | Other |
| legal-status-of-supply | The prescription supply types appropriate to a medicinal product | Internal |
| library-type | The type of knowledge asset this library contains. | Other |
| link-type N | The type of link between this patient resource and another patient resource. | Internal |
| linkage-type | Used to distinguish different roles a resource can play within a set of linked resources. | Internal |
| lipid-ldl-codes | LDL Cholesterol codes - measured or calculated | LOINC |
| list-empty-reason | General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list). | Other |
| list-example-codes | Example use codes for the List resource - typical kinds of use. | Other |
| list-item-flag | Example Item Flags for the List Resource. In this case, these are the kind of flags that would be used on a medication list at the end of a consultation. | Other |
| list-mode | The processing mode that applies to this list. | Internal |
| list-order | Base values for the order of the items in a list resource. | Other |
| list-status | The current state of the list. | Internal |
|
|
|
Internal |
|
|
This example value set defines a set of codes that can be used to indicate the physical form of the Location. | Other |
|
| Indicates whether a resource instance represents a specific location or a class of locations. | Internal |
| location-status | Indicates whether the location is still in use. | Internal |
| manifestation-or-symptom | Example value set for Manifestation and Symptom codes. | SNOMED CT |
|
|
|
Internal |
| map-group-type-mode | If this is the default rule set to apply for the source type, or this combination of types. | Internal |
| map-input-mode | Mode for this instance of data. | Internal |
| map-model-mode | How the referenced structure is used in this mapping. | Internal |
| map-source-list-mode | If field is a list, how to manage the source. | Internal |
| map-target-list-mode | If field is a list, how to manage the production. | Internal |
| map-transform | How data is copied/created. | Internal |
| marital-status N | This value set defines the set of codes that can be used to indicate the marital status of a person. | V3 |
|
| Description Needed Here | Internal |
| measure-aggregate-method | Aggregation method for a measure (e.g. sum, average, median, minimum, maximum, count) | Internal |
| measure-data-usage | The intended usage for supplemental data elements in the measure. | Other |
| measure-definition-example |
| Internal |
| measure-group-example | Example Measure Groups for the Measure Resource. |
|
| measure-improvement-notation | Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue. | Other |
| measure-population | The type of population. | Other |
| measure-report-status | The status of the measure report. | Internal |
| measure-report-type | The type of the measure report. | Internal |
| measure-scoring | The scoring type of the measure. | Other |
|
| This is an example value set illustrating some typical scoring units used in quality measure specifications. | FHIR |
| measure-stratifier-example | Identifier subgroups in a population for measuring purposes. |
|
| measure-supplemental-data-example | Supplemental data in a population for measuring purposes. |
|
| measure-type | The type of measure (includes codes from 2.16.840.1.113883.1.11.20368). | Other |
| measurement-property | This value set represents codes for properties that can be measured and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept has a parent of 118598001 Property of measurement (qualifier value). | SNOMED CT |
| measurereport-stratifier-value-example | Example Measure Stratification Value for MeasureReports Resource. |
|
| med-admin-perform-function | MedicationAdministration Performer Function Codes | Other |
|
|
MedicationAdministration
|
Other |
| medication-admin-status | MedicationAdministration Status Codes |
|
| medication-as-needed-reason | This value set includes all clinical findings from SNOMED CT - provided as an exemplar value set. | SNOMED CT |
| medication-codes | This value set includes all drug or medicament substance codes and all pharmaceutical/biologic products from SNOMED CT - provided as an exemplar value set. | SNOMED CT |
|
| Medication Cost Category Codes | Internal |
| medication-dose-aid | Medication Dose Aids | Internal |
| medication-form-codes | This value set includes all dose form codes from SNOMED CT - provided as an exemplar. | SNOMED CT |
|
|
Medication
|
|
|
|
|
Internal |
| medication-status | Medication Status Codes | Internal |
|
|
|
|
|
| MedicationUsage Status Codes | Internal |
|
|
MedicationDispense
|
|
|
|
MedicationDispense
|
Other |
|
|
MedicationDispense Status Codes |
|
|
|
|
|
|
|
MedicationKnowledge
|
Other |
| medicationknowledge-status | MedicationKnowledge Status Codes |
|
|
|
MedicationRequest
|
Other |
| medicationrequest-course-of-therapy | MedicationRequest Course of Therapy Codes | Other |
| medicationrequest-intent | MedicationRequest Intent Codes | Internal |
| medicationrequest-status | MedicationRequest Status Codes | Internal |
| medicationrequest-status-reason | MedicationRequest Status Reason Codes | Other |
| medicinal-product-additional-monitoring | Extra monitoring defined for a Medicinal Product. | Internal |
|
| This value set includes codes from the Anatomical Therapeutic Chemical Classification System - provided as an exemplar value set. | Other |
| medicinal-product-confidentiality | Confidentiality rating, e.g. commercial sensitivity for a Medicinal Product. | Internal |
| medicinal-product-contact-type | Contact type for a Medicinal Product. | Internal |
| medicinal-product-cross-reference-type | Relationship to another Medicinal Product. | Internal |
| medicinal-product-domain | Applicable domain for this product (e.g. human, veterinary) | Internal |
| medicinal-product-name-part-type | Type of part of a name for a Medicinal Product. | Internal |
| medicinal-product-name-type | Type of a name for a Medicinal Product. | Internal |
| medicinal-product-package-type | Types of medicinal product packs | Internal |
| medicinal-product-pediatric-use | Extra measures defined for a Medicinal Product, such as heightened reporting requirements. | Internal |
| medicinal-product-special-measures | Extra measures defined for a Medicinal Product, such as a requirement to conduct post-authorisation studies. | Internal |
| medicinal-product-type | Overall defining type of this Medicinal Product. | Internal |
| message-events | One of the message events defined as part of this version of FHIR. | Internal |
| message-reason-encounter | Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. | Other |
| message-significance-category | The impact of the content of a message. | Internal |
| message-transport N | The protocol used for message transport. |
|
| messageheader-response-request | HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message. | Internal |
| metric-calibration-state | Describes the state of a metric calibration. | Internal |
| metric-calibration-type | Describes the type of a metric calibration. | Internal |
| metric-category | Describes the category of the metric. | Internal |
| metric-color | Describes the typical color of representation. | Internal |
| metric-operational-status | Describes the operational status of the DeviceMetric. | Internal |
| mimetypes N | This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13) | Other |
| missing-tooth-reason | This value set includes sample Missing Tooth Reason codes. | Other |
| modified-foodtype | TextureModifiedFoodType: Codes for types of foods that are texture-modified. This value set is composed SNOMED CT Concepts from SCTID 255620007 Foods (substance) and is provided as a suggestive example. | SNOMED CT |
| name-assembly-order | A code that represents the preferred display order of the components of a human name. | Other, V2, V3 |
| name-part-qualifier | A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. | V3 |
| name-use N | The use of a human name. | Internal |
| name-v3-representation | A set of codes for each different representation of a name. | V3 |
|
| Identifies the style of unique identifier used to identify a namespace. | V2 |
| namingsystem-identifier-type | Identifies the style of unique identifier used to identify a namespace. | Internal |
| namingsystem-type | Identifies the purpose of the naming system. | Internal |
| narrative-status | The status of a resource narrative. | Internal |
| nhin-purposeofuse | This value set is suitable for use with the provenance resource. It is derived from, but not compatible with, the HL7 v3 Purpose of use Code system. | Other |
|
| This value set represents codes for types of edible substances and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 762766007 Edible Substance (substance). | SNOMED CT |
| note-type | The presentation types of notes. | Internal |
| nutrient-code | NutrientModifier : Codes for types of nutrients that are being modified such as carbohydrate or sodium. This value set includes codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 226355009 (Nutrients(substance)), and the concepts for Sodium, Potassium and Fluid. This is provided as a suggestive example. | SNOMED CT |
| nutrition-product-category |
This
value
set
represents
codes
for
types
of
edible
substances
and
is
provided
as
a
suggestive
example.
It
include
codes
from
[SNOMED
CT](http://snomed.info/sct)
where
concept
has
a
parent
of
|
SNOMED CT |
| nutrition-product-nutrient | This value set represents codes for food nutrients and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept has a parent of 226355009 Nutrients (substance). | SNOMED CT |
| nutritionproduct-status | Codes identifying the lifecycle stage of a product. | Internal |
| object-lifecycle-events |
This
|
Other |
| object-role | Code representing the role the entity played in the audit event. | Other |
|
| Obligation Codes | Internal |
| observation-category | Observation Category codes. | Other |
| observation-codes | This value set includes all LOINC codes | LOINC |
| observation-interpretation N | A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8 (Observation Interpretation), in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR in Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. | V3 |
| observation-methods | Observation Method codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 272394005 (Technique (qualifier value)) or is-a 129264002 (Action (qualifier value)) or is-a 386053000 (Evaluation procedure(procedure)) | SNOMED CT |
| observation-range-category | Codes identifying the category of observation range. | Internal |
|
|
Codes
|
Internal |
|
| Description Needed Here | Internal |
| observation-status N | Codes providing the status of an observation. | Internal |
|
| Codes providing the type of triggeredBy observation. | Internal |
| observation-vitalsignresult | This value set indicates the allowed vital sign result types. The LOINC code for Vitals Signs panel (85353-1) is a grouping structure for a set of vital signs and includes related links (with type=has-member) to the Observations in this set (e.g. respiratory rate, heart rate, BP). The Blood pressure panel (85354-9) is used to group the component observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4). | LOINC |
| operation-kind N | Whether an operation is a normal operation or a query. | Internal |
|
| Operation Outcome codes for translatable phrases used by FHIR test servers (see Implementation file translations.xml) | Internal |
| operation-parameter-scope N | Indicates that a parameter applies when the operation is being invoked at the specified level | Internal |
| operation-parameter-use N | Whether an operation parameter is an input or an output parameter. | Internal |
| organization-role | This example value set defines a set of codes that can be used to indicate the role of one Organization in relation to another. | Internal |
| organization-type | This example value set defines a set of codes that can be used to indicate a type of organization. | Other |
| orientation-type | Type for orientation. | Internal |
| package-material | A material used in the construction of packages and their components. | Internal |
| package-type | A high level categorisation of a package. | Internal |
| packaging-type | A type of packaging. | Internal |
| parent-relationship-codes | The value set includes the v3 RoleCode PRN (parent), TWIN (twin) and all of their specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. | V3 |
|
|
|
Internal |
|
| Roles of participants that may be included in a care team. Defined as: Healthcare professional (occupation) or Services (qualifier value). | SNOMED CT |
| participation-role-type |
This
FHIR
value
set
is
comprised
of
Actor
participation
Type
codes,
which
can
be
used
to
value
FHIR
agents,
actors,
and
other
role
elements.
The
|
Other,
|
| participationstatus | The Participation status of an appointment. | Internal |
| patient-contactrelationship N | The nature of the relationship between the patient and the contact person. | V2 |
| payeetype | This value set includes sample Payee Type codes. | Other |
| payment-adjustment-reason | This value set includes smattering of Payment Adjustment Reason codes. | Other |
|
| The type of payment issuer. | Internal |
| payment-kind | The type of workflow from which this payment arose. | Internal |
| payment-outcome | The outcome of the processing. | Internal |
| payment-status | This value set includes a sample set of Payment Status codes. | Other |
| payment-type | This value set includes sample Payment Type codes. | Other |
| performer-function | The types of involvement of the performer in the Event. | V3 |
| performer-role | This example value set defines the set of codes that can be used to indicate a role of a procedure performer. | SNOMED CT |
|
| Codes identifying rule combining algorithm. | Internal |
| permission-status | Codes identifying the lifecycle stage of a product. | Internal |
| permitted-data-type | Permitted data type for observation value. | Internal |
| plan-definition-type | The type of PlanDefinition. | Other |
| postal-address-use | Uses of an address not included in Address.use. | V3 |
|
| This example value set defines a set of sample job titles. | Internal |
| practitioner-role | This example value set defines a set of codes that can be used to indicate the role of a Practitioner. | Other, SNOMED CT |
| prepare-patient-prior-specimen-collection | Checks on the patient prior specimen collection. All SNOMED CT concepts descendants of 703763000 |Precondition value (qualifier value)| | SNOMED CT |
|
| Codes indicating the kind of the price component. | Internal |
| probability-distribution-type | Codes specifying the type of probability distribution. | V3 |
| procedure-category | Procedure Category code: A selection of relevant SNOMED CT codes. | SNOMED CT |
| procedure-code | Procedure Code: All SNOMED CT procedure codes. | SNOMED CT |
| procedure-followup | Procedure follow up codes: A selection of SNOMED CT codes relevant to procedure follow up. | SNOMED CT |
| procedure-not-performed-reason |
Situation
codes
describing
the
reason
that
a
procedure,
which
might
otherwise
be
expected,
was
not
performed,
or
a
procedure
that
was
started
and
was
not
completed.
Consists
of
SNOMED
CT
codes,
children
of
procedure
contraindicated
(183932001),
procedure
discontinued
(416406003),
procedure
not
done
(416237000),
procedure
not
indicated
(428119001),
procedure
not
offered
(416064006),
procedure
not
wanted
(416432009),
procedure
refused
(183944003),
and
procedure
stopped
|
SNOMED CT |
| procedure-outcome | Procedure Outcome code: A selection of relevant SNOMED CT codes. | SNOMED CT |
| procedure-progress-status-codes | This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the procedure performance process. | Internal |
| procedure-reason | This example value set defines the set of codes that can be used to indicate a reason for a procedure. | SNOMED CT |
| process-priority | This value set includes the financial processing priority codes. | Other |
| product-category | Biologically Derived Product Category. | Internal |
|
|
|
|
|
|
|
Internal |
|
|
|
Internal |
| program | This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties. | Other |
| property-representation N | How a property is represented when serialized. | Internal |
|
|
|
|
|
|
|
Other |
| provenance-entity-role | How an entity was used in an activity. | Internal |
| provenance-history-agent-type | Types of roles indicating how a particular agent was involved with the creation or modification of a resource for use when exposing event history | V3 |
| provenance-history-record-activity | Codes for Provenance activities that are relevant when capturing event history for resources. | V3 |
| provider-qualification | This value set includes sample Provider Qualification codes. | Other |
| provider-taxonomy | NUCC Healthcare Provider Taxonomy codes | Other |
| publication-status N | The lifecycle status of an artifact. | Internal |
| published-in-type | The type of publication such as book, database, or journal. |
|
| quantity-comparator N | How the Quantity should be understood and represented. | Internal |
|
| Codes that describe the types of constraints possible on a question item that has a list of permitted answers | Internal |
| questionnaire-answers | Example list of codes for answers to questions. (Not complete or necessarily appropriate.) | SNOMED CT |
| questionnaire-answers-status | Lifecycle status of the questionnaire response. | Internal |
|
| Codes that guide the display of disabled questionnaire items | Internal |
| questionnaire-display-category |
Codes
defining
the
purpose
of
a
Questionnaire
item
of
type
|
Internal |
| questionnaire-enable-behavior | Controls how multiple enableWhen values are interpreted - whether all or any must be true. | Internal |
| questionnaire-enable-operator | The criteria by which a question is enabled. | Internal |
| questionnaire-item-control | Starter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire. | Internal |
| questionnaire-questions | Example list of codes for questions and groups of questions. (Not necessarily complete or appropriate.) | LOINC |
|
| Description Needed Here | Internal |
| questionnaireresponse-mode | Codes describing how the QuestionnaireResponse was populated | V3 |
| reaction-event-certainty |
|
Internal |
| reaction-event-severity | Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. | Internal |
| reason-medication-given-codes | This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process. | Other |
| reason-medication-not-given-codes | This value set includes all medication refused, medication not administered, and non-administration of necessary drug or medicine codes from SNOMED CT - provided as an exemplar value set. | SNOMED CT |
| reason-medication-status-codes | This value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplar | SNOMED CT |
| reference-handling-policy N | A set of flags that defines how references are supported. | Internal |
| reference-version-rules N | Whether a reference needs to be version specific or version independent, or whether either can be used. | Internal |
|
| This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Made up of a set of non-healthcare specific codes and all LOINC codes where scale type = 'DOC'. | Other, LOINC |
| referencerange-appliesto | This value set defines a set of codes that can be used to indicate the particular target population the reference range applies to. | Other, SNOMED CT |
| referencerange-meaning | This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population. | Other |
| regulated-authorization-basis | A legal or regulatory framework against which an authorization is granted, or other reasons for it. | Internal |
| regulated-authorization-case-type | The type of a case involved in an application. | Internal |
| regulated-authorization-type | Overall type of this authorization. | Internal |
| rejection-criteria | Criterion for rejection of the specimen by laboratory. | Other |
| related-artifact-type | The type of relationship to the related artifact. | Internal |
|
| The type of relationship to the cited artifact. | Internal |
| related-claim-relationship | This value set includes sample Related Claim Relationship codes. | Other |
| relatedperson-relationshiptype | A set of codes that can be used to indicate the relationship between a Patient and a Related Person. | V2, V3 |
| relationship | This value set includes the Patient to subscriber relationship codes. | Internal |
| remittance-outcome | The outcome of the processing. | Internal |
| report-action-result-codes | The results of executing an action. | Internal |
| report-codes | This value set includes LOINC codes that relate to Diagnostic Observations. | LOINC |
| report-participant-type | The type of participant. | Internal |
| report-relation-type | The type of relationship between reports. | Internal |
| report-result-codes | The reported execution result. | Internal |
| report-status-codes | The current status of the test report. | Internal |
| request-intent | Codes indicating the degree of authority/intentionality associated with a request. | Internal |
| request-priority | Identifies the level of importance to be assigned to actioning the request. | Internal |
| request-resource-types N |
|
Internal |
| request-status | Codes identifying the lifecycle stage of a request. | Internal |
|
| Codes for the main intent of the study. | Internal |
|
|
|
Internal |
|
| Codes for the main intent of the study. | Internal |
| research-study-objective-type | Codes for the kind of study objective. |
|
|
| This is a ResearchStudy's party organization type. | Internal |
| research-study-party-role | This is a ResearchStudy's party role. | Internal |
| research-study-phase | Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation. |
|
| research-study-prim-purp-type | Codes for the main intent of the study. |
|
| research-study-reason-stopped | Codes for why the study ended prematurely. |
|
|
| Codes for study registration activities. | Internal |
| research-study-status | Codes that convey the current status of the research study. | Internal |
|
| Indicates the progression of a study subject through the study milestones. | Other |
|
|
Indicates the progression of a study subject through a study. |
|
|
| Identifies the kind of state being refered to. | Other |
| resource-aggregation-mode N | How resource references can be aggregated. | Internal |
| resource-security-category |
|
Internal |
| resource-slicing-rules N | How slices are interpreted when evaluating an instance. | Internal |
| resource-status | The master set of status codes used throughout FHIR. All status codes are mapped to one of these codes. | Internal |
| resource-types N |
|
Internal |
| resource-validation-mode |
|
Internal |
| response-code | The kind of response to a message. | Internal |
| restful-capability-mode N | The mode of a RESTful capability statement. | Internal |
| restful-security-service N | Types of security services used with FHIR. |
|
| risk-probability | Codes representing the likelihood of a particular outcome in a risk assessment. | Other |
| route-codes | This value set includes all Route codes from SNOMED CT - provided as an exemplar. | SNOMED CT |
| search-comparator | What Search Comparator Codes are supported in search. | Internal |
| search-entry-mode N | Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. | Internal |
| search-modifier-code | A supported modifier for a search parameter. | Internal |
| search-param-type N | Data types allowed to be used for search parameters. | Internal |
|
|
How
a
search
parameter
relates
to
the
set
of
elements
returned
by
evaluating
its
|
Internal |
| secondary-finding |
Codes
to
denote
a
guideline
or
policy
|
Internal |
|
|
A
|
|
|
|
| V3 |
| security-label-examples |
A
sample
of
|
|
|
|
|
Other |
|
|
This
value
set
|
Other |
|
|
|
Other |
| sequence-type | Type if a sequence -- DNA, RNA, or amino acid sequence. | Internal |
| series-performer-function | Performer function of an agent in an imaging study series | V3 |
| service-category | This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. | Other |
| service-place | This value set includes a smattering of Service Place codes. | Other |
| service-provision-conditions | The code(s) that detail the conditions under which the healthcare service is available/offered. | Other |
| service-referral-method | The methods of referral can be used when referring to a specific HealthCareService resource. | Other |
| service-type | This value set defines an example set of codes of service-types. | Other |
| service-uscls | This value set includes a smattering of USCLS codes. | Other |
| servicerequest-category | An example value set of SNOMED CT concepts that can classify a requested service | SNOMED CT |
| servicerequest-orderdetail | An example value set of Codified order entry details concepts. These concepts only make sense in the context of what is being ordered. This example is for a patient ventilation order | SNOMED CT |
| sibling-relationship-codes | The value set includes the v3 RoleCode SIB (sibling) and all of its specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. | V3 |
| signature-type | The Digital Signature Purposes, an indication of the reason an entity signs a document. This is included in the signed information and can be used when determining accountability for various actions concerning the document. Examples include: author, transcriptionist/recorder, and witness. | Other |
| slotstatus | The free/busy status of the slot. | Internal |
| sort-direction | The possible sort directions, ascending or descending. | Internal |
| spdx-license | The license that applies to an Implementation Guide (using an SPDX license Identifiers, or 'not-open-source'). The binding is required but new SPDX license Identifiers are allowed to be used (https://spdx.org/licenses/). | Internal |
| specimen-collection | Actions that can be taken for the collection of specimen from a subject. | SNOMED CT |
| specimen-collection-method | This example value set defines a set of codes that can be used to indicate the method by which a specimen was collected. | SNOMED CT |
| specimen-collection-priority | This example value set defines a set of codes that can be used to indicate the priority of collection of a specimen. | Other |
|
| Codes providing the combined status of a specimen. | Internal |
| specimen-contained-preference | Degree of preference of a type of conditioned specimen. | Internal |
| specimen-container-type |
|
SNOMED CT |
|
|
The technique that is used to perform the process or preserve the specimen. | V2 |
|
| Codes providing the role of a specimen. | Internal |
| specimen-status | Codes providing the status/availability of a specimen. | Internal |
| standards-status |
|
Internal |
|
| Indicates why the state of the subject changed. | Other |
| statistic-model-code | The handling of the variable in statistical analysis for exposures or outcomes. |
|
| statistic-type | The type of a statistic, e.g. relative risk or mean | Other |
| strand-type | Type for strand. | Internal |
| structure-definition-kind N | Defines the type of structure that a definition is describing. | Internal |
|
|
|
|
|
|
|
Internal |
| subscriber-relationship | This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient). | Other |
| subscription-channel-type |
|
|
| subscription-error | Codes to represent subscription error details | Other |
| subscription-notification-type | The type of notification represented by the status message. | Internal |
|
| Codes to represent how much resource content to send in the notification payload. | Internal |
| subscription-search-modifier | FHIR search modifiers allowed for use in Subscriptions and SubscriptionTopics. |
|
| subscription-status |
|
Internal |
| subscriptiontopic-cr-behavior | Behavior a server can exhibit when a criteria state does not exist (e.g., state prior to a create or after a delete). | Internal |
| substance-amount-type | The relationship between two substance types. | Internal |
| substance-category | Substance category codes | Other |
| substance-code | This value set contains concept codes for specific substances. It includes codes from [SNOMED](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) | SNOMED CT |
|
| This value set includes all substance codes from SNOMED CT - provided as an exemplar value set. | SNOMED CT |
| substance-form | The substance form, whether it is the base form or a salt. | Internal |
| substance-grade | The quality standard, established benchmark, to which a substance complies. | Internal |
| substance-name-authority | An authority that officates substance names. | Internal |
| substance-name-domain | The use context of a substance name for example if there is a different name when used as a drug active ingredient as opposed to a food colour additive. | Internal |
| substance-name-type | The type of a name given to a substance. | Internal |
| substance-optical-activity | The optical rotation type of a substance. | Internal |
| substance-relationship-type | The relationship between two substance types. | Internal |
| substance-representation-format | A format of a substance representation. | Internal |
| substance-representation-type | The type of a name given to a substance. | Internal |
| substance-source-material-genus | The genus of an organism, typically referring to the Latin epithet of the genus element of the plant/animal scientific name. | Internal |
| substance-source-material-part | An anatomical origin of the source material within an organism. | Internal |
| substance-source-material-species | A species of origin a substance raw material. | Internal |
| substance-source-material-type | A classification that provides the origin of the substance raw material. | Internal |
| substance-status | A code to indicate if the substance is actively used. | Internal |
| substance-stereochemistry | The optical rotation type of a substance. | Internal |
| substance-structure-technique | The method used to elucidate the structure or characterization of the drug substance. | Internal |
| substance-weight-method | The method by which the substance weight was measured. | Internal |
| substance-weight-type | The type of substance weight measurement. | Internal |
| supplement-type | SupplementType : Codes for nutritional supplements to be provided to the patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example. | SNOMED CT |
| supply-item | This value set includes [SNOMED CT](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) or concept is-a 260787004 (Physical object) and provided as an example value set. | SNOMED CT |
| supplydelivery-status | Status of the supply delivery. | Internal |
|
|
This value sets refers to a specific supply item. |
|
| supplyrequest-kind | This value sets refers to a Category of supply. | Other |
| supplyrequest-reason | The reason why the supply item was requested. | Other |
| supplyrequest-status | Status of the supply request. | Internal |
| surface | This value set includes a smattering of FDI tooth surface codes. | Other |
| synthesis-type | Types of combining results from a body of evidence (eg. summary data meta-analysis). | Other |
| system-restful-interaction N | Operations supported by REST at the system level. | Internal |
| target-species | A species for which a medicinal product is intended. | Internal |
| task-code | Codes indicating the type of action that is expected to be performed | Internal |
| task-intent | Distinguishes whether the task is a proposal, plan or full order. | Internal |
| task-status | The current status of the task. | Internal |
|
|
The
current
status
|
|
|
| Description Needed Here | Internal |
| testscript-operation-codes | This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. |
|
| testscript-profile-destination-types | This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript. | Other |
| testscript-profile-origin-types | This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript. | Other |
|
| The expectation of whether the test must pass for the system to be considered conformant with the artifact. | Internal |
| testscript-scope-phase-codes | The phase of testing for this artifact. | Internal |
| texture-code | TextureModifier: Codes for food consistency types or texture modifications to apply to foods. This value set is composed of SNOMED CT (US Extension and Core) Concepts from SCTID 229961002 Food consistency types (substance) hierarchy and is provided as a suggestive example. | SNOMED CT |
| therapy | A therapy. | SNOMED CT |
| therapy-relationship-type | Classification of relationship between a therapy and a contraindication or an indication. | Internal |
| timezones |
An
IANA
|
Other |
| timing-abbreviation | Code for a known / defined timing pattern. | Other, V3 |
| title-type | Used to express the reason and specific aspect for the variant title, such as language and specific language. |
|
| tooth | This value set includes a smattering of FDI oral site codes. | Other |
|
| Codes indicating the type of action that is expected to be performed | Internal |
| transport-intent | Distinguishes whether the transport is a proposal, plan or full order. | Internal |
| transport-status | Status of the transport | Internal |
| transport-status-reason | Status reason of the transport. | Internal |
| trigger-type | The type of trigger. | Internal |
|
| Description Needed Here | Internal |
| type-derivation-rule N | How a type relates to its baseDefinition. | Internal |
| type-restful-interaction N | Operations supported by REST at the type or instance level. | Internal |
| ucum-bodylength | UCUM units for recording body length measures such as height and head circumference | FHIR |
| ucum-bodytemp | UCUM units for recording Body Temperature | FHIR |
| ucum-bodyweight | UCUM units for recording Body Weight | FHIR |
| ucum-common | Commonly encountered UCUM units (for purposes of helping populate look ups). | FHIR |
| ucum-units | Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes | FHIR |
| ucum-vitals-common | Common UCUM units for recording Vital Signs | FHIR |
| udi-entry-type | Codes to identify how UDI data was entered. | Internal |
| undesirable-effect-classification | A categorisation for an undesirable effect. | SNOMED CT |
| undesirable-effect-frequency | A categorisation for a frequency of occurence of an undesirable effect. | Internal |
| undesirable-effect-symptom | An undesirable effect of clinical use. | SNOMED CT |
| unit-of-presentation | The presentation type in which an administrable medicinal product is given to a patient. | Internal |
| units-of-time N | A unit of time (units from UCUM). | FHIR |
|
| Codes for use in UsageContext.valueCodeableConcept when UsageContext.code is agreement-scope | Internal |
| usage-context-type | A code that specifies a type of context being specified by a usage context. | Other |
| use-context | This value set defines a base set of codes that can be used to indicate that the content in a resource was developed with a focus and intent of supporting use within particular contexts. | Other, SNOMED CT |
| vaccine-code | This identifies the vaccine substance administered - CVX codes. | Internal, Other |
|
| The type of comparator operator to use | Internal |
| variable-handling | The handling of the variable in statistical analysis for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive). | Internal |
| variable-role | The role that the assertion variable plays. | Other |
| verificationresult-can-push-updates | Ability of the primary source to push updates/alerts | Other |
| verificationresult-communication-method | Attested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated. | Other |
| verificationresult-failure-action | The result if validation fails | Other |
| verificationresult-need | The frequency with which the target must be validated | Other |
| verificationresult-primary-source-type | Type of the validation primary source | Other |
| verificationresult-push-type-available | Type of alerts/updates the primary source can send | Other |
| verificationresult-status | The validation status of the target | Internal |
| verificationresult-validation-process | The primary process by which the target is validated | Other |
| verificationresult-validation-status | Status of the validation of the target against the primary source | Other |
| verificationresult-validation-type | What the target is validated against | Other |
|
| Indicates the mechanism used to compare versions to determine which is more current. | Internal |
| versioning-policy N | How the system supports versioning for a resource. | Internal |
|
| Example codes for possible virtual service connection types. | Internal |
| vision-base-codes | A coded concept listing the base codes. | Internal |
| vision-eye-codes | A coded concept listing the eye codes. | Internal |
| vision-product | This value set includes a smattering of Prescription Product codes. | Other |
| warning-type | Classification of warning type. | Internal |
|
| The set of weeks in a month. | Internal |
| written-language | This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) for the purpose of writing; this value set (unlike the common languages value set) doesn't include dialects except where they are relevant for written languages | Other |
| yesnodontknow | For Capturing simple yes-no-don't know answers | Other |
| Namespace: http://terminology.hl7.org/ValueSet | ||
|
| Concepts that describe whether a condition is present when a patient is admitted to a healthcare facility. | Other |
|
action-participant-role
| Either a practitioner role or a relationship type. Note from UTG import - may have been a temporary entry that subsequently disappeared from the FHIR source; unable to locate. Version set to 0.1.0 | Other |
|
action-type
| The type of action to be performed. | Other |
|
activity-definition-category
| High-level categorization of the type of activity. | Other |
|
adjudication
| This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc. | Other |
|
adjudication-error
| This value set includes a smattering of adjudication codes. | Other |
|
adjudication-reason
| This value set includes smattering of Adjudication Reason codes. | Other |
|
adverse-event-category
| Overall categorization of the event, e.g. product-related or situational. | Other |
|
adverse-event-causality-assess
| Codes for the assessment of whether the entity caused the event. | Other |
|
adverse-event-causality-method
| TODO. | Other |
|
adverse-event-seriousness
| Overall seriousness of this event for the patient. | Other |
|
adverse-event-severity
| The severity of the adverse event itself, in direct relation to the subject. | Other |
|
allerg-intol-substance-exp-risk
| The risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products). | Other |
|
allergyintolerance-clinical
| Preferred value set for AllergyIntolerance Clinical Status. | Other |
|
allergyintolerance-verification
| The verification status to support or decline the clinical status of the allergy or intolerance. | Other |
|
appointment-cancellation-reason
| This example value set defines a set of reasons for the cancellation of an appointment. | Other |
|
attribute-estimate-type
| Method of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation. | Other |
|
audit-event-outcome
| The type of process where the audit event originated from. | Other |
|
audit-source-type
| The type of process where the audit event originated from. | Other |
|
basic-resource-type
| This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. | Other |
|
benefit-network
| This value set includes a smattering of Network type codes. | Other |
|
benefit-term
| This value set includes a smattering of Benefit Term codes. | Other |
|
benefit-type
| This value set includes a smattering of Benefit type codes. | Other |
|
benefit-unit
| This value set includes a smattering of Unit type codes. | Other |
|
catalogType
| The type of catalog. | Other |
|
certainty-rating
| The relative quality of the statistic. | Other |
|
certainty-subcomponent-rating
| The quality rating of the subcomponent of a quality of evidence rating. | Other |
|
certainty-subcomponent-type
| The subcomponent classification of quality of evidence rating systems. | Other |
|
characteristic-method
| The method used to determine the characteristic(s) of the variable. | Other |
|
chargeitem-billingcodes
| Example set of codes that can be used for billing purposes. | Other |
|
choice-list-orientation
| Direction in which lists of possible answers should be displayed. | Other |
|
chromosome-human
| Chromosome number for human. | Other |
|
claim-careteamrole
| This value set includes sample Claim Care Team Role codes. | Other |
|
claim-exception
| This value set includes sample Exception codes. | Other |
|
claim-informationcategory
| This value set includes sample Information Category codes. | Other |
|
claim-modifiers
| This value set includes sample Modifier type codes. | Other |
|
claim-subtype
| This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation. | Other |
|
claim-type
| This value set includes Claim Type codes. | Other |
|
codesystem-altcode-kind
| Indicates the type of use for which the code is defined. | Other |
|
common-tags
| Common Tag Codes defined by FHIR project | Other |
|
communication-category
| Codes for general categories of communications such as alerts, instructions, etc. | Other |
|
communication-not-done-reason
| Codes for the reason why a communication did not happen. | Other |
|
communication-topic
| Codes describing the purpose or content of the communication. | Other |
|
composite-measure-scoring
| The composite scoring method of the measure. | Other |
|
composition-altcode-kind
| Indicates the type of use for which the code is defined. | Other |
|
condition-category
| Preferred value set for Condition Categories. | Other |
|
condition-clinical
| Preferred value set for Condition Clinical Status. | Other |
|
condition-state
| Enumeration indicating whether the condition is currently active, inactive, or has been resolved. | Other |
|
condition-ver-status
| The verification status to support or decline the clinical status of the condition or diagnosis. | Other |
|
conformance-expectation
| Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification. | Other |
|
consent-action
| This value set includes sample Consent Action codes. | Other |
|
consent-policy
| This value set includes sample Regulatory consent policy types from the US and other regions. | Other |
|
consent-scope
| This value set includes the four Consent scope codes. | Other |
|
consent-verification
| This value set includes base Consent Verification codes. | Other |
|
contactentity-type
| This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party. | Other |
|
container-cap
| Color of the container cap. | Other |
|
contract-action
| This value set includes sample Contract Action codes. | Other |
|
contract-actorrole
| This value set includes sample Contract Actor Role codes. | Other |
|
contract-content-derivative
| This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses. | Other |
|
contract-data-meaning
| How a resource reference is interpreted when evaluating contract offers. | Other |
|
contract-signer-type
| This value set includes sample Contract Signer Type codes. | Other |
|
contract-subtype
| This value set includes sample Contract Subtype codes. | Other |
|
contract-term-subtype
| This value set includes sample Contract Term SubType codes. | Other |
|
contract-term-type
| This value set includes sample Contract Term Type codes. | Other |
|
contract-type
| This value set includes sample Contract Type codes. | Other |
|
copy-number-event
| Copy Number Event. | Other |
|
coverage-class
| This value set includes Coverage Class codes. | Other |
|
coverage-copay-type
| This value set includes sample Coverage Copayment Type codes. | Other |
|
coverage-financial-exception
| This value set includes Example Coverage Financial Exception Codes. | Other |
|
coverage-selfpay
| This value set includes Coverage SelfPay codes. | Other |
|
coverageeligibilityresponse-ex-auth-support
| This value set includes CoverageEligibilityResponse Auth Support codes. | Other |
|
definition-status
| Codes identifying the lifecycle stage of a definition. | Other |
|
definition-topic
| High-level categorization of the definition, used for searching, sorting, and filtering. | Other |
|
definition-use
| Structure Definition Use Codes / Keywords | Other |
|
device-kind
| Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example. | SNOMED CT |
|
device-status-reason
| The availability status reason of the device. | Other |
|
diagnosis-role
| This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record. | Other |
|
directness
| The quality of how direct the match is. | Other |
|
dose-rate-type
| The kind of dose or rate specified. | Other |
|
encounter-admit-source
| This value set defines a set of codes that can be used to indicate from where the patient came in. | Other |
|
encounter-class
| This value set defines a set of codes that can be used to indicate the class of encounter: a specific code indicating class of service provided. | V3 |
|
encounter-diet
| This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. | Other |
|
encounter-discharge-disposition
| This value set defines a set of codes that can be used to where the patient left the hospital. | Other |
|
encounter-special-arrangements
| This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit. | Other |
|
encounter-subject-status
| This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter | Other |
|
encounter-type
| This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided. | Other |
|
endpoint-connection-type
| This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values. | Other |
|
entformula-additive
| EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example. | Other |
|
episodeofcare-type
| This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record. | Other |
|
evidence-quality
| A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems. | Other |
|
ex-benefitcategory
| This value set includes examples of Benefit Category codes. | Other |
|
ex-diagnosis-on-admission
| This value set includes example Diagnosis on Admission codes. | Other |
|
ex-diagnosisrelatedgroup
| This value set includes example Diagnosis Related Group codes. | Other |
|
ex-diagnosistype
| This value set includes example Diagnosis Type codes. | Other |
|
ex-payee-resource-type
| The type of Claim payee Resource. | Other |
|
ex-paymenttype
| This value set includes example Payment Type codes. | Other |
|
ex-procedure-type
| This value set includes example Procedure Type codes. | Other |
|
ex-program-code
| This value set includes sample Program Reason Span codes. | Other |
|
ex-revenue-center
| This value set includes sample Revenue Center codes. | Other |
|
expansion-parameter-source
| Declares what the source of a parameter is. | Other |
|
expansion-processing-rule
| Defines how concepts are processed into the expansion when it's for UI presentation. | Other |
|
financial-taskcode
| This value set includes Financial Task codes. | Other |
|
financial-taskinputtype
| This value set includes Financial Task Input Type codes. | Other |
|
flag-category
| Example list of general categories for flagged issues. (Not complete or necessarily appropriate.) | Other |
|
forms
| This value set includes a sample set of Forms codes. | Other |
|
fundsreserve
| This value set includes sample funds reservation type codes. | Other |
| gender-identity | Codes that indicate a individual's gender identity. | SNOMED CT, V3 |
|
goal-acceptance-status
| Codes indicating whether the goal has been accepted by a stakeholder. | Other |
|
goal-achievement
| Describes the progression, or lack thereof, towards the goal against the target. | Other |
|
goal-category
| Example codes for grouping goals to use for filtering or presentation. | Other |
|
goal-priority
| Indicates the level of importance associated with reaching or sustaining a goal. | Other |
|
goal-relationship-type
| Types of relationships between two goals. | Other |
|
guide-parameter-code
| Code of parameter that is input to the guide. | Other |
|
handling-condition
| Set of handling instructions prior testing of the specimen. | Other |
|
history-absent-reason
| Codes describing the reason why a family member's history is not available. | Other |
|
hl7-work-group
| An HL7 administrative unit that owns artifacts in the FHIR specification. | Other |
|
immunization-evaluation-dose-status
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example. | Other |
|
immunization-evaluation-dose-status-reason
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example. | Other |
|
immunization-funding-source
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example. | Other |
|
immunization-program-eligibility
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's eligibility for a vaccination program. This value set is provided as a suggestive example. | Other |
|
immunization-recommendation-status
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example. | Other |
|
immunization-subpotent-reason
| The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example. | Other |
|
implantStatus
| A set codes that define the functional status of an implanted device. | Other |
|
insuranceplan-applicability
| Whether the cost applies to in-network or out-of-network providers. | Other |
|
insuranceplan-type
| This example value set defines a set of codes that can be used to indicate a type of insurance plan. | Other |
| international-civil-aviation-organization-sex-or-gender | Concepts representing recorded sex or gender values for international exchange. | Other |
|
library-type
| The type of knowledge asset this library contains. | Other |
|
list-empty-reason
| General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list). | Other |
|
list-example-codes
| Example use codes for the List resource - typical kinds of use. | Other |
|
list-order
| Base values for the order of the items in a list resource. | Other |
|
location-physical-type
| This example value set defines a set of codes that can be used to indicate the physical form of the Location. | Other |
|
match-grade
| A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. | Other |
|
measure-data-usage
| The intended usage for supplemental data elements in the measure. | Other |
|
measure-improvement-notation
| Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue. | Other |
|
measure-population
| The type of population. | Other |
|
measure-scoring
| The scoring type of the measure. | Other |
|
measure-type
| The type of measure (includes codes from 2.16.840.1.113883.1.11.20368). | Other |
|
med-admin-perform-function
| MedicationAdministration Performer Function Codes | Other |
|
medication-admin-location
| Direction in which lists of possible answers should be displayed. | Other |
|
medication-usage-admin-location
| Direction in which lists of possible answers should be displayed. | Other |
|
medicationdispense-performer-function
| MedicationDispense Performer Function Codes | Other |
|
medicationknowledge-characteristic
| MedicationKnowledge Characteristic Codes | Other |
|
medicationknowledge-package-type
| MedicationKnowledge Package Type Codes | Other |
|
medicationknowledge-status
| MedicationKnowledge Status Codes | Other |
|
medicationrequest-admin-location
| Direction in which lists of possible answers should be displayed. | Other |
|
medicationrequest-category
| MedicationRequest Category Codes | Other |
|
medicationrequest-course-of-therapy
| MedicationRequest Course of Therapy Codes | Other |
|
medicationrequest-status-reason
| MedicationRequest Status Reason Codes | Other |
|
message-reason-encounter
| Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. | Other |
|
mif-conceptRelationshipKind
| Codes for use in the ext-mif-relationship-relationshipKind to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.relationshipKind values | Other |
|
mif-conceptRelationshipReflexivity
| Codes for use in the ext-mif-relationship-reflexivity to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.reflexivity values | Other |
|
mif-conceptRelationshipSymmetry
| Codes for use in the ext-mif-relationship-symmetry to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.symmetry values | Other |
|
mif-conceptRelationshipTransitivity
| Codes for use in the ext-mif-relationship-transitivity to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.transitivity values | Other |
|
missing-tooth-reason
| This value set includes sample Missing Tooth Reason codes. | Other |
|
nutrition-intake-category
| NutritionIntake Category Codes | Other |
|
object-role
| Code representing the role the entity played in the audit event. | Other |
|
observation-category
| Observation Category codes. | Other |
|
observation-statistics
| The statistical operation parameter -"statistic" codes. | Other |
|
organization-type
| This example value set defines a set of codes that can be used to indicate a type of organization. | Other |
|
parameter-group
| Codes identifying groupings of parameters; e.g. Cardiovascular. | Other |
|
payeetype
| This value set includes sample Payee Type codes. | Other |
|
payment-adjustment-reason
| This value set includes smattering of Payment Adjustment Reason codes. | Other |
|
payment-status
| This value set includes a sample set of Payment Status codes. | Other |
|
payment-type
| This value set includes sample Payment Type codes. | Other |
|
plan-definition-type
| The type of PlanDefinition. | Other |
|
process-priority
| This value set includes the financial processing priority codes. | Other |
|
program
| This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties. | Other |
| pronouns | Codes that indicate the pronouns to be used when communicating with or about an individual. | LOINC |
|
provenance-agent-type
| The type of participation a provenance participant. | Other |
|
provider-qualification
| This value set includes sample Provider Qualification codes. | Other |
|
question-max-occurs
| Flags an element as having unlimited repetitions. | Other |
|
questionnaire-usage-mode
| Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item. | Other |
|
reaction-event-certainty
| Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event. | Other |
|
reason-medication-given-codes
| This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process. | Other |
|
recommendation-strength
| A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems. | Other |
| recorded-sex-or-gender-type | Codes that represent the type of the recorded sex and gender. | LOINC, DICOM |
|
referencerange-meaning
| This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population. | Other |
|
rejection-criteria
| Criterion for rejection of the specimen by laboratory. | Other |
|
related-claim-relationship
| This value set includes sample Related Claim Relationship codes. | Other |
|
research-study-objective-type
| Codes for the kind of study objective. | Other |
|
research-study-phase
| Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation. | Other |
|
research-study-prim-purp-type
| Codes for the main intent of the study. | Other |
|
research-study-reason-stopped
| Codes for why the study ended prematurely. | Other |
|
research-subject-milestone
| Indicates the progression of a study subject through the study milestones. | Other |
|
research-subject-state
| Indicates the progression of a study subject through a study. | Other |
|
research-subject-state-type
| Identifies the kind of state being refered to. | Other |
|
resource-security-category
| Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource. | Other |
|
resource-type-link
| The type of payee Resource. | Other |
|
risk-probability
| Codes representing the likelihood of a particular outcome in a risk assessment. | Other |
|
service-category
| This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. | Other |
|
service-place
| This value set includes a smattering of Service Place codes. | Other |
|
service-provision-conditions
| The code(s) that detail the conditions under which the healthcare service is available/offered. | Other |
|
service-referral-method
| The methods of referral can be used when referring to a specific HealthCareService resource. | Other |
|
service-type
| This value set defines an example set of codes of service-types. | Other |
|
service-uscls
| This value set includes a smattering of USCLS codes. | Other |
| sex-for-clinical-use | Codes that represent the sex characterization appropriate for the associated clinical context. | Other |
|
smart-capabilities
| Codes that define what the server is capable of. | Other |
|
snomed-intl-gps
| SNOMED International Global Patient Set (GPS) value set. The value set includes all of the codes from the SNOMED International Global Patient Set (GPS) subset of SNOMED CT. The current version of the value set contains all concepts (26,158) from the September 2020 release of the GPS (based on the July 2020 SNOMED CT International Edition release). This value set is provided as a FHIR ValueSet resource instance for the convenience of implementers. | SNOMED CT |
|
special-values
| A set of generally useful codes defined so they can be included in value sets. | Other |
|
standards-status
| HL7 Ballot/Standards status of artifact. | Other |
|
state-change-reason
| Indicates why the state of the subject changed. | Other |
|
statistic-type
| The type of a specific statistic. | Other |
|
study-type
| The type of study a statistic was derived from. | Other |
|
subscriber-relationship
| This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient). | Other |
|
subscription-channel-type
| Codes to represent subscription error details | Other |
|
subscription-error
| Codes to represent subscription error details | Other |
|
subscription-status-at-event
| A status code for the state of the Subscription. | Other |
|
subscription-tag
| Tags to put on a resource after subscriptions have been sent. | Other |
|
substance-category
| Substance category codes | Other |
|
supplydelivery-type
| This value sets refers to a specific supply item. | Other |
|
supplyrequest-kind
| This value sets refers to a Category of supply. | Other |
|
supplyrequest-reason
| The reason why the supply item was requested. | Other |
|
surface
| This value set includes a smattering of FDI tooth surface codes. | Other |
|
synthesis-type
| Types of combining results from a body of evidence (eg. summary data meta-analysis). | Other |
|
testscript-operation-codes
| This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. | Other |
|
testscript-profile-destination-types
| This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript. | Other |
|
testscript-profile-origin-types
| This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript. | Other |
|
tooth
| This value set includes a smattering of FDI oral site codes. | Other |
|
usage-context-type
| A code that specifies a type of context being specified by a usage context. | Other |
|
variable-role
| The role that the assertion variable plays. | Other |
|
variant-state
| Codes providing the status of the variant test result. | Other |
|
verificationresult-can-push-updates
| Ability of the primary source to push updates/alerts | Other |
|
verificationresult-communication-method
| Attested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated. | Other |
|
verificationresult-failure-action
| The result if validation fails | Other |
|
verificationresult-need
| The frequency with which the target must be validated | Other |
|
verificationresult-primary-source-type
| Type of the validation primary source | Other |
|
verificationresult-push-type-available
| Type of alerts/updates the primary source can send | Other |
|
verificationresult-validation-process
| The primary process by which the target is validated | Other |
|
verificationresult-validation-status
| Status of the validation of the target against the primary source | Other |
|
verificationresult-validation-type
| What the target is validated against | Other |
|
vision-product
| This value set includes a smattering of Prescription Product codes. | Other |
|
yes-no-unknown-not-asked
| This value set contains 4 concepts commonly used as answers to items in a questionnaire. | V2 |
FHIR
®©
HL7.org
2011+.
FHIR
Release
4B
(v4.3.0)
hl7.fhir.r4b.core#4.3.0
R5
Snapshot
3,
hl7.fhir.core#5.0.0-snapshot3
generated
on
Sat,
May
28,
Wed,
Dec
14,
2022
12:58+1000.
07:17+1100.
Links:
Search
|
Version
History
|
Table
of
Contents
|
Glossary
|
QA
Page
|
Compare
to
R4
R4B
|
Compare
to
R5
Draft
|
|
Propose
a
change