This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2 Using Codes Systems Value Sets v2 Tables v3 Namespaces Concept Maps 1.14.2.0 Value Sets Defined in FHIR 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 define their own codes, and some do both. Name (in http://hl7.org/fhir/vs/) Definition Source Id address-use The use of an address Internal 16 administration-method-codes This value set includes some introduction (procedure) codes from SNOMED CT - provided as an exemplar SNOMED CT 94 administrative-gender This value set defines the set of codes that can be used to indicate the administrative gender of a person V3 24 alert-status Indicates whether this alert is active and needs to be displayed to a user, or whether it is no longer needed or entered in error Internal 208 animal-breeds This example value set defines a set of codes that can be used to indicate breeds of species. Internal 134 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 131 animal-species This example value set defines a set of codes that can be used to indicate species of animal patients. Internal 133 answer-format The expected format of an answer Internal 254 anzsco-occupations Developed for use in the collection, analysis and dissemination of occupation statistics in Australia and New Zealand External 156 approach-site-codes This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar SNOMED CT 95 binding-conformance Binding conformance for applications Internal 144 body-site This value set includes all the "Clinical finding" SNOMED CT codes (i.e. codes with an is-a relationship with 91723000: Anatomical structure) SNOMED CT 62 care-plan-activity-category High-level categorization of the type of activity in a care plan. Internal 39 care-plan-activity-status Indicates where the activity is at in its overall life cycle Internal 41 care-plan-goal-status Indicates whether the goal has been met and is still being targeted Internal 38 care-plan-status Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record. Internal 36 causalityExpectation How likely is it that the given exposure caused a reaction Internal 32 clinical-findings This value set includes all the "Clinical finding" SNOMED CT codes (i.e. codes with an is-a relationship with 404684003: Clinical finding) SNOMED CT 316 composition-attestation-mode The way in which a person authenticated a composition Internal 331 composition-status The workflow/clinical status of the composition Internal 334 concept-equivalence The degree of equivalence between concepts Internal 306 condition-category Example value set for Condition (Problem/Diagnosis) Categories Internal 224 condition-certainty Example value set for Condition/Problem/Diagnosis certainty SNOMED CT 226 condition-code Example value set for Condition/Problem/Diagnosis codes SNOMED CT 313 condition-relationship-type The type of relationship between a condition and its related item Internal 228 condition-severity Example value set for Condition/Diagnosis severity grading SNOMED CT 227 condition-status The clinical status of the Condition or diagnosis Internal 225 conformance-statement-status The status of this conformance statement Internal 255 constraint-severity SHALL applications comply with this constraint? Internal 146 contact-system Telecommunications form for contact Internal 17 contact-use Location, type or status of telecommunications address indicating use Internal 18 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. Internal 127 criticality The criticality of an adverse sensitivity Internal 33 data-absent-reason Used to specify why the normally expected content of the data element is missing Internal 2 data-types The type of an element - one of the FHIR data types Internal 3 defined-types Either a resource or a data type Internal 5 diagnostic-order-event Additional information about an event that occurred to a diagnostic order LOINC 358 diagnostic-order-priority The clinical priority of a diagnostic order Internal 271 diagnostic-order-status The status of a diagnostic order Internal 207 diagnostic-report-status The status of the diagnostic report as a whole Internal 341 diagnostic-requests This value set includes all the LOINC Order codes LOINC 59 diagnostic-service-sections This value set includes all the codes in HL7 v2 table 0074 V2 61 dicm-402-roleid Audit Active Participant Role ID Code DICOM 366 doc-codes FHIR Document Codes - all LOINC codes where scale_type = 'DOC' LOINC 65 doc-section-codes Document section codes - all LOINC codes LOINC 330 docset-codes FHIR Document Codes - all LOINC codes where scale_type = 'DOC' LOINC 307 document-mode Whether the application produces or consumes documents Internal 47 document-reference-status The status of the document reference Internal 67 document-relationship-type The type of relationship between documents Internal 328 documentreference-service-types Known Service types that can be referred to from a Document Reference Internal 247 encounter-admit-source This value set defines a set of codes that can be used to indicate from where the patient came in. Internal 189 encounter-class Classification of the encounter Internal 182 encounter-diet This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. Internal 186 encounter-discharge-disposition This value set defines a set of codes that can be used to where the patient left the hospital Internal 190 encounter-participant-type This value set defines a set of codes that can be used to indicate how an individual parcitipates in an encounter Internal, V3 183 encounter-priority This value set defines a set of codes that can be used to indicate the encounter priority as determined by triage. Internal 187 encounter-reason This examples value set defines the set of codes that can be used to indicate reasons for an encounter SNOMED CT 188 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 Internal 185 encounter-special-courtesy This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. V3 184 encounter-state Current state of the encounter Internal 180 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 . Internal 181 event-timing Real world event that the schedule relates to V3 19 exposureType The type of exposure that resulted in an adverse reaction Internal 31 extension-context How an extension context is interpreted Internal 145 filter-operator The kind of operation to perform as a part of a property based filter Internal 177 group-type Types of resources that are part of group Internal 74 hierarchical-relationship-type Type indicating if this is a parent or child relationship Internal 233 identifier-use Identifies the purpose for this identifier, if known Internal 13 imaging-modality Type of acquired image data in the instance DICOM 19 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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example SNOMED CT 353 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 medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example Internal 356 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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example Internal 355 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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example V3 79 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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example V3 78 instance-availability Availability of the resource DICOM 76 issue-severity How the issue affects the success of the action Internal 120 issue-type A coded expression of the type of issue Internal 121 link-type The type of link between this patient resource and another patient resource. Internal 324 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) Internal 90 list-example-codes Example use codes for the List resource - typical kinds of use. TODO: Does LOINC define useful codes? Internal 320 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 Internal 89 list-mode The processing mode that applies to this list Internal 88 location-mode Indicates whether a resource instance represents a specific location or a class of locations Internal 337 location-physical-type This example value set defines a set of codes that can be used to indicate the physical form of the Location. Internal 336 location-status Indicates whether the location is still in use Internal 343 marital-status This value set defines the set of codes that can be used to indicate the marital status of a person Internal, V3 25 media-subtype Detailed information about the type of the image - it's kind, purpose, or the kind of equipment used to generate it Internal, SNOMED CT 239 media-type Whether the Media is a photo, video, or audio Internal 235 media-view Codes defined in SNOMED CT that can be used to record Media Recording views SNOMED CT 237 medication-admin-status A set of codes indicating the current status of a MedicationAdministration Internal 92 medication-codes This value set includes all Medication codes from Snomed - provided as an exemplar SNOMED CT 321 medication-dispense-status A code specifying the state of the dispense event. Describes the lifecycle of the dispense. Internal 101 medication-form-codes This value set includes all Form codes from SNOMED CT - provided as an exemplar SNOMED CT 108 medication-kind Whether the medication is a product or a package Internal 110 medication-package-form-codes This value set includes all Form codes from SNOMED CT - provided as an exemplar SNOMED CT 111 medication-prescription-status A code specifying the state of the prescribing event. Describes the lifecycle of the prescription. Internal 107 message-conformance-event-mode The mode of a message conformance statement Internal 45 message-events One of the message events defined as part of FHIR Internal 6 message-reason-encounter Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update Internal 112 message-significance-category The impact of the content of a message Internal 342 message-transport The protocol used for message transport Internal 46 modality Type of data in the instance DICOM 811 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 192 name-use The use of a human name Internal 15 narrative-status The status of a resource narrative Internal 28 network-type The type of network access point that originated the audit event Internal 164 no-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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example V3, SNOMED CT 354 null-flavor A collection of codes specifying why a valid value is not present V3 370 object-lifecycle Identifier for the data life-cycle stage for the participant object Internal 168 object-role Code representing the functional application role of Participant Object being audited Internal 167 object-type Code for the participant object type being audited Internal 166 observation-codes This value set includes all LOINC codes LOINC 115 observation-interpretation This value set defines the set of codes that can be used to indicate the meaning/use of a reference range V2 117 observation-methods Method Codes defined as part of v3 V3, SNOMED CT, LOINC 114 observation-relationshiptypes Codes specifying how two observations are related Internal 371 observation-reliability Codes that provide an estimate of the degree to which quality issues have impacted on the value of an observation Internal 118 observation-status Codes providing the status of an observation Internal 7 order-outcome-code The status of the response to an order Internal 323 organization-type This example value set defines a set of codes that can be used to indicate a type of organization. Internal 125 other-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. Internal 128 parent-relationship-codes The value set includes the v3 RoleCode PRN (parent) and all of its specializations. V3 311 patient-contact-relationship This value set defines a set of codes that are used to indicate the nature of the relationship between a patient and a contactperson for that patient Internal 135 postal-address-use Uses of an address not included in Address.use V3 326 practitioner-role This example value set defines a set of codes that can be used to indicate the role of a Practitioner. Internal 154 practitioner-specialty This example value set defines a set of codes that can be used to indicate the specialty of a Practitioner Internal 155 probability-distribution-type Codes specifying the type of probability distribution V3 325 procedure-relationship-type The nature of the relationship with this procedure Internal 136 property-representation How a property is represented on the wire Internal 339 provenance-agent-role The role that a provenance participant played Internal 269 provenance-agent-type The type of a provenance participant. Use either a defined FHIR resource type, or, if the reference is not to a resource, one of the defined codes, or some other code if none of the defined codes are appropriate Internal, FHIR 270 provenance-entity-role How an entity was used in an activity Internal 267 quantity-comparator How the Quantity should be understood and represented Internal 14 query-outcome The outcome of processing a query request Internal 157 questionnaire-group-name This example value set defines a set of codes that can be used to specify a group of questions within a Questionnaire. Internal 253 questionnaire-name This example value set defines a set of codes that can be used to specify a coded name for a standard Questionnaire. Internal 158 questionnaire-question-name This example value set defines a set of codes that can be used to specify a coded name for a question on a Questionnaire. Internal 252 questionnaire-status Lifecycle status of the questionnaire Internal 338 reactionSeverity The severity of an adverse reaction. Internal 29 reason-medication-not-given-codes This value set is provided as an exemplar Internal 93 referencerange-meaning This value set defines a set of codes that can be used to indicate the meaning/use of a reference range Internal, SNOMED CT 119 relatedperson-relationshiptype A set of codes that can be used to indicate the relationship between a Patient and a RelatedPerson. V3 251 report-names This value set includes all the LOINC codes which relate to Diagnostic Observations LOINC 58 resource-aggregation-mode How resource references can be aggregated Internal 310 resource-profile-status The lifecycle status of a Resource Profile Internal 147 resource-slicing-rules How slices are interpreted when evaluating an instance Internal 265 resource-types One of the resource types defined as part of FHIR Internal 4 response-code The kind of response to a message Internal 322 restful-conformance-mode The mode of a RESTful conformance statement Internal 42 restful-security-service Types of security services used with FHIR Internal 43 route-codes This value set includes all Route codes from SNOMED CT - provided as an exemplar SNOMED CT 96 search-param-type Data types allowed to be used for search parameters Internal 9 security-event-action Indicator for type of action performed during the event that generated the audit. Internal 210 security-event-outcome Indicates whether the event succeeded or failed Internal 211 security-event-sensitivity The sensitivity of an object in a secuity event resource. May also encompass confidentiality and rudimentary access control V3 222 security-event-sub-type More detailed code concerning the type of the security event - defined by DICOM with some FHIR specific additions DICOM, FHIR 221 security-event-type Event Types for Security Events - defined by DICOM with some FHIR specific additions Internal, DICOM 220 security-source-type The type of process where the security event originated from Internal 165 sensitivitystatus The status of the adverse sensitivity Internal 35 sensitivitytype The type of an adverse sensitivity Internal 34 special-values A set of generally useful codes defined so they can be included in value sets Internal 10 specimen-collection-method This example value set defines a set of codes that can be used to indicate the method of collection of a specimen. It includes values from HL7 v2 table 0048 SNOMED CT, V2 256 specimen-container-type Containers which may hold specimens or specimen containers - all SNOMED CT specimen containers SNOMED CT 264 specimen-treatment-procedure The technique that is used to perform the process or preserve the specimen V2 263 substance-type This value sets refers to a substance type SNOMED CT 257 supply-item This value sets refers to a specific supply item Internal 262 supply-type This value sets refers to a Category of supply Internal 259 system-restful-operation Operations supported by REST at the system level FHIR 309 type-restful-operation Operations supported by REST at the type or instance level FHIR 308 units-of-time A unit of time (units from UCUM) FHIR 20 vaccination-protocol-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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example Internal 82 vaccination-protocol-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 the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example Internal 83 vaccination-protocol-dose-target 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 medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example Internal 81 valueset-status The lifecycle status of a Value Set or Concept Map Internal 178 valueset-supply-dispense-status Status of the dispense Internal 357 valueset-supply-status Status of the supply Internal 260 xds-facilitycodes Example Connectathon Codes from http://ihexds.nist.gov:12080/xdsref/codes/codes.xml, with substantial corrections applied IHE, V3 246 xds-practice-codes Example Connectathon Codes from http://ihexds.nist.gov:12080/xdsref/codes/codes.xml IHE, SNOMED CT 243 xds-relationship-type The kind of relationship between two XDS documents Internal 242 xds-typecodes Example Connectathon Codes from http://ihexds.nist.gov:12080/xdsref/codes/codes.xml, with substantial corrections applied IHE, LOINC 329 © HL7.org 2011+. FHIR DSTU (v0.0.82.2943) generated on Tue, Sep 30, 2014 18:10+1000. Links: What's a DSTU? | Version History | | Propose a change var disqus_shortname = 'fhirdstu';(function() {var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq); })(); Please enable JavaScript to view the comments powered by Disqus. comments powered by Disqus var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-676355-1']); _gaq.push(['_setDomainName', '.hl7.org']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })();