Release 4 R6 Ballot (1st Full Ballot)

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU v6.0.0-ballot4: Release 6 Ballot (1st Full Ballot) (see Ballot Notes ) in it's permanent home (it will always be available at this URL). ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions for published versions icon . Page versions: R5 R4B R4 R3 R2

4.4.0 Value Sets Defined in FHIR

Maturity Level : N/A
FHIR Responsible Owner: Terminology Infrastructure icon Work Group Standards Status : Informative

This table contains a list of all the value sets defined as part of the core FHIR specification. Some of these value sets include codes defined elsewhere, some contain their own inline code system definitions, codes defined as part of FHIR, and some do both. Any implicit code systems Value sets that are case sensitive, though defined in implementation guides or the HL7 Terminology icon outside this core specification are NOT listed in this table. Additional value sets may be found in FHIR will never define codes that only differ by case. implementation guides in the FHIR registry (https://registry.fhir.org)

Note that these value sets are available as FHIR resources - see the Downloads Page (as part of the FHIR definitions)

FHIR HL7 V3 HL7 v2 Id 726 815 799 Either a practitioner role or a relationship type. 811 813 803 801 69 67 596 39 1 831 833 840 835 19 null 133 129 131 1372 137 1370 Other 484 346 708 710 1295 458 452 454 138 608 612 606 610 141 Laterality: SNOMED-CT concepts for 'left', 'right', and 'bilateral' 140 620 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 67 198 149 care-plan-activity-status Codes that reflect the current state of a care plan activity within its overall life cycle. Internal 146 148 150 155 153 The type of catalog. 1065 The subcomponent classification of quality of evidence rating systems. 848 846 choice-list-orientation Direction in which lists of possible answers should be displayed. Other 933 Other 580 582 566 558 544 232 1046 860 codesystem-altcode-kind Indicates the type of use for which the code is defined. Other 952 782 Other 172 983 786 238 241 17 780 480 Preferred value set for Condition Categories. 164 161 966 168 170 171 condition-state Enumeration indicating whether the condition is currently active, inactive, or has been resolved. Other 963 166 194 200 Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification. 753 751 Other, Internal 748 759 consent-performer This value set includes sample Performer Role codes. Internal 1016 1014 757 consent-scope This value set includes the four Consent scope codes. Other 761 755 81 71 73 contactentity-type This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party. Other 416 850 739 1303 741 1297 1293 1301 1299 Other 745 contract-data-meaning How a resource reference is interpreted when evaluating contract offers. 749 1291 1212 1210 1214 1206 1224 1208 1216 1220 1218 1222 737 743 731 735 733 729 912 1009 527 1328 This value set includes Coverage SelfPay codes. 520 1393 cpt-all A value set that includes all CPT codes Other null 1025 5 22 dataelement-sdcobjectclass The allowed codes for identifying the ISO 11179 ObjectClass for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. SNOMED CT, LOINC, Other 910 512 24 1056 definition-status Codes identifying the lifecycle stage of a definition. Other 107 794 264 205 425 1307 213 214 645 49 diagnostic-based-on-snomed Diagnostic Attachment Type codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182836005 (Review of medication (procedure)) or is-a 404684003 (Clinical finding (finding)) SNOMED CT 960 235 234 Media Type Code 385 62 237 240 document-classcodes This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests. LOINC 46 186 7 1182 1184 255 259 262 250 253 252 248 496 494 ENSEMBL reference sequence identifiers 394 391 664 666 182 event-or-request-resource-types This value set lists all the event or request resource types defined in this version of the specification. Other 1064 1060 109 1174 1169 588 Other 590 ex-onsettype This value set includes sample Service Modifier codes. Internal 578 ex-payee-resource-type The type of Claim payee Resource. 584 616 1387 576 594 null null example-hierarchical Demonstration of extensions that build a hierarchical contains Other null null 618 105 1012 478 financial-taskcode This value set includes Financial Task codes. Other 1389 financial-taskinputtype This value set includes Financial Task Input Type codes. Other 1391 122 124 flag-priority This value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority. Internal 950 Internal 120 fm-conditions This value set includes sample Conditions codes. Internal 556 fm-itemtype This value set includes sample Item Type codes. 548 592 focal-subject Example value set composed from SNOMED CT and HL7 V3 codes for observation targets such as donor, fetus or spouse. As use cases are discovered, more values may be added. SNOMED CT, V3 954 384 1 33 972 1374 273 goal-relationship-type Types of relationships between two goals. Other 915 279 271 280 1345 817 998 996 854 269 267 hl7-work-group An HL7 administrative unit that owns artifacts in the FHIR specification. Other 944 http-operations The allowable request method or HTTP operation codes. Internal 716 531 574 45 57 656 imagingstudy-status The status of the ImagingStudy. Internal 990 995 immunization-funding-source The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example. Other 293 Other 296 immunization-program-eligibility The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's eligibility for a vaccination program. This value set is provided as a suggestive example. 291 SNOMED CT 290 immunization-recommendation-date-criterion The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the definition of dates relevant to recommendations for future doses of vaccines. This value set is provided as a suggestive example. LOINC 308 immunization-recommendation-reason The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reasons why a given recommendation status is assigned. This value set is provided as a suggestive example and includes SNOMED CT concepts. 307 immunization-recommendation-status The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example. Other 305 immunization-recommendation-target-disease The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the disease targeted by a vaccination recommendation. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy. SNOMED CT 309 289 288 295 V3, SNOMED CT 0 157 866 null null null 408 410 444 1022 20 Internal 423 linkage-type Used to distinguish different roles a resource can play within a set of linked resources. 314 322 316 320 318 324 326 330 332 169 679 687 677 675 683 685 681 29 776 778 MedicationAdministration Performer Function Codes Other 96 367 376 Other 1318 26 378 188 652 650 648 654 646 534 388 name-assembly-order A code that represents the preferred display order of the components of a human name. Other, V2, V3 913 name-part-qualifier A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. V3 906 65 492 490 Internal 55 network-type The type of network access point of this agent in the audit event. 456 15 460 403 395 The statistical operation parameter -"statistic" codes. 508 880 414 987 152 participantrequired Is the Participant required to attend the appointment. Internal 488 54 486 31 643 641 null 433 1331 plan-definition-type The type of PlanDefinition. Other 797 postal-address-use Uses of an address not included in Address.use. V3 908 439 practitioner-specialty This example value set defines a set of codes that can be used to indicate the specialty of a Practitioner. Internal 441 precision-estimate-type Method of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation. Other 1357 1399 430 427 429 431 428 procedure-progress-status-codes This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the procedure performance process. Internal 946 432 902 904 1383 87 1003 436 927 926 570 51 3 228 59 Flags an element as having unlimited repetitions. 446 required questionnaire-category Example list of potential categories for questionnaires. SNOMED CT 928 935 1007 1005 questionnaire-item-control Starter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire. Internal 931 443 questionnaire-usage-mode Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item. Other 937 questionnaireresponse-mode Codes describing how the QuestionnaireResponse was populated V3 1290 reaction-event-certainty Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event. Other 942 135 344 342 369 recommendation-strength A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems. Other 1021 ref-sequences REFSEQ : National Center for Biotechnology Information (NCBI) Reference Sequences Other 280 202 407 856 99 568 V2, V3 449 relation-type The type of relations between entries. Internal 35 720 233 722 113 115 1058 111 1341 Codes for why the study ended prematurely. Internal 819 research-subject-status Indicates the progression of a study subject through a study. 829 85 resource-security-category Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource. Other 1403 83 117 resource-type-link The type of payee Resource. Other 614 27 118 380 176 450 98 637 639 11 635 222 221 219 1044 989 516 562 564 service-product This value set includes a smattering of Service/Product codes. Internal 560 514 510 518 542 434 12 482 smart-capabilities Codes that define what the server is capable of. Other 1018 979 1026 special-values A set of generally useful codes defined so they can be included in value sets. Other 9 1398 468 852 470 V2 471 985 668 1349 775 1385 The type of method used to execute a subscription. Internal 500 subscription-status The status of a subscription. 693 181 790 550 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 704 673 180 ucum-bodylength UCUM units for recording body length measures such as height and head circumference FHIR 958 UCUM units for recording Body Weight FHIR 28 884 662 660 -- RoleLinkStatus Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine. Process Interruption Reason
Name Definition Source
Namespace: http://hl7.org/fhir/ValueSet
FHIR-version N All published FHIR Versions. Internal
1309 account-aggregate Indicates who is expected to pay a part of the account balance. Internal
abstract-types N account-balance-term A list of the base types defined by this version of Indicates the FHIR specification - types that are defined, but for which only specializations actually are created. account balance's age. Internal
23 account-billing-status I Indicates whether the account is available to be used for billing purposes. Internal
account-status Indicates whether the account is available to be used. Internal
account-type I This examples value set defines the set of codes that can be used to represent the type of an account. V3
728 action-applicability-behavior Defines applicability behavior of a group. Internal
action-cardinality-behavior Defines behavior for an action or a group for how many times that item may be repeated. Internal
807 action-code I Provides examples of actions to be performed. Internal
action-condition-kind Defines the kinds of conditions that can appear on actions. Internal
action-grouping-behavior Defines organization behavior of a group. Internal
action-participant-role action-participant-function I Other The function performed by the participant for the action. 796 Internal
action-participant-type The type of participant for the action. Internal
action-precheck-behavior Defines selection frequency behavior for an action or group. Internal
805 action-reason-code I Provides examples of reasons for actions to be performed. Internal
action-relationship-type Defines the types of relationships between actions. Internal
action-required-behavior Defines expectations around whether an action or action group is required. Internal
action-selection-behavior Defines selection behavior of a group. Internal
action-type actordefinition-actor-code The Code for the type of action to be performed. Other actor - system or human. 809 Internal
activity-definition-category actordefinition-actor-type High-level categorization of the The type of activity. Other actor - system or human. 792 Internal
additional-instruction-codes additional-binding-purpose This value set includes all SNOMED CT Additional Dosage Instructions. SNOMED CT Binding Purpose 95 Internal
additionalmaterials additional-instruction-codes I This value set includes sample additional material type codes. Internal all SNOMED CT Additional Dosage Instructions. 529 SNOMED CT
address-type N The type of an address (physical / postal). Internal
address-use N The use of an address. Internal
adjudication This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc. Other
adjudication-error I This value set includes a smattering of adjudication codes. Other
adjudication-reason I This value set includes smattering of Adjudication Reason codes. Other
598 administrable-dose-form I Dose form for a medication, in the form suitable for administering to the patient, after mixing, where necessary. Internal
administration-method-codes I This value set includes some method codes from SNOMED CT - provided as an exemplar SNOMED CT
97 administration-subpotent-reason I MedicationAdministration Subpotent Reason Internal
administrative-gender N The gender of a person used for administrative purposes. Internal
adverse-event-actuality Overall nature of the adverse event, e.g. real or potential. Internal
adverse-event-category I Overall categorization of the event, e.g. product-related or situational. Other
adverse-event-causality-assess I Codes for the assessment of whether the entity caused the event. Other
adverse-event-causality-method I TODO. Codes for the method of evaluating the relatedness of the suspected entity to the adverse event Other
842 adverse-event-contributing-factor I This value set includes codes that describe the contributing factors suspected to have increased the probability or severity of the adverse event. SNOMED CT
adverse-event-mitigating-action I This value set includes codes that describe the ameliorating actions taken after the adverse event occurred in order to reduce the extent of harm. SNOMED CT
adverse-event-outcome I TODO (and should this be required?). This value set includes codes that describe the type of outcome from the adverse event. SNOMED CT
Other adverse-event-participant-function I This value set includes codes that describe the type of involvement of the actor in the adverse event. V3
836 adverse-event-preventive-action I This value set includes codes that describe the preventive actions that contributed to avoiding the adverse event. SNOMED CT
adverse-event-seriousness I Overall seriousness of this event for the patient. Other
838 adverse-event-status Codes identifying the lifecycle stage of an adverse event. Internal
adverse-event-severity adverse-event-supporting-info I The severity of This value set includes codes that describe the adverse event itself, in direct relation supporting information relevant to the subject. Other event. 844 SNOMED CT
adverse-event-type I This value set includes all SNOMED CT Clinical Findings. codes that describe the adverse event or incident that occurred or was averted. SNOMED CT
age-units Unified Code for Units of Measure (UCUM). This value set includes all common UCUM codes used for Age - that it is, all commonly used units which have the same canonical unit as 'a' (year) FHIR
all-distance-units Unified Code for Units of Measure (UCUM). This value set includes all possible UCUM codes used for distance measures - that it is, all units of length which have the same canonical unit as 'm' (metre) FHIR
all-languages N This value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47) (see http://tools.ietf.org/html/bcp47) Other
21 all-resource-types All fhir resource types (including abstract resources) Internal
all-time-units Unified Code for Units of Measure (UCUM). This value set includes all possible UCUM codes used for units of time FHIR null all-types N A list of all the concrete types defined in this version of the FHIR specification measures (Age, Duration etc.) - Abstract Types, Data Types and Resource Types. Internal 25 allelename European Bioinformatics Institute Other 1045 allerg-intol-substance-exp-risk The risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to that it is, all units which have the substance (including pharmaceutical products). Other same canonical unit as 'a' (year) 940 FHIR
allergy-intolerance-category Category of an identified substance associated with allergies or intolerances. Internal
allergy-intolerance-criticality Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. Internal
allergy-intolerance-type Identification of the underlying physiological mechanism for a Reaction Risk. Internal
allergyintolerance-clinical Preferred value set for AllergyIntolerance Clinical Status. Other
allergyintolerance-code I This value set includes concept codes for specific substances/pharmaceutical products, allergy or intolerance conditions, and negation/exclusion codes to specify the absence of specific types of allergies or intolerances. Other, SNOMED CT
allergyintolerance-verification Preferred value set for AllergyIntolerance Verification Status. The verification status to support or decline the clinical status of the allergy or intolerance. Other
animal-breeds animal-tissue-type I This example value set defines a set of codes that can be used to indicate breeds A tissue type of species. SNOMED CT an animal. 422 Internal
animal-genderstatus appointment-cancellation-reason I This example value set defines a set of codes that can be used to indicate reasons for the current state cancellation of the animal's reproductive organs. Internal an appointment. 418 Other
animal-species appointment-recurrrence-type This example value set defines a set of codes that can be used to indicate species The recurrence type of animal patients. SNOMED CT a recurring appointment. 420 FHIR
appointment-cancellation-reason appointmentresponse-status This example value set defines The Participation status for a set of reasons participant in response to a request for the cancellation of an appointment. 1381 Internal
appointmentstatus The free/busy status of an appointment. Internal
approach-site-codes I This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar. SNOMED CT
assert-direction-codes artifactassessment-disposition The type of direction to use Possible values for assertion. Internal 706 assert-operator-codes The type the disposition of operator to use a comment or change request, typically used for assertion. comments and change requests, to indicate the disposition of the responsible party towards the changes suggested by the comment or change request. Internal
assert-response-code-types artifactassessment-workflow-status The type Possible values for the workflow status of response code the comment or assessment, typically used to use for assertion. coordinate workflow around the process of accepting and rejecting changes and comments on the artifact. Internal
asset-availability I This value set has asset availability codes. Internal
audit-entity-type audit-entity-detail-type-example I Code Example values for the entity type involved of additional detail about an entity used in the audit an event. Other, Internal
audit-event-action Indicator value set for type of action performed during the event that generated the event. Internal
audit-event-outcome Indicates Example codes to indicate whether the event succeeded or failed. Internal
audit-event-sub-type audit-event-outcome-detail-example I More Example values to indicate more detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions. DICOM, Internal reason for outcome. 464 Other
audit-event-type audit-event-severity Event Types for Audit Events - defined by DICOM with some FHIR specific additions. DICOM, Other The severity of the audit entry. 462 Internal
audit-source-type audit-event-sub-type-example I The Example values for more detailed code concerning the type of process where the audit event originated from. Other - defined by DICOM with some additional FHIR, HL7, and other additions. 466 DICOM, Internal
basic-resource-type audit-event-type-example I This Example 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 Event Categories for Audit Events - defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. DICOM with some FHIR specific additions. DICOM, Other
benefit-network This value set includes a smattering of Network type codes. Other
benefit-term This value set includes a smattering of Benefit Term codes. Other
benefit-type This value set includes a smattering of Benefit type codes. Other
benefit-unit This value set includes a smattering of Unit type codes. Other
binding-strength N Indication of the degree of conformance expectations associated with a binding. Internal
biologicallyderived-product-property-type-codes I This value set can enumerate ISBT 128 Codes published by ICCBBA as a part of the ISBT 128 standard. These example codes represent data elements defined in ST-027 ISBT 128 Dictionary of Standard Data Elements and are used to define data structure and format expectations for electronic exchange with the ISBT 128 standard. Internal
43 biologicallyderived-product-status I Biologically Derived Product Status. Internal
biologicallyderived-productcodes I This value set enumerates ISBT 128 Product Description Codes© published by ICCBBA as a part of the ISBT 128 standard. These codes support characterization and classification of medical products of human origin inclusive of processing conditions such as additives, volumes and handling conditions. Internal
body-site I This value set includes all codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 442083009 (Anatomical or acquired body site (body structure)). SNOMED CT
bodysite-laterality bodystructure-bodylandmarkorientation-clockface-position I Select SNOMED CT codes. A set of codes that describe a things orientation based on a hourly positions of a clock face. 287 SNOMED CT
bodystructure-code I This value set includes all codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 442083009 (Anatomical or acquired body site (body structure)). 118956008 (Body structure, altered from its original anatomical structure (morphologic abnormality)). SNOMED CT
142 bodystructure-laterality I SNOMED-CT concepts modifying the laterality of the anatomic location SNOMED CT
bodystructure-relative-location SNOMED-CT concepts modifying the anatomic location SNOMED CT
bundle-type N Indicates the purpose of a bundle - how it is intended to be used. Internal
c80-facilitycodes I 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
c80-practice-codes I 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 capability-format-type Common format types for FHIR. Internal, Other
capability-statement-kind N How a capability statement is intended to be used. Internal
care-plan-activity-kind care-plan-activity-performed Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity. Internal 145 care-plan-activity-outcome I Example codes indicating the outcome of a care plan activity. activity that was performed. Note that these are in no way complete and might not even be appropriate for some uses. SNOMED CT
care-plan-category I Example codes indicating the category a care plan falls within. Note that these are in no way complete and might not even be appropriate for some uses. SNOMED CT
care-plan-intent Codes indicating the degree of authority/intentionality associated with a care plan. Internal
care-team-category I Indicates the type of care team. LOINC
care-team-status Indicates the status of the care team. Internal
catalogType catalog-type I Other Description Needed Here 968 Internal
cdshooks-indicator This value set captures the set of indicator codes defined by the CDS Hooks specification. Other
certainty-subcomponent-rating characteristic-offset The quality rating of the subcomponent of a quality of evidence rating. Other 1361 certainty-subcomponent-type I Other Reference point for characteristic.valueQuantity. 1359 Internal
chargeitem-billingcodes claim-careteamrole Example This value set of codes that can be used for billing purposes. includes sample Claim Care Team Role codes. Other
chargeitem-status claim-decision Codes identifying the lifecycle stage of a ChargeItem. This value set includes Claim Adjudication Decision codes. Internal
chromosome-human claim-decision-reason Chromosome number for human. Other 224 claim-careteamrole I This value set includes sample example Claim Care Team Role Adjudication Decision Reason codes. 586 Internal
claim-exception I This value set includes sample Exception codes. Other
claim-informationcategory This value set includes sample Information Category codes. Other
claim-modifiers I This value set includes sample Modifier type codes. Other
536 claim-outcome This value set includes Claim Processing Outcome codes. Internal
claim-subtype I This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation. Other
claim-type This value set includes Claim Type codes. Other
claim-use The purpose of the Claim: predetermination, preauthorization, claim. Internal
clinical-findings I This value set includes all the "Clinical finding" [SNOMED CT](http://snomed.info/sct) codes - concepts where concept is-a 404684003 (Clinical finding (finding)). SNOMED CT
clinicalimpression-prognosis clinical-use-definition-category Example value set A categorisation for clinical impression prognosis. SNOMED CT 160 clinicalimpression-status Codes that reflect the current state of a clinical impression within its overall lifecycle. use information item. Internal
clinvar clinical-use-definition-type NCBI central repository for curating pathogenicity Overall defining type of potentially clinically relevant variants Other this clinical use definition. 1041 Internal
code-search-support The degree to which the server supports the code search parameter on ValueSet, if it is supported. Internal
codesystem-content-mode N The extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource. Internal
codesystem-hierarchy-meaning N The meaning of the hierarchy of concepts in a code system. Internal
color-codes This value set includes color codes - either the color names as defined in [CSS4](https://www.w3.org/TR/css-color-4/), or any valid RGB code (```#RRGGBB``` in Hex). Internal
784 combined-dose-form I Dose forms for a product as a whole, considering all individual parts, but before any mixing Internal
common-tags I Common Tag Codes defined by FHIR project 79 Other, V3
communication-category I Codes for general categories of communications such as alerts, instructions, etc. Other
communication-not-done-reason I Codes for the reason why a communication did not happen. Other
174 communication-request-status-reason I Example codes indicating the reason why a CommunicationRequest is on hold or revoked. Note that these are in no way complete and might not even be appropriate for some uses. SNOMED CT
communication-topic I Codes describing the purpose or content of the communication. Other
compartment-type comparison-operation Which type a compartment definition describes. Additional Binding Purpose Internal
composite-measure-scoring The composite scoring method of the measure. Other 773 composition-altcode-kind compartment-type Indicates the Which type of use for which the code is defined. Other a compartment definition describes. 1405 Internal
composition-attestation-mode The way in which a person authenticated a composition. Internal
composition-status The workflow/clinical status of the composition. Internal
concept-map-equivalence concept-map-relationship The degree of equivalence relationship between concepts. Internal
concept-property-type N The type of a property value. Internal
concept-subsumption-outcome Description Needed Here Internal
conceptmap-attribute-type The subsumption relationship between code/Coding "A" and code/Coding "B". There are 4 possible codes to be returned: equivalent, subsumes, subsumed-by, and not-subsumed. If the server is unable to determine the relationship between the codes/Codings, then it returns an error (i.e. an OperationOutcome). type of a ConceptMap mapping attribute value. Internal
1238 conceptmap-property-type The type of a ConceptMap mapping property value. Internal
conceptmap-unmapped-mode Defines which action to take if there is no match in the group. Internal
condition-category concrete-fhir-types Other List of all non-abstract types, data types and resources 162 Internal
condition-cause condition-category I Example Preferred value set for Cause of Condition codes SNOMED CT Categories. 965 Other
condition-clinical Preferred value set for Condition Clinical Status. Other
condition-code I Example value set for Condition/Problem/Diagnosis codes. SNOMED CT
condition-outcome Example value set for condition outcomes. SNOMED CT 967 condition-predecessor I Example value set for condition predecessor codes. outcomes. SNOMED CT
condition-severity Preferred value set for Condition/Diagnosis severity grading. SNOMED CT
condition-stage I Example value Value set for stages of cancer and other conditions. SNOMED CT
condition-stage-type I Example value set for the type of stages of cancer and other conditions SNOMED CT
condition-ver-status The verification status to support or decline the clinical status of the condition or diagnosis. Other
conditional-delete-status N A code that indicates how the server supports conditional delete. Internal
conditional-read-status N A code that indicates how the server supports conditional read. Internal
conformance-expectation Other Description Needed Here 919 Internal
consent-action I This value set includes sample Consent Action codes. Other
consent-category consent-category-example I This value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes; HL7 VALUE SET: ActConsentType(2.16.840.1.113883.1.11.19897); examples of US realm consent directive legal descriptions and references to online and/or downloadable forms such as the SSA-827 Authorization to Disclose Information to the Social Security Administration; and other anticipated consent directives related to participation in a clinical trial, medical procedures, reproductive procedures; health care directive (Living Will); advance directive, do not resuscitate (DNR); Physician Orders for Life-Sustaining Treatment (POLST) Other, LOINC
consent-content-class This value set includes the FHIR resource types, along with some other important content class codes 747 Other
consent-content-code I This example value set contains all LOINC code LOINC
consent-data-meaning How a resource reference is interpreted when testing consent restrictions. Internal
consent-policy I This value set includes sample Regulatory consent policy types from the US and other regions. Other
consent-provision-type How a rule statement is applied, such as adding additional consent or removing consent. Internal
consent-state-codes Indicates the state of the consent. Internal
consistency-type consent-verification I FluidConsistencyType : Codes used to represent the consistency of fluids and liquids provided to the patient. This value set includes concepts from [SNOMED CT](http://snomed.info/sct)(US Extension) where concept is a 435681000124103 (Dietary liquid consistency diet (regime/therapy)). It is provided as a suggestive example. SNOMED CT base Consent Verification codes. 389 Other
constraint-severity N SHALL applications comply with this constraint? Internal
contact-point-system N Telecommunications form for contact point. Internal
contact-point-use N Use of contact point. Internal
container-cap I Color of the container cap. Other
container-material I This value set includes SNOMED CT codes for materials that specimen containers are made of SNOMED CT
1400 containerdevice-code I Codes for specimen container devices. SNOMED CT
contract-action I This value set includes sample Contract Action codes. Other
contract-actionstatus I This value set contract specific codes for action status. Internal
contract-actorrole I This value set includes sample Contract Actor Role codes. Other
contract-assetcontext I This value set contract specific codes for asset context. Internal
contract-assetscope I This value set contract specific codes for asset scope. Internal
contract-assetsubtype I This value set contract specific codes for asset subtype. Internal
contract-assettype I This value set contract specific codes for asset type. Internal
contract-content-derivative I This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses. Other
contract-decision-mode I This value set contract specific codes for decision modes. Internal
contract-definition-subtype I This value set contract specific codes for status. Internal
contract-definition-type I This value set contract specific codes for status. Internal
contract-expiration-type I This value set contract specific codes for status. Internal
contract-legalstate This value set contract specific codes for status. Internal
contract-party-role I This value set contract specific codes for offer party participation. Internal
contract-publicationstatus This value set contract specific codes for status. Internal
contract-scope I This value set contract specific codes for scope. Internal
contract-security-category I This value set contract specific codes for security category. Internal
contract-security-classification I This value set contract specific codes for security classification. Internal
contract-security-control I This value set contract specific codes for security control. Internal
contract-signer-type This value set includes sample Contract Signer Type codes. Other
contract-status This value set contract specific codes for status. Internal
contract-subtype I This value set includes sample Contract Subtype codes. Other
contract-term-subtype I This value set includes sample Contract Term SubType codes. Other
contract-term-type I This value set includes sample Contract Term Type codes. Other
contract-type I This value set includes sample Contract Type codes. Other
contributor-type country The type This value set defines a base set of contributor. Internal 93 copy-number-event Copy Number Event. Other 226 cosmic COSMIC : Catalogue Of Somatic Mutations In Cancer codes for countries. Note: The codes for countries are taken from [ISO 3166](https://www.iso.org/iso-3166-country-codes.html). Other
coverage-class This value set includes Coverage Class codes. Other
coverage-copay-type This value set includes sample Coverage Copayment Type codes. Other
coverage-financial-exception I This value set includes Example Coverage Financial Exception Codes. Other
coverage-selfpay coverage-kind Other The kind of coverage: insurance, selfpay or other. 525 Internal
coverage-type This value set includes Coverage Type codes. Other
coverageeligibilityresponse-ex-auth-support I This value set includes CoverageEligibilityResponse Auth Support codes. Other
currencies N Currency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html) Other
data-absent-reason N Used to specify why the normally expected content of the data element is missing. Other
data-types N A version specific list of the data types defined by the FHIR specification for use as an element type (any of the FHIR defined data types). All fhir datatypes Internal
dataelement-sdcobjectclassproperty datestype 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 This value set includes sample Dates Type codes. 911 Internal
days-of-week N The days of the week. Internal
dbsnp DBSNP : Single Nucleotide Polymorphism database Other 284 defined-types definition-method N I A list of all the concrete types defined in this version of the FHIR specification - Data Types and Resource Types. The method used to define, describe, or determine a characteristic value. Internal
definition-resource-types A list of all the All Resource Types that represent definition resource types defined in this version of the FHIR specification. resources Internal
definition-topic I High-level categorization of the definition, used for searching, sorting, and filtering. Other
definition-use N Structure Definition Use Codes / Keywords Other
1190 deliverydevice-code I Codes for devices used for enteral formula delivery. SNOMED CT
designation-use N Details of how a designation would be used SNOMED CT
detectedissue-category Kinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. V3
detectedissue-code Codes for issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. V3
204 detectedissue-example-medication-class I Example value set illustrating medication classes. Internal
detectedissue-expected-onset-type I Example value set illustrating the expected onset type. SNOMED CT
detectedissue-management-code I Example value set illustrating the type action (management) required. Internal
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
detectedissue-severity Indicates the potential degree of impact of the identified issue on the patient. Internal
206 detectedissue-status Indicates the status of a detected issue Internal
device-action Example codes indicating the change that happened to the device during the procedure. Note that these are in no way complete and might not even be appropriate for some uses. SNOMED CT
device-component-property device-availability-status Codes for identifying device properties. This is based upon IEEE/HCD specified codes. Other The availability status of the device. 634 Internal
device-definition-status device-category I Codes representing the current status The association state of the device - on, off, suspended, etc. device. Internal
device-kind device-correctiveactionscope Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example. SNOMED CT Device - Corrective action scope 208 Internal
device-nametype The type of name the device is referred by. Internal
device-productidentifierinudi Device Production Identifier in UDI Internal
1083 device-property-type I The fixed characteristics or conditions of the device. These codes are for example purposes only. Internal
device-safety I Codes used to identify medical devices safety characteristics. These codes are taken from the [NCI Thesaurus](https://ncit.nci.nih.gov/ncitbrowser/pages/home.jsf) and are provided here as a suggestive example. Other
device-statement-status device-specification-category I A coded concept indicating the current status The kind of standards used by the Device Usage. device. Internal
device-status device-specification-type I The availability status type or specification of the device. Internal a standard that devices can adhere to 209 Other
device-status-reason device-status The availability status reason of the device. Other Device record. 1081 Internal
device-type I Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example. Other, SNOMED CT
1376 device-versiontype I Describes the type of version Other
devicealert-activationState DeviceAlert Activation State Codes Internal
devicealert-annunciation DeviceAlert Annunciation Codes Internal
devicealert-category I DeviceAlert Category Codes Internal
devicealert-condition DeviceAlert Condition Codes Other
devicealert-manifestation DeviceAlert Manifestation Codes Internal
devicealert-presence DeviceAlert Presence Codes Internal
devicealert-priority DeviceAlert Priority Codes Internal
devicealert-signalType I DeviceAlert Signal Type Codes Internal
devicealert-status DeviceAlert Status Codes Internal
devicealert-type DeviceAlert Type Codes Internal
deviceassociation-association-status Codes that describe the state of a device’s association (e.g., implanted, attached, on, off, standby, defective). Internal
deviceassociation-relationship DeviceAssociation Relationship Codes Internal
deviceassociation-status DeviceAssociation Status Codes Internal
deviceassociation-status-reason DeviceAssociation Status Reason Codes Internal
devicedefinition-regulatory-identifier-type Regulatory Identifier type Internal
devicedefinition-relationtype Description Needed Here Internal
devicemetric-type Codes used to identify health care device metric types and units and component types as part of the ISO/IEEE 11073-10101 Medical Device Communication Nomenclature. Other
diagnosis-role This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record. Other
diagnostic-report-status The status of the diagnostic report. Internal
diagnostic-service-sections I This value set includes all the codes in HL7 V2 table 0074. V2
dicm-405-mediatype diagnosticreport-relevant-information-types I DICOM Valueset specifying how referenced information is considered relevant in a DiagnosticReport. ​908 Internal
diet-type Codes that can be used to indicate the type of food being ordered for a patient. This value set is provided as a suggestive example. It includes codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182922004 (Dietary regime (regime/therapy)) is Dietary Regime (182922004) and its sub-concepts, Enteral Feeding (229912004) and its sub-concepts, Mixed Breast Milk and Bottle Feeding (35011000087100), Breast Milk Feeding (1297276008), Bottle Feeding of Patient (40043006). SNOMED CT
discriminator-type N How an element value is interpreted when discrimination is evaluated. Internal
91 disease-status I The status of a disease or symptom. SNOMED CT
disease-symptom-procedure I A symptom, disease or procedure. SNOMED CT
distance-units Unified Code for Units of Measure (UCUM). This value set includes all common UCUM codes used for units of distance - that it is, all commonly used units which have the same canonical unit as 'm' (meter) FHIR
doc-section-codes I Document section codes (LOINC codes used in CCDA sections). LOINC
doc-typecodes FHIR Document Codes - all LOINC codes where scale type = 'DOC'. LOINC
document-mode N Whether the application produces or consumes documents. Internal
document-reference-status The status of the document reference. Internal
document-relationship-type The type of relationship between documents. Internal
244 dosage-condition-code Additional Binding Purpose Internal
dose-rate-type dosage-condition-details The kind of dose or rate specified. Dosage Condition Details Example ValueSet Other SNOMED CT
981 dose-limit-scope Additional Binding Purpose Internal
duration-units N Unified Code for Units of Measure (UCUM). This value set includes all common UCUM codes used for Duration - that it is, all commonly used units which have the same canonical unit as 'a' (year) FHIR
61 edible-substance-type This value set represents codes for types of edible substances. It include codes from [SNOMED CT](http://snomed.info/sct) where concept 762766007 Edible Substance (substance) and its sub-concepts, Infant Formula (412413001) and its sub-concepts, Enteral and Supplement Feeds (346415002) and its sub-concepts, Water (11713004), Potable Water (890302005) and its sub-concepts, and Tap Water (444923006). SNOMED CT
effect-estimate-type elementdefinition-types Allowed types for FHIR elements in ElementDefinition.type.code Internal, Other
Whether the effect estimate is an absolute effect estimate (absolute difference) or a relative effect estimate (relative difference), and the specific type eligibility I Example set of effect estimate (eg relative risk or median difference). HealthcareService eligibility codes Other Internal
1355 eligibility-outcome The outcome of the processing. Internal
eligibilityrequest-purpose A code specifying the types of information being requested. Internal
eligibilityresponse-purpose A code specifying the types of information being requested. Internal
encounter-admit-source This value set defines a set of codes that can be used to indicate from where the patient came in. Other
257 encounter-businessstatus-emergency Business statuses for emergency encounters. Internal
encounter-businessstatus-inpatient Business statuses for inpatient encounters. Internal
encounter-businessstatus-outpatient Business statuses for outpatient encounters. Internal
encounter-businessstatus-type I The kind of workflow the business status is tracking. Internal
encounter-diagnosis-use What a specific Encounter/EpisodeOfCare `diagnosis.condition` is to be used for. Internal
encounter-diet I This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. Other
encounter-discharge-disposition I This value set defines a set of codes that can be used to where the patient left the hospital. Other
encounter-location-status The status of the location. Internal
encounter-participant-type This value set defines a set of codes that can be used to indicate how an individual participates in an encounter. V3, Other
encounter-reason This examples value set defines the set of codes that can be used to indicate reasons for an encounter. SNOMED CT
261 encounter-reason-use I What a specific Encounter/EpisodeOfCare `reason.value` is to be used for. Internal
encounter-special-arrangements This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit. Other
encounter-special-courtesy This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. V3
encounter-status Current state of the encounter. Internal
246 encounter-subject-status I This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter Other
encounter-type I This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided. Other
endpoint-connection-type I This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values. Other
498 endpoint-environment The environment type of the endpoint. Internal
endpoint-payload-type I This is an example value set defined by the FHIR project, that could be used to represent possible payload document types. Other
endpoint-status The status of the endpoint. Internal
ensembl enrollment-outcome Other The outcome of the processing. 1040 Internal
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
entformula-additive EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber components to be provided in addition added to or mixed with the base formula. This value set is provided as a suggestive example. diet. Other 392 SNOMED CT
entformula-type EnteralFormulaType SupplementType : Codes for type of enteral formula nutritional supplements to be administered provided to the patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) 346415002 (Enteral and is provided as a suggestive example. supplement feeds (product)). SNOMED CT
episode-of-care-status The status of the episode of care. Internal
episodeofcare-type I This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record. Other
event-capability-mode N The mode of a message capability statement. Internal
event-resource-types A list of all the All Resource Types that represent event resource types defined in this version of the FHIR specification. resources Internal
event-status Codes identifying the lifecycle stage of an event. Internal
event-timing N Real world Real-world event relating to the schedule. Internal, V3
75 evidence-variable-classifier I Disease, diagnosis, or condition. Internal
evidence-quality evidence-variable-constraint I A rating system that describes the quality of evidence rule, such as the GRADE, DynaMed, a format or Oxford CEBM systems. other expectation, for the data values. Other Internal
1020 evidence-variable-definition I Examples of terms that represent an evidence variable definition. SNOMED CT
evidence-variant-state evidence-variable-definition-modifier-code I Examples of terms that represent an evidence variable definition modifier code. SNOMED CT
Used for results by exposure in variant states such evidence-variable-event The event used as low-risk, medium-risk and high-risk states. a base point (reference point) in time. Other Internal
1353 evidence-variable-unacceptable-data-handling I A method or transformation applied for data that does not match required patterns. Internal
ex-benefitcategory I This value set includes examples of Benefit Category codes. Other
ex-diagnosis-on-admission This value set includes example Diagnosis on Admission codes. Other
ex-diagnosisrelatedgroup I This value set includes example Diagnosis Related Group codes. Other
ex-diagnosistype This value set includes example Diagnosis Type codes. Other
ex-paymenttype This value set includes example Payment Type codes. Other
ex-procedure-type This value set includes example Procedure Type codes. Other
ex-program-code I This value set includes sample Program Reason Span codes. Other
ex-revenue-center I This value set includes sample Revenue Center codes. Other
example-expansion example This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC
example-characteristic-codes I This value set contains an example set of LOINC codes that might be used to define common characteristics for grouping individuals in FHIR Group resources. LOINC
null example-comparison-group I Example values for defining comparison groups. Internal
example-extensional example-cpt-all A value set that includes all CPT codes Other
example-expansion This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC
example-filter ACME Codes for Cholesterol: Plasma only - demonstrating the use of a filter defined in a CodeSystem Internal
example-intensional This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC
examplescenario-actor-type example-metadata The type This is an example value set that illustrates usage of actor - system or human. the metadata resource elements introduced in R5 Internal
858 example-metadata-2 This is an example value set that illustrates usage of the metadata resource elements introduced in R5 Internal
expansion-parameter-source example-supplement Declares what ACME Codes for Cholesterol: Plasma only - demonstrating the source use of a parameter is. supplement defined in a CodeSystem Other Internal
1278 examplescenario-instance-type Types of resource structures that can be passed in or out of exchange operations. Not necessarily FHIR. Other, V2
expansion-processing-rule examplescenario-operation-codes Defines how concepts This value set defines a set of codes that are processed into used to indicate the expansion when it's for UI presentation. Other supported operations of a testing engine or tool. 1280 Internal
explanationofbenefit-status A code specifying the state of the resource instance. Internal
exposure-state expression-language Whether the results by exposure is describing the results for the primary exposure The media type of interest (exposure) or the alternative state (exposureAlternative). Internal expression language. 1351 Other
expression-language extended-resource-types The media type of Current and past FHIR resource types (deleted or renamed), and additional resource types. Note that the expression language. binding to additional resources is not version fixed, and will change over time Other, Internal
extension-context-type N How an extension context is interpreted. Internal
feeding-device fhir-types Materials used or needed to feed the patient. All FHIR types Internal, SNOMED CT Internal
961 fhirpath-types All FHIRPath data types Internal
filter-operator N The kind of operation to perform as a part of a property based filter. Internal
flag-category I Example list of general categories for flagged issues. (Not complete or necessarily appropriate.) Other
flag-code I Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) SNOMED CT
flag-status Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error. Internal
fm-status This value set includes Status codes. Internal
food-type I This value set represents codes for types of foods and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 255620007 (Foods (substance)). SNOMED CT
formatcodes forms I 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 This value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at https://confluence.hl7.org/display/SD/Format+Codes+for+IHE+XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying includes a document encoding, structure and template. The actual list sample set of codes here is incomplete Forms codes. Other
forms frequency-unit This value set includes a sample set of Forms codes. Other Frequency units (i.e. per time-duration-unit). 37 FHIR
fundsreserve This value set includes sample funds reservation type codes. Other
gender-identity global-langpack-support This example value set defines a set of codes that can be used to indicate How a patient's gender identity. server supports global language packs Internal
genenames HGNC: Human Gene Nomenclature Committee Other 281 goal-acceptance-status goal-accept-status Codes indicating that identify whether the goal has been accepted by a stakeholder. Other or not. 917 Internal
goal-achievement Describes the progression, or lack thereof, towards the goal against the target. Other
goal-category I Example codes for grouping goals to use for filtering or presentation. Other
275 goal-description I Example value set for Goal descriptions. SNOMED CT
goal-priority Indicates the level of importance associated with reaching or sustaining a goal. Other
goal-start-event I Identifies types of events that might trigger the start of a goal. SNOMED CT
goal-status Codes that reflect the current state of a goal and whether the goal is still being targeted. Internal
goal-status-reason I Example codes indicating Codes to identify the reason for a current lifecycle status. Note that these are in no way complete and might not even be appropriate for some uses. Internal SNOMED CT
277 group-characteristic-combination Logical grouping of characteristics for the Group Resource. Internal
graph-compartment-rule group-code How a compartment must A code that describes the use of the group. The use of the group usually dictates what kind of entities can be linked. members of the group Internal
graph-compartment-use group-involvement I Defines A code that describes how a compartment rule is used. member of the group participates in the group. Internal
282 group-involvement-set I A code that describes how a member of the group participates in the group. Other
group-measure group-membership-basis Possible Basis for membership in a group measure aggregates (E.g. Mean, Median). Internal
group-type Types of resources that are part of group. Internal
284 guidance-module-code I Example guidance module codes. Internal
guidance-response-status The status of a guidance response. Internal
guide-page-generation A code that indicates how the page is generated. Internal
guide-parameter-code Code of parameter that is input Codes used to the guide. define implementation guide parameters Internal
handling-condition I Set of handling instructions prior testing of the specimen. Other
history-absent-reason I Codes describing the reason why a family member's history is not available. Other
history-status A code that identifies the status of the family history record. Internal
http-verb N HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details. Internal
624 iana-link-relations Link Relation Types defined at https://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 Internal
icd-10 I This value set includes sample ICD-10 codes. Internal
icd-10-procedures I This value set includes sample ICD-10 Procedure codes. Internal
identifier-type N A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. V2
identifier-use N Identifies the purpose for this identifier, if known . Internal
identity-assuranceLevel The level of confidence that this link represents the same actual person, based on NIST Authentication Levels. Internal
immunization-evaluation-dose-status imagingselection-2dgraphictype The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists type of or contains concepts to support 2D coordinates describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example. Other 2D image region. 301 Internal
immunization-evaluation-dose-status-reason imagingselection-3dgraphictype The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists type of or contains concepts to support coordinates describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example. 3D image region. Other 303 Internal
immunization-evaluation-status imagingselection-status The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the current status of the evaluation for vaccine administration event. Other ImagingSelection. 299 Internal
immunization-evaluation-target-disease imagingstudy-status The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists status of or contains concepts to support describing the disease that the evaluation is against. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy. SNOMED CT ImagingStudy. 300 Internal
immunization-function The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the function a practitioner or organization may play in the immunization event. This value set is provided as a suggestive example. V2
immunization-origin I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the data when the report of the immunization event is not based on information from the person, entity or organization who administered the vaccine. This value set is provided as a suggestive example. Other
immunization-reason I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was administered. This value set is provided as a suggestive example. SNOMED CT
immunization-route I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the administrative routes used during vaccination. This value set is provided as a suggestive example. V3
immunization-site I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the body site where the vaccination occurred. This value set is provided as a suggestive example. V3
immunization-status The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the current status of the administered dose of vaccine. Internal
immunization-status-reason I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was not administered. This value set is provided as a suggestive example. 992 V3
immunization-subpotent-reason immunization-target-disease I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a disease that the dose is considered to be subpotent. being administered against. This value set is provided as a suggestive example. Other example and includes SNOMED CT concepts from the 64572001 (Disease) hierarchy. 993 SNOMED CT
immunization-target-disease immunization-vaccine-funding-program I The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the disease programs that the dose is being administered against. a patient may be eligible for to cover vaccine administration costs. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy. example. SNOMED CT LOINC
1047 inactive HL7 v3 ActMood Predicate codes, including inactive codes V3
implantStatus ingredient-function I A set codes that define the functional status classification of an implanted device. Other the ingredient identifying its precise purpose(s) in the drug product (beyond e.g. active/inactive). 1282 Internal
inactive ingredient-manufacturer-role HL7 v3 ActMood Predicate codes, including inactive codes V3 The way in which this manufacturer is associated with the ingredient. For example whether it is a possible one (others allowed), or an exclusive authorized one for this ingredient. Note that this is not the manufacturing process role. null Internal
instance-availability ingredient-role I Availability A classification of the resource. DICOM ingredient identifying its purpose within the product. ​811 Internal
insuranceplan-applicability Whether the cost applies to in-network or out-of-network providers. Other
insuranceplan-type insuranceproduct-type I This example value set defines a set of codes that can be used to indicate a type of insurance plan. Other
870 interactant I An interactant - a substance that may have a clinically significant effect on another. SNOMED CT
intervention interaction-effect I This value set includes sample Intervention codes. A interaction effect of clinical use of a medication or other substance. Internal SNOMED CT
532 interaction-incidence I A categorisation for incidence of occurence of an interaction. Internal
investigation-sets interaction-management I Example value set A type of management for investigation type. an interaction, contraindication or undesirable effect of a medication or other substance. SNOMED CT
invoice-priceComponentType interaction-trigger Codes indicating the kind of the price component. FHIR RESTful interaction codes used for SubscriptionTopic trigger. Internal
868 interaction-type I A categorisation for an interaction between two substances. Internal
invoice-status Codes identifying the lifecycle stage of an Invoice. Internal
iso3166-1-2 I This value set defines the ISO 3166 Part 1 2-letter codes Other
iso3166-1-3 This value set defines the ISO 3166 Part 1 3-letter codes Other
iso3166-1-N This value set defines the ISO 3166 Part 1 Numeric codes Other
issue-severity N How the issue affects the success of the action. Internal
issue-type N A code that describes the type of issue. Internal
item-type Distinguishes groups from questions and display text and indicates data type for questions. Internal
jurisdiction N item-type-useable This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended Item types allowed to be used. Note: The codes for countries and country subdivisions are taken from [ISO 3166](https://www.iso.org/iso-3166-country-codes.html) while appear on Questionnaire.type (excludes the codes for "supra-national" regions are from [UN Standard country or area codes for statistical use (M49)](http://unstats.un.org/unsd/methods/m49/m49.htm). Other abstract 'questionnaire' code. 48 Internal
knowledge-resource-types knowledge-representation-level A list of all the knowledge resource types defined in this version of the FHIR specification. Internal 1062 language-preference-type This value set defines the set of codes for describing the type or mode of the patient's preferred language. representation level, narrative, semi-structured, structured, and executable Internal
languages This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) (see http://tools.ietf.org/html/bcp47) Other
ldlcholesterol-codes legal-status-of-supply LDL Cholesterol codes - measured or calculated LOINC 959 library-type I The type of knowledge asset this library contains. Other prescription supply types appropriate to a medicinal product 763 Internal
link-type N The type of link between this patient Patient resource and another patient Patient/RelatedPerson resource. Internal
list-empty-reason General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list). Other
list-example-codes I Example use codes for the List resource - typical kinds of use. Other
list-item-flag I Example Item Flags for the List Resource. In this case, these are the kind of flags that would be used on a medication list at the end of a consultation. Other
list-mode The processing mode that applies to this list. Internal
list-order Base values for the order of the items in a list resource. Other
list-status The current state of the list. Internal
location-mode location-characteristic I Indicates whether a resource instance represents a specific location or a class Example Set of locations. Location Characteristics Internal
location-physical-type location-form I This example value set defines a set of codes that can be used to indicate the physical form of the Location. Other
328 location-mode Indicates whether a resource instance represents a specific location or a class of locations. Internal
location-status Indicates whether the location is still in use. Internal
manifestation-or-symptom I Example value set for Manifestation and Symptom codes. SNOMED CT
map-context-type manufactured-dose-form I How Dose form for a medication, as manufactured (and before any mixing etc.), not necessarily ready for administration to interpret the context. patient. Internal
map-group-type-mode If this is the default rule set to apply for the source type, or this combination of types. Internal
map-input-mode Mode for this instance of data. Internal
map-model-mode How the referenced structure is used in this mapping. Internal
map-source-list-mode If field is a list, how to manage the source. Internal
map-target-list-mode If field is a list, how to manage the production. Internal
map-transform How data is copied/created. Internal
marital-status N This value set defines the set of codes that can be used to indicate the marital status of a person. V3
match-grade measure-definition-example A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. Other 970 measure-data-usage I The intended usage Example Measure Definitions for supplemental data elements in the measure. Other Measure Resource. 771 Internal
measure-improvement-notation measure-group-example I Observation values that indicate what change in a measurement value or score is indicative of an improvement in Example Measure Groups for the measured item or scored issue. Other Measure Resource. 1236 Internal
measure-population measure-report-evaluation-type The type of population. Other evaluation for the measure report. 765 Internal
measure-report-status The status of the measure report. Internal
measure-report-type The type of the measure report. Internal
measure-scoring measure-scoring-unit I The This is an example value set illustrating some typical scoring type of the measure. units used in quality measure specifications. Other 767 FHIR
measure-type measure-stratifier-example I The type of measure (includes codes from 2.16.840.1.113883.1.11.20368). Other Identifier subgroups in a population for measuring purposes. 769 Internal
med-admin-perform-function measure-supplemental-data-example I Other Supplemental data in a population for measuring purposes. 349 Internal
media-modality measurement-property I Detailed information about the type This value set represents codes for properties that can be measured and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept has a parent of the image - its kind, purpose, or the kind 118598001 Property of equipment used to generate it. Other measurement (qualifier value). 1001 SNOMED CT
media-type measurereport-stratifier-value-example I Codes Example Measure Stratification Value for high level media categories. Other MeasureReports Resource. 1000 Internal
media-view med-admin-perform-function I MedicationAdministration Performer Function Codes defined in SNOMED CT that can be used to record Media Recording views. SNOMED CT 337 Other
medication-admin-category I MedicationAdministration Category Codes Other 347 Internal
medication-admin-status MedicationAdministration Status Codes 340 Internal
medication-as-needed-reason I This value set includes all clinical findings from SNOMED CT - provided as an exemplar value set. SNOMED CT
medication-codes I This value set includes all drug or medicament substance codes and all pharmaceutical/biologic products from SNOMED CT - provided as an exemplar value set. SNOMED CT
375 medication-dose-aid I Medication Dose Aids Internal
medication-form-codes I This value set includes all dose form codes from SNOMED CT - provided as an exemplar. SNOMED CT
374 medication-ingredientstrength Medication Ingredient Strength Codes Internal
medication-statement-category medication-intended-performer-role Medication Status Codes Intended Performer Role Internal
Other medication-statement-adherence I MedicationStatement Adherence Codes Internal
370 medication-statement-medication-codes I MedicationStatement Codes for Medications taken (or not taken) Other, SNOMED CT
medication-statement-status Medication MedicationStatement Status Codes Internal
medication-status Medication Status Codes Internal
medicationdispense-category I MedicationDispense Category Codes 1314 Internal
medicationdispense-performer-function I MedicationDispense Performer Function Codes Other
medicationdispense-status MedicationDispense Status Codes Other 1312 Internal
medicationdispense-status-reason I MedicationDispense Status Reason Codes Other Internal
1316 medicationrequest-category I MedicationRequest Category Codes Internal
medicationknowledge-characteristic medicationrequest-course-of-therapy MedicationKnowledge Characteristic MedicationRequest Course of Therapy Codes Other
1337 medicationrequest-dispenser-instructions I MedicationRequest Dispenser Insruction Codes Internal
medicationknowledge-package-type medicationrequest-intent MedicationKnowledge Package Type MedicationRequest Intent Codes Other Internal
1339 medicationrequest-status MedicationRequest Status Codes Internal
medicationknowledge-status medicationrequest-status-reason I MedicationKnowledge MedicationRequest Status Reason Codes Other
1335 medicinal-product-additional-monitoring I Extra monitoring defined for a Medicinal Product. Internal
medicationrequest-category medicinal-product-classification I MedicationRequest Category Codes This value set includes codes from the Anatomical Therapeutic Chemical Classification System - provided as an exemplar value set. Other
1322 medicinal-product-confidentiality I Confidentiality rating, e.g. commercial sensitivity for a Medicinal Product. Internal
medicationrequest-course-of-therapy medicinal-product-contact-type I MedicationRequest Course of Therapy Codes Contact type for a Medicinal Product. Other Internal
1326 medicinal-product-cross-reference-type I Relationship to another Medicinal Product. Internal
medicationrequest-intent medicinal-product-domain I MedicationRequest Intent Codes Applicable domain for this product (e.g. human, veterinary) Internal
1321 medicinal-product-name-part-type I Type of part of a name for a Medicinal Product. Internal
medicationrequest-status medicinal-product-name-type I MedicationRequest Status Codes Type of a name for a Medicinal Product. Internal
1320 medicinal-product-package-type I Types of medicinal product packs Internal
medicationrequest-status-reason medicinal-product-pediatric-use I MedicationRequest Status Reason Codes Extra measures defined for a Medicinal Product, such as heightened reporting requirements. Internal
Other medicinal-product-special-measures I Extra measures defined for a Medicinal Product, such as a requirement to conduct post-authorization studies. Internal
1324 medicinal-product-type I Overall defining type of this Medicinal Product. Internal
message-events I One of the message events defined as part of this version of FHIR. Internal
message-reason-encounter I Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. Other
message-significance-category The impact of the content of a message. Internal
message-transport N The protocol used for message transport. Other 184 Internal
messageheader-response-request HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message. Internal
924 metric-availability The availability of the means from which a device metric state/value is derived. Internal
metric-calibration-state Describes the state of a metric calibration. Internal
metric-calibration-type Describes the type of a metric calibration. Internal
metric-category Describes the category of the metric. Internal
metric-color metric-operational-status Describes the typical color operational status of representation. the DeviceMetric. Internal
metric-operational-status metric-status Describes the operational status of the DeviceMetric. DeviceMetric record. Internal
mimetypes N This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13) (see http://tools.ietf.org/html/bcp13) Other
1024 mimetypes This value set includes all possible codes from BCP-13 (see http://tools.ietf.org/html/bcp13) Other
missing-tooth-reason I This value set includes sample Missing Tooth Reason codes. Other
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
name-use N The use of a human name. Internal
name-v3-representation namingsystem-identifier-system-type A set of codes for each different representation Identifies the style of unique identifier used to identify a name. V3 namespace. 909 V2
namingsystem-identifier-type Identifies the style of unique identifier used to identify a namespace. Internal
namingsystem-type Identifies the purpose of the naming system. Internal
narrative-status The status of a resource narrative. Internal
nhin-purposeofuse This value set is suitable for use with the provenance resource. It is derived from, but not compatible with, the HL7 v3 Purpose of use Code system. Other
null not-consumed-reason I This value set represents codes for types of edible substances and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 762766007 Edible Substance (substance). SNOMED CT
note-type The presentation types of notes. Internal
nutrient-code I NutrientModifier : Codes for types of nutrients that are being modified such as carbohydrate or sodium. This value set includes codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 226355009 (Nutrients(substance)), and the concepts for Sodium, Potassium and Fluid. This is provided as a suggestive example. SNOMED CT
386 nutrition-product-category This value set represents codes for categories of nutrition products. It includes all of the codes from the Food Type Modifiers valueset. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is Breast Milk (226789007) and its sub-concepts, Infant Formula (412413001) and its sub-concepts, Enteral and Supplement Feeds (346415002) and its sub-concepts, Drinks (226465004) and its sub-concepts, Water (11713004), Potable Water (890302005) and its sub-concepts, and 444923006 (Tap Water). Other, SNOMED CT
object-lifecycle-events nutritionintake-status-reason I This example FHIR value set is comprised represents codes indicating reasons for the status of lifecycle event codes. The FHIR Actor value set is based on DICOM Audit Message, ParticipantObjectDataLifeCycle; ISO Standard, TS 21089-2017; the nutrition intake. Other SNOMED CT, Internal
null nutritionproduct-status Codes identifying the lifecycle stage of a product. Internal
object-role object-role-example I Code Example codes representing the role the entity played in the audit event. Other
observation-category Observation Category codes. Other
observation-codes I This value set includes all LOINC codes LOINC
396 observation-codes-observationorboth I LOINC concepts whose ORDER_OBS property is 'Observation' (Obs only) or 'Both'. LOINC
observation-interpretation N A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8 (Observation Interpretation), in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR in Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version. V3
399 observation-interpretation-context I Codes identifying contextual factors that affect interpretation of observations. Examples include conditions or states such as diabetic, fasting, or paraplegic that may be critical to understanding the significance of an observation. This is an example value set and implementations may use other codes or reference specific conditions as needed. Internal
observation-methods I Observation Method codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 272394005 (Technique (qualifier value)) or is-a 129264002 (Action (qualifier value)) or is-a 386053000 (Evaluation procedure(procedure)) SNOMED CT
observation-range-category Codes identifying the category of observation range. Internal
1333 observation-referencerange-normalvalue I Codes that describe the normal value in the reference range, such as “Negative” or “Absent” Internal
observation-statistics Other Description Needed Here 405 Internal
observation-status N Codes providing the status of an observation. Internal
400 observation-triggeredbytype Codes providing the type of triggeredBy observation. Internal
observation-vitalsignresult observation-vitalsign-bmi This value set indicates defines the allowed set of LOINC codes considered to be appropriate for representing body mass index (BMI) vital sign result types. The measurements in Observation.code. LOINC code for Vitals Signs panel (85353-1) is a grouping structure for a
observation-vitalsign-bodyheight This value set defines the set of vital signs and includes related links (with type=has-member) LOINC codes considered to the Observations be appropriate for representing body height (including body length) vital sign measurements in this Observation.code. LOINC
observation-vitalsign-bodytemp This value set (e.g. respiratory rate, heart rate, BP). The Blood pressure panel (85354-9) is used to group defines the component observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4). set of LOINC codes considered to be appropriate for representing body temperature vital sign measurements in Observation.code. LOINC
62 observation-vitalsign-bodyweight This value set defines the set of LOINC codes considered to be appropriate for representing body weight vital sign measurements in Observation.code. LOINC
operation-kind N observation-vitalsign-bppanel Whether This value set defines the set of LOINC codes considered to be appropriate for representing an operation is a normal operation or a query. arterial szstolic and diastolic BP panel of vital signs measurements in Observation.component.code. Internal LOINC
506 observation-vitalsign-diastolicbp This value set defines the set of LOINC codes considered to be appropriate for representing an arterial diastolic BP vital sign measurement in Observation.component.code. LOINC
operation-outcome observation-vitalsign-headcircum This value set defines the set of LOINC codes considered to be appropriate for representing head circumference vital sign measurements in Observation.code. LOINC
Operation Outcome observation-vitalsign-heartrate This value set defines the set of LOINC codes used by FHIR test servers (see Implementation file translations.xml) considered to be appropriate for representing heart rate vital sign measurements in Observation.code. LOINC
observation-vitalsign-measurement This value set includes the set of expected vital sign measurement codes. Other
412 observation-vitalsign-oxygensat This value set defines the set of LOINC codes considered to be appropriate for representing oxygen saturation vital sign measurements in Observation.code. LOINC
operation-parameter-use observation-vitalsign-panel N This value set defines the set of LOINC codes considered to be appropriate for representing a panel of vital sign measurements in Observation.code. LOINC
observation-vitalsign-resprate This value set defines the set of LOINC codes considered to be appropriate for representing respiratory rate vital sign measurements in Observation.code. LOINC
observation-vitalsign-systolicbp This value set defines the set of LOINC codes considered to be appropriate for representing an arterial systolic BP vital sign measurement in Observation.component.code. LOINC
operation-kind Whether an operation parameter is an input a normal operation or an output parameter. a query. Internal
oral-prosthodontic-material operation-parameter-scope This value set includes sample Oral Prosthodontic Material type codes. Indicates that a parameter applies when the operation is being invoked at the specified level Internal
538 operation-parameter-use Whether an operation parameter is an input or an output parameter. Internal
organization-role I This example value set defines a set of codes that can be used to indicate the role of one Organization in relation to another. Internal
organization-type I This example value set defines a set of codes that can be used to indicate a type of organization. Other
orientation-type package-material I Type for orientation. A material used in the construction of packages and their components. Internal
parameter-group package-type I Codes identifying groupings A high level categorisation of parameters; e.g. Cardiovascular. Other a package. 632 Internal
parent-relationship-codes packaging-type I The value set includes the v3 RoleCode PRN (parent), TWIN (twin) and all A type of their specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. packaging. V3 Internal
921 participant-resource-types All Resource Types that represent participant resources Internal
participant-role I Roles of participants that may be included in a care team. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization Services (qualifier value). SNOMED CT
participation-role-type This FHIR value set is comprised of Actor participation Type codes, which can be used to value FHIR agents, actors, and other role elements. The FHIR Actor participation type value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated are intended to express how the agent participated in some activity. Sometimes refered to the definition comments, then these are example FHIR codes. agent functional-role relative to the activity. Other, V3, DICOM
participationstatus The Participation status of an appointment. Internal
patient-contactrelationship N patch-operation The nature of the relationship between the patient and Codes identifying the contact person. valid FHIRPath patch operations. V2 Internal
1130 patchmimetypes This value set includes the possible codes from [BCP-13](http://tools.ietf.org/html/bcp13) that are valid for Patch formats Other
payeetype I This value set includes sample Payee Type codes. Other
payment-adjustment-reason This value set includes smattering of Payment Adjustment Reason codes. Other
600 payment-issuertype The type of payment issuer. Internal
payment-kind The type of workflow from which this payment arose. Internal
payment-outcome The outcome of the processing. Internal
payment-status This value set includes a sample set of Payment Status codes. Other
payment-type This value set includes sample Payment Type codes. Other
performer-function The types of involvement of the performer in the Event. V3
performer-role I This example value set defines the set of codes that can be used to indicate a role of a procedure performer. SNOMED CT
permitted-data-type Permitted data type for observation value. Internal
practitioner-role I This example value set defines a set of codes that can be used to indicate the role of a Practitioner. Other, SNOMED CT
prepare-patient-prior-specimen-collection I Checks on the patient prior specimen collection. All SNOMED CT concepts descendants of 703763000 |Precondition value (qualifier value)| SNOMED CT
probability-distribution-type price-component-type Codes specifying indicating the type kind of probability distribution. V3 the price component. 907 Internal
procedure-category I Procedure Category code: A selection of relevant SNOMED CT codes. SNOMED CT
procedure-code I Procedure Code: All SNOMED CT procedure codes. SNOMED CT
procedure-followup I Procedure follow up codes: A selection of SNOMED CT codes relevant to procedure follow up. SNOMED CT
procedure-not-performed-reason I Situation codes describing the reason that a procedure, which might otherwise be expected, was not performed, or a procedure that was started and was not completed. Consists of SNOMED CT codes, children of procedure contraindicated (183932001), procedure discontinued (416406003), procedure not done (416237000), procedure not indicated (428119001), procedure not offered (416064006), procedure not wanted (416432009), procedure refused (183944003), and procedure stopped (394908001). (394908001) as well as 410536001 Contraindicated (qualifier value). SNOMED CT
procedure-outcome I Procedure Outcome code: A selection of relevant SNOMED CT codes. SNOMED CT
procedure-reason I This example value set defines the set of codes that can be used to indicate a reason for a procedure. SNOMED CT
process-priority This value set includes the financial processing priority codes. Other
552 processingdevice-code I Codes for devices used in specimen processing. SNOMED CT
product-category I Biologically Derived Product Category. Internal
900 product-characteristic-codes I This value set includes all observable entity codes from SNOMED CT - provided as an exemplar value set. SNOMED CT
product-status product-intended-use Biologically Derived Product Status. The overall intended use of a product. Internal
product-storage-scale product-status BiologicallyDerived Product Storage Scale. Codes identifying the lifecycle stage of a product. Internal
program I This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties. Other
property-representation N How a property is represented when serialized. Internal
provenance-activity-type This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes. V3 438 provenance-agent-role The role that a provenance participant played Internal 1305 provenance-agent-type I The type of participation a provenance participant. code systems are: - [v3-DocumentCompletion](http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion) - [v3-DataOperation](http://terminology.hl7.org/CodeSystem/v3-DataOperation) - [v3-ActCode](http://terminology.hl7.org/CodeSystem/v3-ActCode) - [ISO Lifecycle](http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle) - [FHIR RESTful interactions](codesystem-restful-interaction.html) - [W3C PROV Activity Types](http://hl7.org/fhir/w3c-provenance-activity-type) Other
provenance-entity-role How an entity was used in an activity. Internal
provenance-history-agent-type Types of roles indicating how a particular agent was involved with the creation or modification of a resource for use when exposing event history V3
provenance-history-record-activity Codes for Provenance activities that are relevant when capturing event history for resources. V3
provider-qualification I This value set includes sample Provider Qualification codes. Other
provider-taxonomy NUCC Healthcare Provider Taxonomy codes Other
publication-status N The lifecycle status of an artifact. Internal
quality-type qualification-status Type for quality report. Set of statuses that apply to qualifications of practitioners and organizations Internal
quantity-comparator N How the Quantity should be understood and represented. Internal
question-max-occurs questionnaire-answer-constraint Other Codes that describe the types of constraints possible on a question item that has a list of permitted answers 929 Internal
questionnaire-answers I Example list of codes for answers to questions. (Not complete or necessarily appropriate.) SNOMED CT
questionnaire-answers-status Lifecycle status of the questionnaire response. Internal
questionnaire-display-category questionnaire-disabled-display Codes defining that guide the purpose of a Questionnaire item display of type 'text'. disabled questionnaire items Internal
questionnaire-enable-behavior Controls how multiple enableWhen values are interpreted - whether all or any must be true. Internal
questionnaire-enable-operator The criteria by which a question is enabled. Internal
questionnaire-questions I Example list of codes for questions and groups of questions. (Not necessarily complete or appropriate.) LOINC
reaction-event-severity Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. Internal
reason-medication-given-codes I This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process. Other
reason-medication-not-given-codes I This value set includes all medication refused, medication not administered, and non-administration of necessary drug or medicine codes from SNOMED CT - provided as an exemplar value set. SNOMED CT
reason-medication-status-codes I This value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplar SNOMED CT
reference-handling-policy N A set of flags that defines how references are supported. Internal
reference-version-rules N Whether a reference needs to be version specific or version independent, or whether either can be used. Internal
89 referenced-item-category I This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Made up of a set of non-healthcare specific codes and all LOINC codes where scale type = 'DOC'. Other, LOINC
referencerange-appliesto I This value set defines a set of codes that can be used to indicate the particular target population the reference range applies to. Other, SNOMED CT
referencerange-meaning This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population. Other
397 regulated-authorization-basis I A legal or regulatory framework against which an authorization is granted, or other reasons for it. Internal
regulated-authorization-case-type I The type of a case involved in an application. Internal
regulated-authorization-type I Overall type of this authorization. Internal
rejection-criteria I Criterion for rejection of the specimen by laboratory. Other
related-artifact-type The type of relationship to the related artifact. Internal
related-claim-relationship I This value set includes sample Related Claim Relationship codes. Other
relatedperson-relationshiptype A set of codes that can be used to indicate the relationship between a Patient and a Related Person. 1028 V3, V2
relationship This value set includes the Patient to subscriber relationship codes. Internal
remittance-outcome relativetime-codes This value set includes Claim Processing Outcome codes. Internal Example Codes to illustrate the use of RelativeTime.contextCode 13 Internal, SNOMED CT
report-action-result-codes remittance-outcome The results outcome of executing an action. the processing. Internal
report-codes This value set includes LOINC codes that relate to Diagnostic Observations. LOINC
report-participant-type request-intent The type Codes indicating the degree of participant. authority/intentionality associated with a request. Internal
report-result-codes request-orderdetail-parameter-code The reported execution result. Internal 718 report-status-codes I The current status of the test report. Internal 724 repository-type Type for access of external URI. Internal 230 request-intent Codes indicating the degree of authority/intentionality associated with a request. order detail parameter codes. Internal
request-priority The clinical priority Identifies the level of a diagnostic order. importance to be assigned to actioning the request. Internal
request-resource-types A list of all the All Resource Types that represent request resource types defined in this version of the FHIR specification. resources Internal
request-status Codes identifying the lifecycle stage of a request. Internal
research-element-type research-study-classifiers I The possible types Codes that convey the type of research elements (E.g. Population, Exposure, Outcome). label that is provided. Internal
research-study-objective-type research-study-focus-type I Codes for the kind Some example codes of research study objective. Other focus 823 SNOMED CT
research-study-phase research-study-party-organization-type I Codes for the stage in the progression of This is a therapy from initial experimental use in humans in clinical trials to post-market evaluation. Other ResearchStudy's party organization type. 821 Internal
research-study-prim-purp-type research-study-party-role Codes for the main intent of the study. Other 827 research-study-reason-stopped I Other This is a ResearchStudy's party role. 825 Internal
research-study-status I Codes that convey the current status of the research study. Internal
resource-aggregation-mode N How resource references can be aggregated. Internal
resource-slicing-rules N How slices are interpreted when evaluating an instance. Internal
resource-status The master set of status codes used throughout FHIR. All status codes are mapped to one of these codes. Internal
resource-types N One of the resource types defined as part of this version of FHIR. Concrete FHIR Resource Types Internal
resource-validation-mode Codes indicating the type of validation to perform. Description Needed Here Internal
response-code The kind of response to a message. Internal
restful-capability-mode N The mode of a RESTful capability statement. Internal
restful-security-service N Types of security services used with FHIR. Other 178 Internal
risk-estimate-type risk-assessment-method I Whether Example value set illustrating possible codes for identifying the risk estimate is dichotomous, continuous mechanism or qualitative and algorithm used to make the specific type of risk estimate (eg proportion or median). assessment; e.g. TIMI, PRISM, Cardiff Type 2 diabetes, etc. Other Internal
1363 risk-assessment-outcome I Example value set illustrating possible codes for identifying the condition or other outcome; e.g. death, remission, amputation, infection, etc. Internal
risk-probability I Codes representing the likelihood of a particular outcome in a risk assessment. Other
route-codes I This value set includes all Route codes from SNOMED CT - provided as an exemplar. SNOMED CT
search-comparator What Search Comparator Codes are supported in search. Internal
search-entry-mode N Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. Internal
622 search-modifier-all-codes A supported modifier for a search parameter. Internal, Other
search-modifier-code A supported modifier for a search parameter. Internal
search-param-type N Data types allowed to be used for search parameters. Internal
search-xpath-usage search-processingmode How a search parameter relates to the set of elements returned by evaluating its xpath expression query. Internal
secondary-finding Codes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding. Internal 1285 security-labels security-label-data-example N I A single value set for all sample of security labels defined by FHIR. Other from [Healthcare Privacy and Security Classification System](security-labels.html#hcs) used on data (.meta.security) to indicate confidentialityCode classification and maybe sensitivity codes. 47 V3
security-role-type security-label-event-example I This example FHIR value set is comprised A sample of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles security labels from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; [Healthcare Privacy and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Security Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object System](security-labels.html#hcs) that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations used on those objects. In Attribute-Based Access Control (ABAC), a events and requests/responses (aka user requests to perform operations on objects. That user's access request is granted context or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host organization context) made up of user PurposeOfUse and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, maybe a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient. Other, V3, DICOM refrain/obligation. 978 V3
sequence-quality-method security-label-example This value set includes sequence quality method Other 223 sequence-quality-standardSequence I This value set includes sequence quality standard A sample of security labels from [Healthcare Privacy and Security Classification System](security-labels.html#hcs) as the combination of data and event codes. Other
sequence-referenceSeq security-labels This A single value set includes for all Reference codes security labels defined by FHIR. Other
sequence-species security-role-type-example I Codes identifying atomic results of observations when value is type codeableConcept. This value set includes all the children contains example structural roles. In general, two types of SNOMED CT Concepts from SCTIDs 404684003 Clinical finding (finding), 410607006 Organism (organism),362981000 Qualifier value (qualifier value), 105590001 Substance (substance), roles can be distinguished: structural roles and 123037004 Body structure (body structure). It is provided as a suggestive example SNOMED CT 216 sequence-type Type if a sequence -- DNA, RNA, functional roles. Structural Roles reflect human or amino acid sequence. organizational categories (hierarchies), and describe prerequisites, feasibilities, or competences for actions. Functional roles are bound to the realization or performance of actions. Internal
sequenceontology security-source-type Sequence Ontology The type of process where the audit event originated from. Use of these codes is not required but is encouraged to maintain translation with DICOM AuditMessage schema. Other
series-performer-function Performer function of an agent in an imaging study series V3
service-category I This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. Other
service-modifiers service-mode This value set includes sample Service Modifier codes. Internal 572 service-pharmacy I This value An example set includes a smattering of Pharmacy Service codes. Modes that could be applicable to use to characterize HealthcareServices or PractitionerRoles while searching Internal
service-place I This value set includes a smattering of Service Place codes. Other
service-provision-conditions I The code(s) that detail the conditions under which the healthcare service is available/offered. Other
service-referral-method I The methods of referral can be used when referring to a specific HealthCareService HealthcareService resource. Other
service-type I This value set defines an example set of codes of service-types. Other
service-uscls I This value set includes a smattering of USCLS codes. Other
servicerequest-category I An example value set of SNOMED CT concepts that can classify a requested service SNOMED CT
servicerequest-orderdetail servicerequest-status-reason An example value set of Codified order entry details concepts. These concepts only make sense in the context of what is being ordered. This example is for a patient ventilation order SNOMED CT 435 sibling-relationship-codes I The value set includes Example codes indicating the v3 RoleCode SIB (sibling) and all of its specializations. It covers reason why the relationships needed to establish genetic pedigree relationships between family members. V3 service request is in its current status (e.g., on hold, cancelled, suspended). Note that these are in no way complete and might not even be appropriate for some uses. 922 Internal
signature-type The Digital Signature Purposes, an indication of the reason an entity signs a document. This is included in the signed information and can be used when determining accountability for various actions concerning the document. Examples include: author, transcriptionist/recorder, and witness. Other
slotstatus The free/busy status of the slot. Internal
sort-direction The possible sort directions, ascending or descending. Internal
spdx-license The license that applies to an Implementation Guide (using an SPDX license Identifiers, or 'not-open-source'). The binding is required but new SPDX license Identifiers are allowed to be used (https://spdx.org/licenses/). Internal
specimen-collection I Actions that can be taken for the collection of specimen from a subject. SNOMED CT
specimen-collection-method I This example value set defines a set of codes that can be used to indicate the method by which a specimen was collected. SNOMED CT
specimen-collection-priority specimen-combined This example value set defines a set of codes that can be used to indicate Codes providing the priority of collection combined status of a specimen. Other 939 Internal
specimen-contained-preference Degree of preference of a type of conditioned specimen. Internal
specimen-container-type I Checks on the patient prior Containers which may hold specimens or specimen collection. All containers. Include codes SNOMED CT concepts descendants of 706041008 |Device for body fluid and tissue collection/transfer/processing CT(http://snomed.info/sct) where concept is-a 434711009 (Specimen container (physical object)| object)) SNOMED CT
specimen-processing-procedure specimen-processing-method I The technique that is used to perform the process or preserve the specimen. These are codes from SNOMED CT - provided as an exemplar value set. 469 SNOMED CT
specimen-status specimen-role Codes providing the status/availability role of a specimen. Internal
standards-status specimen-status HL7 Ballot/Standards status Codes providing the status/availability of artifact. Other 1365 strand-type Type for strand. a specimen. Internal
structure-definition-kind N Defines the type of structure that a definition is describing. Internal
study-type study-design Types of research studies (types This is a set of research methods). terms for study design characteristics. Other
subject-type submit-data-update-type Possible types of subjects. Concepts for how a measure report consumer and receiver coordinate data exchange updates. The choices are snapshot or incremental updates Internal
subscriber-relationship This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient). Other
subscription-channel-type Internal 502 subscription-tag Tags to put on a resource after subscriptions have been sent. Other 504 substance-category Substance category codes Other 476 substance-code This value set contains concept codes Core-defined FHIR channel types allowed for specific substances. It includes codes from [SNOMED](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) and where concept is-a 373873005 (Pharmaceutical / biologic product (product)) use in Subscriptions. SNOMED CT 473 Other
substance-status subscription-error A code to indicate if the substance is actively used. Internal 474 supplement-type I SupplementType : Codes for nutritional supplements to be provided to the patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example. SNOMED CT 390 supply-item This value set includes [SNOMED CT](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) or concept is-a 260787004 (Physical object) and provided as an example value set. SNOMED CT 699 supplydelivery-status Status of the supply delivery. Internal 700 supplydelivery-type This value sets refers to a specific supply item. Other 702 supplyrequest-kind This value sets refers to a Category of supply. represent subscription error details Other
supplyrequest-reason subscription-notification-type The reason why the supply item was requested. Other 697 supplyrequest-status Status of the supply request. Internal 695 surface This value set includes a smattering of FDI tooth surface codes. Other 546 synthesis-type Types of combining results from a body type of evidence (eg. summary data meta-analysis). Other 1347 system-restful-interaction N Operations supported notification represented by REST at the system level. status message. Internal
task-code subscription-payload-content Codes indicating the type of action that is expected to be performed Internal 1396 task-intent Distinguishes whether the task is a proposal, plan or full order. Internal 1240 task-status The current status of the task. represent how much resource content to send in notification payloads. Internal
teeth subscription-status This value set includes the FDI Teeth codes. State values for FHIR Subscriptions. Internal
testscript-operation-codes subscription-types This value set defines a set of codes that are Types used to indicate the supported operations of a testing engine or tool. with Subscriptions Internal, Other
testscript-profile-destination-types subscriptiontopic-cr-behavior This value set defines a set of codes that are used to indicate the profile type of Behavior a test system server can exhibit when acting as the destination within a TestScript. Other 714 testscript-profile-origin-types This value set defines a set of codes that are used criteria state does not exist (e.g., state prior to indicate the profile type of a test system when acting as the origin within a TestScript. Other 712 texture-code TextureModifier: Codes for food consistency types create or texture modifications to apply to foods. This value set is composed of SNOMED CT (US Extension and Core) Concepts from SCTID 229961002 Food consistency types (substance) hierarchy and is provided as a suggestive example. SNOMED CT 387 timezones IANA Timezone Codes Other 1036 timing-abbreviation Code for a known / defined timing pattern. V3 78 tooth This value set includes a smattering of FDI oral site codes. Other 540 transaction-mode A code that indicates how transactions are supported. Internal 192 trigger-type The type of trigger. Internal 103 type-derivation-rule N How after a type relates to its baseDefinition. delete). Internal
type-restful-interaction substance-amount-type N I Operations supported by REST at the type or instance level. The relationship between two substance types. Internal
ucum-bodytemp UCUM units for recording Body Temperature FHIR 957 ucum-bodyweight substance-category FHIR Substance category codes 956 Other
ucum-common substance-code Commonly encountered UCUM units (for purposes of helping populate look ups. FHIR null ucum-units I Unified Code for Units of Measure (UCUM). This value set contains concept codes for specific substances. It includes all UCUM codes from [SNOMED](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) 912 SNOMED CT
ucum-vitals-common substance-codes Common UCUM units for recording Vital Signs FHIR 955 udi I This value set includes sample UDI codes. Internal 554 udi-entry-type Codes to identify how UDI data was entered. Internal 211 units-of-time N A unit of time (units all substance codes from UCUM). FHIR 77 unknown-content-code A code that indicates whether SNOMED CT - provided as an application accepts unknown elements or extensions when reading resources. Internal 196 usage-context-type A code that specifies a type of context being specified by a usage context. Other 101 use-context This exemplar 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. set. Other, SNOMED CT
vaccine-code substance-form This identifies the vaccine substance administered - CVX codes. Internal, Other 22 variable-type I The possible types of variables for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive). Internal 1343 variant-state Codes providing the status of the variant test result. Other 217 variants HGVS : Human Genome Variation Society Other 282 verificationresult-can-push-updates Ability of the primary source to push updates/alerts Other 896 verificationresult-communication-method Attested information may be validated by process that are manual or automated. For automated processes substance form, whether it may accomplished by is the system of record reaching out through another system's API base form or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated. Other 1401 verificationresult-failure-action The result if validation fails Other 890 verificationresult-need The frequency with which the target must be validated Other 882 verificationresult-primary-source-type Type of the validation primary source Other 892 verificationresult-push-type-available Type of alerts/updates the primary source can send Other 898 verificationresult-status The validation status of the target salt. Internal
verificationresult-validation-process substance-grade I The primary process by quality standard, established benchmark, to which the target is validated Other 888 verificationresult-validation-status Status of the validation of the target against the primary source Other 894 verificationresult-validation-type What the target is validated against Other 886 versioning-policy N How the system supports versioning for a resource. Internal 190 vision-base-codes A coded concept listing the base codes. substance complies. Internal
vision-eye-codes substance-name-authority A coded concept listing the eye codes. An authority that officates substance names. Internal
vision-product substance-name-domain This value set includes a smattering of Prescription Product codes. Other 658 written-language I This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) for the purpose The use context of writing; this value set (unlike the common languages value set) doesn't include dialects except where they are relevant a substance name for written languages Other null yesnodontknow For Capturing simple yes-no-don't know answers Other null Namespace: http://dicom.nema.org/medical/dicom/current/output/chtml/part16 sect_CID_29.html Transitive closure of CID 29 AcquisitionModality DICOM 19 sect_CID_29.html|20121129 Transitive closure of CID 29 AcquisitionModality DICOM 19 Name (URI = http://terminology.hl7.org/ValueSet/v3-...) Name OID AcknowledgementCondition The codes identify the conditions under which accept acknowledgements are required to be returned in response to this message. Note that accept acknowledgement address two example if there is a different issues at the same time: reliable transport as well as syntactical correctness 2.16.840.1.113883.1.11.155 AcknowledgementDetailCode OpenIssue: Missing description. -- AcknowledgementDetailType A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, name when used as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300' 2.16.840.1.113883.1.11.19358 AcknowledgementType This attribute contains an acknowledgement code a drug active ingredient as described in the HL7 message processing rules. OpenIssue: Description was copied from attribute and needs to be improved opposed to be appropriate for a code system. food colour additive. 2.16.840.1.113883.1.11.8 Internal
ActClass substance-name-type **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.11527 ActClassClinicalDocument I A clinical document is a documentation The type of clinical observations and services, with the following characteristics: (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care; (3) Potential for authentication - A clinical document is an assemblage of information that is intended name given to be legally authenticated; (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; (5) Human readability - A clinical document is human readable." 2.16.840.1.113883.1.11.13948 ActClassDocument Specialization of Act to add the characteristics unique to document management services. substance. 2.16.840.1.113883.1.11.18938 Internal
ActClassInvestigation substance-optical-activity An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government. 2.16.840.1.113883.1.11.20224 ActClassObservation I Description: An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. Thecode attribute of Observation and thevalue attribute of Observation must be considered in combination to determine the semantics of the observation. Discussion: Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. Examples: Recording the results optical rotation type of a Family History Assessment Laboratory test and associated result Physical exam test and associated result Device temperature Soil lead level substance. 2.16.840.1.113883.1.11.11529 Internal
ActClassProcedure substance-relationship-type An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Examples: : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc. 2.16.840.1.113883.1.11.19665 ActClassROI I Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present. two substance types. 2.16.840.1.113883.1.11.17893 Internal
ActClassSupply substance-representation-format Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply. 2.16.840.1.113883.1.11.11535 ActCode I A code specifying the particular kind of Act that the Act-instance represents within its class. Constraints: The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers format of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted. substance representation. -- Internal
ActConsentDirective substance-representation-type I ActConsentDirective codes are used to specify the The type of Consent Directive a name given to which a Consent Directive Act conforms. substance. 2.16.840.1.113883.1.11.20425 Internal
ActConsentType substance-source-material-genus I Definition: The type genus of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or organism, typically referring to disclose health information for purposes such as research. 2.16.840.1.113883.1.11.19897 ActCoverageTypeCode Definition: Set of codes indicating the type Latin epithet of insurance policy or program that pays for the cost genus element of benefits provided to covered parties. 2.16.840.1.113883.1.11.19855 ActEncounterCode Domain provides codes that qualify the ActEncounterClass (ENC) plant/animal scientific name. 2.16.840.1.113883.1.11.13955 Internal
ActExposureLevelCode substance-source-material-part A qualitative measure of the degree of exposure to the causative agent. This includes concepts such as "low", "medium" and "high". This quantifies how the quantity that was available to be administered to the target differs from typical or background levels of the substance. -- ActIncidentCode I Set An anatomical origin of codes indicating the type of incident or accident. 2.16.840.1.113883.1.11.16508 ActInvoiceElementModifier Processing consideration and clarification codes. 2.16.840.1.113883.1.11.17704 ActInvoiceGroupCode Type of invoice element that is used to assist in describing source material within an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. 2.16.840.1.113883.1.11.19398 ActMood OpenIssue: In Ballot 2009May, a strong Negative vote was lodged against several of the concept definitions in the vocabulary used for Act.moodCode. The vote was found "Persuasive With Mod", with the understanding that M and M would undertake a detailed review of these concept definitions for a future release of the RIM. organism. 2.16.840.1.113883.1.11.10196 Internal
ActMoodIntent substance-source-material-species An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order. 2.16.840.1.113883.1.11.10199 ActMoodPredicate I Any A species of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as origin a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events. substance raw material. 2.16.840.1.113883.1.11.10202 Internal
ActPharmacySupplyType substance-source-material-type Identifies types of dispensing events 2.16.840.1.113883.1.11.16208 ActPriority I A set of codes (e.g., for routine, emergency), specifying classification that provides the urgency under which origin of the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. substance raw material. -- Internal
ActReason substance-status A set of codes specifying code to indicate if the motivation, cause, or rationale of an Act, when such rationale substance is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law". -- ActRelationshipCheckpoint **** MISSING DEFINITIONS **** actively used. 2.16.840.1.113883.1.11.10349 Internal
ActRelationshipConditional substance-stereochemistry Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred 2.16.840.1.113883.1.11.18977 ActRelationshipFulfills I The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act. 2.16.840.1.113883.1.11.10342 ActRelationshipHasComponent A collection optical rotation type of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently. 2.16.840.1.113883.1.11.10318 ActRelationshipJoin **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10360 ActRelationshipPertains This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays. substance. 2.16.840.1.113883.1.11.10329 Internal
ActRelationshipSplit substance-structure-technique **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10355 ActRelationshipSubset I <ns1:p>Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.</ns1:p><ns1:p>Used when there is a need to limit the number of components The method used to elucidate the first, the last, the next, the total, the average or some other filtered structure or calculated subset.</ns1:p> 2.16.840.1.113883.1.11.19613 ActRelationshipType The source is an excerpt from the target. 2.16.840.1.113883.1.11.10317 ActSite An anatomical location on an organism which can be the focus of an act. -- ActStatus Codes representing the defined possible states characterization of an Act, as defined by the Act class state machine. 2.16.840.1.113883.1.11.15933 ActSubstanceAdminSubstitutionCode No Description Provided drug substance. 2.16.840.1.113883.1.11.16621 Internal
ActTaskCode substance-weight-method Description: A task or action that a user may perform in a clinical information system. 2.16.840.1.113883.1.11.19846 ActUSPrivacyLaw I A jurisdictional mandate in The method by which the US relating to privacy. Deprecation Comment: Content moved to ActCode under _ActPrivacyLaw; use that instead. substance weight was measured. -- Internal
ActUncertainty substance-weight-type OpenIssue: Missing Description 2.16.840.1.113883.1.11.16899 AddressPartType I Description: Code that specifies whether an address part names the street, city, country, postal code, post box, etc. Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part type of "Street Address Line" substance weight measurement. 2.16.840.1.113883.1.11.10642 Internal
AddressUse supplement-type SupplementType : Codes that provide guidance around the circumstances in which a given address should be used. 2.16.840.1.113883.1.11.190 AdministrativeGender The gender of a person used for adminstrative purposes (as opposed to clinical gender) 2.16.840.1.113883.1.11.1 AmericanIndianAlaskaNativeLanguages American Indian and Alaska Native languages currently being used in the United States. -- Calendar **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.17422 CalendarCycle Calendar cycle identifiers -- CalendarType **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10682 Charset Internet Assigned Numbers Authority (IANA) Charset Types 2.16.840.1.113883.1.11.14853 CodingRationale Identifies how nutritional supplements to interpret the instance of the code, codeSystem value in a set of translations. Since HL7 (or a government body) may mandate that codes from certain code systems be sent in conformant messages, other synonyms that are sent in the translation set need provided to be distinguished among the originally captured source, the HL7 specified code, or some future role. When this code is NULL, it indicates that the translation is an undefined type. When valued, this property must contain one of the following values: SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination) There may be additional values added to this patient. This value set as we work through the use is composed of codes in messages SNOMED CT Concepts from SCTID 346415002 (Enteral and determine other Use Cases requiring special interpretation of the translations. 2.16.840.1.113883.1.11.19250 CommunicationFunctionType Describes the type of communication function that the associated entity plays in the associated transmission. supplement feeds (product)). 2.16.840.1.113883.1.11.16031 SNOMED CT
Compartment supplemented-mimetypes A named tag set for metadata used to populate a security category label field that "segments" an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System) Usage Note: This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk." 2.16.840.1.113883.1.11.20478 CompressionAlgorithm **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10620 Confidentiality A set of includes all possible codes specifying the security classification of acts from BCP-13 (see http://tools.ietf.org/html/bcp13), and roles in accordance with the definition for concept domain "Confidentiality". -- ConfidentialityClassification Set of codes used to value Act.Confidentiality xml, json, and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality". ttl 2.16.840.1.113883.1.11.10228 Other, Internal
ContainerCap surface The type of cap associated with a container -- ContainerSeparator I A material in This value set includes a blood collection container that facilites the separation of smattering of blood cells from serum or plasma 2.16.840.1.113883.1.11.14054 ContentProcessingMode Description: Identifies the order in which content should be processed. FDI tooth surface codes. 2.16.840.1.113883.1.11.19823 Other
ContextControl synchronicity-control A code Indicates that specifies how an ActRelationship operation must always be handled as synchronous or Participation contributes to asynchronous, or that the context of an Act, server must provide both, and whether it may be propagated to descendent Acts whose association allows such propagation (see also attributes Participation.contextControlCode, ActRelationship.contextControlCode, ActRelationship.contextConductionInd). 2.16.840.1.113883.1.11.16478 DataOperation **** MISSING DEFINITIONS **** -- Dentition **** MISSING DEFINITIONS **** -- DeviceAlertLevel Domain values for the Device.Alert_levelCode clients can choose 2.16.840.1.113883.1.11.14066 Internal
DocumentCompletion system-restful-interaction Identifies Operations supported by REST at the current completion state of a clinical document. 2.16.840.1.113883.1.11.271 DocumentSectionType The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc. system level. 2.16.840.1.113883.1.11.10871 Internal
DocumentStorage target-species Identifies the storage status of a document. -- EducationLevel I Years of education that A species for which a person has completed 2.16.840.1.113883.1.11.19175 EmployeeJobClass **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.16036 EncounterAdmissionSource **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.12234 EncounterSpecialCourtesy **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.12242 EntityClass Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and medicinal product is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing. intended. 2.16.840.1.113883.1.11.10882 Internal
EntityClassDevice task-business-status I A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind business-specific nuances of device is identified by the code attribute inherited from Entity. Usage: This includes durable (reusable) medical equipment as well as disposable equipment. 2.16.840.1.113883.1.11.11623 EntityClassLivingSubject Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject.) 2.16.840.1.113883.1.11.10884 EntityClassManufacturedMaterial Corresponds to the ManufacturedMaterial class 2.16.840.1.113883.1.11.13934 EntityClassOrganization A social or legal structure formed by human beings. 2.16.840.1.113883.1.11.10889 EntityClassPlace A physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant. 2.16.840.1.113883.1.11.10892 EntityClassRoot Corresponds to the Entity class 2.16.840.1.113883.1.11.13922 EntityCode OpenIssue: Missing description. task. -- Internal
EntityDeterminer task-code EntityDeterminer in natural language grammar is Codes indicating the class type of words action that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing. 2.16.840.1.113883.1.11.10878 EntityDeterminerDetermined The described determiner is used expected to indicate that the given Entity is taken as a general description of a kind of thing that can be taken in whole, in part, or in multiples. 2.16.840.1.113883.1.11.10879 EntityHandling **** MISSING DEFINITIONS **** performed 2.16.840.1.113883.1.11.13988 Internal
EntityNamePartQualifier task-inputoutput-parameter-type OpenIssue: Needs description 2.16.840.1.113883.1.11.15888 EntityNamePartQualifierR2 I Description: The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to input and output types for the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records. task. 2.16.840.1.113883.1.11.20323 Internal
EntityNamePartType task-intent **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.15880 EntityNamePartTypeR2 Description: Indicates Distinguishes whether the name part task is a given name, family name, prefix, suffix, etc. 2.16.840.1.113883.1.11.20322 EntityNameUse **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.15913 EntityNameUseR2 Description: A set of codes advising a system proposal, plan or user which name in a set of names to select for a given purpose. 2.16.840.1.113883.1.11.20321 EntityRisk Kinds of risks associated with the handling of the material.. -- EntityStatus Codes representing the defined possible states of an Entity, as defined by the Entity class state machine. full order. 2.16.840.1.113883.1.11.16005 Internal
EquipmentAlertLevel task-performer-function-code **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10896 Ethnicity I In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless performer of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both. -- ExposureMode Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure. task. -- Internal
FamilyMember task-reason A relationship between two people characterizing their "familial" relationship 2.16.840.1.113883.1.11.19579 GTSAbbreviation I Open Issue: It appears that the printnames are suboptimal and should be improved The reason for many of the existing codes. -- GenderStatus **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.11523 GeneralPurposeOfUse task being performed. Supports communication of purpose of use at a general level. 2.16.840.1.113883.1.11.20449 Internal
HL7ContextConductionStyle task-status The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model. 2.16.840.1.113883.1.11.20380 HL7StandardVersionCode This code system holds version codes for the Version 3 standards. Values are to be determined by HL7 and added with each new version current status of the HL7 Standard. task. 2.16.840.1.113883.1.11.19373 Internal
HL7UpdateMode task-status-reason The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute. 2.16.840.1.113883.1.11.10018 HtmlLinkType I HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the The current document and the anchor that is the target status reason of the link task. 2.16.840.1.113883.1.11.11017 Internal
HumanLanguage texture-code TextureModifier: Codes for the representation of the names of human languages. 2.16.840.1.113883.1.11.11526 IdentifierReliability Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms. 2.16.840.1.113883.1.11.20277 IdentifierScope Description: Codes food consistency types or texture modifications to specify the scope in which the identifier applies apply to the object with which it foods. This value set is associated, and used in the datatype property II. 2.16.840.1.113883.1.11.20276 InformationSensitivityPolicy Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because composed of differing organizational business rules, security policies, SNOMED CT (US Extension and jurisdictional requirements. For example, an "employee" sensitivity code would make little sense for use outside of a policy domain. "Taboo" would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders Core) Concepts from SCTID 229961002 Food consistency types (substance) hierarchy and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with is provided as a sensitivity identifier and/or Act.title. 2.16.840.1.113883.1.11.20428 IntegrityCheckAlgorithm **** MISSING DEFINITIONS **** suggestive example. 2.16.840.1.113883.1.11.17385 SNOMED CT
LanguageAbilityMode therapy A value representing the method of expression of the language. Example: Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed. OpenIssue: Description copied from Concept Domain of same name. Must be verified. 2.16.840.1.113883.1.11.12249 LanguageAbilityProficiency I A value representing the level of proficiency in a language. Example: Excellent, good, fair, poor. OpenIssue: Description copied from Concept Domain of same name. Must be verified. therapy. 2.16.840.1.113883.1.11.12199 SNOMED CT
LivingArrangement therapy-relationship-type A code depicting the living arrangements Classification of relationship between a person -- LocalMarkupIgnore Tells therapy and a receiver to ignore just the local markup tags (local_markup, local_header, local_attr) when value="markup", contraindication or to ignore the local markup tags and all contained content when value="all" 2.16.840.1.113883.1.11.10975 LocalRemoteControlState **** MISSING DEFINITIONS **** an indication. 2.16.840.1.113883.1.11.10893 Internal
ManagedParticipationStatus timezones Codes representing An IANA timezone code for the defined possible states timezone offset per [BCP 175](https://www.iana.org/go/rfc6557). The offset is specified as part of a Managed Participation, as defined by dateTime/instant (or using the Managed Participation class state machine. 2.16.840.1.113883.1.11.15992 MapRelationship tzOffset extension on a date if necessary). The closeness or quality timezone code may also be provided to allow for human display of the mapping between the HL7 concept (as represented by the HL7 concept identifier) and location associated with the source coding system. The values offset. These are patterned after the similar relationships used in the UMLS Metathesaurus. Because the HL7 coding sy 2.16.840.1.113883.1.11.11052 MaritalStatus * * * No description supplied * * * Open Issue: The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency. -- MessageWaitingPriority Indicates that the receiver has messages like 'America/New_York' or 'America/Los_Angeles'. See [IANA Timezones](https://www.iana.org/time-zones) for the sender OpenIssue: Description does not make sense relative to name of coding system. Must be reviewed and improved. -- MilitaryRoleType Definition: A person playing the role of program eligible under a program based on military status. Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" official source, and the person's status as a member of the military meets jurisdictional or program criteria 2.16.840.1.113883.1.11.19812 ModifyIndicator [Wikipedia](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for information **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.395 Other
NullFlavor timing-abbreviation A collection of codes specifying why Code for a valid value is not present. known / defined timing pattern. 2.16.840.1.113883.1.11.10609 Other, V3
ObligationPolicy tooth Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Examples: encrypt Usage Note: Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision. 2.16.840.1.113883.1.11.20445 ObservationCategory I High level observation categories for the general type of observation being made. URL: http://hl7-fhir.github.io/valueset-observation-category.html This is an inline code system http://hl7.org/fhir/observation-category. 2.16.840.1.113883.4.642.2.222 ObservationInterpretation One or more codes providing a rough qualitative interpretation of the observation, such as "normal" / "abnormal", "low" / "high", "better" / "worse", "resistant" / "susceptible", "expected" / "not expected". The value set is intended to be for ANY use where coded representation of an interpretation is needed. 2.16.840.1.113883.1.11.78 ObservationMethod A code that provides additional detail about the means or technique used to ascertain the observation. Examples: Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Note that the Domain has includes a full discussion about use smattering of the attribute and constraining that is not appropriate for the code system description. Needs to be improved. FDI oral site codes. 2.16.840.1.113883.1.11.20423 Other
ObservationType trigger-type Identifies the kinds The type of observations that can be performed trigger. 2.16.840.1.113883.1.11.16226 Internal
ObservationValue type-derivation-rule This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has How a coded data type. OpenIssue: Description copied from Concept Domain of same name. Must be corrected.. -- ParticipationFunction This code is used type relates to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE). its baseDefinition. 2.16.840.1.113883.1.11.10267 Internal
ParticipationIndirectTarget type-restful-interaction Target that is not substantially present in the act and which is not directly affected Operations supported by REST at the act, but which will be a focus of the record or documentation of the act. 2.16.840.1.113883.1.11.19032 ParticipationInformationGenerator Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), type or information about what Act was performed (e.g., informant witness). instance level. 2.16.840.1.113883.1.11.10251 Internal
ParticipationInformationTranscriber ucum-bmi An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist UCUM units for dictated text transcribed into electronic form. recording BMI 2.16.840.1.113883.1.11.19676 FHIR
ParticipationMode ucum-bodylength A set of codes specifying the modality by which the Entity playing the Role is participating in the Act. Examples: Physically present, over the telephone, written communication. Rationale: Particularly UCUM units for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically. Open Issue: There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies. -- ParticipationPhysicalPerformer A person who actually and principally carries out the action. Need not be the principal responsible actor, e.g. a surgery resident operating under supervision of attending surgeon, and may be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event. 2.16.840.1.113883.1.11.10248 ParticipationSignature A set of codes specifying whether and how the participant has attested his participation through a signature and or whether recording body length measures such a signature is needed. Examples: A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.) 2.16.840.1.113883.1.11.10282 ParticipationTargetDirect Target that is substantially present in the service as height and which is directly affected by the service action (includes consumed material, devices, etc.). head circumference 2.16.840.1.113883.1.11.10286 FHIR
ParticipationTargetLocation ucum-bodytemp The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.) UCUM units for recording Body Temperature 2.16.840.1.113883.1.11.10302 FHIR
ParticipationTargetSubject ucum-bodyweight The principle target that the service acts on. E.g. the patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects, consumables, and devices used as tools UCUM units for a service are not subjects. However, a device may be a subject of a maintenance service. recording Body Weight 2.16.840.1.113883.1.11.19584 FHIR
ParticipationType ucum-bp **** MISSING DEFINITIONS **** UCUM units for recording blood pressure. 2.16.840.1.113883.1.11.10901 FHIR
ParticipationVerifier ucum-common A person who verifies the correctness and appropriateness Commonly encountered UCUM units (for purposes of the service (plan, order, event, etc.) and hence takes on accountability. helping populate look ups). 2.16.840.1.113883.1.11.10259 FHIR
PatientImportance ucum-oxygensat Patient VIP code UCUM units for recording oxygen saturation. 2.16.840.1.113883.1.11.19265 FHIR
PaymentTerms ucum-units Describes payment terms Unified Code for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor Units of an invoice. 2.16.840.1.113883.1.11.14908 PersonDisabilityType A code identifying a person's disability. Measure (UCUM). This value set includes all UCUM codes -- FHIR
PersonalRelationshipRoleType ucum-vitals-common Types of personal relationships between two living subjects. Example: Parent, sibling, unrelated friend, neighbor Common UCUM units for recording Vital Signs 2.16.840.1.113883.1.11.19563 FHIR
ProbabilityDistributionType ucum-vitalsignsrate **** MISSING DEFINITIONS **** UCUM rate units for recording vital signs including heart and respiratory rate. 2.16.840.1.113883.1.11.10747 FHIR
ProcessingID udi-entry-type Codes used to specify whether a message is part of a production, training, or debugging system. identify how UDI data was entered. 2.16.840.1.113883.1.11.103 Internal
ProcessingMode undesirable-effect-classification **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.207 ProvenanceEventCurrentState I Specifies the state change of a target Act, such as a document or A categorisation for an entry, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted". undesirable effect. 2.16.840.1.113883.1.11.20547 SNOMED CT
ProvenanceEventCurrentState-AS undesirable-effect-frequency Specifies the state change of a target Act, using ActStatus codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted". 2.16.840.1.113883.1.11.20545 ProvenanceEventCurrentState-DC I Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of A categorisation for a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted". 2.16.840.1.113883.1.11.20546 PurposeOfUse Supports communication of purpose frequency of use at a general level. 2.16.840.1.113883.1.11.20448 QueryParameterValue The domain occurence of coded values used as parameters within QueryByParameter queries. -- QueryPriority **** MISSING DEFINITIONS **** an undesirable effect. 2.16.840.1.113883.1.11.91 Internal
QueryRequestLimit undesirable-effect-symptom Definition: Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application. -- QueryResponse I A code classifying the general nature An undesirable effect of the response to a given query. Includes whether or not data was found, or whether an error occurred. clinical use. 2.16.840.1.113883.1.11.208 SNOMED CT
QueryStatusCode unit-of-presentation A code specifying the state of the Query. 2.16.840.1.113883.1.11.18899 Race I In the United States, federal standards for classifying data on race determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define race, and they recognize the absence of an anthropological or scientific basis for racial classification. Instead, the federal standards acknowledge that race is a social-political construct presentation type in which an individual's own identification with one more race categories administrable medicinal product is preferred given to observer identification. The standards use a variety of features to define five minimum race categories. Among these features are descent from "the original peoples" of a specified region or nation. The minimum race categories are American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. The federal standards stipulate that race data need not be limited to the five minimum categories, but any expansion must be collapsible to those categories. -- RefrainPolicy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Examples: prohibit redisclosure without consent directive 2.16.840.1.113883.1.11.20446 RelationalOperator **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.209 RelationshipConjunction **** MISSING DEFINITIONS **** patient. 2.16.840.1.113883.1.11.10365 Internal
ReligiousAffiliation units-of-time Assigment A unit of spiritual faith affiliation -- ResponseLevel Specifies whether a response is expected time (units from the addressee of this interaction and what level of detail that response should include UCUM). 2.16.840.1.113883.1.11.14761 FHIR
ResponseModality usage-context-agreement-scope Defines the timing and grouping of the response instances. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Codes for use in UsageContext.valueCodeableConcept when UsageContext.code is agreement-scope 2.16.840.1.113883.1.11.394 Internal
ResponseMode use-context Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities. 2.16.840.1.113883.1.11.19650 RoleClass I Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains: RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity. RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity. RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This value set of roles is further partitioned between: RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity. RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into: RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement. Personal relationship which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as defines a base set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept. OpenIssue: Description copied from Concept Domain of same name. Must be verified. 2.16.840.1.113883.1.11.11555 RoleClassAgent An entity (player) codes that acts or is authorized can be used to act on behalf of another entity (scoper). 2.16.840.1.113883.1.11.14006 RoleClassAssociative A general association between two entities that is neither partitive nor ontological. 2.16.840.1.113883.1.11.19313 RoleClassManufacturedProduct Scoped by the manufacturer 2.16.840.1.113883.1.11.11580 RoleClassMutualRelationship A relationship indicate that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children). 2.16.840.1.113883.1.11.19316 RoleClassPartitive An association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" content in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity resource was developed with a (generally larger) scoping Entity. 2.16.840.1.113883.1.11.10429 RoleClassPassive An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds focus and intent of things done to it in this role happen without an agreement from the playing Entity. 2.16.840.1.113883.1.11.19105 RoleClassRelationshipFormal A relationship between two entities that is formally recognized, frequently by a contract or similar agreement. 2.16.840.1.113883.1.11.10416 RoleClassRoot Corresponds to the Role class 2.16.840.1.113883.1.11.13940 RoleClassServiceDeliveryLocation A role played by a place at which services may be provided. supporting use within particular contexts. 2.16.840.1.113883.1.11.16927 Other, SNOMED CT
RoleClassSpecimen vaccine-code A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen. 2.16.840.1.113883.1.11.11591 RoleCode I A set of codes further specifying This identifies the kind of Role; specific classification codes for further qualifying RoleClass vaccine substance administered - CVX codes. 2.16.840.1.113883.1.11.20413 RoleLinkType **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.11603 RoleStatus Codes representing the defined possible states of an Role, as defined by the Role class state machine. 2.16.840.1.113883.1.11.15999 Internal, Other
RouteOfAdministration value-filter-comparator The path the administered medication takes to get into the body or into contact with the body. -- SecurityControlObservationValue Security observation values used to indicate security control metadata. V:SecurityControl is the union of V:SecurityPolicy,V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, purpose type of use, dissemination controls and other refrain policies, and obligations to which a custodian or receiver is required comparator operator to comply. 2.16.840.1.113883.1.11.20471 SecurityIntegrityObservationValue No Description Provided 2.16.840.1.113883.1.11.20481 SecurityPolicy Types of security policies that further specify the ActClassPolicy value set. Examples: encrypt prohibit redisclosure without consent directive 2.16.840.1.113883.1.11.20444 Sequencing Specifies sequence of sort order. use 2.16.840.1.113883.1.11.390 Internal
ServiceDeliveryLocationRoleType variable-handling-example A role The handling of a place that further classifies the setting (e.g., accident site, road side, work site, community location) variable in which services are delivered. 2.16.840.1.113883.1.11.17660 SetOperator **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.17416 SeverityObservation Potential values statistical analysis for observations of severity. 2.16.840.1.113883.1.11.16643 SpecimenType **** MISSING DEFINITIONS **** -- SubstanceAdminSubstitutionReason No Description Provided 2.16.840.1.113883.1.11.19377 SubstitutionCondition Identifies what sort of change is permitted exposures or has occurred between the item that was ordered/requested and the one that was/will be provided. -- TableCellHorizontalAlign These values are defined within the XHTML 4.0 Table Model 2.16.840.1.113883.1.11.10981 TableCellScope These values are defined within the XHTML 4.0 Table Model 2.16.840.1.113883.1.11.11012 TableCellVerticalAlign These values are defined within the XHTML 4.0 Table Model 2.16.840.1.113883.1.11.10987 TableFrame These values are defined within the XHTML 4.0 Table Model 2.16.840.1.113883.1.11.10992 TableRules These values are defined within the XHTML 4.0 Table Model 2.16.840.1.113883.1.11.11002 TargetAwareness **** MISSING DEFINITIONS **** outcomes (E.g. Dichotomous, Continuous, Descriptive). 2.16.840.1.113883.1.11.10310 Internal
TelecommunicationCapabilities variable-role Description: Concepts The role that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address. 2.16.840.1.113883.1.11.20312 TimingEvent **** MISSING DEFINITIONS **** variable plays. 2.16.840.1.113883.1.11.10706 Internal
TransmissionRelationshipTypeCode version-algorithm Description: A code specifying Indicates the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints mechanism used to what kinds of Transmission objects can be related and in compare versions to determine which way. 2.16.840.1.113883.1.11.19833 TribalEntityUS INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS -- VaccineManufacturer The manufacturer of a vaccine. 2.16.840.1.113883.1.11.227 VerificationMethod No Description Provided is more current. 2.16.840.1.113883.1.11.19707 Internal
WorkClassificationODH version-independent-all-resource-types Code system of concepts representing a person's job type as defined by compensation Current and sector (e.g. paid vs. unpaid, self-employed vs. not self-employed, government vs. private, etc.). 2.16.840.1.113883.1.11.20560 WorkScheduleODH Describes an individual's typical arrangement of working hours for an occupation. 2.16.840.1.113883.1.11.20561 employmentStatusODH Concepts representing whether a person does or does not currently have a job past FHIR resource types (deleted or is not currently in the labor pool seeking employment. renamed), including abstract types 2.16.840.1.113883.1.11.20562 Other, Internal
hl7ApprovalStatus version-independent-resource-types Description: Codes for concepts describing the approval level of HL7 artifacts. This code system reflects the concepts expressed in HL7's Governance & Operations Manual (GOM) past Current and present. -- hl7CMETAttribution **** MISSING DEFINITIONS **** -- hl7ITSType Description: Codes identifying past FHIR resource types of HL7 Implementation Technology Specifications (deleted or renamed) -- Other, Internal
hl7ITSVersionCode versioning-policy HL7 implementation technology specification versions. These codes will document the ITS type and version for message encoding. The code will appear in the instances based upon rules expressed in the ITS, and do not appear in the abstract message, either as it is presented to received from How the ITS. -- hl7PublishingDomain Description: Codes for HL7 publishing domains (specific content area) -- hl7PublishingSection Description: Codes system supports versioning for HL7 publishing sections (major business categories) a resource. -- Internal
hl7PublishingSubSection virtual-service-type Description: Codes for HL7 publishing sub-sections (business sub-categories) -- hl7Realm I Description: Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models) and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms. All affiliate realm codes may automatically be used as both binding realms and namespace realms. Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms. (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.) All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm. For affiliates whose concepts align with nations, the country Example codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm virtual service connection types. It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes. However, tooling does not currently support namepace realm codes greater than 2 characters. Open Issue: The name of the concept property "owningAffiliate" should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code. Open Issue: In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length. 2.16.840.1.113883.1.11.20355 Internal
hl7V3Conformance vision-base-codes Description: Identifies allowed codes for HL7aTMs v3 conformance property. A coded concept listing the base codes. -- Internal
hl7VoteResolution vision-eye-codes Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM). A coded concept listing the eye codes. -- Internal
orderableDrugForm vision-product OpenIssue: Missing description. -- policyHolderRole I This vocabulary is defined by Implementation Guide for CDA Release 2 - Level 1 - Care Record Summary (US realm). It describes roles recognized through the issuance of an insurance policy to a policyholder who value set includes a relationship with the covered party, such as spouse, child, etc. This vocabulary is essentially an inversion of the role relations smattering of the HL7 CoverageRoleType vocabulary. It provides more detailed roles with respect to the underwriter (the scoping organization) for those participants in the policyholder role for a patient. Open Issue: The code values for this coding system must be extracted from the CDA documentation and brought forward through Harmonization for instantiation in this repository. Prescription Product codes. -- Other
styleType warning-type <ns1:p>The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style</ns1:p> -- substanceAdminSubstitution I Identifies what sort Classification of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided. warning type. -- Internal
triggerEventID week-of-month Description: This code system contains all HL7 artifacts of type TE (Trigger Event) that are created by HL7 or its affiliates or their designates using the realm namespacing rules approved by HL7. Local implementations who create trigger events outside of these namespacing rules, (e.g. using the ZZ realm code) must register their own code system. The specific list set of legal codes can be found by consulting the HL7 publications (editions, ballots, implementation guides, etc.) published by HL7 Inc. and by the various HL7 affiliates and their designates. Codes shall be expressed in upper case, with separator as shown weeks in HL7 publications with no version id. E.g. PORX_TE123456UV. a month. 2.16.840.1.113883.1.11.20324 Internal
xBasicConfidentialityKind written-languages Description: Used to enumerate the typical confidentiality constraints placed upon a clinical document. Usage Note: x_BasicConfidentialityKind is a subset of Confidentiality This value set includes common codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that from BCP-47 (see http://tools.ietf.org/html/bcp47) for the receiver may not disclose purpose of writing; this information except as directed by the information custodian, who may be the information subject; or that value set (unlike the receiver may not disclose this information common languages value set) doesn't include dialects except as directed by the information custodian, who may be the information subject. 2.16.840.1.113883.1.11.16926 URI Description OID URI (all prefixed with http://terminology.hl7.org/CodeSystem/v2-/) ID OID 0001 Administrative Sex 0002 Marital Status 0003 Event Type 0004 Patient Class 0005 Race 0006 ReligionVersion Dependent. Use one of: 2.1+ 2.4+ 0007 Admission Type 0008 Acknowledgment code 0009 Ambulatory Status 0012 STOCK LOCATION 0017 Transaction Type 0023 Admit Source 0027 Priority 0033 ROUTE 0034 SITE ADMINISTERED 0038 Order status 0043 Condition Code 0048 What subject filter 0052 Diagnosis Type 0061 Check Digit Scheme 0062 Event Reason 0063 Relationship 0065 Specimen Action Code 0066 Employment Status 0069 Hospital Service 0070 Specimen Source Codes 0074 Diagnostic Service Section ID 0076 Message Type 0078 Interpretation Codes 0080 Nature of Abnormal Testing 0083 Outlier Type 0085 Observation Result Status Codes Interpretation 0091 Query Priority 0092 Re-Admission Indicator 0098 Type of Agreement 0100 Invocation event 0102 Delayed acknowledgment type 0103 Processing ID 0104 Version ID 0105 Source of Comment 0106 Query/response format code 0107 Deferred response type 0108 Query results level 0109 Report priority 0116 Bed Status 0119 Order Control Codes 0121 Response Flag 0122 Charge Type 0123 Result Status 0124 Transportation Mode 0125 Value Type 0126 Quantity Limited Request 0127 Allergen Type 0128 Allergy Severity 0130 Visit User Code 0131 Contact Role 0133 Procedure Practitioner Identifier Code Type 0135 Assignment of Benefits 0136 Yes/no Indicator 0137 Mail Claim Party 0140 Military Service 0141 Military Rank/Grade 0142 Military Status 0144 Eligibility Source 0145 Room Type 0146 Amount Type 0147 Policy Type 0148 Money or Percentage Indicator 0149 Day Type 0150 Certification Patient Type 0153 Value Code 0155 Accept/Application Acknowledgment Conditions 0156 Which date/time qualifier 0157 Which date/time status qualifier 0158 Date/time selection qualifier 0159 Diet Code Specification Type 0160 Tray Type 0161 Allow Substitution 0162 Route of Administration 0163 Body Site 0164 Administration Device 0165 Administration Method 0166 RX Component Type 0167 Substitution Status 0168 Processing Priority 0169 Reporting Priority 0170 Derived Specimen 0173 Coordination of Benefits 0174 Nature of Service/Test/Observation 0175 Master File Identifier Code 0177 Confidentiality Code 0178 File Level Event Code 0179 Response Level 0180 Masterfile Action Code 0181 MFN Record-level Error Return 0183 Active/Inactive 0185 Preferred Method of Contact 0187 Provider Billing 0189 Ethnic Group 0190 Address Type 0191 Type of Referenced Data 0193 Amount Class 0200 Name Type 0201 Telecommunication Use Code 0202 Telecommunication Equipment Type 0203 Identifier Type 0204 Organizational Name Type 0205 Price Type 0206 Segment Action Code 0207 Processing Mode 0208 Query Response Status 0209 Relational Operator 0210 Relational Conjunction 0211 Alternate Character Sets 0213 Purge Status Code 0214 Special Program Code 0215 Publicity Code 0216 Patient Status Code 0217 Visit Priority Code 0220 Living Arrangement 0223 Living Dependency 0224 Transport Arranged 0225 Escort Required 0227 Manufacturers of Vaccines (code=MVX) 0228 Diagnosis Classification 0229 DRG Payor 0230 Procedure Functional Type 0231 Student Status 0232 - Insurance Company Contact Reason 0234 Report Timing 0235 Report Source 0236 Event Reported To 0237 Event Qualification 0238 Event Seriousness 0239 Event Expected 0240 Event Consequence 0241 Patient Outcome 0242 Primary Observer's Qualification 0243 Identity May Be Divulged 0247 Status of Evaluation 0248 Product Source 0250 Relatedness Assessment 0251 Action Taken in Response to the Event 0252 Causality Observations 0253 Indirect Exposure Mechanism 0254 Kind of Quantity 0255 Duration Categories 0256 Time Delay Post Challenge 0257 Nature of Challenge 0258 Relationship Modifier 0259 Modality 0260 Patient Location Type 0261 Location Equipment 0262 Privacy Level 0263 Level of Care 0265 Specialty Type 0267 Days of the Week 0268 Override 0269 Charge On Indicator 0270 Document Type 0271 Document Completion Status 0272 Document Confidentiality Status 0273 Document Availability Status 0275 Document Storage Status 0276 Appointment reason codes 0277 Appointment Type Codes 0278 Filler status codes 0279 Allow Substitution Codes 0280 Referral Priority 0281 Referral Type 0282 Referral Disposition 0283 Referral Status 0284 Referral Category 0286 Provider Role 0287 Problem/Goal Action Code 0290 MIME base64 encoding characters 0291 Subtype of Referenced Data 0292 Vaccines Administered 0294 Time Selection Criteria Parameter Class Codes 0298 CP Range Type 0299 Encoding 0301 Universal ID Type 0305 Person Location Type 0309 Coverage Type 0311 Job Status 0315 Living Will Code 0316 Organ Donor Code 0317 Annotations 0321 Dispense Method 0322 Completion Status 0323 Action Code 0324 Location Characteristic ID 0325 Location Relationship ID 0326 Visit Indicator 0329 Quantity Method 0330 Marketing Basis 0331 Facility Type 0332 Source Type 0334 Disabled Person Code 0335 Repeat Pattern 0336 Referral Reason 0337 Certification Status 0338 Practitioner ID Number Type 0339 Advanced Beneficiary Notice Code 0344 Patient's Relationship to Insured 0350 Occurrence Code 0351 Occurrence Span 0353 CWE statuses 0354 Message Structure 0355 Primary Key Value Type 0356 Alternate Character Set Handling Scheme 0357 Message Error Condition Codes 0359 Diagnosis Priority 0360 Degree/License/CertificateVersion Dependent. Use one of: 2.3.1+ 2.7+ 0363 Assigning Authority 0364 Comment Type 0365 Equipment State 0366 Local/Remote Control State 0367 Alert Level 0368 Remote Control Command 0369 Specimen Role 0370 Container Status 0371 Additive/Preservative 0372 Specimen Component 0373 Treatment 0374 System Induced Contaminants 0375 Artificial Blood 0376 Special Handling Code 0377 where they are relevant for written languages Other Environmental Factors 0383 Substance Status 0384 Substance Type 0387 Command Response 0388 Processing Type 0389 Analyte Repeat Status 0391 Segment GroupVersion Dependent. Use one of: 2.4+ 2.6+ 0392 Match Reason 0393 Match Algorithms 0394 Response Modality 0395 Modify Indicator 0396 Coding System 0397 Sequencing 0398 Continuation Style Code 0401 Government Reimbursement Program 0402 School Type 0403 Language Ability 0404 Language Proficiency 0406 Participant Organization Unit Type 0409 Application Change Type 0411 Supplemental Service Information Values 0415 Transfer Type 0416 Procedure DRG Type 0417 Tissue Type Code 0418 Procedure Priority 0421 Severity of Illness Code 0422 Triage Code 0423 Case Category Code 0424 Gestation Category Code 0425 Newborn Code 0426 Blood Product Code 0427 Risk Management Incident Code 0428 Incident Type Code 0429 Production Class Code 0430 Mode of Arrival Code 0431 Recreational Drug Use Code 0432 Admission Level of Care Code 0433 Precaution Code 0434 Patient Condition Code 0435 Advance Directive Code 0436 Sensitivity to Causative Agent Code 0437 Alert Device Code 0438 Allergy Clinical Status 0440 Data Types 0441 Immunization Registry Status 0442 Location Service Code 0443 Provider Role 0444 Name Assembly Order 0445 Identity Reliability Code 0450 Event Type 0455 Type of Bill Code 0456 Revenue code 0457 Overall Claim Disposition Code 0459 Reimbursement Action Code 0460 Denial or Rejection Code 0465 Name/Address Representation 0466 Ambulatory Payment Classification Code 0468 Payment Adjustment Code 0469 Packaging Status Code 0470 Reimbursement Type Code 0472 TQ Conjunction ID 0473 Formulary Status 0474 Practitioner Organization Unit Type 0475 Charge Type Reason 0477 Controlled Substance Schedule 0478 Formulary Status 0480 Pharmacy Order Types 0482 Order Type 0483 Authorization Mode 0484 Dispense Type 0485 Extended Priority Codes 0487 Specimen Type 0488 Specimen Collection Method 0489 Risk Codes 0490 Specimen Reject Reason 0491 Specimen Quality 0492 Specimen Appropriateness 0493 Specimen Condition 0494 Specimen Child Role 0495 Body Site Modifier 0496 Consent Type 0497 Consent Mode 0498 Consent Status 0499 Consent Bypass Reason 0500 Consent Disclosure Level 0501 Consent Non-Disclosure Reason 0502 Non-Subject Consenter Reason 0503 Sequence/Results Flag 0504 Sequence Condition Code 0505 Cyclic Entry/Exit Indicator 0506 Service Request Relationship 0507 Observation Result Handling 0508 Blood Product Processing Requirements 0510 Blood Product Dispense Status 0511 BP Observation Status Codes Interpretation 0513 Blood Product Transfusion/Disposition Status 0514 Transfusion Adverse Reaction 0516 Error Severity 0517 Inform Person Code 0518 Override Type 0520 Message Waiting Priority 0523 Computation Type 0524 Sequence condition 0527 Calendar Alignment 0528 Event Related Period 0529 Precision 0530 Organization, Agency, Department 0532 Expanded Yes/no Indicator 0534 Notify Clergy Code 0535 Signature Code 0536 Certificate Status 0538 Institution Relationship Type 0540 Inactive Reason Code 0544 Container Condition 0547 Jurisdictional Breadth 0548 Signatory's Relationship to Subject 0550 Body Parts 0553 Invoice Control Code 0554 Invoice Reason Codes 0555 Invoice Type 0556 Benefit Group 0557 Payee Type 0558 Payee Relationship to Invoice 0559 Product/Service Status 0561 Product/Services Clarification Codes 0562 Processing Consideration Codes 0564 Adjustment Category Code 0565 Provider Adjustment Reason Code 0566 Blood Unit Type 0569 Adjustment Action 0570 Payment Method Code 0571 Invoice Processing Results Status 0572 Tax status 0615 User Authentication Credential Type Code 0616 Address Expiration Reason 0617 Address Usage 0618 Protection Code 0625 Item Status Codes 0634 Item Importance Codes 0642 Reorder Theory Codes 0651 Labor Calculation Type 0653 Date Format 0657 Device Type 0659 Lot Control 0667 Device Data State 0669 Load Status 0682 Device Status 0702 Cycle Type 0717 Access Restriction Value 0719 Access Restriction Reason Code 0725 Mood Codes 0728 CCL Value 0731 DRG Diagnosis Determination Status 0734 Grouper Status 0739 DRG Status Patient 0742 DRG Status Financial Calculation 0749 DRG Grouping Status 0755 Status Weight At Birth 0757 DRG Status Respiration Minutes 0759 Status Admission 0761 DRG Procedure Determination Status 0763 DRG Procedure Relevance 0776 Item Status 0778 Item Type 0790 Approving Regulatory Agency 0793 Ruling Act 0806 Sterilization Type 0818 Package 0834 MIME Types
0868 Telecommunication Expiration Reason 0871 Supply Risk Codes 0881 Role Executing Physician 0882 Medical Role Executing Physician 0894 Side of body 0895 Present On Admission (POA) Indicator 0904 Security Check Scheme 0905 Shipment Status 0906 ActPriority 0907 Confidentiality 0909 Patient Results Release Categorization Scheme 0912 Participation 0914 Root Cause 0916 Relevant Clinicial Information 0917 Bolus Type 0918 PCA Type 0919 Exclusive Test 0920 Preferred Specimen/Attribute Status 0921 Certification Type Code 0922 Certification Category Code 0923 Process Interruption 0924 Cumulative Dosage Limit UoM 0925 Phlebotomy Issue 0926 Phlebotomy Status 0927 Arm Stick 0933 Intended Procedure Type 0935 yesnodontknow 4000 For Capturing simple yes-no-don't know answers Name/address representation Other