This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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: R5R4BR4R3R2
This table contains a list of all the value sets defined as part of the FHIR specification. Some of these
value sets include codes defined elsewhere, some contain their own inline code system definitions, and some do both.
Any implicit code systems are case sensitive, though FHIR will never define codes that only differ by case.
Note that these value sets are available as FHIR resources - see the Downloads Page (as part of the FHIR definitions)
NameDefinitionSourceId
Namespace: http://hl7.org/fhir/ValueSet
FHIR-versionN All published FHIR Versions. Internal 1309
abstract-typesN A list of the base types defined by this version of the FHIR specification - types that are defined, but for which only specializations actually are created. Internal 23
account-status Indicates whether the account is available to be used. Internal 726
account-type This examples value set defines the set of codes that can be used to represent the type of an account. V3 728
action-cardinality-behavior Defines behavior for an action or a group for how many times that item may be repeated. Internal 807
action-code Provides examples of actions to be performed. Other 0
action-condition-kind Defines the kinds of conditions that can appear on actions. Internal 815
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 596
adjudication-error This value set includes a smattering of adjudication codes. Other 39
adjudication-reason This value set includes smattering of Adjudication Reason codes. Other 598
administrable-dose-form Dose form for a medication, in the form suitable for administering to the patient, after mixing, where necessary. Internal 1584
administration-method-codes This value set includes some method codes from SNOMED CT - provided as an exemplar SNOMED CT 97
administrative-genderN The gender of a person used for administrative purposes. Internal 1
adverse-event-actuality Overall nature of the adverse event, e.g. real or potential. Internal 831
adverse-event-category Overall categorization of the event, e.g. product-related or situational. Other 833
adverse-event-severity The severity of the adverse event itself, in direct relation to the subject. Other 844
adverse-event-type This value set includes all SNOMED CT Clinical Findings. SNOMED CT 835
age-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes FHIR 19
all-distance-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of length FHIR null
all-languagesN This value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47) Other 21
all-time-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of time FHIR null
all-typesN A list of all the concrete types defined in this version of the FHIR specification - Abstract Types, Data Types and Resource Types. Internal 25
allelename European Bioinformatics Institute Other 1045
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 0
allergy-intolerance-category Category of an identified substance associated with allergies or intolerances. Internal 133
allergy-intolerance-criticality Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. Internal 129
allergy-intolerance-type Identification of the underlying physiological mechanism for a Reaction Risk. Internal 131
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 137
animal-breeds This example value set defines a set of codes that can be used to indicate breeds of species. SNOMED CT 422
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 418
animal-species This example value set defines a set of codes that can be used to indicate species of animal patients. SNOMED CT 420
asset-availability This value set has asset availability codes. Internal 1295
attribute-estimate-type A statistic about a statistic, e.g. Confidence interval or p-value Other 1542
audit-entity-type Code for the entity type involved in the audit event. Other, Internal 458
audit-event-action Indicator for type of action performed during the event that generated the event. Internal 452
audit-event-outcome Indicates whether the event succeeded or failed. Internal 454
audit-event-sub-type More detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions. DICOM, Internal 464
audit-event-type Event Types for Audit Events - defined by DICOM with some FHIR specific additions. DICOM, Other 462
audit-source-type The type of process where the audit event originated from. Other 466
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 138
benefit-network This value set includes a smattering of Network type codes. Other 608
benefit-term This value set includes a smattering of Benefit Term codes. Other 612
benefit-type This value set includes a smattering of Benefit type codes. Other 606
benefit-unit This value set includes a smattering of Unit type codes. Other 610
binding-strengthN Indication of the degree of conformance expectations associated with a binding. Internal 43
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 141
bodysite-laterality Laterality: SNOMED-CT concepts for 'left', 'right', and 'bilateral' SNOMED CT 287
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 142
bundle-typeN Indicates the purpose of a bundle - how it is intended to be used. Internal 620
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 67
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 72
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 145
care-plan-activity-outcome Example codes indicating the outcome of a care plan activity. Note that these are in no way complete and might not even be appropriate for some uses. SNOMED CT 149
care-plan-activity-status Codes that reflect the current state of a care plan activity within its overall life cycle. Internal 146
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 148
care-plan-intent Codes indicating the degree of authority/intentionality associated with a care plan. Internal 150
care-team-status Indicates the status of the care team. Internal 153
careteam-participant-role Roles of participants that may be included in a care team. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization (qualifier value). SNOMED CT 152
claim-modifiers This value set includes sample Modifier type codes. Other 536
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 566
claim-type This value set includes Claim Type codes. Other 558
claim-use The purpose of the Claim: predetermination, preauthorization, claim. Internal 544
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 232
clinicalimpression-status Codes that reflect the current state of a clinical impression within its overall lifecycle. Internal 1046
clinvar NCBI central repository for curating pathogenicity of potentially clinically relevant variants Other 1041
code-search-support The degree to which the server supports the code search parameter on ValueSet, if it is supported. Internal 860
codesystem-content-modeN The extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource. Internal 782
conceptmap-unmapped-mode Defines which action to take if there is no match in the group. Internal 480
condition-category Preferred value set for Condition Categories. Other 162
condition-cause Example value set for Cause of Condition codes SNOMED CT 965
condition-clinical Preferred value set for Condition Clinical Status. Other 164
condition-code Example value set for Condition/Problem/Diagnosis codes. SNOMED CT 161
condition-outcome Example value set for condition outcomes. SNOMED CT 967
condition-predecessor Example value set for condition predecessor codes. SNOMED CT 966
condition-severity Preferred value set for Condition/Diagnosis severity grading. SNOMED CT 168
condition-stage Example value set for stages of cancer and other conditions. SNOMED CT 170
condition-stage-type Example value set for the type of stages of cancer and other conditions SNOMED CT 171
condition-ver-status The verification status to support or decline the clinical status of the condition or diagnosis. Other 166
conditional-delete-statusN A code that indicates how the server supports conditional delete. Internal 194
conditional-read-statusN A code that indicates how the server supports conditional read. Internal 200
consent-action This value set includes sample Consent Action codes. Other 753
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 751
consent-content-class This value set includes the FHIR resource types, along with some other important content class codes Other, Internal 747
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 389
constraint-severityN SHALL applications comply with this constraint? Internal 81
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 416
container-material This value set includes SNOMED CT codes for materials that specimen containers are made of SNOMED CT 1400
contract-action This value set includes sample Contract Action codes. Other 739
contract-actionstatus This value set contract specific codes for action status. Internal 1303
contract-actorrole This value set includes sample Contract Actor Role codes. Other 741
contract-assetcontext This value set contract specific codes for asset context. Internal 1297
contract-assetscope This value set contract specific codes for asset scope. Internal 1293
contract-assetsubtype This value set contract specific codes for asset subtype. Internal 1301
contract-assettype This value set contract specific codes for asset type. Internal 1299
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 745
contract-decision-mode This value set contract specific codes for decision modes. Internal 1291
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 0
coverage-class This value set includes Coverage Class codes. Other 1009
coverage-copay-type This value set includes sample Coverage Copayment Type codes. Other 527
cpt-all A value set that includes all CPT codes Other null
currenciesN Currency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html) Other 1025
data-absent-reasonN Used to specify why the normally expected content of the data element is missing. Other 5
data-typesN A version specific list of the data types defined by the FHIR specification for use as an element type (any of the FHIR defined data types). Internal 22
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 910
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 911
defined-typesN A list of all the concrete types defined in this version of the FHIR specification - Data Types and Resource Types. Internal 24
definition-resource-types A list of all the definition resource types defined in this version of the FHIR specification. Internal 1056
definition-status Codes identifying the lifecycle stage of a definition. Other 107
definition-topic High-level categorization of the definition, used for searching, sorting, and filtering. Other 794
definition-useN Structure Definition Use Codes / Keywords Other 1190
designation-useN Details of how a designation would be used SNOMED CT 264
detectedissue-category Kinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. V3 204
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 205
detectedissue-severity Indicates the potential degree of impact of the identified issue on the patient. Internal 206
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 425
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 208
device-nametype The type of name the device is referred by. Internal 1083
device-statement-status A coded concept indicating the current status of the Device Usage. Internal 214
device-status The availability status of the device. Internal 209
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. SNOMED CT 1376
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 645
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 49
diagnostic-based-on-snomed Diagnostic Attachment Type codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182836005 (Review of medication (procedure)) or is-a 404684003 (Clinical finding (finding)) SNOMED CT 960
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 385
directness The quality of how direct the match is. Other 1458
discriminator-typeN How an element value is interpreted when discrimination is evaluated. Internal 91
disease-status The status of a disease or symptom. SNOMED CT 1664
distance-units Unified Code for Units of Measure (UCUM). This value set includes common UCUM codes for units of distance FHIR 62
doc-classcodes This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests. LOINC 46
doc-section-codes Document section codes (LOINC codes used in CCDA sections). LOINC 237
doc-typecodes FHIR Document Codes - all LOINC codes where scale type = 'DOC'. LOINC 240
document-modeN Whether the application produces or consumes documents. Internal 186
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 250
encounter-reason This examples value set defines the set of codes that can be used to indicate reasons for an encounter. SNOMED CT 261
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 253
encounter-special-courtesy This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. V3 252
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 248
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 498
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 496
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 394
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 392
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 391
filter-operatorN The kind of operation to perform as a part of a property based filter. Internal 478
flag-category Example list of general categories for flagged issues. (Not complete or necessarily appropriate.) Other 122
flag-code Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) SNOMED CT 124
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 950
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 120
fm-status This value set includes Status codes. Internal 592
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 954
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 384
formatcodes The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at https://confluence.hl7.org/display/SD/Format+Codes+for+IHE+XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incomplete Other 1
forms This value set includes a sample set of Forms codes. Other 37
fundsreserve This value set includes sample funds reservation type codes. Other 33
gender-identity This example value set defines a set of codes that can be used to indicate a patient's gender identity. Internal 972
genenames HGNC: Human Gene Nomenclature Committee Other 1037
goal-achievement Describes the progression, or lack thereof, towards the goal against the target. Other 1374
goal-category Example codes for grouping goals to use for filtering or presentation. Other 275
goal-priority Indicates the level of importance associated with reaching or sustaining a goal. Other 273
goal-start-event Identifies types of events that might trigger the start of a goal. SNOMED CT 279
goal-status Codes that reflect the current state of a goal and whether the goal is still being targeted. Internal 271
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 301
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 303
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. Other 299
immunization-evaluation-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 evaluation is against. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy. SNOMED CT 300
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 995
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 293
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 296
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 291
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 290
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 308
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 307
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 305
immunization-recommendation-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 targeted by a vaccination recommendation. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy. SNOMED CT 309
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 289
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 288
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 295
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. V3, SNOMED CT 992
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 993
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 the SNOMED CT concepts from the 64572001 (Disease) hierarchy. SNOMED CT 1047
ingredient-function A classification of the ingredient identifying its precise purpose(s) in the drug product (beyond e.g. active/inactive). Internal 1596
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 1598
ingredient-role A classification of the ingredient identifying its purpose within the product. Internal 1594
invoice-status Codes identifying the lifecycle stage of an Invoice. Internal 866
iso3166-1-2 This value set defines the ISO 3166 Part 1 2-letter codes Other null
iso3166-1-3 This value set defines the ISO 3166 Part 1 3-letter codes Other null
iso3166-1-N This value set defines the ISO 3166 Part 1 Numeric codes Other null
issue-severityN How the issue affects the success of the action. Internal 408
issue-typeN A code that describes the type of issue. Internal 410
item-type Distinguishes groups from questions and display text and indicates data type for questions. Internal 444
jurisdictionN 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 48
knowledge-resource-types A list of all the knowledge resource types defined in this version of the FHIR specification. Internal 1062
language-preference-type This value set defines the set of codes for describing the type or mode of the patient's preferred language. Internal 1022
languages This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) Other 20
legal-status-of-supply The prescription supply types appropriate to a medicinal product Internal 1555
library-type The type of knowledge asset this library contains. Other 763
link-typeN The type of link between this patient resource and another patient resource. Internal 423
linkage-type Used to distinguish different roles a resource can play within a set of linked resources. Internal 314
lipid-ldl-codes LDL Cholesterol codes - measured or calculated LOINC 0
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 322
list-example-codes Example use codes for the List resource - typical kinds of use. Other 316
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 320
list-mode The processing mode that applies to this list. Internal 318
list-order Base values for the order of the items in a list resource. Other 324
list-status The current state of the list. Internal 326
location-mode Indicates whether a resource instance represents a specific location or a class of locations. Internal 330
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 328
location-status Indicates whether the location is still in use. Internal 332
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 1236
measure-type The type of measure (includes codes from 2.16.840.1.113883.1.11.20368). Other 769
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 0
medication-as-needed-reason This value set includes all clinical findings from SNOMED CT - provided as an exemplar value set. SNOMED CT 96
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 375
medication-form-codes This value set includes all dose form codes from SNOMED CT - provided as an exemplar. SNOMED CT 374
medicinal-product-pediatric-use Extra measures defined for a Medicinal Product, such as heightened reporting requirements. Internal 1578
medicinal-product-special-measures Extra measures defined for a Medicinal Product, such as a requirement to conduct post-authorisation studies. Internal 1566
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 924
mimetypesN This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13) Other 1024
missing-tooth-reason This value set includes sample Missing Tooth Reason codes. Other 534
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 388
name-assembly-order A code that represents the preferred display order of the components of a human name. Other, V2, V3 913
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 906
name-v3-representation A set of codes for each different representation of a name. V3 909
namingsystem-identifier-type Identifies the style of unique identifier used to identify a namespace. Internal 492
namingsystem-type Identifies the purpose of the naming system. Internal 490
narrative-status The status of a resource narrative. Internal 55
network-type The type of network access point of this agent in the audit event. Internal 456
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 null
note-type The presentation types of notes. Internal 15
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 386
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 327997002 Foods for special diets (product) or has a parent of 229963004 Cultural food types (substance). SNOMED CT 0
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 0
object-lifecycle-events This example FHIR value set is comprised of lifecycle event codes. The FHIR Actor value set is based on DICOM Audit Message, ParticipantObjectDataLifeCycle; ISO Standard, TS 21089-2017; Other null
object-role Code representing the role the entity played in the audit event. Other 460
observation-interpretationN 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 399
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 395
observation-statistics Codes indicating types of statistics that can be returned Internal 405
observation-statusN Codes providing the status of an observation. Internal 400
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 62
operation-kindN Whether an operation is a normal operation or a query. Internal 506
operation-parameter-useN Whether an operation parameter is an input or an output parameter. Internal 508
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 880
organization-type This example value set defines a set of codes that can be used to indicate a type of organization. Other 414
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 921
participantrequired Is the Participant required to attend the appointment. Internal 488
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 FHIR Actor participation type value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. Other, V3, DICOM 54
participationstatus The Participation status of an appointment. Internal 486
postal-address-use Uses of an address not included in Address.use. V3 908
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 1399
procedure-followup Procedure follow up codes: A selection of SNOMED CT codes relevant to procedure follow up. SNOMED CT 429
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 (394908001). SNOMED CT 431
procedure-outcome Procedure Outcome code: A selection of relevant SNOMED CT codes. SNOMED CT 428
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 946
procedure-reason This example value set defines the set of codes that can be used to indicate a reason for a procedure. SNOMED CT 432
process-priority This value set includes the financial processing priority codes. Other 552
provenance-activity-type This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes. V3 438
provenance-agent-type The type of participation a provenance participant. Other 1003
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 927
questionnaire-item-control Starter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire. Internal 931
questionnaire-questions Example list of codes for questions and groups of questions. (Not necessarily complete or appropriate.) LOINC 443
reaction-event-certainty Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event. Internal 942
reaction-event-severity Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. Internal 135
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 344
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 342
reason-medication-status-codes This value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplar SNOMED CT 369
recommendation-strength A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems. Other 1021
reference-version-rulesN Whether a reference needs to be version specific or version independent, or whether either can be used. Internal 89
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 407
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 397
regulated-authorization-basis A legal or regulatory framework against which an authorization is granted, or other reasons for it. Internal 1642
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 821
risk-probability Codes representing the likelihood of a particular outcome in a risk assessment. Other 450
route-codes This value set includes all Route codes from SNOMED CT - provided as an exemplar. SNOMED CT 98
search-comparator What Search Comparator Codes are supported in search. Internal 637
search-entry-modeN 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 622
search-param-typeN Data types allowed to be used for search parameters. Internal 11
search-xpath-usage How a search parameter relates to the set of elements returned by evaluating its xpath query. Internal 635
secondary-finding Codes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding. Internal 1285
security-labelsN A single value set for all security labels defined by FHIR. Other 47
security-role-type This example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user's access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient. Other, V3, DICOM 978
service-category This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. Other 516
service-place This value set includes a smattering of Service Place codes. Other 564
service-provision-conditions The code(s) that detail the conditions under which the healthcare service is available/offered. Other 514
service-referral-method The methods of referral can be used when referring to a specific HealthCareService resource. Other 510
service-type This value set defines an example set of codes of service-types. Other 518
service-uscls This value set includes a smattering of USCLS codes. Other 542
servicerequest-category An example value set of SNOMED CT concepts that can classify a requested service SNOMED CT 434
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 435
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 922
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 12
slotstatus The free/busy status of the slot. Internal 482
smart-capabilities Codes that define what the server is capable of. Other 1018
sort-direction The possible sort directions, ascending or descending. Internal 979
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 1026
special-values A set of generally useful codes defined so they can be included in value sets. Other 9
specimen-collection Actions that can be taken for the collection of specimen from a subject. SNOMED CT 1398
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 468
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 939
specimen-container-type Containers which may hold specimens or specimen containers. Include codes SNOMED CT(http://snomed.info/sct) where concept is-a 434711009 (Specimen container (physical object)) SNOMED CT 470
study-type The type of study the evidence was derived from. Other 1349
subject-type Possible types of subjects. Internal 775
subscriber-relationship This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient). Other 1385
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 0
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 473
substance-grade The quality standard, established benchmark, to which a substance complies. Internal 1608
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 1632
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 1626
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 390
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 699
target-species A species for which a medicinal product is intended. Internal 1588
task-code Codes indicating the type of action that is expected to be performed Internal 1396
task-intent Distinguishes whether the task is a proposal, plan or full order. Internal 1240
task-status The current status of the task. Internal 790
template-status-code The status indicates the level of maturity of the design and may be used to manage the use of the design. Other 8
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 704
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 714
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 712
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 387
unit-of-presentation The presentation type in which an administrable medicinal product is given to a patient. Internal 1586
units-of-timeN A unit of time (units from UCUM). FHIR 77
usage-context-type A code that specifies a type of context being specified by a usage context. Other 101
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 28
vaccine-code This identifies the vaccine substance administered - CVX codes. Internal, Other 22
variable-handling The handling of the variable in statistical analysis for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive). Internal 0
variable-role The role that the assertion variable plays. Other 1456
variable-type The possible types of variables for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive). Internal 1343
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 1401
versioning-policyN How the system supports versioning for a resource. Internal 190
vision-base-codes A coded concept listing the base codes. Internal 662
vision-eye-codes A coded concept listing the eye codes. Internal 660
vision-product This value set includes a smattering of Prescription Product codes. Other 658
warning-type Classification of warning type. Internal 1455
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 null
yesnodontknow For Capturing simple yes-no-don't know answers Other null