Name Definition Source Id
Namespace: http://hl7.org/fhir/ValueSet
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-type The type of action to be performed. Other 809
additionalmaterials This value set includes sample additional material type codes. Internal 529
address-type N The type of an address (physical / postal). Internal 69
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
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
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
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
approach-site-codes This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar. SNOMED CT 346
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-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
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
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-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
cdshooks-indicator This value set captures the set of indicator codes defined by the CDS Hooks specification. Other 1065
chargeitem-status Codes identifying the lifecycle stage of a ChargeItem. Internal 846
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
clinicalimpression-status Codes that reflect the current state of a clinical impression within its overall lifecycle. Internal 1046
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-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
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
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
condition-cause Example value set for Cause of Condition codes SNOMED CT 965
condition-code Example value set for Condition/Problem/Diagnosis codes. SNOMED CT 161
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
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-data-meaning How a resource reference is interpreted when testing consent restrictions. Internal 759
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
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
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-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-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-party-role This value set contract specific codes for offer party participation. Internal 1224
contract-scope This value set contract specific codes for scope. Internal 1216
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-type This value set includes sample Contract Type codes. Other 729
cosmic COSMIC : Catalogue Of Somatic Mutations In Cancer Other 912
coverage-class This value set includes Coverage Class codes. Other 1009
coverage-type This value set includes Coverage Type codes. Other 520
cpt-all A value set that includes all CPT codes Other null
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
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-topic High-level categorization of the definition, used for searching, sorting, and filtering. Other 794
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-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-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-status The availability status of the device. Internal 209
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
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
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. LOINC 46
document-mode N Whether the application produces or consumes documents. Internal 186
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
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-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-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
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
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-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-diagnosistype This value set includes example Diagnosis Type codes. Other 590
ex-onsettype This value set includes sample Service Modifier codes. Internal 578
ex-paymenttype This value set includes example Payment Type codes. Other 616
ex-program-code This value set includes sample Program Reason Span codes. Other 576
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-intensional This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. LOINC null
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
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
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-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-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
group-measure Possible group measure aggregates (E.g. Mean, Median). Internal 1345
group-type Types of resources that are part of group. Internal 284
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
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 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
insuranceplan-type This example value set defines a set of codes that can be used to indicate a type of insurance plan. Other 870
intervention This value set includes sample Intervention codes. Internal 532
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
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
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-model-mode How the referenced structure is used in this mapping. Internal 675
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-type The type of measure (includes codes from 2.16.840.1.113883.1.11.20368). Other 769
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-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
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
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-color Describes the typical color of representation. Internal 654
mimetypes N This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13) Other 1024
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
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
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-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-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
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
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 (qualifier value). SNOMED CT 152
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
payeetype This value set includes sample Payee Type codes. Other 31
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-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
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
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
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
provenance-activity-type This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes. V3 438
provenance-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
questionnaire-answers Example list of codes for answers to questions. (Not complete or necessarily appropriate.) SNOMED CT 446
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
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
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-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
relation-type The type of relations between entries. Internal 1028
relationship This value set includes the Patient to subscriber relationship codes. Internal 35
report-codes This value set includes LOINC codes that relate to Diagnostic Observations. LOINC 233
request-intent Codes indicating the degree of authority/intentionality associated with a request. Internal 113
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-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
resource-security-category Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource. Other 1403
resource-status The master set of status codes used throughout FHIR. All status codes are mapped to one of these codes. Internal 117
resource-types N One of the resource types defined as part of this version of FHIR. Internal 27
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-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-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-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
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-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
slotstatus The free/busy status of the slot. Internal 482
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-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-status Codes providing the status/availability of a specimen. Internal 471
study-type Types of research studies (types of research methods). Other 1349
subscriber-relationship This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient). Other 1385
subscription-tag Tags to put on a resource after subscriptions have been sent. Other 504
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
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
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
tooth This value set includes a smattering of FDI oral site codes. Other 540
transaction-mode A code that indicates how transactions are supported. Internal 192
ucum-bodylength UCUM units for recording body length measures such as height and head circumference FHIR 958
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
udi This value set includes sample UDI codes. Internal 554
udi-entry-type Codes to identify how UDI data was entered. Internal 211
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-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-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
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
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
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
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
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". --
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
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
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
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
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
Calendar **** MISSING DEFINITIONS **** 2.16.840.1.113883.1.11.17422
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
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
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
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
EducationLevel Years of education that a person has completed 2.16.840.1.113883.1.11.19175
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
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
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
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
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
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
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
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
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. --
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
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 all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type. OpenIssue:
Description copied from Concept Domain of same name. Must be corrected.. --
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
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
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
PersonalRelationshipRoleType Types of personal relationships between two living subjects. Example:
Parent, sibling, unrelated friend, neighbor 2.16.840.1.113883.1.11.19563
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
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
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
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:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, purpose of use, dissemination controls and other refrain policies, and obligations to which a custodian or receiver is required to comply. 2.16.840.1.113883.1.11.20471
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
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. --
TableCellScope These values are defined within the XHTML 4.0 Table Model 2.16.840.1.113883.1.11.11012
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
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 --
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. --
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. --
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). --
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