STU3
Candidate
Terminology
This
page
is
part
of
the
FHIR
Specification
(v1.8.0:
STU
3
Draft).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
This table contains a list of all the value sets defined as part of the FHIR specification. Some of these value sets include codes defined elsewhere, some contain their own inline code system definitions, and some do both. Any implicit code systems are case sensitive, though FHIR will never define codes that only differ by case.
| Name | Definition | Source | Id | |
| Namespace: http://hl7.org/fhir/ValueSet | ||||
| HGNC-geneIdentifiers | This value set includes all international curated set of gene identifiers in HGNC | Other | 468 | |
| HGVSvariant | This value set includes all international curated set for variant naming in HGVS nomenclature | Other | 392 | |
| LOINC-48002-0-answerlist | LOINC answer list for Genomic source class | Internal | 470 | |
| LOINC-48019-4-answerlist | LOINC answer list for Type of variation | Internal | 469 | |
| LOINC-53034-5-answerlist | LOINC answer list for AllelicState | Internal | 472 | |
| abstract-types | A type defined by FHIR that is an abstract type | Internal | abstract-types | |
| account-status | Indicates whether the account is available to be used. | Internal | 362 | |
| action-cardinality-behavior | Defines behavior for an action or a group for how many times that item may be repeated | Internal | 992 | |
| action-condition-kind | Defines the kinds of conditions that can appear on actions | Internal | 0 | |
| action-grouping-behavior | Defines organization behavior of a group | Internal | 988 | |
| action-participant-type | The type of participant for the action | Internal | 994 | |
| action-precheck-behavior | Defines selection frequency behavior for an action or group | Internal | 991 | |
| action-relationship-type | Defines the types of relationships between actions | Internal | 995 | |
| action-required-behavior | Defines requiredness behavior for selecting an action or an action group | Internal | 990 | |
| action-selection-behavior | Defines selection behavior of a group | Internal | 989 | |
| action-type | The type of action to be performed | Internal | 993 | |
| actionlist | List of allowable action which this resource can request. | Internal | 351 | |
| activity-definition-category | High-level categorization of the type of activity in a protocol. | Internal | 546 | |
| activity-reason | Example codes indicating the reason for a clinical activity being performed. | SNOMED CT | 68 | |
| additional-instructions-codes | This value set includes all SNOMED CT Additional Dosage Instructions. | SNOMED CT | 444 | |
| additionalmaterials | This value set includes sample additional material type codes. | Internal | 306 | |
| address-type | The type of an address (physical / postal) | Internal | 38 | |
| address-use | The use of an address | Internal | 37 | |
| adjudication | This value set includes a smattering of Adjudication codes. | Internal | 325 | |
| adjudication-error | This value set includes a smattering of adjudication codes. | Internal | adjudication-error | |
| adjudication-reason | This value set includes smattering of Adjudication Reason codes. | Internal | 479 | |
| administration-method-codes | This value set includes some method codes from SNOMED CT - provided as an exemplar | SNOMED CT | 190 | |
| administrative-gender | The gender of a person used for administrative purposes. | Internal | administrative-gender | |
| age-units | A valueSet of UCUM codes for representing age value units. | FHIR | age-units | |
| all-languages | This value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47) | Other | all-languages | |
| all-types | Either an abstract type, a resource or a data type. | Internal | all-types | |
| allerg-intol-substance-exp-risk | The risk of an adverse reaction (allergy or intolerance) for this patient upon xposure to the substance (including pharmaceutical products). | Internal | 999 | |
| allergy-clinical-status | The clinical status of the allergy or intolerance. | Internal | 0 | |
| allergy-intolerance-category | Category of an identified substance. | Internal | 53 | |
| allergy-intolerance-criticality | Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. | Internal | 51 | |
| allergy-intolerance-type | Identification of the underlying physiological mechanism for a Reaction Risk. | Internal | 52 | |
| allergy-verification-status | Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance. | Internal | 0 | |
| 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 | 935 | |
| animal-breeds | This example value set defines a set of codes that can be used to indicate breeds of species. | SNOMED CT | 232 | |
| animal-genderstatus | This example value set defines a set of codes that can be used to indicate the current state of the animal's reproductive organs. | Internal | 230 | |
| animal-species | This example value set defines a set of codes that can be used to indicate species of animal patients. | SNOMED CT | 231 | |
| anzsco-occupations | Developed for use in the collection, analysis and dissemination of occupation statistics in Australia and New Zealand. | Other | 253 | |
| appointmentstatus | The free/busy status of an appointment. | Internal | 284 | |
| approach-site-codes | This value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar. | SNOMED CT | 189 | |
| assert-direction-codes | The type of direction to use for assertion. | Internal | 359 | |
| assert-operator-codes | The type of operator to use for assertion. | Internal | 360 | |
| assert-response-code-types | The type of response code to use for assertion. | Internal | 361 | |
| audit-event-action | Indicator for type of action performed during the event that generated the audit. | Internal | 263 | |
| audit-event-outcome | Indicates whether the event succeeded or failed | Internal | 264 | |
| audit-event-sub-type | More detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions. | DICOM, Internal | 270 | |
| audit-event-type | Event Types for Audit Events - defined by DICOM with some FHIR specific additions. | DICOM, Internal | 269 | |
| audit-source-type | The type of process where the audit event originated from. | Internal | 272 | |
| basic-resource-type | This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. | Internal | 59 | |
| benefit-category | This value set includes a smattering of Benefit Category codes. | Internal | 481 | |
| benefit-network | This value set includes a smattering of Network type codes. | Internal | 484 | |
| benefit-subcategory | This value set includes a smattering of Benefit SubCategory codes. | Internal | 482 | |
| benefit-term | This value set includes a smattering of Benefit Term codes. | Internal | 486 | |
| benefit-type | This value set includes a smattering of Benefit type codes. | Internal | 483 | |
| benefit-unit | This value set includes a smattering of Unit type codes. | Internal | 485 | |
| binding-strength | Indication of the degree of conformance expectations associated with a binding. | Internal | binding-strength | |
| body-site | This value set includes all the "Anatomical Structure" SNOMED CT codes (i.e. codes with an is-a relationship with 442083009: Anatomical or acquired body site). | SNOMED CT | 78 | |
| bodysite-laterality | Laterality: SNOMED-CT concepts for 'left', 'right', and 'bilateral' | SNOMED CT | 442 | |
| bodysite-relative-location | SNOMED-CT concepts modifying the anatomic location | SNOMED CT | 347 | |
| bundle-type | Indicates the purpose of a bundle - how it was intended to be used. | Internal | 327 | |
| c80-doc-classcodes | This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). The Document Class value set is reproduced from HITSP C80 Table 2-144 Document Class Value Set Definition. Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests. | LOINC | 46 | |
| c80-doc-typecodes | This is the code specifying the precise type of document (e.g. Pulmonary History and Physical, Discharge Summary, Ultrasound Report, etc.). The Document Type value set includes all LOINC values listed in HITSP C80 Table 2-144 Document Class Value Set Definition above used for Document Class, and all LOINC values whose SCALE is DOC in the LOINC database. | LOINC | 47 | |
| c80-facilitycodes | This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147. | SNOMED CT | 67 | |
| c80-practice-codes | This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition. | SNOMED CT | 72 | |
| capability-statement-kind | How a capability statement is intended to be used. | Internal | 0 | |
| care-plan-activity | Example Codes for types of activities that can appear in a care plan. | SNOMED CT | 64 | |
| care-plan-activity-category | High-level categorization of the type of activity in a care plan. | Internal | 63 | |
| care-plan-activity-status | Indicates where the activity is at in its overall life cycle. | Internal | 65 | |
| care-plan-category | Example codes indicating the category a care plan falls within. Note that these are in no way complete and may not even be appropriate for some uses. | SNOMED CT | 67 | |
| care-plan-relationship | Codes identifying the types of relationships between two plans. | Internal | 406 | |
| care-plan-status | Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. | Internal | 60 | |
| choice-list-orientation | Direction in which lists of question options should be displayed | Internal | 429 | |
| chromosome-human | Chromosome number for human | Internal | 523 | |
| claim-careteamrole | This value set includes sample Claim Care Team Role codes. | Internal | 892 | |
| claim-exception | This value set includes sample Exception codes. | Internal | 889 | |
| claim-informationcategory | This value set includes sample Information Category codes. | Internal | 890 | |
| claim-modifiers | This value set includes sample Modifier type codes. | Internal | 311 | |
| claim-subtype | This value set includes sample Claim SubType codes. | Internal | 526 | |
| claim-type | This value set includes sample Claim Type codes. | Internal | 322 | |
| claim-use | Complete, proposed, exploratory, other | Internal | 315 | |
| classification-or-context | Identifies whether a useContext represents a context or classification for the element | Internal | 388 | |
| clinical-findings | This value set includes all the "Clinical finding" SNOMED CT codes (i.e. codes with an is-a relationship with 404684003: Clinical finding). | SNOMED CT | 115 | |
| clinical-impression-status | The workflow state of a clinical impression. | Internal | 71 | |
| clinicalimpression-prognosis | Example value set clinical impression prognosis | SNOMED CT | 937 | |
| codesystem-content-mode | How much of the content of the code system - the concepts and codes it defines - are represented in a code system resource | Internal | 550 | |
| codesystem-hierarchy-meaning | The meaning of the hierarchy of concepts in a code system | Internal | 982 | |
| common-tags | Common Tag Codes defined by FHIR project | Internal | 435 | |
| communication-request-status | The status of the communication. | Internal | 80 | |
| communication-status | The status of the communication. | Internal | 79 | |
| compartment-type | Which compartment a compartmnet definition describes | Internal | 551 | |
| composite-measure-scoring | The composite scoring method of the measure | Internal | 0 | |
| composition-attestation-mode | The way in which a person authenticated a composition. | Internal | 120 | |
| composition-status | The workflow/clinical status of the composition. | Internal | 123 | |
| concept-map-equivalence | The degree of equivalence between concepts. | Internal | concept-map-equivalence | |
| concept-property-type | The type of a property value | Internal | 549 | |
| condition-category | Preferred value set for Condition Categories. | Internal | 73 | |
| condition-cause | Example value set for Cause of Condition codes | SNOMED CT | 376 | |
| condition-clinical | Preferred value set for Condition Clinical Status. | Internal | 74 | |
| condition-code | Example value set for Condition/Problem/Diagnosis codes | SNOMED CT | 72 | |
| condition-outcome | Example value set for Condition Outcomes | SNOMED CT | 149 | |
| condition-predecessor | Example value set for Condition Predecessor codes | SNOMED CT | 377 | |
| condition-severity | Preferred value set for Condition/Diagnosis severity grading | SNOMED CT | 76 | |
| condition-stage | Example value set for stages of cancer and other conditions | SNOMED CT | 408 | |
| condition-state | Enumeration indicating whether the condition is currently active, inactive, or has been resolved. | Internal | 375 | |
| condition-ver-status | The verification status to support or decline the clinical status of the condition or diagnosis. | Internal | 75 | |
| conditional-delete-status | A code that indicates how the server supports conditional delete. | Internal | 91 | |
| conditional-read-status | A code that indicates how the server supports conditional read. | Internal | 939 | |
| conformance-expectation | Indicates the degree of adherence to a specified behavior or capability expected in order for a system to be deemed conformant with a specification. | Internal | 381 | |
| consent-action | This value set includes sample Consent Action codes. | Internal | 902 | |
| consent-actor-role | This value set includes sample Consent Type codes. | V3 | 903 | |
| consent-category | This value set includes sample Consent Category codes. | Internal | 973 | |
| consent-content-class | This value set includes the FHIR resource types, along with some other important content class codes | Other, Internal | 975 | |
| consent-content-code | This example value set contains all LOINC code | LOINC | 976 | |
| consent-data-meaning | How a resource reference is interpreted when testing consent restrictions | Internal | 974 | |
| consent-except-type | How an exception is statement is applied, as adding additional consent, or removing consent | Internal | 900 | |
| consent-status | Indicates the status of the consent | Internal | 904 | |
| consistency-type | FluidConsistencyType : Codes used to represent the consistency of fluids and liquids provided to the patient. This value set includes all the children of SNOMED CT Concepts from SCTID(US Extension): 435681000124103 Dietary liquid consistency diet (regime/therapy) and is provided as a suggestive example. | SNOMED CT | 210 | |
| constraint-severity | SHALL applications comply with this constraint? | Internal | 44 | |
| contact-point-system | Telecommunications form for contact point | Internal | 39 | |
| contact-point-use | Use of contact point | Internal | 40 | |
| contactentity-type | This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party. | Internal | 229 | |
| content-type | The content or mime type. | Internal | 358 | |
| contract-action | This value set includes sample Contract Action codes. | Other | 100 | |
| contract-actorrole | This value set includes sample Contract Actor Role codes. | Other | 102 | |
| contract-signer-type | This value set includes sample Contract Signer Type codes. | Other | 99 | |
| contract-subtype | This value set includes sample Contract Subtype codes. | Internal | 96 | |
| contract-term-subtype | This value set includes sample Contract Term SubType codes. | Internal | 98 | |
| contract-term-type | This value set includes sample Contract Term Type codes. | Internal | 97 | |
| contract-type | This value set includes sample Contract Type codes. | Internal | 95 | |
| contributor-type | The type of contributor | Internal | 923 | |
| copy-number-event | Copy Number Event | Internal | 524 | |
| coverage-exception | This value set includes sample Exception codes. | Internal | 307 | |
| coverage-level | This value set includes sample Coverage Level codes. | Internal | 0 | |
| coverage-selfpay | This value set includes Coverage SelfPay codes. | Internal | 0 | |
| coverage-type | This value set includes Coverage Type codes. | Internal | 304 | |
| cpt-all | A value set that includes all CPT codes | Other | null | |
| dWebType | The type of the service endpoint | Internal | 556 | |
| data-absent-reason | Used to specify why the normally expected content of the data element is missing. | Internal | data-absent-reason | |
| data-types | The type of an element - one of the FHIR data types. | Internal | data-types | |
| dataelement-sdcobjectclass | The allowed codes for identifying the ISO 11179 ObjectClass for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. | SNOMED CT, LOINC, Other | 372 | |
| dataelement-sdcobjectclassproperty | The allowed codes for identifying the ISO 11179 ObjectClass Property for a particular data element if intended for registration/use within the U.S. Structured Data Capture (SDC) project. | SNOMED CT, LOINC, Other | 373 | |
| dataelement-stringency | Indicates the degree of precision of the data element definition. | Internal | 244 | |
| days-of-week | The days of the week. | Internal | 302 | |
| defined-types | Either a resource or a data type. | Internal | defined-types | |
| definition-status | Codes identifying the stage lifecycle stage of a definition | Internal | 926 | |
| designation-use | Details of how a designation would be used | SNOMED CT | 281 | |
| detailed-ethnicity | The 41 [CDC ethnicity codes](http://www.cdc.gov/phin/resources/vocabulary/index.html) that are grouped under one of the 2 OMB ethnicity category codes. | Other | 0 | |
| detailed-race | The 900+ [CDC Race codes](http://www.cdc.gov/phin/resources/vocabulary/index.html) that are grouped under one of the 5 OMB race category codes. | Other | 0 | |
| detectedissue-category | Kinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc. | V3 | 103 | |
| detectedissue-mitigation-action | Kinds of mitigating actions and observations that can be associated with a detected issue or contraindication, such as 'added concurrent therapy', 'prior therapy documented', etc. | V3 | 104 | |
| detectedissue-severity | Indicates the potential degree of impact of the identified issue on the patient. | Internal | 105 | |
| device-action | Example value set for Procedure Device Action code (what happened to a device during a procedure. | Internal | 236 | |
| device-kind | Device Types : Codes used to identify medical devices. This value set includes all children of SNOMED CT Concepts (US Extension and Core) from SCTID 49062001 Device (physical object) and is provided as a suggestive example. | SNOMED CT | 106 | |
| devicestatus | The availability status of the device. | Internal | 107 | |
| diagnostic-report-status | The status of the diagnostic report as a whole. | Internal | 118 | |
| diagnostic-requests | This value set includes all the LOINC Order codes. | LOINC | 112 | |
| diagnostic-service-sections | This value set includes all the codes in HL7 v2 table 0074. | V2 | 117 | |
| dicm-402-roleid | Audit agent Role ID Code | DICOM | 271 | |
| dicm-405-mediatype | Media Type Code | DICOM | 424 | |
| dicom-cid29 | This Value Set includes codes that may be used to identify an image or waveform acquisition modality, as used in the ImagingStudy resource, Dicom Attribute Modality (0008,0060) or HL7 v2 Table 0259 (see HL7 v2.6 Chapter 8 Section 8.8.8.47). It generally corresponds to a class of diagnostic equipment, or to a specific acquisition function or technique in a device. | DICOM | 158 | |
| diet-type | DietCode : Codes that can be used to indicate the type of food being ordered for a patient. This value set includes all children of SNOMED CT Concepts (US Extension and Core) from SCTID 182922004 Dietary regime (Therapeutic or Preventive Procedure) and is provided as a suggestive example. | SNOMED CT | 206 | |
| digital-media-subtype | Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it. | Other, SNOMED CT, Internal | 184 | |
| digital-media-type | Whether the Media is a photo, video, or audio | Internal | 183 | |
| doc-classcodes | LOINC codes for Document Kind, taken from the LOINC document ontology. | LOINC | 125 | |
| doc-section-codes | Document section codes (LOINC codes used in CCDA sections). | LOINC | 119 | |
| doc-typecodes | FHIR Document Codes - all LOINC codes where scale type = 'DOC'. | LOINC | 121 | |
| document-mode | Whether the application produces or consumes documents. | Internal | 87 | |
| document-reference-status | The status of the document reference. | Internal | document-reference-status | |
| document-relationship-type | The type of relationship between documents. | Internal | 133 | |
| encounter-admit-source | This value set defines a set of codes that can be used to indicate from where the patient came in. | Internal | 144 | |
| encounter-diet | This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. | Internal | 142 | |
| encounter-discharge-disposition | This value set defines a set of codes that can be used to where the patient left the hospital. | Internal | 145 | |
| encounter-location-status | The status of the location. | Internal | 147 | |
| encounter-participant-type | This value set defines a set of codes that can be used to indicate how an individual participates in an encounter. | V3, Internal | 139 | |
| encounter-reason | This examples value set defines the set of codes that can be used to indicate reasons for an encounter. | SNOMED CT | 146 | |
| encounter-special-arrangements | This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit. | Internal | 141 | |
| encounter-special-courtesy | This value set defines a set of codes that can be used to indicate special courtesies provided to the patient. | V3 | 140 | |
| encounter-status | Current state of the encounter | Internal | 948 | |
| encounter-type | This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided. | Internal | 137 | |
| 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. | Internal | 0 | |
| 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 | 959 | |
| endpoint-status | The status of the endpoint | Internal | 883 | |
| enteral-route | EnteralRouteOfAdministration: Codes specifying the route of administration of enteral formula. This value set is composed of HL7 v3 codes and is provided as a suggestive example. | V3 | 214 | |
| entformula-additive | EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example. | Internal | 213 | |
| entformula-type | EnteralFormulaType : Codes for type of enteral formula to be administered to patient. This value set is is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 Enteral+supplement feeds hierarchy and is provided as a suggestive example. | SNOMED CT | 212 | |
| episode-of-care-status | The status of the episode of care. | Internal | 346 | |
| event-capability-mode | The mode of a message capability statement. | Internal | 0 | |
| event-status | Codes identifying the stage lifecycle stage of a event | Internal | 929 | |
| event-timing | Real world event that the relating to the schedule. | Internal, V3 | 41 | |
| ex-diagnosisrelatedgroup | This value set includes example Diagnosis Related Group codes. | Internal | 919 | |
| ex-diagnosistype | This value set includes example Diagnosis Type codes. | Internal | 920 | |
| ex-onsettype | This value set includes sample Service Modifier codes. | Internal | 888 | |
| ex-payee-resource-type | The type of payee Resource | Internal | 891 | |
| ex-paymenttype | This value set includes example Payment Type codes. | Internal | 333 | |
| ex-program-code | This value set includes sample Program Reason Span codes. | Internal | 887 | |
| ex-revenue-center | This value set includes sample Revenue Center codes. | Internal | 962 | |
| 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-intensional | This is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36. | LOINC | null | |
| explanationofbenefit-status | A code specifying the state of the resource instance. | Internal | 964 | |
| extension-context | How an extension context is interpreted. | Internal | 349 | |
| filter-operator | The kind of operation to perform as a part of a property based filter. | Internal | 280 | |
| fips-county | This value set defines FIPS codes for US counties and county equivalent entities. | Other | fips-county | |
| flag-category | Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) | Internal | 403 | |
| flag-code | Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.) | SNOMED CT | 404 | |
| flag-priority | This value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority. | Internal | 433 | |
| flag-status | Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or entered in error. | Internal | 49 | |
| fm-conditions | This value set includes sample Conditions codes. | Internal | 321 | |
| fm-itemtype | This value set includes sample Item Type codes. | Internal | 317 | |
| fm-status | This value set includes STatus codes. | Internal | 961 | |
| focal-subject | Example VS composed from SNOMED CT and HL7 v3 codes for observation targets: donor, fetus, spouse. As use cases are discovered more values may be added. | SNOMED CT, V3 | 400 | |
| food-type | FoodType : This value set represents SNOMED CT codes for types of foods. This value set includes all the children of SNOMED CT Concepts from SCTID 255620007 Foods (substance) and is provided as a suggestive example. | SNOMED CT | 205 | |
| formatcodes | The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at http://wiki.hl7.org/index.php?title=CDA_Format_Codes_for_IHE_XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incomplete | Other | 3 | |
| forms | This value set includes a sample set of Forms codes. | Internal | forms | |
| fundsreserve | This value set includes sample funds reservation type codes. | Internal | fundsreserve | |
| goal-acceptance-status | Codes indicating whether the goal has been accepted by a stakeholder | Internal | 431 | |
| goal-category | Example codes for grouping goals for filtering or presentation. | Internal | 411 | |
| goal-priority | Indicates the level of importance associated with reaching or sustaining a goal. | Internal | 151 | |
| goal-relationship-type | Types of relationships between two goals | Internal | 390 | |
| goal-start-event | Identifies types of events that might trigger the start of a goal. | SNOMED CT | 413 | |
| goal-status | Indicates whether the goal has been met and is still being targeted | Internal | 150 | |
| goal-status-reason | Example codes indicating the reason for a current status. Note that these are in no way complete and may not even be appropriate for some uses. | Internal | 412 | |
| group-type | Types of resources that are part of group | Internal | 156 | |
| guidance-response-status | The status of a guidance response | Internal | 489 | |
| guide-dependency-type | How a dependency is represented when the guide is published. | Internal | 170 | |
| guide-page-kind | The kind of an included page. | Internal | 171 | |
| history-status | A code that identifies the status of the family history record. | Internal | 409 | |
| hl7-work-group | An HL7 administrative unit that owns artifacts in the FHIR specification | Internal | 0 | |
| http-verb | HTTP verbs (in the HTTP command line). | Internal | 329 | |
| icd-10 | This value set includes sample ICD-10 codes. | Internal | 308 | |
| icd-10-procedures | This value set includes sample ICD-10 Procedure codes. | Internal | 533 | |
| identifier-type | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | V2, Internal | identifier-type | |
| identifier-use | Identifies the purpose for this identifier, if known . | Internal | 33 | |
| identity-assuranceLevel | The level of confidence that this link represents the same actual person, based on NIST Authentication Levels. | Internal | 342 | |
| immunization-origin | This identifies the source of the data when the report of the immunization event is not based on information from the person who administered the vaccine. | Other | 281 | |
| immunization-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | SNOMED CT | 163 | |
| immunization-recommendation-date-criterion | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | Internal | 169 | |
| immunization-recommendation-status | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | Internal | 168 | |
| immunization-route | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | V3 | 162 | |
| immunization-site | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | V3 | 161 | |
| 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 the immunization process. | Internal | 416 | |
| instance-availability | Availability of the resource | DICOM | 157 | |
| intervention | This value set includes sample Intervention codes. | Internal | 309 | |
| investigation-sets | Example value set for investigation type | SNOMED CT | 69 | |
| issue-severity | How the issue affects the success of the action. | Internal | 223 | |
| issue-type | A code that describes the type of issue. | Internal | 224 | |
| item-type | Distinguishes groups from questions and display text and indicates data type for questions | Internal | 477 | |
| jurisdiction | This value set defines a base set of codes for country and region, for indicating where a resource is intended to be used | Other | jurisdiction | |
| kos-title | The document title code of key object selection | DICOM | 159 | |
| languages | This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) | Other | languages | |
| ldlcholesterol-codes | LDL Cholesterol codes - measured or calculated | LOINC | 444 | |
| library-type | The type of knowledge asset this library contains | Internal | 978 | |
| link-type | The type of link between this patient resource and another patient resource. | Internal | 234 | |
| linkage-type | Used to distinguish different roles a resource can play within a set of linked resources | Internal | 525 | |
| list-empty-reason | General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list). | Internal | 176 | |
| list-example-codes | Example use codes for the List resource - typical kinds of use. | Internal | 173 | |
| list-item-flag | Example Item Flags for the List Resource. In this case, these are the kind of flags that would be used on a medication list at the end of a consultation. | Other | 175 | |
| list-mode | The processing mode that applies to this list | Internal | 174 | |
| list-order | Base values for the order of the items in a list resource. | Internal | 177 | |
| list-status | The current state of the list | Internal | 178 | |
| location-mode | Indicates whether a resource instance represents a specific location or a class of locations. | Internal | 181 | |
| location-physical-type | This example value set defines a set of codes that can be used to indicate the physical form of the Location. | Internal | 179 | |
| location-status | Indicates whether the location is still in use. | Internal | 182 | |
| manifestation-codes | This value set includes all SNOMED CT Clinical Findings. | SNOMED CT | 55 | |
| manifestation-or-symptom | Example value set for Manifestation and Symptom codes. | SNOMED CT | 77 | |
| map-context-type | How to interpret the context | Internal | 536 | |
| map-input-mode | Mode for this instance of data | Internal | 535 | |
| map-list-mode | If field is a list, how to manage the list | Internal | 538 | |
| map-model-mode | How the referenced structure is used in this mapping | Internal | 534 | |
| map-transform | How data is copied / created | Internal | 537 | |
| marital-status | This value set defines the set of codes that can be used to indicate the marital status of a person. | V3 | marital-status | |
| match-grade | A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. | Internal | 563 | |
| measure-data-usage | The intended usage for supplemental data elements in the measure | Internal | 905 | |
| measure-population | The type of population | Internal | 508 | |
| measure-report-status | The status of the measure report | Internal | 541 | |
| measure-report-type | The type of the measure report | Internal | 559 | |
| measure-scoring | The scoring type of the measure | Internal | 539 | |
| measure-type | The type of measure (includes codes from 2.16.840.1.113883.1.11.20368) | Internal | 540 | |
| measurement-principle | Different measurement principle supported by the device. | Internal | 0 | |
| media-view | Codes defined in SNOMED CT that can be used to record Media Recording views. | SNOMED CT | 185 | |
| medication-admin-status | A set of codes indicating the current status of a MedicationAdministration. | Internal | 186 | |
| medication-as-needed-reason | This value set includes all clinical findings from SNOMED CT - provided as an exemplar value set. | SNOMED CT | 193 | |
| 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 | 199 | |
| medication-dispense-status | A coded concept specifying the state of the dispense event. | Internal | 192 | |
| medication-form-codes | This value set includes all Form codes from SNOMED CT - provided as an exemplar. | SNOMED CT | 198 | |
| medication-package-form-codes | This value set includes all Form codes from SNOMED CT - provided as an exemplar. | SNOMED CT | 201 | |
| medication-request-category | A coded concept identifying where the medication ordered is expected to be consumed or administered | Internal | 951 | |
| medication-request-stage | Kind of request - proposal, plan or order. | Internal | 0 | |
| medication-request-status | A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription | Internal | 196 | |
| medication-statement-category | A coded concept identifying where the medication included in the medicationstatement is expected to be consumed or administered | Internal | 952 | |
| medication-statement-nottaken | A coded concept identifying level of certainty if patient has taken or has not taken the medication | Internal | 0 | |
| medication-statement-status | A coded concept indicating the current status of a MedicationStatement. | Internal | 197 | |
| message-events | One of the message events defined as part of FHIR. | Internal | message-events | |
| message-reason-encounter | Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. | Internal | 202 | |
| message-significance-category | The impact of the content of a message. | Internal | 88 | |
| message-transport | The protocol used for message transport. | Internal | 86 | |
| metric-calibration-state | Describes the state of a metric calibration. | Internal | 340 | |
| metric-calibration-type | Describes the type of a metric calibration. | Internal | 339 | |
| metric-category | Describes the category of the metric. | Internal | 338 | |
| metric-color | Describes the typical color of representation. | Internal | 341 | |
| metric-operational-status | Describes the operational status of the DeviceMetric. | Internal | 337 | |
| missing-tooth-reason | This value set includes sample Missing Tooth Reason codes. | Internal | 893 | |
| modified-foodtype | TextureModifiedFoodType: Codes for types of foods that are texture modified. This value set is composed SNOMED CT Concepts from SCTID 255620007 Foods (substance) and is provided as a suggestive example. | SNOMED CT | 209 | |
| name-assembly-order | A code that represents the preferred display order of the components of a human name | Internal, V2, V3 | 0 | |
| name-part-qualifier | A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type | V3 | 363 | |
| name-use | The use of a human name | Internal | 36 | |
| name-v3-representation | A set of codes for each different representation of a name | V3 | 910 | |
| namingsystem-identifier-type | Identifies the style of unique identifier used to identify a namespace. | Internal | 293 | |
| namingsystem-type | Identifies the purpose of the naming system. | Internal | 290 | |
| narrative-status | The status of a resource narrative | Internal | 32 | |
| network-type | The type of network access point of this agent in the audit event | Internal | 955 | |
| 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 | |
| no-immunization-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | V3, SNOMED CT | 164 | |
| note-type | The presentation types of notes. | Internal | note-type | |
| nutrient-code | NutrientModifier : Codes for types of nutrient that is being modified such as carbohydrate or sodium. This value set includes all the children of SNOMED CT Concepts from SCTID 226355009 Nutrients (substance), Sodium, Potassium and Fluid and is provided as a suggestive example. | SNOMED CT | 207 | |
| nutrition-request-status | Codes specifying the state of the request. Describes the lifecycle of the nutrition order. | Internal | 204 | |
| object-lifecycle | Identifier for the data life-cycle stage for the entity. | Internal | 958 | |
| object-role | Code representing the role the entity played in the event. | Internal | 957 | |
| object-type | Code for the entity type involved audited. | Internal | 956 | |
| observation-category | Observation Category codes. | Internal | 222 | |
| observation-codes | This value set includes all LOINC codes | LOINC | 216 | |
| observation-interpretation | This value set defines the set of codes that can be used to indicate the meaning/use of a reference range. | V2 | 218 | |
| observation-methods | Observation Method codes from SNOMED CT (codes subsumed by 272394005 "Technique", and the v3 Code System "ObservationMethod" (which is no longer actively maintained). | V3, SNOMED CT | 215 | |
| observation-relationshiptypes | Codes specifying how two observations are related. | Internal | 220 | |
| observation-statistics | The statistical operation parameter -"statistic" - codes | Internal | 0 | |
| observation-status | Codes providing the status of an observation. | Internal | 219 | |
| observation-valueabsentreason | This value set defines the set of codes for identifying the reason why the expected result in Observation.value[x] is missing. | Internal | 221 | |
| observation-vitalsignresult | This value set indicates the allowed vital sign result types. The concept Vitals Signs Panel (8716-3) 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 systolic and diastolic (55284-4) is used to group the component observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4). | LOINC | 62 | |
| omb-ethnicity | The codes for the ethnicity categories - 'Hispanic or Latino' and 'Non Hispanic or Latino' - as defined by the [OMB Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997](https://www.whitehouse.gov/omb/fedreg_1997standards). | Internal | 0 | |
| omb-race | The codes for the concepts 'Unknown' and 'Asked but no answer' and the the codes for the five race categories - 'American Indian' or 'Alaska Native', 'Asian', 'Black or African American', 'Native Hawaiian or Other Pacific Islander', and 'White' - as defined by the [OMB Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997](https://www.whitehouse.gov/omb/fedreg_1997standards) . | V3 | 575 | |
| operation-kind | Whether an operation is a normal operation or a query. | Internal | 297 | |
| operation-outcome | Operation Outcome codes used by FHIR test servers (see Implementation file translations.xml) | Internal | 225 | |
| operation-parameter-use | Whether an operation parameter is an input or an output parameter. | Internal | 298 | |
| oral-prosthodontic-material | This value set includes sample Oral Prosthodontic Material type codes. | Internal | 312 | |
| organization-type | This example value set defines a set of codes that can be used to indicate a type of organization. | Internal | 228 | |
| parent-relationship-codes | The value set includes the v3 RoleCode PRN (parent), TWIN (twin) and all of their specializations. It covers the relationships needed to establish genetic pedigree relationships between family members. | V3 | 382 | |
| participant-role | Roles of Participants that may be included in a CarePlan.Participants, or in an EpisodeOfCare.CareTeam. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization (qualifier value). | SNOMED CT | 555 | |
| participantrequired | Is the Participant required to attend the appointment. | Internal | 286 | |
| participationstatus | The Participation status of an appointment. | Internal | 285 | |
| patient-mpi-match | A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. | Internal | 434 | |
| payeetype | This value set includes sample Payee Type codes. | Internal | payeetype | |
| payment-adjustment-reason | This value set includes smattering of Payment Adjustment Reason codes. | Internal | 480 | |
| payment-status | This value set includes a sample set of Payment Status codes. | Internal | 334 | |
| payment-type | This value set includes sample Payment Type codes. | Internal | 333 | |
| performer-role | This examples value set defines the set of codes that can be used to indicate a role of procedure performer. | SNOMED CT | 420 | |
| plan-definition-type | The type of PlanDefinition | Internal | 987 | |
| policyholder-relationship | This value set includes codes for the relationship between the Policyholder and the Beneficiary (insured/covered party/patient).. | Internal | 23 | |
| postal-address-use | Uses of an address not included in Address.use | V3 | 365 | |
| practitioner-role | This example value set defines a set of codes that can be used to indicate the role of a Practitioner. | Internal | 251 | |
| practitioner-specialty | This example value set defines a set of codes that can be used to indicate the specialty of a Practitioner. | Internal | 252 | |
| probability-distribution-type | Codes specifying the type of probability distribution | V3 | 364 | |
| procedure-category | Procedure Category code: A selection of relevant SNOMED CT codes. | SNOMED CT | 241 | |
| procedure-code | Procedure Code: All SNOMED CT procedure codes. | SNOMED CT | 417 | |
| procedure-followup | Procedure follow up codes: a selection of SNOMED CT codes relevant to procedure follow up. | SNOMED CT | 240 | |
| procedure-not-performed-reason | Situation codes describing the reason that a procedure, which might otherwise be expected, was not performed, or a procedure that was started 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 | 418 | |
| procedure-outcome | Procedure Outcome code: A selection of relevant SNOMED CT codes. | SNOMED CT | 239 | |
| procedure-progress-status-codes | This value set is provided as an exemplar. The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the procedure performance process. | Internal | 430 | |
| procedure-reason | This examples value set defines the set of codes that can be used to indicate a reasons for a procedure. | SNOMED CT | 419 | |
| procedure-relationship-type | The nature of the relationship with this procedure. | Internal | 235 | |
| procedure-request-priority | The priority of the request. | Internal | 243 | |
| procedure-request-status | The status of the request. | Internal | 242 | |
| procedure-status | A code specifying the state of the procedure. | Internal | 237 | |
| process-outcome | This value set includes sample Process Outcome codes. | Internal | 352 | |
| process-priority | This value set includes the financial processing priority codes. | Internal | 319 | |
| profile-code | Codes for the meaning of the defined structure. | SNOMED CT, LOINC | 350 | |
| property-representation | How a property is represented on the wire. | Internal | 47 | |
| provenance-agent-role | The role that a provenance participant played | Internal | 245 | |
| provenance-agent-type | The type of a provenance participant. Use either a defined FHIR resource type, or, if the reference is not to a resource, one of the defined codes, or some other code if none of the defined codes are appropriate. | Internal | 246 | |
| provenance-entity-role | How an entity was used in an activity. | Internal | 247 | |
| provider-qualification | This value set includes sample Provider Qualification codes. | Internal | 531 | |
| publication-status | The lifecycle status of a Value Set or Concept Map. | Internal | publication-status | |
| quality-type | Type for quality report | Internal | 0 | |
| quantity-comparator | How the Quantity should be understood and represented. | Internal | 34 | |
| question-max-occurs | Flags an element as having unlimited repetitions | Internal | 380 | |
| questionnaire-answers | Example list of codes for answers to questions. (Not complete or necessarily appropriate.) | SNOMED CT | 423 | |
| questionnaire-answers-status | Lifecycle status of the questionnaire response. | Internal | 258 | |
| questionnaire-category | Example list of potential categegories for questionnaires. | SNOMED CT | 379 | |
| questionnaire-display-category | Codes defining the purpose of a Questionnaire item of type 'text'. | Internal | 510 | |
| questionnaire-item-control | Starter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire. | Internal | 509 | |
| questionnaire-questions | Example list of codes for questions and groups of questions. (Not necessariliy complete or appropriate.) | LOINC | 476 | |
| questionnaire-status | Lifecycle status of the questionnaire. | Internal | 256 | |
| questionnaire-usage-mode | Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item | Internal | 998 | |
| reaction-event-certainty | Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in an reaction event. | Internal | 54 | |
| reaction-event-severity | Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. | Internal | 56 | |
| reason-medication-given-codes | This value set is provided as an exemplar. The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process. | Internal | 188 | |
| reason-medication-not-given-codes | This value set 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 | 187 | |
| reason-medication-not-taken-codes | This value set includes some not taken reason codes from SNOMED CT - provided as an exemplar | SNOMED CT | 0 | |
| reference-handling-policy | A set of flags that defines how references are supported | Internal | 0 | |
| reference-version-rules | Whether a reference needs to be version specific or version independent, or whetehr either can be used | Internal | 869 | |
| referencerange-meaning | This value set defines a set of codes that can be used to indicate the meaning/use of a reference range. | Other, SNOMED CT, Internal | 217 | |
| referralcategory | Identifies the degree of intention/authorization associated with the request | Internal | 885 | |
| referralstatus | The status of the referral. | Internal | 300 | |
| related-artifact-type | The type of relationship to the related artifact | Internal | 0 | |
| related-claim-relationship | This value set includes sample Related Claim Relationship codes. | Internal | 527 | |
| relatedperson-relationshiptype | A set of codes that can be used to indicate the relationship between a Patient and a Related Person. | V2, V3 | 259 | |
| relationship | This value set includes the Patient to subscriber relationship codes. | Internal | relationship | |
| remittance-outcome | This value set includes a Claim Processing Outcome codes. | Internal | 7 | |
| report-codes | This value set includes all the LOINC codes which relate to Diagnostic Observations. | LOINC | 116 | |
| report-participant-type | The type of participant. | Internal | 0 | |
| report-result-codes | The results of executing an action. | Internal | 0 | |
| report-status-codes | The execution status of the TestReport. | Internal | 0 | |
| repository-type | Type for access of external uri | Internal | 0 | |
| request-intent | Codes indicating the degree of authority/intentionality associated with a request | Internal | 0 | |
| request-priority | The clinical priority of a diagnostic order. | Internal | 0 | |
| request-stage | Kind of request - proposal, plan or order. | Internal | 940 | |
| request-status | Codes identifying the stage lifecycle stage of a request | Internal | 931 | |
| research-study-status | Codes that convey the current status of the research study | Internal | 0 | |
| research-subject-status | Indicates the progression of a study subject through a study | Internal | 0 | |
| resource-aggregation-mode | How resource references can be aggregated. | Internal | 46 | |
| resource-slicing-rules | How slices are interpreted when evaluating an instance. | Internal | 45 | |
| resource-type-link | The type of payee Resource | Internal | 891 | |
| resource-types | One of the resource types defined as part of FHIR. | Internal | resource-types | |
| resource-validation-mode | Codes indicating the type of validation to perform | Internal | 48 | |
| response-code | The kind of response to a message | Internal | 203 | |
| restful-capability-mode | The mode of a RESTful capability statement. | Internal | 0 | |
| restful-security-service | Types of security services used with FHIR. | Internal | 82 | |
| risk-probability | Codes representing the likelihood of a particular outcome in a risk assessment. | Internal | 262 | |
| route-codes | This value set includes all Route codes from SNOMED CT - provided as an exemplar. | SNOMED CT | 58 | |
| search-comparator | What Search Comparator Codes are supported in search | Internal | 0 | |
| search-entry-mode | Why an entry is in the result set - whether it's included as a match or because of an _include requirement. | Internal | 328 | |
| search-modifier-code | A supported modifier for a search parameter. | Internal | 92 | |
| search-param-type | Data types allowed to be used for search parameters. | Internal | search-param-type | |
| search-xpath-usage | How a search parameter relates to the set of elements returned by evaluating its xpath query. | Internal | 332 | |
| security-labels | A single value set for all security labels defined by FHIR. | Other | security-labels | |
| sequence-referenceSeq | This value set includes all Reference codes | Other | 475 | |
| 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 | 467 | |
| sequence-type | Type if a sequence -- DNA, RNA, or amino acid sequence | Internal | 473 | |
| sequence-variationID | This value set includes all SNP codes | Other | 474 | |
| service-category | This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. | Internal | 879 | |
| service-modifiers | This value set includes sample Service Modifier codes. | Internal | 532 | |
| service-pharmacy | This value set includes a smattering of Pharmacy Service codes. | Internal | 324 | |
| service-place | This value set includes a smattering of Service Place codes. | Internal | 478 | |
| service-product | This value set includes a smattering of Service/Product codes. | Internal | 323 | |
| service-provision-conditions | The code(s) that detail the conditions under which the healthcare service is available/offered. | Internal | 303 | |
| service-referral-method | The methods of referral can be used when referring to a specific HealthCareService resource. | Internal | 301 | |
| service-type | This value set defines an example set of codes of service-types. | Internal | 880 | |
| service-uscls | This value set includes a smattering of USCLS codes. | Internal | 314 | |
| sibling-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 | 0 | |
| 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 | 35 | |
| slotstatus | The free/busy status of the slot. | Internal | 283 | |
| special-values | A set of generally useful codes defined so they can be included in value sets. | Internal | special-values | |
| specimen-collection-method | This example value set defines a set of codes that can be used to indicate the method of collection of a specimen. It includes values from HL7 v2 table 0048. | SNOMED CT, V2 | 275 | |
| specimen-collection-priority | This example value set defines a set of codes that can be used to indicate the priority of collection of a specimen. | Other | 402 | |
| specimen-container-type | Containers which may hold specimens or specimen containers - all SNOMED CT specimen containers. | SNOMED CT | 277 | |
| specimen-status | Codes providing the status/availability of a specimen. | Internal | 426 | |
| specimen-treatment-procedure | The technique that is used to perform the process or preserve the specimen. | V2 | 276 | |
| structure-definition-kind | Defines the type of structure that a definition is describing. | Internal | 348 | |
| subscription-channel-type | The type of method used to execute a subscription. | Internal | 294 | |
| subscription-status | The status of a subscription. | Internal | 295 | |
| subscription-tag | Tags to put on a resource after subscriptions have been sent. | Internal | 296 | |
| substance-category | Substance category codes | Internal | 279 | |
| substance-code | This value set contains concept codes for specific substances. | SNOMED CT | 878 | |
| supplement-type | SupplementType : Codes for nutritional supplements to be provided to the patient. This value set is is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 Enteral+supplement feeds hierarchy and is provided as a suggestive example. | SNOMED CT | 211 | |
| supply-item | This value set includes all substance and physical object codes from SNOMED CT and provided as an example value set. | SNOMED CT | 896 | |
| supplydelivery-status | Status of the supply delivery. | Internal | 355 | |
| supplydelivery-type | This value sets refers to a specific supply item. | Internal | 356 | |
| supplyrequest-kind | This value sets refers to a Category of supply. | Internal | 353 | |
| supplyrequest-reason | Why the supply item was requested | Internal | 464 | |
| supplyrequest-status | Status of the supply request | Internal | 354 | |
| supplyrequest-when | Example codes indicating the timing of when the request should be (is intended to be) fulfilled. | SNOMED CT | 463 | |
| surface | This value set includes a smattering of FDI tooth surface codes. | Internal | 316 | |
| system-restful-interaction | Operations supported by REST at the system level. | Internal | 84 | |
| system-version-processing-mode | How to manage the intersection between a fixed version in a value set, and a fixed version of the system in the expansion profile | Internal | 0 | |
| task-performer-type | The type(s) of task performers allowed | Internal | 560 | |
| task-status | The current status of the task. | Internal | 562 | |
| teeth | This value set includes the FDI Teeth codes. | Internal | 318 | |
| template-status-code | The status indicates the level of maturity of the design and may be used to manage the use of the design | Other | 384 | |
| testscript-operation-codes | This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. | Internal | 898 | |
| 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. | Internal | 558 | |
| 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. | Internal | 557 | |
| 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 | 208 | |
| timing-abbreviation | Code for a known / defined timing pattern. | V3 | 43 | |
| tooth | This value set includes a smattering of FDI oral site codes. | Internal | 313 | |
| transaction-mode | A code that indicates how transactions are supported. | Internal | 90 | |
| trigger-type | The type of trigger | Internal | 522 | |
| type-derivation-rule | How a type relates to it's baseDefinition. | Internal | 895 | |
| type-restful-interaction | Operations supported by REST at the type or instance level. | Internal | 83 | |
| ucum-bodylength | UCUM units for recording Body Length measures such as height and head circumference | FHIR | 915 | |
| ucum-bodytemp | UCUM units for recording Body Temperature | FHIR | 914 | |
| ucum-bodyweight | UCUM units for recording Body Weight | FHIR | 913 | |
| ucum-common | Commonly encountered UCUM units (for purposes of helping populate look ups. | FHIR | null | |
| ucum-units | UCUM Codes for units of measure. This value set includes all UCUM codes | FHIR | 374 | |
| ucum-vitals-common | Common UCUM units for recording Vital Signs | FHIR | 912 | |
| udi | This value set includes sample UDI codes. | Internal | 320 | |
| units-of-time | A unit of time (units from UCUM). | FHIR | 42 | |
| unknown-content-code | A code that indicates whether an application accepts unknown elements or extensions when reading resources. | Internal | 93 | |
| usage-context-type | A code the specifies a type of context being specified by a usage context | Internal | 0 | |
| 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 | use-context | |
| usps-state | This value set defines two letter USPS alphabetic codes. | Other | usps-state | |
| vaccination-protocol-dose-status | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | Internal | 166 | |
| vaccination-protocol-dose-status-reason | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example. | Internal | 167 | |
| vaccination-protocol-dose-target | The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the medication process, in particular the process and reasons for dispensing. This value set is provided as a suggestive example and includes tSNOMED CT concepts from the 64572001 (Disease) hierarchy. | SNOMED CT | 415 | |
| vaccine-code | This identifies the vaccine substance administered - CVX codes. | Internal, Other | 22 | |
| variant-state | Codes providing the status of the variant test result | Internal | 471 | |
| versioning-policy | How the system supports versioning for a resource. | Internal | 89 | |
| vision-base-codes | A coded concept listing the base codes. | Internal | 345 | |
| vision-eye-codes | A coded concept listing the eye codes. | Internal | 344 | |
| vision-product | This value set includes a smattering of Prescription Product codes. | Internal | 343 | |
| yesnodontknow | For Capturing simple yes-no-don't know answers | Other, Internal | null | |
| Name (URI = http://hl7.org/fhir/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 | .1.113883.1.11.155 |
| AcknowledgementDetailCode | OpenIssue: Missing description. | -- |
| AcknowledgementDetailType | A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300' | .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. | .1.113883.1.11.8 |
| ActClass | **** MISSING DEFINITIONS **** | .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." | .1.113883.1.11.13948 |
| ActClassDocument | Specialization of Act to add the characteristics unique to document management services. | .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. | .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 | .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. | .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. | .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. | .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. | -- |
| 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. | .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. | .1.113883.1.11.19855 |
| ActEncounterCode | Domain provides codes that qualify the ActEncounterClass (ENC) | .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. | .1.113883.1.11.16508 |
| ActInvoiceElementModifier | Processing consideration and clarification codes. | .1.113883.1.11.17704 |
| ActInvoiceGroupCode | Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. | .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. | .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. | .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. | .1.113883.1.11.10202 |
| ActPharmacySupplyType | Identifies types of dispensing events | .1.113883.1.11.16208 |
| ActPriority | A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. | -- |
| ActReason | A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law". | -- |
| ActRelationshipCheckpoint | **** MISSING DEFINITIONS **** | .1.113883.1.11.10349 |
| ActRelationshipConditional | Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred | .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. | .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. | .1.113883.1.11.10318 |
| ActRelationshipJoin | **** MISSING DEFINITIONS **** | .1.113883.1.11.10360 |
| ActRelationshipPertains | This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays. | .1.113883.1.11.10329 |
| ActRelationshipSplit | **** MISSING DEFINITIONS **** | .1.113883.1.11.10355 |
| ActRelationshipSubset | <ns1:p>Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.</ns1:p><ns1:p>Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.</ns1:p> | .1.113883.1.11.19613 |
| ActRelationshipType | The source is an excerpt from the target. | .1.113883.1.11.10317 |
| ActSite | An anatomical location on an organism which can be the focus of an act. | -- |
| ActStatus | Codes representing the defined possible states of an Act, as defined by the Act class state machine. | .1.113883.1.11.15933 |
| ActSubstanceAdminSubstitutionCode | No Description Provided | .1.113883.1.11.16621 |
| 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 | .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" | .1.113883.1.11.10642 |
| AddressUse | Codes that provide guidance around the circumstances in which a given address should be used. | .1.113883.1.11.190 |
| AdministrativeGender | The gender of a person used for adminstrative purposes (as opposed to clinical gender) | .1.113883.1.11.1 |
| AmericanIndianAlaskaNativeLanguages | American Indian and Alaska Native languages currently being used in the United States. | -- |
| Calendar | **** MISSING DEFINITIONS **** | .1.113883.1.11.17422 |
| CalendarCycle | Calendar cycle identifiers | -- |
| CalendarType | **** MISSING DEFINITIONS **** | .1.113883.1.11.10682 |
| Charset | Internet Assigned Numbers Authority (IANA) Charset Types | .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. | .1.113883.1.11.19250 |
| CommunicationFunctionType | Describes the type of communication function that the associated entity plays in the associated transmission. | .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." | .1.113883.1.11.20478 |
| CompressionAlgorithm | **** MISSING DEFINITIONS **** | .1.113883.1.11.10620 |
| Confidentiality | A set of codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality". | -- |
| ConfidentialityClassification | Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality". | .1.113883.1.11.10228 |
| ContainerCap | The type of cap associated with a container | -- |
| ContainerSeparator | A material in a blood collection container that facilites the separation of of blood cells from serum or plasma | .1.113883.1.11.14054 |
| ContentProcessingMode | Description: Identifies the order in which content should be processed. | .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). | .1.113883.1.11.16478 |
| DataOperation | **** MISSING DEFINITIONS **** | -- |
| DeviceAlertLevel | Domain values for the Device.Alert_levelCode | .1.113883.1.11.14066 |
| DocumentCompletion | Identifies the current completion state of a clinical document. | .1.113883.1.11.271 |
| DocumentSectionType | The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc. | .1.113883.1.11.10871 |
| DocumentStorage | Identifies the storage status of a document. | -- |
| EducationLevel | Years of education that a person has completed | .1.113883.1.11.19175 |
| EmployeeJobClass | **** MISSING DEFINITIONS **** | .1.113883.1.11.16036 |
| EncounterAdmissionSource | **** MISSING DEFINITIONS **** | .1.113883.1.11.12234 |
| EncounterSpecialCourtesy | **** MISSING DEFINITIONS **** | .1.113883.1.11.12242 |
| EntityClass | Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing. | .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. | .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.) | .1.113883.1.11.10884 |
| EntityClassManufacturedMaterial | Corresponds to the ManufacturedMaterial class | .1.113883.1.11.13934 |
| EntityClassOrganization | A social or legal structure formed by human beings. | .1.113883.1.11.10889 |
| EntityClassPlace | A physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant. | .1.113883.1.11.10892 |
| EntityClassRoot | Corresponds to the Entity class | .1.113883.1.11.13922 |
| EntityCode | OpenIssue: Missing description. | -- |
| EntityDeterminer | EntityDeterminer in natural language grammar is the class of words that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing. | .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. | .1.113883.1.11.10879 |
| EntityHandling | **** MISSING DEFINITIONS **** | .1.113883.1.11.13988 |
| EntityNamePartQualifier | OpenIssue: Needs description | .1.113883.1.11.15888 |
| EntityNamePartQualifierR2 | Description: The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records. | .1.113883.1.11.20323 |
| EntityNamePartType | **** MISSING DEFINITIONS **** | .1.113883.1.11.15880 |
| EntityNamePartTypeR2 | Description: Indicates whether the name part is a given name, family name, prefix, suffix, etc. | .1.113883.1.11.20322 |
| EntityNameUse | **** MISSING DEFINITIONS **** | .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. | .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. | .1.113883.1.11.16005 |
| EquipmentAlertLevel | **** MISSING DEFINITIONS **** | .1.113883.1.11.10896 |
| Ethnicity | In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both. | -- |
| ExposureMode | Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure. | -- |
| FamilyMember | A relationship between two people characterizing their "familial" relationship | .1.113883.1.11.19579 |
| GTSAbbreviation | **** MISSING DEFINITIONS **** | -- |
| GenderStatus | **** MISSING DEFINITIONS **** | .1.113883.1.11.11523 |
| GeneralPurposeOfUse | Supports communication of purpose of use at a general level. | .1.113883.1.11.20449 |
| HL7UpdateMode | The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute. | .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 | .1.113883.1.11.11017 |
| HumanLanguage | Codes for the representation of the names of human languages. | .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. | .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. | .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. | .1.113883.1.11.20428 |
| IntegrityCheckAlgorithm | **** MISSING DEFINITIONS **** | .1.113883.1.11.17385 |
| LanguageAbilityMode | A value representing the method of expression of the language. Example: Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed. OpenIssue: Description copied from Concept Domain of same name. Must be verified. | .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. | .1.113883.1.11.12199 |
| LivingArrangement | A code depicting the living arrangements of a person | -- |
| LocalMarkupIgnore | Tells a receiver to ignore just the local markup tags (local_markup, local_header, local_attr) when value="markup", or to ignore the local markup tags and all contained content when value="all" | .1.113883.1.11.10975 |
| LocalRemoteControlState | **** MISSING DEFINITIONS **** | .1.113883.1.11.10893 |
| ManagedParticipationStatus | Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine. | .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 | .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 | .1.113883.1.11.19812 |
| ModifyIndicator | **** MISSING DEFINITIONS **** | .1.113883.1.11.395 |
| NullFlavor | A collection of codes specifying why a valid value is not present. | .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. | .1.113883.1.11.20445 |
| ObservationInterpretation | One or more codes specifying a rough qualitative interpretation of the observation, such as "normal", "abnormal", "below normal", "change up", "resistant", "susceptible", etc. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Note also that this might be identical to the V2 code system of interpretation codes (formerly Abnormal Flags in older versions). | .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. | .1.113883.1.11.20423 |
| ObservationType | Identifies the kinds of observations that can be performed | .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). | .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. | .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). | .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. | .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. | .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.) | .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.). | .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.) | .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. | .1.113883.1.11.19584 |
| ParticipationType | **** MISSING DEFINITIONS **** | .1.113883.1.11.10901 |
| ParticipationVerifier | A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability. | .1.113883.1.11.10259 |
| PatientImportance | Patient VIP code | .1.113883.1.11.19265 |
| PaymentTerms | Describes payment terms for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor of an invoice. | .1.113883.1.11.14908 |
| PersonDisabilityType | A code identifying a person's disability. | -- |
| PersonalRelationshipRoleType | Types of personal relationships between two living subjects. Example: Parent, sibling, unrelated friend, neighbor | .1.113883.1.11.19563 |
| ProbabilityDistributionType | **** MISSING DEFINITIONS **** | .1.113883.1.11.10747 |
| ProcessingID | Codes used to specify whether a message is part of a production, training, or debugging system. | .1.113883.1.11.103 |
| ProcessingMode | **** MISSING DEFINITIONS **** | .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". | .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". | .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". | .1.113883.1.11.20546 |
| PurposeOfUse | Supports communication of purpose of use at a general level. | .1.113883.1.11.20448 |
| QueryParameterValue | The domain of coded values used as parameters within QueryByParameter queries. | -- |
| QueryPriority | **** MISSING DEFINITIONS **** | .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. | .1.113883.1.11.208 |
| QueryStatusCode | A code specifying the state of the Query. | .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 | .1.113883.1.11.20446 |
| RelationalOperator | **** MISSING DEFINITIONS **** | .1.113883.1.11.209 |
| RelationshipConjunction | **** MISSING DEFINITIONS **** | .1.113883.1.11.10365 |
| ReligiousAffiliation | Assigment of spiritual faith affiliation | -- |
| ResponseLevel | Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include | .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. | .1.113883.1.11.394 |
| ResponseMode | Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities. | .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. | .1.113883.1.11.11555 |
| RoleClassAgent | An entity (player) that acts or is authorized to act on behalf of another entity (scoper). | .1.113883.1.11.14006 |
| RoleClassAssociative | A general association between two entities that is neither partitive nor ontological. | .1.113883.1.11.19313 |
| RoleClassManufacturedProduct | Scoped by the manufacturer | .1.113883.1.11.11580 |
| RoleClassMutualRelationship | A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children). | .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. | .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. | .1.113883.1.11.19105 |
| RoleClassRelationshipFormal | A relationship between two entities that is formally recognized, frequently by a contract or similar agreement. | .1.113883.1.11.10416 |
| RoleClassRoot | Corresponds to the Role class | .1.113883.1.11.13940 |
| RoleClassServiceDeliveryLocation | A role played by a place at which services may be provided. | .1.113883.1.11.16927 |
| RoleClassSpecimen | A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen. | .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. | .1.113883.1.11.20413 |
| RoleLinkType | **** MISSING DEFINITIONS **** | .1.113883.1.11.11603 |
| RoleStatus | Codes representing the defined possible states of an Role, as defined by the Role class state machine. | .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. | .1.113883.1.11.20471 |
| SecurityIntegrityObservationValue | No Description Provided | .1.113883.1.11.20481 |
| SecurityPolicy | Types of security policies that further specify the ActClassPolicy value set. Examples: encrypt prohibit redisclosure without consent directive | .1.113883.1.11.20444 |
| Sequencing | Specifies sequence of sort order. | .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. | .1.113883.1.11.17660 |
| SetOperator | **** MISSING DEFINITIONS **** | .1.113883.1.11.17416 |
| SeverityObservation | Potential values for observations of severity. | .1.113883.1.11.16643 |
| SpecimenType | **** MISSING DEFINITIONS **** | -- |
| SubstanceAdminSubstitutionReason | No Description Provided | .1.113883.1.11.19377 |
| SubstitutionCondition | Identifies what sort of change is permitted or has occurred between the item that was ordered/requested and the one that was/will be provided. | -- |
| TableCellHorizontalAlign | These values are defined within the XHTML 4.0 Table Model | .1.113883.1.11.10981 |
| TableCellScope | These values are defined within the XHTML 4.0 Table Model | .1.113883.1.11.11012 |
| TableCellVerticalAlign | These values are defined within the XHTML 4.0 Table Model | .1.113883.1.11.10987 |
| TableFrame | These values are defined within the XHTML 4.0 Table Model | .1.113883.1.11.10992 |
| TableRules | These values are defined within the XHTML 4.0 Table Model | .1.113883.1.11.11002 |
| TargetAwareness | **** MISSING DEFINITIONS **** | .1.113883.1.11.10310 |
| TelecommunicationCapabilities | Description: Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address. | .1.113883.1.11.20312 |
| TimingEvent | **** MISSING DEFINITIONS **** | .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. | .1.113883.1.11.19833 |
| TribalEntityUS | INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS | -- |
| VaccineManufacturer | The manufacturer of a vaccine. | .1.113883.1.11.227 |
| VerificationMethod | No Description Provided | .1.113883.1.11.19707 |
| 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. | .1.113883.1.11.20355 |
| hl7V3Conformance | Description: Identifies allowed codes for HL7aTMs v3 conformance property. | -- |
| orderableDrugForm | OpenIssue: Missing description. | -- |
| 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. | -- |
| 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. | .1.113883.1.11.16926 |
| URI | Description | OID |
|---|
| URI (all prefixed with http://hl7.org/fhir/v2/) | ID | OID |
| 0001 | Administrative Sex | |
| 0002 | Marital Status | |
| 0003 | Event Type | |
| 0004 | Patient Class | |
| 0005 | Race | |
| 0006 | ReligionVersion Dependent. Use one of: | |
| 0007 | Admission Type | |
| 0008 | Acknowledgment code | |
| 0009 | Ambulatory Status | |
| 0012 | STOCK LOCATION | |
| 0017 | Transaction Type | |
| 0023 | Admit Source | |
| 0027 | Priority | |
| 0033 | ROUTE | |
| 0034 | SITE ADMINISTERED | |
| 0038 | Order status | |
| 0043 | Condition Code | |
| 0048 | What subject filter | |
| 0052 | Diagnosis Type | |
| 0061 | Check Digit Scheme | |
| 0062 | Event Reason | |
| 0063 | Relationship | |
| 0065 | Specimen Action Code | |
| 0066 | Employment Status | |
| 0069 | Hospital Service | |
| 0070 | Specimen Source Codes | |
| 0074 | Diagnostic Service Section ID | |
| 0076 | Message Type | |
| 0078 | Interpretation Codes | |
| 0080 | Nature of Abnormal Testing | |
| 0083 | Outlier Type | |
| 0085 | Observation Result Status Codes Interpretation | |
| 0091 | Query Priority | |
| 0092 | Re-Admission Indicator | |
| 0098 | Type of Agreement | |
| 0100 | Invocation event | |
| 0102 | Delayed acknowledgment type | |
| 0103 | Processing ID | |
| 0104 | Version ID | |
| 0105 | Source of Comment | |
| 0106 | Query/response format code | |
| 0107 | Deferred response type | |
| 0108 | Query results level | |
| 0109 | Report priority | |
| 0116 | Bed Status | |
| 0119 | Order Control Codes | |
| 0121 | Response Flag | |
| 0122 | Charge Type | |
| 0123 | Result Status | |
| 0124 | Transportation Mode | |
| 0125 | Value Type | |
| 0126 | Quantity Limited Request | |
| 0127 | Allergen Type | |
| 0128 | Allergy Severity | |
| 0130 | Visit User Code | |
| 0131 | Contact Role | |
| 0133 | Procedure Practitioner Identifier Code Type | |
| 0135 | Assignment of Benefits | |
| 0136 | Yes/no Indicator | |
| 0137 | Mail Claim Party | |
| 0140 | Military Service | |
| 0141 | Military Rank/Grade | |
| 0142 | Military Status | |
| 0144 | Eligibility Source | |
| 0145 | Room Type | |
| 0146 | Amount Type | |
| 0147 | Policy Type | |
| 0148 | Money or Percentage Indicator | |
| 0149 | Day Type | |
| 0150 | Certification Patient Type | |
| 0153 | Value Code | |
| 0155 | Accept/Application Acknowledgment Conditions | |
| 0156 | Which date/time qualifier | |
| 0157 | Which date/time status qualifier | |
| 0158 | Date/time selection qualifier | |
| 0159 | Diet Code Specification Type | |
| 0160 | Tray Type | |
| 0161 | Allow Substitution | |
| 0162 | Route of Administration | |
| 0163 | Body Site | |
| 0164 | Administration Device | |
| 0165 | Administration Method | |
| 0166 | RX Component Type | |
| 0167 | Substitution Status | |
| 0168 | Processing Priority | |
| 0169 | Reporting Priority | |
| 0170 | Derived Specimen | |
| 0173 | Coordination of Benefits | |
| 0174 | Nature of Service/Test/Observation | |
| 0175 | Master File Identifier Code | |
| 0177 | Confidentiality Code | |
| 0178 | File Level Event Code | |
| 0179 | Response Level | |
| 0180 | Record-level Event Code | |
| 0181 | MFN Record-level Error Return | |
| 0183 | Active/Inactive | |
| 0185 | Preferred Method of Contact | |
| 0187 | Provider Billing | |
| 0189 | Ethnic Group | |
| 0190 | Address Type | |
| 0191 | Type of Referenced Data | |
| 0193 | Amount Class | |
| 0200 | Name Type | |
| 0201 | Telecommunication Use Code | |
| 0202 | Telecommunication Equipment Type | |
| 0203 | Identifier Type | |
| 0204 | Organizational Name Type | |
| 0205 | Price Type | |
| 0206 | Segment Action Code | |
| 0207 | Processing Mode | |
| 0208 | Query Response Status | |
| 0209 | Relational Operator | |
| 0210 | Relational Conjunction | |
| 0211 | Alternate Character Sets | |
| 0213 | Purge Status Code | |
| 0214 | Special Program Code | |
| 0215 | Publicity Code | |
| 0216 | Patient Status Code | |
| 0217 | Visit Priority Code | |
| 0220 | Living Arrangement | |
| 0223 | Living Dependency | |
| 0224 | Transport Arranged | |
| 0225 | Escort Required | |
| 0227 | Manufacturers of Vaccines (code=MVX) | |
| 0228 | Diagnosis Classification | |
| 0229 | DRG Payor | |
| 0230 | Procedure Functional Type | |
| 0231 | Student Status | |
| 0232 | - Insurance Company Contact Reason | |
| 0234 | Report Timing | |
| 0235 | Report Source | |
| 0236 | Event Reported To | |
| 0237 | Event Qualification | |
| 0238 | Event Seriousness | |
| 0239 | Event Expected | |
| 0240 | Event Consequence | |
| 0241 | Patient Outcome | |
| 0242 | Primary Observer's Qualification | |
| 0243 | Identity May Be Divulged | |
| 0247 | Status of Evaluation | |
| 0248 | Product Source | |
| 0250 | Relatedness Assessment | |
| 0251 | Action Taken in Response to the Event | |
| 0252 | Causality Observations | |
| 0253 | Indirect Exposure Mechanism | |
| 0254 | Kind of Quantity | |
| 0255 | Duration Categories | |
| 0256 | Time Delay Post Challenge | |
| 0257 | Nature of Challenge | |
| 0258 | Relationship Modifier | |
| 0259 | Modality | |
| 0260 | Patient Location Type | |
| 0261 | Location Equipment | |
| 0262 | Privacy Level | |
| 0263 | Level of Care | |
| 0265 | Specialty Type | |
| 0267 | Days of the Week | |
| 0268 | Override | |
| 0269 | Charge On Indicator | |
| 0270 | Document Type | |
| 0271 | Document Completion Status | |
| 0272 | Document Confidentiality Status | |
| 0273 | Document Availability Status | |
| 0275 | Document Storage Status | |
| 0276 | Appointment reason codes | |
| 0277 | Appointment Type Codes | |
| 0278 | Filler status codes | |
| 0279 | Allow Substitution Codes | |
| 0280 | Referral Priority | |
| 0281 | Referral Type | |
| 0282 | Referral Disposition | |
| 0283 | Referral Status | |
| 0284 | Referral Category | |
| 0286 | Provider Role | |
| 0287 | Problem/Goal Action Code | |
| 0290 | MIME base64 encoding characters | |
| 0291 | Subtype of Referenced Data | |
| 0292 | Vaccines Administered (code = CVX) (parenteral, un | |
| 0294 | Time Selection Criteria Parameter Class Codes | |
| 0298 | CP Range Type | |
| 0299 | Encoding | |
| 0301 | Universal ID Type | |
| 0305 | Person Location Type | |
| 0309 | Coverage Type | |
| 0311 | Job Status | |
| 0315 | Living Will Code | |
| 0316 | Organ Donor Code | |
| 0317 | Annotations | |
| 0321 | Dispense Method | |
| 0322 | Completion Status | |
| 0323 | Action Code | |
| 0324 | Location Characteristic ID | |
| 0325 | Location Relationship ID | |
| 0326 | Visit Indicator | |
| 0329 | Quantity Method | |
| 0330 | Marketing Basis | |
| 0331 | Facility Type | |
| 0332 | Source Type | |
| 0334 | Disabled Person Code | |
| 0335 | Repeat Pattern | |
| 0336 | Referral Reason | |
| 0337 | Certification Status | |
| 0338 | Practitioner ID Number Type | |
| 0339 | Advanced Beneficiary Notice Code | |
| 0344 | Patient's Relationship to Insured | |
| 0350 | Occurrence Code | |
| 0351 | Occurrence Span | |
| 0353 | CWE statuses | |
| 0354 | Message Structure | |
| 0355 | Primary Key Value Type | |
| 0356 | Alternate Character Set Handling Scheme | |
| 0357 | Message Error Condition Codes | |
| 0359 | Diagnosis Priority | |
| 0360 | Degree/License/CertificateVersion Dependent. Use one of: | |
| 0363 | Assigning Authority | |
| 0364 | Comment Type | |
| 0365 | Equipment State | |
| 0366 | Local/Remote Control State | |
| 0367 | Alert Level | |
| 0368 | Remote Control Command | |
| 0369 | Specimen Role | |
| 0370 | Container Status | |
| 0371 | Additive/Preservative | |
| 0372 | Specimen Component | |
| 0373 | Treatment | |
| 0374 | System Induced Contaminants | |
| 0375 | Artificial Blood | |
| 0376 | Special Handling Code | |
| 0377 | Other Environmental Factors | |
| 0383 | Substance Status | |
| 0384 | Substance Type | |
| 0387 | Command Response | |
| 0388 | Processing Type | |
| 0389 | Analyte Repeat Status | |
| 0391 | Segment GroupVersion Dependent. Use one of: | |
| 0392 | Match Reason | |
| 0393 | Match Algorithms | |
| 0394 | Response Modality | |
| 0395 | Modify Indicator | |
| 0396 | Coding System | |
| 0397 | Sequencing | |
| 0398 | Continuation Style Code | |
| 0401 | Government Reimbursement Program | |
| 0402 | School Type | |
| 0403 | Language Ability | |
| 0404 | Language Proficiency | |
| 0406 | Organization Unit Type | |
| 0409 | Application Change Type | |
| 0411 | Supplemental Service Information Values | |
| 0415 | Transfer Type | |
| 0416 | Procedure DRG Type | |
| 0417 | Tissue Type Code | |
| 0418 | Procedure Priority | |
| 0421 | Severity of Illness Code | |
| 0422 | Triage Code | |
| 0423 | Case Category Code | |
| 0424 | Gestation Category Code | |
| 0425 | Newborn Code | |
| 0426 | Blood Product Code | |
| 0427 | Risk Management Incident Code | |
| 0428 | Incident Type Code | |
| 0429 | Production Class Code | |
| 0430 | Mode of Arrival Code | |
| 0431 | Recreational Drug Use Code | |
| 0432 | Admission Level of Care Code | |
| 0433 | Precaution Code | |
| 0434 | Patient Condition Code | |
| 0435 | Advance Directive Code | |
| 0436 | Sensitivity to Causative Agent Code | |
| 0437 | Alert Device Code | |
| 0438 | Allergy Clinical Status | |
| 0440 | Data Types | |
| 0441 | Immunization Registry Status | |
| 0442 | Location Service Code | |
| 0443 | Provider Role | |
| 0444 | Name Assembly Order | |
| 0445 | Identity Reliability Code | |
| 0450 | Event Type | |
| 0452 | Health Care Provider Type Code | |
| 0453 | Health Care Provider Classification | |
| 0454 | Health Care Provider Area of Specialization | |
| 0455 | Type of Bill Code | |
| 0456 | Revenue code | |
| 0457 | Overall Claim Disposition Code | |
| 0459 | Reimbursement Action Code | |
| 0460 | Denial or Rejection Code | |
| 0465 | Name/Address Representation | |
| 0466 | Ambulatory Payment Classification Code | |
| 0468 | Payment Adjustment Code | |
| 0469 | Packaging Status Code | |
| 0470 | - Reimbursement Type Code | |
| 0472 | TQ Conjunction ID | |
| 0473 | Formulary Status | |
| 0474 | Organization Unit Type | |
| 0475 | Charge Type Reason | |
| 0477 | Controlled Substance Schedule | |
| 0478 | Formulary Status | |
| 0480 | Pharmacy Order Types | |
| 0482 | Order Type | |
| 0483 | Authorization Mode | |
| 0484 | Dispense Type | |
| 0485 | Extended Priority Codes | |
| 0487 | Specimen Type | |
| 0488 | Specimen Collection Method | |
| 0489 | Risk Codes | |
| 0490 | Specimen Reject Reason | |
| 0491 | Specimen Quality | |
| 0492 | Specimen Appropriateness | |
| 0493 | Specimen Condition | |
| 0494 | Specimen Child Role | |
| 0495 | Body Site Modifier | |
| 0496 | Consent Type | |
| 0497 | Consent Mode | |
| 0498 | Consent Status | |
| 0499 | Consent Bypass Reason | |
| 0500 | Consent Disclosure Level | |
| 0501 | Consent Non-Disclosure Reason | |
| 0502 | Non-Subject Consenter Reason | |
| 0503 | Sequence/Results Flag | |
| 0504 | Sequence Condition Code | |
| 0505 | Cyclic Entry/Exit Indicator | |
| 0506 | Service Request Relationship | |
| 0507 | Observation Result Handling | |
| 0508 | Blood Product Processing Requirements | |
| 0510 | Blood Product Dispense Status | |
| 0511 | BP Observation Status Codes Interpretation | |
| 0513 | Blood Product Transfusion/Disposition Status | |
| 0514 | Transfusion Adverse Reaction | |
| 0516 | Error Severity | |
| 0517 | Inform Person Code | |
| 0518 | Override Type | |
| 0520 | Message Waiting Priority | |
| 0523 | Computation Type | |
| 0524 | Sequence condition | |
| 0527 | Calendar Alignment | |
| 0528 | Event Related Period | |
| 0529 | Precision | |
| 0530 | Organization, Agency, Department | |
| 0532 | Expanded Yes/no Indicator | |
| 0534 | Notify Clergy Code | |
| 0535 | Signature Code | |
| 0536 | Certificate Status | |
| 0538 | Institution Relationship Type | |
| 0540 | Inactive Reason Code | |
| 0544 | Container Condition | |
| 0547 | Jurisdictional Breadth | |
| 0548 | Signatory's Relationship to Subject | |
| 0550 | Body Parts | |
| 0553 | Invoice Control Code | |
| 0554 | Invoice Reason Codes | |
| 0555 | Invoice Type | |
| 0556 | Benefit Group | |
| 0557 | Payee Type | |
| 0558 | Payee Relationship to Invoice | |
| 0559 | Product/Service Status | |
| 0561 | Product/Services Clarification Codes | |
| 0562 | Processing Consideration Codes | |
| 0564 | Adjustment Category Code | |
| 0565 | Provider Adjustment Reason Code | |
| 0566 | Blood Unit Type | |
| 0569 | Adjustment Action | |
| 0570 | Payment Method Code | |
| 0571 | Invoice Processing Results Status | |
| 0572 | Tax status | |
| 0615 | User Authentication Credential Type Code | |
| 0616 | Address Expiration Reason | |
| 0617 | Address Usage | |
| 0618 | Protection Code | |
| 0625 | Item Status Codes | |
| 0634 | Item Importance Codes | |
| 0642 | Reorder Theory Codes | |
| 0651 | Labor Calculation Type | |
| 0653 | Date Format | |
| 0657 | Device Type | |
| 0659 | Lot Control | |
| 0667 | Device Data State | |
| 0669 | Load Status | |
| 0682 | Device Status | |
| 0702 | Cycle Type | |
| 0717 | Access Restriction Value | |
| 0719 | Access Restriction Reason Code | |
| 0725 | Mood Codes | |
| 0728 | CCL Value | |
| 0731 | DRG Diagnosis Determination Status | |
| 0734 | Grouper Status | |
| 0739 | DRG Status Patient | |
| 0742 | DRG Status Financial Calculation | |
| 0749 | DRG Grouping Status | |
| 0755 | Status Weight At Birth | |
| 0757 | DRG Status Respiration Minutes | |
| 0759 | Status Admission | |
| 0761 | DRG Procedure Determination Status | |
| 0763 | DRG Procedure Relevance | |
| 0776 | Item Status | |
| 0778 | Item Type | |
| 0790 | Approving Regulatory Agency | |
| 0793 | Ruling Act | |
| 0806 | Sterilization Type | |
| 0818 | Package | |
| 0834 | MIME Types | |
| 0868 | Telecommunication Expiration Reason | |
| 0871 | Supply Risk Codes | |
| 0881 | Role Executing Physician | |
| 0882 | Medical Role Executing Physician | |
| 0894 | Side of body | |
| 0895 | Present On Admission (POA) Indicator | |
| 0904 | Security Check Scheme | |
| 0905 | Shipment Status | |
| 0906 | ActPriority | |
| 0907 | Confidentiality | |
| 0909 | Patient Results Release Categorization Scheme | |
| 0912 | Participation | |
| 0914 | Root Cause | |
| 0916 | Relevant Clincial Information | |
| 0917 | Bolus Type | |
| 0918 | PCA Type | |
| 0919 | Exclusive Test | |
| 0920 | Preferred Specimen/Attribute Status | |
| 0921 | Certification Type Code | |
| 0922 | Certification Category Code | |
| 0923 | Process Interruption | |
| 0924 | Cumulative Dosage Limit UoM | |
| 0925 | Phlebotomy Issue | |
| 0926 | Phlebotomy Status | |
| 0927 | Arm Stick | |
| 0933 | Intended Procedure Type | |
| 0935 | Process Interruption Reason | |
| 4000 | Name/address representation |
©
HL7.org
2011+.
FHIR
STU3
Candidate
(v1.8.0-10521)
generated
on
Tue,
Dec
6,
2016
12:27+1100.
QA
Page
Links:
Search
|
Version
History
|
Table
of
Contents
|
Compare
to
DSTU2
|
|
Propose
a
change