Release 5 Draft Ballot

This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). 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

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

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-version NAll published FHIR Versions.Internal1309
abstract-types NA 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.Internal23
account-statusIndicates whether the account is available to be used.Internal726
account-typeThis examples value set defines the set of codes that can be used to represent the type of an account.V3728
action-cardinality-behaviorDefines behavior for an action or a group for how many times that item may be repeated.Internal807
action-codeProvides examples of actions to be performed.Other0
action-condition-kindDefines the kinds of conditions that can appear on actions.Internal815
action-grouping-behaviorDefines organization behavior of a group.Internal799
action-participant-functionThe function performed by the participant for the action.Internal0
action-participant-typeThe type of participant for the action.Internal811
action-precheck-behaviorDefines selection frequency behavior for an action or group.Internal805
action-reason-codeProvides examples of reasons for actions to be performed.Other0
action-relationship-typeDefines the types of relationships between actions.Internal813
action-required-behaviorDefines expectations around whether an action or action group is required.Internal803
action-selection-behaviorDefines selection behavior of a group.Internal801
action-typeThe type of action to be performed.Other809
additional-instruction-codesThis value set includes all SNOMED CT Additional Dosage Instructions.SNOMED CT95
address-type NThe type of an address (physical / postal).Internal69
address-use NThe use of an address.Internal67
adjudicationThis 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.Other596
adjudication-errorThis value set includes a smattering of adjudication codes.Other39
adjudication-reasonThis value set includes smattering of Adjudication Reason codes.Other598
administration-method-codesThis value set includes some method codes from SNOMED CT - provided as an exemplarSNOMED CT97
administrative-gender NThe gender of a person used for administrative purposes.Internal1
adverse-event-actualityOverall nature of the adverse event, e.g. real or potential.Internal831
adverse-event-categoryOverall categorization of the event, e.g. product-related or situational.Other833
adverse-event-causality-assessCodes for the assessment of whether the entity caused the event.Other840
adverse-event-causality-methodTODO.Other842
adverse-event-contributing-factorThis value set includes codes that describe the contributing factors suspected to have increased the probability or severity of the adverse event.SNOMED CT1478
adverse-event-mitigating-actionThis value set includes codes that describe the ameliorating actions taken after the adverse event occured in order to reduce the extent of harm.SNOMED CT1480
adverse-event-outcomeThis value set includes codes that describe the type of outcome from the adverse event.SNOMED CT836
adverse-event-participant-functionThis value set includes codes that describe the type of involvement of the actor in the adverse event.V31443
adverse-event-preventive-actionThis value set includes codes that describe the preventive actions that contributed to avoiding the adverse event.SNOMED CT1479
adverse-event-seriousnessOverall seriousness of this event for the patient.Other838
adverse-event-statusCodes identifying the lifecycle stage of an adverse event.Internal1444
adverse-event-supporting-infoThis value set includes codes that describe the supporting information relevant to the event.SNOMED CT1481
adverse-event-typeThis value set includes codes that describe the adverse event or incident that occurred or was averted.SNOMED CT835
age-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR19
all-distance-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of lengthFHIRnull
all-languages NThis value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47)Other21
all-media-typesAll media types (Multipurpose Internet Mail Extensions (MIME) Part Four - BCP 13)Othernull
all-time-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of timeFHIRnull
all-types NA list of all the concrete types defined in this version of the FHIR specification - Abstract Types, Data Types and Resource Types.Internal25
allerg-intol-substance-exp-riskDescription Needed HereInternal940
allergen-classThis 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 CT0
allergy-intolerance-categoryCategory of an identified substance associated with allergies or intolerances.Internal133
allergy-intolerance-criticalityEstimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.Internal129
allergy-intolerance-typeIdentification of the underlying physiological mechanism for a Reaction Risk.Internal131
allergyintolerance-clinicalPreferred value set for AllergyIntolerance Clinical Status.Other1372
allergyintolerance-codeThis 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 CT137
allergyintolerance-verificationThe verification status to support or decline the clinical status of the allergy or intolerance.Other1370
animal-breedsThis example value set defines a set of codes that can be used to indicate breeds of species.SNOMED CT422
animal-genderstatusThis example value set defines a set of codes that can be used to indicate the current state of the animal's reproductive organs.Internal418
animal-speciesThis example value set defines a set of codes that can be used to indicate species of animal patients.SNOMED CT420
appointment-cancellation-reasonThis example value set defines a set of reasons for the cancellation of an appointment.Other1381
appointmentstatusThe free/busy status of an appointment.Internal484
approach-site-codesThis value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar.SNOMED CT346
article-url-typeCode the reason for different URLs, eg abstract and full-text.Other1490
artifact-comment-typeThe type of artifact comment (documentation, review, guidance)Internal0
artifact-contribution-instance-typeArtifact Contribution Instance TypeOther0
artifact-contribution-typeCitation contribution.Other1504
artifact-relationship-typeArtifact Relationship TypeOther0
assert-direction-codesThe type of direction to use for assertion.Internal706
assert-operator-codesThe type of operator to use for assertion.Internal708
assert-response-code-typesThe type of response code to use for assertion.Internal710
asset-availabilityThis value set has asset availability codes.Internal1295
attribute-estimate-typeMethod of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation.Other1412
audit-entity-typeCode for the entity type involved in the audit event.DICOM, Other, Internal458
audit-event-actionIndicator for type of action performed during the event that generated the event.Internal452
audit-event-outcomeIndicates whether the event succeeded or failed.Other454
audit-event-severityThe severity of the audit entry.Internal1466
audit-event-sub-typeMore detailed code concerning the type of the audit event - defined by DICOM with some additional FHIR, HL7, and other additions.DICOM, Internal, Other464
audit-event-typeEvent Types for Audit Events - defined by DICOM with some FHIR specific additions.DICOM, Other462
audit-media-typeAgent Media Types for Audit Events - defined by DICOM with some FHIR specific additions.DICOM0
basic-resource-typeThis 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.Other138
benefit-networkThis value set includes a smattering of Network type codes.Other608
benefit-termThis value set includes a smattering of Benefit Term codes.Other612
benefit-typeThis value set includes a smattering of Benefit type codes.Other606
benefit-unitThis value set includes a smattering of Unit type codes.Other610
binding-strength NIndication of the degree of conformance expectations associated with a binding.Internal43
biological-product-statusBiologically Derived Product Status.Internal0
body-siteThis 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 CT141
bodystructure-codeThis 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 CT142
bodystructure-relative-locationSNOMED-CT concepts modifying the anatomic locationSNOMED CT140
bundle-type NIndicates the purpose of a bundle - how it is intended to be used.Internal620
capability-featureA feature that may be declared in a capability statementInternal0
capability-feature-valueA vaule for a feature that may be declared in a capability statementInternal0
capability-statement-kind NHow a capability statement is intended to be used.Internal198
care-plan-activity-kindResource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.Internal145
care-plan-activity-performedExample codes indicating the care plan activity that was performed. Note that these are in no way complete and might not even be appropriate for some uses.SNOMED CT0
care-plan-activity-statusCodes that reflect the current state of a care plan activity within its overall life cycle.Internal146
care-plan-activity-status-reasonExample 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.Other1416
care-plan-categoryExample 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 CT148
care-plan-intentCodes indicating the degree of authority/intentionality associated with a care plan.Internal150
care-team-categoryIndicates the type of care team.LOINC155
care-team-statusIndicates the status of the care team.Internal153
catalogTypeDescription Needed HereInternal968
catalogentry-relation-typeTypes of relationships between entries.Internal1445
catalogentry-statusPublic usability statuses for catalog entries.Internal1449
catalogentry-typeTypes of resources that can be attached to catalog entries.Internal1447
cdshooks-indicatorThis value set captures the set of indicator codes defined by the CDS Hooks specification.Other1065
certainty-ratingThe assessment of quality, confidence, or certainty.Other1414
certainty-typeThe aspect of quality, confidence, or certainty.Other0
characteristic-combinationLogical grouping of characteristics.Internal1527
characteristic-methodThe method used to determine the characteristic(s) of the variable.Other1452
chargeitem-billingcodesExample set of codes that can be used for billing purposes.Other848
chargeitem-statusCodes identifying the lifecycle stage of a ChargeItem.Internal846
choice-list-orientationDescription Needed HereInternal933
chromosome-humanChromosome number for human.Other224
citation-artifact-classifierCitation artifact classifierOther0
citation-classification-typeCitation classification typeOther0
citation-status-typeCitation status typeOther0
citation-summary-styleThe format for display of the citation.Other0
cited-artifact-abstract-typeUsed to express the reason and specific aspect for the variant abstract, such as language and specific language.Other0
cited-artifact-classification-typeCited Artifact Classification TypeOther0
cited-artifact-part-typeTo describe the reason for the variant citation, such as version number or subpart specification.Other1484
cited-artifact-status-typeCited Artifact Status TypeOther0
claim-careteamroleThis value set includes sample Claim Care Team Role codes.Other586
claim-exceptionThis value set includes sample Exception codes.Other580
claim-informationcategoryThis value set includes sample Information Category codes.Other582
claim-modifiersThis value set includes sample Modifier type codes.Other536
claim-outcomeThis value set includes Claim Processing Outcome codes.Internal0
claim-subtypeThis 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.Other566
claim-typeThis value set includes Claim Type codes.Other558
claim-useThe purpose of the Claim: predetermination, preauthorization, claim.Internal544
clinical-findingsThis value set includes all the "Clinical finding" [SNOMED CT](http://snomed.info/sct) codes - concepts where concept is-a 404684003 (Clinical finding (finding)).SNOMED CT232
clinical-use-issue-typeOverall defining type of this clinical use issue.Internal1454
clinicalimpression-prognosisExample value set for clinical impression prognosis.SNOMED CT160
clinicalimpression-status-reasonExample codes indicating the reason why a ClinicalImpression is on hold or stopped. Note that these are in no way complete and might not even be appropriate for some uses.SNOMED CT1417
code-search-supportThe degree to which the server supports the code search parameter on ValueSet, if it is supported.Internal860
codesystem-altcode-kindDescription Needed HereInternal952
codesystem-content-mode NThe extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource.Internal782
codesystem-hierarchy-meaning NThe meaning of the hierarchy of concepts in a code system.Internal784
codesystem-properties-modeDescription Needed HereInternal0
common-tagsCommon Tag Codes defined by FHIR projectOther79
communication-categoryCodes for general categories of communications such as alerts, instructions, etc.Other172
communication-not-done-reasonCodes for the reason why a communication did not happen.Other174
communication-request-status-reasonExample 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 CT1418
communication-topicCodes describing the purpose or content of the communication.Other983
compartment-typeWhich type a compartment definition describes.Internal786
composite-measure-scoringThe composite scoring method of the measure.Other773
composition-attestation-modeThe way in which a person authenticated a composition.Internal238
composition-statusThe workflow/clinical status of the composition.Internal241
concept-map-equivalenceThe degree of equivalence between concepts.Internal17
concept-map-relationshipThe relationship between concepts.Internal1408
concept-property-type NThe type of a property value.Internal780
concept-subsumption-outcomeDescription Needed HereInternal1238
conceptmap-unmapped-modeDefines which action to take if there is no match in the group.Internal480
condition-categoryPreferred value set for Condition Categories.Other162
condition-causeExample value set for Cause of Condition codesSNOMED CT965
condition-clinicalPreferred value set for Condition Clinical Status.Other164
condition-codeExample value set for Condition/Problem/Diagnosis codes.SNOMED CT161
condition-courseValue set for clinical course of a disease (how the disease behaves over time).SNOMED CT1463
condition-outcomeExample value set for condition outcomes.SNOMED CT967
condition-precondition-typeKind of precondition for the condition.Internal1439
condition-predecessorExample value set for condition predecessor codes.SNOMED CT966
condition-questionnaire-purposeThe use of a questionnaire.Internal1441
condition-severityPreferred value set for Condition/Diagnosis severity grading.SNOMED CT168
condition-stageExample value set for stages of cancer and other conditions.SNOMED CT170
condition-stage-typeExample value set for the type of stages of cancer and other conditionsSNOMED CT171
condition-ver-statusThe verification status to support or decline the clinical status of the condition or diagnosis.Other166
conditional-delete-status NA code that indicates how the server supports conditional delete.Internal194
conditional-read-status NA code that indicates how the server supports conditional read.Internal200
conformance-expectationDescription Needed HereInternal919
consent-actionThis value set includes sample Consent Action codes.Other753
consent-categoryThis 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, LOINC751
consent-content-classThis value set includes the FHIR resource types, along with some other important content class codesOther, Internal747
consent-content-codeThis example value set contains all LOINC codeLOINC748
consent-data-meaningHow a resource reference is interpreted when testing consent restrictions.Internal759
consent-policyThis value set includes sample Regulatory consent policy types from the US and other regions.Other1014
consent-provision-typeHow a rule statement is applied, such as adding additional consent or removing consent.Internal757
consent-scopeThis value set includes the four Consent scope codes.Other761
consent-state-codesIndicates the state of the consent.Internal755
consent-verificationThis value set includes base Consent Verification codes.Other1468
consistency-typeFluidConsistencyType : 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 CT389
constraint-severity NSHALL applications comply with this constraint?Internal81
contact-point-system NTelecommunications form for contact point.Internal71
contact-point-use NUse of contact point.Internal73
contactentity-typeThis example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.Other416
container-capColor of the container cap.Other850
container-materialThis value set includes SNOMED CT codes for materials that specimen containers are made ofSNOMED CT1400
contract-actionThis value set includes sample Contract Action codes.Other739
contract-actionstatusThis value set contract specific codes for action status.Internal1303
contract-actorroleThis value set includes sample Contract Actor Role codes.Other741
contract-assetcontextThis value set contract specific codes for asset context.Internal1297
contract-assetscopeThis value set contract specific codes for asset scope.Internal1293
contract-assetsubtypeThis value set contract specific codes for asset subtype.Internal1301
contract-assettypeThis value set contract specific codes for asset type.Internal1299
contract-content-derivativeThis 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.Other745
contract-decision-modeThis value set contract specific codes for decision modes.Internal1291
contract-definition-subtypeThis value set contract specific codes for status.Internal1212
contract-definition-typeThis value set contract specific codes for status.Internal1210
contract-expiration-typeThis value set contract specific codes for status.Internal1214
contract-legalstateThis value set contract specific codes for status.Internal1206
contract-party-roleThis value set contract specific codes for offer party participation.Internal1224
contract-publicationstatusThis value set contract specific codes for status.Internal1208
contract-scopeThis value set contract specific codes for scope.Internal1216
contract-security-categoryThis value set contract specific codes for security category.Internal1220
contract-security-classificationThis value set contract specific codes for security classification.Internal1218
contract-security-controlThis value set contract specific codes for security control.Internal1222
contract-signer-typeThis value set includes sample Contract Signer Type codes.Other737
contract-statusThis value set contract specific codes for status.Internal743
contract-subtypeThis value set includes sample Contract Subtype codes.Other731
contract-term-subtypeThis value set includes sample Contract Term SubType codes.Other735
contract-term-typeThis value set includes sample Contract Term Type codes.Other733
contract-typeThis value set includes sample Contract Type codes.Other729
contributor-roleUsed to code the format of the display string.Other0
contributor-summary-sourceUsed to code the producer or rule for creating the display string.Other0
contributor-summary-styleUsed to code the format of the display string.Other0
contributor-summary-typeUsed to code author list statement, contributorship statement, and such.Other0
contributor-typeThe type of contributor.Internal93
coverage-classThis value set includes Coverage Class codes.Other1009
coverage-copay-typeThis value set includes sample Coverage Copayment Type codes.Other527
coverage-financial-exceptionThis value set includes Example Coverage Financial Exception Codes.Other1328
coverage-typeThis value set includes Coverage Type codes.Other520
coverageeligibilityresponse-ex-auth-supportThis value set includes CoverageEligibilityResponse Auth Support codes.Other1393
cpt-allA value set that includes all CPT codesOther1451
currencies NCurrency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html)Other1025
data-absent-reason NUsed to specify why the normally expected content of the data element is missing.Other5
data-types NA 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).Internal22
dataelement-sdcobjectclassThe 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, Other910
dataelement-sdcobjectclasspropertyThe 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, Other911
days-of-week NThe days of the week.Internal512
defined-types NA list of all the concrete types defined in this version of the FHIR specification - Data Types and Resource Types.Internal24
definition-resource-typesA list of all the definition resource types defined in this version of the FHIR specification.Internal1056
definition-statusCodes identifying the lifecycle stage of a definition.Other107
definition-topicHigh-level categorization of the definition, used for searching, sorting, and filtering.Other794
definition-use NStructure Definition Use Codes / KeywordsOther1190
designation-use NDetails of how a designation would be usedSNOMED CT264
detectedissue-categoryKinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc.V3204
detectedissue-mitigation-actionKinds of mitigating actions and observations that can be associated with a detected issue or contraindication, such as 'added concurrent therapy', 'prior therapy documented', etc.V3205
detectedissue-severityIndicates the potential degree of impact of the identified issue on the patient.Internal206
device-actionExample 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 CT425
device-associationstatusThe association status of the device.Internal0
device-nametypeThe type of name the device is referred by.Internal1083
device-operationalstatusThe operational status of the device.Internal0
device-statusThe availability status of the device.Internal209
device-status-reasonThe availability status reason of the device.Other1081
device-typeCodes 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 CT1376
device-usage-statusA coded concept indicating the current status of the Device Usage.Internal214
devicemetric-typeCodes 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.Other645
diagnosis-roleThis value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.Other49
diagnostic-report-statusThe status of the diagnostic report.Internal235
diagnostic-service-sectionsThis value set includes all the codes in HL7 V2 table 0074.V2234
diet-typeCodes 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 CT385
directnessThe quality of how direct the match is.Other1458
discriminator-type NHow an element value is interpreted when discrimination is evaluated.Internal91
distance-unitsUnified Code for Units of Measure (UCUM). This value set includes common UCUM codes for units of distanceFHIR62
doc-section-codesDocument section codes (LOINC codes used in CCDA sections).LOINC237
doc-typecodesFHIR Document Codes - all LOINC codes where scale type = 'DOC'.LOINC240
document-attestation-modeThe way in which a person authenticated a document.Internal0
document-classcodesThis 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.Other, LOINC46
document-mode NWhether the application produces or consumes documents.Internal186
document-reference-statusThe status of the document reference.Internal7
document-relationship-typeThe type of relationship between documents.Internal244
dose-rate-typeThe kind of dose or rate specified.Other981
duration-units NUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR61
edible-substance-typeThis 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 CT1518
eligibility-outcomeThe outcome of the processing.Internal0
eligibilityrequest-purposeA code specifying the types of information being requested.Internal1182
eligibilityresponse-purposeA code specifying the types of information being requested.Internal1184
encounter-admit-sourceThis value set defines a set of codes that can be used to indicate from where the patient came in.Other257
encounter-dietThis value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.Other255
encounter-discharge-dispositionThis value set defines a set of codes that can be used to where the patient left the hospital.Other259
encounter-location-statusThe status of the location.Internal262
encounter-participant-typeThis value set defines a set of codes that can be used to indicate how an individual participates in an encounter.V3, Other250
encounter-reasonThis examples value set defines the set of codes that can be used to indicate reasons for an encounter.SNOMED CT261
encounter-special-arrangementsThis value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit.Other253
encounter-special-courtesyThis value set defines a set of codes that can be used to indicate special courtesies provided to the patient.V3252
encounter-statusCurrent state of the encounter.Internal246
encounter-subject-statusThis example value set defines a set of codes that can be used to indicate the status of the subject within the encounterOther1419
encounter-typeThis 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.Other248
endpoint-connection-typeThis is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.Other498
endpoint-payload-typeThis is an example value set defined by the FHIR project, that could be used to represent possible payload document types.Other496
endpoint-statusThe status of the endpoint.Internal494
enrollment-outcomeThe outcome of the processing.Internal0
enteral-routeEnteralRouteOfAdministration: 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.V3394
entformula-additiveEnteralFormulaAdditiveType: 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.Other392
entformula-typeEnteralFormulaType : 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 CT391
episode-of-care-statusThe status of the episode of care.Internal664
episodeofcare-typeThis example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.Other666
event-capability-mode NThe mode of a message capability statement.Internal182
event-or-request-resource-typesThis value set lists all the event or request resource types defined in this version of the specification.Other1064
event-resource-typesA list of all the event resource types defined in this version of the FHIR specification.Internal1060
event-statusCodes identifying the lifecycle stage of an event.Internal109
event-timing NReal world event relating to the schedule.Internal, V375
evidence-classifier-codeCommonly used classifiers for evidence sets.Other0
evidence-qualityA rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems.Other1020
evidence-report-sectionEvidence Report Section Type.Other1533
evidence-report-typeThe kind of report, such as grouping of classifiers, search results, or human-compiled expression.Other0
ex-benefitcategoryThis value set includes examples of Benefit Category codes.Other1174
ex-diagnosis-on-admissionThis value set includes example Diagnosis on Admission codes.Other1169
ex-diagnosisrelatedgroupThis value set includes example Diagnosis Related Group codes.Other588
ex-diagnosistypeThis value set includes example Diagnosis Type codes.Other590
ex-paymenttypeThis value set includes example Payment Type codes.Other616
ex-procedure-typeThis value set includes example Procedure Type codes.Other1387
ex-program-codeThis value set includes sample Program Reason Span codes.Other576
ex-revenue-centerThis value set includes sample Revenue Center codes.Other594
example-cpt-allA value set that includes all CPT codesOthernull
example-expansionThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINCnull
example-extensionalThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINCnull
example-filterACME Codes for Cholesterol: Plasma only - demonstrating the use of a filter defined in a CodeSystemInternalnull
example-hierarchicalDemonstration of extensions that build a hierarchical containsOthernull
example-intensionalThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINCnull
examplescenario-actor-typeThe type of actor - system or human.Internal858
expansion-parameter-sourceDescription Needed HereInternal1278
expansion-processing-ruleDescription Needed HereInternal1280
explanationofbenefit-statusA code specifying the state of the resource instance.Internal618
expression-languageThe media type of the expression language.Other105
extension-context-type NHow an extension context is interpreted.Internal1012
feeding-deviceMaterials used or needed to feed the patient.Internal, SNOMED CT961
filter-operator NThe kind of operation to perform as a part of a property based filter.Internal478
flag-categoryExample list of general categories for flagged issues. (Not complete or necessarily appropriate.)Other122
flag-codeExample list of detail codes for flagged issues. (Not complete or necessarily appropriate.)SNOMED CT124
flag-priorityThis value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority.Internal950
flag-statusIndicates 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.Internal120
fm-statusThis value set includes Status codes.Internal592
focal-subjectExample 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, V3954
focus-characteristic-codeEvidence focus characteristic code.Other0
food-typeThis 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 CT384
formatcodesThe 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 incompleteOther1
formsThis value set includes a sample set of Forms codes.Other37
fundsreserveThis value set includes sample funds reservation type codes.Other33
gender-identityThis example value set defines a set of codes that can be used to indicate a patient's gender identity.Internal972
goal-acceptance-statusDescription Needed HereInternal917
goal-achievementDescribes the progression, or lack thereof, towards the goal against the target.Other1374
goal-categoryExample codes for grouping goals to use for filtering or presentation.Other275
goal-priorityIndicates the level of importance associated with reaching or sustaining a goal.Other273
goal-relationship-typeDescription Needed HereInternal915
goal-start-eventIdentifies types of events that might trigger the start of a goal.SNOMED CT279
goal-statusCodes that reflect the current state of a goal and whether the goal is still being targeted.Internal271
graph-compartment-ruleHow a compartment must be linked.Internal280
graph-compartment-useDefines how a compartment rule is used.Internal282
group-measurePossible group measure aggregates (E.g. Mean, Median).Internal1345
group-typeTypes of resources that are part of group.Internal284
guidance-module-codeExample guidance module codes.Internal0
guidance-response-statusThe status of a guidance response.Internal817
guide-page-generationA code that indicates how the page is generated.Internal998
handling-conditionSet of handling instructions prior testing of the specimen.Other854
history-absent-reasonCodes describing the reason why a family member's history is not available.Other269
history-statusA code that identifies the status of the family history record.Internal267
hl7-work-groupDescription Needed HereInternal944
http-operationsThe allowable request method or HTTP operation codes.Internal716
http-verb NHTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details.Internal624
icd-10This value set includes sample ICD-10 codes.Internal531
icd-10-proceduresThis value set includes sample ICD-10 Procedure codes.Internal574
identifier-type NA coded type for an identifier that can be used to determine which identifier to use for a specific purpose.V245
identifier-use NIdentifies the purpose for this identifier, if known .Internal57
identity-assuranceLevelThe level of confidence that this link represents the same actual person, based on NIST Authentication Levels.Internal656
imagingstudy-statusThe status of the ImagingStudy.Internal990
immunization-evaluation-dose-statusThe 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.Other301
immunization-evaluation-dose-status-reasonThe 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.Other303
immunization-evaluation-statusThe 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.Internal299
immunization-evaluation-target-diseaseThe 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 CT300
immunization-functionThe 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.V2995
immunization-funding-sourceThe 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.Other293
immunization-originThe 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.Other296
immunization-program-eligibilityThe 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.Other291
immunization-reasonThe 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 CT290
immunization-recommendation-date-criterionThe 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.LOINC308
immunization-recommendation-reasonThe 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 CT307
immunization-recommendation-statusThe 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.Other305
immunization-recommendation-target-diseaseThe 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 CT309
immunization-routeThe 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.V3289
immunization-siteThe 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.V3288
immunization-statusThe 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.Internal295
immunization-status-reasonThe 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.V3992
immunization-subpotent-reasonThe 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.Other993
immunization-target-diseaseThe 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 concepts from the 64572001 (Disease) hierarchy.SNOMED CT1047
implantStatusDescription Needed HereInternal1282
inactiveHL7 v3 ActMood Predicate codes, including inactive codesV3null
insuranceplan-applicabilityWhether the cost applies to in-network or out-of-network providers.Other0
insuranceplan-typeThis example value set defines a set of codes that can be used to indicate a type of insurance plan.Other870
interaction-triggerFHIR RESTful interaction codes used for SubscriptionTopic trigger.Internal1460
inventoryreport-counttypeThe type of count.Internal0
inventoryreport-statusThe status of the InventoryReport.Internal0
invoice-priceComponentTypeCodes indicating the kind of the price component.Internal868
invoice-statusCodes identifying the lifecycle stage of an Invoice.Internal866
iso3166-1-2This value set defines the ISO 3166 Part 1 2-letter codesOthernull
iso3166-1-3This value set defines the ISO 3166 Part 1 3-letter codesOthernull
iso3166-1-NThis value set defines the ISO 3166 Part 1 Numeric codesOthernull
issue-severity NHow the issue affects the success of the action.Internal408
issue-type NA code that describes the type of issue.Internal410
item-typeDistinguishes groups from questions and display text and indicates data type for questions.Internal444
journal-issue-mediumNLM codes Internet or Print.Other1488
jurisdiction NThis 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).Other48
knowledge-capabilityA capability afforded by a knowledge artifact, e.g. shareable, computable, publishable, executableInternal0
knowledge-representation-levelA knowledge representation level, narrative, semi-structured, structured, and executableInternal0
knowledge-resource-typesA list of all the knowledge resource types defined in this version of the FHIR specification.Internal1062
language-preference-typeThis value set defines the set of codes for describing the type or mode of the patient's preferred language.Internal1022
languagesThis value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)Other20
library-typeThe type of knowledge asset this library contains.Other763
link-type NThe type of link between this patient resource and another patient resource.Internal423
linkage-typeUsed to distinguish different roles a resource can play within a set of linked resources.Internal314
lipid-ldl-codesLDL Cholesterol codes - measured or calculatedLOINC0
list-empty-reasonGeneral 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).Other322
list-example-codesExample use codes for the List resource - typical kinds of use.Other316
list-item-flagExample 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.Other320
list-modeThe processing mode that applies to this list.Internal318
list-orderBase values for the order of the items in a list resource.Other324
list-statusThe current state of the list.Internal326
location-modeIndicates whether a resource instance represents a specific location or a class of locations.Internal330
location-physical-typeThis example value set defines a set of codes that can be used to indicate the physical form of the Location.Other328
location-statusIndicates whether the location is still in use.Internal332
manifestation-or-symptomExample value set for Manifestation and Symptom codes.SNOMED CT169
map-group-type-modeIf this is the default rule set to apply for the source type, or this combination of types.Internal687
map-input-modeMode for this instance of data.Internal677
map-model-modeHow the referenced structure is used in this mapping.Internal675
map-source-list-modeIf field is a list, how to manage the source.Internal683
map-target-list-modeIf field is a list, how to manage the production.Internal685
map-transformHow data is copied/created.Internal681
marital-status NThis value set defines the set of codes that can be used to indicate the marital status of a person.V329
match-gradeDescription Needed HereInternal970
measure-aggregate-methodAggregation method for a measure (e.g. sum, average, median, minimum, maximum, count)Internal0
measure-data-usageThe intended usage for supplemental data elements in the measure.Other771
measure-group-exampleExample Measure Groups for the Measure Resource.Other0
measure-improvement-notationObservation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.Other1236
measure-populationThe type of population.Other765
measure-report-statusThe status of the measure report.Internal776
measure-report-typeThe type of the measure report.Internal778
measure-scoringThe scoring type of the measure.Other767
measure-scoring-unitThis is an example value set illustrating some typical scoring units used in quality measure specifications.FHIR0
measure-stratifier-exampleIdentifier subgroups in a population for measuring purposes.Other0
measure-supplemental-data-exampleSupplemental data in a population for measuring purposes.Other0
measure-typeThe type of measure (includes codes from 2.16.840.1.113883.1.11.20368).Other769
measurement-propertyThis 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 CT0
measurereport-stratifier-value-exampleExample Measure Stratification Value for MeasureReports Resource.Other0
med-admin-perform-functionMedicationAdministration Performer Function CodesOther349
medication-admin-locationMedicationAdministration Location CodesOther1509
medication-admin-statusMedicationAdministration Status CodesInternal340
medication-as-needed-reasonThis value set includes all clinical findings from SNOMED CT - provided as an exemplar value set.SNOMED CT96
medication-codesThis value set includes all drug or medicament substance codes and all pharmaceutical/biologic products from SNOMED CT - provided as an exemplar value set.SNOMED CT375
medication-cost-categoryMedication Cost Category CodesOther0
medication-dose-aidMedication Dose AidsInternal0
medication-form-codesThis value set includes all dose form codes from SNOMED CT - provided as an exemplar.SNOMED CT374
medication-ingredientstrengthMedication Ingredient Strength CodesInternal1426
medication-statusMedication Status CodesInternal376
medication-usage-adherenceMedicationUsage Adherence CodesInternal0
medication-usage-admin-locationMedicationUsage Administration Location CodesOther1516
medication-usage-statusMedicationUsage Status CodesInternal1422
medicationdispense-admin-locationMedicationDispense Administration Location CodesOther1512
medicationdispense-performer-functionMedicationDispense Performer Function CodesOther1318
medicationdispense-statusMedicationDispense Status CodesInternal1312
medicationdispense-status-reasonMedicationDispense Status Reason CodesOther1316
medicationknowledge-characteristicMedicationKnowledge Characteristic CodesOther1337
medicationknowledge-package-typeThis value set includes all unit of presentation codes from SNOMED CT - provided as an exemplar.SNOMED CT1339
medicationknowledge-statusMedicationKnowledge Status CodesOther1335
medicationrequest-admin-locationMedicationRequest Administration Location CodesOther1514
medicationrequest-course-of-therapyMedicationRequest Course of Therapy CodesOther1326
medicationrequest-intentMedicationRequest Intent CodesInternal1321
medicationrequest-statusMedicationRequest Status CodesInternal1320
medicationrequest-status-reasonMedicationRequest Status Reason CodesOther1324
message-eventsOne of the message events defined as part of this version of FHIR.Internal26
message-reason-encounterExample Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.Other378
message-significance-categoryThe impact of the content of a message.Internal188
message-transport NThe protocol used for message transport.Other184
messageheader-response-requestHL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.Internal924
metric-calibration-stateDescribes the state of a metric calibration.Internal652
metric-calibration-typeDescribes the type of a metric calibration.Internal650
metric-categoryDescribes the category of the metric.Internal648
metric-colorDescribes the typical color of representation.Internal654
metric-operational-statusDescribes the operational status of the DeviceMetric.Internal646
mimetypes NThis value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13)Other1024
missing-tooth-reasonThis value set includes sample Missing Tooth Reason codes.Other534
modified-foodtypeTextureModifiedFoodType: 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 CT388
name-assembly-orderA code that represents the preferred display order of the components of a human name.Other, V2, V3913
name-part-qualifierA set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type.V3906
name-use NThe use of a human name.Internal65
name-v3-representationA set of codes for each different representation of a name.V3909
namingsystem-identifier-typeIdentifies the style of unique identifier used to identify a namespace.Internal492
namingsystem-typeIdentifies the purpose of the naming system.Internal490
narrative-statusThe status of a resource narrative.Internal55
network-typeThe type of network access point of this agent in the audit event.Internal456
nhin-purposeofuseThis 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.Othernull
not-consumed-reasonThis 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 CT1519
note-typeThe presentation types of notes.Internal15
nutrient-codeNutrientModifier : 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 CT386
nutrition-product-categoryThis 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 CT0
nutrition-product-nutrientThis 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 CT0
nutritionproduct-statusCodes identifying the lifecycle stage of a product.Internal1529
object-lifecycle-eventsThis 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; Other0
object-roleCode representing the role the entity played in the audit event.Other460
observation-categoryObservation Category codes.Other403
observation-codesThis value set includes all LOINC codesLOINC396
observation-interpretation NA 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.V3399
observation-methodsObservation 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 CT395
observation-range-categoryCodes identifying the category of observation range.Internal1333
observation-statisticsDescription Needed HereInternal405
observation-status NCodes providing the status of an observation.Internal400
observation-vitalsignresultThis 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).LOINC62
operation-kind NWhether an operation is a normal operation or a query.Internal506
operation-parameter-use NWhether an operation parameter is an input or an output parameter.Internal508
organization-roleThis example value set defines a set of codes that can be used to indicate the role of one Organization in relation to another.Internal880
organization-typeThis example value set defines a set of codes that can be used to indicate a type of organization.Other414
orientation-typeType for orientation.Internal987
parent-relationship-codesThe 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.V3921
participant-roleRoles of participants that may be included in a care team. Defined as: Healthcare professional (occupation) or Services (qualifier value).SNOMED CT152
participantrequiredIs the Participant required to attend the appointment.Internal488
participation-role-typeThis 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, DICOM, V354
participationstatusThe Participation status of an appointment.Internal486
patient-contactrelationship NThe nature of the relationship between the patient and the contact person.V21130
payeetypeThis value set includes sample Payee Type codes.Other31
payment-adjustment-reasonThis value set includes smattering of Payment Adjustment Reason codes.Other600
payment-outcomeThe outcome of the processing.Internal0
payment-statusThis value set includes a sample set of Payment Status codes.Other643
payment-typeThis value set includes sample Payment Type codes.Other641
performer-functionThe types of involvement of the performer in the Event.V3null
performer-roleThis example value set defines the set of codes that can be used to indicate a role of a procedure performer.SNOMED CT433
permission-statusCodes identifying the lifecycle stage of a product.Internal1531
permitted-data-typePermitted data type for observation value.Internal1331
plan-definition-typeThe type of PlanDefinition.Other797
postal-address-useUses of an address not included in Address.use.V3908
prepare-patient-prior-specimen-collectionChecks on the patient prior specimen collection. All SNOMED CT concepts descendants of 703763000 |Precondition value (qualifier value)|SNOMED CT1399
probability-distribution-typeCodes specifying the type of probability distribution.V3907
procedure-categoryProcedure Category code: A selection of relevant SNOMED CT codes.SNOMED CT430
procedure-codeProcedure Code: All SNOMED CT procedure codes.SNOMED CT427
procedure-followupProcedure follow up codes: A selection of SNOMED CT codes relevant to procedure follow up.SNOMED CT429
procedure-not-performed-reasonSituation 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) as well as 410536001 Contraindicated (qualifier value).SNOMED CT431
procedure-outcomeProcedure Outcome code: A selection of relevant SNOMED CT codes.SNOMED CT428
procedure-progress-status-codesThis 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.Internal946
procedure-reasonThis example value set defines the set of codes that can be used to indicate a reason for a procedure.SNOMED CT432
process-priorityThis value set includes the financial processing priority codes.Other552
product-categoryBiologically Derived Product Category.Internal900
product-statusCodes identifying the lifecycle stage of a product.Internal902
product-storage-scaleBiologicallyDerived Product Storage Scale.Internal904
programThis value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties.Other1383
property-representation NHow a property is represented when serialized.Internal87
provenance-activity-typeThis 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.Other, Internal, V3438
provenance-entity-roleHow an entity was used in an activity.Internal436
provenance-history-agent-typeTypes of roles indicating how a particular agent was involved with the creation or modification of a resource for use when exposing event historyV3927
provenance-history-record-activityCodes for Provenance activities that are relevant when capturing event history for resources.V3926
provider-qualificationThis value set includes sample Provider Qualification codes.Other570
provider-taxonomyNUCC Healthcare Provider Taxonomy codesOther51
publication-status NThe lifecycle status of an artifact.Internal3
published-in-typeThe type of publication such as book, database, or journal.Other0
quality-typeType for quality report.Internal228
quantity-comparator NHow the Quantity should be understood and represented.Internal59
questionnaire-answer-constraintCodes that describe the types of constraints possible on a question item that has a list of permitted answersInternal0
questionnaire-answersExample list of codes for answers to questions. (Not complete or necessarily appropriate.)SNOMED CT446
questionnaire-answers-statusLifecycle status of the questionnaire response.Internalrequired
questionnaire-disabled-displayCodes that guide the display of disabled questionnaire itemsInternal0
questionnaire-display-categoryCodes defining the purpose of a Questionnaire item of type 'display'.Internal935
questionnaire-enable-behaviorControls how multiple enableWhen values are interpreted - whether all or any must be true.Internal1007
questionnaire-enable-operatorThe criteria by which a question is enabled.Internal1005
questionnaire-item-controlStarter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire.Internal931
questionnaire-questionsExample list of codes for questions and groups of questions. (Not necessarily complete or appropriate.)LOINC443
questionnaire-usage-modeDescription Needed HereInternal937
questionnaireresponse-modeCodes describing how the QuestionnaireResponse was populatedV31290
reaction-event-certaintyDescription Needed HereInternal942
reaction-event-severityClinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.Internal135
reason-medication-given-codesThis 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.Other344
reason-medication-not-given-codesThis 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 CT342
reason-medication-status-codesThis value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplarSNOMED CT369
recommendation-strengthA rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems.Other1021
reference-handling-policy NA set of flags that defines how references are supported.Internal202
reference-version-rules NWhether a reference needs to be version specific or version independent, or whether either can be used.Internal89
referencerange-appliestoThis value set defines a set of codes that can be used to indicate the particular target population the reference range applies to.Other, SNOMED CT407
referencerange-meaningThis 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.Other397
rejection-criteriaCriterion for rejection of the specimen by laboratory.Other856
related-artifact-typeThe type of relationship to the related artifact.Internal99
related-claim-relationshipThis value set includes sample Related Claim Relationship codes.Other568
relatedperson-relationshiptypeA set of codes that can be used to indicate the relationship between a Patient and a Related Person.V2, V3449
relationshipThis value set includes the Patient to subscriber relationship codes.Internal35
remittance-outcomeThe outcome of the processing.Internal13
report-action-result-codesThe results of executing an action.Internal720
report-codesThis value set includes LOINC codes that relate to Diagnostic Observations.LOINC233
report-participant-typeThe type of participant.Internal722
report-relation-typeThe type of relationship between reports.Internal0
report-result-codesThe reported execution result.Internal718
report-status-codesThe current status of the test report.Internal724
repository-typeType for access of external URI.Internal230
request-intentCodes indicating the degree of authority/intentionality associated with a request.Internal113
request-priorityIdentifies the level of importance to be assigned to actioning the request.Internal115
request-resource-typesA list of all the request resource types defined in this version of the FHIR specification.Internal1058
request-statusCodes identifying the lifecycle stage of a request.Internal111
research-study-objective-typeCodes for the kind of study objective.Other823
research-study-phaseCodes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation.Other821
research-study-prim-purp-typeCodes for the main intent of the study.Other827
research-study-reason-stoppedCodes for why the study ended prematurely.Other825
research-study-statusCodes that convey the current status of the research study.Internal819
research-subject-milestoneIndicates the progression of a study subject through the study milestones.Other1474
research-subject-state-typeIdentifies the kind of state being refered to.Other1470
resource-aggregation-mode NHow resource references can be aggregated.Internal85
resource-security-categoryDescription Needed HereInternal1403
resource-slicing-rules NHow slices are interpreted when evaluating an instance.Internal83
resource-statusThe master set of status codes used throughout FHIR. All status codes are mapped to one of these codes.Internal117
resource-types NOne of the resource types defined as part of this version of FHIR.Internal27
resource-validation-modeDescription Needed HereInternal118
response-codeThe kind of response to a message.Internal380
restful-capability-mode NThe mode of a RESTful capability statement.Internal176
restful-security-service NTypes of security services used with FHIR.Other178
risk-probabilityCodes representing the likelihood of a particular outcome in a risk assessment.Other450
route-codesThis value set includes all Route codes from SNOMED CT - provided as an exemplar.SNOMED CT98
search-comparatorWhat Search Comparator Codes are supported in search.Internal637
search-entry-mode NWhy 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.Internal622
search-modifier-codeA supported modifier for a search parameter.Internal639
search-param-type NData types allowed to be used for search parameters.Internal11
search-xpath-usageHow a search parameter relates to the set of elements returned by evaluating its xpath query.Internal635
secondary-findingCodes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding.Internal1285
security-labels NA single value set for all security labels defined by FHIR.Other47
security-role-typeThis 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, V3978
security-source-typeThe type of process where the audit event originated from.Other0
sequence-quality-methodThis value set includes sequence quality methodOther223
sequence-quality-standardSequenceThis value set includes sequence quality standardOther222
sequence-referenceSeqThis value set includes all Reference codesOther221
sequence-typeType if a sequence -- DNA, RNA, or amino acid sequence.Internal219
series-performer-functionPerformer function of an agent in an imaging study seriesV3989
service-categoryThis value set defines an example set of codes that can be used to classify groupings of service-types/specialties.Other516
service-placeThis value set includes a smattering of Service Place codes.Other564
service-provision-conditionsThe code(s) that detail the conditions under which the healthcare service is available/offered.Other514
service-referral-methodThe methods of referral can be used when referring to a specific HealthCareService resource.Other510
service-typeThis value set defines an example set of codes of service-types.Other518
service-usclsThis value set includes a smattering of USCLS codes.Other542
servicerequest-categoryAn example value set of SNOMED CT concepts that can classify a requested serviceSNOMED CT434
servicerequest-orderdetailAn 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 orderSNOMED CT435
sibling-relationship-codesThe 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.V3922
signature-typeThe 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.Other63
slotstatusThe free/busy status of the slot.Internal482
smart-capabilitiesCodes that define what the server is capable of.Other1018
sort-directionThe possible sort directions, ascending or descending.Internal979
spdx-licenseThe 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/).Internal1026
special-valuesA set of generally useful codes defined so they can be included in value sets.Other9
specimen-collectionActions that can be taken for the collection of specimen from a subject.SNOMED CT1398
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 CT468
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.Other939
specimen-contained-preferenceDegree of preference of a type of conditioned specimen.Internal852
specimen-container-typeContainers 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 CT470
specimen-processing-procedureThe technique that is used to perform the process or preserve the specimen.V2469
specimen-statusCodes providing the status/availability of a specimen.Internal471
standards-statusDescription Needed HereInternal1365
state-change-reasonIndicates why the state of the subject changed.Other1476
statistic-model-codeStatistic Model Code.Other0
statistic-model-methodStatistic Model Method.Other0
statistic-typeThe type of a specific statistic.Other1410
strand-typeType for strand.Internal985
structure-definition-kind NDefines the type of structure that a definition is describing.Internal668
study-typeThe type of study the evidence was derived from.Other1349
subject-typePossible types of subjects.Internal775
submit-data-update-typeConcepts for how a measure report consumer and receiver coordinate data exchange updates. The choices are snapshot or incremental updatesInternal0
subscriber-relationshipThis value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient).Other1385
subscription-channel-typeCore-defined FHIR channel types allowed for use in Subscriptions.Other500
subscription-errorCodes to represent subscription error detailsOther1437
subscription-notification-typeThe type of notification represented by the status message.Internal1523
subscription-payload-contentCodes to represent how much resource content to send in the notification payload.Internal1435
subscription-search-modifierFHIR search modifiers allowed for use in Subscriptions and SubscriptionTopics.Other1525
subscription-stateState values for FHIR Subscriptions.Other1521
subscription-url-locationThe location, in Bundle.entry, where URLs for resources should be located.Internal0
subscriptiontopic-cr-behaviorBehavior a server can exhibit when a criteria state does not exist (e.g., state prior to a create or after a delete).Internal0
substance-categorySubstance category codesOther476
substance-codeThis 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 CT473
substance-statusA code to indicate if the substance is actively used.Internal474
supplement-typeSupplementType : 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 CT390
supply-itemThis 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 CT699
supplydelivery-statusStatus of the supply delivery.Internal700
supplydelivery-typeThis value sets refers to a specific supply item.Other702
supplyrequest-kindThis value sets refers to a Category of supply.Other693
supplyrequest-reasonThe reason why the supply item was requested.Other697
supplyrequest-statusStatus of the supply request.Internal695
surfaceThis value set includes a smattering of FDI tooth surface codes.Other546
synthesis-typeTypes of combining results from a body of evidence (eg. summary data meta-analysis).Other1347
system-restful-interaction NOperations supported by REST at the system level.Internal181
task-codeCodes indicating the type of action that is expected to be performedInternal1396
task-intentDistinguishes whether the task is a proposal, plan or full order.Internal1240
task-statusThe current status of the task.Internal790
template-status-codeDescription Needed HereInternal923
testscript-operation-codesThis value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.Other704
testscript-profile-destination-typesThis 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.Other714
testscript-profile-origin-typesThis 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.Other712
testscript-scope-conformance-codesThe expectation of whether the test must pass for the system to be considered conformant with the artifact.Other1536
testscript-scope-phase-codesThe phase of testing for this artifact.Other1538
texture-codeTextureModifier: 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 CT387
timezonesIANA Timezone CodesOther1036
timing-abbreviationCode for a known / defined timing pattern.Other, V378
title-typeUsed to express the reason and specific aspect for the variant title, such as language and specific language.Other1492
toothThis value set includes a smattering of FDI oral site codes.Other540
trigger-typeThe type of trigger.Internal103
type-derivation-rule NHow a type relates to its baseDefinition.Internal673
type-restful-interaction NOperations supported by REST at the type or instance level.Internal180
ucum-bodylengthUCUM units for recording body length measures such as height and head circumferenceFHIR958
ucum-bodytempUCUM units for recording Body TemperatureFHIR957
ucum-bodyweightUCUM units for recording Body WeightFHIR956
ucum-commonCommonly encountered UCUM units (for purposes of helping populate look ups.FHIRnull
ucum-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR912
ucum-vitals-commonCommon UCUM units for recording Vital SignsFHIR955
udi-entry-typeCodes to identify how UDI data was entered.Internal211
units-of-time NA unit of time (units from UCUM).FHIR77
usage-context-typeA code that specifies a type of context being specified by a usage context.Other101
use-contextThis 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 CT28
vaccine-codeThis identifies the vaccine substance administered - CVX codes.Internal, Other22
variable-handlingThe handling of the variable in statistical analysis for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive).Internal0
variable-roleThe role that the assertion variable plays.Other1456
verificationresult-can-push-updatesAbility of the primary source to push updates/alertsOther896
verificationresult-communication-methodAttested 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.Other1401
verificationresult-failure-actionThe result if validation failsOther890
verificationresult-needThe frequency with which the target must be validatedOther882
verificationresult-primary-source-typeType of the validation primary sourceOther892
verificationresult-push-type-availableType of alerts/updates the primary source can sendOther898
verificationresult-statusThe validation status of the targetInternal884
verificationresult-validation-processThe primary process by which the target is validatedOther888
verificationresult-validation-statusStatus of the validation of the target against the primary sourceOther894
verificationresult-validation-typeWhat the target is validated againstOther886
versioning-policy NHow the system supports versioning for a resource.Internal190
vision-base-codesA coded concept listing the base codes.Internal662
vision-eye-codesA coded concept listing the eye codes.Internal660
vision-productThis value set includes a smattering of Prescription Product codes.Other658
written-languageThis 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 languagesOthernull
yesnodontknowFor Capturing simple yes-no-don't know answersOthernull
Namespace: http://dicom.nema.org/medical/dicom/current/output/chtml/part16
sect_CID_29.html Transitive closure of CID 29 AcquisitionModalityDICOM19