DSTU2 Ballot Source
This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). 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
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 (implicit code system), and some do both. Any implicit code systems are case sensitive, though FHIR will never define codes that only differ by case.
| Name | Definition | Source | Id | Usage |
| Namespace: http://hl7.org/fhir/vs | ||||
| ActIncidentCode | This value set includes sample ActIncidentCode codes. | Internal | 446 | core |
| ActInvoiceGroupCode | This value set includes sample ActInvoiceGroupCode codes. | Internal | 462 | core |
| NT-link | The presentation types of notes | Internal | 472 | core |
| RS-link | The outcome of the processing. | Internal | 467 | core |
| actionlist | List of allowable action which this resource can request | Internal | 1676 | core |
| additionalmaterials | This value set includes sample additional material type codes. | Internal | 447 | core |
| address-use | The use of an address | Internal | 16 | core |
| adjudication | This value set includes a smattering of Adjudication codes | Internal | 468 | core |
| adjudication-error | This value set includes a smattering of adjudication codes | Internal | 471 | core |
| adjustment-reason | This value set includes smattering of a Adjustment Reason codes | Internal | 469 | core |
| administration-method-codes | This value set includes some introduction (procedure) codes from SNOMED CT - provided as an exemplar | SNOMED CT | 94 | core |
| administrative-gender | The gender of a person used for administrative purposes | Internal | 24 | core |
| allergy-intolerance-category | Category of an identified Substance | Internal | 481 | core |
| allergy-intolerance-criticality | Estimate of the potential clinical harm, or seriousness, of a reaction to an identified Substance | Internal | 479 | core |
| allergy-intolerance-status | Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified Substance | Internal | 478 | core |
| allergy-intolerance-type | Identification of the underlying physiological mechanism for a Reaction Risk | Internal | 480 | core |
| animal-breeds | This example value set defines a set of codes that can be used to indicate breeds of species. | Internal | 134 | core |
| 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 | core |
| animal-species | This example value set defines a set of codes that can be used to indicate species of animal patients. | Internal | 133 | core |
| answer-format | The expected format of an answer | Internal | 254 | core |
| anzsco-occupations | Developed for use in the collection, analysis and dissemination of occupation statistics in Australia and New Zealand | External | 156 | core |
| appointmentstatus | The free/busy status of an appointment | Internal | 360 | core |
| approach-site-codes | This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar | SNOMED CT | 95 | core |
| audit-event-action | Indicator for type of action performed during the event that generated the audit. | Internal | 1476 | core |
| audit-event-outcome | Indicates whether the event succeeded or failed | Internal | 1477 | core |
| audit-event-sensitivity | The sensitivity of an object in a secuity event resource. May also encompass confidentiality and rudimentary access control | V3 | 1485 | core |
| audit-event-sub-type | More detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions | DICOM, FHIR | 1483 | core |
| audit-event-type | Event Types for Audit Events - defined by DICOM with some FHIR specific additions | Internal, DICOM | 1482 | core |
| audit-source-type | The type of process where the audit event originated from | Internal | 1484 | core |
| base-codes | A coded concept listing the base codes. | Internal | 558 | core |
| basic-resource-type | This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. | Internal | 439 | core |
| binding-conformance | Binding conformance for applications | Internal | 144 | core |
| binding-strength | Indication of the degree of conformance expectations associated with a binding | Internal | 1552 | core |
| body-site | This value set includes all the "Anatomical Structure" SNOMED CT codes (i.e. codes with an is-a relationship with 91723000: Anatomical structure) | SNOMED CT | 62 | core |
| bodysite-relative-location | SNOMED-CT concepts modifying the anatomic location | SNOMED CT | 1917 | core |
| bundle-type | Indicates the purpose of a bundle- how it was intended to be used | Internal | 493 | core |
| c80-doc-classcodes | This is the code specifying the high-level kind of document (e.g., Prescription, Discharge Summary, Report, etc.). The Document Class value set is reproduced from HITSP C80 Table 2-144 Document Class Value Set Definition. Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests. | LOINC | 46 | core |
| c80-doc-typecodes | This is the code specifying the precise type of document (e.g., Pulmonary History and Physical, Discharge Summary, Ultrasound Report, etc.). The Document Type value set includes all LOINC values listed in HITSP C80 Table 2-144 Document Class Value Set Definition above used for Document Class, and all LOINC values whose SCALE is DOC in the LOINC database. | LOINC | 47 | core |
| c80-facilitycodes | This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147. | SNOMED CT | 67 | core |
| c80-practice-codes | This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition. | SNOMED CT | 72 | core |
| care-plan-activity-category | High-level categorization of the type of activity in a care plan. | Internal | 39 | core |
| care-plan-activity-status | Indicates where the activity is at in its overall life cycle | Internal | 41 | core |
| care-plan-goal-status | Indicates whether the goal has been met and is still being targeted | Internal | 38 | core |
| care-plan-status | Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record. | Internal | 36 | core |
| classification-or-context | Identifies whether a useContext represents a context or classification for the element | Internal | 2143 | sdc |
| 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 | core |
| clinical-impression-status | The workflow state of a clinical impression | Internal | 2023 | core |
| communication-request-status | The status of the communication | Internal | 495 | core |
| communication-status | The status of the communication | Internal | 539 | core |
| composition-attestation-mode | The way in which a person authenticated a composition | Internal | 331 | core |
| composition-status | The workflow/clinical status of the composition | Internal | 334 | core |
| concept-equivalence | The degree of equivalence between concepts | Internal | 306 | core |
| cond-uslab-reasonforstudy | This value set includes all ICD-9CM and ICD-10CM concepts and is part of the of the The USLabOrder and USLabReport Implementation Guides. This content may not be published ( EH:Todo - whether and how can display this) | Other | 560 | uslab |
| condition-category | Example value set for Condition (Problem/Diagnosis) Categories | Internal | 224 | core |
| condition-cause | Example value set for Cause of Condition codes | SNOMED CT | 2025 | core |
| condition-code | Example value set for Condition/Problem/Diagnosis codes | SNOMED CT | 313 | core |
| condition-predecessor | Example value set for Condition Predecessor codes | SNOMED CT | 2026 | core |
| condition-severity | Example value set for Condition/Diagnosis severity grading | SNOMED CT | 227 | core |
| condition-state | Enumeration indicating whether the condition is currently active, inactive, or has resolved active| inactive| resolved | Internal | 1469 | core |
| condition-status | The clinical status of the Condition or diagnosis | Internal | 1848 | core |
| conformance-expectation | Indicates the degree of adherence to a specified behavior or capability expected in order for a system to be deemed conformant with a specification | Internal | 550 | core |
| conformance-resource-status | The lifecycle status of a Value Set or Concept Map | Internal | 1549 | core |
| consistency-type | FluidConsistencyType : Codes used to represent the consistency of fluids and liquids provided to the patient. This value set includes all the children of SNOMED CT Concepts from SCTID(US Extension): 435681000124103 Dietary liquid consistency diet (regime/therapy) and is provided as a suggestive example | SNOMED CT | 421 | core |
| constraint-severity | SHALL applications comply with this constraint? | Internal | 146 | core |
| contact-point-system | Telecommunications form for contact point | Internal | 425 | core |
| contact-point-use | Use of contact point | Internal | 426 | core |
| 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 | core |
| contract-action | This value set includes sample Contract Action codes. | External | 1553 | core |
| contract-actorrole | This value set includes sample Contract Actor Role codes. | External | 1555 | core |
| contract-signer-type | The Digital Signature Purposes, an indication of the reason an entity signs a document. This is included in the signed information and can be used when determining accountability for various actions concerning the document. Examples include: author, transcriptionist/recorder, and witness. | Internal | 513 | core |
| contract-subtype | This value set includes sample Contract Subtype codes. | Internal | 441 | core |
| contract-term-subtype | This value set includes sample Contract Term SubType codes. | Internal | 443 | core |
| contract-term-type | This value set includes sample Contract Term Type codes. | Internal | 442 | core |
| contract-type | This value set includes sample Contract Type codes. | Internal | 440 | core |
| contraindication-category | Kinds of contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. | V3 | 401 | core |
| contraindication-mitigation-action | Kinds of mitigating actions and observations that can be associated with a contraindicaiton, such as 'added concurrent therapy', 'prior therapy documented', etc. | V3 | 402 | core |
| daf-bodysite | This identifies the body site at which the substance was administered | SNOMED CT | 9 | daf |
| daf-concern-status | The clinical status of the Condition or diagnosis - that is, the status of the concern about the problem | SNOMED CT | 68 | daf |
| daf-cvx | This identifies the vaccine substance administered - CVX codes | Other | 22 | daf, cqf |
| daf-encounter-dischargedisposition | Discharge Disposition - NUBC manual UB-04, UB form locator 17 | Other | 2090 | daf |
| daf-encounter-reason | Encounter Diagnoses: a specific code indicating type of service provided: SNOMED CT, ICD-10-AM, or CPT | SNOMED CT, Other | 571 | daf, cqf |
| daf-encounter-type | The type of encounter: a specific code indicating type of service provided, from CPT | Other | 1582 | daf, cqf |
| daf-ethnicity | Whether the patient is hispanic or not | V3 | 837 | daf, cqf |
| daf-medication-codes | All prescribable medication formulations represented using either a 'generic' or 'brand-specific' concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form) | Other | 4 | daf |
| daf-medication-route | Route of Administration value set is based upon FDA Drug Registration and Listing Database (FDA Orange Book) which are used in FDA structured product and labelling (SPL) | Other | 11 | daf |
| daf-problem | This describes the problem. Diagnosis/Problem List is broadly defined as a series of brief statements that catalog a patient's medical, nursing, dental, social, preventative and psychiatric events and issues that are relevant to that patient's healthcare (e.g., signs, symptoms, and defined conditions) | SNOMED CT | 4 | daf, cqf |
| daf-procedure-type | This example value set defines a set of codes that can be used to indicate the type of procedure: a specific code indicating type of procedure performed, from CPT, SNOMED CT, ICD10-PCS. | Other, SNOMED CT | 1713 | daf, cqf |
| daf-product-form | This is the physical form of the product as presented to the individual. For example: tablet, capsule, liquid or ointment. NCI concept code for pharmaceutical dosage form: C42636 | Other | 11 | daf |
| daf-race | Meaningful use race code. The 5 base codes (see http://forum.sitenv.org/viewtopic.php?f=16&t=23&sid=8fb101254557843fa05ac94d8d83a095) from PHIN VADS https://phinvads.cdc.gov/vads/ViewValueSet.action?id=94E75E17-176B-DE11-9B52-0015173D1785 (oid: 2.16.840.1.113883.1.11.14914) | V3 | 14914 | daf, cqf |
| daf-substance | A substance or other type of agent (e.g., sunshine) that may be associated with an intolerance reaction event or a propensity to such an event. These concepts are expected to be at a more general level of abstraction (ingredients versus more specific formulations). This value set is quite general and includes concepts that may never cause an adverse event, particularly the included SNOMED CT concepts. The code system-specific value sets in this grouping value set are intended to provide broad coverage of all kinds of agents, but the expectation for use is that the chosen concept identifier for a substance should be appropriately specific and drawn from the available code systems in the following priority order: NDFRT, then RXNORM, then UNII, then SNOMED CT. This overarching grouping value set is intended to support identification of drug classes, individual medication ingredients, foods, general substances and environmental entities | 1 | daf | |
| daf-substance-ndfrt | All ND-FRT NUIs for concepts that are subsumed by 'Mechanism of Action - N0000000223', 'Physiologic Effect - N0000009802' or 'Chemical Structure - N0000000002' | Other | 18 | ?? |
| daf-substance-rxnorm | All RxNorm codes that have TTY = IN,PIN,MIN,BN, but TTY != OCD | Other | 7 | ?? |
| daf-substance-sct | SNOMED CT Substance concepts Other Than Clinical Drug Substances that are not represented by RXNORM drug concepts or FDA UNII substance concepts. This value set is meant to be quite broad and includes many substances that may never be prescribed or be a reactant. It does not remove all overlap with RXNORM and UNII; for those concepts, the alternative code system should be chosen | SNOMED CT | 9 | ?? |
| daf-substance-unii | All UNII codes | Other | 20 | ?? |
| data-absent-reason | Used to specify why the normally expected content of the data element is missing | Internal | 2 | core |
| data-types | The type of an element - one of the FHIR data types | Internal | 3 | core |
| dataelement-sdcobjectclass | The allowed codes for identifying the ISO 11179 ObjectClass for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. | SNOMED CT, LOINC, Other | 396 | elementdefinition-11179 |
| dataelement-sdcobjectclassproperty | The allowed codes for identifying the ISO 11179 ObjectClass Property for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. | SNOMED CT, LOINC, Other | 397 | elementdefinition-11179 |
| dataelement-specificity | Indicates the degree of precision of the data element definition | Internal | 1559 | core |
| days-of-week | The days of the week | Internal | 1928 | core |
| defined-types | Either a resource or a data type | Internal | 5 | core |
| designation-use | Details of how a designation would be used | SNOMED CT | 430 | core |
| device-action | Example value set for Procedure Device Action code (what happened to a device during a procedure | Internal | 1866 | core |
| device-use-request-priority | Codes representing the priority of the request | Internal | 499 | core |
| device-use-request-status | Codes representing the status of the request | Internal | 497 | core |
| devicestatus | The availability status of the device | Internal | 1916 | core |
| dex-mimetype | The allowed codes for identifying the ISO 11179 ObjectClass Property for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. | SNOMED CT, LOINC, Other | 1581 | sdc |
| diagnostic-order-event | Additional information about an event that occurred to a diagnostic order | SNOMED CT | 2139 | core |
| diagnostic-order-priority | The clinical priority of a diagnostic order | Internal | 271 | core |
| diagnostic-order-status | The status of a diagnostic order | Internal | 207 | core |
| diagnostic-report-status | The status of the diagnostic report as a whole | Internal | 341 | core |
| diagnostic-requests | This value set includes all the LOINC Order codes | LOINC | 59 | core |
| diagnostic-service-sections | This value set includes all the codes in HL7 v2 table 0074 | V2 | 61 | core |
| dicm-402-roleid | Audit Active Participant Role ID Code | DICOM | 366 | core |
| diet-type | DietCode : Codes that can be used to indicate the type of food being ordered for a patient. This value set includes all children of SNOMED CT Concepts (US Extension and Core) from SCTID 182922004 Dietary regime (Therapeutic or Preventive Procedure) and is provided as a suggestive example | SNOMED CT | 417 | core |
| digital-media-subtype | Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it | Internal, SNOMED CT | 1624 | core |
| digital-media-type | Whether the Media is a photo, video, or audio | Internal | 1623 | core |
| do-uslab-event | US Realm ambulatory care event codes that correspond the Use cases outlined in the USLabOrder Implementation Guide | Internal | 511 | uslab, cqf |
| doc-section-codes | Document section codes - all LOINC codes | LOINC | 330 | core |
| doc-typecodes | FHIR Document Codes - all LOINC codes where scale_type = 'DOC' | LOINC | 65 | core |
| document-mode | Whether the application produces or consumes documents | Internal | 47 | core |
| document-reference-status | The status of the document reference | Internal | 67 | core |
| document-relationship-type | The type of relationship between documents | Internal | 328 | core |
| 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 | core |
| encounter-class | Classification of the encounter | Internal | 182 | core |
| 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 | core |
| encounter-discharge-disposition | This value set defines a set of codes that can be used to where the patient left the hospital | Internal | 190 | core |
| encounter-location-status | The status of the location | Internal | 564 | core |
| encounter-participant-type | This value set defines a set of codes that can be used to indicate how an individual participates in an encounter | Internal, V3 | 183 | core |
| encounter-priority | This is an example value set defined by the FHIR project, that could be used in Emergency to indicate the encounter priority as determined by triage. | Internal | 187 | core |
| encounter-reason | This examples value set defines the set of codes that can be used to indicate reasons for an encounter | SNOMED CT | 188 | core |
| 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 | core |
| 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 | core |
| encounter-state | Current state of the encounter | Internal | 180 | core |
| 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 | core |
| enteral-route | EnteralRouteOfAdministration: Codes specifying the route of administration of enteral formula. This value set is composed of HL7 V3 codes and is provided as a suggestive example | V3 | 531 | core |
| entformula-additive | EnteralFormulaAdditiveType : Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example | Other | 424 | core |
| entformula-type | EnteralFormulaType : Codes for type of enteral formula to be administered to patient. This value set is is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 Enteral+supplement feeds heirarchy and is provided as a suggestive example | SNOMED CT | 423 | core |
| episode-of-care-status | The status of the encounter | Internal | 582 | core |
| event-timing | Real world event that the schedule relates to | V3 | 19 | core |
| exception | This value set includes sample Exception codes. | Internal | 448 | core |
| extension-context | How an extension context is interpreted | Internal | 145 | core |
| eye-codes | A coded concept listing the eye codes. | Internal | 557 | core |
| filter-operator | The kind of operation to perform as a part of a property based filter | Internal | 177 | core |
| fips-county | This value set defines FIPS codes for US counties and county equivalent entities. | Other | 518 | uslab |
| flag-status | Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or entered in error | Internal | 2001 | core |
| fm-conditions | This value set includes sample Conditions codes. | Internal | 466 | core |
| food-type | FoodType : This value set represents SNOMED CT codes for types of foods. This value set includes all the children of SNOMED CT Concepts from SCTID 255620007 Foods (substance) and is provided as a suggestive example | SNOMED CT | 420 | core |
| formatcodes | The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at http://wiki.hl7.org/index.php?title=CDA_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. | Other | 3 | core |
| forms | This value set includes a sample set of Forms codes | Internal | 470 | core |
| fundsreserve | This value set includes sample funds reservation type codes. | Internal | 449 | core |
| goal-category | goal category - a specific code indicating the type of goal. This value set includes all concepts from SNOMED CT | SNOMED CT | 2015 | cqf |
| goal-priority | goal priority - indicates the level of importance associated with reaching or sustaining a goal | Internal | 2005 | core |
| goal-relationship-type | Types of relationships between two goals | Internal | 2014 | core |
| goal-status | Indicates whether the goal has been met and is still being targeted | Internal | 547 | core |
| group-type | Types of resources that are part of group | Internal | 74 | core |
| http-verb | HTTP verbs (in the HTTP command line) | Internal | 2141 | core |
| icd-10 | This value set includes sample ICD-10 codes. | Internal | 450 | core |
| identifier-type | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose | V2 | 2114 | core |
| identifier-use | Identifies the purpose for this identifier, if known | Internal | 13 | core |
| identity-assuranceLevel | The level of confidence that this link represents the same actual person, based on NIST Authentication Levels | Internal | 555 | core |
| imaging-modality | Type of acquired image data in the instance | DICOM | 19 | core |
| 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 | core |
| 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 | core |
| 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 | core |
| 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 | core |
| 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 | core |
| instance-availability | Availability of the resource | DICOM | 76 | core |
| intervention | This value set includes sample Intervention codes. | Internal | 451 | core |
| investigation-sets | Example value set for Condition/Problem/Diagnosis certainty | SNOMED CT | 541 | core |
| issue-severity | How the issue affects the success of the action | Internal | 120 | core |
| issue-type | A coded expression of the type of issue | Internal | 121 | core |
| kos-title | The document title code of key object selection | DICOM | 7010 | core |
| link-type | The type of link between this patient resource and another patient resource. | Internal | 324 | core |
| lipid-ldl-codes | LDL Cholesterol codes - measured or calculated | LOINC | 444 | core |
| list-DAFMedListCode | This value set indicates the allowed Medication list values in list.code. The vocabulary selected for this value set aligns with the C-CDA section codes. | LOINC | 1910 | daf |
| 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 | core |
| list-example-codes | Example use codes for the List resource - typical kinds of use. TODO: Does LOINC define useful codes? | Internal | 320 | core |
| 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 | core |
| list-mode | The processing mode that applies to this list | Internal | 88 | core |
| list-order | Base values for the order of the items in a list resource | Internal | 1886 | core |
| list-status | The current state of the list | Internal | 2007 | core |
| location-mode | Indicates whether a resource instance represents a specific location or a class of locations | Internal | 337 | core |
| 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 | core |
| location-status | Indicates whether the location is still in use | Internal | 343 | core |
| manifestation-c-cda-codes | This value set includes all SNOMED CT Clinical Findings or Situation with Explicit Context hierarchies. | SNOMED CT | 1576 | daf |
| manifestation-codes | This value set includes all SNOMED CT Clinical Findings | SNOMED CT | 437 | core |
| manifestation-or-symptom | Example value set for Manifestion and Symptom codes | SNOMED CT | 2024 | core |
| 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 | core |
| max-occurs | Flags an element as having unlimited repetitions | Internal | 389 | core |
| measurement-principle | Different measurement principle supported by the device | Internal | 512 | core |
| media-view | Codes defined in SNOMED CT that can be used to record Media Recording views | SNOMED CT | 237 | core |
| medication-admin-status | A set of codes indicating the current status of a MedicationAdministration | Internal | 92 | core |
| medication-codes | This value set includes all Medication codes from Snomed - provided as an exemplar | SNOMED CT | 321 | core |
| medication-dispense-status | A code specifying the state of the dispense event. Describes the lifecycle of the dispense. | Internal | 101 | core |
| medication-form-codes | This value set includes all Form codes from SNOMED CT - provided as an exemplar | SNOMED CT | 108 | core |
| medication-kind | Whether the medication is a product or a package | Internal | 110 | core |
| medication-package-form-codes | This value set includes all Form codes from SNOMED CT - provided as an exemplar | SNOMED CT | 111 | core |
| medication-prescription-status | A code specifying the state of the prescribing event. Describes the lifecycle of the prescription. | Internal | 107 | core |
| medication-statement-status | A set of codes indicating the current status of a MedicationStatement | Internal | 967 | core |
| message-conformance-event-mode | The mode of a message conformance statement | Internal | 45 | core |
| message-events | One of the message events defined as part of FHIR | Internal | 6 | core |
| 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 | core |
| message-significance-category | The impact of the content of a message | Internal | 342 | core |
| message-transport | The protocol used for message transport | Internal | 46 | core |
| metric-calibration-state | Describes the state of a metric calibration | Internal | 537 | core |
| metric-calibration-type | Describes the type of a metric calibration | Internal | 536 | core |
| metric-category | Describes the category of the metric | Internal | 535 | core |
| metric-color | Describes the typical color of representation | Internal | 1491 | core |
| metric-operational-status | Describes the operational status of the DeviceMetric | Internal | 1417 | core |
| missing-tooth-reason | This value set includes sample Missing Tooth Reason codes. | Internal | 452 | core |
| modality | Type of data in the instance | DICOM | 811 | core |
| modified-foodtype | TextureModifiedFoodType: Codes for types of foods that are texture modified. This value set is composed SNOMED CT Concepts from SCTID 255620007 Foods (substance) and is provided as a suggestive example | SNOMED CT | 1556 | core |
| modifiers | This value set includes sample Modifier type codes. | Internal | 453 | core |
| 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 | iso-21090 |
| name-use | The use of a human name | Internal | 15 | core |
| namingsystem-identifier-type | Identifies the style of unique identifier used to identify a namepace | Internal | 477 | core |
| namingsystem-type | Identifies the purpose of the namingsystem | Internal | 474 | core |
| narrative-status | The status of a resource narrative | Internal | 28 | core |
| network-type | The type of network access point of this participant in the audit event | Internal | 1478 | core |
| 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 | core |
| nutrient-code | NutrientModifier : Codes for types of nutrient that is being modified such as carbohydrate or sodium. This value set includes all the children of SNOMED CT Concepts from SCTID 226355009 Nutrients (substance), Sodium, Potassium and Fluid and is provided as a suggestive example | SNOMED CT | 418 | core |
| nutrition-order-status | Codes specifying the state of the request. Describes the lifecycle of the nutrition order. | Internal | 415 | core |
| object-lifecycle | Identifier for the data life-cycle stage for the object | Internal | 1481 | core |
| object-role | Code representing the role the Object played in the event | Internal | 1480 | core |
| object-type | Code for the object type involved audited | Internal | 1479 | core |
| obs-uslab-codedresults | SNOMED CT for coded results This value set includes all concepts from SNOMED CT | SNOMED CT | 1568 | uslab, cqf |
| obs-uslab-codes | LOINC codes. This value set includes all LOINCs | LOINC | 1567 | uslab, cqf |
| obs-uslab-interpretation | This value set defines the set of Codes identifying interpretations of observations | V2 | 522 | uslab |
| obs-uslab-spec-reject | This value set defines the set of code for identifying the reason why the specimen condition prevented the test form being completed. | V2 | 529 | uslab |
| observation-CCDAVitalSignResult | This value set indicates the allowed vital sign result types. The vocabulary selected for this value set align with requirements in the Meaningful Use (MU) Stage 2. Note the concept Blood pressure systolic and diastolic (55284-4) is used to group the related observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4). It SHALL NOT be used alone. | LOINC | 62 | daf |
| observation-ccdasmokingstatus | This value set indicates the current smoking status of a patient. The vocabulary selected for this value set is the best approximation of the statuses in Meaningful Use (MU) Stage 1. The smoking status value set includes a special code to communicate if the smoking status is unknown | SNOMED CT | 0 | daf |
| observation-codes | This value set includes all LOINC codes | LOINC | 115 | core |
| 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 | core |
| observation-methods | Method Codes defined as part of v3 | V3, SNOMED CT, LOINC | 114 | core |
| observation-relationshiptypes | Codes specifying how two observations are related | Internal | 371 | core |
| observation-reliability | Codes that provide an estimate of the degree to which quality issues have impacted on the value of an observation | Internal | 118 | core |
| observation-status | Codes providing the status of an observation | Internal | 7 | core |
| observation-valueabsentreason | This value set defines the set of code for identifying the reason why the expected result in Observation.value[x] is missing. | Internal | 1557 | core |
| observation-values | Codes identifying atomic results of observations when value is type codeableConcept. This value set includes all the children of SNOMED CT Concepts from SCTIDs 404684003 Clinical finding (finding), 410607006 Organism (organism),362981000 Qualifier value (qualifier value), 105590001 Substance (substance), and 123037004 Body structure (body structure). It is provided as a suggestive example | SNOMED CT | 1800 | core |
| operation-definition-parameter-type | Parameter Types used in Operation Definitions | 410 | core | |
| operation-kind | Whether an operation is a normal operation or a query | Internal | 408 | core |
| operation-parameter-use | Whether an operation parameter is an input or an output parameter | Internal | 409 | core |
| oral-prosthodontic-material | This value set includes sample Oral Prosthodontic Material type codes. | Internal | 454 | core |
| order-status | The status of the response to an order | Internal | 1558 | core |
| organization-type | This example value set defines a set of codes that can be used to indicate a type of organization. | Internal | 125 | core |
| parent-relationship-codes | The value set includes the v3 RoleCode PRN (parent), TWIN (twin) and all of their specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. | V3 | 311 | core |
| participantrequired | Is the Participant required to attend the appointment | Internal | 362 | core |
| participantstatus | The Participation status of an appointment | Internal | 364 | core |
| participationstatus | The Participation status of an appointment | Internal | 361 | core |
| 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 | core |
| patient-uslab-nameuse | The name types for US Laboratory ordering and reporting in ambulatory care setting | Other | 524 | uslab |
| patient-uslabph-nameuse | The name types for US Laboratory reporting to Public Health | Other | 525 | uslab |
| payeetype | This value set includes sample Payee type codes. | Internal | 456 | core |
| payment-status | This value set includes a Form codes | Internal | 528 | core |
| payment-type | This value set includes sample Contract Type codes. | Internal | 527 | core |
| postal-address-use | Uses of an address not included in Address.use | V3 | 326 | iso-21090 |
| practitioner-role | This example value set defines a set of codes that can be used to indicate the role of a Practitioner. | Internal | 154 | core |
| practitioner-specialty | This example value set defines a set of codes that can be used to indicate the specialty of a Practitioner | Internal | 155 | core |
| probability-distribution-type | Codes specifying the type of probability distribution | V3 | 325 | iso-21090 |
| procedure-category | Procedure Category code: A selection of relevant SNOMED CT codes | SNOMED CT | 1894 | core |
| procedure-followup | Procedure follow up codes: a selection of snomed codes relevant to procedure follow up | SNOMED CT | 1890 | core |
| procedure-outcome | Procedure Outcome code: A selection of relevant SNOMED CT codes | SNOMED CT | 1889 | core |
| procedure-relationship-type | The nature of the relationship with this procedure | Internal | 136 | core |
| procedure-request-priority | The priority of the request | Internal | 502 | core |
| procedure-request-status | The status of the request | Internal | 500 | core |
| procedure-status | A code specifying the state of the procedure record | Internal | 1470 | core |
| procedure-type | Procedure Type code: All SNOMED CT procedure codes | SNOMED CT | 1877 | core |
| process-outcome | This value set includes sample Process Outcome codes. | Internal | 514 | core |
| process-priority | This value set includes the financial processing priority codes | Internal | 464 | core |
| property-representation | How a property is represented on the wire | Internal | 339 | core |
| provenance-agent-role | The role that a provenance participant played | Internal | 269 | core |
| 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 | 270 | core |
| provenance-entity-role | How an entity was used in an activity | Internal | 267 | core |
| qicore-bodysite-precoordinated | SELECT SNOMED CT code system values representing precoordinated body sites. | SNOMED CT | 1574 | cqf |
| qicore-bodysite-relative-location | SNOMED-CT concepts modifying the anatomic location | SNOMED CT | 2091 | cqf |
| qicore-communication-medium | Value Set for QICore Communication Medium (Example) | Internal | 2082 | cqf |
| qicore-condition-criticality | Value Set for QICore Condition Criticality (Example) | Internal | 2032 | cqf |
| qicore-condition-stage | A period or phase in the course of a disease, or the degree of involvement or severity of a disease. Stage acts as a qualifier for the condition. | SNOMED CT | 2033 | cqf |
| qicore-diagnosticorder-precondition | The condition, state, or problem that the patient is in or has prior to a therapy or procedure. This captures temporal (temporary circumstances) that have bearing on the data that it qualifies but will not necessarily modify its meaning. Things like 'after activity', 'at rest', or 'post-op'. | Internal | 1912 | cqf |
| qicore-encounter-condition-role | This value set includes all the "Qualifier for type of diagnosis" SNOMED CT codes (i.e. codes with an is-a relationship with 106229004: Qualifier for type of diagnosis). | SNOMED CT | 1966 | cqf |
| qicore-encounter-diet | This value set includes all the "Dietary finding" SNOMED CT codes (i.e. codes with an is-a relationship with 41829006: Dietary finding). | SNOMED CT | 2012 | cqf |
| qicore-encounter-priority | This value set includes all the "Priorities" SNOMED CT codes (i.e. codes with an is-a relationship with 272125009: Priorities). | SNOMED CT | 2013 | cqf |
| qicore-flag-category | Value Set for Flag Category (Example). This value set defines category codes for Patient Record Flags. Patient record flags is a mechanism in which an alert can be assigned to patients who have certain high risk clinical needs or behavior problems. Flags can be configured to appear during the patient look-up process. | Internal | 2092 | cqf |
| qicore-medication-codes | All prescribable medication formulations represented using either a 'generic' or 'brand-specific' concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form) | Other | 4 | cqf |
| qicore-medication-dose-type | This value set includes all the "Dosages" SNOMED CT codes (i.e. codes with an is-a relationship with 277406006: Dosages). | SNOMED CT | 2008 | cqf |
| qicore-observation-body-position | SNOMED CT code system values descending from the following:'body position finding' 9851009 | SNOMED CT | 1970 | cqf |
| qicore-observation-delta | Code indicating how the current observation compares to previous observations - e.g., no change, rising trend, decreasing trend, etc... | V2 | 1969 | cqf |
| qicore-observation-verification | Code for method by which the observation result was validated, e.g., human review, sliding average. | Internal | 1971 | cqf |
| qicore-patient-disability | Disability is broadly defined as a physical or mental condition that limits a person's movements, senses, or activities. This includes items such as handicap, impairment, invalidism, functional dependency, and incompetence. | SNOMED CT | 1979 | cqf |
| qicore-patient-military-service | Value Set for Military Service (Example) | Internal | 1978 | cqf |
| qicore-procedure-not-performed-reason | Situation codes describing the reason that a procedure, which might otherwise be expected, was not performed, or a procedure that was started was not completed. Consists of SNOMED CT codes, children of procedure contraindicated (183932001), procedure discontinued (416406003), procedure not done (416237000), procedure not indicated (428119001), procedure not offered (416064006), procedure not wanted (416432009), procedure refused (183944003), and procedure stopped (394908001). | SNOMED CT | 2035 | cqf |
| quantity-comparator | How the Quantity should be understood and represented | Internal | 445 | core |
| questionnaire-answers-status | Lifecycle status of the questionnaire answers | Internal | 387 | core |
| questionnaire-status | Lifecycle status of the questionnaire | Internal | 338 | core |
| reaction-event-certainty | Statement about the degree of clinical certainty that a Specific Substance was the cause of the Manifestation in an reaction event | Internal | 482 | core |
| reaction-event-severity | Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations | Internal | 483 | core |
| reason-medication-given-codes | This value set is provided as an exemplar. 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 | Internal | 966 | core |
| reason-medication-not-given-codes | This value set is provided as an exemplar. 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 | Internal | 93 | core |
| 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 | core |
| referralstatus | The status of the referral | Internal | 412 | core |
| relatedperson-relationshiptype | A set of codes that can be used to indicate the relationship between a Patient and a RelatedPerson. | V3 | 251 | core |
| relationship | This value set includes the Patient to subscriber relationship codes. | Internal | 457 | core |
| report-names | This value set includes all the LOINC codes which relate to Diagnostic Observations | LOINC | 58 | core |
| resource-aggregation-mode | How resource references can be aggregated | Internal | 310 | core |
| resource-slicing-rules | How slices are interpreted when evaluating an instance | Internal | 265 | core |
| resource-types | One of the resource types defined as part of FHIR | Internal | 4 | core |
| response-code | The kind of response to a message | Internal | 322 | core |
| restful-conformance-mode | The mode of a RESTful conformance statement | Internal | 42 | core |
| restful-interaction | The set of interactions defined by the RESTful part of the FHIR specification | Internal | null | ?? |
| restful-security-service | Types of security services used with FHIR | Internal | 43 | core |
| risk-probability | Codes representing the likelihood of a particular outcome in a risk assessment | Internal | 405 | core |
| route-codes | This value set includes all Route codes from SNOMED CT - provided as an exemplar | SNOMED CT | 96 | core |
| ruleset | This value set includes sample ruleset codes. | Internal | 458 | core |
| search-entry-mode | Why an entry is in the result set - whether it's included as a match or because of an _include requirement | Internal | 906 | core |
| search-param-type | Data types allowed to be used for search parameters | Internal | 9 | core |
| security-labels | A single value set for all security labels defined by FHIR | 1770 | core | |
| service-pharmacy | This value set includes a smattering of Pharmacy Service codes | Internal | 553 | core |
| service-product | This value set includes a smattering of Service/Product codes | Internal | 554 | core |
| service-provision-conditions | The code(s) that detail the conditions under which the healthcare service is available/offered | Internal | 1963 | core |
| service-referral-method | The methods of referral can be used when referring to a specific HealthCareService resource | Internal | 1927 | core |
| service-uscls | This value set includes a smattering of USCLS codes | Internal | 459 | core |
| signature-type | The Digital Signature Purposes, an indication of the reason an entity signs a document. This is included in the signed information and can be used when determining accountability for various actions concerning the document. Examples include: author, transcriptionist/recorder, and witness. | Internal | 12 | core |
| slotstatus | The free/busy status of a slot | Internal | 365 | core |
| spec-uslab-bodysite | USLab Specimen Body Site: Codes to describe the specimen collection body site. This value set includes all SNOMED CT concepts that are descendents of Anatomical Structure (91723000) | SNOMED CT | 1585 | uslab |
| spec-uslab-type | USLab Specimen Type: Codes to describe the Specimen. This value set includes all SNOMED CT concepts that are descendents of the Specimen Heirarchy (123038009) | SNOMED CT | 551 | uslab |
| special-values | A set of generally useful codes defined so they can be included in value sets | Internal | 10 | core |
| 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 | core |
| specimen-collection-priority | This example value set defines a set of codes that can be used to indicate the priority of collection of a specimen. | Other | 1492 | core |
| specimen-container-type | Containers which may hold specimens or specimen containers - all SNOMED CT specimen containers | SNOMED CT | 264 | core |
| specimen-treatment-procedure | The technique that is used to perform the process or preserve the specimen | V2 | 263 | core |
| structure-definition-type | Defines the type of structure that a definition is describing | Internal | 1161 | core |
| subscription-channel-type | The type of method used to execute a subscription | Internal | 379 | core |
| subscription-status | The status of a subscription | Internal | 381 | core |
| substance-type | This value sets refers to a substance type | SNOMED CT | 257 | core |
| supplement-type | SupplementType : Codes for nutritional supplements to be provided to the patient. This value set is is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 Enteral+supplement feeds heirarchy and is provided as a suggestive example | SNOMED CT | 422 | core |
| supply-item | This value sets refers to a specific supply item | Internal | 262 | core |
| supply-kind | This value sets refers to a Category of supply | Internal | 505 | core |
| surface | This value set includes a smattering of FDI tooth surface codes. | Internal | 461 | core |
| system-restful-interaction | Operations supported by REST at the system level | FHIR | 407 | core |
| teeth | This value set includes the FDI Teeth codes. | Internal | 463 | core |
| template-status-code | The status indicates the level of maturity of the design and may be used to manage the use of the design | Other | 8 | core |
| texture-code | TextureModifier: Codes for food consistency types or texture modifications to apply to foods. This value set is composed of SNOMED CT (US Extension and Core) Concepts from SCTID 229961002 Food consistency types (substance) heirarchy and is provided as a suggestive example | SNOMED CT | 419 | core |
| timing-abbreviation | Code for a known / defined timing pattern | V3 | 2112 | core |
| tooth | This value set includes a smattering of FDI tooth surface codes. | Internal | 455 | core |
| transaction-operation | The operation associated with an entry in either a update history, or a transaction/ transaction response | Internal, FHIR | 2140 | core |
| transaction-processing-mode | Defines how a match URL should be used when processing a transaction | Internal | 904 | core |
| type-link | The type or discipline-style of the claim | Internal | 1730 | core |
| type-restful-interaction | Operations supported by REST at the type or instance level | FHIR | 406 | core |
| ucum-common | Commonly encountered UCUM units (for purposes of helping populate look ups | FHIR | null | ?? |
| ucum-vitals-common | Common UCUM units for recording Vital Signs | FHIR | 521 | daf |
| udi | This value set includes sample UDI codes. | Internal | 465 | core |
| units | UCUM Codes for units of measure. This value set includes all UCUM codes | FHIR | 523 | uslab, elementdefinition-extensions |
| units-of-time | A unit of time (units from UCUM) | FHIR | 20 | core |
| use-context | This value set defines a base set of codes that can be used to indicate that the content in a resource was developed with a focus and intent of supporting use within particular contexts | Other | 1550 | core |
| use-link | Complete, proposed, exploratory, other | Internal | 460 | core |
| uslab-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 | 1580 | uslab, cqf |
| usps-state | This value set defines two letter USPS alphabetic codes. | Other | 517 | uslab, cqf, daf |
| 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 | core |
| 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 | core |
| 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 | core |
| vaccinetype | This identifies the vaccine substance administered - CVX codes | Other | 22 | core |
| valueset-obs-uslab-kind | Code to classify the kind of observation in Observation.value[x] | Internal | 530 | uslab |
| valueset-supply-dispense-status | Status of the dispense | Internal | 357 | core |
| valueset-supply-status | Status of the supply | Internal | 260 | core |
| versioning-policy | How the system supports versioning for a resource | Internal | 473 | core |
| vision-product | This value set includes a smattering of Prescription Product codes | Internal | 556 | core |
| xds-relationship-type | The kind of relationship between two XDS documents | Internal | 242 | ihe |
| Namespace: http://hl7.org/fhir | ||||
| valueset-systems | This is a list of the explicitly named systems in the FHIR Specification | Other | null | ?? |
| Namespace: http://hl7.org/fhir/ValueSet | ||||
| cpt-all | A value set that includes all CPT codes | Other | null | ?? |
| Namespace: http://nema.org/dicom/vs | ||||
| dicm | The meanings of codes defined in DICOM, either explicitly or by reference to another part of DICOM or an external reference document or standard (OID = 1.2.840.10008.2.16.4) | DICOM | null | ?? |
© HL7.org 2011+. FHIR DSTU (v0.5.0-5149) generated on Fri, Apr 3, 2015 14:36+1100.
Links: What's a DSTU? |
Version History |
Specification Map |
Compare to DSTU1 |
|
Propose a change