DSTU2 QA Preview
This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). 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 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.
Implementation Guides that define value sets: USLab | SDC | SDC-DE | DAF | QICore | CQIF
| Name | Definition | Source | Id | |
| Namespace: http://hl7.org/fhir/ValueSet | ||||
| account-status | Indicates whether the account is available to be used | Internal | 362 | |
| actionlist | List of allowable action which this resource can request | Internal | 351 | |
| activity-reason | Example codes indicating the reason for a clinical activity being performed. | SNOMED CT | 68 | |
| additionalmaterials | This value set includes sample additional material type codes. | Internal | 306 | |
| address-type | The type of an address (physical / postal) | Internal | 38 | |
| address-use | The use of an address | Internal | 37 | |
| adjudication | This value set includes a smattering of Adjudication codes | Internal | 325 | |
| adjudication-error | This value set includes a smattering of adjudication codes | Internal | 25 | |
| adjustment-reason | This value set includes smattering of a Adjustment Reason codes | Internal | 326 | |
| administrative-gender | The gender of a person used for administrative purposes | Internal | 1 | |
| age-units | A valueSet of UCUM codes for representing age value units | FHIR | 10 | |
| allergy-intolerance-category | Category of an identified Substance | Internal | 53 | |
| allergy-intolerance-criticality | Estimate of the potential clinical harm, or seriousness, of a reaction to an identified Substance | Internal | 51 | |
| allergy-intolerance-status | Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified Substance | Internal | 50 | |
| allergy-intolerance-type | Identification of the underlying physiological mechanism for a Reaction Risk | Internal | 52 | |
| allergyintolerance-substance-code | This value set includes concept codes for specific substances and negation codes to specify the absence of specific types of allergies. | SNOMED CT | 405 | |
| animal-breeds | This example value set defines a set of codes that can be used to indicate breeds of species. | Internal | 232 | |
| 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 | 230 | |
| animal-species | This example value set defines a set of codes that can be used to indicate species of animal patients. | Internal | 231 | |
| answer-format | The expected format of an answer | Internal | 257 | |
| anzsco-occupations | Developed for use in the collection, analysis and dissemination of occupation statistics in Australia and New Zealand | External | 253 | |
| appointmentstatus | The free/busy status of an appointment | Internal | 284 | |
| approach-site-codes | This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar | SNOMED CT | 189 | |
| assert-direction-codes | The type of direction to use for assertion. The direction to use for assertions. | Internal | 359 | |
| assert-operator-codes | The type of operator to use for assertion. The type of operator to use for assertions. | Internal | 360 | |
| assert-response-code-types | The type of response code to use for assertion. The response code to expect in the response. | Internal | 361 | |
| audit-event-action | Indicator for type of action performed during the event that generated the audit. | Internal | 263 | |
| audit-event-outcome | Indicates whether the event succeeded or failed | Internal | 264 | |
| audit-event-sub-type | More detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions | DICOM, FHIR | 270 | |
| audit-event-type | Event Types for Audit Events - defined by DICOM with some FHIR specific additions | Internal, DICOM | 269 | |
| audit-source-type | The type of process where the audit event originated from | Internal | 272 | |
| 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 | 59 | |
| binding-strength | Indication of the degree of conformance expectations associated with a binding | Internal | 29 | |
| 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 | 78 | |
| bodysite-relative-location | SNOMED-CT concepts modifying the anatomic location | SNOMED CT | 347 | |
| bundle-type | Indicates the purpose of a bundle- how it was intended to be used | Internal | 327 | |
| 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 | |
| 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 | |
| c80-facilitycodes | This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147. | SNOMED CT | 67 | |
| c80-practice-codes | This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition. | SNOMED CT | 72 | |
| care-plan-activity | Example Codes for types of activities that can appear in a care plan | SNOMED CT | 64 | |
| care-plan-activity-category | High-level categorization of the type of activity in a care plan. | Internal | 63 | |
| care-plan-activity-status | Indicates where the activity is at in its overall life cycle | Internal | 65 | |
| care-plan-category | Example codes indicating the category a care plan falls within. Note that these are in no way complete and may not even be appropriate for some uses. | SNOMED CT | 67 | |
| care-plan-relationship | Codes identifying the types of relationships between two plans. | Internal | 406 | |
| care-plan-status | Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record. | Internal | 60 | |
| choice-list-orientation | Direction in which lists of question options should be displayed | Internal | 429 | |
| claim-exception | This value set includes sample Exception codes. | Internal | 307 | |
| claim-modifiers | This value set includes sample Modifier type codes. | Internal | 311 | |
| claim-type-link | The type or discipline-style of the claim | Internal | 322 | |
| claim-use-link | Complete, proposed, exploratory, other | Internal | 315 | |
| classification-or-context | Identifies whether a useContext represents a context or classification for the element | Internal | 388 | |
| 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 | 115 | |
| clinical-impression-status | The workflow state of a clinical impression | Internal | 71 | |
| communication-request-status | The status of the communication | Internal | 80 | |
| communication-status | The status of the communication | Internal | 79 | |
| composition-attestation-mode | The way in which a person authenticated a composition | Internal | 120 | |
| composition-status | The workflow/clinical status of the composition | Internal | 123 | |
| concept-map-equivalence | The degree of equivalence between concepts | Internal | 9 | |
| condition-category | Preferred value set for Condition Categories | Internal | 73 | |
| condition-cause | Example value set for Cause of Condition codes | SNOMED CT | 376 | |
| condition-clinical | Preferred value set for Condition Clinical Status | Internal | 74 | |
| condition-code | Example value set for Condition/Problem/Diagnosis codes | SNOMED CT | 72 | |
| condition-outcome | Example value set for Condition Outcomes | SNOMED CT | 149 | |
| condition-predecessor | Example value set for Condition Predecessor codes | SNOMED CT | 377 | |
| condition-severity | Preferred value set for Condition/Diagnosis severity grading | SNOMED CT | 76 | |
| condition-stage | Example value set for stages of cancer and other conditions | SNOMED CT | 408 | |
| condition-state | Enumeration indicating whether the condition is currently active, inactive, or has resolved active| inactive| resolved | Internal | 375 | |
| condition-ver-status | The verification status to support or decline the clinical status of the Condition or diagnosis. | Internal | 75 | |
| conditional-delete-status | A code that indicates how the server supports conditional delete | Internal | 91 | |
| 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 | 381 | |
| conformance-resource-status | The lifecycle status of a Value Set or Concept Map | Internal | 2 | |
| conformance-statement-kind | How a conformance statement is intended to be used | Internal | 94 | |
| 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 | 210 | |
| constraint-severity | SHALL applications comply with this constraint? | Internal | 44 | |
| contact-point-system | Telecommunications form for contact point | Internal | 39 | |
| contact-point-use | Use of contact point | Internal | 40 | |
| 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 | 229 | |
| content-type | The content or mime type. The content type or mime type to be specified in Accept or Content-Type header. | Internal | 358 | |
| contract-action | This value set includes sample Contract Action codes. | External | 100 | |
| contract-actorrole | This value set includes sample Contract Actor Role codes. | External | 102 | |
| 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 | 99 | |
| contract-subtype | This value set includes sample Contract Subtype codes. | Internal | 96 | |
| contract-term-subtype | This value set includes sample Contract Term SubType codes. | Internal | 98 | |
| contract-term-type | This value set includes sample Contract Term Type codes. | Internal | 97 | |
| contract-type | This value set includes sample Contract Type codes. | Internal | 95 | |
| cpt-all | A value set that includes all CPT codes | Other | null | |
| data-absent-reason | Used to specify why the normally expected content of the data element is missing | Internal | 3 | |
| data-types | The type of an element - one of the FHIR data types | Internal | 13 | |
| 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 | 372 | |
| 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 | 373 | |
| dataelement-stringency | Indicates the degree of precision of the data element definition | Internal | 244 | |
| days-of-week | The days of the week | Internal | 302 | |
| defined-types | Either a resource or a data type | Other, FHIR | 14 | |
| designation-use | Details of how a designation would be used | SNOMED CT | 281 | |
| detectedissue-category | Kinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. | V3 | 103 | |
| detectedissue-mitigation-action | Kinds of mitigating actions and observations that can be associated with a detected issue or contraindication, such as 'added concurrent therapy', 'prior therapy documented', etc. | V3 | 104 | |
| detectedissue-severity | Indicates the potential degree of impact of the identified issue on the patient | Internal | 105 | |
| device-action | Example value set for Procedure Device Action code (what happened to a device during a procedure | Internal | 236 | |
| device-use-request-priority | Codes representing the priority of the request | Internal | 109 | |
| device-use-request-status | Codes representing the status of the request | Internal | 108 | |
| devicestatus | The availability status of the device | Internal | 107 | |
| diagnostic-order-event | Additional information about an event that occurred to a diagnostic order | SNOMED CT | 113 | |
| diagnostic-order-priority | The clinical priority of a diagnostic order | Internal | 111 | |
| diagnostic-order-status | The status of a diagnostic order | Internal | 110 | |
| diagnostic-report-status | The status of the diagnostic report as a whole | Internal | 118 | |
| diagnostic-requests | This value set includes all the LOINC Order codes | LOINC | 112 | |
| diagnostic-service-sections | This value set includes all the codes in HL7 v2 table 0074 | V2 | 117 | |
| dicm-402-roleid | Audit Active Participant Role ID Code | DICOM | 271 | |
| dicm-405-mediatype | Media Type Code | DICOM | 424 | |
| dicom-cid29 | This Value Set includes codes that may be used to identify an image or waveform acquisition modality, as used in the ImagingStudy resource, Dicom Attribute Modality (0008,0060) or HL7 v2 Table 0259 (see HL7 v2.6 Chapter 8 Section 8.8.8.47). It generally corresponds to a class of diagnostic equipment, or to a specific acquisition function or technique in a device | DICOM | 158 | |
| dicom-dcim | DICOM Code Definitions (Coding Scheme Designator "DCM" Coding Scheme Version "01") | DICOM | null | |
| 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 | 206 | |
| 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 | 184 | |
| digital-media-type | Whether the Media is a photo, video, or audio | Internal | 183 | |
| doc-classcodes | LOINC codes for Document Kind, taken from the LOINC document ontology | LOINC | 125 | |
| doc-section-codes | Document section codes (LOINC codes used in CCDA sections) | LOINC | 119 | |
| doc-typecodes | FHIR Document Codes - all LOINC codes where scale_type = 'DOC' | LOINC | 121 | |
| document-mode | Whether the application produces or consumes documents | Internal | 87 | |
| document-reference-status | The status of the document reference | Internal | 4 | |
| document-relationship-type | The type of relationship between documents | Internal | 133 | |
| encounter-admit-source | This value set defines a set of codes that can be used to indicate from where the patient came in. | Internal | 144 | |
| encounter-class | Classification of the encounter | Internal | 138 | |
| 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 | 142 | |
| encounter-discharge-disposition | This value set defines a set of codes that can be used to where the patient left the hospital | Internal | 145 | |
| encounter-location-status | The status of the location | Internal | 147 | |
| 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 | 139 | |
| 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 | 143 | |
| encounter-reason | This examples value set defines the set of codes that can be used to indicate reasons for an encounter | SNOMED CT | 146 | |
| 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 | 141 | |
| encounter-special-courtesy | This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. | V3 | 140 | |
| encounter-state | Current state of the encounter | Internal | 136 | |
| 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 | 137 | |
| 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 | 214 | |
| 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 | Internal | 213 | |
| 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 | 212 | |
| episode-of-care-status | The status of the encounter | Internal | 346 | |
| event-timing | Real world event that the schedule relates to | V3 | 41 | |
| example-expansion | This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36 | LOINC | null | |
| example-extensional | This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36 | LOINC | null | |
| example-inline | This is an example value set that includes all the ACME codes for serum/plasma cholesterol from v2.36 | External | null | |
| example-intensional | This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36 | LOINC | null | |
| extension-context | How an extension context is interpreted | Internal | 349 | |
| filter-operator | The kind of operation to perform as a part of a property based filter | Internal | 280 | |
| fips-county | This value set defines FIPS codes for US counties and county equivalent entities. | Other | 27 | |
| flag-category | Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) | Internal | 403 | |
| flag-code | Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) | SNOMED CT | 404 | |
| flag-priority | This value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority | IHE | 433 | |
| 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 | 49 | |
| fm-conditions | This value set includes sample Conditions codes. | Internal | 321 | |
| focal-subject | Example VS composed from SNOMED CT and V3 codes for observation targets: donor, fetus, spouse. As uses case are discovered may add more values. | SNOMED CT, V3 | 400 | |
| 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 | 205 | |
| 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. The actual list of codes here is incomplete | Other | 3 | |
| forms | This value set includes a sample set of Forms codes | Internal | 24 | |
| fundsreserve | This value set includes sample funds reservation type codes. | Internal | 22 | |
| goal-acceptance-status | Codes indicating whether the goal has been accepted by a stakeholder | Internal | 431 | |
| goal-category | goal category - example codes for grouping goals for filtering or presentation | Internal | 411 | |
| goal-priority | goal priority - indicates the level of importance associated with reaching or sustaining a goal | Internal | 151 | |
| goal-relationship-type | Types of relationships between two goals | Internal | 390 | |
| goal-start-event | Identifies types of events that might trigger the start of a goal | SNOMED CT | 413 | |
| goal-status | Indicates whether the goal has been met and is still being targeted | Internal | 150 | |
| goal-status-reason | Example codes indicating the reason for a current status. Note that these are in no way complete and may not even be appropriate for some uses. | Internal | 412 | |
| group-type | Types of resources that are part of group | Internal | 156 | |
| guide-dependency-type | How a dependency is represented when the guide is published | Internal | 170 | |
| guide-page-kind | The kind of an included page | Internal | 171 | |
| guide-resource-purpose | Why a resource is included in the guide | Internal | 172 | |
| history-status | A code that identifies the status of the family history record | Internal | 409 | |
| http-verb | HTTP verbs (in the HTTP command line) | Internal | 329 | |
| icd-10 | This value set includes sample ICD-10 codes. | Other | 308 | |
| identifier-type | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose | Internal, V2 | 30 | |
| identifier-use | Identifies the purpose for this identifier, if known | Internal | 33 | |
| identity-assuranceLevel | The level of confidence that this link represents the same actual person, based on NIST Authentication Levels | Internal | 342 | |
| 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 | 163 | |
| 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 | 169 | |
| 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 | 168 | |
| 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 | 162 | |
| 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 | 161 | |
| instance-availability | Availability of the resource | DICOM | 157 | |
| intervention | This value set includes sample Intervention codes. | Internal | 309 | |
| investigation-sets | Example value set for Condition/Problem/Diagnosis certainty | SNOMED CT | 69 | |
| issue-severity | How the issue affects the success of the action | Internal | 223 | |
| issue-type | A code that describes the type of issue | Internal | 224 | |
| kos-title | The document title code of key object selection | DICOM | 159 | |
| ldlcholesterol-codes | LDL Cholesterol codes - measured or calculated | LOINC | 444 | |
| link-type | The type of link between this patient resource and another patient resource. | Internal | 234 | |
| 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 | 176 | |
| list-example-codes | Example use codes for the List resource - typical kinds of use. TODO: Does LOINC define useful codes? | Internal | 173 | |
| 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 | 175 | |
| list-mode | The processing mode that applies to this list | Internal | 174 | |
| list-order | Base values for the order of the items in a list resource | Internal | 177 | |
| list-status | The current state of the list | Internal | 178 | |
| location-mode | Indicates whether a resource instance represents a specific location or a class of locations | Internal | 181 | |
| 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 | 179 | |
| location-status | Indicates whether the location is still in use | Internal | 182 | |
| manifestation-codes | This value set includes all SNOMED CT Clinical Findings | SNOMED CT | 55 | |
| manifestation-or-symptom | Example value set for Manifestion and Symptom codes | SNOMED CT | 77 | |
| marital-status | This value set defines the set of codes that can be used to indicate the marital status of a person | Internal, V3 | 19 | |
| measurement-principle | Different measurement principle supported by the device | Internal | 331 | |
| media-view | Codes defined in SNOMED CT that can be used to record Media Recording views | SNOMED CT | 185 | |
| medication-admin-status | A set of codes indicating the current status of a MedicationAdministration | Internal | 186 | |
| medication-codes | This value set includes all Medication codes from Snomed - provided as an exemplar | SNOMED CT | 199 | |
| medication-dispense-status | A code specifying the state of the dispense event. Describes the lifecycle of the dispense. | Internal | 192 | |
| medication-form-codes | This value set includes all Form codes from SNOMED CT - provided as an exemplar | SNOMED CT | 198 | |
| medication-order-status | A code specifying the state of the prescribing event. Describes the lifecycle of the prescription. | Internal | 196 | |
| medication-package-form-codes | This value set includes all Form codes from SNOMED CT - provided as an exemplar | SNOMED CT | 201 | |
| medication-statement-status | A set of codes indicating the current status of a MedicationStatement | Internal | 197 | |
| message-conformance-event-mode | The mode of a message conformance statement | Internal | 85 | |
| message-events | One of the message events defined as part of FHIR | Internal | 15 | |
| message-reason-encounter | Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update | Internal | 202 | |
| message-significance-category | The impact of the content of a message | Internal | 88 | |
| message-transport | The protocol used for message transport | Internal | 86 | |
| metric-calibration-state | Describes the state of a metric calibration | Internal | 340 | |
| metric-calibration-type | Describes the type of a metric calibration | Internal | 339 | |
| metric-category | Describes the category of the metric | Internal | 338 | |
| metric-color | Describes the typical color of representation | Internal | 341 | |
| metric-operational-status | Describes the operational status of the DeviceMetric | Internal | 337 | |
| missing-tooth-reason | This value set includes sample Missing Tooth Reason codes. | Internal | 310 | |
| 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 | 209 | |
| 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 | 363 | |
| name-use | The use of a human name | Internal | 36 | |
| namingsystem-identifier-type | Identifies the style of unique identifier used to identify a namepace | Internal | 293 | |
| namingsystem-type | Identifies the purpose of the namingsystem | Internal | 290 | |
| narrative-status | The status of a resource narrative | Internal | 32 | |
| network-type | The type of network access point of this participant in the audit event | Internal | 265 | |
| nhin-purposeofuse | This value set is suitable for use with the provenance resource. It is derived from, but not compatible with, the V3 Purpose of use Code system | External | null | |
| 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 | 164 | |
| note-type | The presentation types of notes | Internal | 8 | |
| 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 | 207 | |
| nutrition-order-status | Codes specifying the state of the request. Describes the lifecycle of the nutrition order. | Internal | 204 | |
| object-lifecycle | Identifier for the data life-cycle stage for the object | Internal | 268 | |
| object-role | Code representing the role the Object played in the event | Internal | 267 | |
| object-type | Code for the object type involved audited | Internal | 266 | |
| observation-category | Observation Category codes | Internal | 222 | |
| observation-codes | This value set includes all LOINC codes | LOINC | 216 | |
| observation-interpretation | This value set defines the set of codes that can be used to indicate the meaning/use of a reference range | V2 | 218 | |
| observation-methods | Observation Method codes from SNOMED CT (codes subsumed by 272394005 "Technique", and the v3 Code System "ObservationMethod" (which is no loner actively maintained) | V3, SNOMED CT | 215 | |
| observation-relationshiptypes | Codes specifying how two observations are related | Internal | 220 | |
| observation-status | Codes providing the status of an observation | Internal | 219 | |
| observation-valueabsentreason | This value set defines the set of code for identifying the reason why the expected result in Observation.value[x] is missing. | Other | 221 | |
| operation-kind | Whether an operation is a normal operation or a query | Internal | 297 | |
| operation-outcome | Operation Outcome codes used by FHIR test servers (see Implementation file translations.xml) | Internal | 225 | |
| operation-parameter-type | Parameter Types used in Operation Definitions | 299 | ||
| operation-parameter-use | Whether an operation parameter is an input or an output parameter | Internal | 298 | |
| oral-prosthodontic-material | This value set includes sample Oral Prosthodontic Material type codes. | Internal | 312 | |
| order-status | The status of the response to an order | Internal | 227 | |
| organization-type | This example value set defines a set of codes that can be used to indicate a type of organization. | Internal | 228 | |
| 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 | 382 | |
| participant-role | Roles of Participants that may be included in a CarePlan.Participants, or in an EpisodeOfCare.CareTeam. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization (qualifier value) | SNOMED CT | 61 | |
| participantrequired | Is the Participant required to attend the appointment | Internal | 286 | |
| participantstatus | The Participation status of an appointment | Internal | 289 | |
| participationstatus | The Participation status of an appointment | Internal | 285 | |
| 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 | 233 | |
| patient-mpi-match | A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not | Internal | 434 | |
| payeetype | This value set includes sample Payee type codes. | Internal | 21 | |
| payment-status | This value set includes a Form codes | Internal | 334 | |
| payment-type | This value set includes sample Contract Type codes. | Internal | 333 | |
| performer-role | This examples value set defines the set of codes that can be used to indicate a role of procedure performer. | SNOMED CT | 420 | |
| postal-address-use | Uses of an address not included in Address.use | V3 | 365 | |
| practitioner-role | This example value set defines a set of codes that can be used to indicate the role of a Practitioner. | Internal | 251 | |
| practitioner-specialty | This example value set defines a set of codes that can be used to indicate the specialty of a Practitioner | Internal | 252 | |
| probability-distribution-type | Codes specifying the type of probability distribution | V3 | 364 | |
| procedure-category | Procedure Category code: A selection of relevant SNOMED CT codes | SNOMED CT | 241 | |
| procedure-code | Procedure Code: All SNOMED CT procedure codes | SNOMED CT | 417 | |
| procedure-followup | Procedure follow up codes: a selection of snomed codes relevant to procedure follow up | SNOMED CT | 240 | |
| 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 | 418 | |
| procedure-outcome | Procedure Outcome code: A selection of relevant SNOMED CT codes | SNOMED CT | 239 | |
| procedure-progress-status-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 procedure performance process | Internal | 430 | |
| procedure-reason | This examples value set defines the set of codes that can be used to indicate a reasons for a procedure. | SNOMED CT | 419 | |
| procedure-relationship-type | The nature of the relationship with this procedure | Internal | 235 | |
| procedure-request-priority | The priority of the request | Internal | 243 | |
| procedure-request-status | The status of the request | Internal | 242 | |
| procedure-status | A code specifying the state of the procedure record | Internal | 237 | |
| process-outcome | This value set includes sample Process Outcome codes. | Internal | 352 | |
| process-priority | This value set includes the financial processing priority codes | Internal | 319 | |
| profile-code | Codes for the meaning of the defined structure | SNOMED CT, LOINC | 350 | |
| property-representation | How a property is represented on the wire | Internal | 47 | |
| provenance-agent-role | The role that a provenance participant played | Internal | 245 | |
| 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 | 246 | |
| provenance-entity-role | How an entity was used in an activity | Internal | 247 | |
| quantity-comparator | How the Quantity should be understood and represented | Internal | 34 | |
| question-max-occurs | Flags an element as having unlimited repetitions | Internal | 380 | |
| questionnaire-answers | Example list of codes for answers to questions. (Not complete or necessarily appropriate.) | SNOMED CT | 423 | |
| questionnaire-answers-status | Lifecycle status of the questionnaire response | Internal | 258 | |
| questionnaire-category | Example list of potential categegories for questionnaires | SNOMED CT | 379 | |
| questionnaire-question-control | Starter set of user interface controls that might be used when capturing data from Questionnaire questions | Internal | 428 | |
| questionnaire-questions | Example list of codes for questions and groups of questions. (Not necessariliy complete or appropriate) | LOINC | 255 | |
| questionnaire-status | Lifecycle status of the questionnaire | Internal | 256 | |
| 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 | 54 | |
| reaction-event-severity | Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations | Internal | 56 | |
| 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 | 188 | |
| 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 | 187 | |
| 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 | 217 | |
| referralstatus | The status of the referral | Internal | 300 | |
| relatedperson-relationshiptype | A set of codes that can be used to indicate the relationship between a Patient and a RelatedPerson. | V3 | 259 | |
| relationship | This value set includes the Patient to subscriber relationship codes. | Internal | 23 | |
| remittance-outcome | The outcome of the processing. | Internal | 7 | |
| report-codes | This value set includes all the LOINC codes which relate to Diagnostic Observations | LOINC | 116 | |
| resource-aggregation-mode | How resource references can be aggregated | Internal | 46 | |
| resource-slicing-rules | How slices are interpreted when evaluating an instance | Internal | 45 | |
| resource-types | One of the resource types defined as part of FHIR | Internal | 16 | |
| resource-validation-mode | Codes indicating the type of validation to perform | Internal | 48 | |
| response-code | The kind of response to a message | Internal | 203 | |
| restful-conformance-mode | The mode of a RESTful conformance statement | Internal | 81 | |
| 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 | 82 | |
| risk-probability | Codes representing the likelihood of a particular outcome in a risk assessment | Internal | 262 | |
| route-codes | This value set includes all Route codes from SNOMED CT - provided as an exemplar | SNOMED CT | 58 | |
| ruleset | This value set includes sample ruleset codes. | Internal | 20 | |
| 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 | 328 | |
| search-modifier-code | A supported modifier for a search parameter | Internal | 92 | |
| search-param-type | Data types allowed to be used for search parameters | Internal | 6 | |
| search-xpath-usage | How a search parameter relates to the set of elements returned by evaluating the its xpath query | Internal | 332 | |
| security-labels | A single value set for all security labels defined by FHIR | 31 | ||
| service-pharmacy | This value set includes a smattering of Pharmacy Service codes | Internal | 324 | |
| service-product | This value set includes a smattering of Service/Product codes | Internal | 323 | |
| service-provision-conditions | The code(s) that detail the conditions under which the healthcare service is available/offered | Internal | 303 | |
| service-referral-method | The methods of referral can be used when referring to a specific HealthCareService resource | Internal | 301 | |
| service-uscls | This value set includes a smattering of USCLS codes | Internal | 314 | |
| 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 | 35 | |
| slotstatus | The free/busy status of a slot | Internal | 283 | |
| special-values | A set of generally useful codes defined so they can be included in value sets | Internal | 5 | |
| 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 | 275 | |
| 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 | 402 | |
| specimen-container-type | Containers which may hold specimens or specimen containers - all SNOMED CT specimen containers | SNOMED CT | 277 | |
| specimen-status | Codes providing the status/availability of a specimen | Internal | 426 | |
| specimen-treatment-procedure | The technique that is used to perform the process or preserve the specimen | V2 | 276 | |
| structure-definition-kind | Defines the type of structure that a definition is describing | Internal | 348 | |
| subscription-channel-type | The type of method used to execute a subscription | Internal | 294 | |
| subscription-status | The status of a subscription | Internal | 295 | |
| subscription-tag | Tags to put on a resource after subscriptions sent | Internal | 296 | |
| substance-category | Substance category codes | Internal | 279 | |
| substance-code | This value set contains concept codes for specific substances | SNOMED CT | 57 | |
| 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 | 211 | |
| supplydelivery-status | Status of the Supply delivery | Internal | 355 | |
| supplydelivery-type | This value sets refers to a specific supply item | Internal | 356 | |
| supplyrequest-kind | This value sets refers to a Category of supply | Internal | 353 | |
| supplyrequest-status | Status of the supply request | Internal | 354 | |
| surface | This value set includes a smattering of FDI tooth surface codes. | Internal | 316 | |
| system-restful-interaction | Operations supported by REST at the system level | FHIR | 84 | |
| teeth | This value set includes the FDI Teeth codes. | Internal | 318 | |
| 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 | 384 | |
| testscript-operation-codes | This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. | Internal | 357 | |
| 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 | 208 | |
| timing-abbreviation | Code for a known / defined timing pattern | Internal, V3 | 43 | |
| tooth | This value set includes a smattering of FDI tooth surface codes. | Internal | 313 | |
| transaction-mode | A code that indicates how transactions are supported | Internal | 90 | |
| type-restful-interaction | Operations supported by REST at the type or instance level | FHIR | 83 | |
| ucum-common | Commonly encountered UCUM units (for purposes of helping populate look ups | FHIR | null | |
| udi | This value set includes sample UDI codes. | Internal | 320 | |
| units-of-time | A unit of time (units from UCUM) | FHIR | 42 | |
| unknown-content-code | A code that indicates whether an application accepts unknown elements or extensions when reading resources | Internal | 93 | |
| 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 | 18 | |
| usps-state | This value set defines two letter USPS alphabetic codes. | Other | 26 | |
| 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 | 166 | |
| 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 | 167 | |
| 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 and includes tSNOMED CT concepts from the 64572001 (Disease) hierarchy | SNOMED CT | 415 | |
| vaccine-code | This identifies the vaccine substance administered - CVX codes | Other | 22 | |
| versioning-policy | How the system supports versioning for a resource | Internal | 89 | |
| vision-base-codes | A coded concept listing the base codes. | Internal | 345 | |
| vision-eye-codes | A coded concept listing the eye codes. | Internal | 344 | |
| vision-product | This value set includes a smattering of Prescription Product codes | Internal | 343 | |
| xds-relationship-type | The kind of relationship between two XDS documents | Internal | 383 | |
| yesnodontknow | For Capturing simple yes-no-don't know answers | Other | null | |
© HL7.org 2011+. FHIR DSTU2 (v1.0.0-6850) generated on Tue, Sep 1, 2015 14:42+1000.
Links: What's a DSTU? |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change