Release 4 5 Preview #1

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.4.0 Value Sets Defined in FHIR

FHIR Infrastructure Work Group Maturity Level : N/A Standards Status : Informative

This table contains a list of all the value sets defined as part of the FHIR specification. Some of these value sets include codes defined elsewhere, some contain their own inline code system definitions, and some do both. Any implicit code systems are case sensitive, though FHIR will never define codes that only differ by case.

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

Name Definition Source Id
Namespace: http://hl7.org/fhir/ValueSet
FHIR-version N All published FHIR Versions. Internal 1309
abstract-types N A list of the base types defined by this version of the FHIR specification - types that are defined, but for which only specializations actually are created. Internal 23
account-status Indicates whether the account is available to be used. Internal 726
account-type This examples value set defines the set of codes that can be used to represent the type of an account. V3 728
action-cardinality-behavior Defines behavior for an action or a group for how many times that item may be repeated. Internal 807
action-condition-kind Defines the kinds of conditions that can appear on actions. Internal 815
action-grouping-behavior Defines organization behavior of a group. Internal 799
action-participant-role Either a practitioner role or a relationship type. Other 796
action-participant-type The type of participant for the action. Internal 811
action-precheck-behavior Defines selection frequency behavior for an action or group. Internal 805
action-relationship-type Defines the types of relationships between actions. Internal 813
action-required-behavior Defines expectations around whether an action or action group is required. Internal 803
action-selection-behavior Defines selection behavior of a group. Internal 801
action-type The type of action to be performed. Other 809
activity-definition-category High-level categorization of the type of activity. Other 792
additional-instruction-codes This value set includes all SNOMED CT Additional Dosage Instructions. SNOMED CT 95
additionalmaterials This value set includes sample additional material type codes. Internal 529
address-type N The type of an address (physical / postal). Internal 69
address-use N The use of an address. Internal 67
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 596
adjudication-error This value set includes a smattering of adjudication codes. Other 39
adjudication-reason This value set includes smattering of Adjudication Reason codes. Other 598
administration-method-codes This value set includes some method codes from SNOMED CT - provided as an exemplar SNOMED CT 97
administrative-gender N The gender of a person used for administrative purposes. Internal 1
adverse-event-actuality Overall nature of the adverse event, e.g. real or potential. Internal 831
adverse-event-category Overall categorization of the event, e.g. product-related or situational. Other 833
adverse-event-causality-assess Codes for the assessment of whether the entity caused the event. Other 840
adverse-event-causality-method TODO. Other 842
adverse-event-contributing-factor This value set includes codes that describe the contributing factors suspected to have increased the probability or severity of the adverse event. SNOMED CT 0
adverse-event-mitigating-action This value set includes codes that describe the ameliorating actions taken after the adverse event occured in order to reduce the extent of harm. SNOMED CT 0
adverse-event-outcome TODO (and should this be required?). This value set includes codes that describe the type of outcome from the adverse event. Other 836
adverse-event-participant-function This value set includes codes that describe the type of involvement of the actor in the adverse event. V3 1443
adverse-event-preventive-action This value set includes codes that describe the preventive actions that contributed to avoiding the adverse event. SNOMED CT 0
adverse-event-seriousness Overall seriousness of this event for the patient. Other 838
adverse-event-severity The severity of the adverse event itself, in direct relation to the subject. Other 844
adverse-event-type adverse-event-status Codes identifying the lifecycle stage of an adverse event. Internal 1444
adverse-event-supporting-info This value set includes all codes that describe the supporting information relevant to the event. SNOMED CT Clinical Findings. 0
adverse-event-type This value set includes codes that describe the adverse event or incident that occurred or was averted. SNOMED CT 835
age-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes FHIR 19
all-distance-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of length FHIR null
all-languages N This value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47) Other 21
all-time-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of time FHIR null
all-types N A list of all the concrete types defined in this version of the FHIR specification - 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 the substance (including pharmaceutical products). Other 940
allergy-intolerance-category Category of an identified substance associated with allergies or intolerances. Internal 133
allergy-intolerance-criticality Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. Internal 129
allergy-intolerance-type Identification of the underlying physiological mechanism for a Reaction Risk. Internal 131
allergyintolerance-clinical Preferred value set for AllergyIntolerance Clinical Status. Other 1372
allergyintolerance-code 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 137
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 1370
animal-breeds This example value set defines a set of codes that can be used to indicate breeds of species. SNOMED CT 422
animal-genderstatus This example value set defines a set of codes that can be used to indicate the current state of the animal's reproductive organs. Internal 418
animal-species This example value set defines a set of codes that can be used to indicate species of animal patients. SNOMED CT 420
appointment-cancellation-reason This example value set defines a set of reasons for the cancellation of an appointment. Other 1381
appointmentstatus The free/busy status of an appointment. Internal 484
approach-site-codes This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar. SNOMED CT 346
assert-direction-codes The type of direction to use for assertion. Internal 706
assert-operator-codes The type of operator to use for assertion. Internal 708
assert-response-code-types The type of response code to use for assertion. Internal 710
asset-availability This value set has asset availability codes. Internal 1295
attribute-estimate-type Method of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation. Other 1412
audit-entity-type Code for the entity type involved in the audit event. Other, Internal 458
audit-event-action Indicator for type of action performed during the event that generated the event. Internal 452
audit-event-outcome Indicates whether the event succeeded or failed. Internal 454
audit-event-severity The severity of the audit entry. Internal 0
audit-event-sub-type More detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions. DICOM, Internal 464
audit-event-type Event Types for Audit Events - defined by DICOM with some FHIR specific additions. DICOM, Other 462
audit-source-type The type of process where the audit event originated from. Other 466
basic-resource-type This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. Other 138
benefit-network This value set includes a smattering of Network type codes. Other 608
benefit-term This value set includes a smattering of Benefit Term codes. Other 612
benefit-type This value set includes a smattering of Benefit type codes. Other 606
benefit-unit This value set includes a smattering of Unit type codes. Other 610
binding-strength N Indication of the degree of conformance expectations associated with a binding. Internal 43
body-site 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 141
bodysite-laterality Laterality: SNOMED-CT concepts for 'left', 'right', and 'bilateral' SNOMED CT 287
bodystructure-code 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 142
bodystructure-relative-location SNOMED-CT concepts modifying the anatomic location SNOMED CT 140
bundle-type N Indicates the purpose of a bundle - how it is intended to be used. Internal 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
c80-facilitycodes This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147. SNOMED CT 67
c80-practice-codes This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition. SNOMED CT 72
capability-statement-kind N How a capability statement is intended to be used. Internal 198
care-plan-activity-kind 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 Example codes indicating the outcome of a care plan activity. Note that these are in no way complete and might not even be appropriate for some uses. SNOMED CT 149
care-plan-activity-status Codes that reflect the current state of a care plan activity within its overall life cycle. Internal 146
care-plan-activity-status-reason Example codes indicating the reason why the activity isn't yet started, is on hold, was cancelled, etc. Note that these are in no way complete and might not even be appropriate for some uses. Other 1416
care-plan-category 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 148
care-plan-intent Codes indicating the degree of authority/intentionality associated with a care plan. Internal 150
care-team-category Indicates the type of care team. LOINC 155
care-team-status Indicates the status of the care team. Internal 153
catalogType The type of catalog. Other 968
catalogentry-relation-type Types of relationships between entries. Internal 1445
catalogentry-status Public usability statuses for catalog entries. Internal 1449
catalogentry-type Types of resources that can be attached to catalog entries. Internal 1447
cdshooks-indicator This value set captures the set of indicator codes defined by the CDS Hooks specification. Other 1065
certainty-rating The relative quality of the statistic. Other 1414
certainty-subcomponent-rating The quality rating of the subcomponent of a quality of evidence rating. Other 1361
certainty-subcomponent-type The subcomponent classification of quality of evidence rating systems. Other 1359
characteristic-method The method used to determine the characteristic(s) of the variable. Other 1452
chargeitem-billingcodes Example set of codes that can be used for billing purposes. Other 848
chargeitem-status Codes identifying the lifecycle stage of a ChargeItem. Internal 846
choice-list-orientation Direction in which lists of possible answers should be displayed. Other 933
chromosome-human Chromosome number for human. Other 224
claim-careteamrole This value set includes sample Claim Care Team Role codes. Other 586
claim-exception This value set includes sample Exception codes. Other 580
claim-informationcategory This value set includes sample Information Category codes. Other 582
claim-modifiers This value set includes sample Modifier type codes. Other 536
claim-subtype 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 566
claim-type This value set includes Claim Type codes. Other 558
claim-use The purpose of the Claim: predetermination, preauthorization, claim. Internal 544
clinical-findings 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 232
clinical-use-issue-type Overall defining type of this clinical use issue. Internal 1454
clinicalimpression-prognosis Example value set for clinical impression prognosis. SNOMED CT 160
clinicalimpression-status clinicalimpression-status-reason Codes that reflect Example codes indicating the current state of reason why a clinical impression within its overall lifecycle. ClinicalImpression is on hold or stopped. Note that these are in no way complete and might not even be appropriate for some uses. Internal SNOMED CT 1046 1417
clinvar NCBI central repository for curating pathogenicity of potentially clinically relevant variants Other 1041
code-search-support The degree to which the server supports the code search parameter on ValueSet, if it is supported. Internal 860
codesystem-altcode-kind Indicates the type of use for which the code is defined. Other 952
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 782
codesystem-hierarchy-meaning N The meaning of the hierarchy of concepts in a code system. Internal 784
common-tags Common Tag Codes defined by FHIR project Other 79
communication-category Codes for general categories of communications such as alerts, instructions, etc. Other 172
communication-not-done-reason Codes for the reason why a communication did not happen. Other 174
communication-request-status-reason 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 1418
communication-topic Codes describing the purpose or content of the communication. Other 983
compartment-type Which type a compartment definition describes. Internal 786
composite-measure-scoring The composite scoring method of the measure. Other 773
composition-altcode-kind Indicates the type of use for which the code is defined. Other 1405
composition-attestation-mode The way in which a person authenticated a composition. Internal 238
composition-status The workflow/clinical status of the composition. Internal 241
concept-map-equivalence The degree of equivalence between concepts. Internal 17
concept-map-relationship The relationship between concepts. Internal 1408
concept-property-type N The type of a property value. Internal 780
concept-subsumption-outcome 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). Internal 1238
conceptmap-unmapped-mode Defines which action to take if there is no match in the group. Internal 480
condition-category Preferred value set for Condition Categories. Other 162
condition-cause Example value set for Cause of Condition codes SNOMED CT 965
condition-clinical Preferred value set for Condition Clinical Status. Other 164
condition-code Example value set for Condition/Problem/Diagnosis codes. SNOMED CT 161
condition-course Value set for clinical course of a disease (how the disease behaves over time). SNOMED CT 1463
condition-outcome Example value set for condition outcomes. SNOMED CT 967
condition-precondition-type Kind of precondition for the condition. Internal 1439
condition-predecessor Example value set for condition predecessor codes. SNOMED CT 966
condition-questionnaire-purpose The use of a questionnaire. Internal 1441
condition-severity Preferred value set for Condition/Diagnosis severity grading. SNOMED CT 168
condition-stage Example value set for stages of cancer and other conditions. SNOMED CT 170
condition-stage-type Example value set for the type of stages of cancer and other conditions SNOMED CT 171
condition-state Enumeration indicating whether the condition is currently active, inactive, or has been resolved. Other 963
condition-ver-status The verification status to support or decline the clinical status of the condition or diagnosis. Other 166
conditional-delete-status N A code that indicates how the server supports conditional delete. Internal 194
conditional-read-status N A code that indicates how the server supports conditional read. Internal 200
conformance-expectation Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification. Other 919
consent-action This value set includes sample Consent Action codes. Other 753
consent-category 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 751
consent-content-class This value set includes the FHIR resource types, along with some other important content class codes Other, Internal 747
consent-content-code This example value set contains all LOINC code LOINC 748
consent-data-meaning How a resource reference is interpreted when testing consent restrictions. Internal 759
consent-performer This value set includes sample Performer Role codes. Internal 1016
consent-policy This value set includes sample Regulatory consent policy types from the US and other regions. Other 1014
consent-provision-type How a rule statement is applied, such as adding additional consent or removing consent. Internal 757
consent-scope This value set includes the four Consent scope codes. Other 761
consent-state-codes Indicates the state of the consent. Internal 755
consent-verification This value set includes base Consent Verification codes. Other 0
consistency-type 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 389
constraint-severity N SHALL applications comply with this constraint? Internal 81
contact-point-system N Telecommunications form for contact point. Internal 71
contact-point-use N Use of contact point. Internal 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
container-cap Color of the container cap. Other 850
container-material This value set includes SNOMED CT codes for materials that specimen containers are made of SNOMED CT 1400
contract-action This value set includes sample Contract Action codes. Other 739
contract-actionstatus This value set contract specific codes for action status. Internal 1303
contract-actorrole This value set includes sample Contract Actor Role codes. Other 741
contract-assetcontext This value set contract specific codes for asset context. Internal 1297
contract-assetscope This value set contract specific codes for asset scope. Internal 1293
contract-assetsubtype This value set contract specific codes for asset subtype. Internal 1301
contract-assettype This value set contract specific codes for asset type. Internal 1299
contract-content-derivative 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 745
contract-data-meaning How a resource reference is interpreted when evaluating contract offers. Other 749
contract-decision-mode This value set contract specific codes for decision modes. Internal 1291
contract-definition-subtype This value set contract specific codes for status. Internal 1212
contract-definition-type This value set contract specific codes for status. Internal 1210
contract-expiration-type This value set contract specific codes for status. Internal 1214
contract-legalstate This value set contract specific codes for status. Internal 1206
contract-party-role This value set contract specific codes for offer party participation. Internal 1224
contract-publicationstatus This value set contract specific codes for status. Internal 1208
contract-scope This value set contract specific codes for scope. Internal 1216
contract-security-category This value set contract specific codes for security category. Internal 1220
contract-security-classification This value set contract specific codes for security classification. Internal 1218
contract-security-control This value set contract specific codes for security control. Internal 1222
contract-signer-type This value set includes sample Contract Signer Type codes. Other 737
contract-status This value set contract specific codes for status. Internal 743
contract-subtype This value set includes sample Contract Subtype codes. Other 731
contract-term-subtype This value set includes sample Contract Term SubType codes. Other 735
contract-term-type This value set includes sample Contract Term Type codes. Other 733
contract-type This value set includes sample Contract Type codes. Other 729
contributor-type The type of contributor. Internal 93
copy-number-event Copy Number Event. Other 226
cosmic COSMIC : Catalogue Of Somatic Mutations In Cancer Other 912
coverage-class This value set includes Coverage Class codes. Other 1009
coverage-copay-type This value set includes sample Coverage Copayment Type codes. Other 527
coverage-financial-exception This value set includes Example Coverage Financial Exception Codes. Other 1328
coverage-selfpay This value set includes Coverage SelfPay codes. Other 525
coverage-type This value set includes Coverage Type codes. Other 520
coverageeligibilityresponse-ex-auth-support This value set includes CoverageEligibilityResponse Auth Support codes. Other 1393
cpt-all A value set that includes all CPT codes Other null 1451
currencies N Currency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html) Other 1025
data-absent-reason N Used to specify why the normally expected content of the data element is missing. Other 5
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). Internal 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
dataelement-sdcobjectclassproperty The allowed codes for identifying the ISO 11179 ObjectClass Property for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. SNOMED CT, LOINC, Other 911
days-of-week N The days of the week. Internal 512
dbsnp DBSNP : Single Nucleotide Polymorphism database Other 284
defined-types N A list of all the concrete types defined in this version of the FHIR specification - Data Types and Resource Types. Internal 24
definition-resource-types A list of all the definition resource types defined in this version of the FHIR specification. Internal 1056
definition-status Codes identifying the lifecycle stage of a definition. Other 107
definition-topic High-level categorization of the definition, used for searching, sorting, and filtering. Other 794
definition-use N Structure Definition Use Codes / Keywords Other 1190
designation-use N Details of how a designation would be used SNOMED CT 264
detectedissue-category Kinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. V3 204
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 205
detectedissue-severity Indicates the potential degree of impact of the identified issue on the patient. Internal 206
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 425
device-component-property Codes for identifying device properties. This is based upon IEEE/HCD specified codes. Other 634
device-definition-status Codes representing the current status of the device - on, off, suspended, etc. Internal 1307
device-kind 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 208
device-nametype The type of name the device is referred by. Internal 1083
device-safety 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 213
device-statement-status A coded concept indicating the current status of the Device Usage. Internal 214
device-status The availability status of the device. Internal 209
device-status-reason The availability status reason of the device. Other 1081
device-type 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 1376
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 645
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 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
diagnostic-report-status The status of the diagnostic report. Internal 235
diagnostic-service-sections This value set includes all the codes in HL7 V2 table 0074. V2 234
dicm-405-mediatype Media Type Code DICOM ​908
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)) SNOMED CT 385
directness The quality of how direct the match is. Other 1458
discriminator-type N How an element value is interpreted when discrimination is evaluated. Internal 91
distance-units Unified Code for Units of Measure (UCUM). This value set includes common UCUM codes for units of distance FHIR 62
doc-section-codes Document section codes (LOINC codes used in CCDA sections). LOINC 237
doc-typecodes FHIR Document Codes - all LOINC codes where scale type = 'DOC'. LOINC 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. Other, LOINC 46
document-mode N Whether the application produces or consumes documents. Internal 186
document-reference-status The status of the document reference. Internal 7
document-relationship-type The type of relationship between documents. Internal 244
dose-rate-type The kind of dose or rate specified. Other 981
duration-units N Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes FHIR 61
effect-estimate-type Whether the effect estimate is an absolute effect estimate (absolute difference) or a relative effect estimate (relative difference), and the specific type of effect estimate (eg relative risk or median difference). Other 1355 eligibilityrequest-purpose A code specifying the types of information being requested. Internal 1182
eligibilityresponse-purpose A code specifying the types of information being requested. Internal 1184
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-diet This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. Other 255
encounter-discharge-disposition This value set defines a set of codes that can be used to where the patient left the hospital. Other 259
encounter-location-status The status of the location. Internal 262
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 250
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-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 253
encounter-special-courtesy This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. V3 252
encounter-status Current state of the encounter. Internal 246
encounter-subject-status This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter Other 1419
encounter-type This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided. Other 248
endpoint-connection-type 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-payload-type This is an example value set defined by the FHIR project, that could be used to represent possible payload document types. Other 496
endpoint-status The status of the endpoint. Internal 494
ensembl ENSEMBL reference sequence identifiers Other 1040
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 394
entformula-additive EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example. Other 392
entformula-type EnteralFormulaType : Codes for type of enteral formula to be administered to patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example. SNOMED CT 391
episode-of-care-status The status of the episode of care. Internal 664
episodeofcare-type This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record. Other 666
event-capability-mode N The mode of a message capability statement. Internal 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
event-resource-types A list of all the event resource types defined in this version of the FHIR specification. Internal 1060
event-status Codes identifying the lifecycle stage of an event. Internal 109
event-timing N Real world event relating to the schedule. Internal, V3 75
evidence-quality A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems. Other 1020
evidence-variant-state Used for results by exposure in variant states such as low-risk, medium-risk and high-risk states. Other 1353 ex-benefitcategory This value set includes examples of Benefit Category codes. Other 1174
ex-diagnosis-on-admission This value set includes example Diagnosis on Admission codes. Other 1169
ex-diagnosisrelatedgroup This value set includes example Diagnosis Related Group codes. Other 588
ex-diagnosistype This value set includes example Diagnosis Type codes. Other 590
ex-onsettype This value set includes sample Service Modifier codes. Internal 578
ex-payee-resource-type The type of Claim payee Resource. Other 584
ex-paymenttype This value set includes example Payment Type codes. Other 616
ex-procedure-type This value set includes example Procedure Type codes. Other 1387
ex-program-code This value set includes sample Program Reason Span codes. Other 576
ex-revenue-center This value set includes sample Revenue Center codes. Other 594
example-cpt-all A value set that includes all CPT codes Other null
example-expansion This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC null
example-extensional This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC null
example-filter ACME Codes for Cholesterol: Plasma only - demonstrating the use of a filter defined in a CodeSystem Internal null
example-hierarchical Demonstration of extensions that build a hierarchical contains Other null
example-intensional This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC null
examplescenario-actor-type The type of actor - system or human. Internal 858
expansion-parameter-source Declares what the source of a parameter is. Other 1278
expansion-processing-rule Defines how concepts are processed into the expansion when it's for UI presentation. Other 1280
explanationofbenefit-status A code specifying the state of the resource instance. Internal 618
exposure-state Whether the results by exposure is describing the results for the primary exposure of interest (exposure) or the alternative state (exposureAlternative). Internal 1351 expression-language The media type of the expression language. Internal 105
extension-context-type N How an extension context is interpreted. Internal 1012
feeding-device Materials used or needed to feed the patient. Internal, SNOMED CT 961
filter-operator N The kind of operation to perform as a part of a property based filter. Internal 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
flag-category Example list of general categories for flagged issues. (Not complete or necessarily appropriate.) Other 122
flag-code Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) SNOMED CT 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
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 120
fm-conditions This value set includes sample Conditions codes. Internal 556
fm-itemtype This value set includes sample Item Type codes. Internal 548
fm-status This value set includes Status codes. Internal 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
food-type 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 384
formatcodes The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at https://confluence.hl7.org/display/SD/Format+Codes+for+IHE+XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incomplete Other 1
forms This value set includes a sample set of Forms codes. Other 37
fundsreserve This value set includes sample funds reservation type codes. Other 33
gender-identity This example value set defines a set of codes that can be used to indicate a patient's gender identity. Internal 972
genenames HGNC: Human Gene Nomenclature Committee Other 281
goal-acceptance-status Codes indicating whether the goal has been accepted by a stakeholder. Other 917
goal-achievement Describes the progression, or lack thereof, towards the goal against the target. Other 1374
goal-category Example codes for grouping goals to use for filtering or presentation. Other 275
goal-priority Indicates the level of importance associated with reaching or sustaining a goal. Other 273
goal-relationship-type Types of relationships between two goals. Other 915
goal-start-event Identifies types of events that might trigger the start of a goal. SNOMED CT 279
goal-status Codes that reflect the current state of a goal and whether the goal is still being targeted. Internal 271
goal-status-reason Example codes indicating the reason for a current status. Note that these are in no way complete and might not even be appropriate for some uses. Internal 277
graph-compartment-rule How a compartment must be linked. Internal 280
graph-compartment-use Defines how a compartment rule is used. Internal 282
group-measure Possible group measure aggregates (E.g. Mean, Median). Internal 1345
group-type Types of resources that are part of group. Internal 284
guidance-response-status The status of a guidance response. Internal 817
guide-page-generation A code that indicates how the page is generated. Internal 998
guide-parameter-code Code of parameter that is input to the guide. Internal Other 996
handling-condition Set of handling instructions prior testing of the specimen. Other 854
history-absent-reason Codes describing the reason why a family member's history is not available. Other 269
history-status A code that identifies the status of the family history record. Internal 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
http-verb N HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details. Internal 624
icd-10 This value set includes sample ICD-10 codes. Internal 531
icd-10-procedures This value set includes sample ICD-10 Procedure codes. Internal 574
identifier-type N A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. V2 45
identifier-use N Identifies the purpose for this identifier, if known . Internal 57
identity-assuranceLevel The level of confidence that this link represents the same actual person, based on NIST Authentication Levels. Internal 656
imagingstudy-status The status of the ImagingStudy. Internal 990
immunization-evaluation-dose-status The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example. Other 301
immunization-evaluation-dose-status-reason The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support 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. Other 303
immunization-evaluation-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 299
immunization-evaluation-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 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 300
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 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
immunization-origin 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 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. Other 291
immunization-reason The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was administered. This value set is provided as a suggestive example. 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. SNOMED CT 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
immunization-route The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the administrative routes used during vaccination. This value set is provided as a suggestive example. V3 289
immunization-site The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the body site where the vaccination occurred. This value set is provided as a suggestive example. V3 288
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 295
immunization-status-reason The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was not administered. This value set is provided as a suggestive example. V3, SNOMED CT V3 992
immunization-subpotent-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 reason why a dose is considered to be subpotent. This value set is provided as a suggestive example. Other 993
immunization-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 that the dose is being administered against. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy. SNOMED CT 1047
implantStatus A set codes that define the functional status of an implanted device. Other 1282
inactive HL7 v3 ActMood Predicate codes, including inactive codes V3 null
instance-availability Availability of the resource. DICOM ​811
insuranceplan-applicability Whether the cost applies to in-network or out-of-network providers. Other 0
insuranceplan-type This example value set defines a set of codes that can be used to indicate a type of insurance plan. Other 870
interaction-trigger FHIR RESTful interaction codes used for Topic trigger. Internal 1460
intervention This value set includes sample Intervention codes. Internal 532
investigation-sets Example value set for investigation type. SNOMED CT 157
invoice-priceComponentType Codes indicating the kind of the price component. Internal 868
invoice-status Codes identifying the lifecycle stage of an Invoice. Internal 866
iso3166-1-2 This value set defines the ISO 3166 Part 1 2-letter codes Other null
iso3166-1-3 This value set defines the ISO 3166 Part 1 3-letter codes Other null
iso3166-1-N This value set defines the ISO 3166 Part 1 Numeric codes Other null
issue-severity N How the issue affects the success of the action. Internal 408
issue-type N A code that describes the type of issue. Internal 410
item-type Distinguishes groups from questions and display text and indicates data type for questions. Internal 444
jurisdiction N This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used. Note: The codes for countries and country subdivisions are taken from [ISO 3166](https://www.iso.org/iso-3166-country-codes.html) while the codes for "supra-national" regions are from [UN Standard country or area codes for statistical use (M49)](http://unstats.un.org/unsd/methods/m49/m49.htm). Other 48
knowledge-resource-types 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. Internal 1022
languages This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) Other 20
ldlcholesterol-codes LDL Cholesterol codes - measured or calculated LOINC 959
library-type The type of knowledge asset this library contains. Other 763
link-type N The type of link between this patient resource and another patient resource. Internal 423
linkage-type Used to distinguish different roles a resource can play within a set of linked resources. Internal 314
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 322
list-example-codes Example use codes for the List resource - typical kinds of use. Other 316
list-item-flag Example Item Flags for the List Resource. In this case, these are the kind of flags that would be used on a medication list at the end of a consultation. Other 320
list-mode The processing mode that applies to this list. Internal 318
list-order Base values for the order of the items in a list resource. Other 324
list-status The current state of the list. Internal 326
location-mode Indicates whether a resource instance represents a specific location or a class of locations. Internal 330
location-physical-type This example value set defines a set of codes that can be used to indicate the physical form of the Location. Other 328
location-status Indicates whether the location is still in use. Internal 332
manifestation-or-symptom Example value set for Manifestation and Symptom codes. SNOMED CT 169
map-context-type How to interpret the context. Internal 679
map-group-type-mode If this is the default rule set to apply for the source type, or this combination of types. Internal 687
map-input-mode Mode for this instance of data. Internal 677
map-model-mode How the referenced structure is used in this mapping. Internal 675
map-source-list-mode If field is a list, how to manage the source. Internal 683
map-target-list-mode If field is a list, how to manage the production. Internal 685
map-transform How data is copied/created. Internal 681
marital-status N This value set defines the set of codes that can be used to indicate the marital status of a person. V3 29
match-grade A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. Other 970
measure-data-usage The intended usage for supplemental data elements in the measure. Other 771
measure-improvement-notation Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue. Other 1236
measure-population The type of population. Other 765
measure-report-status The status of the measure report. Internal 776
measure-report-type The type of the measure report. Internal 778
measure-scoring The scoring type of the measure. Other 767
measure-type The type of measure (includes codes from 2.16.840.1.113883.1.11.20368). Other 769
med-admin-perform-function MedicationAdministration Performer Function Codes Other 349
media-modality Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it. Other 1001 media-type Codes for high level media categories. Other 1000 media-view Codes defined in SNOMED CT that can be used to record Media Recording views. SNOMED CT 337 medication-admin-category MedicationAdministration Category Codes Other 347
medication-admin-status MedicationAdministration Status Codes Other 340
medication-as-needed-reason This value set includes all clinical findings from SNOMED CT - provided as an exemplar value set. SNOMED CT 96
medication-codes 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-form-codes This value set includes all dose form codes from SNOMED CT - provided as an exemplar. SNOMED CT 374
medication-statement-category medication-ingredientstrength Medication Status Ingredient Strength Codes Other Internal 370 1426
medication-statement-status medication-status Medication Status Codes Internal 367 376
medication-status medication-usage-category Medication MedicationUsage Category Codes Other 1424
medication-usage-status MedicationUsage Status Codes Internal 376 1422
medicationdispense-category MedicationDispense Category Codes Other 1314
medicationdispense-performer-function MedicationDispense Performer Function Codes Other 1318
medicationdispense-status MedicationDispense Status Codes Other 1312
medicationdispense-status-reason MedicationDispense Status Codes Other 1316
medicationknowledge-characteristic MedicationKnowledge Characteristic Codes Other 1337
medicationknowledge-package-type MedicationKnowledge Package Type Codes Other 1339
medicationknowledge-status MedicationKnowledge Status Codes Other 1335
medicationrequest-category MedicationRequest Category Codes Other 1322
medicationrequest-course-of-therapy MedicationRequest Course of Therapy Codes Other 1326
medicationrequest-intent MedicationRequest Intent Codes Internal 1321
medicationrequest-status MedicationRequest Status Codes Internal 1320
medicationrequest-status-reason MedicationRequest Status Reason Codes Other 1324
message-events One of the message events defined as part of this version of FHIR. Internal 26
message-reason-encounter Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. Other 378
message-significance-category The impact of the content of a message. Internal 188
message-transport N The protocol used for message transport. Other 184
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-calibration-state Describes the state of a metric calibration. Internal 652
metric-calibration-type Describes the type of a metric calibration. Internal 650
metric-category Describes the category of the metric. Internal 648
metric-color Describes the typical color of representation. Internal 654
metric-operational-status Describes the operational status of the DeviceMetric. Internal 646
mimetypes N This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13) Other 1024
missing-tooth-reason This value set includes sample Missing Tooth Reason codes. Other 534
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 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
name-use N The use of a human name. Internal 65
name-v3-representation A set of codes for each different representation of a name. V3 909
namingsystem-identifier-type Identifies the style of unique identifier used to identify a namespace. Internal 492
namingsystem-type Identifies the purpose of the naming system. Internal 490
narrative-status The status of a resource narrative. Internal 55
network-type The type of network access point of this agent in the audit event. Internal 456
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
note-type The presentation types of notes. Internal 15
nutrient-code 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-intake-category NutritionIntake Category Codes Other 1430
nutrition-intake-status NutritionIntake Status Codes Internal 1428
object-lifecycle-events This example FHIR value set is comprised of lifecycle event codes. The FHIR Actor value set is based on DICOM Audit Message, ParticipantObjectDataLifeCycle; ISO Standard, TS 21089-2017; Other null
object-role Code representing the role the entity played in the audit event. Other 460
observation-category Observation Category codes. Other 403
observation-codes This value set includes all LOINC codes LOINC 396
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-methods 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 395
observation-range-category Codes identifying the category of observation range. Internal 1333
observation-statistics The statistical operation parameter -"statistic" codes. Other 405
observation-status N Codes providing the status of an observation. Internal 400
observation-vitalsignresult This value set indicates the allowed vital sign result types. The LOINC code for Vitals Signs panel (85353-1) is a grouping structure for a set of vital signs and includes related links (with type=has-member) to the Observations in this set (e.g. respiratory rate, heart rate, BP). The Blood pressure panel (85354-9) is used to group the component observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4). LOINC 62
operation-kind N Whether an operation is a normal operation or a query. Internal 506
operation-outcome Operation Outcome codes used by FHIR test servers (see Implementation file translations.xml) Other 412
operation-parameter-use N Whether an operation parameter is an input or an output parameter. Internal 508
oral-prosthodontic-material This value set includes sample Oral Prosthodontic Material type codes. Internal 538
organization-role 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 880
organization-type This example value set defines a set of codes that can be used to indicate a type of organization. Other 414
orientation-type Type for orientation. Internal 987
parameter-group Codes identifying groupings of parameters; e.g. Cardiovascular. Other 632
parent-relationship-codes The value set includes the v3 RoleCode PRN (parent), TWIN (twin) and all of their specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. V3 921
participant-role 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 152
participantrequired Is the Participant required to attend the appointment. Internal 488
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 in the definition comments, then these are example FHIR codes. Other, V3, DICOM 54
participationstatus The Participation status of an appointment. Internal 486
patient-contactrelationship N The nature of the relationship between the patient and the contact person. V2 1130
payeetype This value set includes sample Payee Type codes. Other 31
payment-adjustment-reason This value set includes smattering of Payment Adjustment Reason codes. Other 600
payment-status This value set includes a sample set of Payment Status codes. Other 643
payment-type This value set includes sample Payment Type codes. Other 641
performer-function The types of involvement of the performer in the Event. V3 null
performer-role This example value set defines the set of codes that can be used to indicate a role of a procedure performer. SNOMED CT 433
permitted-data-type Permitted data type for observation value. Internal 1331
plan-definition-type The type of PlanDefinition. Other 797
postal-address-use Uses of an address not included in Address.use. V3 908
practitioner-role This example value set defines a set of codes that can be used to indicate the role of a Practitioner. Other, SNOMED CT 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 prepare-patient-prior-specimen-collection Checks on the patient prior specimen collection. All SNOMED CT concepts descendants of 703763000 |Precondition value (qualifier value)| SNOMED CT 1399
probability-distribution-type Codes specifying the type of probability distribution. V3 907
procedure-category Procedure Category code: A selection of relevant SNOMED CT codes. SNOMED CT 430
procedure-code Procedure Code: All SNOMED CT procedure codes. SNOMED CT 427
procedure-followup Procedure follow up codes: A selection of SNOMED CT codes relevant to procedure follow up. SNOMED CT 429
procedure-not-performed-reason Situation codes describing the reason that a procedure, which might otherwise be expected, was not performed, or a procedure that was started 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). SNOMED CT 431
procedure-outcome Procedure Outcome code: A selection of relevant SNOMED CT codes. SNOMED CT 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
procedure-reason This example value set defines the set of codes that can be used to indicate a reason for a procedure. SNOMED CT 432
process-priority This value set includes the financial processing priority codes. Other 552
product-category Biologically Derived Product Category. Internal 900
product-status Biologically Derived Product Status. Internal 902
product-storage-scale BiologicallyDerived Product Storage Scale. Internal 904
program This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties. Other 1383
property-representation N How a property is represented when serialized. Internal 87
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 V3, Other 438
provenance-agent-role The role that a provenance participant played Internal 1305
provenance-agent-type The type of participation a provenance participant. Other 1003
provenance-entity-role How an entity was used in an activity. Internal 436
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 927
provenance-history-record-activity Codes for Provenance activities that are relevant when capturing event history for resources. V3 926
provider-qualification This value set includes sample Provider Qualification codes. Other 570
provider-taxonomy NUCC Healthcare Provider Taxonomy codes Other 51
publication-status N The lifecycle status of an artifact. Internal 3
quality-type Type for quality report. Internal 228
quantity-comparator N How the Quantity should be understood and represented. Internal 59
question-max-occurs Flags an element as having unlimited repetitions. Other 929
questionnaire-answers Example list of codes for answers to questions. (Not complete or necessarily appropriate.) SNOMED CT 446
questionnaire-answers-status Lifecycle status of the questionnaire response. Internal required
questionnaire-category Example list of potential categories for questionnaires. SNOMED CT 928
questionnaire-display-category Codes defining the purpose of a Questionnaire item of type 'text'. Internal 935
questionnaire-enable-behavior Controls how multiple enableWhen values are interpreted - whether all or any must be true. Internal 1007
questionnaire-enable-operator The criteria by which a question is enabled. Internal 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
questionnaire-questions Example list of codes for questions and groups of questions. (Not necessarily complete or appropriate.) LOINC 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
reaction-event-severity Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. Internal 135
reason-medication-given-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 medication process. Other 344
reason-medication-not-given-codes 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 342
reason-medication-status-codes This value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplar SNOMED CT 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
reference-handling-policy N A set of flags that defines how references are supported. Internal 202
reference-version-rules N Whether a reference needs to be version specific or version independent, or whether either can be used. Internal 89
referencerange-appliesto 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 407
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
rejection-criteria Criterion for rejection of the specimen by laboratory. Other 856
related-artifact-type The type of relationship to the related artifact. Internal 99
related-claim-relationship This value set includes sample Related Claim Relationship codes. Other 568
relatedperson-relationshiptype A set of codes that can be used to indicate the relationship between a Patient and a Related Person. V2, V3 449
relation-type The type of relations between entries. Internal 1028 relationship This value set includes the Patient to subscriber relationship codes. Internal 35
remittance-outcome This value set includes Claim Processing Outcome codes. Internal 13
report-action-result-codes The results of executing an action. Internal 720
report-codes This value set includes LOINC codes that relate to Diagnostic Observations. LOINC 233
report-participant-type The type of participant. Internal 722
report-result-codes The reported execution result. Internal 718
report-status-codes 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. Internal 113
request-priority The clinical priority of a diagnostic order. Internal 115
request-resource-types A list of all the request resource types defined in this version of the FHIR specification. Internal 1058
request-status Codes identifying the lifecycle stage of a request. Internal 111
research-element-type The possible types of research elements (E.g. Population, Exposure, Outcome). Internal 1341 research-study-objective-type Codes for the kind of study objective. Other 823
research-study-phase Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation. Other 821
research-study-prim-purp-type Codes for the main intent of the study. Other 827
research-study-reason-stopped Codes for why the study ended prematurely. Other 825
research-study-status Codes that convey the current status of the research study. Internal 819
research-subject-milestone Indicates the progression of a study subject through the study milestones. Other 0
research-subject-state Indicates the progression of a study subject through a study. Other 0
research-subject-state-type Identifies the kind of state being refered to. Other 0
research-subject-status Indicates the progression of a study subject through a study. Internal 829
resource-aggregation-mode N How resource references can be aggregated. Internal 85
resource-security-category Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource. Other 1403
resource-slicing-rules N How slices are interpreted when evaluating an instance. Internal 83
resource-status The master set of status codes used throughout FHIR. All status codes are mapped to one of these codes. Internal 117
resource-type-link The type of payee Resource. Other 614
resource-types N One of the resource types defined as part of this version of FHIR. Internal 27
resource-validation-mode Codes indicating the type of validation to perform. Internal 118
response-code The kind of response to a message. Internal 380
restful-capability-mode N The mode of a RESTful capability statement. Internal 176
restful-security-service N Types of security services used with FHIR. Other 178
risk-estimate-type Whether the risk estimate is dichotomous, continuous or qualitative and the specific type of risk estimate (eg proportion or median). Other 1363 risk-probability Codes representing the likelihood of a particular outcome in a risk assessment. Other 450
route-codes This value set includes all Route codes from SNOMED CT - provided as an exemplar. SNOMED CT 98
search-comparator What Search Comparator Codes are supported in search. Internal 637
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-code A supported modifier for a search parameter. Internal 639
search-param-type N Data types allowed to be used for search parameters. Internal 11
search-xpath-usage How a search parameter relates to the set of elements returned by evaluating its xpath query. Internal 635
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 N A single value set for all security labels defined by FHIR. Other 47
security-role-type This example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user's access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient. Other, V3, DICOM 978
sequence-quality-method This value set includes sequence quality method Other 223
sequence-quality-standardSequence This value set includes sequence quality standard Other 222
sequence-referenceSeq This value set includes all Reference codes Other 221
sequence-species Codes identifying atomic results of observations when value is type codeableConcept. This value set includes all the children of SNOMED CT Concepts from SCTIDs 404684003 Clinical finding (finding), 410607006 Organism (organism),362981000 Qualifier value (qualifier value), 105590001 Substance (substance), and 123037004 Body structure (body structure). It is provided as a suggestive example SNOMED CT 216
sequence-type Type if a sequence -- DNA, RNA, or amino acid sequence. Internal 219
sequenceontology Sequence Ontology Other 1044
series-performer-function Performer function of an agent in an imaging study series V3 989
service-category This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. Other 516
service-modifiers This value set includes sample Service Modifier codes. Internal 572
service-pharmacy This value set includes a smattering of Pharmacy Service codes. Internal 562
service-place This value set includes a smattering of Service Place codes. Other 564
service-product This value set includes a smattering of Service/Product codes. Internal 560
service-provision-conditions The code(s) that detail the conditions under which the healthcare service is available/offered. Other 514
service-referral-method The methods of referral can be used when referring to a specific HealthCareService resource. Other 510
service-type This value set defines an example set of codes of service-types. Other 518
service-uscls This value set includes a smattering of USCLS codes. Other 542
servicerequest-category An example value set of SNOMED CT concepts that can classify a requested service SNOMED CT 434
servicerequest-orderdetail 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 The value set includes the v3 RoleCode SIB (sibling) and all of its specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. V3 922
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 12 63
slotstatus The free/busy status of the slot. Internal 482
smart-capabilities Codes that define what the server is capable of. Other 1018
sort-direction The possible sort directions, ascending or descending. Internal 979
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 1026
special-values A set of generally useful codes defined so they can be included in value sets. Other 9
specimen-collection Actions that can be taken for the collection of specimen from a subject. SNOMED CT 1398
specimen-collection-method This example value set defines a set of codes that can be used to indicate the method by which a specimen was collected. SNOMED CT 468
specimen-collection-priority This example value set defines a set of codes that can be used to indicate the priority of collection of a specimen. Other 939
specimen-contained-preference Degree of preference of a type of conditioned specimen. Internal 852
specimen-container-type Checks on the patient prior specimen collection. All SNOMED CT concepts descendants of 706041008 |Device for body fluid and tissue collection/transfer/processing (physical object)| SNOMED CT 470
specimen-processing-procedure The technique that is used to perform the process or preserve the specimen. V2 469
specimen-status Codes providing the status/availability of a specimen. Internal 471
standards-status HL7 Ballot/Standards status of artifact. Other 1365
state-change-reason Indicates why the state of the subject changed. Other 0
statistic-type The type of a specific statistic. Other 1410
strand-type Type for strand. Internal 985
structure-definition-kind N Defines the type of structure that a definition is describing. Internal 668
study-type Types of research studies (types The type of research methods). study a statistic was derived from. Other 1349
subject-type Possible types of subjects. Internal 775
subscriber-relationship This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient). Other 1385
subscription-channel-type The type of method used Codes to execute a subscription. represent subscription error details Internal Other 500
subscription-error Codes to represent subscription error details Other 1437
subscription-operator Operator to apply to filter label. Internal 1433
subscription-payload-content Codes to represent how much resource content to send in the notification payload. Internal 1435
subscription-status The status of a subscription. Internal 502
subscription-status-at-event A status code for the state of the Subscription. Other 1464
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 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)) SNOMED CT 473
substance-status A code to indicate if the substance is actively used. Internal 474
supplement-type 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. Other 693
supplyrequest-reason 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 of evidence (eg. summary data meta-analysis). Other 1347
system-restful-interaction N Operations supported by REST at the system level. Internal 181
task-code 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. Internal 790
teeth This value set includes the FDI Teeth codes. Internal 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
testscript-operation-codes This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. Other 704
testscript-profile-destination-types This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript. Other 714
testscript-profile-origin-types This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript. Other 712
texture-code TextureModifier: Codes for food consistency types or texture modifications to apply to foods. This value set is composed of SNOMED CT (US Extension and Core) Concepts from SCTID 229961002 Food consistency types (substance) 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
topic-match-operator Operator to apply to filter label. Internal 1461
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 a type relates to its baseDefinition. Internal 673
type-restful-interaction N Operations supported by REST at the type or instance level. Internal 180
ucum-bodylength UCUM units for recording body length measures such as height and head circumference FHIR 958
ucum-bodytemp UCUM units for recording Body Temperature FHIR 957
ucum-bodyweight UCUM units for recording Body Weight FHIR 956
ucum-common Commonly encountered UCUM units (for purposes of helping populate look ups. FHIR null
ucum-units Unified Code for Units of Measure (UCUM). This value set includes all UCUM codes FHIR 912
ucum-vitals-common Common UCUM units for recording Vital Signs FHIR 955
udi 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 from UCUM). FHIR 77
unknown-content-code A code that indicates whether 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 value set defines a base set of codes that can be used to indicate that the content in a resource was developed with a focus and intent of supporting use within particular contexts. Other, SNOMED CT 28
vaccine-code This identifies the vaccine substance administered - CVX codes. Internal, Other 22
variable-role The role that the assertion variable plays. Other 1456
variable-type 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 it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated. 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 Internal 884
verificationresult-validation-process The primary process by 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. Internal 662
vision-eye-codes A coded concept listing the eye codes. Internal 660
vision-product This value set includes a smattering of Prescription Product codes. Other 658
written-language This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) for the purpose of writing; this value set (unlike the common languages value set) doesn't include dialects except where they are relevant for written 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 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, 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 as described in the HL7 message processing rules. OpenIssue: Description was copied from attribute and needs to be improved to be appropriate for a code system. 2.16.840.1.113883.1.11.8
ActClass **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.11527
ActClassClinicalDocument A clinical document is a documentation 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 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. 2.16.840.1.113883.1.11.18938
ActClassInvestigation 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 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 of a Family History Assessment Laboratory test and associated result Physical exam test and associated result Device temperature Soil lead level 2.16.840.1.113883.1.11.11529
ActClassProcedure 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 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. 2.16.840.1.113883.1.11.17893
ActClassSupply 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 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 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. --
ActConsentDirective ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms. 2.16.840.1.113883.1.11.20425
ActConsentType Definition: The type 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 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 of insurance policy or program that pays for the cost of benefits provided to covered parties. 2.16.840.1.113883.1.11.19855
ActEncounterCode Domain provides codes that qualify the ActEncounterClass (ENC) 2.16.840.1.113883.1.11.13955
ActExposureLevelCode 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 Set 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 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. 2.16.840.1.113883.1.11.10196
ActMoodIntent 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 Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events. 2.16.840.1.113883.1.11.10202
ActPharmacySupplyType Identifies types of dispensing events 2.16.840.1.113883.1.11.16208
ActPriority A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. --
ActReason A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale 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 **** 2.16.840.1.113883.1.11.10349
ActRelationshipConditional 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 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 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. 2.16.840.1.113883.1.11.10329
ActRelationshipSplit **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10355
ActRelationshipSubset <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 to the first, the last, the next, the total, the average or some other filtered 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 of an Act, as defined by the Act class state machine. 2.16.840.1.113883.1.11.15933
ActSubstanceAdminSubstitutionCode No Description Provided 2.16.840.1.113883.1.11.16621
ActTaskCode Description: A task or action that a user may perform in a clinical information system. 2.16.840.1.113883.1.11.19846
ActUSPrivacyLaw A jurisdictional mandate in the US relating to privacy. Deprecation Comment: Content moved to ActCode under _ActPrivacyLaw; use that instead. --
ActUncertainty OpenIssue: Missing Description 2.16.840.1.113883.1.11.16899
AddressPartType 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 of "Street Address Line" 2.16.840.1.113883.1.11.10642
AddressUse 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 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 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 value set as we work through the use of codes in messages 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. 2.16.840.1.113883.1.11.16031
Compartment 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 codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality". --
ConfidentialityClassification Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality". 2.16.840.1.113883.1.11.10228
ContainerCap The type of cap associated with a container --
ContainerSeparator A material in a blood collection container that facilites the separation of 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. 2.16.840.1.113883.1.11.19823
ContextControl A code that specifies how an ActRelationship or Participation contributes to the context of an Act, 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 2.16.840.1.113883.1.11.14066
DocumentCompletion Identifies 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. 2.16.840.1.113883.1.11.10871
DocumentStorage Identifies the storage status of a document. --
EducationLevel Years of education that 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 is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing. 2.16.840.1.113883.1.11.10882
EntityClassDevice A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind 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. --
EntityDeterminer EntityDeterminer in natural language grammar is the class of words 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 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 **** 2.16.840.1.113883.1.11.13988
EntityNamePartQualifier OpenIssue: Needs description 2.16.840.1.113883.1.11.15888
EntityNamePartQualifierR2 Description: The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to 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. 2.16.840.1.113883.1.11.20323
EntityNamePartType **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.15880
EntityNamePartTypeR2 Description: Indicates whether the name part 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 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. 2.16.840.1.113883.1.11.16005
EquipmentAlertLevel **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10896
Ethnicity 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 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. --
FamilyMember A relationship between two people characterizing their "familial" relationship 2.16.840.1.113883.1.11.19579
GTSAbbreviation Open Issue: It appears that the printnames are suboptimal and should be improved for many of the existing codes. --
GenderStatus **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.11523
GeneralPurposeOfUse Supports communication of purpose of use at a general level. 2.16.840.1.113883.1.11.20449
HL7ContextConductionStyle 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 of the HL7 Standard. 2.16.840.1.113883.1.11.19373
HL7UpdateMode 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 HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the current document and the anchor that is the target of the link 2.16.840.1.113883.1.11.11017
HumanLanguage 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 to specify the scope in which the identifier applies to the object with which it 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 of differing organizational business rules, security policies, 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 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 a sensitivity identifier and/or Act.title. 2.16.840.1.113883.1.11.20428
IntegrityCheckAlgorithm **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.17385
LanguageAbilityMode 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 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. 2.16.840.1.113883.1.11.12199
LivingArrangement A code depicting the living arrangements of a person --
LocalMarkupIgnore Tells a receiver to ignore just the local markup tags (local_markup, local_header, local_attr) when value="markup", 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 **** 2.16.840.1.113883.1.11.10893
ManagedParticipationStatus Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine. 2.16.840.1.113883.1.11.15992
MapRelationship The closeness or quality of the mapping between the HL7 concept (as represented by the HL7 concept identifier) and the source coding system. The values 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. Open Issue: fixing and completion of the hierarchy and proper good definitions of all the concepts is badly needed. -- 2.16.840.1.113883.1.11.12212
MessageWaitingPriority Indicates that the receiver has messages 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" 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 **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.395
NullFlavor A collection of codes specifying why a valid value is not present. 2.16.840.1.113883.1.11.10609
ObligationPolicy 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 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 a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved. 2.16.840.1.113883.1.11.20423
ObservationType Identifies the kinds of observations that can be performed 2.16.840.1.113883.1.11.16226
ObservationValue This domain is the root domain to which code system covers all HL7-recognized value sets concepts of HL7-defined values for the Observation.value attribute will be linked Observation value element, when Observation.value it has a coded data type. OpenIssue: Description copied from Concept Domain of same name. Must be corrected.. datatype. --
ParticipationFunction This code is used to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE). 2.16.840.1.113883.1.11.10267
ParticipationIndirectTarget Target that is not substantially present in the act and which is not directly affected by 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), or information about what Act was performed (e.g., informant witness). 2.16.840.1.113883.1.11.10251
ParticipationInformationTranscriber 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 for dictated text transcribed into electronic form. 2.16.840.1.113883.1.11.19676
ParticipationMode 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 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 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 and which is directly affected by the service action (includes consumed material, devices, etc.). 2.16.840.1.113883.1.11.10286
ParticipationTargetLocation 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.) 2.16.840.1.113883.1.11.10302
ParticipationTargetSubject 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 for a service are not subjects. However, a device may be a subject of a maintenance service. 2.16.840.1.113883.1.11.19584
ParticipationType **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10901
ParticipationVerifier A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability. 2.16.840.1.113883.1.11.10259
PatientImportance Patient VIP code 2.16.840.1.113883.1.11.19265
PaymentTerms Describes payment terms for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor of an invoice. 2.16.840.1.113883.1.11.14908
PersonDisabilityType A code identifying a person's disability. --
PersonalRelationshipRoleType Types of personal relationships between two living subjects. Example: Parent, sibling, unrelated friend, neighbor 2.16.840.1.113883.1.11.19563
ProbabilityDistributionType **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.10747
ProcessingID Codes used to specify whether a message is part of a production, training, or debugging system. 2.16.840.1.113883.1.11.103
ProcessingMode **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.207
ProvenanceEventCurrentState Specifies the state change of a target Act, such as a document or 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". 2.16.840.1.113883.1.11.20547
ProvenanceEventCurrentState-AS 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 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 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 of use at a general level. 2.16.840.1.113883.1.11.20448
QueryParameterValue The domain of coded values used as parameters within QueryByParameter queries. --
QueryPriority **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.91
QueryRequestLimit 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 A code classifying the general nature of the response to a given query. Includes whether or not data was found, or whether an error occurred. 2.16.840.1.113883.1.11.208
QueryStatusCode A code specifying the state of the Query. 2.16.840.1.113883.1.11.18899
Race 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 in which an individual's own identification with one more race categories is preferred 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 **** 2.16.840.1.113883.1.11.10365
ReligiousAffiliation Assigment of spiritual faith affiliation --
ResponseLevel Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include 2.16.840.1.113883.1.11.14761
ResponseModality Defines the timing and grouping of the response instances. OpenIssue: Description copied from Concept Domain of same name. Must be verified. 2.16.840.1.113883.1.11.394
ResponseMode 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 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 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 a 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) that acts or is authorized 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 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" 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 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 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. 2.16.840.1.113883.1.11.16927
RoleClassSpecimen 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 A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes. --
RoleLinkStatus Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine. 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
RouteOfAdministration 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:SecurityPolicy, V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use Use, V:PrivacyMark, V:SecurityLabelMark, and V:ControlledUnclassifiedInformation used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, caveats including, purpose of use, obligation policy, refrain policy, dissemination controls and other refrain policies, and obligations privacy marks to which a custodian or receiver is required 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. 2.16.840.1.113883.1.11.390
ServiceDeliveryLocationRoleType A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) 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 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 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 **** 2.16.840.1.113883.1.11.10310
TelecommunicationCapabilities Description: Concepts 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 **** 2.16.840.1.113883.1.11.10706
TransmissionRelationshipTypeCode Description: A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in 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 2.16.840.1.113883.1.11.19707
WorkClassificationODH Code system of concepts representing a person's job type as defined by compensation 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 or is not currently in the labor pool seeking employment. 2.16.840.1.113883.1.11.20562
hl7ApprovalStatus 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 and present. --
hl7CMETAttribution **** MISSING DEFINITIONS **** --
hl7ITSType Description: Codes identifying types of HL7 Implementation Technology Specifications --
hl7ITSVersionCode 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 the ITS. --
hl7PublishingDomain Description: Codes for HL7 publishing domains (specific content area) --
hl7PublishingSection Description: Codes for HL7 publishing sections (major business categories) --
hl7PublishingSubSection Description: Codes for HL7 publishing sub-sections (business sub-categories) --
hl7Realm 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 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 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
hl7V3Conformance Description: Identifies allowed codes for HL7aTMs v3 conformance property. --
hl7VoteResolution Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM). --
orderableDrugForm OpenIssue: Missing description. --
policyHolderRole 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 a relationship with the covered party, such as spouse, child, etc. This vocabulary is essentially an inversion of the role relations 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. -- styleType <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 Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided. --
triggerEventID 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 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 in HL7 publications with no version id. E.g. PORX_TE123456UV. 2.16.840.1.113883.1.11.20324
xBasicConfidentialityKind Description: Used to enumerate the typical confidentiality constraints placed upon a clinical document. Usage Note: x_BasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject; or that the receiver may not disclose this information 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:
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:
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 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:
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 Process Interruption Reason
4000 Name/address representation